Skip to content

Instantly share code, notes, and snippets.

View bowrocker's full-sized avatar

Jon Anderson bowrocker

  • Fastly
  • Massachusetts
View GitHub Profile

Feedback on delivery-cluster installation documentation

  1. [Prerequisites/ Supported OSs]: These could be broken out for clarity. Build nodes, delivery server, provisioning node, etc. It is implied below that OSX is supported for the provision node, but not mentioned here.
  2. [Prerequisites]: Verbiage describing Chef Delivery could a little more wide-ranging perhaps? Not sure it's important to mention the implementation language, etc., i.e.:

|chef delivery| is comprised of: a server that manages and visualizes the software change lifecycle through the Continuous Delivery process; build nodes that run tests and build articfacts; as well as a CLI that interfaces with the server, source control and does job control. The Delivery server hosts projects' version control using an embedded Git server, coordinates builds and tests on build nodes via push jobs, visualizes pipeline status and progress, as well as providing code review tools, and administration interfaces.

Pipelines are composed of a series of stag

# INCIDENT DATE - INCIDENT TYPE
## Meeting
TBD
#### Start every PM stating the following
1. This is a blameless Post Mortem.
2. We will not focus on the past events as they pertain to "could've", "should've", etc.
PS C:\Users\Administrator\delivery\workspace\bin> ruby delivery-cmd eyJlbnRlcnByaXNlIjoiQ2hlZiIsIm9yZ2FuaXphdGlvbiI6IkNo
ZWZfRGVsaXZlcnkiLCJwcm9qZWN0IjoiZGVsaXZlcnktY2xpIiwicGlwZWxpbmUiOiJtYXN0ZXIiLCJjaGFuZ2VfaWQiOiIyYjc0MWJhNC05ZmVhLTQxZjQt
ODg0Zi1mNjBlNTQzMDI1NTUiLCJwYXRjaHNldF9udW1iZXIiOjQsInN0YWdlIjoidmVyaWZ5Iiwic3RhZ2VfcnVuX2lkIjo5MzUwLCJwaGFzZSI6InVuaXQi
LCJwaGFzZV9ydW5faWQiOjM1Mzc5LCJnaXRfdXJsIjoic3NoOi8vYnVpbGRlckBDaGVmQGRlbGl2ZXJ5LnNoZC5jaGVmLmNvOjg5ODkvQ2hlZi9DaGVmX0Rl
bGl2ZXJ5L2RlbGl2ZXJ5LWNsaSIsInNoYSI6ImZlYWIyZTA5MTA0NGRlZmE3NGFlNDRlODJmYTczY2NlYjU1NTBjODYiLCJwYXRjaHNldF9icmFuY2giOiJf
cmV2aWV3cy9tYXN0ZXIvanJhL3dpbl9mcmllbmRseV9jb29rYm9va3MvNCIsImRlbGl2ZXJ5X2FwaV91cmwiOiJodHRwczovL2RlbGl2ZXJ5LnNoZC5jaGVm
LmNvL2FwaS92MC9lLyIsImRlbGl2ZXJ5X2RhdGFfdXJsIjoiaHR0cHM6Ly9kZWxpdmVyeS5zaGQuY2hlZi5jby9hcGkvdjAvZS8iLCJkZWxpdmVyeV9jaGFu
Z2VfdXJsIjoiaHR0cHM6Ly9kZWxpdmVyeS5zaGQuY2hlZi5jby9lL0NoZWYvIy9vcmdhbml6YXRpb25zL0NoZWZfRGVsaXZlcnkvcHJvamVjdHMvZGVsaXZl
cnktY2xpL2NoYW5nZXMvMmI3NDFiYTQtOWZlYS00MWY0LTg4NGYtZjYw
Summary:
- Have a 2008R2 building from delivery_build with all the correct dependencies, including:
- 64 bit mingw (part of the 64 bit rubies package), required for building delivery-cli
- Rust 1.4
- the Delivery CLI package install
- chefdk
- Git
- A beefy EC2 host running 2008R2
- The install delivery works and builds itself
environment({
'PATH' => "C:/rubies/#{ruby_version}/bin;C:/rubies/#{ruby_version}/mingw/bin;C:/Program Files (x86)/Git/Cmd;C:/Program Files (x86)/Git/libexec/git-core;C:/wix;C:/7-zip;C:/Program Files (x86)/Windows Kits/8.1/bin/x64;C:/Windows/system32;C:/Windows;C:/Windows/System32/Wbem;C:/Program Files/OpenSSH/bin;C:/opscode/chef/bin/;C:/opscode/chefdk/bin/;C:/opscode/chefdk/embedded/mingw/bin;C:/Program Files/Rust nightly 1.4/bin;C:/chef/delivery-cli/bin;C:/chef/delivery-cli/bin",
'HOME' => ENV['USERPROFILE'],
'C_INCLUDE_PATH' => 'C:/OpenSSL-Win64/include;C:/opscode/chefdk/embedded/mingw/i686-w64-mingw32/include',
'OPENSSL_INCLUDE_DIR' => 'C:/OpenSSL-Win64/include',
'OPENSSL_LIB_DIR' => 'C:/OpenSSL-Win64',
'LD_LIBRARY_PATH' => 'C:/OpenSSL-Win64',
'SSL_CERT_FILE' => 'C:/opscode/chefdk/embedded/ssl/certs/cacert.pem'
})
Enter PS C:\chef> chef-client
Starting Chef Client, version 12.4.1
[2015-09-02T13:44:15+00:00] INFO: *** Chef 12.4.1 ***
[2015-09-02T13:44:15+00:00] INFO: Chef-client pid: 1564
[2015-09-02T13:44:22+00:00] INFO: Run List is [role[windows_builders]]
[2015-09-02T13:44:22+00:00] INFO: Run List expands to [git, chef-client, chef-client::delete_validation, push-jobs, deli
very_build]
[2015-09-02T13:44:22+00:00] INFO: Starting Chef Run for win-builder1.shd.chef.co
[2015-09-02T13:44:22+00:00] INFO: Running start handlers
[2015-09-02T13:44:22+00:00] INFO: Start handlers complete.
https://www.dropbox.com/s/lal6vt7tn6cdcf0/delivery-cli-0.0.0%2B20150824144123-1.exe?dl=0
---- cli::job_verify_unit_with_path_config stdout ----
thread 'cli::job_verify_unit_with_path_config' panicked at 'Failed command "C:\\var\\opt\\delivery\\workspace\\l
ocalhost\\local\\workstation\\delivery-cli\\master\\verify\\unit\\repo\\target\\debug\\delivery" "job" "verify" "unit" "
--no-spinner" "--job-root" "C:\\Users\\vagrant\\AppData\\Local\\Temp\\job-root.1CXL9GagDAnS"
OUT: Chef Delivery
Loading configuration from C:\Users\vagrant\AppData\Local\Temp\local-project.oBFdkGZwvliY
Starting job for local-project.oBFdkGZwvliY verify unit
Creating workspace in C:\Users\vagrant\AppData\Local\Temp\job-root.1CXL9GagDAnS
Cloning repository, and merging master to master
Configuring the job
execute "cargo clean" do
cwd "C:/Users/vagrant/delivery-cli"
cwd node['delivery_builder']['repo']
end
#execute "set > C:\outfile" do
# if Chef::VERSION !~ /^12/
# environment({
# 'RUST_TEST_TASKS' => "1"
# })
execute "cargo clean" do
cwd node['delivery_builder']['repo']
end
execute "cargo test" do
if Chef::VERSION !~ /^12/
environment({
'RUST_TEST_TASKS' => "1"
})
end