-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Apply -snapshot suffix during build task #7317
Conversation
``` | ||
|
||
#### Debugging unit tests | ||
|
||
The standard `npm run test` task runs several sub tasks and can take several minutes to complete, making debugging failures pretty painful. In order to ease the pain specialized tasks provide alternate methods for running the tests. | ||
|
||
|
||
`npm run test:quick` | ||
`npm run test:quick` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no clue why all of these lines had spaces after them, but my editor removed them on save.
The default behavior of the build task is to now apply the -snapshot suffix dynamically rather than us manually hardcoding and managing it within the source code itself. The `--release` flag will drop the -snapshot suffix on a build, which should be used for any release candidate. The default behavior of the build task has also changed to create rpm/deb packages as well. Since we've only confirmed that this works on linux, you can override that behavior by passing `skip-os-packages`. If you do not want to create any zip or tar.gz archives, you can pass `--skip-archives`.
This isn't a huge issue, but using more than one option doesn't seem to be working: |
^ Looks like it's fixed in grunt 1.0 |
LGTM |
Yeah, it's really annoying. You need to set all but the last flag explicitly if you're doing more than one:
|
--------- **Commit 1:** Apply -snapshot suffix during build task The default behavior of the build task is to now apply the -snapshot suffix dynamically rather than us manually hardcoding and managing it within the source code itself. The `--release` flag will drop the -snapshot suffix on a build, which should be used for any release candidate. The default behavior of the build task has also changed to create rpm/deb packages as well. Since we've only confirmed that this works on linux, you can override that behavior by passing `skip-os-packages`. If you do not want to create any zip or tar.gz archives, you can pass `--skip-archives`. * Original sha: 834f563 * Authored by Court Ewing <court@epixa.com> on 2016-05-27T20:40:57Z
--------- **Commit 1:** Apply -snapshot suffix during build task The default behavior of the build task is to now apply the -snapshot suffix dynamically rather than us manually hardcoding and managing it within the source code itself. The `--release` flag will drop the -snapshot suffix on a build, which should be used for any release candidate. The default behavior of the build task has also changed to create rpm/deb packages as well. Since we've only confirmed that this works on linux, you can override that behavior by passing `skip-os-packages`. If you do not want to create any zip or tar.gz archives, you can pass `--skip-archives`. * Original sha: 834f563 * Authored by Court Ewing <court@epixa.com> on 2016-05-27T20:40:57Z
[backport] PR #7317 to 4.x - Apply -snapshot suffix during build task
Apply -snapshot suffix during build task Former-commit-id: dbfee59
The default behavior of the build task is to now apply the -snapshot
suffix dynamically rather than us manually hardcoding and managing it
within the source code itself. The
--release
flag will drop the-snapshot suffix on a build, which should be used for any release
candidate.
The default behavior of the build task has also changed to create
rpm/deb packages as well. Since we've only confirmed that this works on
linux, you can override that behavior by passing
skip-os-packages
.If you do not want to create any zip or tar.gz archives, you can pass
--skip-archives
.Closes #6941