In some cases, you might need to use multiple source control repositories for a single pipeline. For example, you might have your source code in subversion and your deployment scripts in a mercurial repository. If either your source code or your deployment scripts change, Go will run a build.
When using multiple <materials>, each material must have a unique "dest" folder specified for the agent to check the source into.
Assuming the source code is stored in the subversion repo at http://svn-server.local/ and the deployment scripts are stored in the mercurial repo at http://hg-server.local/
- Follow the Quick pipeline setup instructions, using the subversion repository url as your SCM details.
- Your pipeline should now be set up with one material. We want to now add another.
- Navigate to the Admin section
- Select your pipeline from the pipeline list.
- Click "Edit This Pipeline"
Update the materials section to include the Mercurial (Hg) repo:
<pipeline name="deploy"> <materials> <svn url="http://svn-server.local/" dest="code" /> <hg url="http://hg-server.local/" dest="deploy-scripts" /> </materials> ... </pipeline>
- Click "Save"