Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve docs for try server with non-tip mozilla-central changeset #61

Open
PaulMorris opened this issue Feb 12, 2020 · 0 comments
Open

Comments

@PaulMorris
Copy link
Contributor

Yesterday comm-central was busted when I did a try server run (which failed due to the bustage). I followed the docs to redo the try run with a mozilla-central changeset that was earlier than the one that busted comm-central. The docs could be improved for this use case.

The relevant docs are here, but they cover a different use case, and didn't work for me when I tried to follow them. I had to get some help on IRC, and what I ended up having to do is not what was described in the docs.

All I had to do was add a GECKO_HEAD_REV line to my .gecko_rev.yml file so it looked like this:

GECKO_BASE_REPOSITORY: https://hg.mozilla.org/mozilla-unified
GECKO_HEAD_REPOSITORY: https://hg.mozilla.org/mozilla-central
GECKO_HEAD_REF: default
GECKO_HEAD_REV: 7faec8e0996bce01fdd1bb9f1b2a1c60045de16c

One thing I didn't realize, since these docs don't mention it, is that you have to commit your changes to the .gecko_rev.yml file for them to take effect on the try server.

Since bustages are still common, I think it would be worth having a different section in the docs to cover this scenario.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant