You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore: fix travis build of next/rc/release-patch versions
Currently the Travis build of `next`, `rc` and `release-patch` versions takes way too long as the packaging and execution of unit tests is done twice - first time from `grunt pack` execution inside the script and the second time from the npm deploy provider.
To fix this introduce new Grunt task - `travisPack` - it checks if `--travisBranch=<branch name>` is passed and in case it is one of the branches from which we'll release the package, the grunt pack task is skipped. Pass the `--travisBranch` option only to `grunt pack` command in the `.travis.yml` script section, so it will be skipped, but the one from npm deploy step will still be executed.
Also delete some unused and not needed logic.
Copy file name to clipboardExpand all lines: .travis/add-publishConfig.js
+6-12Lines changed: 6 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -16,19 +16,13 @@ if (!branch) {
16
16
process.exit(1);
17
17
}
18
18
19
-
switch(branch){
20
-
case"release":
21
-
packageDef.publishConfig.tag="rc";
22
-
break;
23
-
case"release-patch":
24
-
packageDef.publishConfig.tag="patch";
25
-
break;
26
-
case"master":
27
-
packageDef.publishConfig.tag="next";
28
-
break;
29
-
default:
30
-
thrownewError(`Unable to publish as the branch ${branch} does not have corresponding tag. Supported branches are master (next tag), release (rc tag) and release-patch (patch tag)`);
thrownewError(`Unable to publish as the branch ${branch} does not have corresponding tag. Supported branches are ${JSON.stringify(releaseBranches,null,2)}`);
0 commit comments