Introducing FirefoxCI Changelog

[Danut Labici]

Hi all,


If you care about Firefox CI then this mail might be of interest to you.

The CiDuty team has been working on an automated tool[1] which builds a
changelog of commits across repos affecting Firefox CI.


How does it work?

*

A .json and .md file is generated for every git and hg repository
that we currently track[2]

*

If any commit is deemed infra-affecting and is in production, an
entry is added to each respective json and md file.

*

A "main" changelog.mdfile is also generated to easily see the
commits of the last 24 hours, this can be changed by the user.

*

Can track preconfigured directories within a repository. This is
useful for monolithic repositories like gecko

*

Determines what is actually in production by preconfiguring a
“production” branch, watching version tags, or even monitoring
version bumps in places such as a puppet file.


CiDuty successfully used this tool to identify which commit caused the
W10 workers to break in January 2019.


Although it is in a working state, we will continuously be adding
improvements. We hope this will help other teams the way it helped
CiDuty thus far.


If you happen to encounter an error or you have a question please take a
look at the current open issues[3] and contact CiDuty if your
problem/question isn’t covered in any of them.


If you would like to use it, you can quickly see changes over the last
24h by monitoring this url:
https://github.com/mozilla-releng/firefox-infra-changelog/blob/master/changelog.md

A good idea would be to bookmark it.


[1]https://github.com/mozilla-releng/firefox-infra-changelog

[2] we are interested in adding more repositories and directories to
watch. E.g. build sys and test harness automation:
https://github.com/mozilla-releng/firefox-infra-changelog/tree/master/repositories

[3] https://github.com/mozilla-releng/firefox-infra-changelog/issues


-- The CiDuty Team

[Sebastian Hengst]

Hi,

thanks to the CiDuty team for implementing this.

-- Sebastian

> --
> You received this message because you are subscribed to the Google
> Groups "firefox-ci" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to firefox-ci+...@mozilla.com
> <mailto:firefox-ci+...@mozilla.com>.
> To post to this group, send email to firef...@mozilla.com
> <mailto:firef...@mozilla.com>.
> To view this discussion on the web visit
> https://groups.google.com/a/mozilla.com/d/msgid/firefox-ci/9b7d46dc-e489-d08d-57be-d5b3501f2a80%40mozilla.com
> <https://groups.google.com/a/mozilla.com/d/msgid/firefox-ci/9b7d46dc-e489-d08d-57be-d5b3501f2a80%40mozilla.com?utm_medium=email&utm_source=footer>.
>
> _______________________________________________
> Sheriffs mailing list
> Sher...@mozilla.org
> https://mail.mozilla.org/listinfo/sheriffs
>

[Dustin Mitchell]

This is really cool -- nice work!

As we shift toward new deployments of Taskcluster, we'll be deploying a
single revision of the TC repo as a unit. That's similar to what a puppet
run does, for example. I wonder if it would make sense to have some way of
signalling that such a deployment took place? An API method where I can
post {"service": "taskcluster.prod.mozaws.net", "revision": "abcd"} or the
like? Then the Changelog service can figure out which revisions went into
production in which environment at which time. We could also send a pulse
message if that would be easier, or even make some kind of automated commit
to a git repo.

Dustin

On Wed, Feb 13, 2019 at 10:12 AM Danut Labici <dla...@mozilla.com> wrote:

> Hi all,
>
> If you care about Firefox CI then this mail might be of interest to you.
>
> The CiDuty team has been working on an automated tool[1] which builds a
> changelog of commits across repos affecting Firefox CI.
>
> How does it work?
>

> -

>
> A .json and .md file is generated for every git and hg repository that
> we currently track[2]

> -

>
> If any commit is deemed infra-affecting and is in production, an entry
> is added to each respective json and md file.

> -
>
> A "main" changelog.md file is also generated to easily see the commits

> of the last 24 hours, this can be changed by the user.

> -

>
> Can track preconfigured directories within a repository. This is
> useful for monolithic repositories like gecko

> -

> email to firefox-ci+...@mozilla.com.
> To post to this group, send email to firef...@mozilla.com.