From b77467ca8f4ceafecddafd054bcd696bb02fe4c6 Mon Sep 17 00:00:00 2001 From: John Kleinschmidt Date: Fri, 29 Sep 2017 16:11:42 -0400 Subject: [PATCH] Update CI information (#10644) * Update CI information * Formatting updates --- docs/development/releasing.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/development/releasing.md b/docs/development/releasing.md index b767150ba425..514c9951a1c1 100644 --- a/docs/development/releasing.md +++ b/docs/development/releasing.md @@ -56,8 +56,9 @@ will [trigger the release process](https://github.com/electron/electron/blob/796 To monitor the build progress, see the following pages: -- [208.52.191.140:8080/view/All/builds](http://208.52.191.140:8080/view/All/builds) for Mac and Windows -- [jenkins.githubapp.com/label/chromium/](https://jenkins.githubapp.com/label/chromium/) for Linux +- [208.52.191.140:8080/view/All/builds](http://208.52.191.140:8080/view/All/builds) for Mac +- [circleci.com/gh/electron](https://circleci.com/gh/electron) for Linux +- [windows-ci.electronjs.org/project/AppVeyor/electron](https://windows-ci.electronjs.org/project/AppVeyor/electron) for Windows ## Compile release notes @@ -237,8 +238,8 @@ Then edit the release on GitGub: In the case of a corrupted release with broken CI machines, we might have to re-upload the binaries for an already published release. -The first step is to go to the -[Releases](https://github.com/electron/electron/releases) page and delete the +The first step is to go to the +[Releases](https://github.com/electron/electron/releases) page and delete the corrupted binaries with the `SHASUMS256.txt` checksum file. Then manually create distributions for each platform and upload them: @@ -261,4 +262,4 @@ file: ```sh npm run release -``` \ No newline at end of file +```