[JIRA] (JENKINS-27927) Some interface idioms do not work in Groovy CPS
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-27927 Some interface idioms do not work in Groovy CPS Change By: Andrew Bayer Labels: complex-cps-code groovy triaged-2018-11 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Raphael Greger commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 I have this issue on new updated Jenkins (2.138.3). I can't create or open a Jenkins job with Maven type. It tries to load the config page and the loading symbol do not stop moving. If I remove the mentioned "violations" plugin, it works again. But I can't just remove the plugin. It will be needed for the code analysis I guess. Are there any news? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54651) Refusing to marshal net.sf.json.JSONObject
Title: Message Title sushobhit dua commented on JENKINS-54651 Re: Refusing to marshal net.sf.json.JSONObject Thanks Oleg Nenashev for your reply. It works with below command mvn hpi:run -Dhudson.remoting.ClassFilter=net.sf.json.JSONObject,org.apache.commons.collections.map.ListOrderedMap Is this correct way to do ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-48283) InterruptedException processing the outputs of Maven builds (processing the logs generated by the pipeline maven spy)
Title: Message Title Cyrille Le Clerc commented on JENKINS-48283 Re: InterruptedException processing the outputs of Maven builds (processing the logs generated by the pipeline maven spy) 3.5.15 adds messages to help understand the problem: In case of InterruptedException, a message in the logs with the duration since the beginning of the processing is outputted, we want to verify if we have reached the standard timeout of the pipeline steps: [withMaven] Processing of Maven build outputs interrupted in " + mavenPublisher.toString() + " after " + TimeUnit.MILLISECONDS.convert(System.nanoTime() - nanosBefore, TimeUnit.NANOSECONDS) + "ms. When INFO level is enabled on org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor, a summary of the duration of each publisher is added to the build logs. Sample: [withMaven] Publishers: Generated Artifacts Publisher: 36 ms, Junit Publisher: 9 ms, Dependencies Fingerprint Publisher: 6 ms, Pipeline Graph Publisher: 1 ms, Open Task Scanner Publisher: 25 ms Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-52152) xunit cannot read junit time attributes with more than three decimals or using exponential notation
Title: Message Title
Christophe Muller edited a comment on JENKINS-52152
Re: xunit cannot read junit time attributes with more than three decimals or using exponential notation
I understand that it is cleaner to validate the XML files but it brings a lot of issues when using several test frameworks. {{ We had to upgrade nose so that it now puts *{{skipped}}* instead of *{{skip}}* (which was fixed in nose2) and this was OK because it looked like an issue on nose part (when they say it "follows" junit standard). But here for catch2 it is not an issue on their part, they have better precision and it's good. What we did as a workaround is to patch the xsd file to allow for better precision of time attributes and it worked: }} {{}} * {code:java} --- a/junit-10.xsd 2018-11-15 18:25:44.849045904 +0100 * * +++ b/junit-10.xsd 2018-11-15 18:27:26.705774044 +0100 * * @@ -25,7 +25,7 @@ * * * * * * * * - \ {0,3},)*[0-9] \ {3}|[0-9] \ {0,3})*(\.[0-9] \ {0,3})?"/> * * + \ {0,3},)*[0-9] \ {3}|[0-9] \ {0,3})*(\.[0-9] \ {0,9})?"/> * * * * * {code} It would be nice that such feature be considered in the xunit plugin IMHO.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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-52152) xunit cannot read junit time attributes with more than three decimals or using exponential notation
Title: Message Title
Christophe Muller edited a comment on JENKINS-52152
Re: xunit cannot read junit time attributes with more than three decimals or using exponential notation
I understand that it is cleaner to validate the XML files but it brings a lot of issues when using several test frameworks.{{We had to upgrade nose so that it now puts * {{ skipped * }} * instead of *{{skip}}* (which was fixed in nose2) and this was OK because it looked like an issue on nose part (when they say it "follows" junit standard). But here for catch2 it is not an issue on their part, they have better precision and it's good. What we did as a workaround is to patch the xsd file to allow for better precision of time attributes and it worked:}} \ {{}}{code:java}--- a/junit-10.xsd 2018-11-15 18:25:44.849045904 +0100+++ b/junit-10.xsd 2018-11-15 18:27:26.705774044 +0100@@ -25,7 +25,7 @@ - + {code}It would be nice that such feature be considered in the xunit plugin IMHO.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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-52152) xunit cannot read junit time attributes with more than three decimals or using exponential notation
Title: Message Title
Christophe Muller edited a comment on JENKINS-52152
Re: xunit cannot read junit time attributes with more than three decimals or using exponential notation
I understand that it is cleaner to validate the XML files but it brings a lot of issues when using several test frameworks.{{We had to upgrade nose so that it now puts *skipped*}} instead of *{{skip}}* (which was fixed in nose2) and this was OK because it looked like an issue on nose part (when they say it "follows" junit standard). But here for catch2 it is not an issue on their part, they have better precision and it's good. What we did as a workaround is to patch the xsd file to allow for better precision of time attributes and it worked: }} \{{}} {code:java}--- a/junit-10.xsd 2018-11-15 18:25:44.849045904 +0100+++ b/junit-10.xsd 2018-11-15 18:27:26.705774044 +0100@@ -25,7 +25,7 @@ - + {code}It would be nice that such feature be considered in the xunit plugin IMHO.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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-52152) xunit cannot read junit time attributes with more than three decimals or using exponential notation
Title: Message Title
Christophe Muller commented on JENKINS-52152
Re: xunit cannot read junit time attributes with more than three decimals or using exponential notation
I understand that it is cleaner to validate the XML files but it brings a lot of issues when using several test frameworks. We had to upgrade nose so that it now puts skipped instead of skip (which was fixed in nose2) and this was OK because it looked like an issue on nose part (when they say it "follows" junit standard). But here for catch2 it is not an issue on their part, they have better precision and it's good. What we did as a workaround is to patch the xsd file to allow for better precision of time attributes and it worked:
a/junit-10.xsd 2018-11-15 18:25:44.849045904 +0100* +++ b/junit-10.xsd 2018-11-15 18:27:26.705774044 +0100 @@ -25,7 +25,7 @@
[0-9]{0,3},)[0-9]{3}|[0-9]{0,3})(\.[0-9]{0,3})?"/>* + [0-9]{0,3},)[0-9]{3}|[0-9]{0,3})(\.[0-9]{0,9})?"/>
It would be nice that such feature be considered in the xunit plugin IMHO.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You
[JIRA] (JENKINS-51277) Possible bug around labels when using google-compute-engine-plugin
Title: Message Title Florian Ramillien commented on JENKINS-51277 Re: Possible bug around labels when using google-compute-engine-plugin More informations about this bugs. On a gcloud configuration with many labels, and some projects using only some of this labels. Node is created with a subset of labels from the job triggering this node creation (and no labels if we are creating the node manually). It's an expected behavior ? We think about node reuse to skip some provisionning steps, but if nodes are created with only a subset of their labels, this break our node reuse workflow. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-45129) Unable to scan branches in multibranch plugin when user has two-step verification enabled
Title: Message Title Chris Hemp commented on JENKINS-45129 Re: Unable to scan branches in multibranch plugin when user has two-step verification enabled I tested this out this morning on a local jenkins 2.151 (via docker) with using bitbucket-branch-source-plugin version 2.2.14. Using the Bitbucket `username` with an App Password worked successfully with my SAML/SSO configured user. This is great! Thanks again Nenad Miksa TLDR: User without SAML/SSO use: email-address / password User with SAML/SSO use: bitbucket-user-name / app-password Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54667) Getting Error while accessing Performance Report
Title: Message Title Artem Fedorov commented on JENKINS-54667 Re: Getting Error while accessing Performance Report ok. I'll try to investigate it on the next week Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-51404) processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
Title: Message Title Cyrille Le Clerc commented on JENKINS-51404 Re: processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method" Ulli Hafner thanks, if you could by any chance cut a version of the "old findbugs plugin", it would help the transition to the new world. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54394) Publish Over SSH plugin jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection. Message: [Failed to change to remote directory [D:]]
Title: Message Title Alex Earl commented on JENKINS-54394 Re: Publish Over SSH plugin jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection. Message: [Failed to change to remote directory [D:]] Error No, I tried some tests and it seems like the jsch library won't work with openssh for Windows for some reason. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54668) Unable to provide NodeJS path to Jenkins plugin
Title: Message Title Monali Chaudhary updated an issue Jenkins / JENKINS-54668 Unable to provide NodeJS path to Jenkins plugin Change By: Monali Chaudhary Priority: Minor Blocker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-51985) Create official jenkins/jenkins Docker images for Java 10 and 11 versions
Title: Message Title Baptiste Mathus commented on JENKINS-51985 Re: Create official jenkins/jenkins Docker images for Java 10 and 11 versions First pre-stab https://github.com/jenkinsci/docker/pull/760 in review. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54667) Getting Error while accessing Performance Report
Title: Message Title Satish Ramamuni updated an issue Jenkins / JENKINS-54667 Getting Error while accessing Performance Report Change By: Satish Ramamuni Attachment: image-2018-11-16-16-44-32-205.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54667) Getting Error while accessing Performance Report
Title: Message Title Satish Ramamuni commented on JENKINS-54667 Re: Getting Error while accessing Performance Report Hi After making changes also, still getting error Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54206) Merged PRs not being removed from multibranch
Title: Message Title Stephen Connolly commented on JENKINS-54206 Re: Merged PRs not being removed from multibranch Does the other one have an orphaned strategy configured? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-52397) Org Scan blows up when repository has no tags
Title: Message Title Stephen Connolly commented on JENKINS-52397 Re: Org Scan blows up when repository has no tags culprit looks to be https://github.com/kohsuke/github-api/commit/a17ce04552ddd3f6bd8210c740184e6c7ad13ae4 I have asked rsandell to see if he can drive https://github.com/jenkinsci/github-branch-source-plugin/pull/191 over the finish line Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54671) Script not found results in success in durable-task-plugin
Title: Message Title
peter anderson created an issue
Jenkins / JENKINS-54671
Script not found results in success in durable-task-plugin
Issue Type:
Bug
Assignee:
Unassigned
Components:
durable-task-plugin
Created:
2018-11-16 11:07
Environment:
CloudBees Jenkins Enterprise 2.121.1.2-rolling Durable Task Plugin: 1.22
Priority:
Major
Reporter:
peter anderson
When running the powershell task, if the path you pass doesn't exist, the step does not cause the build to fail: pipeline: node("WINDOWS_MACHINE") { powershell("a_file_that_doesnt_exist") } output: Running in Durability level: MAX_SURVIVABILITY [Pipeline] node Running on in D:\J\workspace\TEST_POWERSHELL_STEP [Pipeline] { [Pipeline] powershell [TEST_POWERSHELL_STEP] Running PowerShell script powershell.exe : a_file_that_doesnt_exist : The term 'a_file_that_doesnt_exist' is not recognized as the name of a cmdlet, function, At D:\J\workspace\TEST_POWERSHELL_STEP@tmp\durable-feef7c1b\powershellWrapper.ps1:5 char:3 + & powershell -NoProfile -NonInteractive -ExecutionPolicy Bypass -Fi ... + ~~~ + CategoryInfo : NotSpecified: (a_file_that_doe...let, function, :String) [], RemoteException + FullyQualifiedErrorId : NativeCommandError script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At D:\J\workspace\TEST_POWERSHELL_STEP@tmp\durable-feef7c1b\powershellScript.ps1:1 char:1 + a_file_that_doesnt_exist + + CategoryInfo : ObjectNotFound: (a_file_that_doesnt_exist:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Finished: SUCCESS — I would expect that
[JIRA] (JENKINS-54667) Getting Error while accessing Performance Report
Title: Message Title Artem Fedorov commented on JENKINS-54667 Re: Getting Error while accessing Performance Report https://prnt.sc/lj3ir0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54667) Getting Error while accessing Performance Report
Title: Message Title Satish Ramamuni commented on JENKINS-54667 Re: Getting Error while accessing Performance Report Hi I am not getting the configure option after Performance trend Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54667) Getting Error while accessing Performance Report
Title: Message Title Satish Ramamuni updated an issue Jenkins / JENKINS-54667 Getting Error while accessing Performance Report Change By: Satish Ramamuni Attachment: image-2018-11-16-16-31-55-154.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54670) Continous builds upon bitbuckt pull request
Title: Message Title
Luca Moscato commented on JENKINS-54670
Re: Continous builds upon bitbuckt pull request
Some logs from Jenkins console, the same behavior with latest version of bitbucketpullrequestbuilder Nov 16, 2018 10:07:01 AM WARNING bitbucketpullrequestbuilder.bitbucketpullrequestbuilder.bitbucket.ApiClient getAllValues invalid response. org.codehaus.jackson.JsonParseException: Unexpected character ('T' (code 84)): expected a valid value (number, String, array, object, 'true', 'false' or 'null') at [Source: java.io.StringReader@6faf0530; line: 1, column: 2] at org.codehaus.jackson.JsonParser._constructError(JsonParser.java:1433) at org.codehaus.jackson.impl.JsonParserMinimalBase._reportError(JsonParserMinimalBase.java:521) at org.codehaus.jackson.impl.JsonParserMinimalBase._reportUnexpectedChar(JsonParserMinimalBase.java:442) at org.codehaus.jackson.impl.ReaderBasedParser._handleUnexpectedValue(ReaderBasedParser.java:1198) at org.codehaus.jackson.impl.ReaderBasedParser.nextToken(ReaderBasedParser.java:485) at org.codehaus.jackson.map.ObjectMapper._initForReading(ObjectMapper.java:2770) at org.codehaus.jackson.map.ObjectMapper._readMapAndClose(ObjectMapper.java:2718) at org.codehaus.jackson.map.ObjectMapper.readValue(ObjectMapper.java:1877) at bitbucketpullrequestbuilder.bitbucketpullrequestbuilder.bitbucket.ApiClient.parse(ApiClient.java:275) at bitbucketpullrequestbuilder.bitbucketpullrequestbuilder.bitbucket.ApiClient.getAllValues(ApiClient.java:206) at bitbucketpullrequestbuilder.bitbucketpullrequestbuilder.bitbucket.ApiClient.getPullRequests(ApiClient.java:105) at bitbucketpullrequestbuilder.bitbucketpullrequestbuilder.BitbucketRepository.getTargetPullRequests(BitbucketRepository.java:94) at bitbucketpullrequestbuilder.bitbucketpullrequestbuilder.BitbucketPullRequestsBuilder.run(BitbucketPullRequestsBuilder.java:37) at bitbucketpullrequestbuilder.bitbucketpullrequestbuilder.BitbucketBuildTrigger.run(BitbucketBuildTrigger.java:292) at hudson.triggers.Trigger.checkTriggers(Trigger.java:278) at hudson.triggers.Trigger$Cron.doRun(Trigger.java:226) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
Add Comment
[JIRA] (JENKINS-54670) Continous builds upon bitbuckt pull request
Title: Message Title Luca Moscato created an issue Jenkins / JENKINS-54670 Continous builds upon bitbuckt pull request Issue Type: Bug Assignee: Unassigned Components: bitbucket-pullrequest-builder-plugin Created: 2018-11-16 10:53 Environment: jenkins-2.138.3-1.1.noarch runnnig on centos6 bitbucket-pull-request-builder 1.4.26 Priority: Critical Reporter: Luca Moscato The projects that make a build triggered by a Bitbucket pull request continuously perform builds even nothing new is available Bitbucket side. This has 2 main consequence, longest build queue but, on top of that, this issue is literally killing our infrastructure since is based on AWS EC2 using T type machine, optimized for cpu load peaks with a credit mechanism https://aws.amazon.com/ec2/instance-types/t2/?nc1=h_ls Add Comment
[JIRA] (JENKINS-54667) Getting Error while accessing Performance Report
Title: Message Title Artem Fedorov commented on JENKINS-54667 Re: Getting Error while accessing Performance Report So, you have a lot of builds and it cause StackOverFlow error. I think you can configure the count of builds for show in Performance Trend -> Configure Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-48687) Bitbucket Branch Source Plugin: changes are missing for builds again
Title: Message Title benoit guerin updated an issue Jenkins / JENKINS-48687 Bitbucket Branch Source Plugin: changes are missing for builds again Change By: benoit guerin Attachment: jenkins_global_lib.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-48687) Bitbucket Branch Source Plugin: changes are missing for builds again
Title: Message Title benoit guerin commented on JENKINS-48687 Re: Bitbucket Branch Source Plugin: changes are missing for builds again Also, for global pipeline librairies, be aware that, by defaut, changelog is not computed for them. You can override this behaviour on library configuration or in a Jenkinsfile, like said in the doc : Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54667) Getting Error while accessing Performance Report
Title: Message Title Artem Fedorov updated an issue Jenkins / JENKINS-54667 Getting Error while accessing Performance Report Change By: Artem Fedorov Attachment: Screenshot.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54651) Refusing to marshal net.sf.json.JSONObject
Title: Message Title Oleg Nenashev updated JENKINS-54651 AFAICT you report an issue for your custom plugin you are trying to create. "MagicPlugBuildWrapper" does not exist in GitHub. The error is a valid rejection of a class. JSONObject instances should not be persisted to the disk. See JEP-200 for the explanation and guidelines: https://jenkins.io/blog/2018/03/15/jep-200-lts/ Jenkins / JENKINS-54651 Refusing to marshal net.sf.json.JSONObject Change By: Oleg Nenashev Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54651) Refusing to marshal net.sf.json.JSONObject
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54651 Refusing to marshal net.sf.json.JSONObject Change By: Oleg Nenashev Component/s: other Component/s: maven-hpi-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54651) Refusing to marshal net.sf.json.JSONObject
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54651 Refusing to marshal net.sf.json.JSONObject Change By: Oleg Nenashev Labels: JEP-200 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-51985) Create official jenkins/jenkins Docker images for Java 10 and 11 versions
Title: Message Title Baptiste Mathus started work on JENKINS-51985 Change By: Baptiste Mathus Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54663) Unable to run Perfromance Center scenario from Jenkins
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54663 Unable to run Perfromance Center scenario from Jenkins Change By: Oleg Nenashev Component/s: micro-focus-performance-center-integration-plugin Component/s: _unsorted Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54663) Unable to run Perfromance Center scenario from Jenkins
Title: Message Title Oleg Nenashev assigned an issue to Daniel Danan Jenkins / JENKINS-54663 Unable to run Perfromance Center scenario from Jenkins Change By: Oleg Nenashev Assignee: Oleg Nenashev Daniel Danan Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-45478) Add support for utm_ query parameters
Title: Message Title Stephen Connolly updated JENKINS-45478 Jenkins / JENKINS-45478 Add support for utm_ query parameters Change By: Stephen Connolly Status: In Review Resolved Assignee: Stephen Connolly Resolution: Fixed Released As: 2.3.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54667) Getting Error while accessing Performance Report
Title: Message Title Satish Ramamuni commented on JENKINS-54667 Re: Getting Error while accessing Performance Report Hi Artem The build is getting created every 15 mins. Gave the screenshot of latest build Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54667) Getting Error while accessing Performance Report
Title: Message Title Satish Ramamuni updated an issue Jenkins / JENKINS-54667 Getting Error while accessing Performance Report Change By: Satish Ramamuni Attachment: image-2018-11-16-16-06-15-773.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54669) Use sensible defaults settings for the datasource configuration
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-54669 Use sensible defaults settings for the datasource configuration Issue Type: New Feature Assignee: Cyrille Le Clerc Components: pipeline-maven-plugin Created: 2018-11-16 10:36 Priority: Minor Reporter: Cyrille Le Clerc Use sensible defaults settings for the datasource configuration. https://github.com/brettwooldridge/HikariCP#configuration-knobs-baby Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-54667) Getting Error while accessing Performance Report
Title: Message Title Satish Ramamuni assigned an issue to Satish Ramamuni Jenkins / JENKINS-54667 Getting Error while accessing Performance Report Change By: Satish Ramamuni Assignee: Artem Fedorov Satish Ramamuni Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-52279) Create Dockerfiles for Java 11 jenkins/ssh-slave images
Title: Message Title Baptiste Mathus commented on JENKINS-52279 Re: Create Dockerfiles for Java 11 jenkins/ssh-slave images Fixed: $ docker pull jenkins/ssh-slave:latest latest: Pulling from jenkins/ssh-slave Digest: sha256:0ba642d8ea4a4ea6aed01ac9786c14b458a69ee14e35c69b61d140237256b7a6 Status: Image is up to date for jenkins/ssh-slave:latest $ docker pull jenkins/ssh-slave:latest-jdk11 latest-jdk11: Pulling from jenkins/ssh-slave Digest: sha256:3972de8d1901889e34c9eebbc3cf66c1ce53657e513a9a8932a2eecbf779dad7 Status: Image is up to date for jenkins/ssh-slave:latest-jdk11 $ docker run --entrypoint=java jenkins/ssh-slave:latest -version openjdk version "1.8.0_181" OpenJDK Runtime Environment (build 1.8.0_181-8u181-b13-2~deb9u1-b13) OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode) $ docker run --entrypoint=java jenkins/ssh-slave:latest-jdk11 -version openjdk version "11.0.1" 2018-10-16 OpenJDK Runtime Environment (build 11.0.1+13-Debian-2) OpenJDK 64-Bit Server VM (build 11.0.1+13-Debian-2, mixed mode, sharing) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-52279) Create Dockerfiles for Java 11 jenkins/ssh-slave images
Title: Message Title Baptiste Mathus updated JENKINS-52279 Jenkins / JENKINS-52279 Create Dockerfiles for Java 11 jenkins/ssh-slave images Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54666) vsphere plugin job succesful but VMs in vcenter not created
Title: Message Title Velan Nagarajan updated an issue Jenkins / JENKINS-54666 vsphere plugin job succesful but VMs in vcenter not created Sorted out the issue, I was using Datastore_Cluster name in place of individual datastore name, Hence i have marked this as an improvements. As while using for CICD whenever the datastore gets exhausted manual intervention is required to change to other datastore, If the Datastore Cluster value is also accepted for VM provisioning that would support CICD. Change By: Velan Nagarajan Issue Type: Bug Improvement Priority: Blocker Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54667) Getting Error while accessing Performance Report
Title: Message Title Artem Fedorov commented on JENKINS-54667 Re: Getting Error while accessing Performance Report Hi, How much builds do you have in your job? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-48687) Bitbucket Branch Source Plugin: changes are missing for builds again
Title: Message Title benoit guerin commented on JENKINS-48687 Re: Bitbucket Branch Source Plugin: changes are missing for builds again Ok, got it, it is in the git plugin, which does not compute changelog for the first build of a new branch : JENKINS-14138 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54667) Getting Error while accessing Performance Report
Title: Message Title Artem Fedorov assigned an issue to Artem Fedorov Jenkins / JENKINS-54667 Getting Error while accessing Performance Report Change By: Artem Fedorov Assignee: Andrey Pokhilko Artem Fedorov Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-44849) Changeset for first run of generated job is empty
Title: Message Title benoit guerin commented on JENKINS-44849 Re: Changeset for first run of generated job is empty Same on bitbucket-branch-source-plugin here : JENKINS-48687 It goes down to the git plugin itself, not computing the changelog for the first build of a new branch : JENKINS-14138 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-16867) Default ProcessTree should call any plugins to kill build
Title: Message Title Oleg Nenashev started work on JENKINS-16867 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-16867) Default ProcessTree should call any plugins to kill build
Title: Message Title Oleg Nenashev commented on JENKINS-16867 Re: Default ProcessTree should call any plugins to kill build https://github.com/jenkinsci/jenkins/pull/3730 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-16867) Default ProcessTree should call any plugins to kill build
Title: Message Title Oleg Nenashev updated JENKINS-16867 Jenkins / JENKINS-16867 Default ProcessTree should call any plugins to kill build Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-16867) Default ProcessTree should call any plugins to kill build
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-16867 Default ProcessTree should call any plugins to kill build Change By: Oleg Nenashev Assignee: sam leung Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-52279) Create Dockerfiles for Java 11 jenkins/ssh-slave images
Title: Message Title Oleg Nenashev commented on JENKINS-52279 Re: Create Dockerfiles for Java 11 jenkins/ssh-slave images https://github.com/jenkinsci/docker-ssh-slave/pull/24 was another iteration Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54666) vsphere plugin job succesful but VMs in vcenter not created
Title: Message Title Velan Nagarajan updated an issue Jenkins / JENKINS-54666 vsphere plugin job succesful but VMs in vcenter not created Change By: Velan Nagarajan Started by user |http://*.com:8080/user/][EnvInject] - Loading node environment variables.Building remotely on [drake|http://**.com:8080/computer/drake] in workspace C:\cygwin\home\current\workspace\DeployVM[vSphere] [vSphere] Performing vSphere build step: "Deploy VM from template"[vSphere] Attempting to use server configuration: "E**Vcenter"[vSphere] Deploying new vm "AUTNEW" from template "***_Template"Finished: SUCCESSAbove logs are displayed in console logs of vsphere job, But when i checked the vcenter for the VM existence VM is not created. Still the jenkins says job status success.I am blocked because of this and no VM creation is happening. But Datastore is available in vsphere. Attached logsJenkins.txt from /var/log/jenkins/. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54666) vsphere plugin job succesful but VMs in vcenter not created
Title: Message Title Velan Nagarajan updated an issue Jenkins / JENKINS-54666 vsphere plugin job succesful but VMs in vcenter not created Change By: Velan Nagarajan Attachment: logsJenkins.txt Started by user |http://*.com:8080/user/][EnvInject] - Loading node environment variables.Building remotely on [drake|http://**.com:8080/computer/drake] in workspace C:\cygwin\home\current\workspace\DeployVM[vSphere] [vSphere] Performing vSphere build step: "Deploy VM from template"[vSphere] Attempting to use server configuration: "E**Vcenter"[vSphere] Deploying new vm "AUTNEW" from template "***_Template"Finished: SUCCESSAbove logs are displayed in console logs of vsphere job, But when i checked the vcenter for the VM existence VM is not created. Still the jenkins says job status success.I am blocked because of this and no VM creation is happening. Attached logsJenkins.txt from /var/log/jenkins/. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from
[JIRA] (JENKINS-54206) Merged PRs not being removed from multibranch
Title: Message Title Gunter Grodotzki commented on JENKINS-54206 Re: Merged PRs not being removed from multibranch Aaaah, thanks so much for this. Actually it never gets to that, because it is crashing earlier: https://issues.jenkins-ci.org/browse/JENKINS-52397?focusedCommentId=353950=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-353950 I am not quite sure though if this is happening from the github-branch plugin (discovering tags) or build-strategies. On another installation where I am not having above issue, but the same issue that PRs/Branches/Tags are not being removed, however I do not see any mention of "Evaluating orphaned..." in the logs: Branch indexing [Fri Nov 16 09:46:02 UTC 2018] Starting branch indexing... Connecting to https://api.github.com using lifeofguenter/** (github-lifeofguenter-jenkins_sudo) Examining lifeofguenter/jenkinsfile-test Checking branches... Getting remote branches... Checking branch master Getting remote pull requests... ‘Jenkinsfile’ found Met criteria No changes detected: master (still at 4c0116442a6e632994ccf58c9af2fde9b6f01049) Checking branch foobarb Checking branch test-shared-lib Checking branch test-tag 4 branches were processed Checking pull-requests... Checking pull request #13 ‘Jenkinsfile’ found Met criteria No changes detected: PR-13 (still at e7990d4573285eff2e0c0bdb2b94e82214b59386) 1 pull requests were processed Checking tags... Getting remote tags... Checking tag 0.0.1 ‘Jenkinsfile’ found Met criteria Changes detected: 0.0.1 (null → 8254b3af7e2278babc43dfcc414810ab4121) No automatic builds for 0.0.1 Checking tag 0.0.2 ‘Jenkinsfile’ found Met criteria Changes detected: 0.0.2 (null → 8254b3af7e2278babc43dfcc414810ab4121) No automatic builds for 0.0.2 Checking tag 0.0.3 ‘Jenkinsfile’ found Met criteria Changes detected: 0.0.3 (null → 8254b3af7e2278babc43dfcc414810ab4121) No automatic builds for 0.0.3 Checking tag 0.0.4 ‘Jenkinsfile’ found Met criteria No changes detected: 0.0.4 (still at 4c0116442a6e632994ccf58c9af2fde9b6f01049) 4 tags were processed Finished examining lifeofguenter/jenkinsfile-test [Fri Nov 16 09:46:05 UTC 2018] Finished branch indexing. Indexing took 2.9 sec Finished: SUCCESS Add Comment
[JIRA] (JENKINS-52397) Org Scan blows up when repository has no tags
Title: Message Title Gunter Grodotzki commented on JENKINS-52397 Re: Org Scan blows up when repository has no tags I am also getting the error on projects that have tags? Getting remote tags... ERROR: [Fri Nov 16 00:49:03 UTC 2018] Could not fetch branches from source org.jenkinsci.plugins.github_branch_source.GitHubSCMNavigator::https://api.github.com::foobar::chef-wrapper-ntp org.kohsuke.github.GHException: Failed to retrieve https://api.github.com/repos/foobar/chef-wrapper-ntp/git/refs/tags at org.kohsuke.github.Requester$PagingIterator.fetch(Requester.java:521) at org.kohsuke.github.Requester$PagingIterator.hasNext(Requester.java:486) at org.kohsuke.github.PagedIterator.fetch(PagedIterator.java:44) at org.kohsuke.github.PagedIterator.hasNext(PagedIterator.java:32) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource$LazyTags$1$1.hasNext(GitHubSCMSource.java:) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:1016) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:374) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:284) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:633) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1024) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) [Fri Nov 16 00:49:03 UTC 2018] Finished branch indexing. Indexing took 2.3 sec FATAL: Failed to recompute children of foobar » chef-wrapper-ntp org.kohsuke.github.GHException: Failed to retrieve https://api.github.com/repos/foobar/chef-wrapper-ntp/git/refs/tags at org.kohsuke.github.Requester$PagingIterator.fetch(Requester.java:521) at org.kohsuke.github.Requester$PagingIterator.hasNext(Requester.java:486) at org.kohsuke.github.PagedIterator.fetch(PagedIterator.java:44) at org.kohsuke.github.PagedIterator.hasNext(PagedIterator.java:32) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource$LazyTags$1$1.hasNext(GitHubSCMSource.java:) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:1016) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:374) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:284) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:633) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1024) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Finished: FAILURE
[JIRA] (JENKINS-54668) Unable to provide NodeJS path to Jenkins plugin
Title: Message Title Monali Chaudhary updated an issue Jenkins / JENKINS-54668 Unable to provide NodeJS path to Jenkins plugin Change By: Monali Chaudhary Hi,I have RHEL env on which Jenkins is installed as well as NodeJS. I have the node file located in /usr/local/bin.. but when I give this same path in the NodeJS installation path of Jenkins Configure Tool section, it fails when I run the job, below is the error:_ERROR: Couldn't find any executable in "/usr/local/bin/"__Finished: FAILURE_Please tell me what path needs to be given in linux Jenkins for NodeJS as in windows we have .exe location, in linux I could only find the location for my node as :whereis nodenode: /usr/bin/node /usr/local/bin/node Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54668) Unable to provide NodeJS path to Jenkins plugin
Title: Message Title Monali Chaudhary created an issue Jenkins / JENKINS-54668 Unable to provide NodeJS path to Jenkins plugin Issue Type: Task Assignee: Nikolas Falco Components: nodejs-plugin Created: 2018-11-16 09:36 Environment: RHEL 7.2 Priority: Minor Reporter: Monali Chaudhary Hi, I have RHEL env on which Jenkins is installed as well as NodeJS. I have the node file located in /usr/local/bin.. but when I give this same path in the NodeJS installation path of Jenkins Configure Tool section, it fails when I run the job, below is the error: ERROR: Couldn't find any executable in "/usr/local/bin/" Finished: FAILURE Please tell me what path needs to be given in linux for NodeJS as in windows we have .exe location, in linux I could only find the location for my node as : whereis node node: /usr/bin/node /usr/local/bin/node Add Comment
[JIRA] (JENKINS-54601) Include some changes from 1.9.40
Title: Message Title Evaristo Gutierrez updated JENKINS-54601 Jenkins / JENKINS-54601 Include some changes from 1.9.40 Change By: Evaristo Gutierrez Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54010) Support two levels of parallelity in stages
Title: Message Title Dirk Gausmann edited a comment on JENKINS-54010 Re: Support two levels of parallelity in stages This picture demonstrates it better... running parallel within parallel without a step before makes no sense since you could just run them in the outer parallel task. ! https://issues.jenkins-ci.org/secure/attachment/36602/ pipeline_mockup.png ! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54010) Support two levels of parallelity in stages
Title: Message Title Dirk Gausmann edited a comment on JENKINS-54010 Re: Support two levels of parallelity in stages This picture demonstrates it better... running parallel within parallel without a step before makes no sense since you could just run them in the outer parallel task.!pipeline_mockup.png! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54206) Merged PRs not being removed from multibranch
Title: Message Title Stephen Connolly resolved as Incomplete Marking as incomplete until more info is provided... likely this is build logs being requested to be kept in which case functioning as designed Jenkins / JENKINS-54206 Merged PRs not being removed from multibranch Change By: Stephen Connolly Status: Reopened Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54206) Merged PRs not being removed from multibranch
Title: Message Title Stephen Connolly commented on JENKINS-54206 Re: Merged PRs not being removed from multibranch The most likely reason is somebody is requesting that the build logs be kept: https://github.com/jenkinsci/cloudbees-folder-plugin/blob/f313065f5fb613c4fedf78627a9cddee7a600388/src/main/java/com/cloudbees/hudson/plugins/folder/computed/DefaultOrphanedItemStrategy.java#L252-L271 and if you request the build logs be kept then we'll honour that request Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54206) Merged PRs not being removed from multibranch
Title: Message Title Stephen Connolly commented on JENKINS-54206 Re: Merged PRs not being removed from multibranch Go to the Scan Repository Log screen, i.e. the one with the URL that ends in `/indexing/console`. Scroll down to the bottom and see what the orphaned item strategy is printing out. I'd expect something like: Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54206) Merged PRs not being removed from multibranch
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-54206 Merged PRs not being removed from multibranch Change By: Stephen Connolly Attachment: Screenshot 2018-11-16 at 09.10.24.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-52279) Create Dockerfiles for Java 11 jenkins/ssh-slave images
Title: Message Title Baptiste Mathus commented on JENKINS-52279 Re: Create Dockerfiles for Java 11 jenkins/ssh-slave images PR was https://github.com/jenkinsci/docker-ssh-slave/pull/22 Image was uploaded, tag latest-jdk11 on https://hub.docker.com/r/jenkins/ssh-slave/tags/ But seems like for some reason it wasn't updated to JDK11, digging: $ docker run --entrypoint=java jenkins/ssh-slave:latest-jdk11 -version openjdk version "1.8.0_181" OpenJDK Runtime Environment (build 1.8.0_181-8u181-b13-2~deb9u1-b13) OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-52279) Create Dockerfiles for Java 11 jenkins/ssh-slave images
Title: Message Title Baptiste Mathus updated JENKINS-52279 Jenkins / JENKINS-52279 Create Dockerfiles for Java 11 jenkins/ssh-slave images Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54010) Support two levels of parallelity in stages
Title: Message Title Dirk Gausmann commented on JENKINS-54010 Re: Support two levels of parallelity in stages This picture demonstrates it better... running parallel within parallel without a step before makes no sense since you could just run them in the outer parallel task. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54633) build dedicated VPC while installing evergreen on AWS
Title: Message Title Baptiste Mathus assigned an issue to Dominik Bartholdi Jenkins / JENKINS-54633 build dedicated VPC while installing evergreen on AWS Change By: Baptiste Mathus Assignee: Baptiste Mathus Dominik Bartholdi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54633) build dedicated VPC while installing evergreen on AWS
Title: Message Title Baptiste Mathus started work on JENKINS-54633 Change By: Baptiste Mathus Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-51191) hudson.remoting.Channel$CallSiteStackTrace: Remote call to
Title: Message Title Roman Zwi commented on JENKINS-51191 Re: hudson.remoting.Channel$CallSiteStackTrace: Remote call to Is the correct version of slave.jar running on the slave? You can download it from /jnlpJars/slave.jar You can use the Versions Node Monitors plugin to have it checked automatically. It also adds the versions to the node list. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-49997) Pipeline Declarative post unsuccessful block
Title: Message Title
Reinhold Füreder commented on JENKINS-49997
Re: Pipeline Declarative post unsuccessful block
In the meantime there are also:
"cleanup", which is presumably the suggested "finally" ("Always run after all other conditions, regardless of build status")
"regression, but this will not be run anymore if it keeps to be unsuccessful ("Run if the current builds status is worse than the previous builds status")
However, I was also looking for an "unsuccessful" to be able to notify for broken build (a) independent of "unstable"/"failure"/"aborted" and (b) also keep notifying if it is still broken (so not just on first broken build, which would be supported by "regression") A little bit related sounds JENKINS-53889? An alternative approach that I guess might also be not easy to support could be a let's call it "multi-":
post {
always {
// do some stuff to collect junit reports
}
success {
// push the tags
}
unstable|failure|aborted {
sh "mvn nexus-staging:drop"
}
}
=> So agreeing with Stephen Connolly, maybe the "unsuccessful" might be the easiest to implement and use!?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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.
