Last active
April 3, 2019 01:22
-
-
Save hauleth/1aa37e804991a43ddba872795d823fa9 to your computer and use it in GitHub Desktop.
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
## Build | |
build: | |
stage: build | |
tags: | |
- elixir | |
script: | |
- eval $(ssh-agent -s) | |
- echo "$SSH_BUILD_KEY" | tr -d '\r' | ssh-add - | |
- git branch -f master HEAD | |
- mix edeliver build release --revision="$CI_BUILD_REF" --auto-version=revision | |
## Deploy | |
deploy:staging: | |
stage: deploy | |
environment: staging | |
tags: | |
- elixir | |
script: | |
- eval $(ssh-agent -s) | |
- echo "$SSH_DEPLOY_STAGING_KEY" | tr -d '\r' | ssh-add - | |
- mix edeliver deploy release to staging --version="$VERSION" | |
- mix edeliver stop staging | |
- mix edeliver start staging | |
- mix edeliver migrate staging | |
when: manual | |
How do u check that proper version of
edeliver
exists on CI?
edeliver should be the latest version in your deps. you can just run mix deps.get
to get that version that your mix lock file is pinned to.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How do u check that proper version of
edeliver
exists on CI?