[JIRA] [ghprb-plugin] (JENKINS-31214) Move Job DSL for GitHub Pull Request Builder to ghprb-plugin
Title: Message Title Arcadiy Ivanov commented on JENKINS-31214 Re: Move Job DSL for GitHub Pull Request Builder to ghprb-plugin It would be a great addition, yes. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [coverity-plugin] (JENKINS-30886) BUG: Could not find Coverity Analysis home directory
Title: Message Title Jonathan Strickland commented on JENKINS-30886 Re: BUG: Could not find Coverity Analysis home directory Coverity Plugin Version: 1.6.0 we hit issue. Rolled back to 1.5.2 and service restored. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory-plugin] (JENKINS-31249) Temporary files used by the Artifactory plugin (with Gradle integration) are not cleaned up
Title: Message Title
onejli updated an issue
Jenkins / JENKINS-31249
Temporary files used by the Artifactory plugin (with Gradle integration) are not cleaned up
Change By:
onejli
When leveraging the Artifactory plugin to publish artifacts (jar, war, etc.) from a Gradle build (i.e., the Gradle-Artifactory Integration option is enabled), the temporary files containing the build information and Gradle/Artifactory stub that are created in /tmp are not cleaned up after the build completes (regardless of success/failure). 1. Before the build:{code:java}$ ls -la /tmptotal 48drwxrwxrwt. 4 root root 32768 Oct 28 18:18 .dr-xr-xr-x. 22 root root 4096 May 14 13:31 ..drwxrwxrwt 2 root root 4096 May 14 13:31 .ICE-unixdrwx-- 2 root root 4096 Jun 19 15:44 .ssh_script_automation_9600.tmp{code}2. 3. After the build has successfully completed:{code:java}$ ls -la /tmptotal 196drwxrwxrwt. 5 rootroot32768 Oct 28 18:17 .dr-xr-xr-x. 22 rootroot 4096 May 14 13:31 ..-rw-rw-r-- 1 jenkins jenkins 4304 Oct 28 18:17 buildInfo2754263552212503876.properties-rw-rw-r-- 1 jenkins jenkins 4306 Oct 28 18:17 buildInfo3094215615494783413.properties-rw-rw-r-- 1 jenkins jenkins 4306 Oct 28 18:17 buildInfo4563259066817889305.properties-rw-rw-r-- 1 jenkins jenkins 4173 Oct 28 18:16 buildInfo4840690737184691532.properties-rw-rw-r-- 1 jenkins jenkins 4173 Oct 28 18:17 buildInfo4867868067522153588.properties-rw-rw-r-- 1 jenkins jenkins 4173 Oct 28 18:17 buildInfo5161010698629287103.properties-rw-rw-r-- 1 jenkins jenkins 4306 Oct 28 18:16 buildInfo5453726483552054197.properties-rw-rw-r-- 1 jenkins jenkins 4305 Oct 28 18:17 buildInfo5527867601058892184.properties-rw-rw-r-- 1 jenkins jenkins 4173 Oct 28 18:17 buildInfo6737751503841270964.properties-rw-rw-r-- 1 jenkins jenkins 4306 Oct 28 18:16 buildInfo7055270731756693827.properties-rw-rw-r-- 1 jenkins jenkins 4306 Oct 28 18:17 buildInfo8135505113497629230.properties-rw-rw-r-- 1 jenkins jenkins 4306 Oct 28 18:17 buildInfo8254801048238679777.propertiesdrwxr-xr-x 2 jenkins jenkins 4096 Oct 28 18:17 hsperfdata_jenkinsdrwxrwxrwt 2 rootroot 4096 May 14 13:31 .ICE-unix-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:17 init-artifactory11184285959621809gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:16 init-artifactory1527093786774486333gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:17 init-artifactory183972521235824332gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:17 init-artifactory2327215488458291841gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:16 init-artifactory2418733176174666728gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:17 init-artifactory2660007329172251838gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:16 init-artifactory3222368236967924379gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:17 init-artifactory3415711751868865261gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:17 init-artifactory4463086551357442236gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:17 init-artifactory7109448943276826421gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:17 init-artifactory7489101883991264269gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:17 init-artifactory7984552170437924807gradledrwx-- 2 rootroot 4096 Jun
[JIRA] [parameterized-remote-trigger-plugin] (JENKINS-24240) Add support for folders plugin
Title: Message Title Will Saxon commented on JENKINS-24240 Re: Add support for folders plugin See https://github.com/jenkinsci/parameterized-remote-trigger-plugin/pull/16 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory-plugin] (JENKINS-31249) Temporary files used by the Artifactory plugin (with Gradle integration) are not cleaned up
Title: Message Title
onejli updated an issue
Jenkins / JENKINS-31249
Temporary files used by the Artifactory plugin (with Gradle integration) are not cleaned up
Change By:
onejli
When leveraging the Artifactory plugin to publish artifacts (jar, war, etc.) from a Gradle build (i.e., the Gradle-Artifactory Integration option is enabled), the temporary files containing the build information and Gradle/Artifactory stub that are created in /tmp are not cleaned up after the build completes (regardless of success/failure). # 1. Before the build:{code:java}$ ls -la /tmptotal 48drwxrwxrwt. 4 root root 32768 Oct 28 18:18 .dr-xr-xr-x. 22 root root 4096 May 14 13:31 ..drwxrwxrwt 2 root root 4096 May 14 13:31 .ICE-unixdrwx-- 2 root root 4096 Jun 19 15:44 .ssh_script_automation_9600.tmp{code} # 2. # 3. After the build has successfully completed:{code:java}$ ls -la /tmptotal 196drwxrwxrwt. 5 rootroot32768 Oct 28 18:17 .dr-xr-xr-x. 22 rootroot 4096 May 14 13:31 ..-rw-rw-r-- 1 jenkins jenkins 4304 Oct 28 18:17 buildInfo2754263552212503876.properties-rw-rw-r-- 1 jenkins jenkins 4306 Oct 28 18:17 buildInfo3094215615494783413.properties-rw-rw-r-- 1 jenkins jenkins 4306 Oct 28 18:17 buildInfo4563259066817889305.properties-rw-rw-r-- 1 jenkins jenkins 4173 Oct 28 18:16 buildInfo4840690737184691532.properties-rw-rw-r-- 1 jenkins jenkins 4173 Oct 28 18:17 buildInfo4867868067522153588.properties-rw-rw-r-- 1 jenkins jenkins 4173 Oct 28 18:17 buildInfo5161010698629287103.properties-rw-rw-r-- 1 jenkins jenkins 4306 Oct 28 18:16 buildInfo5453726483552054197.properties-rw-rw-r-- 1 jenkins jenkins 4305 Oct 28 18:17 buildInfo5527867601058892184.properties-rw-rw-r-- 1 jenkins jenkins 4173 Oct 28 18:17 buildInfo6737751503841270964.properties-rw-rw-r-- 1 jenkins jenkins 4306 Oct 28 18:16 buildInfo7055270731756693827.properties-rw-rw-r-- 1 jenkins jenkins 4306 Oct 28 18:17 buildInfo8135505113497629230.properties-rw-rw-r-- 1 jenkins jenkins 4306 Oct 28 18:17 buildInfo8254801048238679777.propertiesdrwxr-xr-x 2 jenkins jenkins 4096 Oct 28 18:17 hsperfdata_jenkinsdrwxrwxrwt 2 rootroot 4096 May 14 13:31 .ICE-unix-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:17 init-artifactory11184285959621809gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:16 init-artifactory1527093786774486333gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:17 init-artifactory183972521235824332gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:17 init-artifactory2327215488458291841gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:16 init-artifactory2418733176174666728gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:17 init-artifactory2660007329172251838gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:16 init-artifactory3222368236967924379gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:17 init-artifactory3415711751868865261gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:17 init-artifactory4463086551357442236gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:17 init-artifactory7109448943276826421gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:17 init-artifactory7489101883991264269gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:17 init-artifactory7984552170437924807gradledrwx-- 2 rootroot
[JIRA] [artifactory-plugin] (JENKINS-31249) Temporary files used by the Artifactory plugin (with Gradle integration) are not cleaned up
Title: Message Title onejli updated an issue Jenkins / JENKINS-31249 Temporary files used by the Artifactory plugin (with Gradle integration) are not cleaned up Change By: onejli Environment: Jenkins 1.625.1Artifactory Plugin 1 2 . 625 3 .1Linux 2.6.32-431.1.2.el6.x86_64JDK 1.8.0_25x64Gradle 2.2 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-30833) newline character is missing after import the config.xml
Title: Message Title Christopher Simons updated an issue Jenkins / JENKINS-30833 newline character is missing after import the config.xml Change By: Christopher Simons Environment: OS: CentOS Linux release 7.1.1503Jenkins version: 1.625Browser: Fireofx Firefox ESR 38.3.0 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory-plugin] (JENKINS-31249) Temporary files used by the Artifactory plugin (with Gradle integration) are not cleaned up
Title: Message Title
onejli updated an issue
Jenkins / JENKINS-31249
Temporary files used by the Artifactory plugin (with Gradle integration) are not cleaned up
Change By:
onejli
When leveraging the Artifactory plugin to publish artifacts (jar, war, etc.) from a Gradle build (i.e., the Gradle-Artifactory Integration option is enabled), the temporary files containing the build information and Gradle/Artifactory stub that are created in /tmp are not cleaned up after the build completes (regardless of success/failure). # 1. Before the build:{code:java}$ ls -la /tmptotal 48drwxrwxrwt. 4 root root 32768 Oct 28 18:18 .dr-xr-xr-x. 22 root root 4096 May 14 13:31 ..drwxrwxrwt 2 root root 4096 May 14 13:31 .ICE-unixdrwx-- 2 root root 4096 Jun 19 15:44 .ssh_script_automation_9600.tmp{code} # 2. # 3. After the build has successfully completed:{code:java}$ ls -la /tmptotal 196drwxrwxrwt. 5 rootroot32768 Oct 28 18:17 .dr-xr-xr-x. 22 rootroot 4096 May 14 13:31 ..-rw-rw-r-- 1 jenkins jenkins 4304 Oct 28 18:17 buildInfo2754263552212503876.properties-rw-rw-r-- 1 jenkins jenkins 4306 Oct 28 18:17 buildInfo3094215615494783413.properties-rw-rw-r-- 1 jenkins jenkins 4306 Oct 28 18:17 buildInfo4563259066817889305.properties-rw-rw-r-- 1 jenkins jenkins 4173 Oct 28 18:16 buildInfo4840690737184691532.properties-rw-rw-r-- 1 jenkins jenkins 4173 Oct 28 18:17 buildInfo4867868067522153588.properties-rw-rw-r-- 1 jenkins jenkins 4173 Oct 28 18:17 buildInfo5161010698629287103.properties-rw-rw-r-- 1 jenkins jenkins 4306 Oct 28 18:16 buildInfo5453726483552054197.properties-rw-rw-r-- 1 jenkins jenkins 4305 Oct 28 18:17 buildInfo5527867601058892184.properties-rw-rw-r-- 1 jenkins jenkins 4173 Oct 28 18:17 buildInfo6737751503841270964.properties-rw-rw-r-- 1 jenkins jenkins 4306 Oct 28 18:16 buildInfo7055270731756693827.properties-rw-rw-r-- 1 jenkins jenkins 4306 Oct 28 18:17 buildInfo8135505113497629230.properties-rw-rw-r-- 1 jenkins jenkins 4306 Oct 28 18:17 buildInfo8254801048238679777.propertiesdrwxr-xr-x 2 jenkins jenkins 4096 Oct 28 18:17 hsperfdata_jenkinsdrwxrwxrwt 2 rootroot 4096 May 14 13:31 .ICE-unix-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:17 init-artifactory11184285959621809gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:16 init-artifactory1527093786774486333gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:17 init-artifactory183972521235824332gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:17 init-artifactory2327215488458291841gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:16 init-artifactory2418733176174666728gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:17 init-artifactory2660007329172251838gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:16 init-artifactory3222368236967924379gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:17 init-artifactory3415711751868865261gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:17 init-artifactory4463086551357442236gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:17 init-artifactory7109448943276826421gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:17 init-artifactory7489101883991264269gradle-rw-rw-r-- 1 jenkins jenkins 798 Oct 28 18:17 init-artifactory7984552170437924807gradledrwx-- 2 rootroot
[JIRA] [artifactory-plugin] (JENKINS-31249) Temporary files used by the Artifactory plugin (with Gradle integration) are not cleaned up
Title: Message Title J L created an issue Jenkins / JENKINS-31249 Temporary files used by the Artifactory plugin (with Gradle integration) are not cleaned up Issue Type: Bug Assignee: yossis Components: artifactory-plugin Created: 29/Oct/15 1:34 AM Environment: Jenkins 1.625.1 Artifactory Plugin 1.625.1 Linux 2.6.32-431.1.2.el6.x86_64 JDK 1.8.0_25x64 Gradle 2.2 Priority: Minor Reporter: J L When leveraging the Artifactory plugin to publish artifacts (jar, war, etc.) from a Gradle build (i.e., the Gradle-Artifactory Integration option is enabled), the temporary files containing the build information and Gradle/Artifactory stub that are created in /tmp are not cleaned up after the build completes (regardless of success/failure). Before the build: $ ls -la /tmp total 48 drwxrwxrwt. 4 root root 32768 Oct 28 18:18 . dr-xr-xr-x. 22 root root 4096 May 14 13:31 .. drwxrwxrwt 2 root root 4096 May 14 13:31 .ICE-unix drwx-- 2 root root 4096 Jun 19 15:44 .ssh_script_automation_9600.tmp After the build has
[JIRA] [ruby-runtime-plugin] (JENKINS-31227) Ruby Runtime Plugin installation throws SEVERE: Failed to install Ruby Runtime Plugin
Title: Message Title Michael Barany commented on JENKINS-31227 Re: Ruby Runtime Plugin installation throws SEVERE: Failed to install Ruby Runtime Plugin This is a duplicate of JENKINS-31019 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [repository-connector-plugin] (JENKINS-30554) Complete ability to manually deploy artifacts TO a repository
Title: Message Title Brantone started work on JENKINS-30554 Change By: Brantone 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] [repository-connector-plugin] (JENKINS-30671) ArtifactDeploy is not expanding tokens for File
Title: Message Title Brantone started work on JENKINS-30671 Change By: Brantone 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] [repository-connector-plugin] (JENKINS-30671) ArtifactDeploy is not expanding tokens for File
Title: Message Title Brantone commented on JENKINS-30671 Re: ArtifactDeploy is not expanding tokens for File PR : https://github.com/jenkinsci/repository-connector-plugin/pull/16 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [repository-connector-plugin] (JENKINS-31206) Provide option to NOT upload Pom with artifact
Title: Message Title Brantone commented on JENKINS-31206 Re: Provide option to NOT upload Pom with artifact PR : https://github.com/jenkinsci/repository-connector-plugin/pull/17 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-31235) /createItem?mode=copy shouldn't require Content-Type header
Title: Message Title Christopher Simons resolved as Fixed I have submitted a fix for this: Pull Request #1892. Jenkins / JENKINS-31235 /createItem?mode=copy shouldn't require Content-Type header Change By: Christopher Simons 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-31235) /createItem?mode=copy shouldn't require Content-Type header
Title: Message Title Christopher Simons stopped work on JENKINS-31235 Change By: Christopher Simons Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-remote-trigger-plugin] (JENKINS-24240) Add support for folders plugin
Title: Message Title Will Saxon commented on JENKINS-24240 Re: Add support for folders plugin Using a Build Token Root url it is possible to kick off the job, so it should be possible to do the same w/ this plugin. However, this plugin checks to see if a job is parameterized using the regular url path prior to calling it via the buildToken path. So it still fails. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-25545) Multiple git repository names are not check and repositories risk be merged (our case 12286)
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-25545 Multiple git repository names are not check and repositories risk be merged (our case 12286) Change By: Bue Petersen Status: Resolved Closed Assignee: Praqma Support Bue Petersen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-24285) Improve commit message (our case 11772)
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-24285 Improve commit message (our case 11772) Change By: Bue Petersen Status: Resolved Closed Assignee: Praqma Support Bue Petersen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-26332) Deprecate old pretest-commit plugin (our case 11962)
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-26332 Deprecate old pretest-commit plugin (our case 11962) Change By: Bue Petersen Status: Resolved Closed Assignee: Praqma Support Bue Petersen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-25544) Default repository name (origin) must work with git scm and multi SCMs git (our case 12285)
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-25544 Default repository name (origin) must work with git scm and multi SCMs git (our case 12285) Change By: Bue Petersen Status: Resolved Closed Assignee: Praqma Support Bue Petersen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-27309) Plugin always leads to merge failure (case 12800)
Title: Message Title Bue Petersen closed an issue as Cannot Reproduce Jenkins / JENKINS-27309 Plugin always leads to merge failure (case 12800) Change By: Bue Petersen Status: Resolved Closed Assignee: Praqma Support Bue Petersen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-25959) Post-buid steps is executed though master is integration branch (our case 12427)
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-25959 Post-buid steps is executed though master is integration branch (our case 12427) Change By: Bue Petersen Status: Resolved Closed Assignee: Praqma Support Bue Petersen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-25445) Incorrect workspace selection when checkout to subfolder (case 12252)
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-25445 Incorrect workspace selection when checkout to subfolder (case 12252) Change By: Bue Petersen Status: Resolved Closed Assignee: Praqma Support Bue Petersen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-25960) MultiScm configurations does not resolve corret git-client (our case 12426)
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-25960 MultiScm configurations does not resolve corret git-client (our case 12426) Change By: Bue Petersen Status: Resolved Closed Assignee: Praqma Support Bue Petersen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-27690) Improve log output if git merge fails (Praqma case 12876)
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-27690 Improve log output if git merge fails (Praqma case 12876) Change By: Bue Petersen Status: Resolved Closed Assignee: Praqma Support Bue Petersen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-25886) Implement job configuration check - explicitly named remotes for MultiSCM (our case 12401)
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-25886 Implement job configuration check - explicitly named remotes for MultiSCM (our case 12401) Change By: Bue Petersen Status: Resolved Closed Assignee: Praqma Support Bue Petersen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-24443) Use original commit object for author and commit message info (our case 11862)
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-24443 Use original commit object for author and commit message info (our case 11862) Change By: Bue Petersen Status: Resolved Closed Assignee: Praqma Support Bue Petersen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-25888) Add more documentation on workflows and configuration (our case 12404)
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-25888 Add more documentation on workflows and configuration (our case 12404) Change By: Bue Petersen Status: Resolved Closed Assignee: Praqma Support Bue Petersen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-25546) Support individual git scm configuration part in the Multi SCMs plugin (our case 12287)
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-25546 Support individual git scm configuration part in the Multi SCMs plugin (our case 12287) Change By: Bue Petersen Status: Resolved Closed Assignee: Praqma Support Bue Petersen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-27697) Functional tests fails due to locked files on Windows (Praqma case 12882)
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-27697 Functional tests fails due to locked files on Windows (Praqma case 12882) Change By: Bue Petersen Status: Resolved Closed Assignee: Praqma Support Bue Petersen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-25618) Use standard commit message when the squash strategy is used case 12299
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-25618 Use standard commit message when the squash strategy is used case 12299 Change By: Bue Petersen Status: Resolved Closed Assignee: Praqma Support Bue Petersen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-24754) Add Support for named repositories, required for multiple scm selections (Praqma case 12019)
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-24754 Add Support for named repositories, required for multiple scm selections (Praqma case 12019) Change By: Bue Petersen Status: Resolved Closed Assignee: Praqma Support Bue Petersen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-26568) Implement new accummulated merge strategy commit message (our case 12618)
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-26568 Implement new accummulated merge strategy commit message (our case 12618) Change By: Bue Petersen Status: Resolved Closed Assignee: Praqma Support Bue Petersen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-24284) In the commit message - don't write "origin" (our case 11769)
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-24284 In the commit message - don't write "origin" (our case 11769) Change By: Bue Petersen Status: Resolved Closed Assignee: Praqma Support Bue Petersen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-24286) Plugin tries to delete origin/master (our case 11770)
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-24286 Plugin tries to delete origin/master (our case 11770) Change By: Bue Petersen Status: Resolved Closed Assignee: Praqma Support Bue Petersen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-27662) Double quotes in commit message results in merge failure (Praqma case 12871)
Title: Message Title Bue Petersen closed an issue as Cannot Reproduce Jenkins / JENKINS-27662 Double quotes in commit message results in merge failure (Praqma case 12871) Change By: Bue Petersen Status: Resolved Closed Assignee: Praqma Support Bue Petersen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-27328) Plugin hangs the jobs just after printing version out to console (Praqma case 12801)
Title: Message Title Bue Petersen closed an issue as Cannot Reproduce Jenkins / JENKINS-27328 Plugin hangs the jobs just after printing version out to console (Praqma case 12801) Change By: Bue Petersen Status: Resolved Closed Assignee: Praqma Support Bue Petersen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-28596) Hardcoded branch name when resolving commit messages (Praqma case 13073)
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-28596 Hardcoded branch name when resolving commit messages (Praqma case 13073) Change By: Bue Petersen Status: Resolved Closed Assignee: Praqma Support Bue Petersen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-28590) Author of last commit becomes the author of the integration commit (Praqma case 13102)
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-28590 Author of last commit becomes the author of the integration commit (Praqma case 13102) Change By: Bue Petersen Status: Resolved Closed Assignee: Praqma Support Bue Petersen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-28640) Quotationmarks in commit message leads to merge failure (Praqma case 13083)
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-28640 Quotationmarks in commit message leads to merge failure (Praqma case 13083) Change By: Bue Petersen Status: Resolved Closed Assignee: Praqma Support Bue Petersen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-24844) Commit fails when running on slaves in both integration strategies (our case 12050)
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-24844 Commit fails when running on slaves in both integration strategies (our case 12050) Change By: Bue Petersen Status: Resolved Closed Assignee: Praqma Support Bue Petersen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-27516) Plugin hangs - reproduced with failed earlier build (Praqma case 12906)
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-27516 Plugin hangs - reproduced with failed earlier build (Praqma case 12906) Change By: Bue Petersen Status: Resolved Closed Assignee: Praqma Support Bue Petersen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-29369) Accumulated commit message is locale and launguage dependent (Praqma case 13296)
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-29369 Accumulated commit message is locale and launguage dependent (Praqma case 13296) Change By: Bue Petersen Status: Resolved Closed Assignee: Praqma Support Bue Petersen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-25873) Extend version number with git SHA (our case 12396)
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-25873 Extend version number with git SHA (our case 12396) Change By: Bue Petersen Status: Resolved Closed Assignee: Praqma Support Bue Petersen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-31058) Add license file (case 13735)
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-31058 Add license file (case 13735) Change By: Bue Petersen Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-31247) Copyartifact: more integration with workflow
Title: Message Title Jesse Glick commented on JENKINS-31247 Re: Copyartifact: more integration with workflow An implementation of JENKINS-29922 would simplify the syntax without any action on your part. You would benefit from a custom step only if the semantics were indeed simpler or different for Workflow. For example, some of the more exotic logic elements proposed for Copy Artifact 2.0 (and even some of the logic in 1.x) could be written directly in the user’s Groovy code, using if-statements and loops and so on. Yes the result would be somewhat more verbose, but on the other hand it is clear without reading any external documentation what the script is really doing, and you can make minor customizations (“pick the last stable build, or an unstable build if there has been no stable build in the past week”) without having to wait for your weird use case to be supported in the Jenkins plugin code. Common use cases can be packaged as script libraries or just written up as examples in plugin documentation. Enabling this kind of usage means providing lower-level steps and/or Groovy objects that can offer safe (@Whitelisted) access to critical information about Jenkins builds. There is already a RunWrapper in Workflow, though currently available only as currentBuild or the return value of the build step; could be expanded to let you get, say, the lastBuild of a job which you have Item.READ access to. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-30192) Job DSL support
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-30192 Job DSL support Change By: Bue Petersen Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-27343) Plugin does not compile with core > 1.554 (case 12803)
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-27343 Plugin does not compile with core > 1.554 (case 12803) Change By: Bue Petersen Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-30885) Support variable expansion (case 13544)
Title: Message Title Bue Petersen closed an issue as Fixed Jenkins / JENKINS-30885 Support variable expansion (case 13544) Change By: Bue Petersen Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-31248) Build trigger comment overrides build status of a previous trigger
Title: Message Title Oksana Yaremchuk created an issue Jenkins / JENKINS-31248 Build trigger comment overrides build status of a previous trigger Issue Type: Bug Assignee: Honza Brázdil Components: ghprb-plugin Created: 28/Oct/15 10:50 PM Priority: Major Reporter: Oksana Yaremchuk I have configured the plugin for two different jobs on the same CI server. One job does not define "Commit Status Context" and thus defaults to "default". Another job has "Commit Status Context" set to "test". Every time I push to my pull request it triggers my build job with "Commit Status Context" set to default. After completion, I get proper status update but, whenever I trigger a build with the trigger phrase in a comment my previous status gets overridden. The trigger phrase configured to launch a job that has "Commit Status Context" set to "test". Is it possible to have two different status updates in this case ? Add Comment
[JIRA] [copyartifact-plugin] (JENKINS-31247) Copyartifact: more integration with workflow
Title: Message Title ikedam commented on JENKINS-31247 Re: Copyartifact: more integration with workflow Is it possible to simplify also selector like this ? copyartifact projectName: 'test', filter: '**/*', selector: StatusBuildSelector(false) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-31247) Copyartifact: more integration with workflow
Title: Message Title ikedam commented on JENKINS-31247 Re: Copyartifact: more integration with workflow Workflow integration for htmlpublisher plugin looks good example for this extension. https://github.com/jenkinsci/htmlpublisher-plugin/pull/15 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-31247) Copyartifact: more integration with workflow
Title: Message Title ikedam created an issue Jenkins / JENKINS-31247 Copyartifact: more integration with workflow Issue Type: Improvement Assignee: Unassigned Components: copyartifact-plugin Created: 28/Oct/15 10:24 PM Labels: workflow Priority: Minor Reporter: ikedam (current feature) Copyartifact 1.34 introduced integration with workflow plugin. You can use copyartifact in workflow jobs like this: step([ $class: 'CopyArtifact', projectName: 'test', filter: '**/*', selector: [$class: 'StatusBuildSelector', stable: false] ]) (expected improvement) Workflow plugin provides plugins a way to define its own step functions like this: copyartifact projectName: 'test', filter: '**/*', selector: [$class: 'StatusBuildSelector', stable: false]
[JIRA] [promoted-builds-plugin] (JENKINS-13447) Show link to promotion jobs archived artifacts
Title: Message Title Nick minkler edited a comment on JENKINS-13447 Re: Show link to promotion jobs archived artifacts This should actually be considered a bug. It's a breaking functionality when dealing with promotions and slaves, as there's no way to produce a working link for a build artifact that is only archived during a promotion. The UI clearly accepts this as a valid setup, and all other artifact archiving format methods produce valid links and are expected to do so. However this does not. None of the 'workarounds' listed work for dealing with slaves either, as the artifact is transfered to the master in our setup but any attempts to browse through the job site don't work , and you can't run a script to copy the artifact down a couple directories to have it show up as they need to be present on the master, not the slave where the workspace is located . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-13447) Show link to promotion jobs archived artifacts
Title: Message Title Nick minkler edited a comment on JENKINS-13447 Re: Show link to promotion jobs archived artifacts This should actually be considered a bug. It's a breaking functionality when dealing with promotions and slaves, as there's no way to produce a working link for a build artifact that is only archived during a promotion. The UI clearly accepts this as a valid setup, and all other artifact archiving format methods produce valid links and are expected to do so. However this does not. None of the 'workarounds' listed work for dealing with slaves either, as the artifact is transfered to the master in our setup but any attempts to browse through the job site don't work. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-13447) Show link to promotion jobs archived artifacts
Title: Message Title Nick minkler updated an issue Jenkins / JENKINS-13447 Show link to promotion jobs archived artifacts Change By: Nick minkler Issue Type: Improvement Bug Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-13447) Show link to promotion jobs archived artifacts
Title: Message Title Nick minkler commented on JENKINS-13447 Re: Show link to promotion jobs archived artifacts This should actually be considered a bug. It's a breaking functionality when dealing with promotions and slaves, as there's no way to produce a working link for a build artifact that is only archived during a promotion. The UI clearly accepts this as a valid setup, and all other artifact archiving format methods produce valid links and are expected to do so. However this does not. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vsphere-cloud-plugin] (JENKINS-31246) Process environment variables for Take Snapshot name and description.
Title: Message Title Bill Hopper created an issue Jenkins / JENKINS-31246 Process environment variables for Take Snapshot name and description. Issue Type: Improvement Assignee: Unassigned Components: vsphere-cloud-plugin Created: 28/Oct/15 9:42 PM Environment: Windows 7 x64, Jenkins 1.634, vSphere plugin 2.6 Priority: Minor Reporter: Bill Hopper When capturing a snapshot for a VM, the name and description would be immensely more useful if they could contain expanded environment variables. E.g. Name = %DATE% nightly freeze Description = %BUILD_URL% for details. Add Comment
[JIRA] [git-client-plugin] (JENKINS-31212) git clone with embedded username/password failed using https auth
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-31212 git clone with embedded username/password failed using https auth Change By: Mark Waite Summary: git clone with embedded username/password failed when using https auth Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-31212) git clone with embedded username/password failed when using https auth
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-31212 git clone with embedded username/password failed when using https auth Change By: Mark Waite Summary: git clone with embedded username/password failed when using https auth Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-31244) Misconfiguration of submodules not clearly reported by git plugin
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-31244 Misconfiguration of submodules not clearly reported by git plugin Change By: Mark Waite Summary: Misconfiguration of submodules not well diagnosed clearly reported by git 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] [git-plugin] (JENKINS-31244) GIT plugin does use provided ssh key credentials for top-level repository, but not for submodules
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-31244 GIT plugin does use provided ssh key credentials for top-level repository, but not for submodules Change By: Mark Waite Component/s: credentials-plugin Component/s: git-client-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] [git-plugin] (JENKINS-31244) GIT plugin does use provided ssh key credentials for top-level repository, but not for submodules
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-31244 GIT plugin does use provided ssh key credentials for top-level repository, but not for submodules Change By: Mark Waite Assignee: stephenconnolly Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-31244) Misconfiguration of submodules not well diagnosed by git plugin
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-31244 Misconfiguration of submodules not well diagnosed by git plugin Change By: Mark Waite Summary: GIT plugin does use provided ssh key credentials for top-level repository, but not for Misconfiguration of submodules not well diagnosed by git 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] [exclusion-plugin] (JENKINS-12399) Dynamic exclusion resourced based on parameter name
Title: Message Title Nathan Neulinger commented on JENKINS-12399 Re: Dynamic exclusion resourced based on parameter name Yeah, it works wonderfully... significant simplification of the jobs. Lack of the control panel is the only real flaw. I am actually not even using 0.11 yet. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-27140) Workflow support for Integrity SCM Plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27140 Re: Workflow support for Integrity SCM Plugin Code changed in jenkins User: Cletus D'Souza Path: src/main/java/hudson/scm/IntegritySCMChkptNotifierStep.java src/main/java/hudson/scm/IntegritySCMChkptStep.java src/main/resources/hudson/scm/IntegritySCMChkptStep/config.jelly src/main/resources/hudson/scm/IntegritySCMChkptStep/help-checkpointLabel.html src/main/resources/hudson/scm/IntegritySCMLabelStep/config.jelly src/main/resources/hudson/scm/IntegritySCMLabelStep/help-checkpointLabel.html src/main/webapp/help-checkpointDesc.html http://jenkins-ci.org/commit/integrity-plugin/3c281361acf2b7618fc449c07d41caf9050cfe75 Log: Adding Integrity SCM Checkpoint step in support of workflow JENKINS-27140 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [exclusion-plugin] (JENKINS-12399) Dynamic exclusion resourced based on parameter name
Title: Message Title Oleksandr Kulychok edited a comment on JENKINS-12399 Re: Dynamic exclusion resourced based on parameter name Yes, this is actually works ( speaking about v0.11 released 27 Oct 2015).But due issue JENKINS-23010 allocated resources which defined with variable are displayed incorrectly in Control Panel. Actually only variable name is displayed but real resource (i.e. variable value/_expression_) does not present (and cannot be released manually) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-31232) Maven Install from Apache does not work
Title: Message Title Yuriy Burtsev assigned an issue to Aaron Simmons Jenkins / JENKINS-31232 Maven Install from Apache does not work Change By: Yuriy Burtsev Assignee: Aaron Simmons Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [exclusion-plugin] (JENKINS-12399) Dynamic exclusion resourced based on parameter name
Title: Message Title Oleksandr Kulychok commented on JENKINS-12399 Re: Dynamic exclusion resourced based on parameter name Yes, this is actually works (v0.11 released 27 Oct 2015). But due issue JENKINS-23010 allocated resources which defined with variable are displayed incorrectly in Control Panel. Actually only variable name is displayed but real resource (i.e. variable value/_expression_) does not present (and cannot be released manually) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cmakebuilder-plugin] (JENKINS-31215) cmake installation on osx: missing files & strange layout
Title: Message Title
Martin Weber commented on JENKINS-31215
Re: cmake installation on osx: missing files & strange layout
This directory:
/Volumes/data/tools/cmake/share/cmake-3.3/
is not the directory where the plugin places the downloaded cmake.
Like any other tool-installer, it places the files under
${JENKINS_HOME}/tools/hudson.plugins.cmake.CmakeTool/3.3.2/
Have a look at the build log, it will tell you exactly, which cmake is invoked, e.g.
/home/jenkins/tools/hudson.plugins.cmake.CmakeTool/3.2.3/bin/cmake -G "Unix Makefiles"...
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-29603) notifyCommit branch parameter can't contain slashes
Title: Message Title Warren Seine commented on JENKINS-29603 Re: notifyCommit branch parameter can't contain slashes It makes a lot of sense. Wouldn't a checkbox in the settings do the job? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-29603) notifyCommit branch parameter can't contain slashes
Title: Message Title Mark Waite commented on JENKINS-29603 Re: notifyCommit branch parameter can't contain slashes Warren Seine the plugin is not using the same library. I believe the root reason the notifyCommit branch parameter has difficulty with some forms of branch names is do the legacy compatibility retained for imprecisely declared branch names. With 60 000+ installations, compatibility matters very much. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-31244) GIT plugin does use provided ssh key credentials for top-level repository, but not for submodules
Title: Message Title Wolfgang Steiner commented on JENKINS-31244 Re: GIT plugin does use provided ssh key credentials for top-level repository, but not for submodules Right after I created the issue I found out what the problem actually was and it is not related to Jenkins. I had used absolute paths using the http:// protocol in the top-level repository's .gitmodules file. This of course caused trouble when Jenkins tried to clone the submodules, since it had to authenticate with something other than the ssh key that I provided. (a good explaination how to fix this in the .gitmodules file can be found at this website ... http://blog.tremily.us/posts/Relative_submodules/) What still could be discussed in this is issue is the error reporting by Jenkins / the GIT plugins in such a case. I guess it would be possible to put an additional warning or error message in the build log if a GIT repository uses submodules inside a repository that have the same host URL but use different protocols (http, https, ssh). A warning that such a scenario could be a potential missconfiguration in .gitmodules would make it more obvious that the error might be not coming from Jenkins or GIT themselves. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-31155) Workflow shared library improvements
Title: Message Title Brian Ray edited a comment on JENKINS-31155 Re: Workflow shared library improvements I am very slowly piloting a refactor of certain multijob and build DSL job chains into workflow DSL and the shared library mechanism is a bit of a sticking point because 1) the repo is 1) internal to Jenkins and 2) we're going to be an SVN shop for a long time to come.The approach implemented in that experimental plugin would be good for us, if it supported SVN. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [collapsing-console-sections-plugin] (JENKINS-31245) frame/content sizing
Title: Message Title Greg Moncreaff created an issue Jenkins / JENKINS-31245 frame/content sizing Issue Type: Improvement Assignee: Dean Yu Components: collapsing-console-sections-plugin, core Created: 28/Oct/15 7:34 PM Priority: Minor Reporter: Greg Moncreaff is there anyway to adjust the sizing of the frame where the collapsing sections puts its stuff (is this constrained to the build executor list width?). Goal is to avoid wraps. Options A. in main Jenkins be able to set frame width to some % of browser width (and buy a wider monitor) B. be able to change the font in the frame C. be able to size the frame as needed in the browser window D. on the fly adjust the font to be smaller for long section names All these imply that you want to size the font of the console navigator independently of the text in the console, otherwise you would just ctrl +/- in browser and affect both The reason I think this is possible is there is a bug when scrolling in the console, the frame width of the navigation frame changes (narrower if not at top of console output). This accident implies that maybe something can be done on purpose?
[JIRA] [workflow-plugin] (JENKINS-31155) Workflow shared library improvements
Title: Message Title Brian Ray commented on JENKINS-31155 Re: Workflow shared library improvements I am very slowly piloting a refactor of certain multijob and build DSL job chains into workflow DSL and the shared library mechanism is a bit of a sticking point because the repo is 1) internal to Jenkins and 2) we're going to be an SVN shop for a long time to come. The approach implemented in that experimental plugin would be good for us, if it supported SVN. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-31244) GIT plugin does use provided ssh key credentials for top-level repository, but not for submodules
Title: Message Title
Wolfgang Steiner updated an issue
Jenkins / JENKINS-31244
GIT plugin does use provided ssh key credentials for top-level repository, but not for submodules
Change By:
Wolfgang Steiner
I'm trying to clone a git repository that is hosted on a Atlassian Stash instance.The special case about the repository is that it has several submodules in it.Here is what I did to get to the error:1) I installed the latest git-plugin (2.4.0) / git-client-plugin (1.19.0) in Jenkins2) setup a ssh rsa key in Stash3) configured a Jenkins job to clone the repository from the Stash remote host (via ssh://)4) configured the ssh key & credentials in the Jenkins job git-plugin settingsnow when I run the build, Jenkins sucessfully clones the top-level git repository, but fails when trying to update the submodules (the error looks like Jenkins is trying to read username & password from a CLI, but only for the submodules){code:java}Gestartet durch Benutzer anonymousBaue in Arbeitsbereich C:\Program Files (x86)\Jenkins\jobs\test node\workspaceNo JDK named 'null' foundNo JDK named 'null' found > git.exe rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git.exe config remote.origin.url ssh://git@ logicxklubuild jenkinshost :7999/ipp/ipp-project.git # timeout=10Fetching upstream changes from ssh://git@ logicxklubuild jenkinshost :7999/ipp/ipp-project.git > git.exe --version # timeout=10using GIT_SSH to set credentials > git.exe -c core.askpass=true fetch --tags --progress ssh://git@ logicxklubuild jenkinshost :7999/ipp/ipp-project.git +refs/heads/*:refs/remotes/origin/* > git.exe rev-parse "refs/remotes/origin/master^{commit}" # timeout=10 > git.exe rev-parse "refs/remotes/origin/origin/master^{commit}" # timeout=10Checking out Revision a27c48024088c36e6eff3420c699ea1d1977e5cd (refs/remotes/origin/master)No JDK named 'null' found > git.exe config core.sparsecheckout # timeout=10 > git.exe checkout -f a27c48024088c36e6eff3420c699ea1d1977e5cd > git.exe rev-list a27c48024088c36e6eff3420c699ea1d1977e5cd # timeout=10 > git.exe remote # timeout=10 > git.exe submodule init # timeout=10 > git.exe submodule sync # timeout=10 > git.exe config --get remote.origin.url # timeout=10 > git.exe submodule updateFATAL: Command "git.exe submodule update" returned status code 1:stdout: stderr: Cloning into 'apps/ipp-app'...error: cannot spawn echo : No such file or directorybash: /dev/tty: No such device or addresserror: failed to execute prompt script (exit code 1)fatal: could not read Username for 'http:// logicxklubuild jenkinshost :7990': No errorClone of 'http:// logicxklubuild jenkinshost :7990/scm/ipp/ipp-app.git' into submodule path 'apps/ipp-app' failedhudson.plugins.git.GitException: Command "git.exe submodule update" returned status code 1:stdout: stderr: Cloning into 'apps/ipp-app'...error: cannot spawn echo : No such file or directorybash: /dev/tty: No such device or addresserror: failed to execute prompt script (exit code 1)fatal: could not read Username for 'http:// logicxklubuild jenkinshost :7990': No errorClone of 'http:// logicxklubuild jenkinshost :7990/scm/ipp/ipp-app.git' into submodule path 'apps/ipp-app' failed at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1640) at org.jenkinsc
[JIRA] [workflow-plugin] (JENKINS-31153) Rename workflow to pipeline
Title: Message Title Brian Ray commented on JENKINS-31153 Re: Rename workflow to pipeline Agree if only for the fact that I've been referring to the rewrite of my employer's Jenkins jobs chains (using workflow-plugin) as "pipeline" since the beginning of the project. Vanity aside, pipeline seems like a stronger brand to me. It connotes that interconnectedness mentioned above and seems more kinetic than "workflow." Ie, a product is actually moving through something to its ultimate destination. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-31244) GIT plugin does use provided ssh key credentials for top-level repository, but not for submodules
Title: Message Title Wolfgang Steiner created an issue Jenkins / JENKINS-31244 GIT plugin does use provided ssh key credentials for top-level repository, but not for submodules Issue Type: Bug Assignee: stephenconnolly Components: credentials-plugin, git-client-plugin, git-plugin Created: 28/Oct/15 7:14 PM Environment: Windows 10 x64 Jenkins 1.635 Labels: plugin git-plugin git credentials username password ssh Priority: Minor Reporter: Wolfgang Steiner I'm trying to clone a git repository that is hosted on a Atlassian Stash instance. The special case about the repository is that it has several submodules in it. Here is what I did to get to the error: 1) I installed the latest git-plugin (2.4.0) / git-client-plugin (1.19.0) in Jenkins 2) setup a ssh rsa key in Stash 3) configured a Jenkins job to clone the repository from the Stash remote host (via ssh://) 4) configured the ssh key & credentials in the Jenkins job git-plugin settings now when I run the build, Jenkins su
[JIRA] [envinject-plugin] (JENKINS-31243) EnvInject refuses to set 2 variables with the same character sequence but different case (example no_proxy and NO_PROXY)
Title: Message Title Kris Musard created an issue Jenkins / JENKINS-31243 EnvInject refuses to set 2 variables with the same character sequence but different case (example no_proxy and NO_PROXY) Issue Type: Bug Assignee: Oleg Nenashev Components: envinject-plugin Created: 28/Oct/15 7:08 PM Environment: Environment Injector Plugin 1.92.1 [root@localhost jenkins]# cat /etc/centos-release CentOS Linux release 7.0.1406 (Core) [root@localhost jenkins]# uname -a Linux localhost.localdomain 3.10.0-123.el7.x86_64 #1 SMP Mon Jun 30 12:09:22 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux [root@localhost jenkins]# /etc/alternatives/java -version openjdk version "1.8.0_60" OpenJDK Runtime Environment (build 1.8.0_60-b27) OpenJDK 64-Bit Server VM (build 25.60-b23, mixed mode) [root@localhost jenkins]# rpm -q jenkins jenkins-1.625.1-1.1.noarch Priority: Minor Reporter: Kris Musard I have tried this both using the key/value in the GUI and inside of a properties file. set no_proxy key and value set NO_PROXY key and value If the character sequence is the same aside from the case, the second variable will not be set. This is verified by looking in config.xml and returning back to the manage system page in the GUI and the second variable is not added. I think this is a bug since the shell allows you to do
[JIRA] [workflow-plugin] (JENKINS-30519) Declarative job properties in multibranch
Title: Message Title Jesse Glick resolved as Fixed 1, 2, and 3.1 done; enough for now, can file follow-up issues if the need arises for 3.2–5. Jenkins / JENKINS-30519 Declarative job properties in multibranch Change By: Jesse Glick Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26535) DescribableHelper does not handle wildcards well
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26535 Re: DescribableHelper does not handle wildcards well Code changed in jenkins User: Jesse Glick Path: multibranch/src/main/java/org/jenkinsci/plugins/workflow/multibranch/JobPropertyStep.java multibranch/src/test/java/org/jenkinsci/plugins/workflow/multibranch/JobPropertyStepTest.java step-api/src/main/java/org/jenkinsci/plugins/workflow/structs/DescribableHelper.java http://jenkins-ci.org/commit/workflow-plugin/b5302ebc2e2479f03c538060460e43d0c1c0b47a Log: JENKINS-26535 can be worked around using a collection of raw types. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27295) Boolean parameters injected as String
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27295 Re: Boolean parameters injected as String Code changed in jenkins User: Jesse Glick Path: multibranch/src/test/java/org/jenkinsci/plugins/workflow/multibranch/JobPropertyStepTest.java http://jenkins-ci.org/commit/workflow-plugin/4320015acd28c40e6cce462c15e86d4873762f55 Log: ParametersDefinitionProperty not set when the first build begins. Without JENKINS-27295, this makes it awkward to have a default parameter value. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-29726) Cannot upgrade ssh-credentials plugin
Title: Message Title
Edmund Haselwanter edited a comment on JENKINS-29726
Re: Cannot upgrade ssh-credentials plugin
same here { { noformat} sudo java -jar /var/cache/jenkins/war/WEB-INF/jenkins-cli.jar -s http://localhost:8080/ version1.628sudo java -jar /var/cache/jenkins/war/WEB-INF/jenkins-cli.jar -s http://localhost:8080/ list-plugins |grep credentialsplain-credentials Plain Credentials Plugin 1.1credentials Credentials Plugin 1.18 (1.24)ssh-credentials SSH Credentials Plugin 1.10 (1.11) Recipe: * remote_file[/var/chef/cache/credentials-1.24.plugin] action create (up to date)* remote_file[/var/chef/cache/jenkins-cli.jar] action create (up to date)- Upgrade jenkins_plugin[credentials] from 1.18 to 1.24* remote_file[/var/chef/cache/ssh-credentials-1.11.plugin] action create (up to date)- Upgrade jenkins_plugin[ssh-credentials] from 1.10 to 1.11sudo java -jar /var/cache/jenkins/war/WEB-INF/jenkins-cli.jar -s http://localhost:8080/ list-plugins |grep credentialsplain-credentials Plain Credentials Plugin 1.1credentials Credentials Plugin 1.18 (1.24)ssh-credentials SSH Credentials Plugin 1.10 (1.11) {noformat } }
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-29726) Cannot upgrade ssh-credentials plugin
Title: Message Title
Edmund Haselwanter edited a comment on JENKINS-29726
Re: Cannot upgrade ssh-credentials plugin
same here ``` {{ sudo java -jar /var/cache/jenkins/war/WEB-INF/jenkins-cli.jar -s http://localhost:8080/ version1.628sudo java -jar /var/cache/jenkins/war/WEB-INF/jenkins-cli.jar -s http://localhost:8080/ list-plugins |grep credentialsplain-credentials Plain Credentials Plugin 1.1credentials Credentials Plugin 1.18 (1.24)ssh-credentials SSH Credentials Plugin 1.10 (1.11) Recipe: * remote_file[/var/chef/cache/credentials-1.24.plugin] action create (up to date)* remote_file[/var/chef/cache/jenkins-cli.jar] action create (up to date)- Upgrade jenkins_plugin[credentials] from 1.18 to 1.24* remote_file[/var/chef/cache/ssh-credentials-1.11.plugin] action create (up to date)- Upgrade jenkins_plugin[ssh-credentials] from 1.10 to 1.11sudo java -jar /var/cache/jenkins/war/WEB-INF/jenkins-cli.jar -s http://localhost:8080/ list-plugins |grep credentialsplain-credentials Plain Credentials Plugin 1.1credentials Credentials Plugin 1.18 (1.24)ssh-credentials SSH Credentials Plugin 1.10 (1.11) }} ```
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-29726) Cannot upgrade ssh-credentials plugin
Title: Message Title Edmund Haselwanter commented on JENKINS-29726 Re: Cannot upgrade ssh-credentials plugin same here ``` sudo java -jar /var/cache/jenkins/war/WEB-INF/jenkins-cli.jar -s http://localhost:8080/ version 1.628 sudo java -jar /var/cache/jenkins/war/WEB-INF/jenkins-cli.jar -s http://localhost:8080/ list-plugins |grep credentials plain-credentials Plain Credentials Plugin 1.1 credentials Credentials Plugin 1.18 (1.24) ssh-credentials SSH Credentials Plugin 1.10 (1.11) Recipe: remote_file[/var/chef/cache/credentials-1.24.plugin] action create (up to date) remote_file[/var/chef/cache/jenkins-cli.jar] action create (up to date) Upgrade jenkins_plugin[credentials] from 1.18 to 1.24 remote_file[/var/chef/cache/ssh-credentials-1.11.plugin] action create (up to date) Upgrade jenkins_plugin[ssh-credentials] from 1.10 to 1.11 sudo java -jar /var/cache/jenkins/war/WEB-INF/jenkins-cli.jar -s http://localhost:8080/ list-plugins |grep credentials plain-credentials Plain Credentials Plugin 1.1 credentials Credentials Plugin 1.18 (1.24) ssh-credentials SSH Credentials Plugin 1.10 (1.11) ``` Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [workflow-plugin] (JENKINS-31152) 2.0: Pipeline as code in front & center
Title: Message Title Jesse Glick commented on JENKINS-31152 Re: 2.0: Pipeline as code in front & center John Mellor the “proposed” solution already exists and is available for use, so I am not sure why the description was worded the way it was. This is not the place to ask for technical help. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-31152) 2.0: Pipeline as code in front & center
Title: Message Title John Mellor commented on JENKINS-31152 Re: 2.0: Pipeline as code in front & center I have one project that has ~130 sub-builds, in a fairly complex ordering tree with some build threads in parallel and then some in serial, and then some in parallel again. Almost all steps are freestyle builds running autotools and make or a modified debuild. Are we going to be able to bring the job steps together into several choke-points throughout the pipeline, or is the proposed solution going to be more simplistic? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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 Jesse Glick commented on JENKINS-31153 Re: Rename workflow to pipeline Still unsure about renaming the GitHub repository. This could be disruptive. Anyway I want to move toward putting plugins in their own repos wherever possible, and these will be workflow-something-plugin to follow the convention of naming the repository after the short name / artifact ID, and it would be confusing to have pipeline-plugin as one repository and workflow-something-plugin closely related to that. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [accurev-plugin] (JENKINS-30336) Accurev plugin 0.6.33 does not work with Accurev installation on Mac ios Yosemite 10.10.5
Title: Message Title Jeremy Tellier commented on JENKINS-30336 Re: Accurev plugin 0.6.33 does not work with Accurev installation on Mac ios Yosemite 10.10.5 I am having this problem as well, any updates? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [winstone-jetty] (JENKINS-31242) server uses weak ephemeral Diffie-Hellman key in the server exchange handshake
Title: Message Title
Roger Moore updated an issue
Jenkins / JENKINS-31242
server uses weak ephemeral Diffie-Hellman key in the server exchange handshake
Change By:
Roger Moore
Daniel Beck asked me to create this issue. Jenkins cannot be accessed after Chrome was updated to v45 and FireFox was updated to v39? Chrome reports:"This error can occur when connecting to a secure (HTTPS) server. It means that the server is trying to set up a secure connection but, due to a disastrous misconfiguration, the connection wouldn't be secure at all! In this case the server needs to be fixed. Google Chrome won't use insecure connections in order to protect your privacy."Firefox v39.0 reports:"An error occurred during a connection to 'servername:portnumber'. SSL received a weak ephemeral Diffie-Hellman key in Server Key Exchange handshake message. (Error code: ssl_error_weak_server_ephemeral_dh_key)."I can connect using IE and Safari though.The Jenkins logs do not provide messages at the time when the attempt to connect is made.I tried looking at the Jenkins configuration and using Google searches, but could not find where to change the setting in Jenkins to force Jenkins to use the stronger key.We already are using 1024-bit certificates.I am using the default installation/configuration of Jenkins which I understand is Jetty. But I have configured it to use https on a port that our IT department requires me to use.Therefore, the command that runs is (some info modified for brevity and security): {{ java -Dcom.sun.akuma.Daemon=daemonized-Djava.awt.headless=true -DJENKINS_HOME=/var/lib/jenkins -jar/usr/lib/jenkins/jenkins.war --logfile=jenkins.log --webroot=/var/cache/jenkins/war--daemon --httpPort=-1 --httpsPort=ourportnumber --httpsKeyStore=locationOfOurKeyStore --httpsKeyStorePassword=xxx --httpsListenAddress:0.0.0.0 --ajp13Port=a_port_number --debug=5 --handlerCountMax=100 --handlerCountMaxIdle=20 }} I had thought the Jetty config file would be in/var/cache/Jenkins/war or in /usr/lib/jenkins/jenkins.war but I didn't see the cipher related entries in .xml files in the former and didn't want to change anything in the latter. I also looked in /var/lib/jenkins but didn't see anything that matched what I thought I was looking for there either.My real question then is what do I modify in our Jenkins implementation to get around this issue? Assuming that there is something to modify...Roger Moore
Add Comment
[JIRA] [core] (JENKINS-31217) No JDK named ‘null’ found in Jenkins 1.635
Title: Message Title Jesse Glick commented on JENKINS-31217 Re: No JDK named ‘null’ found in Jenkins 1.635 For the workaround you might need to create a dummy JDK so you can not select it. See JENKINS-10191 and JENKINS-17373. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [winstone-jetty] (JENKINS-31242) server uses weak ephemeral Diffie-Hellman key in the server exchange handshake
Title: Message Title
Roger Moore updated an issue
Jenkins / JENKINS-31242
server uses weak ephemeral Diffie-Hellman key in the server exchange handshake
Change By:
Roger Moore
Daniel Beck asked me to create this issue. Jenkins cannot be accessed after Chrome was updated to v45 and FireFox was updated to v39? Chrome reports:"This error can occur when connecting to a secure (HTTPS) server. It means that the server is trying to set up a secure connection but, due to a disastrous misconfiguration, the connection wouldn't be secure at all! In this case the server needs to be fixed. Google Chrome won't use insecure connections in order to protect your privacy."Firefox v39.0 reports:"An error occurred during a connection to 'servername:portnumber'. SSL received a weak ephemeral Diffie-Hellman key in Server Key Exchange handshake message. (Error code: ssl_error_weak_server_ephemeral_dh_key)."I can connect using IE and Safari though.The Jenkins logs do not provide messages at the time when the attempt to connect is made.I tried looking at the Jenkins configuration and using Google searches, but could not find where to change the setting in Jenkins to force Jenkins to use the stronger key.We already are using 1024-bit certificates.I am using the default installation/configuration of Jenkins which I understand is Jetty. But I have configured it to use https on a port that our IT department requires me to use.Therefore, the command that runs is (some info modified for brevity and security): {{ java -Dcom.sun.akuma.Daemon=daemonized-Djava.awt.headless=true -DJENKINS_HOME=/var/lib/jenkins -jar/usr/lib/jenkins/jenkins.war --logfile=jenkins.log --webroot=/var/cache/jenkins/war--daemon --httpPort=-1 --httpsPort=ourportnumber --httpsKeyStore=locationOfOurKeyStore --httpsKeyStorePassword=xxx --httpsListenAddress:0.0.0.0 --ajp13Port=a_port_number --debug=5 --handlerCountMax=100 --handlerCountMaxIdle=20 }} I had thought the Jetty config file would be in/var/cache/Jenkins/war or in /usr/lib/jenkins/jenkins.war but I didn't see the cipher related entries in .xml files in the former and didn't want to change anything in the latter. I also looked in /var/lib/jenkins but didn't see anything that matched what I thought I was looking for there either.My real question then is what do I modify in our Jenkins implementation to get around this issue? Assuming that there is something to modify...Roger Moore
Add Comment
[JIRA] [winstone-jetty] (JENKINS-31242) server uses weak ephemeral Diffie-Hellman key in the server exchange handshake
Title: Message Title Roger Moore updated an issue Jenkins / JENKINS-31242 server uses weak ephemeral Diffie-Hellman key in the server exchange handshake Change By: Roger Moore Daniel Beck asked me to create this issue. Jenkins cannot be accessed after Chrome was updated to v45 and FireFox was updated to v39? Chrome reports:"This error can occur when connecting to a secure (HTTPS) server. It means that the server is trying to set up a secure connection but, due to a disastrous misconfiguration, the connection wouldn't be secure at all! In this case the server needs to be fixed. Google Chrome won't use insecure connections in order to protect your privacy."Firefox v39.0 reports:"An error occurred during a connection to 'servername:portnumber'. SSL received a weak ephemeral Diffie-Hellman key in Server Key Exchange handshake message. (Error code: ssl_error_weak_server_ephemeral_dh_key)."I can connect using IE and Safari though.The Jenkins logs do not provide messages at the time when the attempt to connect is made.I tried looking at the Jenkins configuration and using Google searches, but could not find where to change the setting in Jenkins to force Jenkins to use the stronger key.We already are using 1024-bit certificates.I am using the default installation/configuration of Jenkins which I understand is Jetty. But I have configured it to use https on a port that our IT department requires me to use.Therefore, the command that runs is (some info modified for brevity and security):java -Dcom.sun.akuma.Daemon=daemonized-Djava.awt.headless=true -DJENKINS_HOME=/var/lib/jenkins -jar/usr/lib/jenkins/jenkins.war --logfile=jenkins.log --webroot=/var/cache/jenkins/war--daemon --httpPort=-1 --httpsPort=ourportnumber--httpsKeyStore=locationOfOurKeyStore --httpsKeyStorePassword=xxx--httpsListenAddress:0.0.0.0 --ajp13Port=a_port_number --debug=5--handlerCountMax=100 --handlerCountMaxIdle=20 I had thought the Jetty config file would be in/var/cache/Jenkins/war or in /usr/lib/jenkins/jenkins.war but I didn't see the cipher related entries in .xml files in the former and didn't want to change anything in the latter. I also looked in /var/lib/jenkins but didn't see anything that matched what I thought I was looking for there either.My real question then is what do I modify in our Jenkins implementation to get around this issue? Assuming that there is something to modify...Roger Moore Add Comment
[JIRA] [winstone-jetty] (JENKINS-31242) server uses weak ephemeral Diffie-Hellman key in the server exchange handshake
Title: Message Title Roger Moore updated an issue Jenkins / JENKINS-31242 server uses weak ephemeral Diffie-Hellman key in the server exchange handshake Change By: Roger Moore Daniel Beck asked me to create this issue. Jenkins cannot be accessed after Chrome was updated to v45 and FireFox was updated to v39? Chrome reports:"This error can occur when connecting to a secure (HTTPS) server. It means that the server is trying to set up a secure connection but, due to a disastrous misconfiguration, the connection wouldn't be secure at all! In this case the server needs to be fixed. Google Chrome won't use insecure connections in order to protect your privacy."Firefox v39.0 reports:"An error occurred during a connection to 'servername:portnumber'. SSL received a weak ephemeral Diffie-Hellman key in Server Key Exchange handshake message. (Error code: ssl_error_weak_server_ephemeral_dh_key)."I can connect using IE and Safari though.The Jenkins logs do not provide messages at the time when the attempt to connect is made.I tried looking at the Jenkins configuration and using Google searches, but could not find where to change the setting in Jenkins to force Jenkins to use the stronger key.We already are using 1024-bit certificates.I am using the default installation/configuration of Jenkins which I understand is Jetty. But I have configured it to use https on a port that our IT department requires me to use.Therefore, the command that runs is (some info modified for brevity and security):java -Dcom.sun.akuma.Daemon=daemonized-Djava.awt.headless=true -DJENKINS_HOME=/var/lib/jenkins -jar/usr/lib/jenkins/jenkins.war --logfile=jenkins.log --webroot=/var/cache/jenkins/war--daemon --httpPort=-1 --httpsPort=ourportnumber--httpsKeyStore=locationOfOurKeyStore --httpsKeyStorePassword=xxx--httpsListenAddress:0.0.0.0 --ajp13Port=a_port_number --debug=5--handlerCountMax=100 --handlerCountMaxIdle=20 I had thought the Jetty config file would be in/var/cache/Jenkins/war or in /usr/lib/jenkins/jenkins.war but I didn't see the cipher related entries in .xml files in the former and didn't want to change anything in the latter. I also looked in /var/lib/jenkins but didn't see anything that matched what I thought I was looking for there either.My real question then is what do I modify in our Jenkins implementation to get around this issue? Assuming that there is something to modify...Roger Moore Add Comment
[JIRA] [winstone-jetty] (JENKINS-31242) server uses weak ephemeral Diffie-Hellman key in the server exchange handshake
Title: Message Title Roger Moore created an issue Jenkins / JENKINS-31242 server uses weak ephemeral Diffie-Hellman key in the server exchange handshake Issue Type: Improvement Assignee: Unassigned Components: winstone-jetty Created: 28/Oct/15 6:02 PM Environment: Jenkins 1.596, Chrome v45+, Firefox v39+ Labels: security configuration Priority: Minor Reporter: Roger Moore Daniel Beck asked me to create this issue. Jenkins cannot be accessed after Chrome was updated to v45 and FireFox was updated to v39? Chrome reports: "This error can occur when connecting to a secure (HTTPS) server. It means that the server is trying to set up a secure connection but, due to a disastrous misconfiguration, the connection wouldn't be secure at all! In this case the server needs to be fixed. Google Chrome won't use insecure connections in order to prote
[JIRA] [sonar-gerrit-plugin] (JENKINS-31241) Check and fix process for whole-file SonarQube issues.
Title: Message Title Tatiana Didik created an issue Jenkins / JENKINS-31241 Check and fix process for whole-file SonarQube issues. Issue Type: Improvement Assignee: Tatiana Didik Components: sonar-gerrit-plugin Created: 28/Oct/15 6:00 PM Priority: Critical Reporter: Tatiana Didik Process whole-file SonarQube issues: post this issues as comment to whole file if "comments to changed lines only" is unchecked. Add Comment This message was sent by At
[JIRA] [sonar-gerrit-plugin] (JENKINS-31240) Hide score settings if "Post score" is not checked.
Title: Message Title Tatiana Didik updated an issue Jenkins / JENKINS-31240 Hide score settings if "Post score" is not checked. Change By: Tatiana Didik Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sonar-gerrit-plugin] (JENKINS-31240) Hide score settings if "Post score" is not checked.
Title: Message Title Tatiana Didik created an issue Jenkins / JENKINS-31240 Hide score settings if "Post score" is not checked. Issue Type: Bug Assignee: Tatiana Didik Components: sonar-gerrit-plugin Created: 28/Oct/15 5:56 PM Priority: Minor Reporter: Tatiana Didik Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Go
