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
It would be great to have this option, utilizing Jenkins' OnceRetentionStrategy such that a given executor will only run one job.
The problem I'm having at the moment is migrating a job with blocking subproject builds from Google Cloud to Oracle. Without a one-shot mode, the subproject waits on a free executor from the instance that is running the main job, which is waiting on the completion of the subproject job. A classic deadlock ensues.
If I could configure my Jenkins OCI cloud to run everything in one-shot mode, the subproject would cause a new executor to be provisioned and the job would flow as intended.
The text was updated successfully, but these errors were encountered:
It would be great to have this option, utilizing Jenkins' OnceRetentionStrategy such that a given executor will only run one job.
The problem I'm having at the moment is migrating a job with blocking subproject builds from Google Cloud to Oracle. Without a one-shot mode, the subproject waits on a free executor from the instance that is running the main job, which is waiting on the completion of the subproject job. A classic deadlock ensues.
If I could configure my Jenkins OCI cloud to run everything in one-shot mode, the subproject would cause a new executor to be provisioned and the job would flow as intended.
The text was updated successfully, but these errors were encountered: