[JIRA] [core] (JENKINS-20190) Ability to sort or group /lib/hudson/newFromList:form
Title: Message Title Jesse Glick commented on JENKINS-20190 Re: Ability to sort or group /lib/hudson/newFromList:form gus reiber had a more ambitious version of this floating around in mockup form. 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-31153) Rename workflow to pipeline
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-31153 Re: Rename workflow to pipeline IMHO, Jenkins project is part of that industry and the names are only names. I remember when I started to use Software Development Ecosystem instead of Application Lifecycle Management. If we leave out criteria based on marketing, Workflow is great. I agree with Oleg Nenashev when he said Workflow is not about pipeline in general, it's only a particular use-case. 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-30519) Declarative job properties in multibranch
Title: Message Title Oleg Nenashev commented on JENKINS-30519 Re: Declarative job properties in multibranch I suspect that you can create an external periodic FreeStyle project, which would trigger the desired branches (dirty 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] [http-request-plugin] (JENKINS-32210) ldap and proxy access problem
Title: Message Title angel Liang created an issue Jenkins / JENKINS-32210 ldap and proxy access problem Issue Type: Bug Assignee: Unassigned Components: http-request-plugin, ldap-plugin, security Created: 28/Dec/15 9:35 AM Environment: UAT Priority: Blocker Reporter: angel Liang I am using Jenkins version 1.638, and i do the configure global security for using LDAP as my access control, i setup the load serer and its manager DN/manager password, it looks like already working, because when i do the save, there is no error in GUI. how ever, i get error "Invalid login information. Please try again." when i try to login with my AD access, i try both username like 'abc' and domain\username like 'AP\abc' but both failed. Also i Failed to connect to https://www.google.com.hk/ (code 407). when i use plugin manager-->HTTP proxy configuration, error logs are as below: org.apache.commons.httpclient.HttpMethodDirector executeConnect SEVERE: Credentials cannot be used for NTLM authentication: org.apache.commons.httpclient.UsernamePasswordCredentials org.apache.commons.httpclient.auth.InvalidCredentialsException: Credentials cannot be used for NTLM authentication:
[JIRA] [subversion-plugin] (JENKINS-30925) Subversion revision check consistently fails first time when using svn+ssh protocol
Title: Message Title Craig Rodrigues resolved as Fixed Fixed with SVNKit 1.8.11 as noted by Robbie Cargill Jenkins / JENKINS-30925 Subversion revision check consistently fails first time when using svn+ssh protocol Change By: Craig Rodrigues 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] [subversion-plugin] (JENKINS-27718) Build parameter for "List Subversion Tags (and more)" is not exposed to workflow script.
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-27718 Re: Build parameter for "List Subversion Tags (and more)" is not exposed to workflow script. Craig Rodrigues Sure. 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-30293) Make Subversion plugin support Subversion 1.9
Title: Message Title Craig Rodrigues resolved as Fixed Fixed in Subversion plugin 2.5.5, which updates to SVNKit 1.8.11 After upgrading to this plugin, you need to go to Manager Jenkins -> Configure System -> Subversion Workspace version and change the default version to 1.8 1.8 and 1.9 have compatible working copy versions Jenkins / JENKINS-30293 Make Subversion plugin support Subversion 1.9 Change By: Craig Rodrigues 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] [subversion-plugin] (JENKINS-30293) Make Subversion plugin support Subversion 1.9
Title: Message Title Manuel Jesús Recena Soto assigned an issue to Manuel Jesús Recena Soto Jenkins / JENKINS-30293 Make Subversion plugin support Subversion 1.9 Change By: Manuel Jesús Recena Soto Assignee: Manuel Jesús Recena Soto 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-30293) Make Subversion plugin support Subversion 1.9
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-30293 Re: Make Subversion plugin support Subversion 1.9 Craig Rodrigues, thanks for your feedback. I forgot to update this issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [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 Hi, We had similar issue with sub-modules in our project and I had installed latest beta plugins for Git and Git client. Apparently, the authentication issue seems to be resolved, but facing a new issue. Each time the project tries to run git sub-module update, it fails with this error: _ git submodule update --init --recursive --remote generators # timeout=10 FATAL: Command "/bin/git submodule update --init --recursive --remote generators" returned status code 1: stdout: stderr: error: pathspec 'generators' did not match any file(s) known to git. Did you forget to 'git add'? _hudson.plugins.git.GitException: Command "/bin/git submodule update --init --recursive --remote generators" returned status code 1: stdout: stderr: error: pathspec 'generators' did not match any file(s) known to git. Did you forget to 'git add'?_ We are using https git url. Can some one guide us please. 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] [subversion-plugin] (JENKINS-27718) Build parameter for "List Subversion Tags (and more)" is not exposed to workflow script.
Title: Message Title Craig Rodrigues assigned an issue to Manuel Jesús Recena Soto Jenkins / JENKINS-27718 Build parameter for "List Subversion Tags (and more)" is not exposed to workflow script. Change By: Craig Rodrigues Assignee: Jesse Glick Manuel Jesús Recena Soto 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-27718) Build parameter for "List Subversion Tags (and more)" is not exposed to workflow script.
Title: Message Title Craig Rodrigues commented on JENKINS-27718 Re: Build parameter for "List Subversion Tags (and more)" is not exposed to workflow script. Manuel Jesús Recena Soto Please look at https://github.com/jenkinsci/subversion-plugin/pull/151 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] [extended-choice-parameter-plugin] (JENKINS-31690) getGroovyBinding NPE
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31690 Re: getGroovyBinding NPE Code changed in jenkins User: vimil Path: src/main/java/com/cwctravel/hudson/plugins/extended_choice_parameter/ExtendedChoiceParameterDefinition.java http://jenkins-ci.org/commit/extended-choice-parameter-plugin/719e73494132baf272abe4a461da6ee0eeb344e1 Log: JENKINS-31690 fix for getGroovyBinding NPE Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Mark Waite commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated Doesn't that indicate that your submodule definition is somehow inconsistent? A stackoverflow article gives a few possible alternatives. 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 Andres Rodriguez created an issue Jenkins / JENKINS-32211 Allow Groovy Method `tokenize` to be used in the sandbox Issue Type: Improvement Assignee: Andres Rodriguez Components: script-security-plugin Created: 28/Dec/15 4:51 PM Environment: Script-Security-Plugin 1.15 Priority: Minor Reporter: Andres Rodriguez Include tokenize in the whitelist. Add Comment
[JIRA] [ec2-plugin] (JENKINS-25322) EnvInject channel is already closed when used with ec2 autoscaling plugin
Title: Message Title Christopher Orr updated an issue Jenkins / JENKINS-25322 EnvInject channel is already closed when used with ec2 autoscaling plugin Change By: Christopher Orr Component/s: android-emulator-plugin Component/s: envinject-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] [ec2-plugin] (JENKINS-25322) EnvInject channel is already closed when used with ec2 autoscaling plugin
Title: Message Title Christopher Orr assigned an issue to Francis Upton Jenkins / JENKINS-25322 EnvInject channel is already closed when used with ec2 autoscaling plugin Change By: Christopher Orr Assignee: Christopher Orr Francis Upton 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 Andres Rodriguez started work on JENKINS-32211 Change By: Andres Rodriguez 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] [ec2-plugin] (JENKINS-30284) EC2 plugin too aggressive in timing in contacting new AWS instance over SSH
Title: Message Title E Camden Fisher commented on JENKINS-30284 Re: EC2 plugin too aggressive in timing in contacting new AWS instance over SSH Same issue here, running CentOS 7 slaves. Output looks the same as above please make these timing configurable! Thanks Node Jenkins Docker Slave (i-386b0fc1)(i-386b0fc1) is still pending/launching, waiting 5s Node Jenkins Docker Slave (i-386b0fc1)(i-386b0fc1) is still pending/launching, waiting 5s Node Jenkins Docker Slave (i-386b0fc1)(i-386b0fc1) is still pending/launching, waiting 5s Node Jenkins Docker Slave (i-386b0fc1)(i-386b0fc1) is still pending/launching, waiting 5s Node Jenkins Docker Slave (i-386b0fc1)(i-386b0fc1) is still pending/launching, waiting 5s Node Jenkins Docker Slave (i-386b0fc1)(i-386b0fc1) is still pending/launching, waiting 5s Node Jenkins Docker Slave (i-386b0fc1)(i-386b0fc1) is ready Connecting to ec2-52-91-128-246.compute-1.amazonaws.com on port 22, with timeout 1. Failed to connect via ssh: The kexTimeout (1 ms) expired. Waiting for SSH to come up. Sleeping 5. Connecting to ec2-52-91-128-246.compute-1.amazonaws.com on port 22, with timeout 1. Failed to connect via ssh: The kexTimeout (1 ms) expired. Waiting for SSH to come up. Sleeping 5. Connecting to ec2-52-91-128-246.compute-1.amazonaws.com on port 22, with timeout 1. Failed to connect via ssh: The kexTimeout (1 ms) expired. Waiting for SSH to come up. Sleeping 5. Connecting to ec2-52-91-128-246.compute-1.amazonaws.com on port 22, with timeout 1. Failed to connect via ssh: The kexTimeout (1 ms) expired. Waiting for SSH to come up. Sleeping 5. Connecting to ec2-52-91-128-246.compute-1.amazonaws.com on port 22, with timeout 1. Failed to connect via ssh: The kexTimeout (1 ms) expired. Waiting for SSH to come up. Sleeping 5. Connecting to ec2-52-91-128-246.compute-1.amazonaws.com on port 22, with timeout 1. Failed to connect via ssh: The kexTimeout (1 ms) expired. Waiting for SSH to come up. Sleeping 5. Connecting to ec2-52-91-128-246.compute-1.amazonaws.com on port 22, with timeout 1. Failed to connect via ssh: The kexTimeout (1 ms) expired. Waiting for SSH to come up. Sleeping 5. Connecting to ec2-52-91-128-246.compute-1.amazonaws.com on port 22, with timeout 1. Failed to connect via ssh: The kexTimeout (1 ms) expired. Waiting for SSH to come up. Sleeping 5. Connecting to ec2-52-91-128-246.compute-1.amazonaws.com on port 22, with timeout 1. Failed to connect via ssh: The kexTimeout (1 ms) expired. Waiting for SSH to come up. Sleeping 5. Connecting to ec2-52-91-128-246.compute-1.amazonaws.com on port 22, with timeout 1. Failed to connect via ssh: There was a problem while connecting to ec2-52-91-128-246.compute-1.amazonaws.com:22 Waiting for SSH to come up. Sleeping 5. Connecting to ec2-52-91-128-246.compute-1.amazonaws.com on port 22, with timeout 1. Failed to connect via ssh: There was a problem while connecting to ec2-52-91-128-246.compute-1.amazonaws.com:22 Waiting for SSH to come up. Sleeping 5. Connecting to ec2-52-91-128-246.compute-1.amazonaws.com on port 22, with timeout 1. Failed to connect via ssh: There was a problem while connecting to ec2-52-91-128-246.compute-1.amazonaws.com:22 Waiting for SSH to come up. Sleeping 5. Connecting to ec2-52-91-128-246.compute-1.amazonaws.com on port 22, with timeout 1. Failed to connect via ssh: There was a problem while connecting to ec2-52-91-128-246.compute-1.amazonaws.com:22 Waiting for SSH to come up. Sleeping 5. Connecting to ec2-52-91-128-246.compute-1.amazonaws.com on port 22, with timeout 1. Failed to connect via ssh: There was a problem while connecting to ec2-52-91-128-246.compute-1.amazonaws.com:22 Waiting
[JIRA] [workflow-plugin] (JENKINS-30519) Declarative job properties in multibranch
Title: Message Title Andrew Bayer commented on JENKINS-30519 Re: Declarative job properties in multibranch So, before I file a JIRA, just want to make sure - triggers are still not possible, right? So there's no way to currently have a Multibranch branch Jenkinsfile that gets executed @daily, etc? 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-31161) Update HTMLUnit in Jenkins Core
Title: Message Title Jesse Glick assigned an issue to Tom FENNELLY Jenkins / JENKINS-31161 Update HTMLUnit in Jenkins Core Change By: Jesse Glick Assignee: Tom FENNELLY 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-31185) Bitbucket Plugin: add scm hg
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31185 Re: Bitbucket Plugin: add scm hg Code changed in jenkins User: fbelzunc Path: pom.xml src/main/java/com/cloudbees/jenkins/plugins/BitbucketJobProbe.java src/main/java/com/cloudbees/jenkins/plugins/BitbucketPayloadProcessor.java src/test/java/com/cloudbees/jenkins/plugins/BitbucketPayloadProcessorTest.java http://jenkins-ci.org/commit/bitbucket-plugin/2dd1b394bf2c97f47806dcaba8cb7231c00453b0 Log: Merge pull request #21 from matthewcmorgan/master [FIXED JENKINS-31185] Added hg support Compare: https://github.com/jenkinsci/bitbucket-plugin/compare/67fb8b71eea7...2dd1b394bf2c 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-31185) Bitbucket Plugin: add scm hg
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-31185 Bitbucket Plugin: add scm hg Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31161) Update HTMLUnit in Jenkins Core
Title: Message Title Jesse Glick resolved as Fixed I think this was fixed a while ago? Jenkins / JENKINS-31161 Update HTMLUnit in Jenkins Core Change By: Jesse Glick 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] [extensible-choice-parameter-plugin] (JENKINS-29942) Add findbugs to extensible-choice-parameter plugin
Title: Message Title ikedam resolved as Fixed Jenkins / JENKINS-29942 Add findbugs to extensible-choice-parameter plugin Change By: ikedam Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-25048) Git plugin ignores included/excluded paths when triggering build on commit nitification
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-25048 Git plugin ignores included/excluded paths when triggering build on commit nitification Change By: Daniel Beck Labels: git-plugin-PathRestriction 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-32212) "Check Now" to refresh plugin data isn't available on updates tab if last had none
Title: Message Title Nathan Neulinger created an issue Jenkins / JENKINS-32212 "Check Now" to refresh plugin data isn't available on updates tab if last had none Issue Type: Bug Assignee: Unassigned Components: core Created: 28/Dec/15 6:26 PM Environment: 1.642 on fc20 Labels: plugin plugin-manager Priority: Minor Reporter: Nathan Neulinger If most recent cache update indicated that no plugins were available for update, the 'Check Now' and last update date information is not displayed on the updates tab. It is still displayed on the Available tab, and you can click on it there (at which point, since new ones were available, the button started showing up on the updates tab). I think this info should be displayed on all of the plugin update tabs.
[JIRA] [workflow-plugin] (JENKINS-31155) Workflow shared library improvements
Title: Message Title Oleg Nenashev commented on JENKINS-31155 Re: Workflow shared library improvements https://github.com/jenkinsci/workflow-remote-loader-plugin is another partial solution Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-28808) 'undefined method `extensions'' on processing Multiple SCMs projects
Title: Message Title Luis Ehlen commented on JENKINS-28808 Re: 'undefined method `extensions'' on processing Multiple SCMs projects +1 Thanks Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31687) Which node Groovy code actually executes on is not documented clearly
Title: Message Title Jesse Glick commented on JENKINS-31687 Re: Which node Groovy code actually executes on is not documented clearly BTW in this case you would now use isUnix. 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-oauth-plugin] (JENKINS-32198) avax.servlet.ServletException: org.scribe.exceptions.OAuthConnectionException: There was a problem while creating a connection to the remote service.
Title: Message Title Victor Martinez commented on JENKINS-32198 Re: avax.servlet.ServletException: org.scribe.exceptions.OAuthConnectionException: There was a problem while creating a connection to the remote service. You can add some loggers https://wiki.jenkins-ci.org/display/JENKINS/Logging Look at the bitbucket oauth source code https://github.com/jenkinsci/bitbucket-oauth-plugin/blob/master/src/main/java/org/jenkinsci/plugins/BitbucketSecurityRealm.java In order to grab those logger details and get some verbose output. Cheers 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-29990) NPE from CpsCallableInvocation. when passing null to one-arg method
Title: Message Title Jesse Glick commented on JENKINS-29990 Re: NPE from CpsCallableInvocation. when passing null to one-arg method Possible duplicate of JENKINS-32062, but need to expand that test case to verify 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] [workflow-plugin] (JENKINS-32213) Must declare classes to implement Serializable
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-32213 Must declare classes to implement Serializable Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 28/Dec/15 7:10 PM Labels: groovy Priority: Minor Reporter: Jesse Glick A script like class C { int x } def c = new C() c.x = 5 sh "echo ${c.x}" will fail since the local variable c is of a nonserializable type. You need to explicitly say class C implements Serializable { // ... Since groovy-cps demands that local variables may be serialized, any locally defined classes must also be serializable (unless they are only ever being passed to binary methods: legal but unlikely). Perhaps the transformer could implicitly add implements Serializable to any class declarations it finds.
[JIRA] [warnings-plugin] (JENKINS-32150) Cannot resolve relative filenames referencing parent directory
Title: Message Title Anatoly Trosinenko commented on JENKINS-32150 Re: Cannot resolve relative filenames referencing parent directory In JENKINS-9463 there was proposal to use just basename to resolve relative paths and you told that it was already done in that way. I am not sure that this approach will not break anything, but if relative paths are still supposed to be resolved by basename only, then something goes wrong. PS: The message "Found multiple matches: [directory-a/file-in-subdir.txt]." seems strange. 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-32215) jenkins will not delete /tmp/upload_*.tmp files,after use File parameter upload file for build
Title: Message Title R. Tyler Croy moved an issue Jenkins / JENKINS-32215 jenkins will not delete /tmp/upload_*.tmp files,after use File parameter upload file for build Change By: R. Tyler Croy Project: Jenkins Website Key: WEBSITE JENKINS - 57 32215 Workflow: WEBSITE: Software Development Workflow JNJira Status: To Do Open Component/s: core Component/s: design Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-32215) jenkins will not delete /tmp/upload_*.tmp files,after use File parameter upload file for build
Title: Message Title R. Tyler Croy commented on JENKINS-32215 Re: jenkins will not delete /tmp/upload_*.tmp files,after use File parameter upload file for build I've moved this to the JENKINS project where such issues belong 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 Nikita Salnikov-Tarnovski commented on JENKINS-24989 Re: Support Mercurial repositories Is this a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-31185 ? 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] [artifact-promotion-plugin] (JENKINS-29623) Add classifier support for ArtifactPromotionPlugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29623 Re: Add classifier support for ArtifactPromotionPlugin Code changed in jenkins User: Mate Farkas Path: src/main/java/org/jenkinsci/plugins/artifactpromotion/AetherInteraction.java src/main/java/org/jenkinsci/plugins/artifactpromotion/ArtifactPromotionBuilder.java src/main/java/org/jenkinsci/plugins/artifactpromotion/NexusOSSPromoterClosure.java src/main/java/org/jenkinsci/plugins/artifactpromotion/PromotionBuildTokens.java src/main/resources/org/jenkinsci/plugins/artifactpromotion/ArtifactPromotionBuilder/config.jelly http://jenkins-ci.org/commit/artifact-promotion-plugin/26366488cb0b0703666d3bef20cd508fc2331f98 Log: JENKINS-29623 Classifier coordinate has been added. 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] [extensible-choice-parameter-plugin] (JENKINS-29942) Add findbugs to extensible-choice-parameter plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29942 Re: Add findbugs to extensible-choice-parameter plugin Code changed in jenkins User: ikedam Path: src/main/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/ChoiceWatchRunListener.java src/main/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/GlobalTextareaChoiceListEntry.java http://jenkins-ci.org/commit/extensible-choice-parameter-plugin/1777c06a7d91d413b2e6d7400889e0726023dc83 Log: JENKINS-29942 Fixed problems pointed by findbugs. 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-5253) artifacts archiving: add option for treating patterns in case insensitive way
Title: Message Title Dominique Brice resolved as Fixed Fix was merged in master branch and is available in Jenkins 1.634 onwards. Jenkins / JENKINS-5253 artifacts archiving: add option for treating patterns in case insensitive way Change By: Dominique Brice Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifact-promotion-plugin] (JENKINS-29623) Add classifier support for ArtifactPromotionPlugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29623 Re: Add classifier support for ArtifactPromotionPlugin Code changed in jenkins User: Mate Farkas Path: README.md src/main/resources/org/jenkinsci/plugins/artifactpromotion/ArtifactPromotionBuilder/config.jelly src/main/resources/org/jenkinsci/plugins/artifactpromotion/ArtifactPromotionBuilder/help-skipDeletion.html http://jenkins-ci.org/commit/artifact-promotion-plugin/8948fee3a0797cce817913dfd1eb29038a63d461 Log: JENKINS-29623 Skip deletion is true by default. Readme and tooltip have been updated 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] [test-results-analyzer-plugin] (JENKINS-32203) Allow users to set custom colors for status in tabular report
Title: Message Title Varun Menon resolved as Fixed Jenkins / JENKINS-32203 Allow users to set custom colors for status in tabular report Change By: Varun Menon 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] [extensible-choice-parameter-plugin] (JENKINS-29942) Add findbugs to extensible-choice-parameter plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29942 Re: Add findbugs to extensible-choice-parameter plugin Code changed in jenkins User: ikedam Path: pom.xml http://jenkins-ci.org/commit/extensible-choice-parameter-plugin/7029286f77d37e33ede78808063f7f236cd5ceca Log: JENKINS-29942 Enabled findbugs. 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-31500) Centralized collection of information from pipeline jobs
Title: Message Title Jesse Glick resolved as Won't Do Yes. Jenkins / JENKINS-31500 Centralized collection of information from pipeline jobs Change By: Jesse Glick Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifact-promotion-plugin] (JENKINS-29623) Add classifier support for ArtifactPromotionPlugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29623 Re: Add classifier support for ArtifactPromotionPlugin Code changed in jenkins User: Mate Farkas Path: pom.xml src/main/java/org/jenkinsci/plugins/artifactpromotion/AetherInteraction.java http://jenkins-ci.org/commit/artifact-promotion-plugin/15efea23eb22e4362b7bfbd6b8f779134722dbdf Log: JENKINS-29623 Checking for POM file in releaserepo. Only deploy POM file if it's not in the targeted repository The repository maybe configured to do not support re-deployment Nexus OSS doesn't handle re-deployment well Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23852) slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed"
Title: Message Title Moshe Zvi commented on JENKINS-23852 Re: slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed" +1 Florian 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-31678) NullPointerException when using GitPublisher in release post build actions
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-31678 NullPointerException when using GitPublisher in release post build actions Change By: Mark Waite Assignee: Mark Waite 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] [extensible-choice-parameter-plugin] (JENKINS-29942) Add findbugs to extensible-choice-parameter plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29942 Re: Add findbugs to extensible-choice-parameter plugin Code changed in jenkins User: ikedam Path: src/main/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/SystemGroovyChoiceListProvider.java src/test/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/SystemGroovyChoiceListProviderJenkinsTest.java http://jenkins-ci.org/commit/extensible-choice-parameter-plugin/6619f61a9d71c90f98ae3b8909008452ad192248 Log: JENKINS-29942 Make project in SystemGroovyChoiceListProvider transient not to break Serializable constraint. 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] [label-linked-jobs-plugin] (JENKINS-32049) Labels Dashboard is not showing any Labels and any Nodes
Title: Message Title Dominique Brice commented on JENKINS-32049 Re: Labels Dashboard is not showing any Labels and any Nodes I wasn't able to reproduce the issue, which may occur only with specific JVM implementations (I tested with jdk1.7.0_79 and jdk1.8.0_65 on Mac OS 10.11.2). It could behave differently on Windows, Linux, etc. In the plugin the problem becomes apparent when a job is configured via/for the Parameterized Trigger Plugin with the $ syntax (to specify a macro). In any case, I have a good hunch as to what's causing the problem and I created release 4.0.3 with the specific fix. m r since I can't test in my development environment I would appreciate if you could confirm whether it work for you (yeah!) or not (please provide logs in that case ). Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [test-results-analyzer-plugin] (JENKINS-32204) Show a loading icon until the tabular report is loaded
Title: Message Title Varun Menon resolved as Fixed Jenkins / JENKINS-32204 Show a loading icon until the tabular report is loaded Change By: Varun Menon 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] [git-client-plugin] (JENKINS-30371) Symlinks still not supported on unix with JGit 3.7.1
Title: Message Title Mark Waite resolved as Fixed Fix included in git client plugin 1.19.1 released 26 Dec 2015 Jenkins / JENKINS-30371 Symlinks still not supported on unix with JGit 3.7.1 Change By: Mark Waite Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31153) Rename workflow to pipeline
Title: Message Title Daniel Beck commented on JENKINS-31153 Re: Rename workflow to pipeline Workflow could also easily be considered a product name rather than a generic name based on what it does and treated as such. Only requires a rephrasing of the top level item types if use of "pipeline" as a term is desired (e.g. "Workflow pipeline (job)", Workflow multibranch pipeline (job)") and some documentation rework, most of which is external to 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] [workflow-plugin] (JENKINS-32214) Workflow and svn polling
Title: Message Title Owen Wood created an issue Jenkins / JENKINS-32214 Workflow and svn polling Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 28/Dec/15 8:11 PM Priority: Major Reporter: Owen Wood When pulling my workflow script from a svn repo I get two builds triggered for one revision change if build runs longer then pull interval, To reproduce: Create workflow job with a standard svn pull configured in job, for my test I set to every minute Sample Job DSL --- node ('master') { checkout changelog: false, poll: false, scm: [ $class: "SubversionSCM", locations: [[ remote:'SVNURL/trunk/flow']] ] load 'flow/Test.groovy' }() Sample Test.groovy --- { -> node() { ws() { checkout changelog: true, poll: true, scm: [$class: "SubversionSCM", locations: [[remote: 'SVNURL/trunk']]] sleep 300 } } } Note: I pull my workflow scripts from the same repo as my build. Any
[JIRA] [git-plugin] (JENKINS-29731) AssemblaWeb URL is incorrect
Title: Message Title Mark Waite commented on JENKINS-29731 Re: AssemblaWeb URL is incorrect Included in git plugin 2.4.1 released 26 Dec 2015 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-27248) List Subversion Tags parameter not available in workflow
Title: Message Title Craig Rodrigues resolved as Duplicate Jenkins / JENKINS-27248 List Subversion Tags parameter not available in workflow Change By: Craig Rodrigues Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifact-promotion-plugin] (JENKINS-29623) Add classifier support for ArtifactPromotionPlugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29623 Re: Add classifier support for ArtifactPromotionPlugin Code changed in jenkins User: Mate Farkas Path: README.md src/main/java/org/jenkinsci/plugins/artifactpromotion/jobdsl/ArtifactPromotionDslContext.java src/main/java/org/jenkinsci/plugins/artifactpromotion/jobdsl/ArtifactPromotionJobDslExtension.java http://jenkins-ci.org/commit/artifact-promotion-plugin/fec45158406ff4633911f66aa04ed1d119b0880b Log: JENKINS-29623 Classifier coordinate has been added for jobdsl-extension. 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-27718) Build parameter for "List Subversion Tags (and more)" is not exposed to workflow script.
Title: Message Title Manuel Jesús Recena Soto started work on JENKINS-27718 Change By: Manuel Jesús Recena Soto 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] [artifact-promotion-plugin] (JENKINS-29623) Add classifier support for ArtifactPromotionPlugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29623 Re: Add classifier support for ArtifactPromotionPlugin Code changed in jenkins User: Mate Farkas Path: README.md pom.xml src/main/java/org/jenkinsci/plugins/artifactpromotion/AetherInteraction.java src/main/java/org/jenkinsci/plugins/artifactpromotion/ArtifactPromotionBuilder.java src/main/java/org/jenkinsci/plugins/artifactpromotion/NexusOSSPromoterClosure.java src/main/java/org/jenkinsci/plugins/artifactpromotion/PromotionBuildTokens.java src/main/java/org/jenkinsci/plugins/artifactpromotion/jobdsl/ArtifactPromotionDslContext.java src/main/java/org/jenkinsci/plugins/artifactpromotion/jobdsl/ArtifactPromotionJobDslExtension.java src/main/resources/org/jenkinsci/plugins/artifactpromotion/ArtifactPromotionBuilder/config.jelly src/main/resources/org/jenkinsci/plugins/artifactpromotion/ArtifactPromotionBuilder/help-skipDeletion.html http://jenkins-ci.org/commit/artifact-promotion-plugin/4a944953afe91ea3142b1f877a7e852142a4c617 Log: [FIXED JENKINS-29623] Merge branch 'feature/ JENKINS-29623 -Add_classifier_support_for_ArtifactPromotionPlugin' 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] [nodelabelparameter-plugin] (JENKINS-32002) Build is sheduled on one node and not all of them for node parameter
Title: Message Title Michal Cichra commented on JENKINS-32002 Re: Build is sheduled on one node and not all of them for node parameter I can confirm. If I schedule on all nodes except the first one, it correctly runs on all selected ones. 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] [label-linked-jobs-plugin] (JENKINS-32049) Labels Dashboard is not showing any Labels and any Nodes
Title: Message Title Dominique Brice edited a comment on JENKINS-32049 Re: Labels Dashboard is not showing any Labels and any Nodes I wasn't able to reproduce the issue, which may occur only with specific JVM implementations (I tested with jdk1.7.0_79 and jdk1.8.0_65 on Mac OS 10.11.2). It could behave differently on Windows, Linux, etc.In the plugin the problem becomes apparent when a job is configured via/for the Parameterized Trigger Plugin with the $ syntax (to specify a macro).In any case, I have a good hunch as to what's causing the problem and I created [ release 4.0.3 |http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/label-linked-jobs/4.0.3/] with the specific fix.[~olibolib] since I can't test in my development environment I would appreciate if you could confirm whether it work for you (yeah!) or not (please provide logs in that case :-) ). Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-27718) Build parameter for "List Subversion Tags (and more)" is not exposed to workflow script.
Title: Message Title Manuel Jesús Recena Soto assigned an issue to Craig Rodrigues Jenkins / JENKINS-27718 Build parameter for "List Subversion Tags (and more)" is not exposed to workflow script. Change By: Manuel Jesús Recena Soto Assignee: Manuel Jesús Recena Soto Craig Rodrigues 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-23654) UpdateCenter stuck at preparation phase when jenkins server is behind GFW
Title: Message Title mgy tdxmgy commented on JENKINS-23654 Re: UpdateCenter stuck at preparation phase when jenkins server is behind GFW y g 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] [test-results-analyzer-plugin] (JENKINS-29114) Allow user to configure what text to be shown on the UI for passed/failed/skipped tests
Title: Message Title Varun Menon resolved as Fixed Jenkins / JENKINS-29114 Allow user to configure what text to be shown on the UI for passed/failed/skipped tests Change By: Varun Menon 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] [test-results-analyzer-plugin] (JENKINS-32206) Tabular report should load child results on request
Title: Message Title Varun Menon created an issue Jenkins / JENKINS-32206 Tabular report should load child results on request Issue Type: New Feature Assignee: Varun Menon Components: test-results-analyzer-plugin Created: 27/Dec/15 1:15 PM Priority: Major Reporter: Varun Menon Currently the plugin tabular report loads the report for all the results. It will be good to load the report only for the required content. For ex. The report can be loaded for only packages initially and when user clicks on the expand then the rest of the report should be loaded. Add Comment
[JIRA] [artifact-promotion-plugin] (JENKINS-29623) Add classifier support for ArtifactPromotionPlugin
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-29623 Add classifier support for ArtifactPromotionPlugin Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-27180) Upgrade to version 1.600 broke GIT plugin
Title: Message Title Mark Waite commented on JENKINS-27180 Re: Upgrade to version 1.600 broke GIT plugin Included in git plugin 2.4.1 released 26 Dec 2015 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-23654) UpdateCenter stuck at preparation phase when jenkins server is behind GFW
Title: Message Title mgy tdxmgy commented on JENKINS-23654 Re: UpdateCenter stuck at preparation phase when jenkins server is behind GFW If you want to update some plugins, you can modify jenkins_home/updates/default.json ,change connectionCheckUrl from http://www.google.com/ to some one you can access ,maybe https://www.baidu.com for china, then reload configuration,and install plugins.But jenkins will get this file daily,so if you need,you can 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] [extensible-choice-parameter-plugin] (JENKINS-29942) Add findbugs to extensible-choice-parameter plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29942 Re: Add findbugs to extensible-choice-parameter plugin Code changed in jenkins User: ikedam Path: src/main/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/AddEditedChoiceListProvider.java src/main/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/ChoiceListProvider.java src/main/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/FilenameChoiceListProvider.java src/main/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/GlobalTextareaChoiceListProvider.java src/main/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/SystemGroovyChoiceListProvider.java src/main/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/TextareaChoiceListProvider.java src/test/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/ExtensibleChoiceParameterDefinitionJenkinsTest.java http://jenkins-ci.org/commit/extensible-choice-parameter-plugin/652cf12e39bb639d1407f1ad2a93462d18de2ec2 Log: JENKINS-29942 Make ChoiceListProvider Serializable. 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] [distfork-plugin] (JENKINS-15228) Impossible to kill job run by dist-fork
Title: Message Title Jan Hollevoet commented on JENKINS-15228 Re: Impossible to kill job run by dist-fork Is this still an issue? I don't see this behavior in my installation of Jenkins: when the cli process is killed, also the job disappears from 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] [git-plugin] (JENKINS-26587) Checkout fails with Multiple SCMs plugin on commit notification
Title: Message Title Mark Waite resolved as Fixed Pull request PR296 has been included in git plugin 2.4.1 released 26 Dec 2015. Jenkins / JENKINS-26587 Checkout fails with Multiple SCMs plugin on commit notification Change By: Mark Waite Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-32157) Jenkins is unable to start a process using shell script
Title: Message Title Vijetha Nayak updated an issue Jenkins / JENKINS-32157 Jenkins is unable to start a process using shell script Change By: Vijetha Nayak Priority: Minor Major 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-7643) "Workspace is offline" on every SCM poll
Title: Message Title Oded Arbel commented on JENKINS-7643 Re: "Workspace is offline" on every SCM poll Still experiencing this problem - with latest everything. I've removed the "force workspace" option from all builds, and it works no "permission denied" errors, but it issues `nonexisting_workspace` every couple of hours for all of my builds 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.