![]() |
|
|
|
|
Issue Type:
|
![New Feature]() New Feature
|
|
Assignee:
|
Unassigned |
|
Components:
|
maven |
|
Created:
|
24/Dec/13 1:50 PM
|
|
Description:
|
We have a problem where some developers try to use the maven job type instead of just invocing maven on command line. Unfortunately, this results in over 600 job records being defined for every invocation of this particular job, which basically brings Jenkins server to a crawl with multi-minute hangs/etc.
Since developers won't properly communicate - is there any way to effectively just disable this job type?
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Nathan Neulinger
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
