[JIRA] [multijob-plugin] (JENKINS-27371) Parent builds sometimes hang on successful child builds of same type
Daniel Beck commented on JENKINS-27371 Parent builds sometimes hang on successful child builds of same type If something hangs, thread dumps would be helpful. https://wiki.jenkins-ci.org/display/JENKINS/Obtaining+a+thread+dump 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/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-27448) Success and failure trigger work even after setting the cancel variable to true in the pre-send script
Nirav Shah commented on JENKINS-27448 Success and failure trigger work even after setting the cancel variable to true in the pre-send script I am not using any return variable from the script. I just wanted email sending to be cancelled when I set cancel to be true. However, seeing this kind of behaviour it does indicate that the email sending does not solely depend on cancel variable for plugin Or it get over ridden by something fishy in during compilation. 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/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-27448) Success and failure trigger work even after setting the cancel variable to true in the pre-send script
Alex Earl
commented on JENKINS-27448
Success and failure trigger work even after setting the cancel variable to true in the pre-send script
This is how the plugin gets the value of "cancel"
Object output = shell.evaluate(script);
if (output != null) {
pw.println("Result: " + output);
cancel = ((Boolean) shell.getVariable("cancel"));
debug(context.getListener().getLogger(), "Pre-send script set cancel to %b", cancel);
}
The unit tests show that setting cancel to true work, so something else is possibly interfering.
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/d/optout.
[JIRA] [maven-plugin] (JENKINS-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
Ulli Hafner resolved JENKINS-22252 as Fixed Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap Change By: Ulli Hafner (16/Mar/15 9:32 PM) Status: Open Resolved Resolution: Fixed 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/d/optout.
[JIRA] [scoverage-plugin] (JENKINS-27418) NPE in scoverage plugin
SCM/JIRA link daemon commented on JENKINS-27418 NPE in scoverage plugin Code changed in jenkins User: Claudio Bley Path: src/main/java/org/jenkinsci/plugins/scoverage/ScoverageProjectAction.java http://jenkins-ci.org/commit/scoverage-plugin/42eb91cba9b389bbb96aa8041019ec95c80a Log: Avoid NPE in ScoverageProjectAction.doDynamic The exception was thrown when getLastSuccessfulBuildAction returned null. Fixes JENKINS-27418 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/d/optout.
[JIRA] [http_request] (JENKINS-22488) HTTP Redirection 301 and 302 are not followed
Janario Oliveira closed JENKINS-22488 as Fixed HTTP Redirection 301 and 302 are not followed Change By: Janario Oliveira (17/Mar/15 2:51 AM) Status: Resolved Closed 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/d/optout.
[JIRA] [http_request] (JENKINS-21994) Add HTTP header
Janario Oliveira resolved JENKINS-21994 as Fixed Add HTTP header Thanks to James-Chapman who sent a pull request https://github.com/jenkinsci/http-request-plugin/pull/6 Change By: Janario Oliveira (17/Mar/15 1:14 AM) Status: InProgress Resolved Resolution: Fixed 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/d/optout.
[JIRA] [http_request] (JENKINS-22488) HTTP Redirection 301 and 302 are not followed
Janario Oliveira started work on JENKINS-22488 HTTP Redirection 301 and 302 are not followed Change By: Janario Oliveira (17/Mar/15 1:23 AM) Status: Open InProgress 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/d/optout.
[JIRA] [http_request] (JENKINS-18395) Add post-build step
Janario Oliveira commented on JENKINS-18395 Add post-build step It is possible to add more than one build in a single job. Why don't a build right after the build deploy? (As build I mean the build list of a job) 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/d/optout.
[JIRA] [http_request] (JENKINS-18395) Add post-build step
Janario Oliveira assigned JENKINS-18395 to Janario Oliveira Add post-build step Change By: Janario Oliveira (17/Mar/15 1:37 AM) Assignee: JanarioOliveira 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/d/optout.
[JIRA] [gradle-jpi-plugin] (JENKINS-27451) String resources cannot be compiled due to package name clash
Christopher Orr
created JENKINS-27451
String resources cannot be compiled due to package name clash
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
gradle-jpi-plugin
Created:
17/Mar/15 2:13 AM
Description:
I have a plugin where I have Jelly string resources in a description.properties file, e.g. similar to https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/model/Cause/UserIdCause/description.properties
However, this cannot be compiled, as the generated Localizable class is created (in this case as description.java) with a package name that clashes with the source class name.
:compileJava
/home/.../foo-plugin/src/main/java/org/jenkinsci/plugins/foo/FooBarCause.java:8: error: class FooBarCause clashes with package of same name
public class FooBarCause extends Cause {
^
/home/.../foo-plugin/build/generated-src/localizer/org/jenkinsci/plugins/foo/FooBarCause/description.java:3: error: package org.jenkinsci.plugins.foo.FooBarCause clashes with class of
same name
package org.jenkinsci.plugins.foo.FooBarCause;
^
2 errors
:compileJava FAILED
Environment:
Plugin 0.10.0
Project:
Jenkins
Priority:
Minor
Reporter:
Christopher Orr
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/d/optout.
[JIRA] [http_request] (JENKINS-26014) No preemptive authentication
Janario Oliveira commented on JENKINS-26014 No preemptive authentication Patch applied. Thanks. 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/d/optout.
[JIRA] [http_request] (JENKINS-26014) No preemptive authentication
Janario Oliveira resolved JENKINS-26014 as Fixed No preemptive authentication Change By: Janario Oliveira (17/Mar/15 2:13 AM) Status: InProgress Resolved Resolution: Fixed 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/d/optout.
[JIRA] [http_request] (JENKINS-21994) Add HTTP header
Janario Oliveira closed JENKINS-21994 as Fixed Add HTTP header Change By: Janario Oliveira (17/Mar/15 2:51 AM) Status: Resolved Closed 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/d/optout.
[JIRA] [http_request] (JENKINS-22488) HTTP Redirection 301 and 302 are not followed
Janario Oliveira resolved JENKINS-22488 as Fixed HTTP Redirection 301 and 302 are not followed It was already fixed from JENKINS-25801 SystemDefaultHttpClient follows redirect Change By: Janario Oliveira (17/Mar/15 1:31 AM) Status: Open Resolved Resolution: Fixed 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/d/optout.
[JIRA] [core] (JENKINS-27447) LTS 1.596.1 REST api job/api/json?depth=1 produces ERROR 500, Oops page
Daryl Spartz commented on JENKINS-27447 LTS 1.596.1 REST api job/api/json?depth=1 produces ERROR 500, Oops page Does not fail if no builds. Narrowed test case to one build. Attached job config, builds directory, support core bundle. Create job, untar builds tar under job, restart Jenkins, goto: http://your-host:your-port/jenkins/job/globalmedia-lego_core-trunk-deploy-qa1p-gq1/api/json?depth=1 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/d/optout.
[JIRA] [http_request] (JENKINS-26014) No preemptive authentication
SCM/JIRA link daemon commented on JENKINS-26014 No preemptive authentication Code changed in jenkins User: Janario Oliveira Path: src/main/java/jenkins/plugins/http_request/HttpRequest.java src/main/java/jenkins/plugins/http_request/auth/Authenticator.java src/main/java/jenkins/plugins/http_request/auth/BasicDigestAuthentication.java src/main/java/jenkins/plugins/http_request/auth/FormAuthentication.java src/main/java/jenkins/plugins/http_request/util/HttpClientUtil.java http://jenkins-ci.org/commit/http-request-plugin/49fe66a3467283817c417bed91ee35f97f523cc0 Log: JENKINS-26014 No preemptive authentication - applied patch (author Angel López Cima) 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/d/optout.
[JIRA] [http_request] (JENKINS-21994) Add HTTP header
Janario Oliveira started work on JENKINS-21994 Add HTTP header Change By: Janario Oliveira (17/Mar/15 1:12 AM) Status: Open InProgress 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/d/optout.
[JIRA] [http_request] (JENKINS-21994) Add HTTP header
Janario Oliveira assigned JENKINS-21994 to Janario Oliveira Add HTTP header Change By: Janario Oliveira (17/Mar/15 1:13 AM) Assignee: JanarioOliveira 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/d/optout.
[JIRA] [core] (JENKINS-27447) LTS 1.596.1 REST api job/api/json?depth=1 produces ERROR 500, Oops page
Daryl Spartz updated JENKINS-27447 LTS 1.596.1 REST api job/api/json?depth=1 produces ERROR 500, Oops page Change By: Daryl Spartz (17/Mar/15 1:13 AM) Attachment: support.zip Attachment: builds.tar Attachment: config.xml 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/d/optout.
[JIRA] [http_request] (JENKINS-22488) HTTP Redirection 301 and 302 are not followed
Janario Oliveira assigned JENKINS-22488 to Janario Oliveira HTTP Redirection 301 and 302 are not followed Change By: Janario Oliveira (17/Mar/15 1:21 AM) Assignee: JanarioOliveira 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/d/optout.
[JIRA] [http_request] (JENKINS-22488) HTTP Redirection 301 and 302 are not followed
Janario Oliveira updated JENKINS-22488 HTTP Redirection 301 and 302 are not followed Change By: Janario Oliveira (17/Mar/15 1:29 AM) Environment: wehavesomehttpscriptswhichredirecttoothersscripts.THisworksfineusingwgetwhichcorrectlyexecutetheredirect.Butwhenweusehttp_requestplugin,theredirectsarenotfollowed,andsothescriptsarenotexecuted.Whoulditbepossibletoaddtheabilitytofollow301or302redirectslikewgetdoes?Thankyou,Fred Description: wehavesomehttpscriptswhichredirecttoothersscripts.THisworksfineusingwgetwhichcorrectlyexecutetheredirect.Butwhenweusehttp_requestplugin,theredirectsarenotfollowed,andsothescriptsarenotexecuted.Whoulditbepossibletoaddtheabilitytofollow301or302redirectslikewgetdoes?Thankyou,Fred 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/d/optout.
[JIRA] [http_request] (JENKINS-22488) HTTP Redirection 301 and 302 are not followed
Janario Oliveira stopped work on JENKINS-22488 HTTP Redirection 301 and 302 are not followed Change By: Janario Oliveira (17/Mar/15 1:29 AM) Status: InProgress Open 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/d/optout.
[JIRA] [http_request] (JENKINS-26014) No preemptive authentication
Janario Oliveira started work on JENKINS-26014 No preemptive authentication Change By: Janario Oliveira (17/Mar/15 1:57 AM) Status: Open InProgress 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/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-27448) Success and failure trigger work even after setting the cancel variable to true in the pre-send script
Nirav Shah
commented on JENKINS-27448
Success and failure trigger work even after setting the cancel variable to true in the pre-send script
here is my presend script
def env = build.getEnvironment()
String A = envBuild Type;
String B= envInstaller Changed;
logger.println "Build is a " + A + " Build;
if (A == true | B == true)
{ logger.println "Email not sent for Debug Build";
cancel=true;
}
I have a test running which uses robot framework and publishes result as SUCCESS or FAILURE.
Here is what happens at console output even though it prints the email not sent line.
Checking if email needs to be generated
15:31:15 Email was triggered for: Success
15:31:15 Sending email for trigger: Success
15:31:15 NOT overriding default server settings, using Mailer to create session
15:31:15 messageContentType = text/html; charset=UTF-8
15:31:15 Adding recipients from project recipient list
15:31:15 Adding recipients from trigger recipient list
15:31:15 Setting In-Reply-To since last build was not successful
15:31:15 Successfully created MimeMessage
15:31:15 Executing pre-send script
15:31:15 Build is a Debug Build
15:31:15 Email not sent for Debug Build
15:31:15
15:31:15 Sending email to: xx
15:31:15 Finished: SUCCESS
If you have any job with this presend script , the same behaviour is observed.
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/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-27448) Success and failure trigger work even after setting the cancel variable to true in the pre-send script
Alex Earl commented on JENKINS-27448 Success and failure trigger work even after setting the cancel variable to true in the pre-send script A and B are strings, yet you are checking them against true? 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/d/optout.
[JIRA] [multijob-plugin] (JENKINS-27371) Parent builds sometimes hang on successful child builds of same type
Simon Weber commented on JENKINS-27371 Parent builds sometimes hang on successful child builds of same type Is the api change you're thinking of in that specific version? We're still on version 1.593, and I think we saw this behavior on a version 1.565.1 as well. 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/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-27448) Success and failure trigger work even after setting the cancel variable to true in the pre-send script
Nirav Shah commented on JENKINS-27448 Success and failure trigger work even after setting the cancel variable to true in the pre-send script A and B are boolean variables which are of string values true and false (as mentioned in the help function for boolean variables. Also I could see it print and not print depending on values of A and B so that is working. 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/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-27448) Success and failure trigger work even after setting the cancel variable to true in the pre-send script
Nirav Shah commented on JENKINS-27448 Success and failure trigger work even after setting the cancel variable to true in the pre-send script Thanks for the prompt replies. I would say it is still a issue that it works only if cancel=true is the last line in the script. Assume everything else is working just fine. 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/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-27448) Success and failure trigger work even after setting the cancel variable to true in the pre-send script
Daniel Beck commented on JENKINS-27448 Success and failure trigger work even after setting the cancel variable to true in the pre-send script Without looking at the sources, this looks a lot like the return value of the script is used rather than the value of the cancel variable? 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/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-27448) Success and failure trigger work even after setting the cancel variable to true in the pre-send script
Nirav Shah commented on JENKINS-27448 Success and failure trigger work even after setting the cancel variable to true in the pre-send script I guess it got solved. I did two things : 1. Restarted Jenkins. 2. There was another script before which had some print command afte the line cancel=true and I read somewhere that cancel=true has to be the last line in the script. Well now this is a bug that cancel=true works only if it is the last line. Still I got it working for now that way. 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/d/optout.
[JIRA] [git-client-plugin] (JENKINS-27093) Spurious gits scm poll change detection
Kevin Normoyle commented on JENKINS-27093 Spurious gits scm poll change detection I'm totally confused now. I may not be able to reproduce the problem I went back and upgraded all my jenkins servers to git plugin 2.3.5 and did a apt-get install jenkins --reinstall to get the latest 1.604 jenksin and now they seem to all be polling correctly and not detecting changes (because the branch didn't change) They all have that "already built by .." message ..that says what the prior build was, which is good Git Polling Log Started on Mar 16, 2015 6:20:00 AM Using strategy: Default poll Last Built Revision: Revision 1dad640e7ec50cea3965522efa8c797a3ea9b3bc (origin/seb_jenkins) git ls-remote -h https://github.com/h2oai/h2o-dev.git # timeout=10 poll Latest remote head revision on origin/seb_jenkins is: 1dad640e7ec50cea3965522efa8c797a3ea9b3bc - already built by 44 Done. Took 1.7 sec No changes 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/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-12290) Lockup when using trigger/call builds on other projects and Block until the triggered projects finish their builds is used with only 1 executo
Dominic Cleal commented on JENKINS-12290 Lockup when using trigger/call builds on other projects and Block until the triggered projects finish their builds is used with only 1 executor I think what Roland's describing is the "flyweight" job which is used for matrix jobs - a job that doesn't use an executor slot. It'd be interesting if when blocking for a triggered job, the triggering process could be changed to a flyweight, the triggered job inherits the slot and then it swaps back on completion, or for the builder to get a temporary additional slot as the blocked process won't be using much in the way of resources. 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/d/optout.
[JIRA] [dashboard-view-plugin] (JENKINS-27439) FATAL : Failed to serialize jenkins.model.Jenkins#views
Raghav Vaidhyanathan created JENKINS-27439 FATAL : Failed to serialize jenkins.model.Jenkins#views Issue Type: Bug Assignee: Peter Hayes Attachments: JenkinsException.txt Components: dashboard-view-plugin, matrix-auth-plugin, nested-view-plugin Created: 16/Mar/15 2:26 PM Description: I dont know since when but I often see Jenkins failed to Serialize exception and I am suspecting that the installation of Dashboard view and Nested view in particular has caused the problem. I am attaching the detailed exception trace. This is quite fatal as application changes are not persisted and all of the changes have to be redone in case of a system restart. Environment: Jenkins ver. 1.602 Dashboard View 2.9.4 Nested View 1.14 Matrix Auth Plugin 1.2 Project: Jenkins Labels: plugin jenkins Priority: Critical Reporter: Raghav Vaidhyanathan 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/d/optout.
[JIRA] [core] (JENKINS-27353) Matrix Job: Build Cause is always UpstreamCause
Sverre Moe commented on JENKINS-27353 Matrix Job: Build Cause is always UpstreamCause I understand that B/default was triggered by the build of B. However I was looking for the cause in the middle. I did not see that Cause.UpstreamCause had method getUpstreamCauses() as I was mostly just looking into Cause. That fixes my problem actually. I thought it might be a bug, but does not look like it any more. 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/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-27438) Gerrit Trigger NPE causes folder not to load
Ben Courliss updated JENKINS-27438 Gerrit Trigger NPE causes folder not to load Change By: Ben Courliss (16/Mar/15 1:39 PM) Environment: Jenkins LTS 1.580.3 , (installedstandaloneusingbuiltinwebcontainer) Cloudbeesenterprisepluginsinstalled , LinuxRHEL6.5 , Javaversion1.7.0_76 , GerritTriggerPlugin2.12.0 Description: Foldercontainingjobsdisappeared.I triedreloadingtheconfigfromthefilesystemoptionandIstill see thesameerrormessage.Otherteamfoldersarevisibleandworkingcorrectly.Gerrittriggerfunctionalityseemstoworkaswell.IcanhitthequeryandtriggerGerritPatcheslinkanditworksfine.Isee inthelogs:Mar16,201512:35:20PMjenkins.InitReactorRunner$1onTaskFailedSEVERE:FailedLoadingjobteam_xyzjava.lang.NullPointerException atcom.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTrigger.start(GerritTrigger.java:396) atcom.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTrigger.start(GerritTrigger.java:124) athudson.model.AbstractProject.onLoad(AbstractProject.java:325) athudson.model.Project.onLoad(Project.java:95) athudson.model.Items.load(Items.java:279) athudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:108) atcom.cloudbees.hudson.plugins.folder.Folder.onLoad(Folder.java:239) athudson.model.Items.load(Items.java:279) athudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:108) atcom.cloudbees.hudson.plugins.folder.Folder.onLoad(Folder.java:239) athudson.model.Items.load(Items.java:279) athudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:108) atcom.cloudbees.hudson.plugins.folder.Folder.onLoad(Folder.java:239) athudson.model.Items.load(Items.java:279) atjenkins.model.Jenkins$17.run(Jenkins.java:2656) atorg.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) atorg.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) atjenkins.model.Jenkins$7.runTask(Jenkins.java:886) atorg.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) atorg.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) atjava.lang.Thread.run(Thread.java:745) 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/d/optout.
[JIRA] [groovy-postbuild-plugin] (JENKINS-27317) Run Groovy script only on matrix parent
Sverre Moe commented on JENKINS-27317 Run Groovy script only on matrix parent I have created a project called template-project. This has Build script and Post build actions used on all my projects. It helps with not having to update the same build script 70 times over. Created a new Multi-Configuration project that does not use builders or publishers from another project. Added just one Groovy Postbuild. Same result. Parent: #1 16-Mar-2015 15:08 "no parent ShortText" Configuration 1: #1 16-Mar-2015 15:08 child Configuration 2: #1 16-Mar-2015 15:08 child 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/d/optout.
[JIRA] [cloudbees-folder-plugin] (JENKINS-27138) All build history lost after moving a job to the folder
Igor Komrakov commented on JENKINS-27138 All build history lost after moving a job to the folder I've upgraded jenkins to 1.602. Jenkins is on Ubuntu 14.04. When I click "move" on job to another folder first time - I get error: directory lastUnsuccessfulBuil doesn't exist. So, I looked at filesystem, this is not a folder - it is a link (points to -1 if there is no unsuccessful builds). I tried to point all these "specific folders" to some builds folders. Moving was done without errors after that. But these "specific folders" are real folders now. And jenkins doesn't want showing build history anyway. Can someone confirm such behaviour? 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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26121) Input step should maintain audit record
valentina armenise edited a comment on JENKINS-26121 Input step should maintain audit record The rejected action was already audited in the summary UI since it extends the CauseOfInterruption: https://github.com/jenkinsci/workflow-plugin/blob/0294f3305d665170931c781abca47aa40f46c25a/support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/input/Rejection.java#L12 which is in the core: https://github.com/jenkinsci/jenkins/blob/68b383e0b2cdd2b1403a13a4284dc1a2d3e03e12/core/src/main/resources/jenkins/model/CauseOfInterruption/summary.groovy The rejected action was also logged by the FlowInterruptedExpection class: https://github.com/jenkinsci/workflow-plugin/blob/master/support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/input/InputStepExecution.java#L179 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/d/optout.
[JIRA] [git-client-plugin] (JENKINS-27093) Spurious gits scm poll change detection
Kanstantsin Shautsou commented on JENKINS-27093 Spurious gits scm poll change detection Hi, sorry was busy with fixing other bad plugins. Please, don't wait me I also hope that author of this regression will resolve itself. Kevin, could you reproduce this issue with clean job, that will track 1 branch and provide 2 build.xml files with build/polling logs for them? (Linux kernel is really big) 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/d/optout.
[JIRA] [debian-package-builder-plugin] (JENKINS-27437) Debian package should allow to pass parameters to dpkg-buildpackage
Luigi Sandon created JENKINS-27437 Debian package should allow to pass parameters to dpkg-buildpackage Issue Type: Improvement Assignee: Unassigned Components: debian-package-builder-plugin Created: 16/Mar/15 1:17 PM Description: Debian Package Builder has no option to easily pass parameters to dpkg-buildpackage, for example to build a binary package without source code. A configuration option to set dpkg-buildpackage (or simply pass the desired ones) would be very welcome. Actually, the only way it to set the DEBUILD_DPKG_BUILDPACKAGE_OPTS environment variable, but it means parameters are not easily visible when checking debian package builder settings. Project: Jenkins Priority: Major Reporter: Luigi Sandon 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/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-27438) Gerrit Trigger NPE causes folder not to load
Ben Courliss created JENKINS-27438 Gerrit Trigger NPE causes folder not to load Issue Type: Bug Assignee: rsandell Components: gerrit-trigger-plugin Created: 16/Mar/15 1:31 PM Description: Folder containing jobs disappeared. I see in the logs: Mar 16, 2015 12:35:20 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job team_xyz java.lang.NullPointerException at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTrigger.start(GerritTrigger.java:396) at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTrigger.start(GerritTrigger.java:124) at hudson.model.AbstractProject.onLoad(AbstractProject.java:325) at hudson.model.Project.onLoad(Project.java:95) at hudson.model.Items.load(Items.java:279) at hudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:108) at com.cloudbees.hudson.plugins.folder.Folder.onLoad(Folder.java:239) at hudson.model.Items.load(Items.java:279) at hudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:108) at com.cloudbees.hudson.plugins.folder.Folder.onLoad(Folder.java:239) at hudson.model.Items.load(Items.java:279) at hudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:108) at com.cloudbees.hudson.plugins.folder.Folder.onLoad(Folder.java:239) at hudson.model.Items.load(Items.java:279) at jenkins.model.Jenkins$17.run(Jenkins.java:2656) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:886) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Environment: Jenkins 1.580.3, Cloudbees enterprise plugins installed, Linux RHEL 6.5, Java version 1.7.0_76, Gerrit Trigger Plugin 2.12.0 Project: Jenkins Priority: Critical Reporter: Ben Courliss 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/d/optout.
[JIRA] [core] (JENKINS-27440) Cannot restrict job running on one node
ale n created JENKINS-27440 Cannot restrict job running on one node Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: core, matrix-project-plugin, parameterized-trigger-plugin Created: 16/Mar/15 2:31 PM Description: I have two nodes where I'm running my tests, one is on WinXP (QA1), and the other one Win8 (QA2). I'm trying to run a job ONLY on QA1, and I've tried restricting the job in several ways, but none of them work: 1. Restrict where this project can be run option in the job's configuration 2. Using Parametrized Trigger Plugin, where I've set both Default nodes and Possible nodes to QA1 3. Using Matrix Project Plugin, where I've added a Slave Axis and selected only QA1 from the Individual nodes list. In this case, I created a new Multi-Configuration Project in Jenkins and I've only cloned the tests project from GitHub on the QA1 machine before the tests started running (QA2 did not have the project on disk). When I ran the job, it executed the git pull command I've set as a build step on QA1 and then the tests started running on QA2. I cannot seem to restrict it from running on QA2. Any help would be highly appreciated! Environment: Jenkins 1.602, Parametrized Trigger Plugin, Matrix Project Plugin, Selenium Grid, Selenium WebDriver 2.45, Firefox 34 Project: Jenkins Priority: Blocker Reporter: ale n 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/d/optout.
[JIRA] [debian-package-builder-plugin] (JENKINS-27437) Debian package should allow to pass parameters to dpkg-buildpackage
Luigi Sandon commented on JENKINS-27437 Debian package should allow to pass parameters to dpkg-buildpackage It looks it's even worse... if debuild is invoked without the --no-conf option it will read configuration from /etc/devscripts.conf and ~/.devscripts, and will ignore environment variables. No way then to pass per project options. 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/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-27139) Active Directory plugin doesn't work, in attempt to be connected to the domain controler on the Internet
movavi team
updated JENKINS-27139
Active Directory plugin doesnt work, in attempt to be connected to the domain controler on the Internet
Change By:
movavi team
(16/Mar/15 9:35 AM)
Description:
Useversion:latestActiveDirectoryplugin1.39latestJenkinsver.1.599Ataplug-inconfiguration,thereisamistakeprovidedbelow.Theappealtoportofthecontrolerofthedomaindoesnthappen.{code
:title=ERROR
}javax.servlet.ServletException:java.lang.NumberFormatException:Forinputstring:4f8:0:a102::add: atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:876) atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:876) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:649) atorg.kohsuke.stapler.Stapler.service(Stapler.java:238) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:848) atorg.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) atnet.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:198) atnet.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:176) atnet.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) atorg.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:99) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) athudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) athudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) athudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) atorg.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) atorg.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474)
[JIRA] [workflow-plugin] (JENKINS-26121) Input step should maintain audit record
valentina armenise commented on JENKINS-26121 Input step should maintain audit record The rejected action was already audited since it extends the CauseOfInterruption: https://github.com/jenkinsci/workflow-plugin/blob/0294f3305d665170931c781abca47aa40f46c25a/support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/input/Rejection.java#L12 which is in the core: https://github.com/jenkinsci/jenkins/blob/68b383e0b2cdd2b1403a13a4284dc1a2d3e03e12/core/src/main/resources/jenkins/model/CauseOfInterruption/summary.groovy 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/d/optout.
[JIRA] [core] (JENKINS-27256) Jenkins Remote API - Queue behavior changed
Morgwai Kotarbinski commented on JENKINS-27256 Jenkins Remote API - Queue behavior changed that's strange: it works for me and others here also reported it works for them... 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/d/optout.
[JIRA] [core] (JENKINS-27256) Jenkins Remote API - Queue behavior changed
Barthélémy von Haller commented on JENKINS-27256 Jenkins Remote API - Queue behavior changed Yes, I must be doing something wrong. 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/d/optout.
[JIRA] [core] (JENKINS-27256) Jenkins Remote API - Queue behavior changed
Barthélémy von Haller commented on JENKINS-27256 Jenkins Remote API - Queue behavior changed I installed the plugin but to no avail. I am still getting a 404 when going to server/jenkins/queue/item/13/ A fix is urgently needed. Our build system is partially broken because of this. Thank you for the very quick reaction and assessment of the situation. 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/d/optout.
[JIRA] [git-client-plugin] (JENKINS-27093) Spurious gits scm poll change detection
Kevin Normoyle commented on JENKINS-27093 Spurious gits scm poll change detection I am having the problem of polling always deciding that there were changes. I have a master with many branches and I want to just look at one branch. there were many past problems in this area, so it was confusing looking at jiras in 2014 Finally I found this jira. The code in question that decides if there were changes, had a big change Feb 3, 2015 look here for the diff see where the buildData.hasBeenBuilt(head) continue; has been been replaced by other code https://github.com/jenkinsci/git-plugin/commit/70857d247d1ef3ab57f7ce047b8d4c7fe88aa4f3#diff-f1f2ff967f38c8b53a4901be3169035e I took the hint from above and reverted my git-plugin from 2.3.5 to 2.3.4 (not all the way back to 2.3.3) I finally got the git polling log to say "no changes" rather than changes all the time. However I also added a "git checkout $BRANCH" to my build script. So I have to isolate whether that may have helped. The comment about headless git stuff got me wondering about whether a "git checkout $BRANCH" would help get my workspace into a "good" state. I don't use the workspace polling additional thing though. here's evidence that I was able to get it to to not detect a change. Before, I was seeing what others are reporting above: the sha's were the same but it was still detecting changes. I suspect the code change at the above url isn't exactly right. Started on Mar 16, 2015 3:15:00 AM Using strategy: Default poll Last Built Revision: Revision f79163c96d12a2277de247c0d8c530db0a9b606c (origin/brandon_jenkins) git ls-remote -h https://github.com/h2oai/h2o-dev.git brandon_jenkins # timeout=10 poll Latest remote head revision is: f79163c96d12a2277de247c0d8c530db0a9b606c Done. Took 1.9 sec No changes -kevin 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/d/optout.
[JIRA] [cloudbees-folder-plugin] (JENKINS-27355) Move several jobs into a folder at the same time
valentina armenise started work on JENKINS-27355 Move several jobs into a folder at the same time Change By: valentina armenise (16/Mar/15 10:45 AM) Status: Open InProgress 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/d/optout.
[JIRA] [cloudbees-folder-plugin] (JENKINS-27355) Move several jobs into a folder at the same time
valentina armenise assigned JENKINS-27355 to valentina armenise Move several jobs into a folder at the same time Change By: valentina armenise (16/Mar/15 10:45 AM) Assignee: FélixBelzunceArcos valentinaarmenise 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/d/optout.
[JIRA] [core] (JENKINS-27256) Jenkins Remote API - Queue behavior changed
Morgwai Kotarbinski edited a comment on JENKINS-27256 Jenkins Remote API - Queue behavior changed @Barthélémy von Haller, Please read Daniel Beck's comment about the plugin again carefully: it's 'queuefix' not 'queue' in the URI. You can use some http proxy to rewrite it for you if changing your client side is not an acceptable solution. 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/d/optout.
[JIRA] [core] (JENKINS-27256) Jenkins Remote API - Queue behavior changed
Barthélémy von Haller commented on JENKINS-27256 Jenkins Remote API - Queue behavior changed @Morgwai Kotarbinski, Indeed, I overlooked the address. Unfortunately, it does not work either. I restarted Jenkins after installing the plugin and the plugin is said to be installed. Well, I guess that we will wait for the fix. 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/d/optout.
[JIRA] [git-client-plugin] (JENKINS-27093) Spurious gits scm poll change detection
Kevin Normoyle commented on JENKINS-27093 Spurious gits scm poll change detection Hi Kanstantsin, yes I'll do that. I have to use another server with 2.3.5 plugin. Those servers have to stay at 2.3.4 now that they seem to work (I actually didn't check now that they see changes correctly, I have both scheduled and polled build on them. but I'll find out in a day or two whether they build on changes) I'll get the files you mention with another test job. -kevin 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/d/optout.
[JIRA] [git-client-plugin] (JENKINS-27093) Spurious gits scm poll change detection
Kevin Normoyle commented on JENKINS-27093 Spurious gits scm poll change detection I'm trying on another server, and oddly it seemed to work. I may have to restore the original server to 2.3.5 to get the failing case I'm using two different branches but the setups are the same. But look here. there are two different messages in the polling logs from these two servers. On the 'Latest remote head revision.." line.. one says "already built by 2" (build #2) so something weird made this first case "work". ..but the 2nd case failed when git plugin was at 2.3.5 apparently jenkins is now at 1.604. I've since upgraded both to 1.604 to get jenkins version questions eliminated. this is one machine that I thought would fail (always detect changes), but apparently didn't. jenkins was at 1.602 git plugin 2.3.5 git client 1.16.1 Git Polling Log Started on Mar 16, 2015 5:27:00 AM Using strategy: Default poll Last Built Revision: Revision 61afd429821a5850a04c9a4870062189a359ca69 (origin/kevin_jenkins) git --version # timeout=10 git -c core.askpass=true ls-remote -h https://github.com/h2oai/h2o-dev.git # timeout=10 poll Latest remote head revision on origin/kevin_jenkins is: 61afd429821a5850a04c9a4870062189a359ca69 - already built by 2 Done. Took 0.79 sec No changes When I did a commit/push, it correctly detected the change with the poll.. Polling Log View as plain text This page captures the polling log that triggered this build. Started on Mar 16, 2015 5:31:00 AM Using strategy: Default poll Last Built Revision: Revision 61afd429821a5850a04c9a4870062189a359ca69 (origin/kevin_jenkins) git --version # timeout=10 git -c core.askpass=true ls-remote -h https://github.com/h2oai/h2o-dev.git # timeout=10 poll Latest remote head revision on origin/kevin_jenkins is: e1f6277d4489a067b1ccf2b4ab6be57d148e5879 Done. Took 0.74 sec Changes found the other machine says no changes also, but it doesn't have that "already built by" message I am trying with a different branch here, but same repo. this is the machine that failed with 2.3.5 (too many builds) and now correctly detects "no changes" with 2.3.4 jenkins was at 1.602 git plugin 2.3.4 (downgraded manually form 2.3.5) git client plugin 1.16.1 Git Polling Log Started on Mar 16, 2015 5:17:00 AM Using strategy: Default poll Last Built Revision: Revision f79163c96d12a2277de247c0d8c530db0a9b606c (origin/tomk_jenkins) git ls-remote -h https://github.com/h2oai/h2o-dev.git tomk_jenkins # timeout=10 poll Latest remote head revision is: f79163c96d12a2277de247c0d8c530db0a9b606c Done. Took 2.1 sec No changes 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/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-27139) Active Directory plugin doesn't work, in attempt to be connected to the domain controler on the Internet
Daniel Beck commented on JENKINS-27139 Active Directory plugin doesnt work, in attempt to be connected to the domain controler on the Internet Could be that JNDI cannot handle IPv6. I'd check whether that's a possible issue with the Java version used. 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/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-14608) Crash on firefox 14.0.1
Kanstantsin Shautsou resolved JENKINS-14608 as Cannot Reproduce Crash on firefox 14.0.1 Change By: Kanstantsin Shautsou (16/Mar/15 10:40 AM) Status: Open Resolved Resolution: CannotReproduce 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/d/optout.
[JIRA] [core] (JENKINS-27436) 'Check Now' function seems to have no effect
davida2009 created JENKINS-27436 Check Now function seems to have no effect Issue Type: Bug Assignee: Unassigned Components: core Created: 16/Mar/15 11:45 AM Description: In Manage Jenkins Plugin Center, if I click 'Check Now' I am taken to the 'Installing Plugins/Upgrades' page. I don't see the relevance of that page to this function. I just want to stay on the page that lists the available updates. Also, when I return to Manage Jenkins Plugin Center the update time is still shown as a day or so ago. So the 'Check now' seems to have had no effect. 'Use browser for metadata download' is unchecked. Environment: Jenkins 1.602 Chrome browser Project: Jenkins Labels: user-experience Priority: Minor Reporter: davida2009 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/d/optout.
[JIRA] [core] (JENKINS-27256) Jenkins Remote API - Queue behavior changed
Morgwai Kotarbinski commented on JENKINS-27256 Jenkins Remote API - Queue behavior changed @Barthélémy von Haller, Read Daniel Beck's comment about the plugin again carefully: it's 'queuefix' not 'queue' in the URI. you can use some http proxy to rewrite it for you if changing your client side is not an acceptable solution. 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/d/optout.
[JIRA] [findbugs-plugin] (JENKINS-8174) no details in findbugs view
Ulli Hafner resolved JENKINS-8174 as Cannot Reproduce no details in findbugs view Just tried with LTS 1.596.1 and Findbugs 4.60 and Analysis Core 1.71: works quite well. Can you please try with these components (and no other plugins installed?). If not please create a new issue with details about your setup and environment. Or you can check by downloading the acceptance test harness and running the following command: BROWSER=chrome mvn -Dtest=FindBugsPluginTest#should_find_warnings_in_freestyle_job Change By: Ulli Hafner (16/Mar/15 11:52 AM) Status: Reopened Resolved Resolution: CannotReproduce 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/d/optout.
[JIRA] [envinject-plugin] (JENKINS-27287) EnvInject plugin 1.91 causes javax.servlet.ServletException in job view
David Rubio commented on JENKINS-27287 EnvInject plugin 1.91 causes javax.servlet.ServletException in job view Version 1.91.1 seems to fix this problem, see JENKINS-27342 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/d/optout.
[JIRA] [mstestrunner-plugin] (JENKINS-14791) MSTest to support /testmetadata use instead of solely /testcontainer
Ivo Bellin Salarin updated JENKINS-14791 MSTest to support /testmetadata use instead of solely /testcontainer Change By: Ivo Bellin Salarin (16/Mar/15 3:01 PM) Component/s: mstestrunner-plugin Component/s: mstest-plugin 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/d/optout.
[JIRA] [git-plugin] (JENKINS-27444) Git revision information displays information regarding last build
T.B. Anton created JENKINS-27444 Git revision information displays information regarding last build Issue Type: Bug Assignee: Nicolas De Loof Attachments: shown_revision_vs_requested_branch.png Components: git-plugin Created: 16/Mar/15 4:49 PM Description: Visiting the build page shortly after a new build has been started, the revision information displayed is from the last build. Obviously, Jenkins only knows the details on the current revision after the SCM step is done. However, on several occassions this has lead to confusion among our users, who thought something was going wrong and aborted the build. How about not displaying revision information until it is available? Would that be possible? Environment: Jenkins 1.580.2, Git Plugin 2.3.2 Project: Jenkins Labels: user-experience gui Priority: Minor Reporter: T.B. Anton 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/d/optout.
[JIRA] [mstest-plugin] (JENKINS-17506) MsTest plugin doesn't parse and display the TextMessages from the Output tag.
SCM/JIRA link daemon resolved JENKINS-17506 as Fixed MsTest plugin doesnt parse and display the TextMessages from the Output tag. Change By: SCM/JIRA link daemon (16/Mar/15 2:56 PM) Status: Open Resolved Resolution: Fixed 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/d/optout.
[JIRA] [mstest-plugin] (JENKINS-17506) MsTest plugin doesn't parse and display the TextMessages from the Output tag.
SCM/JIRA link daemon commented on JENKINS-17506 MsTest plugin doesnt parse and display the TextMessages from the Output tag. Code changed in jenkins User: nilleb Path: src/main/resources/hudson/plugins/mstest/mstest-to-junit.xsl src/test/resources/hudson/plugins/mstest/JENKINS-17506.trx http://jenkins-ci.org/commit/mstest-plugin/cee1feeeb4bd731b514c0c5f5155fb4f5e7b2be5 Log: FIXED JENKINS-17506 support for TextMessages (standard output of mstest unit tests) 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/d/optout.
[JIRA] [mstest-plugin] (JENKINS-17610) MSTest plugin don't show VSTS standard console output message for passed test cases in Jenkins.
Ivo Bellin Salarin commented on JENKINS-17610 MSTest plugin dont show VSTS standard console output message for passed test cases in Jenkins. I assume that this issue was a duplicate of the JENKINS-17506. If this wasn't the case, please reopen the issue providing adequate test material (i.e. a trw which shows where the problem is). 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/d/optout.
[JIRA] [core] (JENKINS-27441) hudson.model.Run.getLog throws IndexOutOfBoundsException when called with 0
Valentin Batz updated JENKINS-27441 hudson.model.Run.getLog throws IndexOutOfBoundsException when called with 0 Change By: Valentin Batz (16/Mar/15 3:33 PM) Description: Igetastacktracewhenconfiguringa pluging plugin toincludenologentrieswhenpostingjobnotification:java.lang.IndexOutOfBoundsException:Index:0,Size:0 atjava.util.LinkedList.entry(LinkedList.java:382) atjava.util.LinkedList.set(LinkedList.java:345) athudson.model.Run.getLog(Run.java:1963) atcom.tikal.hudson.plugins.notification.Phase.getLog(Phase.java:141) atcom.tikal.hudson.plugins.notification.Phase.buildJobState(Phase.java:79) atcom.tikal.hudson.plugins.notification.Phase.handle(Phase.java:42) atcom.tikal.hudson.plugins.notification.JobListener.onStarted(JobListener.java:31) athudson.model.listeners.RunListener.fireStarted(RunListener.java:213) athudson.model.Run.execute(Run.java:1747) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) athudson.model.ResourceController.execute(ResourceController.java:89) athudson.model.Executor.run(Executor.java:240) 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/d/optout.
[JIRA] [core] (JENKINS-27441) hudson.model.Run.getLog throws IndexOutOfBoundsException when called with 0
Valentin Batz created JENKINS-27441 hudson.model.Run.getLog throws IndexOutOfBoundsException when called with 0 Issue Type: Bug Assignee: Unassigned Components: core Created: 16/Mar/15 3:31 PM Description: I get a stacktrace when configuring a pluging to include no log entries when posting job notification: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.LinkedList.entry(LinkedList.java:382) at java.util.LinkedList.set(LinkedList.java:345) at hudson.model.Run.getLog(Run.java:1963) at com.tikal.hudson.plugins.notification.Phase.getLog(Phase.java:141) at com.tikal.hudson.plugins.notification.Phase.buildJobState(Phase.java:79) at com.tikal.hudson.plugins.notification.Phase.handle(Phase.java:42) at com.tikal.hudson.plugins.notification.JobListener.onStarted(JobListener.java:31) at hudson.model.listeners.RunListener.fireStarted(RunListener.java:213) at hudson.model.Run.execute(Run.java:1747) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Project: Jenkins Priority: Minor Reporter: Valentin Batz 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/d/optout.
[JIRA] [core] (JENKINS-27443) PATH environment variable incorrect on slaves
Cameron Horn created JENKINS-27443 PATH environment variable incorrect on slaves Issue Type: Bug Assignee: Unassigned Components: core Created: 16/Mar/15 3:59 PM Description: Jenkins 1.599: Path E:\BoxTone\Database\BoxToneDB\bin;E:\BoxTone\sql-client;E:\BoxTone\utilities\CSVUpload;E:\BoxTone\dlls;E:\BoxTone\maintenancewindow\bin;E:\BoxTone\rails\ruby\bin;E:\BoxTone\Database\BoxToneDB\OHS\jlibs;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft\Exchange Server\bin;C:\Program Files\Microsoft\Exchange Server\Scripts Jenkins 1.602 Path C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft\Exchange Server\bin;C:\Program Files\Microsoft\Exchange Server\Scripts Project: Jenkins Priority: Minor Reporter: Cameron Horn 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/d/optout.
[JIRA] [crowd-plugin] (JENKINS-17288) Packaging of spring-context-support causes crowd plugin to prevent Jenkins starting properly
C2PA IT commented on JENKINS-17288 Packaging of spring-context-support causes crowd plugin to prevent Jenkins starting properly Still an issue for us as well. 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/d/optout.
[JIRA] [mstest-plugin] (JENKINS-17610) MSTest plugin don't show VSTS standard console output message for passed test cases in Jenkins.
Ivo Bellin Salarin resolved JENKINS-17610 as Duplicate MSTest plugin dont show VSTS standard console output message for passed test cases in Jenkins. Change By: Ivo Bellin Salarin (16/Mar/15 2:59 PM) Status: Open Resolved Resolution: Duplicate 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/d/optout.
[JIRA] [groovy-postbuild-plugin] (JENKINS-27317) Run Groovy script only on matrix parent
Sverre Moe edited a comment on JENKINS-27317 Run Groovy script only on matrix parent @danielbeck: Groovy Postbuild was updated last year with an implementation of MatrixAggregatable https://issues.jenkins-ci.org/browse/JENKINS-21924 @ikedam: I have created a project called template-project. This has Build script and Post build actions used on all my projects. It helps with not having to update the same build script 70 times over. Created a new Multi-Configuration project that does not use builders or publishers from another project. Added just one Groovy Postbuild. Same result. Parent: #1 16-Mar-2015 15:08 "no parent ShortText" Configuration 1: #1 16-Mar-2015 15:08 child Configuration 2: #1 16-Mar-2015 15:08 child 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/d/optout.
[JIRA] [core] (JENKINS-27442) Failed to record SCM polling for hudson.model.FreeStyleProject
Cameron Horn created JENKINS-27442 Failed to record SCM polling for hudson.model.FreeStyleProject Issue Type: Bug Assignee: Unassigned Components: core Created: 16/Mar/15 3:55 PM Description: SCM polling is failing for multiple projects, using multiple SCMs (git and svn). Jenkins 1.599 Log excerpt: Mar 15, 2015 4:36:28 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@5f0bc88b7.5-CORE_rails_ios-enrollment-api java.lang.NullPointerException Mar 15, 2015 4:36:28 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@3ee89b6d7.5_rails_ios-enrollment-api java.lang.NullPointerException Mar 15, 2015 4:36:28 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@271d900d7.5patch216_uss java.lang.NullPointerException Mar 15, 2015 4:36:28 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@347e4f517.5patch358_uss java.lang.NullPointerException Mar 15, 2015 4:36:28 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@55f55e9f8.0_active-directory java.lang.NullPointerException Mar 15, 2015 4:36:28 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@54da11b4heavyseas_active-directory java.lang.NullPointerException Mar 15, 2015 4:36:28 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@6a04009trunk_active-directory java.lang.NullPointerException Mar 15, 2015 4:36:28 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@5c6647cbtrunk_user-device-service java.lang.NullPointerException Project: Jenkins Priority: Major Reporter: Cameron Horn 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/d/optout.
[JIRA] [core] (JENKINS-27440) Cannot restrict job running on one node
Daniel Beck commented on JENKINS-27440 Cannot restrict job running on one node Make sure QA2 does not have "QA1" in its labels. 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/d/optout.
[JIRA] [mstestrunner-plugin] (JENKINS-14791) MSTest to support /testmetadata use instead of solely /testcontainer
Ivo Bellin Salarin commented on JENKINS-14791 MSTest to support /testmetadata use instead of solely /testcontainer fixed component 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/d/optout.
[JIRA] [mstest-plugin] (JENKINS-19384) Adding stdout to be displayed in your test results
Ivo Bellin Salarin resolved JENKINS-19384 as Duplicate Adding stdout to be displayed in your test results duplicate of JENKINS-17506 Change By: Ivo Bellin Salarin (16/Mar/15 3:03 PM) Status: Open Resolved Resolution: Duplicate 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/d/optout.
[JIRA] [groovy-postbuild-plugin] (JENKINS-27317) Run Groovy script only on matrix parent
Sverre Moe edited a comment on JENKINS-27317 Run Groovy script only on matrix parent @danielbeck: Groovy Postbuild was updated last year with an implementation of MatrixAggregatable https://github.com/jenkinsci/groovy-postbuild-plugin/commit/4dfeeec7f670cf29de62a3b93eb89b6bd6623328 I have created a project called template-project. This has Build script and Post build actions used on all my projects. It helps with not having to update the same build script 70 times over. Created a new Multi-Configuration project that does not use builders or publishers from another project. Added just one Groovy Postbuild. Same result. Parent: #1 16-Mar-2015 15:08 "no parent ShortText" Configuration 1: #1 16-Mar-2015 15:08 child Configuration 2: #1 16-Mar-2015 15:08 child 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/d/optout.
[JIRA] [groovy-postbuild-plugin] (JENKINS-27317) Run Groovy script only on matrix parent
Sverre Moe edited a comment on JENKINS-27317 Run Groovy script only on matrix parent @danielbeck: Groovy Postbuild was updated last year with an implementation of MatrixAggregatable https://issues.jenkins-ci.org/browse/JENKINS-21924 I have created a project called template-project. This has Build script and Post build actions used on all my projects. It helps with not having to update the same build script 70 times over. Created a new Multi-Configuration project that does not use builders or publishers from another project. Added just one Groovy Postbuild. Same result. Parent: #1 16-Mar-2015 15:08 "no parent ShortText" Configuration 1: #1 16-Mar-2015 15:08 child Configuration 2: #1 16-Mar-2015 15:08 child 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/d/optout.
[JIRA] [core] (JENKINS-27256) Jenkins Remote API - Queue behavior changed
Daniel Beck
commented on JENKINS-27256
Jenkins Remote API - Queue behavior changed
When running the following in Manage Jenkins, Script Console:
Jenkins.instance.getExtensionList(RootAction).each { println it.urlName } ; return
It should show an entry "queuefix" (among other items). Otherwise, something probably went wrong when loading the plugin. Check the Jenkins log.
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/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-27139) Active Directory plugin doesn't work, in attempt to be connected to the domain controler on the Internet
Daniel Beck commented on JENKINS-27139 Active Directory plugin doesnt work, in attempt to be connected to the domain controler on the Internet Weird, because the string in the error message looks a lot like an IPv6 address. And it happens when JNDI accesses the NS DNS record for the host name you specify IIUC. 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/d/optout.
[JIRA] [groovy-postbuild-plugin] (JENKINS-27317) Run Groovy script only on matrix parent
Daniel Beck commented on JENKINS-27317 Run Groovy script only on matrix parent Thanks, I saw that when I checked after ikedam's very true comment. 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/d/optout.
[JIRA] [core] (JENKINS-27441) hudson.model.Run.getLog throws IndexOutOfBoundsException when called with 0
Daniel Beck commented on JENKINS-27441 hudson.model.Run.getLog throws IndexOutOfBoundsException when called with 0 It is not clear what you're doing to get this error. Could you please provide more details? https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue 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/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-27139) Active Directory plugin doesn't work, in attempt to be connected to the domain controler on the Internet
movavi team edited a comment on JENKINS-27139 Active Directory plugin doesnt work, in attempt to be connected to the domain controler on the Internet Nevertheless I risked to lose access to settings and I applied all changes. Authorization earned, but in attempt to test settings I receive the same set of messages that brought above. I applied an example of settings in the form of the picture. If to make through a domain name which was set and entered 2 and more addresses in advance, authorization doesn't work any more, it is necessary to list addresses of servers in "Domain Controller", then works with alternation. 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/d/optout.
[JIRA] [core] (JENKINS-27443) PATH environment variable incorrect on slaves
Cameron Horn commented on JENKINS-27443 PATH environment variable incorrect on slaves Env-inject is installed, and was recently updated. It is not enabled on the slave jobs, and the path shows up incorrectly on the node | system information page. Jenkins master path: c:\app\oracle\product\11.2.0\dbhome_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Graphviz 2.28\bin;C:\Program Files\7-Zip;c:\cygwin\bin;C:\Program Files\Microsoft Windows Performance Toolkit\;C:\Program Files\TortoiseSVN\bin 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/d/optout.
[JIRA] [maven-plugin] (JENKINS-4561) Delete All Disabled Modules Not visible for project users
Skylar Sutton commented on JENKINS-4561 Delete All Disabled Modules Not visible for project users Experiencing this on v1.597 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/d/optout.
[JIRA] [mailer-plugin] (JENKINS-26740) Failed to set Jenkins Identity header on email. java.lang.NullPointerException
shane knapp commented on JENKINS-26740 Failed to set Jenkins Identity header on email. java.lang.NullPointerException also happens w/mailer 1.15 and jenkins 1.604. 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/d/optout.
[JIRA] [ec2-plugin] (JENKINS-27445) java.lang.NullPointerException in tag support
Mariusz Dalewski created JENKINS-27445 java.lang.NullPointerException in tag support Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 16/Mar/15 6:16 PM Description: Mar 16, 2015 7:01:56 PM hudson.slaves.NodeProvisioner update WARNING: Provisioned slave jenkins-spot-ami (...) failed to launch java.lang.NullPointerException at hudson.plugins.ec2.SlaveTemplate.provisionSpot(SlaveTemplate.java:655) at hudson.plugins.ec2.SlaveTemplate.provision(SlaveTemplate.java:285) at hudson.plugins.ec2.EC2Cloud$1.call(EC2Cloud.java:398) at hudson.plugins.ec2.EC2Cloud$1.call(EC2Cloud.java:394) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Code in SlaveTemplate.java:655 doesn't work. If tags variable is empty hasCustomTypeTag is still false, and inst_tags is null. Environment: =1.25 Project: Jenkins Priority: Minor Reporter: Mariusz Dalewski 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/d/optout.
[JIRA] [core] (JENKINS-27446) Rerun SecretRewriter
Jesse Glick moved JENKINS-27446 Rerun SecretRewriter Change By: Jesse Glick (16/Mar/15 6:21 PM) Project: SecurityIssues Jenkins Key: SECURITY JENKINS - 174 27446 Workflow: Securityv1.2 JNJira Component/s: core Component/s: core 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/d/optout.
[JIRA] [core] (JENKINS-27441) hudson.model.Run.getLog throws IndexOutOfBoundsException when called with 0
Daniel Beck commented on JENKINS-27441 hudson.model.Run.getLog throws IndexOutOfBoundsException when called with 0 How many log lines did you configure for the endpoint? 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/d/optout.
[JIRA] [dashboard-view-plugin] (JENKINS-27439) FATAL : Failed to serialize jenkins.model.Jenkins#views
Daniel Beck resolved JENKINS-27439 as Not A Defect FATAL : Failed to serialize jenkins.model.Jenkins#views Clearly caused by the Environment Dashboard Plugin which doesn't track its issues on this site for whatever braindead reason. Resolving as Not A Defect, as there's no better suitable reason. Change By: Daniel Beck (16/Mar/15 5:31 PM) Status: Open Resolved Assignee: PeterHayes Resolution: NotADefect 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/d/optout.
[JIRA] [core] (JENKINS-27441) hudson.model.Run.getLog throws IndexOutOfBoundsException when called with 0
Valentin Batz commented on JENKINS-27441 hudson.model.Run.getLog throws IndexOutOfBoundsException when called with 0 Steps to reproduce: Jenkins 1.604 notification plugin version 1.9 installed Create a new free style job. Add a HTTP Notification Endpoint pointing to some request endpoint created on http://requestb.in/ Set Event to All Events Run the job, the exception noted in description will occur instead of a HTTP POST to the created notification Endpoint. 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/d/optout.
[JIRA] [core] (JENKINS-27443) PATH environment variable incorrect on slaves
Cameron Horn commented on JENKINS-27443 PATH environment variable incorrect on slaves 1.602 specific madness? Will upgrade Jenkins and disable env-inject when I can. 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/d/optout.
[JIRA] [core] (JENKINS-27256) Jenkins Remote API - Queue behavior changed
SCM/JIRA link daemon commented on JENKINS-27256 Jenkins Remote API - Queue behavior changed Code changed in jenkins User: tfennelly Path: changelog.html cli/pom.xml core/pom.xml core/src/main/java/hudson/model/AbstractItem.java debian/debian/changelog plugins/pom.xml pom.xml test/pom.xml war/pom.xml http://jenkins-ci.org/commit/jenkins/7e5063937c31ee33de29254f1f13f5d4aa0d6174 Log: Merge branch 'master' into JENKINS-27256 master: Updated changelog updated changelog as a part of the release maven-release-plugin prepare for next development iteration maven-release-plugin prepare release jenkins-1.604 Noting #1597 Noting #1593, #1579, move JENKINS-22346, #1558 Remove two fixes that were backported to RC JENKINS-27183 Avoid deadlock when using build-monitor-plugin 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/d/optout.
[JIRA] [core] (JENKINS-27443) PATH environment variable incorrect on slaves
Daniel Beck commented on JENKINS-27443 PATH environment variable incorrect on slaves Did you recently install or upgrade the env-inject plugin? What is the path on Jenkins master? 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/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-27139) Active Directory plugin doesn't work, in attempt to be connected to the domain controler on the Internet
movavi team commented on JENKINS-27139 Active Directory plugin doesnt work, in attempt to be connected to the domain controler on the Internet Nevertheless I risked to lose access to settings and I applied all changes. Authorization earned, but in attempt to test settings I receive the same set of messages that brought above. I applied an example of settings in the form of the picture. 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/d/optout.
[JIRA] [core] (JENKINS-27353) Matrix Job: Build Cause is always UpstreamCause
Daniel Beck resolved JENKINS-27353 as Not A Defect Matrix Job: Build Cause is always UpstreamCause getUpstreamCauses(), for UpstreamCause provides original causes. Change By: Daniel Beck (16/Mar/15 5:19 PM) Status: Open Resolved Assignee: KohsukeKawaguchi Resolution: NotADefect 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/d/optout.
[JIRA] [core] (JENKINS-27443) PATH environment variable incorrect on slaves
Daniel Beck commented on JENKINS-27443 PATH environment variable incorrect on slaves Env-Inject does all sort of madness even if disabled. Try downgrading that again to see what happens if possible. 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/d/optout.
[JIRA] [core] (JENKINS-27443) PATH environment variable incorrect on slaves
Cameron Horn commented on JENKINS-27443 PATH environment variable incorrect on slaves Will upgrade Jenkins and downgrade env-inject, I mean. 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/d/optout.
[JIRA] [build-monitor-plugin] (JENKINS-27183) Deadlock when renaming and updating item in the same view
SCM/JIRA link daemon commented on JENKINS-27183 Deadlock when renaming and updating item in the same view Code changed in jenkins User: tfennelly Path: changelog.html cli/pom.xml core/pom.xml core/src/main/java/hudson/model/AbstractItem.java debian/debian/changelog plugins/pom.xml pom.xml test/pom.xml war/pom.xml http://jenkins-ci.org/commit/jenkins/7e5063937c31ee33de29254f1f13f5d4aa0d6174 Log: Merge branch 'master' into JENKINS-27256 master: Updated changelog updated changelog as a part of the release maven-release-plugin prepare for next development iteration maven-release-plugin prepare release jenkins-1.604 Noting #1597 Noting #1593, #1579, move JENKINS-22346, #1558 Remove two fixes that were backported to RC JENKINS-27183 Avoid deadlock when using build-monitor-plugin 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/d/optout.
