calm-parrot-72437
04/29/2020, 3:30 PMchilly-hairdresser-56259
04/29/2020, 4:01 PMbillowy-army-68599
cool-egg-852
04/29/2020, 4:24 PMcalm-parrot-72437
04/29/2020, 4:26 PMcool-egg-852
04/29/2020, 4:29 PMcalm-parrot-72437
04/29/2020, 4:30 PMcool-egg-852
04/29/2020, 4:30 PMcalm-parrot-72437
04/29/2020, 4:31 PMcool-egg-852
04/29/2020, 4:32 PMcalm-parrot-72437
04/29/2020, 4:34 PMcool-egg-852
04/29/2020, 4:35 PMtestapp1
, and it needs a DB, s3 bucket, etc., that would all go in the testapp1
pulumi project.calm-parrot-72437
04/29/2020, 4:37 PMcool-egg-852
04/29/2020, 4:37 PMcalm-parrot-72437
04/29/2020, 4:43 PMcool-egg-852
04/29/2020, 4:44 PMcalm-parrot-72437
04/29/2020, 4:45 PMcool-egg-852
04/29/2020, 4:45 PMcalm-parrot-72437
04/29/2020, 4:46 PMcool-egg-852
04/29/2020, 4:46 PMcalm-parrot-72437
04/29/2020, 4:47 PMcool-egg-852
04/29/2020, 4:48 PMcalm-parrot-72437
04/29/2020, 4:50 PMcool-egg-852
04/29/2020, 4:51 PMproject:useLinkerd
bool in the Pulumi.staging.yaml
file. If it’s true, we use the linkerd configuration, otherwise we use the istio
configuration.
This to us is easier to manage than separate branches.limited-rainbow-51650
04/29/2020, 5:06 PMgit
support allows for a path
specification which results in only triggering builds when files within that(/those) path(s) are changed.
https://concourse-ci.org/
https://github.com/concourse/git-resource
It is also the only CI where pipelines can be modelled over multiple git repositories. See Concourse CI building its own codebase as an example: https://ci.concourse-ci.org/teams/main/pipelines/concoursecalm-parrot-72437
04/29/2020, 5:17 PM