Comments
Go versions its own config internally (using JGit) as of 2.2 in fact. However we haven't yet exposed this through the UI. It is exposed as a RESTful API as described here: http://www.thoughtworks-studios.com/go/2.2/help/Configuration_API.html
Exposing previous versions of the config through the UI will be in 2.3.
Thanks,
Jez.
Hi Dom
Grab the zip download from the site.
Then follow the instructions here: http://www.thoughtworks-studios.com/go/2.2/help/run_go_without_install.html
Thanks,
Jez.
Hi Cliffe
Yes, I was bummed that Chris was selfish enough to hibernate the project after I shouted it out in the book ;-)
We've discussed putting this into Go, but it's not something that will be in the next couple of releases.
What a lot of people do is either use properties files checked into version control, or something like LDAP. Since (as Chris mentions) Neo4J now has a RESTful interface, you could probably use that without too much trouble too.
Apache Zookeeper looks like it might be able to do something along these lines, but I haven't had a chance to look at it in detail.
Sorry not to be more helpful - that's all I've got.
Another possibility would be subscribing to the devops and continuousdelivery google groups and asking there.
Thanks,
Jez.
We have opened a support ticket for this issue. Please email support@thoughtworks.com if you have not received it.
Yep, as Brett says, the dependency mapping view gets you some of the way there. It should be pretty easy for us to show you the stages from upstream pipelines - I'll add that to the backlog. It won't get into the release we're currently working on, but perhaps we can get it into the next one.
Thanks,
Jez.
Hey leebenhart
One thing - are you running Go server and your svn repo on a VM, as your report seems to suggest? If so, you'll want to move to bare metal if performance is an issue. Both Subversion and Go Server are very much I/O bound and we strongly recommend against running them on VMs, which typically show relatively poor I/O performance.
If your config file is that long, you might also consider using templates in Go to factor out duplication: http://www.thoughtworks-studios.com/go/2.1/help/pipeline_templates.html (although these are only available on Go Enterprise)
Ori, are you using the 64 bit JVM? The 32 bit JVM is significantly faster (even on 64 bit boxes). It's a known issue (with the JVM).
Thanks,
Jez.
- Hey Steve EC2 integration been under consideration for a while, but based on customer feedback it's not at the top of our list. When we come to do it, of course we'll solve the problem of agent-server communication. In the meantime, you could create your own reverse ssh tunnel - we've had some success with this, although for reasons of robustness it's best to do it on a per-job basis: start up the ssh tunnel, spin up the agent, then when you're done, spin down the agent and kill the ssh tunnel. Alternatively you could have a pipeline with an initial stage which does the set-up, one which does the work on the agent, and then a final stage which pulls everything down.
Thanks for your request Mark. Other people have asked for this too. I'll put it in the backlog with the aim to include it in our 2.2 release.
Looking for the Cruise Beta? We jumped the gun a bit on that announcement. Sorry about that. Please check back here tomorrow, June 16th, or email support@thoughtworks.com if you are interested in joining the program.
You're right, it would be great, and Cruise should do this. It's been in our backlog for a long time. I'm sorry to say it didn't make it into 2.0, but we plan to do it as part of the 2.x series. Initially Cruise will version it internally, but we do plan to support integration with supported VCSs. The tricky bit is integrating with the point-and-click administration UI we are planning to introduce (a problem the OSS CC tools don't have to worry about).
Thanks for your feedback,
Jez.
Hey Victor
Early access builds are available for existing customers - I've contacted you privately about this. We are planning to open up our early access program more widely next month - watch this space for more details.
Jez.
Hi Andy
We're still planning on adding support for a plug-in API to allow for third party developed source control integrations. However we're not there yet. Again, it's on the backlog, but I don't have a date for it yet. Sorry for the lack of progress on this.
It is possible to work around Cruise's lack of built-in support for AccuRev - check out the white paper here: http://www.thoughtworks-studios.com/resources
Thanks,
Jez.
Hey Victor
This is a known issue which Lisa and Jerry brought up with me last week. The alternatives are to edit through the pipeline wizards, or as Qiao Liang say, to use a text editor. In the medium term, our plan is to create a more powerful administration system so you don't need to edit the source at all.
Thanks,
Jez.
An update on Cruise 2.0 is available here: http://community.thoughtworks.com/posts/2ba2acb8cd