We are using VSTS for our CI/CD environment. In our project we have multiple parts, like Database and Frontend1, which have a separate folder in our repository:
src/
Database
Frontend1
...
I have created a separate build for each of the components of our project, which are triggered if there changes pushed to the corresponding subfolder. I want this separation to easily control and check the version of each component.
Database --> Build Database
Frontend1 --> Build Frontend1
With this configuration there are two builds triggered if I check in changes for Database and Frontend1 with a single commit.
Additionaly I have configured a single release with both artefacts linked. The release is also triggered for each build.
The problem now is, that if I check in a change for the Database and Frontend1, both builds are triggered and after every build there is also a release triggered. This means I have two releases for the same commit. I want to achive that there is only one release which combines both builds:
Database --> Build Database |
| --> Release Database and Frontend1
Frontend1 --> Builds Frontend1 |
Is there any possibility to achive such a configuration?