[JIRA] [core] (JENKINS-28200) update plugin makes timeout error
Title: Message Title Dave Molinari updated an issue Jenkins / JENKINS-28200 update plugin makes timeout error Change By: Dave Molinari Attachment: Snip20160201_1.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28200) update plugin makes timeout error
Title: Message Title Dave Molinari commented on JENKINS-28200 Re: update plugin makes timeout error Same issue, i have ports 80 and 443 open going out to updates.jenkins-ci.org over a very secure network, i'm able to test my proxy configurations successfully, however, when i click update now i get a timeout. If I rightclick and open in new window I see the following message, try POSTing does not work either, it essentially times out the same way. I'm assuming i need to open a port, but i'm not sure which currently. I need to do more research. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28200) update plugin makes timeout error
Title: Message Title Daniel Beck resolved as Not A Defect There is no bug here. Occasionally, very rarely, one of the mirrors isn't reachable. Try again later. There is no way to select a specific mirror unless you e.g. route all the host names you can receive to a specific mirror. Even then I'm not sure about it. Jenkins / JENKINS-28200 update plugin makes timeout error Change By: Daniel Beck Status: In Progress Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28200) update plugin makes timeout error
Title: Message Title Dave Molinari edited a comment on JENKINS-28200 Re: update plugin makes timeout error Same issue, i have ports 80 and 443 open going out to updates.jenkins-ci.org over a very secure completely locked down network, i'm able to test my proxy configurations successfully, however, when i click update now i get a timeout. If I rightclick and open in new window I see the following message, try POSTing does not work either, it essentially times out the same way. I'm assuming i need to open a port, but i'm not sure which currently. I need to do more research. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32716) Archive artefacts crashes on file names containing Unicode characters
Title: Message Title Richard Moss created an issue Jenkins / JENKINS-32716 Archive artefacts crashes on file names containing Unicode characters Issue Type: Bug Assignee: Unassigned Components: core Created: 01/Feb/16 8:11 PM Environment: Server: OS: Windows Home Server 2011 (64bit) Jenkins: 1.646 JRE: 1.8.0_66-b18 according to /systeminfo Installation: Windows Installer, Windows Service Plugins: Plugins: ant: 1.2 antisamy-markup-formatter: 1.3 change-assembly-version-plugin: 1.5.1 credentials: 1.24 cvs: 2.12 email-ext: 2.40.5 external-monitor-job: 1.4 gravatar: 2.1 htmlpublisher: 1.10 javadoc: 1.3 junit: 1.10 ldap: 1.11 mailer: 1.16 mapdb-api: 1.0.6.0 matrix-auth: 1.2 matrix-project: 1.6 maven-plugin: 2.12.1 msbuild: 1.25 nunit: 0.17 pam-auth: 1.2 powershell: 1.3 scm-api: 1.0 script-security: 1.17 simple-theme-plugin: 0.3 ssh-credentials: 1.11 ssh-slaves: 1.10 subversion: 2.5.7 token-macro: 1.12.1 translation: 1.12 windows-slaves: 1.1 workflow-step-api: 1.13 Slave: OS: Windows 10 Professional (64bit) JRE: Version 8 update 71 (32bit) Browser: Chrome Installation: Windows Service Labels: artifact unicode crash Priority: Major Reporter: Richard Moss
[JIRA] [htmlpublisher-plugin] (JENKINS-32714) HTML Report not accessible
Title: Message Title Kalyan Koduru created an issue Jenkins / JENKINS-32714 HTML Report not accessible Issue Type: Bug Assignee: mcrooney Attachments: Capture.JPG Components: htmlpublisher-plugin Created: 01/Feb/16 7:03 PM Environment: Jenkins v1.641, HTML Publisher plugin 1.10 Priority: Major Reporter: Kalyan Koduru Hello, I configured my jenkins job to publish html reports as per documentation. However, in the recent times, I started to notice that clicking HTML report redirects to an empty index page as attached below:
[JIRA] [core] (JENKINS-32716) Archive artefacts crashes on file names containing Unicode characters
Title: Message Title
Richard Moss updated an issue
Jenkins / JENKINS-32716
Archive artefacts crashes on file names containing Unicode characters
Change By:
Richard Moss
I created a simple project which didn't contain any build actions, only a post-build "archive artifacts" action. The project was supposed to pull a bunch of files out of SVN and dump them into a zip file, excluding certain files to make it easier for me to deploy.One of the files however is named {{specialcharacters-ę.html}} - notice the non-ASCII character.On attempting to "build" the project, the following content is dumped to the console log:{noformat}Archiving artifactsERROR: Failed to archive artifacts: **/*java.io.IOException: java.io.IOException: Failed to extract E:\Jenkins\workspace\demo.cyotek.com/transfer of 151 files at hudson.FilePath.readFromTar(FilePath.java:2300) at hudson.FilePath.copyRecursiveTo(FilePath.java:2209) at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:236) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668) at hudson.model.Run.execute(Run.java:1763) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Caused by: java.io.FileNotFoundException: E:\Jenkins\jobs\demo.cyotek.com\builds\3\archive\features\specialcharacters-?.html (The filename, directory name, or volume label syntax is incorrect) at java.io.FileOutputStream.open0(Native Method) at java.io.FileOutputStream.open(Unknown Source) at java.io.FileOutputStream.(Unknown Source) at java.io.FileOutputStream.(Unknown Source) at hudson.util.IOUtils.copy(IOUtils.java:38) at hudson.FilePath.readFromTar(FilePath.java:2290) ... 13 more at hudson.FilePath.copyRecursiveTo(FilePath.java:2216) at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:236) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668) at hudson.model.Run.execute(Run.java:1763) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Caused by: java.util.concurrent.ExecutionException: java.io.IOException: This archives contains unclosed entries. at
[JIRA] [mercurial-plugin] (JENKINS-7155) Support multiple Mercurial repositories per job
Title: Message Title James Sandlin commented on JENKINS-7155 Re: Support multiple Mercurial repositories per job The multi-scm plugin (which was never intended more than a POC) works fine until you attempt to do CI. At this point, the lack of real integration and capabilities breaks. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [next-executions-plugin] (JENKINS-32652) XSS in Possible Next Executions widget
Title: Message Title Adam Gabryś assigned an issue to Ignacio Albors Jenkins / JENKINS-32652 XSS in Possible Next Executions widget Change By: Adam Gabryś Assignee: Ignacio Albors Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [shiningpanda-plugin] (JENKINS-32715) virtualenv creation blows up on concurrent jobs started at the same-ish time
Title: Message Title oeuftete created an issue Jenkins / JENKINS-32715 virtualenv creation blows up on concurrent jobs started at the same-ish time Issue Type: Bug Assignee: Unassigned Components: shiningpanda-plugin Created: 01/Feb/16 8:07 PM Priority: Minor Reporter: oeuftete In our environment, we often have a dynamically-provisioned, multi-executor slave come online and immediately run parallel builds of the same job (for example, for different pull requests). The ShiningPanda plugin can sometimes cause a build failure in this scenario. It appears to try to create the same virtualenv in each job, and one fails: Succeeding job: 15:47:55 [some_job@2] $ /usr/bin/python2.7 /home/jenkins/shiningpanda/jobs/5cdc8cf6/virtualenv.py /home/jenkins/shiningpanda/jobs/5cdc8cf6/virtualenvs/d41d8cd9 15:47:56 New python executable in /home/jenkins/shiningpanda/jobs/5cdc8cf6/virtualenvs/d41d8cd9/bin/python2.7 15:47:56 Also creating executable in /home/jenkins/shiningpanda/jobs/5cdc8cf6/virtualenvs/d41d8cd9/bin/python 15:47:57 Installing setuptools, pip, wheel...done. 15:48:02 [some_job@2] $ /bin/sh -xe /tmp/shiningpanda8205115405688864725.sh Failing job:
[JIRA] [core] (JENKINS-28200) update plugin makes timeout error
Title: Message Title Dave Molinari commented on JENKINS-28200 Re: update plugin makes timeout error Looks like the updatesite json file actually is redirected to multiple mirrors...http://ftp-nyc.osuosl.org/ and http://mirror.xmission.com/ to name a few... Since we're being redirected, is there a way to still keep my network locked down and still use the proxy without getting all the possible mirrors? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multiple-scms-plugin] (JENKINS-31191) Jenkins Multiple SCM TFS Unkown Host
Title: Message Title Olivier Dagenais resolved as Duplicate The multiple-scms plugin is not currently supported; JENKINS-4542 will allow a job to specify multiple mappings while, as a workaround, JENKINS-4709 was recently implemented and version 4.1 of the plugin will support workspace cloaking. Jenkins / JENKINS-31191 Jenkins Multiple SCM TFS Unkown Host Change By: Olivier Dagenais Status: Open Resolved Assignee: Kevin Bell Stefan Issmer Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You
[JIRA] [tfs-plugin] (JENKINS-31405) com.microsoft.tfs.core.clients.versioncontrol.exceptions.LocalPathFormatException encountered when TFS repository has DOS format path
Title: Message Title Olivier Dagenais assigned an issue to Olivier Dagenais Jenkins / JENKINS-31405 com.microsoft.tfs.core.clients.versioncontrol.exceptions.LocalPathFormatException encountered when TFS repository has DOS format path Change By: Olivier Dagenais Assignee: redsolo Olivier Dagenais Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-11337) Git plugin only triggers a build for one branch
Title: Message Title Andrew Erickson commented on JENKINS-11337 Re: Git plugin only triggers a build for one branch Why was this closed? I just had a user request this functionality. It would be nice it was just an option in the git plugin. Thanks. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ownership-plugin] (JENKINS-32711) Adding Co-Owners by "Display Name" does not work
Title: Message Title Oleg Nenashev commented on JENKINS-32711 Re: Adding Co-Owners by "Display Name" does not work The field explicitly requires "User ID". User full name has never been supposed to work, and it has never worked AFAIK. If the user ID does not exist, the plugin prints explicit warning about it. See the attachment. The wording could be improve, but I don't see a bug here. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [performance-plugin] (JENKINS-28284) Images for Test Case trends is broken and generate exception
Title: Message Title dave davejenk commented on JENKINS-28284 Re: Images for Test Case trends is broken and generate exception Zhenya Frolov Did that new hpi fix things for you? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ownership-plugin] (JENKINS-32711) Adding Co-Owners by "Display Name" does not work
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-32711 Adding Co-Owners by "Display Name" does not work Change By: Oleg Nenashev Attachment: Screen Shot 2016-02-01 at 23.48.18.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multi-branch-project-plugin] (JENKINS-32253) Want an option to encode slashes in branch names differently
Title: Message Title brice maron commented on JENKINS-32253 Re: Want an option to encode slashes in branch names differently it seems that this issue is affecting a bunch of users as 4 of the 5 Pull-request are about this kind of problems with the "/" encoded in the directory name. might want to do smth here. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-30687) FATAL: Interrupted while waiting in MultiThreadedHttpConnectionManager
Title: Message Title Olivier Dagenais assigned an issue to Olivier Dagenais Jenkins / JENKINS-30687 FATAL: Interrupted while waiting in MultiThreadedHttpConnectionManager Change By: Olivier Dagenais Assignee: redsolo Olivier Dagenais Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-28973) naming autogenerated project does not postfix with branchname on first creation
Title: Message Title Javier Palacios commented on JENKINS-28973 Re: naming autogenerated project does not postfix with branchname on first creation About your idea, my current thinking is that it could be a work for another plugin. On one side, whichever 'script' receives the hook should be able to hande a few kins (standard push, tag, branch deletion), which becomes a bit complex. And on another side, there is the 'triggering' issue, because the matching project is selected based on the git url & branch, so the script should get executed on every push. And, finally, there is little control about what the 'script' does, and I don't want the plugin to create something it can't delete (and oppositely only delete things that it created before). Maybe I don't see clearly your use case, but the closer ones I see are pipeline alike , could be accomplished (maybe not easily) by chaining standard jenkins jobs or with plugins like flow dsl one. If you can live by triggering always the same job for a given repo (which is your 'script'), then there is a feature I'm working on might be useful to you (have a look to JENKINS-29317). If you are able to elaborate a bit more your use case, I will thing a bit more about this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-28973) naming autogenerated project does not postfix with branchname on first creation
Title: Message Title Javier Palacios resolved as Won't Do Jenkins / JENKINS-28973 naming autogenerated project does not postfix with branchname on first creation Change By: Javier Palacios Status: Reopened Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-11337) Git plugin only triggers a build for one branch
Title: Message Title Andrew Erickson commented on JENKINS-11337 Re: Git plugin only triggers a build for one branch Scenario: Job has multiple 'branches to build' configured. User desires a build of a branch other than the first configured (usually master). 'Build now' will build the first branch. User has no way of triggering a build of the specific branch. Current solutions: push a whitespace change to the branch desired to be built create discreet jobs per branch parameterize the job and don't use the git plugin Ideal solution: git plugin option: "pick branch on 'build now'" would basically do what https://github.com/phemmer/jenkins-git-chooser-build-branches, but inside the git plugin as you suggest ... Sorry to restart a long thread. Are you open to that solution? Should I open a new ticket with the above content (happy to work on it)? Thanks, Andy Add Comment
[JIRA] [tfs-plugin] (JENKINS-32513) TFS polling doesnt get triggered on some changes
Title: Message Title Olivier Dagenais resolved as Duplicate Jenkins / JENKINS-32513 TFS polling doesnt get triggered on some changes Change By: Olivier Dagenais Status: Open Resolved Assignee: redsolo ahmed daniel Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-32717) Multiple class directories and source directories not parsed if there is a space after comma delimiter
Title: Message Title Christopher Simons created an issue Jenkins / JENKINS-32717 Multiple class directories and source directories not parsed if there is a space after comma delimiter Issue Type: Bug Assignee: Christopher Simons Components: jacoco-plugin Created: 02/Feb/16 3:08 AM Priority: Minor Reporter: Christopher Simons Migrated from GitHub Issue #59; original description appears below, verbatim: This does not work: app/build/intermediates/classes/staging/debug, data/build/intermediates/classes/debug when changing to this: app/build/intermediates/classes/staging/debug,data/build/intermediates/classes/debug it works. Relates to this line https://github.com/jenkinsci/jacoco-plugin/blob/master/src/main/java/hudson/plugins/jacoco/JacocoPublisher.java#L272
[JIRA] [hockeyapp-plugin] (JENKINS-32128) Uploading to HockeyApp timed out
Title: Message Title Brantone commented on JENKINS-32128 Re: Uploading to HockeyApp timed out What's the latency like from master -> HockeyApp? How big is the app size? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-32718) Adaptive Build Health Thresholds
Title: Message Title Christopher Simons created an issue Jenkins / JENKINS-32718 Adaptive Build Health Thresholds Issue Type: New Feature Assignee: Unassigned Components: jacoco-plugin Created: 02/Feb/16 3:12 AM Priority: Minor Reporter: Christopher Simons Migrated from GitHub Issue #57; original description appears below, verbatim: This is a feature idea to support product teams adoption of test driven development (TDD). Right now it is a manual process to set the build failure thresholds, which is good in most cases. To support enforced improvement, these thresholds should be adaptive to the last successful build. That is, if the last successful build had a 81% test coverage, but the threshold was set to require only 80%, the threshold should automatically be increased. This is a special mode and must be selected as an option. The threshold increase is intended to only allow test coverage improvement while disallowing degradation. The manual process of setting these thresholds is not scalable for organizations as the jobs grow exponentially.
[JIRA] [hockeyapp-plugin] (JENKINS-31522) Hockeyapp Plugin: Support passing Token and ID as a variables
Title: Message Title Brantone commented on JENKINS-31522 Re: Hockeyapp Plugin: Support passing Token and ID as a variables This exists in repo (ex : https://github.com/jenkinsci/hockeyapp-plugin/commit/9b55000bec29d84ea9bb7edbb051c933b35e7e5a) But hasn't been released yet. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-11337) Git plugin only triggers a build for one branch
Title: Message Title Mark Waite commented on JENKINS-11337 Re: Git plugin only triggers a build for one branch If you'd like to build a particular git branch, you might try using the git parameter plugin to allow your users to choose the specific branch they want to build. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-31875) No working folder mapping when accessing TFS (win 10)
Title: Message Title Olivier Dagenais assigned an issue to Olivier Dagenais Jenkins / JENKINS-31875 No working folder mapping when accessing TFS (win 10) Change By: Olivier Dagenais Assignee: redsolo Olivier Dagenais Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-32395) Exception thrown when TFS plugin does SCM polling to TFS (on Jenkins version 1.643)
Title: Message Title Olivier Dagenais assigned an issue to Olivier Dagenais Jenkins / JENKINS-32395 Exception thrown when TFS plugin does SCM polling to TFS (on Jenkins version 1.643) Change By: Olivier Dagenais Assignee: redsolo Olivier Dagenais Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-11337) Git plugin only triggers a build for one branch
Title: Message Title Mark Waite commented on JENKINS-11337 Re: Git plugin only triggers a build for one branch Andrew Erickson this was closed because the original report was confirmed to be closed based on my interpretation of the phrasing of the bug report. The git plugin triggers builds for as many branches as match the "Branches to build" specification and have distinct SHA1 hashes. About 4 years after the original bug report, Patrick Hemmer reported that if two branches have the same SHA1 hash, he wanted two separate builds. I noted that is not the way the git plugin operates, that it assumes once a SHA1 has been built, it does not need to be rebuilt. He noted that he was able to implement an extension to the plugin which allows a new choosing strategy that can build the same SHA1 multiple times, once per uniquely named branch. Can you be more specific about the functionality that your user requested? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-31802) Allow TFS Plugin to use Global Credentials
Title: Message Title Olivier Dagenais resolved as Duplicate Jenkins / JENKINS-31802 Allow TFS Plugin to use Global Credentials Change By: Olivier Dagenais Status: Open Resolved Assignee: redsolo Sunil Fernandes Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-31803) Workflow support for TFS plugin
Title: Message Title Olivier Dagenais assigned an issue to Olivier Dagenais Jenkins / JENKINS-31803 Workflow support for TFS plugin Change By: Olivier Dagenais Assignee: redsolo Olivier Dagenais Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-32719) Ability to load properties from a file
Title: Message Title Christopher Simons created an issue Jenkins / JENKINS-32719 Ability to load properties from a file Issue Type: New Feature Assignee: Unassigned Components: jacoco-plugin Created: 02/Feb/16 3:13 AM Priority: Minor Reporter: Christopher Simons Migrated from GitHub Issue #52; original description appears below, verbatim: Currently the JaCoCo Jenkins plugin has 5 UI fields to set JaCoCo properties: exec files, class files, source files, inclusions. and exclusions. This causes an issue for us because it does not permit the use of dynamically generated inclusion/exclusion files and has overhead of maintaining job settings. It would be nice if there was an option to import properties from a file. Add Comment
[JIRA] [workflow-plugin] (JENKINS-32146) ArtifactArchiver does not mark step as failing
Title: Message Title Jesse Glick commented on JENKINS-32146 Re: ArtifactArchiver does not mark step as failing The ball color in Pipeline Steps for the last step does not reflect overall build status. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32146) Last step misleadingly marked as blue even though build status is FAILURE
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32146 Last step misleadingly marked as blue even though build status is FAILURE Change By: Jesse Glick Summary: ArtifactArchiver does not mark Last step misleadingly marked as failing blue even though build status is FAILURE Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Murali Phani commented on JENKINS-32588 Re: Unable to launch linux slaves using ec2 plugin using Eucalyptus This one works fine . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32545) failFast has no effect when withCredentials is used
Title: Message Title Jesse Glick commented on JENKINS-32545 Re: failFast has no effect when withCredentials is used No idea offhand, would have to see if reproducible in a functional test. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-32552) Multibranch project git branch checkout
Title: Message Title Jesse Glick commented on JENKINS-32552 Re: Multibranch project git branch checkout …for which you need JENKINS-31924. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-32552) Multibranch project git branch checkout
Title: Message Title Jesse Glick resolved as Not A Defect For whatever reason, the Git plugin checks out branch heads in detached mode. You can override this behavior with an extension. Jenkins / JENKINS-32552 Multibranch project git branch checkout Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32192) Step termination link fails silently when site accessed by short name
Title: Message Title Jesse Glick commented on JENKINS-32192 Re: Step termination link fails silently when site accessed by short name A warning gets printed to the Jenkins log but it should probably be shown in the build log. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32192) Hyperlinks quietly fail when JenkinsLocationConfiguration incorrect
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32192 Hyperlinks quietly fail when JenkinsLocationConfiguration incorrect Change By: Jesse Glick Summary: Step termination link fails silently Hyperlinks quietly fail when site accessed by short name JenkinsLocationConfiguration incorrect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-plugin] (JENKINS-32551) Pipeline script from SCM: ClearCase not available
Title: Message Title Jesse Glick assigned an issue to Praqma Support There are at least three ClearCase SCM plugins; I am not sure which you are using. Whichever it is, it would need to be updated to support Pipeline. Jenkins / JENKINS-32551 Pipeline script from SCM: ClearCase not available Change By: Jesse Glick Issue Type: Bug New Feature Component/s: clearcase-plugin Component/s: workflow-plugin Priority: Minor Major Labels: clearcase workflow Assignee: Jesse Glick Praqma Support Add Comment
[JIRA] [git-plugin] (JENKINS-32552) Multibranch project git branch checkout
Title: Message Title Jesse Glick assigned an issue to Mark Waite Jenkins / JENKINS-32552 Multibranch project git branch checkout Change By: Jesse Glick Component/s: git-plugin Component/s: workflow-plugin Assignee: Jesse Glick Mark Waite Labels: workflow Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26761) WorkflowJob.getSCMs throws NullPointerException from notifyCommit hooks after Jenkins Restart
Title: Message Title Jesse Glick commented on JENKINS-26761 Re: WorkflowJob.getSCMs throws NullPointerException from notifyCommit hooks after Jenkins Restart I suspect this is actually just one of many symptoms of JENKINS-22767 . If so, it should quietly disappear in 1.646+. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31769) sh steps on slaves randomly hang when complete
Title: Message Title Jesse Glick resolved as Cannot Reproduce I fixed a number of potentially related issues in 1.13. Jenkins / JENKINS-31769 sh steps on slaves randomly hang when complete Change By: Jesse Glick Status: In Progress Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Murali Phani commented on JENKINS-32588 Re: Unable to launch linux slaves using ec2 plugin using Eucalyptus But i have one issue (in 1.29 also same issue) "with only 'root' account i could able to launch instances .if i provide other LDAP account is not able to authenticate and launch instance. Remote FS root /root Remote user root Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32533) [pipeline multibranch] Job configuration more explicitly readonly?
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32533 [pipeline multibranch] Job configuration more explicitly readonly? Change By: Jesse Glick Labels: multibranch Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32533) [pipeline multibranch] Job configuration more explicitly readonly?
Title: Message Title Jesse Glick commented on JENKINS-32533 Re: [pipeline multibranch] Job configuration more explicitly readonly? View Configuration? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32159) Errors with DescribableHelper.Schema
Title: Message Title Jesse Glick commented on JENKINS-32159 Re: Errors with DescribableHelper.Schema parallel is a lost cause, needs to be handled specially. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32480) Continuous integration using Jenkins Workflow and Validated Merge
Title: Message Title Jesse Glick commented on JENKINS-32480 Re: Continuous integration using Jenkins Workflow and Validated Merge Which Validated Merge plugin? If you mean the CloudBees proprietary one, there is an internal RFE for this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32533) [pipeline multibranch] Job configuration more explicitly readonly?
Title: Message Title Jesse Glick commented on JENKINS-32533 Re: [pipeline multibranch] Job configuration more explicitly readonly? Really a core issue. Probably duplicate though I am unsure how to find the original issue if there is one. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-30744) multibranch issues if branch contains /
Title: Message Title Jesse Glick resolved as Fixed This issue is fixed. If there are problems with Windows bat steps that are related to particular characters, file them in the durable-task plugin with workflow label and link to this issue. Jenkins / JENKINS-30744 multibranch issues if branch contains / Change By: Jesse Glick Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32073) Scheduling of workflow "node" allocation needs some better controls.
Title: Message Title Jesse Glick commented on JENKINS-32073 Re: Scheduling of workflow "node" allocation needs some better controls. Probably solvable with the stage step, though I would need to see a self-contained demo to really evaluate. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32122) A List passed to a function is received as a String
Title: Message Title Jesse Glick commented on JENKINS-32122 Re: A List passed to a function is received as a String Probably same as JENKINS-32062 , try 1.13. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32122) A List passed to a function is received as a String
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-32122 A List passed to a function is received as a String Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32675) Pipeline Plugin: Adjusting the Visualization of Pipeline Steps
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-32675 Pipeline Plugin: Adjusting the Visualization of Pipeline Steps Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32343) User task list
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-32343 User task list Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32352) [WORKFLOW] Progress Bar when stash/unstashing files in Workflow
Title: Message Title Jesse Glick commented on JENKINS-32352 Re: [WORKFLOW] Progress Bar when stash/unstashing files in Workflow Jenkins has never had a progress bar for the basic artifact archival feature, so this is a more general issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task-plugin] (JENKINS-32701) Slashes in branch names cause 'bat' workflow task to hang
Title: Message Title
Jan Arend Jansen updated an issue
Jenkins / JENKINS-32701
Slashes in branch names cause 'bat' workflow task to hang
Change By:
Jan Arend Jansen
As first reported in JENKINS-30744 windows 'bat' workflow task hangs on the encoding of git branch names when these branches contain special characters (tested with gitflow naming convention that has '/' in the branch name).The encoded path seems to create problems on windows when using 'bat'.Any branch that has a slash in it for example ('feature/myfeature') will get an encoded path on windows like /feature%2Fmyfeature@script and /feature%2Fmyfeature.When I apply the following workflow in a multibranch job in a root file 'Jenkinsfile', Jenkins hangs forever on the bat command {code} node {stage 'Checkout'checkout scmstage 'Build'bat "echo 'test'"} {code| When I add this same script on the 'master' branch everything is fine.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task-plugin] (JENKINS-32701) Slashes in branch names cause 'bat' workflow task to hang
Title: Message Title
Jan Arend Jansen created an issue
Jenkins / JENKINS-32701
Slashes in branch names cause 'bat' workflow task to hang
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
durable-task-plugin
Created:
01/Feb/16 9:42 AM
Environment:
Windows 8.1 Jenkins 1.643 Workflow Plugin 1.12
Labels:
workflow
Priority:
Major
Reporter:
Jan Arend Jansen
As first reported in
JENKINS-30744
windows 'bat' workflow task hangs on the encoding of git branch names when these branches contain special characters (tested with gitflow naming convention that has '/' in the branch name).
The encoded path seems to create problems on windows when using 'bat'. Any branch that has a slash in it for example ('feature/myfeature') will get an encoded path on windows like /feature%2Fmyfeature@script and /feature%2Fmyfeature. When I apply the following workflow in a multibranch job in a root file
[JIRA] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Francis Upton commented on JENKINS-32588 Re: Unable to launch linux slaves using ec2 plugin using Eucalyptus The issue that you have with 1.29 about the root should be a separate JIRA since it happens in that version. This issue is only the problem introduced since 1.29. I looked at the log and there is little in it. I don't see any tracing of exceptions or anything. Do you have more information? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Murali Phani updated an issue Jenkins / JENKINS-32588 Unable to launch linux slaves using ec2 plugin using Eucalyptus Change By: Murali Phani Attachment: jenkins._1.32_1_30_2016.log Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32690) Cannot manually provision new slave if one already exists
Title: Message Title Ohad Basan commented on JENKINS-32690 Re: Cannot manually provision new slave if one already exists I am also hitting this issue and I have a different use case for it I have a workflow job that does stress tests with several works when the job runs it starts 10 slaves concurrently and then runs a another job once on each slave. I can't use this architecture since the latest change. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32533) [pipeline multibranch] Job configuration more explicitly readonly?
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-32533 [pipeline multibranch] Job configuration more explicitly readonly? Change By: Cyrille Le Clerc Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Murali Phani edited a comment on JENKINS-32588 Re: Unable to launch linux slaves using ec2 plugin using Eucalyptus It is having still same issue .Not able to launch instance .Attached log jenkins._1.32_1_30_2016.log Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Murali Phani updated an issue Jenkins / JENKINS-32588 Unable to launch linux slaves using ec2 plugin using Eucalyptus Change By: Murali Phani Attachment: jenkins._1.32_1_30_2016.log Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32690) Cannot manually provision new slave if one already exists
Title: Message Title Ohad Basan edited a comment on JENKINS-32690 Re: Cannot manually provision new slave if one already exists I am also hitting this issue and I have a different use case for itI have a workflow job that does stress tests with several works workers when the job runs it starts 10 slaves concurrently and then runs a another job once on each slave.I can't use this architecture since the latest change. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32122) A List passed to a function is received as a String
Title: Message Title Dean Birch commented on JENKINS-32122 Re: A List passed to a function is received as a String I can confirm it's resolved with 1.13. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-32642) Parameters are considered non-default in builds triggered by timer
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32642 Re: Parameters are considered non-default in builds triggered by timer Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/plugins/credentials/CredentialsParameterDefinition.java src/test/java/com/cloudbees/plugins/credentials/CredentialsParameterDefinitionTest.java http://jenkins-ci.org/commit/credentials-plugin/3b59fbb153384c05937a5fbf72e6e6b0792883ca Log: Merge pull request #40 from daniel-beck/ JENKINS-32642 [FIX JENKINS-32642] Consider default value to be the default Compare: https://github.com/jenkinsci/credentials-plugin/compare/5a528b27a262...3b59fbb15338 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-32642) Parameters are considered non-default in builds triggered by timer
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32642 Re: Parameters are considered non-default in builds triggered by timer Code changed in jenkins User: Daniel Beck Path: src/main/java/com/cloudbees/plugins/credentials/CredentialsParameterDefinition.java src/test/java/com/cloudbees/plugins/credentials/CredentialsParameterDefinitionTest.java http://jenkins-ci.org/commit/credentials-plugin/0c811af0765f3e31619528a95a1de0ec240f6915 Log: [FIX JENKINS-32642] Consider default value to be the default Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-32642) Parameters are considered non-default in builds triggered by timer
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-32642 Parameters are considered non-default in builds triggered by timer Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-30744) multibranch issues if branch contains /
Title: Message Title Jan Arend Jansen commented on JENKINS-30744 Re: multibranch issues if branch contains / Done Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task-plugin] (JENKINS-32701) Slashes in branch names cause 'bat' workflow task to hang
Title: Message Title
Jan Arend Jansen updated an issue
Jenkins / JENKINS-32701
Slashes in branch names cause 'bat' workflow task to hang
Change By:
Jan Arend Jansen
As first reported in JENKINS-30744 windows 'bat' workflow task hangs on the encoding of git branch names when these branches contain special characters (tested with gitflow naming convention that has '/' in the branch name).The encoded path seems to create problems on windows when using 'bat'.Any branch that has a slash in it for example ('feature/myfeature') will get an encoded path on windows like /feature%2Fmyfeature@script and /feature%2Fmyfeature.When I apply the following workflow in a multibranch job in a root file 'Jenkinsfile', Jenkins hangs forever on the bat command{code}node {stage 'Checkout'checkout scmstage 'Build'bat "echo 'test'"}{code | } When I add this same script on the 'master' branch everything is fine.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Murali Phani edited a comment on JENKINS-32588 Re: Unable to launch linux slaves using ec2 plugin using Eucalyptus sorry it is ,the new pluginis working fine.But it is taking too long to create instance.At least 5-10 mins for initiating instance launch About root account ,the only log appearing at console.I will attach log . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle-plugin] (JENKINS-27393) Workflow step for Gradle invocation
Title: Message Title Christopher Orr commented on JENKINS-27393 Re: Workflow step for Gradle invocation Jean-Francois Bibeau: I agree this would be nice to have. But just in case you didn't see already, arbitrary shell script stuff is supported, e.g. sh './gradlew assemble' Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Murali Phani updated an issue Jenkins / JENKINS-32588 Unable to launch linux slaves using ec2 plugin using Eucalyptus Change By: Murali Phani Comment: It is having still same issue .Not able to launch instance.Attached log jenkins._1.32_1_30_2016.log Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-31862) "Build Now" should trigger Perforce polling
Title: Message Title Paul Allen commented on JENKINS-31862 Re: "Build Now" should trigger Perforce polling Thank you for trying this out. I'll close the ticket when the change goes out in the next release. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [project-inheritance-plugin] (JENKINS-23993) Page load time of inheritance projects
Title: Message Title Emilio Escobar commented on JENKINS-23993 Re: Page load time of inheritance projects Hi Martin Schröder, after 1.5.3 with the add of copyAndSortParametersByName instead of sortParametersByName we are facing performance issues. Basically because every parameters inside inheritance jobs are evaluated every time a dashboard is rendered, or build history is rendered. Also there is a trigger? thats evaluate continuously thous parameters. This is really needed? It seems that there is a lack of performance here. Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32533) [pipeline multibranch] Job configuration more explicitly readonly?
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-32533 Re: [pipeline multibranch] Job configuration more explicitly readonly? [~jglick] this screen "View Configuration" uses read/write html form elements instead of readonly elements.!screenshot-1.png |thumbnail ! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32533) [pipeline multibranch] Job configuration more explicitly readonly?
Title: Message Title Cyrille Le Clerc commented on JENKINS-32533 Re: [pipeline multibranch] Job configuration more explicitly readonly? Jesse Glick this screen "View Configuration" uses read/write html form elements instead of readonly elements. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer-plugin] (JENKINS-32686) Limit Scan by Job Label, Job Type, Name Etc.
Title: Message Title Tomas Westling commented on JENKINS-32686 Re: Limit Scan by Job Label, Job Type, Name Etc. I assume that the main driver for this idea is to spend less time and resources on scanning? Sounds like a good idea and I agree, the obvious place to start is with the easy implementations e.g. job name. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Murali Phani edited a comment on JENKINS-32588 Re: Unable to launch linux slaves using ec2 plugin using Eucalyptus This one works fine It is having still same issue . Not able to launch instance Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [metrics-plugin] (JENKINS-32695) Result from health checks are lost when more than 3 run at the same time
Title: Message Title Carlos Sanchez commented on JENKINS-32695 Re: Result from health checks are lost when more than 3 run at the same time https://github.com/jenkinsci/metrics-plugin/pull/18 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [metrics-plugin] (JENKINS-32696) healthcheck API endpoint causes a new run of health checks instead of reusing previous values
Title: Message Title Carlos Sanchez commented on JENKINS-32696 Re: healthcheck API endpoint causes a new run of health checks instead of reusing previous values https://github.com/jenkinsci/metrics-plugin/pull/19 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Murali Phani commented on JENKINS-32588 Re: Unable to launch linux slaves using ec2 plugin using Eucalyptus sorry it is working fine.But it is taking too long to create instance.At least 5-10 mins for initiating instance launch Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker] (JENKINS-32702) Using Env variable on Build/Publish docker container
Title: Message Title sébastien glon created an issue Jenkins / JENKINS-32702 Using Env variable on Build/Publish docker container Issue Type: Bug Assignee: Nicolas De Loof Components: docker, docker-plugin Created: 01/Feb/16 11:02 AM Priority: Critical Reporter: sébastien glon I have defined build param IMAGE; On "Directory for Dockerfile", i want to set ./library/$IMAGE But $Image is not resolved I have this error: Docker Build: building image at path /home/jenkins/workspace/BuildLabsService/library/$IMAGE ERROR: Build step failed with exception Jenkins 1.625.3 Docker plugin 0.16.0 Add Comment
[JIRA] [analysis-core-plugin] (JENKINS-31202) Trend Graphs are not shown in Job view for Workflow builds
Title: Message Title Antonio Muñiz commented on JENKINS-31202 Re: Trend Graphs are not shown in Job view for Workflow builds Might this be connected with JENKINS-31926 ? No, it's unrelated. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-container-registry-auth-plugin] (JENKINS-32700) 403 Forbidden
Title: Message Title James Green created an issue Jenkins / JENKINS-32700 403 Forbidden Issue Type: Bug Assignee: Wei Z Components: google-container-registry-auth-plugin Created: 01/Feb/16 9:16 AM Environment: jenkins:1.642.1 (master only) within a Docker 1.9.1 container Google Container Registry Auth Plugin:0.3 Google OAuth Credentials plugin:0.4 Priority: Critical Reporter: James Green I tried using both JSON and p12 flavours but both result in the following failure: [workspace] $ docker tag --force=true 2815f91921d7 eu.gcr.io/project-id/reporting-server:latest [workspace] $ docker inspect 2815f91921d7 [workspace] $ docker push eu.gcr.io/project-id/reporting-server:12 The push refers to a repository [eu.gcr.io/project-id/reporting-server] (len: 1) 2815f91921d7: Preparing Post https://eu.gcr.io/v2/project-id/reporting-server/blobs/uploads/: token auth attempt for registry: https://eu.gcr.io/v2/token?account=_token=repository%3Aproject-id%2Freporting-server%3Apush%2Cpull=eu.gcr.io request failed with status: 403 Forbidden Build step 'Docker Build and Publish' marked build as failure Sadly it is not clear precisely what has failed. The user that created the token successfully pushed the image manually using the gcloud tool so there was no permission
[JIRA] [core] (JENKINS-25930) Race condition creating build links during concurrent builds causes build failures
Title: Message Title Kenneth Baltrinic commented on JENKINS-25930 Re: Race condition creating build links during concurrent builds causes build failures Not sure if it is really the mutli-job plugin or just the ability to start the jobs really closely together. We are experiencing this and do no have the multi-job plugin installed. In stead we use the build-flow plugin. Our use case is that we kick of multiple jobs in parallel using the parallel command in the build-flow dsl. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32480) Continuous integration using Jenkins Workflow and Validated Merge
Title: Message Title Jason Swager commented on JENKINS-32480 Re: Continuous integration using Jenkins Workflow and Validated Merge Ran into the same issue and have the same question. Just finished converting some non-validated merge pipelines to Workflow/Pipeline and their teams are highly impressed at the results. Now the Validated Merge pipeline teams are drooling to have the same coolness... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21977) "java.io.IOException: Failed to clean up temp dirs" because of "secret.key"
Title: Message Title SCM/JIRA link daemon commented on JENKINS-21977 Re: "java.io.IOException: Failed to clean up temp dirs" because of "secret.key" Code changed in jenkins User: Nicolas BACOT Path: pom.xml http://jenkins-ci.org/commit/mattermost-plugin/43909e6e1161b2964e9235e86f7ee6fdd1943480 Log: Align with Jenkins 1.579 to include fix JENKINS-21977 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-20217) Too many PingThread's
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-20217 Too many PingThread's Change By: Jesse Glick Labels: performance remoting Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-32705) jenkins-cli.jar should not use PWD for temporary files
Title: Message Title Heikki Hokkanen created an issue Jenkins / JENKINS-32705 jenkins-cli.jar should not use PWD for temporary files Issue Type: Bug Assignee: Unassigned Components: cli Created: 01/Feb/16 1:35 PM Environment: 1.646 Priority: Major Reporter: Heikki Hokkanen Latest jenkins-cli.jar uses present working directory for temporary files when installing plugins, exploding spectacularly when a directory with the plugin name already exists. To reproduce, run: $ mkdir job-dsl $ java -jar /opt/jenkins-cli.jar -s http://localhost:8080/ install-plugin job-dsl Installing a plugin from local file: job-dsl Unexpected exception occurred while performing install-plugin command! java.io.IOException: Failed to copy job-dsl to /var/lib/jenkins/plugins/job-dsl.jpi at hudson.FilePath.copyTo(FilePath.java:1990) at hudson.cli.InstallPluginCommand.run(InstallPluginCommand.java:85) at hudson.cli.CLICommand.main(CLICommand.java:238) at hudson.cli.CliManagerImpl.main(CliManagerImpl.java:92) Caused by: java.io.FileNotFoundException: job-dsl (Is a directory)
[JIRA] [remoting] (JENKINS-27035) Request/response statistics
Title: Message Title Jesse Glick commented on JENKINS-27035 Re: Request/response statistics Wireshark plugin or other detailed diagnostics would be good too. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [neoload-jenkins] (JENKINS-32706) Neoload test result broken links
Title: Message Title JP Gamby created an issue Jenkins / JENKINS-32706 Neoload test result broken links Issue Type: Bug Assignee: Unassigned Components: neoload-jenkins Created: 01/Feb/16 2:04 PM Environment: Jenkins ver. 1.644 with NeoLoad Plugin 1.0.1 Labels: plugin neoload Priority: Minor Reporter: JP Gamby Most of my Neoload test report links are broken ... I get the following message when I click on Performance Result link: A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace
[JIRA] [description-setter-plugin] (JENKINS-11349) Project description field with a long text renders configuration page unusable
Title: Message Title Shaun Reich edited a comment on JENKINS-11349 Re: Project description field with a long text renders configuration page unusable other this is a dup of JENKINS-29632that issue is more generic, though created after this -- . this bug doesn't apply to just the description setter plugin, or the desc field. it applies to most every field in job settings Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-20217) Too many PingThread's
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-20217 Too many PingThread's Change By: Jesse Glick Component/s: remoting Component/s: core Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32480) Continuous integration using Jenkins Workflow and Validated Merge
Title: Message Title JT Chu commented on JENKINS-32480 Re: Continuous integration using Jenkins Workflow and Validated Merge Jesse Glick Yes, Validated Merge plugin. Any estimated time for this RFE delivery? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-agent-plugin] (JENKINS-32704) Command line ssh-add does not work
Title: Message Title Michael Rumpf created an issue Jenkins / JENKINS-32704 Command line ssh-add does not work Issue Type: Bug Assignee: Unassigned Components: ssh-agent-plugin Created: 01/Feb/16 12:56 PM Priority: Major Reporter: Michael Rumpf I have the ssh-agent-plugin configured for one of my Jenkins jobs. The SSH connection uses a jump server to get to a target machine. | Jenkins Build Node | -A-> | Jump Server | -B-> | Target Machine | A) The key for the "deploy" user on the jump server has been added to the Jenkins configuration and is added to the SSH Agent as part of the job. B) The user on the target server is selected from a drop-down box in the parameterized job form, which is displayed when clicking on the link "Build with Paramaters". For this to work a Bash shell script is started which adds the private key for the selected environment to the SSH agent by running ssh-add seckeys/dev. The connection to the SSH agent is established by the Unix socket, as defined by SSH_AUTH_SOCK=/tmp/jenkins421145548058133.jnr. I run ssh-add -l afterwards to validate that the key has been added: 4096
