[JIRA] (JENKINS-61471) A message body reader for Java class com.atlassian.confluence.api.model.content.Space, and Java type class com.atlassian.confluence.api.model.content.Space, and MIME media type
Title: Message Title sgao thaich updated an issue Jenkins / JENKINS-61471 A message body reader for Java class com.atlassian.confluence.api.model.content.Space, and Java type class com.atlassian.confluence.api.model.content.Space, and MIME media type text/html; charset=UTF-8 was not found Change By: sgao thaich Priority: Trivial Minor Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205152.1584106532000.8295.1584430260525%40Atlassian.JIRA.
[JIRA] (JENKINS-61471) A message body reader for Java class com.atlassian.confluence.api.model.content.Space, and Java type class com.atlassian.confluence.api.model.content.Space, and MIME media type
Title: Message Title
sgao thaich updated an issue
Jenkins / JENKINS-61471
A message body reader for Java class com.atlassian.confluence.api.model.content.Space, and Java type class com.atlassian.confluence.api.model.content.Space, and MIME media type text/html; charset=UTF-8 was not found
Change By:
sgao thaich
Publishing fails after upgrading from 2.0.3 to 2.0.5 with com.sun.jersey.api.client.ClientHandlerException. {code:java}agent {archiveArtifacts artifacts: file.txtpublishConfluence pageName: 'My page', spaceName: ' SpaceABC SpaceA ', attachArchivedArtifacts: true}{code} {code:java}com.sun.jersey.api.client.ClientHandlerException: A message body reader for Java class com.atlassian.confluence.api.model.content.Space, and Java type class com.atlassian.confluence.api.model.content.Space, and MIME media type text/html; charset=UTF-8 was not found at com.sun.jersey.api.client.ClientResponse.getEntity(ClientResponse.java:630) at com.sun.jersey.api.client.ClientResponse.getEntity(ClientResponse.java:586) at com.sun.jersey.api.client.WebResource.handle(WebResource.java:686) at com.sun.jersey.api.client.WebResource.get(WebResource.java:193) at com.atlassian.confluence.rest.client.AbstractRemoteService.getOption(AbstractRemoteService.java:181) at com.atlassian.confluence.rest.client.AbstractRemoteService.lambda$getFutureOption$1(AbstractRemoteService.java:77) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748){code} It seems to fail when fetching the space, the response status is < 300 so we try the plugin tries to get a deserialize the response body into Space entity but content is html which is probably an error. A {code:java}remoteSpaceService.find().withKeys(spaceKey).fetchOne().claim(){code}When i try the following curl i get a valid json response, using the same basic auth user used by the plugin:{code:java}curl -i -X GET to -H "Authorization: Basic *" https:// myconfluence.com/rest/api/space /SpaceABC with the same basic authentication user gives med a valid json response. ?spaceKey=SpaceA {code}
[JIRA] (JENKINS-61499) Unable to delete maven project when scheduler and node configuration is set
Title: Message Title Hareesha Gajula created an issue Jenkins / JENKINS-61499 Unable to delete maven project when scheduler and node configuration is set Issue Type: Bug Assignee: Unassigned Attachments: UnableToDeleteProject.png Components: maven-plugin Created: 2020-03-17 08:21 Priority: Major Reporter: Hareesha Gajula Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61500) workflow job (a) that calling another workflow job (b) - in Pipeline topology missing link from (a) to (b)
Title: Message Title Radi Berkovich created an issue Jenkins / JENKINS-61500 workflow job (a) that calling another workflow job (b) - in Pipeline topology missing link from (a) to (b) Issue Type: Bug Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2020-03-17 08:50 Priority: Minor Reporter: Radi Berkovich Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61384) warnings-ng plugin doesn't copy files from workspace if source directory is given
Title: Message Title Ulli Hafner resolved as Won't Fix Ok: I hope that your use case is some kind of exception. If someone else requires more root folders (during one recordIssues step call) we can reopen this issue again and think on how to implement that. Jenkins / JENKINS-61384 warnings-ng plugin doesn't copy files from workspace if source directory is given Change By: Ulli Hafner Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" gr
[JIRA] (JENKINS-60970) Improvement recognition of jobs in folder
Title: Message Title Radi Berkovich updated JENKINS-60970 Jenkins / JENKINS-60970 Improvement recognition of jobs in folder Change By: Radi Berkovich Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204433.1580893119000.8305.1584435960424%40Atlassian.JIRA.
[JIRA] (JENKINS-60971) Add post build action that allows to inject pull requests to Octane from different SCM tools (bitbucket, github)
Title: Message Title Radi Berkovich updated JENKINS-60971 Jenkins / JENKINS-60971 Add post build action that allows to inject pull requests to Octane from different SCM tools (bitbucket, github) Change By: Radi Berkovich Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204435.1580893941000.8306.1584435960437%40Atlassian.JIRA.
[JIRA] (JENKINS-60971) Add post build action that allows to inject pull requests to Octane from different SCM tools (bitbucket, github)
Title: Message Title Radi Berkovich updated JENKINS-60971 Jenkins / JENKINS-60971 Add post build action that allows to inject pull requests to Octane from different SCM tools (bitbucket, github) Change By: Radi Berkovich Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204435.1580893941000.8307.1584435960449%40Atlassian.JIRA.
[JIRA] (JENKINS-60970) Improvement recognition of jobs in folder
Title: Message Title Radi Berkovich updated JENKINS-60970 Jenkins / JENKINS-60970 Improvement recognition of jobs in folder Change By: Radi Berkovich Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204433.1580893119000.8304.1584435960379%40Atlassian.JIRA.
[JIRA] (JENKINS-60993) Workflow jobs are not sending build logs to Octane
Title: Message Title Radi Berkovich updated JENKINS-60993 Jenkins / JENKINS-60993 Workflow jobs are not sending build logs to Octane Change By: Radi Berkovich Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204461.158098303.8308.1584436020094%40Atlassian.JIRA.
[JIRA] (JENKINS-60993) Workflow jobs are not sending build logs to Octane
Title: Message Title Radi Berkovich updated JENKINS-60993 Jenkins / JENKINS-60993 Workflow jobs are not sending build logs to Octane Change By: Radi Berkovich Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204461.158098303.8309.1584436080080%40Atlassian.JIRA.
[JIRA] (JENKINS-61248) fix integration of ALM Octane - CloudBees Role-Based Access Control plugin
Title: Message Title Radi Berkovich updated JENKINS-61248 Jenkins / JENKINS-61248 fix integration of ALM Octane - CloudBees Role-Based Access Control plugin Change By: Radi Berkovich Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204815.1582786917000.8310.1584436140157%40Atlassian.JIRA.
[JIRA] (JENKINS-61248) fix integration of ALM Octane - CloudBees Role-Based Access Control plugin
Title: Message Title Radi Berkovich updated JENKINS-61248 Jenkins / JENKINS-61248 fix integration of ALM Octane - CloudBees Role-Based Access Control plugin Change By: Radi Berkovich Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204815.1582786917000.8311.1584436140189%40Atlassian.JIRA.
[JIRA] (JENKINS-61249) Reduce bootstrap plugin time by asyncronious initial loading of Octane configurations
Title: Message Title Radi Berkovich updated JENKINS-61249 Jenkins / JENKINS-61249 Reduce bootstrap plugin time by asyncronious initial loading of Octane configurations Change By: Radi Berkovich Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204816.1582787125000.8312.1584436200262%40Atlassian.JIRA.
[JIRA] (JENKINS-61249) Reduce bootstrap plugin time by asyncronious initial loading of Octane configurations
Title: Message Title Radi Berkovich updated JENKINS-61249 Jenkins / JENKINS-61249 Reduce bootstrap plugin time by asyncronious initial loading of Octane configurations Change By: Radi Berkovich Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204816.1582787125000.8313.1584436200311%40Atlassian.JIRA.
[JIRA] (JENKINS-61104) Allow to inject component with test result injection, not only for Maven projects
Title: Message Title Radi Berkovich updated JENKINS-61104 Jenkins / JENKINS-61104 Allow to inject component with test result injection, not only for Maven projects Change By: Radi Berkovich Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204616.1581843357000.8314.1584436200325%40Atlassian.JIRA.
[JIRA] (JENKINS-61104) Allow to inject component with test result injection, not only for Maven projects
Title: Message Title Radi Berkovich updated JENKINS-61104 Jenkins / JENKINS-61104 Allow to inject component with test result injection, not only for Maven projects Change By: Radi Berkovich Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204616.1581843357000.8315.1584436260086%40Atlassian.JIRA.
[JIRA] (JENKINS-61501) Checks fail while merging PR due to Findbugs
Title: Message Title Qualys Plugins created an issue Jenkins / JENKINS-61501 Checks fail while merging PR due to Findbugs Issue Type: Task Assignee: Qualys Plugins Components: qualys-cs-plugin Created: 2020-03-17 10:08 Priority: Blocker Reporter: Qualys Plugins The PR checks fail because of the Findbugs and I do not see a way to disable the findbugs checks - https://github.com/jenkinsci/qualys-cs-plugin/pull/1#partial-pull-merging When searched about it, maven version seems to be the culprit - http://maven.40175.n5.nabble.com/3-4-0-SNAPSHOT-failure-with-findbugs-Re-colorized-Maven-output-td5871591.html Not sure although, what is causing it, can someone please address this, as we are blocked from releasing the next version of the plugin. Add Comment
[JIRA] (JENKINS-59901) UFT Tests from ALM. Run on Planned Host.
Title: Message Title Anda Sorina Laakso commented on JENKINS-59901 Re: UFT Tests from ALM. Run on Planned Host. This has been fixed and will be included in the next release. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202650.1571836527000.8327.1584440160329%40Atlassian.JIRA.
[JIRA] (JENKINS-61172) ALM Plug in not working while running from Linux
Title: Message Title Anda Sorina Laakso commented on JENKINS-61172 Re: ALM Plug in not working while running from Linux Is the Jenkins master a Linux machine or the nodes running the tests are in Linux? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204647.1582036282000.8325.1584440160276%40Atlassian.JIRA.
[JIRA] (JENKINS-60071) [JenkinsPlugin][MC3.3][UFT14.03]The UFT cannot be launched
Title: Message Title Anda Sorina Laakso resolved as Fixed Jenkins / JENKINS-60071 [JenkinsPlugin][MC3.3][UFT14.03]The UFT cannot be launched Change By: Anda Sorina Laakso Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202905.1573021329000.8335.1584440220207%40Atlassian.JIRA.
[JIRA] (JENKINS-61501) Checks fail while merging PR due to Findbugs
Title: Message Title
Qualys Plugins updated an issue
Jenkins / JENKINS-61501
Checks fail while merging PR due to Findbugs
Change By:
Qualys Plugins
The PR checks fail because of the Findbugs and I do not see a way to disable the findbugs checks - [https://github.com/jenkinsci/qualys-cs-plugin/pull/1#partial-pull-merging ] Failed to execute goal org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs (findbugs) on project qualys-cs: Unable to parse configuration of mojo org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs for parameter pluginArtifacts: Cannot assign configuration entry 'pluginArtifacts' with value '${plugin.artifacts}' of type java.util.Collections.UnmodifiableRandomAccessList to property of type java.util.ArrayList -> [Help 1] [|https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fqualys-cs-plugin/detail/release%2F1.6.0.2/5/pipeline#step-37-log-118][2020-03-17T09:55:15.792Z] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs (findbugs) on project qualys-cs: Unable to parse configuration of mojo org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs for parameter pluginArtifacts: Cannot assign configuration entry 'pluginArtifacts' with value '${plugin.artifacts}' of type java.util.Collections.UnmodifiableRandomAccessList to property of type java.util.ArrayList When searched about it, maven version seems to be the culprit - [http://maven.40175.n5.nabble.com/3-4-0-SNAPSHOT-failure-with-findbugs-Re-colorized-Maven-output-td5871591.html]Not sure although, what is causing it, can someone please address this, as we are blocked from releasing the next version of the plugin.
Add Comment
[JIRA] (JENKINS-59090) Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing
Title: Message Title Anda Sorina Laakso commented on JENKINS-59090 Re: Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing What version of the plugin are you using? Did you try to udpate the plugin for the latest version? Do you have any timeout set on the job configuration page? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201510.1566845071000.8338.1584440460189%40Atlassian.JIRA.
[JIRA] (JENKINS-61501) Checks fail while merging PR due to Findbugs
Title: Message Title Qualys Plugins updated an issue Jenkins / JENKINS-61501 Checks fail while merging PR due to Findbugs Change By: Qualys Plugins Component/s: qualys-was-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205188.1584439716000.8343.1584440880136%40Atlassian.JIRA.
[JIRA] (JENKINS-61501) Checks fail while merging PR due to Findbugs
Title: Message Title
Qualys Plugins updated an issue
Jenkins / JENKINS-61501
Checks fail while merging PR due to Findbugs
Change By:
Qualys Plugins
The PR checks fail because of the Findbugs and I do not see a way to disable the findbugs checks - Failing for 2 projects - [https://github.com/jenkinsci/qualys- was-plugin/pull/3][https://github.com/jenkinsci/qualys- cs-plugin/pull/1#partial-pull-merging ] Failed to execute goal org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs (findbugs) on project qualys-cs: Unable to parse configuration of mojo org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs for parameter pluginArtifacts: Cannot assign configuration entry 'pluginArtifacts' with value '${plugin.artifacts}' of type java.util.Collections.UnmodifiableRandomAccessList to property of type java.util.ArrayList -> [Help 1] [ | https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fqualys-cs-plugin/detail/release%2F1.6.0.2/5/pipeline#step-37-log-118][2020-03-17T09:55:15.792Z] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs (findbugs) on project qualys-cs: Unable to parse configuration of mojo org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs for parameter pluginArtifacts: Cannot assign configuration entry 'pluginArtifacts' with value '${plugin.artifacts}' of type java.util.Collections.UnmodifiableRandomAccessList to property of type java.util.ArrayList When searched about it, maven version seems to be the culprit - [http://maven.40175.n5.nabble.com/3-4-0-SNAPSHOT-failure-with-findbugs-Re-colorized-Maven-output-td5871591.html] Not sure although, what is causing it, can someone please address this, as we are blocked from releasing the next version of the plugin.
Add Comment
[JIRA] (JENKINS-61216) NPE in git plugin building environment variables for node
Title: Message Title Rishabh Budhouliya commented on JENKINS-61216 Re: NPE in git plugin building environment variables for node "That seems impossible, since a null key in an environment variable would mean that the computer has an environment variable with an empty name." EnvironmentVariablesNodeProperty sets additional environment variables, could it be possible that the user might be setting an empty env variable for the node? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204770.1582622477000.8350.1584449520154%40Atlassian.JIRA.
[JIRA] (JENKINS-61216) NPE in git plugin building environment variables for node
Title: Message Title Mark Waite commented on JENKINS-61216 Re: NPE in git plugin building environment variables for node Could be, though I think you're describing a null value, rather than a null key. At least, I think I can envision ways that I might assign a null value to a non-null key. I don't know how I would create a null key. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204770.1582622477000.8360.1584450660130%40Atlassian.JIRA.
[JIRA] (JENKINS-59090) Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing
Title: Message Title Sandeep Yadav commented on JENKINS-59090 Re: Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing We tried taking the timeout and that didnt work. Currently we have the timeout set to 45000. We are on 5.5 and upgrading to 5.6 and 5.7 gave lots of other errors and known issues hence we had to roll back to 5.5 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201510.1566845071000.8363.1584450720212%40Atlassian.JIRA.
[JIRA] (JENKINS-61238) Missing start function in configuration of a slave which is a virtual machine
Title: Message Title
Reiner Wirtz commented on JENKINS-61238
Re: Missing start function in configuration of a slave which is a virtual machine
Possible it depends on a duplicate name ("launcher") in the xml-structure. After saving the configuration the inner block with name "launcher" is missing in the configuration file "config.xml" for the node. If the inner block in the node confguration is missing, there are problems in connecting the slave. This is true for both slaves, linux (connected by ssh-launcher) or windows (slave as windows service).
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204793.1582726396000.8368.1584450900122%40Atlassian.JIRA.
[JIRA] (JENKINS-59090) Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing
Title: Message Title Anda Sorina Laakso commented on JENKINS-59090 Re: Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing I meant to remove the timeout completely. And second thing is that current version is 6.1.3. So you should update to that one, because there have been quite a lot of changes since 5.7. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201510.1566845071000.8370.1584451440411%40Atlassian.JIRA.
[JIRA] (JENKINS-59090) Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing
Title: Message Title Anda Sorina Laakso edited a comment on JENKINS-59090 Re: Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing I meant to Please remove the timeout completely. And second thing is that current version is 6.1.3. So you should update to that one, because there have been quite a lot of changes since 5.7. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201510.1566845071000.8375.1584451500178%40Atlassian.JIRA.
[JIRA] (JENKINS-61216) NPE in git plugin building environment variables for node
Title: Message Title Mark Waite edited a comment on JENKINS-61216 Re: NPE in git plugin building environment variables for node Could be, though I think you're describing a null value, rather than a null key. At least, I think I can envision ways that I might assign a null value to a non-null key. I don't know how I would create a null key. The `buildEnvironment` method in Computer allocates a [new EnvVars|https://github.com/jenkinsci/jenkins/blob/cc3d24c67b62cf6baa37e4e350889ee86c5ccce8/core/src/main/java/hudson/model/Computer.java#L1201], so the EnvVars is not null. It passes that env to [each nodeProperty|https://github.com/jenkinsci/jenkins/blob/cc3d24c67b62cf6baa37e4e350889ee86c5ccce8/core/src/main/java/hudson/model/Computer.java#L1211] , which then [calls env.putAll|https://github.com/jenkinsci/jenkins/blob/cc3d24c67b62cf6baa37e4e350889ee86c5ccce8/core/src/main/java/hudson/slaves/EnvironmentVariablesNodeProperty.java#L86] to add the agent specific properties to the env that was passed.The call to `env.putAll()` reports the null pointer exception inside the putAll. Since the NPE is not reported at buildEnvVars, `env` must not be null. The putAll NPE seems to indicate that either the [EnvironmentVariablesNodeProperty.envVars|https://github.com/jenkinsci/jenkins/blob/cc3d24c67b62cf6baa37e4e350889ee86c5ccce8/core/src/main/java/hudson/slaves/EnvironmentVariablesNodeProperty.java#L55] is null or it contains a null key. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-61216) NPE in git plugin building environment variables for node
Title: Message Title Mark Waite edited a comment on JENKINS-61216 Re: NPE in git plugin building environment variables for node Could be, though I think you're describing a null value, rather than a null key. At least, I think I can envision ways that I might assign a null value to a non-null key. I don't know how I would create a null key.The `buildEnvironment` method in Computer allocates a [new EnvVars|https://github.com/jenkinsci/jenkins/blob/cc3d24c67b62cf6baa37e4e350889ee86c5ccce8/core/src/main/java/hudson/model/Computer.java#L1201], so the EnvVars is not null. It passes that env to [each nodeProperty|https://github.com/jenkinsci/jenkins/blob/cc3d24c67b62cf6baa37e4e350889ee86c5ccce8/core/src/main/java/hudson/model/Computer.java#L1211] , which then [calls env.putAll|https://github.com/jenkinsci/jenkins/blob/cc3d24c67b62cf6baa37e4e350889ee86c5ccce8/core/src/main/java/hudson/slaves/EnvironmentVariablesNodeProperty.java#L86] to add the agent specific properties to the env that was passed.The call to `env.putAll()` reports the null pointer exception inside the putAll. Since the NPE is not reported at buildEnvVars, `env` must not be null. The putAll NPE seems to indicate that either the [EnvironmentVariablesNodeProperty.envVars|https://github.com/jenkinsci/jenkins/blob/cc3d24c67b62cf6baa37e4e350889ee86c5ccce8/core/src/main/java/hudson/slaves/EnvironmentVariablesNodeProperty.java#L55] is null or it contains a null key. I've confirmed that I can define an environment variable for an agent and an environment variable for the master which has no name and no value. When I do that, the system configure and job configure operations both save successfully. I still don't understand how to duplicate this report. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61387) SlaveComputer not cleaned up after the channel is closed
Title: Message Title Jesse Glick commented on JENKINS-61387 Re: SlaveComputer not cleaned up after the channel is closed Hmm, this is supposed to have been addressed by a patch towards JENKINS-49707. See test case. Can you check with fine logging on org.csanchez.jenkins.plugins.kubernetes.pod.retention.Reaper? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205040.1583744035000.8391.1584453480186%40Atlassian.JIRA.
[JIRA] (JENKINS-61383) Current new messages detection mechanism is not working for simple line insertion in case of many similar adjacent warning
Title: Message Title Ulli Hafner commented on JENKINS-61383 Re: Current new messages detection mechanism is not working for simple line insertion in case of many similar adjacent warning Just a few comments: 1) The source_file_name, error id, error message, and the source line contents (NOT the line number). Isn't that almost the same algorithm I am using? Just without using a multi-line context - just the line with the warning. I think we can make that property configurable. Another thing to consider: currently there is no API to access Git (or any other version control system) to get diffs. So if you plan to extend that part it should be a generic approach that still works if nobody is using Git. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205036.1583663669000.8393.1584453600157%40Atlassian.JIRA.
[JIRA] (JENKINS-59090) Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing
Title: Message Title Sandeep Yadav commented on JENKINS-59090 Re: Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing I see the current version as 6.0. Please provide a link to 6.1.3 as per your comment https://github.com/jenkinsci/hpe-application-automation-tools-plugin/blob/latest/doc/README.md Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201510.1566845071000.8395.1584454740179%40Atlassian.JIRA.
[JIRA] (JENKINS-59090) Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing
Title: Message Title Anda Sorina Laakso commented on JENKINS-59090 Re: Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing So current version is 6.1, available here: http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/hp-application-automation-tools-plugin/6.1/hp-application-automation-tools-plugin-6.1.hpi 6.1.3 is still beta version. Or you can try to go to Jenkins-> Manage plugins and when looking for our plugin you will find the latest version all the time. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201510.1566845071000.8400.1584455220361%40Atlassian.JIRA.
[JIRA] (JENKINS-52732) Test epic
Title: Message Title UDAY SETTI updated JENKINS-52732 Jenkins / JENKINS-52732 Test epic Change By: UDAY SETTI Resolution: Won't Do Status: Closed In Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192624.1532507107000.8408.1584457500377%40Atlassian.JIRA.
[JIRA] (JENKINS-61500) workflow job (a) that calling another workflow job (b) - in Pipeline topology missing link from (a) to (b)
Title: Message Title UDAY SETTI started work on JENKINS-61500 Change By: UDAY SETTI Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205187.1584435036000.8410.1584457500415%40Atlassian.JIRA.
[JIRA] (JENKINS-59117) Add support for WorkflowPipelineView to JobDSL
Title: Message Title Jakub Siberski commented on JENKINS-59117 Re: Add support for WorkflowPipelineView to JobDSL I've just spend a day trying to figure out my jobdsl config for WorkflowPipelineView is not working, without realising `deliveryPipelineView` is not the way. Daniel Spilker since other two PRs you have linked are merged is there anything else blocking this issue? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201546.1566985699000.8413.1584459060270%40Atlassian.JIRA.
[JIRA] (JENKINS-60972) Rename the root breadcrumb
Title: Message Title Félix Queiruga Balado commented on JENKINS-60972 Re: Rename the root breadcrumb Something like that indeed. My OG idea was to to have on the Java side 2 models: Breadcrumbs: has the logic to build the whole breadcrumb trail (maybe a getBreadcrumbItems method) and hooked into the jelly view. It would also allow prepending and appending breadcrumbs, and renaming the first one (??) BreadcrumbItem: has logic to determine if it's the last one, get the parent, check if it has a contextual menu, etc. Then on the jelly side you would get the breadcrumb model and iterate on the breadcrumb items Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204437.1580894909000.8424.1584463680220%40Atlassian.JIRA.
[JIRA] (JENKINS-54502) Jenkins crashed when a running build was aborted.
Title: Message Title Vipul Madaan updated JENKINS-54502 Jenkins / JENKINS-54502 Jenkins crashed when a running build was aborted. Change By: Vipul Madaan Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195272.1541539669000.8461.1584465842487%40Atlassian.JIRA.
[JIRA] (JENKINS-54502) Jenkins crashed when a running build was aborted.
Title: Message Title Vipul Madaan updated JENKINS-54502 Jenkins / JENKINS-54502 Jenkins crashed when a running build was aborted. Change By: Vipul Madaan Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195272.1541539669000.8463.1584465842627%40Atlassian.JIRA.
[JIRA] (JENKINS-54502) Jenkins crashed when a running build was aborted.
Title: Message Title Vipul Madaan started work on JENKINS-54502 Change By: Vipul Madaan Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195272.1541539669000.8433.1584465780845%40Atlassian.JIRA.
[JIRA] (JENKINS-13916) Multiline text parameter displays as single line
Title: Message Title Jarrett B commented on JENKINS-13916 Re: Multiline text parameter displays as single line Hello, Issue still exists in 2.204.5. Is this still being worked on? Thanks Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.144384.1337950164000.8490.1584474000494%40Atlassian.JIRA.
[JIRA] (JENKINS-27129) More consistent use of PauseAction
Title: Message Title Jesse Glick commented on JENKINS-27129 Re: More consistent use of PauseAction Also makes sense in ExecutorStep while the task is in the queue. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.160922.1424881499000.8530.1584475620170%40Atlassian.JIRA.
[JIRA] (JENKINS-60779) Pipeline Build Step: Remove Message converting string Parameter to Extensible Choice Parameter
Title: Message Title Devin Nusbaum updated JENKINS-60779 A fix for this issue was just released in Pipeline: Build Step Plugin version 2.12. Thanks Paul Thevenot for testing the fix! Jenkins / JENKINS-60779 Pipeline Build Step: Remove Message converting string Parameter to Extensible Choice Parameter Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: pipeline-build-step 2.12 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-58697) Jenkins crashed after restarting post downloading and installing plugins
Title: Message Title Anirban Pal started work on JENKINS-58697 Change By: Anirban Pal Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200986.1564363857000.8541.1584480360257%40Atlassian.JIRA.
[JIRA] (JENKINS-58697) Jenkins crashed after restarting post downloading and installing plugins
Title: Message Title Anirban Pal stopped work on JENKINS-58697 Change By: Anirban Pal Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200986.1564363857000.8545.1584480420264%40Atlassian.JIRA.
[JIRA] (JENKINS-40429) Copy artifacts from multi-branch pipeline project with project name as a build parameter fails with "Unable to find project for artifact copy"
Title: Message Title Marc Wäckerlin updated an issue Jenkins / JENKINS-40429 Copy artifacts from multi-branch pipeline project with project name as a build parameter fails with "Unable to find project for artifact copy" Change By: Marc Wäckerlin Priority: Minor Blocker Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177095.1481689512000.8582.1584483961154%40Atlassian.JIRA.
[JIRA] (JENKINS-40429) Copy artifacts from multi-branch pipeline project with project name as a build parameter fails with "Unable to find project for artifact copy"
Title: Message Title
Marc Wäckerlin commented on JENKINS-40429
Re: Copy artifacts from multi-branch pipeline project with project name as a build parameter fails with "Unable to find project for artifact copy"
First of all, it seems, that I am running into the same problem. But for me, it looks strange that this error has been reported such a long time ago (and why is it not fixed in these years?), but I am sure that it used to work short time ago. I cannot exactly say, how long it used to work for me, but I had successful builds. I ran into it now that I am moving my jenkins to a new server and re-running all builds. I am wondering why the priority should be minor, it's a blocker, the plugin is no more usable. My situation: Global Jenkins environment variable:
name: MINGW_ARCH
value: x86_64-w64-mingw32 i686-w64-mingw32
ProjectA:
matrix build:
name: mingw
variable: MINGW_ARCH
Artifacts: */usr and .zip
ProjectB (built after ProjectA):
matrix build:
name: mingw
variable: MINGW_ARCH
Copy Artifacts:
project name: ProjectA/mingw=$mingw
Artifacts: */usr and .zip
This results in: ERROR: Unable to find project for artifact copy: ProjectA/mingw=x86_64-w64-mingw32 Then, if I replace the project name to ProjectA/mingw=x86_64-w64-mingw32, that means hard coded, no variable, then it works. As you see from the error log, the variable substitution is 100% correct! But still there is somehow a failure with regard to the variable. The projects configurations (ProjectA is mrw-cxx.win and ProjectB is libxml-cxx.win): ProjectA:false 2 https://mrw.dev/libraries/mrw-cxx */master false5 10 true false true true @monthly H/5 * * * * false false mingw MINGW_ARCHS MINGW_ARCHS default docker pull mwaeckerlin/mingw docker run --rm -v $(pwd):/workdir -u $(id -u) -e MINGW=$mingw -e BUILD_NUMBER=$BUILD_NUMBER mwaeckerlin/mingw /build.sh -z FILE=mrw-c++-*_${mingw%-w64-mingw32}.zip TARGET=~/repository/windows/${mingw%-w64-mingw32}/${JOB_NAME%.win/*} test -d ${TARGET} || mkdir -p ${TARGET} cp ${FILE} ${TARGET}/ usr/**, *.zip false false false true true false falsefalse ProjectB:false 2 https://mrw.dev/libra
[JIRA] (JENKINS-61497) Searching for "Credentials" in plugin list gives list of plugins with insecure storage
Title: Message Title Daniel Beck assigned an issue to Daniel Beck Jenkins / JENKINS-61497 Searching for "Credentials" in plugin list gives list of plugins with insecure storage Change By: Daniel Beck Assignee: Daniel Beck Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205184.1584379956000.8628.1584485820245%40Atlassian.JIRA.
[JIRA] (JENKINS-40429) Copy artifacts from multi-branch pipeline project with project name as a build parameter fails with "Unable to find project for artifact copy"
Title: Message Title
Marc Wäckerlin commented on JENKINS-40429
Re: Copy artifacts from multi-branch pipeline project with project name as a build parameter fails with "Unable to find project for artifact copy"
My personal Workaround: I removed the artifact copy plugin and replaced the copy artifact build step by a freeform shell script as follows, which does the same as this plugin, just set the name of the source project in FROM: FROM=mrw-cxx.win STABLE=$(sed -n 's/^lastSuccessfulBuild //p' ~/jobs/${FROM}/builds/permalinks) SOURCE=~/jobs/${FROM}/configurations/axis-mingw/${mingw}/builds/${STABLE}/archive/usr cp -a ${SOURCE} .
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177095.1481689512000.8630.1584486420426%40Atlassian.JIRA.
[JIRA] (JENKINS-40429) Copy artifacts from multi-branch pipeline project with project name as a build parameter fails with "Unable to find project for artifact copy"
Title: Message Title
Marc Wäckerlin edited a comment on JENKINS-40429
Re: Copy artifacts from multi-branch pipeline project with project name as a build parameter fails with "Unable to find project for artifact copy"
First of all, it seems, that I am running into the same problem. But for me, it looks strange that this error has been reported such a long time ago (and why is it not fixed in these years?), but I am sure that it used to work short time ago. I cannot exactly say, how long it used to work for me, but I had successful builds. I ran into it now that I am moving my jenkins to a new server and re-running all builds. I am wondering why the priority should be minor, it's a blocker, the plugin is no more usable.My situation: Jenkins ver. 2.225Tested Copy Artifact 1.43.1 and 1.43 Global Jenkins environment variable: * name: {{MINGW_ARCH}} * value: {{x86_64-w64-mingw32 i686-w64-mingw32}}ProjectA: * matrix build: ** name: {{mingw}} ** variable: {{MINGW_ARCH}} * Artifacts: {{**/usr * }} * and {{ }} * {{ .zip}}ProjectB (built after ProjectA): * matrix build: ** name: {{mingw}} ** variable: {{MINGW_ARCH}} * Copy Artifacts: ** project name: {{ProjectA/mingw=$mingw}} * Artifacts: {{**/usr * }} * and {{ }} * {{ .zip}}This results in:{{ERROR: Unable to find project for artifact copy: ProjectA/mingw=x86_64-w64-mingw32}}Then, if I replace the project name to {{ProjectA/mingw=x86_64-w64-mingw32}}, that means hard coded, no variable, then it works.As you see from the error log, the variable substitution is 100% correct! But still there is somehow a failure with regard to the variable.The projects configurations ({{ProjectA}} is {{mrw-cxx.win}} and {{ProjectB}} is {{libxml-cxx.win}}):ProjectA: false2[ https://mrw.dev/libraries/mrw-cxx ] */master false5 10 true false true true @monthly H/5 * * * * false false mingw MINGW_ARCHS MINGW_ARCHS default docker pull mwaeckerlin/mingwdocker run --rm -v $(pwd):/workdir -u $(id -u) -e MINGW=$mingw -e BUILD_NUMBER=$BUILD_NUMBER mwaeckerlin/mingw /build.sh -zFILE=mrw-c++-*_${mingw%-w64-mingw32}.zipTARGET=~/repository/windows/${mingw%-w64-mingw32}/${JOB_NAME%.win/*}test -d ${TARGET} || mkdir -p ${TARGET}cp ${FILE} ${TARGET}/ usr/**, *.zip false false false true true false falsefalse ProjectB: false2[ https://mrw.dev/libraries/libxml-cxx ] */master false 5 10 true false true truemrw-cxx.win SUCCESS 0 BLUE true@monthly H/5 * * * * false false mingw MINGW_ARCHS MINGW_ARCHS default mrw-cxx.win/mingw=$mingw false docker pull mwaeckerlin/mingwdocker run --rm -v $(pwd):/workdir -u $(id -u) -e MINGW=$mingw -e BUILD_NUMBER=$BUILD_NUMBER mwaeckerlin/mingw /build.sh -zFILE=$ \ {JOB_NAME%.win/*}-*_${mingw%-w64-mingw32}.zipTARGET=~/repository/windows/${mingw%-w64-mingw32}/${JOB_NAME%.win/*}test -d ${TARGET} || mkdir -p ${TARGET}cp ${FILE} ${TARGET}/ usr/**, *.zip false false false true true false falsefalse
[JIRA] (JENKINS-40177) Use BitBucket Server project icon for jenkins folder icon
Title: Message Title Tiernan Messmer closed an issue as Fixed Jenkins / JENKINS-40177 Use BitBucket Server project icon for jenkins folder icon Change By: Tiernan Messmer Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176824.1480638135000.8672.1584490080538%40Atlassian.JIRA.
[JIRA] (JENKINS-27082) Sparse checkouts and submodules: Error on checkout, submodule missing
Title: Message Title Mark Waite commented on JENKINS-27082 Re: Sparse checkouts and submodules: Error on checkout, submodule missing ASHOK MOHANTY I can't tell from your message if you're using a submodule with the sparse checkout or not. If you're not using a submodule with a sparse checkout, then this issue does not apply to you. You may want to check the version of command line git on the system that has the issue. If you're using Red Hat Linux 6, CentOS 6, Oracle Linux 6, Scientific Linux 6, Red Hat Linux 7, CentOS 7, Oracle Linux 7, or Scientific Linux 7, you may have a version of command line git that is too old to support sparse checkout. I believe reliable sparse checkout support requires at least command line git 1.9. If your command line git version is not too old and you are not using a submodule, then you should open a new issue. This issue is specifically related to sparse checkout interaction with submodules. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.160872.1424699584000.8678.1584507000274%40Atlassian.JIRA.
