You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered:
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: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.
The text was updated successfully, but these errors were encountered: