.pipeline/config.yaml
ActivePublic
Actions

Authored by • dduvall on Feb 15 2019, 8:14 PM.

Tags

None

Referenced Files

	F28225039: .pipeline/config.yaml
	Feb 15 2019, 8:35 PM

	F28224920: .pipeline/config.yaml
	Feb 15 2019, 8:14 PM

Subscribers

None

	pipelines:
	serviceOne:
	blubberfile: serviceOne/blubber.yaml # could be the default based on service name for the dir
	directory: src/serviceOne
	execution: # an "execution plan" (a directional graph of stages to run)
	- [unittests, mocha] # set of stages to run in parallel
	- production # next stage to run if the previous ran successfully
	stages: # stage defintions
	- name: unittests
	variant: phpunit # defaults to the stage name but can be different
	publish:
	- type: files # publish select artifact files from the built/run image
	paths: ["foo/", "bar"] # copy files {foo/,bar} from the image fs to ./artifacts/{foo/*,bar}
	- name: mocha # default (build/run "mocha" variant, no artifacts, etc.)
	- name: production
	testDeploy: # deploy to the "ci" k8s cluster, run `helm test`, etc.
	- chart: http://helm/chart # use this chart (don't need the helmConfig field anymore)
	publish:
	- type: image # publish built image to our docker registry
	tags: [candidate] # additional tags
	deploy: true # al final, trigger production deployment (however)
	serviceTwo:
	directory: src/serviceTwo

• dduvall changed the title of this paste from untitled to .pipeline/config.yaml.

• dduvall updated the paste's language from autodetect to yaml.

.pipeline/config.yamlActivePublicActions