Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Find possible type errors in jobdefinitions on jobserver start (migrated) #32

Open
michaelschnyder opened this issue Mar 27, 2017 · 0 comments
Labels
Milestone

Comments

@michaelschnyder
Copy link
Member

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.

@michaelschnyder 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
@olibanjoli olibanjoli added this to the vNext milestone Apr 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants