Stages within pipeline should be able to work with separate SCM repositories

Follow

Sergey

February 18, 2011 14:10

I expect to have Build and Deployment stages withing the same pipeline in order to visualize the approval workflow in my organization.
The Build stage and the Deployment stage usually require different sources (application sources and deployment scripts) which can be located in different source control repositories.
Since the Stages work currently with the same repositories defined in the pipeline I have to put my deployment scripts into the same repository where the main application sources are located (or at least check them together out).

0

• 

  Anush Ramani March 11, 2011 11:19

  Agreed. The ability to cherry-pick material checkouts is useful. One feature that we recently implemented that gets us one step closer to that is the fetchMaterials flag. With this, you can tell a stage not to perform checkouts. I understand that this is not quite the use case you need, but we will track your feedback and add it to our backlog.

  0

  Comment actions Permalink
• 

  Sergey March 11, 2011 11:43

  Yeah, that would be a step in the right direction especially in conjunction with the feature of binding two concurent jobs/stages to the _same_ build agent. That would save copying numerous binaries between agents, which are not worth storing as artifacts in the system.

  0

  Comment actions Permalink

Please sign in to leave a comment.