[JIRA] (JENKINS-54714) Allow downloading raw CSV data for external processing
Title: Message Title Alberto Mardegan created an issue Jenkins / JENKINS-54714 Allow downloading raw CSV data for external processing Issue Type: Improvement Assignee: Veaceslav Gaidarji Components: plot-plugin Created: 2018-11-20 07:58 Priority: Minor Reporter: Alberto Mardegan It would be nice to have a way to download the CSV historical data, so that the user could process them offline via some external tool. While I suspect that a way to download the files might already exist, I was not able to find it. Add Comment
[JIRA] (JENKINS-54708) org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20:
Title: Message Title kboz edited a comment on JENKINS-54708 Re: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20: com/trilead/ssh2/crypto/Base64 Same problem, same solution as above. Downgrading only the SSH Slaves plugin to 1.28.1 is working for us on Jenkins 2.152 Thanks to Kurt (y) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54708) org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20:
Title: Message Title kboz commented on JENKINS-54708 Re: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20: com/trilead/ssh2/crypto/Base64 Same problem, same solution as above. Downgrading only the SSH Slaves plugin to 1.28.1 is working for us on Jenkins 2.152 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54713) UI Exception after upgraden plugins
Title: Message Title
Norbert Pfistner updated an issue
Jenkins / JENKINS-54713
UI Exception after upgraden plugins
Change By:
Norbert Pfistner
After updating some plugins jenkins ui is rendered unusable.It shows very shorty the expacted page but the switches to a broken page only showing some kind of stacktrace/broken page mixture. The same stacktrace is also in the logfile:{noformat}Caused by: java.lang.NoClassDefFoundError: com/trilead/ssh2/crypto/Base64at hudson.plugins.translation.L10nDecorator.encodeRecording(L10nDecorator.java:97)at sun.reflect.GeneratedMethodAccessor222.invoke(Unknown Source)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:498)at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258)at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104)at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74)at org.apache.commons.jelly.parser.EscapingExpression.evaluate(EscapingExpression.java:24)at org.apache.commons.jelly.impl.ExpressionScript.run(ExpressionScript.java:66)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)... 72 more{noformat} The plugins I updated should be the following ones:{noformat}ls -lrt jenkins/plugins-rw-r--r-- 1 281390 20. Nov 07:26 branch-api.jpi-rw-r--r-- 1 51513 20. Nov 07:26 durable-task.jpi-rw-r--r-- 1 215545 20. Nov 07:26 cloudbees-folder.jpi-rw-r--r-- 1 2599005 20. Nov 07:26 git-client.jpi-rw-r--r-- 1 385003 20. Nov 07:26 trilead-api.jpi-rw-r--r-- 1 104090 20. Nov 07:26 ssh-slaves.jpi-rw-r--r-- 1 26561 20. Nov 07:26 display-url-api.jpi-rw-r--r-- 1 154949 20. Nov 07:26 workflow-api.jpi-rw-r--r-- 1 19109 20. Nov 07:26 pipeline-graph-analysis.jpidrwxr-xr-x 4 4096 20. Nov 07:27 trilead-apidrwxr-xr-x 4 4096 20. Nov 07:27 git-clientdrwxr-xr-x 4 4096 20. Nov 07:27 workflow-apidrwxr-xr-x 5 4096 20. Nov 07:27 cloudbees-folderdrwxr-xr-x 4 4096 20. Nov 07:27
[JIRA] (JENKINS-54668) Unable to provide NodeJS path to Jenkins plugin
Title: Message Title Nikolas Falco commented on JENKINS-54668 Re: Unable to provide NodeJS path to Jenkins plugin /usr/local/nodejs is the nodejs home path Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54713) UI Exception after upgraden plugins
Title: Message Title Norbert Pfistner created an issue Jenkins / JENKINS-54713 UI Exception after upgraden plugins Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: trilead-api-plugin Created: 2018-11-20 07:40 Environment: Jenkins ver. 2.151 Priority: Blocker Reporter: Norbert Pfistner After updating some plugins jenkins ui is rendered unusable. It shows very shorty the expacted page but the switches to a broken page only showing some kind of stacktrace/broken page mixture. The same stacktrace is also in the logfile: Caused by: java.lang.NoClassDefFoundError: com/trilead/ssh2/crypto/Base64 at hudson.plugins.translation.L10nDecorator.encodeRecording(L10nDecorator.java:97) at sun.reflect.GeneratedMethodAccessor222.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at
[JIRA] (JENKINS-54708) org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20:
Title: Message Title Denis Shvedchenko edited a comment on JENKINS-54708 Re: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20: com/trilead/ssh2/crypto/Base64 yep, it caused by SSH Slaves plugin 1.29.0, also downgrade fixed this issue. FYI: [~ifernandezcalvo] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54708) org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20:
Title: Message Title Denis Shvedchenko commented on JENKINS-54708 Re: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20: com/trilead/ssh2/crypto/Base64 yep, it caused by SSH Slaves plugin 1.29.0, also downgrade fixed this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54708) org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20:
Title: Message Title Kurt commented on JENKINS-54708 Re: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20: com/trilead/ssh2/crypto/Base64 Finally I was able to remove the Ooops by downgrading the SSH Slaves plugin from 1.29.0 to 1.28.1. Sounds like at least my problem was related to the breaking change mentioned in the changelog: It does not longer use the Trilead-ssh2 library provided by the core, it now uses Trilead-api plugin. However, I'm not really sure what it means as I cannot find a Trailed-api plugin in the plugin manager (and sorry, I'm not a Java developer). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54061) org.apache.commons.jelly.impl.TagScript.handleException
Title: Message Title Federico Pellegrin updated an issue Jenkins / JENKINS-54061 org.apache.commons.jelly.impl.TagScript.handleException Change By: Federico Pellegrin Component/s: ssh-slaves-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-54061) org.apache.commons.jelly.impl.TagScript.handleException
Title: Message Title Federico Pellegrin commented on JENKINS-54061 Re: org.apache.commons.jelly.impl.TagScript.handleException Just to pin down a bit more the issue: I just tried to manually install 1.28.1 and all works well, so the jump 1.28.1 to 1.29.0 is the game breaker indeed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54712) after update ssh-slave plugin to 1.29.0 just stacktrace in browser
Title: Message Title Ronny Borchert created an issue Jenkins / JENKINS-54712 after update ssh-slave plugin to 1.29.0 just stacktrace in browser Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: ssh-slaves-plugin Created: 2018-11-20 07:17 Environment: Windows Server 2016 Priority: Blocker Reporter: Ronny Borchert After updating all plugins it comes up that a stacktrace appear on all pages of checkins, nothing really clickable, just access by sub url. After reverting plugin for plugin it comes out it is gone after revert ssh-slaves.plugin with version 1.28.1. org.apache.commons.jelly.JellyTagException: jar:file:/H:/Jenkins/war/WEB-INF/lib/jenkins-core-2.151.jar!/lib/layout/hasPermission.jelly:35:20: com/trilead/ssh2/crypto/Base64org.apache.commons.jelly.JellyTagException: jar:file:/H:/Jenkins/war/WEB-INF/lib/jenkins-core-2.151.jar!/lib/layout/hasPermission.jelly:35:20: com/trilead/ssh2/crypto/Base64 at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:745) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:289) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at
[JIRA] (JENKINS-54061) org.apache.commons.jelly.impl.TagScript.handleException
Title: Message Title Federico Pellegrin commented on JENKINS-54061 Re: org.apache.commons.jelly.impl.TagScript.handleException While the beginning of the stack trace looks same, if I look deeper at mine I can find a more obvious: Caused by: java.lang.NoClassDefFoundError: com/trilead/ssh2/crypto/Base64 As by changelog of 1.29.0: It does not longer use the Trilead-ssh2 library provided by the core, it now uses Trilead-api plugin. But indeed I have the plugin installed (version 1.0.1, the latest) So probably the ticket should be renamed / reclassified better ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54711) jenkins-jobs.mv.db failed
Title: Message Title Владислав Ненашев created an issue Jenkins / JENKINS-54711 jenkins-jobs.mv.db failed Issue Type: Bug Assignee: Unassigned Attachments: jenkins.rar Components: core Created: 2018-11-20 07:15 Priority: Minor Reporter: Владислав Ненашев Hi, we got the following problem: we see a problem in the jenkins log, the file update date was more than a day in the system, in a temporary solution, the jenkins was restarted, after a while it continued to appear. Jenkins 2.138.2 The log in the attachment SELECT ID FROM JENKINS_BUILD WHERE JOB_ID=? AND NUMBER=? [5-196]SELECT ID FROM JENKINS_BUILD WHERE JOB_ID=? AND NUMBER=? [5-196] at org.h2.message.DbException.getJdbcSQLException(DbException.java:345) at org.h2.message.DbException.get(DbException.java:168) at org.h2.message.DbException.convert(DbException.java:295) at org.h2.command.Command.executeQuery(Command.java:215) at org.h2.jdbc.JdbcPreparedStatement.executeQuery(JdbcPreparedStatement.java:111) at org.jenkinsci.plugins.pipeline.maven.dao.PipelineMavenPluginH2Dao.getOrCreateBuildPrimaryKey(PipelineMavenPluginH2Dao.java:400) ... 19 moreCaused by: java.lang.IllegalStateException: Reading from nio:/u01/jenkins/jenkins_home/jenkins-jobs/jenkins-jobs.mv.db failed; file length -1 read length 512 at 99917712 [1.4.196/1] at org.h2.mvstore.DataUtils.newIllegalStateException(DataUtils.java:765) at org.h2.mvstore.DataUtils.readFully(DataUtils.java:435) at org.h2.mvstore.FileStore.readFully(FileStore.java:98) at org.h2.mvstore.Page.read(Page.java:190) at org.h2.mvstore.MVStore.readPage(MVStore.java:1952) at
[JIRA] (JENKINS-54708) org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20:
Title: Message Title
Kurt edited a comment on JENKINS-54708
Re: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20: com/trilead/ssh2/crypto/Base64
*I'm seeing a similar Oops error (see below) when accessing the console log. But for me the problem persists even after downgrading to core 2.151.*Additionally I had another issue with core 2.152 which might be related to the SSL/Crypt error: My 2.152 was not able to access the update servers through our companie's proxy server that needs authentication. Always got a 407 response. So authentication to proxy failed. Reverting back to 2.151 fixed that instantanously.Platform here: Windows Server 2008R2 running Oracle JDK-JRE 1.8.0_152. Jenkins running on Jetty but access through an Nginx reverse proxy.I'll will now first update JRE to latest version. If problem remains I will start downgrading plugins one-by-one and whether the problem disappears. I'll comment here on new findings. +Stack trace:+ { { noformat} java.lang.NoClassDefFoundError: com/trilead/ssh2/crypto/Base64 }} {{ at org.jenkinsci.plugins.workflow.log.ConsoleAnnotators.setAnnotator(ConsoleAnnotators.java:101) }} {{ at org.jenkinsci.plugins.workflow.log.FileLogStorage$1.writeHtmlTo(FileLogStorage.java:248) }} {{ at hudson.console.AnnotatedLargeText.writeLogTo(AnnotatedLargeText.java:144) }} {{ at org.kohsuke.stapler.framework.io.LargeText.doProgressText(LargeText.java:264) }} {{ at hudson.console.AnnotatedLargeText.doProgressiveHtml(AnnotatedLargeText.java:92) }} {{ at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) }} {{ at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) }} {{ at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) }} {{ at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) }} {{ at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:130) }} {{ at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) }} {{ at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) }} {{ Caused: javax.servlet.ServletException }} {{ at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:789) }} {{ at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) }} {{ at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:212) }} {{ 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$10.dispatch(MetaClass.java:384) }} {{ at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) }} {{ at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) }} {{ at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:253) }} {{ 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$5.doDispatch(MetaClass.java:253) }} {{ 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$5.doDispatch(MetaClass.java:253) }} {{ at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) }} {{ at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) }} {{ at
[JIRA] (JENKINS-54686) Use trilead-api plugin instead trilead-ssh2 from core
Title: Message Title king arthur commented on JENKINS-54686 Re: Use trilead-api plugin instead trilead-ssh2 from core thank you, ye yulei, jenkins is back! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54708) org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20:
Title: Message Title
Kurt commented on JENKINS-54708
Re: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20: com/trilead/ssh2/crypto/Base64
I'm seeing a similar Oops error (see below) when accessing the console log. But for me the problem persists even after downgrading to core 2.151. Additionally I had another issue with core 2.152 which might be related to the SSL/Crypt error: My 2.152 was not able to access the update servers through our companie's proxy server that needs authentication. Always got a 407 response. So authentication to proxy failed. Reverting back to 2.151 fixed that instantanously. Platform here: Windows Server 2008R2 running Oracle JDK-JRE 1.8.0_152. Jenkins running on Jetty but access through an Nginx reverse proxy. I'll will now first update JRE to latest version. If problem remains I will start downgrading plugins one-by-one and whether the problem disappears. I'll comment here on new findings. Stack trace: java.lang.NoClassDefFoundError: com/trilead/ssh2/crypto/Base64 {{ at org.jenkinsci.plugins.workflow.log.ConsoleAnnotators.setAnnotator(ConsoleAnnotators.java:101)}} {{ at org.jenkinsci.plugins.workflow.log.FileLogStorage$1.writeHtmlTo(FileLogStorage.java:248)}} {{ at hudson.console.AnnotatedLargeText.writeLogTo(AnnotatedLargeText.java:144)}} {{ at org.kohsuke.stapler.framework.io.LargeText.doProgressText(LargeText.java:264)}} {{ at hudson.console.AnnotatedLargeText.doProgressiveHtml(AnnotatedLargeText.java:92)}} {{ at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)}} {{ at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343)}} {{ at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184)}} {{ at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117)}} {{ at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:130)}} {{ at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)}} {{ at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739)}} Caused: javax.servlet.ServletException {{ at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:789)}} {{ at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870)}} {{ at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:212)}} {{ 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$10.dispatch(MetaClass.java:384)}} {{ at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739)}} {{ at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870)}} {{ at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:253)}} {{ 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$5.doDispatch(MetaClass.java:253)}} {{ 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$5.doDispatch(MetaClass.java:253)}} {{ 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$5.doDispatch(MetaClass.java:253)}} {{ at
[JIRA] (JENKINS-54061) org.apache.commons.jelly.impl.TagScript.handleException
Title: Message Title Björn Pedersen reopened an issue I got a similar stacktrace after upgrading to 1.29.0. This renders the ui unusable, as the trace appears on all pages. Jenkins / JENKINS-54061 org.apache.commons.jelly.impl.TagScript.handleException Change By: Björn Pedersen Resolution: Cannot Reproduce Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54686) Use trilead-api plugin instead trilead-ssh2 from core
Title: Message Title ye yulei commented on JENKINS-54686 Re: Use trilead-api plugin instead trilead-ssh2 from core Using SSH Slaves 1.29.0 to configure the slave page, you can add credentials, but you can't choose. By default, you limit the current and only the current Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54686) Use trilead-api plugin instead trilead-ssh2 from core
Title: Message Title ye yulei commented on JENKINS-54686 Re: Use trilead-api plugin instead trilead-ssh2 from core I also have the same problem. I have rolled back the SSH slave plug-in to the previous version, waiting for repair. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54686) Use trilead-api plugin instead trilead-ssh2 from core
Title: Message Title king arthur commented on JENKINS-54686 Re: Use trilead-api plugin instead trilead-ssh2 from core did someone help to fix it, my jenkins has down for 1 day Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54061) org.apache.commons.jelly.impl.TagScript.handleException
Title: Message Title Federico Pellegrin edited a comment on JENKINS-54061 Re: org.apache.commons.jelly.impl.TagScript.handleException I stumbled at the same problem today (or at least same stack trace) after a multiple plugin update. There was no way to go in the plugin manager via Web or such, so I had to do it on it by hand on the filesystem. The offending plugin resulted to be the ssh-slaves as downgrading just that to the previous backed up version solved the problem.New version creating problem: 1.29.0My previous version: 1.26 On the upgrade instruction indeed there is a warning:"Warning: the new version of this plugin claims to use a different settings format than the installed version. Jobs using this plugin may need to be reconfigured, and/or you may not be able to cleanly revert to the prior version without manually restoring old settings. Consult the plugin release notes for details." But I would still expect it to be caught so I can eventually reconfigure the plugin / jobs via UI. Jenkins version: both 2.150 and 2.152 behaved the same.Platform: LinuxJava:java.runtime.name OpenJDK Runtime Environmentjava.runtime.version 1.8.0_65-b17 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54061) org.apache.commons.jelly.impl.TagScript.handleException
Title: Message Title Federico Pellegrin commented on JENKINS-54061 Re: org.apache.commons.jelly.impl.TagScript.handleException I stumbled at the same problem today (or at least same stack trace) after a multiple plugin update. There was no way to go in the plugin manager via Web or such, so I had to do it on it by hand on the filesystem. The offending plugin resulted to be the ssh-slaves as downgrading just that to the previous backed up version solved the problem. New version creating problem: 1.29.0 My previous version: 1.26 On the upgrade instruction indeed there is a warning: "Warning: the new version of this plugin claims to use a different settings format than the installed version. Jobs using this plugin may need to be reconfigured, and/or you may not be able to cleanly revert to the prior version without manually restoring old settings. Consult the plugin release notes for details." But I would still expect it to be caught so I can eventually reconfigure the plugin / jobs via UI. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54493) ALM Octane CI in Configure System throws exception
Title: Message Title Daniel Gront assigned an issue to Radi Berkovich Jenkins / JENKINS-54493 ALM Octane CI in Configure System throws exception Change By: Daniel Gront Assignee: Michael Seldin Radi Berkovich Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54622) [MC 3.0] [Jenkins latest Version] when trying to add server for testing in jenkins page, it will return exception "url MUST NOT be null nor empty"
Title: Message Title Daniel Gront closed an issue as Fixed Jenkins / JENKINS-54622 [MC 3.0] [Jenkins latest Version] when trying to add server for testing in jenkins page, it will return exception "url MUST NOT be null nor empty" Change By: Daniel Gront Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54686) Use trilead-api plugin instead trilead-ssh2 from core
Title: Message Title Mike Corum reopened an issue Can this "fix" be reversed? It completely breaks all uses of the SSH Slaves plugin. Any job using this plugin immediately gets a stack trace with a ClassNotFoundException with the trilead ssh2 Base64 class. This includes being at the very latest release of Jenkins and the latest of all other plugins. I tried reverting the Jenkins to the previous release but it didn't help. Jenkins / JENKINS-54686 Use trilead-api plugin instead trilead-ssh2 from core Change By: Mike Corum Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54686) Use trilead-api plugin instead trilead-ssh2 from core
Title: Message Title Mike Corum commented on JENKINS-54686 Re: Use trilead-api plugin instead trilead-ssh2 from core This "fix" busted all my jobs that use SSH slaves - they all get a classNotFoundException on the trilead/ssh2/Base64 class. I assumed there was some other dependency that this required so I made sure to be on the very latest Jenkins and the very latest of all my plugins. It still broke everything. What do we have to do in order to make this version work? It's seriously busted. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54668) Unable to provide NodeJS path to Jenkins plugin
Title: Message Title Monali Chaudhary commented on JENKINS-54668 Re: Unable to provide NodeJS path to Jenkins plugin I did below steps now: Downloaded the tar for nodev8.9.4 Created folder nodejs under /usr/local moved the node js tar file under the nodejs folder Executed the cmd: sudo tar -C /usr/local/nodejs --strip-components 1 -xzf node-v8.9.4-linux-x64.tar.gz Linked /usr/local/bin/node to executable in /usr/local/nodejs/bin/node Updated Jenkins NOdejs Installation path --> /usr/local/nodejs/bin But I am still getting the same error $ node -v v8.9.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-54710) GitException was not retried in shared libraries fetcher
Title: Message Title Ted created an issue Jenkins / JENKINS-54710 GitException was not retried in shared libraries fetcher Issue Type: Bug Assignee: Unassigned Components: workflow-cps-global-lib-plugin Created: 2018-11-20 05:29 Priority: Minor Reporter: Ted https://github.com/jenkinsci/workflow-cps-global-lib-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/libs/SCMSourceRetriever.java#L129 GitException is not subclass of IOException org.eclipse.jgit.errors.NoRemoteRepositoryException: X: fatal: remote error: Server busy Bitbucket is currently under heavy load and is not able to service your request. Please wait briefly and try your request again. at org.eclipse.jgit.transport.TransportGitSsh.cleanNotFound(TransportGitSsh.java:209) at org.eclipse.jgit.transport.TransportGitSsh$SshFetchConnection.(TransportGitSsh.java:290) at org.eclipse.jgit.transport.TransportGitSsh.openFetch(TransportGitSsh.java:162) at org.eclipse.jgit.api.LsRemoteCommand.execute(LsRemoteCommand.java:198) Caused: org.eclipse.jgit.api.errors.TransportException: X: fatal: remote error: Server busy Bitbucket is currently under heavy load and is not able to service your request. Please wait briefly and try your request again. at org.eclipse.jgit.api.LsRemoteCommand.execute(LsRemoteCommand.java:221) at org.eclipse.jgit.api.LsRemoteCommand.call(LsRemoteCommand.java:159) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.getRemoteReferences(JGitAPIImpl.java:787) Caused: hudson.plugins.git.GitException at org.jenkinsci.plugins.gitclient.JGitAPIImpl.getRemoteReferences(JGitAPIImpl.java:801) at jenkins.plugins.git.AbstractGitSCMSource.retrieve(AbstractGitSCMSource.java:708) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:598) at
[JIRA] (JENKINS-54401) NPE when parsing scm git revision date on PR branches
Title: Message Title Joseph Petersen commented on JENKINS-54401 Re: NPE when parsing scm git revision date on PR branches Seems to have resolved itself: INFRA-1868 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54708) org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20:
Title: Message Title Jethro Leevers updated an issue Jenkins / JENKINS-54708 org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20: com/trilead/ssh2/crypto/Base64 Change By: Jethro Leevers Environment: Windows Server 2012 R2 Standard java version "1.8.0_171"Java(TM) SE Runtime Environment (build 1.8.0_171-b11)Java HotSpot(TM) 64-Bit Server VM (build 25.171-b11, mixed mode) Build Pipeline Plugin 1.5.8Build Timeout 1.19CVS Plug-in 2.14Dependency Graph Viewer Plugin 0.13Dependency Queue Plugin 1.1Email Extension Plugin 2.63Extra Columns Plugin 1.20Fail The Build Plugin 1.0GitHub Organization Folder Plugin 1.6Gradle Plugin 1.29Green Balls 1.15Icon Shim Plugin 2.0.3IRC Plugin 2.30NodeJS Plugin 1.2.7Pipeline 2.6Priority Sorter Plugin 3.6.0SSH Slaves plugin 1.29.0ThinBackup 1.9Timestamper 1.8.10Translation Assistance plugin 1.16 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54709) Docker Agent templates could not chose SSH Credentials
Title: Message Title
king arthur created an issue
Jenkins / JENKINS-54709
Docker Agent templates could not chose SSH Credentials
Issue Type:
Bug
Assignee:
Devin Nusbaum
Attachments:
7.png
Components:
ssh-credentials-plugin
Created:
2018-11-20 03:37
Environment:
Jenkins ver. 2.152 Docker plugin ver 1.1.5
Labels:
jenkins
Priority:
Blocker
Reporter:
king arthur
20-Nov-2018 11:12:06.870 INFO [main] org.apache.catalina.core.ApplicationContext.log ContextListener: contextInitialized() 20-Nov-2018 11:12:06.870 INFO [main] org.apache.catalina.core.ApplicationContext.log SessionListener: contextInitialized() 20-Nov-2018 11:12:06.871 INFO [main] org.apache.catalina.core.ApplicationContext.log ContextListener: attributeAdded('StockTicker', 'async.Stockticker@45072949') 20-Nov-2018 11:13:00.838 SEVERE [Handling POST /jenkins/descriptorByName/org.jvnet.hudson.plugins.SSHBuildWrapper/fillCredentialIdItems from 10.10.15.210 : http-nio-8080-exec-3] org.apache.catalina.core.ApplicationContext.log Error while serving http://10.1.14.206:8080/jenkins/descriptorByName/org.jvnet.hudson.plugins.SSHBuildWrapper/fillCredentialIdItems java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:347) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at
[JIRA] (JENKINS-44849) Changeset for first run of generated job is empty
Title: Message Title Nathan Mische commented on JENKINS-44849 Re: Changeset for first run of generated job is empty I just ran into this today. Any update on this issue? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54699) Durable Task Version 1.28 break jenkins pipeline
Title: Message Title Vivek Pandey commented on JENKINS-54699 Re: Durable Task Version 1.28 break jenkins pipeline Devin Nusbaum maybe caused due to https://issues.jenkins-ci.org/plugins/servlet/mobile#issue/JENKINS-50902? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54289) Create year round GSoC schedule
Title: Message Title Lloyd Chang updated JENKINS-54289 Jenkins / JENKINS-54289 Create year round GSoC schedule Change By: Lloyd Chang Status: Open Fixed but Unreleased Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54289) Create year round GSoC schedule
Title: Message Title Lloyd Chang commented on JENKINS-54289 Re: Create year round GSoC schedule (attached) sched.pdf and (above) google calendar link resolve this JENKINS-54289 i granted Martin d'Anjou Jeff Pearce Oleg Nenashev permission to make changes and manage sharing of the calendar Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54708) org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20:
Title: Message Title Jethro Leevers created an issue Jenkins / JENKINS-54708 org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20: com/trilead/ssh2/crypto/Base64 Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-11-20 01:22 Environment: Windows Server 2012 R2 Standard Build Pipeline Plugin 1.5.8 Build Timeout 1.19 CVS Plug-in 2.14 Dependency Graph Viewer Plugin 0.13 Dependency Queue Plugin 1.1 Email Extension Plugin 2.63 Extra Columns Plugin 1.20 Fail The Build Plugin 1.0 GitHub Organization Folder Plugin 1.6 Gradle Plugin 1.29 Green Balls 1.15 Icon Shim Plugin 2.0.3 IRC Plugin 2.30 NodeJS Plugin 1.2.7 Pipeline 2.6 Priority Sorter Plugin 3.6.0 SSH Slaves plugin 1.29.0 ThinBackup 1.9 Timestamper 1.8.10 Translation Assistance plugin 1.16 Labels: jenkins exception Priority: Minor Reporter: Jethro Leevers After updating jenkins to 2.152 I get the following error on all pages org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20: com/trilead/ssh2/crypto/Base64 at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:745) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:289) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at
[JIRA] (JENKINS-54289) Create year round GSoC schedule
Title: Message Title Lloyd Chang updated an issue Jenkins / JENKINS-54289 Create year round GSoC schedule Change By: Lloyd Chang Attachment: sched.pdf Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54289) Create year round GSoC schedule
Title: Message Title Lloyd Chang commented on JENKINS-54289 Re: Create year round GSoC schedule https://calendar.google.com/calendar?cid=NW9vNjYxbXFnZHExb2pvMTI3YWZxaTlvc2dAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54645) Send queue data in JSON Payload
Title: Message Title Mike Delaney closed an issue as Duplicate Jenkins / JENKINS-54645 Send queue data in JSON Payload Change By: Mike Delaney Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54628) Poll error when no view in Manual workspace for stream
Title: Message Title Dave Miller commented on JENKINS-54628 Re: Poll error when no view in Manual workspace for stream It seems likely that this is related to similar null pointer exceptions that popped up in pipeline syncs with the same sort of workspace specs since upgrading to 1.9.4. It's made a minor mess of log parsing. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54694) PTC integrity plugin throw error for project not registered in the current server
Title: Message Title jian gao updated an issue Jenkins / JENKINS-54694 PTC integrity plugin throw error for project not registered in the current server Change By: jian gao when I create a job for integrity and do build, the console output as following:Started by user AdministratorBuilding in workspace C:\Program Files (x86)\Jenkins\workspace\integrityDocs[Local Client] Checkout started using local client for :/ProjectsPreparing to execute si projectinfo for /Projects[Local Client] An API Exception was caught!The project /Projects could not be located on the server CYSVR037ALM01:7001: MKS125211: The project file /Projects is not registered with the current server.si projectinfo --user=administrator --port=7001 --hostname=CYSVR037ALM01 --project=/Projects -- – returned exit code 128ERROR: [Local Client] Caught Integrity APIException!Finished: FAILURE Anyone who can Can anyone help me on this issue? thx 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-28010) Use Google Apps group for Authorization
Title: Message Title Ben Walding commented on JENKINS-28010 Re: Use Google Apps group for Authorization Ryan Campbell - in regards your pondering of Org Unit vs. Groups - my feeling is that mapping groups from GSuite to Jenkins makes the most sense. Org Units are much more limiting since a user only exists in a single Org Unit (although OUs are hierarchical). If you look at how GCP (Google Cloud) works, they let you assign groups directly into the permissions lists - so I can have engineering-tea...@example.com as a group with permissions on a given project etc. The Google API for managing / querying users as groups is solid and well-documented - happy to discuss when you're available - you know where I am! Christopher Orr - in regards your question about the API - the API is a bit finicky to setup initially. You have two options for calling the API a service account with appropriate scopes / permissions assigned a set of OAuth tokens for the "Jenkins" (or app), those token can then be used to issue an OAuth request (with required scopes) - which is basically a URL that a human will click on to generate a token. That token is then used by the Jenkins / app to issue directory HTTP requests. The guidance from Google is that you can't use hard-coded tokens in OSS products (so Jenkins can't have a set burned in) - my gut feeling is that the most expedient way for Jenkins to work would be for end-users to create service accounts (this is not a GSuite user, but essentially a set of tokens) with the correct scopes. The service account credentials would then be entered into Jenkins as another pair of credential fields. This guide is the one I used - https://developers.google.com/admin-sdk/directory/v1/quickstart/go (There are Java versions of the same thing if that's more your style). The example uses the "app" style token setup (rather than service account style setup) Add Comment This message was sent by
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down I'm trying to test this but breaking changes keep stacking up for me: https://issues.jenkins-ci.org/browse/JENKINS-54686. I've disabled credentials tracking but I'll need to manually load 1.28.1 or wait for a version of SSH Slaves that has trilead-ssh2 restored. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51998) Pipeline serialization fails on Java 10: java.lang.NoClassDefFoundError: Could not initialize class org.jboss.marshalling.river.RiverMarshaller
Title: Message Title Samuel Gabriel reopened an issue This issue is not resolved. We are experiencing this issue again with our Jenkins installation. It happens with a very simple pipeline that calls npm build We are using Jenkins 2.152 Pipeline Support 2.22 Here is the stacktrace: // code placeholder Nov 19, 2018 7:31:45 PM org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService reportProblemNov 19, 2018 7:31:45 PM org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService reportProblemWARNING: Unexpected exception in CPS VM thread: CpsFlowExecution[Owner[live-chat-feature/9:live-chat-feature #9]]java.lang.NoClassDefFoundError: Could not initialize class org.jboss.marshalling.river.RiverMarshaller at org.jboss.marshalling.river.RiverMarshallerFactory.createMarshaller(RiverMarshallerFactory.java:54) at org.jenkinsci.plugins.workflow.support.pickles.serialization.RiverWriter.(RiverWriter.java:136) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:480) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:458) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgramIfPossible(CpsThreadGroup.java:445) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:372) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$200(CpsThreadGroup.java:83) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:244) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:232) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) 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.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:514) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1135) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) at java.base/java.lang.Thread.run(Thread.java:844) Not sure if it is related by numerous errors appear before that regarding the atomic file locked by another process. Nov 19, 2018 7:31:45 PM org.jenkinsci.plugins.workflow.cps.CpsThreadGroup saveProgramIfPossibleNov 19, 2018 7:31:45 PM org.jenkinsci.plugins.workflow.cps.CpsThreadGroup saveProgramIfPossibleWARNING: program state save failedjava.io.IOException: Unable to delete 'C:\Jenkins\jobs\live-chat-feature\builds\9\atomic2269173168243097261.tmp'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. at hudson.Util.deleteFile(Util.java:277) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:499) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:458) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgramIfPossible(CpsThreadGroup.java:445) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:372) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$200(CpsThreadGroup.java:83) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:244) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:232) at
[JIRA] (JENKINS-54289) Create year round GSoC schedule
Title: Message Title Lloyd Chang assigned an issue to Lloyd Chang Jenkins / JENKINS-54289 Create year round GSoC schedule Change By: Lloyd Chang Assignee: Lloyd Chang Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54686) Use trilead-api plugin instead trilead-ssh2 from core
Title: Message Title
John Zila commented on JENKINS-54686
Re: Use trilead-api plugin instead trilead-ssh2 from core
SSHLauncher{host='10.0.0.21', port=22, credentialsId='b6a4fe2c-9ba5-4052-b91c-7a15e913df37', jvmOptions='-Xmx8192m', javaPath='', prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=210, maxNumRetries=10, retryWaitTime=15, sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.ManuallyTrustedKeyVerificationStrategy, tcpNoDelay=true, trackCredentials=false}
[11/20/18 00:29:56] [SSH] Opening SSH connection to 10.0.0.21:22.
[11/20/18 00:29:57] [SSH] SSH host key matches key seen previously for this host. Connection will be allowed.
ERROR: Unexpected error in launching a agent. This is probably a bug in Jenkins.
java.lang.NoClassDefFoundError: com/trilead/ssh2/Connection
at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPasswordAuthenticator$Factory.supports(TrileadSSHPasswordAuthenticator.java:194)
at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPasswordAuthenticator$Factory.newInstance(TrileadSSHPasswordAuthenticator.java:181)
at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.newInstance(SSHAuthenticator.java:216)
at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.newInstance(SSHAuthenticator.java:170)
at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1213)
at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:846)
at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:833)
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)
[11/20/18 00:29:57] Launch failed - cleaning up connection
[11/20/18 00:29:57] [SSH] Connection closed.
Add Comment
[JIRA] (JENKINS-54686) Use trilead-api plugin instead trilead-ssh2 from core
Title: Message Title John Zila commented on JENKINS-54686 Re: Use trilead-api plugin instead trilead-ssh2 from core FYI this breaks the ec2-fleet 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-54707) Allow setting of P4IGNORE to alternate names
Title: Message Title Joel Brown created an issue Jenkins / JENKINS-54707 Allow setting of P4IGNORE to alternate names Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2018-11-20 00:14 Labels: P4_VERIFY Priority: Minor Reporter: Joel Brown Need a way to specify an alternative for P4IGNORE and/or not use it. setIgnoreFileName() is always set in https://swarm.workshop.perforce.com/projects/p4-jenkins/files/main/src/main/java/org/jenkinsci/plugins/p4/client/ConnectionHelper.java Add Comment
[JIRA] (JENKINS-54611) Timestamper does not work properly with Windows style line endings
Title: Message Title Gabriel Loewen resolved as Cannot Reproduce Jenkins / JENKINS-54611 Timestamper does not work properly with Windows style line endings Change By: Gabriel Loewen 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-54611) Timestamper does not work properly with Windows style line endings
Title: Message Title Gabriel Loewen commented on JENKINS-54611 Re: Timestamper does not work properly with Windows style line endings The issue went away after restarting Jenkins... Resolving for now, but confused why this was the resolution. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53022) Cannot disable a job from Blue Ocean UI
Title: Message Title Gavin Mogan assigned an issue to Gavin Mogan Jenkins / JENKINS-53022 Cannot disable a job from Blue Ocean UI Change By: Gavin Mogan Assignee: Gavin Mogan Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44715) Pipeline plugin won't get updated PR github title
Title: Message Title Gordon Shieh commented on JENKINS-44715 Re: Pipeline plugin won't get updated PR github title I can vouch that this is happening with our Cloudbees Enterprise Jenkins too scm-api - 2.3.0 branch-api 2.0.20 github-api 1.92 github-branch-source - 2.4.1 We were trying to rollout some workflow changes to our developers, but this bug is now a blocker for us Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47989) HTML publisher argument reportTitles is marked as optional in PipelineSyntax editor, but it's required
Title: Message Title Stephan Hadamik commented on JENKINS-47989 Re: HTML publisher argument reportTitles is marked as optional in PipelineSyntax editor, but it's required Jenkins ver. 2.129-SNAPSHOT org.jenkins-ci.plugins:htmlpublisher:1.17 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47989) HTML publisher argument reportTitles is marked as optional in PipelineSyntax editor, but it's required
Title: Message Title
Stephan Hadamik commented on JENKINS-47989
Re: HTML publisher argument reportTitles is marked as optional in PipelineSyntax editor, but it's required
A bit more testing: If you use a named parameter like on https://jenkins.io/blog/2017/02/10/declarative-html-publisher/ validation succeeds. However: if you try to roundtrip convert you'll get this issue, too.
pipeline {
agent any
stages {
stage('Publish') {
steps {
publishHTML target: [allowMissing: true, alwaysLinkToLastBuild: false, keepAll: false, reportDir: 'reports', reportFiles: 'index.html', reportName: 'Coverage reports']
}
}
}
}
$ curl -F "jenkinsfile= -X POST http://localhost:8080/pipeline-model-converter/validate
Jenkinsfile successfully validated.
$ curl -F "jenkinsfile= -X POST http://localhost:8080/pipeline-model-converter/toJson | jq ".data.json" | curl -F "json=<-" -X POST http://localhost:8080/pipeline-model-converter/toJenkinsfile
{
"status": "ok",
"data": {
"result": "failure",
"errors": [
{
"jenkinsfileErrors": {
"result": "failure",
"errors": [
{
"error": [
"Missing required parameter: \"reportTitles\" @ line 18, column 9.",
"Missing required parameter: \"reportTitles\" @ line 18, column 9.",
"Missing required parameter: \"reportTitles\" @ line 18, column 9.",
"Missing required parameter: \"reportTitles\" @ line 18, column 9.",
"Missing required parameter: \"reportTitles\" @ line 18, column 9.",
"Missing required parameter: \"reportTitles\" @ line 18, column 9."
]
}
]
}
}
]
}
}
Add Comment
[JIRA] (JENKINS-47989) HTML publisher argument reportTitles is marked as optional in PipelineSyntax editor, but it's required
Title: Message Title
Stephan Hadamik edited a comment on JENKINS-47989
Re: HTML publisher argument reportTitles is marked as optional in PipelineSyntax editor, but it's required
I came across this issue using declarative. Here is how to reproduce:{code:java}pipeline { agent anystages { stage('Publish') {steps { publishHTML([allowMissing: true, alwaysLinkToLastBuild: false, keepAll: false, reportDir: 'reports', reportFiles: 'index.html', reportName: 'Coverage reports'])} } }}{code}Try to convert to json:{code:bash}$ curl - u admin:admin - F "jenkinsfile=Errors encountered validating Jenkinsfile:WorkflowScript: 6: Missing required parameter: "reportTitles" @ line 6, column 15. publishHTML([allowMissing: true, alwaysLinkToLastBuild: false, keepAll: false, reportDir: 'reports', reportFiles: 'index.html', reportName: 'Coverage reports']) ^{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50191) Multibranch Pipeline tends to keep rebuilding same commits
Title: Message Title Andrew Gray updated an issue Jenkins / JENKINS-50191 Multibranch Pipeline tends to keep rebuilding same commits Change By: Andrew Gray Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47989) HTML publisher argument reportTitles is marked as optional in PipelineSyntax editor, but it's required
Title: Message Title
Stephan Hadamik edited a comment on JENKINS-47989
Re: HTML publisher argument reportTitles is marked as optional in PipelineSyntax editor, but it's required
I came across this issue using declarative. Here is how to reproduce:{code:java}pipeline { agent anystages { stage('Publish') {steps { publishHTML([allowMissing: true, alwaysLinkToLastBuild: false, keepAll: false, reportDir: 'reports', reportFiles: 'index.html', reportName: 'Coverage reports'])} } }}{code}Try to convert to json:{code :bash } $ curl -u admin:admin -F "jenkinsfile=Errors encountered validating Jenkinsfile:WorkflowScript: 6: Missing required parameter: "reportTitles" @ line 6, column 15. publishHTML([allowMissing: true, alwaysLinkToLastBuild: false, keepAll: false, reportDir: 'reports', reportFiles: 'index.html', reportName: 'Coverage reports']) ^{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47989) HTML publisher argument reportTitles is marked as optional in PipelineSyntax editor, but it's required
Title: Message Title
Stephan Hadamik edited a comment on JENKINS-47989
Re: HTML publisher argument reportTitles is marked as optional in PipelineSyntax editor, but it's required
I came across this issue using declarative. Here is how to reproduce:{code:java}pipeline { agent anystages { stage('Publish') {steps { publishHTML([allowMissing: true, alwaysLinkToLastBuild: false, keepAll: false, reportDir: 'reports', reportFiles: 'index.html', reportName: 'Coverage reports'])} } }}{code}Try to convert to json:{code :bash }$ curl -u admin:admin -F "jenkinsfile=Errors encountered validating Jenkinsfile:WorkflowScript: 6: Missing required parameter: "reportTitles" @ line 6, column 15. publishHTML([allowMissing: true, alwaysLinkToLastBuild: false, keepAll: false, reportDir: 'reports', reportFiles: 'index.html', reportName: 'Coverage reports']) ^{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47989) HTML publisher argument reportTitles is marked as optional in PipelineSyntax editor, but it's required
Title: Message Title
Stephan Hadamik edited a comment on JENKINS-47989
Re: HTML publisher argument reportTitles is marked as optional in PipelineSyntax editor, but it's required
I came across this issue using declarative. Here is how to reproduce:{code :java }pipeline { agent anystages { stage('Publish') {steps { publishHTML([allowMissing: true, alwaysLinkToLastBuild: false, keepAll: false, reportDir: 'reports', reportFiles: 'index.html', reportName: 'Coverage reports'])} } }}{code}Try to convert to json:{code :bash }curl - u admin:admin - F "jenkinsfile= toJson validate {code}{code}{ "status" Errors encountered validating Jenkinsfile : "ok", "data" WorkflowScript : {"result" 6 : "failure","errors": [ {"error": [ " Missing required parameter: \ "reportTitles \ " @ line 6, column 15. ", "Missing required parameter publishHTML([allowMissing : \"reportTitles\" @ line 6 true , column 15.", "Missing required parameter alwaysLinkToLastBuild : \"reportTitles\" @ line 6 false , column 15.", "Missing required parameter keepAll : \"reportTitles\" @ line 6 false , column 15.", "Missing required parameter reportDir : \"reportTitles\" @ line 6 'reports' , column 15 reportFiles: 'index . " html' , "Missing required parameter reportName : \"reportTitles\" @ line 6, column 15." 'Coverage reports' ] ) } ^ ] }} {code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47989) HTML publisher argument reportTitles is marked as optional in PipelineSyntax editor, but it's required
Title: Message Title Stephan Hadamik reopened an issue Jenkins / JENKINS-47989 HTML publisher argument reportTitles is marked as optional in PipelineSyntax editor, but it's required Change By: Stephan Hadamik Resolution: Incomplete Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39467) Project Inheritance Plugin is not compatible with Rebuild Plugin 1.23+
Title: Message Title Mitchell Young edited a comment on JENKINS-39467 Re: Project Inheritance Plugin is not compatible with Rebuild Plugin 1.23+ Apologies; I missed the two `isApplicable()` methods that are defined by the Rebuild plugin . It does appear that the project inheritance plugin is incompatible Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47989) HTML publisher argument reportTitles is marked as optional in PipelineSyntax editor, but it's required
Title: Message Title
Stephan Hadamik commented on JENKINS-47989
Re: HTML publisher argument reportTitles is marked as optional in PipelineSyntax editor, but it's required
I came across this issue using declarative. Here is how to reproduce:
pipeline {
agent any
stages {
stage('Publish') {
steps {
publishHTML([allowMissing: true, alwaysLinkToLastBuild: false, keepAll: false, reportDir: 'reports', reportFiles: 'index.html', reportName: 'Coverage reports'])
}
}
}
}
Try to convert to json:
curl -F "jenkinsfile= -X POST http://localhost:8080/pipeline-model-converter/toJson
{
"status": "ok",
"data": {
"result": "failure",
"errors": [
{
"error": [
"Missing required parameter: \"reportTitles\" @ line 6, column 15.",
"Missing required parameter: \"reportTitles\" @ line 6, column 15.",
"Missing required parameter: \"reportTitles\" @ line 6, column 15.",
"Missing required parameter: \"reportTitles\" @ line 6, column 15.",
"Missing required parameter: \"reportTitles\" @ line 6, column 15.",
"Missing required parameter: \"reportTitles\" @ line 6, column 15."
]
}
]
}
}
Add Comment
This message was sent by
[JIRA] (JENKINS-39467) Project Inheritance Plugin is not compatible with Rebuild Plugin 1.23+
Title: Message Title Mitchell Young commented on JENKINS-39467 Re: Project Inheritance Plugin is not compatible with Rebuild Plugin 1.23+ Apologies; I missed the two `isApplicable()` methods that are defined by the Rebuild 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-39467) Project Inheritance Plugin is not compatible with Rebuild Plugin 1.23+
Title: Message Title Mitchell Young commented on JENKINS-39467 Re: Project Inheritance Plugin is not compatible with Rebuild Plugin 1.23+ Looking at the current state of these two plugins, they appear to be compatible now (disclaimer: I'm not super familiar with Java). They both lack the `abstract` keyword, at least. However, I am still getting a similar exception regarding the `isApplicable()` method. Could this be related to: https://issues.jenkins-ci.org/browse/JENKINS-50244? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53868) Show full date and time when stage triggered
Title: Message Title
Tommy Tynjä commented on JENKINS-53868
Re: Show full date and time when stage triggered
The screenshot above is essentially just a one-line modification: https://github.com/Diabol/delivery-pipeline-plugin/blob/ec00b37ab512b647c008bd930158e55d3e8e3d58/src/main/webapp/pipe.js#L558 ... as: return date !== null ? moment(date, '-MM-DDTHH:mm:ss').format('-MM-DD HH:mm:ss') : '';
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53868) Show full date and time when stage triggered
Title: Message Title Tommy Tynjä commented on JENKINS-53868 Re: Show full date and time when stage triggered Craig Webb it would be quite trivial to support this. However, the preferred way would probably be to support this as a configuration option on the view so those users who wants this behavior could override the default (which shows relative times). Would something like this be sufficient (see attachment)? An open question is whether to account for time zone offsets. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53868) Show full date and time when stage triggered
Title: Message Title Tommy Tynjä updated an issue Jenkins / JENKINS-53868 Show full date and time when stage triggered Change By: Tommy Tynjä Attachment: image-2018-11-19-22-36-01-993.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-26257) java.lang.ClassCastException/NPE in Remoting while executing Maven Builder
Title: Message Title Moshe Zvi commented on JENKINS-26257 Re: java.lang.ClassCastException/NPE in Remoting while executing Maven Builder Warren Morgan: Thanks for the tip. In my case the Disable automatic artifact archiving was not set, and I still got the error. However, selecting Disable automatic fingerprinting ... seems to have done the trick. So it's definitely a fingerprint issue, and I agree that it's unrelated to remote execution. For anyone looking this up: In the maven section (Build), expand the Advanced section, and look for these properties. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26257) java.lang.ClassCastException/NPE in Remoting while executing Maven Builder
Title: Message Title Moshe Zvi updated an issue Jenkins / JENKINS-26257 java.lang.ClassCastException/NPE in Remoting while executing Maven Builder Change By: Moshe Zvi Attachment: fingerprints_1.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26257) java.lang.ClassCastException/NPE in Remoting while executing Maven Builder
Title: Message Title Moshe Zvi updated an issue Jenkins / JENKINS-26257 java.lang.ClassCastException/NPE in Remoting while executing Maven Builder Change By: Moshe Zvi Attachment: fingerprints_1.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54401) NPE when parsing scm git revision date on PR branches
Title: Message Title Joseph Petersen commented on JENKINS-54401 Re: NPE when parsing scm git revision date on PR branches Create a ticket for Jenkins infra, it is uploaded to artifactory as posted on GitHub Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47442) Parameterized Trigger hangs waiting for downstream job
Title: Message Title Mark Hermon commented on JENKINS-47442 Re: Parameterized Trigger hangs waiting for downstream job We were never able to get it working, we've since switched to kicking off the build from our normal jobs instead of from the Promoted Builds 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-54566) Failed to execute command Pipe.Flush
Title: Message Title Devin Nusbaum updated JENKINS-54566 This error was fixed in version 2.33 of the Pipeline API plugin. Jenkins / JENKINS-54566 Failed to execute command Pipe.Flush Change By: Devin Nusbaum Status: Fixed but Unreleased Resolved Released As: toward workflow-api 2.33 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49555) Split most of Spring Framework out of core
Title: Message Title Matt Sicker commented on JENKINS-49555 Re: Split most of Spring Framework out of core What if we upgraded Spring and actually used it in core instead of Stapler? We could use various Spring functionality to support current Stapler annotations, data types, etc. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54706) Drop support for themes
Title: Message Title Tommy Tynjä created an issue Jenkins / JENKINS-54706 Drop support for themes Issue Type: Improvement Assignee: Tommy Tynjä Components: delivery-pipeline-plugin Created: 2018-11-19 20:52 Environment: Jenkins 2.73.3 Delivery Pipeline plugin 1.3.0 Priority: Minor Reporter: Tommy Tynjä Currently, the delivery pipeline plugin supports three different themes which visualizes the delivery pipeline views in different views. The default and the contrast themes are similar apart from minor css configuration. The current implementation requires multiple versions of css and _javascript_ files to account for the various themes which adds extra complexity and burden on maintaining these themes. It is not obvious for instance new contributors that one particular css change needs to be taken into account several times. Same goes for the _javascript_ files that renders the different views. In order to allow this plugin to be maintained in a sustainable way in the future, it is therefore suggested that the current contrast and overview themes are dropped in favor of one provided default theme. It will still be possible to override the default css and the full screen css using the already existing custom css configuration options.
[JIRA] (JENKINS-54566) Failed to execute command Pipe.Flush
Title: Message Title Jesse Glick stopped work on JENKINS-54566 Change By: Jesse Glick Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54566) Failed to execute command Pipe.Flush
Title: Message Title Jesse Glick updated JENKINS-54566 Jenkins / JENKINS-54566 Failed to execute command Pipe.Flush Change By: Jesse Glick Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54566) Failed to execute command Pipe.Flush
Title: Message Title Jesse Glick updated JENKINS-54566 Jenkins / JENKINS-54566 Failed to execute command Pipe.Flush Change By: Jesse Glick Status: Open Fixed but Unreleased Resolution: Fixed Released As: toward 2.33 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50244) java.lang.AbstractMethodError: you must override the new overload of isApplicable in hudson.plugins.project_inheritance.projects.rebuild.RebuildValidatorSuppressor
Title: Message Title
Mitchell Young edited a comment on JENKINS-50244
Re: java.lang.AbstractMethodError: you must override the new overload of isApplicable in hudson.plugins.project_inheritance.projects.rebuild.RebuildValidatorSuppressor
Also experiencing this:{noformat}Nov 19, 2018 9:20:47 AM WARNING hudson.ExpressionFactory2$JexlExpression evaluateCaught exception evaluating: it.transientActions in /job/New%20Pipelines/job/EXAMPLEJOB/42/console. Reason: java.lang.reflect.InvocationTargetExceptionjava.lang.AbstractMethodError: you must override the new overload of isApplicable in hudson.plugins.project_inheritance.projects.rebuild.RebuildValidatorSuppressor at com.sonyericsson.rebuild.RebuildValidator.isApplicable(RebuildValidator.java:50) at com.sonyericsson.rebuild.RebuildActionFactory.createFor(RebuildActionFactory.java:61) at hudson.model.Run.getTransientActions(Run.java:388)Caused: java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor567.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125){noformat} Not using declarative pipelines, so no extra "agent any"s
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50244) java.lang.AbstractMethodError: you must override the new overload of isApplicable in hudson.plugins.project_inheritance.projects.rebuild.RebuildValidatorSuppressor
Title: Message Title Mitchell Young commented on JENKINS-50244 Re: java.lang.AbstractMethodError: you must override the new overload of isApplicable in hudson.plugins.project_inheritance.projects.rebuild.RebuildValidatorSuppressor Also experiencing this: Nov 19, 2018 9:20:47 AM WARNING hudson.ExpressionFactory2$JexlExpression evaluateCaught exception evaluating: it.transientActions in /job/New%20Pipelines/job/EXAMPLEJOB/42/console. Reason: java.lang.reflect.InvocationTargetException java.lang.AbstractMethodError: you must override the new overload of isApplicable in hudson.plugins.project_inheritance.projects.rebuild.RebuildValidatorSuppressor at com.sonyericsson.rebuild.RebuildValidator.isApplicable(RebuildValidator.java:50) at com.sonyericsson.rebuild.RebuildActionFactory.createFor(RebuildActionFactory.java:61) at hudson.model.Run.getTransientActions(Run.java:388) Caused: java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor567.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54209) Can't read file: Can't access the file
Title: Message Title Amo Mamo commented on JENKINS-54209 Re: Can't read file: Can't access the file Something tells me that it's time to fork the 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-35708) EC2 Plugin: Ability to round robin EC2 availability zones
Title: Message Title Edward Quick commented on JENKINS-35708 Re: EC2 Plugin: Ability to round robin EC2 availability zones Hi Nicola, I could be wrong but a colleague of mine mentioned that you need to provide the AZ list as space delimited (not comma delimited). Ed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45466) Adjuncts and lazy loading failures in global configuration
Title: Message Title Jesse Glick stopped work on JENKINS-45466 Change By: Jesse Glick Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45466) Adjuncts and lazy loading failures in global configuration
Title: Message Title Jesse Glick updated JENKINS-45466 Jenkins / JENKINS-45466 Adjuncts and lazy loading failures in global configuration Change By: Jesse Glick Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54645) Send queue data in JSON Payload
Title: Message Title Markus Winter commented on JENKINS-54645 Re: Send queue data in JSON Payload I think there are more and more requests for custom data. That would justify that we introduce something like a data provider as an extension point. This way others can easily extend by implementing the extension point in an own plugin. Precondition would be JENKINS-54685 I think. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54690) System configuration page error
Title: Message Title Oleg Nenashev resolved as Duplicate Duplicate of JENKINS-54596 Jenkins / JENKINS-54690 System configuration page error Change By: Oleg Nenashev Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54690) System configuration page error
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54690 System configuration page error Change By: Oleg Nenashev Summary: 系统配置页面报错 System configuration page error Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54690) System configuration page error
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-54690 System configuration page error Change By: Oleg Nenashev Assignee: Praqma Support Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54690) System configuration page error
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54690 System configuration page error Change By: Oleg Nenashev Component/s: _unsorted Component/s: component Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54705) Jenkins slave agent does not start
Title: Message Title Oleg Nenashev assigned an issue to Emilio Escobar Jenkins / JENKINS-54705 Jenkins slave agent does not start Change By: Oleg Nenashev Assignee: Emilio Escobar Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54705) Jenkins slave agent does not start
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54705 Jenkins slave agent does not start Change By: Oleg Nenashev Component/s: windows-slaves-plugin Component/s: core Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54705) Jenkins slave agent does not start
Title: Message Title d t created an issue Jenkins / JENKINS-54705 Jenkins slave agent does not start Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-11-19 18:30 Environment: UAT Priority: Minor Reporter: d t Hi, I am running jenkins 2.89.4 (windows based )and jenkins slave on another windows based server. i am not able to bring jenkins window slave online and when i click on launch agent i do see Access is denied.. ERROR: [2018-11-19 13:27:45] [windows-slaves] Access is denied. See http://wiki.jenkins-ci.org/display/JENKINS/Windows+slaves+fail+to+start+via+DCOM for more information about how to resolve this. org.jinterop.dcom.common.JIException: Message not found for errorCode: 0x0005 at org.jinterop.winreg.smb.JIWinRegStub.winreg_CreateKey(JIWinRegStub.java:297) at org.jinterop.dcom.core.JIComServer.initialise(JIComServer.java:480) at org.jinterop.dcom.core.JIComServer.(JIComServer.java:427) at org.jvnet.hudson.wmi.WMI.connect(WMI.java:59) at hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:208) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:285) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: org.jinterop.dcom.common.JIRuntimeException: Message not found for errorCode: 0x0005 at org.jinterop.winreg.IJIWinReg$createKey.read(IJIWinReg.java:459) at ndr.NdrObject.decode(NdrObject.java:19) at rpc.ConnectionOrientedEndpoint.call(ConnectionOrientedEndpoint.java:138) at rpc.Stub.call(Stub.java:112) at
[JIRA] (JENKINS-54704) Problem with some paths (folder) blue ocean jenkins Nginx reverse proxy
Title: Message Title
Gopal Rathi updated an issue
Jenkins / JENKINS-54704
Problem with some paths (folder) blue ocean jenkins Nginx reverse proxy
Change By:
Gopal Rathi
Greetings ,We are facing issues with some paths (eg folders) with Blue Ocean , running Jenkins behind Nginx.Please find below the Nginx configurations:*Can you please confirm where how the suggested solution snippet from ([https://wiki.jenkins.io/display/JENKINS/Running+Jenkins+behind+Nginx)] should be defined used in the below proxy configurations :**or if some other suggestions to fix the problem.* {{if}} {{($request_uri ~ * * }} * {{"/blue(/. }} * {{ )"}}{{) {}}{{}}{{proxy_pass http:}}{{//YOUR_SERVER_IP:YOUR_JENKINS_PORT/blue$1;}}{{}}{{break}}{{;}}{{}}}**server { listen 8999; ssl on; ssl_certificate /swa/certs/project.tool.crt; ssl_certificate_key /swa/certs/project.tool.key; ssl_protocols TLSv1.2; ssl_ciphers HIGH:!aNULL:!MD5; ssl_session_cache shared:SSL:10m; ssl_session_timeout 10m; keepalive_timeout 60; sendfile on; tcp_nopush on; tcp_nodelay on; proxy_buffering off; access_log /var/log/nginx/jenkins_access.log; port_in_redirect off; client_max_body_size 0; client_body_buffer_size 128k; client_header_timeout 3m; client_body_timeout 3m; send_timeout 3m; location / { { proxy_pass [http://jenkins:8080/]; proxy_read_timeout 900; proxy_max_temp_file_size 0; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Real-IP $remote_addr; proxy_redirect off; }} *The error while accessing the job inside folder through blue ocean :*The requested URL /LPFG/blue/organizations/jenkins/product-desktop-air-operations/spa-air-flight-status was not found on this server.Apache/2.4.25 (Debian) Server at [jenkins-tools.swacorp.com|http://jenkins-tools.swacorp.com/] Port 443
Add Comment
[JIRA] (JENKINS-54704) Problem with some paths (folder) blue ocean jenkins Nginx reverse proxy
Title: Message Title
Gopal Rathi created an issue
Jenkins / JENKINS-54704
Problem with some paths (folder) blue ocean jenkins Nginx reverse proxy
Issue Type:
Bug
Assignee:
Unassigned
Components:
blueocean-plugin
Created:
2018-11-19 18:17
Priority:
Major
Reporter:
Gopal Rathi
Greetings , We are facing issues with some paths (eg folders) with Blue Ocean , running Jenkins behind Nginx. Please find below the Nginx configurations: Can you please confirm where the suggested solution should be defined in the below configurations : or if some other suggestions to fix the problem. if ($request_uri ~ "/blue(/.)") { proxy_pass http://YOUR_SERVER_IP:YOUR_JENKINS_PORT/blue$1; break; } server { listen 8999; ssl on; ssl_certificate /swa/certs/project.tool.crt; ssl_certificate_key /swa/certs/project.tool.key; ssl_protocols TLSv1.2; ssl_ciphers HIGH:!aNULL:!MD5; ssl_session_cache shared:SSL:10m; ssl_session_timeout 10m; keepalive_timeout 60; sendfile on; tcp_nopush on; tcp_nodelay on; proxy_buffering off; access_log /var/log/nginx/jenkins_access.log; port_in_redirect off; client_max_body_size 0; client_body_buffer_size 128k; client_header_timeout 3m; client_body_timeout 3m; send_timeout 3m; location / { proxy_pass [http://jenkins:8080/]; proxy_read_timeout 900; proxy_max_temp_file_size 0; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Real-IP $remote_addr; proxy_redirect off; } } The error while accessing the job inside folder through blue ocean : The requested URL /LPFG/blue/organizations/jenkins/product-desktop-air-operations/spa-air-flight-status was
[JIRA] (JENKINS-47442) Parameterized Trigger hangs waiting for downstream job
Title: Message Title Travis Neal commented on JENKINS-47442 Re: Parameterized Trigger hangs waiting for downstream job Was this ever fixed for you guys? we're running into the same issues. We tried downgrading to 2.32 but this is lower than required for the Git plugin (which requires 2.33, which is the breaking version) downgrading the Git plugin to allow the parameterized trigger plugin to work correctly would mean removing core functionality from our Jenkins implementation. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54701) Support branch indexing and branch event trigger causes
Title: Message Title Tommy Tynjä started work on JENKINS-54701 Change By: Tommy Tynjä 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-54701) Support branch indexing and branch event trigger causes
Title: Message Title Tommy Tynjä commented on JENKINS-54701 Re: Support branch indexing and branch event trigger causes Proposed solution: https://github.com/Diabol/delivery-pipeline-plugin/pull/293 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54603) Memory leak in remoting causes Jenkins to crash
Title: Message Title Jesse Glick commented on JENKINS-54603 Re: Memory leak in remoting causes Jenkins to crash I cannot speculate about any relationship to a memory leak, since we have no diagnostics for that. The workflow-api plugin patch fixes (or purports to fix) the Failed to execute command Pipe.Flush error. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53572) Can't Update Build Status With Bitbucket PR Builder Plugin On Latest Jenkins
Title: Message Title Mochal Sochon edited a comment on JENKINS-53572 Re: Can't Update Build Status With Bitbucket PR Builder Plugin On Latest Jenkins try You can even see the warning message on the screen you provided.Try changing `localhost` to `localhost.localdomain`, but for proper setup it should be FQDN. So this is not a plugin issue per se but jenkins misconfiguration. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
