[JIRA] [blamesubversion-plugin] (JENKINS-26318) Subversion Plug in 2.5 causes sporadic problems
Title: Message Title Daniel Beck commented on JENKINS-26318 Re: Subversion Plug in 2.5 causes sporadic problems Why do you think this issue has anything to do with the BlameSubversion plugin? If GitHub is right, the BlameSubversion project has no changes for 3 years. BlameSubversion also does not seem to do any custom class loading. Because it's a terrible idea to copy a class from another plugin, as that sets you up for trouble like this. Since Subversion plugin's existed first, BlameSubversion is the copy, and hence (no pun intended) to blame. 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-31090) Not compiling against Jenkins 1.580+
Title: Message Title Manuel Jesús Recena Soto edited a comment on JENKINS-31090 Re: Not compiling against Jenkins 1.580+ A [PR|https://github.com/jenkinsci/subversion-plugin/pull/ 138 140 ] has been added. 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-31098) New delete-node CLI command breaks node cleanup in cloud plugins
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31098 Re: New delete-node CLI command breaks node cleanup in cloud plugins Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/cli/DeleteNodeCommand.java test/src/test/java/hudson/cli/DeleteNodeCommandTest.java http://jenkins-ci.org/commit/jenkins/0a56c1d5078bc6f36a305ee25538eeff1a0e2442 Log: Merge pull request #1882 from pjanouse/JENKINS-31098 JENKINS-31098 Deletage remove a node back to Computer.doDoDelete() Compare: https://github.com/jenkinsci/jenkins/compare/be8c57460ce2...0a56c1d5078b 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-31098) New delete-node CLI command breaks node cleanup in cloud plugins
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31098 Re: New delete-node CLI command breaks node cleanup in cloud plugins Code changed in jenkins User: Ing. Pavel Janousek Path: core/src/main/java/hudson/cli/DeleteNodeCommand.java test/src/test/java/hudson/cli/DeleteNodeCommandTest.java http://jenkins-ci.org/commit/jenkins/04a874ac9572245314208fdeea485383d621fcf6 Log: JENKINS-31098 Deletage remove a node back to Computer.doDoDelete() 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-15792) jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title SCM/JIRA link daemon commented on JENKINS-15792 Re: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path Code changed in jenkins User: Oleg Nenashev Path: core/pom.xml http://jenkins-ci.org/commit/jenkins/fef832fb9ff53b4ffd075870e4a6cb6fef4333d7 Log: Merge pull request #1861 from rodrigc/JENKINS-15792 JENKINS-15792 Update jna to 4.2.0 Compare: https://github.com/jenkinsci/jenkins/compare/730d6ecb2d29...fef832fb9ff5 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-15792) jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title SCM/JIRA link daemon commented on JENKINS-15792 Re: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path Code changed in jenkins User: Craig Rodrigues Path: core/pom.xml http://jenkins-ci.org/commit/jenkins/4fa14ab6ff56e9c7f6ca47280eb8e8ca8873150b Log: JENKINS-15792 Update jna to 4.2.0 This pulls in libjnidispatch.so for linux-ppc64 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-25742) Concurrent "job rename" and "edit view" results in deadlock that puts Jenkins in a non responsive state
Title: Message Title Oleg Nenashev started work on JENKINS-25742 Change By: Oleg Nenashev 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.
RE: GOOD NEWS
From: Sophie Liu Sent: 24 October 2015 14:03 To: Sophie Liu Subject: GOOD NEWS Recipîent of a donatîon contact [sessilmalcol...@outlook.com] for details -- 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-31108) Git-Publisher should allow to push tags from a shallow clone
Title: Message Title Jarek Lipski commented on JENKINS-31108 Re: Git-Publisher should allow to push tags from a shallow clone Thank you for a detailed answer. I think I have enough information to start working on a first version of a pull request. 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-15792) jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title dogfood commented on JENKINS-15792 Re: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path Integrated in jenkins_main_trunk #4340 JENKINS-15792 Update jna to 4.2.0 (Revision 4fa14ab6ff56e9c7f6ca47280eb8e8ca8873150b) Result = SUCCESS rodrigc : 4fa14ab6ff56e9c7f6ca47280eb8e8ca8873150b Files : core/pom.xml 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-31098) New delete-node CLI command breaks node cleanup in cloud plugins
Title: Message Title dogfood commented on JENKINS-31098 Re: New delete-node CLI command breaks node cleanup in cloud plugins Integrated in jenkins_main_trunk #4340 JENKINS-31098 Deletage remove a node back to Computer.doDoDelete() (Revision 04a874ac9572245314208fdeea485383d621fcf6) Result = SUCCESS pjanouse : 04a874ac9572245314208fdeea485383d621fcf6 Files : core/src/main/java/hudson/cli/DeleteNodeCommand.java test/src/test/java/hudson/cli/DeleteNodeCommandTest.java 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-755) Default JDK meaning in project options is confusing.
Title: Message Title dogfood commented on JENKINS-755 Re: Default JDK meaning in project options is confusing. Integrated in jenkins_main_trunk #4340 JENKINS-755 Describe the built-in JDK as '(System)'. (Revision ff021d3c374a067d622fdb078a4e391149df7d41) Result = SUCCESS whughes : ff021d3c374a067d622fdb078a4e391149df7d41 Files : core/src/main/java/hudson/model/JDK.java 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-31089) Signature verification failed in update site 'default'
Title: Message Title Mike Caspar commented on JENKINS-31089 Re: Signature verification failed in update site 'default' Hi there, I saw no change so I thought.. OK.. maybe it's caching of some sort. Let's restart my server. Much better progress. The initial signature error is gone and doesn't show any exceptions in the logs. That first message has gone away to now be replaced by a new one (1.634,java 1.8.0_66-b17, ubuntu 14.04). Strangely, there is no error in the jenkins.log. I get the following in the jenkins.log Oct 24, 2015 9:32:43 AM hudson.model.UpdateSite updateData INFO: Obtained the latest update center data file for UpdateSource default followed by the following in the web interface... at /pluginManager/checkUpdatesServer Signature verification failed in downloadable 'hudson.tasks.Maven.MavenInstaller' (show details) Would you like me to open a ticket somewhere or just consider this message to be sufficient ? (which module if so). Not sure.. same (related) problem or different one? Thanks 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-31089) Signature verification failed in update site 'default'
Title: Message Title Mike Caspar edited a comment on JENKINS-31089 Re: Signature verification failed in update site 'default' Hi there,I saw no change so I thought.. OK.. maybe it's caching of some sort. Let's restart my server. Much better progress. The initial signature error is gone and doesn't show any exceptions in the logs for the original problem . . However, That first message has gone away to now be replaced by a new one (1.634,java 1.8.0_66-b17, ubuntu 14.04).Strangely, there is no *error* in the jenkins.log. I get the following in the jenkins.logOct 24, 2015 9:32:43 AM hudson.model.UpdateSite updateDataINFO: Obtained the latest update center data file for UpdateSource defaultfollowed by the following in the web interface...at /pluginManager/checkUpdatesServer*Signature verification failed in downloadable 'hudson.tasks.Maven.MavenInstaller' (show details)*Would you like me to open a ticket somewhere or just consider this message to be sufficient ? (which module if so). Not sure.. same (related) problem or different one?Thanks 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-name-setter-plugin] (JENKINS-31149) Latest version of token-macro-plugin doesn't work with build-name-setter PROPFILE
Title: Message Title
Erik Lattimore created an issue
Jenkins / JENKINS-31149
Latest version of token-macro-plugin doesn't work with build-name-setter PROPFILE
Issue Type:
Bug
Assignee:
Kohsuke Kawaguchi
Components:
build-name-setter-plugin, token-macro-plugin
Created:
24/Oct/15 2:17 PM
Priority:
Minor
Reporter:
Erik Lattimore
In some of our jobs, we use the build-name-setter plugin along with property files to set the name of the job based on values generated from the build. After upgrading to the latest version of the token-macro plugin, we are getting exceptions in the build. In our jobs, we have build-name-setter configured as follows:
"build-name-setter@1.3">
${PROPFILE,file="debian.properties",property="version"}
However, now when the build runs, we get the following exception:
00:00:39.540 FATAL: Remote call on USLOLBLDV80 failed
00:00:39.541 java.io.IOException: Remote call on USLOLBLDV80 failed
00:00:39.541 at hudson.remoting.Channel.call(Channel.java:786)
00:00:39.541 at hudson.FilePath.act(FilePath.java:1073)
00:00:39.541 at org.jenkinsci.plugins.tokenmacro.impl.PropertyFromFileMacro.evaluate(PropertyFromFileMacro.java:42)
00:00:39.541 at org.jenkinsci.plugins.tokenmacro.DataBoundTokenMacro.evaluate(DataBoundTokenMacro.java:190)
00:00:39.541 at org.j
[JIRA] [core] (JENKINS-31089) Signature verification failed in update site 'default'
Title: Message Title Daniel Beck reopened an issue Different but related issue, as the tool installer metadata is generated by a different process. Reusing this issue for this problem. Looks like Kohsuke Kawaguchi needs to provide new secrets to the infra_backend_crawler project. Jenkins / JENKINS-31089 Signature verification failed in update site 'default' Change By: Daniel Beck Resolution: Fixed 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-30745) First poll does not run on copied jobs which aren't yet saved or applied
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30745 Re: First poll does not run on copied jobs which aren't yet saved or applied Code changed in jenkins User: Oleg Nenashev Path: changelog.html http://jenkins-ci.org/commit/jenkins/f53b529fa0f7abb3e936b3c19214ee20116b811c Log: Noting the revert of https://github.com/jenkinsci/jenkins/pull/1617 in #1870 ( JENKINS-30745 ) 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-31098) New delete-node CLI command breaks node cleanup in cloud plugins
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31098 Re: New delete-node CLI command breaks node cleanup in cloud plugins Code changed in jenkins User: Oleg Nenashev Path: changelog.html http://jenkins-ci.org/commit/jenkins/e3b3638f76107c020fa43d545890329d92e2bcdf Log: Noting fix of JENKINS-31098 in #1882 Compare: https://github.com/jenkinsci/jenkins/compare/fef832fb9ff5...e3b3638f7610 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-755) Default JDK meaning in project options is confusing.
Title: Message Title Oleg Nenashev commented on JENKINS-755 Re: Default JDK meaning in project options is confusing. Fixed in https://github.com/jenkinsci/jenkins/pull/1528 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] [htmlpublisher-plugin] (JENKINS-7139) HtmlPublisher should be able to handle wildcard paths to find multiple html files
Title: Message Title mcrooney reopened an issue Apologies, indeed, there were regressions in normal report archiving that required a revert. If anyone wants to look at improving https://github.com/jenkinsci/htmlpublisher-plugin/pull/17, it shouldn't be too hard. Jenkins / JENKINS-7139 HtmlPublisher should be able to handle wildcard paths to find multiple html files Change By: mcrooney Resolution: Fixed 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] [rundeck-plugin] (JENKINS-31150) Support Multiple SCM tags for rundeck notifier
Title: Message Title Yuri Goikhman created an issue Jenkins / JENKINS-31150 Support Multiple SCM tags for rundeck notifier Issue Type: Improvement Assignee: Yuri Goikhman Components: rundeck-plugin Created: 24/Oct/15 5:43 PM Priority: Minor Reporter: Yuri Goikhman Currently you can provide a single scm tag in the "SCM Tag" post build rundeck notifier option. Sometimes you want to trigger the same rundeck job on different scm tags (e.g both #staging and #production tags will trigger the same rundeck job on the staging environment) Add Comment
[JIRA] [subversion-plugin] (JENKINS-27265) SvnPlugin ignores system credentials (svn: E175002: SSL handshake failed: 'Received fatal alert: handshake_failure' )
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-27265 Re: SvnPlugin ignores system credentials (svn: E175002: SSL handshake failed: 'Received fatal alert: handshake_failure' ) Sven Appenrodt, If you agree, I'd like to close this ticket. 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-27265) SvnPlugin ignores system credentials (svn: E175002: SSL handshake failed: 'Received fatal alert: handshake_failure' )
Title: Message Title Manuel Jesús Recena Soto resolved as Not A Defect Jenkins / JENKINS-27265 SvnPlugin ignores system credentials (svn: E175002: SSL handshake failed: 'Received fatal alert: handshake_failure' ) Change By: Manuel Jesús Recena Soto Status: Open Resolved Resolution: Not A Defect 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-28749) Incorrect local modification being identified when svn:keywords are used on 1.8
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-28749 Re: Incorrect local modification being identified when svn:keywords are used on 1.8 dan russell, Could you provide any feedback? 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-28749) Incorrect local modification being identified when svn:keywords are used on 1.8
Title: Message Title Manuel Jesús Recena Soto updated an issue Jenkins / JENKINS-28749 Incorrect local modification being identified when svn:keywords are used on 1.8 Change By: Manuel Jesús Recena Soto Priority: Critical 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] [sonar-gerrit-plugin] (JENKINS-31004) Check if usage of gerrit-trigger RestApi is allowed
Title: Message Title Tatiana Didik resolved as Fixed Jenkins / JENKINS-31004 Check if usage of gerrit-trigger RestApi is allowed Change By: Tatiana Didik 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] [sonar-gerrit-plugin] (JENKINS-31013) Add parameter to do not notify developer when posting comments
Title: Message Title Tatiana Didik resolved as Fixed 1.0.4 Jenkins / JENKINS-31013 Add parameter to do not notify developer when posting comments Change By: Tatiana Didik 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] [sonar-gerrit-plugin] (JENKINS-31005) Move "project base directory" setting to "Advanced" section
Title: Message Title Tatiana Didik resolved as Fixed 1.0.4 Jenkins / JENKINS-31005 Move "project base directory" setting to "Advanced" section Change By: Tatiana Didik 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] [core] (JENKINS-30655) Remoting blocks when the slave disconnects during copying files
Title: Message Title ikedam commented on JENKINS-30655 Re: Remoting blocks when the slave disconnects during copying files I found that the hang doesn't reproduce with Jenkins-1.559 + remoting-2.39 (I built that by modifying the source code) and this should be caused for changes in core rather than changes in remoting. The hang in my environment looks caused for d4c74bf. Reverting this change makes the hang unreproducible. > JY Hsu Let us know followings: How do you launch your slaves? The suspected change affects only JNLP slaves. It might not concern this problem if you use SSH slaves. How do you cancel jobs? You look use build-timeout plugin. Aborting by build-timeout and aborting by clicking "x" button work in different ways. 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://g
[JIRA] [token-macro-plugin] (JENKINS-27542) Pass parent job name to triggered jobs
Title: Message Title Alex Earl started work on JENKINS-27542 Change By: Alex Earl 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] [ec2-plugin] (JENKINS-23787) EC2-plugin not spooling up stopped nodes - "still in the queue ... all nodes of label ... are offline"
Title: Message Title Francis Upton commented on JENKINS-23787 Re: EC2-plugin not spooling up stopped nodes - "still in the queue ... all nodes of label ... are offline" I believe I have now fixed 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] [ec2-plugin] (JENKINS-23787) EC2-plugin not spooling up stopped nodes - "still in the queue ... all nodes of label ... are offline"
Title: Message Title Francis Upton resolved as Fixed Should be released in 1.30 Jenkins / JENKINS-23787 EC2-plugin not spooling up stopped nodes - "still in the queue ... all nodes of label ... are offline" Change By: Francis Upton 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] [ec2-plugin] (JENKINS-27601) instance caps incorrectly calculated
Title: Message Title Francis Upton commented on JENKINS-27601 Re: instance caps incorrectly calculated Can you try out the snapshot and see if it works for you (there were other problems with it that prevented me from doing a release)? 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] [ec2-plugin] (JENKINS-26493) Use new EC2 API endpoint hostnames
Title: Message Title Francis Upton commented on JENKINS-26493 Re: Use new EC2 API endpoint hostnames Can you verify this is working in the current (1.30) snapshot, and then I can release it? 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] [ec2-plugin] (JENKINS-26493) Use new EC2 API endpoint hostnames
Title: Message Title Francis Upton resolved as Fixed To be released in 1.30 Jenkins / JENKINS-26493 Use new EC2 API endpoint hostnames Change By: Francis Upton Status: Reopened 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] [ec2-plugin] (JENKINS-30527) After Jenkins restart existing on-demand EC2 slaves can't be used
Title: Message Title Francis Upton resolved as Duplicate I think this is a dup of JENKINS-23787 Jenkins / JENKINS-30527 After Jenkins restart existing on-demand EC2 slaves can't be used Change By: Francis Upton Status: Open Resolved Resolution: Duplicate 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.
