[JIRA] (JENKINS-40825) "Pipe not connected" errors when running multiple builds simultaneously
Title: Message Title Jean Mertz commented on JENKINS-40825 Re: "Pipe not connected" errors when running multiple builds simultaneously I'm also interested in this workaround, to see if it fits our setup. Of course also hoping for a permanent solution Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41878) Runtime Exception while using jira trigger plugin in maven job
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41878 Re: Runtime Exception while using jira trigger plugin in maven job Code changed in jenkins User: Wisen Tanasa Path: src/main/groovy/com/ceilfors/jenkins/plugins/jiratrigger/JiraIssueEnvironmentContributingAction.groovy src/main/groovy/com/ceilfors/jenkins/plugins/jiratrigger/JiraTrigger.groovy http://jenkins-ci.org/commit/jira-trigger-plugin/46705cb0bab782a8f4d5b44fdad76d555feb4258 Log: JENKINS-41878 Do not serialize JIRA issue object unnecessarily. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41878) Runtime Exception while using jira trigger plugin in maven job
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41878 Re: Runtime Exception while using jira trigger plugin in maven job Code changed in jenkins User: Wisen Tanasa Path: src/integrationTest/groovy/com/ceilfors/jenkins/plugins/jiratrigger/JiraTriggerIntegrationTest.groovy http://jenkins-ci.org/commit/jira-trigger-plugin/854998eb26ad34f9cfd2e8872e1b1d72709b3cf7 Log: JENKINS-41878 Add failing test. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41878) Runtime Exception while using jira trigger plugin in maven job
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41878 Re: Runtime Exception while using jira trigger plugin in maven job Code changed in jenkins User: Wisen Tanasa Path: src/integrationTest/groovy/com/ceilfors/jenkins/plugins/jiratrigger/JiraTriggerIntegrationTest.groovy http://jenkins-ci.org/commit/jira-trigger-plugin/cec87807099343a33fa651447153bebaba4a8a52 Log: JENKINS-41878 Make test DRY. Compare: https://github.com/jenkinsci/jira-trigger-plugin/compare/ee8d6a55fe5e...cec878070993 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42389) Modifying Folder configuration removes all config files
Title: Message Title Dominik Bartholdi commented on JENKINS-42389 Re: Modifying Folder configuration removes all config files hmm, strange that never made to my mailbox - thanks! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42741) Option "Prepare SonarQube Scanner Environment" missing in Job DSL Plugin
Title: Message Title Erik Nellessen updated an issue Jenkins / JENKINS-42741 Option "Prepare SonarQube Scanner Environment" missing in Job DSL Plugin Change By: Erik Nellessen Labels: job-dsl-plugin sonarqube Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42724) Windows Slaves Plugin: agent is not starting after upgrade to Jenkins 2.50
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42724 Re: Windows Slaves Plugin: agent is not starting after upgrade to Jenkins 2.50 Code changed in jenkins User: Oleg Nenashev Path: content/_data/changelogs/weekly.yml http://jenkins-ci.org/commit/jenkins.io/525a918e2646fcc2a106d363b0c42af4112a7f46 Log: Merge pull request #754 from oleg-nenashev/changelog/JENKINS-42724 Changelog: Reference the JENKINS-42724 regression in Jenkins 2.50 Compare: https://github.com/jenkins-infra/jenkins.io/compare/82fa1dd813e0...525a918e2646 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42389) Modifying Folder configuration removes all config files
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42389 Re: Modifying Folder configuration removes all config files Code changed in jenkins User: imod Path: src/main/java/org/jenkinsci/plugins/configfiles/folder/FolderConfigFileProperty.java http://jenkins-ci.org/commit/config-file-provider-plugin/3a4282fe3ead6de1de1d3b8034646083f1dfc380 Log: [FIXED JENKINS-42389] implement ReconfigurableDescribable to fix data lost when folder gets updated Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42389) Modifying Folder configuration removes all config files
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-42389 Modifying Folder configuration removes all config files Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42794) Retry failed plugin installation
Title: Message Title Lukas Beerens created an issue Jenkins / JENKINS-42794 Retry failed plugin installation Issue Type: Improvement Assignee: Unassigned Components: core Created: 2017/Mar/15 7:53 AM Environment: jenkins-2.50 Priority: Major Reporter: Lukas Beerens If you try to update the plugins it can sometimes happen that you get a timeout exception/error. In this case it would be nice if jenkins would retry to download the plugin. Current behaviour: Throws an error for the single plugin, wants a restart before being able to try to update the plugin again. Improved behaviour: Same behaviour as was implemented in JENKINS-33244. After a failed download retry for 3 times or give an option to retry without needing to actually restart jenkins. Add Comment
[JIRA] (JENKINS-40825) "Pipe not connected" errors when running multiple builds simultaneously
Title: Message Title
Lars Lawoko commented on JENKINS-40825
Re: "Pipe not connected" errors when running multiple builds simultaneously
Esentially the bug is in the "container" step, so if you avoid it this bug should be worked around. Of course if you rely on shared disk of one pod with multiple containers this won't work Instead of having podTemplate(label: 'mypod', containers: [ containerTemplate(name: 'debian', image: 'debian', ttyEnabled: true, command: 'cat') ]) { node('mypod') { container('debian') { stage('stage 1') { sh 'echo hello' sh 'sleep 30' sh 'echo world' } stage('stage 2') { sh 'echo hello' sh 'sleep 30' sh 'echo world' } } } } (pusdocode, might need more tweaking) have: ( note the new image,the name is jnlp ( See https://issues.jenkins-ci.org/browse/JENKINS-40847), and no contianer step) podTemplate(label: 'mypod', containers: [ containerTemplate(name: 'jnlp', image: 'custom/debian-with-jnlp'), ]) { node('mypod') { stage('stage 1') { sh 'echo hello' sh 'sleep 30' sh 'echo world' } stage('stage 2') { sh 'echo hello' sh 'sleep 30' sh 'echo world' } } } Not at work now, but If someone needs a more indepth walkthrough, comment here.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42765) Cannot create bot user with SAML integration
Title: Message Title Ivan Fernandez Calvo resolved as Not A Defect This is a questions not and issue, for questions you could use https://groups.google.com/forum/#!forum/jenkinsci-users in any case take a look of how to use API tokens https://wiki.jenkins-ci.org/display/JENKINS/Authenticating+scripted+clients Jenkins / JENKINS-42765 Cannot create bot user with SAML integration Change By: Ivan Fernandez Calvo Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google
[JIRA] (JENKINS-40825) "Pipe not connected" errors when running multiple builds simultaneously
Title: Message Title
Lars Lawoko edited a comment on JENKINS-40825
Re: "Pipe not connected" errors when running multiple builds simultaneously
Esentially the bug is in the "container" step, so if you avoid it this bug should be worked around. Of course if you rely on shared disk of one pod with multiple containers this won't workInstead of having {code:java} podTemplate(label: 'mypod', containers: [ containerTemplate(name: 'debian', image: 'debian', ttyEnabled: true, command: 'cat')]) \{ node('mypod') \{container('debian') \{ stage('stage 1') \{sh 'echo hello'sh 'sleep 30'sh 'echo world' } stage('stage 2') \{sh 'echo hello'sh 'sleep 30'sh 'echo world' }} }} {code} (pusdocode, might need more tweaking)have: ( note the new image,the name is jnlp ( See https://issues.jenkins-ci.org/browse/JENKINS-40847), and no contianer step) {code:java} podTemplate(label: 'mypod', containers: [ containerTemplate(name: 'jnlp', image: 'custom/debian-with-jnlp'),]) \{ node('mypod') \{ stage('stage 1') \{sh 'echo hello'sh 'sleep 30'sh 'echo world' } stage('stage 2') \{sh 'echo hello'sh 'sleep 30'sh 'echo world' } }} {code} Not at work now, but If someone needs a more indepth walkthrough, comment here.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more
[JIRA] (JENKINS-42608) connection still allocated
Title: Message Title Roman Gurevitch commented on JENKINS-42608 Re: connection still allocated sébastien glon, we have done some modification in the way we are handling the HTTP client connections. Can you please verify those changes resolve your issue? Jenkins Artifactory Plugin. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42778) Unable to run project in firefox browser through Jenkins
Title: Message Title Oleg Nenashev commented on JENKINS-42778 Re: Unable to run project in firefox browser through Jenkins "CFMessagePort: bootstrap_register(): failed 1100 (0x44c) 'Permission denied'". Likely it is about missing permission for your Jenkins account on the agent Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42778) Unable to run project in firefox browser through Jenkins
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-42778 Unable to run project in firefox browser through Jenkins Change By: Oleg Nenashev Component/s: _unsorted Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42795) Bitbucket scan organization folder fails
Title: Message Title Ali Rizwan created an issue Jenkins / JENKINS-42795 Bitbucket scan organization folder fails Issue Type: Bug Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin Created: 2017/Mar/15 8:31 AM Environment: Jenkins 2.50 Bitbucket branch source plguin 2.1.1 Priority: Blocker Reporter: Ali Rizwan The scan organization action fails with the following output: [Wed Mar 15 13:24:11 PKT 2017] Starting organization scan... [Wed Mar 15 13:24:11 PKT 2017] Updating actions... Looking up team details of innexiv-dev... Connecting to https://bitbucket.org using alirizwan/** [Wed Mar 15 13:24:12 PKT 2017] Finished organization scan. Scan took 0.32 sec FATAL: Failed to recompute children of innexiv-dev java.lang.ClassCastException: java.util.ArrayList cannot be cast to com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketHref at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMNavigator.getLink(BitbucketSCMNavigator.java:334) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMNavigator.retrieveActions(BitbucketSCMNavigator.java:307) at jenkins.scm.api.SCMNavigator.fetchActions(SCMNavigator.java:315) at jenkins.branch.OrganizationFolder.computeChildren(OrganizationFolder.java:350) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:255) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:154) at jenkins.branch.OrganizationFolder$OrganizationScan.run(OrganizationFolder.java:850) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model
[JIRA] (JENKINS-42795) Bitbucket scan organization folder fails
Title: Message Title Ali Rizwan updated an issue Jenkins / JENKINS-42795 Bitbucket scan organization folder fails Change By: Ali Rizwan Environment: Jenkins 2.50Bitbucket branch source plguin plugin 2.1.1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42796) Emoji Support in Jenkins
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-42796 Emoji Support in Jenkins Issue Type: Epic Assignee: Unassigned Components: core, other, pipeline Created: 2017/Mar/15 8:34 AM Priority: Minor Reporter: Oleg Nenashev It is not April 1st, but I would like to aggregate the existing tickets in order to redirect anybody asking for that to this ticket. With "feel free to contribute", of course. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42761) CulpritsRecipientProvider is not working as expected
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42761 Re: CulpritsRecipientProvider is not working as expected Code changed in jenkins User: Darío Villadiego Path: src/main/java/hudson/plugins/emailext/plugins/recipients/CulpritsRecipientProvider.java http://jenkins-ci.org/commit/email-ext-plugin/3208a515f52913c996b752fdfa453508ebaa7403 Log: fixing JENKINS-42761 (#152) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42761) CulpritsRecipientProvider is not working as expected
Title: Message Title David van Laatum closed an issue as Fixed merged Jenkins / JENKINS-42761 CulpritsRecipientProvider is not working as expected Change By: David van Laatum Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32891) Project specific avatar doesn't work
Title: Message Title Oleg Nenashev commented on JENKINS-32891 Re: Project specific avatar doesn't work Brady Bouchard It is likely JENKINS-42442. Or feel free to create another ticket and to link it to the JENKINS-42796 EPIC Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42797) Periodic Reincarnation plugin does not work with folders
Title: Message Title Javier Pérez created an issue Jenkins / JENKINS-42797 Periodic Reincarnation plugin does not work with folders Issue Type: Bug Assignee: Unassigned Attachments: image-2017-03-15-09-50-42-342.png, image-2017-03-15-09-53-06-476.png, image-2017-03-15-09-53-53-681.png Components: periodic-reincarnation-plugin Created: 2017/Mar/15 8:56 AM Environment: Tested on Jenkins 1.59 and Jenkins 2.49 Priority: Major Reporter: Javier Pérez Global configuration for Periodic Reincarnation plugin only works for the jobs in the root directory of Jenkins, it does not integrate with folders. Add Comment
[JIRA] (JENKINS-42713) Fresh install Exception at system config
Title: Message Title Bence Nagy commented on JENKINS-42713 Re: Fresh install Exception at system config Hey, Can you give me some hints? I can't even remove SSH Credential Plugin because disabled. So what is next? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42797) Periodic Reincarnation plugin does not work with folders
Title: Message Title Javier Pérez assigned an issue to Yordan Boev Jenkins / JENKINS-42797 Periodic Reincarnation plugin does not work with folders Change By: Javier Pérez Assignee: Yordan Boev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42766) Job with emoji in the name not treated correctly
Title: Message Title Jo Shields commented on JENKINS-42766 Re: Job with emoji in the name not treated correctly This seems to be a mishandling of wide characters, not non-ascii in general. U+0402 CYRILLIC CAPITAL LETTER DJE no problem, U+10398 UGARITIC LETTER THANNA 404. And, again, JIRA throws exceptions on trying to include said characters directly in my bug. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42713) Fresh install Exception at system config
Title: Message Title Oleg Nenashev commented on JENKINS-42713 Re: Fresh install Exception at system config I was unable to reproduce the issue. Could you please provide a full system log starting from the beginning of the startup? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42766) Job with emoji in the name not treated correctly
Title: Message Title Oleg Nenashev commented on JENKINS-42766 Re: Job with emoji in the name not treated correctly Yes, I also noticed the issue in the Bugtracker when I tried to copy-paste a comment from GitHub several days ago. Feel free to create an INFERA ticket for that Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42713) Fresh install Exception at system config
Title: Message Title Bence Nagy commented on JENKINS-42713 Re: Fresh install Exception at system config Hey, I have reinstalled the Jenkins I removed all default plugins. Still Exception: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/D:/apache-tomcat-8.0.32/webapps/jenkins/WEB-INF/lib/jenkins-core-2.32.3.jar!/jenkins/model/Jenkins/configure.jelly:59:84: org.apache.commons.jelly.JellyTagException: jar:file:/D:/apache-tomcat-8.0.32/webapps/jenkins/WEB-INF/lib/jenkins-core-2.32.3.jar!/lib/form/section.jelly:48:21: org.apache.commons.jelly.JellyTagException: jar:file:/D:/apache-tomcat-8.0.32/webapps/jenkins/WEB-INF/lib/jenkins-core-2.32.3.jar!/lib/form/entry.jelly:77:23: java.lang.StackOverflowError at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) 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:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:292) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:86) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(Ch
[JIRA] (JENKINS-42798) SVN update failure causes fresh checkout
Title: Message Title Beast Mode created an issue Jenkins / JENKINS-42798 SVN update failure causes fresh checkout Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 2017/Mar/15 9:39 AM Priority: Major Reporter: Beast Mode We sometimes face an issue in Jenkins that when an svn update step fails it locks the workspace, so when the next build is run it notices this and decides to wipe out the workspace and check out a new one, which takes enormous amount of time to build it again. -- [02:38:31] - Update dev Success build fororg.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder@1cae7e0 Updating http://repos/wss/soseco/dev at revision '2017-03-08T18:35:59.190 +0530' At revision 311237 Updating http://repos/wss/soseco/dev at revision '2017-03-08T18:35:59.190 +0530' Workspace appear to be locked, so getting a fresh workspace Cleaning local Directory ../../../src/dev Checking out http://repos/wss/soseco/dev at revision '2017-03-08T18:35:59.190 +0530' -- Instead of getting a fresh workspace, it should simply fail the build. And then the user can check why it happened and do svn cleanup.
[JIRA] (JENKINS-42799) Add support for Cloud Statistics Plugin
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-42799 Add support for Cloud Statistics Plugin Issue Type: Improvement Assignee: Azure DevOps Components: azure-vm-agents-plugin Created: 2017/Mar/15 9:41 AM Priority: Minor Reporter: Jo Shields https://github.com/jenkinsci/cloud-stats-plugin It would be nice for Azure VMs to get reported by this plugin.I'd be interested in some of the statistics cloud-stats-plugin tracks Add Comment This message was sent by Atlassian JIRA (v7.3.
[JIRA] (JENKINS-41587) Multijob : Phase job blocks if MultiJob parent comes in the queue
Title: Message Title Gaurav Joshi updated an issue Jenkins / JENKINS-41587 Multijob : Phase job blocks if MultiJob parent comes in the queue Change By: Gaurav Joshi I have a multi job job say 'A', 'A' defines three phases,Phase 1 - Run job 'B'Phase 2 - Run job 'C','D','E'Phase 3 - Run job 'F' - clean up jobI am facing a problem wherein when 'B' runs, it sometime times blocks if 'A' comes back in build queue (due to scm change). So this becomes a deadlock for me, 'A' build 1 runs which builds 'B' build 1. However, 'A' build 2 comes in pipeline (due to scm change or upstream project change). 'B' waits endlessly since 'A' build 2 is in waiting queue.'A' build 1 -waits for--> 'B' build 1 ---blocked by ---> 'A' build 2 in build queueSimilar issue reported earlier by different user is [ https://groups.google.com/forum/#!topic/jenkinsci-users/jkFWsiw6V0c ] And Please help.Thanks Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are
[JIRA] (JENKINS-40548) Pipeline resume not possible after restart caused by java.lang.ClassNotFoundException when loading (load) main pipeline script
Title: Message Title UHP commented on JENKINS-40548 Re: Pipeline resume not possible after restart caused by java.lang.ClassNotFoundException when loading (load) main pipeline script This is quite major for us since we cannot restart jenkins server without losing all states of waiting builds. Is there any feedback on this? It looks quite similiar to https://issues.jenkins-ci.org/browse/JENKINS-31570 even if there it is connected to a CloudBees feature which we are not using. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34581) Please add support for Pipelines to the Powershell plugin
Title: Message Title Yogesh Bhole commented on JENKINS-34581 Re: Please add support for Pipelines to the Powershell plugin Thanks Gabriel Loewen for the support. Hoping powershell support will be available in Jenkins pipeline soon. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28499) tcpSlaveAgentListener not found
Title: Message Title Andreas Tscharner commented on JENKINS-28499 Re: tcpSlaveAgentListener not found No. I was not clear enough before: I forgot the double quotes here in the issue tracker; on the system they have always been there... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42800) Update plugin parent pom to be compatible with JaCoCo jenkins plugin
Title: Message Title Alvaro Lobato created an issue Jenkins / JENKINS-42800 Update plugin parent pom to be compatible with JaCoCo jenkins plugin Issue Type: Task Assignee: Alvaro Lobato Components: plugin-pom Created: 2017/Mar/15 10:36 AM Priority: Minor Reporter: Alvaro Lobato The JaCoCo plugin is displaying empty coverage reports with the current plugin parent pom. According to this issue JENKINS-28652 maven plugin should be updated to >0.7.5 to fix the issue. Add Comment This message was sen
[JIRA] (JENKINS-34433) pipeline lock does not retry
Title: Message Title Antonio Muñiz commented on JENKINS-34433 Re: pipeline lock does not retry This may be fixed by https://github.com/jenkinsci/lockable-resources-plugin/pull/46 Needs checking. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42800) Update plugin parent pom to be compatible with JaCoCo jenkins plugin
Title: Message Title Alvaro Lobato started work on JENKINS-42800 Change By: Alvaro Lobato Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42801) Can't access "include" or "list" in parallel test executor. Security exceptions thrown.
Title: Message Title g hs1 created an issue Jenkins / JENKINS-42801 Can't access "include" or "list" in parallel test executor. Security exceptions thrown. Issue Type: Bug Assignee: Unassigned Components: parallel-test-executor-plugin Created: 2017/Mar/15 10:41 AM Environment: Win2008 R2. Jenkins 2.49. Latest plugins. Priority: Critical Reporter: g hs1 Jenkins throws security exceptions when trying to access "split.includes" or "split.list", as described in examples such as [this|https://jenkins.io/blog/2016/06/16/parallel-test-executor-plugin/.] There's no apparent way around the exceptions and it's not clear how to make it work in other ways. Add Comment
[JIRA] (JENKINS-42775) NodeJS Plugin - Unresolvable nodeJS installer for version in Windows i386
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-42775 NodeJS Plugin - Unresolvable nodeJS installer for version in Windows i386 Change By: Nikolas Falco Assignee: Nikolas Falco Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42581) Introduce reIndex for Multibranch Pipelines
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42581 Re: Introduce reIndex for Multibranch Pipelines Code changed in jenkins User: Evaristo Gutiérrez Path: src/test/java/plugins/WorkflowMultibranchTest.java http://jenkins-ci.org/commit/acceptance-test-harness/033f31d5bb24f62085a21e54391a24ce39a4ef99 Log: JENKINS-42581 Change also assertion for scan action. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41416) "Scan Organisation" is a verb - but this performs no action.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41416 Re: "Scan Organisation" is a verb - but this performs no action. Code changed in jenkins User: Evaristo Gutiérrez Path: src/main/java/org/jenkinsci/test/acceptance/po/WorkflowMultiBranchJob.java http://jenkins-ci.org/commit/acceptance-test-harness/ba4dd2f6562672e7919f6db496d8854b3cc5a0e5 Log: JENKINS-42581 Adapt to changes in JENKINS-41416. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42581) Introduce reIndex for Multibranch Pipelines
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42581 Re: Introduce reIndex for Multibranch Pipelines Code changed in jenkins User: Evaristo Gutiérrez Path: src/main/java/org/jenkinsci/test/acceptance/po/Folder.java src/main/java/org/jenkinsci/test/acceptance/po/WorkflowMultiBranchJob.java src/test/java/plugins/WorkflowMultibranchTest.java http://jenkins-ci.org/commit/acceptance-test-harness/2756ba78e2f925a130e3e6d2625d581f8aeaa56e Log: JENKINS-42581 Introduce method to trigger a re-index. Also contemplate that a folder might not have a new view tab. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42581) Introduce reIndex for Multibranch Pipelines
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42581 Re: Introduce reIndex for Multibranch Pipelines Code changed in jenkins User: Oliver Gondža Path: src/main/java/org/jenkinsci/test/acceptance/po/Folder.java src/main/java/org/jenkinsci/test/acceptance/po/WorkflowMultiBranchJob.java src/test/java/plugins/WorkflowMultibranchTest.java http://jenkins-ci.org/commit/acceptance-test-harness/cabefea57705baac441e341739b3b3a4082dc8d7 Log: Merge pull request #282 from varyvol/JENKINS-42581 JENKINS-42581 Introduce method to trigger a re-index Compare: https://github.com/jenkinsci/acceptance-test-harness/compare/73a7bdca25b3...cabefea57705 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42581) Introduce reIndex for Multibranch Pipelines
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42581 Re: Introduce reIndex for Multibranch Pipelines Code changed in jenkins User: Evaristo Gutiérrez Path: src/main/java/org/jenkinsci/test/acceptance/po/WorkflowMultiBranchJob.java http://jenkins-ci.org/commit/acceptance-test-harness/ba4dd2f6562672e7919f6db496d8854b3cc5a0e5 Log: JENKINS-42581 Adapt to changes in JENKINS-41416. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42581) Introduce reIndex for Multibranch Pipelines
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42581 Re: Introduce reIndex for Multibranch Pipelines Code changed in jenkins User: Evaristo Gutiérrez Path: src/main/java/org/jenkinsci/test/acceptance/po/Folder.java http://jenkins-ci.org/commit/acceptance-test-harness/be0ea7fbb695a5d7239dc70e285947ae2a79c6e0 Log: JENKINS-42581 Add comment clarifying first view. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42775) NodeJS Plugin - Unresolvable nodeJS installer for version in Windows i386
Title: Message Title
Nikolas Falco updated an issue
Jenkins / JENKINS-42775
NodeJS Plugin - Unresolvable nodeJS installer for version in Windows i386
Change By:
Nikolas Falco
Using the "Install automatically" feature of the plugin in a x86 Windows environment triggers the error: ``` FATAL: Unresolvable nodeJS installer for version=7.7.2, cpu=i386, platform=WINDOWS java.lang.IllegalArgumentException: Unresolvable nodeJS installer for version=7.7.2, cpu=i386, platform=WINDOWS at jenkins.plugins.nodejs.tools.pathresolvers.LatestInstallerPathResolver.resolvePathFor(LatestInstallerPathResolver.java:63) at jenkins.plugins.nodejs.tools.NodeJSInstaller.getInstallable(NodeJSInstaller.java:110) at jenkins.plugins.nodejs.tools.NodeJSInstaller.performInstallation(NodeJSInstaller.java:125) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:72) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:109) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:206) at jenkins.plugins.nodejs.tools.NodeJSInstallation.forNode(NodeJSInstallation.java:94) at jenkins.plugins.nodejs.NodeJSBuildWrapper.setUp(NodeJSBuildWrapper.java:110) at jenkins.tasks.SimpleBuildWrapper.setUp(SimpleBuildWrapper.java:145) at hudson.model.Build$BuildExecution.doRun(Build.java:156) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1728) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) ``` In the plugin code, more specifically in the "LatestInstallerPathResolver.java" file:switch (cpu) \{ case i386: if (NodeJSVersion.parseVersion(version).compareTo(new NodeJSVersion(4, 0, 0)) >= 0) \{ throw new IllegalArgumentException("Unresolvable nodeJS installer for version=" + version + ", cpu=" + cpu.name() + ", platform=" + platform.name()); } arch = "x86"; break;Reading the code, if the NodeJS version is greater then 4.0.0, the plugin throws a error, so x86 users only can use Node on versions 0.X.X.
Add Comment
[JIRA] (JENKINS-42775) NodeJS Plugin - Unresolvable nodeJS installer for version in Windows i386
Title: Message Title
Nikolas Falco updated an issue
Jenkins / JENKINS-42775
NodeJS Plugin - Unresolvable nodeJS installer for version in Windows i386
Change By:
Nikolas Falco
Using the "Install automatically" feature of the plugin in a x86 Windows environment triggers the error: ``` {noformat} FATAL: Unresolvable nodeJS installer for version=7.7.2, cpu=i386, platform=WINDOWS java.lang.IllegalArgumentException: Unresolvable nodeJS installer for version=7.7.2, cpu=i386, platform=WINDOWS at jenkins.plugins.nodejs.tools.pathresolvers.LatestInstallerPathResolver.resolvePathFor(LatestInstallerPathResolver.java:63) at jenkins.plugins.nodejs.tools.NodeJSInstaller.getInstallable(NodeJSInstaller.java:110) at jenkins.plugins.nodejs.tools.NodeJSInstaller.performInstallation(NodeJSInstaller.java:125) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:72) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:109) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:206) at jenkins.plugins.nodejs.tools.NodeJSInstallation.forNode(NodeJSInstallation.java:94) at jenkins.plugins.nodejs.NodeJSBuildWrapper.setUp(NodeJSBuildWrapper.java:110) at jenkins.tasks.SimpleBuildWrapper.setUp(SimpleBuildWrapper.java:145) at hudson.model.Build$BuildExecution.doRun(Build.java:156) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1728) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) ``` {noformat} In the plugin code, more specifically in the "LatestInstallerPathResolver.java" file: {code:java} switch (cpu) \{ case i386: if (NodeJSVersion.parseVersion(version).compareTo(new NodeJSVersion(4, 0, 0)) >= 0) \{ throw new IllegalArgumentException("Unresolvable nodeJS installer for version=" + version + ", cpu=" + cpu.name() + ", platform=" + platform.name()); } arch = "x86"; break; {code} Reading the code, if the NodeJS version is greater then 4.0.0, the plugin throws a error, so x86 users only can use Node on versions 0.X.X.
Add Comment
[JIRA] (JENKINS-42801) Can't access "include" or "list" in parallel test executor. Security exceptions thrown.
Title: Message Title g hs1 updated an issue Jenkins / JENKINS-42801 Can't access "include" or "list" in parallel test executor. Security exceptions thrown. Change By: g hs1 Jenkins throws security exceptions when trying to access "split.includes" or "split.list", as described in examples such as [this|[https://jenkins.io/blog/2016/06/16/parallel-test-executor-plugin/] . ] . There's no apparent way around the exceptions and it's not clear how to make it work in other ways. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42785) Parameterized Pipeline Projects have their Build Triggers unset after each build
Title: Message Title
Christopher Orr commented on JENKINS-42785
Re: Parameterized Pipeline Projects have their Build Triggers unset after each build
Is this specific to Declarative Pipelines, i.e. in the style you've written above, starting with pipeline {? Just wondering whether this should be reassigned to the pipeline-model-definition component.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42801) Can't access "include" or "list" in parallel test executor. Security exceptions thrown.
Title: Message Title g hs1 updated an issue Jenkins / JENKINS-42801 Can't access "include" or "list" in parallel test executor. Security exceptions thrown. Change By: g hs1 Jenkins throws security exceptions when trying to access "split.includes" or "split.list", as described in examples such as [this| [ https://jenkins.io/blog/2016/06/16/parallel-test-executor-plugin/] ] .There's no apparent way around the exceptions and it's not clear how to make it work in other ways. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41828) wget of large artifacts causes exception
Title: Message Title Oleg Danilov commented on JENKINS-41828 Re: wget of large artifacts causes exception Oleg Nenashev, I just reproduced this issue on our setup as well. Note, that there is even more dangerous issue which is related to this one - #39909 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42581) Introduce reIndex for Multibranch Pipelines
Title: Message Title Evaristo Gutierrez updated JENKINS-42581 Jenkins / JENKINS-42581 Introduce reIndex for Multibranch Pipelines Change By: Evaristo Gutierrez Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41987) Cryptic error message when loading JnlpSlaveAgentProtocol4
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-41987 Cryptic error message when loading JnlpSlaveAgentProtocol4 Change By: Oliver Gondža Labels: 2.46.1-fixed diagnostics jnlp lts-candidate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33358) Groovy and PermGen memory leak
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-33358 Groovy and PermGen memory leak Change By: Oliver Gondža Labels: 2.46.1-rejected groovy lts-candidate memory-leak Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42795) Bitbucket scan organization folder fails
Title: Message Title Auke Noppe commented on JENKINS-42795 Re: Bitbucket scan organization folder fails I've downgraded to version 2.0.2 which resolves the error. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33358) Groovy and PermGen memory leak
Title: Message Title Oliver Gondža commented on JENKINS-33358 Re: Groovy and PermGen memory leak I am rejecting this from 2.46.1 as agreed. There is first issue that is suspected to be caused by this change: JENKINS-42637. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23349) Views with a name that start with an emoji are not accessible
Title: Message Title Christopher Orr commented on JENKINS-23349 Re: Views with a name that start with an emoji are not accessible I can reproduce in Jenkins 2.32.3 with all sorts of items: view, freestyle job, folder. I created items called "X robofolder" etc., where "X" is a robot face (U+1F916). JIRA throws a 500 error and doesn't accept this comment if I use the actual emoji character… The items do get created, and displayed on the home page, but the emoji character is stripped from the URL, so clicking through results in a 404. It seems to happen as soon as you go >= U+1 (which has a 4-byte rather than 3-byte UTF-8 representation). That character does not work in an item name, but U+FE6B does. The character can be anywhere in the name — it doesn't have to be at the start, it will be stripped out regardless. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22692) Jenkins Windows-Slave throwing exception on shutdown causes connection reset issues
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-22692 Jenkins Windows-Slave throwing exception on shutdown causes connection reset issues Change By: Oleg Nenashev Labels: lts 2.46.1 - candidate rejected remoting winsw Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23349) Item names containing an emoji are not accessible
Title: Message Title Christopher Orr updated an issue Jenkins / JENKINS-23349 Item names containing an emoji are not accessible Change By: Christopher Orr Summary: Views with a name that start with Item names containing an emoji are not accessible Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22692) Jenkins Windows-Slave throwing exception on shutdown causes connection reset issues
Title: Message Title Oleg Nenashev commented on JENKINS-22692 Re: Jenkins Windows-Slave throwing exception on shutdown causes connection reset issues Rejecting from LTS 2.46.1 due to the JENKINS-42744 regression reported to 2.50 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42766) Job with emoji in the name not treated correctly
Title: Message Title Christopher Orr commented on JENKINS-42766 Re: Job with emoji in the name not treated correctly I think this is a duplicate of JENKINS-23349, and the JIRA brokenness issue is likely INFRA-1093. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42164) Exceptions during Jenkins#cleanup() should not block the restart logic
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-42164 Exceptions during Jenkins#cleanup() should not block the restart logic Change By: Oliver Gondža Labels: lts 2.46.1 - candidate fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41864) Illegal dates for cron entry cause 100% cpu
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-41864 Illegal dates for cron entry cause 100% cpu Change By: Oliver Gondža Labels: lts 2.46.1 - candidate fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42800) Update plugin parent pom to be compatible with JaCoCo jenkins plugin
Title: Message Title Alvaro Lobato updated JENKINS-42800 Jenkins / JENKINS-42800 Update plugin parent pom to be compatible with JaCoCo jenkins plugin Change By: Alvaro Lobato Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27094) WriteFileStep ignores encoding
Title: Message Title Daniel Butler commented on JENKINS-27094 Re: WriteFileStep ignores encoding PR: https://github.com/jenkinsci/workflow-basic-steps-plugin/pull/38 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32820) Queue is not persisted on Safe Restart when Jenkins is installed as Windows Service (clean up is not performed)
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-32820 Queue is not persisted on Safe Restart when Jenkins is installed as Windows Service (clean up is not performed) Change By: Oliver Gondža Labels: lts 2.46.1 - candidate fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41756) Indecently translated main menu items
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-41756 Indecently translated main menu items Change By: Oliver Gondža Labels: lts 2.46.1 - candidate fixed translation Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40088) JSON serialization should not fail if a plugins action failed to serialize
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-40088 JSON serialization should not fail if a plugins action failed to serialize Change By: Oliver Gondža Labels: blueocean lts-candidate rest robustness stapler Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40088) JSON serialization should not fail if a plugins action failed to serialize
Title: Message Title Oliver Gondža commented on JENKINS-40088 Re: JSON serialization should not fail if a plugins action failed to serialize Removing lts-candidate label as the core part seems done and made it to 2.46, witch is the LTS baseline. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42670) Windows Service Installer may leak File descriptors
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-42670 Windows Service Installer may leak File descriptors Change By: Oliver Gondža Labels: leak lts 2.46.1 - candidate fixed leak Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42802) Add a friendly message for missing deployment policy
Title: Message Title André Duarte created an issue Jenkins / JENKINS-42802 Add a friendly message for missing deployment policy Issue Type: Improvement Assignee: Raphael CHAUMIER Components: weblogic-deployer-plugin Created: 2017/Mar/15 11:59 AM Labels: weblogic-deployer-plugin-3.6 Priority: Minor Reporter: André Duarte Hi, I'd like to suggest a friendly message for missing deployment policy on weblogic-deployer-plugin. The build was started by an SCM change, and the message was: [WeblogicDeploymentPlugin] - Current build causes (hudson.triggers.SCMTrigger$SCMTriggerCause@3) do not contain any of the configured (org.jenkinsci.plugins.deploy.weblogic.data.policy.UserIdCauseDeploymentPolicy@47408485). The plugin execution is disabled. [INFO] [INFO] DEPLOYMENT UNSTABLE [INFO] Printing the objects instances .toString() is not so friendly. I'd like to suggest something like: [WeblogicDeploymentPlugin] - Current build cause(s) "SCMTriggerCause" do(es) not contain any of the configured "Deployment Policy". The plugin execution is disabled. The message could also explain how to setup the Deployment Policy, e.g: [WeblogicDeploymentPlugin] - Verify at "Post-build Actions > D
[JIRA] (JENKINS-42802) Add a friendly message for missing deployment policy
Title: Message Title
André Duarte updated an issue
Jenkins / JENKINS-42802
Add a friendly message for missing deployment policy
Change By:
André Duarte
Hi, I'd like to suggest a friendly message for missing deployment policy on weblogic-deployer-plugin.The build was started by an SCM change, and the message was:{quote}[WeblogicDeploymentPlugin] - Current build causes (hudson.triggers.SCMTrigger$SCMTriggerCause@3) do not contain any of the configured (org.jenkinsci.plugins.deploy.weblogic.data.policy.UserIdCauseDeploymentPolicy@47408485). The plugin execution is disabled. [INFO] [INFO] DEPLOYMENT UNSTABLE [INFO] {quote}Printing the objects instances .toString() is not so friendly. I'd like to suggest something like:{quote}[WeblogicDeploymentPlugin] - Current build cause(s) "SCMTriggerCause" do(es) not contain any of the configured "Deployment Policy Policies ". The plugin execution is disabled.{quote}The message could also explain how to setup the Deployment Policy, e.g:{quote}[WeblogicDeploymentPlugin] - Verify at "Post-build Actions > Deploy the artifact to any Weblogic environments > Deployment policies" if all the appropriate policies are applied according to enabled build triggers.{quote}#My Jenkins:Jenkins:2.32.3 weblogic-deployer-plugin:3.6
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42802) Add a friendly message for missing deployment policy
Title: Message Title André Duarte updated an issue Jenkins / JENKINS-42802 Add a friendly message for missing deployment policy Change By: André Duarte Attachment: weblogic-deployer-message.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42803) Configuring two jira instances fails
Title: Message Title Peter Lord created an issue Jenkins / JENKINS-42803 Configuring two jira instances fails Issue Type: Bug Assignee: Unassigned Components: jira-plugin Created: 2017/Mar/15 12:06 PM Priority: Blocker Reporter: Peter Lord We have two JIRA instances - lets call them A and B. If we configure A in jenkins then all is well. Likewise if we configure B all is also okay. However if we configure A and B ( with separate issue patterns ) then both fail - for example mentions of JIRA issues in changes are not highlighted. Let me know what debug information is useful. Thanks. Add Comment
[JIRA] (JENKINS-32820) Queue is not persisted on Safe Restart when Jenkins is installed as Windows Service (clean up is not performed)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32820 Re: Queue is not persisted on Safe Restart when Jenkins is installed as Windows Service (clean up is not performed) Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/WebAppMain.java core/src/main/java/hudson/lifecycle/SolarisSMFLifecycle.java core/src/main/java/hudson/lifecycle/UnixLifecycle.java core/src/main/java/hudson/lifecycle/WindowsServiceLifecycle.java http://jenkins-ci.org/commit/jenkins/5f655a59b6d263061d6c5c1d05ac8d5d1d1d391f Log: Merge pull request #2746 from oleg-nenashev/bug/JENKINS-32820 [JENKINS-32820, JENKINS-42164] - Windows service restart does not retain the build queue (cherry picked from commit 4ab693846ca7a4aa112959a2e92688c3fb9122c3) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42164) Exceptions during Jenkins#cleanup() should not block the restart logic
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42164 Re: Exceptions during Jenkins#cleanup() should not block the restart logic Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/WebAppMain.java core/src/main/java/hudson/lifecycle/SolarisSMFLifecycle.java core/src/main/java/hudson/lifecycle/UnixLifecycle.java core/src/main/java/hudson/lifecycle/WindowsServiceLifecycle.java http://jenkins-ci.org/commit/jenkins/5f655a59b6d263061d6c5c1d05ac8d5d1d1d391f Log: Merge pull request #2746 from oleg-nenashev/bug/JENKINS-32820 [JENKINS-32820, JENKINS-42164] - Windows service restart does not retain the build queue (cherry picked from commit 4ab693846ca7a4aa112959a2e92688c3fb9122c3) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41987) Cryptic error message when loading JnlpSlaveAgentProtocol4
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41987 Re: Cryptic error message when loading JnlpSlaveAgentProtocol4 Code changed in jenkins User: Jesse Glick Path: core/src/main/java/jenkins/slaves/JnlpSlaveAgentProtocol4.java http://jenkins-ci.org/commit/jenkins/e2a8c0efd149b4e08bf1c61768f2010fa9dfe8bc Log: JENKINS-41987 Improved message. (cherry picked from commit dbf5efa6ae60c30d00afca61d3fd24f56f2c860c) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41864) Illegal dates for cron entry cause 100% cpu
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41864 Re: Illegal dates for cron entry cause 100% cpu Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/scheduler/CronTab.java core/src/main/java/hudson/scheduler/RareOrImpossibleDateException.java core/src/main/java/hudson/triggers/TimerTrigger.java core/src/main/resources/hudson/triggers/Messages.properties http://jenkins-ci.org/commit/jenkins/933a4785afa03354055c6d12a8bb1ce3b8e43b0a Log: [FIX JENKINS-41864] Add warning for rare dates Previously, impossible dates caused 100% CPU while Jenkins was trying to find the previous/next occurrence of the date. (cherry picked from commit 6e5225c06b45a3e196c8647dd30275234e57a54c) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42429) Cannot view dependency of jobs
Title: Message Title Jochen A. Fürbacher assigned an issue to Jochen A. Fürbacher Jenkins / JENKINS-42429 Cannot view dependency of jobs Change By: Jochen A. Fürbacher Assignee: wolfs Jochen A. Fürbacher Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42429) Cannot view dependency of jobs
Title: Message Title Jochen A. Fürbacher assigned an issue to wolfs Jenkins / JENKINS-42429 Cannot view dependency of jobs Change By: Jochen A. Fürbacher Assignee: Jochen A. Fürbacher wolfs Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34547) Make WorkflowJob.concurrentBuild into a JobProperty
Title: Message Title Stefan Cordes commented on JENKINS-34547 Re: Make WorkflowJob.concurrentBuild into a JobProperty Moving properties ([ buildDiscarder(logRotator(numToKeepStr: '5')) , disableConcurrentBuilds() ]); to the very first line does not hinder 2 feature branches to build in parallel (as reported in JENKINS-35359) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42429) Cannot view dependency of jobs
Title: Message Title
Jochen A. Fürbacher commented on JENKINS-42429
Re: Cannot view dependency of jobs
I noticed, that this issue occures, if we use special characters in display names of projects, such as ampersands and that name get put in the label parameter of a diagraph node. Then dot also throws an error, if I manually run dot with the generated graph.vz file:
Error: not well-formed (invalid token) in line 1
... "center" href="" class="code-quote" style="color: #009100">"http://myjenkinsinstance/job/MyJob/" >X & Y ...
in label of node X & Y
When I manually escape the ampersand character in the generated graph.vz file ("&" -> "&"), then dot can gerate a valid image. I think, there's some problem with special characters that should get escaped. Maybe in this method.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34547) Make WorkflowJob.concurrentBuild into a JobProperty
Title: Message Title Peter Leibiger commented on JENKINS-34547 Re: Make WorkflowJob.concurrentBuild into a JobProperty Stefan Cordes AFAIK two feature branches are two different jobs with two different workspaces. You can not prevent concurrent builds this way. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42429) Cannot view dependency of jobs
Title: Message Title Vikas Kumar commented on JENKINS-42429 Re: Cannot view dependency of jobs Hey Jochen A. Fürbacher, This isn't working for me even when using jobs names without any special characters. Have a look at the below screenshot. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42429) Cannot view dependency of jobs
Title: Message Title Vikas Kumar updated an issue Jenkins / JENKINS-42429 Cannot view dependency of jobs Change By: Vikas Kumar Attachment: 2017-03-15_23-35-45.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42429) Cannot view dependency of jobs
Title: Message Title
Jochen A. Fürbacher edited a comment on JENKINS-42429
Re: Cannot view dependency of jobs
I noticed, that this issue occures, if we use special characters in display names of projects, such as ampersands and that name get put in the label parameter of a diagraph node. Then dot also throws an error, if I manually run dot with the generated graph.vz file: {code:java}Error: not well-formed (invalid token) in line 1... X & Y ...in label of node X & Y{code} When I manually escape the ampersand character in the generated graph.vz file ("&" -> "&"), then dot can gerate a valid image.I think, there's some problem with special characters that should get escaped. Maybe in [this|https://github.com/jenkinsci/depgraph-view-plugin/blob/master/src/main/java/hudson/plugins/depgraph_view/model/display/DotStringGenerator.java#L139-L142] method.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42429) Cannot view dependency of jobs
Title: Message Title
Jochen A. Fürbacher edited a comment on JENKINS-42429
Re: Cannot view dependency of jobs
I noticed, that this issue occures, if we use special characters in display names of projects, such as ampersands and that name get put in the label parameter of a diagraph node. Then dot also throws an error, if I manually run dot with the generated graph.vz file: {code:java}Error: not well-formed (invalid token) in line 1... X & Y ...in label of node X & Y{code} When I manually escape the ampersand character in the generated graph.vz file ("&" -> "&") , then dot can gerate a valid image.I think, there's some problem with special characters that should get escaped. Maybe in [this|https://github.com/jenkinsci/depgraph-view-plugin/blob/master/src/main/java/hudson/plugins/depgraph_view/model/display/DotStringGenerator.java#L139-L142] method.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42429) Cannot view dependency of jobs
Title: Message Title Vikas Kumar edited a comment on JENKINS-42429 Re: Cannot view dependency of jobs Hey [~jochenafuerbacher], This isn't It working for me even when using jobs names without any special characters. Have a look at the below screenshot. !2017-03-15_23-35-45.png|thumbnail! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42636) During pipeline stage build time reported incorrectly
Title: Message Title Sam Van Oort commented on JENKINS-42636 Re: During pipeline stage build time reported incorrectly Vivek Pandey Why is the first node showing up with a null start time? (Specifically, do you have the node XML file?) The only nodes that should ever have a null start time are: (a) FlowStartNodes and (b) Nodes that have been freshly generated and are about to begin execution, which is to say that the start time reflects the current system time, which is what this logic is intended to handle Anything else points to an error deeper in the stack, probably in serialization/deserialization Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42429) Cannot view dependency of jobs
Title: Message Title Jochen A. Fürbacher commented on JENKINS-42429 Re: Cannot view dependency of jobs What happens, if you try to execute the graph.vz file, that you can download on the dependency view page of your project, manually on command line? E.g.: dot -Tpng graph.vz > graph.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42034) Reactive Reference parameter with Formated HTML loses script section when binding to other build parameters
Title: Message Title Ioannis Moutsatsos commented on JENKINS-42034 Re: Reactive Reference parameter with Formated HTML loses script section when binding to other build parameters Currently away for business. I'll review it when I get back. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42429) Cannot view dependency of jobs
Title: Message Title Vikas Kumar commented on JENKINS-42429 Re: Cannot view dependency of jobs I couldn't find this file anywhere on my Alpine box. ~ # find / -iname *.vz ~ # Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22506) HP ALM Tools Plug-In Displays ALM URL to View Test Results Rather Than Showing Reporter Details
Title: Message Title Keith Jacobs commented on JENKINS-22506 Re: HP ALM Tools Plug-In Displays ALM URL to View Test Results Rather Than Showing Reporter Details Sounds good. Yeah, the details have always displayed for the build type "Execute HP functional tests from HP ALM". The newer build type for Lab Management has never displayed the details. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42429) Cannot view dependency of jobs
Title: Message Title Vikas Kumar updated an issue Jenkins / JENKINS-42429 Cannot view dependency of jobs Change By: Vikas Kumar Attachment: graph.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42429) Cannot view dependency of jobs
Title: Message Title
Vikas Kumar edited a comment on JENKINS-42429
Re: Cannot view dependency of jobs
I couldn't find this file anywhere on my Alpine box. {noformat}~ # find / -iname *.vz~ #{noformat} I have created one now using my Jenkins graph view http://depgraph-view/graph.gv{noformat}/ # cat graph.vzdigraph {node [shape=box, style=rounded];subgraph clusterMain {"petertest" [href=""];"vikastest" [href=""];color=invis;}subgraph clusterStandalone {color=invis;}"petertest" -> "vikastest" [ color=black ] ;}/ #/ # dot -Tpng graph.vz > graph.pngFontconfig warning: ignoring C.UTF-8: not a valid language tag/ # ls graph.pnggraph.png/ # {noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42429) Cannot view dependency of jobs
Title: Message Title
Vikas Kumar edited a comment on JENKINS-42429
Re: Cannot view dependency of jobs
I couldn't find this file anywhere on my Alpine box.{noformat}~ # find / -iname *.vz~ #{noformat}I have created one now using my Jenkins graph view http://depgraph-view/graph.gv Pls find attached !graph.png|thumbnail! {noformat}/ # cat graph.vzdigraph {node [shape=box, style=rounded];subgraph clusterMain {"petertest" [href=""];"vikastest" [href=""];color=invis;}subgraph clusterStandalone {color=invis;}"petertest" -> "vikastest" [ color=black ] ;}/ #/ # dot -Tpng graph.vz > graph.pngFontconfig warning: ignoring C.UTF-8: not a valid language tag/ # ls graph.pnggraph.png/ # {noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42429) Cannot view dependency of jobs
Title: Message Title
Vikas Kumar edited a comment on JENKINS-42429
Re: Cannot view dependency of jobs
I couldn't find this file anywhere on my Alpine box.{noformat}~ # find / -iname *.vz~ #{noformat}I have created one now using my Jenkins graph view http://depgraph-view/graph.gv Pls find attached !graph.png|thumbnail! {noformat}/ # cat graph.vzdigraph {node [shape=box, style=rounded];subgraph clusterMain {"petertest" [href=""];"vikastest" [href=""];color=invis;}subgraph clusterStandalone {color=invis;}"petertest" -> "vikastest" [ color=black ] ;}/ #/ # dot -Tpng graph.vz > graph.pngFontconfig warning: ignoring C.UTF-8: not a valid language tag/ # ls graph.pnggraph.png/ # {noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42804) Windows (x86) - Can't install >= v4.0.0
Title: Message Title Jared Beach created an issue Jenkins / JENKINS-42804 Windows (x86) - Can't install >= v4.0.0 Issue Type: Bug Assignee: Unassigned Components: nodejs-plugin Created: 2017/Mar/15 1:21 PM Environment: Jenkins ver. 2 NodeJS Plugin Priority: Minor Reporter: Jared Beach I am trying to use the NodeJS plugin on an x86 Windows machine and I get the error thrown on this line: java.lang.IllegalArgumentException Unresolvable nodeJS installer for version=4.0.0, cpu=i386, platform=WINDOWS The logic which throws this error is `NodeJSVersion.parseVersion(version).compareTo(new NodeJSVersion(4, 0, 0)) >= 0` But that does not make sense to me because if you go to NodeJS's distrobutions, there is an x86 Windows distro for every node version. Why enforce it to be less than version 4? Add Comment
[JIRA] (JENKINS-42429) Cannot view dependency of jobs
Title: Message Title
Vikas Kumar edited a comment on JENKINS-42429
Re: Cannot view dependency of jobs
I couldn't find this file anywhere on my Alpine box.{noformat}~ # find / -iname *.vz~ #{noformat}I have created one now using my Jenkins graph view http://depgraph-view/graph.gv !graph.png|thumbnail! {noformat}/ # cat graph.vzdigraph {node [shape=box, style=rounded];subgraph clusterMain {"petertest" [href=""];"vikastest" [href=""];color=invis;}subgraph clusterStandalone {color=invis;}"petertest" -> "vikastest" [ color=black ] ;}/ #/ # dot -Tpng graph.vz > graph.pngFontconfig warning: ignoring C.UTF-8: not a valid language tag/ # ls graph.pnggraph.png/ # {noformat} !graph.png|thumbnail!
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
