Ensure order of builds
Hi,
I have an application consist of three components: API, Database, Client. My goal is to have separate build and deploy configuration for each component so they can be deployed faster. However, whn a new feature branch is created - then all components needs to be deployed with specific order.
TC configuration looks like this:
- Build API
- Build Database
- Build Client
- Deploy API
- Deploy Database
- Deploy Client
4, 5, 6 have snapshot depenedencies on 1, 2, 3 respectively.
I added VCS triggers on
- 4 - src/Api/**
- 5 - src/Database/**
- 6 - src/Client/**
Now, when a change is commited to a specific directory i.e. src/Client then Deploy Client triggers Build Client and when it finishes then Deploy Client is ran, which is exactly what I want.
In a scenario when a new feature branch is created - I need to deploy all components in specific order (might be manually triggered) - that is Deploy Database must be first, and then Deploy API and Deploy Client can be ran.
However I cannot set Deploy API to have Deploy Database snapshot dependency because when there are changes to src/API/** then database will be deployed which is something I dont want - I want to deploy components separately.
I also tried to add "Deploy new feature branch" configuration which allow me to have deploy steps in proper order, but then individual deploy configuration are also triggered.
Please sign in to leave a comment.
Hi,
The deploy new feature branch would be a way to go, how did you configure it? If you set it up with the 3 steps in the right order, plus a dependency on the 3 build X configurations it should work without triggering the other 3 deploys.