Referencing build outputs from previous stages#1015

Subscribe to Referencing build outputs from previous stages 3 post(s), 2 voice(s)

 
Avatar Marco Studer 5 post(s) #2737

Hi
I’m just getting started with cruise and configured a simple pipeline with two stages. The first stage is a compilation stage which produces dome dll’s. How can I reference these dll’s in a later stage? Do I have to use artifacts for this scenario?

Is there a sample configuration file available for a simple pipeline with compile and test stages available?

Thanks.

Marco

 
Avatar Jez Humble Administrator 108 post(s) #2738

Hey Marco

Yes, you’d want to use artifacts for this.

You can get Cruise to upload the artifacts for you from the job they’re created in. It looks something like this:

<job>
  <tasks>
    ....
  </tasks>
  <artifacts>
    <artifact src="relative/path/to/where/your/dlls/are/created"/>
  </artifacts>
</job>

Currently you have to retrieve artifacts from your build script, which is described here: http://studios.thoughtworks.com/cruise-continuous-integration/1.1/help/cruise_integration.html

We’re going to be making it possible to have Cruise download the artifacts you need in your later stage for you as part of 1.2.

I’ll look into creating a sample configuration file—the danger in doing it is that we have to do it for every technology or people tend to feel left out. There is a guide to the basic principles here though: http://studios.thoughtworks.com/cruise-continuous-integration/deployment-pipelines

Thanks,

Jez.

 
Avatar Marco Studer 5 post(s) #2743

You helped me a lot Jez, thanks.