Open benjdudas opened 3 years ago
I support this idea. Currently my client is having more than 250 active projects which often rely on the "Update Revision on Launch" feature. When we take our version control down for an update (<10 minutes) it breaks a lot of projects and API calls.
Especially the last thing is adding additional stress on having good exception handling in the clients which call the API. In such case you can not simply retry the job after restoring access to version control.
We are migrating the projects to refresh the code by explicit updates after committing to the main branch. This is a large change due to the amount of projects and teams involved. A feature like this would reduce the operational load significantly when version control is not available.
ISSUE TYPE
SUMMARY
A previously failed project update would require a manual sync in order to remove the blocker to launch the job. This RFE is to allow a job to launch if the project is in a failed state when "Update Revision on Launch" is configured on the project. The current behavior will break workflows in environments with unstable connections to source control and would require manual intervention each time a project sync failed.