[JIRA] (JENKINS-27548) Sporadic IOException: Failed to persist config
Title: Message Title Tomas Norre Mikkelsen commented on JENKINS-27548 Re: Sporadic IOException: Failed to persist config I'll Start to create Pull Request for the changes on the dependencies. Shouldn't harm anything if I read the Changelog correctly https://xerces.apache.org/xerces2-j/releases.html 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-27548) Sporadic IOException: Failed to persist config
Title: Message Title Tomas Norre Mikkelsen commented on JENKINS-27548 Re: Sporadic IOException: Failed to persist config Could it be an idea to update the Plugins still using an older version of the `xercesImpl-2.11.0.jar` or even older [1]. The Plugins I currently have using this library is following versions: 2.11.0 (Released Feb. 2013) 2.9.1 (Release Oct. 2008) 2.8.1 (Release Oct. 2006) So they are all pretty old. 1) https://mvnrepository.com/artifact/xerces/xercesImpl 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-53435) Categorizing of jenkins job failing
Title: Message Title Dinesh updated an issue Jenkins / JENKINS-53435 Categorizing of jenkins job failing Change By: Dinesh I wanted to move my Jenkins job into a particular category in view, we used *jenkins-cli.jar* for this (This is an automation). It was working earlier and since few weeks it stopped working and facing the below issue. [java] Exception in thread "main" java.io.EOFException [java] at java.io.DataInputStream.readFully(DataInputStream.java:197) [java] at java.io.DataInputStream.readUTF(DataInputStream.java:609) [java] at java.io.DataInputStream.readUTF(DataInputStream.java:564) [java] at hudson.cli.CLI.connectViaCliPort(CLI.java:225) [java] at hudson.cli.CLI.(CLI.java:126) [java] at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:72) [java] at hudson.cli.CLI._main(CLI.java:466) [java] at hudson.cli.CLI.main(CLI.java:382) [java] Suppressed: java.io.EOFException: unexpected stream termination [java] at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:331) [java] at hudson.remoting.Channel.(Channel.java:421) [java] at hudson.remoting.Channel.(Channel.java:400) [java] at hudson.remoting.Channel.(Channel.java:396) [java] at hudson.remoting.Channel.(Channel.java:385) [java] at hudson.remoting.Channel.(Channel.java:377) [java] at hudson.remoting.Channel.(Channel.java:353) [java] at hudson.cli.CLI.connectViaHttp(CLI.java:157) [java] at hudson.cli.CLI.(CLI.java:130) [java] ... 3 more The only change made in project was the URL from HTTP to HTTPS. Will it cause the issue to happen ? If this is the issue how can we make it work ? Please suggest. As an alternative way, I tried creating Jenkins job inside a view using cURL and I wanted the particular job inside a category. Moving a job inside category doesn't work here. Kindly help. Add Comment
[JIRA] (JENKINS-53435) Categorizing of jenkins job failing
Title: Message Title Dinesh created an issue Jenkins / JENKINS-53435 Categorizing of jenkins job failing Issue Type: Bug Assignee: Unassigned Components: cli Created: 2018-09-06 05:28 Environment: Jenkins version - 2.121.2 Priority: Critical Reporter: Dinesh I wanted to move my Jenkins job into a particular category in view, we used jenkins-cli.jar for this (This is an automation). It was working earlier and since few weeks it stopped working and facing the below issue. [java] Exception in thread "main" java.io.EOFException [java] at java.io.DataInputStream.readFully(DataInputStream.java:197) [java] at java.io.DataInputStream.readUTF(DataInputStream.java:609) [java] at java.io.DataInputStream.readUTF(DataInputStream.java:564) [java] at hudson.cli.CLI.connectViaCliPort(CLI.java:225) [java] at hudson.cli.CLI.(CLI.java:126) [java] at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:72) [java] at hudson.cli.CLI._main(CLI.java:466) [java] at hudson.cli.CLI.main(CLI.java:382) [java] Suppressed: java.io.EOFException: unexpected stream termination [java] at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:331) [java] at hudson.remoting.Channel.(Channel.java:421) [java] at hudson.remoting.Channel.(Channel.java:400) [java] at hudson.remoting.Channel.(Channel.java:396) [java] at hudson.remoting.Channel.(Channel.java:385) [java] at hudson.remoting.Channel.(Channel.java:377) [java] at hudson.remoting.Channel.(Channel.java:353) [java] at hudson.cli.CLI.connectViaHttp(CLI.java:157) [java] at hudson.cli.CLI.(CLI.java:130) [java] ... 3 more The only change made in project was the URL from HTTP to HTTPS. Will it cause the issue to happen ? If this is the issue how can we make it work ? Please suggest. As an alternative way, I tried creating Jenkins
[JIRA] (JENKINS-53399) Lost all saved managed files after upgrade to 3.0
Title: Message Title Dominik Bartholdi commented on JENKINS-53399 Re: Lost all saved managed files after upgrade to 3.0 Giacomo Boccardo Stefan Rempfer not sure this will be possible - the problem is that the serialized field is not part of my code, but a member of TreeMap -> java.util.TreeMap#comparator Oleg Nenashev do you have any idea how this could be solved? I currently only see the possibility to lift 'compatibleSince' or roll back and therefore screw the users who upgraded to 3.0 again... 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-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title Maxfield Stewart commented on JENKINS-51057 Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM We're having this problem with blue ocean 1.4.2 and Jenkins 2.112. Out of a 18 GB heap, 16GB are the GuavaPubSub object which containes the concurrent queue and EventDispatchers. We ran Jon Sten 's script and it cleaned up only 2.5GB's of retry objects but still had 14GB's of references to EventDispatchers. It takes' out our Jenkins Server in about 14-15 days. I took a heap dump and am adding a screenshot of a MAT analyzer view of the memory consumption. Was hoping someone would accept the PR for the memory leak fix which seems to be outstanding for some time now. 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-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title Maxfield Stewart updated an issue Jenkins / JENKINS-51057 EventDispatcher and ConcurrentLinkedQueue ate my JVM Change By: Maxfield Stewart Attachment: image-2018-09-05-18-59-08-587.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-53434) Jenkins redirecting to http url even though jenkins_url is configured to be https
Title: Message Title Nitin Surana created an issue Jenkins / JENKINS-53434 Jenkins redirecting to http url even though jenkins_url is configured to be https Issue Type: Bug Assignee: Unassigned Components: url-auth Created: 2018-09-06 01:49 Priority: Minor Reporter: Nitin Surana I don't know what component does it belong to. I have jenkins behind a https gateway. Gateway gets request at 443 and forwards to jenkins running at 8080. It works fine for many urls but when I click on any plugin/job url which doesn't end in `/` then jenkins redirects to an http url with a `/` at the end, which breaks because there's no http. I already have the https url configured in ConfigureSystem settings, yet jenkins keep redirecting to a http url. It's probably duplicate of https://issues.jenkins-ci.org/browse/JENKINS-10675 Add Comment
[JIRA] (JENKINS-53140) Intermittent Random Stage Failures - No Changes Detected - Parallel Stages
Title: Message Title jerry wiltse commented on JENKINS-53140 Re: Intermittent Random Stage Failures - No Changes Detected - Parallel Stages is there any additional logging i can turn on to try to identify the root cause of this issue? Also, if we have 3 or 4 commits in a row before, we have 1 job for each commit kick off basically at the same time. They all share a single source directory, so I wonder if there's not some contention/conflict between each of those build threads. Also, I want to make sure you have taken notice of my previous point about duplicate changes messages, so i attached a screenshot. 1 commit, 5 identical changes are listed (the number of times it appears is equal to number of stages). Also, currently we have parallel builds disabled and it's still showing these duplicates. 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-53140) Intermittent Random Stage Failures - No Changes Detected - Parallel Stages
Title: Message Title jerry wiltse updated an issue Jenkins / JENKINS-53140 Intermittent Random Stage Failures - No Changes Detected - Parallel Stages Change By: jerry wiltse Attachment: Screenshot-of-jenkins-svn-duplicate-changes.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-45693) Ability to decorate Pipeline builds as a global extension
Title: Message Title Jesse Glick commented on JENKINS-45693 Re: Ability to decorate Pipeline builds as a global extension when for example using the logstash plugin …though this is an invalid use case. JEP-210 has direct support for external log storage. There is work underway on a Logstash implementation, not based on the existing 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-45693) Ability to decorate Pipeline builds as a global extension
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-45693 Ability to decorate Pipeline builds as a global extension Change By: Jesse Glick Issue Type: Bug New Feature Priority: Minor Major Labels: api console 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-45693) Ability to decorate Pipeline builds as a global extension
Title: Message Title Jesse Glick updated JENKINS-45693 Jenkins / JENKINS-45693 Ability to decorate Pipeline builds as a global extension Change By: Jesse Glick 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-38381) [JEP-210] Optimize log handling in Pipeline and Durable Task
Title: Message Title Jesse Glick updated JENKINS-38381 Jenkins / JENKINS-38381 [JEP-210] Optimize log handling in Pipeline and Durable Task Change By: Jesse Glick 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-45693) Ability to decorate Pipeline builds as a global extension
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-45693 Ability to decorate Pipeline builds as a global extension ConsoleLogFilter itself did not work out; filed PRs introducing a better API. Change By: Jesse Glick Summary: Apply ConsoleLogFilter Ability to decorate Pipeline builds as a global extension Component/s: workflow-api-plugin Component/s: workflow-job-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-53345) The evergreen UI constantly redirects to http:/// instead of http://:8080
Title: Message Title R. Tyler Croy started work on JENKINS-53345 Change By: R. Tyler Croy 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-49033) Issue with HPE Application Automation Tools plugin
Title: Message Title Edwin Avedian commented on JENKINS-49033 Re: Issue with HPE Application Automation Tools plugin Rolando-Mihai Vlad, I apologize for the long delay. I am picking up this issue from my colleague Harsimrat and I am attaching the 2 .lra files requested, LRA.lra from the Jenkins run and Session1.lra from the LR controller run. What I notice is that NoData is showing up for missing transactions when run from Jenkins. The question is why some transactions are missing when the scenario is run using Jenkins plugin. Session1.lra LRA.lra 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-49033) Issue with HPE Application Automation Tools plugin
Title: Message Title Edwin Avedian updated an issue Jenkins / JENKINS-49033 Issue with HPE Application Automation Tools plugin Change By: Edwin Avedian Attachment: Session1.lra 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-49033) Issue with HPE Application Automation Tools plugin
Title: Message Title Edwin Avedian updated an issue Jenkins / JENKINS-49033 Issue with HPE Application Automation Tools plugin Change By: Edwin Avedian Attachment: LRA.lra 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-49033) Issue with HPE Application Automation Tools plugin
Title: Message Title Edwin Avedian reopened an issue Jenkins / JENKINS-49033 Issue with HPE Application Automation Tools plugin Change By: Edwin Avedian Resolution: Incomplete Status: Closed Reopened 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-53433) withEnv case wrong variable modified.
Title: Message Title
Kevin Fox created an issue
Jenkins / JENKINS-53433
withEnv case wrong variable modified.
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2018-09-05 20:26
Priority:
Minor
Reporter:
Kevin Fox
I have a system on which both NO_PROXY and no_proxy are defined already. I have a program I am trying to execute in my pipeline that reads only NO_PROXY. I tried to override NO_PROXY like: withEnv(["NO_PROXY=$NO_PROXY,otherthingy"]) { sh 'program' } but it mistakenly edits the 'no_proxy' version instead, not touching the NO_PROXY one.
Add Comment
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Devin Nusbaum commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume Keith Ball There is often a slight time delay between when a new release is visible on the update center and when it is available on all mirrors, my guess is that was what happened for you. 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-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Keith Ball commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume Forget it. it's there now 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-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Keith Ball commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume I just tried to update the plugin but received a FileNotFoundException: http://archives.jenkins-ci.org/plugins/workflow-job/2.25/workflow-job.hpi Failed to download from http://updates.jenkins-ci.org/download/plugins/workflow-job/2.25/workflow-job.hpi (redirected to: http://archives.jenkins-ci.org/plugins/workflow-job/2.25/workflow-job.hpi) Did someone forget to publish the latest version? 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-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Devin Nusbaum updated JENKINS-50199 I just released version 2.25 of the Pipeline Job plugin which should fix the issue where completed builds are resuming after restarting Jenkins. If anyone is still seeing the issue after upgrading the plugin, please comment with any additional information you can provide, such as the build folder of the build in question. Note that there are other issues that may appear similar but seem to have distinct causes. For anyone newly commenting on this issue, if you are seeing stuck executors without ever restarting Jenkins, please check if JENKINS-45571, JENKINS-53223, or JENKINS-51568 are closer to your situation and if so, comment there instead. Thanks! Jenkins / JENKINS-50199 Failed pipeline jobs stuck running after incorrect resume Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: Pipeline Job 2.25 Add Comment This
[JIRA] (JENKINS-53427) Agent creation failure because of concurrent attempts to schedule a pod
Title: Message Title Alex Medvedev updated an issue Jenkins / JENKINS-53427 Agent creation failure because of concurrent attempts to schedule a pod Change By: Alex Medvedev Summary: Failed create agent Agent creation failure because of concurrent attempts to schedule a pod 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-45693) Apply ConsoleLogFilter
Title: Message Title Jesse Glick started work on JENKINS-45693 Change By: Jesse Glick 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-45693) Apply ConsoleLogFilter
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-45693 Apply ConsoleLogFilter Change By: Jesse Glick Assignee: Jesse Glick 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-48873) EC2 Plugin does not support us-gov-west-1 region
Title: Message Title Andrew Hamilton commented on JENKINS-48873 Re: EC2 Plugin does not support us-gov-west-1 region I'd like to add my name to the list as really needing this. 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-52058) Provide report filename as variable to Groovy parser
Title: Message Title Ulli Hafner commented on JENKINS-52058 Re: Provide report filename as variable to Groovy parser There are two ways to start the same parser twice: use a comma separated list in the pattern text box enable the check box "Aggregate results" Would it make more sense to add ID and name per each parser in the UI? This will bloat up the user interface... 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-53432) Unable to automatically discover and build git tags with Jenkins multibranch pipelines and the Git Plugin
Title: Message Title Ryan Taylor created an issue Jenkins / JENKINS-53432 Unable to automatically discover and build git tags with Jenkins multibranch pipelines and the Git Plugin Issue Type: Bug Assignee: Mark Waite Attachments: image-2018-09-05-12-57-45-991.png, image-2018-09-05-13-03-24-545.png Components: git-plugin Created: 2018-09-05 17:05 Environment: * Jenkins v2.141 * Basic Branch Build Strategies Plugin v1.0.1 * Git plugin v3.9.1 * Bitbucket Server v5.13.1 * Webhook to Jenkins for Bitbucket Server v4.4.4 * Windows Server 2012 R2 Priority: Major Reporter: Ryan Taylor I configured a multibranch pipeline job to discover and build branches and tags for my git repository hosted in Bitbucket Server. New branches and commits are discovered and built correctly but new tags remain undiscovered. I can force tag discovery if I initiate a manual scan in Jenkins or I click "Trigger Jenkins" in the Webhook to Jenkins for Bitbucket Server UI for my repository. My Jenkins Configuration My Webhook to Jenkins for Bitbucket Server Configuration Originally, I wanted to use the Bitbucket Branch Source Plugin rather than the Git Plugin but in that case JENKINS-51063 prevents tag discovery and build. Is there a similar issue with the Git Plugin?
[JIRA] (JENKINS-49305) view-job-filters-plugin regex filter fails to match any jobs from folders
Title: Message Title Joshua Olson commented on JENKINS-49305 Re: view-job-filters-plugin regex filter fails to match any jobs from folders Reference info: https://wiki.jenkins.io/display/JENKINS/View+Job+Filters https://wiki.jenkins.io/display/JENKINS/Using+the+View+Job+Filters+Match+Type https://www.cloudbees.com/blog/controlling-what-you-see-view-job-filters-jenkins-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-49305) view-job-filters-plugin regex filter fails to match any jobs from folders
Title: Message Title
Joshua Olson commented on JENKINS-49305
Re: view-job-filters-plugin regex filter fails to match any jobs from folders
Under "Job Filters" have you tried checking the "Recurse in subfolders" box? I'm using the jenkins dsl plugin, and the code below works for me. ### buildMonitorView("Failed-Jobs") { recurse() jobFilters { }}{{ }}{{status { }}{{ }}{{ }}{{matchType(MatchType.INCLUDE_MATCHED) }}{{ }}{{ }}{{status(Status.FAILED) }}{{ }}{{ }}{{status(Status.UNSTABLE) }}{{ }}{ }}{{ }}{{regex { }}{{ }}{{ }}{{matchType(MatchType.EXCLUDE_MATCHED) }}{{ }}{{ }}{{matchValue(RegexMatchValue.NAME) // https://jenkinsci.github.io/job-dsl-plugin/#path/buildMonitorView-jobFilters-regex-matchValue }}{{ }}{{ }}{{regex('.RMQ.') }}{{ }}{ } // jobFilters } // buildMonitorView{{}}
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-27548) Sporadic IOException: Failed to persist config
Title: Message Title
Tomas Norre Mikkelsen updated an issue
Jenkins / JENKINS-27548
Sporadic IOException: Failed to persist config
Change By:
Tomas Norre Mikkelsen
Comment:
Running in jenkins console{code:java}import org.xml.sax.XMLReader;import javax.xml.parsers.SAXParser;import javax.xml.parsers.SAXParserFactory;SAXParserFactory spf = SAXParserFactory.newInstance();SAXParser sp = spf.newSAXParser();XMLReader xr = sp.getXMLReader();{code}I get following:Not Working Instance:{code:java}Result: com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser@7c31937{code}Working Instance:{code:java}Result: com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser@2eed9e14{code}So the value of the setting is the same (besides the Object id) in my two instances where the one is not working.
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-52058) Provide report filename as variable to Groovy parser
Title: Message Title Ulli Hafner commented on JENKINS-52058 Re: Provide report filename as variable to Groovy parser Ok, I fixed it in https://github.com/jenkinsci/warnings-plugin/commit/70f3bf376a51821ac62821406d84944148099d27, needs 30 minutes to 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-53431) Agent attempts reconnect after termination. Leaves Kube pod in failed state
Title: Message Title Matt McKay created an issue Jenkins / JENKINS-53431 Agent attempts reconnect after termination. Leaves Kube pod in failed state Issue Type: Bug Assignee: Carlos Sanchez Attachments: active.txt, node_info, pod_describe, pod_log Components: core, kubernetes-plugin Created: 2018-09-05 16:30 Environment: Operating system - BUILD_ID=10452.109.0 - NAME="Container-Optimized OS" - GOOGLE_CRASH_ID=Lakitu - VERSION_ID=66 - PRETTY_NAME="Container-Optimized OS from Google" - VERSION=66 - GOOGLE_METRICS_PRODUCT_ID=26 - HOME_URL="https://cloud.google.com/compute/docs/containers/vm-image/" master image: jenkins/jenkins:2.121.3 Remoting version: 3.25 Kubernetes 1.10.6-gke.2 JAVA_VERSION=8u181 JENKINS_VERSION=2.121.3 ace-editor:1.1:not-pinned ant:1.8:not-pinned antisamy-markup-formatter:1.5:not-pinned apache-httpcomponents-client-4-api:4.5.5-3.0:not-pinned audit-trail:2.3:not-pinned authentication-tokens:1.3:not-pinned aws-credentials:1.23:not-pinned aws-java-sdk:1.11.341:not-pinned bouncycastle-api:2.17:not-pinned branch-api:2.0.20:not-pinned build-failure-analyzer:1.20.0:not-pinned build-name-setter:1.6.9:not-pinned build-timeout:1.19:not-pinned cloudbees-folder:6.5.1:not-pinned command-launcher:1.2:not-pinned conditional-buildstep:1.3.6:not-pinned credentials:2.1.18:not-pinned credentials-binding:1.16:not-pinned disable-failed-job:1.15:not-pinned display-url-api:2.2.0:not-pinned docker-commons:1.13:not-pinned docker-workflow:1.17:not-pinned durable-task:1.25:not-pinned envinject:2.1.6:not-pinned envinject-api:1.5:not-pinned external-monitor-job:1.7:not-pinned failedJobDeactivator:1.2.1:not-pinned git:3.9.1:not-pinned git-client:2.7.3:not-pinned git-parameter:0.9.4:not-pinned git-server:1.7:not-pinned github:1.29.2:not-pinned github-api:1.92:not-pinned github-branch-source:2.3.6:not-pinned github-oauth:0.29:not-pinned google-container-registry-auth:0.3:not-pinned google-oauth-plugin:0.6:not-pinned gradle:1.29:not-pinned handlebars:1.1.1:not-pinned icon-shim:2.0.3:not-pinned jackson2-api:2.8.11.3:not-pinned javadoc:1.4:not-pinned jdk-tool:1.1:not-pinned job-dsl:1.70:not-pinned jobConfigHistory:2.18:not-pinned jquery:1.12.4-0:not-pinned jquery-detached:1.2.1:not-pinned jsch:0.1.54.2:not-pinned junit:1.24:not-pinned kubernetes:1.12.4:not-pinned kubernetes-credentials:0.3.1:not-pinned ldap:1.20:not-pinned mailer:1.21:not-pinned
[JIRA] (JENKINS-53182) Uncaught TypeError: Cannot read property 'firstChild' of undefined
Title: Message Title Sai Prasad Tirunagari Narayan commented on JENKINS-53182 Re: Uncaught TypeError: Cannot read property 'firstChild' of undefined Hi Oleg Nenashev, Is there some update on this issue. Please help me out a little. Thanks 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-52058) Provide report filename as variable to Groovy parser
Title: Message Title Ulli Hafner commented on JENKINS-52058 Re: Provide report filename as variable to Groovy parser Yes, there seems to be something broken. The save method for the parsers is not called. This should be done automatically... 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-39598) MultiSCM/config.jelly passes descriptors=null
Title: Message Title Jesse Glick commented on JENKINS-39598 Re: MultiSCM/config.jelly passes descriptors=null Jakub Pawlinski that is a known core UI bug. Workaround IIRC (untested): touch $JENKINS_HOME/plugins/multiple-scms.jpi.disabled 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-53429) Attachment attribute has wrong conversion type
Title: Message Title Gaël Reyrol commented on JENKINS-53429 Re: Attachment attribute has wrong conversion type I submitted a pull request to solve this issue : https://github.com/jenkinsci/rocketchatnotifier-plugin/pull/25 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-53305) javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed;
Title: Message Title Steve Arch commented on JENKINS-53305 Re: javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed; It seems to be an issue with the context class loader. By running lots of jobs, I could see that the thread's current class loader was `null` when the problem occurred. I can re-create the issue exactly by running `Thread.currentThread().setContextClassLoader(null);` just before the call to `Transport.send(mimeMessage);` Still investigating... 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-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Brian J Murrell commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should I'm failing to understand how this issue is any less than Critical. It completely invalidates the result of any and every pipeline job run that has even the smallest subset of stage failures. The problem even propagates outside of Jenkins and Blue Ocean as it leads to other plugins such as the Pipeline Githubnotify Step Plugin incorrectly setting FAILURE status on GitHub PR commit statuses set from stages in the pipeline. This issue leads to developers having to waste time and drive up frustration having to hunt through the stages of their pipeline job runs to figure out which stage actually did fail. Additionally, it's really disheartening to see that this issue is only as far as Planned on the Blue Ocean Roadmap. Surely the 116 (or more) votes and 143 (or more) watchers on this issue demonstrates how important it is for a lot of people. Other items on the roadmap that are In Progress even, such as JENKINS-44699 don't have anywhere near as many votes and/or watchers. Is there any ETA, no matter how much of guesstimate it is, available as to how long this issue will take to be 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-53305) javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed;
Title: Message Title
Steve Arch edited a comment on JENKINS-53305
Re: javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed;
It seems to be an issue with the context class loader. By running lots of jobs, I could see that the thread's current class loader was ` {{ null ` }} when the problem occurred.I can re-create the issue exactly by running ` {{ Thread.currentThread().setContextClassLoader(null); ` }} just before the call to ` {{ Transport.send(mimeMessage); ` }} Still investigating...
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-53429) Attachment attribute has wrong conversion type
Title: Message Title Martin Reinhardt started work on JENKINS-53429 Change By: Martin Reinhardt 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-52814) Build status set to failed but not failed immediately
Title: Message Title Jakub Pawlinski commented on JENKINS-52814 Re: Build status set to failed but not failed immediately got it, the stopProcessingIfError parameter does it had to use some old documentation or smth, thanks! xunit testTimeMargin: '3000', thresholdMode: 1, thresholds: [], tools: [MSTest(deleteOutputFiles: true, failIfNotNew: true, pattern: '', skipNoTestFiles: false, stopProcessingIfError: true)] 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-53305) javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed;
Title: Message Title Steve Arch started work on JENKINS-53305 Change By: Steve Arch 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-53305) javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed;
Title: Message Title Steve Arch assigned an issue to Steve Arch Jenkins / JENKINS-53305 javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed; Change By: Steve Arch Assignee: Steve Arch 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-53299) Cloud does not exist: kubernetes
Title: Message Title Kevin Cai updated JENKINS-53299 Jenkins / JENKINS-53299 Cloud does not exist: kubernetes Change By: Kevin Cai Status: Resolved 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-52923) Error Signal Description not displayed in Blue Ocean
Title: Message Title Jakub Pawlinski commented on JENKINS-52923 Re: Error Signal Description not displayed in Blue Ocean feels like something is interfering with propagating the signal message to UI, could not replicate it in simpler cases yet 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-53299) Cloud does not exist: kubernetes
Title: Message Title Kevin Cai commented on JENKINS-53299 Re: Cloud does not exist: kubernetes Maybe a misunderstanding here. Clarify again. Yes, there is a config there in Jenkins settings as in the "cloud" section. However, when I set the cloud name to a different name other than 'kubernetes', e.g. 'myk8scluster', the Kubernetes plugin will panic on pipeline definition use case, error message: "ERROR: Cloud does not exist: kubernetes" is reported. 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-53406) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
Title: Message Title Andrew Bayer closed an issue as Not A Defect Jenkins / JENKINS-53406 org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: Change By: Andrew Bayer Status: Open Closed 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-53406) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
Title: Message Title Andrew Bayer commented on JENKINS-53406 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: The stacktrace is just showing the context in which the compilation ran. The error is definitely a compilation error in your code. 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-49778) If one stage in the pipeline fails, all the states are marked/color with the same status color
Title: Message Title Brian J Murrell commented on JENKINS-49778 Re: If one stage in the pipeline fails, all the states are marked/color with the same status color I upped the Priority here to Critical as this is almost a show-stopper for being able to deploy useful Pipeline jobs with many stages. It's cumbersome on the user to have to hunt through the results of a pipeline job to figure out which stage was actually unstable and which ones were not. I have also changed the Component/s to pipeline since this issue has ramifications outside of Blue Ocean and is not directly related to Blue Ocean in my estimation. Blue Ocean is just the visual representation of the underlying issue with Pipeline jobs setting all stages to unstable when only a subset are actually unstable. For example, when one uses the Pipeline Githubnotify Step Plugin to set commit statuses for each stage on a Github PR, they all get set to FAILURE even though only a subset actually failed. That all said, this is probably a duplicate of JENKINS-39203. 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-53406) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
Title: Message Title huifen weng commented on JENKINS-53406 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: it shows the back trace from Jenkins, will it possible be the Jenkins issue? 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-53430) Capture logged in username and IP Address Audit Trail Plugin
Title: Message Title Trey Owens created an issue Jenkins / JENKINS-53430 Capture logged in username and IP Address Audit Trail Plugin Issue Type: New Feature Assignee: Tomasz Sęk Components: audit-trail-plugin Created: 2018-09-05 15:26 Priority: Minor Reporter: Trey Owens Enhance the audit trail plugin to capture the logged in username and Client IP address for all the action that is configured in audit trail parser. New feature would support capturing the username and client IP address for the "login action" , all the build, configuration related action each requests appended with logged in user and "clientIP address" including the user actions. Add Comment
[JIRA] (JENKINS-49778) If one stage in the pipeline fails, all the states are marked/color with the same status color
Title: Message Title Brian J Murrell updated an issue Jenkins / JENKINS-49778 If one stage in the pipeline fails, all the states are marked/color with the same status color Change By: Brian J Murrell Priority: Minor Critical 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-49778) If one stage in the pipeline fails, all the states are marked/color with the same status color
Title: Message Title Brian J Murrell updated an issue Jenkins / JENKINS-49778 If one stage in the pipeline fails, all the states are marked/color with the same status color Change By: Brian J Murrell Component/s: pipeline Component/s: blueocean-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-53285) Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages
Title: Message Title Baptiste Mathus commented on JENKINS-53285 Re: Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages Dominik Bartholdi thanks a bunch! 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-39598) MultiSCM/config.jelly passes descriptors=null
Title: Message Title Jakub Pawlinski commented on JENKINS-39598 Re: MultiSCM/config.jelly passes descriptors=null Jesse Glick: maybe I'm reading it wrong, but none can be disabled. 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-39598) MultiSCM/config.jelly passes descriptors=null
Title: Message Title Jakub Pawlinski updated an issue Jenkins / JENKINS-39598 MultiSCM/config.jelly passes descriptors=null Change By: Jakub Pawlinski Attachment: image-2018-09-05-16-15-21-458.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-39598) MultiSCM/config.jelly passes descriptors=null
Title: Message Title Jakub Pawlinski updated an issue Jenkins / JENKINS-39598 MultiSCM/config.jelly passes descriptors=null Change By: Jakub Pawlinski Attachment: image-2018-09-05-16-14-09-867.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-39598) MultiSCM/config.jelly passes descriptors=null
Title: Message Title Jakub Pawlinski updated an issue Jenkins / JENKINS-39598 MultiSCM/config.jelly passes descriptors=null Change By: Jakub Pawlinski Attachment: image-2018-09-05-16-14-57-133.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-39598) MultiSCM/config.jelly passes descriptors=null
Title: Message Title Jakub Pawlinski updated an issue Jenkins / JENKINS-39598 MultiSCM/config.jelly passes descriptors=null Change By: Jakub Pawlinski Attachment: image-2018-09-05-16-14-21-879.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-53429) Attachment attribute has wrong conversion type
Title: Message Title Gaël Reyrol created an issue Jenkins / JENKINS-53429 Attachment attribute has wrong conversion type Issue Type: Bug Assignee: Martin Reinhardt Components: rocket-chat-notifier-plugin Created: 2018-09-05 15:05 Environment: Plugin version 1.3.0 Labels: plugin jenkins pipeline Priority: Critical Reporter: Gaël Reyrol Hi, Rocket Chat API expects a boolean value for titleLinkDownload in attachements object. cf : https://rocket.chat/docs/developer-guides/rest-api/chat/postmessage/#attachments-detail When this is true, a download icon appears and clicking this saves the link to file. This breaks the usage of attachements in the workflow pipeline syntax because it needs a string for titleLinkDownload. (MessageAttachment.java#L46) e.g. : rocketSend( attachments: [[ title: 'My repository', color: 'red', text: 'unit test failed :sob:', thumbUrl: '', messageLink: '', collapsed: false, authorName: 'Zevran', authorIcon: '', authorLink: '', titleLink: 'https://github.com', titleLinkDownload: '', imageUrl: '', audioUrl: '', videoUrl: '' ]], channel: 'devops', message: '',
[JIRA] (JENKINS-53262) Folder URL forward slashes are double encoded for Outlook notifications
Title: Message Title
Jason Curtis commented on JENKINS-53262
Re: Folder URL forward slashes are double encoded for Outlook notifications
This Jenkins master is behind Apache with the rewrite module enabled, and rewrite directives configured. The double encoding problem was resolved by adding the NE flag to the RewriteRule directive to prevent mod_rewrite from applying hexcode escaping of special characters in the result of the rewrite. The forward slash ('/') characters are no longer being double encoded. Related links: https://httpd.apache.org/docs/current/mod/mod_rewrite.html#rewriterule https://httpd.apache.org/docs/2.4/rewrite/flags.html#flag_ne http://tkurek.blogspot.com/2013/06/252f-instead-of-2f-in-url-apache.html
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-52058) Provide report filename as variable to Groovy parser
Title: Message Title iostrym edited a comment on JENKINS-52058 Re: Provide report filename as variable to Groovy parser thanks.what do you mean by "if you do not select the aggregate option" : is there anyway an option to activate in my job so that I can run the parser two times ? thanks for the proposal with coma separator but problem is that the same parser is used to parse 2 kind of information. one kind of information are final test result. if I use your proposal, the final test result will be mixed with all other low level test so it will be hard to figure quickly if all is OK. Maybe a prefix to add for the parser so that they could be used several time and have a separate URL ? concerning 5.X parser configuration (groovy script) lost, do you have any idea ? I'm about to rewrite them :( and I wanted to know if there is a chance to refind them and worst, if there is a chance that eveything disapear again... [EDIT] I did a test by re-configuring one parser for 5.X warning plugin. before that I made a backup of jenkins directory. After saving the configuration, I made a diff between current jenkins directory and backuped directory. and there is no differences about 5.X parser configuration. So where should the groovy script of 5.X be stored ? is it a bug of the 5.X version ? in file hudson.plugins.analysis.core.GlobalSettings.xml, there is only this even after adding a new parser : false false false [EDIT]Also there is nothing about 5.X parser in hudson.plugins.warnings.WarningsPublisher.xmlthere are only 4.X parser whereas on top of file there is : I though that it was because my 5.x parser have same name than 4.x parser but I did a trial with a new 5.X parser with a different name and it is the same :no 5.X parser are written in any file of jenkins (I did a complete search) 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
[JIRA] (JENKINS-53420) groovy.lang.MissingPropertyException: No such property: node for class: groovy.lang.Binding
Title: Message Title Jiri Meluzin commented on JENKINS-53420 Re: groovy.lang.MissingPropertyException: No such property: node for class: groovy.lang.Binding thanks for quick fix, works for me 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-52058) Provide report filename as variable to Groovy parser
Title: Message Title iostrym edited a comment on JENKINS-52058 Re: Provide report filename as variable to Groovy parser thanks.what do you mean by "if you do not select the aggregate option" : is there anyway an option to activate in my job so that I can run the parser two times ? thanks for the proposal with coma separator but problem is that the same parser is used to parse 2 kind of information. one kind of information are final test result. if I use your proposal, the final test result will be mixed with all other low level test so it will be hard to figure quickly if all is OK. Maybe a prefix to add for the parser so that they could be used several time and have a separate URL ? concerning 5.X parser configuration (groovy script) lost, do you have any idea ? I'm about to rewrite them :( and I wanted to know if there is a chance to refind them and worst, if there is a chance that eveything disapear again... [EDIT] I did a test by re-configuring one parser for 5.X warning plugin. before that I made a backup of jenkins directory. After saving the configuration, I made a diff between current jenkins directory and backuped directory. and there is no differences about 5.X parser configuration. So where should the groovy script of 5.X be stored ? is it a bug of the 5.X version ? in file hudson.plugins.analysis.core.GlobalSettings.xml, there is only this even after adding a new parser : false false false 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-48007) Client error during trying to send rocket message
Title: Message Title Phlegx Systems edited a comment on JENKINS-48007 Re: Client error during trying to send rocket message [~mreinhardt] I tried now again with newest version 1.3.0 but no luck, with some users I still get: !https://ci.perma.fund/static/65f860f2/images/none.gif|width=1,height=16! Client error - Could not send messagejava.io.IOException: The username and password provided are incorrect. I tried it also on a second jenkins instance in a different company with pretty much the same setup there the same problem appears. here is the full error: https://pastebin.com/L3z1NZm1 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-48007) Client error during trying to send rocket message
Title: Message Title Phlegx Systems commented on JENKINS-48007 Re: Client error during trying to send rocket message Martin Reinhardt I tried now again with newest version 1.3.0 but no luck, with some users I still get: Client error - Could not send message java.io.IOException: The username and password provided are incorrect. I tried it also on a second jenkins instance in a different company with pretty much the same setup there the same problem appears. 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Jesse Glick commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline Sorry, that was a corollary that should have been made explicit: if you are maintaining a persistent mapping of this kind, then the need to include some manner of hash in the workspace path disappears. (You would still need to translate dangerous characters to something more neutral 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-53411) Jacoco Plugin 3.0.3 fails build when no Jacoco exec files are available
Title: Message Title
Adam Crowther edited a comment on JENKINS-53411
Re: Jacoco Plugin 3.0.3 fails build when no Jacoco exec files are available
Ticket JENKINS-49823 (linked) references the same problem in the comments at the bottom. The last comment in that thread is: {panel} [~centic] added a comment - 2018-04-25 17:59 " You are welcome to send a PR for this, the code and the change is not complicated, the plugin is just short on active maintainers... " {panel}
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-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title
Alexey Grigorov edited a comment on JENKINS-46507
Re: Parallel Pipeline random java.lang.InterruptedException
Same here. I'm running a @NonCPS labeled method in library and if fails with this error randomly in the middle{code:java}import jenkins.*import jenkins.model.*import hudson.*import hudson.model.*/* This method will find all jobs and verify their disk usage.Then it will remove job runs to fit quotaThat will help to save disk space*/@NonCPSdef call() {def maxRunSize = 21474836480 //20Gbdef maxJobSize = 42949672960 //40GbJenkins.instance.getAllItems(hudson.model.Job).each{println itdef runs = it.getBuilds()def job = itdef totalSize = 0def jobSizeReached = falseruns.each{def currentRun = itdef currentRunSize = it.getRootDir().directorySize()println itprintln currentRunSizeswitch (currentRunSize) { case {it > maxRunSize} : currentRun.delete() println "deleted " + currentRun + " for having size " + it + " over allowed " + maxRunSize break case {it + totalSize > maxJobSize || jobSizeReached } : jobSizeReached = true currentRun.delete() println "deleted " + currentRun + " for not fitting total " + job + " jobs size " + (totalSize+currentRunSize) +" to max allowed " + maxJobSize break default : totalSize += currentRunSize println 'leaving ' + currentRun + ". current total = " + totalSize break}println '--'}println '=='}}{code}{noformat} <> --[Pipeline] echo[Pipeline] End of Pipelinejava.lang.InterruptedException at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1302) at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:275) at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:111) at org.jenkinsci.plugins.workflow.cps.CpsStepContext.getThreadGroupSynchronously(CpsStepContext.java:248) at org.jenkinsci.plugins.workflow.cps.CpsStepContext.getThreadSynchronously(CpsStepContext.java:237) at org.jenkinsci.plugins.workflow.cps.CpsStepContext.doGet(CpsStepContext.java:298) at org.jenkinsci.plugins.workflow.support.DefaultStepContext.get(DefaultStepContext.java:61) at org.jenkinsci.plugins.workflow.steps.StepDescriptor.checkContextAvailability(StepDescriptor.java:258) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:206) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at org.jenkinsci.plugins.workflow.cps.CpsScript.println(CpsScript.java:221) at sun.reflect.GeneratedMethodAccessor1023.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at
[JIRA] (JENKINS-52058) Provide report filename as variable to Groovy parser
Title: Message Title iostrym commented on JENKINS-52058 Re: Provide report filename as variable to Groovy parser thanks. what do you mean by "if you do not select the aggregate option" : is there anyway an option to activate in my job so that I can run the parser two times ? thanks for the proposal with coma separator but problem is that the same parser is used to parse 2 kind of information. one kind of information are final test result. if I use your proposal, the final test result will be mixed with all other low level test so it will be hard to figure quickly if all is OK. Maybe a prefix to add for the parser so that they could be used several time and have a separate URL ? concerning 5.X parser configuration (groovy script) lost, do you have any idea ? I'm about to rewrite them and I wanted to know if there is a chance to refind them and worst, if there is a chance that eveything disapear again... 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Josh Trow commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline I did read what you wrote, hence my question - nothing in this: Each node (master, agent) should just pay attention to when a workspace is used. (If in core, via WorkspaceList; otherwise, perhaps via WorkspaceListener.) Then record a workspaces.xml, a sibling of workspace/, with a list of records: relative workspace path, Item.fullName, timestamp. seems to say that you are intending to 'clean' or 'modify' or 'change' the paths from what they are today to anything nicer - just that you want to maintain a map of job to workspace for cleanup purposes down the road. 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-52058) Provide report filename as variable to Groovy parser
Title: Message Title Ulli Hafner commented on JENKINS-52058 Re: Provide report filename as variable to Groovy parser java.lang.IllegalStateException: ID testparser is already used by another action In Freestyle Jobs you cannot use the same parser multiple times (if you do not select the aggregate option). You can specify multiple file patterns using a comma separator, this should prevent the problem. The reason is that each result is accessible using the ID of the parser as URL. 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-53420) groovy.lang.MissingPropertyException: No such property: node for class: groovy.lang.Binding
Title: Message Title Andrew Bayer commented on JENKINS-53420 Re: groovy.lang.MissingPropertyException: No such property: node for class: groovy.lang.Binding Released, propagating to the update center now. 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-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Mark Piersak updated an issue Jenkins / JENKINS-33487 Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 We are experiencing the same issue as Jamie Nolan. Same exact plugin version 5.139.2 and Jenkins 2.121.2 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-52058) Provide report filename as variable to Groovy parser
Title: Message Title iostrym edited a comment on JENKINS-52058 Re: Provide report filename as variable to Groovy parser it is a freestyle job. in the meanwhile, I have a big problem, I don't know if it is a jenkins one or a plug-in warning one... During lunch my computer reboot abnormally (windows update process). I did a lot of groovy script configuration yesterday (4.x to 5.x migration + bug correction). configuration was saved in jenkins and used in jobs. And now, (after reboot I think), all 5.X parser are lost :( :( :( is there any chance that they are backuped somewhere in a xml file ? how can this append ? when jenkins configuration is done and saved it is not written directly in a xml file ? [edit] : some other jenkins modification from yesterday are not lost so it seems it is not a jenkins problem. is seems to be a specific 5.X warning plugin problem as I have lost only 5.X warning parser configuration. [edit] : when performing a search in jenkins directory I can see my parser name in "C:\Program Files (x86)\Jenkins\hudson.plugins.warnings.WarningsPublisher.xml" but this file contain only parser configuration for 4.X version. Not those for 5.X version that I have lost. I don't see any other file (except those in job configuration/result) in jenkins directory that contain my parser names. [edit] I have the feeling that the file for configuring 5.X warning plugin parser is hudson.plugins.analysis.core.GlobalSettings.xml but is now a blank file : false false false for your information yesterday I have used "reload configuration from disk" in jenkins administation. but it was working, parser were not deleted after this action. I used it to reload a job that I had modified using its xml file (to copy parser configuration from one job to another) 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
[JIRA] (JENKINS-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title Sam Van Oort commented on JENKINS-46507 Re: Parallel Pipeline random java.lang.InterruptedException Devin Nusbaum Please, could you take a look? 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-53428) Secrets are printed on logs
Title: Message Title Henrique Barcellos created an issue Jenkins / JENKINS-53428 Secrets are printed on logs Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2018-09-05 13:22 Priority: Minor Reporter: Henrique Barcellos Secrets (secretEnvVar) should be (optionally?) masked from job logs. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Jesse Glick commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline in that corresponding XML file you're holding a mapping of what the paths are today to some shorter friendly your name This. Read what I wrote. 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-53427) Failed create agent because of concurrent attempts to schedule a pod
Title: Message Title
Alex Medvedev updated an issue
Jenkins / JENKINS-53427
Failed create agent because of concurrent attempts to schedule a pod
Change By:
Alex Medvedev
The vast majority of the pods have been created properly, but for some of them it looks like there are several concurrent attempts to create a single pod.I've just grep'ed logs on the master for such particular pod which plugin tried to create in several threads (Pod and PodTemplates details skiped): {code:java}../custom/k8s.log:2018-09-03 12:08:12.876+ [id=629145] FINE o.c.j.p.k.PodTemplateBuilder#build: Pod built: Pod(apiVersion=v1, kind=Pod, ...)./custom/k8s.log:2018-09-03 12:08:12.876+ [id=629145] FINE o.c.j.p.k.KubernetesLauncher#launch: Creating Pod: test-0ghpx in namespace dev./custom/k8s.log:2018-09-03 12:08:12.969+ [id=629145] INFO o.c.j.p.k.KubernetesLauncher#launch: Created Pod: test-0ghpx in namespace dev./custom/k8s.log:2018-09-03 12:08:12.970+ [id=629145] INFO o.c.j.p.k.KubernetesLauncher#launch: Waiting for Pod to be scheduled (0/100): test-0ghpx./custom/k8s.log:2018-09-03 12:08:14.143+ [id=640057] FINE o.c.j.p.k.PodTemplateBuilder#build: Pod built: Pod(...)./custom/k8s.log:2018-09-03 12:08:14.144+ [id=640057] FINE o.c.j.p.k.KubernetesLauncher#launch: Creating Pod: test-0ghpx in namespace dev./custom/k8s.log:2018-09-03 12:08:14.214+ [id=640057] WARNING o.c.j.p.k.KubernetesLauncher#launch: Error in provisioning; agent=KubernetesSlave name: test-0ghpx, template=PodTemplate{...}./custom/k8s.log:io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: POST at: https://k8s.local:6443/api/v1/namespaces/dev/pods. Message: pods "test-0ghpx" already exists. Received status: Status(apiVersion=v1, code=409, details=StatusDetails(causes=[], group=null, kind=pods, name=test-0ghpx, retryAfterSeconds=null, uid=null, additionalProperties={}), kind=Status, message=pods "test-0ghpx" already exists, metadata=ListMeta(resourceVersion=null, selfLink=null, additionalProperties={}), reason=AlreadyExists, status=Failure, additionalProperties={})../custom/k8s.log:2018-09-03 12:08:14.214+ [id=640057] FINER o.c.j.p.k.KubernetesLauncher#launch: Removing Jenkins node: test-0ghpx./custom/k8s.log:2018-09-03 12:08:14.215+ [id=640057] INFO o.c.j.p.k.KubernetesSlave#_terminate: Terminating Kubernetes instance for agent test-0ghpx./custom/k8s.log:2018-09-03 12:08:14.289+ [id=640057] INFO o.c.j.p.k.KubernetesSlave#_terminate: Terminated Kubernetes instance for agent dev/test-0ghpx./custom/k8s.log:2018-09-03 12:08:14.290+ [id=640057] INFO o.c.j.p.k.KubernetesSlave#_terminate: Disconnected computer test-0ghpx./custom/k8s.log:2018-09-03 12:08:14.542+ [id=640056] FINE o.c.j.p.k.PodTemplateBuilder#build: Pod built: Pod(...)./custom/k8s.log:2018-09-03 12:08:14.543+ [id=640056] FINE o.c.j.p.k.KubernetesLauncher#launch: Creating Pod: test-0ghpx in namespace dev./custom/k8s.log:2018-09-03 12:08:14.615+ [id=640056] INFO o.c.j.p.k.KubernetesLauncher#launch: Created Pod: test-0ghpx
[JIRA] (JENKINS-53427) Failed create agent because of concurrent attempts to schedule a pod
Title: Message Title
Alex Medvedev updated an issue
Jenkins / JENKINS-53427
Failed create agent because of concurrent attempts to schedule a pod
Change By:
Alex Medvedev
The vast majority of the pods have been created properly, but for some of them it looks like there are several concurrent attempts to create a single pod.I've just grep'ed logs on the master for such particular pod which plugin tried to create in several threads (Pod and PodTemplates details skiped): {code:java}../custom/k8s.log:2018-09-03 12:08:12.876+ [id=629145] FINE o.c.j.p.k.PodTemplateBuilder#build: Pod built: Pod(apiVersion=v1, kind=Pod, ...)./custom/k8s.log:2018-09-03 12:08:12.876+ [id=629145] FINE o.c.j.p.k.KubernetesLauncher#launch: Creating Pod: test-0ghpx in namespace dev./custom/k8s.log:2018-09-03 12:08:12.969+ [id=629145] INFO o.c.j.p.k.KubernetesLauncher#launch: Created Pod: test-0ghpx in namespace dev./custom/k8s.log:2018-09-03 12:08:12.970+ [id=629145] INFO o.c.j.p.k.KubernetesLauncher#launch: Waiting for Pod to be scheduled (0/100): test-0ghpx./custom/k8s.log:2018-09-03 12:08:14.143+ [id=640057] FINE o.c.j.p.k.PodTemplateBuilder#build: Pod built: Pod(...)./custom/k8s.log:2018-09-03 12:08:14.144+ [id=640057] FINE o.c.j.p.k.KubernetesLauncher#launch: Creating Pod: test-0ghpx in namespace dev./custom/k8s.log:2018-09-03 12:08:14.214+ [id=640057] WARNING o.c.j.p.k.KubernetesLauncher#launch: Error in provisioning; agent=KubernetesSlave name: test-0ghpx, template=PodTemplate{...}./custom/k8s.log:io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: POST at: https://k8s.local:6443/api/v1/namespaces/dev/pods. Message: pods "test-0ghpx" already exists. Received status: Status(apiVersion=v1, code=409, details=StatusDetails(causes=[], group=null, kind=pods, name=test-0ghpx, retryAfterSeconds=null, uid=null, additionalProperties={}), kind=Status, message=pods "test-0ghpx" already exists, metadata=ListMeta(resourceVersion=null, selfLink=null, additionalProperties={}), reason=AlreadyExists, status=Failure, additionalProperties={})../custom/k8s.log:2018-09-03 12:08:14.214+ [id=640057] FINER o.c.j.p.k.KubernetesLauncher#launch: Removing Jenkins node: test-0ghpx./custom/k8s.log:2018-09-03 12:08:14.215+ [id=640057] INFO o.c.j.p.k.KubernetesSlave#_terminate: Terminating Kubernetes instance for agent test-0ghpx./custom/k8s.log:2018-09-03 12:08:14.289+ [id=640057] INFO o.c.j.p.k.KubernetesSlave#_terminate: Terminated Kubernetes instance for agent dev/test-0ghpx./custom/k8s.log:2018-09-03 12:08:14.290+ [id=640057] INFO o.c.j.p.k.KubernetesSlave#_terminate: Disconnected computer test-0ghpx./custom/k8s.log:2018-09-03 12:08:14.542+ [id=640056] FINE o.c.j.p.k.PodTemplateBuilder#build: Pod built: Pod(...)./custom/k8s.log:2018-09-03 12:08:14.543+ [id=640056] FINE o.c.j.p.k.KubernetesLauncher#launch: Creating Pod: test-0ghpx in namespace dev./custom/k8s.log:2018-09-03 12:08:14.615+ [id=640056] INFO o.c.j.p.k.KubernetesLauncher#launch: Created Pod: test-0ghpx
[JIRA] (JENKINS-53427) Failed create agent because of concurrent attempts to schedule a pod
Title: Message Title
Alex Medvedev updated an issue
Jenkins / JENKINS-53427
Failed create agent because of concurrent attempts to schedule a pod
Change By:
Alex Medvedev
The vast majority of the pods have been created properly, but for some of them it looks like there are several concurrent attempts to create a single pod.I've just grep'ed logs on the master for such particular pod which plugin tried to create in several threads (Pod and PodTemplates details skiped): {code:java}../custom/k8s.log:2018-09-03 12:08:12.876+ [id=629145] FINE o.c.j.p.k.PodTemplateBuilder#build: Pod built: Pod(apiVersion=v1, kind=Pod, ...)./custom/k8s.log:2018-09-03 12:08:12.876+ [id=629145] FINE o.c.j.p.k.KubernetesLauncher#launch: Creating Pod: test-0ghpx in namespace dev./custom/k8s.log:2018-09-03 12:08:12.969+ [id=629145] INFO o.c.j.p.k.KubernetesLauncher#launch: Created Pod: test-0ghpx in namespace dev./custom/k8s.log:2018-09-03 12:08:12.970+ [id=629145] INFO o.c.j.p.k.KubernetesLauncher#launch: Waiting for Pod to be scheduled (0/100): test-0ghpx./custom/k8s.log:2018-09-03 12:08:14.143+ [id=640057] FINE o.c.j.p.k.PodTemplateBuilder#build: Pod built: Pod(...)./custom/k8s.log:2018-09-03 12:08:14.144+ [id=640057] FINE o.c.j.p.k.KubernetesLauncher#launch: Creating Pod: test-0ghpx in namespace dev./custom/k8s.log:2018-09-03 12:08:14.214+ [id=640057] WARNING o.c.j.p.k.KubernetesLauncher#launch: Error in provisioning; agent=KubernetesSlave name: test-0ghpx, template=PodTemplate{...}./custom/k8s.log:io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: POST at: https://k8s.local:6443/api/v1/namespaces/dev/pods. Message: pods "test-0ghpx" already exists. Received status: Status(apiVersion=v1, code=409, details=StatusDetails(causes=[], group=null, kind=pods, name=test-0ghpx, retryAfterSeconds=null, uid=null, additionalProperties={}), kind=Status, message=pods "test-0ghpx" already exists, metadata=ListMeta(resourceVersion=null, selfLink=null, additionalProperties={}), reason=AlreadyExists, status=Failure, additionalProperties={})../custom/k8s.log:2018-09-03 12:08:14.214+ [id=640057] FINER o.c.j.p.k.KubernetesLauncher#launch: Removing Jenkins node: test-0ghpx./custom/k8s.log:2018-09-03 12:08:14.215+ [id=640057] INFO o.c.j.p.k.KubernetesSlave#_terminate: Terminating Kubernetes instance for agent test-0ghpx./custom/k8s.log:2018-09-03 12:08:14.289+ [id=640057] INFO o.c.j.p.k.KubernetesSlave#_terminate: Terminated Kubernetes instance for agent dev/test-0ghpx./custom/k8s.log:2018-09-03 12:08:14.290+ [id=640057] INFO o.c.j.p.k.KubernetesSlave#_terminate: Disconnected computer test-0ghpx./custom/k8s.log:2018-09-03 12:08:14.542+ [id=640056] FINE o.c.j.p.k.PodTemplateBuilder#build: Pod built: Pod(...)./custom/k8s.log:2018-09-03 12:08:14.543+ [id=640056] FINE o.c.j.p.k.KubernetesLauncher#launch: Creating Pod: test-0ghpx in namespace dev./custom/k8s.log:2018-09-03 12:08:14.615+ [id=640056] INFO o.c.j.p.k.KubernetesLauncher#launch: Created Pod: test-0ghpx
[JIRA] (JENKINS-53420) groovy.lang.MissingPropertyException: No such property: node for class: groovy.lang.Binding
Title: Message Title Andrew Bayer updated JENKINS-53420 Merged, releasing 1.46 as we speak. Again, I'm very sorry for introducing this! Jenkins / JENKINS-53420 groovy.lang.MissingPropertyException: No such property: node for class: groovy.lang.Binding Change By: Andrew Bayer Status: In Review Resolved Resolution: Fixed Released As: script-security 1.46 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-52058) Provide report filename as variable to Groovy parser
Title: Message Title iostrym edited a comment on JENKINS-52058 Re: Provide report filename as variable to Groovy parser it is a freestyle job. in the meanwhile, I have a big problem, I don't know if it is a jenkins one or a plug-in warning one... During lunch my computer reboot abnormally (windows update process). I did a lot of groovy script configuration yesterday (4.x to 5.x migration + bug correction). configuration was saved in jenkins and used in jobs. And now, (after reboot I think), all 5.X parser are lost :( :( :( is there any chance that they are backuped somewhere in a xml file ? how can this append ? when jenkins configuration is done and saved it is not written directly in a xml file ? [edit] : some other jenkins modification from yesterday are not lost so it seems it is not a jenkins problem. is seems to be a specific 5.X warning plugin problem as I have lost only 5.X warning parser configuration. [edit] : when performing a search in jenkins directory I can see my parser name in "C:\Program Files (x86)\Jenkins\hudson.plugins.warnings.WarningsPublisher.xml" but this file contain only parser configuration for 4.X version. Not those for 5.X version that I have lost. I don't see any other file (except those in job configuration/result) in jenkins directory that contain my parser names. 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Josh Trow commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline Unless in that corresponding XML file you're holding a mapping of what the paths are today to some shorter friendly your name that is then used in actuality I'm still not sure how that resolves the issue of the workspace having a path that has a 'mangled' name. I agree that having better logic around work spaces and the ability to clean them up automatically is a good thing but I don't think it's directly related to this nor will one automatically solve the other (depending on the implementation it could) 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Jesse Glick commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline This is just beating around the bush. See JENKINS-2111 for the proper permanent solution to handling inelastic (“dumb”) build agents. 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-47722) "Local Proxy" textbox tooltip: the text slides outside of the visible area
Title: Message Title Daniel Gront updated JENKINS-47722 Jenkins / JENKINS-47722 "Local Proxy" textbox tooltip: the text slides outside of the visible area Change By: Daniel Gront Status: In Review Closed 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-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title Toby Broyles commented on JENKINS-46507 Re: Parallel Pipeline random java.lang.InterruptedException We are seeing this error quite often lately. Is there anything I can do to help troubleshoot? 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-51055) Rebranding - HPE still appears in a few places in Job Configuration
Title: Message Title Daniel Gront closed an issue as Fixed Jenkins / JENKINS-51055 Rebranding - HPE still appears in a few places in Job Configuration Change By: Daniel Gront Status: Open Closed 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-51293) PCBuild pipeline gives java.lang.ClassCastException error
Title: Message Title Daniel Gront closed an issue as Fixed Jenkins / JENKINS-51293 PCBuild pipeline gives java.lang.ClassCastException error Change By: Daniel Gront Status: Open Closed 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-51631) Jenkins Plugin micro focus UI rebranding
Title: Message Title Daniel Gront closed an issue as Fixed Jenkins / JENKINS-51631 Jenkins Plugin micro focus UI rebranding Change By: Daniel Gront Status: Open Closed 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-51631) Jenkins Plugin micro focus UI rebranding
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-51631 Jenkins Plugin micro focus UI rebranding Change By: Daniel Gront Summary: Jenkins Plugin micro focus UI rebranding 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-45701) Plot plugin will not update trend graph when PC job is configured to run on slave
Title: Message Title Daniel Gront updated JENKINS-45701 Jenkins / JENKINS-45701 Plot plugin will not update trend graph when PC job is configured to run on slave Change By: Daniel Gront Status: In Review Closed 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-53370) Failed to count the # of live instances on Kubernetes - NullPointerException
Title: Message Title Pablo Ramirez commented on JENKINS-53370 Re: Failed to count the # of live instances on Kubernetes - NullPointerException Works now! Thanks Carlos. 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-52960) When running a job in distributed node, logs reports errors related to creation of csv files in workspace
Title: Message Title Daniel Gront updated JENKINS-52960 Jenkins / JENKINS-52960 When running a job in distributed node, logs reports errors related to creation of csv files in workspace Change By: Daniel Gront Status: In Review 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-52960) When running a job in distributed node, logs reports errors related to creation of csv files in workspace
Title: Message Title Daniel Gront updated JENKINS-52960 Will be included in beta version 5.5.1 Jenkins / JENKINS-52960 When running a job in distributed node, logs reports errors related to creation of csv files in workspace Change By: Daniel Gront Status: In Progress Fixed but Unreleased 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-53005) com.thoughtworks.xstream.mapper.CannotResolveClassException: html
Title: Message Title Daniel Gront closed an issue as Fixed Jenkins / JENKINS-53005 com.thoughtworks.xstream.mapper.CannotResolveClassException: html Change By: Daniel Gront Status: In Progress Closed 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.
