Hey Clark

The GoCD team are currently testing out some new ideas for the new user 
experience in GoCD. Given your newness to Go and helpful feedback above I 
wondered if you might have time to help us with this. 

To test our prototype with you I would ask for 30 minutes of your time and 
I would need to ask you to share your screen with us so we can see you 
interact with our prototype. I'd send you all the details on how to do that 
in advance.

Let me know if you're up for that. 

Thanks
Suzie 

On Tuesday, 13 June 2017 06:56:35 UTC-7, [email protected] wrote:
>
> Hi,
>
> I'm new to GoCD and have been working with it for only a couple of weeks, 
> testing the system out as a possible alternative to Jenkins for our new 
> project. First impressions are good, it seems really well thought out (no 
> pun intended, hah), fairly straightforward to automate and the UI is nice 
> and clean :)
>
> Today I carried out an exercise to replicate the loss of the Datacentre 
> hosting our GoCD Cloud and through a combination of our Ansible 
> provisioning scripts and the GoCD Pipelines as code feature, I was able to 
> quickly spin up a replacement GoCD Cloud with all our Pipelines intact 
> which was great!
>
> What wasn't so great though, was that all of the Pipelines started to 
> execute as soon as the services were online, albeit in terms of 
> concurrency, they were throttled by the number of available Agents.
>
> 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'?
>
> Thanks,
>
> Clark
>

-- 
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.

Reply via email to