| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
1 parent b28f6a5 commit 75d5dce
2 files changed
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -70,7 +70,7 @@ test should *fail* before the change, and *pass* after the change. | |||
| 70 | 70 | ||
| 71 | 71 | All pull requests that modify executable code should be subjected to | |
| 72 | 72 | continuous integration tests on the | |
| 73 | - [project CI server](https://jenkins-iojs.nodesource.com/). | ||
| 73 | + [project CI server](https://ci.nodejs.org/). | ||
| 74 | 74 | ||
| 75 | 75 | ### Involving the TC | |
| 76 | 76 | ||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -11,11 +11,11 @@ Release authorization is given by the node.js TSC. Once authorized, an individua | |||
| 11 | 11 | ||
| 12 | 12 | There are three relevant Jenkins jobs that should be used for a release flow: | |
| 13 | 13 | ||
| 14 | - **a.** **Test runs:** **[iojs+any-pr+multi](https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/)** is used for a final full-test run to ensure that the current *HEAD* is stable. | ||
| 14 | + **a.** **Test runs:** **[node-test-pull-request](https://ci.nodejs.org/job/node-test-pull-request/)** is used for a final full-test run to ensure that the current *HEAD* is stable. | ||
| 15 | 15 | ||
| 16 | - **b.** **Nightly builds:** (optional) **[iojs+release](https://jenkins-iojs.nodesource.com/job/iojs+release/)** can be used to create a nightly release for the current *HEAD* if public test releases are required. Builds triggered with this job are published straight to <https://nodejs.org/download/nightly/> and are available for public download. | ||
| 16 | + **b.** **Nightly builds:** (optional) **[iojs+release](https://ci.nodejs.org/job/iojs+release/)** can be used to create a nightly release for the current *HEAD* if public test releases are required. Builds triggered with this job are published straight to <https://nodejs.org/download/nightly/> and are available for public download. | ||
| 17 | 17 | ||
| 18 | - **c.** **Release builds:** **[iojs+release](https://jenkins-iojs.nodesource.com/job/iojs+release/)** does all of the work to build all required release assets. Promotion of the release files is a manual step once they are ready (see below). | ||
| 18 | + **c.** **Release builds:** **[iojs+release](https://ci.nodejs.org/job/iojs+release/)** does all of the work to build all required release assets. Promotion of the release files is a manual step once they are ready (see below). | ||
| 19 | 19 | ||
| 20 | 20 | The [Node.js build team](https://github.com/nodejs/build) is able to provide this access to individuals authorized by the TC. | |
| 21 | 21 | ||
@@ -52,11 +52,11 @@ Notes: | |||
| 52 | 52 | ||
| 53 | 53 | ### 1. Ensure that HEAD Is Stable | |
| 54 | 54 | ||
| 55 | - Run a **[iojs+any-pr+multi](https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/)** test run to ensure that the build is stable and the HEAD commit is ready for release. | ||
| 55 | + Run a **[node-test-pull-request](https://ci.nodejs.org/job/node-test-pull-request/)** test run to ensure that the build is stable and the HEAD commit is ready for release. | ||
| 56 | 56 | ||
| 57 | 57 | ### 2. Produce a Nightly Build _(optional)_ | |
| 58 | 58 | ||
| 59 | - If there is a reason to produce a test release for the purpose of having others try out installers or specifics of builds, produce a nightly build using **[iojs+release](https://jenkins-iojs.nodesource.com/job/iojs+release/)** and wait for it to drop in <https://nodejs.org/download/nightly/>. Follow the directions and enter a proper length commit sha, a date string and select "nightly" for "disttype". | ||
| 59 | + If there is a reason to produce a test release for the purpose of having others try out installers or specifics of builds, produce a nightly build using **[iojs+release](https://ci.nodejs.org/job/iojs+release/)** and wait for it to drop in <https://nodejs.org/download/nightly/>. Follow the directions and enter a proper length commit sha, a date string and select "nightly" for "disttype". | ||
| 60 | 60 | ||
| 61 | 61 | This is particularly recommended if there has been recent work relating to the OS X or Windows installers as they are not tested in any way by CI. | |
| 62 | 62 | ||
@@ -145,7 +145,7 @@ Note that it is not essential that the release builds be created from the Node.j | |||
| 145 | 145 | ||
| 146 | 146 | ### 7. Produce Release Builds | |
| 147 | 147 | ||
| 148 | - Use **[iojs+release](https://jenkins-iojs.nodesource.com/job/iojs+release/)** to produce release artifacts. Enter the commit that you want to build from and select "release" for "disttype". | ||
| 148 | + Use **[iojs+release](https://ci.nodejs.org/job/iojs+release/)** to produce release artifacts. Enter the commit that you want to build from and select "release" for "disttype". | ||
| 149 | 149 | ||
| 150 | 150 | Artifacts from each slave are uploaded to Jenkins and are available if further testing is required. Use this opportunity particularly to test OS X and Windows installers if there are any concerns. Click through to the individual slaves for a run to find the artifacts. | |
| 151 | 151 | ||
| Back | FazBrowse Home | New Git URL |
0 commit comments