Let me know if this sounds, right.
I work at a company that has N services. Each service has it's own
deployable artifact. Each artifact creation process is unique, but the
pipeline, and deployment processes are similar. As we grow we are looking
to create more services. I would like to manage
I've tried the seed job-dsl method previously. Some automation was better
then no automation, but I think the Jenkinsfile in repo is even better. If
I make a change to the Jenkinsfile, that change can be isolated in each
environment/branch until it has been promoted to next step. If I have one
mast
Mike, I'd just like to chime in and say that makes a lot of sense to me. As
others have noted their can be times when you want multiple pipelines with
a repo. My own specific use case is that I'd like to be able to trigger a
rollback pipeline.
On Tuesday, July 12, 2016 at 12:16:27 PM UTC-6, Mik
