This repository was archived by the owner on Apr 2, 2024. It is now read-only.
Provision staging when merging into master #104
Merged
Conversation
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
sauloperez
force-pushed
the
stage-after-merge-into-master
branch
from
2cbeae9 to
bcc45b6
Compare
This way we skip the manual step. We always want the staging server in sync with master so we can test things in a production-like environment. To do that, we need to add an encrypted file to Travis containing the vault's password.
Unfortunatley, Travis does not support encrypting multiple files (see: travis-ci/travis.rb#239) and although it's been solved in travis-ci/travis.rb#678 there's still no release including it. I followed the documentation at https://docs.travis-ci.com/user/encrypting-files/?source=post_page---------------------------#encrypting-multiple-files and encrypted a tar file that contains all files: the deployment private key and the vault password file. Yet another reason to switch to an alternative like Circe CI or GitLab...
sauloperez
force-pushed
the
stage-after-merge-into-master
branch
from
bcc45b6 to
e94ea0b
Compare
|
travis-ci/travis.rb#627 (comment) might be another workaround |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This way we skip the manual step. We always want the staging server in sync with master so we can test things in a production-like environment.
EDIT
Unfortunatley, Travis does not support encrypting multiple files (see: travis-ci/travis.rb#239) and although it's been solved in travis-ci/travis.rb#678 there's still no release including it. I followed the documentation at https://docs.travis-ci.com/user/encrypting-files/?source=post_page---------------------------#encrypting-multiple-files and encrypted a tar file that contains all files: the deployment private key and the vault password file.
Yet another reason to switch to an alternative like Circe CI or GitLab...