Trigger Datadog synthetic tests for an MFE pipeline on a lower environment

[jristau1984]

• Demonstrate triggering off of Git merge on new pipeline added to MFE pipeline group
• Create repository config for MFE pipeline to pick up workstream's tubular work
• Have pipeline synthetic tests triggered from GIT merge on MFE pipeline in a lower environment
• Update tubular to run full set of intended tests
• Have tubular work PR'ed

[bszabo]

Prior work was off of the test GoCD tool, located at https://test-gocd.tools.edx.org/go/pipelines#!/

The work leverages a new pipeline defined via a YAML file as a config repository. GoCD names the config repository "dd_tests" and its YAML file is located at [email protected]:edx/edx-gocd-synthetic-testing.git (dd-tests-fresh branch) "release_tests.gocd.yaml"

Documentation for interpreting the YAML file's contents is located here.

[bszabo]

Tubular enters the picture via the "tubular" material specified in the YAML file. This references the edx/tubular repo, and specifies that the repo is to be downloaded onto the "tubular" folder on the GoCD agent. Then, the specification for the job to be run on the pipeline lists a python file in this folder to run as the executuable; moreover, it lists that folder as the working directory.

In combination, the above steps serve to ensure that the job run off the pipleine is the intended Tubular script.

[bszabo]

In the previous phase of this project, I was running the pipeline, its stage, and the jobs within that stage, by manually triggering the pipeline. This means the work was divorced from any development environment stage, as it wasn't tied to any deployment activity on any such stage.

To tie a GoCD pipeline to a development environment, the pipeline needs a dependency on an upstream pipeline/stage. Need to investigate whether the dependency scope on the YAML file is restricted to pipelines and stages running on the test GoCD server. I ssupect it is. If so, need to figure out how to trigger a build on this server. (May need to create my own upstream pipeline, manually trigger than, and then have the target pipeline show proper dependency on the upstream pipeline).