PATH remote: . specs: jenkins_workflow (0.1.0) jenkins_api_client (~> 1.4) rubyzip (~> 1.1) thor (~> 0.19) GEM remote: https://rubygems.org/ specs: jenkins_api_client (1.4.0) json mixlib-shellout (>= 1.1.0) nokogiri (~> 1.6.0) terminal-table (>= 1.4.0) thor (>= 0.16.0) json (1.8.3) mini_portile (0.6.2) mixlib-shellout (2.2.0) nokogiri (1.6.6.2) mini_portile (~> 0.6.0) rake (10.4.2) rubyzip (1.1.7) terminal-table (1.5.2) thor (0.19.1) PLATFORMS ruby DEPENDENCIES bundler (~> 1.10) jenkins_workflow! rake (~> 10.0) BUNDLED WITH 1.10.6
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#1 | 15688 | Doug Scheirer |
Populate -o //guest/perforce_software/helix-web-services/... //guest/doug_scheirer/helix-web-services/.... |
||
//guest/perforce_software/helix-web-services/main/infrastructure/jenkins_workflow/Gemfile.lock | |||||
#2 | 15675 | tjuricek |
Add basic 'publish' step for Jenkins jobs. This will archive files in a local workspace. The exact automated workflow hasn't been ironed out yet. |
||
#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. |