Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build: Updates to the release process #13597

Merged
merged 2 commits into from
Jul 10, 2018
Merged

build: Updates to the release process #13597

merged 2 commits into from
Jul 10, 2018

Conversation

jkleinsc
Copy link
Contributor

@jkleinsc jkleinsc commented Jul 9, 2018

This PR includes two updates to our release process:

  1. Adds support for running the 32-bit and 64-bit AppVeyor release builds as separate builds. The builds have already been split into separate builds, but the release process needs to be updated to accommodate this change.

  2. The upload script (script/upload.py) used by the release process was using an old python module to get the release information from GitHub. It also used this module to create the release if it didn't exist. This release creation isn't necessary anymore as script/prepare-release.js does this work. Also, in the last couple of releases, there was an issue where this ended up creating extra releases and uploading the files to the wrong release. This PR changes to use a new node script script/find-release.js to find the release instead.

Checklist
  • PR description included and stakeholders cc'd
  • npm test passes
  • commit messages or PR title follow semantic commit guidelines

@jkleinsc jkleinsc requested review from a team and ckerr July 9, 2018 23:02
John Kleinschmidt added 2 commits July 10, 2018 09:40
AppVeyor builds got split into two jobs, `electron-x64` and `electron-ia32`
Our upload script was relying on an old python script to find the GitHub release for uploading.
@jkleinsc jkleinsc merged commit 4ebe716 into master Jul 10, 2018
@trop
Copy link
Contributor

trop bot commented Jul 10, 2018

An error occurred while attempting to backport this PR to "2-0-x", you will need to perform this backport manually

@trop
Copy link
Contributor

trop bot commented Jul 10, 2018

We have automatically backported this PR to "3-0-x", please check out #13612

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants