[JIRA] (JENKINS-35170) GHPRB latest version incorrectly identifying the base branch for merge
Title: Message Title Joel Dale commented on JENKINS-35170 Re: GHPRB latest version incorrectly identifying the base branch for merge I'm on 1.33.1 and from what I can tell the right sha1 is being used. The console output from the build is pointing to the right checkpoint. I also have manually added every parameter that the plugin was trying to write. So is this still a bug? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit] (JENKINS-7970) If all JUnit tests are skipped, the build fails
Joel Beaudoin commented on JENKINS-7970 If all JUnit tests are skipped, the build fails Thanks mate. I missed the 'upcoming changes' link. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12002) NPE when saving global config
[
https://issues.jenkins-ci.org/browse/JENKINS-12002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160084#comment-160084
]
Joel Beaudoin edited comment on JENKINS-12002 at 3/9/12 9:01 PM:
-
We are also having the same problem that every attempt to save Jenkins
configuration produces this stacktrace. Thanks for the mention of the
workaround (add space in schedule field) ... we were previously making changes
directly to the configuration .xml's on the filesystem.
Can anyone comment on a timeframe for a fix?
was (Author: joelbdoin):
We are also having the same problem that every attempt to save Jenkins
configuration produces this stacktrace. Thanks for the mention of the
workaround (add space in schedule field) and we were previously making changes
directly to the configuration .xml's on the filesystem.
Can anyone comment on a timeframe for a fix?
NPE when saving global config
-
Key: JENKINS-12002
URL: https://issues.jenkins-ci.org/browse/JENKINS-12002
Project: Jenkins
Issue Type: Bug
Components: maven-repo-cleaner
Environment: Jenkins 1.442
Winstone
Reporter: Christopher Orr
lpe in IRC reported this stack trace when saving the global job configuration.
The Schedule field was empty. He said adding a space to the Schedule field
fixed the problem.
{noformat}
Status Code: 500
Exception:
Stacktrace:
java.lang.NullPointerException
at
org.jenkinsci.plugins.mavenrepocleaner.MavenRepoCleanerProperty$DescriptorImpl.configure(MavenRepoCleanerProperty.java:99)
at jenkins.model.Jenkins.configureDescriptor(Jenkins.java:2560)
at jenkins.model.Jenkins.doConfigSubmit(Jenkins.java:2523)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:282)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:149)
at
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:88)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:104)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:561)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:646)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:477)
at org.kohsuke.stapler.Stapler.service(Stapler.java:159)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12002) NPE when saving global config
[
https://issues.jenkins-ci.org/browse/JENKINS-12002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160084#comment-160084
]
Joel Beaudoin commented on JENKINS-12002:
-
We are also having the same problem that every attempt to save Jenkins
configuration produces this stacktrace. Thanks for the mention of the
workaround (add space in schedule field) and we were previously making changes
directly to the configuration .xml's on the filesystem.
Can anyone comment on a timeframe for a fix?
NPE when saving global config
-
Key: JENKINS-12002
URL: https://issues.jenkins-ci.org/browse/JENKINS-12002
Project: Jenkins
Issue Type: Bug
Components: maven-repo-cleaner
Environment: Jenkins 1.442
Winstone
Reporter: Christopher Orr
lpe in IRC reported this stack trace when saving the global job configuration.
The Schedule field was empty. He said adding a space to the Schedule field
fixed the problem.
{noformat}
Status Code: 500
Exception:
Stacktrace:
java.lang.NullPointerException
at
org.jenkinsci.plugins.mavenrepocleaner.MavenRepoCleanerProperty$DescriptorImpl.configure(MavenRepoCleanerProperty.java:99)
at jenkins.model.Jenkins.configureDescriptor(Jenkins.java:2560)
at jenkins.model.Jenkins.doConfigSubmit(Jenkins.java:2523)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:282)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:149)
at
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:88)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:104)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:561)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:646)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:477)
at org.kohsuke.stapler.Stapler.service(Stapler.java:159)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
