Hi guys I've looked at the documentation but could'nt find anything explaining or mentioning how to call an configuration from another one.
What I'm trying to active is the follow, I have an configuration that do the tests, build it, and deploy it in a dropbox folder.
So this one should be my configuration used to perform my nightly builds, so now I need the same configuration but it will just disable the deploy and be triggered by the repository trigger.
After that It will be created another one that will be used to release the app, that will tag it and commit the tag to mercurial.
So how do you guys planned this to work with ? should I create a new configuration for every case ? because to maintain this it get a litle dificult as it would require a review in all configurations when something changes.
Any tips on that ? How are you guys working with that in continua ? I would not like to add a lote of variables and check it...
It’s not possible to reference the stages in one configuration from another.
You can clone an existing configuration. This can be done while editing a project in the Finished tab of the Project Wizard. There is not however any link between the cloned and original configurations.
In your case, you may be able to achieve the same functionality using multiple triggers on one configuration. You can set a different variable value for each trigger and then use the Flow Control actions and Stage Gate conditions to define logic to specify which actions or stages should be run for each trigger.
Note you can also set up a “Build Completed” trigger to trigger one configuration when another finishes.
As Dave said, it’s snot possible… and to be honest I’m not sure it will ever be. When we implement dependencies, you will be able to have configurations triggered before/after other configurations… right now the “Build Completed” Trigger can do that, but it’s limited because it doesn’t pass any information through about the completed build.
One of the advantages that Continua CI triggers have over other CI server products is that triggers can set variables, which makes it very easy to use the same configuration for different purposes (using the flow control actions). We do that with the Continua CI build, different triggers set variables to control how the build progresses. For example, feature branch builds disable the ability to build the installers and deploy to the webserver… they stop after the unit testing stage. This sort of workflow is trivial to set up and maintain with Continua CI.