Link multiple configuration with each other

Continua CI Discussion
1

Hi guys,

is there a way to run a different ContinuaCI configuration from an action and include an artifact from the configuration in the calling configuration?

Kind regards

Kay Zumbusch

2

Hi Kay,

There is no such action and we don’t currently plan to implement this type of functionality as an action. 

There is however the Build Completed trigger which enables you to run one configuration when another has completed. It allows you to copy selected variable values from the triggering build, but does not currently transfer artifacts - it will do this soon (possibly in the next version). 

We have a plan to introduce a dependencies feature - where one configuration can depend multiple other configurations. This is however a long term plan, awaiting completion of the set of features we are currently working on.


3

Hi Dave,

thanks for the information. The build completed trigger will likely not work for our scenario. Let me explain our planned scenario. Our .NET based application includes a web access based on Angular. We would like to release updates for the web access independently from the .NET application and therefor would move the web access build tasks to a separate configuration. Our main configuration would not be started for every build of the web access configuration so the build completed task would not work. If we cannot link the configurations we would just copy the build tasks for the web application to the web access configuration and update both configurations if we need to tweak the build tasks.

Kind regards

Kay Zumbusch

4

Hi Kay,

The build completed trigger includes conditions. If I understand your scenario correctly, you could set a variable in the Angular configuration when you want the .Net configuration to start. Once the Angular configuration is complete, the build completed trigger will check its conditions. If the variable has be set, the .Net configuration will be run.

Alternatively, you can put the actions for each application in separate stages and use skip conditions to decide whether the .Net application stage should run.