Skip to content

[grunt] Task to rebuild archives with new version#7225

Merged
epixa merged 1 commit intoelastic:masterfrom
epixa:repackage
May 18, 2016
Merged

[grunt] Task to rebuild archives with new version#7225
epixa merged 1 commit intoelastic:masterfrom
epixa:repackage

Conversation

@epixa
Copy link
Copy Markdown
Contributor

@epixa epixa commented May 17, 2016

This is useful for when a pre-release build is completely tested and
could be released as-is if it weren't for the pre-release suffix and
commit hash. It will extract the archives in the target, replace the
version, sha, and build numbers with the current working copy's, and
then recreate the archives and shas.

@epixa epixa added the review label May 17, 2016
@epixa epixa self-assigned this May 17, 2016
@epixa epixa removed the review label May 17, 2016
This is useful for when a pre-release build is completely tested and
could be released as-is if it weren't for the pre-release suffix and
commit hash. It will extract the archives in the target, replace the
version, sha, and build numbers with the current working copy's, and
then recreate the archives and shas.
@epixa epixa added the review label May 17, 2016
@epixa epixa assigned jbudz and unassigned epixa May 17, 2016
@jbudz
Copy link
Copy Markdown
Contributor

jbudz commented May 18, 2016

example: node_modules/.bin/grunt rebuild --buildsha="abc123" --buildnum="91" --buildversion="10.1.1" --skip-archives

@jbudz
Copy link
Copy Markdown
Contributor

jbudz commented May 18, 2016

LGTM
edit: one comment, but don't want it to block

import { join } from 'path';

export default (grunt) => {
grunt.registerTask('_rebuild:createArchives', function () {
Copy link
Copy Markdown
Contributor

@jbudz jbudz May 18, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

would it make sense to reuse _build:archives instead?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I originally tried to go down that route, but it would have required pretty fundamental changes to _build:archives, so I decided against it. Basically, _build:archives assumes that all platforms are present in the build directory (something not guaranteed in a rebuild) and that all builds have the same version as the current working copy's package.json (something not true if you're using the buildversion argument).

@jbudz jbudz assigned epixa and unassigned jbudz May 18, 2016
@epixa epixa merged commit d117d7c into elastic:master May 18, 2016
@epixa epixa deleted the repackage branch May 18, 2016 18:51
@epixa epixa mentioned this pull request Jul 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants