angrycuban
opened 6 months ago
-
There is a job/executor matching change in recent version. Previously if executor is not specified in job, it will use first executor matching the job requirement settings. Now in addition to job requirement check, job's step definition will also take into account: for instance if a job has a step running in container, it only matches docker based executors. Or if a job has a step requires to publish html reports, it only matches executors with html publish privilege enabled.
-
Thanks Robin, sounds like it is working as designed. I’ll be sure to specify my executor from now on.
-
Previous Value Current Value Open
Closed
| Type |
Question
|
| Priority |
Normal
|
| Assignee | |
| Labels |
No labels
|
Issue Votes (0)
Watchers (2)
Recently, jobs are failing with
No applicable job executor discovered for current job.I have not changed anything in my
.onedev-buildspec.yml. If I go to Administration > Job Executors and specify one and tell the job to use it, it seems to work.My CI/CD is pretty basic, just publishing some internal Powershell modules to an internal NuGet repository so nothing fancy, but I am not sure if this is a recent change. The last time we made any updates to the modules was back in November 2024 and everything was working great then. I have kept OneDev up to date since then but do not remember reading anything in the release notes about job executor behavior changing, however, I could have overlooked it at some point.
If this is the new expected behavior, that is fine I just want to make sure I am not missing something.