#release-engineering - January 2019

@Igor Rodionov ☝️

Nice

Hey we are evaluating diff tools for CI/CD (codefresh, buildkite, codepipeline, etc). I have a question for the users of codepipeline, how do you CD your pipeline definitions?
EG: in codefresh or buildkite, this is read from VCS when a run is triggered

Close I could see is have the pipeline, update the pipeline itself, but im a bit concerned how would this effect the run itself that updated the build.
Lets say you have a PR that updates the pipeline and some code to acomodate the pipeline update, you PR CI runs using the old pipeline.
Lets say you merge, it deploys the new pipeline update first, would the subsequent steps run with the updated pipeline?

@Gonzalo Peci we have an example of using CodePipeline here https://github.com/cloudposse/terraform-aws-jenkins/blob/master/main.tf#L115

it deploys this repo (by default) https://github.com/cloudposse/jenkins

Yeah I have seen that @Andriy Knysh (Cloud Posse) thanks

so i think everything goes into https://github.com/cloudposse/jenkins/blob/master/buildspec.yml

which is in the repo itself

i mean you can add any commends in there

Yeah,but I dont know if that answers my question tho

yea, I don’t know either 🙂 was long time when we tested it

I mean, the module deploys a pipeline, that is great, and then the jenkins repo has its own build definitions

which is also good

but then, what deploys the pipeline itself? another pipeline?

(talking about AWS codepipeline)

the module deploys it

when using codefresh, buildkite, etc you can define the pipeline itself in the repo

the module defines the code for it, but does not deploy it

you have to "apply" that module somewhere

ah i see now what you mean 🙂

I have seen some other CI/CD tools/companies have a repo containing all the pipelines, and that itself had its own pipeline, manually deployed as it was simple enought

but meh, not a fan of that workflow

so for a workflow to update the pipeline itself, maybe consider atlantis

(which of cause needs its own pipeline to be deployed 🙂 or you can just apply it to deploy on fargate as @Erik Osterman (Cloud Posse) is doing now)

Exactly! 😄 its the chicken and egg

Yeah fargate seems perfect for atlantis

TBH, some of the things that we dont deploy often, I dont mind deploying "automanually"

as a side note, I think I mentioned this before, as much as I like the idea of atlantis I dont like the apply before PR merge workflow. It would be like deploying before merge

it can even have issues on non up to date branches