#!/usr/bin/env bash set -ex apt-get install curl -y sudo -Hiu jenkins gpg --keyserver hkp://keys.gnupg.net --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3 sudo -Hiu jenkins bash -c 'curl -sSL https://get.rvm.io | bash -s head' sudo -Hiu jenkins bash -c "echo '[[ -s /var/lib/jenkins/.rvm/scripts/rvm ]] && source /var/lib/jenkins/.rvm/scripts/rvm' >> /var/lib/jenkins/.bashrc" cat << "END" > /var/lib/jenkins/.rvmrc rvm_install_on_use_flag=1 rvm_project_rvmrc=1 rvm_gemset_create_on_use_flag=1 END chown jenkins /var/lib/jenkins/.rvmrc
| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #1 | 15741 | ptomiak | Branch HWS for my use. | ||
| //guest/perforce_software/helix-web-services/main/infrastructure/shell/install_rvm_jenkins.sh | |||||
| #1 | 15623 | tjuricek |
Add infrastructure project. This project should allow any team to setup a CD environment locally using VMWare products. A 'build' workflow will run tests, generate installers, etc, on a Jenkins instance configured with necessary plugins. A later 'release' workflow will initially push successful runs into the 'build/' directory of the branch in the workshop. (A 'production release' will use that data and push it into internal infrastructure for package signing and hosting.) Documentation will be written. This is a large set of files, so I wanted to submit them where my connection to the workshop server is faster. |
||