[JIRA] (JENKINS-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Olivier Lamy commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 Tomas Zaleniakas with 3.0.4? Can I get a screenshot of the UI and errors logs when trying to annotate. This will help to understand the problem as it should be fixed. 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-54299) Jenkins failed to start after updating pluins and restart
Title: Message Title Sam Tang updated an issue Jenkins / JENKINS-54299 Jenkins failed to start after updating pluins and restart Change By: Sam Tang Summary: Jenkins failed to start after updatimh updating pluins and restart 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-54253) fix SSC (Fortify) integration
Title: Message Title Yuri Guller closed an issue as Fixed Jenkins / JENKINS-54253 fix SSC (Fortify) integration Change By: Yuri Guller Status: Resolved 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-54253) fix SSC (Fortify) integration
Title: Message Title Yuri Guller resolved as Fixed Jenkins / JENKINS-54253 fix SSC (Fortify) integration Change By: Yuri Guller 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-54300) silently close uft dispatcher queue on Jenkins shutdown
Title: Message Title Yuri Guller created an issue Jenkins / JENKINS-54300 silently close uft dispatcher queue on Jenkins shutdown Issue Type: Bug Assignee: Yuri Guller Components: hp-application-automation-tools-plugin Created: 2018-10-29 07:50 Environment: Dev env Priority: Trivial Reporter: Yuri Guller When running tests, Jenkins shutdown is prevented from cleaning up temporary folder due to some of our plugin's files are still held open. One of them - uft dispatcher's queue file - should be handled as part of this defect Another one - nga.log, will be handled separately as part of SDK fix Add Comment
[JIRA] (JENKINS-54301) silently close uft dispatcher queue on Jenkins shutdown
Title: Message Title Yuri Guller created an issue Jenkins / JENKINS-54301 silently close uft dispatcher queue on Jenkins shutdown Issue Type: Bug Assignee: Yuri Guller Components: hp-application-automation-tools-plugin Created: 2018-10-29 07:51 Environment: Dev env Priority: Trivial Reporter: Yuri Guller When running tests, Jenkins shutdown is prevented from cleaning up temporary folder due to some of our plugin's files are still held open. One of them - uft dispatcher's queue file - should be handled as part of this defect Another one - nga.log, will be handled separately as part of SDK fix Add Comment
[JIRA] (JENKINS-54301) silently close uft dispatcher queue on Jenkins shutdown
Title: Message Title Yuri Guller started work on JENKINS-54301 Change By: Yuri Guller 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-54302) silently close octane log (SDK managed)
Title: Message Title Yuri Guller created an issue Jenkins / JENKINS-54302 silently close octane log (SDK managed) Issue Type: Bug Assignee: Yuri Guller Components: hp-application-automation-tools-plugin Created: 2018-10-29 07:54 Environment: Dev env Priority: Trivial Reporter: Yuri Guller When closing Jenkins instance - shutdown sequence of plugin and its SDK is being executed. This sequence should ALSO stop/close custom logging and its files. In dev env, this prevents from removing TEMP folders, yet it is generally correct for any env. Add Comment
[JIRA] (JENKINS-26439) Build does not abort when «Send files or execute commands over SSH» fails
Title: Message Title
Stephan Watermeyer commented on JENKINS-26439
Re: Build does not abort when «Send files or execute commands over SSH» fails
Even if i change failOnError to true it still executes the next step.
SSH: Connecting from host [3e88a1716d53]
SSH: Connecting with configuration [swpsws46] ...
SSH: EXEC: STDOUT/STDERR from command [
echo "i am a failure"
exit 9 ] ...
i am a failure
SSH: EXEC: completed after 201 ms
SSH: Disconnecting configuration [swpsws46] ...
ERROR: Exception when publishing, exception message [Exec exit status not zero. Status [9]]
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Do sth on jenkins)
[Pipeline] echo
Should not run any more
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: FAILURE
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-54216) NPE when calculating culprits
Title: Message Title Frédéric Meyrou updated an issue Jenkins / JENKINS-54216 NPE when calculating culprits Change By: Frédéric Meyrou Component/s: clearcase-plugin Component/s: scm-api-plugin Component/s: mailer-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-54303) Pipeline zip does not suport symbolic links
Title: Message Title Hubert Li created an issue Jenkins / JENKINS-54303 Pipeline zip does not suport symbolic links Issue Type: New Feature Assignee: Unassigned Components: pipeline Created: 2018-10-29 08:12 Priority: Major Reporter: Hubert Li Pipeline zip does not support symbolic links. Please "store symbolic links as such in the zip archive, instead of compressing and storing the file referred to by the link.", like Linux zip with "–symlinks" option. This will save lot of time in zipping and disk space. Add Comment
[JIRA] (JENKINS-54117) [Jenkins Plugin] [5.5.2] Cannot stop executing the job on Jenkins side (Already checked UFT log no stop replay send to MC)
Title: Message Title feng jianzheng closed an issue as Cannot Reproduce Check with dev, now it cannot reproduce with latest mc set to closed Jenkins / JENKINS-54117 [Jenkins Plugin] [5.5.2] Cannot stop executing the job on Jenkins side (Already checked UFT log no stop replay send to MC) Change By: feng jianzheng Status: Open Closed Resolution: Cannot Reproduce 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-54222) p4-plugin keeps opening connection during the build. Causing long delays
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-54222 p4-plugin keeps opening connection during the build. Causing long delays Change By: Paul Allen Labels: P4_A p4-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-54222) p4-plugin keeps opening connection during the build. Causing long delays
Title: Message Title Paul Allen started work on JENKINS-54222 Change By: Paul Allen 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-54222) p4-plugin keeps opening connection during the build. Causing long delays
Title: Message Title Paul Allen updated JENKINS-54222 Ready for release. Jenkins / JENKINS-54222 p4-plugin keeps opening connection during the build. Causing long delays Change By: Paul Allen Status: In Progress Fixed but Unreleased Assignee: Paul Allen 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-54222) p4-plugin keeps opening connection during the build. Causing long delays
Title: Message Title Paul Allen commented on JENKINS-54222 Re: p4-plugin keeps opening connection during the build. Causing long delays Thank you for trying this out, I'm pleased it resolved your issue. I have marked this 'ready for release' and it should be officially available in the next few days. 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-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title fisnik hajredini created an issue Jenkins / JENKINS-54304 Jobs in parallel dont display the variant they are running. Issue Type: Bug Assignee: Oleg Nenashev Attachments: Selection_047.png, Selection_048.png Components: _unsorted Created: 2018-10-29 08:39 Environment: Jenkins 2.138.2 Priority: Major Reporter: fisnik hajredini This issue manifested itself since October 15th. When a build is triggered and it runs on multiple slaves parallely, you normally get an output for each line corresponding to the variant its running. Since a Jenkins update on October 15th, this has not been the case. This is making it harder for us to debug the issues on the variants/slaves, as we don't know on which variant the issue is being manifested. NOTE: Although unrelated, this issue was manifested together with another bug which doesn't allow an anonymous user to view jobs, even if logged in as a non-admin. Only users with admin privileges are allowed to view the logs. That issue has been found on your backlog.
[JIRA] (JENKINS-52487) p4-plugin + global pipeline shared library - no ${JOB_NAME} expansion in view
Title: Message Title
Paul Allen closed an issue as Won't Fix
Unable to resolve the issue as the environment is managed by Jenkins. Documented using single quotes for Strings containing environment variables.
Jenkins / JENKINS-52487
p4-plugin + global pipeline shared library - no ${JOB_NAME} expansion in view
Change By:
Paul Allen
Status:
Open Closed
Resolution:
Won't Fix
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-54305) Oracle JDK 10 not available anymore - Oracle JDK 11 is not free
Title: Message Title Marcus Philip moved an issue Jenkins / JENKINS-54305 Oracle JDK 10 not available anymore - Oracle JDK 11 is not free Change By: Marcus Philip Project: Infrastructure Jenkins Key: INFRA JENKINS - 1820 54305 Workflow: classic default workflow JNJira + In-Review Component/s: jdk-tool-plugin Component/s: etc 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-54251) RunResults throws NullPointerException
Title: Message Title Tamas Florin closed an issue as Fixed Jenkins / JENKINS-54251 RunResults throws NullPointerException Change By: Tamas Florin 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-54118) UFT jobs should be grouped together
Title: Message Title Tamas Florin closed an issue as Fixed Jenkins / JENKINS-54118 UFT jobs should be grouped together Change By: Tamas Florin 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-47837) Able to show part of the test result when a build reachs it's timeout
Title: Message Title Tamas Florin closed an issue as Fixed Jenkins / JENKINS-47837 Able to show part of the test result when a build reachs it's timeout Change By: Tamas Florin 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-54272) Bibucket Plugin is not triggering the job because of minimal url mismatch (".*/scm/.*")
Title: Message Title
Roxana Muresan updated an issue
Jenkins / JENKINS-54272
Bibucket Plugin is not triggering the job because of minimal url mismatch (".*/scm/.*")
Change By:
Roxana Muresan
Bitbucket Plugin is not triggering matching Jobs.I have added a FINE log to investigate where it hangs and I followed the source code in Github in paralel to understand the source of the problem. Looks like the match method in BitbucketJobProbe returns false when it checks the url from my jenkins job with the url from the payload.Logs:Considering candidate job trigger-build-branchOct 26, 2018 3:15:14 PM FINE com.cloudbees.jenkins.plugins.BitbucketJobProbeConsidering to poke trigger-build-branchOct 26, 2018 3:15:14 PM FINE com.cloudbees.jenkins.plugins.BitbucketJobProbeTrying to match [ https://[host]/ bitbucket/ scm/[project]/[repository].git |https://[host]/scm/[project]/[repository].git] <--> [ https://[host]/ bitbucket/ [project]/[repository |https://[host ] /[project]/[repository]] Oct 26, 2018 3:15:14 PM FINE com.cloudbees.jenkins.plugins.BitbucketJobProbetrigger-build-branch SCM doesnt match remote repo \{1} There is a check for "/scm" before actually comparing the url but it removes the "/scm" only if it appears at the start. In my case "/scm" is somewhere inside the url. [https://[host] /bitbucket */scm*/[project]/[repository].git] [ https://[host]/ bitbucket/ [project]/[repository |https://[host ] /[project]/[repository]]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Paul Holden commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 Hi Olivier Lamy, is there any specific part of my configuration you want to see? Same as Tomas Zaleniakas - the plugin worked fine up until 3.0.2 but has been broken in the two subsequent releases. The configuration for my JIRA site hasn't changed since 3.0.2. Current problem is with the changelog annotator after a triggered build, and when trying to validate settings in admin UI. 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-54105) Maven Event Spy InterruptedException
Title: Message Title Cyrille Le Clerc commented on JENKINS-54105 Re: Maven Event Spy InterruptedException 3.5.15 adds messages to help understand the problem: In case of InterruptedException, a message in the logs with the duration since the beginning of the processing is outputted, we want to verify if we have reached the standard timeout of the pipeline steps: [withMaven] Processing of Maven build outputs interrupted in " + mavenPublisher.toString() + " after " + TimeUnit.MILLISECONDS.convert(System.nanoTime() - nanosBefore, TimeUnit.NANOSECONDS) + "ms. When INFO level is enabled on org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor, a summary of the duration of each publisher is added to the build logs. Sample: [withMaven] Publishers: Generated Artifacts Publisher: 36 ms, Junit Publisher: 9 ms, Dependencies Fingerprint Publisher: 6 ms, Pipeline Graph Publisher: 1 ms, Open Task Scanner Publisher: 25 ms Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54306) Move Chart Context Menu icon up in Load Runner Performance Result report
Title: Message Title Omer Kenan created an issue Jenkins / JENKINS-54306 Move Chart Context Menu icon up in Load Runner Performance Result report Issue Type: Bug Assignee: Rolando-Mihai Vlad Attachments: ChartContextMenu.PNG Components: hp-application-automation-tools-plugin Created: 2018-10-29 09:43 Labels: loadrunner Priority: Minor Reporter: Omer Kenan Move Chart Context Menu icon up in LoadRunner Performance Result report Add Comment
[JIRA] (JENKINS-49337) InterruptedException - Exception processing the logs
Title: Message Title Cyrille Le Clerc commented on JENKINS-49337 Re: InterruptedException - Exception processing the logs 3.5.15 adds messages to help understand the problem: In case of InterruptedException, a message in the logs with the duration since the beginning of the processing is outputted, we want to verify if we have reached the standard timeout of the pipeline steps: [withMaven] Processing of Maven build outputs interrupted in " + mavenPublisher.toString() + " after " + TimeUnit.MILLISECONDS.convert(System.nanoTime() - nanosBefore, TimeUnit.NANOSECONDS) + "ms. When INFO level is enabled on org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor, a summary of the duration of each publisher is added to the build logs. Sample: [withMaven] Publishers: Generated Artifacts Publisher: 36 ms, Junit Publisher: 9 ms, Dependencies Fingerprint Publisher: 6 ms, Pipeline Graph Publisher: 1 ms, Open Task Scanner Publisher: 25 ms Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54105) Maven Event Spy InterruptedException
Title: Message Title
Cyrille Le Clerc edited a comment on JENKINS-54105
Re: Maven Event Spy InterruptedException
3.5.15 adds messages to help understand the problem:In case of {{InterruptedException}}, a message in the logs with the duration since the beginning of the processing is outputted, we want to verify if we have reached the standard timeout of the pipeline steps:{noformat}[withMaven] Processing of Maven build outputs interrupted in " + mavenPublisher.toString() + " after " + TimeUnit.MILLISECONDS.convert(System.nanoTime() - nanosBefore, TimeUnit.NANOSECONDS) + "ms.{noformat}When INFO level is enabled on {{org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor}}, a summary of the duration of each publisher is added to the build logs. Sample:{ quote noformat }[withMaven] Publishers: Generated Artifacts Publisher: 36 ms, Junit Publisher: 9 ms, Dependencies Fingerprint Publisher: 6 ms, Pipeline Graph Publisher: 1 ms, Open Task Scanner Publisher: 25 ms{ quote noformat }
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-46096) Pipeline stage view rendered at bottom of page, below build history
Title: Message Title Marcus Philip updated an issue Jenkins / JENKINS-46096 Pipeline stage view rendered at bottom of page, below build history Change By: Marcus Philip Attachment: PipelineAtBottom-NotOK.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-46096) Pipeline stage view rendered at bottom of page, below build history
Title: Message Title Marcus Philip updated an issue Jenkins / JENKINS-46096 Pipeline stage view rendered at bottom of page, below build history Change By: Marcus Philip Attachment: NoPipelineAtTop-NotOK.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-54307) Plot plugin is not working for zero values on logaritmic scale
Title: Message Title david gomez created an issue Jenkins / JENKINS-54307 Plot plugin is not working for zero values on logaritmic scale Issue Type: Bug Assignee: Veaceslav Gaidarji Attachments: Screenshot from 2018-10-29 10-48-07.png Components: plot-plugin Created: 2018-10-29 09:55 Priority: Major Reporter: david gomez If for any reason, some value of a csv containing zero, the logaritmic graph representation fails as you can see on the attached image. How to reproduce: add a job with plotplugin after build step create a csv file like this: echo "Method,Name,# requests,# failures,Median response time,Average response time,Min response time,Max response time,Average Content Size","Requests/s" > requests2.csv echo "None,Total,1737387,21,170,185,0,31948,4023,1916.17" >> requests2.csv Check logaritmic representation Note: changing zero value to another one the plot plugin is able to represent the graph Plot plugin version: 2.1.0 jenkins version: 2.3
[JIRA] (JENKINS-49337) InterruptedException - Exception processing the logs
Title: Message Title Vincent Massol commented on JENKINS-49337 Re: InterruptedException - Exception processing the logs Thanks Cyrille Le Clerc. Waiting for a release of 3.5.15 and we'll upgrade and report the output here. I'll also investigate how to set the INFO level logging you mentioned, 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Olivier Lamy commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 I need to know if you have the same error log with 3.0.4? what happen if you configure correctly the value in the ui? anyway I need some ui screenshots or console logs 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-54307) Plot plugin is not working for zero values on logaritmic scale
Title: Message Title
david gomez updated an issue
Jenkins / JENKINS-54307
Plot plugin is not working for zero values on logaritmic scale
Change By:
david gomez
If for any reason, some value of a csv containing zero, the logaritmic graph representation fails as you can see on the attached image.How to reproduce: * add a job with plotplugin after build step * create a csv file like this:{code:java}echo "Method,Name,# requests,# failures,Median response time,Average response time,Min response time,Max response time,Average Content Size","Requests/s" > requests2.csvecho "None,Total,1737387,21,170,185,0,31948,4023,1916.17" >> requests2.csv{code} * Check logaritmic representationNote: changing zero value to another other positive one greater than 0, the plot plugin is able to represent the graphPlot plugin version: 2.1.0jenkins version: 2.3
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-49337) InterruptedException - Exception processing the logs
Title: Message Title
Vincent Massol edited a comment on JENKINS-49337
Re: InterruptedException - Exception processing the logs
Thanks [~cleclerc]. Waiting for a release of 3.5.15 and we'll upgrade and report the output here. I'll also investigate how to set the INFO level logging you mentioned, thanks. FTM we're plagued with ClosedChannelException errors in our logs, such as with:{noformat}[withMaven] junitPublisher - Archive test results for Maven artifact org.xwiki.platform:xwiki-platform-search-solr-query:jar:10.10-SNAPSHOT generated by maven-surefire-plugin:test (default-test): xwiki-platform-core/xwiki-platform-search/xwiki-platform-search-solr/xwiki-platform-search-solr-query/target/surefire-reports/*.xmlRecording test resultsFATAL: Failed to save the JUnit test resultjava.io.IOException: com.thoughtworks.xstream.io.StreamException: : null at hudson.XmlFile.write(XmlFile.java:200) at hudson.tasks.junit.TestResultAction.setResult(TestResultAction.java:117) at hudson.tasks.junit.TestResultAction.mergeResult(TestResultAction.java:270) at hudson.tasks.junit.JUnitResultArchiver.parseAndAttach(JUnitResultArchiver.java:179) at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:154) at org.jenkinsci.plugins.pipeline.maven.publishers.JunitTestsPublisher.executeReporter(JunitTestsPublisher.java:295) at org.jenkinsci.plugins.pipeline.maven.publishers.JunitTestsPublisher.process(JunitTestsPublisher.java:196) at org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor.processMavenSpyLogs(MavenSpyLogProcessor.java:118) at org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution$WithMavenStepExecutionCallBack.finished(WithMavenStepExecution.java:1053) at org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback$TailCall.onFailure(BodyExecutionCallback.java:124) at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$FailureAdapter.receive(CpsBodyExecution.java:349) at com.cloudbees.groovy.cps.impl.ValueBoundContinuation.receive(ValueBoundContinuation.java:21) at com.cloudbees.groovy.cps.Block$Noop.eval(Block.java:30) at com.cloudbees.groovy.cps.Next.step(Next.java:83) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163) at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122) at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:261) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$101(SandboxContinuable.java:34) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.lambda$run0$0(SandboxContinuable.java:59) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:58) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:182) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:332) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$200(CpsThreadGroup.java:83) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:244) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:232) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at jenkins.securi
[JIRA] (JENKINS-54306) Move Chart Context Menu icon up in LoadRunner Performance Result/Transaction Summary reports
Title: Message Title Omer Kenan updated an issue Jenkins / JENKINS-54306 Move Chart Context Menu icon up in LoadRunner Performance Result/Transaction Summary reports Change By: Omer Kenan Summary: Move Chart Context Menu icon up in Load Runner LoadRunner Performance Result report /Transaction Summary reports Move Chart Context Menu icon up in LoadRunner Performance Result report /Transaction Summary reports. 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-46096) Pipeline stage view rendered at bottom of page, below build history
Title: Message Title Marcus Philip commented on JENKINS-46096 Re: Pipeline stage view rendered at bottom of page, below build history Sam Van Oort: I agree with the proper solution of the GUI layout. But there stops our agreement. Either you do not understand the problem, or this project has very strange policies for regressions. We do have wide screen (I have a retina screen, 2560 px wide!), but if you have a pipeline larger than around 6 stages with stage names that have long words, this problem still occurs. See and NoPipelineAtTop-NotOK.png In my projects the regression policy are: if a change cause major regressions, you revert it until it's fixed, unless this would cause even worse consequences. I think that is a sound policy. What do you think? Otherwise you are encouraging people to just solve their small use case and don't test for any regressions. This change was not properly tested with realistic test data and should never have been merged. Can you please admit that. I think the value of the change is small and the damage of the regression is large, so this should be an easy call. Maybe you should get a second opinion on this. Like you, my CSS skills are limited, but I think I can say that much that there is no easy fix due to how the html of the surrounding elements are structured. You would need to change in the test results plugin and or core. So reverting this is reasonable because it's likely to never get fixed (note that it's more than a year since I opened this). Add Comment This message was sent by A
[JIRA] (JENKINS-46096) Pipeline stage view rendered at bottom of page, below build history
Title: Message Title Marcus Philip edited a comment on JENKINS-46096 Re: Pipeline stage view rendered at bottom of page, below build history [~svanoort]: I agree with the proper solution of the GUI layout. But there stops our agreement. Either you do not understand the problem, or this project has very strange policies for regressions. # We _do_ have wide screen (I have a retina screen, 2560 px wide!), but if you have a pipeline larger than around 6 stages with stage names that have long words, this problem still occurs. See !PipelineAtBottom-NotOK.png|thumbnail! and [^ ! NoPipelineAtTop-NotOK.png ] |thumbnail! # In _my_ projects the regression policy are: if a change cause major regressions, you revert it until it's fixed, unless this would cause even worse consequences. I think that is a sound policy. What do you think? ** Otherwise you are encouraging people to just solve their small use case and don't test for any regressions. This change was not properly tested with realistic test data and should never have been merged. Can you please admit that. ** I think the value of the change is small and the damage of the regression is large, so this should be an easy call. ** Maybe you should get a second opinion on this. # Like you, my CSS skills are limited, but I think I can say that much that there is no easy fix due to how the html of the surrounding elements are structured. You would need to change in the test results plugin and or core. So reverting this is reasonable because it's likely to never get fixed (note that it's more than a year since I opened 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-50244) java.lang.AbstractMethodError: you must override the new overload of isApplicable in hudson.plugins.project_inheritance.projects.rebuild.RebuildValidatorSuppressor
Title: Message Title Erik Zivkovic commented on JENKINS-50244 Re: java.lang.AbstractMethodError: you must override the new overload of isApplicable in hudson.plugins.project_inheritance.projects.rebuild.RebuildValidatorSuppressor This is happening to one of my builds 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-46096) Pipeline stage view rendered at bottom of page, below build history
Title: Message Title Marcus Philip edited a comment on JENKINS-46096 Re: Pipeline stage view rendered at bottom of page, below build history [~svanoort]: I agree with the proper solution of the GUI layout. But there stops our agreement. Either you do not understand the problem, or this project has very strange policies for regressions. # We _do_ have wide screen (I have a retina screen, 2560 px wide!), but if you have a pipeline larger than around 6 stages with stage names that have long words, this problem still occurs. See !PipelineAtBottom-NotOK.png|thumbnail! and !NoPipelineAtTop-NotOK.png|thumbnail! # In _my_ projects the regression policy are: if a change cause major regressions, you revert it until it's fixed, unless this would cause even worse consequences. I think that is a sound policy. What do you think? ** Otherwise you are encouraging people to just solve their small use case and don't test for any regressions. This change was not properly tested with realistic test data and should never have been merged. Can you please admit that. ** I think the value of the change is small and the damage of the regression is large, so this should be an easy call. ** Maybe you should get a second opinion on this. # Like I tried to fix it properly, and like you, my CSS skills are limited, but I think I can say that much that there is no easy fix due to how the html of the surrounding elements are structured. You would need to change in the test results plugin and or core. So reverting this is reasonable because it's likely to never get fixed (note that it's more than a year since I opened 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-54308) Change "I" in "Average Transaction Response Time" to lowercase in Performance Project Report
Title: Message Title Omer Kenan created an issue Jenkins / JENKINS-54308 Change "I" in "Average Transaction Response Time" to lowercase in Performance Project Report Issue Type: Bug Assignee: Rolando-Mihai Vlad Attachments: ProjectPerformanceReport.PNG Components: hp-application-automation-tools-plugin Created: 2018-10-29 10:07 Labels: LoadRunner Priority: Minor Reporter: Omer Kenan Change "I" in "Average Transaction Response Time" to lowercase in Performance Project Report Only in Chrome "Time (Sec.) is overlap the graph. anyway low priority. Add Comment
[JIRA] (JENKINS-54309) Plugin builds Pull Requests on Jenkins Master, ignores Jenkins Workers
Title: Message Title Otmar Jatsch created an issue Jenkins / JENKINS-54309 Plugin builds Pull Requests on Jenkins Master, ignores Jenkins Workers Issue Type: Bug Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2018-10-29 10:13 Priority: Minor Reporter: Otmar Jatsch Hello, I have a Jenkins setup with one master and several workers. Master is configured to run zero builds. Whenever a build for a branch is done, it is properly run on one of the workers. Whenever a build for a pull request is done, it is run on the master. It fails there because some necessary tools are not installed on the master. Remora Add Comment
[JIRA] (JENKINS-54286) Unable to use variable tokens as build property values in Create Package in Declarative Script
Title: Message Title
Andrew Sumner commented on JENKINS-54286
Re: Unable to use variable tokens as build property values in Create Package in Declarative Script
I've released a new version as I didn't like the syntax for adding variables to a package - you'll need to install version 2.1.1 of the plugin. Syntax should be: ... = buildMasterCreatePackage(..., packageVariables: [}}{{variables: }}{{"hello=world\nsource=$BUILD_URL"}}{{]) Let me know how that goes. If this is not what you're after can you provide an example of what you're doing thanks. Also: I've just upgraded to BuildMaster 6.0.11 and there has been a change in the security model which is preventing access to the APIs - so this is just a friendly hint not to upgrade BuildMaster just 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-54286) Unable to use variable tokens as build property values in Create Package in Declarative Script
Title: Message Title
Andrew Sumner edited a comment on JENKINS-54286
Re: Unable to use variable tokens as build property values in Create Package in Declarative Script
I've released a new version as I didn't like the syntax for adding variables to a package - you'll need to install version 2.1.1 of the plugin.Syntax should be: {{ ... = buildMasterCreatePackage(..., packageVariables: [ }}{{ variables: }}{{ "hello=world\nsource=$BUILD_URL" }}{{ ]) }} {{Let me know how that goes. If this is not what you're after can you provide an example of what you're doing thanks.}}Also: I've just upgraded to BuildMaster 6.0.11 and there has been a change in the security model which is preventing access to the APIs - so this is just a friendly hint not to upgrade BuildMaster just 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Paul Holden commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 Yes, the current problem I'm experiencing is with 3.0.4 - see my previous comment for the stacktrace, under: Upgrading the plugin to 3.0.4 and triggering another build, with the JIRA issue number in the commit message and I now get the following exception in the Jenkins log, and no posted comment back in JIRA: As far as I know, the configuration for the plugin is correct. I haven't changed any of it since the plugin was last working (in 3.0.2). I've mailed you a screenshot of the configuration, in case that helps. 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-48787) Wrong Emulator Tool Path (EMULATOR_DIR)
Title: Message Title Tim Kist commented on JENKINS-48787 Re: Wrong Emulator Tool Path (EMULATOR_DIR) I'm having exactly the same problem. How did you fix it? What do you mean by you were missing the 'SDK Upgrade'? 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-53946) Bitbucket plugin unable to parse a Pull Request JSON Object
Title: Message Title Francisco A. R. Vivas commented on JENKINS-53946 Re: Bitbucket plugin unable to parse a Pull Request JSON Object I have discover that I was using Webhooks instead of Post Webhooks. If you have the same problem check both because they doesn't work properly when are both configured. I will close this issue. Sorry Roxana Muresan, I will vote yours if you create a new one with better information than mine. 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-53946) Bitbucket plugin unable to parse a Pull Request JSON Object
Title: Message Title Francisco A. R. Vivas closed an issue as Fixed It is not a correct issue. Jenkins / JENKINS-53946 Bitbucket plugin unable to parse a Pull Request JSON Object Change By: Francisco A. R. Vivas 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-54310) java.io.IOException: Stream is closed when the CLI has not read entirely the input
Title: Message Title Francisco Fernández created an issue Jenkins / JENKINS-54310 java.io.IOException: Stream is closed when the CLI has not read entirely the input Issue Type: Task Assignee: Francisco Fernández Components: cli Created: 2018-10-29 10:38 Priority: Minor Reporter: Francisco Fernández Class hudson.cli.CLI opens several threads for different purposes. One is the "input reader" to store internally the standard input. In case of an abrupt or quick ending of the CLI command (-auth option not provided when it's necessary, for example) and the standard input is large, it might not be entirely read, throwing an unexpected warning message and error trace: WARNING: null java.io.IOException: Stream is closed at sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.checkError(HttpURLConnection.java:3530) at sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.write(HttpURLConnection.java:3504) at java.io.DataOutputStream.writeInt(DataOutputStream.java:197) at hudson.cli.PlainCLIProtocol$EitherSide.send(PlainCLIProtocol.java:180) at hudson.cli.PlainCLIProtocol$EitherSide.send(PlainCLIProtocol.java:187) at hudson.cli.PlainCLIProtocol$EitherSide$1.write(PlainCLIProtocol.java:207) at hudson.cli.CLI$5.run(CLI.java:721) Although the CLI ends with no error, this message should not be displayed since it's indicating an undesired situation.
[JIRA] (JENKINS-54310) java.io.IOException: Stream is closed when the CLI has not read entirely the input
Title: Message Title Francisco Fernández updated an issue Jenkins / JENKINS-54310 java.io.IOException: Stream is closed when the CLI has not read entirely the input Change By: Francisco Fernández 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-54310) java.io.IOException: Stream is closed when the CLI has not read entirely the input
Title: Message Title Francisco Fernández started work on JENKINS-54310 Change By: Francisco Fernández 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-53946) Bitbucket plugin unable to parse a Pull Request JSON Object
Title: Message Title Roxana Muresan commented on JENKINS-53946 Re: Bitbucket plugin unable to parse a Pull Request JSON Object Hi Francisco A. R. Vivas, No problem. In the mean time I found out some more details on this. Just for clarification, this issue appears when using the Hook "Post-Receive WebHooks" on Bitbucket (not the normal Post Webhook) and the Bitbucket-Plugin for Jenkins. Now I'm using a normal Post Webhook on Bitbucket but I stumbled on a different issue with the Bitbucket-Plugin for Jenkins (see https://issues.jenkins-ci.org/browse/JENKINS-54272 and https://issues.jenkins-ci.org/browse/JENKINS-49177). For this issue there are already 3 PRs open on github so a fix might be available soon.. hopefully. Best regards, 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-54310) java.io.IOException: Stream is closed when the CLI has not read entirely the input
Title: Message Title Francisco Fernández updated JENKINS-54310 Jenkins / JENKINS-54310 java.io.IOException: Stream is closed when the CLI has not read entirely the input Change By: Francisco Fernández 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-54311) Create user with . in name doesn't work
Title: Message Title
Rick Löhlefink created an issue
Jenkins / JENKINS-54311
Create user with . in name doesn't work
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2018-10-29 11:12
Environment:
Jenkins 2.148
Priority:
Minor
Reporter:
Rick Löhlefink
Creating a user (via Manage Jenkins -> Manage Users -> Create User) with a name containing a dot (".") returns HTTP/1.1 200 but does not create user and remains on same page. I can not find this behavior documented anywhere, and in an older Jenkins version I was able to create users with dots in their name. Currently I have several users with dots in their name, but I can no longer create new ones.
Add Comment
[JIRA] (JENKINS-54041) EC2 Plugin no longer able to start build slaves
Title: Message Title David Goate reopened an issue On latest version (1.41) I still get the warning: WARNING: Failed to load org.jenkinsci.plugins.github.pullrequest.extra.GitHubPRLabelUnblockQueueCondition$DescriptorImpl java.lang.NoClassDefFoundError: org/jenkinsci/plugins/blockqueuedjob/condition/BlockQueueCondition$BlockQueueConditionDescriptor Reverting back to 1.39 now also gives: Connecting to 10.1.1.90 on port 22, with timeout 1. Oct 29, 2018 11:19:39 AM WARNING org.jvnet.hudson.annotation_indexer.Index$2$1 fetchFailed to load org.jenkinsci.plugins.github.pullrequest.extra.GitHubPRLabelUnblockQueueCondition$DescriptorImpl java.lang.ClassNotFoundException: org.jenkinsci.plugins.blockqueuedjob.condition.BlockQueueCondition$BlockQueueConditionDescriptor at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1374) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1327) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1080) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) Currently none of my Jenkins builds will run. Do you think this is related to this plugin or a different issue. Jenkins / JENKINS-54041 EC2 Plugin no longer able to start build slaves Change By: David Goate Resolution: Fixed Status: Closed Reopened
[JIRA] (JENKINS-54301) silently close uft dispatcher queue on Jenkins shutdown
Title: Message Title Yuri Guller closed an issue as Fixed Jenkins / JENKINS-54301 silently close uft dispatcher queue on Jenkins shutdown Change By: Yuri Guller Status: Resolved 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-54301) silently close uft dispatcher queue on Jenkins shutdown
Title: Message Title Yuri Guller resolved as Fixed Jenkins / JENKINS-54301 silently close uft dispatcher queue on Jenkins shutdown Change By: Yuri Guller 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-54300) silently close uft dispatcher queue on Jenkins shutdown
Title: Message Title Yuri Guller closed an issue as Duplicate Jenkins / JENKINS-54300 silently close uft dispatcher queue on Jenkins shutdown Change By: Yuri Guller Status: Open Closed 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-54312) Chane LR Script Report to LR VuGen Report
Title: Message Title Omer Kenan created an issue Jenkins / JENKINS-54312 Chane LR Script Report to LR VuGen Report Issue Type: Bug Assignee: Rolando-Mihai Vlad Attachments: VuGenReport.PNG Components: hp-application-automation-tools-plugin Created: 2018-10-29 11:41 Labels: LoadRunner Priority: Minor Reporter: Omer Kenan Change "LR Script Report" to "LR VuGen Report" or "VuGen Script Report" Add Comment
[JIRA] (JENKINS-47566) Unexpected end of ZLIB input stream on permission errors
Title: Message Title Simon Martineau reopened an issue The problem that should be resolved, as described by the person who initially opened this ticket is the highly misleading error message. This has to be fixed. I wasted a lot of time, exactly as the person who initially open this ticket. Jenkins / JENKINS-47566 Unexpected end of ZLIB input stream on permission errors Change By: Simon Martineau Resolution: Not A Defect 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-48787) Wrong Emulator Tool Path (EMULATOR_DIR)
Title: Message Title Tim Kist edited a comment on JENKINS-48787 Re: Wrong Emulator Tool Path (EMULATOR_DIR) I'm having exactly the same problem. How did you fix it? What do you mean by you were missing the 'SDK Upgrade'? No worries. Did `./sdkmanager --update` and that's worked :) 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-50244) java.lang.AbstractMethodError: you must override the new overload of isApplicable in hudson.plugins.project_inheritance.projects.rebuild.RebuildValidatorSuppressor
Title: Message Title
Erik Zivkovic commented on JENKINS-50244
Re: java.lang.AbstractMethodError: you must override the new overload of isApplicable in hudson.plugins.project_inheritance.projects.rebuild.RebuildValidatorSuppressor
I solved my issue by removing a redundant "agent any":
pipeline {
agent any
stages {
stage('Setup') {
// agent any // Removed this line
steps {
sh 'xxx'
}
}
}
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-54308) Change "I" in "Average Transaction Response Time" to lowercase in Performance Project Report
Title: Message Title Rolando-Mihai Vlad resolved as Fixed Jenkins / JENKINS-54308 Change "I" in "Average Transaction Response Time" to lowercase in Performance Project Report Change By: Rolando-Mihai Vlad Status: Open 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-54312) Change LR Script Report to LR VuGen Report
Title: Message Title Rolando-Mihai Vlad resolved as Fixed Jenkins / JENKINS-54312 Change LR Script Report to LR VuGen Report Change By: Rolando-Mihai Vlad Status: Open 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-54312) Change LR Script Report to LR VuGen Report
Title: Message Title Rolando-Mihai Vlad updated an issue Jenkins / JENKINS-54312 Change LR Script Report to LR VuGen Report Change By: Rolando-Mihai Vlad Summary: Chane Change LR Script Report to LR VuGen Report 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-54306) Move Chart Context Menu icon up in LoadRunner Performance Result/Transaction Summary reports
Title: Message Title Rolando-Mihai Vlad resolved as Fixed Jenkins / JENKINS-54306 Move Chart Context Menu icon up in LoadRunner Performance Result/Transaction Summary reports Change By: Rolando-Mihai Vlad Status: Open 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-54306) Move Chart Context Menu icon up in LoadRunner Performance Result/Transaction Summary reports
Title: Message Title Rolando-Mihai Vlad commented on JENKINS-54306 Re: Move Chart Context Menu icon up in LoadRunner Performance Result/Transaction Summary reports The html is generated from Analysis, thus it is not a plugin issues. 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-52857) Cannot find git-lfs when it is not installed in /usr/bin/
Title: Message Title Ilya Evseenkov assigned an issue to Ilya Evseenkov Jenkins / JENKINS-52857 Cannot find git-lfs when it is not installed in /usr/bin/ Change By: Ilya Evseenkov Assignee: Ilya Evseenkov 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-2111) removing a job (including multibranch/org folder branches/repos) does not remove the workspace
Title: Message Title Tyler Smith commented on JENKINS-2111 Re: removing a job (including multibranch/org folder branches/repos) does not remove the workspace I tried your experimental build and it worked for the slave agents. When the, apparently scheduled, clean up occurred, it removed and @tmp folders from all the slave agents. However, I still have a @script folder on my Jenkins master. Is that the responsibility of another component to delete? 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-52857) Cannot find git-lfs when it is not installed in /usr/bin/
Title: Message Title Ilya Evseenkov commented on JENKINS-52857 Re: Cannot find git-lfs when it is not installed in /usr/bin/ Hi Mark, I`m using core 2.107.3 and git plugin 3.9.1. My Linux node runs CentOS 6.7. When I do "git --version" on it, I get "git version 1.7.1". I installed another git into "/anotherfs/git-2.19.0/" and added it "Manage Jenkins->Global Tools configuration->git". I didn`t re-configured PATH, "which git" still point "/usr/bin/git" After that, I added git lfs like "/anotherfs/git-2.19.0/bin/git lfs install". Command "/anotherfs/git-2.19.0/bin/git-lfs version" shows "git-lfs/2.4.0 (GitHub; linux amd64; go 1.8.3; git 1a98fa5c)" After that I`m configuring my Pipeline job with Jenkinsfile and "Git LFS pull after checkout". It works on master and get Jenkinsfile, but at node: hudson.plugins.git.GitException: Command "/anotherfs/git-2.19.0/bin/git checkout -f f52336bc40265a1f8703eac49b89cd6b7a778df7" returned status code 128: stdout: stderr: git-lfs filter-process: git-lfs: command not found It happens, because "/anotherfs/git-2.19.0/bin/" is not in the PATH. If I add/overwrite PATH at node configuration page, git plugin ignores it and use OS version of PATH. If I add "PATH" from console, it works too, Hope. it is enough ) 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-54021) Pulling alpine image fails when using custom registry for build image.
Title: Message Title Kimon Hoffmann commented on JENKINS-54021 Re: Pulling alpine image fails when using custom registry for build image. Further investigation suggests that the root cause for this issue is the behavior described in JENKINS-33985 and thus should probably be solved by JENKINS-51406. 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-54299) Jenkins failed to start after updating pluins and restart
Title: Message Title Devin Nusbaum commented on JENKINS-54299 Re: Jenkins failed to start after updating pluins and restart Sam Tang This kind of question is much better suited for the jenkinsci-users mailing list or IRC, see https://jenkins.io/mailing-lists/ and https://jenkins.io/chat/. Based on CannotResolveClassException: hudson.security.ProjectMatrixAuthorizationStrategy, it looks like you do not have the Matrix Authorization Strategy Plugin installed, or maybe your version is too old. I would post your question on the mailing list or ask in IRC, and include the output of `ls -l $JENKINS_HOME/plugins` so we can see what plugins are installed on your instance. If matrix-auth is not listed in that directory, then I would manually download https://updates.jenkins.io/2.73/latest/matrix-auth.hpi and copy into that directory and try to restart. I would also make sure to take a backup of your current Jenkins Home directory before you lose any additional data or configuration. 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-2111) removing a job (including multibranch/org folder branches/repos) does not remove the workspace
Title: Message Title Tyler Smith edited a comment on JENKINS-2111 Re: removing a job (including multibranch/org folder branches/repos) does not remove the workspace I tried your experimental build and it worked for the slave agents. When the, apparently scheduled, clean up occurred, it removed and @tmp folders from all the slave agents. However, I still have a @script folder on my Jenkins master. Is that the responsibility of another component to delete? Edit:Nevermind. I recently updated the subversion plugin which enabled lightweight checkouts and no longer creates @script folders, so it is a non-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-54313) null pointer com.cloudbees.jenkins.plugins.kubernetes_credentials_provider.SecretUtils.getKeyName(SecretUtils.java:186)
Title: Message Title James Rawlings created an issue Jenkins / JENKINS-54313 null pointer com.cloudbees.jenkins.plugins.kubernetes_credentials_provider.SecretUtils.getKeyName(SecretUtils.java:186) Issue Type: Bug Assignee: James Nord Attachments: exception.log Components: kubernetes-credentials-provider-plugin Created: 2018-10-29 13:35 Environment: v0.9 Priority: Critical Reporter: James Rawlings Error when a secret doesn't have an annotation. As a workaround I added a dummy annotation to all my secrets, i.e. kubectl annotate secret --all jenkins.io/foo=bar Issue seems to be here not checking that annotations can be null https://github.com/jenkinsci/kubernetes-credentials-provider-plugin/blob/82b67a06d24b8cc500856e46f3328337e58a63ca/src/main/java/com/cloudbees/jenkins/plugins/kubernetes_credentials_provider/SecretUtils.java#L186
[JIRA] (JENKINS-54313) null pointer com.cloudbees.jenkins.plugins.kubernetes_credentials_provider.SecretUtils.getKeyName(SecretUtils.java:186)
Title: Message Title James Rawlings commented on JENKINS-54313 Re: null pointer com.cloudbees.jenkins.plugins.kubernetes_credentials_provider.SecretUtils.getKeyName(SecretUtils.java:186) PR with a fix submitted https://github.com/jenkinsci/kubernetes-credentials-provider-plugin/pull/20 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-54275) (Google Apps/SAML) org.pac4j.saml.exceptions.SAMLException: Authentication issue instant is too old
Title: Message Title Jonas Liljestrand commented on JENKINS-54275 Re: (Google Apps/SAML) org.pac4j.saml.exceptions.SAMLException: Authentication issue instant is too old Hi, Me and my team is also facing this issue, we do not use HTTP-POST binding but can see the same issue in the log. Below I provide the same log output but with some more details on the dates Oct 29, 2018 11:20:28 AM FINEST org.pac4j.saml.sso.impl.SAML2DefaultResponseValidator isDateValid interval=86400,before=2018-10-29T11:22:28.841Z,after=2018-10-28T11:18:28.841Z,issueInstant=2018-10-25T14:39:22.000Z Oct 29, 2018 11:20:28 AM SEVERE org.pac4j.saml.sso.impl.SAML2DefaultResponseValidator validateSamlSSOResponse Current assertion validation failed, continue with the next one org.pac4j.saml.exceptions.SAMLException: Authentication issue instant is too old or in the future at org.pac4j.saml.sso.impl.SAML2DefaultResponseValidator.validateAuthenticationStatements(SAML2DefaultResponseValidator.java:620) at org.pac4j.saml.sso.impl.SAML2DefaultResponseValidator.validateAssertion(SAML2DefaultResponseValidator.java:393) at org.pac4j.saml.sso.impl.SAML2DefaultResponseValidator.validateSamlSSOResponse(SAML2DefaultResponseValidator.java:302) at org.pac4j.saml.sso.impl.SAML2DefaultResponseValidator.validate(SAML2DefaultResponseValidator.java:138) at org.pac4j.saml.sso.impl.SAML2WebSSOMessageReceiver.receiveMessage(SAML2WebSSOMessageReceiver.java:77) at org.pac4j.saml.sso.impl.SAML2WebSSOProfileHandler.receive(SAML2WebSSOProfileHandler.java:35) 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 u
[JIRA] (JENKINS-54026) Database maybe alredy in use "Server is running"(pipeline+maven)
Title: Message Title Cyrille Le Clerc commented on JENKINS-54026 Re: Database maybe alredy in use "Server is running"(pipeline+maven) FYI I'm working at optimising the database queries to significantly reduce the workload on the database. This optimisation is very likely to reduce the need of concurrent connections to the database. 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-54314) LR 5.6 jenkins features break backwards compatibility
Title: Message Title Rolando-Mihai Vlad updated an issue Jenkins / JENKINS-54314 LR 5.6 jenkins features break backwards compatibility Change By: Rolando-Mihai Vlad Labels: LoadRunner 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-44772) User Scoped credentials are not used by the "withCredentials" pipeline step
Title: Message Title John Zerbe commented on JENKINS-44772 Re: User Scoped credentials are not used by the "withCredentials" pipeline step Are there any updates for this 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-54314) LR 5.6 jenkins features break backwards compatibility
Title: Message Title Rolando-Mihai Vlad created an issue Jenkins / JENKINS-54314 LR 5.6 jenkins features break backwards compatibility Issue Type: Bug Assignee: Rolando-Mihai Vlad Components: hp-application-automation-tools-plugin Created: 2018-10-29 13:53 Priority: Critical Reporter: Rolando-Mihai Vlad 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-54315) Instances sometimes stay sorphaned:stale due to AWS API nature - eventual consistency
Title: Message Title Gavriel Fishel created an issue Jenkins / JENKINS-54315 Instances sometimes stay sorphaned:stale due to AWS API nature - eventual consistency Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2018-10-29 14:04 Priority: Minor Reporter: Gavriel Fishel 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-54315) Instances sometimes stay disconnected
Title: Message Title
Gavriel Fishel updated an issue
Jenkins / JENKINS-54315
Instances sometimes stay disconnected
Change By:
Gavriel Fishel
Summary:
Instances sometimes stay sorphaned:stale due to AWS API nature - eventual consistency disconnected
Sometimes when ec2-plugin spins an instance it will stay disconnected forever.The instance will not receive any tags on AWS.Cloudtrail on AWS shows this errocode: {code:java}{"eventVersion": "1.05","userIdentity": {"type": "IAMUser","principalId": "AIDAJGXAEWBUSKS3WYALG","arn": "arn:aws:iam::802760723056:user/_nsof_int_jenkins","accountId": "802760723056","accessKeyId": "AKIAJMCV6V36FPFYJ2WA","userName": "_nsof_int_jenkins"},"eventTime": "2018-10-25T17:31:16Z","eventSource": "ec2.amazonaws.com","eventName": "DescribeInstances","awsRegion": "us-east-1","sourceIPAddress": "52.70.50.139","userAgent": "aws-sdk-java/1.11.403 Linux/4.4.0-1069-aws OpenJDK_64-Bit_Server_VM/25.181-b13 java/1.8.0_181 groovy/2.4.11","errorCode": "Client.InvalidInstanceID.NotFound","errorMessage": "The instance ID 'i-05a000703b7084e53' does not exist","requestParameters": {"instancesSet": {"items": [{"instanceId": "i-05a000703b7084e53"}]},"filterSet": {}},"responseElements": null,"requestID": "2d9f3866-19d7-482c-a4cb-057c0e6c","eventID": "cb5da0a7-15f7-4360-979e-fff11effa285","eventType": "AwsApiCall","recipientAccountId": "802760723056"}{code} After chatting with AWS support they say it's due to the nature of their API's [eventual consistency|https://docs.aws.amazon.com/AWSEC2/latest/APIReference/query-api-troubleshooting.html#eventual-consistency]
Add Comment
[JIRA] (JENKINS-54315) Instances sometimes stay disconnected
Title: Message Title
Gavriel Fishel updated an issue
Jenkins / JENKINS-54315
Instances sometimes stay disconnected
Change By:
Gavriel Fishel
Sometimes when ec2-plugin spins an instance it will stay disconnected forever and will never be used . Jenkins log shows this error:{code:java}com.amazonaws.services.ec2.model.AmazonEC2Exception: The instance will ID 'i-05a000703b7084e53' does not receive any tags on AWS exist (Service: AmazonEC2; Status Code: 400; Error Code: InvalidInstanceID . NotFound; Request ID: 2d9f3866-19d7-482c-a4cb-057c0e6c) {code} Cloudtrail on AWS shows this errocode: {code:java}{"eventVersion": "1.05","userIdentity": {"type": "IAMUser","principalId": "AIDAJGXAEWBUSKS3WYALG","arn": "arn:aws:iam::802760723056:user/_nsof_int_jenkins","accountId": "802760723056","accessKeyId": "AKIAJMCV6V36FPFYJ2WA","userName": "_nsof_int_jenkins"},"eventTime": "2018-10-25T17:31:16Z","eventSource": "ec2.amazonaws.com","eventName": "DescribeInstances","awsRegion": "us-east-1","sourceIPAddress": "52.70.50.139","userAgent": "aws-sdk-java/1.11.403 Linux/4.4.0-1069-aws OpenJDK_64-Bit_Server_VM/25.181-b13 java/1.8.0_181 groovy/2.4.11","errorCode": "Client.InvalidInstanceID.NotFound","errorMessage": "The instance ID 'i-05a000703b7084e53' does not exist","requestParameters": {"instancesSet": {"items": [{"instanceId": "i-05a000703b7084e53"}]},"filterSet": {}},"responseElements": null,"requestID": "2d9f3866-19d7-482c-a4cb-057c0e6c","eventID": "cb5da0a7-15f7-4360-979e-fff11effa285","eventType": "AwsApiCall","recipientAccountId": "802760723056"}{code} After chatting with AWS support they say it's due to the nature of their API's [eventual consistency|https://docs.aws.amazon.com/AWSEC2/latest/APIReference/query-api-troubleshooting.html#eventual-consistency] There were API calls before the instance spawned on AWS.Is there a way to add a retry in these cases?
Add Comment
[JIRA] (JENKINS-54315) Instances sometimes stay disconnected
Title: Message Title
Gavriel Fishel updated an issue
Jenkins / JENKINS-54315
Instances sometimes stay disconnected
Change By:
Gavriel Fishel
Sometimes when ec2-plugin spins up an instance it will stay disconnected and will never be used. The error on Jenkins log shows this error :{code:java}com.amazonaws.services.ec2.model.AmazonEC2Exception: The instance ID 'i-05a000703b7084e53' does not exist (Service: AmazonEC2; Status Code: 400; Error Code: InvalidInstanceID.NotFound; Request ID: 2d9f3866-19d7-482c-a4cb-057c0e6c){code}Cloudtrail on AWS shows this errocode: {code:java}{"eventVersion": "1.05","userIdentity": {"type": "IAMUser","principalId": "AIDAJGXAEWBUSKS3WYALG","arn": "arn:aws:iam::802760723056:user/_nsof_int_jenkins","accountId": "802760723056","accessKeyId": "AKIAJMCV6V36FPFYJ2WA","userName": "_nsof_int_jenkins"},"eventTime": "2018-10-25T17:31:16Z","eventSource": "ec2.amazonaws.com","eventName": "DescribeInstances","awsRegion": "us-east-1","sourceIPAddress": "52.70.50.139","userAgent": "aws-sdk-java/1.11.403 Linux/4.4.0-1069-aws OpenJDK_64-Bit_Server_VM/25.181-b13 java/1.8.0_181 groovy/2.4.11","errorCode": "Client.InvalidInstanceID.NotFound","errorMessage": "The instance ID 'i-05a000703b7084e53' does not exist","requestParameters": {"instancesSet": {"items": [{"instanceId": "i-05a000703b7084e53"}]},"filterSet": {}},"responseElements": null,"requestID": "2d9f3866-19d7-482c-a4cb-057c0e6c","eventID": "cb5da0a7-15f7-4360-979e-fff11effa285","eventType": "AwsApiCall","recipientAccountId": "802760723056"}{code} After chatting with AWS support they say it's due to the nature of their API's [eventual consistency|https://docs.aws.amazon.com/AWSEC2/latest/APIReference/query-api-troubleshooting.html#eventual-consistency] There were API calls were made before the instance spawned on AWS.Is there a way to add a retry in these cases?
Add Comment
[JIRA] (JENKINS-54315) Instances sometimes stay disconnected
Title: Message Title
Gavriel Fishel updated an issue
Jenkins / JENKINS-54315
Instances sometimes stay disconnected
Change By:
Gavriel Fishel
Sometimes when ec2-plugin spins up an instance it will stay disconnected and will never be used. The error on Jenkins log:{code:java} INFO: Started provisioning js-ubuntu (ami-d7bhbda9) from ec2-mng-jenkins-slave with 1 executors. Remaining excess workload: 0 Oct 25, 2018 8:31:18 PM hudson.slaves.NodeProvisioner$2 run WARNING: Unexpected exception encountered while provisioning agent js-ubuntu (ami-d7bhbda9) com.amazonaws.services.ec2.model.AmazonEC2Exception: The instance ID 'i-05a000703b7084e53' does not exist (Service: AmazonEC2; Status Code: 400; Error Code: InvalidInstanceID.NotFound; Request ID: 2d9f3866-19d7-482c-a4cb-057c0e6c) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleErrorResponse(AmazonHttpClient.java:1658) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1322) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1072) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:745) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:719) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:701) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:669) at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:651) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:515) at com.amazonaws.services.ec2.AmazonEC2Client.doInvoke(AmazonEC2Client.java:17597) at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:17566) at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:17555) at com.amazonaws.services.ec2.AmazonEC2Client.executeDescribeInstances(AmazonEC2Client.java:8680) at com.amazonaws.services.ec2.AmazonEC2Client.describeInstances(AmazonEC2Client.java:8651) at hudson.plugins.ec2.CloudHelper.getInstance(CloudHelper.java:47) at hudson.plugins.ec2.EC2Cloud$1.call(EC2Cloud.java:603) at hudson.plugins.ec2.EC2Cloud$1.call(EC2Cloud.java:586) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) {code}Cloudtrail on AWS shows this errocode: {code:java}{"eventVersion": "1.05","userIdentity": {"type": "IAMUser","principalId": "AIDAJGXAEWBUSKS3WYALG","arn": "arn:aws:iam::802760723056:user/_nsof_int_jenkins","accountId": "802760723056","accessKeyId": "AKIAJMCV6V36FPFYJ2WA","
[JIRA] (JENKINS-54316) Update plugins defined in package-config.yml of CWP
Title: Message Title Michael Werner created an issue Jenkins / JENKINS-54316 Update plugins defined in package-config.yml of CWP Issue Type: New Feature Assignee: Oleg Nenashev Components: custom-war-packager, incrementals-tools Created: 2018-10-29 14:19 Priority: Minor Reporter: Michael Werner It would be nice if the incrementals-tool could update the plugins defined in the package-config.yml of the custom war packager project. Add Comment This message was sent by Atlassian Jira (v7.11.2#71100
[JIRA] (JENKINS-54275) (Google Apps/SAML) org.pac4j.saml.exceptions.SAMLException: Authentication issue instant is too old
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-54275 Re: (Google Apps/SAML) org.pac4j.saml.exceptions.SAMLException: Authentication issue instant is too old This exception it is supposed to be captured in 1.1.0 and transformed in a BadCredentials here https://github.com/jenkinsci/saml-plugin/blob/master/src/main/java/org/jenkinsci/plugins/saml/SamlProfileWrapper.java#L52-L60 I have to test it locally, but it is weird, Which Jenkins core version do you use? There is a workaround for this it is to decrease "Advanced Configuration/Maximum Session Lifetime" to a lower value than your token validity, then set "Maximum Authentication Lifetime" near to your token validity. Another workaround is to set "Advanced Configuration/Force Authentication" but this will as for login everytime the session expires. 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-54316) Update plugins defined in package-config.yml of CWP
Title: Message Title Oleg Nenashev commented on JENKINS-54316 Re: Update plugins defined in package-config.yml of CWP That's for sure. I would also like Dependabot to support such format or standard Jenkins BOM from JEP-309 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-54316) Update plugins defined in package-config.yml of CWP
Title: Message Title Oleg Nenashev commented on JENKINS-54316 Re: Update plugins defined in package-config.yml of CWP BTW, using pom.xml as a plugin list input for CWP is one of the possible workarounds for 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-54317) change NAT timeout
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-54317 change NAT timeout Change By: Dominik Bartholdi Summary: increase change NAT timeout 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-54317) increase NAT timeout
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-54317 increase NAT timeout Issue Type: Improvement Assignee: R. Tyler Croy Components: evergreen Created: 2018-10-29 14:42 Priority: Minor Reporter: Dominik Bartholdi As I'm following the development quite a bit, I noticed you are using an official AWS AMI as agent. I just want to make you aware of an issue I have been debugging with cloudbees stuff for a couple of months until Yoann Dubreuil finally found the issue... I was having issues to execute long running DB update tasks from within jenkins, everytime the tasks ran into a timeout... This was caused by a timeout on the NAT gateway. You can read more about it here: http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-nat-gateway.html#nat-gateway-troubleshooting-timeout http://docs.aws.amazon.com/redshift/latest/mgmt/connecting-firewall-guidance.html#connecting-firewall-guidance.change-tcpip-settings The issue could finally be fixed with the following settings (placed in a file in `/etc/sysctl.d`): net.ipv4.tcp_keepalive_time=200 net.ipv4.tcp_keepalive_intvl=200 net.ipv4.tcp_keepalive_probes=5 As I'm very interested in using evergreen myself one day, I would love to see this find place in the AWS evergreen setup.
[JIRA] (JENKINS-54302) silently close octane log (SDK managed)
Title: Message Title Yuri Guller started work on JENKINS-54302 Change By: Yuri Guller 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-54275) (Google Apps/SAML) org.pac4j.saml.exceptions.SAMLException: Authentication issue instant is too old
Title: Message Title Jonas Liljestrand commented on JENKINS-54275 Re: (Google Apps/SAML) org.pac4j.saml.exceptions.SAMLException: Authentication issue instant is too old I'm using Jenkins core 2.138.2 So are you saying that this issue occurs because the plugin is configured to require fresh provider sessions? 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-54316) Update plugins defined in package-config.yml of CWP
Title: Message Title Michael Werner commented on JENKINS-54316 Re: Update plugins defined in package-config.yml of CWP Is there an example? I tried it and got an error, that the CasC plugin is not defined within the plugins block. 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-54275) (Google Apps/SAML) org.pac4j.saml.exceptions.SAMLException: Authentication issue instant is too old
Title: Message Title Jonas Liljestrand commented on JENKINS-54275 Re: (Google Apps/SAML) org.pac4j.saml.exceptions.SAMLException: Authentication issue instant is too old I can also add that signing out from google and signing in again "solves" the problem. We have around 30 users and this has been the solution for them all. 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-54316) Update plugins defined in package-config.yml of CWP
Title: Message Title Oleg Nenashev commented on JENKINS-54316 Re: Update plugins defined in package-config.yml of CWP > Is there an example? I tried it and got an error, that the CasC plugin is not defined within the plugins block. Thanks for testing! Likely it is a bug then (CWP checks only the config metadata for JCasC instead of all inputs). Could you please submit it as a separate ticket? 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-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title fisnik hajredini updated an issue Jenkins / JENKINS-54304 Jobs in parallel dont display the variant they are running. Change By: fisnik hajredini This issue manifested itself since October 15th.When a build is triggered and it runs on multiple slaves parallely, you normally get an output for each line corresponding to the variant its running. Since a Jenkins update on October 15th, this has not been the case. This is making it harder for us to debug the issues on the variants/slaves, as we don't know on which variant the issue is being manifested. _NOTE:_Although unrelated, this issue was manifested together with another bug which doesn't allow an anonymous user to view jobs, even if logged in as a non-admin. Only users with admin privileges are allowed to view the logs. That issue has been found on your backlog. https://issues.jenkins-ci.org/browse/JENKINS-54031 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Hal Deadman updated an issue Jenkins / JENKINS-54131 "Failed to parse changelog" in JIRA plugin 3.0.3 Change By: Hal Deadman Attachment: screenshot-1.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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Hal Deadman commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 We are getting this warning when we validate settings, even though Thread Executor Size is 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-54317) change NAT timeout
Title: Message Title
Dominik Bartholdi updated an issue
Jenkins / JENKINS-54317
change NAT timeout
Change By:
Dominik Bartholdi
As I'm following the development quite a bit, I noticed you are using an official AWS AMI as agent.I just want to make you aware of an issue I have been debugging with cloudbees stuff for a couple of months until Yoann Dubreuil finally found the issue...I was having issues to execute long running DB update tasks from within jenkins, everytime the tasks ran into a timeout...This was caused by a timeout on the NAT gateway.You can read more about it here: * [http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-nat-gateway.html#nat-gateway-troubleshooting-timeout] * [http://docs.aws.amazon.com/redshift/latest/mgmt/connecting-firewall-guidance.html#connecting-firewall-guidance.change-tcpip-settings]The issue could finally be fixed with the following settings (placed in a file in `/etc/sysctl.d`):{code:java}net.ipv4.tcp_keepalive_time=200 net.ipv4.tcp_keepalive_intvl=200 net.ipv4.tcp_keepalive_probes=5{code} As I'm very interested in using evergreen myself one day, I would love to see this find place in the AWS evergreen setup. Here is an other article describing the same issue: [https://www.vertica.com/blog/configuring-tcp-idle-settings-long-running-idle-sessions/]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
