[JIRA] (JENKINS-50125) Jenkins parameters missing in build when using jira trigger
Title: Message Title Wisen Tanasa resolved as Fixed Jenkins / JENKINS-50125 Jenkins parameters missing in build when using jira trigger Change By: Wisen Tanasa Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50125) Jenkins parameters missing in build when using jira trigger
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50125 Re: Jenkins parameters missing in build when using jira trigger Code changed in jenkins User: Wisen Tanasa Path: src/integrationTest/groovy/com/ceilfors/jenkins/plugins/jiratrigger/JiraTriggerIntegrationTest.groovy src/integrationTest/groovy/com/ceilfors/jenkins/plugins/jiratrigger/integration/JiraTriggerProject.groovy http://jenkins-ci.org/commit/jira-trigger-plugin/f7b2deeec3ad4519648a77e8fb16c19fa6513258 Log: JENKINS-50125 Abstract ParametersDefinitionProperty creation in test. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50125) Jenkins parameters missing in build when using jira trigger
Title: Message Title Wisen Tanasa commented on JENKINS-50125 Re: Jenkins parameters missing in build when using jira trigger Fixed in 0.6.2. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50125) Jenkins parameters missing in build when using jira trigger
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50125 Re: Jenkins parameters missing in build when using jira trigger Code changed in jenkins User: Wisen Tanasa Path: src/integrationTest/groovy/com/ceilfors/jenkins/plugins/jiratrigger/JiraTriggerIntegrationTest.groovy src/integrationTest/groovy/com/ceilfors/jenkins/plugins/jiratrigger/integration/JiraTriggerProject.groovy src/main/groovy/com/ceilfors/jenkins/plugins/jiratrigger/JiraTrigger.groovy src/main/groovy/com/ceilfors/jenkins/plugins/jiratrigger/parameter/DefaultParametersAction.groovy http://jenkins-ci.org/commit/jira-trigger-plugin/ec0e6c1850a587d8930f732869c2869342cdf904 Log: JENKINS-50125 Add DefaultParametersAction to triggered job. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26138) Support workspaces for Pipeline jobs
Title: Message Title Andrew Gray commented on JENKINS-26138 Re: Support workspaces for Pipeline jobs Yes bharath ganesh kumar balasubrmanian, but where is the Wipe Out Workspace button? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50931) EC2 Instance cap is not respected
Title: Message Title A B created an issue Jenkins / JENKINS-50931 EC2 Instance cap is not respected Issue Type: Bug Assignee: Francis Upton Attachments: 1 - Configure EC2 plugin.png, 2 - Multiple instances are launched.png, 3 - Software versions.png Components: ec2-plugin Created: 2018-04-23 04:06 Environment: Jenkins version: 2.107.1 ec2-plugin version: 1.39 Java version: 8u151 OS: Linux (4.4.0-1052-aws) Labels: ec2 ec2-plugin aws configuration Priority: Major Reporter: A B In Manage Jenkins -> Configure System -> Cloud -> Advanced, I set "Instance Cap" to 5 I push changes to many branches (more than 5) In the sidebar, I see that more than 5 instances have been created. I expected that a maximum of 5 instances would be created. I am using EC2 spot instances in the ap-southeast-2 region. I have only one 'cloud' set up, and all the instances are building (different branches of) the same job. Please let me know if any other information would be helpful. (I see that this bug has been reported previously, but closed. Is this a regression? Am I doing something wrong?)
[JIRA] (JENKINS-50930) Multibranch fails if gerrit lives at a subdirectory
Title: Message Title
Will Saxon updated an issue
Jenkins / JENKINS-50930
Multibranch fails if gerrit lives at a subdirectory
Change By:
Will Saxon
I enabled the http scheme this evening and tried to set up a multibranch job. I put in the clone URL - http://gerrit/gerrit/a/repo - and received the following error:{noformat}ERROR: [Sun Apr 22 23:25:24 EDT 2018] Could not fetch branches from source bc69d1d2-f5e2-4030-a2d4-a322692fddafcom.urswolfer.gerrit.client.rest.http.HttpStatusException: Request not successful. Message: Not Found. Status-Code: 404. Content: 404 Not FoundNot FoundThe requested URL /a/changes/ was not found on this server.Apache/2.4.18 (Ubuntu) Server at gerrit Port 80. at com.urswolfer.gerrit.client.rest.http.GerritRestClient.throwHttpStatusException(GerritRestClient.java:467) at com.urswolfer.gerrit.client.rest.http.GerritRestClient.checkStatusCodeError(GerritRestClient.java:454) at com.urswolfer.gerrit.client.rest.http.GerritRestClient.checkStatusCodeClientError(GerritRestClient.java:440) at com.urswolfer.gerrit.client.rest.http.GerritRestClient.checkStatusCode(GerritRestClient.java:432) at com.urswolfer.gerrit.client.rest.http.GerritRestClient.request(GerritRestClient.java:227) at com.urswolfer.gerrit.client.rest.http.GerritRestClient.requestRest(GerritRestClient.java:163) at com.urswolfer.gerrit.client.rest.http.GerritRestClient.requestRest(GerritRestClient.java:155) at com.urswolfer.gerrit.client.rest.http.GerritRestClient.requestJson(GerritRestClient.java:132) at com.urswolfer.gerrit.client.rest.http.GerritRestClient.getRequest(GerritRestClient.java:101) at com.urswolfer.gerrit.client.rest.http.changes.ChangesRestClient.get(ChangesRestClient.java:113) at com.urswolfer.gerrit.client.rest.http.changes.ChangesRestClient.access$000(ChangesRestClient.java:35) at com.urswolfer.gerrit.client.rest.http.changes.ChangesRestClient$1.get(ChangesRestClient.java:78) at jenkins.plugins.gerrit.AbstractGerritSCMSource.getOpenChanges(AbstractGerritSCMSource.java:175) at jenkins.plugins.gerrit.AbstractGerritSCMSource.access$100(AbstractGerritSCMSource.java:59) at jenkins.plugins.gerrit.AbstractGerritSCMSource$1.discoverBranches(AbstractGerritSCMSource.java:124)Caused: java.io.IOException at jenkins.plugins.gerrit.AbstractGerritSCMSource$1.discoverBranches(AbstractGerritSCMSource.java:156) at jenkins.plugins.gerrit.AbstractGerritSCMSource$1.run(AbstractGerritSCMSource.java:98) at jenkins.plugins.gerrit.AbstractGerritSCMSource$1.run(AbstractGerritSCMSource.java:82) at jenkins.plugins.gerrit.AbstractGerritSCMSource.doRetrieve(AbstractGerritSCMSource.java:497) at jenkins.plugins.gerrit.AbstractGerritSCMSource.retrieve(AbstractGerritSCMSource.java:81) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:357) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:267) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:633) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:276) at
[JIRA] (JENKINS-50930) Multibranch fails if gerrit lives at a subdirectory
Title: Message Title
Will Saxon updated an issue
Jenkins / JENKINS-50930
Multibranch fails if gerrit lives at a subdirectory
Change By:
Will Saxon
I enabled the http scheme this evening and tried to set up a multibranch job. I put in the clone URL - http://gerrit/gerrit/a/repo - and received the following error:{noformat}ERROR: [Sun Apr 22 23:25:24 EDT 2018] Could not fetch branches from source bc69d1d2-f5e2-4030-a2d4-a322692fddafcom.urswolfer.gerrit.client.rest.http.HttpStatusException: Request not successful. Message: Not Found. Status-Code: 404. Content: 404 Not FoundNot FoundThe requested URL /a/changes/ was not found on this server.Apache/2.4.18 (Ubuntu) Server at gerrit Port 80. at com.urswolfer.gerrit.client.rest.http.GerritRestClient.throwHttpStatusException(GerritRestClient.java:467) at com.urswolfer.gerrit.client.rest.http.GerritRestClient.checkStatusCodeError(GerritRestClient.java:454) at com . urswolfer . gerrit . snipped client.rest.http.GerritRestClient.checkStatusCodeClientError(GerritRestClient.java:440) at com.urswolfer.gerrit.client.rest.http.GerritRestClient.checkStatusCode(GerritRestClient.java:432) at com.urswolfer.gerrit.client.rest.http.GerritRestClient.request(GerritRestClient.java:227) at com.urswolfer.gerrit.client.rest.http.GerritRestClient.requestRest(GerritRestClient.java:163) at com.urswolfer.gerrit.client.rest.http.GerritRestClient.requestRest(GerritRestClient.java:155) at com.urswolfer.gerrit.client.rest.http.GerritRestClient.requestJson(GerritRestClient.java:132) at com.urswolfer.gerrit.client.rest.http.GerritRestClient.getRequest(GerritRestClient.java:101) at com.urswolfer.gerrit.client.rest.http.changes.ChangesRestClient.get(ChangesRestClient.java:113) at com.urswolfer.gerrit.client.rest.http.changes.ChangesRestClient.access$000(ChangesRestClient.java:35) at com.urswolfer.gerrit.client.rest.http.changes.ChangesRestClient$1.get(ChangesRestClient.java:78) at jenkins.plugins.gerrit.AbstractGerritSCMSource.getOpenChanges(AbstractGerritSCMSource.java:175) at jenkins.plugins.gerrit.AbstractGerritSCMSource.access$100(AbstractGerritSCMSource.java:59) at jenkins.plugins.gerrit.AbstractGerritSCMSource$1.discoverBranches(AbstractGerritSCMSource.java:124)Caused: java.io.IOException at jenkins.plugins.gerrit.AbstractGerritSCMSource$1.discoverBranches(AbstractGerritSCMSource.java:156) at jenkins.plugins.gerrit.AbstractGerritSCMSource$1.run(AbstractGerritSCMSource.java:98) at jenkins.plugins.gerrit.AbstractGerritSCMSource$1.run(AbstractGerritSCMSource.java:82) at jenkins.plugins.gerrit.AbstractGerritSCMSource.doRetrieve(AbstractGerritSCMSource.java:497) at jenkins.plugins.gerrit.AbstractGerritSCMSource.retrieve(AbstractGerritSCMSource.java:81) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:357) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:267) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:633) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:276) at
[JIRA] (JENKINS-50930) Multibranch fails if gerrit lives at a subdirectory
Title: Message Title
Will Saxon updated an issue
Jenkins / JENKINS-50930
Multibranch fails if gerrit lives at a subdirectory
Change By:
Will Saxon
I enabled the http scheme this evening and tried to set up a multibranch job. I put in the clone URL - http://gerrit/gerrit/a/repo - and received the following error:{noformat}ERROR: [Sun Apr 22 23:25:24 EDT 2018] Could not fetch branches from source bc69d1d2-f5e2-4030-a2d4-a322692fddafcom.urswolfer.gerrit.client.rest.http.HttpStatusException: Request not successful. Message: Not Found. Status-Code: 404. Content: 404 Not FoundNot FoundThe requested URL /a/changes/ was not found on this server.Apache/2.4.18 (Ubuntu) Server at gerrit Port 80. at com.urswolfer.gerrit.client.rest.http.GerritRestClient.throwHttpStatusException(GerritRestClient.java:467) at com.urswolfer.gerrit.client.rest.http.GerritRestClient.checkStatusCodeError(GerritRestClient.java:454) at com.urswolfer.gerrit.client.rest.http.GerritRestClient.checkStatusCodeClientError(GerritRestClient.java:440) at com.urswolfer.gerrit.client.rest.http.GerritRestClient.checkStatusCode(GerritRestClient.java:432) at com.urswolfer.gerrit.client.rest.http.GerritRestClient.request(GerritRestClient.java:227) at com.urswolfer.gerrit.client.rest.http.GerritRestClient.requestRest(GerritRestClient.java:163) at com.urswolfer.gerrit.client.rest.http.GerritRestClient.requestRest(GerritRestClient.java:155) at com.urswolfer.gerrit.client.rest.http.GerritRestClient.requestJson(GerritRestClient.java:132) at com.urswolfer.gerrit.client.rest.http.GerritRestClient.getRequest(GerritRestClient.java:101) at com.urswolfer.gerrit.client.rest.http.changes.ChangesRestClient.get(ChangesRestClient.java:113) at com.urswolfer.gerrit.client.rest.http.changes.ChangesRestClient.access$000(ChangesRestClient.java:35) at com.urswolfer.gerrit.client.rest.http.changes.ChangesRestClient$1.get(ChangesRestClient.java:78) at jenkins.plugins.gerrit.AbstractGerritSCMSource.getOpenChanges(AbstractGerritSCMSource.java:175) at jenkins.plugins.gerrit.AbstractGerritSCMSource.access$100(AbstractGerritSCMSource.java:59) at jenkins.plugins.gerrit.AbstractGerritSCMSource$1.discoverBranches(AbstractGerritSCMSource.java:124)Caused: java.io.IOException at jenkins.plugins.gerrit.AbstractGerritSCMSource$1.discoverBranches(AbstractGerritSCMSource.java:156) at jenkins.plugins.gerrit.AbstractGerritSCMSource$1.run(AbstractGerritSCMSource.java:98) at jenkins.plugins.gerrit.AbstractGerritSCMSource$1.run(AbstractGerritSCMSource.java:82) at jenkins.plugins.gerrit.AbstractGerritSCMSource.doRetrieve(AbstractGerritSCMSource.java:497) at jenkins.plugins.gerrit.AbstractGerritSCMSource.retrieve(AbstractGerritSCMSource.java:81) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:357) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:267) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:633) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:276) at
[JIRA] (JENKINS-50930) Multibranch fails if gerrit lives at a subdirectory
Title: Message Title Will Saxon created an issue Jenkins / JENKINS-50930 Multibranch fails if gerrit lives at a subdirectory Issue Type: Bug Assignee: lucamilanesio Components: gerrit-code-review-plugin Created: 2018-04-23 03:34 Environment: Apache 2.4 as reverse proxy, Gerrit lives at http://gerrit/gerrit. Gerrit 2.14.6, plugin version 0.1.1 with Jenkins 2.107.1 Priority: Major Reporter: Will Saxon I enabled the http scheme this evening and tried to set up a multibranch job. I put in the clone URL - http://gerrit/gerrit/a/repo - and received the following error: ERROR: [Sun Apr 22 23:25:24 EDT 2018] Could not fetch branches from source bc69d1d2-f5e2-4030-a2d4-a322692fddaf com.urswolfer.gerrit.client.rest.http.HttpStatusException: Request not successful. Message: Not Found. Status-Code: 404. Content: 404 Not Found Not Found The requested URL /a/changes/ was not found on this server. Apache/2.4.18 (Ubuntu) Server at gerrit Port 80 . at com.urswolfer.gerrit.client.rest.http.GerritRestClient.throwHttpStatusException(GerritRestClient.java:467) at com.urswolfer.gerrit.client.rest.http.GerritRestClient.checkStatusCodeError(GerritRestClient.java:454) at ... snipped I don't think there's currently a workaround for this other than mapping /a to /gerrit/a on my server. Am I correct?
[JIRA] (JENKINS-10383) platformlabeler plugin doesn't detect 64-bit windows
Title: Message Title SCM/JIRA link daemon commented on JENKINS-10383 Re: platformlabeler plugin doesn't detect 64-bit windows Code changed in jenkins User: Mark Waite Path: src/main/java/org/jvnet/hudson/plugins/platformlabeler/PlatformDetailsTask.java http://jenkins-ci.org/commit/platformlabeler-plugin/798c90fc19d99eac532b22b2205a4814fd0abf0a Log: Undo compatibility breaks of PR#2 & JENKINS-10383 Prefer compatibility with prior behavior over new names for Windows operating system versions. Reverts some of the changes from the fix for JENKINS-10383. The plugin has not been released in 5+ years. Users have adapted to the existing behavior and will value retaining existing behavior more than they will value additional detection of specifically named Windows versions. Retain SunOS behavior from platformlabeler 1.1 The code in the 1.1 release accepted os.name as an argument, folded it to lower case, then compared the result with "SunOS". Since there are upper case characters in "SunOS", the comparison would never have matched. Since it did not match, the result fell through to return the lower case form "sunos" rather than "solaris" the code hints was intended. Fix JENKINS-10383 - report bits of platform instead of JRE JENKINS-10383 changes behavior on 64 bit Windows and 64 bit Linux running a 32 bit JRE. Release 1.1 reported "x86" (32 bit) on a 32 bit JRE running on a 64 bit operating system. Release 2.0 and later reports "amd64" (64 bit) on a 32 bit JRE running on a 64 bit operating system. Before JENKINS-10383 the bits of the JRE were reported. After JENKINS-10383 the bits of the operating system are reported. There is no behavioral change for 32 bit machines running a 32 bit JRE. There is no behavioral change for 64 bit machines running a 64 bit JRE. There is no behavioral change for machines that are not Windows and not Linux. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50740) gitlabCommitStatus clobbers Groovy compilation exceptions
Title: Message Title Owen Mehegan commented on JENKINS-50740 Re: gitlabCommitStatus clobbers Groovy compilation exceptions Andrew Bayer any chance you could give me a pointer about how gitlab-plugin might handle this scenario more gracefully? I'm surprised that something we do causes the more useful exception to be swallowed. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50925) jenkins returns internal server error (500) when sending a push hook from GitLab
Title: Message Title Owen Mehegan commented on JENKINS-50925 Re: jenkins returns internal server error (500) when sending a push hook from GitLab What versions of GitLab and gitlab-plugin are you using? How exactly are you sending the test webhook request? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50756) HTML and LRA folder not getting created after LR scenario execution with Jenkins
Title: Message Title Ashwin Unnikrishnan commented on JENKINS-50756 Re: HTML and LRA folder not getting created after LR scenario execution with Jenkins Hi, Any updates on this issue? Thanks Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24766) Add support to multiple Xcode versions
Title: Message Title Kazuhide Takahashi assigned an issue to Kazuhide Takahashi I Add function for support multiple versions of Xcode without using 'EnvInject Plugin'. Because it seems that codesign of xcodebuild has a problem with recently released Xcode 9.3, the archive built with app-store can not be signed with AdHoc provisioning profile for the following error. I have not yet merged to master, PR etc. Because we need more tests and reviews. My branch https://github.com/kazuhidet/xcode-plugin/commits/xcode_select Jenkins / JENKINS-24766 Add support to multiple Xcode versions Change By: Kazuhide Takahashi Assignee: Kazuhide Takahashi Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues"
[JIRA] (JENKINS-50920) NPM registry credentials not correctly formatted
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-50920 NPM registry credentials not correctly formatted Change By: Dominik Bartholdi Component/s: config-file-provider-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50920) NPM registry credentials not correctly formatted
Title: Message Title Dominik Bartholdi assigned an issue to Nikolas Falco Jenkins / JENKINS-50920 NPM registry credentials not correctly formatted Change By: Dominik Bartholdi Assignee: Dominik Bartholdi Nikolas Falco Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33990) Polling support
Title: Message Title Wisen Tanasa commented on JENKINS-33990 Re: Polling support Confirmed that JIRA Cloud webhook is working with JIRA Trigger Plugin. We no longer need the polling support. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33990) Polling support
Title: Message Title Wisen Tanasa closed an issue as Won't Do Jenkins / JENKINS-33990 Polling support Change By: Wisen Tanasa Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50846) Cannot start build runner due to Trend error even if no Trend option is selected
Title: Message Title Daniel Danan resolved as Fixed solution in hp-application-automation-tools-plugin-5.3.5 Jenkins / JENKINS-50846 Cannot start build runner due to Trend error even if no Trend option is selected Change By: Daniel Danan Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options,
[JIRA] (JENKINS-50929) Add ability to Performance Center Jenkins plugin to upload vuserLog.zip artefact in the end of Load Test
Title: Message Title Alex Geifman created an issue Jenkins / JENKINS-50929 Add ability to Performance Center Jenkins plugin to upload vuserLog.zip artefact in the end of Load Test Issue Type: Improvement Assignee: Hanan Bem Attachments: image-2018-04-22-17-16-36-001.png Components: performance-plugin Created: 2018-04-22 14:21 Priority: Major Reporter: Alex Geifman Currently only HTML report is uploaded into Jenkins repository and available for download by user. There is a need to also upload VuserLog so that it will be available for downloading by Jenkins plugin user after the performance test has ended. Add Comment
[JIRA] (JENKINS-50927) [SRF] Failed to present report in Jenkins if the test run via Tunnel
Title: Message Title noam doron assigned an issue to noam doron Jenkins / JENKINS-50927 [SRF] Failed to present report in Jenkins if the test run via Tunnel Change By: noam doron Assignee: Ofir Shaked noam doron Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50928) [SRF] After running a Jenkins job with create tunnel a CPU jumps to 100% at the end of a run
Title: Message Title noam doron created an issue Jenkins / JENKINS-50928 [SRF] After running a Jenkins job with create tunnel a CPU jumps to 100% at the end of a run Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 2018-04-22 13:01 Priority: Major Reporter: noam doron Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this
[JIRA] (JENKINS-50928) [SRF] After running a Jenkins job with create tunnel a CPU jumps to 100% at the end of a run
Title: Message Title noam doron assigned an issue to noam doron Jenkins / JENKINS-50928 [SRF] After running a Jenkins job with create tunnel a CPU jumps to 100% at the end of a run Change By: noam doron Assignee: Ofir Shaked noam doron Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50927) [SRF] Failed to present report in Jenkins if the test run via Tunnel
Title: Message Title noam doron created an issue Jenkins / JENKINS-50927 [SRF] Failed to present report in Jenkins if the test run via Tunnel Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 2018-04-22 13:00 Priority: Major Reporter: noam doron Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are
[JIRA] (JENKINS-49572) [SRF] [Tunneling] > settings are missing in create tunnel step
Title: Message Title noam doron resolved as Fixed Jenkins / JENKINS-49572 [SRF] [Tunneling] > settings are missing in create tunnel step Change By: noam doron Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50926) Unable to find files on analysis-core 3.0
Title: Message Title Chen Fliesher created an issue Jenkins / JENKINS-50926 Unable to find files on analysis-core 3.0 Issue Type: Bug Assignee: Ulli Hafner Components: analysis-core-plugin Created: 2018-04-22 11:33 Environment: Jenkins 2.116 on a Azure Kubernetes Cloud (using kubernetes-plugin 1.15.1) All Pods are over CoreOS 1688.5.3 (docker 17.07) 1 master with statless slaves as pods. Plugins: Parameterized-Remote-Trigger: 2.3.0-SNAPSHOT (private-01/07/2018 23:50-cfliesher) ace-editor: 1.1 analysis-core: 2.0-SNAPSHOT (private-6b615c34-jenkins) - From 3.0 branch ansicolor: 0.5.2 antisamy-markup-formatter: 1.5 apache-httpcomponents-client-4-api: 4.5.3-2.1 authentication-tokens: 1.3 blueocean: 1.5.0 blueocean-autofavorite: 1.2.2 blueocean-bitbucket-pipeline: 1.5.0 blueocean-commons: 1.5.0 blueocean-config: 1.5.0 blueocean-core-js: 1.5.0 blueocean-dashboard: 1.5.0 blueocean-display-url: 2.2.0 blueocean-events: 1.5.0 blueocean-git-pipeline: 1.5.0 blueocean-github-pipeline: 1.5.0 blueocean-i18n: 1.5.0 blueocean-jira: 1.5.0 blueocean-jwt: 1.5.0 blueocean-personalization: 1.5.0 blueocean-pipeline-api-impl: 1.5.0 blueocean-pipeline-editor: 1.5.0 blueocean-pipeline-scm-api: 1.5.0 blueocean-rest: 1.5.0 blueocean-rest-impl: 1.5.0 blueocean-web: 1.5.0 bouncycastle-api: 2.16.2 branch-api: 2.0.19 build-monitor-plugin: 1.12+build.201708172343 build-token-root: 1.4 cloudbees-bitbucket-branch-source: 2.2.10 cloudbees-folder: 6.4 command-launcher: 1.2 copyartifact: 1.39.1 credentials: 2.1.16 credentials-binding: 1.16 display-url-api: 2.2.0 docker-commons: 1.11 docker-workflow: 1.15.1 durable-task: 1.22 email-ext: 2.62 favorite: 2.3.1 ghprb: 1.40.0 git: 3.8.0 git-client: 2.7.1 git-server: 1.7 github: 1.29.0 github-api: 1.90 github-branch-source: 2.3.3 github-oauth: 0.29 github-pullrequest: 0.1.0-rc29 greenballs: 1.15 handlebars: 1.1.1 handy-uri-templates-2-api: 2.1.6-1.0 htmlpublisher: 1.16 jackson2-api: 2.8.11.1 javadoc: 1.4 jdk-tool: 1.1 jenkins-design-language: 1.5.0 jira: 2.5 jquery-detached: 1.2.1 jsch: 0.1.54.2 junit: 1.24 kubernetes: 1.5.2 kubernetes-credentials: 0.3.1 lockable-resources: 2.2 mailer: 1.21 matrix-auth: 2.2 matrix-project: 1.13 maven-plugin: 3.1.2 mercurial: 2.3 momentjs: 1.1.1 pipeline-build-step: 2.7 pipeline-github-lib: 1.0 pipeline-githubnotify-step: 1.0.4 pipeline-graph-analysis: 1.6 pipeline-input-step: 2.8 pipeline-milestone-step: 1.3.1 pipeline-model-api: 1.2.8 pipeline-model-declarative-agent: 1.1.1 pipeline-model-definition: 1.2.8 pipeline-model-extensions: 1.2.8 pipeline-rest-api: 2.10
[JIRA] (JENKINS-50125) Jenkins parameters missing in build when using jira trigger
Title: Message Title Wisen Tanasa started work on JENKINS-50125 Change By: Wisen Tanasa Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46836) JIRA Trigger Plugin fails job on null value attributes
Title: Message Title Wisen Tanasa commented on JENKINS-46836 Re: JIRA Trigger Plugin fails job on null value attributes Fixed under 0.6.1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46836) JIRA Trigger Plugin fails job on null value attributes
Title: Message Title Wisen Tanasa resolved as Fixed Jenkins / JENKINS-46836 JIRA Trigger Plugin fails job on null value attributes Change By: Wisen Tanasa Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46836) JIRA Trigger Plugin fails job on null value attributes
Title: Message Title SCM/JIRA link daemon commented on JENKINS-46836 Re: JIRA Trigger Plugin fails job on null value attributes Code changed in jenkins User: Wisen Tanasa Path: src/integrationTest/groovy/com/ceilfors/jenkins/plugins/jiratrigger/JiraTriggerIntegrationTest.groovy src/main/groovy/com/ceilfors/jenkins/plugins/jiratrigger/ParameterMappingAction.groovy http://jenkins-ci.org/commit/jira-trigger-plugin/9375c1b6141fcb6ff12873e7151dbe99e87a951a Log: JENKINS-46836 Convert parameterResolver null return value to empty string. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48347) Winp - v1.25 - Failed to locate JAR file by URL zip:
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48347 Re: Winp - v1.25 - Failed to locate JAR file by URL zip: Code changed in jenkins User: Oleg Nenashev Path: core/pom.xml http://jenkins-ci.org/commit/jenkins/534bb120f4d41942c1b8215d3f5fe7db5db5e3c3 Log: Merge pull request #3399 from oleg-nenashev/winp/1.26 JENKINS-48347 - Update WinP from 1.25 to 1.26 to pick the Weblogic classloader fix for WinP DLLs Compare: https://github.com/jenkinsci/jenkins/compare/398e032fa08b...534bb120f4d4 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48347) Winp - v1.25 - Failed to locate JAR file by URL zip:
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48347 Re: Winp - v1.25 - Failed to locate JAR file by URL zip: Code changed in jenkins User: Oleg Nenashev Path: core/pom.xml http://jenkins-ci.org/commit/jenkins/a5e9cbd731722d7594da77a6fddd10a800172c0a Log: JENKINS-48347 - Update WinP from 1.25 to 1.26 to pick the weblogic fix Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50925) jenkins returns internal server error (500) when sending a push hook from GitLab
Title: Message Title Oleg Nenashev assigned an issue to Owen Mehegan Jenkins / JENKINS-50925 jenkins returns internal server error (500) when sending a push hook from GitLab Change By: Oleg Nenashev Assignee: Owen Mehegan Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50925) jenkins returns internal server error (500) when sending a push hook from GitLab
Title: Message Title Oleg Nenashev moved an issue Jenkins / JENKINS-50925 jenkins returns internal server error (500) when sending a push hook from GitLab Change By: Oleg Nenashev Project: Infrastructure Jenkins Key: INFRA JENKINS - 1567 50925 Workflow: classic default workflow JNJira + In-Review Component/s: gitlab-plugin Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50846) Cannot start build runner due to Trend error even if no Trend option is selected
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50846 Re: Cannot start build runner due to Trend error even if no Trend option is selected Code changed in jenkins User: Yafim Kazak Path: src/main/java/com/hpe/application/automation/tools/pc/PcClient.java src/main/java/com/hpe/application/automation/tools/run/PcBuilder.java http://jenkins-ci.org/commit/hpe-application-automation-tools-plugin/ab96f3ea55d578c9efcb33cf1447b32dc54dd8dc Log: Merge pull request #79 from danieldanan/latest JENKINS-50846: Cannot start build runner due to Trend error even if n… Compare: https://github.com/jenkinsci/hpe-application-automation-tools-plugin/compare/f43a0895159f...ab96f3ea55d5 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50846) Cannot start build runner due to Trend error even if no Trend option is selected
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50846 Re: Cannot start build runner due to Trend error even if no Trend option is selected Code changed in jenkins User: danieldanan Path: src/main/java/com/hpe/application/automation/tools/pc/PcClient.java src/main/java/com/hpe/application/automation/tools/run/PcBuilder.java http://jenkins-ci.org/commit/hpe-application-automation-tools-plugin/3f14e11d44e423bf8dcb454e8ed4947409b0b77d Log: JENKINS-50846: Cannot start build runner due to Trend error even if no Trend option is selected Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
