Hello Clark, On Tue, Jun 13, 2017 at 9:56 AM, <[email protected]> wrote:
> Being a rookie, this could well be an oversight on my behalf, but I > noticed that after *manually* creating a Pipeline, it is in a 'paused' > state initially and I kinda expected the same behaviour when the new GoCD > Server pulled the Pipelines from the config repo for the first time. Is > there anything I can do to influence this behaviour, so the initial state > of the Pipelines is 'paused'? > That's a good point. I'm not sure I would expect it to be paused, since I'd expect such a setup to automatically run. But, you're not the first person to ask this. Someone asked the same question over on the gitter channel for config repo plugins <https://gitter.im/gocd/configrepo-plugins?at=581098d0c3569a036e1e7ea4>. Might be useful to let tomzo (the author of the plugins) know, over in the channel that it's something you're interested in too. If he agrees it's useful, I'm sure he wouldn't mind a pull request too. Cheers, Aravind -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
