[JIRA] [envinject-plugin] (JENKINS-27765) Environment Injector plugin Null Pointers
Title: Message Title Ajay Yadav commented on JENKINS-27765 Re: Environment Injector plugin Null Pointers Me too had same issue but Solved after updating to 1.91.2 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28294) "JDK 5 not supported with Maven" error with JDK 6
Title: Message Title Falko Schumann commented on JENKINS-28294 Re: "JDK 5 not supported with Maven" error with JDK 6 I can also reproduce this with maven-project-plugin 2.8 and 2.9 using Maven 3.2. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28294) "JDK 5 not supported with Maven" error with JDK 6
Title: Message Title Falko Schumann edited a comment on JENKINS-28294 Re: "JDK 5 not supported with Maven" error with JDK 6 I can also reproduce this with maven-project-plugin 2.8 and 2.9 using Maven 3.2 and Oracle SDKs JDKs . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28294) "JDK 5 not supported with Maven" error with JDK 6
Title: Message Title Falko Schumann edited a comment on JENKINS-28294 Re: "JDK 5 not supported with Maven" error with JDK 6 I can also reproduce this with maven-project-plugin 2.8 and 2.9 using Maven 3.2 and Oracle SDKs . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28234) javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class" for Jmeter maven project
Title: Message Title Jason Zheng commented on JENKINS-28234 Re: javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class" for Jmeter maven project I am encountering the same problem. Hope it gets fixed soon. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [delivery-pipeline-plugin] (JENKINS-28347) Doesn't detect promotion "Trigger/call builds on other projects"
Title: Message Title Glen Mailer created an issue Jenkins / JENKINS-28347 Doesn't detect promotion "Trigger/call builds on other projects" Issue Type: Improvement Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 12/May/15 7:57 AM Priority: Minor Reporter: Glen Mailer The delivery pipeline plugin has the functionality to detect downstream jobs which are configured as promotions using the "Trigger parameterised build on other projects" action, but not the "Trigger/call builds on other projects". Is this something that could be added? I prefer the "Trigger/call builds on other projects" job as I can block the trigger until it completes and mark failure/success. Add Comment
[JIRA] [delivery-pipeline-plugin] (JENKINS-28348) Cannot use number from version number plugin as pipeline version
Title: Message Title Glen Mailer created an issue Jenkins / JENKINS-28348 Cannot use number from version number plugin as pipeline version Issue Type: Improvement Assignee: Patrik Boström Attachments: Screen Shot 2015-05-12 at 09.00.19.png Components: delivery-pipeline-plugin Created: 12/May/15 8:05 AM Priority: Minor Reporter: Glen Mailer The pipeline version task seems to run before the version generator task from https://wiki.jenkins-ci.org/display/JENKINS/Version+Number+Plugin - so the variable isn't set at this point. eg. with the following config I get these environment variables [build] $ /bin/sh -xe /tmp/hudson4088077174362603015.sh + env HUDSON_SERVER_COOKIE=9882fe58cbf3bb2d SHELL=/bin/bash SSH_CLIENT=--- BUILD_TAG=--- GIT_PREVIOUS_COMMIT=da17c63d09f6fa3799d0c07157cdf8b34d0e2e1b WORKSPACE=/home/jenkins/workspace/build USER=jenkins NLSPATH=/usr/dt/lib/nls/msg/%L/%N.cat JENKINS_HOME=/var/lib/jenkins GIT_COMMIT=da17c63d09f6fa3799d0c07157cdf8b34d0e2e1b MAIL=/var/mail/jenkins PATH=/usr/local/bin:/bin:/usr/bin _=/bin/env PWD=/home/jenkins/workspace/build JOB_NAME=build BUILD_VERSION=v-2015-05-12-r1 BUI
[JIRA] [email-ext-plugin] (JENKINS-28349) Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher
Title: Message Title
Heena Chauhan created an issue
Jenkins / JENKINS-28349
Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher
Issue Type:
Bug
Assignee:
Alex Earl
Components:
email-ext-plugin
Created:
12/May/15 8:05 AM
Labels:
configuration jenkins
Priority:
Blocker
Reporter:
Heena Chauhan
While I click save for saving the Editable Email Notification after customizing the trigger for always , the below is message is get. It does not allow me to save.
A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace
javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher from {"project_disabled":false,"project_recipient_list":"$DEFAULT_RECIPIENTS","project_replyto":"$DEFAULT_REPLYTO","project_content_type":"default","project_default_subject":"$DEFAULT_SUBJECT","proje
[JIRA] [claim-plugin] (JENKINS-27091) No longer compiles (since Jenkins Core 1.561)
Title: Message Title Christian Bremer started work on JENKINS-27091 Change By: Christian Bremer Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [claim-plugin] (JENKINS-27091) No longer compiles (since Jenkins Core 1.561)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27091 Re: No longer compiles (since Jenkins Core 1.561) Code changed in jenkins User: ki82 Path: pom.xml http://jenkins-ci.org/commit/claim-plugin/a69fbfd5d2644a44d101c66082803ff20cbc933d Log: Merge pull request #16 from jan-molak/master JENKINS-27091 Compatibility with Jenkins core 1.577 and newer Compare: https://github.com/jenkinsci/claim-plugin/compare/e120f9c38ac2...a69fbfd5d264 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28349) Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher
Title: Message Title Heena Chauhan commented on JENKINS-28349 Re: Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher I made some changes and the email notfications saved. After the build ran, following is the message the console output displayed BUILD SUCCESSFUL Total time: 43 seconds Email was triggered for: Always Sending email for trigger: Always Sending email to: chauhanhe...@gmail.com Connection error sending email, retrying once more in 10 seconds... Connection error sending email, retrying once more in 10 seconds... Failed after second try sending email Finished: SUCCESS Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [claim-plugin] (JENKINS-27091) No longer compiles (since Jenkins Core 1.561)
Title: Message Title Christian Bremer resolved as Fixed Released in 2.7 Jenkins / JENKINS-27091 No longer compiles (since Jenkins Core 1.561) Change By: Christian Bremer Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [repository-connector-plugin] (JENKINS-28323) Add RELEASE and LATEST to version selection dropdown list
Title: Message Title Michael Rumpf edited a comment on JENKINS-28323 Re: Add RELEASE and LATEST to version selection dropdown list Resolved with https://github.com/jenkinsci/repository-connector-plugin/pull/ 8 9 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [repository-connector-plugin] (JENKINS-28323) Add RELEASE and LATEST to version selection dropdown list
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28323 Re: Add RELEASE and LATEST to version selection dropdown list Code changed in jenkins User: mrumpf Path: src/main/java/org/jvnet/hudson/plugins/repositoryconnector/VersionParameterDefinition.java http://jenkins-ci.org/commit/repository-connector-plugin/f0035fd9acd1d3aeb20d1ee75e6e3a52ccdcc217 Log: JENKINS-28323 : Added special versions RELEASE and LATEST to the version selection dropdown list (incl. order reversal to make the later versions appear on top of the list) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [repository-connector-plugin] (JENKINS-27641) Name of version selection build parameter should be customized
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27641 Re: Name of version selection build parameter should be customized Code changed in jenkins User: Michael Rumpf Path: src/main/java/org/jvnet/hudson/plugins/repositoryconnector/VersionParameterDefinition.java src/main/java/org/jvnet/hudson/plugins/repositoryconnector/VersionParameterValue.java src/main/resources/org/jvnet/hudson/plugins/repositoryconnector/VersionParameterDefinition/config.jelly src/main/resources/org/jvnet/hudson/plugins/repositoryconnector/VersionParameterDefinition/config.properties src/main/resources/org/jvnet/hudson/plugins/repositoryconnector/VersionParameterDefinition/config_de.properties http://jenkins-ci.org/commit/repository-connector-plugin/9d9175fb8de509d94733f28c51f63205a4d9e7f7 Log: Merge pull request #9 from mrumpf/master Fixes for JENKINS-28323 and JENKINS-27641 . All tests are fine. Compare: https://github.com/jenkinsci/repository-connector-plugin/compare/a75b5e676155...9d9175fb8de5 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [repository-connector-plugin] (JENKINS-28323) Add RELEASE and LATEST to version selection dropdown list
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28323 Re: Add RELEASE and LATEST to version selection dropdown list Code changed in jenkins User: Michael Rumpf Path: src/main/java/org/jvnet/hudson/plugins/repositoryconnector/VersionParameterDefinition.java src/main/java/org/jvnet/hudson/plugins/repositoryconnector/VersionParameterValue.java src/main/resources/org/jvnet/hudson/plugins/repositoryconnector/VersionParameterDefinition/config.jelly src/main/resources/org/jvnet/hudson/plugins/repositoryconnector/VersionParameterDefinition/config.properties src/main/resources/org/jvnet/hudson/plugins/repositoryconnector/VersionParameterDefinition/config_de.properties http://jenkins-ci.org/commit/repository-connector-plugin/9d9175fb8de509d94733f28c51f63205a4d9e7f7 Log: Merge pull request #9 from mrumpf/master Fixes for JENKINS-28323 and JENKINS-27641 . All tests are fine. Compare: https://github.com/jenkinsci/repository-connector-plugin/compare/a75b5e676155...9d9175fb8de5 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [repository-connector-plugin] (JENKINS-27641) Name of version selection build parameter should be customized
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27641 Re: Name of version selection build parameter should be customized Code changed in jenkins User: mrumpf Path: src/main/java/org/jvnet/hudson/plugins/repositoryconnector/VersionParameterDefinition.java src/main/java/org/jvnet/hudson/plugins/repositoryconnector/VersionParameterValue.java src/main/resources/org/jvnet/hudson/plugins/repositoryconnector/VersionParameterDefinition/config.jelly src/main/resources/org/jvnet/hudson/plugins/repositoryconnector/VersionParameterDefinition/config.properties src/main/resources/org/jvnet/hudson/plugins/repositoryconnector/VersionParameterDefinition/config_de.properties http://jenkins-ci.org/commit/repository-connector-plugin/8b485b775caa72f15bd4e455ddf68e23bb413a32 Log: JENKINS-27641 : Made the parameter name configurable. When the propertyName field is left empty, the default property groupId.artifactId=value is set. If the propertyName is set then the parameter propertyName=value will be passed to the build. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-19163) Use REST API for commenting on changes
Title: Message Title Orgad Shaneh commented on JENKINS-19163 Re: Use REST API for commenting on changes reping Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [cli] (JENKINS-28346) Inconsistent CLI failiures
Title: Message Title Daniel Beck commented on JENKINS-28346 Re: Inconsistent CLI failiures Does it fail randomly for the same user, on the same machine? As the error is in SSH Key authentication, it is dependent on your environment. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28294) "JDK 5 not supported with Maven" error with JDK 6
Title: Message Title Daniel Beck commented on JENKINS-28294 Re: "JDK 5 not supported with Maven" error with JDK 6 Jenkins 1.612 moved to a Java 6 requirement as you can see in the changelog, it's possible this is just the wrong error message with the '5' hard-coded. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28294) "JDK 5 not supported with Maven" error with JDK 6
Title: Message Title Daniel Beck edited a comment on JENKINS-28294 Re: "JDK 5 not supported with Maven" error with JDK 6 Jenkins 1.612 moved to a Java 6 requirement as you can see in the changelog, it's possible this is just the wrong error message with the '5' hard-coded. Since the (mis)design of the Maven Project Plugin results in tight integration between Maven and Jenkins, it wouldn't be surprising if you were now unable to run builds with JDK 6 or earlier with it without additional effort. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [p4-plugin] (JENKINS-28213) Force syncing a workspace that does not exist on the filesystem causes a FileNotFoundException
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28213 Re: Force syncing a workspace that does not exist on the filesystem causes a FileNotFoundException Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/client/ClientHelper.java src/main/java/org/jenkinsci/plugins/p4/credentials/P4Credentials.java src/main/java/org/jenkinsci/plugins/p4/workspace/Workspace.java http://jenkins-ci.org/commit/p4-plugin/939279eb79f7f48a8a7dbb70f6b9d5288d2d86ff Log: Merge pull request #11 from rpocase/master JENKINS-28213 Force syncing a workspace that does not exist on the filesystem causes a FileNotFoundException Compare: https://github.com/jenkinsci/p4-plugin/compare/f830dd453a2e...939279eb79f7 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27948) Script timeout during start of configure a jenkins job
Title: Message Title Krzysztof Malinowski commented on JENKINS-27948 Re: Script timeout during start of configure a jenkins job Thank you, I could not find it However, I actually get both issues, JENKINS-26445 and JENKINS-27948, so I would suggest they might be related. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-26445) Browser freezes when clicking more link on a job to see other builds
Title: Message Title Krzysztof Malinowski commented on JENKINS-26445 Re: Browser freezes when clicking more link on a job to see other builds Also have this problem when there is a long list of builds. Firefox developer tools console logs: Error: Script terminated by timeout at: Element.Methods.removeClassName@https://server:8080/static/63938483/scripts/prototype.js:2371:9 getElementOverflowParams@https://server:8080/static/63938483/scripts/hudson-behavior.js:1952:5 checkRowCellOverflows@https://server:8080/static/63938483/scripts/hudson-behavior.js:1693:37 checkAllRowCellOverflows@https://server:8080/static/63938483/scripts/hudson-behavior.js:1883:13 updateBuilds/<.onSuccess@https://server:8080/static/63938483/scripts/hudson-behavior.js:1927:21 Ajax.Request<.respondToReadyState@https://server:8080/static/63938483/scripts/prototype.js:1655:10 Ajax.Request<.onStateChange@https://server:8080/static/63938483/scripts/prototype.js:1600:7 bind/<@https://server:8080/static/63938483/scripts/prototype.js:414:14 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-17667) Unable to kill a job which is running
Title: Message Title Ozgur Kaya resolved as Fixed Disable the job and then enable the job.. You will see that all jobs has killed and not rerunning. Jenkins / JENKINS-17667 Unable to kill a job which is running Change By: Ozgur Kaya Status: Reopened Resolved Assignee: Jesse Glick Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-27977) NullPointer & authentication cancelled occure immediately on SVN checkout
Title: Message Title Romuald Fleury commented on JENKINS-27977 Re: NullPointer & authentication cancelled occure immediately on SVN checkout Up ! it is a big problem for us to not be able to use HTTPS with Jenkins :s Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-17667) Unable to kill a job which is running
Title: Message Title Ozgur Kaya assigned an issue to Aswini Rajasekaran Jenkins / JENKINS-17667 Unable to kill a job which is running Change By: Ozgur Kaya Assignee: Aswini Rajasekaran Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-22129) H/2 * * * * is polling every second minute, but H/1 * * * * only once per hour
Title: Message Title Daniel Beck commented on JENKINS-22129 Re: H/2 * * * * is polling every second minute, but H/1 * * * * only once per hour with an offset of a random number of seconds Wasn't the random seconds offset resolved as a bug? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [slave-status-plugin] (JENKINS-25195) Jenkins jobs start but periodically hang on newly restarted slave
Title: Message Title nyoung02 commented on JENKINS-25195 Re: Jenkins jobs start but periodically hang on newly restarted slave Also seen on Windows 7 Slave using Oracle Java 1.8.0_45 - Jenkins 1.549 and more recent builds 1.6.x Slave is connected using java -jar slave.jar -jnlpUrl http://myserver/computer/myslave/slave-agent.jnlp Disconnecting and reconnecting the slave sometimes kicks it back into life. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-17667) Unable to kill a job which is running
Title: Message Title Daniel Beck commented on JENKINS-17667 Re: Unable to kill a job which is running I didn't want to disseminate data onto different JIRA issues A good idea as long as it never misleads or contradicts. As soon as that happens it's a mess and you need to figure out what's going on. Since you can mark jobs as being related, this shouldn't be an issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28350) LInk to polling log for builds started by upstream doesn't work
Title: Message Title Peter Kristiansen created an issue Jenkins / JENKINS-28350 LInk to polling log for builds started by upstream doesn't work Issue Type: Bug Assignee: Unassigned Attachments: build.PNG, upstreamjob.PNG Components: core Created: 12/May/15 11:55 AM Environment: Jenkins: 1.602 Priority: Minor Reporter: Peter Kristiansen I'm not sure if it should be the Jenkins Core, but I couldn't see any plugins which related to this. The issue is that for builds which are started by upstream project the link "Started by an SCM change" points to a non-existant location (http://build/pollingLog), where build is the name of our server. See the build.png, the link circled in red. The Upstreamjob.png attachment shows the definition of the upstream job
[JIRA] [openshift-deployer-plugin] (JENKINS-28351) no support for ssh options such as proxy tunnel
Title: Message Title
david crosson created an issue
Jenkins / JENKINS-28351
no support for ssh options such as proxy tunnel
Issue Type:
Bug
Assignee:
Siamak Sadeghianfar
Components:
openshift-deployer-plugin
Created:
12/May/15 12:08 PM
Environment:
ALL
Priority:
Major
Reporter:
david crosson
No SSH options is supported in openshift-deployer-plugin, and as jsch is used, there's no workaround possible. If standard git, or ssh commands were used then it would be possible to add a ~/.ssh/config file with extra SSH configuration such as proxy tunnel.
For example : {{ $ cat ~/.ssh/config Host *.mycompany.fr ProxyCommand proxytunnel -E -p tunnel.mycompany.fr:443 -d "%h:%p" TCPKeepAlive yes StrictHostKeyChecking no }}
jsch support various options, such as proxy tunnel, would be possible to make them configurable for both direct usage by openshift-deployer-plugin but also for jgit ?
Typical error I get : {{ [OPENSHIFT] Deployments found: [/var/jenkins_home/jobs/primesui/workspace/target/scala-2.11/primesui_2.11-0.1.2.war] [OPENSHIFT] Deploying to OpenShift at http://broker.x.mycompany.fr. Be patient! It might take a minute... [OPENSHIFT] Deployging /var/jenkins_home/jobs/primesui/workspace/target/scala-2.11/primesui_2.11-0.1.2.war [OPENSHIFT] Starting SS
[JIRA] [ssh-plugin] (JENKINS-24402) jsch version
Title: Message Title Quim Calpe commented on JENKINS-24402 Re: jsch version Tested locally and solves related issues https://issues.jenkins-ci.org/browse/JENKINS-25412 & https://issues.jenkins-ci.org/browse/JENKINS-25258 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-25416) text parameter with newlines causing the default goal run
Title: Message Title Oliver Gondža commented on JENKINS-25416 Re: text parameter with newlines causing the default goal run After a great deal of googling around I am starting to think it is not possible to pass newline in an argument of cmd.exe. I would love to be proven wrong. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [p4-plugin] (JENKINS-28343) Add quiet option to p4-plugin sync
Title: Message Title Robby Pocase started work on JENKINS-28343 Change By: Robby Pocase Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [p4-plugin] (JENKINS-28237) p4-plugin does not provide accurate polling results in workflow job
Title: Message Title Robby Pocase stopped work on JENKINS-28237 Change By: Robby Pocase Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [p4-plugin] (JENKINS-28343) Add quiet option to p4-plugin sync
Title: Message Title Robby Pocase assigned an issue to Robby Pocase Jenkins / JENKINS-28343 Add quiet option to p4-plugin sync Change By: Robby Pocase Assignee: Robby Pocase Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [p4-plugin] (JENKINS-28343) Add quiet option to p4-plugin sync
Title: Message Title Robby Pocase commented on JENKINS-28343 Re: Add quiet option to p4-plugin sync I'm looking at adding a checkbox to enable this under the populate field. It seems like it would be better as a global option currently, but in the future it might be nice to configure "quiet" on a per task basis (e.g., quiet sync, quiet reconcile, etc). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28349) Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher
Title: Message Title Alex Earl commented on JENKINS-28349 Re: Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher What did you change to make it work? Also, did you setup your mail server information in the global config? Is this a new install of Jenkins or did you upgrade recently? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [jenkins-testswarm] (JENKINS-28352) Jenkins restart hangs
Title: Message Title rajesh kumar created an issue Jenkins / JENKINS-28352 Jenkins restart hangs Issue Type: Bug Assignee: Unassigned Components: jenkins-testswarm Created: 12/May/15 1:19 PM Priority: Major Reporter: rajesh kumar I am starting jenkins with java -DsessionTimeout=1440 -jar jenkins.war After that If I try to restart jenkins by issuing restart request from browser then Jenkins hangs with error message WARNING: Failed to restart Hudson java.io.IOException: Failed to exec '' No such file or directory at hudson.lifecycle.UnixLifecycle.restart(UnixLifecycle.java:84) at jenkins.model.Jenkins$22.run(Jenkins.java:3357) Add Comment
[JIRA] [core] (JENKINS-28350) LInk to polling log for builds started by upstream doesn't work
Title: Message Title Daniel Beck assigned an issue to Daniel Beck Jenkins / JENKINS-28350 LInk to polling log for builds started by upstream doesn't work Change By: Daniel Beck Assignee: Daniel Beck Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28350) LInk to polling log for builds started by upstream doesn't work
Title: Message Title Daniel Beck commented on JENKINS-28350 Re: LInk to polling log for builds started by upstream doesn't work Weird, I thought I'd fixed this forever ago in https://github.com/jenkinsci/jenkins/pull/1250 – probably something wrong with the fix that was applied shortly after because that change broke Jenkins. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [jenkins-testswarm] (JENKINS-28352) Jenkins restart hangs
Title: Message Title Daniel Beck resolved as Incomplete Too little information about your environment to investigate further (e.g. Java version, OS and version, whether there are other warnings/errors in the log, etc.) Please follow the instructions on https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue Jenkins / JENKINS-28352 Jenkins restart hangs Change By: Daniel Beck Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-26757) "Error cloning remote repo 'origin'" with username:passw...@bitbucket.org URLs
Title: Message Title Alexander Uvizhev commented on JENKINS-26757 Re: "Error cloning remote repo 'origin'" with username:passw...@bitbucket.org URLs I've the same problem and in one case it appeared in jobs running on 'master'. What solved problem in this case was putting ssh key in /.ssh/id_rsa. So it seems it's a ssh access issue. What's bad - there are no records about the problem in jenkins log. Now I have the second case. The same symptoms but on JClouds provided slaves and I wonder what should I do. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [jenkins-testswarm] (JENKINS-28352) Jenkins restart hangs
Title: Message Title rajesh kumar updated an issue Jenkins / JENKINS-28352 Jenkins restart hangs Change By: rajesh kumar Environment: jenkins: 1.611 Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28352) Jenkins restart hangs
Title: Message Title rajesh kumar reopened an issue Jenkins / JENKINS-28352 Jenkins restart hangs Change By: rajesh kumar Resolution: Incomplete Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28352) Jenkins restart hangs
Title: Message Title rajesh kumar updated an issue Jenkins / JENKINS-28352 Jenkins restart hangs Change By: rajesh kumar Component/s: core Component/s: jenkins-testswarm Environment: jenkins: 1.611 jdk7u71 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28352) Jenkins restart hangs
Title: Message Title rajesh kumar updated an issue Jenkins / JENKINS-28352 Jenkins restart hangs Change By: rajesh kumar Environment: jenkins: 1.611jdk7u71 Solaris os 5.10 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [testlink-plugin] (JENKINS-26000) Invalid processing of suite-files in testng
Title: Message Title aurelien dubois commented on JENKINS-26000 Re: Invalid processing of suite-files in testng Hello. I have exactly the same problem described below Jenkins Version : 1.613 Plugin Version : 3.10 A correction time is it planned? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-25416) text parameter with newlines causing the default goal run
Title: Message Title Oliver Gondža assigned an issue to Unassigned Jenkins / JENKINS-25416 text parameter with newlines causing the default goal run Change By: Oliver Gondža Assignee: Oliver Gondža Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [cli] (JENKINS-28346) Inconsistent CLI failiures
Title: Message Title Raymond Accary commented on JENKINS-28346 Re: Inconsistent CLI failiures Hi Daniel, It's the same user. Two machines submitting to the same master often fail. However, I spent some time looking at things yesterday, and I realized that even in the case where the CLI build submission is actually invoked, the log would still show: May 12, 2015 6:41:53 AM WARNING org.jenkinsci.main.modules.cli.auth.ssh.SshCliAuthenticator authenticate CLI authentication failure java.io.EOFException at java.io.DataInputStream.readUnsignedShort(DataInputStream.java:323) at java.io.DataInputStream.readUTF(DataInputStream.java:572) at java.io.DataInputStream.readUTF(DataInputStream.java:547) at hudson.cli.Connection.readUTF(Connection.java:85) at hudson.cli.Connection.verifyIdentity(Connection.java:244) at org.jenkinsci.main.modules.cli.auth.ssh.SshCliAuthenticator.authenticate(SshCliAuthenticator.java:39) at hudson.cli.CliManagerImpl$2.run(CliManagerImpl.java:109) Any ideas? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-14157) allow to set subversion workspace version per slave
Title: Message Title dan russell commented on JENKINS-14157 Re: allow to set subversion workspace version per slave Was looking for something similar where you could specify the subversion version in the same way you would a jdk. I have recently updated our jenkins and servers to use svn 1.8, but we have some older builds that need hotfixes that use svnkit and ant, which are currently 1.5 Obviously easier to switch subversion version on a server than it is to update an unknown number of branches/tags with a newer svn version. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-14690) allow to set subversion workspace version per job
Title: Message Title dan russell commented on JENKINS-14690 Re: allow to set subversion workspace version per job Was looking for something similar where you could specify the subversion version in the same way you would a jdk. I have recently updated our jenkins and servers to use svn 1.8, but we have some older builds that need hotfixes that use svnkit and ant, which are currently 1.5 Obviously easier to switch subversion version on a server than it is to update an unknown number of branches/tags with a newer svn version Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-26757) "Error cloning remote repo 'origin'" with username:passw...@bitbucket.org URLs
Title: Message Title Mark Waite commented on JENKINS-26757 Re: "Error cloning remote repo 'origin'" with username:passw...@bitbucket.org URLs Alexander Uvizhev I am surprised that you're having a problem which is specific to bitbucket and a username / password embedded directly in the URL. From other bug reports, it seems you're using GitHub Enterprise, not bitbucket. Up to this time, I've only heard of this problem affecting bitbucket users, and only with the user name and password embedded directly into the URL. If you resolved the issue by adding .ssh/id_rsa to the home directory of your Jenkins user, then you should also be able to use the Jenkins credentials plugin to insert that same private key into Jenkins, then reference that private key from the Git configuration within the specific job using that repository. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28294) "JDK 5 not supported with Maven" error with JDK 6
Title: Message Title Karl Katzke commented on JENKINS-28294 Re: "JDK 5 not supported with Maven" error with JDK 6 I completely agree with you, Daniel, but it's not the error message – it's the automatic upgrading to JDK 7 that is the bug. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-26757) "Error cloning remote repo 'origin'" with username:passw...@bitbucket.org URLs
Title: Message Title Alexander Uvizhev commented on JENKINS-26757 Re: "Error cloning remote repo 'origin'" with username:passw...@bitbucket.org URLs Mark Waite yes, I use GitHub Enterprise. I googled this bug and didn't see any other related to GitHub. Now I cannot reproduce the first case but in second I tried both anonymous repo fetching and specifying credentials (not directly in URL). I already put my private key into Jenkins Credentials and it seems to work since I can execute buildsteps on JClouds slaves, but cannot fetch repo. If there's GitHub related issue please point me to it. Thanks in advance. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28329) Workflow Steps should have way to be exposed on the Jenkins build homepage
Title: Message Title Jesse Glick resolved as Won't Fix This is what stage is for. See this CloudBees Jenkins Enterprise feature for example. Jenkins / JENKINS-28329 Workflow Steps should have way to be exposed on the Jenkins build homepage Change By: Jesse Glick Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28131) Pass NODE_NAME into node{}
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-28131
Pass NODE_NAME into node{}
Change By:
Jesse Glick
It would be useful and natural to be able to use {{ env.NODE_NAME }} inside a node { {node } } .Currently. the following code results in null: {code} node('myNode') { echo "My name is ${env.NODE_NAME}" } {code} Perhaps {{ ExecutorStepExecution }} should define {{ NODE_NAME }} for use by steps inside node { {node } } .
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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-28321) Method pointer operator (.&) broken
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-28321
Method pointer operator (.&) broken
Just one of many exotic Groovy language features not currently supported by the CPS engine.
Change By:
Jesse Glick
The method pointer operator ( {{ .& }} ) is entirely broken. The following test: {code} def bar = 'foo'.&toUpperCase {code} Results in: {code:none} startup failed:General error during canonicalization: java.lang.UnsupportedOperationException {code} Plus a giant call stack.The workaround is to instead explicitly create a closure which calls the method, which is syntactically cumbersome and reduces semantic readability.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [job-dsl-plugin] (JENKINS-28353) Error in documentation
Title: Message Title Kent Källström created an issue Jenkins / JENKINS-28353 Error in documentation Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 12/May/15 2:15 PM Priority: Minor Reporter: Kent Källström Hi, There seems to be a documentation error in the section 'Parameterized Trigger as Build Step' on https://github.com/jenkinsci/job-dsl-plugin/wiki/Job-reference When using this plugin as a build step, the docs says 'The condition arg is one of these possible values: SUCCESS, UNSTABLE, UNSTABLE_OR_BETTER, UNSTABLE_OR_WORSE, FAILED.' The only valid value is 'ALWAYS'. If using any of the above values the downstream job will not get triggered. The above values are valid when configuring the plugin as a post build step. Workaround is to re-save the job in Jenkins and the correct value is inserted. Regards Kent Källström Add Comment
[JIRA] [analysis-core-plugin] (JENKINS-25977) Make publishers of analysis-core a SimpleBuildStep
Title: Message Title Jesse Glick commented on JENKINS-25977 Re: Make publishers of analysis-core a SimpleBuildStep My guess is that it could be done compatibly, albeit with some effort. (Switches based on Util.isOverridden etc.) Workflow will ignore getRequiredMonitorService, but anyway NONE is the recommended value even for freestyle projects. If a build step behaves differently based on the status of previous builds which are still in progress, blocking the new build is rarely what the user wants. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28317) withEnv does not support nesting
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-28317 withEnv does not support nesting Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28317) withEnv does not support nesting
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28317 Re: withEnv does not support nesting Code changed in jenkins User: Jesse Glick Path: CHANGES.md http://jenkins-ci.org/commit/workflow-plugin/9aba34f91cfcc36873497c5aefc239d631869e00 Log: [FIXED JENKINS-28317] Noting that this was recently fixed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-17667) Unable to kill a job which is running
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Not sure why this got reassigned away from me. I committed the fix to the known issue. (If there are other issues with similar symptoms, they should be filed separately and linked.) Jenkins / JENKINS-17667 Unable to kill a job which is running Change By: Jesse Glick Assignee: Aswini Rajasekaran Jesse Glick Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-26010) Workflow plugin not working with with Gerrit event
Title: Message Title Jesse Glick commented on JENKINS-26010 Re: Workflow plugin not working with with Gerrit event Some work. TBD how much. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28354) Add Fixed build trigger
Title: Message Title Shawn McCarthy created an issue Jenkins / JENKINS-28354 Add Fixed build trigger Issue Type: Improvement Assignee: huybrechts Components: parameterized-trigger-plugin Created: 12/May/15 3:21 PM Priority: Minor Reporter: Shawn McCarthy The Fixed build trigger will trigger when the previous build was UNSTABLE or FAILURE and the current build status is SUCCESS. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sh
[JIRA] [parameterized-trigger-plugin] (JENKINS-28354) Add Fixed build trigger
Title: Message Title Shawn McCarthy commented on JENKINS-28354 Re: Add Fixed build trigger Here is the pull request for this improvement : https://github.com/jenkinsci/parameterized-trigger-plugin/pull/84 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28355) Project's Build History frame size is short for icons
Title: Message Title Pavel C created an issue Jenkins / JENKINS-28355 Project's Build History frame size is short for icons Issue Type: Bug Assignee: Pavel C Attachments: build_history.jpg Components: core Created: 12/May/15 3:32 PM Environment: Linux , Jenkins 1.611, Gerrit, Artifactory, Bintray, Groovy plugins IE and Chrome browsers Labels: jenkins build-history Priority: Trivial Reporter: Pavel C Issue started from upgrading Jenkins from 1.596 to 1.611 Project build history table in the left side of Project Dashboard is not wide enough for different plugin icons. Wide Size of the table is not dynamically changed if build icons added by different plugins. My project builds have gerrit
[JIRA] [email-ext-plugin] (JENKINS-28349) Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher
Title: Message Title Alex Earl commented on JENKINS-28349 Re: Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher What do you mean "the 4 default triggers that showed up everytime I added a Trigger"? Can you capture in a video what you are seeing? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [docker-build-step-plugin] (JENKINS-28356) It is not possible to use variables in "Registry Server Addresses" input for "Push Image" step.
Title: Message Title Artem Kozlov created an issue Jenkins / JENKINS-28356 It is not possible to use variables in "Registry Server Addresses" input for "Push Image" step. Issue Type: Bug Assignee: vjuranek Components: docker-build-step-plugin Created: 12/May/15 3:33 PM Environment: plugin version: 1.24 jenkins version: 1.596.2 Priority: Minor Reporter: Artem Kozlov Quite strange because I can use variables in "Name of the image to push (repository/image)" field without any problems. Add Comment
[JIRA] [email-ext-plugin] (JENKINS-28349) Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher
Title: Message Title Heena Chauhan commented on JENKINS-28349 Re: Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher I had missed setting the smtp setting in the Editable Email notification in the master confgiuration. That is the reason the emails were not sent. For the "Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher" error. I deletedthe 4 default triggered that showed up everytime I added a Trigger. That did it all. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28324) ServletException in /hudson/model/View/index.jelly / java.lang.Integer incompatible with hudson.model.Action
Title: Message Title Herr Phon commented on JENKINS-28324 Re: ServletException in /hudson/model/View/index.jelly / java.lang.Integer incompatible with hudson.model.Action After some more testing I found out that some old job builds were broken... so removing all the old builds works as well... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [p4-plugin] (JENKINS-28343) Add quiet option to p4-plugin sync
Title: Message Title Robby Pocase commented on JENKINS-28343 Re: Add quiet option to p4-plugin sync Added in pull request https://github.com/jenkinsci/p4-plugin/pull/12. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [shelve-project-plugin] (JENKINS-10986) Symlinks in a shelved project are archived as directories on Unix platforms
Title: Message Title James Howe commented on JENKINS-10986 Re: Symlinks in a shelved project are archived as directories on Unix platforms From my testing, it appears that any job that's been unshelved will break Jenkins if loaded after 1.597, as the layout migration fails. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28333) Browse users is broken
Title: Message Title
Herr Phon commented on JENKINS-28333
Re: Browse users is broken
Hi Daniel,
you were right! There were some broken builds. I used the script console to find them...
Jenkins.instance.items.each { project ->
println project.class;
println project.name;
println project.builds;
println "";
};
return
Every problem will result in an exception...
I have looked at the build.xml's of these few jobs but couldn't find any obvious problems One thing these jobs had in common was, that they were all quite old... actually one of the first jobs ever run on the instance and I had not activated any job cleanup yet...
Anyway, thank you very much for your support!
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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-3122) auto build of downstream projects doesn't workfor m2 jobs in unstable state, when using surefire flag testFailureIgnore
Title: Message Title Thomas Reinhardt commented on JENKINS-3122 Re: auto build of downstream projects doesn't workfor m2 jobs in unstable state, when using surefire flag testFailureIgnore I really could need this feature and am willing to help out here. Any hints for me where to start looking in the sources? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [shelve-project-plugin] (JENKINS-10986) Symlinks in a shelved project are archived as directories on Unix platforms
Title: Message Title James Howe edited a comment on JENKINS-10986 Re: Symlinks in a shelved project are archived as directories on Unix platforms From my testing, it appears that any job that's been unshelved will break Jenkins if loaded after 1.597, as the layout migration fails. Failed to update hudson.model.FreeStyleProject@61d2876c[Job1] lastSuccessfulBuild permalink for Job1 #7java.nio.file.DirectoryNotEmptyException: /var/lib/jenkins/jobs/Job1/builds/lastSuccessfulBuild at sun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:242) at sun.nio.fs.AbstractFileSystemProvider.delete(AbstractFileSystemProvider.java:103) at java.nio.file.Files.delete(Files.java:1079) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28294) "JDK 5 not supported with Maven" error with JDK 6
Title: Message Title Daniel Beck commented on JENKINS-28294 Re: "JDK 5 not supported with Maven" error with JDK 6 To clarify, this issue is primarily about the feature that says: retrying with slave Java and setting compile/test properties to point to ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28333) Browse users is broken
Title: Message Title Daniel Beck commented on JENKINS-28333 Re: Browse users is broken Would be great if you could provide a list of installed plugins and their versions, and some of the broken build.xml files. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [cli] (JENKINS-28346) Inconsistent CLI failiures
Title: Message Title Daniel Beck commented on JENKINS-28346 Re: Inconsistent CLI failiures Try to add the -noKeyAuth option to the java -jar jenkins-cli.jar invocation. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-26757) "Error cloning remote repo 'origin'" with username:passw...@bitbucket.org URLs
Title: Message Title Mark Waite commented on JENKINS-26757 Re: "Error cloning remote repo 'origin'" with username:passw...@bitbucket.org URLs Alexander Uvizhev the problem you're describing with your environment is very different from the one described in this bug. This bug is specific to bitbucket, and specific to user name and password credentials embedded directly into the URL. If the private key works for fetches to your JClouds slaves, then it seems like it should also work for any other slave, unless your JCloud slave has some environment setup which assures the git authentication will work (without using the private key). I think you'll be better served by opening a new bug report rather than inserting your descriptions into this bug report. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title
Jon Starbird created an issue
Jenkins / JENKINS-28357
Cannot use Jelly Template after recent 2.40 fix
Issue Type:
Bug
Assignee:
Alex Earl
Components:
email-ext-plugin
Created:
12/May/15 4:39 PM
Environment:
Jenkins LTS 1.596.2, Plugin 2.40.1
Priority:
Blocker
Reporter:
Jon Starbird
When using $ {JELLY_SCRIPT,template="mod1.template"}
I get the error that was reported about Groovy scripts for Jenkins-28202, Jelly file [mod1.template] was not found in $JENKINS_HOME/email-templates
Nothing was changed in my environment and the file was used fine before. The file does exist and has the full filename of mod1.template.jelly but now it won't work. Doing a Test email and putting the full filename there it does find it in the correct location it is only when a build fires it off that this is failing.
[JIRA] [email-ext-plugin] (JENKINS-28202) groovy templates do not work after upgrading to 2.40
Title: Message Title Jon Starbird commented on JENKINS-28202 Re: groovy templates do not work after upgrading to 2.40 When Jenkins-28202 was fixed for Groovy it seems to have broken Jelly. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28294) "JDK 5 not supported with Maven" error with JDK 6
Title: Message Title Karl Katzke commented on JENKINS-28294 Re: "JDK 5 not supported with Maven" error with JDK 6 Daniel: The first attempt to build using this JDK: /usr/lib/jvm/java-6-openjdk-amd64//bin/java Results in an error about JDK5. It then results in a build that attempts using this JDK: /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java This means there are two bugs: JDK 5 is not allowed, but JDK 6 should be. When JDK 6 is selected, it should not attempt to build using JDK7, which isn't even configured as an available JDK in Jenkins. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28202) groovy templates do not work after upgrading to 2.40
Title: Message Title Jon Starbird edited a comment on JENKINS-28202 Re: groovy templates do not work after upgrading to 2.40 When Jenkins-28202 was fixed for Groovy it seems to have broken Jelly. See Jenkins-28357 for the Jelly bug. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title Alex Earl commented on JENKINS-28357 Re: Cannot use Jelly Template after recent 2.40 fix Ok, I'll look into this ASAP. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27289) Masking classLoader doesn`t work on remote Slave
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27289 Re: Masking classLoader doesn`t work on remote Slave Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/util/MaskingClassLoader.java test/src/test/java/hudson/ClassicPluginStrategyTest.java test/src/test/resources/hudson/ClassicPluginStrategyTest/testMaskResourceClassLoader.zip http://jenkins-ci.org/commit/jenkins/caedb49c23f2ec24dae9c28f8a604864dc1fbb3e Log: JENKINS-27289 Noting merge of #1598. Compare: https://github.com/jenkinsci/jenkins/compare/0d553783fdfe...caedb49c23f2 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27289) Masking classLoader doesn`t work on remote Slave
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27289 Re: Masking classLoader doesn`t work on remote Slave Code changed in jenkins User: liorha Path: core/src/main/java/hudson/util/MaskingClassLoader.java test/src/test/java/hudson/ClassicPluginStrategyTest.java test/src/test/resources/hudson/ClassicPluginStrategyTest/testMaskResourceClassLoader.zip http://jenkins-ci.org/commit/jenkins/7db618e64a8b70514df227dd706566e93a0e112c Log: JENKINS-27289 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27289) Masking classLoader doesn`t work on remote Slave
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27289 Re: Masking classLoader doesn`t work on remote Slave Code changed in jenkins User: liorha Path: changelog.html cli/pom.xml core/pom.xml plugins/pom.xml pom.xml test/pom.xml war/pom.xml http://jenkins-ci.org/commit/jenkins/6428d15aae54d5716fc34ace386fc87bfcb031a0 Log: Merge branch 'master' into JENKINS-27289 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27289) Masking classLoader doesn`t work on remote Slave
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27289 Re: Masking classLoader doesn`t work on remote Slave Code changed in jenkins User: liorha Path: changelog.html core/src/main/java/hudson/model/Computer.java core/src/main/java/hudson/slaves/SlaveComputer.java test/src/test/java/hudson/model/ComputerTest.java http://jenkins-ci.org/commit/jenkins/a503b66977e3058cdd54f1701c248cc864d9e36c Log: Merge branch 'master' into JENKINS-27289 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27289) Masking classLoader doesn`t work on remote Slave
Title: Message Title Jesse Glick started work on JENKINS-27289 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27289) Masking classLoader doesn`t work on remote Slave
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27289 Re: Masking classLoader doesn`t work on remote Slave Code changed in jenkins User: liorha Path: changelog.html core/src/main/java/hudson/model/Run.java core/src/main/java/hudson/tasks/Maven.java core/src/test/java/hudson/model/RunTest.java war/pom.xml http://jenkins-ci.org/commit/jenkins/e166c9268e3cffbe8eab1d7a7502ac272b325a02 Log: Merge branch 'master' into JENKINS-27289 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27289) Masking classLoader doesn`t work on remote Slave
Title: Message Title Jesse Glick assigned an issue to lior hasson Jenkins / JENKINS-27289 Masking classLoader doesn`t work on remote Slave Change By: Jesse Glick Assignee: lior hasson Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27289) Masking classLoader doesn`t work on remote Slave
Title: Message Title Jesse Glick commented on JENKINS-27289 Re: Masking classLoader doesn`t work on remote Slave Fixed for getResource as called by Which.classFileUrl. Still need a fix for getResources, but that should not block merging to LTS. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28358) Console Window doesn't show
Title: Message Title Herr Phon created an issue Jenkins / JENKINS-28358 Console Window doesn't show Issue Type: Bug Assignee: Unassigned Components: build-pipeline-plugin Created: 12/May/15 5:04 PM Environment: Jenkins ver. 1.596.2 Build Pipeline Plugin ver. 1.4.7 Browser: latest Chrome Priority: Minor Reporter: Herr Phon Hi, when clicking on the console icon in a build pipeline no popup appears but instead in the JS console I get the following error message: Uncaught TypeError: jQuery.fancybox is not a function BuildPipeline.fillDialog @ build-pipeline.js:101 onclick @ (index):116 I can see the fancybox css and js in the header and I can even load these two files - so the webserver does serve these files. But they seem to be broken. Then loading the css and js from another source, it works again. As a work-around I just put in some js that loads these two files in the description of the build pipeline..
[JIRA] [build-pipeline-plugin] (JENKINS-28358) Console Window doesn't show
Title: Message Title
Herr Phon updated an issue
Jenkins / JENKINS-28358
Console Window doesn't show
Change By:
Herr Phon
Hi,when When clicking on the console icon in a build pipeline no popup appears but instead in the JS console I get the following error message:{code}Uncaught TypeError: jQuery.fancybox is not a functionBuildPipeline.fillDialog @ build-pipeline.js:101onclick @ (index):116{code}I can see the fancybox css and js in the header and I can even load these two files - so the webserver does serve these files. But they seem to be broken. When loading the css and js from another source, it works again. As a work-around I just put in some js that loads these two files in the description of the build pipeline..
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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-28358) Console Window doesn't show
Title: Message Title
Herr Phon updated an issue
Jenkins / JENKINS-28358
Console Window doesn't show
Change By:
Herr Phon
Hi,when clicking on the console icon in a build pipeline no popup appears but instead in the JS console I get the following error message:{code}Uncaught TypeError: jQuery.fancybox is not a functionBuildPipeline.fillDialog @ build-pipeline.js:101onclick @ (index):116{code}I can see the fancybox css and js in the header and I can even load these two files - so the webserver does serve these files. But they seem to be broken. Then When loading the css and js from another source, it works again. As a work-around I just put in some js that loads these two files in the description of the build pipeline..
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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-28294) "JDK 5 not supported with Maven" error with JDK 6
Title: Message Title Daniel Beck commented on JENKINS-28294 Re: "JDK 5 not supported with Maven" error with JDK 6 JDK 5 is not allowed, but JDK 6 should be. As I wrote, Maven jobs are tightly integrated with Jenkins, and since Jenkins raised the Java runtime requirement to 7, it's possible this was changed as well (and it's just the message that wasn't adjusted to reflect this) which isn't even configured as an available JDK in Jenkins The message (and code) indicates this is actually a deliberate feature. Not sure what to do about this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title
Alex Earl commented on JENKINS-28357
Re: Cannot use Jelly Template after recent 2.40 fix
I'm actually not able to reproduce this. I put my template into email-templates and set the content to $ {JELLY_SCRIPT, template="module1.template"}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title
Alex Earl edited a comment on JENKINS-28357
Re: Cannot use Jelly Template after recent 2.40 fix
I'm actually not able to reproduce this. I put my template into email-templates and set the content to {code} ${JELLY_SCRIPT, template="module1.template"} {code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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.
