[JIRA] [git-client-plugin] (JENKINS-20879) SSH Credentials (private key with passphrase) do not work
Title: Message Title Alberto Gallardo commented on JENKINS-20879 Re: SSH Credentials (private key with passphrase) do not work I'm the reporter of JENKINS-32834 . I'm using a file on Jenkins as private key. See . Credentials work independently of configured username. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-32732) Using unix server every time build fail through SVN
Title: Message Title Pardeep Kumar commented on JENKINS-32732 Re: Using unix server every time build fail through SVN i have an issue on Jenkins . when i create a checkout build file through SVN , then mentioned error occur . i recently installed jenkins on my unix system through deployed WAR file. java home path configured. but cant be able to svn checkout build file. please help on this, may be i am something missing, Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-20879) SSH Credentials (private key with passphrase) do not work
Title: Message Title Alberto Gallardo updated an issue Jenkins / JENKINS-20879 SSH Credentials (private key with passphrase) do not work Change By: Alberto Gallardo Attachment: CredentialsConfig-fileOnJenkins.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] [mailer-plugin] (JENKINS-32872) javax.mail.AuthenticationFailedException
Title: Message Title farhan sumbul created an issue Jenkins / JENKINS-32872 javax.mail.AuthenticationFailedException Issue Type: Bug Assignee: Unassigned Components: mailer-plugin Created: 10/Feb/16 7:06 AM Environment: Windows Priority: Minor Reporter: farhan sumbul javax.servlet.ServletException: javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) 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
[JIRA] [git-client-plugin] (JENKINS-32834) Failed to connect to repository with password-protected ssh key
Title: Message Title Alberto Gallardo commented on JENKINS-32834 Re: Failed to connect to repository with password-protected ssh key If it helps, I have the 'SSH Credentials Plugin' v. 1.11 installed. 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] [extra-columns-plugin] (JENKINS-32871) add environment variable view
Title: Message Title mor lajb created an issue Jenkins / JENKINS-32871 add environment variable view Issue Type: New Feature Assignee: Fred G Components: extra-columns-plugin Created: 10/Feb/16 6:55 AM Priority: Minor Reporter: mor lajb it will be great to have the ability to add 1 or several environment variables Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [git-client-plugin] (JENKINS-32834) Failed to connect to repository with password-protected ssh key
Title: Message Title Alberto Gallardo commented on JENKINS-32834 Re: Failed to connect to repository with password-protected ssh key I'm still perplexed how you make it work in your environment. Re-reading my posts, I'm afraid I have confused you a bit. I'm sorry. "I'm using the ssh-agent" as in "I have installed it" (it's a GitHub Pull Request Builder dependency). The problem is that I'm not that familiarized with each plugin responsibility, and I assumed that it was a jenkins core component already being used. I added the ssh-agent plugin to my Jenkins installation, modified the job I had previously defined to use a passphrase protected credential for its git repository, then selected that same passphrase protected credential for use by the ssh-agent in the "Build Environment" section of the job configuration. I then encountered what appears to be JENKINS-32120 (ssh-agent fails when using a passphrase protected key). That confirms my findings in my previous post. Thanks! I'm even more perplexed because your config.xml does not include the ssh-agent build wrapper that I was expecting. Are you sure that is the job configuration file of one of the jobs using ssh-agent? My fault making you believe I was using it: no, I'm not using it in this job. I have now re-tested, removing the "ssh agent" plugin (and consequently, the "github pull request builder" plugin). The problem is always reproducible, and I can confirm that the commit revert still works (built git-client git-client-1.19.4 from github). Unfortunatelly, my jenkins doesn't see the new 1.19.4 release yet. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [git-client-plugin] (JENKINS-20879) SSH Credentials (private key with passphrase) do not work
Title: Message Title Mark Waite edited a comment on JENKINS-20879 Re: SSH Credentials (private key with passphrase) do not work My attempts to create a case which will use a passphrase protected credential have consistently failed with command line git . I still don't know how others are able to use passphrase protected private keys with command line git, but I am not. I add the private key as a credential, I enter the passphrase into the credential, and it does not authenticate. I even attempted installing the ssh-agent plugin and then tried enabling it for one job. Still no luck.JENKINS-32834 includes a report from one user that a change made in git client plugin 1.19.3 broke passphrase handling for him (BatchMode=yes was added to the ssh arguments) . I reverted the problem change and released it as git client plugin 1.19.4. There definitely are users who are able to use passphrase protected rsa private keys. I'm not one of them.I was able to create a job which uses a password protected private key so long as I use JGit as the git implementation. The same job definition fails when I use command line git. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-20879) SSH Credentials (private key with passphrase) do not work
Title: Message Title Mark Waite edited a comment on JENKINS-20879 Re: SSH Credentials (private key with passphrase) do not work My attempts to create a case which will use a passphrase protected credential have consistently failed. I still don't know how others are able to use passphrase protected private keys but I am not. I add the private key as a credential, I enter the passphrase into the credential, and it does not authenticate. I even attempted installing the ssh-agent plugin and then tried enabling it for one job. Still no luck.JENKINS-32834 includes a report from one user that a change made in git client plugin 1.19.3 broke passphrase handling for him. I reverted the problem change and released it as git client plugin 1.19.4. There definitely are users who are able to use passphrase protected rsa private keys. I'm not one of them. I was able to create a job which uses a password protected private key so long as I use JGit as the git implementation. The same job definition fails when I use command line git. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-20879) SSH Credentials (private key with passphrase) do not work
Title: Message Title Mark Waite commented on JENKINS-20879 Re: SSH Credentials (private key with passphrase) do not work My attempts to create a case which will use a passphrase protected credential have consistently failed. I still don't know how others are able to use passphrase protected private keys but I am not. I add the private key as a credential, I enter the passphrase into the credential, and it does not authenticate. I even attempted installing the ssh-agent plugin and then tried enabling it for one job. Still no luck. JENKINS-32834 includes a report from one user that a change made in git client plugin 1.19.3 broke passphrase handling for him. I reverted the problem change and released it as git client plugin 1.19.4. There definitely are users who are able to use passphrase protected rsa private keys. I'm not one of them. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-23415) 2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading
Title: Message Title Mark Waite commented on JENKINS-23415 Re: 2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading Roman Revyakin you might consider adding the optional behavior for a reference repository, then place a bare copy of your 850 MB repository on each of the slaves in a known location. The clone will then create pointers to the reference repository, rather than downloading a fresh copy of the repository each time. 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] [join-plugin] (JENKINS-32604) join-pluging missing licensing information
Title: Message Title mdonohue resolved as Fixed Jenkins / JENKINS-32604 join-pluging missing licensing information Change By: mdonohue 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] [join-plugin] (JENKINS-32604) join-pluging missing licensing information
Title: Message Title mdonohue commented on JENKINS-32604 Re: join-pluging missing licensing information Saying something is "unusable" is a bit extreme. I added an explicit MIT license to the pom.xml file just now. 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] [join-plugin] (JENKINS-32604) join-pluging missing licensing information
Title: Message Title mdonohue reopened an issue Jenkins / JENKINS-32604 join-pluging missing licensing information Change By: mdonohue Resolution: Won't Fix Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-32834) Failed to connect to repository with password-protected ssh key
Title: Message Title Mark Waite resolved as Fixed Fixed in git client plugin 1.19.4, released 9 Feb 2016 Jenkins / JENKINS-32834 Failed to connect to repository with password-protected ssh key Change By: Mark Waite Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-32870) Missing pom.xml dependency for 'matrix-project'
Title: Message Title Antek Baranski closed an issue as Not A Defect Jenkins / JENKINS-32870 Missing pom.xml dependency for 'matrix-project' Change By: Antek Baranski Status: Open Closed 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] [join-plugin] (JENKINS-22348) Join Plugin: intermittent NullPointerException in child project when all downstream projects complete
Title: Message Title mdonohue resolved as Fixed Jenkins / JENKINS-22348 Join Plugin: intermittent NullPointerException in child project when all downstream projects complete Change By: mdonohue Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [join-plugin] (JENKINS-22348) Join Plugin: intermittent NullPointerException in child project when all downstream projects complete
Title: Message Title mdonohue commented on JENKINS-22348 Re: Join Plugin: intermittent NullPointerException in child project when all downstream projects complete the suggested fix is in the 1.19 release of the join plugin 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-32870) Missing pom.xml dependency for 'matrix-project'
Title: Message Title Antek Baranski updated an issue Jenkins / JENKINS-32870 Missing pom.xml dependency for 'matrix-project' Change By: Antek Baranski The pom.xml is missing a dependency for 'matrix-project', build will fail on a clean system if this is not present in the pom.xml. org.jenkins-ci.plugins matrix-project 1.6 ` [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5:compile (default-compile) on project p4: Compilation failure: Compilation failure:[ERROR] /Users//GitHub/p4-jenkins/src/main/java/org/jenkinsci/plugins/p4/matrix/MatrixOptions.java:[4,20] error: package hudson.matrix does not exist[ERROR] /Users//GitHub/p4-jenkins/src/main/java/org/jenkinsci/plugins/p4/matrix/MatrixOptions.java:[5,20] error: package hudson.matrix does not exist[ERROR] /Users//GitHub/p4-jenkins/src/main/java/org/jenkinsci/plugins/p4/matrix/MatrixOptions.java:[6,32] error: package hudson.matrix.MatrixBuild does not exist[ERROR] /Users//GitHub/p4-jenkins/src/main/java/org/jenkinsci/plugins/p4/matrix/MatrixOptions.java:[13,35] error: cannot find symbol[ERROR] symbol: class MatrixExecutionStrategy[ERROR] /Users//GitHub/p4-jenkins/src/main/java/org/jenkinsci/plugins/p4/matrix/MatrixOptions.java:[28,19] error: cannot find symbol[ERROR] symbol: class MatrixBuildExecution[ERROR] location: class MatrixOptions[ERROR] /Users//GitHub/p4-jenkins/src/main/java/org/jenkinsci/plugins/p4/matrix/MatrixOptions.java:[34,3] error: cannot find symbol ` Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received thi
[JIRA] [p4-plugin] (JENKINS-32870) Missing pom.xml dependency for 'matrix-project'
Title: Message Title Antek Baranski assigned an issue to Antek Baranski Jenkins / JENKINS-32870 Missing pom.xml dependency for 'matrix-project' Change By: Antek Baranski Assignee: Antek Baranski 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-32870) Missing pom.xml dependency for 'matrix-project'
Title: Message Title Antek Baranski created an issue Jenkins / JENKINS-32870 Missing pom.xml dependency for 'matrix-project' Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 10/Feb/16 4:07 AM Priority: Minor Reporter: Antek Baranski The pom.xml is missing a dependency for 'matrix-project', build will fail on a clean system if this is not present in the pom.xml. org.jenkins-ci.plugins matrix-project 1.6 `[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5:compile (default-compile) on project p4: Compilation failure: Compilation failure: [ERROR] /Users//GitHub/p4-jenkins/src/main/java/org/jenkinsci/plugins/p4/matrix/MatrixOptions.java:[4,20] error: package hudson.matrix does not exist [ERROR] /Users//GitHub/p4-jenkins/src/main/java/org/jenkinsci/plugins/p4/matrix/MatrixOptions.java:[5,20] error: package hudson.matrix does not exist [ERROR] /Users//GitHub/p4-jenkins/src/main/java/org/jenkinsci/plugins/p4/matrix/MatrixOptions.java:[6,32] error: package hudson.matrix.MatrixBuild does not exist [ERROR] /Users//GitHub/p4-jenkins/src/main/java/org/jenkinsci/plugins/p4/matrix/MatrixOptions.java:[13,35] error: cannot find symbol [ERROR] symbol: class MatrixExecutionStrategy [ERROR] /Users//GitHub/p4-jenkins/src/main/java/org/jenkinsci/plugins/p4/matrix/MatrixOptions.java:[28,19] error: cannot find symbol [ERROR] symbol: class MatrixBuildExecution [ERROR] location: class MatrixOptions [ERROR] /Users//GitHub/p4-jenkins/src/main/java/org/jenkinsci/plugins/p4/matrix/MatrixOptions.java:[34,3] error: cannot find symbol
[JIRA] [git-plugin] (JENKINS-17346) git project building twice every time new change committed
Title: Message Title Roman Revyakin edited a comment on JENKINS-17346 Re: git project building twice every time new change committed Seems to be still happening on Jenkins ver. 1.609.3 - although not consistently: I've got 2 separate Jenkins instances running the same Jenkins versions and setup identically, running on 2 different machines and tracking 2 different private GitHub repositories: one of the Jenkins will always trigger the build twice for the same changset, exactly as described, another one triggers the builds properly - once per each changset changes . I've just noticed the link to another issue above (https://issues.jenkins-ci.org/browse/JENKINS-23415) and realised that it might be well related to the fact that one of the repositories that is causing this troubles is a large one (>850 Mb), and is wiped out every time prior to the build is triggered, so it's a new git clone every time the build is happening. And according to the linked issue the duplicate build happens whenever the git clone for the first one is still running. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-23415) 2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading
Title: Message Title Roman Revyakin commented on JENKINS-23415 Re: 2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading Seems to be still happening on Jenkins ver. 1.609.3 - and I am running git-client-plugin 1.19.0 and specify the branches as "ref/heads/", and I use polling mechanism to trigger the build of a private repository hosted on GitHub (as GitHub push notifications do not work for some reason). Seems to be really caused by the fact that the repository is a really large one ( >850 Mb) and we need to wipe out the workspace prior to the new checkout - so it is essentially a new git clone every time the job is triggered. 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-17346) git project building twice every time new change committed
Title: Message Title Roman Revyakin commented on JENKINS-17346 Re: git project building twice every time new change committed Seems to be still happening on Jenkins ver. 1.609.3 - although not consistently: I've got 2 separate Jenkins instances running the same Jenkins versions and setup identically, running on 2 different machines and tracking 2 different private GitHub repositories: one of the Jenkins will always trigger the build twice for the same changset, exactly as described, another one triggers the builds properly - once per each changset. 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] [artifactory-plugin] (JENKINS-32869) Artifactory plugin creates directories instead of uploading files
Title: Message Title Nickolay Rumyantsev created an issue Jenkins / JENKINS-32869 Artifactory plugin creates directories instead of uploading files Issue Type: Bug Assignee: yossis Components: artifactory-plugin Created: 10/Feb/16 2:28 AM Environment: Jenkins 1.625.3 Artifactory plugin 2.4.7 (2.2.4 too) Artifactory OSS (latest docker image: 29d2cd2e846a) Priority: Blocker Reporter: Nickolay Rumyantsev My job builds some tgz and rpms. I configured it to use Artifactory plugin as a Generic deployer to my test Artifactory instance. During the execution plugin reports in the log that it found the artifacts and deployed them successfully. But it ran too fast so I check the artifacts on the Artifactory page. There I saw that instead of files there were directories with the same names! Publishing rules are the following (yes, there are version-named directories as the dest): /jenkins/workspace/BuildJob/RPMS/x86_64/1.5.0.0-155.COREOS.tgz=>com/foo/bar/coreos/1.5.0.0-155.COREOS /jenkins/workspace/BuildJob/RPMS/x86_64/1.5.0.0-155.RHEL.rpm=>com/foo/bar/rhel7/1.5.0.0-155.RHEL I also tried appending the filenam
[JIRA] [metrics-plugin] (JENKINS-32868) Metrics Plugin holds references to Destroyed Build Node objects
Title: Message Title Maxfield Stewart created an issue Jenkins / JENKINS-32868 Metrics Plugin holds references to Destroyed Build Node objects Issue Type: Bug Assignee: Unassigned Attachments: detailpic.PNG, heappic.PNG Components: metrics-plugin Created: 10/Feb/16 1:25 AM Environment: 1.617 (Jenkins) Docker Plugin (0.15) Metrics Plugin (3.1.2.2) Metrics Graphite Reporting Plugin (3.0.0 ) Labels: plugin jenkins slave memory-leak Priority: Minor Reporter: Maxfield Stewart I'm attaching some screenshots from MAT for heap analysis. Not %100 positive but it appears the Metrics plugin holds data and references for Build Slaves that have been destroyed and no longer exist.
[JIRA] [core] (JENKINS-27268) "dumb" slave?
Title: Message Title Christopher Orr commented on JENKINS-27268 Re: "dumb" slave? I like the "agent" terminology (as I wrote on GitHub), and it's also what a number of other CI servers seem to use. Microsoft Team Foundation Server supposedly uses (or used to?) controller/agent — I think "controller" or "manager" would be a reasonable replacement, if we wanted to also replace "master". 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-32793) POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version
Title: Message Title Rami Abughazaleh commented on JENKINS-32793 Re: POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version Thank 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] [build-name-setter-plugin] (JENKINS-32867) Make build-name-setter-plugin compatible with Pipeline / Workflow
Title: Message Title Manuel Jesús Recena Soto updated an issue Jenkins / JENKINS-32867 Make build-name-setter-plugin compatible with Pipeline / Workflow Change By: Manuel Jesús Recena Soto Add support for pipeline / workflow Pipeline. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-name-setter-plugin] (JENKINS-32867) Make build-name-setter-plugin compatible with Pipeline / Workflow
Title: Message Title Manuel Jesús Recena Soto updated an issue Jenkins / JENKINS-32867 Make build-name-setter-plugin compatible with Pipeline / Workflow Change By: Manuel Jesús Recena Soto Labels: pipeline Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32793) POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version
Title: Message Title Daniel Beck commented on JENKINS-32793 Re: POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version Jenkins update sites have no metadata on obsolete releases, so this isn't quite this easy. Jenkins CLI has a command to install/update a plugin that takes a URL as argument. 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] [zephyr-for-jira-test-management-plugin] (JENKINS-32801) Pipeline build step for Zephyr for Jira
Title: Message Title Ivan Fernandez Calvo reopened an issue Jenkins / JENKINS-32801 Pipeline build step for Zephyr for Jira Change By: Ivan Fernandez Calvo Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [zephyr-for-jira-test-management-plugin] (JENKINS-32801) Pipeline build step for Zephyr for Jira
Title: Message Title Ivan Fernandez Calvo updated JENKINS-32801 Jenkins / JENKINS-32801 Pipeline build step for Zephyr for Jira Change By: Ivan Fernandez Calvo Status: Reopened Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-32834) Failed to connect to repository with password-protected ssh key
Title: Message Title Mark Waite edited a comment on JENKINS-32834 Re: Failed to connect to repository with password-protected ssh key I'm still perplexed how you make it work in your environment.I added the ssh-agent plugin to my Jenkins installation, modified the job I had previously defined to use a passphrase protected credential for its git repository, then selected that same passphrase protected credential for use by the ssh-agent in the "*Build Environment*" section of the job configuration. I then encountered what appears to be JENKINS-32120 (ssh-agent fails when using a passphrase protected key). I'm even more perplexed because your config.xml does not include the ssh-agent build wrapper that I was expecting. Are you sure that is the job configuration file of one of the jobs using ssh-agent? 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] [zephyr-for-jira-test-management-plugin] (JENKINS-32801) Pipeline build step for Zephyr for Jira
Title: Message Title Ivan Fernandez Calvo resolved as Fixed Jenkins / JENKINS-32801 Pipeline build step for Zephyr for Jira Change By: Ivan Fernandez Calvo Status: Open Resolved Assignee: Jesse Glick Ivan Fernandez Calvo 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] [zephyr-for-jira-test-management-plugin] (JENKINS-32801) Pipeline build step for Zephyr for Jira
Title: Message Title
Ivan Fernandez Calvo commented on JENKINS-32801
Re: Pipeline build step for Zephyr for Jira
I add compatibility with Pipeline plugin, now you can run a step of Zephyr fro jita test management plugin.
node { git url: 'file:Users/inifc/Documents/workspace/statusCheck' def mvnHome = tool 'maven3' sh "$ {mvnHome}
/bin/mvn clean package" step([$class: 'JUnitResultArchiver', testResults: '**/target/surefire-reports/TEST-*.xml']) step([$class: 'ZfjReporter',serverAddress: 'http://127.0.0.1:9090',projectKey:'PRJ',versionKey:'1',cycleKey:'CreateNewCycle',cycleDuration:'30 days',cyclePrefix:'']) }
https://github.com/jenkinsci/zephyr-for-jira-test-management-plugin/pull/2
quoted text
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] [zephyr-for-jira-test-management-plugin] (JENKINS-32801) Pipeline build step for Zephyr for Jira
Title: Message Title
Ivan Fernandez Calvo edited a comment on JENKINS-32801
Re: Pipeline build step for Zephyr for Jira
I add compatibility with Pipeline plugin, now you can run a step of Zephyr fro jita test management plugin. {quote} node { git url: 'file:Users/inifc/Documents/workspace/statusCheck' def mvnHome = tool 'maven3' sh "${mvnHome}/bin/mvn clean package" step([$class: 'JUnitResultArchiver', testResults: '**/target/surefire-reports/TEST-*.xml']) step([$class: 'ZfjReporter',serverAddress: 'http://127.0.0.1:9090',projectKey:'PRJ',versionKey:'1',cycleKey:'CreateNewCycle',cycleDuration:'30 days',cyclePrefix:'']) } {quote} https://github.com/jenkinsci/zephyr-for-jira-test-management-plugin/pull/2 {quote}quoted text{quote}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-32834) Failed to connect to repository with password-protected ssh key
Title: Message Title Mark Waite commented on JENKINS-32834 Re: Failed to connect to repository with password-protected ssh key I'm still perplexed how you make it work in your environment. I added the ssh-agent plugin to my Jenkins installation, modified the job I had previously defined to use a passphrase protected credential for its git repository, then selected that same passphrase protected credential for use by the ssh-agent in the "Build Environment" section of the job configuration. I then encountered what appears to be JENKINS-32120 (ssh-agent fails when using a passphrase protected key). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-22909) Jenkins SSH connection to a Git server is not working using username/password
Title: Message Title Mark Waite stopped work on JENKINS-22909 Change By: Mark Waite Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-31025) git-plugin / credentials - unable to select a certificate credential (P12) to access a GIT repository
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-31025 git-plugin / credentials - unable to select a certificate credential (P12) to access a GIT repository Change By: Mark Waite Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-31464 git-client uses proxy from plugins section of jenkins Change By: Mark Waite Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-32712) Job with Git polling "succeeds" with "no changes" although the Git polling failed
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-32712 Job with Git polling "succeeds" with "no changes" although the Git polling failed Change By: Mark Waite Issue Type: Bug New Feature 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] [cucumber-testresult-plugin] (JENKINS-29328) NullPointerException parsing a Background section that has a Before hook.
Title: Message Title Antonio Tello commented on JENKINS-29328 Re: NullPointerException parsing a Background section that has a Before hook. I'm really glad someone has figured out what was causing this problem because I just started running into it a couple weeks ago and could not figure out what was causing it for the life of me. After comparing our feature files with your examples, this is the exact problem. Unfortunately locking cucumber to 2.0.0 is not feasible for us due to some of the post 2.0.0 functionality we use. I've taken to just putting the Background conditions in each scenario, which, while inconvenient, at least allows us to continue using the cucumber parsing plugin. +1 for a fix. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service
Title: Message Title Ryan Pavlik commented on JENKINS-20356 Re: Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service I may be experiencing this in what I reported in https://issues.jenkins-ci.org/browse/JENKINS-20941?focusedCommentId=247772&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-247772 There, I have a private github repo, with SSH credentials set, specified as g...@github.com:sensics/abcde.git , which I think cloned fine on its own. It has submodules specified, in the same format, for which the same credential should work, in the repo, and the additional submodule behaviors added to the config, but the "access rights" error as seen above occurs for the submodules. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Ryan Pavlik commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated Ah, thank you - it might be that one, though as I said it works fine with the main repo, it's just the submodules that it can't deal with. Since it seemed specific to submodules that's what I searched for so I ended up here, but I will follow that issue as well. Is there any information I can provide on my setup to help diagnose this? Windows 8.1 x64, standard git for windows (64-bit) installed with Chocolatey, git version 2.6.3.windows.1, running the latest (non-LTS) Jenkins installed as a service using the regular method IIRC. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Mark Waite commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated Ryan Pavlik I think you may be seeing JENKINS-20356 (Windows service doesn't work with private key credentials) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title
Ryan Pavlik edited a comment on JENKINS-20941
Re: Stored git credentials not used when submodule is updated
What I believe is the same problem is happening here, with a private github repo accessed over ssh, that have other private github repos (over ssh) as submodules. The experimental plugin did not help. The same SSH credential should be usable for all repos (the super-repo and the submodules), and it clones the main repo fine:{{using GIT_SSH to set credentials sensics-bot on github and gitlab}}before the main clone, but then the individual {{git.exe submodule update --init --recursive path/to/private/submodule}} calls fail (and are not preceded by a similar line mentioning GIT_SSH).This is on a Windows machine running the Jenkins server as a service (as "Local System"). My only limited workaround I was able to find was to launch a cmd prompt as the Local System account with {{psexec -i -s cmd.exe}} - see this info http://stackoverflow.com/a/78691/265522 , in the new window change to the home directory's .ssh dir with {{cd %USERPROFILE%\.ssh}}, and copy my ssh keys in {{copy c:\jenkins-server\id_rsa c:\jenkins-server\id_rsa.pub .}} That makes those keys the default to use by SSH, so it lets me complete the task, but it's still not using the stored/specified credentials, it's just that I only have one set of credentials I want this server to use.
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-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title
Kevin Yu edited a comment on JENKINS-23271
Re: Intermittent Invalid Object ID in remoting module
We started to see this issue the first time.We have a matrix job with 130 variants and the problem happened in post build when it's evaluating whether the current build status is success before triggering other things.{code:java} eb 09, 2016 7:12:00 AM org.jenkins_ci.plugins.run_condition.BuildStepRunner logEvaluateExceptionWARNING: Exception caught evaluating condition: [java.lang.IllegalStateException: Invalid object ID 901 883 iota= 902 884 ], action = [Fail the build] Build step 'Execute a set of scripts' changed build result java.lang.IllegalStateException: Invalid object ID 883 iota=884at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:386)at hudson.remoting.ExportTable.get(ExportTable.java:330)at hudson.remoting.Channel.getExportedObject(Channel.java:633)at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:599)at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:583)at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:542)at hudson.remoting.UserRequest.perform(UserRequest.java:120)at hudson.remoting.UserRequest.perform(UserRequest.java:48)at hudson.remoting.Request$2.run(Request.java:326)at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)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)at ..remote call to FAILURE jenkins-slave4(192.168.100.153)(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)at hudson.remoting.UserResponse.retrieve(UserRequest.java:220)at hudson.remoting.Channel.call(Channel.java:781)at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:250)at com.sun.proxy.$Proxy50.join(Unknown Source)at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:991)at hudson.Launcher$ProcStarter.join(Launcher.java:388)at org.jenkins_ci.plugins.run_condition.contributed.CommandInterperterCondition.runPerform(CommandInterperterCondition.java:89)at org.jenkins_ci.plugins.run_condition.BuildStepRunner$2.evaluate(BuildStepRunner.java:107)at org.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail.conditionalRun(BuildStepRunner.java:147)at org.jenkins_ci.plugins.run_condition.BuildStepRunner.perform(BuildStepRunner.java:105)at org.jenkinsci.plugins.conditionalbuildstep.ConditionalBuilder.perform(ConditionalBuilder.java:133)at org.jenkinsci.plugins.postbuildscript.PostBuildScript.processBuildSteps(PostBuildScript.java:204)at org.jenkinsci.plugins.postbuildscript.PostBuildScript.processScripts(PostBuildScript.java:143)at org.jenkinsci.plugins.postbuildscript.PostBuildScript._perform(PostBuildScript.java:105)at org.jenkinsci.plugins.postbuildscript.PostBuildScript.perform(PostBuildScript.java:82)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.matrix.MatrixRun.run(MatrixRun.java:146)at hudson.model.ResourceController.execute(ResourceController.java:98)at hudson.model.Executor.run(Executor.java:410)Caused by: java.lang.Exception: Object was recently deallocated#883
[JIRA] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Ryan Pavlik commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated What I believe is the same problem is happening here, with a private github repo accessed over ssh, that have other private github repos (over ssh) as submodules. The experimental plugin did not help. The same SSH credential should be usable for all repos (the super-repo and the submodules), and it clones the main repo fine: using GIT_SSH to set credentials sensics-bot on github and gitlab before the main clone, but then the individual git.exe submodule update --init --recursive path/to/private/submodule calls fail (and are not preceded by a similar line mentioning GIT_SSH). This is on a Windows machine running the Jenkins server as a service (as "Local System"). 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] [log-parser-plugin] (JENKINS-32866) Log Parser Plugin does not parse workflow console outputs
Title: Message Title
Jeff Burke updated an issue
Jenkins / JENKINS-32866
Log Parser Plugin does not parse workflow console outputs
Change By:
Jeff Burke
Versions:* Jenkins: 1.644* Workflow plugins: 1.12* Log Parser Plugin: 2.0Issue: I have the following workflow job:{code:java}node { step([$class: 'LogParserPublisher', parsingRulesPath: '/var/lib/jenkins/jenkins-rule-logparser', useProjectRule: false]) echo 'Error: oh no'}{code}and it produces the following console output:{noformat}Started by user anonymous[Workflow] Allocate node : StartRunning on master in /var/lib/jenkins/jobs/ntsvc-monitor-dev/workspace[Workflow] node {[Workflow] step[Workflow] echoError: oh noes[Workflow] } //node[Workflow] Allocate node : End[Workflow] End of WorkflowFinished: SUCCESS{noformat}The log parser config (/var/lib/jenkins/jenkins-rule-logparser) is:{noformat}error /Error/{noformat}The parsed log view shows only:{noformat}Started by user anonymous[Workflow] Allocate node : StartRunning on master in /var/lib/jenkins/jobs/ntsvc-monitor-dev/workspace[Workflow] node {{noformat}For a FreeStyle job, the same echo message and log parser rules, results in fully parsed log and the error message is detected/colored red. See attachments for views of parsed log screens. The Jenkins system log does not contain errors for the jobs or the Log Parse plugin... indeed, it contains success messages from the Log Parse plugin.
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.
T
[JIRA] [build-name-setter-plugin] (JENKINS-32867) Make build-name-setter-plugin compatible with Pipeline / Workflow
Title: Message Title Emilio Escobar created an issue Jenkins / JENKINS-32867 Make build-name-setter-plugin compatible with Pipeline / Workflow Issue Type: New Feature Assignee: Lev Mishin Components: build-name-setter-plugin Created: 09/Feb/16 9:23 PM Priority: Minor Reporter: Emilio Escobar Add support for pipeline / workflow Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [log-parser-plugin] (JENKINS-32866) Log Parser Plugin does not parse workflow console outputs
Title: Message Title Jeff Burke updated an issue Jenkins / JENKINS-32866 Log Parser Plugin does not parse workflow console outputs Screen shots of parse working and not working. Change By: Jeff Burke Attachment: parsed-freestyle.png Attachment: parsed-workflow.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] [log-parser-plugin] (JENKINS-9659) Parsed logs not created
Title: Message Title Jeff Burke updated an issue Jenkins / JENKINS-9659 Parsed logs not created Change By: Jeff Burke Attachment: parsed-workflow.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] [log-parser-plugin] (JENKINS-9659) Parsed logs not created
Title: Message Title Jeff Burke updated an issue Jenkins / JENKINS-9659 Parsed logs not created Change By: Jeff Burke Attachment: parsed-freestyle.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] [log-parser-plugin] (JENKINS-9659) Parsed logs not created
Title: Message Title Jeff Burke updated an issue Jenkins / JENKINS-9659 Parsed logs not created Change By: Jeff Burke Comment: Screenshots of parse log console view 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] [log-parser-plugin] (JENKINS-9659) Parsed logs not created
Title: Message Title Jeff Burke updated an issue Jenkins / JENKINS-9659 Parsed logs not created Screenshots of parse log console view Change By: Jeff Burke Attachment: parsed-freestyle.png Attachment: parsed-workflow.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] [log-parser-plugin] (JENKINS-32866) Log Parser Plugin does not parse workflow console outputs
Title: Message Title
Jeff Burke created an issue
Jenkins / JENKINS-32866
Log Parser Plugin does not parse workflow console outputs
Issue Type:
Bug
Assignee:
Manuel Jesús Recena Soto
Components:
log-parser-plugin
Created:
09/Feb/16 9:12 PM
Priority:
Minor
Reporter:
Jeff Burke
Versions:
Jenkins: 1.644
Workflow plugins: 1.12
Log Parser Plugin: 2.0
Issue: I have the following workflow job:
node {
step([$class: 'LogParserPublisher', parsingRulesPath: '/var/lib/jenkins/jenkins-rule-logparser', useProjectRule: false])
echo 'Error: oh no'
}
and it produces the following console output:
Started by user anonymous
[Workflow] Allocate node : Start
Running on master in /var/lib/jenkins/jobs/ntsvc-monitor-de
[JIRA] [amazon-ecs-plugin] (JENKINS-32865) InvalidKeyException: ECDH key agreement requires ECPublicKey for doPhase
Title: Message Title
Nicolas De Loof created an issue
Jenkins / JENKINS-32865
InvalidKeyException: ECDH key agreement requires ECPublicKey for doPhase
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
amazon-ecs-plugin
Created:
09/Feb/16 8:50 PM
Priority:
Blocker
Reporter:
Nicolas De Loof
Environment : Amazon AMI ami-60b6c60a java-1.8.0-openjdk.x86_64 : openjdk version "1.8.0_65" jenkins 1.625.3
When configuring an ECS Cloud, get this exception : {{févr. 09, 2016 6:45:29 PM com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$DescriptorImpl doFillClusterItems INFOS: Exception searching clusters for credentials=75a41905-e23e-485f-b3cf-7d48a7e8984e, regionName=us-east-1 com.amazonaws.AmazonClientException: Unable to execute HTTP request: Could not generate secret at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:587) at com.amazonaws.http.AmazonHttpClient.doExecute(AmazonHttpClient.java:362) at com.amazonaws.http.AmazonHttpClient.executeWithTimer(AmazonHttpClient.java:328) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:307) at com.amazonaws.services.ecs.AmazonECSClient.invoke(AmazonECSClient.java:2220) at com.amazonaws.services.ecs.AmazonECSClient.listClusters(AmazonECSClient.java:1170) at com.amazonaws.services.ecs.AmazonECSClient.listClusters(AmazonECSClient.java:1182) ... Caused by: javax.net.ssl.SSLHandshakeException: Could not generate secret at sun.security.ssl.ECDHCrypt.getAgreedSecret(ECDHCrypt.java:103) ... at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:822) at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:576) ... 86 more Caused by: java.security.Invalid
[JIRA] [cluster-stats-plugin] (JENKINS-32864) Cluster Stats Plugin: Add a skip list of known log-running jobs
Title: Message Title John Mellor created an issue Jenkins / JENKINS-32864 Cluster Stats Plugin: Add a skip list of known log-running jobs Issue Type: New Feature Assignee: Unassigned Components: cluster-stats-plugin Created: 09/Feb/16 8:34 PM Priority: Minor Reporter: John Mellor The build timings provided the the cluster-stats plugin are highly skewed by a few long-running jobs - notably integration test suite runs and field deployment runs. In my case, most builds take 5 to 30 minutes to compile and unit-test. However, there are a dozen full integration testsuite runs that take most of the night to run, as well as deployment runs that can take many days to push the new products out. The numbers provided by the plugin are not useful as a result of this skewing. ENHANCEMENT REQUEST: Add a skiplist of jobs to ignore when compiling stats. Add Comment
[JIRA] [core] (JENKINS-32793) POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version
Title: Message Title Rami Abughazaleh commented on JENKINS-32793 Re: POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version The reason I want to install an older plugin is because the new version of the plugin caused some issues and we cannot move forward with it until those issues are fixed for example. Is there a work-around to installing an older version of a plugin programmatically? Thank 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] [cucumber-perf-plugin] (JENKINS-28767) Cucumber Performance Reporting Not generating project performance graph
Title: Message Title Michael Salvia commented on JENKINS-28767 Re: Cucumber Performance Reporting Not generating project performance graph I am experiencing the same issues. It maybe due to a _javascript_ Console error I see many in mine. 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-32765) Allow the directory that plugins are exploded into to be changed
Title: Message Title dogfood commented on JENKINS-32765 Re: Allow the directory that plugins are exploded into to be changed Integrated in jenkins_main_trunk # [FIXED JENKINS-32765] Allow the directory that plugins are exploded (Revision d27cff8fd2f500162368c265ab4d40808eb444da) JENKINS-32765 Perhaps it makes more sense to make this a property of (Revision c0cbff72972d7611da187f6258116e6b60d78e7d) JENKINS-32765 As I am not adding a new import, I will annotate with (Revision bdb3c0c6d5e368d3751b3c6dcac8863df217604a) JENKINS-32765 Fix failing tests (Revision 566def3bd6e0d1f9fd8b0cd6f7e9600c95107780) Result = SUCCESS stephen connolly : d27cff8fd2f500162368c265ab4d40808eb444da Files : core/src/main/java/hudson/ClassicPluginStrategy.java stephen connolly : c0cbff72972d7611da187f6258116e6b60d78e7d Files : core/src/main/java/hudson/PluginManager.java core/src/main/java/hudson/ClassicPluginStrategy.java stephen connolly : bdb3c0c6d5e368d3751b3c6dcac8863df217604a Files : core/src/main/java/hudson/PluginManager.java stephen connolly : 566def3bd6e0d1f9fd8b0cd6f7e9600c95107780 Files : core/src/main/java/hudson/PluginManager.java Add Comment
[JIRA] [github-oauth-plugin] (JENKINS-14524) Slave agent authorization 401
Title: Message Title fayyaz rehman commented on JENKINS-14524 Re: Slave agent authorization 401 i am having the same issue Failing to obtain https://ci.corvit.lab/jenkins/computer/slave3/slave-agent.jnlp java.io.IOException: Failed to load https://ci.corvit.lab/jenkins/computer/slave3/slave-agent.jnlp: 401 Unauthorized at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:275) at hudson.remoting.Launcher.run(Launcher.java:219) at hudson.remoting.Launcher.main(Launcher.java:192) Waiting 10 seconds before retry 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-custom-build-environment-plugin] (JENKINS-32861) Checking Dockerfile in project is too early in the process
Title: Message Title Thomas Collignon updated an issue Jenkins / JENKINS-32861 Checking Dockerfile in project is too early in the process Change By: Thomas Collignon In docker-custom-build-environnment-plugin 1.6.5-SNAPSHOT, I have this issue : *Your project is missing a Dockerfile*But I haven' in 1.6.4 release version.In fact this is due to this PR : https://github.com/jenkinsci/docker-custom-build-environment-plugin/pull/37I have tested without, and it's works.I think that the test is too early in the process, maybe only with slave? Or only with gerrit-trigger-plugin? Or maybe the control will not be the same at this place? I will continue my test and maybe propose a new PR to fix 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-32863) Sleep function causes premature exit of loop in some cases
Title: Message Title Zach Norris created an issue Jenkins / JENKINS-32863 Sleep function causes premature exit of loop in some cases Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 09/Feb/16 6:10 PM Environment: Workflow: 1.13 Jenkins: 1.642.1 Priority: Major Reporter: Zach Norris In this use case the for loop is prematurely exited directly after the sleep function. See gist URL for code snippets and output. They were run under the same conditions. The only difference the inclusion of the sleep statement. Add Comment
[JIRA] [slave-utilization] (JENKINS-32862) java.io.IOException: Failed to load https://ci.marlysys.lab/jenkins/computer/slave3/slave-agent.jnlp: 401 Unauthorized
Title: Message Title fayyaz rehman created an issue Jenkins / JENKINS-32862 java.io.IOException: Failed to load https://ci.marlysys.lab/jenkins/computer/slave3/slave-agent.jnlp: 401 Unauthorized Issue Type: Bug Assignee: Unassigned Components: slave-utilization Created: 09/Feb/16 6:07 PM Labels: slave Priority: Minor Reporter: fayyaz rehman Failing to obtain https://ci.corvit.lab/jenkins/computer/slave3/slave-agent.jnlp java.io.IOException: Failed to load https://ci.corvit.lab/jenkins/computer/slave3/slave-agent.jnlp: 401 Unauthorized at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:275) at hudson.remoting.Launcher.run(Launcher.java:219) at hudson.remoting.Launcher.main(Launcher.java:192) Waiting 10 seconds before retry Add Comment
[JIRA] [git-plugin] (JENKINS-29482) Prune stale branches prevents git plugin change history display
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-29482 Prune stale branches prevents git plugin change history display Change By: Mark Waite Status: Resolved Closed 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-custom-build-environment-plugin] (JENKINS-32861) Checking Dockerfile in project is too early in the process
Title: Message Title Thomas Collignon updated an issue Jenkins / JENKINS-32861 Checking Dockerfile in project is too early in the process Change By: Thomas Collignon Environment: Linux master , Linux Slave , Jenkins 1.625.3.1 , docker-custom-build 1.6.5-SNAPSHOT , gerrit-trigger-plugin 2.18.3 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-32834) Failed to connect to repository with password-protected ssh key
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32834 Re: Failed to connect to repository with password-protected ssh key Code changed in jenkins User: Mark Waite Path: README.md http://jenkins-ci.org/commit/git-client-plugin/fda981f35a28683f53b480ffad779850bfaebc39 Log: [Fix JENKINS-32834] don't break ssh passphrase in few working cases Refer to 7711aacb34aa597a92aad14e8d7429347a920b8d README change because I made a mistake in commit message for 7711aacb 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-custom-build-environment-plugin] (JENKINS-32861) Checking Dockerfile in project is too early in the process
Title: Message Title Thomas Collignon created an issue Jenkins / JENKINS-32861 Checking Dockerfile in project is too early in the process Issue Type: Bug Assignee: Nicolas De Loof Components: docker-custom-build-environment-plugin Created: 09/Feb/16 5:50 PM Environment: Linux master, Linux Slave, Jenkins 1.625.3.1, docker-custom-build 1.6.5-SNAPSHOT, gerrit-trigger-plugin 2.18.3 Labels: plugin regression Priority: Minor Reporter: Thomas Collignon In docker-custom-build-environnment-plugin 1.6.5-SNAPSHOT, I have this issue : Your project is missing a Dockerfile But I haven' in 1.6.4 release version. In fact this is due to this PR : https://github.com/jenkinsci/docker-custom-build-environment-plugin/pull/37 I have tested without, and it's works. I think that the test is too early in the process, maybe only with slave? Or only with gerrit-trigger-plugin? I will continue my test and
[JIRA] [core] (JENKINS-32765) Allow the directory that plugins are exploded into to be changed
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-32765 Allow the directory that plugins are exploded into to be changed Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32765) Allow the directory that plugins are exploded into to be changed
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32765 Re: Allow the directory that plugins are exploded into to be changed Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/PluginManager.java http://jenkins-ci.org/commit/jenkins/bdb3c0c6d5e368d3751b3c6dcac8863df217604a Log: JENKINS-32765 As I am not adding a new import, I will annotate with `@CheckForNull` Of course the import being used is in a package name that is reserved for artifacts produced by a JSR... and the JSR that the dependency is claiming to come from has not actually published anything... thus whoever produced the artifact has broken the JSR policy... and it is also not safe for us to actually use these annotations as we do not know what a JSR may change on the road to actually providing this... but that is a war for a different PR 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-custom-build-environment-plugin] (JENKINS-32758) Docker build from Dockerfile requires full path to Dockerfile
Title: Message Title
Thomas Collignon edited a comment on JENKINS-32758
Re: Docker build from Dockerfile requires full path to Dockerfile
Hi,We set Dockerfile field to : _ {code:java} ${WORKSPACE}/ Dockerfile_ Dockerfile {code} and it's works.Can you try it?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32765) Allow the directory that plugins are exploded into to be changed
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32765 Re: Allow the directory that plugins are exploded into to be changed Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/PluginManager.java http://jenkins-ci.org/commit/jenkins/566def3bd6e0d1f9fd8b0cd6f7e9600c95107780 Log: JENKINS-32765 Fix failing tests 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-32765) Allow the directory that plugins are exploded into to be changed
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32765 Re: Allow the directory that plugins are exploded into to be changed Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/ClassicPluginStrategy.java http://jenkins-ci.org/commit/jenkins/d27cff8fd2f500162368c265ab4d40808eb444da Log: [FIXED JENKINS-32765] Allow the directory that plugins are exploded into to be changed This really has to be controlled by either a system property or a CLI parameter as we cannot guarantee that any path specified in a configuration file in JENKINS_HOME will be valid on another machine where the JENKINS_HOME is mounted Obviously Jenkins does not currently support fully starting two Jenkins instances on the same JENKINS_HOME, so this fix is to assist in Disaster Recovery (or semi-higher availability) sceanarios where the backup node is being brought up. In such cases, the node that failed may not have correctly released all its file handles in the backing NFS share and thus could be blocking the recovery node from starting up. An additional use case is where the JENKINS_HOME is stored on a remote disk, e.g. a SAN, etc. and the user wants to take advantage of the faster local disk to serve the resources from both plugins and Jenkins core. Without this change only Jenkins core can be relocated outside of JENKINS_HOME (using the '--webroot=...' command line option). Ideally we would introduce this into the extras-executable-war module once the system property has had time to soak (although in an ideal world that module would be agnostic of Jenkins and thus it might not be appropriate there) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-32765) Allow the directory that plugins are exploded into to be changed
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32765 Re: Allow the directory that plugins are exploded into to be changed Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/ClassicPluginStrategy.java core/src/main/java/hudson/PluginManager.java http://jenkins-ci.org/commit/jenkins/c0cbff72972d7611da187f6258116e6b60d78e7d Log: JENKINS-32765 Perhaps it makes more sense to make this a property of the PluginManager rather than the classic strategy Also expose via servlet context parameter of same name to allow multiple instances of Jenkins in the same servlet container to have different directories As we are no longer a constant, change the system property to camelCase 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-custom-build-environment-plugin] (JENKINS-32758) Docker build from Dockerfile requires full path to Dockerfile
Title: Message Title
Thomas Collignon edited a comment on JENKINS-32758
Re: Docker build from Dockerfile requires full path to Dockerfile
Hi,We set Dockerfile field to : _ ${WORKSPACE}/ Dockerfile Dockerfile_ , and it's works.Can you try it?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-32758) Docker build from Dockerfile requires full path to Dockerfile
Title: Message Title
Thomas Collignon edited a comment on JENKINS-32758
Re: Docker build from Dockerfile requires full path to Dockerfile
Hi,We set Dockerfile field to : _ ${WORKSPACE}/Dockerfile_ , and it's works.Can you try it?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32765) Allow the directory that plugins are exploded into to be changed
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32765 Re: Allow the directory that plugins are exploded into to be changed Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/ClassicPluginStrategy.java core/src/main/java/hudson/PluginManager.java http://jenkins-ci.org/commit/jenkins/c11e26504e3936c9ebe8306de5900645a1ab6fa6 Log: Merge pull request #2012 from stephenc/jenkins-32765 [FIXED JENKINS-32765] Allow the directory that plugins are exploded into to be changed Compare: https://github.com/jenkinsci/jenkins/compare/51f215c3b878...c11e26504e39 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-32840) Step ‘Git Publisher’ failed when pushing the build tag of a job inside a folder
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32840 Re: Step ‘Git Publisher’ failed when pushing the build tag of a job inside a folder Code changed in jenkins User: Mark Waite Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/7711aacb34aa597a92aad14e8d7429347a920b8d Log: [Fix JENKINS-32840] ssh passphrase support The BatchMode=yes setting breaks at least one working use case for passphrase protected RSA private keys. Needs further investigation to understand why the passphrase case works for one user but does not work for many others. Revert "Disable ssh password and passphrase prompting" This reverts commit e564b6ca704130bb5706ad7bd504c99aab050087. 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-custom-build-environment-plugin] (JENKINS-32758) Docker build from Dockerfile requires full path to Dockerfile
Title: Message Title
Thomas Collignon edited a comment on JENKINS-32758
Re: Docker build from Dockerfile requires full path to Dockerfile
Hi,We set Dockerfile filed field to : ${WORKSPACE}/Dockerfile, and it's works.Can you try it?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-32758) Docker build from Dockerfile requires full path to Dockerfile
Title: Message Title
Thomas Collignon commented on JENKINS-32758
Re: Docker build from Dockerfile requires full path to Dockerfile
Hi,
We set Dockerfile filed to : $ {WORKSPACE}
/Dockerfile, and it's works.
Can you try it?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32860) Performance issue when retrieving build details of a job run with many artifacts
Title: Message Title Bernhard Berbuir created an issue Jenkins / JENKINS-32860 Performance issue when retrieving build details of a job run with many artifacts Issue Type: Bug Assignee: Unassigned Attachments: JenkinsCPUload.png Components: core Created: 09/Feb/16 5:00 PM Environment: Windows 7, Java 1.8.0_71 Labels: api Priority: Major Reporter: Bernhard Berbuir I have some jobs which have lots of artifacts (over 5000 files in over 400 folders). When i retrieve build details of job run via REST api (e.g. https://jenkins/job/JenkinsJob/123/api/xml) then a huge response XML document has to be created. With the last LTS version (1.625.3) this wasn't an issue but after upgrading (1.642.1) I
[JIRA] [maven-plugin] (JENKINS-26048) Jenkins no longer cleaning up child processes when build stopped - as of 1.587
Title: Message Title Don Bogardus commented on JENKINS-26048 Re: Jenkins no longer cleaning up child processes when build stopped - as of 1.587 I've kept my company on Jenkins version 1.586 this whole time. It does not suffer from this bug and cleans up all surefire and phantomjs processes nicely. 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] [_unsorted] (JENKINS-32856) Can't update registry settings through Jenkins
Title: Message Title VENUS PATHAK updated JENKINS-32856 Jenkins / JENKINS-32856 Can't update registry settings through Jenkins Change By: VENUS PATHAK Status: Reopened Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [_unsorted] (JENKINS-32856) Can't update registry settings through Jenkins
Title: Message Title VENUS PATHAK closed an issue as Done Jenkins / JENKINS-32856 Can't update registry settings through Jenkins Change By: VENUS PATHAK Status: Open Closed Resolution: 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] [_unsorted] (JENKINS-32856) Can't update registry settings through Jenkins
Title: Message Title VENUS PATHAK assigned an issue to VENUS PATHAK Jenkins / JENKINS-32856 Can't update registry settings through Jenkins Change By: VENUS PATHAK Assignee: Oleg Nenashev VENUS PATHAK 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] [_unsorted] (JENKINS-32856) Can't update registry settings through Jenkins
Title: Message Title VENUS PATHAK assigned an issue to Oleg Nenashev Jenkins / JENKINS-32856 Can't update registry settings through Jenkins Change By: VENUS PATHAK Assignee: VENUS PATHAK Oleg Nenashev 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] [_unsorted] (JENKINS-32856) Can't update registry settings through Jenkins
Title: Message Title VENUS PATHAK updated an issue Jenkins / JENKINS-32856 Can't update registry settings through Jenkins Change By: VENUS PATHAK I am trying to add some registry settings from Jenkins on a remote machine using the a batch script below : . *The Jenkins build is successful but it doe not update the registry 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] [_unsorted] (JENKINS-32856) Can't update registry settings through Jenkins
Title: Message Title VENUS PATHAK reopened an issue Jenkins / JENKINS-32856 Can't update registry settings through Jenkins Change By: VENUS PATHAK Resolution: Fixed Status: Closed Reopened Assignee: Oleg Nenashev VENUS PATHAK 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] [_unsorted] (JENKINS-32856) Can't update registry settings through Jenkins
Title: Message Title VENUS PATHAK updated an issue Jenkins / JENKINS-32856 Can't update registry settings through Jenkins Change By: VENUS PATHAK I am trying to add some registry settings from Jenkins on a remote machine using the batch script below : reg add "HKEY_LOCAL_MACHINE\SOFTWARE\webPLAN Inc.\webPLAN" /v RestoreOldData /t REG_DWORD /d 0x0001 /f reg add "HKEY_LOCAL_MACHINE\SOFTWARE\webPLAN Inc.\webPLAN" /v RunScheduledTasks /t REG_DWORD /d 0x /freg add "HKEY_LOCAL_MACHINE\SOFTWARE\webPLAN Inc.\webPLAN" /v SkipScenarioCleanUp /t REG_DWORD /d 0x0001 /freg add "HKEY_LOCAL_MACHINE\SOFTWARE\webPLAN Inc.\webPLAN\RRMonitor" /v LimitedDumpOnFirstChance /t REG_DWORD /d 0x0001 /f *The Jenkins build is successful but it doe not update the registry 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] [_unsorted] (JENKINS-32856) Can't update registry settings through Jenkins
Title: Message Title VENUS PATHAK closed an issue as Fixed Jenkins / JENKINS-32856 Can't update registry settings through Jenkins Change By: VENUS PATHAK Status: Open Closed 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] [_unsorted] (JENKINS-32856) Can't update registry settings through Jenkins
Title: Message Title VENUS PATHAK updated an issue Jenkins / JENKINS-32856 Can't update registry settings through Jenkins Change By: VENUS PATHAK Comment: my account has admin permissions.I tried to modify permissions in regedit as well.I am not able top attach a file here. So i copied the log and attached it here.Started by user [8mha:lh+LCP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAzOEgYu/dLi1CL9vNKcHACFIKlWvw== [0manonymous[EnvInject] - Loading node environment variables.Building remotely on [8mha:nx+LCP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAzOEgZh/eT83ILSktQi/fySkrLcFEMzQwDCXkDiyA== [0mottvmd161 in workspace c:\jenkins\workspace\temp\test[test] $ cmd /c call C:\Users\vpathak\AppData\Local\Temp\hudson6737948905643074208.batc:\jenkins\workspace\temp\test>CALL "C:\TOOLS\ToolBox\SetRegistryBeforeLoadPKG.bat" c:\jenkins\workspace\temp\test>reg add "HKEY_LOCAL_MACHINE\SOFTWARE\webPLAN Inc.\webPLAN" /v RestoreOldData /t REG_DWORD /d 0x0001 /f The operation completed successfully.c:\jenkins\workspace\temp\test>reg add "HKEY_LOCAL_MACHINE\SOFTWARE\webPLAN Inc.\webPLAN" /v RunScheduledTasks /t REG_DWORD /d 0x /f The operation completed successfully.c:\jenkins\workspace\temp\test>reg add "HKEY_LOCAL_MACHINE\SOFTWARE\webPLAN Inc.\webPLAN" /v SkipScenarioCleanUp /t REG_DWORD /d 0x0001 /f The operation completed successfully.c:\jenkins\workspace\temp\test>reg add "HKEY_LOCAL_MACHINE\SOFTWARE\webPLAN Inc.\webPLAN\RRMonitor" /v LimitedDumpOnFirstChance /t REG_DWORD /d 0x0001 /f The operation completed successfully.c:\jenkins\workspace\temp\test>exit 0 Started calculate disk usage of buildFinished Calculation of disk usage of build in 0 secondsStarted calculate disk usage of workspaceFinished Calculation of disk usage of workspace in 0 secondsNotifying upstream projects of job completionFinished: SUCCESSThanks a lot Add Comment
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-32542) Maven project failed with "Connection refused" when built in a docker Container
Title: Message Title Sylvie Carrier commented on JENKINS-32542 Re: Maven project failed with "Connection refused" when built in a docker Container No. We always had this behaviour. So we currently progress with freestyle job only... 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-workflow-plugin] (JENKINS-32859) tests hung in docker container due to PID1 not reaping zombies
Title: Message Title Edwin Török created an issue Jenkins / JENKINS-32859 tests hung in docker container due to PID1 not reaping zombies Issue Type: Bug Assignee: Jesse Glick Attachments: config.xml Components: docker-workflow-plugin Created: 09/Feb/16 4:20 PM Environment: jenkins:latest Docker container master, no slaves Docker 1.8.2 on CentOS Linux release 7.1.1503 (Core) Jenkins 1.642.1 Docker Pipeline plugin 1.13 Docker Commons plugin 1.2 FROM jenkins:latest COPY plugins.txt /tmp/plugins.txt RUN /usr/local/bin/plugins.sh /tmp/plugins.txt Dockerfile building an image I called jenkins-configured: USER root COPY JENKINS_HOME /usr/share/jenkins/ref RUN chown -R jenkins.jenkins /usr/share/jenkins/ref RUN apt-get update -qq && apt-get install -y docker.io && apt-get clean # jenkins accesses docker from host, it has root-equivalent rights RUN usermod -G 0 -a jenkins USER jenkins CMD /usr/local/bin/jenkins.sh Running jenkins: docker run --name jenkins-run -p 8080:8080 -p 5:5 \ -v /var/jenkins_home:/var/jenkins_home:z\ -v /var/run/docker.sock:/var/run/docker.sock \ --privileged \ jenkins-configured Priority: Major Reporter: Edwin Török
[JIRA] [_unsorted] (JENKINS-32856) Can't update registry settings through Jenkins
Title: Message Title VENUS PATHAK commented on JENKINS-32856 Re: Can't update registry settings through Jenkins They work on the same account. And the script work when i run it manually. I just found one thing. When I run the same script on another slave but from the same master, it works. What can be the problem with the first slave ? 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-27268) "dumb" slave?
Title: Message Title Daniel Beck commented on JENKINS-27268 Re: "dumb" slave? Butler/servant would have been thematic Oh well… Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [discard-old-build-plugin] (JENKINS-32858) "Status to keep" options are missing
Title: Message Title Anentropic created an issue Jenkins / JENKINS-32858 "Status to keep" options are missing Issue Type: Bug Assignee: nkns165 Components: discard-old-build-plugin Created: 09/Feb/16 4:11 PM Environment: Jenkins ver. 1.638 discard-old-build v 1.05 Labels: plugin Priority: Critical Reporter: Anentropic UI does not match the screenshots shown here https://wiki.jenkins-ci.org/display/JENKINS/Discard+Old+Build+plugin I do not have the "Status to keep" checkboxes. Without option to keep successful builds I don't find plugin useful.
[JIRA] [_unsorted] (JENKINS-32856) Can't update registry settings through Jenkins
Title: Message Title Oleg Nenashev commented on JENKINS-32856 Re: Can't update registry settings through Jenkins Does your Jenkins master/slave run on the same account? Does the script work when you invoke it manually? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-32834) Failed to connect to repository with password-protected ssh key
Title: Message Title Alberto Gallardo commented on JENKINS-32834 Re: Failed to connect to repository with password-protected ssh key Apparently, there is not much more I can test: I have disabled the 'SSH Slaves plugin' (I don't have slaves). The GUI renders the error independently of the 'Build Environment > SSH Agent' setting. If it helps, when setting this 'SSH Agent' option, the job fails with this message (I have to launch it manually): Started by user ... Building in workspace /srv/jenkins/jobs/Tests/jobs/test_github_jenkins_integration_ghp/workspace [ssh-agent] Looking for ssh-agent implementation... [ssh-agent] Java/JNR ssh-agent [ssh-agent] Started. [ssh-agent] Unable to read key: Unable to create OpenSSL PBDKF: PBKDF-OpenSSL SecretKeyFactory not available org.bouncycastle.openssl.PEMException: Unable to create OpenSSL PBDKF: PBKDF-OpenSSL SecretKeyFactory not available at org.bouncycastle.openssl.jcajce.PEMUtilities.getKey(Unknown Source) at org.bouncycastle.openssl.jcajce.PEMUtilities.getKey(Unknown Source) at org.bouncycastle.openssl.jcajce.PEMUtilities.crypt(Unknown Source) at org.bouncycastle.openssl.jcajce.JcePEMDecryptorProviderBuilder$1$1.decrypt(Unknown Source) at org.bouncycastle.openssl.PEMEncryptedKeyPair.decryptKeyPair(Unknown Source) at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgent.addIdentity(JNRRemoteAgent.java:98) at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper$SSHAgentEnvironment.add(SSHAgentBuildWrapper.java:388) at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.preCheckout(SSHAgentBuildWrapper.java:227) at jenkins.scm.SCMCheckoutStrategy.preCheckout(SCMCheckoutStrategy.java:76) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528) at hudson.model.Run.execute(Run.java:1738) 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.security.NoSuchAlgorithmException: PBKDF-OpenSSL SecretKeyFactory not available at javax.crypto.SecretKeyFactory.(SecretKeyFactory.java:121) at javax.crypto.SecretKeyFactory.getInstance(SecretKeyFactory.java:159) at org.bouncycastle.jcajce.util.DefaultJcaJceHelper.createSecretKeyFactory(Unknown Source) ... 14 more [ssh-agent] Using credentials jenkins (jenkins.tests.id_rsa pass) Wiping out workspace first. Cloning the remote Git repository Cloning repository g...@github.tik.uni-stuttgart.de:NFL/tests.git > git init /srv/jenkins/jobs/Tests/jobs/test_github_jenkins_integration_ghp/workspace # timeout=10 Fetching upstream changes from g...@github.tik.uni-stuttgart.de:NFL/tests.git > git --version # timeout=10 using GIT_SSH to set credentials jenkins.tests.id_rsa pass > git -c core.askpass=true fetch --tags --progress g...@github.tik.uni-stuttgart.de:NFL/tests.git +refs/heads/*:refs/remotes/origin/* ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "git -c core.askpass=true fetch --tags --progress g...@github.tik.uni-stuttgart.de:NFL/tests.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.
