We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I wonder if a tutorial / hint like the pipeline editor (VS / Atom ) for ctpl could be usefull in general.
ctpl
I am using https://github.com/EugenMayer/concourse-pipeline-templateer for all our production pipelines since about half a year and it helped a lot making pipelines more easy to maintain, edit and understand.
E.g. we also split our jobs into jobs/staging/_somejob.yml and jobs/release/_somejob.yml for pipelines where we have a lot of jobs.
jobs/staging/_somejob.yml
jobs/release/_somejob.yml
One example can be found here https://github.com/kw-concourse-example/concourse-app-release-lifecycle-example/tree/master/ci/pipeline
The usage is fairly simple, but also check the docs
gem install ctpl # generate the template and deploy in one go ctpl && fly sp -t target -c pipeline.yaml -p mypipeline
Eventhough there is no fly integration, it can just be run beforehand.
to be compatible with something like https://github.com/concourse/concourse-pipeline-resource i usually checking the pipeline.yml into the CI repo too so the deployment works as usual.
Let me know if there is any interest, i could for sure write a first article draft or whatever is needed.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I wonder if a tutorial / hint like the pipeline editor (VS / Atom ) for
ctpl
could be usefull in general.I am using https://github.com/EugenMayer/concourse-pipeline-templateer for all our production pipelines since about half a year and it helped a lot making pipelines more easy to maintain, edit and understand.
E.g. we also split our jobs into
jobs/staging/_somejob.yml
andjobs/release/_somejob.yml
for pipelines where we have a lot of jobs.One example can be found here https://github.com/kw-concourse-example/concourse-app-release-lifecycle-example/tree/master/ci/pipeline
The usage is fairly simple, but also check the docs
Eventhough there is no fly integration, it can just be run beforehand.
to be compatible with something like https://github.com/concourse/concourse-pipeline-resource
i usually checking the pipeline.yml into the CI repo too so the deployment works as usual.
Let me know if there is any interest, i could for sure write a first article draft or whatever is needed.
The text was updated successfully, but these errors were encountered: