DevOps Zone is brought to you in partnership with:

Abhishek Kumar has interests in: Ethical Hacking, Developing & Tweaking Web/Network Applications. Security and Development are his two motivations in this industry. He is a developer at heart and artist by brain. So, he doesn't get limited to a certain solutions when he develops and isvery well know to give it an artist's touch wherever needed. http://abhishekkr.github.io Abhishek is a DZone MVB and is not an employee of DZone and has posted 12 posts at DZone. You can read more from them at their website. View Full User Profile

A Console Utility for ThoughtWorks' Go

09.25.2012
| 4539 views |
  • submit to reddit




I recently created a rubygem console utility to get focused information about your Go Continuous Delivery pipeline easily; no more switching again to browsers.  It's called ci-go-nfo.

@RubyGems: https://rubygems.org/gems/ci-go-nfo

@GitHubhttps://github.com/abhishekkr/ci-go-nfo

Free Go Community Downloads  Installation 

$ gem install ci-go-nfo


Using Ci-Go-Nfo ver.0.0.1 

To set-up credential configurations for your go-ci, type:
$ ci-go-nfo setup

it asks for
(a.) the location where you want to store your configuration file
(b.) the URL for your Go Server like http://my.go.server:8153
(c.) then username and password (create a read-only account for it)



to show go-ci info for all runs
$ ci-go-nfo

to show go-ci info for failed runs
$ ci-go-nfo fail

to show go-ci info for passed runs
$ ci-go-nfo pass

_____

.....more to come


output example:

 $ ci-go-nfo setup
  Store sensitive Go Configs in file {current file: /home/myuser/.go.abril}:

 Enter Base URL of Go Server {like http://:8153}:
                                                           http://my.go.server:8153

 This is better to be ReadOnly account details...

 Enter Log-in UserName: go_user

 Password: restrictedpassword


 $ ci-go-nfo pass
   my_pipeline -> specs -> specs
  Success  for run#2 at 2012-09-19T04:24:38
  details at http://my.go.server:8153/go/tab/build/detail/my_pipeline/10/specs/2/specs

  my_pipeline -> package ->gemify
  Success  for run#1 at 2012-09-19T07:04:39
  details at http://my.go.server:8153/go/tab/build/detail/my_pipeline/10/package/1/gemify


 $ ci-go-nfo fail
   your_pipeline -> smoke -> cukes
  Failure  for run#5 at 2012-09-19T04:24:38
  details at http://my.go.server:8153/go/tab/build/detail/your_pipeline/7/smoke/5/cukes


 $ ci-go-nfo
   my_pipeline -> specs -> specs
  Success  for run#2 at 2012-09-19T04:24:38
  details at http://my.go.server:8153/go/tab/build/detail/my_pipeline/10/specs/2/specs

  my_pipeline -> package ->gemify
  Success  for run#1 at 2012-09-19T07:04:39
  details at http://my.go.server:8153/go/tab/build/detail/my_pipeline/10/package/1/gemify
  your_pipeline -> smoke -> cukes   Failure  for run#5 at 2012-09-19T04:24:38   details at http://my.go.server:8153/go/tab/build/detail/your_pipeline/7/smoke/5/cukes



Published at DZone with permission of Abhishek Kumar, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)