Satyajeet Patil
opened 1 day ago
-
This is expected behavior in OneDev 15.0.0, not a bug or misconfiguration.
What changed
OneDev 15.0.0 added the ability to re-run dependency jobs when you re-run a job (see OneDev 15 release notes and issue #2735).
- Before (e.g. 13.0.0): Rerunning a finished deploy job reused already successful dependency builds. Only unsuccessful required dependencies were resubmitted.
- From 15.0.0: Rerunning a finished job also resubmits its job dependencies. The deploy build stays in Waiting until those dependency builds finish, then continues. That matches what you are seeing for both failed and successful deploy reruns.
There is currently no setting to restore the old “reuse successful dependencies on Rerun” behavior.
First-time run vs Rerun
If you run a deploy job for a commit for the first time (not Rerun on an existing deploy build), OneDev still resolves job dependencies against existing builds for the same commit / job / parameters when they already exist. The new always-rerun-dependencies behavior applies specifically when you Rerun an existing build.
Next step
If you need an option such as “Rerun this job only; keep successful dependencies”, please say so and we can track that as an improvement. Otherwise, this question can be closed as answered.
-
This will be addressed in OD-2949
-
Previous Value Current Value Open
Closed
| Type |
Question
|
| Priority |
Normal
|
| Assignee | |
| Labels |
No labels
|
Hi @robin ,
After upgrading OneDev from 13.0.0 to 15.0.0, we started seeing an issue with our pipelines. We have several manual deploy jobs that depend on a build job. Normally, the build job is triggered automatically when code is pushed to a branch. However, after the upgrade, when we manually trigger a deploy job, the build job starts again instead of using the existing successful build. At the same time, the deploy job remains in the Waiting state until the new build finishes. We are specifically seeing this behavior in the following cases:
Could you please let us know: Is this a known issue or bug in OneDev 15.0.0? Or is there any new setting or configuration required to prevent the build job from being triggered again when rerunning a manual deploy job?
Thank you.