Update build to allow for CI usage #6884
Labels
accepted
There is consensus among the team that this change meets the criteria for inclusion
archived due to age
This issue has been archived; please open a new issue for any further discussion
build
This change relates to ESLint's build process
enhancement
This change enhances an existing feature of ESLint
In order to move our builds onto Jenkins, some new npm scripts need to be introduced:
npm run ci-release
is the primary script used by our Jenkins setup to initiate a release (does the changelog generation, version calculation and tagging). The main different fromnpm run release
is that this task should not attempt to push changes back to GitHub (Jenkins handles that directly).npm run gh-release
is run after the fact to post the changelog information to a GitHub release.The current
npm run release
will still be present and still work locally as a fallback.Edit: The
gh-release
task is no longer needed thanks to figuring out an easier way to do releases on Jenkins.The text was updated successfully, but these errors were encountered: