I trying deploy micro-services with multiples container in same bitbucket repository. currently.
For some newly added features, only some of the container will be modify, and I would like to avoid all container build again in "build" step (Noticed that there could be control over branches, but controlling step within the branch ? ).
In gitlab, Its allow some sort of control on job (step in bitbucket) so that it could avoid container without modification be re-build again and hence avoid wasting build time.
docker build: script: docker build -t my-image:$CI_COMMIT_REF_SLUG . rules: - changes: # Will include the job and set to when:manual if any of the follow paths match a modified file. - Dockerfile when: manual
Run manually if
Dockerfile has changed OR
$VAR == "string value"
Is there already such feature ? if not, would it be on product roadmap ?
- using GCP
- my situation (used docker-compose to develop locally, for a single service with multiple backend micro-services)
Looking forward to your advise !
At the moment there is no built-in support for having these types of conditions on steps being triggered.
We an open feature request for triggering pipelines after certain files change. Which you can follow.
You can also open a new feature request here: https://jira.atlassian.com/secure/CreateIssue!default.jspa
...hey are a part of us, shaping how we interact with the world around us. The same holds true for programming languages when we think about how different kinds of vulnerabilities raise their heads in t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events