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

Hi @robin ,

Thanks for the clarification.

Yes, we'd like this to be tracked as an improvement.

Our expectation is that when rerunning a job, only the selected job should be rerun, while any successful dependency jobs should be reused and not triggered again. Only failed or missing dependencies should be rerun if required.

This behavior would help reduce unnecessary execution time and resource usage.

Thanks!

Hi @robin ,

Thanks for the clarification.

Yes, we'd like this to be tracked as an improvement.

Our expectation is that when rerunning a job, only the selected job should be rerun, while any successful dependency jobs should be reused and not triggered again. Only failed or missing dependencies should be rerun if required.

This behavior would help reduce unnecessary execution time and resource usage.

Thanks!

Thanks for confirming.

Your expected behavior—rerun only the selected job, reuse successful dependencies, and only rerun failed or missing ones—is tracked in issue OD-2949. That improvement has already been completed and shipped in OneDev 16.4.0.

After upgrading to 16.4.0 or later, rerunning a deploy job should no longer retrigger successful upstream/dependency builds. Please comment here if anything still looks wrong after upgrading.