[JIRA] [rundeck-plugin] (JENKINS-27983) Rundeck does not use Jenkins proxy settings
Anders Hammar commented on JENKINS-27983 Rundeck does not use Jenkins proxy settings I've run into the same problem and the root cause is in the underlaying rundeck API java client library. What I did locally was to patch that library and did a custom build of the plugin. The proxy stuff is changing in the upcoming version for v13 of the Rundeck API. It will then pick up the http.proxyHost et al system properties. If we want the plugin to use the Jenkins proxy config hte plugin needs to be updated to handle that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rundeck-plugin] (JENKINS-22479) Rundeck plugin apiVersion change does not persist
Anders Hammar commented on JENKINS-22479 Rundeck plugin apiVersion change does not persist I believe the problem is even worse, the apiVersion doesn't seem to be used at all. At least not for the test connection. Still a problem in v3.4. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
mwebber commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive I am running Java 8 on both master and slave (both Linux), and get the problem. From the comments on https://github.com/jenkinsci/jenkins/pull/1667, it looks the maintainers can now reproduce the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [support-core-plugin] (JENKINS-28056) Cleanup old thread dump data
Steven Christou created JENKINS-28056 Cleanup old thread dump data Issue Type: Improvement Assignee: Steven Christou Components: support-core-plugin Created: 23/Apr/15 8:45 AM Description: Any deadlock that is more than 7 days after the process has started, then we can safely delete, but make sure that one of the support bundles has the deadlocks before deleting. Another option would be to add a folder called `startup` which contains startup logs, and after 7 days we log rotate the oldest files. This includes deadlocks, and slow-requests. Project: Jenkins Priority: Minor Reporter: Steven Christou This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-28057) CMake, CPack, CTest parser
Dave Taddei created JENKINS-28057 CMake, CPack, CTest parser Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-plugin Created: 23/Apr/15 9:16 AM Description: It would be incredibly useful to have parsing for CMake, CPack and CTest errors. Currently I do not believe the GNU Make or compiler parsing is detecting errors for CMake, CPack or CTest. Currently much of our technology is based on CMake build systems but we have to use a generic error/warning parser to detect problems. Environment: Ubuntu and Windows OS Project: Jenkins Labels: build plugin cmake cpack ctest Priority: Major Reporter: Dave Taddei This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28058) Excessive classes being sent to slave machine
Steven Christou created JENKINS-28058 Excessive classes being sent to slave machine Issue Type: Improvement Assignee: Unassigned Components: core Created: 23/Apr/15 9:16 AM Description: The `Computer.getHostName` method sends the `Computer.class` which will send `Jenkins.class` for only logging. This can lead to slow Jenkins startups. Project: Jenkins Priority: Minor Reporter: Steven Christou This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rundeck-plugin] (JENKINS-28059) API Version is not used in test connection
Anders Hammar created JENKINS-28059 API Version is not used in test connection Issue Type: Bug Assignee: Vincent Behar Components: rundeck-plugin Created: 23/Apr/15 9:18 AM Description: When performing a test connection (in teh global config) the specified API version is not honored. Environment: rundeck-plugin v3.4 Project: Jenkins Priority: Minor Reporter: Anders Hammar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28058) Excessive classes being sent to slave machine
SCM/JIRA link daemon resolved JENKINS-28058 as Fixed Excessive classes being sent to slave machine Change By: SCM/JIRA link daemon (23/Apr/15 9:18 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28058) Excessive classes being sent to slave machine
SCM/JIRA link daemon commented on JENKINS-28058 Excessive classes being sent to slave machine Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/model/Computer.java http://jenkins-ci.org/commit/jenkins/df831325b6623c479dcf4b215415f4523d10530b Log: [FIXED JENKINS-28058] Don't send a reference to Computer.class over remoting channels Logging added to help diagnose was actually causing Jenkins.class to be initialized on the remoting side This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rundeck-plugin] (JENKINS-22479) Rundeck plugin apiVersion change does not persist
Anders Hammar commented on JENKINS-22479 Rundeck plugin apiVersion change does not persist Digging into this I realize that the API version not being used in the test connection is a separate issue. Will open a separate ticket for that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rundeck-plugin] (JENKINS-28059) API Version is not used in test connection
Anders Hammar assigned JENKINS-28059 to Anders Hammar API Version is not used in test connection Change By: Anders Hammar (23/Apr/15 9:19 AM) Assignee: Vincent Behar Anders Hammar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rundeck-plugin] (JENKINS-22479) Rundeck plugin apiVersion change does not persist
Anders Hammar edited a comment on JENKINS-22479 Rundeck plugin apiVersion change does not persist Digging into this I realize that the API version not being used in the test connection is a separate issue. Will open a separate ticket for that (JENKINS-28059). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-28060) Getting Error while Trying to save anything from any of the Jenkins jobs Configuration
Christopher Orr moved JENKINS-28060 Getting Error while Trying to save anything from any of the Jenkins jobs Configuration Change By: Christopher Orr (23/Apr/15 9:31 AM) Project: Infrastructure Jenkins Key: INFRA JENKINS - 280 28060 Workflow: jira JNJira Component/s: maven-plugin Component/s: etc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-28060) Getting Error while Trying to save anything from any of the Jenkins jobs Configuration
Christopher Orr assigned JENKINS-28060 to Unassigned Getting Error while Trying to save anything from any of the Jenkins jobs Configuration Moving this issue, as it was incorrectly filed against the INFRA project instead of JENKINS. Change By: Christopher Orr (23/Apr/15 9:33 AM) Assignee: R. Tyler Croy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [heavy-job-plugin] (JENKINS-28061) Heavy-job-plugin to consistently use first executor on a node
Ed Randall created JENKINS-28061 Heavy-job-plugin to consistently use first executor on a node Issue Type: Improvement Assignee: Unassigned Components: heavy-job-plugin Created: 23/Apr/15 9:46 AM Description: heavy-job-plugin randomly picks an executor on the slave node to actually run the job and marks the other "n-1" executors as unavailable. We use a maven repository-per-executor and this behaviour means that all the repositories eventually get very large. If the executor picked was consistently the lowest-numbered one (ie. #1 on a slave where all are allocated to the heavy job) this would help. Perhaps this could be configured via a checkbox "Use first available executor on the slave". Environment: heavy-job-plugin 1.1 jenkins 1.596.2 Project: Jenkins Labels: heavy-job Priority: Minor Reporter: Ed Randall This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26580) For JNLP slaves the master-slave communication should be encrypted
akshay_abd commented on JENKINS-26580 For JNLP slaves the master-slave communication should be encrypted I've created a pull request on the remoting repo that adds JNLP3: https://github.com/jenkinsci/remoting/pull/41 I'm still writing tests for the changes to jenkins-core, I'll create a pull request for that soon too. It would be nice to get a few security folks to review these changes. Also in a follow-up CL I'll be enabling JNLP3, probably through a flag, getting folks to try it and help with end-to-end testing would be appreciated. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xshell-plugin] (JENKINS-28038) xshell should make itself available in "conditional build step" and "post-build actions" lists
Ed Randall commented on JENKINS-28038 xshell should make itself available in "conditional build step" and "post-build actions" lists From the "Conditional BuildStep plugin" wiki page: Missing builder If you're not able to add the builder of your choice within a conditional build step (because it's not available within the dropdown), then this is ikely because the builder does not provide a @DataBoundConstructor constructor and/or the Descriptor does not extend hudson.tasks.BuildStepDescriptor. For non programmers: the plugin you would like to use does not yet follow the newest Jenkins coding guidelines. Without this, the conditional buildstep plugin is not able to work with it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xshell-plugin] (JENKINS-28038) xshell should make itself available in "conditional build step" and "post-build actions" lists
Ed Randall edited a comment on JENKINS-28038 xshell should make itself available in "conditional build step" and "post-build actions" lists From the Conditional BuildStep plugin wiki page: Missing builder If you're not able to add the builder of your choice within a conditional build step (because it's not available within the dropdown), then this is likely because the builder does not provide a @DataBoundConstructor constructor and/or the Descriptor does not extend hudson.tasks.BuildStepDescriptor. For non programmers: the plugin you would like to use does not yet follow the newest Jenkins coding guidelines. Without this, the conditional buildstep plugin is not able to work with it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-28062) Channel listener onClose propogated exceptions
Steven Christou created JENKINS-28062 Channel listener onClose propogated exceptions Issue Type: Bug Assignee: Unassigned Components: remoting Created: 23/Apr/15 9:59 AM Description: Channel.onClose Project: Jenkins Priority: Minor Reporter: Steven Christou This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-28062) Channel listener onClose propogated exceptions
SCM/JIRA link daemon resolved JENKINS-28062 as Fixed Channel listener onClose propogated exceptions Change By: SCM/JIRA link daemon (23/Apr/15 10:00 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-28062) Channel listener onClose propogated exceptions
SCM/JIRA link daemon commented on JENKINS-28062 Channel listener onClose propogated exceptions Code changed in jenkins User: Stephen Connolly Path: src/main/java/hudson/remoting/Channel.java http://jenkins-ci.org/commit/remoting/b60df6b39caa403f29845b86338579d1cf76b819 Log: [FIXED JENKINS-28062] A Channel.Listener's onClose method that propagates an exception is a sign of a bad listener not a problem closing the channel. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-28062) Channel listener onClose propagated exceptions
Steven Christou updated JENKINS-28062 Channel listener onClose propagated exceptions Change By: Steven Christou (23/Apr/15 10:01 AM) Summary: Channel listener onClose propogated propagated exceptions Description: Channel . listeners onClose method would propagate exceptions causing extra noise when failing to close the channel. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-25666) Wrong view for build pipeline plugin
Kanstantsin Shautsou resolved JENKINS-25666 as Fixed Wrong view for build pipeline plugin Change By: Kanstantsin Shautsou (23/Apr/15 10:11 AM) Status: Reopened Resolved Assignee: Kanstantsin Shautsou Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-25666) Wrong view for build pipeline plugin
Kanstantsin Shautsou commented on JENKINS-25666 Wrong view for build pipeline plugin What do you mean under again? Jan Vansteenkiste i don't see https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue#Howtoreportanissue-WhatinformationtoprovideforEnvironmentandDescription , so please open new issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-25666) Wrong view for build pipeline plugin
Jan Vansteenkiste commented on JENKINS-25666 Wrong view for build pipeline plugin beneath, see the attached screenshot. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-25666) Wrong view for build pipeline plugin
Jan Vansteenkiste edited a comment on JENKINS-25666 Wrong view for build pipeline plugin beneath, see the attached screenshot: This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-28060) Getting Error while Trying to save anything from any of the Jenkins jobs Configuration
Daniel Beck resolved JENKINS-28060 as Not A Defect Getting Error while Trying to save anything from any of the Jenkins jobs Configuration Same stupid request as JENKINS-28050. Please don't spam. Change By: Daniel Beck (23/Apr/15 10:26 AM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudbees-folder-plugin] (JENKINS-28043) Reload configs of all jobs in folder
Daniel Beck updated JENKINS-28043 Reload configs of all jobs in folder Loading of folder items is done by the Folders plugin. This report needs much more information to allow investigating further. Change By: Daniel Beck (23/Apr/15 10:27 AM) Component/s: cloudbees-folder-plugin Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-25666) Wrong view for build pipeline plugin
Kanstantsin Shautsou commented on JENKINS-25666 Wrong view for build pipeline plugin Does it work with 1.596.1? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [heavy-job-plugin] (JENKINS-28061) Heavy-job-plugin to consistently use first executor on a node
Daniel Beck commented on JENKINS-28061 Heavy-job-plugin to consistently use first executor on a node There is no way for a plugin to do this, and no expectation for plugins to influence work assignment this way. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28063) Triggering the same job twice results in zombie workflow run
Michal Piekarczyk
created JENKINS-28063
Triggering the same job twice results in zombie workflow run
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
23/Apr/15 10:37 AM
Description:
When two workflow jobs try to trigger the same job at the same time, java.hudson.model.Queue#scheduleInternal may detect a duplicate.
When that happens, a second instance of WaitingItem does not get created, meaning one of the workflow runs will have no listeners related to the triggered job.
When the triggered job ends, only one workflow run will be notified and continue, the other one will stay listening forever.
The workaround I've had to apply to deal with this is running the following in scriptler:
Jenkins.instance.getItemByFullName(jobName)
.builds.findAll{it.building}
.each{it.execution.currentExecutions.get()
.each{it.context.onFailure(new Exception())}
}
Environment:
Jenkins ver. 1.610
workflow-plugin 1.5
Project:
Jenkins
Priority:
Critical
Reporter:
Michal Piekarczyk
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-25666) Wrong view for build pipeline plugin
Jan Vansteenkiste commented on JENKINS-25666 Wrong view for build pipeline plugin Looks like the jenkins version is not the issue. my bad To reproduce: Create a dashboard view, add the 'Build pipeline view' as a portlet. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-25666) Wrong view for build pipeline plugin
Kanstantsin Shautsou commented on JENKINS-25666 Wrong view for build pipeline plugin Fill new issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xfpanel-plugin] (JENKINS-28064) 'Replace nr. of failed test cases' option doesn't work
Tomasz Bech created JENKINS-28064 'Replace nr. of failed test cases' option doesn't work Issue Type: Bug Assignee: Julien RENAUT Components: xfpanel-plugin Created: 23/Apr/15 10:53 AM Description: When 'Claim' plugin is used, and some of the tests are claimed, in extreme panel job total number of failed test always shows number of unclaimed tests - option 'Replace nr. of failed test cases' is not taken into account. Project: Jenkins Priority: Major Reporter: Tomasz Bech This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [unity3d-plugin] (JENKINS-23958) Pipe Broken
lacostej commented on JENKINS-23958 Pipe Broken As anyone tried to add some standard Jenkins debugging for the remoting element ? For example, following https://wiki.jenkins-ci.org/display/JENKINS/Logging 1. Go to Jenkins / Manage / Logging 2. add a new log recorder, e.g. named "Remoting" 3. add a logger, with name hudson.remoting, level FINEST 4. optional add logging of anything unity3d related. 5. save it Check that it works (you should start seeing logs appear as soon as some slaves are involved). When the bug triggers, look at the logs and add them here or send them privately to me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [unity3d-plugin] (JENKINS-23958) Pipe Broken
lacostej edited a comment on JENKINS-23958 Pipe Broken As anyone tried to add some standard Jenkins debugging for the remoting element ? For example, following https://wiki.jenkins-ci.org/display/JENKINS/Logging 1. Go to Jenkins / Manage Jenkins / System Log 2. add a new log recorder, e.g. named "Remoting" 3. add a logger, with name hudson.remoting, level FINEST 4. optional add another Logger for anything unity3d related (org.jenkinsci.plugins.unity3d / FINEST) 5. save it Check that it works (you should start seeing logs appear as soon as some slaves are involved). When the bug triggers, look at the logs and add them here or send them privately to me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-28011) Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job
SCM/JIRA link daemon resolved JENKINS-28011 as Fixed Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job Change By: SCM/JIRA link daemon (23/Apr/15 11:19 AM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-28011) Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job
SCM/JIRA link daemon
commented on JENKINS-28011
Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job
Code changed in jenkins
User: Jesse Glick
Path:
core/src/main/resources/lib/form/class-entry.jelly
http://jenkins-ci.org/commit/jenkins/343382b9ff8a978f6914cc64714a5c16bd9b511a
Log:
[FIXED JENKINS-28011] Amending #1563, ${descriptor} is not necessarily ${attrs.descriptor}!
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-28011) Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job
SCM/JIRA link daemon commented on JENKINS-28011 Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/resources/lib/form/class-entry.jelly http://jenkins-ci.org/commit/jenkins/8c94920973c4e28432d89d4427cfb350e92d7d4d Log: JENKINS-28011 Noting merge of #1663. Compare: https://github.com/jenkinsci/jenkins/compare/fd42e33d6195...8c94920973c4 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-28011) Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job
Jesse Glick commented on JENKINS-28011 Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job Will be fixed in 1.611. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-28011) Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job
Martin Reinhardt commented on JENKINS-28011 Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job same issues here This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [config-rotator-plugin] (JENKINS-28065) Subscribe module: Extension to enable/disable information
Mads Nielsen created JENKINS-28065 Subscribe module: Extension to enable/disable information Issue Type: Bug Assignee: Praqma Support Components: config-rotator-plugin Created: 23/Apr/15 11:24 AM Project: Jenkins Priority: Minor Reporter: Mads Nielsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xfpanel-plugin] (JENKINS-28064) 'Replace nr. of failed test cases' option doesn't work
Tomasz Bech commented on JENKINS-28064 'Replace nr. of failed test cases' option doesn't work pull request created https://github.com/jenkinsci/xfpanel-plugin/pull/14 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sitemonitor-plugin] (JENKINS-28066) Checkbox with the text 'Monitor Site' not appearing
Tojan John created JENKINS-28066 Checkbox with the text 'Monitor Site' not appearing Issue Type: Bug Assignee: cliffano Components: sitemonitor-plugin Created: 23/Apr/15 12:16 PM Description: I am using Jenkins 1.610 and installed on WIndows 7. I installed sitemonitor plugin, but the checkbox to add the URL is not appearing. Environment: Windows 7 Project: Jenkins Priority: Major Reporter: Tojan John This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27571) Workflow Job: "Back to Project" link not navigating
SCM/JIRA link daemon commented on JENKINS-27571 Workflow Job: "Back to Project" link not navigating Code changed in jenkins User: Jesse Glick Path: CHANGES.md http://jenkins-ci.org/commit/workflow-plugin/e7e1a1ed501528333bbe6b746b8815e345b42ee4 Log: JENKINS-27571 Noting. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27571) Workflow Job: "Back to Project" link not navigating
SCM/JIRA link daemon commented on JENKINS-27571 Workflow Job: "Back to Project" link not navigating Code changed in jenkins User: Jesse Glick Path: CHANGES.md job/src/main/resources/org/jenkinsci/plugins/workflow/job/WorkflowRun/sidepanel.jelly http://jenkins-ci.org/commit/workflow-plugin/6a1c76514ae3fe5389996f2781ac09a5ffa651e9 Log: Merge pull request #117 from jglick/upUrl-JENKINS-27571 JENKINS-27571 Non-link in build sidepanel Compare: https://github.com/jenkinsci/workflow-plugin/compare/7a14f6af5418...6a1c76514ae3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27571) Workflow Job: "Back to Project" link not navigating
SCM/JIRA link daemon commented on JENKINS-27571 Workflow Job: "Back to Project" link not navigating Code changed in jenkins User: Jesse Glick Path: job/src/main/resources/org/jenkinsci/plugins/workflow/job/WorkflowRun/sidepanel.jelly http://jenkins-ci.org/commit/workflow-plugin/275bfa8a06cc37cf47d37e74d9d064147ad69440 Log: [FIXED JENKINS-27571] AbstractBuild defines getUpUrl, but WorkflowRun never had it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27571) Workflow Job: "Back to Project" link not navigating
SCM/JIRA link daemon resolved JENKINS-27571 as Fixed Workflow Job: "Back to Project" link not navigating Change By: SCM/JIRA link daemon (23/Apr/15 12:18 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-28011) Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job
dogfood
commented on JENKINS-28011
Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job
Integrated in jenkins_main_trunk #4101
[FIXED JENKINS-28011] Amending #1563, ${descriptor} is not necessarily ${attrs.descriptor}! (Revision 343382b9ff8a978f6914cc64714a5c16bd9b511a)
Result = UNSTABLE
jesse glick : 343382b9ff8a978f6914cc64714a5c16bd9b511a
Files :
core/src/main/resources/lib/form/class-entry.jelly
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23149) ArtifactArchiver throws java.lang.OutOfMemoryError: Map failed
Mircea D commented on JENKINS-23149 ArtifactArchiver throws java.lang.OutOfMemoryError: Map failed Happened to me too on 1.604... I'm trying to see if restarting Jenkins works as a workaround. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ldap-plugin] (JENKINS-23214) LDAP Plugin occasionally does not connect LDAP server
Mark Nejman commented on JENKINS-23214 LDAP Plugin occasionally does not connect LDAP server I am still experiencing this issue where after about 3 or 4 hours, I can no longer log in and need to restart. The Jenkins log did not show any errors, but I tried using the Jenkins CLI and got a stack trace. Hopefully this can shed some light on the issue. I should note that our LDAP connection is an SSL connection through an F5 load balancer. Our certificates are signed by a CA, and I do have the trust store set up. org.acegisecurity.AuthenticationServiceException: Unable to connect to LDAP server; nested exception is javax.naming.CommunicationException: :636 [Root exception is javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: Path does not chain with any of the trust anchors]; nested exception is org.acegisecurity.ldap.LdapDataAccessException: Unable to connect to LDAP server; nested exception is javax. naming.CommunicationException: :636 [Root exception is javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: Path does not chain with any of the trust anchors] at org.acegisecurity.providers.ldap.LdapAuthenticationProvider.retrieveUser(LdapAuthenticationProvider.java:238) at org.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:122) at org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:200) at org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:47) at hudson.security.LDAPSecurityRealm$LDAPAuthenticationManager.authenticate(LDAPSecurityRealm.java:786) at hudson.security.LDAPSecurityRealm.authenticate(LDAPSecurityRealm.java:663) at hudson.security.AbstractPasswordBasedSecurityRealm.doAuthenticate(AbstractPasswordBasedSecurityRealm.java:114) at hudson.security.AbstractPasswordBasedSecurityRealm.access$100(AbstractPasswordBasedSecurityRealm.java:39) at hudson.security.AbstractPasswordBasedSecurityRealm$1.authenticate(AbstractPasswordBasedSecurityRealm.java:81) at hudson.cli.CLICommand.main(CLICommand.java:231) at hudson.cli.CliManagerImpl.main(CliManagerImpl.java:92) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:326) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:301) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:260) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:325) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at hudson.cli.CliManagerImpl$1.call(CliManagerImpl.java:63) at hudson.remoting.CallableDecoratorAdapter.call(CallableDecoratorAdapter.java:18) at hudson.remoting.CallableDecoratorList$1.call(CallableDecoratorList.java:21) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: org.acegisecurity.ldap.LdapDataAccessException: Unable to connect to LDAP server; nested exception is javax.naming.CommunicationException: :636 [Root exception is javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: Path does not chain with any of the trust anchors] at org.acegisecurity.ldap.DefaultInitialDirContextFactory.connect(DefaultInitialDirCon
[JIRA] [git-plugin] (JENKINS-28031) Git plugin using committer rather than author name in Changes log
Mark Waite
resolved JENKINS-28031 as Cannot Reproduce
Git plugin using committer rather than author name in Changes log
The environment variable ${CHANGES} is not mentioned anywhere in the git plugin or the git client plugin or Jenkins core, at least as far as I can tell.
When I ran a job that included an XShell step "echo ${CHANGES}" it showed no value for CHANGES.
When I ran a job that included a shell step "echo ${CHANGES}" it showed an empty string for CHANGES.
Can you either assign this to the plugin that is providing those values for you, or provide more details so that the problem can be duplicated?
Change By:
Mark Waite
(23/Apr/15 12:58 PM)
Status:
Open
Resolved
Resolution:
Cannot Reproduce
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-28057) CMake, CPack, CTest parser
Ulli Hafner commented on JENKINS-28057 CMake, CPack, CTest parser Why don't you convert your generic parser to a native parser and provide it as a pull request? Most parsers are provided by volunteers. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-28057) CMake, CPack, CTest parser
Ulli Hafner updated JENKINS-28057 CMake, CPack, CTest parser Change By: Ulli Hafner (23/Apr/15 1:09 PM) Assignee: Ulli Hafner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-28057) CMake, CPack, CTest parser
Dave Taddei commented on JENKINS-28057 CMake, CPack, CTest parser Generic parser was perhaps misleading. We are supplying a parsing regex to the Log Parser plugin (https://wiki.jenkins-ci.org/display/JENKINS/Log+Parser+Plugin) as a workaround. For what it's worth the Warning parser works extremely well! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-28067) android emulator fails to start "error: device offline"
Richard Mortimer created JENKINS-28067 android emulator fails to start "error: device offline" Issue Type: Bug Assignee: Richard Mortimer Components: android-emulator-plugin Created: 23/Apr/15 1:25 PM Description: A bit more evidence in the long running saga of Android emulator failing to start properly. I have started a new issue but this is closely related to JENKINS-11952 Notes: The information below was gathered using plugin 2.12. That would fail often enough for me that I could get some slow debug. I'm pretty sure that what I've found will apply to 2.13 and onwards. I'm personally not convinced that switching back to the localhost: method of connection is 100% safe given my previous investigations for JENKINS-12821 but that is a different matter. For those who do not want to try to understand the logs below then the short story is that I suspect that the android-emulator-plugin is causing the emulator<->ADB connection to lock up by connecting to the emulator ADB port to check whether it has started up. It maybe that the lockup would happen anyway but I think we can remove the waitForSocket (and subsequent single ADB connect - if using the emulator- connection) without any adverse effects on the startup procedure. I do not have a sample pull request yet but I have a modified version of 2.12 running locally and will see if my once/twice daily lockups continue to happen. Only the brave need read below... Below is the TCP traffic to the emulator ADB port (5561 in this instance) on a startup that fails. I have a number of examples of this with the same symptoms. richm@bishop:~$ tcpdump -r /tmp/150423_android1.pcap port 5561 reading from file /tmp/150423_android1.pcap, link-type LINUX_SLL (Linux cooked) => ADB server connects here (port 60975) 10:44:18.487165 IP localhost.60975 > localhost.5561: Flags [S], seq 3774551783, win 43690, options [mss 65495,sackOK,TS val 791658429 ecr 0,nop,wscale 7], length 0 10:44:18.487183 IP localhost.5561 > localhost.60975: Flags [R.], seq 0, ack 3774551784, win 0, length 0 10:44:25.247907 IP localhost.32808 > localhost.5561: Flags [S], seq 1102610480, win 43690, options [mss 65495,sackOK,TS val 791660119 ecr 0,nop,wscale 7], length 0 10:44:25.247950 IP localhost.5561 > localhost.32808: Flags [S.], seq 869467149, ack 1102610481, win 43690, options [mss 65495,sackOK,TS val 791660119 ecr 791660119,nop,wscale 7], length 0 10:44:25.247987 IP localhost.32808 > localhost.5561: Flags [.], ack 1, win 342, options [nop,nop,TS val 791660119 ecr 791660119], length 0 => ADB server sends start of CNXN handshake 10:44:25.252799 IP localhost.32808 > localhost.5561: Flags [P.], seq 1:32, ack 1, win 342, options [nop,nop,TS val 791660121 ecr 791660119], length 31 10:44:25.252886 IP localhost.5561 > localhost.32808: Flags [.], ack 32, win 342, options [nop,nop,TS val 791660121 ecr 791660121], length 0 => Jenkins android plugin tests for emulator adb port alive => When things go wrong the emulator seems to ignore this for a while 10:44:26.651163 IP localhost.32810 > localhost.5561: Flags [S], seq 571765708, win 43690, options [mss 65495,sackOK,TS val 791660470 ecr 0,nop,wscale 7], length 0 10:44:26.651200 IP localhost.5561 > localhost.32810: Flags [S.], seq 2069788705, ack 571765709, win 43690, options [mss 65495,sackOK,TS val 791660470 ecr 791660470,nop,wscale 7], length 0 10:44:26.651237 IP localhost.32810 > localhost.5561: Flags [.], ack 1, win 342, options [nop,nop,TS val 791660470 ecr 791660470], length 0 => Jenkins android plugin immediately closes connection => Emulator looks to be sitting waiting for CNXN handshake 10:44:26.651407 IP localhost.32810 > localhost.5561: Flags [F.], seq 1, ack 1, win 342, options [nop,nop,TS val 791660470 ecr 791660470], length 0 10:44:26.652528 IP localhost.5561 > localhost.32810: Flags [.], ack 2, win 342, options [nop,nop,TS val 791660471 ecr 791660470], length 0 10:45:41.012188 IP localhost.5561 > localhost.32808: Flags [F.], seq 1, ack 32, win 342, options [nop,nop,TS val 791679060 ecr 791660121], length 0 => ADB server gives up waiting for
[JIRA] [build-pipeline-plugin] (JENKINS-28068) Build Pipeline Dashboard View destroys layout of jenkins
Vadimo created JENKINS-28068 Build Pipeline Dashboard View destroys layout of jenkins Issue Type: Bug Assignee: Unassigned Attachments: Bildschirmfoto 2015-04-23 um 15.41.59.png Components: build-pipeline-plugin Created: 23/Apr/15 1:43 PM Description: this is related to issue JENKINS-25666 but it appears that the plugin also destroys the layout of jenkins if a Build Pipeline Dashboard View is added to the an existing view. Project: Jenkins Priority: Major Reporter: Vadimo This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-27910) Cyrillic symbols and file removal
Mark Waite commented on JENKINS-27910 Cyrillic symbols and file removal Can you provide the specific characters which are in the problem file name? There are already automated tests in the code for various interesting characters, and it may be that we need to add more tests with the specific characters you have identified. Also, can you confirm (as Daniel Beck noted) that the Java configuration of the slave running that process is using UTF-8 settings for its locale? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-27910) Cyrillic symbols and file removal
Alexander Chernyy commented on JENKINS-27910 Cyrillic symbols and file removal Mark: Nothing specific in those filenames. I met this issue from time to time with different cyrillic filenames. For example лицо.png (face.png) or плавание.png (swim.png). Daniel: One build machine was configured to UTF-8 but another was not. I can not provoke bug now but if I did this I will comment this issue. Thanks a lot for you help. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28069) Builf failures due to artifacts being lost by jenkins 1.610
John Mellor created JENKINS-28069 Builf failures due to artifacts being lost by jenkins 1.610 Issue Type: Bug Assignee: Unassigned Components: core Created: 23/Apr/15 2:10 PM Description: Updating from Jenkins 1.609 to 1.610 causes artifacts that are actually present to become invisible to Jenkins, causing incorrect product build failures. I have multiple builds showing the same problem using several different build mechanisms. All show a bogus failure to see the artifact. All components and plugins are up-to-date. Reverting back to Jenkins 1.609 corrects the problem. Example build log excerpt showing impossible operation follows. The artifact is successfully moved to a subdir, followed by several empty build steps (commented out to isolate the bug), followed by artifact archiving in the post-build actions. The missing artifact is actually present in the expected place, as verified manually. However, Jenkins cannot see it. Possible fatal error in the artifact archiving code in 1.610? . . . 00:05:26.255 + mkdir -p build/trusty 00:05:26.257 + mv build/cape_1.6.0-1~develop~e239_amd64.deb build/trusty/ 00:05:26.275 + exit 0 00:05:26.295 [cape_develop] $ /bin/bash -xe /tmp/hudson3392614376804147389.sh 00:05:26.339 [cape_develop] $ /bin/bash -xe /tmp/hudson150957069606062707.sh 00:05:26.376 [cape_develop] $ /bin/bash -xe /tmp/hudson2456916382110583231.sh 00:05:26.417 [cape_develop] $ /bin/bash -xe /tmp/hudson782672795510148539.sh 00:05:26.454 [cape_develop] $ /bin/bash -xe /tmp/hudson3270660334305912197.sh 00:05:27.502 Archiving artifacts 00:05:32.094 ERROR: Failed to archive artifacts: build/trusty/*.deb 00:05:32.094 java.io.IOException: Failed to extract /var/lib/jenkins/workspace/cape_develop/transfer of 1 files 00:05:32.094 at hudson.FilePath.readFromTar(FilePath.java:2299) 00:05:32.094 at hudson.FilePath.copyRecursiveTo(FilePath.java:2208) 00:05:32.094 at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61) 00:05:32.094 at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:219) 00:05:32.094 at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74) 00:05:32.094 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 00:05:32.094 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) 00:05:32.094 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:721) 00:05:32.094 at hudson.model.Build$BuildExecution.post2(Build.java:183) 00:05:32.094 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670) 00:05:32.094 at hudson.model.Run.execute(Run.java:1766) 00:05:32.094 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 00:05:32.094 at hudson.model.ResourceController.execute(ResourceController.java:98) 00:05:32.094 at hudson.model.Executor.run(Executor.java:374) 00:05:32.094 Caused by: java.io.IOException: Truncated TAR archive 00:05:32.094 at org.apache.commons.compress.archivers.tar.TarArchiveInputStream.read(TarArchiveInputStream.java:614) 00:05:32.094 at java.io.InputStream.read(InputStream.java:101) 00:05:32.094 at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1792) 00:05:32.094 at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1769) 00:05:32.094 at org.apache.commons.io.IOUtils.copy(IOUtils.java:1744) 00:05:32.094 at hudson.util.IOUtils.copy(IOUtils.java:40) 00:05:32.094 at hudson.FilePath.readFromTar(FilePath.java:2289) 00:05:32.094 ... 13 more 00:05:32.094 Build step 'Archive the artifacts' changed build result to FAILURE Environment: Ubuntu 12.04.1 64bit, JDK-6 (the default openJDK6b24-1.11.5) Project: Jenkins Priority: Major Reporter: John Mellor
[JIRA] [core] (JENKINS-28069) Builf failures due to artifacts being lost by jenkins 1.610
Daniel Beck resolved JENKINS-28069 as Duplicate Builf failures due to artifacts being lost by jenkins 1.610 Change By: Daniel Beck (23/Apr/15 2:15 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23149) ArtifactArchiver throws java.lang.OutOfMemoryError: Map failed
Mircea D commented on JENKINS-23149 ArtifactArchiver throws java.lang.OutOfMemoryError: Map failed Yes, restarting Jenkins seems to be a good workaround. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23149) ArtifactArchiver throws java.lang.OutOfMemoryError: Map failed
Daniel Beck commented on JENKINS-23149 ArtifactArchiver throws java.lang.OutOfMemoryError: Map failed It's likely that Jenkins simply has too little RAM available. increase it using the -Xmx argument to java, and maybe install the Monitoring plugin to keep an eye on memory usage of the JVM. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-28062) Channel listener onClose propagated exceptions
Jesse Glick updated JENKINS-28062 Channel listener onClose propagated exceptions Change By: Jesse Glick (23/Apr/15 2:43 PM) Labels: diagnostics This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23149) ArtifactArchiver throws java.lang.OutOfMemoryError: Map failed
Mircea D commented on JENKINS-23149 ArtifactArchiver throws java.lang.OutOfMemoryError: Map failed Sounds reasonable enough, I'll keep an eye out when it happens again and try to increase the heap. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-20709) CLI client hangs
Jeremy Van Haren commented on JENKINS-20709 CLI client hangs We are still seeing this issue where cli commands can hang. We are getting this on 1.580.2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-20709) CLI client hangs
Jeremy Van Haren edited a comment on JENKINS-20709 CLI client hangs We are still seeing this issue where cli commands can hang. We are getting this on 1.580.2. We kick off about 100-200 cli commands nightly, and we'll get a hang on one of them about 1-2 times a week. So, 1/1000 times approximately. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-28070) Maven 3.3.1 build fail on Unix if Maven is the default installation
Laurent TOURREAU created JENKINS-28070 Maven 3.3.1 build fail on Unix if Maven is the default installation Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 23/Apr/15 3:26 PM Description: We face the following build error when using Maven 3.3.1 (the unique Maven installation) in Jenkins. Building on master in workspace /myapp/mymodule Updating svn://svn.mycompany.com/mymodule at revision '2015-04-23T16:00:24.616 +0100' At revision 37434 no change for svn://svn.mycompany.com/mymodule since the previous build [build_mymodule] $ mvn -DparentVersion=[31.0.26] versions:update-parent versions:use-releases -X Build step 'Invoke top-level Maven targets' marked build as failure Environment: Red Hat Linux 6.6, Jenkins 1.609 Project: Jenkins Priority: Blocker Reporter: Laurent TOURREAU This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28071) BuildCommand limited to AbstractProject
Jesse Glick created JENKINS-28071 BuildCommand limited to AbstractProject Issue Type: Bug Assignee: Unassigned Components: core Created: 23/Apr/15 3:46 PM Description: Should use ParameterizedBuildMixIn.ParameterizedJob instead. Project: Jenkins Labels: workflow cli Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-28011) Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job
Miguel Rojas commented on JENKINS-28011 Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job Awesome, thanks for the fill. I'll be awaiting for the release. Regards. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-28011) Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job
Miguel Rojas edited a comment on JENKINS-28011 Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job Awesome, thanks for the fix. I'll be awaiting for the release. Regards. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-28062) Channel listener onClose propagated exceptions
SCM/JIRA link daemon commented on JENKINS-28062 Channel listener onClose propagated exceptions Code changed in jenkins User: Stephen Connolly Path: src/main/java/hudson/remoting/Channel.java http://jenkins-ci.org/commit/remoting/846b3e0527aa1dc5629a2a7e870f4b7efb653cfb Log: Merge pull request #42 from jenkinsci/safe-listener-fire [FIXED JENKINS-28062] A Channel.Listener's onClose method that propagate... Compare: https://github.com/jenkinsci/remoting/compare/2b6a02192ca4...846b3e0527aa This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudbees-folder-plugin] (JENKINS-28043) Reload configs of all jobs in folder
Jesse Glick commented on JENKINS-28043 Reload configs of all jobs in folder Loading of folder items is done by the Folders plugin. Yes, but in response to loading of the Folder itself, which should happen during a general Jenkins reload too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudbees-folder-plugin] (JENKINS-28043) Reload configs of all jobs in folder
Jesse Glick updated JENKINS-28043 Reload configs of all jobs in folder Change By: Jesse Glick (23/Apr/15 3:59 PM) Labels: folders reload This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-25340) lost trend history after skipping build
Jesse Glick commented on JENKINS-25340 lost trend history after skipping build JENKINS-24380 makes it feasible to add an API by which a plugin could ask about the list of builds which exist, which previously would have been very hard; it does not actually include such an API. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-28012) "Failed to parse POMs" during archiving of poms when running maven job
SCM/JIRA link daemon commented on JENKINS-28012 "Failed to parse POMs" during archiving of poms when running maven job Code changed in jenkins User: Oleg Nenashev Path: core/pom.xml core/src/main/java/hudson/FilePath.java core/src/main/java/hudson/org/apache/tools/tar/TarInputStream.java core/src/main/java/hudson/org/apache/tools/tar/TarOutputStream.java core/src/main/java/hudson/util/io/TarArchiver.java http://jenkins-ci.org/commit/jenkins/ca21c65bf2538982126bd465eb70840071a61e4e Log: Merge pull request #1667 from oleg-nenashev/JENKINS-10629-FIX [JENKINS-28013,JENKINS-28012] - Revert changes for JENKINS-10629 Compare: https://github.com/jenkinsci/jenkins/compare/8c94920973c4...ca21c65bf253 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10629) Tar implimentation can't handle > 8GB and doesn't error out.
SCM/JIRA link daemon commented on JENKINS-10629 Tar implimentation can't handle > 8GB and doesn't error out. Code changed in jenkins User: Oleg Nenashev Path: core/pom.xml core/src/main/java/hudson/FilePath.java core/src/main/java/hudson/org/apache/tools/tar/TarInputStream.java core/src/main/java/hudson/org/apache/tools/tar/TarOutputStream.java core/src/main/java/hudson/util/io/TarArchiver.java http://jenkins-ci.org/commit/jenkins/ca21c65bf2538982126bd465eb70840071a61e4e Log: Merge pull request #1667 from oleg-nenashev/JENKINS-10629-FIX [JENKINS-28013,JENKINS-28012] - Revert changes for JENKINS-10629 Compare: https://github.com/jenkinsci/jenkins/compare/8c94920973c4...ca21c65bf253 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10629) Tar implimentation can't handle > 8GB and doesn't error out.
SCM/JIRA link daemon commented on JENKINS-10629 Tar implimentation can't handle > 8GB and doesn't error out. Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/util/io/TarArchiver.java http://jenkins-ci.org/commit/jenkins/ee57300963ca0137565f61fe314d459b627ad74b Log: Revert "FIXED JENKINS-10629] - Enable BigNumber mode to support archiving of files with size >8Gb" This reverts commit 4ddeeb84195fa29c964ef2e55661b669c310baeb. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
SCM/JIRA link daemon commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive Code changed in jenkins User: Oleg Nenashev Path: core/pom.xml core/src/main/java/hudson/FilePath.java core/src/main/java/hudson/org/apache/tools/tar/TarInputStream.java core/src/main/java/hudson/org/apache/tools/tar/TarOutputStream.java core/src/main/java/hudson/util/io/TarArchiver.java http://jenkins-ci.org/commit/jenkins/ca21c65bf2538982126bd465eb70840071a61e4e Log: Merge pull request #1667 from oleg-nenashev/JENKINS-10629-FIX [JENKINS-28013,JENKINS-28012] - Revert changes for JENKINS-10629 Compare: https://github.com/jenkinsci/jenkins/compare/8c94920973c4...ca21c65bf253 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10629) Tar implimentation can't handle > 8GB and doesn't error out.
SCM/JIRA link daemon commented on JENKINS-10629 Tar implimentation can't handle > 8GB and doesn't error out. Code changed in jenkins User: Oleg Nenashev Path: core/pom.xml core/src/main/java/hudson/FilePath.java core/src/main/java/hudson/org/apache/tools/tar/TarInputStream.java core/src/main/java/hudson/org/apache/tools/tar/TarOutputStream.java core/src/main/java/hudson/util/io/TarArchiver.java http://jenkins-ci.org/commit/jenkins/8f1280a85c54ea6150b15c38303464ab23b32e92 Log: Revert "JENKINS-10629 - Migrate the Tar archives handling code to commons-compress" This reverts commit b6c7b83e7ba1a7538382d220d044626f2b2e65be. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-28072) Active Directory Binding is failed in Jenkins
Rajesh Kondakindi created JENKINS-28072 Active Directory Binding is failed in Jenkins Issue Type: Task Assignee: Unassigned Components: active-directory-plugin Created: 23/Apr/15 4:31 PM Description: I tried both secured and non-secured authentication. But failed to bind and getting below error in configure Global Security page: Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request POST /descriptorByName/hudson.plugins.active_directory.ActiveDirectorySecurityRealm/validate. Reason: Error reading from remote server This is very urgent for me to resolve this issue. I am getting below error in the log: Apr 23, 2015 12:14:27 PM hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl bind WARNING: Failed to bind to xx.xxx.xx.xxx:3269 javax.naming.CommunicationException: xx.xxx.xx.xxx:3269 [Root exception is java.net.ConnectException: Connection timed out] at com.sun.jndi.ldap.Connection.(Connection.java:216) at com.sun.jndi.ldap.LdapClient.(LdapClient.java:137) at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1613) at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2746) at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:319) at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192) at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:151) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:480) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:430) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.doValidate(ActiveDirectorySecurityRealm.java:369) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:198) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:176) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:99) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at huds
[JIRA] [copyartifact-plugin] (JENKINS-28011) Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job
Raphael Castaneda commented on JENKINS-28011 Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job Thanks for the quick fix. In the meantime for anyone looking at this I can confirm that downgrading to 1.609 resolves the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [join-plugin] (JENKINS-28073) Join doesn't trigger if downstream project(s) fail
Christopher Orr moved JENKINS-28073 Join doesn't trigger if downstream project(s) fail Change By: Christopher Orr (23/Apr/15 6:00 PM) Project: Infrastructure Jenkins Key: INFRA JENKINS - 281 28073 Workflow: jira JNJira Component/s: join-plugin Component/s: ci This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [join-plugin] (JENKINS-28073) Join doesn't trigger if downstream project(s) fail
Christopher Orr assigned JENKINS-28073 to mdonohue Join doesn't trigger if downstream project(s) fail Moved to JENKINS project as this was incorrectly filed under the INFRA project. Change By: Christopher Orr (23/Apr/15 6:01 PM) Assignee: R. Tyler Croy mdonohue This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodejs-plugin] (JENKINS-28074) NodeJS does not list current installable versions
Erik L created JENKINS-28074 NodeJS does not list current installable versions Issue Type: Bug Assignee: Unassigned Attachments: screenshot.png Components: nodejs-plugin Created: 23/Apr/15 6:03 PM Description: Trying to install the NodeJS plugin on a fresh instance of Jenkins, and I've normally been met with a list of configurable versions of NodeJS that the plugin is aware of. This isn't the case in this installation. I've removed the NodeJS plugin and readded to nothing. I've then reviewed the updates/ folder inside the jenkins install folder and I didn't find the hudson.plugins.nodejs.tools.NodeJSInstaller file. Is that normal? Isn't that where the list comes from? I've attached a screen shot of what I am currently seeing in the configuration manager. I've tried to set the version manually, but the plugin throws errors about not knowing about the version. Environment: Ubuntu 14.04,Jenkins 1.610, NodeJS Plugin 0.2.1 Project: Jenkins Priority: Minor Reporter: Erik L This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10629) Tar implimentation can't handle > 8GB and doesn't error out.
Daniel Beck reopened JENKINS-10629 Tar implimentation can't handle > 8GB and doesn't error out. Reopening this issue as the fix has been reverted due to regressions. Change By: Daniel Beck (23/Apr/15 6:16 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
Daniel Beck resolved JENKINS-28013 as Fixed Archiving artifiacts fails with java.io.IOException: Truncated TAR archive Resolved by reverting the fix for JENKINS-10629. Change By: Daniel Beck (23/Apr/15 6:21 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-28012) "Failed to parse POMs" during archiving of poms when running maven job
Daniel Beck resolved JENKINS-28012 as Fixed "Failed to parse POMs" during archiving of poms when running maven job Resolved by reverting the fix for JENKINS-10629. Change By: Daniel Beck (23/Apr/15 6:21 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27268) "dumb" slave?
luke pao commented on JENKINS-27268 "dumb" slave? VERY much appreciate the transparency of process here. It sounds like some of you genuinely care that this language is highly offensive outside of this tech bubble we're in, but the sad reality is redit/hn flame-throwing tends to be the biggest motivation for making these kind of changes and saving face. As for next steps, what I've gathered from the meeting is SUBJ terminology will likely be addressed. That's good, but satisfactory would be a change in terminology similar to Django. However, the idea of making that kind of change sounded unfavorable in the meeting logs, so can you clarify exactly what changes will and will not be made regarding this issue? Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27442) Failed to record SCM polling for hudson.model.FreeStyleProject
Daniel Mish commented on JENKINS-27442 Failed to record SCM polling for hudson.model.FreeStyleProject I am seeing this as well, however, I do not have EnvInject installed, so https://issues.jenkins-ci.org/browse/JENKINS-16036 does not apply in my case. The Jenkins version is 1.602. Here is a Stack Trace: Apr 23, 2015 2:16:00 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@528d94b0[vendorCommon] java.lang.NullPointerException at org.jenkinsci.plugins.chromedriver.EnvironmentContributorImpl.buildEnvironmentFor(EnvironmentContributorImpl.java:23) at hudson.model.Run.getEnvironment(Run.java:2248) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:917) at hudson.scm.SubversionSCM.compareRemoteRevisionWith(SubversionSCM.java:1343) at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:380) at hudson.scm.SCM.poll(SCM.java:397) at hudson.model.AbstractProject._poll(AbstractProject.java:1446) at hudson.model.AbstractProject.poll(AbstractProject.java:1349) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:515) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:544) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Hello
Please is your email active? I have a confidential partnership request for you -- 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] [hockeyapp-plugin] (JENKINS-23549) HockeyApp Plugin : ArrayIndexOutOfBoundsException
Antek Baranski commented on JENKINS-23549 HockeyApp Plugin : ArrayIndexOutOfBoundsException It was fixed on my fork of the plugin on github.com This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-28048) Allow DslScriptLoader classloading customisation for reuse in other plug-ins
Damien Coraboeuf commented on JENKINS-28048 Allow DslScriptLoader classloading customisation for reuse in other plug-ins In order to add more context, I'd like to be able to call the Job DSL from within another plug-in. In the DSL scripts, I want to refer to classes and methods which are in my plug-in. As of version 1.32, the class loader for the DslScriptLoader does not allow to look for those classes. I have fiddled around with passing variables in the scope (see this commit - no pull request yet) but this does not resolve the class loading issues. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10629) Tar implimentation can't handle > 8GB and doesn't error out.
Oleg Nenashev commented on JENKINS-10629 Tar implimentation can't handle > 8GB and doesn't error out. Daniel, thanks for handling JIRA issues. I'll continue working on the issue to achieve a better test coverage. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-28075) Want to see the LoadRunner controller execute when runing from Jenkins
Copelin Thomas created JENKINS-28075 Want to see the LoadRunner controller execute when runing from Jenkins Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 23/Apr/15 7:59 PM Description: We upgraded the plugin to 3.0.7 for the HP LoadRunner and now we can't see the Controller execute during a build. Is there some setting we have misconfigured? Environment: HP Application Automation Tools ver 3.0.7 Project: Jenkins Labels: plugin Priority: Minor Reporter: Copelin Thomas This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10629) Tar implimentation can't handle > 8GB and doesn't error out.
dogfood commented on JENKINS-10629 Tar implimentation can't handle > 8GB and doesn't error out. Integrated in jenkins_main_trunk #4103 Result = SUCCESS This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-28076) git plugin: support JOB_NAME in included/excluded regions
Sean McLaughlin updated JENKINS-28076 git plugin: support JOB_NAME in included/excluded regions Change By: Sean McLaughlin (23/Apr/15 8:24 PM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-28076) git plugin: support JOB_NAME in included/excluded regions
Sean McLaughlin created JENKINS-28076 git plugin: support JOB_NAME in included/excluded regions Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 23/Apr/15 8:24 PM Description: I expected $JOB_NAME/.* to work in the included regions section of the git plugin. I propose doing env variable replacement in such paths. Project: Jenkins Priority: Minor Reporter: Sean McLaughlin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-28070) Maven 3.3.1 build fail on Unix if Maven is the default installation
Daniel Beck commented on JENKINS-28070 Maven 3.3.1 build fail on Unix if Maven is the default installation Isn't this just a duplicate of the linked issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-28072) Active Directory Binding is failed in Jenkins
Daniel Beck resolved JENKINS-28072 as Not A Defect Active Directory Binding is failed in Jenkins Does not appear to be a bug. Please note that this is an issue tracker, not a support website. Change By: Daniel Beck (23/Apr/15 9:19 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
