{"id":3485,"date":"2017-04-25T16:00:22","date_gmt":"2017-04-25T14:00:22","guid":{"rendered":"https:\/\/florianbrinkmann.com\/en\/?p=3485"},"modified":"2020-02-09T10:59:52","modified_gmt":"2020-02-09T09:59:52","slug":"deployment-travis-ci","status":"publish","type":"post","link":"https:\/\/florianbrinkmann.com\/en\/deployment-travis-ci-3485\/","title":{"rendered":"Auto deployment to staging and production server with Travis CI"},"content":{"rendered":"\n

Two weeks ago I wrote a post about deployment via GitLab<\/a>. Now I realized the same behavior for a public GitHub repository with Travis, and this post shows you how I did it.<\/p>\n\n\n\n\n\n\n\n

The goal was, like already said, the same like in the GitLab post \u2014 I wanted to move a theme to the staging or production server, depending on if the push goes to staging<\/code> or master<\/code> branch. Travis CI<\/a> is free for public GitHub repos.<\/p>\n\n\n\n

Travis works with a .travis.yml<\/code> file, which stores the CI steps. The finished file looks like that:<\/p>\n\n\n

language: php\n\naddons:\n  ssh_known_hosts:\n  - $STAGING_SERVER\n  - $PRODUCTION_SERVER\n\nbefore_script:\n  - echo<\/span> -e \"Host $STAGING_SERVERntStrictHostKeyChecking non\"<\/span> >> ~\/.ssh\/config\n  - echo<\/span> -e \"Host $PRODUCTION_SERVERntStrictHostKeyChecking non\"<\/span> >> ~\/.ssh\/config\n\nscript:\n  -\nbefore_deploy:\n  - openssl aes-256<\/span>-cbc -K $ENCRYPTED_KEY -iv $ENCRYPTED_IV -in deploy_rsa.enc -out \/tmp\/deploy_rsa -d\n  - eval<\/span> \"$(ssh-agent -s)\"<\/span>\n  - chmod 600<\/span> \/tmp\/deploy_rsa\n  - ssh-add \/tmp\/deploy_rsa\n\ndeploy:\n  - provider: script\n    skip_cleanup: true<\/span>\n    script: ssh -p22 $STAGING_SERVER_USER@$STAGING_SERVER \"mkdir -p $STAGING_PATH_STABLE\"<\/span> && ssh -p22 $STAGING_SERVER_USER@$STAGING_SERVER \"mkdir -p $STAGING_PATH_TRUNK\"<\/span> && rsync -rav -e ssh --exclude='.git\/'<\/span> --exclude=scripts\/ --exclude='.travis.yml'<\/span> --delete-excluded .\/ $STAGING_SERVER_USER@$STAGING_SERVER:$STAGING_PATH_TRUNK && rsync -rav -e ssh --exclude='.git\/'<\/span> --exclude=scripts\/ --exclude='.travis.yml'<\/span> --delete-excluded .\/ $STAGING_SERVER_USER@$STAGING_SERVER:$STAGING_PATH_STABLE\n    on:\n      branch: staging\n  - provider: script\n    skip_cleanup: true<\/span>\n    script: ssh -p22 $PRODUCTION_SERVER_USER@$PRODUCTION_SERVER \"mkdir -p $PRODUCTION_SERVER_THEMES_PATH\/_tmp-bornholm\"<\/span>&& ssh -p22 $PRODUCTION_SERVER_USER@$PRODUCTION_SERVER \"mkdir -p $PRODUCTION_SERVER_THEMES_PATH\/bornholm\"<\/span> && rsync -rav -e ssh --exclude='.git\/'<\/span> --exclude=scripts\/ --exclude='.travis.yml'<\/span> --delete-excluded .\/ $PRODUCTION_SERVER_USER@$PRODUCTION_SERVER:$PRODUCTION_SERVER_THEMES_PATH\/_tmp-bornholm && ssh -p22 $PRODUCTION_SERVER_USER@$PRODUCTION_SERVER \"mv $PRODUCTION_SERVER_THEMES_PATH\/bornholm $PRODUCTION_SERVER_THEMES_PATH\/_old-bornholm && mv $PRODUCTION_SERVER_THEMES_PATH\/_tmp-bornholm $PRODUCTION_SERVER_THEMES_PATH\/bornholm\"<\/span> && ssh -p22 $PRODUCTION_SERVER_USER@$PRODUCTION_SERVER \"rm -rf $PRODUCTION_SERVER_THEMES_PATH\/_old-bornholm\"<\/span>\n    on:\n      branch: master<\/code><\/div>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Be careful not to write sensitive data directly into the file, but use the Travis variables as the file is publicly in the GitHub repo!<\/strong><\/p>\n\n\n\n
After that we prevent that we need to confirm the fingerprint of the unknown server<\/a> in the before_script<\/code> part. If no script<\/code> is defined, Travis runs a default procedur depending on the choosen language (for example PHPunit for PHP) \u2013 we only want a deployment, so we set an empty script.<\/p>\n\n\n\n
How to get ready for the SSH connection is described in the post \u00bbSSH deploys with Travis CI<\/a>\u00ab on oncletom.io (the encryption does not work without problems on Windows, you can use the Windows Subsystem for Linux on Windows 10. The command I needed to get it working are listed at the end of the post) \u2014 the result is our before_deploy<\/code>.<\/p>\n\n\n\n
The deploy<\/code> part has two sub areas \u2014 one for staging<\/code> and one for master<\/code>. The script:<\/code> commands are mostly the same as in the GitLab deployment post<\/a>.<\/p>\n\n\n\n
Steps for encrypting the SSH key on Windows with the Subsystem for Linux<\/strong> (run in the git repository directory):<\/p>\n\n\n
apt-get<\/span> install ruby-dev\ngem install travis -v 1.8.8 --no-rdoc --no-ri\nsudo travis login\nssh-keygen -t rsa -b 4096 -C 'build@travis-ci.org' -f .\/deploy_rsa\nsudo travis encrypt-file deploy_rsa --add<\/code><\/div>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
After that you add the public key to your server and remove the key files (do not leave them in the repository and accidently push them to GitHub!):<\/p>\n\n\n
rm<\/span> -f<\/span> deploy_rsa<\/span> deploy_rsa<\/span>.pub<\/span><\/code><\/div>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>","protected":false},"excerpt":{"rendered":"
Two weeks ago I wrote a post about deployment via GitLab. Now I realized the same behavior for a public GitHub repository with Travis, and this post shows you how I did it.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","wpf_show_in_dewp_planet_feed":false,"flobn_post_versions":"","lazy_load_responsive_images_disabled":false},"categories":[6],"tags":[],"wp-worthy-pixel":{"ignored":false,"public":"ceef17546a2544b09f78ace29a29336c","server":"vg07.met.vgwort.de","url":"https:\/\/vg07.met.vgwort.de\/na\/ceef17546a2544b09f78ace29a29336c"},"wp-worthy-type":"normal","_links":{"self":[{"href":"https:\/\/florianbrinkmann.com\/en\/wp-json\/wp\/v2\/posts\/3485"}],"collection":[{"href":"https:\/\/florianbrinkmann.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/florianbrinkmann.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/florianbrinkmann.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/florianbrinkmann.com\/en\/wp-json\/wp\/v2\/comments?post=3485"}],"version-history":[{"count":3,"href":"https:\/\/florianbrinkmann.com\/en\/wp-json\/wp\/v2\/posts\/3485\/revisions"}],"predecessor-version":[{"id":5895,"href":"https:\/\/florianbrinkmann.com\/en\/wp-json\/wp\/v2\/posts\/3485\/revisions\/5895"}],"wp:attachment":[{"href":"https:\/\/florianbrinkmann.com\/en\/wp-json\/wp\/v2\/media?parent=3485"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/florianbrinkmann.com\/en\/wp-json\/wp\/v2\/categories?post=3485"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/florianbrinkmann.com\/en\/wp-json\/wp\/v2\/tags?post=3485"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
At first, we set php<\/code> as the language of our project and add the server addresses to the known_hosts<\/code>, like described in the docu post \u00bbAdding to SSH Known Hosts<\/a>\u00ab \u2014 the variables can be set under Settings in the repo in Travis.<\/p>\n\n\n\n