Confirmed users
250
edits
Jetpack/Integration Process: Difference between revisions
→Testing changes: mention some steps for try failures
(→Testing changes: mention some steps for try failures) |
|||
| Line 84: | Line 84: | ||
Pushes the temporary commit to the try server, depending on your TryChooser string you should get an email telling you where to look for results. | Pushes the temporary commit to the try server, depending on your TryChooser string you should get an email telling you where to look for results. | ||
=== Failure === | |||
If the try push fails, you'll have to investigate why, and make some changes, once you've made some changes, try | |||
hg status | |||
This should show you only the files which you have changed, they should only be changes to the addon-sdk folder normally. | |||
hg addremove addon-sdk | |||
Then, you'll need to update your patch | |||
hg qrefresh -e | |||
You can test that this worked with | |||
hg status | |||
Which should have no results | |||
hg log -l 2 | |||
Should show your one patch in a queue, now you may push to try again | |||
hg push -f ssh://hg.mozilla.org/try/ | |||
=== Success === | |||
Once you're done the following converts the temporary commit to a real commit that can be pushed to the project branch: | Once you're done the following converts the temporary commit to a real commit that can be pushed to the project branch: | ||