[JIRA] (JENKINS-34617) Make extended-choice-parameter-plugin pipeline compatibility easier
Title: Message Title Craig Rodrigues edited a comment on JENKINS-34617 Re: Make extended-choice-parameter-plugin pipeline compatibility easier I have a patch which allows you to specify ***extendedChoice* in the paramters block of a declarative pipeline. https://github.com/jenkinsci/extended-choice-parameter-plugin/pull/25 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34617) Make extended-choice-parameter-plugin pipeline compatibility easier
Title: Message Title Craig Rodrigues commented on JENKINS-34617 Re: Make extended-choice-parameter-plugin pipeline compatibility easier I have a patch which allows you to specify **extendedChoice in the paramters block of a declarative pipeline. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56326) Git fetch in a later Pipeline stage fails when master received new revisions in the meantime
Title: Message Title Raphael Reitzig commented on JENKINS-56326 Re: Git fetch in a later Pipeline stage fails when master received new revisions in the meantime We have the following potpourri of Git versions: master: git version 2.17.1 (Ubuntu 18.04) agent A: git version 2.11.0 (Debian stretch) agent B: git version 2.7.4 (Ubuntu 16.04) agent C: git version 2.7.4 (Ubuntu 16.04) agent D: git version 2.7.4 (Ubuntu 16.04) agent E: git version 2.17.1 (Ubuntu 18.04) The error occurred on agent D. Parallel stages on agents A, C, and E completed successfully. Actually, C and D are the same host which appears in the executor list twice (with different names). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56375) custom jnlp not working
Title: Message Title
Carlos Sanchez commented on JENKINS-56375
Re: custom jnlp not working
check the logs for entries {{containers=[ContainerTemplate ... }} https://github.com/jenkinsci/kubernetes-plugin/#debugging
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55096) can not override jnlp container
Title: Message Title Carlos Sanchez commented on JENKINS-55096 Re: can not override jnlp container suryatej yaramada your pod is failing, you need to check why Agent is not connected after 30 seconds so it is probably using an old agent or another one you have with the same label Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56356) clif doesn't handle no jar gracefully
Title: Message Title Bruno Dillenseger commented on JENKINS-56356 Re: clif doesn't handle no jar gracefully This occurs when you forget to select a file. It may also occur when you first select a file and Jenkins' auto-refresh is activated: if auto-refresh actually happens, then the file selection disappears and the same exception is thrown. This is really not graceful indeed, but the work-around is simple: just go back to the previous page in your browser and select a file. Also consider deactivating auto-refresh. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Wadeck Follonier commented on JENKINS-56114 Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy) Jeremy Kam That's really appreciated to receive such feedback, thank you The correction will normally be part of the next weekly (~2.168) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34617) Make extended-choice-parameter-plugin pipeline compatibility easier
Title: Message Title Craig Rodrigues edited a comment on JENKINS-34617 Re: Make extended-choice-parameter-plugin pipeline compatibility easier I have a patch which allows you to specify ***extendedChoice* in the paramters parameters block of a declarative pipeline. [ https://github.com/jenkinsci/extended-choice-parameter-plugin/pull/25 ] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56383) Blue Ocean pipeline UI stopped appearing after plugin upgrade
Title: Message Title Jon B created an issue Jenkins / JENKINS-56383 Blue Ocean pipeline UI stopped appearing after plugin upgrade Issue Type: Bug Assignee: Unassigned Attachments: image-2019-03-04-03-41-15-501.png, image-2019-03-04-03-41-47-525.png Components: blueocean-plugin Created: 2019-03-04 08:42 Priority: Minor Reporter: Jon B Just upgraded to the latest jenkins core and all plugins. Now, we are not seeing most of the stages in our giant pipeline. Before: After: However, I can see that in the console, all of the stages and steps ran. The problem is just that the UI is not depicting the pipeline correctly. Add Comment
[JIRA] (JENKINS-55805) Warnings Next Generation Plugin is slow at parsing the log output
Title: Message Title Ronald Brill commented on JENKINS-55805 Re: Warnings Next Generation Plugin is slow at parsing the log output Any update on this? Thanks for your support. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56356) clif doesn't handle no jar gracefully
Title: Message Title Bruno Dillenseger edited a comment on JENKINS-56356 Re: clif doesn't handle no jar gracefully This occurs when you forget to select a file in the "Import Clif archive" option .It may also occur when you first select a file and Jenkins' auto-refresh is activated: if auto-refresh actually happens, then the file selection disappears and the same exception is thrown.This is really not graceful indeed, but the work-around is simple: just go back to the previous page in your browser and select a file. Also consider deactivating auto-refresh. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56356) clif doesn't handle no jar gracefully
Title: Message Title Bruno Dillenseger edited a comment on JENKINS-56356 Re: clif doesn't handle no jar gracefully This occurs when you forget to select a file in the "Import Clif archive" option. It may also occur when you first select a file and Jenkins' auto-refresh is activated: if auto-refresh actually happens, then the file selection disappears is cleared and the same exception is thrown.This is really not graceful indeed, but the work-around is simple: just go back to the previous page in your browser and select a file. Also consider deactivating auto-refresh. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55962) Plugin Compat Tester Docker image should not be using Module patches starting from 2.163
Title: Message Title Oleg Nenashev updated JENKINS-55962 Jenkins / JENKINS-55962 Plugin Compat Tester Docker image should not be using Module patches starting from 2.163 Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55805) JavaDocParser is slow at parsing the log output
Title: Message Title Ulli Hafner assigned an issue to Unassigned No. The remaining parser that is slow is the JavaDoc parser. I don't see a simple way to improve the speed here without rewriting the parser. It currently has too many or conditions. Do you have an idea how to solve such a problem in general? I think several of the parsers have a rather complex regexp. Jenkins / JENKINS-55805 JavaDocParser is slow at parsing the log output Change By: Ulli Hafner Summary: Warnings Next Generation Plugin JavaDocParser is slow at parsing the log output Component/s: analysis-model Component/s: warnings-ng-plugin Labels: help-wanted Released As: warnings-ng 2.2.0 (and analysis model 2.1.1) Assignee: Ulli Hafner Add Comment
[JIRA] (JENKINS-55805) JavaDocParser is slow at parsing the log output
Title: Message Title Ronald Brill commented on JENKINS-55805 Re: JavaDocParser is slow at parsing the log output Made already a suggestion: Maybe using the regex with the first e.g. 400 chars of a line to make sure this is a candidate for a deeper analysis is an option to make the parser faster. But if you like i can have a deeper look. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52826) Clicking Configure on a worker created by GCE Plugin results in an error
Title: Message Title Simon Elliott commented on JENKINS-52826 Re: Clicking Configure on a worker created by GCE Plugin results in an error Yeah so functionally its OK, i've added 2 "clouds" from /configure and they work as expected. its just when going to Nodes - New Node - Google Compute Engine does it error out. this imo is the instinctive path to follow, if not the correct one.. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55202) Performance Signature Plugin: JAXB API is missing with Java 11
Title: Message Title Adrien Lecharpentier updated an issue Jenkins / JENKINS-55202 Performance Signature Plugin: JAXB API is missing with Java 11 Change By: Adrien Lecharpentier Labels: java11 java11-compatibility scrub triaged Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32619) Javadoc link displays only documentation frame with no content
Title: Message Title Oleg Nenashev commented on JENKINS-32619 Re: Javadoc link displays only documentation frame with no content https://github.com/jenkinsci/javadoc-plugin/pull/10 needs to be released to close it Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55805) JavaDocParser is slow at parsing the log output
Title: Message Title Ronald Brill commented on JENKINS-55805 Re: JavaDocParser is slow at parsing the log output Another option: Use https://www.brics.dk/automaton/ as regex engine. Have done this successfully in the past for Wetator to increase performance. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40643) Disk Usage plugin does not show single or multibranch pipeline jobs
Title: Message Title Anurag Srivastava commented on JENKINS-40643 Re: Disk Usage plugin does not show single or multibranch pipeline jobs Same problem persist here, disk usage plugin is not working with jenkins pipeline (only fresstyle job showing disk space stats) any idea, when this can be 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-40643) Disk Usage plugin does not show single or multibranch pipeline jobs
Title: Message Title Anurag Srivastava edited a comment on JENKINS-40643 Re: Disk Usage plugin does not show single or multibranch pipeline jobs Same problem persist here, disk usage plugin is not working with jenkins pipeline (only fresstyle freestyle job showing disk space stats)any idea, when this can be 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-56384) Shareable Libraries on Slave - FileNotFoundException
Title: Message Title Matteo Turra created an issue Jenkins / JENKINS-56384 Shareable Libraries on Slave - FileNotFoundException Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2019-03-04 09:56 Environment: Jenkins ver. 2.150.2 Labels: shared-libraries Priority: Major Reporter: Matteo Turra We used a shared library in pipelines for nine month in a master only configuration, Now we want to add slaves to improve the speed and share jobs between more cpu, but we have a strange behavior. In the shared library there a Groovy method to read a properties file from the workspace and we get a FileNotFoundException. How can the groovy script read file on workspace in the slave node? If it is true that "Groovy execution is still on the master" as in JENKINS-54646 (https://issues.jenkins-ci.org/browse/JENKINS-54646) this means shared-libraries are useless in a master slave configuration?
[JIRA] (JENKINS-56384) Shared Libraries on Slave - FileNotFoundException
Title: Message Title Matteo Turra updated an issue Jenkins / JENKINS-56384 Shared Libraries on Slave - FileNotFoundException Change By: Matteo Turra Summary: Shareable Shared Libraries on Slave - FileNotFoundException Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55805) JavaDocParser is slow at parsing the log output
Title: Message Title Ulli Hafner commented on JENKINS-55805 Re: JavaDocParser is slow at parsing the log output Interested in helping with this? I am open for any solution that does not break the rest of the tests Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56384) Shared Libraries on Slave - FileNotFoundException
Title: Message Title Matteo Turra updated an issue Jenkins / JENKINS-56384 Shared Libraries on Slave - FileNotFoundException Change By: Matteo Turra Released As: JENKINS-54646 (https://issues.jenkins-ci.org/browse/JENKINS-54646) JENKINS-40695 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56384) Shared Libraries on Slave - FileNotFoundException
Title: Message Title Matteo Turra updated an issue Jenkins / JENKINS-56384 Shared Libraries on Slave - FileNotFoundException Change By: Matteo Turra Released As: JENKINS-54646 (https://issues.jenkins-ci.org/browse/ JENKINS- 54646) JENKINS- 40695 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54255) xUnit sets build status incorrectly
Title: Message Title Nikolas Falco commented on JENKINS-54255 Re: xUnit sets build status incorrectly The order of parameters are not meaningful. Are used to contruct the object by reflection. > Any new failed test to fail the build, if no new failures, any old failure to cause to unstable build status. Failed thresholds are analysed before unstable thresholds. Total count of test failure are taken into account before of New test failures. This logic is applied to all thresholds (skipped, failed and passed). This means your scenario is not possible. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56382) Only one stage visible in BlueOcean
Title: Message Title James Shorthouse commented on JENKINS-56382 Re: Only one stage visible in BlueOcean Also experiencing the same issue Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Carlos Sanchez commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN There is a fix in 4.1.8, others will come later Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55150) [jenkins-dev] jenkins-dev:run no longer has hot reload after 2.152
Title: Message Title Isa Vilacides updated an issue Jenkins / JENKINS-55150 [jenkins-dev] jenkins-dev:run no longer has hot reload after 2.152 Change By: Isa Vilacides Priority: Critical Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55805) JavaDocParser is slow at parsing the log output
Title: Message Title Ronald Brill commented on JENKINS-55805 Re: JavaDocParser is slow at parsing the log output Ok will have a look. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44808) Unable to print stacktrace on jenkins pipeline
Title: Message Title Constantin Bugneac commented on JENKINS-44808 Re: Unable to print stacktrace on jenkins pipeline Has anyone got a proper way to print the stacktrace ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55896) Jenkins is not triggering build on any pullrequest created in bitbucket repo
Title: Message Title Christian Del Monte closed an issue as Fixed Jenkins / JENKINS-55896 Jenkins is not triggering build on any pullrequest created in bitbucket repo Change By: Christian Del Monte Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56198) Source details inference fails on Java 11 (Fix test, not the bug)
Title: Message Title Ramon Leon updated JENKINS-56198 Jenkins / JENKINS-56198 Source details inference fails on Java 11 (Fix test, not the bug) Change By: Ramon Leon Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56366) Global level pipeline syntax throwing exception for both hubotApprove / hubotSend
Title: Message Title Naresh Rayapati updated an issue Jenkins / JENKINS-56366 Global level pipeline syntax throwing exception for both hubotApprove / hubotSend Change By: Naresh Rayapati Summary: Global level pipeline syntax throwing exception for both hubotApprove - java.lang.NullPointerException at org.thoughtslive.jenkins.plugins.hubot.steps.ApproveStep$DescriptorImpl.doFillSiteItems(ApproveStep.java:107) / hubotSend Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44449) Provide GIT_COMMIT_SHORT environment variable
Title: Message Title Björn Michael commented on JENKINS-9 Re: Provide GIT_COMMIT_SHORT environment variable git rev-parse ensures that short SHA1 is unique during execution and increases number of digits appropriately. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56366) Global level pipeline syntax throwing exception for both hubotApprove / hubotSend
Title: Message Title Naresh Rayapati commented on JENKINS-56366 Re: Global level pipeline syntax throwing exception for both hubotApprove / hubotSend Nice catch Josh Soref I missed testing this global level pipeline syntax page, this shouldn't be the case when we look at the pipeline syntax on one of the pipeline jobs (just in case) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56366) Global level pipeline syntax throwing exception for both hubotApprove / hubotSend
Title: Message Title Naresh Rayapati updated JENKINS-56366 Jenkins / JENKINS-56366 Global level pipeline syntax throwing exception for both hubotApprove / hubotSend Change By: Naresh Rayapati 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-56366) Global level pipeline syntax throwing exception for both hubotApprove / hubotSend
Title: Message Title Naresh Rayapati started work on JENKINS-56366 Change By: Naresh Rayapati 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-56366) Global level pipeline syntax throwing exception for both hubotApprove / hubotSend
Title: Message Title Naresh Rayapati commented on JENKINS-56366 Re: Global level pipeline syntax throwing exception for both hubotApprove / hubotSend PR: https://github.com/jenkinsci/hubot-steps-plugin/pull/23 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40507) maven plugin : build hang when downloading some artifacts
Title: Message Title Eric Thiebaut-George commented on JENKINS-40507 Re: maven plugin : build hang when downloading some artifacts We experienced the same problem. After looking at Nexus (Support/Metrics) it appeared that 3/4 of the threads were BLOCKED (red). Restarting Nexus seems to fix the problem for us. There is probably a lock somewhere. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56324) Age does not look correct for new issues when compared with a reference build
Title: Message Title Julie Shamji commented on JENKINS-56324 Re: Age does not look correct for new issues when compared with a reference build I have checked both builds outstanding XML and the id D0C733D61919401C83027E30C424C021 is not present in the files at 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-53532) KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed
Title: Message Title Filip Pytloun commented on JENKINS-53532 Re: KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed Hello, I am also getting this exception occasionaly: java.net.SocketException: Socket closed at java.net.SocketInputStream.read(SocketInputStream.java:204) at java.net.SocketInputStream.read(SocketInputStream.java:141) at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) at sun.security.ssl.InputRecord.read(InputRecord.java:503) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:940) at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) at okio.Okio$2.read(Okio.java:139) at okio.AsyncTimeout$2.read(AsyncTimeout.java:237) Caused: java.net.SocketTimeoutException: timeout at okio.Okio$4.newTimeoutException(Okio.java:230) at okio.AsyncTimeout.exit(AsyncTimeout.java:285) at okio.AsyncTimeout$2.read(AsyncTimeout.java:241) at okio.RealBufferedSource.indexOf(RealBufferedSource.java:345) at okio.RealBufferedSource.readUtf8LineStrict(RealBufferedSource.java:217) at okhttp3.internal.http1.Http1Codec.readHeaderLine(Http1Codec.java:212) at okhttp3.internal.http1.Http1Codec.readResponseHeaders(Http1Codec.java:189) at okhttp3.internal.http.CallServerInterceptor.intercept(CallServerInterceptor.java:88) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:45) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:125) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) at io.fabric8.kubernetes.client.utils.BackwardsCompatibilityInterceptor.intercept(BackwardsCompatibilityInterceptor.java:119) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) at io.fabric8.kubernetes.client.utils.ImpersonatorInterceptor.intercept(ImpersonatorInterceptor.java:68) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) at io.fabric8.kubernetes.client.utils.HttpClientUtils$2.intercept(HttpClientUtils.java:107) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:200) at okhttp3.RealCall.execute(RealCall.java:77) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:379) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:344) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleGet(OperationSupport.java:313) at io.fabric8.ku
[JIRA] (JENKINS-54940) brokenBuildSuspects() returns empty list in pipeline script
Title: Message Title Emmanuel Ruhnau commented on JENKINS-54940 Re: brokenBuildSuspects() returns empty list in pipeline script Seems to be not working also for culprits() Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Daniel Watrous commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN Carlos Sanchez I'm confused by the version number you mention, 4.1.8. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38447) Bitbucket hooks don't work for Pipeline jobs
Title: Message Title
omer haim commented on JENKINS-38447
Re: Bitbucket hooks don't work for Pipeline jobs
I am using Bitbucket organization, and trying to automatically trigger a build for a multi branch pipeline. The hook arrives to jenkins but doesnt trigger the job. Jenkins log: ``` INFO: Received commit hook notification for {"scm":"git","website":"","name":"test-repo","links":{"self": {"href":"https://api.bitbucket.org/2.0/repositories/omerh/test-repo"} ,"html":{"href":"https://bitbucket.org/omerh/test-repo"},"avatar":{"href":"https://bytebucket.org/ravatar/%7B8c189537-3a35-430a-a5e1-26ab25cb16f8%7D?ts=java"}},"project":{"key":"BAC","type":"project","uuid":" {9359e998-bf48-4adf-9924-356ccdd06686} ","links":{"self": {"href":"https://api.bitbucket.org/2.0/teams/omerh/projects/BAC"} ,"html":{"href":"https://bitbucket.org/account/user/omerh/projects/BAC"},"avatar":{"href":"https://bitbucket.org/account/user/omerh/projects/BAC/avatar/32"}},"name":"Backend"},"full_name":"omerh/test-repo","owner":{"username":"omerh","display_name":"minerva-prime","type":"team","uuid":" {4e4e35b7-b1ce-4a47-8286-7789660275ab} ","links":{"self": {"href":"https://api.bitbucket.org/2.0/teams/omerh"} ,"html":{"href":"https://bitbucket.org/omerh/"},"avatar":{"href":"https://bitbucket.org/account/omerh/avatar/"}}},"type":"repository","is_private":true,"uuid":"{8c189537-3a35-430a-a5e1-26ab25cb16f8}"} ``` This bug is couple of years old!, can someone post a workaround or a 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-56231) Suppress automatic SCM triggering is deprecated
Title: Message Title Andreas Sieferlinger commented on JENKINS-56231 Re: Suppress automatic SCM triggering is deprecated We also experience this issue, and neither found a way to work around this? Anybody has a suitable workaround or some more information on why this was removed at 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-38447) Bitbucket hooks don't work for Pipeline jobs
Title: Message Title
omer haim edited a comment on JENKINS-38447
Re: Bitbucket hooks don't work for Pipeline jobs
I am using Bitbucket organization, and trying to automatically trigger a build for a multi branch pipeline.The hook arrives to jenkins but doesnt trigger the job. Jenkins log: ``` {code:java} INFO: Received commit hook notification for \ {"scm":"git","website":"","name":"test-repo","links":{"self": {"href":"https://api.bitbucket.org/2.0/repositories/omerh/test-repo"} ,"html": \ {"href":"https://bitbucket.org/omerh/test-repo"},"avatar": \ {"href":"https://bytebucket.org/ravatar/%7B8c189537-3a35-430a-a5e1-26ab25cb16f8%7D?ts=java"}},"project": \ {"key":"BAC","type":"project","uuid":" {9359e998-bf48-4adf-9924-356ccdd06686} ","links": \ {"self": {"href":"https://api.bitbucket.org/2.0/teams/omerh/projects/BAC"} ,"html": \ {"href":"https://bitbucket.org/account/user/omerh/projects/BAC"},"avatar": \ {"href":"https://bitbucket.org/account/user/omerh/projects/BAC/avatar/32"}},"name":"Backend"},"full_name":"omerh/test-repo","owner": \ {"username":"omerh","display_name":"minerva-prime","type":"team","uuid":" {4e4e35b7-b1ce-4a47-8286-7789660275ab} ","links": \ {"self": {"href":"https://api.bitbucket.org/2.0/teams/omerh"} ,"html": \ {"href":"https://bitbucket.org/omerh/"},"avatar": \ {"href":"https://bitbucket.org/account/omerh/avatar/"}}},"type":"repository","is_private":true,"uuid":" \ {8c189537-3a35-430a-a5e1-26ab25cb16f8}"} {code} ``` This bug is couple of years old!, can someone post a workaround or a 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-56211) Fix broken ATH test for rvm plugin
Title: Message Title Oleg Nenashev edited a comment on JENKINS-56211 Re: Fix broken ATH test for rvm plugin liver Oliver : JRuby library might be a root cause Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Narayanan Singaram commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN Carlos Sanchez I think the fix in 4.1.8 only addresses the issue caused by ContainerLog step. Will the same fix help if ContainerLog step is not getting used? In out case, we are impacted by this bug and our jenkinsfile is not using ContainerLog, I'm trying to find will the fix help in our scenario? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56385) allow setting of env. variables or parameters in triggered runs
Title: Message Title Brian J Murrell created an issue Jenkins / JENKINS-56385 allow setting of env. variables or parameters in triggered runs Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2019-03-04 13:52 Priority: Major Reporter: Brian J Murrell While it's useful to be able to trigger a pipeline run based on a cron schedule, it would be even more useful, if along with the cron schedule, parameters or environment variables could be defined so that one could define different run models with the triggers. Probably a common example of this would be to run different sets of testing at pre-defined times, such as running more comprehensive (and resource intensive) testing on weekends when resource contention is low. Add Comment
[JIRA] (JENKINS-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Carlos Sanchez commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN Fat fingers 1.14.8 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55961) Nodejs plugin installs wrong platform package when using parallel pipeline
Title: Message Title Paulomart commented on JENKINS-55961 Re: Nodejs plugin installs wrong platform package when using parallel pipeline Its there any update on this issue? We have a lot of parallel pipelines and this fails a lot. Thanks, Paul Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55805) JavaDocParser is slow at parsing the log output
Title: Message Title Ronald Brill commented on JENKINS-55805 Re: JavaDocParser is slow at parsing the log output Looks like my theory is correct, the regex is the show stopper. What do you think about limiting the content that is inspected by the regex. Did some tests and limiting the length to 4000 chars cures all the problems without failing tests. Optional every subclass can provide a length restriction (default none) every subclass can restrict the line (default is to return the whole line) every subclass can overwrite the match and limit the line before calling the matcher What do you think? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56231) Suppress automatic SCM triggering is deprecated
Title: Message Title Christian Ciach commented on JENKINS-56231 Re: Suppress automatic SCM triggering is deprecated The deprecation is part of JENKINS-47859 The JavaDoc of the class `NoTriggerBranchProperty` says: @deprecated Replaced by a named branch build strategy in the basic-branch-build-strategies 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-56324) Age does not look correct for new issues when compared with a reference build
Title: Message Title Ulli Hafner commented on JENKINS-56324 Re: Age does not look correct for new issues when compared with a reference build Is a warning in outstanding.xml that has most of the properties equal to the new warning? Whitespace WhitespaceAroundCheck "../../issue[21]/severity"/> '=' is not followed by whitespace. 25 25 52 52 a03d2555-c7fc-4281-8d36-639d0c89cb46 183 checkstyle Soft Entity Service com.unisys.holmes2.h2ng.softentity.quickSearch.impl C:/Program Files (x86)/Jenkins/workspace/U-LEAF Full with Site/holmes2ng/softentity-service/src/test/java/com/unisys/holmes2/h2ng/softentity/quickSearch/impl/DescriptionAndUrnQuickSearchTest.java D0C733D61919401C83027E30C424C021 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55805) JavaDocParser is slow at parsing the log output
Title: Message Title Ulli Hafner commented on JENKINS-55805 Re: JavaDocParser is slow at parsing the log output I think hard coding the 4000 limit is ok. We can make it configurable later on if really someone requires something different. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56381) 'Enter directly' should be selected by default when creating SSH key credentials
Title: Message Title Devin Nusbaum assigned an issue to Unassigned Jenkins / JENKINS-56381 'Enter directly' should be selected by default when creating SSH key credentials Change By: Devin Nusbaum Assignee: Devin Nusbaum Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55805) JavaDocParser is slow at parsing the log output
Title: Message Title Ronald Brill commented on JENKINS-55805 Re: JavaDocParser is slow at parsing the log output Should i prepare a PR? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56355) FATAL: "c:\program files (x86)\msbuild\14.0\bin\msbuild.exe" doesn't exist
Title: Message Title Gerald Britton commented on JENKINS-56355 Re: FATAL: "c:\program files (x86)\msbuild\14.0\bin\msbuild.exe" doesn't exist that fixed it! I wonder though if the plugin could handle the quoted path as is, since that kind of thing is idiomatic in Windows? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56386) File handles are not release by java process after running OWASP Dependency-Check Plugin
Title: Message Title
Laurent Quillérou created an issue
Jenkins / JENKINS-56386
File handles are not release by java process after running OWASP Dependency-Check Plugin
Issue Type:
Bug
Assignee:
Unassigned
Components:
dependency-check-jenkins-plugin
Created:
2019-03-04 14:30
Environment:
Jenkins ver. 2.150.3 (debian) OWASP Dependency-Check Plugin 4.0.2 Jenkins node: windows 2016 (with latest updates applied) java version on Jenkins node: 1.8.0_201
Priority:
Major
Reporter:
Laurent Quillérou
We are running into the following exception at the cleanup phase after running dependency-check on a windows agent:
java.nio.file.FileSystemException: ${WS_PATH}\protobuf\win\include\google\protobuf\compiler\js\well_known_types\any.js: The process cannot access the file because it is being used by another process.
at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)
at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)
at java.nio.file.Files.deleteIfExists(Unknown Source)
at hudson.Util.tryOnceDeleteFile(Util.java:318)
at hudson.Util.deleteFile(Util.java:274)
Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from ${NODE_DNS}/${NODE_IP}:3625
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)
at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)
at hudson.remotin
[JIRA] (JENKINS-55805) JavaDocParser is slow at parsing the log output
Title: Message Title Ulli Hafner commented on JENKINS-55805 Re: JavaDocParser is slow at parsing the log output Yes please! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56387) Upgrading to 2.150.3 results in No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executePostBuild()
Title: Message Title lee benhart created an issue Jenkins / JENKINS-56387 Upgrading to 2.150.3 results in No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executePostBuild() Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-03-04 14:58 Environment: Jenkins Version 2.150.3 Priority: Minor Reporter: lee benhart PostBuild steps are failing, below is the exception hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executePostBuild() is applicable for argument types: (org.jenkinsci.plugins.pipeline.modeldefinition.model.Root) values: [org.jenkinsci.plugins.pipeline.modeldefinition.model.Root(org.jenkinsci.plugins.pipeline.modeldefinition.model.Agent(org.jenkinsci.plugins.workflow.cps.CpsClosure2@3b11b3b5), org.jenkinsci.plugins.pipeline.modeldefinition.model.Stages([org.jenkinsci.plugins.pipeline.modeldefinition.model.Stage(setup to get roles, null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageConditionals(org.jenkinsci.plugins.workflow.cps.CpsClosure2@fbcc393, false, false), null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@2fedc262), null, [], null, false, null, null), org.jenkinsci.plugins.pipeline.modeldefinition.model.Stage(Update Jenkins, null, null, null, null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@500f74dc), null, [], null, false, null, null)]), org.jenkinsci.plugins.pipeline.modeldefinition.model.MappedClosure([always:org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@6347c
[JIRA] (JENKINS-56387) Upgrading to 2.150.3 results in No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executePostBuild()
Title: Message Title lee benhart created an issue Jenkins / JENKINS-56387 Upgrading to 2.150.3 results in No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executePostBuild() Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-03-04 14:58 Environment: Jenkins Version 2.150.3 Priority: Minor Reporter: lee benhart PostBuild steps are failing, below is the exception hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executePostBuild() is applicable for argument types: (org.jenkinsci.plugins.pipeline.modeldefinition.model.Root) values: [org.jenkinsci.plugins.pipeline.modeldefinition.model.Root(org.jenkinsci.plugins.pipeline.modeldefinition.model.Agent(org.jenkinsci.plugins.workflow.cps.CpsClosure2@3b11b3b5), org.jenkinsci.plugins.pipeline.modeldefinition.model.Stages([org.jenkinsci.plugins.pipeline.modeldefinition.model.Stage(setup to get roles, null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageConditionals(org.jenkinsci.plugins.workflow.cps.CpsClosure2@fbcc393, false, false), null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@2fedc262), null, [], null, false, null, null), org.jenkinsci.plugins.pipeline.modeldefinition.model.Stage(Update Jenkins, null, null, null, null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@500f74dc), null, [], null, false, null, null)]), org.jenkinsci.plugins.pipeline.modeldefinition.model.MappedClosure([always:org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@6347c
[JIRA] (JENKINS-56387) Upgrading to 2.150.3 results in No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executePostBuild()
Title: Message Title Oleg Nenashev assigned an issue to Andrew Bayer Jenkins / JENKINS-56387 Upgrading to 2.150.3 results in No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executePostBuild() Change By: Oleg Nenashev Assignee: Andrew Bayer Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56387) Upgrading to 2.150.3 results in No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executePostBuild()
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-56387 Upgrading to 2.150.3 results in No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executePostBuild() Change By: Oleg Nenashev Component/s: pipeline-model-definition-plugin Component/s: core Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56354) NPE in Caught exception evaluating: h.filterExcludingFrom(it.buildsAsMap,from,to).values()
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-56354 NPE in Caught exception evaluating: h.filterExcludingFrom(it.buildsAsMap,from,to).values() Change By: Oleg Nenashev Component/s: core Component/s: _unsorted Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56354) NPE in Caught exception evaluating: h.filterExcludingFrom(it.buildsAsMap,from,to).values()
Title: Message Title Oleg Nenashev commented on JENKINS-56354 Re: NPE in Caught exception evaluating: h.filterExcludingFrom(it.buildsAsMap,from,to).values() Looks like a Jenkins core defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56388) Duplicate ChangeLog on Jenkins builds for concurrent builds
Title: Message Title hariprasad Narnavara, created an issue Jenkins / JENKINS-56388 Duplicate ChangeLog on Jenkins builds for concurrent builds Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2019-03-04 15:11 Priority: Major Reporter: hariprasad Narnavara, Change Log are repeated in the builds as shown below. Build take one hour to complete and hence below 3 build executed in parallel but i see the changelog is repeated. #12 (Jan 29, 2019 8:59:07 AM) JIRA-XXX: Added validation — User3 [JIRA-XXX] clean up — User1 JIRA-XXX: Cleanup — User2 JIRA-XXX: State model and final cleanup - user1 #10 (Jan 29, 2019 8:54:55 AM) JIRA-XXX: Added validation — User3 [JIRA-XXX] clean up — User1 JIRA-XXX: Cleanup — User2 #9 (Jan 28, 2019 8:45:43 AM) JIRA-XXX: Added validation — User3
[JIRA] (JENKINS-56388) Duplicate ChangeLog on Jenkins builds for concurrent builds
Title: Message Title hariprasad Narnavara, updated an issue Jenkins / JENKINS-56388 Duplicate ChangeLog on Jenkins builds for concurrent builds Change By: hariprasad Narnavara, Change Log are repeated in the builds as shown below.Build take one hour to complete and hence below 3 build executed in parallel but i see the changelog is repeated. [Jenkins ver. 2.121.3|https://jenkins.io/]This is pipeline jobGit Changelog plugin version 2.16 h2. [#12 (Jan 29, 2019 8:59:07 AM)|http://denotsl1444.int.kn:8091/jenkins/job/Test/job/QT_TestChangeLog/12/changes] # JIRA-XXX: Added validation — User3 # [JIRA-XXX] clean up — User1 # JIRA-XXX: Cleanup — User2 # JIRA-XXX: State model and final cleanup - user1h2. [#10 (Jan 29, 2019 8:54:55 AM)|http://denotsl1444.int.kn:8091/jenkins/job/Test/job/QT_TestChangeLog/10/changes] # JIRA-XXX: Added validation — User3 # [JIRA-XXX] clean up — User1 # JIRA-XXX: Cleanup — User2h2. [#9 (Jan 28, 2019 8:45:43 AM)|http://denotsl1444.int.kn:8091/jenkins/job/Test/job/QT_TestChangeLog/9/changes] # JIRA-XXX: Added validation — User3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, vis
[JIRA] (JENKINS-56388) Duplicate ChangeLog on Jenkins builds for concurrent builds
Title: Message Title hariprasad Narnavara, updated an issue Jenkins / JENKINS-56388 Duplicate ChangeLog on Jenkins builds for concurrent builds Change By: hariprasad Narnavara, Change Log are repeated in the builds as shown below.Build take one hour to complete and hence below 3 build executed in parallel but i see the changelog is repeated.[Jenkins ver. 2.121.3|https://jenkins.io/]This is pipeline jobGit Changelog plugin version 2.16 git-client 2.7.0git 3.7.1 h2. [#12 (Jan 29, 2019 8:59:07 AM)|http://denotsl1444.int.kn:8091/jenkins/job/Test/job/QT_TestChangeLog/12/changes] # JIRA-XXX: Added validation — User3 # [JIRA-XXX] clean up — User1 # JIRA-XXX: Cleanup — User2 # JIRA-XXX: State model and final cleanup - user1h2. [#10 (Jan 29, 2019 8:54:55 AM)|http://denotsl1444.int.kn:8091/jenkins/job/Test/job/QT_TestChangeLog/10/changes] # JIRA-XXX: Added validation — User3 # [JIRA-XXX] clean up — User1 # JIRA-XXX: Cleanup — User2h2. [#9 (Jan 28, 2019 8:45:43 AM)|http://denotsl1444.int.kn:8091/jenkins/job/Test/job/QT_TestChangeLog/9/changes] # JIRA-XXX: Added validation — User3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.c
[JIRA] (JENKINS-56388) Duplicate ChangeLog on Jenkins builds for concurrent builds
Title: Message Title hariprasad Narnavara, updated an issue Jenkins / JENKINS-56388 Duplicate ChangeLog on Jenkins builds for concurrent builds Change By: hariprasad Narnavara, Component/s: git-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-56389) MSBuild fails in Declaritive Pipeline
Title: Message Title
Gerald Britton created an issue
Jenkins / JENKINS-56389
MSBuild fails in Declaritive Pipeline
Issue Type:
Bug
Assignee:
Lionel Cabasson
Attachments:
image-2019-03-04-10-18-04-103.png
Components:
msbuild-plugin, pipeline
Created:
2019-03-04 15:27
Environment:
Windows Server 2012-R2, Jenkins 2.138.2, MSBuild 1.29
Labels:
pipeline msbuild
Priority:
Minor
Reporter:
Gerald Britton
MSbuild Setup:Jenkinsfile snippet:
stage('Build') {
steps {
echo 'Building..'
bat "\"${tool 'MSBuild'}\" ${SQLPROJ} /p:Configuration=Release /p:Platform=\"Any CPU\" /p:ProductVersion=1.0.0.${env.BUILD_NUMBER}"
}
}
Console output: {{D:\var\lib\jenkins\workspace\VisionPipeline>"c:\program files (x86)\msbuild\14.0\bin\" TBSM.Vision.Database\TBSM.Vision.Database\Vision.sqlproj /p:Configuration=Release /p:Platform="Any CPU" /p:ProductVersion=1.0.0.11 '"c:\program files (x86)\msbuild\14.0\bin\"' is not recognized as an internal or external command, operable program or batch file. ??}} Do I have to
[JIRA] (JENKINS-56388) Duplicate ChangeLog on Jenkins builds for concurrent builds
Title: Message Title hariprasad Narnavara, updated an issue Jenkins / JENKINS-56388 Duplicate ChangeLog on Jenkins builds for concurrent builds Change By: hariprasad Narnavara, Change Log are repeated in the builds as shown below.Build take one hour to complete and hence below 3 build executed in parallel but i see the changelog is repeated.[Jenkins ver. 2.121.3|https://jenkins.io/]This is pipeline jobGit Changelog plugin version 2.16git-client 2.7.0git 3.7.1 h2. [ * #12 (Jan 29, 2019 8:59:07 AM) |http://denotsl1444.int.kn:8091/jenkins/job/Test/job/QT_TestChangeLog/12/changes] * # JIRA-XXX: Added validation — User3 # [JIRA-XXX] clean up — User1 # JIRA-XXX: Cleanup — User2 # JIRA-XXX: State model and final cleanup - user1 h2. [ * #10 (Jan 29, 2019 8:54:55 AM) |http://denotsl1444.int.kn:8091/jenkins/job/Test/job/QT_TestChangeLog/10/changes] * # JIRA-XXX: Added validation — User3 # [JIRA-XXX] clean up — User1 # JIRA-XXX: Cleanup — User2 h2. [ * #9 (Jan 28 29 , 2019 8:45:43 AM) |http://denotsl1444.int.kn:8091/jenkins/job/Test/job/QT_TestChangeLog/9/changes] * # JIRA-XXX: Added validation — User3 h2. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an em
[JIRA] (JENKINS-56388) Duplicate ChangeLog on Jenkins builds for concurrent builds
Title: Message Title hariprasad Narnavara, updated an issue Jenkins / JENKINS-56388 Duplicate ChangeLog on Jenkins builds for concurrent builds Change By: hariprasad Narnavara, Change Log are repeated in the builds as shown below.Build take one hour to complete and hence below 3 build executed in parallel but i see the changelog is repeated.[Jenkins ver. 2.121.3|https://jenkins.io/]This is pipeline jobGit Changelog plugin version 2.16git-client 2.7.0 git 3.7.1*#12 (Jan 29, 2019 8:59:07 AM)*JIRA-XXX: Added validation — User3[JIRA-XXX] clean up — User1JIRA-XXX: Cleanup — User2JIRA-XXX: State model and final cleanup - user1 *#10 (Jan 29, 2019 8:54:55 AM)*JIRA-XXX: Added validation — User3[JIRA-XXX] clean up — User1JIRA-XXX: Cleanup — User2 *#9 (Jan 29, 2019 8:45:43 AM)*JIRA-XXX: Added validation — User3h2. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56388) Duplicate ChangeLog on Jenkins builds for concurrent builds
Title: Message Title hariprasad Narnavara, updated an issue Jenkins / JENKINS-56388 Duplicate ChangeLog on Jenkins builds for concurrent builds Change By: hariprasad Narnavara, Change Log The Git ChangeLog's are repeated in the builds as shown below. Build take This is pipeline job and the build takes one hour to complete and hence below 3 build executed in parallel but i see the changelog is repeated.[Jenkins ver. 2.121.3|https://jenkins.io/] This is pipeline job Git Changelog plugin version 2.16git-client 2.7.0 git 3.7.1*#12 (Jan 29, 2019 8:59:07 AM)* JIRA-XXX: Added validation — User3 [JIRA-XXX] clean up — User1 JIRA-XXX: Cleanup — User2 JIRA-XXX: State model and final cleanup - user1 *#10 (Jan 29, 2019 8:54:55 AM)* JIRA-XXX: Added validation — User3 [JIRA-XXX] clean up — User1 JIRA-XXX: Cleanup — User2 *#9 (Jan 29, 2019 8:45:43 AM)* JIRA-XXX: Added validation — User3h2. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56388) Duplicate ChangeLog on Jenkins builds for concurrent builds
Title: Message Title hariprasad Narnavara, updated an issue Jenkins / JENKINS-56388 Duplicate ChangeLog on Jenkins builds for concurrent builds Change By: hariprasad Narnavara, The Git ChangeLog's are repeated in the builds as shown below.This is pipeline job and the build takes one hour to complete and hence below 3 build executed in parallel but i see the changelog is repeated. Versions used: [Jenkins ver. 2.121.3|https://jenkins.io/]Git Changelog plugin version 2.16git-client 2.7.0 git 3.7.1 * ChangeLog** #12 (Jan 29, 2019 8:59:07 AM)* JIRA-XXX: Added validation — User3 [JIRA-XXX] clean up — User1 JIRA-XXX: Cleanup — User2 JIRA-XXX: State model and final cleanup - user1*#10 (Jan 29, 2019 8:54:55 AM)* JIRA-XXX: Added validation — User3 [JIRA-XXX] clean up — User1 JIRA-XXX: Cleanup — User2*#9 (Jan 29, 2019 8:45:43 AM)* JIRA-XXX: Added validation — User3h2. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56388) No issue
Title: Message Title hariprasad Narnavara, updated an issue Jenkins / JENKINS-56388 No issue Change By: hariprasad Narnavara, Summary: Duplicate ChangeLog on Jenkins builds for concurrent builds No issue The Git ChangeLog's are repeated in the builds as shown below.This is pipeline job and the build takes one hour to complete and hence below 3 build executed in parallel but i see the changelog is repeated.Versions used:[Jenkins ver. 2.121.3|https://jenkins.io/]Git Changelog plugin version 2.16 git-client 2.7.0git 3.7.1 *ChangeLog**#12 (Jan 29, 2019 8:59:07 AM)* JIRA-XXX: Added validation — User3 [JIRA-XXX] clean up — User1 JIRA-XXX: Cleanup — User2 JIRA-XXX: State model and final cleanup - user1*#10 (Jan 29, 2019 8:54:55 AM)* JIRA-XXX: Added validation — User3 [JIRA-XXX] clean up — User1 JIRA-XXX: Cleanup — User2*#9 (Jan 29, 2019 8:45:43 AM)* JIRA-XXX: Added validation — User3 h2. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsub
[JIRA] (JENKINS-56388) Duplicate ChangeLog on Jenkins builds for concurrent builds
Title: Message Title hariprasad Narnavara, closed an issue as Fixed Jenkins / JENKINS-56388 Duplicate ChangeLog on Jenkins builds for concurrent builds Change By: hariprasad Narnavara, 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-56390) Duplicate ChangeLog on Jenkins builds for concurrent builds
Title: Message Title hariprasad Narnavara, created an issue Jenkins / JENKINS-56390 Duplicate ChangeLog on Jenkins builds for concurrent builds Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2019-03-04 15:33 Priority: Critical Reporter: hariprasad Narnavara, The Git ChangeLog's are repeated in the builds as shown below. This is pipeline job and the build takes one hour to complete and hence below 3 build executed in parallel but i see the changelog is repeated. Versions used: Jenkins ver. 2.121.3 Git Changelog plugin version 2.16 git-client 2.7.0 git 3.7.1 ChangeLog #12 (Jan 29, 2019 8:59:07 AM) JIRA-XXX: Added validation — User3 [JIRA-XXX] clean up — User1 JIRA-XXX: Cleanup — User2 JIRA-XXX: State model and final cleanup - user1 #10 (Jan 29, 2019 8:54:55 AM) JIRA-XXX: Added validation — User3 [JIRA-XXX] clean up — User1 JIRA-XXX: Cleanup — User2 #9 (Jan 29, 2019 8:45:43 AM) JIRA-XXX: Added validation — User3 Add Comment
[JIRA] (JENKINS-56388) No issue
Title: Message Title hariprasad Narnavara, updated an issue Jenkins / JENKINS-56388 No issue Change By: hariprasad Narnavara, Component/s: git-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-56391) Whitespace entered during role assignments is handled inconsistently
Title: Message Title Anton Wiedermann created an issue Jenkins / JENKINS-56391 Whitespace entered during role assignments is handled inconsistently Issue Type: Bug Assignee: Oleg Nenashev Components: role-strategy-plugin Created: 2019-03-04 15:34 Environment: Jenkins ver. 2.166 Role-based Authorization Strategy 2.10 Priority: Minor Reporter: Anton Wiedermann I have copy pasted user login when assigning user to a role. It went with some whitespace around it. I was able to add user like this just fine. Entry was resolved to full user name as expected but permissions granted to the user are not applied by Jenkins. Seems like user check should be consistent with permission application to the user. I would probably vote for trim of whitespace from entered user name. Or it should not be bale to resolve the user. Or at least display warning there is whitespace in login and results can be weird. Add Comment
[JIRA] (JENKINS-56388) a
Title: Message Title hariprasad Narnavara, updated an issue Jenkins / JENKINS-56388 a Change By: hariprasad Narnavara, Summary: No issue a Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56383) Blue Ocean pipeline UI stopped appearing after plugin upgrade
Title: Message Title Balaal Ashraf commented on JENKINS-56383 Re: Blue Ocean pipeline UI stopped appearing after plugin upgrade Having this too... stops generating the stages after the first parallel 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-56383) Blue Ocean pipeline UI stopped rendering correctly after plugin upgrade
Title: Message Title Jon B updated an issue Jenkins / JENKINS-56383 Blue Ocean pipeline UI stopped rendering correctly after plugin upgrade Change By: Jon B Summary: Blue Ocean pipeline UI stopped appearing rendering correctly after plugin 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-55805) JavaDocParser is slow at parsing the log output
Title: Message Title Ronald Brill commented on JENKINS-55805 Re: JavaDocParser is slow at parsing the log output Ok PR is there, have implemented a more generic solution, hope you like it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55720) ec2-plugin 1.42 doesn't work well with ec2 spot instances
Title: Message Title Vyacheslav Sarzhan assigned an issue to Vyacheslav Sarzhan Jenkins / JENKINS-55720 ec2-plugin 1.42 doesn't work well with ec2 spot instances Change By: Vyacheslav Sarzhan Assignee: FABRIZIO MANFREDI Vyacheslav Sarzhan Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56390) Duplicate ChangeLog on Jenkins builds for concurrent builds
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-56390 Duplicate ChangeLog on Jenkins builds for concurrent builds Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56390) Duplicate ChangeLog on Jenkins builds for concurrent builds
Title: Message Title Mark Waite commented on JENKINS-56390 Re: Duplicate ChangeLog on Jenkins builds for concurrent builds The changelog wants to present the changes since the last completed build. Since the 3 jobs you listed all ran in parallel and had not completed. the changes list may be correct displaying it for each of the jobs. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Henry Borchers commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Jesse Glick, a few post ago you mentioned something about creating a different execution engine that wouldn't have this issue. Anything you can point me to so that I can follow the progress or, at least, is anything interesting that you can tease to keep me hopeful that the future looks bright? I have been putting any "steps block" that is more than 1 line into into helper functions but I'm still running into issues. I'm sorry if I come off as nagging. I just really love Jenkins. The declarative pipeline has been my one of favorite tools which I used for everything I build, Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56392) blue-ocean links from classic do not use https
Title: Message Title Björn Pedersen created an issue Jenkins / JENKINS-56392 blue-ocean links from classic do not use https Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2019-03-04 16:07 Priority: Minor Reporter: Björn Pedersen trying to open a job located in a folder from the classic view (open- blue ocean link) raises a 404 error. The URL in the link has correct escaping of slashes Inspecting the http-requests seems to indicate that jenkins sends an intermediate page via Location: that is not using https. Initals request (https) GET /jenkins/blue/organizations/jenkins/debocker%2FBuildEntangleContainersV2 HTTP/1.1 Host: User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:65.0) Gecko/20100101 Firefox/65.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,/;q=0.8 Accept-Language: en-US,en;q=0.5 Accept-Encoding: gzip, deflate, br Referer: https:///jenkins/job/debocker/job/BuildEntangleContainersV2/ Connection: keep-alive Cookie: screenResolution=1920x1200; jenkins-timestamper-offset=-360; jenkins-timestamper=none; jenkins-timestamper-local=true; Upgrade-Insecure-Requests: 1 Response: HTTP/1.1 302 Found Date: Mon, 04 Mar 2019 15:43:13 GMT Server: Jetty(9.4.z-SNAPSHOT) X-Content-Type-Options: nosniff X-Blueocean-Refresher: . Location: http://forge.frm2.tum.de/jenkins/blue/organizations/jenkins/debocker/BuildEntangleContainersV2/ Keep-Alive: timeout=5, max=86 Connection: Keep-Alive Transfer-Encoding: chunked Note the http in there. Possibly also related to JENKINS-46347
[JIRA] (JENKINS-55720) ec2-plugin 1.42 doesn't work well with ec2 spot instances
Title: Message Title Vyacheslav Sarzhan assigned an issue to Unassigned Jenkins / JENKINS-55720 ec2-plugin 1.42 doesn't work well with ec2 spot instances Change By: Vyacheslav Sarzhan Assignee: Vyacheslav Sarzhan Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55720) ec2-plugin 1.42 doesn't work well with ec2 spot instances
Title: Message Title Vyacheslav Sarzhan assigned an issue to Unassigned Jenkins / JENKINS-55720 ec2-plugin 1.42 doesn't work well with ec2 spot instances Change By: Vyacheslav Sarzhan Assignee: Vyacheslav Sarzhan Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title
Jesse Glick commented on JENKINS-37984
Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Henry Borchers I believe that work is now inactive. I am afraid I have no particular advice for now beyond:
If at all possible, remove logic from Pipeline Groovy code and move it into external processes. We see a lot of people with these very complex calculations that could better have been done in some Python script or whatever in the workspace, so that the Pipeline part would boil down to just node {sh './something'}.
When not possible (for example because the Pipeline script is actually required to determine how to configure steps such as parallel or Jenkins publishers), split up long functions (including the implicit main function at top level of a Jenkinsfile) into shorter functions.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56088) FinishLogin throws: Illegal character in query at index 89
Title: Message Title Davíð Jóhannsson updated an issue Jenkins / JENKINS-56088 FinishLogin throws: Illegal character in query at index 89 Change By: Davíð Jóhannsson Priority: Minor Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56383) Blue Ocean pipeline UI stopped rendering correctly after plugin upgrade
Title: Message Title Jon B updated an issue Jenkins / JENKINS-56383 Blue Ocean pipeline UI stopped rendering correctly after plugin upgrade Change By: Jon B Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56383) Blue Ocean pipeline UI stopped rendering correctly after plugin upgrade
Title: Message Title Jon B assigned an issue to Unassigned Jenkins / JENKINS-56383 Blue Ocean pipeline UI stopped rendering correctly after plugin upgrade Change By: Jon B Assignee: Jon B Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56383) Blue Ocean pipeline UI stopped rendering correctly after plugin upgrade
Title: Message Title Jon B assigned an issue to Jon B Jenkins / JENKINS-56383 Blue Ocean pipeline UI stopped rendering correctly after plugin upgrade Change By: Jon B Assignee: Jon B Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56383) Blue Ocean pipeline UI stopped rendering correctly after plugin upgrade
Title: Message Title Jon B commented on JENKINS-56383 Re: Blue Ocean pipeline UI stopped rendering correctly after plugin upgrade I updated this to "major" since this is something all of our engineers depend on and this is obviously some kind of regression. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56255) occasionally builds the branch for a PR also
Title: Message Title Brian J Murrell commented on JENKINS-56255 Re: occasionally builds the branch for a PR also Any response here? Having the branch build for PRs that are opened within a very small number of seconds of pushing the branch is quite annoying at best and frequently confusing for users who don't understand the workings of the github-branch-source-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.
