You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A pipeline ran again on my development branch when it shouldn't have; the former run was sufficient. There were no changes for the workflow against the prior commit.
Expected behavior
I don't think workflows should run again on a development branch if they ran on the last commit. We should assume they've been compartmentalized (?) enough that they do not need to run again. We should allow users to configure whether they want workflows to run if there have been changes compared to the last commit, not just against the master branch?
Additional Information
In the below pipeline example, no changes were made at all under /docker/*, yet it rebuilt the containers (as expected) because this branch of course has changes under /docker/ comparing to master, or the default branch.
The text was updated successfully, but these errors were encountered:
Orb version
3.4.0
What happened
A pipeline ran again on my development branch when it shouldn't have; the former run was sufficient. There were no changes for the workflow against the prior commit.
Expected behavior
I don't think workflows should run again on a development branch if they ran on the last commit. We should assume they've been compartmentalized (?) enough that they do not need to run again.We should allow users to configure whether they want workflows to run if there have been changes compared to the last commit, not just against the master branch?Additional Information
In the below pipeline example, no changes were made at all under
/docker/*
, yet it rebuilt the containers (as expected) because this branch of course has changes under/docker/
comparing tomaster
, or the default branch.The text was updated successfully, but these errors were encountered: