[JIRA] [workflow-plugin] (JENKINS-32214) Workflow and svn polling
Title: Message Title Jesse Glick commented on JENKINS-32214 Re: Workflow and svn polling I suspect this affects the Subversion and Mercurial plugins, which correctly use SCMRevisionState, but not the Git plugin, which completes ignores it in favor of its own BuildData hack. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector-plugin] (JENKINS-32216) Need Help Plz on GitHub Integration with Jenkins
Title: Message Title Ulli Hafner resolved as Not A Defect Please ask questions on the users mailing list and do not spam the issue tracker. Jenkins / JENKINS-32216 Need Help Plz on GitHub Integration with Jenkins Change By: Ulli Hafner Status: Reopened Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-32220) email-ext-plugin does seems to not run after installed
Title: Message Title Daniel Castro created an issue Jenkins / JENKINS-32220 email-ext-plugin does seems to not run after installed Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin Created: 29/Dec/15 4:24 PM Environment: Jenkins - 1.642 email-ext-plugin - 2.40.5 awt.toolkit sun.awt.X11.XToolkit executable-war /usr/lib/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / hudson.diyChunking true java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/lib/jenkins/jenkins.war java.class.version 51.0 java.endorsed.dirs /usr/java/jdk1.7.0_51/jre/lib/endorsed java.ext.dirs /usr/java/jdk1.7.0_51/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/java/jdk1.7.0_51/jre java.io.tmpdir /tmp java.library.path /usr/starteam/sdk/lib:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib java.runtime.name Java(TM) SE Runtime Environment java.runtime.version 1.7.0_51-b13 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.7 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.7.0_51 java.vm.info mixed mode java.vm.name Java HotSpot(TM) 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.7 java.vm.vendor Oracle Corporation java.vm.version 24.51-b03 JENKINS_HOME /var/lib/jenkins jna.loaded true jna.platform.library.path /usr/lib64:/lib64:/usr/lib:/lib:/usr/lib/vmware-tools/lib64/libvmGuestLibJava.so:/usr/lib/vmware-tools/lib32/libvmGuestLibJava.so:/usr/lib/vmware-tools/lib64/libvmGuestLib.so:/usr/lib/vmware-tools/lib32/libvmGuestLib.so:/usr/lib64/mysql:/usr/lib/vmware-tools/lib64/libDeployPkg.so:/usr/lib/vmware-tools/lib32/libDeployPkg.so jnidispatch.path /tmp/jna--1712433994/jna2288037668175642317.tmp line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch amd64 os.name Linux os.version 2.6.32-431.5.1.el6.x86_64 path.separator : sun.arch.data.model 64 sun.boot.class.path
[JIRA] [multiple-scms-plugin] (JENKINS-27638) GIT : Fatal : ClassCastException: hudson.scm.SCMRevisionState$None cannot be cast to org.jenkinsci.plugins.multiplescms.MultiSCMRevisionState
Title: Message Title Neon Ngo commented on JENKINS-27638 Re: GIT : Fatal : ClassCastException: hudson.scm.SCMRevisionState$None cannot be cast to org.jenkinsci.plugins.multiplescms.MultiSCMRevisionState I am running Jenkins ver. 1.625.3, Git Plugin 2.3.5, Multiple SCMs plugin 0.4 and got the below error I selected Multiple SCMs and added two Git repos... FATAL: hudson.scm.SCMRevisionState$None cannot be cast to org.jenkinsci.plugins.multiplescms.MultiSCMRevisionState java.lang.ClassCastException: hudson.scm.SCMRevisionState$None cannot be cast to org.jenkinsci.plugins.multiplescms.MultiSCMRevisionState at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:106) at hudson.scm.SCM.checkout(SCM.java:485) at hudson.model.AbstractProject.checkout(AbstractProject.java:1275) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532) at hudson.model.Run.execute(Run.java:1741) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:306) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:408) Finished: FAILURE actually, I got the same ClassCastException when I only had one Git Repo under Multiple SCM repo. What plugin and version is this issue fixed under? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-32220) email-ext-plugin does seems to not run after installed
Title: Message Title Alex Earl commented on JENKINS-32220 Re: email-ext-plugin does seems to not run after installed That's why you are getting the error. You need to figure out what is causing the token macro plugin to be disabled. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector-plugin] (JENKINS-32216) Need Help Plz on GitHub Integration with Jenkins
Title: Message Title SAYOM GHOSH reopened an issue Hello, Can you kindly help me please as to what should I do in order to get rid of the situation please. Jenkins / JENKINS-32216 Need Help Plz on GitHub Integration with Jenkins Change By: SAYOM GHOSH Resolution: Not A Defect 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] [email-ext-plugin] (JENKINS-32220) email-ext-plugin does seems to not run after installed
Title: Message Title Daniel Castro edited a comment on JENKINS-32220 Re: email-ext-plugin does seems to not run after installed What Token Macro is token macro enabled by defautl and how should I do it ? can not be disabled.It is also a pinned plugin. It´s version is 1.12.1 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-32220) email-ext-plugin does seems to not run after installed
Title: Message Title Daniel Castro edited a comment on JENKINS-32220 Re: email-ext-plugin does seems to not run after installed Token Macro is enabled by defautl and it can not be disabled.It is also a pinned plugin. It´s version is 1.12.1See the png file attached to the issue!token macro.png|thumbnail! I also tried to go back to version 1.10. Did not work.The screen that shows the status of each plugin keeps showing the token macro disabled whie the plugin installed page says it can not be disabled. So I changed back to 1.12.1 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [allure-plugin] (JENKINS-32219) Allure Reports are not visible after upgrading to Jenkins 1.643
Title: Message Title Artem Eroshenko commented on JENKINS-32219 Re: Allure Reports are not visible after upgrading to Jenkins 1.643 http://wiki.qatools.ru/display/AL/Allure+Jenkins+Plugin#AllureJenkinsPlugin-configure-securityConfigureJenkinsContentSecurity Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [prioritysorter-plugin] (JENKINS-32138) Impossible to assign priority more than 5
Title: Message Title Alexey Pakseykin resolved as Not A Defect Jenkins / JENKINS-32138 Impossible to assign priority more than 5 Change By: Alexey Pakseykin Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-32220) email-ext-plugin does seems to not run after installed
Title: Message Title Daniel Castro updated an issue Jenkins / JENKINS-32220 email-ext-plugin does seems to not run after installed Change By: Daniel Castro Attachment: token macro.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] [email-ext-plugin] (JENKINS-32220) email-ext-plugin does seems to not run after installed
Title: Message Title Daniel Castro edited a comment on JENKINS-32220 Re: email-ext-plugin does seems to not run after installed Token Macro is enabled by defautl and it can not be disabled.It is also a pinned plugin. It´s version is 1.12.1 See the png file attached to the issue!token macro.png|thumbnail! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multiple-scms-plugin] (JENKINS-25787) Repository Browser broken with Multiple SCMs plugin
Title: Message Title Daniel Beck commented on JENKINS-25787 Re: Repository Browser broken with Multiple SCMs plugin I cannot imagine using Jenkins without a chance to browsing changes... can you? Sounds like a major loss of functionality, which is what Major is for. See the help page accessible from the Edit Issue form. The frequent misuse of these levels (nobody wants the issue they're experiencing classified as a Minor inconvenience when it messes up their day by requiring stupid workarounds) leads to inflation and in the end everything is Critical or Blocker, rendering this classification completely useless and impossible to tell the really critical things (like data loss) from the rest. But feel free to contribute to that. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-32214) Workflow and svn polling
Title: Message Title Jesse Glick started work on JENKINS-32214 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector-plugin] (JENKINS-32216) Need Help Plz on GitHub Integration with Jenkins
Title: Message Title SAYOM GHOSH commented on JENKINS-32216 Re: Need Help Plz on GitHub Integration with Jenkins Hello, Can you kindly let me know what is the resolution please. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-32218) buildsByBranchName is not set anymore
Title: Message Title Alex Nederlof commented on JENKINS-32218 Re: buildsByBranchName is not set anymore Looking at [the diff](https://github.com/jenkinsci/git-plugin/compare/git-2.4.0...git-2.4.1) and the version timestamps I'm almost certain we ran 2.4.0 before this version, so it is a regression to 2.4.1 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-32218) buildsByBranchName is not set anymore
Title: Message Title Alex Nederlof edited a comment on JENKINS-32218 Re: buildsByBranchName is not set anymore Looking at [the diff ]( | https://github.com/jenkinsci/git-plugin/compare/git-2.4.0...git-2.4.1 ) ] and the version timestamps I'm almost certain we ran 2.4.0 before this version, so it is a regression to 2.4.1 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [allure-plugin] (JENKINS-32219) Allure Reports are not visible after upgrading to Jenkins 1.643
Title: Message Title Liya Katz created an issue Jenkins / JENKINS-32219 Allure Reports are not visible after upgrading to Jenkins 1.643 Issue Type: Bug Assignee: Artem Eroshenko Components: allure-plugin Created: 29/Dec/15 3:43 PM Environment: Jenkins 1.643 Allure Report plugin 2.8 and 2.10 Priority: Blocker Reporter: Liya Katz When trying to open Allure Report, it stuck on "Loading" forever. Same for new and old reports (those that were ok before Jenkins upgrade) Add Comment
[JIRA] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue
Title: Message Title Trevor Baker reopened an issue Jenkins / JENKINS-25786 Renaming Job Causes a poisoned commitQueue Change By: Trevor Baker 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] [email-ext-plugin] (JENKINS-32220) email-ext-plugin does seems to not run after installed
Title: Message Title Alex Earl commented on JENKINS-32220 Re: email-ext-plugin does seems to not run after installed It looks like token macro might be disabled, please enable 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] [prioritysorter-plugin] (JENKINS-32138) Impossible to assign priority more than 5
Title: Message Title Alexey Pakseykin commented on JENKINS-32138 Re: Impossible to assign priority more than 5 My bad. I dug deeper and realized there is also (main) configuration under "Manage Jenkins" => "Configure System". And I also found second XML config file: /var/lib/jenkins/jenkins.advancedqueue.PrioritySorterConfiguration.xml - per job configuration accessible via main side panel "Job Priorities" /var/lib/jenkins/jenkins.advancedqueue.PriorityConfiguration.xml - main configuration. Hmm... These facts closes this issue. Thanks for the hint! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-32220) email-ext-plugin does seems to not run after installed
Title: Message Title Daniel Castro commented on JENKINS-32220 Re: email-ext-plugin does seems to not run after installed What is token macro and how should I do 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] [envinject-plugin] (JENKINS-27313) Environment variable Injection failing after upgrading from 1.90 to 1.91
Title: Message Title Clinton Foster commented on JENKINS-27313 Re: Environment variable Injection failing after upgrading from 1.90 to 1.91 I just installed v 1.92.1. The problem appears to be fixed, although I'm not certain because the way the job in question uses EnvInject may have changed. Can you confirm that a fix was made? I also upgraded from Jenkins 1.623 to 1.643. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-32218) buildsByBranchName is not set anymore
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-32218 buildsByBranchName is not set anymore Change By: Mark Waite _emphasized text_I I noticed that GIT_PREVIOUS_SUCCESSFUL_COMMIT was not set anymore on the Job that only builds our master branch. After some digging I found out that since the upgrade from the previous version (I can't find which version that was, is that stored somewhere?) the buildsByBranchName variable in any `build.xml` is not set anymore (it's empty). It is set in other jobs we have, just not this one.This env is critical for us, so I'm going to try to rollback. I'm glad to help track down this problem if possible. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-32218) buildsByBranchName is not set anymore
Title: Message Title Mark Waite commented on JENKINS-32218 Re: buildsByBranchName is not set anymore Can you explain the relationship between buildsByBranchName in your build.xml file and GIT_PREVIOUS_SUCCESSFUL_COMMIT? When you say that GIT_PREVIOUS_SUCCESSFUL_COMMIT is not set anymore on the job that builds your master branch, I assume that means in git plugin 2.4.0 it was set on builds of that job, but now with git plugin 2.4.1 it is no longer set. Have I interpreted that part correctly? Can you also further explain your comment that this behavior seems to be specific to a single job? I assume that means you are using GIT_PREVIOUS_SUCCESSFUL_COMMIT in other jobs, and it is still working in those other jobs. Can you identify key differences between the jobs where it is working and the jobs where it is not working? The code which computes GIT_PREVIOUS_SUCCESSFUL_COMMIT uses "getBuildData()". That general area of the plugin which modified in the 2.4.1 change window by a change from Nicolas de Loof and by one or more changes from Andrew Bayer. It has been an especially challenging portion of the 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] [allure-plugin] (JENKINS-32224) Correct support for matrix job
Title: Message Title Liya Katz created an issue Jenkins / JENKINS-32224 Correct support for matrix job Issue Type: Bug Assignee: Artem Eroshenko Components: allure-plugin Created: 29/Dec/15 10:54 PM Priority: Major Reporter: Liya Katz I have a matrix job that runs on 2 nodes, each one runs the same set of tests and creates the report. The Allure report is shown just fine for each node build. For the "main" build: If both nodes were successful (or unstable), the report just stuck forever on "Loading" If one of them has failed and no report was created, the "main" build report shows the successful node build report. Both are confusing I suggest to add an option to show merged report on the main build - probably should be the default option, alternative should be not to show Allure report on the main build at all Add Comment
[JIRA] [http-request-plugin] (JENKINS-32210) ldap and proxy access problem
Title: Message Title angel Liang assigned an issue to Janario Oliveira Jenkins / JENKINS-32210 ldap and proxy access problem Change By: angel Liang Assignee: Janario Oliveira Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [statusmonitor-plugin] (JENKINS-32223) Compatibility with folders plugin
Title: Message Title Steven Christou created an issue Jenkins / JENKINS-32223 Compatibility with folders plugin Issue Type: New Feature Assignee: danielgalan Components: statusmonitor-plugin Created: 29/Dec/15 10:38 PM Priority: Minor Reporter: Steven Christou Currently the status monitor plugin only provides a list of jobs at the root folder instead of providing status on any of the subfolders also. It would be nice for the status monitor plugin to iterate through each folder to provide a status on the subfolder jobs also. Add Comment
[JIRA] [statusmonitor-plugin] (JENKINS-32223) Compatibility with folders plugin
Title: Message Title Steven Christou updated an issue Jenkins / JENKINS-32223 Compatibility with folders plugin Change By: Steven Christou Currently the status monitor plugin only provides a the list of jobs at the root folder level instead of providing status on any of the subfolders also jobs within a folder . It would be nice for I setup the status monitor plugin to iterate through each folder to provide a status on have the subfolder status monitor postbuild action, however it still only shows top level folder jobs also . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-32218) buildsByBranchName is not set anymore
Title: Message Title Mark Waite edited a comment on JENKINS-32218 Re: buildsByBranchName is not set anymore Can you explain the relationship between buildsByBranchName in your build.xml file and GIT_PREVIOUS_SUCCESSFUL_COMMIT?When you say that GIT_PREVIOUS_SUCCESSFUL_COMMIT is not set anymore on the job that builds your master branch, I assume that means in git plugin 2.4.0 it was set on builds of that job, but now with git plugin 2.4.1 it is no longer set. Have I interpreted that part correctly?Can you also further explain your comment that this behavior seems to be specific to a single job? I assume that means you are using GIT_PREVIOUS_SUCCESSFUL_COMMIT in other jobs, and it is still working in those other jobs. Can you identify key differences between the jobs where it is working and the jobs where it is not working?The code which computes GIT_PREVIOUS_SUCCESSFUL_COMMIT uses "getBuildData()". That general area of the plugin which modified in the 2.4.1 change window by a change from Nicolas de Loof and by one or more changes from Andrew Bayer. It has been an especially challenging portion of the plugin. The "Manage plugins" section of the Jenkins configuration pages includes a page which allows you to revert to the prior plugin version. If you have not already reverted, that will show you the version of the plugin you were previously 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] [allure-plugin] (JENKINS-32224) Correct support for matrix job
Title: Message Title Liya Katz updated an issue Jenkins / JENKINS-32224 Correct support for matrix job Change By: Liya Katz Environment: Jenkins 1.643 Allure Report plugin 2.10 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-32218) buildsByBranchName is not set anymore
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-32218 buildsByBranchName is not set anymore Change By: Mark Waite I _emphasized text_I noticed that GIT_PREVIOUS_SUCCESSFUL_COMMIT was not set anymore on the Job that only builds our master branch. After some digging I found out that since the upgrade from the previous version (I can't find which version that was, is that stored somewhere?) the buildsByBranchName variable in any `build.xml` is not set anymore (it's empty). It is set in other jobs we have, just not this one.This env is critical for us, so I'm going to try to rollback. I'm glad to help track down this problem if possible. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-32221) Jenkinsfile Workflow script loading from external file doesn't populate pending script approvals
Title: Message Title Andrew Bayer commented on JENKINS-32221 Re: Jenkinsfile Workflow script loading from external file doesn't populate pending script approvals The invoked method was a GString.plus, which made this harder to unravel, since, well, that could have been a lot of things, but I eventually put what I thought was the right thing into the main Jenkinsfile and it showed up in the pending approvals right away... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-32157) Jenkins is unable to start a process using shell script
Title: Message Title Daniel Beck resolved as Not A Defect This is an issue tracker, not a support site, and your report does not show that whatever behavior you are seeing is a bug in Jenkins. Jenkins / JENKINS-32157 Jenkins is unable to start a process using shell script Change By: Daniel Beck Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [aws-java-sdk-plugin] (JENKINS-32162) Please bump to latest aws-java-sdk
Title: Message Title Daniel Beck assigned an issue to Vincent Latombe Created the component. Vincent Latombe Please remember to create the JIRA component when creating a plugin. Jenkins / JENKINS-32162 Please bump to latest aws-java-sdk Change By: Daniel Beck Component/s: aws-java-sdk-plugin Component/s: core Component/s: amazon-ecs-plugin Assignee: Nicolas De Loof Vincent Latombe Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [email-ext-plugin] (JENKINS-32220) email-ext-plugin does seems to not run after installed
Title: Message Title Daniel Beck commented on JENKINS-32220 Re: email-ext-plugin does seems to not run after installed Delete the file $JENKINS_HOME/plugins/token-macro.jpi.disabled (or similar), then restart Jenkins. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-32221) Jenkinsfile Workflow parallel script doesn't populate pending script approvals
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-32221 Jenkinsfile Workflow parallel script doesn't populate pending script approvals Issue Type: Bug Assignee: Jesse Glick Components: script-security-plugin, workflow-plugin Created: 29/Dec/15 8:57 PM Environment: Workflow 1.12, Script Security 1.15, core 1.625.2 Priority: Minor Reporter: Andrew Bayer Still digging into this, so expect more later, but in the following case, a method errored out due to needing script approval but did not show up in the pending script approvals: Jenkinsfile driven build. Loads from an external groovy file (after cloning from git, etc) to pull in some methods. Within a parallel block, invokes a method from that external groovy file that calls a not-yet-whitelisted method (in this case, `replaceAll(String, String)` but I don't think this is specific to that method).
[JIRA] [allure-plugin] (JENKINS-32219) Allure Reports are not visible after upgrading to Jenkins 1.643
Title: Message Title Liya Katz commented on JENKINS-32219 Re: Allure Reports are not visible after upgrading to Jenkins 1.643 Thank you! It works. Please update Jenkins plugin wiki page with this info Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [allure-plugin] (JENKINS-32219) Allure Reports are not visible after upgrading to Jenkins 1.643
Title: Message Title Liya Katz resolved as Fixed Jenkins / JENKINS-32219 Allure Reports are not visible after upgrading to Jenkins 1.643 Change By: Liya Katz 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] [envinject-plugin] (JENKINS-16754) $JOB_NAME is set to some autogenerated string instead of the project name
Title: Message Title John McGehee commented on JENKINS-16754 Re: $JOB_NAME is set to some autogenerated string instead of the project name I see "sge" in your path. Note that Sun Grid Engine also defines variable JOB_NAME, which overwrites the Jenkins JOB_NAME value. I work around this by defining. export JENKINS_JOB_NAME="$JOB_NAME" before qsub. See my Jenkins SGE plugin for more information. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-32221) Jenkinsfile Workflow script loading from external file doesn't populate pending script approvals
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-32221 Jenkinsfile Workflow script loading from external file doesn't populate pending script approvals Change By: Andrew Bayer Summary: Jenkinsfile Workflow parallel script loading from external file doesn't populate pending script approvals Still digging into this, so expect more later, but in the following case, a method errored out due to needing script approval but did not show up in the pending script approvals:- Jenkinsfile driven build.- Loads from an external groovy file (after cloning from git, etc) to pull in some methods.- Within Invokes a parallel block, invokes a method from that external groovy file that calls a not-yet-whitelisted method (in this case, `replaceAll(String, String)` but I don't think this is specific to that method).- The execution of those parallel blocks fail that method fails , unsurprisingly, but the method never shows up in the script security plugin's pending approvals, so there's no way to actually approve 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
[JIRA] [subversion-plugin] (JENKINS-32222) Disable SCM Change Logs
Title: Message Title Owen Wood created an issue Jenkins / JENKINS-3 Disable SCM Change Logs Issue Type: New Feature Assignee: Unassigned Components: subversion-plugin Created: 29/Dec/15 9:17 PM Priority: Minor Reporter: Owen Wood We run a fairly high load Jenkins install with 16 gb of ram, 8 cores and 47 executors (none on the master). One of our main git repositories is very large, containing about 60K files and receives multi-hundreds of commits per day. As a result the process of generating change logs is very cpu and memory intensive and we often have upwards of 20 or more such builds in flight at any one time. This results in several such change logs being generated at the same time, often resulting a heap errors on the master. To Jenkins credit, it survives these w/o crashing. The builds fail though and get retried, only adding to the load. However, such extremely large change logs are fairly useless and we can generate them after the fact any way when we really do need them. Therefore it would be very advantage for use to be able to turn of change log generation either system-wide or ideally, on a job by job basis.
[JIRA] [packaging] (JENKINS-32215) jenkins will not delete /tmp/upload_*.tmp files,after use File parameter upload file for build
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-32215 jenkins will not delete /tmp/upload_*.tmp files,after use File parameter upload file for build Possible packaging issue, maybe we just need to add a cron task to delete old temporary upload files? Change By: Daniel Beck Component/s: packaging Component/s: winstone-jetty Component/s: core Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options,
[JIRA] [git-plugin] (JENKINS-32222) Disable SCM Change Logs
Title: Message Title Owen Wood commented on JENKINS-3 Re: Disable SCM Change Logs Daniel Beck my brain saw SCM and converted to SVN Fixed component. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-32152) java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188)
Title: Message Title Daniel Beck commented on JENKINS-32152 Re: java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188) Weird. Would be interesting to know whether there are files named "atomic" in the affected job's directory. Also, can be resolved by setting a higher next build number. Use e.g. the Set Next Build Number plugin to do that. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject-plugin] (JENKINS-16754) $JOB_NAME is set to some autogenerated string instead of the project name
Title: Message Title
John McGehee edited a comment on JENKINS-16754
Re: $JOB_NAME is set to some autogenerated string instead of the project name
I see "sge" in your path. Note that Sun Grid Engine also defines variable {{JOB_NAME}}, which overwrites the Jenkins {{JOB_NAME}} value.I work around this by defining.{code}export JENKINS_JOB_NAME="$JOB_NAME"{code}before {{qsub}}.See my [Jenkins SGE plugin|https://github.com/jmcgeheeiv/sge-cloud-plugin #environment-variables ] for more information.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-32221) Jenkinsfile Workflow script loading from external file doesn't populate pending script approvals
Title: Message Title Andrew Bayer commented on JENKINS-32221 Re: Jenkinsfile Workflow script loading from external file doesn't populate pending script approvals Ok, not actually sure about this still. Might be because it was running in a catch? I don't know. Having trouble reproducing... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-32220) email-ext-plugin does seems to not run after installed
Title: Message Title Alex Earl commented on JENKINS-32220 Re: email-ext-plugin does seems to not run after installed I think you would want to check the Jenkins logs since the error would probably happen during startup. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-31932) Performance regression after fixing synchronization issue when setting JDK installations. (issue 28292)
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-31932 Performance regression after fixing synchronization issue when setting JDK installations. (issue 28292) Change By: Daniel Beck Labels: regression Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [allure-plugin] (JENKINS-32219) Allure Reports are not visible after upgrading to Jenkins 1.643
Title: Message Title Liya Katz closed an issue as Fixed Jenkins / JENKINS-32219 Allure Reports are not visible after upgrading to Jenkins 1.643 Change By: Liya Katz 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] [email-ext-plugin] (JENKINS-32220) email-ext-plugin does seems to not run after installed
Title: Message Title Daniel Castro commented on JENKINS-32220 Re: email-ext-plugin does seems to not run after installed The problem is how to do it. What log categories should I declare on http://myhost:8080/log/levels to try to trace the reason for this behavior? Also, the Token Macro has no log definition. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-32222) Disable SCM Change Logs
Title: Message Title Daniel Beck commented on JENKINS-3 Re: Disable SCM Change Logs subversion-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] [core] (JENKINS-25625) SECURITY-144-compat usage breaks tests due to code signing
Title: Message Title Kanstantsin Shautsou commented on JENKINS-25625 Re: SECURITY-144-compat usage breaks tests due to code signing What is the status of this issue? Updated plugin core from 1.609.3 to 1.625.3 and got the same error. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25625) SECURITY-144-compat usage breaks tests due to code signing
Title: Message Title Kanstantsin Shautsou commented on JENKINS-25625 Re: SECURITY-144-compat usage breaks tests due to code signing Found (resolved), in my case because of different remoting jars on jenkins jvm and CLI connection. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-32222) Disable SCM Change Logs
Title: Message Title Owen Wood updated an issue Jenkins / JENKINS-3 Disable SCM Change Logs Change By: Owen Wood Component/s: git-plugin Component/s: subversion-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] [core] (JENKINS-31256) hudson.Remoting.Engine#waitForServerToBack does not use credentials for connection
Title: Message Title Daniel Beck commented on JENKINS-31256 Re: hudson.Remoting.Engine#waitForServerToBack does not use credentials for connection This only applies to setups that don't implement the 'contract' that unprotected root actions need to be accessible without authentication, right? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-32199) Created a hidden job, but could not remove it
Title: Message Title Daniel Beck resolved as Not A Defect This is an issue tracker, not a support site, and this report doesn't definitively show there's a bug in Jenkins. To get answers for your question, ask for example in #jenkins on Freenode. Jenkins / JENKINS-32199 Created a hidden job, but could not remove it Change By: Daniel Beck Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-32222) Disable SCM Change Logs
Title: Message Title Mark Waite edited a comment on JENKINS-3 Re: Disable SCM Change Logs If it truly is change log generation which causes the problem, then you might try an experiment of computing the change log against a base version, and list that base version as "HEAD". The change log against "HEAD" should always be empty (I think), so should compute very quickly and with low overhead. I fear that the problem may be related to BuildData (rather than change log). If using HEAD as the basis for change log calculation does not resolve the problem, then it may indicate the much larger challenge that too much information is being carried in BuildData. Unfortunately, that is a very hard problem to solve. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-32222) Disable SCM Change Logs
Title: Message Title Mark Waite commented on JENKINS-3 Re: Disable SCM Change Logs If it truly is change log generation which causes the problem, then you might try an experiment of computing the change log against a base version, and list that base version as "HEAD". The change log against "HEAD" should always be empty (I think), so should compute very quickly and with low overhead. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-32157) Jenkins is unable to start a process using shell script
Title: Message Title Vijetha Nayak commented on JENKINS-32157 Re: Jenkins is unable to start a process using shell script When the same script works fine from command prompt and not from jenkins.Then it is a bug Right? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27251) windows slaves disconnect during build
Title: Message Title qingqing zhang commented on JENKINS-27251 Re: windows slaves disconnect during build any process?I have the same error. environment: master is linux jenkins version 1.639 jdk version:1.7.0 slave is windows,jdk version:1.8.0 Slave went offline during the build 00:38:11 ERROR: Connection was broken: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@4dc74f50[name=10.140.164.129] 00:38:11 at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208) 00:38:11 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:628) 00:38:11 at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) 00:38:11 at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) 00:38:11 at java.util.concurrent.FutureTask.run(Unknown Source) 00:38:11 at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) 00:38:11 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) 00:38:11 at java.lang.Thread.run(Unknown Source) 00:38:11 Caused by: java.io.IOException: Connection reset by peer 00:38:11 at sun.nio.ch.FileDispatcherImpl.read0(Native Method) 00:38:11 at sun.nio.ch.SocketDispatcher.read(Unknown Source) 00:38:11 at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source) 00:38:11 at sun.nio.ch.IOUtil.read(Unknown Source) 00:38:11 at sun.nio.ch.SocketChannelImpl.read(Unknown Source) 00:38:11 at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:136) 00:38:11 at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:306) 00:38:11 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:561) 00:38:11 ... 6 more Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27251) windows slaves disconnect during build
Title: Message Title qingqing zhang commented on JENKINS-27251 Re: windows slaves disconnect during build and the master and slave connection is through JNLP,following is slave node log: JNLP agent connected from /10.140.164.129 <===[JENKINS REMOTING CAPACITY]===>Slave.jar version: 2.53.2 This is a Windows slave ERROR: Connection terminated java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@67f414e7[name=10.140.164.129] at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:628) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.io.IOException: Connection reset by peer at sun.nio.ch.FileDispatcherImpl.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(Unknown Source) at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source) at sun.nio.ch.IOUtil.read(Unknown Source) at sun.nio.ch.SocketChannelImpl.read(Unknown Source) at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:136) at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:306) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:561) ... 6 more Slave successfully connected and online Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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 Srikanth Paramatmuni commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated Thanks for your reply Mark. Prior to installing the git plugins, the same setup worked fine with workaround for sub-module authentication. the commands fired by Git plugin seemed to have changed from earlier version plugin to the latest one. Earlier version plugin: git submodule update --init --recursive --remote # timeout=10 Latest version plugin: git submodule update --init --recursive --remote generators # timeout=10 The command is adding each sub-module separately in the latest plugin. Just wanted to verify if that could be causing any issue. There are 6 sub-modules in our repository and when tried with each of them on Command line also, the same error happens whereas issuing the same command with just "- remote" instead of " -remote " works fine. Thanks Sri Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-32166) TFS plugin doesn't use system proxy
Title: Message Title Yorick Bosman commented on JENKINS-32166 Re: TFS plugin doesn't use system proxy I've made a pull request that fixes this: https://github.com/jenkinsci/tfs-plugin/pull/66 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [bitbucket-plugin] (JENKINS-24989) Support Mercurial repositories
Title: Message Title Christopher Swingler commented on JENKINS-24989 Re: Support Mercurial repositories Nikita Salnikov-Tarnovski appears that it is. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27570) Add environment variable for last successful build commit
Title: Message Title Alex Nederlof commented on JENKINS-27570 Re: Add environment variable for last successful build commit This issue is outdated. GIT_PREVIOUS_SUCCESSFUL_COMMIT has been built: https://github.com/jenkinsci/git-plugin/blob/959bca0d9f92b31ed83c991bdbd6c24c2463daa3/src/main/java/hudson/plugins/git/GitSCM.java#L1183-L1206 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-32218) buildsByBranchName is not set anymore
Title: Message Title Alex Nederlof created an issue Jenkins / JENKINS-32218 buildsByBranchName is not set anymore Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 29/Dec/15 3:03 PM Environment: git-plugin 2.4.1 Jenkins 1.643 Priority: Major Reporter: Alex Nederlof I noticed that GIT_PREVIOUS_SUCCESSFUL_COMMIT was not set anymore on the Job that only builds our master branch. After some digging I found out that since the upgrade from the previous version (I can't find which version that was, is that stored somewhere?) the buildsByBranchName variable in any `build.xml` is not set anymore (it's empty). It is set in other jobs we have, just not this one. This env is critical for us, so I'm going to try to rollback. I'm glad to help track down this problem if possible.
[JIRA] [analysis-collector-plugin] (JENKINS-32216) Need Help Plz on GitHub Integration with Jenkins
Title: Message Title SAYOM GHOSH created an issue Jenkins / JENKINS-32216 Need Help Plz on GitHub Integration with Jenkins Issue Type: Task Assignee: Ulli Hafner Components: analysis-collector-plugin Created: 29/Dec/15 10:47 AM Priority: Minor Reporter: SAYOM GHOSH I am facing some challenges while trying to integrate GitHub with Jenkins. The following are the versions that I am using: Jenkins -1.643 Git client plugin -1.19.1 Git plugin 2.4.1 GitHub API Plugin 1.71 GitHub plugin 1.14.2 GitHub Pull Request Builder 1.29.7 My Git Repository URL is https://github.com/sayom88/SalesTool.git But I am getting the following error: Failed to connect to repository : Error performing command: ls-remote -h https://github.com/sayom88/SalesTool.git HEAD Can anybody help me how to resolve this. Add Comment
[JIRA] [analysis-collector-plugin] (JENKINS-32216) Need Help Plz on GitHub Integration with Jenkins
Title: Message Title Ulli Hafner resolved as Not A Defect Jenkins / JENKINS-32216 Need Help Plz on GitHub Integration with Jenkins Change By: Ulli Hafner Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [_unsorted] (JENKINS-32186) bad links to bitbucket
Title: Message Title Serg Pr updated an issue Jenkins / JENKINS-32186 bad links to bitbucket Can anyone help me? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-remote-trigger-plugin] (JENKINS-32217) parambuild should use the type of parameter
Title: Message Title vissu kumar created an issue Jenkins / JENKINS-32217 parambuild should use the type of parameter Issue Type: Improvement Assignee: Maurice W. Attachments: j1.jpg, j2.jpg Components: parameterized-remote-trigger-plugin Created: 29/Dec/15 3:02 PM Priority: Trivial Reporter: vissu kumar To pass default values to a job in Jenkins using URL we generally use "parambuild" option like below, Ex: https://jenkins/job/Sandbox/parambuild?Test=foo I have 3 input parameters for a job and are of drop_down type. Now i want to pass default values for 2 parameters, so i used the below URL directly to get values selected for 2 parameters, but when i see all three parameters changed as text fields although their type is drop_down, so users has to remember the choices for the third parameter, but instead if the default drop_down type is in place, then Users can easily select from the list we have, Ex URL: https://jenkins/job/Sandbox/parambuild?Test=foo=foo1 Attached images.
[JIRA] [multiple-scms-plugin] (JENKINS-25787) Repository Browser broken with Multiple SCMs plugin
Title: Message Title Nora Mate commented on JENKINS-25787 Re: Repository Browser broken with Multiple SCMs plugin IT IS CRITICAL. I cannot imagine using Jenkins without a chance to browsing changes... can you? After having spent 2-3 hours figuring out that this is not working, I decided not using this plugin at all and use MultiJob instead, with separate subjob to checkout each repo separately. I do not have any better idea. This plugin in this form is useless. And why it is taking 2-3 hours to find out that something is not working: because it has its UI fully enabled, so it did not even occur to me that there is such a limitation. PLEASE: either fix it ASAP OR at least disable the source browsing UI elements WITH a tooltip saying not yet implemented. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-32211) Allow Groovy Method `tokenize` to be used in the sandbox
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32211 Re: Allow Groovy Method `tokenize` to be used in the sandbox Code changed in jenkins User: Andres Rodriguez Path: src/main/resources/org/jenkinsci/plugins/scriptsecurity/sandbox/whitelists/generic-whitelist src/test/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/SandboxInterceptorTest.java http://jenkins-ci.org/commit/script-security-plugin/4d178ecbc8baafb15c460814c2396d9b72b845cb Log: JENKINS-32211 Add `tokenize` to the whitelist. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-32211) Allow Groovy Method `tokenize` to be used in the sandbox
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32211 Re: Allow Groovy Method `tokenize` to be used in the sandbox Code changed in jenkins User: Jesse Glick Path: src/main/resources/org/jenkinsci/plugins/scriptsecurity/sandbox/whitelists/generic-whitelist src/test/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/SandboxInterceptorTest.java http://jenkins-ci.org/commit/script-security-plugin/9534da3bc01e6becec4542089623e51f0f91ecf2 Log: Merge pull request #34 from andresrc/tokenize- JENKINS-32211 JENKINS-32211 Add `tokenize` to the whitelist. Compare: https://github.com/jenkinsci/script-security-plugin/compare/af0b1ae64f36...9534da3bc01e Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-32211) Allow Groovy Method `tokenize` to be used in the sandbox
Title: Message Title Jesse Glick resolved as Fixed Jenkins / JENKINS-32211 Allow Groovy Method `tokenize` to be used in the sandbox Change By: Jesse Glick Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
