[JIRA] (JENKINS-56578) Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master
Title: Message Title
Remi Van Goethem updated an issue
Jenkins / JENKINS-56578
Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master
Change By:
Remi Van Goethem
Hi there, After updating Jenkins to version 2.168 I started experiencing build failure using the html publisher plugin {code:java}publishHTML([allowMissing: false, alwaysLinkToLastBuild: true, keepAll: true, reportDir: 'target', reportFiles: 'docs/index.html', reportName: 'SmartRoaming API', reportTitles: '']) publishHTML([allowMissing: false, alwaysLinkToLastBuild: true, keepAll: true, reportDir: 'target', reportFiles: 'docs/index.html', reportName: 'SmartRoaming API', reportTitles: '']) {code} Would result into the following console output and build failure: {code:java}08:26:47 [htmlpublisher] Archiving at BUILD level C:/Jenkins2/workspace/t_RDSFTUKTCL_comms-app-api_PR-12/smart-roaming-api/target to /var/lib/jenkins/jobs/Bitbucket Project/jobs/RDSFTUKTCL/jobs/comms-app-api/branches/PR-12/builds/14/htmlreports/SmartRoaming_20API08:26:47 ERROR: Directory 'C:/Jenkins2/workspace/t_RDSFTUKTCL_comms-app-api_PR-12/smart-roaming-api/target' exists but failed copying to '/var/lib/jenkins/jobs/Bitbucket Project/jobs/RDSFTUKTCL/jobs/comms-app-api/branches/PR-12/builds/14/htmlreports/SmartRoaming_20API'. {code} Downgrading Jenkins to version 2.167 fixes the issue. Would you please advise/support me with that matter?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56578) Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master
Title: Message Title Remi Van Goethem commented on JENKINS-56578 Re: Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master Typo sorry! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56583) warnings and findbugs deprecated without showing replacement
Title: Message Title jpschewe commented on JENKINS-56583 Re: warnings and findbugs deprecated without showing replacement Thanks. I would find it helpful if the snippet generator and the title on the plugin page had similar titles so that it was clear which snippet to use. This would have helped considerably "recordIssues: Record compiler warnings and static analysis results (Warnings-ng)". Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Mark Waite commented on JENKINS-55836 Re: Unable to delete workspace due to locked git .pack file Idan Bidani I don't see anything in the differences you listed that would leave a file open. The git client sequence of changes added support for git large files, but I assume you're not using git large files and thus are not executing the new code paths. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Idan Bidani commented on JENKINS-55836 Re: Unable to delete workspace due to locked git .pack file I looked at https://github.com/jenkinsci/git-plugin/compare/git-3.0.5...git-3.1.0 which led me to https://github.com/jenkinsci/git-client-plugin/compare/git-client-2.1.0...git-client-2.3.0 Mark Waite do you think it could be related to think it could be caused by https://github.com/jenkinsci/git-client-plugin/compare/git-client-2.1.0...git-client-2.3.0#diff-4a13310f7c84a9d6e133def48c0aed5a thanks in advance! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44032) embeddable build status should bust cache
Title: Message Title Kevin Carrasco commented on JENKINS-44032 Re: embeddable build status should bust cache Thomas Döring I'm using 2.0 and this is not an issue for me anymore. It actually wasnt the plugin's fault but a misconfiguration of the nginx proxy ssl certs. I put an nginx proxy infront of Jenkins to handle the ssl stuff. When adding the cert you must concatenate the server certificate and the CA certificate together. For example: cat servercert.crt ca_cert.crt > nginxcert.crt If you dont do this and only use servercert.crt, everything will look fine if you use a browser to go to Jenkins but when you use a tool like curl, the cert will not be trusted. I've seen other system tools behave this way and have also seen this when using SSL libraries for some programming/scripting languages which is probably why GitHub's markdown renderer didnt want to load the badge. After configuring this properly, the badge loaded with no problems. 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-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Idan Bidani edited a comment on JENKINS-55836 Re: Unable to delete workspace due to locked git .pack file I can actually reproduce the bug on Git 3.8.0 and couldn't reproduce it on 3.0.5. I hope to bisect it to later versions to narrow the changes caused it. reproduced on git I've isolated the bug to a change that happened between the 3.0.5(no bug) and 3.1.0 releaseIt may be a case of a conflicting change with another plugin change. If anyone else can try testing 3. 6 0 . 4 5 fixes the issue it will be helpful Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56246) VERSION Column on Mysql is too small
Title: Message Title Cyrille Le Clerc updated JENKINS-56246 Jenkins / JENKINS-56246 VERSION Column on Mysql is too small Change By: Cyrille Le Clerc 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-56246) VERSION Column on Mysql is too small
Title: Message Title Cyrille Le Clerc started work on JENKINS-56246 Change By: Cyrille Le Clerc 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-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Idan Bidani edited a comment on JENKINS-55836 Re: Unable to delete workspace due to locked git .pack file I can actually reproduce the bug on Git 3.8.0 and couldn't reproduce it on 3.0.5. I hope to bisect it to later versions to narrow the changes caused it .reproduced on git plugin 3.6.4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Idan Bidani commented on JENKINS-55836 Re: Unable to delete workspace due to locked git .pack file I can actually reproduce the bug on Git 3.8.0 and couldn't reproduce it on 3.0.5. I hope to bisect it to later versions to narrow the changes caused 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-56578) Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master
Title: Message Title Richard Bywater commented on JENKINS-56578 Re: Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master Remi Van Goethem just to check, do you actually have a duplicate `publishHTML` in your Jenkinsfile or is that just a typo on the issue description? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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 Matthew Ludlum commented on JENKINS-53532 Re: KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed The ping setting is only settable via parameter when starting jenkins as of right now, per my reading through the source and docs. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55345) DocFX info messages count as warnings
Title: Message Title Lorenz Aebi assigned an issue to Lorenz Aebi Jenkins / JENKINS-55345 DocFX info messages count as warnings Change By: Lorenz Aebi Assignee: Lorenz Aebi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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 Daniel Watrous commented on JENKINS-53532 Re: KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed Matthew Ludlum Are you suggesting that this might be better moved out of the plugin and handled by passing in a parameter when starting Jenkins? My other question is: Does the current connectTimeout value set that ping interval? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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 Matthew Ludlum edited a comment on JENKINS-53532 Re: KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed ***setting the timeout will probably not fix the ping issue***To confirm, this is likely an issue with updating to the latest fabric8 client, which went from 3.9.1 to 3.12.0 of okhttp as of the latest release.[https://github.com/fabric8io/kubernetes-client/commit/9a40df1346876764fecf1cc170f482cc3722cd7a#diff-600376dffeb79835ede4a0b285078036L82]Starting with okhttp 3.10([https://github.com/square/okhttp/blob/master/CHANGELOG.md#version-3100|https://github.com/square/okhttp/blob/master/CHANGELOG.md#version-3100] )- it started aggressively checking connectivity with the pingInterval as well.To fix this, adding -Dkubernetes.websocket.ping.interval= to the jenkins startup or system file should change the ping interval. The okhttp docs recommend 30s : bq. If you have a configured ping interval, you should confirm that it is long enough for a roundtrip from client to server. If your ping interval is too short, slow connections may be misinterpreted as failed connections. A ping interval of 30 seconds is reasonable for most use cases. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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 Matthew Ludlum edited a comment on JENKINS-53532 Re: KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed ***setting the timeout will probably not fix the ping issue***To confirm, this is likely an issue with updating to the latest fabric8 client, which went from 3.9.1 to 3.12.0 of okhttp as of the latest release.[https://github.com/fabric8io/kubernetes-client/commit/9a40df1346876764fecf1cc170f482cc3722cd7a#diff-600376dffeb79835ede4a0b285078036L82]Starting with okhttp 3.10([https://github.com/square/okhttp/blob/master/CHANGELOG.md#version-3100|https://github.com/square/okhttp/blob/master/CHANGELOG.md#version-3100 ) ] )- it started aggressively checking connectivity with the pingInterval as well.To fix this, adding -Dkubernetes.websocket.ping.interval= to the jenkins startup or system file should change the ping interval. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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 Matthew Ludlum edited a comment on JENKINS-53532 Re: KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed ***setting the timeout will probably not fix the ping issue***To confirm, this is likely an issue with updating to the latest fabric8 client, which went from 3.9.1 to 3.12.0 of okhttp as of the latest release. [https://github.com/fabric8io/kubernetes-client/commit/9a40df1346876764fecf1cc170f482cc3722cd7a#diff-600376dffeb79835ede4a0b285078036L82]Starting with okhttp 3.10([https://github.com/square/okhttp/blob/master/CHANGELOG.md#version-3100 |https://github.com/square/okhttp/blob/master/CHANGELOG.md#version-3100 )] ) - it started aggressively checking connectivity with the pingInterval as well.To fix this, adding -Dkubernetes.websocket.ping.interval= to the jenkins startup or system file should change the ping interval. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56587) PerfPublisher 8.08 does not mark build as unstable even if there are errors
Title: Message Title Torben Thellefsen commented on JENKINS-56587 Re: PerfPublisher 8.08 does not mark build as unstable even if there are errors I can confirm your workaround works - but you likely knew that Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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 Matthew Ludlum commented on JENKINS-53532 Re: KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed **setting the timeout will probably not fix the ping issue** To confirm, this is likely an issue with updating to the latest fabric8 client, which went from 3.9.1 to 3.12.0 of okhttp as of the latest release. https://github.com/fabric8io/kubernetes-client/commit/9a40df1346876764fecf1cc170f482cc3722cd7a#diff-600376dffeb79835ede4a0b285078036L82 Starting with okhttp 3.10(https://github.com/square/okhttp/blob/master/CHANGELOG.md#version-3100) - it started aggressively checking connectivity with the pingInterval as well. To fix this, adding -Dkubernetes.websocket.ping.interval= to the jenkins startup or system file should change the ping interval. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42513) Increase default keep-alive timeouts
Title: Message Title Josh Soref commented on JENKINS-42513 Re: Increase default keep-alive timeouts Note: --httpKeepAliveTimeout=1 appears to be honored whether winstone means jetty or actually winstone... This is what we hit: java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms at org.eclipse.jetty.util.SharedBlockingCallback$Blocker.block(SharedBlockingCallback.java:235) at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:216) at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:514) at net.bull.javamelody.internal.web.FilterServletOutputStream.write(FilterServletOutputStream.java:88) at net.bull.javamelody.internal.web.CounterResponseStream.write(CounterResponseStream.java:81) at org.kohsuke.stapler.Stapler.serveStaticResource(Stapler.java:604) at org.kohsuke.stapler.ResponseImpl.serveFile(ResponseImpl.java:216) at hudson.model.DirectoryBrowserSupport.serveFile(DirectoryBrowserSupport.java:349) at hudson.model.DirectoryBrowserSupport.generateResponse(DirectoryBrowserSupport.java:141) at org.kohsuke.stapler.HttpResponseRenderer$Default.handleHttpResponse(HttpResponseRenderer.java:124) at org.kohsuke.stapler.HttpResponseRenderer$Default.generateResponse(HttpResponseRenderer.java:69) at org.kohsuke.stapler.Function.renderResponse(Function.java:164) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:147) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:537) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:458) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:282) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:243) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at com.cloudbees.jenkins.support.slowrequest.SlowRequestFilter.doFilter(SlowRequestFilter.java:37) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:47) at
[JIRA] (JENKINS-39909) Incomplete downloads of artifacts
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-39909 Incomplete downloads of artifacts Change By: Josh Soref Comment: . Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39909) Incomplete downloads of artifacts
Title: Message Title Josh Soref commented on JENKINS-39909 Re: Incomplete downloads of artifacts . Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56235) Strip file:// from IDEA inspection file paths
Title: Message Title Lorenz Aebi updated an issue Jenkins / JENKINS-56235 Strip file:// from IDEA inspection file paths Change By: Lorenz Aebi Released As: warnings-ng 4.0.0, analysis-model-api 3.0.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37121) WorkspaceListLeasePickle should help diagnose locked workspaces
Title: Message Title Basil Crow commented on JENKINS-37121 Re: WorkspaceListLeasePickle should help diagnose locked workspaces Got this error a few times today after a Jenkins restart: Resuming build at Thu Mar 14 20:01:13 PDT 2019 after Jenkins restart Waiting to resume part of devops-gate » master » git-blackbox [Pipeline] cleanWs (hide) 20:01:14 [WS-CLEANUP] Deleting project workspace... 20:01:14 [WS-CLEANUP] Deferred wipeout is used... 20:01:14 [WS-CLEANUP] done [Pipeline] } [Pipeline] // timeout [Pipeline] End of Pipeline [Pipeline] } java.lang.IllegalStateException: JENKINS-37121: something already locked /var/tmp/jenkins_slaves/jenkins-selfservice/workspace/devops-gate/master/git-blackbox at org.jenkinsci.plugins.workflow.support.pickles.WorkspaceListLeasePickle$1.tryResolve(WorkspaceListLeasePickle.java:75) at org.jenkinsci.plugins.workflow.support.pickles.WorkspaceListLeasePickle$1.tryResolve(WorkspaceListLeasePickle.java:51) at org.jenkinsci.plugins.workflow.support.pickles.TryRepeatedly$1.run(TryRepeatedly.java:92) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) Caused: java.io.IOException: Failed to load build state at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$3.onSuccess(CpsFlowExecution.java:854) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$3.onSuccess(CpsFlowExecution.java:852) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$4$1.run(CpsFlowExecution.java:906) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:35) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 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.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Finished: FAILURE
[JIRA] (JENKINS-40700) Display communication protocol in agent logs
Title: Message Title Long Nguyen assigned an issue to Long Nguyen Jenkins / JENKINS-40700 Display communication protocol in agent logs Change By: Long Nguyen Assignee: Long Nguyen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Daniel Beck commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) Could we get thread dumps for this while Jenkins is busy? https://wiki.jenkins.io/display/JENKINS/Obtaining+a+thread+dump Note that this might simply be a side effect of a bad performing security realm (AD server) that's getting hit more frequently. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56587) PerfPublisher 8.08 does not mark build as unstable even if there are errors
Title: Message Title
Eugene Schava commented on JENKINS-56587
Re: PerfPublisher 8.08 does not mark build as unstable even if there are errors
This change is a result of bugfix marking the build as "unstable" if it had the status of "failed" before the perfpublisher In your example status is undefined and that's why it cannot be changed to unstable Looks like this should be fixed but as a workaround, you can add script { currentBuild.result = 'SUCCESS' } instruction before calling perfpublisher
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56587) PerfPublisher 8.08 does not mark build as unstable even if there are errors
Title: Message Title
Torben Thellefsen created an issue
Jenkins / JENKINS-56587
PerfPublisher 8.08 does not mark build as unstable even if there are errors
Issue Type:
Bug
Assignee:
Eugene Schava
Components:
perfpublisher-plugin
Created:
2019-03-15 16:03
Environment:
Jenkins 2.150.3, perfpublisher 8.08, many others
Priority:
Minor
Reporter:
Torben Thellefsen
Since upgrading from 8.06 to 8.08 (which fixed some html issues for us), we have noticed that builds are no longer marked unstable when there are test errors. It does not matter whether we set the parameter "threshold" (or "unstableThreshold") to blank or zero '0'. To reproduce, make a pipeline with this configuration and run it:
pipeline {
agent any
stages {
stage('perf') {
steps {
writeFile file: 'result.xml', text: '''
FAILBAD
GOOD
'''
perfpublisher name: 'result.xml', threshold: '0', unstableThreshold: '0', healthy: '', unhealthy: '', metrics: '', parseAllMetrics: false
}
}
}
}
Expected result: Build is unstable (yellow), because there's 1 test failure. Actual result: Build is stable (blue/green). The plugin does correctly show that there's 1 success and 1 failure, but does not set status correctly. Here's an excerpt of the log output from the build:
[JIRA] (JENKINS-56585) Should use POST to send Quiet Down message
Title: Message Title Yudong Li updated JENKINS-56585 Jenkins / JENKINS-56585 Should use POST to send Quiet Down message Change By: Yudong Li 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-55075) Pipeline: If job fails it will run again on next poll.
Title: Message Title Karl Wirth commented on JENKINS-55075 Re: Pipeline: If job fails it will run again on next poll. Hi Brad Wehmeier and Mykola Ulianytskyi. Thank you very much. That is great feedback. FYI - Charusheela Bopardikar Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55075) Pipeline: If job fails it will run again on next poll.
Title: Message Title
Mykola Ulianytskyi edited a comment on JENKINS-55075
Re: Pipeline: If job fails it will run again on next poll.
{quote}After internal discussion we know of at least a few customers that would want the build to retry on failure.An ideal solution is therefore if we could have a tickbox against a job to switch between rebuild on OS/Jenkins fail and ignore fail.{quote}SCM Plugin should trigger build only once if new changes found and never retry it on failure because build loops occur. All existing SCM plugins (Git, CVS, SVN, etc) don't retry builds on failure. Users can use built-in Jenkins features for: 1) Steps Retry:{code:java}stage('Deploy') {steps {retry(3) { sh './deploy.sh'}}}{code}[https://jenkins.io/doc/pipeline/tour/running-multiple-steps/#timeouts-retries-and-more] 2) Entire Pipeline Retry:{code:java}pipeline {options { retry(3) }...{code} [ https://jenkins.io/doc/book/pipeline/syntax/#options ]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55075) Pipeline: If job fails it will run again on next poll.
Title: Message Title Brad Wehmeier edited a comment on JENKINS-55075 Re: Pipeline: If job fails it will run again on next poll. Customers who what to retry failed builds should use a Jenkins plugin designed for that. e.g. [ https://wiki.jenkins.io/display/JENKINS/Naginator+Plugin ]If you still decide a checkbox is necessary, please set the default it to NOT trigger another build on failure since that is the behavior of other SCM plugins for Jenkins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53532) KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed
Title: Message Title Matthew Ludlum commented on JENKINS-53532 Re: KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed I'm guessing a change in the fabric8 client 4.1.2 upgrade which included okHttp 3.12.0 caused this regression to pop up in 1.14.8 vs . prior versions. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55075) Pipeline: If job fails it will run again on next poll.
Title: Message Title
Mykola Ulianytskyi edited a comment on JENKINS-55075
Re: Pipeline: If job fails it will run again on next poll.
{quote}After internal discussion we know of at least a few customers that would want the build to retry on failure.An ideal solution is therefore if we could have a tickbox against a job to switch between rebuild on OS/Jenkins fail and ignore fail.{quote}SCM Plugin should trigger build only once if new changes found and never retry it on failure because build loops occur. Users can use built-in Jenkins features for: 1) Steps Retry:{code:java}stage('Deploy') {steps {retry(3) { sh './deploy.sh'}}}{code}[https://jenkins.io/doc/pipeline/tour/running-multiple-steps/#timeouts-retries-and-more] 2) Entire Pipeline Retry:{code:java}pipeline {options { retry(3) }...{code} [ https://jenkins.io/doc/book/pipeline/syntax/#options ]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55075) Pipeline: If job fails it will run again on next poll.
Title: Message Title Brad Wehmeier commented on JENKINS-55075 Re: Pipeline: If job fails it will run again on next poll. Customers who what to retry failed builds should use a Jenkins plugin designed for that. e.g. https://wiki.jenkins.io/display/JENKINS/Naginator+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-55075) Pipeline: If job fails it will run again on next poll.
Title: Message Title
Mykola Ulianytskyi edited a comment on JENKINS-55075
Re: Pipeline: If job fails it will run again on next poll.
{quote}After internal discussion we know of at least a few customers that would want the build to retry on failure.An ideal solution is therefore if we could have a tickbox against a job to switch between rebuild on OS/Jenkins fail and ignore fail.{quote}SCM Plugin should trigger build only once if new changes foundand never retry it on failure because build loops occurs occur . Users can use built-in Jenkins features for: 1) Steps Retry:{code:java}stage('Deploy') {steps {retry(3) { sh './deploy.sh'}}}{code}[https://jenkins.io/doc/pipeline/tour/running-multiple-steps/#timeouts-retries-and-more] 2) Entire Pipeline Retry:{code:java}pipeline {options { retry(3) }...{code}[https://jenkins.io/doc/book/pipeline/syntax/#options]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55075) Pipeline: If job fails it will run again on next poll.
Title: Message Title
Mykola Ulianytskyi commented on JENKINS-55075
Re: Pipeline: If job fails it will run again on next poll.
After internal discussion we know of at least a few customers that would want the build to retry on failure.
An ideal solution is therefore if we could have a tickbox against a job to switch between rebuild on OS/Jenkins fail and ignore fail.
SCM Plugin should trigger build only once if new changes found and never retry it on failure because build loops occurs. Users can use built-in Jenkins features for: 1) Steps Retry:
stage('Deploy') {
steps {
retry(3) {
sh './deploy.sh'
}
}
}
https://jenkins.io/doc/pipeline/tour/running-multiple-steps/#timeouts-retries-and-more 2) Entire Pipeline Retry:
pipeline {
options {
retry(3)
}
...
[https://jenkins.io/doc/book/pipeline/syntax/#options ]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For
[JIRA] (JENKINS-56585) Should use POST to send Quiet Down message
Title: Message Title Yudong Li started work on JENKINS-56585 Change By: Yudong Li 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-56456) Warnings Next Generation Plugin - Newbie Issues
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-56456 Warnings Next Generation Plugin - Newbie Issues Change By: Ulli Hafner There are a lot of simple to fix issues in the Warnings Next Generation Plugin. Most of these issues just require some small changes and are labeled with *newbie friendly*. These issues will be fixed in the course "Testing of enterprise applications" at the University of Applied Sciences Munich in this summer semester. In order to fix such an issue, please install the [development environment|https://github.com/uhafner/warnings-ng-plugin-devenv] and follow these steps:# Fork the repository (warnings-ng or analysis-model)# Create a new branch # Write a new test that exposes the bug (test is red)# Fix the bug (test is green)# Commit the changes and push them to your forked repository# Create a pull request (PR)# Wait for the CI to check the PR# Fix any reported problems and push your changes again (no need to create a new PR)# Wait for a review of your PR# Fix comments and push your changes again # Wait for the changes to be integrated# Delete your branch Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-56583) warnings and findbugs deprecated without showing replacement
Title: Message Title
Ulli Hafner edited a comment on JENKINS-56583
Re: warnings and findbugs deprecated without showing replacement
The new syntax is available in the Snippet Generator, the new step is called ` {{ recordIssues ` }} .
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56583) warnings and findbugs deprecated without showing replacement
Title: Message Title Ulli Hafner resolved as Cannot Reproduce The new syntax is available in the Snippet Generator, the new step is called `recordIssues`. Jenkins / JENKINS-56583 warnings and findbugs deprecated without showing replacement Change By: Ulli Hafner Status: Open Resolved 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-55075) Pipeline: If job fails it will run again on next poll.
Title: Message Title Karl Wirth commented on JENKINS-55075 Re: Pipeline: If job fails it will run again on next poll. After internal discussion we know of at least a few customers that would want the build to retry on failure. An ideal solution is therefore if we could have a tickbox against a job to switch between rebuild on OS/Jenkins fail and ignore fail. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56586) Parallel stages or branches can only be included in a top-level stage
Title: Message Title
Brian J Murrell created an issue
Jenkins / JENKINS-56586
Parallel stages or branches can only be included in a top-level stage
Issue Type:
Improvement
Assignee:
Unassigned
Components:
pipeline, workflow-basic-steps-plugin
Created:
2019-03-15 15:02
Priority:
Critical
Reporter:
Brian J Murrell
When I try to use nested parallel statements in a declarative pipeline as such:
pipeline {
agent none
stages {
stage('Cancel Previous Builds') { steps { echo "Cancel Previous Builds" } }
stage('Pre-build') { steps { echo "Pre-build" } }
stage("Build and Test") {
parallel {
stage('Build and Test') {
stages {
stage('Build Platform 1') { steps { echo "Build Platform 1" } }
stage('Test Platform 1') {
parallel {
stage('Test 1') { steps { echo "Test 1" } }
stage('Test 2') { steps { echo "Test 2" } }
stage('Test 3') { steps { echo "Test 3" } }
}
}
}
}
stage('Build Platform 2') { steps { echo "Build Platform 2" } }
stage('Build Platform 3') { steps { echo "Build Platform 3" } }
}
}
}
}
I get an error:
WorkflowScript: 25: Parallel stages or branches can only be included in a top-level stage. @ line 25,
[JIRA] (JENKINS-56585) Should use POST to send Quiet Down message
Title: Message Title Yudong Li created an issue Jenkins / JENKINS-56585 Should use POST to send Quiet Down message Issue Type: Bug Assignee: Yudong Li Components: java-client-api Created: 2019-03-15 14:58 Priority: Minor Reporter: Yudong Li https://github.com/jenkinsci/java-client-api/blob/master/jenkins-client/src/main/java/com/offbytwo/jenkins/JenkinsServer.java#L652 uses GET to send Quiet Down message, which would be returned 405 Method Not Allowed. Add Comment This message was sent by
[JIRA] (JENKINS-53532) KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed
Title: Message Title Daniel Watrous commented on JENKINS-53532 Re: KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed I created PR https://github.com/jenkinsci/kubernetes-plugin/pull/442 to fix the issue of these always reverting to zero. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56584) Allow to enforce quality gate at WhiteSource step
Title: Message Title Slawomir Wieczorkowski created an issue Jenkins / JENKINS-56584 Allow to enforce quality gate at WhiteSource step Issue Type: Bug Assignee: Unassigned Components: whitesource-plugin Created: 2019-03-15 14:51 Environment: Jenkins ver. 2.150.3 WhiteSource plugin 19.1.1 Pipelines scripted Priority: Critical Reporter: Slawomir Wieczorkowski Currenly WhiteSource Plugin could be defined to fail job only globally at Jenkins Global Setting section. This functionality should be allowed at whitesource step as parameter to call within pipeline. Add Comment
[JIRA] (JENKINS-55889) JUnit publisher does not automatically pick up test results from the tycho-surefire-plugin
Title: Message Title Cyrille Le Clerc commented on JENKINS-55889 Re: JUnit publisher does not automatically pick up test results from the tycho-surefire-plugin Fixed in pipeline-maven-3.6.8-beta-1 , Robert Munteanu can you please test? Release and release notes: https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.6.8-beta-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-56044) Merge publishers (junit) with the same filename pattern
Title: Message Title Cyrille Le Clerc commented on JENKINS-56044 Re: Merge publishers (junit) with the same filename pattern Fixed in pipeline-maven-3.6.8-beta-1 , Tobias Gruetzmacher can you please test? Release and release notes: https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.6.8-beta-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-56246) VERSION Column on Mysql is too small
Title: Message Title Cyrille Le Clerc commented on JENKINS-56246 Re: VERSION Column on Mysql is too small Fixed in pipeline-maven-3.6.8-beta-1 , Stephan Pauxberger can you please test? Release and release notes: https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.6.8-beta-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-50856) Cannot connect to bitbucket server from Blueocean.
Title: Message Title Sachin Giri commented on JENKINS-50856 Re: Cannot connect to bitbucket server from Blueocean. When the username contains @ for email then it does not let login. for other users with no special chars it lets login. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56134) ActiveDirectory Crash During Reconfiguration
Title: Message Title Marc Pejga commented on JENKINS-56134 Re: ActiveDirectory Crash During Reconfiguration I can confirm this. Additional Information: It doesn't work if the windows service is started with either the default "Local System account" or a local user account It does work if the windows service is started with an Active Directory User. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56044) Merge publishers (junit) with the same filename pattern
Title: Message Title Cyrille Le Clerc assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-56044 Merge publishers (junit) with the same filename pattern Change By: Cyrille Le Clerc Assignee: Alvaro Lobato Cyrille Le Clerc Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56044) Merge publishers (junit) with the same filename pattern
Title: Message Title Cyrille Le Clerc updated JENKINS-56044 Jenkins / JENKINS-56044 Merge publishers (junit) with the same filename pattern Change By: Cyrille Le Clerc 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-56044) Merge publishers (junit) with the same filename pattern
Title: Message Title Cyrille Le Clerc started work on JENKINS-56044 Change By: Cyrille Le Clerc 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-55889) JUnit publisher does not automatically pick up test results from the tycho-surefire-plugin
Title: Message Title Cyrille Le Clerc updated JENKINS-55889 Jenkins / JENKINS-55889 JUnit publisher does not automatically pick up test results from the tycho-surefire-plugin Change By: Cyrille Le Clerc 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-55889) JUnit publisher does not automatically pick up test results from the tycho-surefire-plugin
Title: Message Title Cyrille Le Clerc started work on JENKINS-55889 Change By: Cyrille Le Clerc 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-55889) JUnit publisher does not automatically pick up test results from the tycho-surefire-plugin
Title: Message Title Cyrille Le Clerc assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-55889 JUnit publisher does not automatically pick up test results from the tycho-surefire-plugin Change By: Cyrille Le Clerc Assignee: Alvaro Lobato Cyrille Le Clerc Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45164) In jenkins pipeline a "checkout scm" now adds "--no-tags" instead of "--tags" for git projects
Title: Message Title Dumitru Gurjui commented on JENKINS-45164 Re: In jenkins pipeline a "checkout scm" now adds "--no-tags" instead of "--tags" for git projects Hey Jan Hoppe, you can try to define your scm like this: checkout scm: [ $class: 'GitSCM', branches: [[name: "BRANCH_NAME"]], userRemoteConfigs: [[credentialsId: "GIT_CREDENTIALS", url: "GIT_REPOSITORY"]] ] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45164) In jenkins pipeline a "checkout scm" now adds "--no-tags" instead of "--tags" for git projects
Title: Message Title Dumitru Gurjui commented on JENKINS-45164 Re: In jenkins pipeline a "checkout scm" now adds "--no-tags" instead of "--tags" for git projects Hey Jan Hoppe, you can try to define your scm like this: checkout scm: [ $class: 'GitSCM', branches: [[name: "BRANCH_NAME"]], userRemoteConfigs: [[credentialsId: "GIT_CREDENTIALS", url: "GIT_REPOSITORY"]] ] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56583) warnings and findbugs deprecated without showing replacement
Title: Message Title jpschewe created an issue Jenkins / JENKINS-56583 warnings and findbugs deprecated without showing replacement Issue Type: Bug Assignee: Ulli Hafner Components: findbugs-plugin, warnings-ng-plugin, warnings-plugin Created: 2019-03-15 11:58 Environment: Jenkins 2.164.1 Priority: Minor Reporter: jpschewe I see that according to https://wiki.jenkins.io/display/JENKINS/FindBugs+Plugin the FindBugs plugin has been deprecated and replaced by warnings next generation. I went into the pipeline snippet creator to see what the syntax looks like and was surprised to find that warnings next generation doesn't show up, although all of the other warnings plugins are marked as deprecated. How can be have an LTS release of Jenkins that deprecates plugins, but doesn't provide the replacement? Add Comment
[JIRA] (JENKINS-56579) .mvn/extensions.xml not recognized
Title: Message Title Benjamin Brummer edited a comment on JENKINS-56579 Re: .mvn/extensions.xml not recognized * Building on the jenkins linux master works with maven 3.6.0 with and without pom.xml in subdirectory. * Windows 10 Agent fails * Ubuntu agent is fineSo looks like a Windows problem. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56579) .mvn/extensions.xml not recognized
Title: Message Title Benjamin Brummer edited a comment on JENKINS-56579 Re: .mvn/extensions.xml not recognized * Building on the jenkins linux master works with maven 3.6.0 with and without pom.xml in subdirectory. * Windows 10 Agent fails Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56582) Job's status and node details does not show after upgrade jenkins from 2.138.3 to 2.150.3
Title: Message Title Samarnath Gande created an issue Jenkins / JENKINS-56582 Job's status and node details does not show after upgrade jenkins from 2.138.3 to 2.150.3 Issue Type: Bug Assignee: Unassigned Components: multijob-plugin Created: 2019-03-15 11:19 Environment: Using Jenkins war file in production Labels: multijob job status Priority: Major Reporter: Samarnath Gande Job's status and node details does not show after upgrade jenkins from 2.138.3 to 2.150.3 Add Comment
[JIRA] (JENKINS-56580) Configuration for JaCoCo plugin doesn't generate source inclusions
Title: Message Title
cristalp updated an issue
Jenkins / JENKINS-56580
Configuration for JaCoCo plugin doesn't generate source inclusions
Change By:
cristalp
I configure the JaCoCo plugin by hand, trying to be as specific as possible: The paths are all configured for my project ({{wdl-util}}).In the GUI, I can see {{Inclusions (e.g.: **/*.java,**/*.groovy,**/*.gs)}}, which translates to the following in {{config.xml}} :{code:xml} **/wdl-util/**/target/**.exec **/wdl-util/**/target/classes **/wdl-util/**/src/main/java **/*.java**/*.class **/*Test*.class ...{code}When I run the job, this is what I see:{code}[JaCoCo plugin] Collecting JaCoCo coverage data...[JaCoCo plugin] **/wdl-util/**/target/**.exec;**/wdl-util/**/target/classes;**/wdl-util/**/src/main/java; locations are configured[JaCoCo plugin] Number of found exec files for pattern **/wdl-util/**/target/**.exec: 1[JaCoCo plugin] Saving matched execfiles: /ige/jenkins/work/jobs/wdl-util/workspace/wdl-util/target/jacoco.exec[JaCoCo plugin] Saving matched class directories for class-pattern: **/wdl-util/**/target/classes: [JaCoCo plugin] - /ige/jenkins/work/jobs/wdl-util/workspace/wdl-util/target/classes 26 files[JaCoCo plugin] Saving matched source directories for source-pattern: **/wdl-util/**/src/main/java: [JaCoCo plugin] Source Inclusions: **/*.java[JaCoCo plugin] Source Exclusions: [JaCoCo plugin] - /ige/jenkins/work/jobs/wdl-util/workspace/wdl-util/src/main/java 32 files[JaCoCo plugin] Loading inclusions files..[JaCoCo plugin] inclusions: [**/*.class][JaCoCo plugin] exclusions: [**/*Test*.class][JaCoCo plugin] Thresholds: JacocoHealthReportThresholds [minClass=0, maxClass=0, minMethod=0, maxMethod=0, minLine=0, maxLine=0, minBranch=0, maxBranch=0, minInstruction=0, maxInstruction=0, minComplexity=0, maxComplexity=0][JaCoCo plugin] Publishing the results..[JaCoCo plugin] Loading packages..[JaCoCo plugin] Done.[JaCoCo plugin] Overall coverage: class: 96, method: 88, line: 89, branch: 85, instruction: 89{code}Note the line with {{Source Inclusions}}.Apparently, this is a part that I can't generate with the Job DSL plugin, since this option (and a couple of others that I can find in {{config.xml}}) are missing.So, generating the job{code:groovy}publishers {jacocoCodeCoverage{ execPattern("**/${project}/**/target/**.exec") inclusionPattern("**/*.class") exclusionPattern("**/*Test*.class") classPattern("**/${project}/**/target/classes") sourcePattern("**/${project}/**/src/main/java")} }{code}results in the following {{config.xml}} :{code:xml}**/wdl-util/**/target/**.exec**/wdl-util/**/target/classes**/wdl-util/**/src/main/java**/*.class**/*Test*.class...{code}{{sourceInclusionPattern}} and {{sourceExclusionPattern}} are missing.When I open the job configuration, I can still see {{Inclusions (e.g.: **/*.java,**/*.groovy,**/*.gs)}} with a default
[JIRA] (JENKINS-56580) Configuration for JaCoCo plugin doesn't generate source inclusions
Title: Message Title
cristalp updated an issue
Jenkins / JENKINS-56580
Configuration for JaCoCo plugin doesn't generate source inclusions
Change By:
cristalp
I configure the JaCoCo plugin by hand, trying to be as specific as possible: The paths are all configured for my project ({{wdl-util}}).In the GUI, I can see {{Inclusions (e.g.: **/*.java,**/*.groovy,**/*.gs)}}, which translates to the following in {{config.xml}} :{code:xml} **/wdl-util/**/target/**.exec **/wdl-util/**/target/classes **/wdl-util/**/src/main/java **/*.java**/*.class **/*Test*.class ...{code}When I run the job, this is what I see:{code}[JaCoCo plugin] Collecting JaCoCo coverage data...[JaCoCo plugin] **/wdl-util/**/target/**.exec;**/wdl-util/**/target/classes;**/wdl-util/**/src/main/java; locations are configured[JaCoCo plugin] Number of found exec files for pattern **/wdl-util/**/target/**.exec: 1[JaCoCo plugin] Saving matched execfiles: /ige/jenkins/work/jobs/wdl-util/workspace/wdl-util/target/jacoco.exec[JaCoCo plugin] Saving matched class directories for class-pattern: **/wdl-util/**/target/classes: [JaCoCo plugin] - /ige/jenkins/work/jobs/wdl-util/workspace/wdl-util/target/classes 26 files[JaCoCo plugin] Saving matched source directories for source-pattern: **/wdl-util/**/src/main/java: [JaCoCo plugin] Source Inclusions: **/*.java[JaCoCo plugin] Source Exclusions: [JaCoCo plugin] - /ige/jenkins/work/jobs/wdl-util/workspace/wdl-util/src/main/java 32 files[JaCoCo plugin] Loading inclusions files..[JaCoCo plugin] inclusions: [**/*.class][JaCoCo plugin] exclusions: [**/*Test*.class][JaCoCo plugin] Thresholds: JacocoHealthReportThresholds [minClass=0, maxClass=0, minMethod=0, maxMethod=0, minLine=0, maxLine=0, minBranch=0, maxBranch=0, minInstruction=0, maxInstruction=0, minComplexity=0, maxComplexity=0][JaCoCo plugin] Publishing the results..[JaCoCo plugin] Loading packages..[JaCoCo plugin] Done.[JaCoCo plugin] Overall coverage: class: 96, method: 88, line: 89, branch: 85, instruction: 89{code}Note the line with {{Source Inclusions}}.Apparently, this is a part that I can't generate with the Job DSL plugin, since this option (and a couple of others that I can find in {{config.xml}}) are missing.So, generating the job{code:groovy}publishers {jacocoCodeCoverage{ execPattern("**/${project}/**/target/**.exec") inclusionPattern("**/*.class") exclusionPattern("**/*Test*.class") classPattern("**/${project}/**/target/classes") sourcePattern("**/${project}/**/src/main/java")} }{code}results in the following {{config.xml}} :{code:xml}**/wdl-util/**/target/**.exec**/wdl-util/**/target/classes**/wdl-util/**/src/main/java**/*.class**/*Test*.class...{code}{{sourceInclusionPattern}} and {{sourceExclusionPattern}} are missing.When I open the job configuration, I can still see {{Inclusions (e.g.: **/*.java,**/*.groovy,**/*.gs)}} with a default
[JIRA] (JENKINS-56579) .mvn/extensions.xml not recognized
Title: Message Title Benjamin Brummer commented on JENKINS-56579 Re: .mvn/extensions.xml not recognized Building on the jenkins linux master works with maven 3.6.0 with and without pom.xml in subdirectory. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56581) org.jenkinsci.remoting.protocol.IOHub takes 100% CPU
Title: Message Title Jörg Sautter created an issue Jenkins / JENKINS-56581 org.jenkinsci.remoting.protocol.IOHub takes 100% CPU Issue Type: Bug Assignee: Unassigned Attachments: cpu_time_per_thread.png, thread_cpu_samples.png Components: _unsorted Created: 2019-03-15 10:56 Environment: v2.150.2, Windows Server 2012 R2, x64 Labels: performance Priority: Major Reporter: Jörg Sautter Our 4 Jenkins installations (all on the same HW) are running at 100% CPU after some time, until they get restarted. Sometimes all of them or only some of them are affected by this. I had a closer look at one installation and found out IOHub is running out of control. I added a logger to the class and it prints dozens of "0 scheduled tasks to process" per secound, nothing else. See the attached screenshots of VisualVM for details, the jenkis was idle at the point of record. I could provide more infos if someone tells what is needed. Kind regards Jörg
[JIRA] (JENKINS-54557) hudson.AbortException: Ansible playbook execution failed
Title: Message Title badie saliba commented on JENKINS-54557 Re: hudson.AbortException: Ansible playbook execution failed Hi, We have the same issue. We are using Jenkins 2.150.3 running on CentOS 6.9 OS. Ansible plugin version : 1.0 Ansible version: 2.3.2.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54557) hudson.AbortException: Ansible playbook execution failed
Title: Message Title badie saliba updated an issue Jenkins / JENKINS-54557 hudson.AbortException: Ansible playbook execution failed Change By: badie saliba Attachment: image-2019-03-15-12-50-23-763.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-56580) Configuration for JaCoCo plugin doesn't generate source inclusions
Title: Message Title cristalp created an issue Jenkins / JENKINS-56580 Configuration for JaCoCo plugin doesn't generate source inclusions Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2019-03-15 10:49 Environment: Jenkins LTS 2.138.3 Job DSL plugin 1.70 JaCoCo plugin 3.0.4 Priority: Minor Reporter: cristalp I configure the JaCoCo plugin by hand, trying to be as specific as possible: The paths are all configured for my project (wdl-util). In the GUI, I can see Inclusions (e.g.: */.java,*/.groovy,*/.gs), which translates to the following in config.xml : "jacoco@3.0.4"> **/wdl-util/**/target/**.exec **/wdl-util/**/target/classes **/wdl-util/**/src/main/java **/*.java **/*.class **/*Test*.class ... When I run the job, this is what I see: [JaCoCo plugin] Collecting JaCoCo coverage data... [JaCoCo plugin] **/wdl-util/**/target/**.exec;**/wdl-util/**/target/classes;**/wdl-util/**/src/main/java; locations are configured [JaCoCo plugin] Number of found exec files for pattern **/wdl-util/**/target/**.exec: 1 [JaCoCo plugin] Saving matched execfiles: /ige/jenkins/work/jobs/wdl-util/workspace/wdl-util/target/jacoco.exec [JaCoCo plugin] Saving matched class directories for class-pattern:
[JIRA] (JENKINS-56475) Error in PCT when running jsch 0.1.55 with Java 11 and Jenkins 2.164
Title: Message Title Baptiste Mathus commented on JENKINS-56475 Re: Error in PCT when running jsch 0.1.55 with Java 11 and Jenkins 2.164 Filed https://github.com/jenkinsci/jsch-plugin/pull/7 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-56475) Error in PCT when running jsch 0.1.55 with Java 11 and Jenkins 2.164
Title: Message Title Baptiste Mathus commented on JENKINS-56475 Re: Error in PCT when running jsch 0.1.55 with Java 11 and Jenkins 2.164 FTR, I just ran mvn -V clean verify -Djenkins.version=2.164 both on JDK 8 and JDK 11 on the current master branch (d37861cfff67e319a4d2cdead99966c26fbd76e2), and it was successful each time. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52669) IndexOutOfBoundsException after upgrade to 1.2.3
Title: Message Title
Sébastien Gautrin edited a comment on JENKINS-52669
Re: IndexOutOfBoundsException after upgrade to 1.2.3
I encountered the same issue recently with one artifact. I got multiple artifacts from a multi-module maven project that are released to nexus by another job, then several similar scripted pipeline jobs for deploying different artifacts, with all of them using an Artifact parameter with the same artifact configured.With one of them, I encounter this error (whether using the job parameter or a hardcoded version, the configured version in the step being overriden by the job parameter anyway according to the log “Overriding configured version ... with version ... from build parameter”).The {{IndexOutOfBoundException}} itself comes from a mistake in the code in [ReleasedVersionRangeResolver|https://github.com/jenkinsci/repository-connector-plugin/blob/master/src/main/java/org/jvnet/hudson/plugins/repositoryconnector/aether/ReleasedVersionRangeResolver.java] : before accessing the first entry in {{vs}} collection, there is a check on {{versions}} collection instead of the filtered {{vs}} collection; with a test on the filtered collection, the method would return {{null}} instead of raising an exception, though this would possibly raise an exception down the line anyway. In my case and the OP's though, we should not even enter this method, as we specify a single version and not a version range: I've yet to identify why in this case I end up there, while I do not with other artifacts.Edit: I might have found the cause: in the final pom of my artifact, I do have a dependency defined as a range, and the corresponding artifact is not present on the same repository (the artifact I want is on a private repository, the ranged dependency is on central); I cannot confirm yet this is the cause, but it seems likely considering the error occurs within {{Aether.resolve}} and the dependencies collection.[~vlastimil_dolejs] (and [~justinm89]) do you also happen to have a dependency with a version range on the artifact you encounter the error with? (check the {{pom.xml}} of the artifact version on your repository)However, considering this plugin, we should probably ignore dependencies or the requested artifact, should we not?
Add Comment
[JIRA] (JENKINS-56525) Add Filters to Assign Roles page
Title: Message Title Kevin Delord commented on JENKINS-56525 Re: Add Filters to Assign Roles page Oleg Nenashev we were able to quickly create a _javascript_ addon to fulfil our needs and made it open source. https://github.com/smartmobilefactory/jenkins-role-strategy-filter We will integrate the auto update in the following weeks Regarding an official fork+PR: we will estimate how much time we gonna need first. We don't know the project yet and I doubt we will have the resources to implement a solution "short-term". But we gonna try! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56492) [ATH] Fix Javadoc failures on Java11
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-56492 [ATH] Fix Javadoc failures on Java11 Change By: Baptiste Mathus Summary: [ATH] Fix Javadoc failures on Java11 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56579) .mvn/extensions.xml not recognized
Title: Message Title Benjamin Brummer updated an issue Jenkins / JENKINS-56579 .mvn/extensions.xml not recognized Change By: Benjamin Brummer Environment: jenkins 2.164.1 maven-invoker-plugin 2.4ubuntu 18.04.2 masterwindows 7 slaves Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51542) Git checkout is slower than the command line execution
Title: Message Title Antony Gelberg commented on JENKINS-51542 Re: Git checkout is slower than the command line execution Still really slow using git 2.21.0 on Windows Server 2012 R2 slave. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56579) .mvn/extensions.xml not recognized
Title: Message Title Benjamin Brummer created an issue Jenkins / JENKINS-56579 .mvn/extensions.xml not recognized Issue Type: Bug Assignee: Olivier Lamy Components: maven-invoker-plugin Created: 2019-03-15 09:35 Environment: jenkins 2.164.1 Priority: Minor Reporter: Benjamin Brummer We wanted to setup a tycho-pomless build on jenkins, with maven 3.6.0. Running the build without Jenkins works fine. The pom.xml is in a subfolder next to the .mvn/extensions.xml This job only works when the pom.xml is in the workspace root and maven 3.3.9 is used. Useing dir() in a pipeline when calling maven 3.3.9 is working to. We could reproduce this issue with the tycho-example form here too https://github.com/vogellacompany/tycho-example 3.3.9 + code in "sub" [Vogella] $ cmd.exe /C "c:\jenkins\tools\hudson.tasks.Maven_MavenInstallation\3.3.9\bin\mvn.cmd clean verify -V -B --file sub/pom.xml && exit %%ERRORLEVEL%%" Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00) Maven home: c:\jenkins\tools\hudson.tasks.Maven_MavenInstallation\3.3.9 Java version: 1.8.0_202, vendor: Oracle Corporation Java home: c:\jenkins\tools\hudson.model.JDK\8\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos" [INFO] Scanning for projects... [ERROR] [ERROR] Some problems were encountered while processing the POMs: [ERROR] Child module C:\jenkins\workspace\Vogella\sub\bundles\com.vogella.logging.config\pom.xml of C:\jenkins\workspace\Vogella\sub\bundles\pom.xml does not exist @ [ERROR] Child module
[JIRA] (JENKINS-56578) Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master
Title: Message Title Remi Van Goethem updated an issue Jenkins / JENKINS-56578 Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master Change By: Remi Van Goethem Environment: JenkinsVersion detailsVersion: 2. 136 168 Mode: WARUrl: http:// uksudvjen.usr. ***.loc/ JavaHome: /usr/lib/jvm/java-8-openjdk-amd64/jreVendor: Oracle CorporationVersion: 1.8.0_171Maximum memory: 1.73 GB (1860698112)Allocated memory: 910 1 . 50 MB 68 GB ( 954728448 1806172160 )Free memory: 309 125 . 06 17 MB ( 324069424 131247024 )In-use memory: 601 1 . 44 MB 56 GB ( 630659024 1674925136 )GC strategy: ParallelGCJava Runtime SpecificationName: Java Platform API SpecificationVendor: Oracle CorporationVersion: 1.8JVM SpecificationName: Java Virtual Machine SpecificationVendor: Oracle CorporationVersion: 1.8JVM ImplementationName: OpenJDK 64-Bit Server VMVendor: Oracle CorporationVersion: 25.171-b11Operating systemName: LinuxArchitecture: amd64Version: 4.4.0- 62 128 -genericDistribution: Ubuntu 16.04.4 LTSProcess ID: 9196 26546 ( 0x23ec 0x67b2 )Process started: 2018 2019 - 08 03 - 08 07 13 06 : 19 52 : 28 58 . 534 738 +Process uptime: 1 min 8 sec day 16 hr JVM startup parameters:Boot classpath: /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/resources.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/rt.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/jsse.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/jce.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/charsets.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/jfr.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/classesClasspath: /usr/share/jenkins/jenkins.warLibrary path: /usr/java/packages/lib/amd64:/usr/lib/x86_64-linux-gnu/jni:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/usr/lib/jni:/lib:/usr/libarg[0]: -Djava.awt.headless=truearg[1]: -Dhudson.model.DirectoryBrowserSupport.CSP=Important configurationSecurity realm: hudson.security.LDAPSecurityRealmAuthorization strategy: hudson.security.GlobalMatrixAuthorizationStrategyCSRF Protection: trueInitialization Milestone: Completed initializationSupport bundle anonymization: falseActive Pluginsace-editor:1.1 '_javascript_ GUI Lib: ACE Editor bundle plugin'active-directory:2. 8 12 'Jenkins Active Directory plugin'all-changes:1.5 'All changes plugin'analysis-collector: 1 2 . 52 0.0 'Static Analysis Collector Plug-in'analysis-core:1.95 'Static Analysis Utilities' analysis-model-api:2.1.2 'Analysis Model API Plug-in'ansible:1.0 'Jenkins Ansible plugin' ansicolor:0. 5 6 .2 'AnsiColor'ant:1. 8 9 'Ant Plugin'antisamy-markup-formatter:1.5 'OWASP Markup Formatter Plugin'apache-httpcomponents-client-4-api:4.5.5-3.0 'Jenkins Apache HttpComponents Client 4.x API Plugin'artifact-promotion:0.5.1 'artifact-promotion'artifactdeployer:1.2 'Jenkins Artifact Deployer Plug-in'async-http-client:1.9.40.0 'Async Http Client'authentication-tokens:1.3 'Authentication Tokens API Plugin' avatar:1.2 'Avatar Plugin' badge:1. 5 7 'Badge' basic-branch-build-strategies:1.1.1 'Basic Branch Build Strategies Plugin' behave-testresults-publisher:0.0.11 'behave-testresults-publisher'bitbucket:1.1.8 'Jenkins Bitbucket Plugin'bitbucket-approve:1.0.3 'Bitbucket Approve Plugin'bitbucket-oauth:0. 7 9
[JIRA] (JENKINS-56578) Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master
Title: Message Title Remi Van Goethem created an issue Jenkins / JENKINS-56578 Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master Issue Type: Bug Assignee: Richard Bywater Components: core, htmlpublisher-plugin Created: 2019-03-15 09:21 Environment: Jenkins Version details Version: 2.136 Mode: WAR Url: http:// Java Home: /usr/lib/jvm/java-8-openjdk-amd64/jre Vendor: Oracle Corporation Version: 1.8.0_171 Maximum memory: 1.73 GB (1860698112) Allocated memory: 910.50 MB (954728448) Free memory: 309.06 MB (324069424) In-use memory: 601.44 MB (630659024) GC strategy: ParallelGC Java Runtime Specification Name: Java Platform API Specification Vendor: Oracle Corporation Version: 1.8 JVM Specification Name: Java Virtual Machine Specification Vendor: Oracle Corporation Version: 1.8 JVM Implementation Name: OpenJDK 64-Bit Server VM Vendor: Oracle Corporation Version: 25.171-b11 Operating system Name: Linux Architecture: amd64 Version: 4.4.0-62-generic Distribution: Ubuntu 16.04.4 LTS Process ID: 9196 (0x23ec) Process started: 2018-08-08 07:19:28.534+ Process uptime: 1 min 8 sec JVM startup parameters: Boot classpath: /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/resources.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/rt.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/jsse.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/jce.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/charsets.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/jfr.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/classes Classpath: /usr/share/jenkins/jenkins.war Library path: /usr/java/packages/lib/amd64:/usr/lib/x86_64-linux-gnu/jni:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/usr/lib/jni:/lib:/usr/lib arg[0]: -Djava.awt.headless=true arg[1]: -Dhudson.model.DirectoryBrowserSupport.CSP= Important configuration Security realm: hudson.security.LDAPSecurityRealm Authorization strategy: hudson.security.GlobalMatrixAuthorizationStrategy CSRF Protection: true Initialization Milestone: Completed initialization Support bundle anonymization: false Active Plugins ace-editor:1.1 '_javascript_ GUI Lib: ACE Editor bundle plugin' active-directory:2.8 'Jenkins Active Directory plugin' all-changes:1.5 'All changes plugin' analysis-collector:1.52 'Static Analysis Collector Plug-in' analysis-core:1.95 'Static Analysis Utilities' ansicolor:0.5.2 'AnsiColor' ant:1.8 'Ant Plugin' antisamy-markup-formatter:1.5 'OWASP Markup Formatter Plugin' apache-httpcomponents-client-4-api:4.5.5-3.0 'Jenkins Apache HttpComponents Client 4.x API Plugin'
[JIRA] (JENKINS-56011) UI fails to set ECS Task Creation Timeout
Title: Message Title Andreas Sieferlinger commented on JENKINS-56011 Re: UI fails to set ECS Task Creation Timeout this seems to be fixed in the current state of the github repo (altough not released) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56536) currentBuild.currentResult not set to failed
Title: Message Title Christoph Läubrich commented on JENKINS-56536 Re: currentBuild.currentResult not set to failed We also have this problem, this is critical for us since now all E-Mails and anouncements always state that the build is successfull! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56536) currentBuild.currentResult not set to failed
Title: Message Title Christoph Läubrich updated an issue Jenkins / JENKINS-56536 currentBuild.currentResult not set to failed Change By: Christoph Läubrich 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-56101) ECS plugin - can't overwrite inheritFrom
Title: Message Title Andreas Sieferlinger commented on JENKINS-56101 Re: ECS plugin - can't overwrite inheritFrom see https://github.com/jenkinsci/amazon-ecs-plugin/pull/82 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56577) Unable to add Jira Site
Title: Message Title Dhananjay Patade created an issue Jenkins / JENKINS-56577 Unable to add Jira Site Issue Type: Bug Assignee: Unassigned Components: jira-plugin Created: 2019-03-15 08:51 Environment: Jenkins Version: 2.150.3 Jira plugin: 3.0.5 Priority: Blocker Reporter: Dhananjay Patade Not able to add Jira site in Jenkins. Steps to reproduce: 1 Login to Jenkins (localhost:8080) 2. Select Manage Jenkins 3. Go to JIRA sites and click on Add 4. Enter your Jira URL, user name and password 5. Click on Test Connection It fails with below error java.lang.NoSuchMethodError: okhttp3.HttpUrl.get(Ljava/lang/String;)Lokhttp3/HttpUrl; at retrofit2.Retrofit$Builder.baseUrl(Retrofit.java:458) at org.thoughtslive.jenkins.plugins.jira.service.JiraService.(JiraService.java:49) at org.thoughtslive.jenkins.plugins.jira.Site$DescriptorImpl.doValidateBasic(Site.java:183) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) Add Comment
[JIRA] (JENKINS-56577) Unable to add Jira Site
Title: Message Title Dhananjay Patade created an issue Jenkins / JENKINS-56577 Unable to add Jira Site Issue Type: Bug Assignee: Unassigned Components: jira-plugin Created: 2019-03-15 08:51 Environment: Jenkins Version: 2.150.3 Jira plugin: 3.0.5 Priority: Blocker Reporter: Dhananjay Patade Not able to add Jira site in Jenkins. Steps to reproduce: 1 Login to Jenkins (localhost:8080) 2. Select Manage Jenkins 3. Go to JIRA sites and click on Add 4. Enter your Jira URL, user name and password 5. Click on Test Connection It fails with below error java.lang.NoSuchMethodError: okhttp3.HttpUrl.get(Ljava/lang/String;)Lokhttp3/HttpUrl; at retrofit2.Retrofit$Builder.baseUrl(Retrofit.java:458) at org.thoughtslive.jenkins.plugins.jira.service.JiraService.(JiraService.java:49) at org.thoughtslive.jenkins.plugins.jira.Site$DescriptorImpl.doValidateBasic(Site.java:183) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) Add Comment
[JIRA] (JENKINS-56576) Whitesource-plugin changed product name
Title: Message Title Slawomir Wieczorkowski updated an issue Jenkins / JENKINS-56576 Whitesource-plugin changed product name Change By: Slawomir Wieczorkowski Attachment: jenkins_output.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56576) Whitesource-plugin changed product name
Title: Message Title Slawomir Wieczorkowski commented on JENKINS-56576 Re: Whitesource-plugin changed product name It may be related to fact that MultiBranch pipeline type is used. Anyway I think it should be possibility to keep product name as provided and project version should be always product - productVersion. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56576) Whitesource-plugin changed product name
Title: Message Title
Slawomir Wieczorkowski created an issue
Jenkins / JENKINS-56576
Whitesource-plugin changed product name
Issue Type:
Bug
Assignee:
Unassigned
Components:
whitesource-plugin
Created:
2019-03-15 08:30
Environment:
Jenkins ver. 2.150.3 WhiteSource plugin 19.1.1 Pipelines scripted
Priority:
Critical
Reporter:
Slawomir Wieczorkowski
Hi, I use whitesource plugin within scripted Pipelines at groovy: def scanStep() { script.echo " *** start WhiteSource scan ***" script.echo "productName: ${this.productName}" script.echo "productVersion: ${this.productVersion}" script.echo "includes: ${this.includes}" script.echo "excluded: ${this.excludes}" script.whitesource jobApiToken: this.jobApiToken, jobCheckPolicies: 'global', jobForceUpdate: 'global', libIncludes: this.includes, libExcludes: this.excludes, product: this.productName, productVersion: this.productVersion script.echo "*** stop WhiteSource scan ***" } Execution Console output: 07:31:52 *** start WhiteSource scan **[Pipeline] echo*07:31:52 productName: node-js-sample[Pipeline] echo*07:31:52* productVersion: 1.1.1-devel[Pipeline] echo*07:31:52* includes: */.js[Pipeline] echo*07:31:52* excluded: [Pipeline] whitesource*07:31:52* Updating White Source.07:31:52 Collecting OSS usage information*07:31:52* Starting generic job on /myworkspace*07:31:53* Job finished.07:31:53 WhiteSource Service URL:07:31:53 Checking policies*07:31:52* Scanning folder ojects_MD_jpl-sample-npm_develop*07:31:53* Found 322 dependencies matching include / exclude pattern in folder.07:32:55 Generating policy check report*07:32:55* Some dependencies violate open source policies, however all were force updated to
[JIRA] (JENKINS-32087) Configure JIRA credentials at the Job configuration level
Title: Message Title Adrien Lecharpentier commented on JENKINS-32087 Re: Configure JIRA credentials at the Job configuration level At this moment, the plugin is using credentials-plugin to store the username/password to connect the a Jira server. It was not the case when this ticket was created but only since 3.0.0 (May 20th, 2018). The thing is, from what I see, the plugin allow to configure Jira connection on the global level only. So that we can maximize the connection details usage. Having the connection details configurable on the job / folder level might go in the opposite direction (not really in the folder case but bear with me). I didn't see any step / action in the plugin requiring any credentials, as they all JiraSite#get to find the Jira configuration required for project. I'm not saying we couldn't make this happen, I'm just wondering about the need to have the Jira server connection configurable on job level, as most of the time (all the time?) the connection is configured by an administrator. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-5393) Jenkins falsely fails builds due to aggressive up-to-date check on junit artifacts
Title: Message Title Carlos Garcia commented on JENKINS-5393 Re: Jenkins falsely fails builds due to aggressive up-to-date check on junit artifacts I have a similar problem. Even though my clocks are in sync (agents and master), Jenkins complains about them being out of sync. I agree with you, making this "magic number" of 1000 configurable, or even disabling this unnecessary check, is necessary. Given that this is a 9-year-old bug I don't expect this to be fixed; I'll try to modify this behaviour myself and build Jenkins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49521) Trivial rebase is not triggering build
Title: Message Title wushu zh commented on JENKINS-49521 Re: Trivial rebase is not triggering build I meet this issue with Jenkins 2.150.3 and gerrit plugin 2.27.7. If there is some fix plan 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.
