Update HOW_THE_PIPELINE_WORKS.md
Hab packages are now built in habitat/build pipelines
Consolidation of nightly pipelines
@@ -292,11 +292,20 @@ access to the underlying buildkite-agents. However, you can:
"Environment" tab of a given step. From here you can get high level
information like monitoring data on the machine in question.
-## Post-Merge Expeditor Build
+## Post-Merge build pipeline
-After merge, Expeditor will build any changed packages, taking into
-account dependency information. These packages are then be uploaded to
-the Habitat depot and promoted into the dev channel.
+After merge, Expeditor will trigger the 'habitat/build' pipeline:
+
+https://buildkite.com/chef/chef-automate-master-habitat-build
+
+This pipeline builds any packages that have changed in the most recent
+commit. The buildkite pipeline definition itself is autogenerated
+using the data found in `.bldr.toml`. `.bldr.toml` is generated by
+
+ go run tools/bldr-config-gen
+
+These packages are then be uploaded to the Habitat depot and promoted
+into the dev channel.
We also publish a "manifest". The manifest is a list of all the
packages that compose "Automate" and their required version. This
@@ -313,9 +322,9 @@ action that failed.
## Post-Build deploy/dev pipeline
-After the Expeditor build is complete, Expeditor will trigger the
-deploy/dev pipeline. This pipeline runs another set of tests on the
-newly promoted set of packages. These tests are a combination of new
+After the build is complete, Expeditor will trigger the deploy/dev
+pipeline. This pipeline runs another set of tests on the newly
+promoted set of packages. These tests are a combination of new
installations and upgrades of long-lived environments under different
configurations.
@@ -338,25 +347,9 @@ and ssh key and do any investigation required to debug the issue.
## Nightly Pipelines
-In addition to the pipelines described above, we have some pipelines
-that run nightly. Failures in these pipelines do not block merges or
-deploys; however, their failure is still taken seriously and
+In addition to the pipelines described above, we have a pipeline that
+is run nightly. Failures in this pipelines do not block merges or
+deploys; however, failures here are still taken seriously and
investigated.
-Our nightly pipelines can be found in the expeditor
-configuration:
-
-```
- - workload: schedule_triggered:chef/automate:master:nightly_tests:*
- actions:
- - trigger_pipeline:a1-migration/dev
- - trigger_pipeline:deploy/proxy
- - trigger_pipeline:basic-a1/dev
-```
-
-To see what these pipelines do, you can look at the job configuration
-in:
-
- - .expeditor/a1-migration.pipeline.yml
- - .expeditor/proxy.pipeline.yml
- - .expeditor/basic-a1.pipeline.yml
+Our nightly pipeline is defined in `.expeditor/nightly.pipeline.yml`
