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
originally posted by @michaelschnyder on Mar 22, 2015 on the old repo
When a job has an incorrect Type for the class, this gets an error while executing the job since the CLR-Type of the JobClass cannot be found. (Already implemented, Fails at the end)
Proposed change:
Give the JobbrServer the possibility to check (maybe with the help of the runner) all defined jobs and warn for not existing type-names.
The text was updated successfully, but these errors were encountered:
michaelschnyder
changed the title
When a job has an incorrect Type for the class, this gets an error while executing the job since the CLR-Type of the JobClass cannot be found. (Already implemented, Fails at the end) Proposed change: Give the JobbrServer the possibility to check (maybe with the help of the runner) all defined jobs and warn for not existing type-names. (migrated)
Find possible type errors in jobdefinitions on jobserver start (migrated)
Mar 27, 2017
originally posted by @michaelschnyder on Mar 22, 2015 on the old repo
When a job has an incorrect Type for the class, this gets an error while executing the job since the CLR-Type of the JobClass cannot be found. (Already implemented, Fails at the end)
Proposed change:
Give the JobbrServer the possibility to check (maybe with the help of the runner) all defined jobs and warn for not existing type-names.
The text was updated successfully, but these errors were encountered: