I was inspired by this BuildKite pipeline sample given by the support team:
YAML
x
12
12
1
# .buildkite/pipeline.yml2
steps3
commandecho building a thing4
blockTest the thing?5
commandecho testing a thing6
wait7
command buildkite-agent pipeline upload .buildkite/pipeline.deploy.yml8
9
# .buildkite/pipeline.deploy.yml10
steps11
blockDeploy the thing?12
commandecho deploy the thingSo in the above case, if the first 2 commands succeed, pipeline.deploy.yml will be loaded into the main CI pipeline. This implementation is just brilliant. I’m not sure if jenkinsfile can do dynamic pipeline like this, but at least jenkinsfile won’t look as elegant as yaml.
Since buildkite-agent pipeline upload .buildkite/pipeline.deploy.yml is just another bash command, I can even use it in a script to put more logic in it, such as git flow implementation like:
YAML
xxxxxxxxxx1
30
30
1
#!/bin/bash2
export CHOICE=$(buildkite-agent meta-data get "next-section")3
4
case $CHOICE in5
deploy)6
buildkite-agent pipeline upload .buildkite/pipeline.qa.yml7
;;8
signoff)9
# feature finish10
if $BUILDKITE_BRANCH == feature* ; then11
python .buildkite/scripts/github_ci.py \12
--action pr \13
--repo flow-work \14
--head $BUILDKITE_BRANCH \15
--base develop16
17
# release start18
elif $BUILDKITE_BRANCH == develop ; then19
git checkout -b release/$FULL_VERSION20
git push --set-upstream origin release/$BUILDKITE_BUILD_NUMBER21
22
# release finish23
elif $BUILDKITE_BRANCH == release* ; then24
buildkite-agent pipeline upload .buildkite/pipeline.pass.yml25
fi26
;;27
reject)28
#mark build as failure29
exit -130
;;FYI. example tested with BuildKite agent version 3.2.0.
