I'd suggest having TeamCity store it into a package repository which GoCD is watching. You can see the existing plugins for that at https://www.go.cd/plugins/
That said, you may find that having more than one orchestration system doesn't give you the end to end visibility you'll want and / or need. Using a package repo for now is totally reasonable (and why that endpoint was originally created), but ultimately you should consider choosing one or the other. Ken On Wednesday, August 17, 2016 at 2:22:01 AM UTC-7, Matt Featherstone wrote: > > Hi - I'm new to GoCD and trying to get it set up for the first time. > Currently we use TeamCity to start our pipeline but want to introduce GoCD > for the pipeline after Integration. To this end I would need to configure a > pipeline that picks up the artefacts created within TeamCity, how do I do > this? Is there a plugin to enable this to happen? Or do I configure the > pipeline to look at the location of where TeamCity stores it's artefacts? > Or am I missing something? > > Thanks > -- 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.
