3 ms·
> You know what version of your pipeline built the software at any point in its history. Source control can tell you when changes to the pipeline were checked
by twic 11y ago
> You know what version of your pipeline built the software at any point in its history.
Source control can tell you when changes to the pipeline were checked in, but they actually take effect when they're applied with 'fly set-pipeline'. That may be before or after they were checked in. Perhaps a sensible team would set up a pipeline to watch the pipeline repository for changes and apply them automatically. Mine hasn't.
> Concourse boils the unit of extension down to "resources"
Which you can only actually use by forking the Concourse BOSH release to add them to the workers [1]. I'm not sure i'd honestly call it a point of extension.
[1] https://github.com/concourse/concourse/blob/master/jobs/groundcrew/spec#L23 https://github.com/concourse/concourse/blob/master/jobs/grou...
- dprotaso 11y agoNo need to fork anymore http://concourse.ci/configuring-resource-types.html http://concourse.ci/configuring-resource-types.html
- twic 11y agoOho! That's excellent. I see that came in 0.74; we're still on 0.70 i think, so i look forward even more to upgrading.
- jacques_chester 11y agoYeah, a few of us griped at the Concourse team about this large escape hatch from historical reproducibility and they took us seriously.