Release task now always publishes to staging#7500
Merged
epixa merged 1 commit intoelastic:masterfrom Jun 17, 2016
Merged
Conversation
Production builds should never be published directly from a local machine. Instead, the release command will now publish to a commit-specific staging URL, so you use it to publish a release candidate, and then when those builds have been verified, you need to copy the RC builds from on the staging location on s3 to the production folder.
Contributor
|
LGTM |
epixa
added a commit
that referenced
this pull request
Jul 22, 2016
--------- **Commit 1:** Release task now always publishes to staging Production builds should never be published directly from a local machine. Instead, the release command will now publish to a commit-specific staging URL, so you use it to publish a release candidate, and then when those builds have been verified, you need to copy the RC builds from on the staging location on s3 to the production folder. * Original sha: 1e2c953 * Authored by Court Ewing <court@epixa.com> on 2016-06-17T18:26:08Z
epixa
added a commit
that referenced
this pull request
Jul 22, 2016
[backport] PR #7500 to 4.x - Release task now always publishes to staging
airow
pushed a commit
to airow/kibana
that referenced
this pull request
Feb 16, 2017
Release task now always publishes to staging Former-commit-id: 2074195
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Production builds should never be published directly from a local
machine. Instead, the release command will now publish to a
commit-specific staging URL, so you use it to publish a release
candidate, and then when those builds have been verified, you need to
copy the RC builds from on the staging location on s3 to the production
folder.
Or if you're not set up with fpm and such:
You can release snapshot builds as well, but this is not the mechanism used by our automatic snapshot process. Any snapshot builds released in this way will periodically be deleted.