...
The first time you push a new branch to the submission forest, you need to use the "--new-branch" option like this:
| Code Block | ||
|---|---|---|
| ||
$ #From the root of your local forest
$ hg tpush --new-branch |
Subsequent pushes to your branch in the submission forest do not need the "--new-branch" option.
If your local forest has several fixes under development and you're ready to push only one, you can do that with the "--branch" option:
| Code Block | ||
|---|---|---|
| ||
$ # From the root of your local forest
$ hg tpush --branch "JDK-4040458" --new-branch |
...
What
...
happens with my submission?
When changes are pushed to a branch in a Submission Forest, a job is created on an internal Oracle system to build and test those changes. Jobs which integrate to the same upstream forest are run sequentially in order to manage merge issues so it is possible that your job will wait for some time to get started. Once running, a successful job should take about <60> minutes to complete. Unsuccessful jobs will usually complete more quickly. When your job is finished you will get an email describing what happened. If you are subscribed to the change alias for the upstream forest, you should also see an email if your change successfully integrates upstream.
What if my submission fails?
...
You will get an email describing which of these things happened however these emails are brief. At this time we are not able to provide build or test logs which fully describe the problem. If you are unable to diagnose the problem yourself, contact an Oracle engineer and provide her with the token in your email message. They She will be able to access internal logs and help you resolve the problem.
...
Overview
Content Tools
ThemeBuilder