Repo dependency archived #196

New issue

Open

opened 2020-09-21 16:18:58 -07:00 by luciusbono · 1 comment

luciusbono commented

2020-09-21 16:18:58 -07:00

(Migrated from github.com)

This is not a well documented feature, but I noticed today that the informant repo had been archived. I recommend that this repo be reinstated and ownership transferred to @jlin or someone else in EUS.

This repo is just a simple text file that the Corsica auto-update scripts reference to make sure it's ok to continue to automatically update on a nightly basis. See relevant code:
mozilla/dinobuildr@1f8f112731/resources/corsica/auto-update.sh (L14)

If the script does not see the string "greenlight" in the upstream text file, it will not run softwareupdate -ia and the machine will not automatically get software updates. The intent of this feature is to allow some machines to act as a "canary" in order to live-test new operating system versions. If an OS version introduced a breaking change, someone with access to the informant repo could change the text file (to say literally anything other than greenlight) and the fleet would cease updating until the issue was resolved.

Feel free to reach out to me here, via e-mail or on keybase if you want to discuss this further: https://keybase.io/kingmetal

This is not a well documented feature, but I noticed today that the [informant](https://github.com/mozilla-it/informant) repo had been archived. I recommend that this repo be reinstated and ownership transferred to @jlin or someone else in EUS. This repo is just a simple text file that the Corsica auto-update scripts reference to make sure it's ok to continue to automatically update on a nightly basis. See relevant code: https://github.com/mozilla/dinobuildr/blob/1f8f112731dd09883771a4ff730658f884b7996f/resources/corsica/auto-update.sh#L14 If the script does not see the string "greenlight" in the upstream text file, it will not run `softwareupdate -ia` and the machine will not automatically get software updates. The intent of this feature is to allow some machines to act as a "canary" in order to live-test new operating system versions. If an OS version introduced a breaking change, someone with access to the informant repo could change the text file (to say literally anything other than `greenlight`) and the fleet would cease updating until the issue was resolved. Feel free to reach out to me here, via e-mail or on keybase if you want to discuss this further: https://keybase.io/kingmetal

jlin commented

2020-09-24 12:21:12 -07:00

(Migrated from github.com)

Thanks lucius! hope you are doing ok!!

I'll bundle this into a request to get access to the https://github.com/mozilla/macos-desktop/ repo - into which we have dependencies and need access rights to.

Thanks lucius! hope you are doing ok!! I'll bundle this into a request to get access to the https://github.com/mozilla/macos-desktop/ repo - into which we have dependencies and need access rights to.