![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Jerry Maloney
|
|
Components:
|
mercurial |
|
Created:
|
29/Mar/13 2:06 PM
|
|
Description:
|
Version 1.506 of Jenkins and version 1.44 of the Mercurial plugin.
My users were having the issue that, when working against a repository that has an hg hook that triggers a Jenkins job, running hg push from a console would cause the process to hang permanently, until it was killed. I tracked down the issue to a NullPointerException that was not handled by handleNotifyCommit.
This only occurs if there is at least one Jenkins project that (A) has Source Code Management enabled and (B) does not have a Repository URL entered. This is a situation that shouldn't happen – there's no use case for it – but in an environment where we let individual developers control their own Jenkins projects, mistakes happen. Everyone in the organization should not suffer because of another developer's mistake.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Jerry Maloney
|
|
|
|
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.
