Converting TeamCity builds to GoCD builds

[Matt Featherstone]

All - We have a number of builds within TeamCity that we are looking to move to Go. The builds contain Powershell scripts, VCS Roots, Dependencies etc. Is there a process to follow to ensure that the too remain aligned and that when I create the Go builds they match the TeamCity ones.

Thanks

[Sriram Narayanan]

On Tue, Aug 23, 2016 at 8:19 PM, Matt Featherstone <mattfeath...@gmail.com> wrote:

All - We have a number of builds within TeamCity that we are looking to move to Go. The builds contain Powershell scripts, VCS Roots, Dependencies etc. Is there a process to follow to ensure that the too remain aligned and that when I create the Go builds they match the TeamCity ones.

I have had to migrate from Team City's Build Chains to GoCD's Build Pipelines a few times.

In general:

1. You can accomplish with GoCD what you can with TeamCity

Both of them essentially run commands and scripts that you ask them to.

2. Consider moving away from from inline commands, to invoking scripts.

That is, instead of "mvn foo && curl something && echo something else" (all examples of actual commands", invoke a script.

3. Rendering reports.

Team City may generate and render reports for you. Other CI systems do this too. Under the cover, all of them just invoke command line tools specific to the build platform. With GoCD's custom commands, you can perform such invocations, and display the reports in custom tabs.

4. Move toward Build Pipelines

Rather than the serial flow of chaining jobs, consider moving toward build pipelines. This model can give you some really interesting orchestration capabilities. In short, a pipeline comprises of stages that are run sequentially. Stages have jobs that are run in parallel across agents. A job may have a number of tasks that are run sequentially in an agent.

5. A GoCD agent will run just one job at a time, but one can have multiple GoCD agents on the same computer.

Please keep in mind that there would be Ops considerations like security, sign on, backups, file and artefact storage, high availability, and so on. If you have such The GoCD codebase is open source, and a number of Ops folks frequent this list.

Depending upon your timelines and how you wish to pilot a migration to GoCD, you may wish to either take this up yourself, or seek the occasional advise from a consultant, or engage the GoCD team directly.

Get started, ask questions, and we'll all help where we can.

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 go-cd+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Manoj Mahalingam]

My Powershell task runner plugin for GoCD is modelled very closely to what TeamCity's awesome Powershell integration does, so may want to try that out, even for running scripts.

I haven't worked on it for a while, but with Powershell being open sourced and available on Linux and OSX, I must be able to add features if needed.

On Tue, Aug 23, 2016 at 5:49 PM, Matt Featherstone <mattfeath...@gmail.com> wrote:

All - We have a number of builds within TeamCity that we are looking to move to Go. The builds contain Powershell scripts, VCS Roots, Dependencies etc. Is there a process to follow to ensure that the too remain aligned and that when I create the Go builds they match the TeamCity ones.

Thanks

--