-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
We have a deployment job that has a VERSION parameter, which can be a branch name.
Example:
Schedule a job for tomorrow with VERSION=develop.
Schedule a job for next week with VERSION=master.
Scenario 1)
Directly deploy with VERSION=feature/new-buttons
Outcome: The two scheduled jobs still exist.
Scenario 2)
Directly deploy with VERSION=master
Outcome: The scheduled job with VERSION=master doesn't exist anymore.
The outcome in scenario 2 may seem logical. But on the other hand, it's not. If I plan a deployment for next week, I should not have impact when I deploy something right now.
The use case is:
Schedule a certain branch to deploy next week, while in the mean time patches in that branch can be deployed.