We are pleased to welcome you to our online community for Go.
Resources for logging defects, troubleshooting installation and having general discussion about the product are all available. We welcome you input and ideas for new features.
| name | posts | comments | activity |
|---|---|---|---|
| Bug Reports | 103 | 221 | February 6, 2012 |
| Feature Requests | 138 | 263 | February 5, 2012 |
| General Discussion | 235 | 505 | February 4, 2012 |
| Troubleshooting | 50 | 155 | January 17, 2012 |
| Announcements | 29 | 26 | January 10, 2012 |
| API | 6 | 15 | January 10, 2012 |
| How To | 38 | 7 | January 10, 2012 |
| Go Add-Ons and Extras | 10 | 16 | January 10, 2012 |
| Go Blog | 7 | 6 | January 10, 2012 |
| Go Instructional Videos | 3 | 0 | January 10, 2012 |
I tried to install go-server on CentOS 6.2 in VMWare. During the linux installation process I set hostname to "mobeplace.build". I successfully installed the go-server, but it didn't start.
I checked the logs and found out that UnknownHostException was thrown (see attached stack trace). I changed server's hostname to a real hostname and go-server works now.

I've been hacking around trying to find who triggered a pipeline from within a Go job. Looking through the feeds API I mananged to find some value, either "changes" or the username of some person who manually triggered the pipeline.
Here is a ruby script that shows how to get either the username (if manually triggered) or the authors of changesets in materials: https://gist.github.com/1731305.
If you don't care about who made the changes you can use this ruby script: https://gist.github.com/1753163.
The second approach is based on feedback from the Go dev team. Still using the API, you use this URL:
url = "#{ENV['GO_SERVER_URL']}pipelines/#{ENV['GO_PIPELINE_NAME']}/#{ENV['GO_PIPELINE_COUNTER']}/#{ENV['GO_STAGE_NAME']}/#{ENV['GO_STAGE_COUNTER']}.xml"
Then, use XPath to lookup //approvedBy/text().
Ultimately, it will be cleaner to have an environment variable on the Go job with the value of the "approveBy" XML element. This has already been logged as a feature request, but I wanted to share the undocumented API and a programmatic way to use it.

I like the feature to filter the shown pipeline groups and pipelines on the main dashboard. As I have to switch quite often my context and focus, I would love to have multiple views.
A view should have a name, and the usual CRUD operations: Create, update, delete, maybe no read operation. The views should be persistet, and belong to a single user only.
Hi
I have recently received an email from my cloud hosted repository provider to reduce the number of http requests transmitted from my Go server. Apparently, they are being hit by 300,000 requests per day and have asked me to reduce requests to once every 10 minutes (are they being unreasonable?).
What would be the best way to configure the materials in my pipelines to reduce the number of polling requests? Or would it be best to get a provider that can handle the traffic I need to build an enterprise build, test and release pipeline?
The other option I've thought of is to host my own repository on an ec2 instance. Is this a good idea?
What are the best stategies for hosted repositories as providers start to compain about traffic generated to their servers by polling CIs?
Rustin
Registered ThoughtWorks Studios Community users can interact, exchange knowledge and ultimately improve their usage of Mingle, Go and Twist to deliver great software.
New Users: Join Now
For more details, please visit the How This Site Works page.
Stop by the Go Mobile Home Page to register for upcoming events and view presentations from previous meetups.