13 nightly. In the userland consolidation, developers will commit changes to the |
13 nightly. In the userland consolidation, developers will commit changes to the |
14 integration gate. These changes will not be accepted until some basic |
14 integration gate. These changes will not be accepted until some basic |
15 validation is performed. Once the validation completes successfully, the |
15 validation is performed. Once the validation completes successfully, the |
16 changes are accepted and pushed into the canonical source gate. |
16 changes are accepted and pushed into the canonical source gate. |
17 |
17 |
18 Integration repository (ssh://[email protected]//nevada/incoming) |
18 Integration repository (ssh://[email protected]//gates/incoming) |
19 The integration gate is the Mercurial repository that all tools, source |
19 The integration gate is the Mercurial repository that all tools, source |
20 code, and build recipies are committed to. Unlike ON, SFW, and other |
20 code, and build recipies are committed to. Unlike ON, SFW, and other |
21 Solaris gates this source code repository does not contains the canonical |
21 Solaris gates this source code repository does not contains the canonical |
22 source for the product. This repository is a staging area for change |
22 source for the product. This repository is a staging area for change |
23 integration and acceptance. |
23 integration and acceptance. |
62 incremental build on all architectures |
62 incremental build on all architectures |
63 unit test on all architectures |
63 unit test on all architectures |
64 package publication for all architectures |
64 package publication for all architectures |
65 |
65 |
66 |
66 |
67 Canonical source repository (ssh://[email protected]//nevada/gate) |
67 Canonical source repository (ssh://[email protected]//gates/gate) |
68 The clone gate is actually the mercurial repository that contains the |
68 The clone gate is actually the mercurial repository that contains the |
69 canonical tools, source code, and build recipies for the product. It |
69 canonical tools, source code, and build recipies for the product. It |
70 should always be in a stable, buildable state. When changes are pushed |
70 should always be in a stable, buildable state. When changes are pushed |
71 to this gate, they are mirrored on the external mirror repository from |
71 to this gate, they are mirrored on the external mirror repository from |
72 here. |
72 here. |
78 | |
78 | |
79 v |
79 v |
80 notify gatelings |
80 notify gatelings |
81 |
81 |
82 |
82 |
83 External mirror repository (ssh://[email protected]//hg/userland/gate) |
83 External mirror repository (https://hg.java.net/hg/solaris-userland~gate) |
84 The external mirror is the mercurial repository that contains an externally |
84 The external mirror is the mercurial repository that contains an externally |
85 accessible copy of the canonical tools, source code, and build recipies for |
85 accessible copy of the canonical tools, source code, and build recipies for |
86 the product. It should always be in a stable, buildable state. |
86 the product. It should always be in a stable, buildable state. |
87 |
87 |
88 external mirror update |
88 external mirror update |