Automated version control of pipelines

Comments

5 comments

  • Avatar
    Jez Humble

    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.

    0
    Comment actions Permalink
  • Avatar
    Scott Baldwin

    Jez, did this (or a portion of it) make the cut for the 2.3 release?

    0
    Comment actions Permalink
  • Avatar
    Jez Humble

    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.

    0
    Comment actions Permalink
  • Avatar
    Scott Baldwin

    Jez, this is great! I hadn't seen this page in the docs. Thanks for the link. We're really digging Go (we started with 2.1).

    0
    Comment actions Permalink
  • Avatar
    LeeBenhart

    I did somthing similar to this by setting up an automated pipeline task to run nightly which would execute nant scripts to copy my config xml file, break it up to individual pipeline.xml files, and check each into source control(svn). I also checked in the main config.  This allowed us to track changes to each pipeline.  I also had a manual task which would checkout the individual pipelines, assemble the config xml file and then deploy it (copy over the existing one).  This allowed me to manually edit the pipeline.xml files and check them in to easily add new pipelines. This was especially handy since we were using community edition and using templates and pipeline groups was not available.

    0
    Comment actions Permalink

Please sign in to leave a comment.