search

mozilla-releng / firefox-infra-changelog

Automated tool which builds a changelog of commits happening on git and hg that could affect Firefox CI Infra.
2 stars 8 forks source link

Update repos #423

Closed klibby closed 5 years ago

klibby commented 5 years ago

In repositories/mercurial_repositories.md, at the bottom, you have a section of "maybe" repos. Those are no longer valid, or in use. The repo you DO want, however, is https://hg.mozilla.org/hgcustom/version-control-tools/ as it controls the configuration of hgmo.

And in github_repositories.md, you should add the following:

danlabici commented 5 years ago

@klibby Thanks for pointing out the missing repos.

@mutterroland Please add the listed repositories and give them an order value above script workers, as we don't know how important they are yet, and land the code in master (no review needed). All you should do is, add them in repositories.json and make sure that the files exist in hg/git data folders.

Once that's done, don't forget to use update-files.py to push the new repos to github changelog.md

klibby commented 5 years ago

(carrying the conversation from slack back to the PR so that it's easier to track)

Interesting files/folders within the above repos...

In version-control-tools there's quite a lot, probably enough to look at it as what to exclude. I think all of the top level files can be ignored, and then ignore the following directories: vcssync, third_party, testing, docs, and git. Pretty sure the rest all contain something that could break CI.

In relops-image-builder, just about everything except the license, readme, and gitignore.

In relops-hardware-controller, gonna say that most of the top level files, plus the relops_hardware_controller directory.

In ronin_puppet, pretty much everything except the obvious top level files (readmes, etc).

mutterroland commented 5 years ago

I've finished including the requested repos into the script. As I merged #424 , I'm going to close this issue.