Created
August 27, 2016 15:14
-
-
Save DennisAlund/4285f7d9e8ea306e967820f1e439aa4e to your computer and use it in GitHub Desktop.
Automatic deployment of Google App Engine project with Gitlab Continuous Integration - https://medium.com/evenbit/an-easy-guide-to-automatically-deploy-your-google-app-engine-project-with-gitlab-ci-48cb84757125
This file contains 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
image: python:2.7 | |
before_script: | |
- echo "deb http://packages.cloud.google.com/apt cloud-sdk-jessie main" | tee /etc/apt/sources.list.d/google-cloud-sdk.list | |
- curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key add - | |
- apt-get update && apt-get install google-cloud-sdk | |
after_script: | |
- rm /tmp/$CI_PIPELINE_ID.json | |
deploy_production: | |
stage: deploy | |
environment: Production | |
only: | |
- master | |
script: | |
- echo $DEPLOY_KEY_FILE_PRODUCTION > /tmp/$CI_PIPELINE_ID.json | |
- gcloud auth activate-service-account --key-file /tmp/$CI_PIPELINE_ID.json | |
- gcloud --quiet --project $PROJECT_ID_PRODUCTION app deploy |
@davux Thanks man, this seemed to work!
instead of using the before script to install the google-cloud-sdk, it's possible to use image: google/cloud-sdk
if you're running this on gitlab.com
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@bgold0, that's because the
apt-get install
step didn't work, so the job went frompre_script
topost_script
. As a result, the JSON file was never created sorm
failed. If you useapt-get install -y
it will be fixed. At any rate, if you don't want therm
bit to fail unnecessarily you can also change it to[ -e /tmp/$CI_PIPELINE_ID.json ] && rm /tmp/$CI_PIPELINE_ID.json
.