[JIRA] (JENKINS-6334) Support for displaying changesets in submodule updates
Title: Message Title Carlos Garcia commented on JENKINS-6334 Re: Support for displaying changesets in submodule updates This is I have currently installed, after building the sbm branch (yesterday). 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-6334) Support for displaying changesets in submodule updates
Title: Message Title Carlos Garcia updated an issue Jenkins / JENKINS-6334 Support for displaying changesets in submodule updates Change By: Carlos Garcia Attachment: git-plugins.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-6334) Support for displaying changesets in submodule updates
Title: Message Title John Kuzniar commented on JENKINS-6334 Re: Support for displaying changesets in submodule updates Carlos, Have you tried his recent 4.0 beta build on the sbm branch? I was using the 3.6 version, but now need at least 3.9. 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-6334) Support for displaying changesets in submodule updates
Title: Message Title Carlos Garcia commented on JENKINS-6334 Re: Support for displaying changesets in submodule updates John, I used Yakov's plugins building them from 'sbm' branch. They worked fine so far. I had minor issues during building, "findbugs" complained about a possible Null pointer dereference, and a test did not pass in git-client plugin. Despite that, for now, all is working normally, so unless a major problem arises, I will stick to Yakov's 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-6334) Support for displaying changesets in submodule updates
Title: Message Title John Kuzniar commented on JENKINS-6334 Re: Support for displaying changesets in submodule updates Yakov, could you deliver your solution? I built your version (worked well, there were a few random java failures), but we need to update our git and git client plugins. 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-48525) Perforce plugin doesn't sync
Title: Message Title William Brode commented on JENKINS-48525 Re: Perforce plugin doesn't sync Tom Sackett - I think we found that the issue was partially related to proxy or edge servers and how they were set up with regards to parallel syncing. So you could look at your p4 server configuration to get it to work properly. Perhaps you could reply here if you figure out the steps that work 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-20151) Allow customizing date format in changes token
Title: Message Title Alex Earl commented on JENKINS-20151 Re: Allow customizing date format in changes token Please don't hijack an issue with a question. You can ask questions on the jenkins-users mailing list. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52171) Gitlab plugin uncompatible with Jira plugin in pipeline
Title: Message Title Owen Mehegan commented on JENKINS-52171 Re: Gitlab plugin uncompatible with Jira plugin in pipeline Dave Nichols yep, same problem, class conflict because of the jersey-core library. 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-53360) Add ability to send list of data to InfluxDB
Title: Message Title Pavel Vasilevich created an issue Jenkins / JENKINS-53360 Add ability to send list of data to InfluxDB Issue Type: Improvement Assignee: Aleksi Simell Components: influxdb-plugin Created: 2018-08-31 02:07 Environment: Jenkins 2.121.1 Priority: Minor Reporter: Pavel Vasilevich Main idea: get information about different stages in pipeline reported to InfluxDB. It will be good if there will be automatic PointGenerator that collects information about stages in pipeline build and then prepares list of BatchPoints: pipeline_data: project_name build_number stage time pipeline1 14 init 3
[JIRA] (JENKINS-51640) Optimization in query used to get current revision info
Title: Message Title José Lamas resolved as Fixed Fixed on version 1.2 Jenkins / JENKINS-51640 Optimization in query used to get current revision info Change By: José Lamas Status: In Progress Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/genexus-plugin/releases/tag/genexus-1.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-52983) Missing root URL in the generated link to build while using groovy-html.template
Title: Message Title Gregory Fong commented on JENKINS-52983 Re: Missing root URL in the generated link to build while using groovy-html.template I am hitting this issue with the Stash Pullrequest Builder plugin after we upgraded to 2.140, and we do have a jenkins.model.JenkinsLocationConfiguration.xml file. Exploring a bit, this plugin uses this code in order to get the URL (see https://github.com/nemccarthy/stash-pullrequest-builder-plugin/blob/master/src/main/java/stashpullrequestbuilder/stashpullrequestbuilder/StashBuilds.java#L52): JenkinsLocationConfiguration globalConfig = new JenkinsLocationConfiguration(); String rootUrl = globalConfig.getUrl(); However, I confirmed using script console that this returns null in 2.140: JenkinsLocationConfiguration globalConfig = new JenkinsLocationConfiguration(); println(globalConfig.getUrl()); On the other hand, running the following on script console returns the configured URL as expected: config = JenkinsLocationConfiguration.get(); println(config.getUrl()) It looks like the commit that caused this difference in behavior is: https://github.com/jenkinsci/jenkins/commit/c3988aae8ad66fde529830e799fe3d49cd241ebb#diff-1439884ddd002c6ca6463d9657412b15 . It seems like constructing a new JenkinsLocationConfiguration no longer invokes the load() method automatically, and I confirmed that calling it manually does result in the configured URL being returned as expected: JenkinsLocationConfiguration globalConfig = new JenkinsLocationConfiguration(); globalConfig.load() println(globalConfig.getUrl()); I can't say that what plugins are doing is right or wrong, but the new behavior does break some plugins. If this is a policy change for plugins, then I can open a bug ticket or submit a pull request for this particular plugin. But it'd be good to get some feedback from someone who understands the problem better to answer this question: Is this an problem with the plugin's expectations, or is this a Jenkins regression?
[JIRA] (JENKINS-53112) Filter the "Known instances" by "active in the last seven days"
Title: Message Title R. Tyler Croy commented on JENKINS-53112 Re: Filter the "Known instances" by "active in the last seven days" I believe we need to change the backend to modify the updatedAt field on instances for this to work 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-53112) Filter the "Known instances" by "active in the last seven days"
Title: Message Title R. Tyler Croy stopped work on JENKINS-53112 Change By: R. Tyler Croy Status: In Progress Open 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-53317) Update level number should be displayed on the backend status page
Title: Message Title R. Tyler Croy resolved as Fixed Will be in next backend deployment Jenkins / JENKINS-53317 Update level number should be displayed on the backend status page Change By: R. Tyler Croy Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53359) job-dsl has deprecated concurrentBuild() on pipeline jobs
Title: Message Title Joshua Hoblitt created an issue Jenkins / JENKINS-53359 job-dsl has deprecated concurrentBuild() on pipeline jobs Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2018-08-30 22:26 Priority: Major Reporter: Joshua Hoblitt Per https://github.com/jenkinsci/job-dsl-plugin/wiki/Migration#migrating-to-170, and warnings in the console on seed jobs, concurrentBuild() is deprecated for pipeline jobs. Is this is error? concurrent builds can certainly be enabled/disabled on pipeline jobs. Add Comment
[JIRA] (JENKINS-51762) NullPointerException in some jobs when listing last changes
Title: Message Title Rafael Pestano commented on JENKINS-51762 Re: NullPointerException in some jobs when listing last changes Please try with attached SNAPSHOT: last-changes-2.6.3-SNAPSHOT.hpi 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-51762) NullPointerException in some jobs when listing last changes
Title: Message Title Rafael Pestano updated an issue Jenkins / JENKINS-51762 NullPointerException in some jobs when listing last changes Change By: Rafael Pestano Attachment: last-changes-2.6.3-SNAPSHOT.hpi 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-53358) Pipeline Still Persists Run Regularly Even in Performance-Optimized Mode
Title: Message Title Sam Van Oort commented on JENKINS-53358 Re: Pipeline Still Persists Run Regularly Even in Performance-Optimized Mode Was previously blocked due to the JENKINS-50199 fix due to the durability implications, but that is now resolved! 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-53358) Pipeline Still Persists Run Regularly Even in Performance-Optimized Mode
Title: Message Title Sam Van Oort started work on JENKINS-53358 Change By: Sam Van Oort 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-53358) Pipeline Still Persists Run Regularly Even in Performance-Optimized Mode
Title: Message Title Sam Van Oort updated JENKINS-53358 Jenkins / JENKINS-53358 Pipeline Still Persists Run Regularly Even in Performance-Optimized Mode Change By: Sam Van Oort 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-53358) Pipeline Still Persists Run Regularly Even in Performance-Optimized Mode
Title: Message Title Sam Van Oort created an issue Jenkins / JENKINS-53358 Pipeline Still Persists Run Regularly Even in Performance-Optimized Mode Issue Type: Bug Assignee: Unassigned Components: workflow-cps-plugin Created: 2018-08-30 22:01 Labels: performance pipeline durability Priority: Minor Reporter: Sam Van Oort In "performance-optimized" mode, Pipelines should only be persisting the Run a couple times (mostly at the start, finish, and when pausing or restarting) – that's part of what "optimized" means. Instead a notify call is causing this to happen multiple times. Add Comment
[JIRA] (JENKINS-53307) Transform anonymous classes sent over remoting into non anonymous classes
Title: Message Title Jesse Glick resolved as Duplicate In fact with a little digging you can see that this was already fixed and the fix released in 3.0.0-beta4. Jenkins / JENKINS-53307 Transform anonymous classes sent over remoting into non anonymous classes Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate 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-52948) Attempt to (de-)serialize anonymous class in gitclient
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-52948 Attempt to (de-)serialize anonymous class in gitclient Change By: Jesse Glick Labels: JEP-200 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53307) Transform anonymous classes sent over remoting into non anonymous classes
Title: Message Title Jesse Glick commented on JENKINS-53307 Re: Transform anonymous classes sent over remoting into non anonymous classes Let me see: git-client-plugin$ git pull && mvn compile && javap -classpath target/classes -c -private -l 'org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1' … Error: class not found: org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1 Baptiste Mathus are you sure you are running the most recent version of git-client? I just started Evergreen and it claims to be running 2.7.0. According to the wiki the current version is 3.0.0-beta5. It is not very useful to report bugs to plugin authors about old versions, in this case from December. 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-48463) Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0
Title: Message Title Ioannis Moutsatsos commented on JENKINS-48463 Re: Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0 You must note that most editors that work fine with XML 1.0 can't parse XML 1.1. After more than a decade successfully using the free MS utility XML Notepad for all XML tasks I may have to look for another editor. How much of a demand there was for this change? 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-48463) Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-48463 Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0 Change By: Ioannis Moutsatsos Attachment: image-2018-08-30-17-20-59-194.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-53307) Transform anonymous classes sent over remoting into non anonymous classes
Title: Message Title Mark Waite commented on JENKINS-53307 Re: Transform anonymous classes sent over remoting into non anonymous classes All my attempts to find those anonymous inner classes with either Netbeans or IntelliJ have failed. I feel stupid that I can't find them inside the source files. I see the evidence in the target/classes directory that anonymous inner classes are being generated, but I just don't see them in the implementation. Any pointers to techniques to identify them would be much appreciated (preferably without mocking my ineptitude). I've tried finding them with Netbeans. I've tried finding them with IntelliJ. I've tried using a Java decompiler. 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-53247) Support JCasC in Config File Provider Plugin
Title: Message Title Stefan Rempfer edited a comment on JENKINS-53247 Re: Support JCasC in Config File Provider Plugin https://wiki.jenkins.io/display/JENKINS/Choosing+Jenkins+version+to+build+against https://github.com/jenkinsci/plugin-pom#usage 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-53247) Support JCasC in Config File Provider Plugin
Title: Message Title Stefan Rempfer commented on JENKINS-53247 Re: Support JCasC in Config File Provider Plugin https://wiki.jenkins.io/display/JENKINS/Choosing+Jenkins+version+to+build+against 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-49177) Bitbucket Plugin - HTTPS URI not matched when path does not start with "/scm"
Title: Message Title Dmitry Bigunyak commented on JENKINS-49177 Re: Bitbucket Plugin - HTTPS URI not matched when path does not start with "/scm" Any chance this ticket gets someone's attention? 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-53227) evergreen-client should do integrity checking on downloads and gracefully handle errors
Title: Message Title R. Tyler Croy updated JENKINS-53227 Jenkins / JENKINS-53227 evergreen-client should do integrity checking on downloads and gracefully handle errors Change By: R. Tyler Croy Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53309) Flavor should be pushed into Sentry
Title: Message Title R. Tyler Croy updated JENKINS-53309 Will be deployed with the next prod deploy Jenkins / JENKINS-53309 Flavor should be pushed into Sentry Change By: R. Tyler Croy Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52058) Provide report filename as variable to Groovy parser
Title: Message Title Ulli Hafner updated JENKINS-52058 See https://github.com/jenkinsci/warnings-plugin/tree/5.0 Jenkins / JENKINS-52058 Provide report filename as variable to Groovy parser Change By: Ulli Hafner Status: Open 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-53307) Transform anonymous classes sent over remoting into non anonymous classes
Title: Message Title Jesse Glick commented on JENKINS-53307 Re: Transform anonymous classes sent over remoting into non anonymous classes Note: from the NetBeans IDE you can just Ctrl-Alt-Shift-A and if possible make sure the result is static. 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-53281) Convert com.nirima.jenkins.plugins.docker.DockerImagePullStrategy$2 to non anymous class
Title: Message Title Baptiste Mathus commented on JENKINS-53281 Re: Convert com.nirima.jenkins.plugins.docker.DockerImagePullStrategy$2 to non anymous class Right, hadn't checked that DockerImagePullStrategy is actually an enum. So I just checked the other similar one JENKINS-53307 I had filed for the Git plugin, and there it seems like a fix would be needed. 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-53172) parallel-test-executor-plugin should check that the job is not running
Title: Message Title Andrew Bayer updated JENKINS-53172 Merged! Jenkins / JENKINS-53172 parallel-test-executor-plugin should check that the job is not running Change By: Andrew Bayer Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-791) slave log should include timestamp
Title: Message Title Josiah Eubank commented on JENKINS-791 Re: slave log should include timestamp Has this regressed or purposely removed? 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-53295) error log should be collapsed by default too
Title: Message Title Naresh Rayapati commented on JENKINS-53295 Re: error log should be collapsed by default too We also have few steps implementing retry on these long running shell scrips, with retryCount of 3 to 4 times, causing the same 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-53317) Update level number should be displayed on the backend status page
Title: Message Title R. Tyler Croy started work on JENKINS-53317 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-53112) Filter the "Known instances" by "active in the last seven days"
Title: Message Title R. Tyler Croy started work on JENKINS-53112 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-53323) Only include node_modules required for runtime in the container
Title: Message Title R. Tyler Croy updated JENKINS-53323 Jenkins / JENKINS-53323 Only include node_modules required for runtime in the container Change By: R. Tyler Croy 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-53309) Flavor should be pushed into Sentry
Title: Message Title R. Tyler Croy updated JENKINS-53309 Jenkins / JENKINS-53309 Flavor should be pushed into Sentry Change By: R. Tyler Croy 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-53357) Error logs will fill up production disk indefinitely
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-53357 Error logs will fill up production disk indefinitely Issue Type: Bug Assignee: Baptiste Mathus Components: evergreen Created: 2018-08-30 18:27 Priority: Minor Reporter: R. Tyler Croy Based on my reading of this code in the src/services/errorTelemetry/errorTelemetry.class.js, all client-sent errors will fill up a single file on disk indefinitely. I don't understand the need for this file in anything other than a testing scenario. Add Comment
[JIRA] (JENKINS-53327) Simple Theme Plugin v0.5 - CSS rule omitted by Jelly
Title: Message Title Philip Steiner commented on JENKINS-53327 Re: Simple Theme Plugin v0.5 - CSS rule omitted by Jelly I can confirm that the fix in v0.5.1 corrected the problem I reported - thanks for the speedy resolution! 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-53309) Flavor should be pushed into Sentry
Title: Message Title R. Tyler Croy started work on JENKINS-53309 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-53233) Unable to run Performance Test in Jenkins - executeRequest exception: Operation failed. Error code: 1001
Title: Message Title Mark Laurora commented on JENKINS-53233 Re: Unable to run Performance Test in Jenkins - executeRequest exception: Operation failed. Error code: 1001 Hello Experts, Good day! Can someone help us with this please? We are currently doing a Proof of Concept for the integration of HPE Performance Center and Jenkins and unable to move on. I hope someone can help us with this please? Your response is highly appreciated. Thanks in Advance! 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-33761) Ability to disable Pipeline durability and "resume" build.
Title: Message Title Russell Gallop commented on JENKINS-33761 Re: Ability to disable Pipeline durability and "resume" build. We have seen the same thing. Resume definitely disabled and still causing hangs. 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-48798) Error when using HP ALM Quality in a Post Build step
Title: Message Title Abdel Akkoub reopened an issue Hello Roy, I have the trial version of ALM 12.5 on my machine. I am running Maven project on Jenkins. I am attempting to send the results from the Maven project build to ALM test lab folder, I am able to successfully test my ALM connection when I add ALM server URL and credentials in the HP Quality Center Integration settings in system configurations in Jenkins. However, When I attempt to configure the HP Quality Center Integration settings from Post Build Actions for my Maven project, the domain dropdown appears blank and shows the following error: A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace javax.ws.rs.NotFoundException: HTTP 404 Not Found at org.glassfish.jersey.client.JerseyInvocation.convertToException(JerseyInvocation.java:956) at org.glassfish.jersey.client.JerseyInvocation.translate(JerseyInvocation.java:855) at org.glassfish.jersey.client.JerseyInvocation.access$600(JerseyInvocation.java:91) at org.glassfish.jersey.client.JerseyInvocation$3.call(JerseyInvocation.java:705) at org.glassfish.jersey.internal.Errors.process(Errors.java:315) at org.glassfish.jersey.internal.Errors.process(Errors.java:297) at org.glassfish.jersey.internal.Errors.process(Errors.java:228) at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:424) at org.glassfish.jersey.client.JerseyInvocation.invoke(JerseyInvocation.java:701) at org.glassfish.jersey.client.JerseyInvocation$Builder.method(JerseyInvocation.java:417) at org.glassfish.jersey.client.JerseyInvocation$Builder.get(JerseyInvocation.java:313) at org.jenkinsci.plugins.qc.client.QualityCenter.domains(QualityCenter.java:34) at org.jenkinsci.plugins.qc.QualityCenterIntegrationRecorder$QualityCenterIntegrationDescriptor.doFillDomainItems(QualityCenterIntegrationRecorder.java:473) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:734) Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:784) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:864) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:734) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:864) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:734) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:864) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:741) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at
[JIRA] (JENKINS-38893) Active Choice Reactive Reference parameter value rendered as File Selector not cascaded
Title: Message Title Ioannis Moutsatsos commented on JENKINS-38893 Re: Active Choice Reactive Reference parameter value rendered as File Selector not cascaded Changed the severity, as this is directly affecting the expected behavior of the AC control 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-38893) Active Choice Reactive Reference parameter value rendered as File Selector not cascaded
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-38893 Active Choice Reactive Reference parameter value rendered as File Selector not cascaded Change By: Ioannis Moutsatsos Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53247) Support JCasC in Config File Provider Plugin
Title: Message Title
Stefan Rempfer edited a comment on JENKINS-53247
Re: Support JCasC in Config File Provider Plugin
Currently the JCasC plugin couldn't used as optional dependency because of a Java7/ Java 8 clash: {code :java }[INFO] --- maven-enforcer-plugin:1.4.1:enforce (display-info) @ config-file-provider ---[INFO] Restricted to JDK 1.7 yet io.jenkins:configuration-as-code:jar:1.0-rc2:compile contains io/jenkins/plugins/casc/CasCGlobalConfig.class targeted to JDK 1.8[WARNING] Rule 2: org.apache.maven.plugins.enforcer.EnforceBytecodeVersion failed with message:Found Banned Dependency: io.jenkins:configuration-as-code:jar:1.0-rc2Use 'mvn dependency:tree' to locate the source of the banned dependencies. {code} So only the setter for "org.jenkinsci.plugins.configfiles.GlobalConfigFiles.getConfigs()" could be added.The Configurator registration have to be done in JCasC plugin integration project.[~oleg_nenashev] / [~ndeloof] : Would this be suitable for you, even it fits not 100% to the roadmap of JCasC plugin?[~domi]: Is there a plan to baseline the plugin on Java 8?
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-53247) Support JCasC in Config File Provider Plugin
Title: Message Title Stefan Rempfer edited a comment on JENKINS-53247 Re: Support JCasC in Config File Provider Plugin Here are the Java Levels levels of the LTS versions based on [https://jenkins.io/doc/upgrade-guide/]||Jenkins Version||Java Version|||LTS 2.7.x|unknown - nothing defined in the guide||LTS 2.19.x|unknown - nothing defined in the guide||LTS 2.32.x|unknown / Java 7 for JNLP4 remoting||LTS 2.46.x|unknown / Java 7 for JNLP4 remoting||LTS 2.60.x|Java 8||LTS 2.73.x|Java 8||LTS 2.89.x|Java 8||LTS 2.107.x|Java 8||LTS 2.121.x|Java 8| 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-53247) Support JCasC in Config File Provider Plugin
Title: Message Title Stefan Rempfer commented on JENKINS-53247 Re: Support JCasC in Config File Provider Plugin Here the Java Levels of LTS versions based on https://jenkins.io/doc/upgrade-guide/ Jenkins Version Java Version LTS 2.7.x unknown - nothing defined in the guide LTS 2.19.x unknown - nothing defined in the guide LTS 2.32.x unknown / Java 7 for JNLP4 remoting LTS 2.46.x unknown / Java 7 for JNLP4 remoting LTS 2.60.x Java 8 LTS 2.73.x Java 8 LTS 2.89.x Java 8 LTS 2.107.x Java 8 LTS 2.121.x Java 8
[JIRA] (JENKINS-53356) Scriptlet 'ViewScript' link and Required Parameters not displayed in configuration
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-53356 Scriptlet 'ViewScript' link and Required Parameters not displayed in configuration Change By: Ioannis Moutsatsos In the UIproject UI project configuration: Adding Scriptler based Active Choice parameters to a project does not display the '_ViewScript_' and Scriptler _Required Parameters_. This *makes it difficult to inspect the scriptlet and set the job parameters.*The ' _ViewScrip_t _ViewScrip ' and _Required Required parameters_ are displayed ONLY IF a Scriptler based build step is added.Here is an comparison of what the configuration screen looks like without and with a Scriptler build step!image-2018-08-30-13-28-49-996.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-53356) Scriptlet 'ViewScript' link and Required Parameters not displayed in configuration
Title: Message Title Ioannis Moutsatsos created an issue Jenkins / JENKINS-53356 Scriptlet 'ViewScript' link and Required Parameters not displayed in configuration Issue Type: Bug Assignee: Bruno P. Kinoshita Attachments: image-2018-08-30-13-28-49-996.png Components: active-choices-plugin Created: 2018-08-30 17:30 Environment: Jenkins v 2.212.3, Active-Choices v2.1 Priority: Minor Reporter: Ioannis Moutsatsos In the UIproject configuration: Adding Scriptler based Active Choice parameters to a project does not display the 'ViewScript' and Scriptler Required Parameters. This makes it difficult to inspect the scriptlet and set the job parameters. The 'ViewScrip_t' and _Required parameters are displayed ONLY IF a Scriptler based build step is added. Here is an comparison of what the configuration screen looks like without and with a Scriptler build step
[JIRA] (JENKINS-53354) Git polling forces workspace-based polling when using parameters in Branch Specifier field
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-53354 Git polling forces workspace-based polling when using parameters in Branch Specifier field Change By: Mark Waite Assignee: Mark Waite 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-53355) use credential storage for Jira Pipeline Steps authentication
Title: Message Title Jason Curtis updated an issue Jenkins / JENKINS-53355 use credential storage for Jira Pipeline Steps authentication Change By: Jason Curtis Environment: Jenkins ver. 2.107.1 Folders Plugin version 6.1.2 Role-based Authorization Strategy Plugin version 2.6.1 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-53355) use credential storage for Jira Pipeline Steps authentication
Title: Message Title Jason Curtis created an issue Jenkins / JENKINS-53355 use credential storage for Jira Pipeline Steps authentication Issue Type: Improvement Assignee: Naresh Rayapati Components: jira-steps-plugin Created: 2018-08-30 17:16 Environment: Jenkins ver. 2.107.1 Folders Plugin version 6.1.2 Role-based Authorization Strategy version 2.6.1 Priority: Minor Reporter: Jason Curtis The JIRA Pipeline Steps Plugin version 1.4.3 only allows global configuration for authentication at Manage Jenkins > Configure System > JIRA Steps We use Role-based access control to folders and projects with a combination of the Folders Plugin and Role-based Authorization Strategy Plugin. Project owners depend on plugins allowing use of the withCredentials Pipeline step for authentication. Add Comment
[JIRA] (JENKINS-51111) Navigating to downstream job via Blue Ocean Triggered Builds does not show tests in Tests tab
Title: Message Title Roger Wooley commented on JENKINS-5 Re: Navigating to downstream job via Blue Ocean Triggered Builds does not show tests in Tests tab I updated to Blue Ocean (1.7.2) and the issue doesn't occur anymore. I'm not sure if 1.6 or 1.7.x fixed it. 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-53354) Git polling forces workspace-based polling when using parameters in Branch Specifier field
Title: Message Title Jamie Saliga created an issue Jenkins / JENKINS-53354 Git polling forces workspace-based polling when using parameters in Branch Specifier field Issue Type: Bug Assignee: Mark Waite Attachments: image-2018-08-30-11-41-32-133.png Components: git-plugin Created: 2018-08-30 16:44 Environment: Jenkins server v2.121.2 Git plugin v3.9.1 Git client plugin v2.7.3 Priority: Minor Reporter: Jamie Saliga We're using dynamic docker slaves which are spun up to build and then immediately deleted when the job is completed. We ran into an issue where the git polling was not working and tracked it down to the use of a parameter in the Branch Specifier field (See screenshot). Having to hard-code this value into the field is fine but we prefer to use a parameter to avoid having to hard-code this value in other related fields which adds the risk of missing one when making a job change. The same problem seems to also affect the Lightweight Checkout option.
[JIRA] (JENKINS-53342) agent went offline after jenkins instance restart
Title: Message Title Oleg Nenashev assigned an issue to Jeff Thompson Jenkins / JENKINS-53342 agent went offline after jenkins instance restart Change By: Oleg Nenashev Assignee: Jeff Thompson 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-53342) agent went offline after jenkins instance restart
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-53342 agent went offline after jenkins instance restart Change By: Oleg Nenashev Component/s: remoting Component/s: jenkins-reviewbot 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-53256) Backend should fill out `deletes` in the update level for plugins
Title: Message Title R. Tyler Croy commented on JENKINS-53256 Re: Backend should fill out `deletes` in the update level for plugins The backend has the versions table which contains the versions of software installed on the instance. The client is not sent the full contents of ingest.json for example, the backend computes what the client needs to know about to keep the client rather dumb. Using that versions information, the backend should be able to compute some deletes as well 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 commented on JENKINS-52058 Re: Provide report filename as variable to Groovy parser thanks a lot. don't hesitate to provide us a test version if you need help to test it before deployment. 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 Roy Arnon edited a comment on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume [~svanoort] we have also recently encountered this issue, or something similar as in our case the resuming jobs completed with SUCCESS.I commented [ here |https://issues.jenkins-ci.org/browse/JENKINS-33761?focusedCommentId=347675=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-347675] But it seems this issue is more relevant to this ticket.In our case the resuming build was marked as SUCCESS which marked at as success in Bitbucket (with bitbucket-branch-source plugin). The build itself never completed and in fact had a failing test. This allowed one of our developers to merge a failing build into release unfortunately, If there is anything you need from our jenkins instance I am happy to provide it. 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 Roy Arnon edited a comment on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume [~svanoort] we have also recently encountered this issue , or something similar as in our case the resuming jobs completed with SUCCESS .I commented hereBut it seems this issue is more relevant to this ticket.In our case the resuming build was marked as SUCCESS which marked at as success in Bitbucket (with bitbucket-branch-source plugin). The build itself never completed and in fact had a failing test. This allowed one of our developers to merge a failing build into release unfortunately, If there is anything you need from our jenkins instance I am happy to provide it. 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-53149) GitHubCommitStatusSetter is not reading proper commit id from a shared library
Title: Message Title Manuel de la Peña commented on JENKINS-53149 Re: GitHubCommitStatusSetter is not reading proper commit id from a shared library Hi Kirill Merkushev, I noticed the plugin always takes into account the first repository that the build action has. But when there is more than one repository, i.e. when loading a shared library, then it would be necessary to inspect the repos, and verify if they relate to the proper repository, which is the project's one. I sent a possible fix here: https://github.com/jenkinsci/github-plugin/pull/198 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-25845) Node startup log should contain a timestamp
Title: Message Title Josiah Eubank commented on JENKINS-25845 Re: Node startup log should contain a timestamp Is this specific to a plugin or for all Nodes? Using vsphere plugin to reboot/revert nodes and the node logs do not have timestamps. Attempting to determine if this ticket has regressed or it does not apply to the current lack of timestamps. 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-53351) upload testing result to alm by jenkins groovy
Title: Message Title Mohamed Alaa updated an issue Jenkins / JENKINS-53351 upload testing result to alm by jenkins groovy Change By: Mohamed Alaa Priority: Major 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-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Roy Arnon edited a comment on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume [~svanoort] we have also recently encountered this issue.I commented [ here |https://issues.jenkins-ci.org/browse/JENKINS-33761?focusedCommentId=347675=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-347675] But it seems this issue is more relevant to this ticket.In our case the resuming build was marked as SUCCESS which marked at as success in Bitbucket (with bitbucket-branch-source plugin). The build itself never completed and in fact had a failing test. This allowed one of our developers to merge a failing build into release unfortunately, If there is anything you need from our jenkins instance I am happy to provide it. 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 Roy Arnon commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume Sam Van Oort we have also recently encountered this issue. I commented here But it seems this issue is more relevant to this ticket. In our case the resuming build was marked as SUCCESS which marked at as success in Bitbucket (with bitbucket-branch-source plugin). This allowed one of our developers to merge a failing build into release unfortunately, If there is anything you need from our jenkins instance I am happy to provide it. 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-53353) Jenkins requires restart when installing plugins with TransientActionFactories
Title: Message Title Steve Arch created an issue Jenkins / JENKINS-53353 Jenkins requires restart when installing plugins with TransientActionFactories Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-08-30 15:39 Environment: jenkins-core:2.140 Priority: Minor Reporter: Steve Arch TransientViewActionFactories are only ever called once per view, see here This means that if you install a plugin that affects the view (via a TransientViewActionFactory) and getActions() has already been called for that view, your implementation of TransientViewActionFactory will not be called and your action will not happen (eg, populating a sidepanel entry etc). We should either implement an ExtensionListener to dirty the cached transientActions when a new plugin is loaded, or do away with the caching altogether Add Comment
[JIRA] (JENKINS-53289) Test that upgrading Evergreen through a new docker pull && docker run keeps things running
Title: Message Title R. Tyler Croy assigned an issue to Baptiste Mathus Jenkins / JENKINS-53289 Test that upgrading Evergreen through a new docker pull && docker run keeps things running Change By: R. Tyler Croy Assignee: R. Tyler Croy Baptiste Mathus 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) Log in page redirects to http://localhost instead of http://localhost:8080
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-53345 Log in page redirects to http://localhost instead of http://localhost:8080 Please file bugs as bugs, that helps me triage and sort Change By: R. Tyler Croy Issue Type: Task Bug 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-53323) Only include node_modules required for runtime in the container
Title: Message Title R. Tyler Croy started work on JENKINS-53323 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-53227) evergreen-client should do integrity checking on downloads and gracefully handle errors
Title: Message Title R. Tyler Croy updated JENKINS-53227 Jenkins / JENKINS-53227 evergreen-client should do integrity checking on downloads and gracefully handle errors Change By: R. Tyler Croy 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-53352) Consecutive white space is not rendered
Title: Message Title
Edward Hartwell Goose updated an issue
Jenkins / JENKINS-53352
Consecutive white space is not rendered
Change By:
Edward Hartwell Goose
We found a discrepancy between how Jenkins and Blue Ocean render test results: This is what Jenkins renders: {code:java}Failed asserting that two strings are equal.— Expected+++ Actual@@ @@-'This is an email from the xyz system (this is not shown when live)'+'This is an email from the xyz system (this is not shown when live)'{code} And this is what BlueOcean renders: {code:java}Failed asserting that two strings are equal. — Expected +++ Actual @@ @@ -'This is an email from the mentionme.dev xyz system (this is not shown when live)' +'This is an email from the mentionme.dev xyz system (this is not shown when live)'{code} This confused us for quite some time until we switched back to Jenkins and saw the whitespace was removed from Blue Ocean.
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-53352) Consecutive white space is not rendered
Title: Message Title
Edward Hartwell Goose updated an issue
Jenkins / JENKINS-53352
Consecutive white space is not rendered
Change By:
Edward Hartwell Goose
We found a discrepancy between how Jenkins and Blue Ocean render test results: This is what Jenkins renders: {code:java} ``` Failed asserting that two strings are equal. --- — Expected +++ Actual @@ @@ -'This is an email from the xyz system (this is not shown when live)' +'This is an email from the xyz system (this is not shown when live)' {code} ``` And this is what BlueOcean renders: {code:java} ``` Failed asserting that two strings are equal. --- — Expected+++ Actual@@ @@-'This is an email from the mentionme.dev system (this is not shown when live)'+'This is an email from the mentionme.dev system (this is not shown when live)' ``` {code} This confused us for quite some time until we switched back to Jenkins and saw the whitespace was removed from Blue Ocean.
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-52171) Gitlab plugin uncompatible with Jira plugin in pipeline
Title: Message Title Dave Nichols commented on JENKINS-52171 Re: Gitlab plugin uncompatible with Jira plugin in pipeline Getting the same error, but with a different plugin from the Jira one. java.lang.LinkageError: ClassCastException: attempting to castjar:file:/var/jenkins_home/plugins/gitlab-plugin/WEB-INF/lib/jboss-jaxrs-api_2.0_spec-1.0.0.Final.jar!/javax/ws/rs/ext/RuntimeDelegate.classtojar:file:/var/jenkins_home/plugins/coverity/WEB-INF/lib/jersey-core-1.13.jar!/javax/ws/rs/ext/RuntimeDelegate.class at javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:116) at javax.ws.rs.ext.RuntimeDelegate.getInstance(RuntimeDelegate.java:91) at javax.ws.rs.core.UriBuilder.newInstance(UriBuilder.java:69) at javax.ws.rs.core.UriBuilder.fromUri(UriBuilder.java:80) at jenkins.plugins.coverity.ws.ViewsService.getViewContents(ViewsService.java:83) at jenkins.plugins.coverity.CIMInstance.getIssuesVorView(CIMInstance.java:303) at jenkins.plugins.coverity.ws.ViewIssuesReader.getIssuesFromConnectView(ViewIssuesReader.java:47) at jenkins.plugins.coverity.CoverityViewResultsPublisher.perform(CoverityViewResultsPublisher.java:77) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Finished: FAILURE Not sure if it is related Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-53352) Consecutive white space is not rendered
Title: Message Title Edward Hartwell Goose created an issue Jenkins / JENKINS-53352 Consecutive white space is not rendered Issue Type: Bug Assignee: Unassigned Attachments: mention-me_MentionMe_PR-5596__1_test_-_test___EmailBundleUnitTests___testReferrerRegistrationEmail_with_data_set__0__Jenkins__and_jenkins___mention-me_MentionMe___PR-55961.png Components: blueocean-plugin Created: 2018-08-30 15:24 Environment: Jenkins 2.138 Blue Ocean 1.8.2 PHPUnit 6 JUnit 1.2.4 plugin Priority: Minor Reporter: Edward Hartwell Goose We found a discrepancy between how Jenkins and Blue Ocean render test results: This is what Jenkins renders: ``` Failed asserting that two strings are equal. — Expected +++ Actual @@ @@ -'This is an email from the xyz system (this is not shown when live)' +'This is an email from the xyz system (this is not shown when live)' ``` And this is what BlueOcean renders: ``` Failed asserting that two strings are equal. — Expected +++ Actual @@ @@ -'This is an email from the mentionme.dev system (this is not shown when live)' +'This is an email from the mentionme.dev system (this is not shown when live)' ```
[JIRA] (JENKINS-33761) Ability to disable Pipeline durability and "resume" build.
Title: Message Title Roy Arnon commented on JENKINS-33761 Re: Ability to disable Pipeline durability and "resume" build. Hello, I am not sure this is related to this issue, but in our pipeline build job we recently added the disableResume step and it does not seem to work correctly: Jenkins 2.89.3 Pipeline 2.5 Pipeline API 2.27 Pipeline Nodes and Processes 2.20 Pipeline Step API 2.16 Scripts Security 1.44 durabilityHint=PERFORMANCE_OPTIMIZED org.jenkinsci.plugins.workflow.job.properties.DisableResumeJobProperty Groovy Sandbox = disabled Creating placeholder flownodes because failed loading originals. Resuming build at Thu Aug 30 12:42:45 UTC 2018 after Jenkins restart [Bitbucket] Notifying pull request build result [Bitbucket] Build result notified [lockable-resources] released lock on [UNIT_TEST_RESOURCE_3] java.io.IOException: Tried to load head FlowNodes for execution Owner[Products.Pipeline/PR-5615/7:Products.Pipeline/PR-5615 #7] but FlowNode was not found in storage for head id:FlowNodeId 1:586 at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.initializeStorage(CpsFlowExecution.java:678) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad(CpsFlowExecution.java:715) at org.jenkinsci.plugins.workflow.job.WorkflowRun.getExecution(WorkflowRun.java:875) at org.jenkinsci.plugins.workflow.job.WorkflowRun.onLoad(WorkflowRun.java:745) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:57) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:500) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:482) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:380) at hudson.model.RunMap.getById(RunMap.java:205) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.run(WorkflowRun.java:1098) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(WorkflowRun.java:1109) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:65) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:57) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl.onLoaded(FlowExecutionList.java:178) at jenkins.model.Jenkins.(Jenkins.java:974) at hudson.model.Hudson.(Hudson.java:86) at hudson.model.Hudson.(Hudson.java:82) at hudson.WebAppMain$3.run(WebAppMain.java:233) Finished: SUCCESS This is an issue for us as the build was marked as SUCCESS in bitbucket, which allowed a user to merge a failing test into our release branch. The job was definitely running with resume disabled, as this was printed at start of job: Resume disabled by user, switching to high-performance, low-durability mode. Any ideas?
[JIRA] (JENKINS-52753) Uploads archived junit results from Jenkinsfile
Title: Message Title Mohamed Alaa edited a comment on JENKINS-52753 Re: Uploads archived junit results from Jenkinsfile Is the above code working ? it gives me the following error ```java.lang.UnsupportedOperationException: no known implementation of interface jenkins.tasks.SimpleBuildStep is named uploadTestResultToAlmModel``` 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-52753) Uploads archived junit results from Jenkinsfile
Title: Message Title Mohamed Alaa commented on JENKINS-52753 Re: Uploads archived junit results from Jenkinsfile Is the above code 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-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Devin Nusbaum updated JENKINS-50199 Jenkins / JENKINS-50199 Failed pipeline jobs stuck running after incorrect resume Change By: Devin Nusbaum 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-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Devin Nusbaum started work on JENKINS-50199 Change By: Devin Nusbaum Status: Reopened 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-53347) NPM cannot find node binary
Title: Message Title Jon Rimmer updated JENKINS-53347 Jenkins / JENKINS-53347 NPM cannot find node binary Change By: Jon Rimmer Status: Fixed but Unreleased Closed 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-53347) NPM cannot find node binary
Title: Message Title Jon Rimmer updated JENKINS-53347 OK, I figured this out: The jenkins/blueocean image is based on Alpine Linux, but the binaries downloaded by the nodejs plugin are not compatible with it. Jenkins / JENKINS-53347 NPM cannot find node binary Change By: Jon Rimmer Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49947) unclear usage of input step in declarative pipeline
Title: Message Title Liam Fitzpatrick commented on JENKINS-49947 Re: unclear usage of input step in declarative pipeline I have a similar issue to Fernando Nasser. I have 2 parallel stages, one for dev and one for prod and a when condition determines which stage to run based on the environment. I want to prompt for input in the prod stage only but as the input happens before the when I get prompted for input in regardless of the environment, 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-53351) upload testing result to alm by jenkins groovy
Title: Message Title Mohamed Alaa created an issue Jenkins / JENKINS-53351 upload testing result to alm by jenkins groovy Issue Type: Task Assignee: Daniel Gront Components: hp-application-automation-tools-plugin, http-request-plugin Created: 2018-08-30 14:26 Priority: Major Reporter: Mohamed Alaa I am using Jenkins to upload my testing result to ALM in GUI, I want to add this step to my pipeline in Jenkinsfile Is there any way or work around to make this step Add Comment This message was
[JIRA] (JENKINS-53140) Intermittent Random Stage Failures - No Changes Detected - Parallel Stages
Title: Message Title Andrew Bayer commented on JENKINS-53140 Re: Intermittent Random Stage Failures - No Changes Detected - Parallel Stages Hrm, can't see why skipDefaultCheckout(true) would mess with the environment at all, other than that any environment variables contributed by the SCM plugin's checkout process (in this case, SVN_REVISION and SVN_URL) wouldn't be automatically added to the environment as they would be with the normal default checkout happening. 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-53350) Pipeline graph fails to display per-step ErrorAction
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-53350 Pipeline graph fails to display per-step ErrorAction Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2018-08-30 14:24 Priority: Major Reporter: Jesse Glick Not sure if this is still true today, but was at the time JENKINS-48250 was filed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-48250) junit step failures hidden in console output
Title: Message Title Jesse Glick commented on JENKINS-48250 Re: junit step failures hidden in console output This is a bug in Blue Ocean, not in junit. There is no expectation in general that details of a step failure would be present in its LogAction, if it even has one. Blue Ocean should be displaying the ErrorAction message. I am reverting the bogus logic and commenting out the bogus test as part of the external storage work. 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 commented on JENKINS-53140 Re: Intermittent Random Stage Failures - No Changes Detected - Parallel Stages Per the suggestion, at the top level of the Jenkinsfile we added the following: skipDefaultCheckout(true) Unfortunately, it caused a surprising issue that we don't understand. You can see the following lines in our steps: python build.py build.py runs a docker container passing the SVN credentials via -e. The docker container runs another python script which does an SVN checkout all of which works as desired. After adding skipDefaultCheckout(true), the SVN checkout inside the docker containers failed. The most likely candidate seems to be that it somehow broke the passing of the SVN_CREDENTIALS environment variables to the container. Rather than troubleshoot that at yesterday, i tried putting skipDefaultCheckout(true) in the checkout step. Unfortunately, that did not fix the issue. If you have ideas about why skipDefaultCheckout(true) might have broken the environment variable, maybe we can work around it. 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
[JIRA] (JENKINS-53349) Parameterized Classes are not displayed properly when published with nunit-plugin
Title: Message Title
Patrick Buech updated an issue
Jenkins / JENKINS-53349
Parameterized Classes are not displayed properly when published with nunit-plugin
Change By:
Patrick Buech
A parameterized test, will be shown wrong in Test Result Analyzer.The attached "Class1.cs" should show 3 different TestClasses inside TestResultAnalyzer:# TestClass("a")# TestClass("b")# TestClass("c")Instead only TestClass is shown. It is unclear in which results are presented here inside.Adding the parameters to the classname attribute in TestResult.xml yields the same results.Find attached:# Class1.cs: TestClass# TestResult.original.xml: Result file for parameterized class# TestResult.patched1.xml: 1st try to patch TestResult.xml (not successful)# visualstudio-testexplorer.PNG: Tests shown in VisualStudio# test-result-analyzer.PNG: Tests shown in Jenkins # nunit-console.PNG: output from console runner
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-50116) Last changes history becomes empty after Jenkins restart
Title: Message Title Daniel Beck commented on JENKINS-50116 Re: Last changes history becomes empty after Jenkins restart Make the transient action factory the only source for project actions – not any job property or whatever else you did. 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-53349) Parameterized Classes are not displayed properly when published with nunit-plugin
Title: Message Title Patrick Buech updated an issue Jenkins / JENKINS-53349 Parameterized Classes are not displayed properly when published with nunit-plugin Change By: Patrick Buech Attachment: nunit-console.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-53349) Parameterized Classes are not displayed properly when published with nunit-plugin
Title: Message Title
Patrick Buech created an issue
Jenkins / JENKINS-53349
Parameterized Classes are not displayed properly when published with nunit-plugin
Issue Type:
Bug
Assignee:
Alex Earl
Attachments:
Class1.cs, test-result-analyzer.PNG, TestResult.original.xml, TestResult.patched1.xml, visualstudio-testexplorer.PNG
Components:
nunit-plugin, test-results-analyzer-plugin
Created:
2018-08-30 14:01
Environment:
Jenkins 2.140 (on Debian Stretch) org.jenkins-ci.plugins:nunit:0.23 org.jenkins-ci.plugins:test-results-analyzer:0.3.5
Priority:
Minor
Reporter:
Patrick Buech
A parameterized test, will be shown wrong in Test Result Analyzer. The attached "Class1.cs" should show 3 different TestClasses inside TestResultAnalyzer:
TestClass("a")
TestClass("b")
TestClass("c")
Instead only TestClass is shown. It is unclear in which results are presented here inside. Adding the parameters to the classname attribute in TestResult.xml yields the same results. Find attached:
Class1.cs: TestClass
TestResult.original.xml: Result file for parameterized class
[JIRA] (JENKINS-51568) Pipeline jobs hanging in Build Executor even if it is finished
Title: Message Title Devin Nusbaum commented on JENKINS-51568 Re: Pipeline jobs hanging in Build Executor even if it is finished Alexander Moiseenko I thought this might be a dupe of JENKINS-45571, but in your case it looks like the stuck executors are full Executors running on build agents rather than the flyweight executors that run on the master, so it seems like it might be something else. What versions of the Pipeline Groovy Plugin, Pipeline Job Plugin, Durable Task Plugin, and the Pipeline Nodes and Processes Plugin are you running? 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-52937) Add tooling for updating Incrementals in Docker image plugins.txt
Title: Message Title Oleg Nenashev updated JENKINS-52937 Jesse Glick has released the patch. I also submitted a documentation update PR: https://github.com/jenkinsci/docker/pull/721 Jenkins / JENKINS-52937 Add tooling for updating Incrementals in Docker image plugins.txt Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Incrementals Tools 1.0-beta-6 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-53281) Convert com.nirima.jenkins.plugins.docker.DockerImagePullStrategy$2 to non anymous class
Title: Message Title Jesse Glick resolved as Duplicate Actually not a plugin bug; the same root cause as JENKINS-52945. Jenkins / JENKINS-53281 Convert com.nirima.jenkins.plugins.docker.DockerImagePullStrategy$2 to non anymous class Change By: Jesse Glick Status: In Progress Resolved Resolution: Duplicate 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.
