[JIRA] (JENKINS-50888) NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information
Title: Message Title Reinhold Füreder commented on JENKINS-50888 Re: NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information I just experienced the same problem when setting a description for a ~5 days old build: interestingly the description was actually updated nonetheless! please note, that it was a Replayed build! BUT when clicking on the "diff" Link from the builds "Status" page's "Replayed #2443 (diff)" it just re-renders the build "Status" page => Could it be somehow linked with JENKINS-50784? Well, the same problem happens also for a NOT-"Replayed" build Here is the stacktrace from jenkins log file: 2018-04-25 07:40:47 WARNING [org.eclipse.jetty.server.handler.ContextHandler$Context log] Error while serving https://jenkins2.acme.com/job/ACME-Pipeline/2444/submitDescription java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:347) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:860) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:225) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at
[JIRA] (JENKINS-50984) SSHLauncher/Fingerprint Thread Locking Stopping Dynamic Slave Launch
Title: Message Title Maxfield Stewart commented on JENKINS-50984 Re: SSHLauncher/Fingerprint Thread Locking Stopping Dynamic Slave Launch I believe this is related to this issue: https://issues.jenkins-ci.org/browse/JENKINS-49235 The SSH Slaves plugin started to store fingerprints and that's causing a bit of a race condition I think when the containers shutdown/startup, not entirely sure. It might just be that the Docker Plugin I'm using (0.15) doesn't handle this shutdown/spin up well and the newer ones do. (The newer ones have very different expectations of SSH slaves which require us to completely refactor our container environments, so we'd actually move off SSH connectors). I'm curious if I just revert the SSH Slaves plugin if this problem goes away. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50984) SSHLauncher/Fingerprint Thread Locking Stopping Dynamic Slave Launch
Title: Message Title Maxfield Stewart updated an issue Jenkins / JENKINS-50984 SSHLauncher/Fingerprint Thread Locking Stopping Dynamic Slave Launch Change By: Maxfield Stewart Component/s: credentials-plugin Environment: Jenkins v2.1112Docker Plugin 0.15 Latest SSH Slaves Plugin 1.26 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44285) Kubernetes Plugin , Tool Location overwrites not preserved
Title: Message Title Aytunc BEKEN commented on JENKINS-44285 Re: Kubernetes Plugin , Tool Location overwrites not preserved Hi, I did manage to find bug and fix it. I will open a pull request for this. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44285) Kubernetes Plugin , Tool Location overwrites not preserved
Title: Message Title Aytunc BEKEN assigned an issue to Aytunc BEKEN Jenkins / JENKINS-44285 Kubernetes Plugin , Tool Location overwrites not preserved Change By: Aytunc BEKEN Assignee: Carlos Sanchez Aytunc BEKEN Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27457) deploy is completed however deployed ear(war) doesn't start with a error (SRVE0303E)
Title: Message Title Greg Peters resolved as Won't Fix This technically isn't a bug in the WDP. It's a project setup issue by using the aforementioned ibm-.xml files in the WAR file. If there are other features needed instead of using the ibm-.xml settings, please create an improvement request. Jenkins / JENKINS-27457 deploy is completed however deployed ear(war) doesn't start with a error (SRVE0303E) Change By: Greg Peters Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to
[JIRA] (JENKINS-50769) Deploying EAR to WAS 7 Issue with JDK
Title: Message Title Greg Peters resolved as Duplicate StackOverflow is duplicate and is related to using IBM JRE. The other issues are related to deploying to WebSphere with a mismatched version of Oracle JRE. If this server if WAS v7, sometimes WebSphere uses Java 1.5. Incompatible class errors are caused by the aforementioned issue Jenkins / JENKINS-50769 Deploying EAR to WAS 7 Issue with JDK Change By: Greg Peters Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the
[JIRA] (JENKINS-42297) Websphere Deployer Plugin can't connect to WAS server more than 1 environment at once
Title: Message Title Greg Peters resolved as Fixed Should be fixed in v1.4.8 (beta). Please download it from the plugin site and test it out! Jenkins / JENKINS-42297 Websphere Deployer Plugin can't connect to WAS server more than 1 environment at once Change By: Greg Peters Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-23520) SOAP Connection Exception at 8879
Title: Message Title Greg Peters resolved as Fixed This issue is now ready for testing. v1.4.8 (beta) can be manually installed to address this limitation. You must check the new "Trust All SSL Certificates" setting in the job configuration. No more TrustStore & KeyStore configurations, Hooray!!! Jenkins / JENKINS-23520 SOAP Connection Exception at 8879 Change By: Greg Peters Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To
[JIRA] (JENKINS-50986) Change JENKINS_USER, and then Update Permissions of /var/cache/jenkins
Title: Message Title Morris Yang created an issue Jenkins / JENKINS-50986 Change JENKINS_USER, and then Update Permissions of /var/cache/jenkins Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: packaging Created: 2018-04-25 02:33 Environment: CentOS 7 Jenkins ver. 2.107.2 Priority: Minor Reporter: Morris Yang In the /ect/sysconif/jenkins, ## Type: string ## Default: "jenkins" ## ServiceRestart: jenkins # # Unix user account that runs the Jenkins daemon # Be careful when you change this, as you need to update # permissions of $JENKINS_HOME and /var/log/jenkins. # JENKINS_USER="jenkins" I think we should add /var/cache/jenkins, if ever run the applications. Add Comment
[JIRA] (JENKINS-50985) Deploy backend services to evergreen.jenkins.io
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-50985 Deploy backend services to evergreen.jenkins.io Issue Type: Task Assignee: R. Tyler Croy Components: essentials Created: 2018-04-25 02:18 Priority: Minor Reporter: R. Tyler Croy Need to write a quick JEP and then the kubernetes resources for pushing this container up Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49815) Bump up plugin versions
Title: Message Title Vivek Pandey updated JENKINS-49815 Jenkins / JENKINS-49815 Bump up plugin versions Change By: Vivek Pandey Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50984) SSHLauncher/Fingerprint Thread Locking Stopping Dynamic Slave Launch
Title: Message Title Maxfield Stewart created an issue Jenkins / JENKINS-50984 SSHLauncher/Fingerprint Thread Locking Stopping Dynamic Slave Launch Issue Type: Bug Assignee: Nicolas De Loof Components: docker-plugin, ssh-slaves-plugin Created: 2018-04-25 01:10 Environment: Jenkins v2.1112 Docker Plugin 0.15 Latest SSH Slaves Plugin Priority: Major Reporter: Maxfield Stewart Curious if someone can help me unpack this. We recently upgraded Jenkins. We use the Docker-plugin to dynamically provision slaves and we're now running into a situation where the slaves do not properly finish provisioning (The SSH connection is never established). When taking a thread dump there is a very large number of Blocked threads on the SSHLauncher teardown and Fingerprinting for some reason, here's the dumps: "Computer.threadPoolForRemoting [#1020]" daemon prio=5 BLOCKED hudson.plugins.sshslaves.SSHLauncher.tearDownConnection(SSHLauncher.java:1407) hudson.plugins.sshslaves.SSHLauncher.afterDisconnect(SSHLauncher.java:1403) com.nirima.jenkins.plugins.docker.launcher.DockerComputerLauncher.afterDisconnect(DockerComputerLauncher.java:71) hudson.slaves.SlaveComputer$3.run(SlaveComputer.java:665) jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) java.util.concurrent.FutureTask.run(FutureTask.java:266) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[JIRA] (JENKINS-49183) Retry in Declarative options passes stage but causes false fail in pipeline
Title: Message Title Sam Van Oort commented on JENKINS-49183 Re: Retry in Declarative options passes stage but causes false fail in pipeline Oleg Nenashev I'm unclear why you reassigned this, given that Andrew had already self-assigned this to himself and marked it as a Declarative issue, suggesting he thinks it's an issue with Declarative. That's what my gut says too – likely Declarative is doing something that creates odd status codings here, probably some small bug is resulting in the retry marking the build a failure. Stage View is only providing a visualization of that data, they just provided a screenshot that shows this, and Blue Ocean matches that. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43235) Total container cap of 10 reached when NO slaves are running?
Title: Message Title
Michael FIG edited a comment on JENKINS-43235
Re: Total container cap of 10 reached when NO slaves are running?
I'm getting (in Kubernetes Plugin v1.5.2):{{Total container cap of 10 reached, not provisioning: 10 running or errored in namespace default with Kubernetes labels \{}}} {{}} even though I have labels set in the pod template as:{{Labels: good-pika-jenkins-slave}}This is an installation that was performed by the stable/jenkins helm chart, then I upgraded the plugins within it.Are there any tricks to setting the labels?Thanks,Michael.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43235) Total container cap of 10 reached when NO slaves are running?
Title: Message Title
Michael FIG reopened an issue
I'm getting (in Kubernetes Plugin v1.5.2): Total container cap of 10 reached, not provisioning: 10 running or errored in namespace default with Kubernetes labels {}{{}} even though I have labels set in the pod template as: Labels: good-pika-jenkins-slave This is an installation that was performed by the stable/jenkins helm chart, then I upgraded the plugins within it. Are there any tricks to setting the labels? Thanks, Michael.
Jenkins / JENKINS-43235
Total container cap of 10 reached when NO slaves are running?
Change By:
Michael FIG
Resolution:
Fixed
Status:
Closed Reopened
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49183) Retry in Declarative options passes stage but causes false fail in pipeline
Title: Message Title Sam Van Oort assigned an issue to Andrew Bayer Jenkins / JENKINS-49183 Retry in Declarative options passes stage but causes false fail in pipeline Change By: Sam Van Oort Assignee: Sam Van Oort Andrew Bayer Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49183) Retry in Declarative options passes stage but causes false fail in pipeline
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-49183 Retry in Declarative options passes stage but causes false fail in pipeline Change By: Sam Van Oort Component/s: pipeline-model-definition-plugin Component/s: pipeline-stage-view-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49183) Retry in Declarative options passes stage but causes false fail in pipeline
Title: Message Title Jonh Wendell commented on JENKINS-49183 Re: Retry in Declarative options passes stage but causes false fail in pipeline I'm also suffering from this issue as you can see in the screenshot above. Even open ocean recognizes the job failed when in fact only 1 step within the retry clause failed, at the first time. Second time it worked fine. The state of the build is failed - in all jenkins views - when in fact it succeeded. I'm using Jenkins 2.89.4 + Pipeline declarative 1.2.7 + Build Pipeline plugin 1.5.8. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49183) Retry in Declarative options passes stage but causes false fail in pipeline
Title: Message Title Jonh Wendell updated an issue Jenkins / JENKINS-49183 Retry in Declarative options passes stage but causes false fail in pipeline Change By: Jonh Wendell Attachment: Screenshot from 2018-04-24 21-32-39.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47247) Allow roundtrip editing for http/https repositories
Title: Message Title Josh McDonald updated JENKINS-47247 Jenkins / JENKINS-47247 Allow roundtrip editing for http/https repositories Change By: Josh McDonald Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47247) Allow roundtrip editing for http/https repositories
Title: Message Title Josh McDonald commented on JENKINS-47247 Re: Allow roundtrip editing for http/https repositories https://github.com/jenkinsci/blueocean-plugin/pull/1720 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50983) LoadFocus LoadTest publisher persists PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-50983 LoadFocus LoadTest publisher persists PrintStream to the disk (JEP-200) Issue Type: Bug Assignee: Unassigned Components: loaderio-jenkins Created: 2018-04-24 23:46 Labels: JEP-200 Priority: Minor Reporter: Oleg Nenashev According to the code inspection, there is a JEP-200 issue in the plugin: https://github.com/jenkinsci/loaderio-plugin/blob/987a638da8cfeda2f7cbe7bfab0d71ca920289bc/src/main/java/io/loader/jenkins/LoaderPublisher.java#L73 This code likely causes a JEP-200 security exception when the object gets persisted to the disk. "java.io.PrintStream" is not whitelisted in Jenkins for a reason, because loggers are not expected reliably after being deserialized from the disk. Useful links about JEP-200: Blog post for users: https://jenkins.io/blog/2018/03/15/jep-200-lts/ JEP-200 guidelines for plugin developers: https://jenkins.io/blog/2018/01/13/jep-200/#for-plugin-developers
[JIRA] (JENKINS-50983) LoadFocus LoadTest publisher persists PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50983 LoadFocus LoadTest publisher persists PrintStream to the disk (JEP-200) Change By: Oleg Nenashev According to the code inspection, there is a JEP-200 issue in the plugin: * https://github.com/jenkinsci/ loaderio loadfocus - loadtest- plugin/blob/ 987a638da8cfeda2f7cbe7bfab0d71ca920289bc 79a5c19e9a84240b093e78a0c4d0e3f3ac4be75e /src/main/java/ io com / loader loadfocus /jenkins/ LoaderPublisher LoadPublisher .java# L73 L46 This code likely causes a JEP-200 security exception when the object gets persisted to the disk. "java.io.PrintStream" is not whitelisted in Jenkins for a reason, because loggers are not expected reliably after being deserialized from the disk. Useful links about JEP-200:* Blog post for users: https://jenkins.io/blog/2018/03/15/jep-200-lts/* JEP-200 guidelines for plugin developers: https://jenkins.io/blog/2018/01/13/jep-200/#for-plugin-developers Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50983) LoadFocus LoadTest publisher persists PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50983 LoadFocus LoadTest publisher persists PrintStream to the disk (JEP-200) Change By: Oleg Nenashev Component/s: loadfocus-loadtest-plugin Component/s: loaderio-jenkins Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50983) LoadFocus LoadTest publisher persists PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev assigned an issue to Load Focus Jenkins / JENKINS-50983 LoadFocus LoadTest publisher persists PrintStream to the disk (JEP-200) Change By: Oleg Nenashev Assignee: Load Focus Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50982) AppScanStandardBuilder persists PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev assigned an issue to Tiago Lopes Jenkins / JENKINS-50982 AppScanStandardBuilder persists PrintStream to the disk (JEP-200) Change By: Oleg Nenashev Assignee: Kevin Fealey Tiago Lopes Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50982) AppScanStandardBuilder persists PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50982 AppScanStandardBuilder persists PrintStream to the disk (JEP-200) Change By: Oleg Nenashev According to the code inspection, there is a JEP-200 issue in the plugin: * https://github.com/jenkinsci/ibm-security- appscansource appscanstandard -scanner-plugin/blob/ 3a925c5b9016a6a5db8c5c68d2764805a4603f94 62c0967a9d2e623d6eb97dd2c2f354f9ff87f5ac /src/main/java/ com appscanstdrdintegration / aspectsecurity appscanstandard / automationservices/plugins/jenkins/appscansource/AppScanSourceBuilder AppScanStandardBuilder .java# L55 L146 This code likely causes a JEP-200 security exception when the object gets persisted to the disk. "java.io.PrintStream" is not whitelisted in Jenkins for a reason, because loggers are not expected reliably after being deserialized from the disk. Useful links about JEP-200:* Blog post for users: https://jenkins.io/blog/2018/03/15/jep-200-lts/* JEP-200 guidelines for plugin developers: https://jenkins.io/blog/2018/01/13/jep-200/#for-plugin-developers Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50982) AppScanStandardBuilder persists PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50982 AppScanStandardBuilder persists PrintStream to the disk (JEP-200) Change By: Oleg Nenashev Component/s: ibm-security-appscanstandard-scanner-plugin Component/s: ibm-security-appscansource-scanner-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50982) AppScanStandardBuilder persists PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-50982 AppScanStandardBuilder persists PrintStream to the disk (JEP-200) Issue Type: Bug Assignee: Kevin Fealey Components: ibm-security-appscansource-scanner-plugin Created: 2018-04-24 23:44 Labels: JEP-200 Priority: Minor Reporter: Oleg Nenashev According to the code inspection, there is a JEP-200 issue in the plugin: https://github.com/jenkinsci/ibm-security-appscansource-scanner-plugin/blob/3a925c5b9016a6a5db8c5c68d2764805a4603f94/src/main/java/com/aspectsecurity/automationservices/plugins/jenkins/appscansource/AppScanSourceBuilder.java#L55 This code likely causes a JEP-200 security exception when the object gets persisted to the disk. "java.io.PrintStream" is not whitelisted in Jenkins for a reason, because loggers are not expected reliably after being deserialized from the disk. Useful links about JEP-200: Blog post for users: https://jenkins.io/blog/2018/03/15/jep-200-lts/ JEP-200 guidelines for plugin developers: https://jenkins.io/blog/2018/01/13/jep-200/#for-plugin-developers
[JIRA] (JENKINS-50981) AppScanSourceBuilder persists PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50981 AppScanSourceBuilder persists PrintStream to the disk (JEP-200) Change By: Oleg Nenashev According to the code inspection, there is a JEP-200 issue in the plugin: * https://github.com/jenkinsci/ loaderio ibm - security-appscansource-scanner- plugin/blob/ 987a638da8cfeda2f7cbe7bfab0d71ca920289bc 3a925c5b9016a6a5db8c5c68d2764805a4603f94 /src/main/java/ io com / loader aspectsecurity / automationservices/plugins/ jenkins/ LoaderPublisher appscansource/AppScanSourceBuilder .java# L73 L55 This code likely causes a JEP-200 security exception when the object gets persisted to the disk. "java.io.PrintStream" is not whitelisted in Jenkins for a reason, because loggers are not expected reliably after being deserialized from the disk. Useful links about JEP-200:* Blog post for users: https://jenkins.io/blog/2018/03/15/jep-200-lts/* JEP-200 guidelines for plugin developers: https://jenkins.io/blog/2018/01/13/jep-200/#for-plugin-developers Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50981) AppScanSourceBuilder persists PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50981 AppScanSourceBuilder persists PrintStream to the disk (JEP-200) Change By: Oleg Nenashev Component/s: ibm-security-appscansource-scanner-plugin Component/s: loaderio-jenkins Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50981) AppScanSourceBuilder persists PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-50981 AppScanSourceBuilder persists PrintStream to the disk (JEP-200) Issue Type: Bug Assignee: Unassigned Components: loaderio-jenkins Created: 2018-04-24 23:43 Labels: JEP-200 Priority: Minor Reporter: Oleg Nenashev According to the code inspection, there is a JEP-200 issue in the plugin: https://github.com/jenkinsci/loaderio-plugin/blob/987a638da8cfeda2f7cbe7bfab0d71ca920289bc/src/main/java/io/loader/jenkins/LoaderPublisher.java#L73 This code likely causes a JEP-200 security exception when the object gets persisted to the disk. "java.io.PrintStream" is not whitelisted in Jenkins for a reason, because loggers are not expected reliably after being deserialized from the disk. Useful links about JEP-200: Blog post for users: https://jenkins.io/blog/2018/03/15/jep-200-lts/ JEP-200 guidelines for plugin developers: https://jenkins.io/blog/2018/01/13/jep-200/#for-plugin-developers
[JIRA] (JENKINS-50981) AppScanSourceBuilder persists PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev assigned an issue to Kevin Fealey Jenkins / JENKINS-50981 AppScanSourceBuilder persists PrintStream to the disk (JEP-200) Change By: Oleg Nenashev Assignee: Kevin Fealey Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50980) MicroFocus DA step persists PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50980 MicroFocus DA step persists PrintStream to the disk (JEP-200) Change By: Oleg Nenashev According to the code inspection, there is a JEP-200 issue in the plugin: * https://github.com/jenkinsci/ loaderio microfocus - da- plugin/blob/ 987a638da8cfeda2f7cbe7bfab0d71ca920289bc d8b4f731e0d46a45f6a8cbacfd43084181f4d028 /src/main/java/ io com / loader microfocus /jenkins/ LoaderPublisher plugins/da/model/DAStep .java# L73 L128 This code likely causes a JEP-200 security exception when the object gets persisted to the disk. "java.io.PrintStream" is not whitelisted in Jenkins for a reason, because loggers are not expected reliably after being deserialized from the disk. Useful links about JEP-200:* Blog post for users: https://jenkins.io/blog/2018/03/15/jep-200-lts/* JEP-200 guidelines for plugin developers: https://jenkins.io/blog/2018/01/13/jep-200/#for-plugin-developers Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50980) MicroFocus DA step persists PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev assigned an issue to Kevin Lee Jenkins / JENKINS-50980 MicroFocus DA step persists PrintStream to the disk (JEP-200) Change By: Oleg Nenashev Assignee: Kevin Lee Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49483) When using Streams, custom view definition seems to be ignored
Title: Message Title Ben L updated an issue Jenkins / JENKINS-49483 When using Streams, custom view definition seems to be ignored Change By: Ben L Comment: I have this same issue. This seems pretty limiting. The problem here is that submit will fail if you don't define the stream due to this issue: [https://stackoverflow.com/questions/12731649/perforce-error-cannot-submit-from-non-stream-client] I'm doing this in a Jenkins pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50980) MicroFocus DA step persists PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50980 MicroFocus DA step persists PrintStream to the disk (JEP-200) Change By: Oleg Nenashev Component/s: microfocus-da-plugin Component/s: loaderio-jenkins Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50980) MicroFocus DA step persists PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-50980 MicroFocus DA step persists PrintStream to the disk (JEP-200) Issue Type: Bug Assignee: Unassigned Components: loaderio-jenkins Created: 2018-04-24 23:41 Labels: JEP-200 Priority: Minor Reporter: Oleg Nenashev According to the code inspection, there is a JEP-200 issue in the plugin: https://github.com/jenkinsci/loaderio-plugin/blob/987a638da8cfeda2f7cbe7bfab0d71ca920289bc/src/main/java/io/loader/jenkins/LoaderPublisher.java#L73 This code likely causes a JEP-200 security exception when the object gets persisted to the disk. "java.io.PrintStream" is not whitelisted in Jenkins for a reason, because loggers are not expected reliably after being deserialized from the disk. Useful links about JEP-200: Blog post for users: https://jenkins.io/blog/2018/03/15/jep-200-lts/ JEP-200 guidelines for plugin developers: https://jenkins.io/blog/2018/01/13/jep-200/#for-plugin-developers
[JIRA] (JENKINS-50979) LoaderIO publisher persists PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50979 LoaderIO publisher persists PrintStream to the disk (JEP-200) Change By: Oleg Nenashev According to the code inspection, there is a JEP-200 issue in the plugin: * https://github.com/jenkinsci/ cloudcoreo loaderio - deploytime- plugin/blob/ 4be75455a056a0fb80ad14cd544e608956775153 987a638da8cfeda2f7cbe7bfab0d71ca920289bc /src/main/java/ com io / cloudcoreo loader / plugins/ jenkins/ CloudCoreoBuildWrapper LoaderPublisher .java# L36 L73 * https://github.com/jenkinsci/cloudcoreo-deploytime-plugin/blob/4be75455a056a0fb80ad14cd544e608956775153/src/main/java/com/cloudcoreo/plugins/jenkins/CloudCoreoPublisher.java#L33 This code likely causes a JEP-200 security exception when the object gets persisted to the disk. "java.io.PrintStream" is not whitelisted in Jenkins for a reason, because loggers are not expected reliably after being deserialized from the disk. Useful links about JEP-200:* Blog post for users: https://jenkins.io/blog/2018/03/15/jep-200-lts/* JEP-200 guidelines for plugin developers: https://jenkins.io/blog/2018/01/13/jep-200/#for-plugin-developers Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50979) LoderIO publisher persists PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50979 LoderIO publisher persists PrintStream to the disk (JEP-200) Change By: Oleg Nenashev Component/s: loaderio-jenkins Component/s: cloudcoreo-deploytime-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50979) LoaderIO publisher persists PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50979 LoaderIO publisher persists PrintStream to the disk (JEP-200) Change By: Oleg Nenashev Summary: LoderIO LoaderIO publisher persists PrintStream to the disk (JEP-200) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50979) LoaderIO publisher persists PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-50979 LoaderIO publisher persists PrintStream to the disk (JEP-200) Change By: Oleg Nenashev Assignee: Andrew Armaneous Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50979) LoderIO publisher persists PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-50979 LoderIO publisher persists PrintStream to the disk (JEP-200) Issue Type: Bug Assignee: Andrew Armaneous Components: cloudcoreo-deploytime-plugin Created: 2018-04-24 23:40 Labels: JEP-200 Priority: Minor Reporter: Oleg Nenashev According to the code inspection, there is a JEP-200 issue in the plugin: https://github.com/jenkinsci/cloudcoreo-deploytime-plugin/blob/4be75455a056a0fb80ad14cd544e608956775153/src/main/java/com/cloudcoreo/plugins/jenkins/CloudCoreoBuildWrapper.java#L36 https://github.com/jenkinsci/cloudcoreo-deploytime-plugin/blob/4be75455a056a0fb80ad14cd544e608956775153/src/main/java/com/cloudcoreo/plugins/jenkins/CloudCoreoPublisher.java#L33 This code likely causes a JEP-200 security exception when the object gets persisted to the disk. "java.io.PrintStream" is not whitelisted in Jenkins for a reason, because loggers are not expected reliably after being deserialized from the disk. Useful links about JEP-200: Blog post for users: https://jenkins.io/blog/2018/03/15/jep-200-lts/ JEP-200 guidelines for plugin developers: https://jenkins.io/blog/2018/01/13/jep-200/#for-plugin-developers
[JIRA] (JENKINS-50978) CloudCoreo Deploy Wrapper and publisher persist PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50978 CloudCoreo Deploy Wrapper and publisher persist PrintStream to the disk (JEP-200) Change By: Oleg Nenashev According to the code inspection, there is a JEP-200 issue in the plugin: * https://github.com/jenkinsci/cloudcoreo-deploytime-plugin/blob/4be75455a056a0fb80ad14cd544e608956775153/src/main/java/com/cloudcoreo/plugins/jenkins/CloudCoreoBuildWrapper.java#L36* https://github.com/jenkinsci/cloudcoreo-deploytime-plugin/blob/4be75455a056a0fb80ad14cd544e608956775153/src/main/java/com/cloudcoreo/plugins/jenkins/CloudCoreoPublisher.java#L33This code likely causes a JEP-200 issue security exception when the object gets persisted to the disk. "java.io.PrintStream" is not whitelisted in Jenkins for a reason, because loggers are not expected reliably after being deserialized from the disk. Useful links about JEP-200:* Blog post for users: https://jenkins.io/blog/2018/03/15/jep-200-lts/* JEP-200 guidelines for plugin developers: https://jenkins.io/blog/2018/01/13/jep-200/#for-plugin-developers Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50978) CloudCoreo Deploy Wrapper and publisher persist PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50978 CloudCoreo Deploy Wrapper and publisher persist PrintStream to the disk (JEP-200) Change By: Oleg Nenashev Summary: CloudCoreo Deploy Wrapper persists and publisher persist PrintStream to the disk (JEP-200) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50978) CloudCoreo Deploy Wrapper persists PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50978 CloudCoreo Deploy Wrapper persists PrintStream to the disk (JEP-200) Change By: Oleg Nenashev According to the code inspection, there is a JEP-200 issue in the plugin: * https://github.com/jenkinsci/cloudcoreo-deploytime-plugin/blob/4be75455a056a0fb80ad14cd544e608956775153/src/main/java/com/cloudcoreo/plugins/jenkins/CloudCoreoBuildWrapper.java#L36 * https://github.com/jenkinsci/cloudcoreo-deploytime-plugin/blob/4be75455a056a0fb80ad14cd544e608956775153/src/main/java/com/cloudcoreo/plugins/jenkins/CloudCoreoPublisher.java#L33 This code likely causes a JEP-200 issue when the object gets persisted to the disk. "java.io.PrintStream" is not whitelisted in Jenkins for a reason, because loggers are not expected reliably after being deserialized from the disk. Useful links about JEP-200:* Blog post for users: https://jenkins.io/blog/2018/03/15/jep-200-lts/* JEP-200 guidelines for plugin developers: https://jenkins.io/blog/2018/01/13/jep-200/#for-plugin-developers Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50978) CloudCoreo Deploy Wrapper persists PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50978 CloudCoreo Deploy Wrapper persists PrintStream to the disk (JEP-200) Change By: Oleg Nenashev According to the code inspection, there is a JEP-200 issue in the plugin: https://github.com/jenkinsci/ gatling cloudcoreo - deploytime- plugin/blob/ 775b494c4ba020018d0aef24316f844e47e0bb32 4be75455a056a0fb80ad14cd544e608956775153 /src/main/java/ io com / gatling cloudcoreo / plugins/ jenkins/ GatlingPublisher CloudCoreoBuildWrapper .java# L44 L36 This code likely causes a JEP-200 issue when the object gets persisted to the disk. "java.io.PrintStream" is not whitelisted in Jenkins for a reason, because loggers are not expected reliably after being deserialized from the disk. Useful links about JEP-200:* Blog post for users: https://jenkins.io/blog/2018/03/15/jep-200-lts/* JEP-200 guidelines for plugin developers: https://jenkins.io/blog/2018/01/13/jep-200/#for-plugin-developers Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50978) CloudCoreo Deploy Wrapper persists PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev assigned an issue to Andrew Armaneous Jenkins / JENKINS-50978 CloudCoreo Deploy Wrapper persists PrintStream to the disk (JEP-200) Change By: Oleg Nenashev Assignee: Andrew Armaneous Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50978) CloudCoreo Deploy Wrapper persists PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-50978 CloudCoreo Deploy Wrapper persists PrintStream to the disk (JEP-200) Issue Type: Bug Assignee: Unassigned Components: gatling-plugin Created: 2018-04-24 23:37 Labels: JEP-200 Priority: Minor Reporter: Oleg Nenashev According to the code inspection, there is a JEP-200 issue in the plugin: https://github.com/jenkinsci/gatling-plugin/blob/775b494c4ba020018d0aef24316f844e47e0bb32/src/main/java/io/gatling/jenkins/GatlingPublisher.java#L44 This code likely causes a JEP-200 issue when the object gets persisted to the disk. "java.io.PrintStream" is not whitelisted in Jenkins for a reason, because loggers are not expected reliably after being deserialized from the disk. Useful links about JEP-200: Blog post for users: https://jenkins.io/blog/2018/03/15/jep-200-lts/ JEP-200 guidelines for plugin developers: https://jenkins.io/blog/2018/01/13/jep-200/#for-plugin-developers
[JIRA] (JENKINS-50978) CloudCoreo Deploy Wrapper persists PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50978 CloudCoreo Deploy Wrapper persists PrintStream to the disk (JEP-200) Change By: Oleg Nenashev Component/s: cloudcoreo-deploytime-plugin Component/s: gatling-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50977) Gatling plugin - publisher persists PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50977 Gatling plugin - publisher persists PrintStream to the disk (JEP-200) Change By: Oleg Nenashev Labels: JEP-200 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50977) Gatling plugin - publisher persists PrintStream to the disk (JEP-200)
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-50977 Gatling plugin - publisher persists PrintStream to the disk (JEP-200) Issue Type: Bug Assignee: Unassigned Components: gatling-plugin Created: 2018-04-24 23:36 Priority: Minor Reporter: Oleg Nenashev According to the code inspection, there is a JEP-200 issue in the plugin: https://github.com/jenkinsci/gatling-plugin/blob/775b494c4ba020018d0aef24316f844e47e0bb32/src/main/java/io/gatling/jenkins/GatlingPublisher.java#L44 This code likely causes a JEP-200 issue when the object gets persisted to the disk. "java.io.PrintStream" is not whitelisted in Jenkins for a reason, because loggers are not expected reliably after being deserialized from the disk. Useful links about JEP-200: Blog post for users: https://jenkins.io/blog/2018/03/15/jep-200-lts/ JEP-200 guidelines for plugin developers: https://jenkins.io/blog/2018/01/13/jep-200/#for-plugin-developers Add Comment
[JIRA] (JENKINS-49483) When using Streams, custom view definition seems to be ignored
Title: Message Title Ben L edited a comment on JENKINS-49483 Re: When using Streams, custom view definition seems to be ignored I have this same issue. This seems pretty limiting. The problem here is that submit will fail if you don't define the stream due to this issue: [ https://stackoverflow.com/questions/12731649/perforce-error-cannot-submit-from-non-stream-client ] I'm doing this in a Jenkins pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49483) When using Streams, custom view definition seems to be ignored
Title: Message Title Ben L commented on JENKINS-49483 Re: When using Streams, custom view definition seems to be ignored I have this same issue. This seems pretty limiting. The problem here is that submit will fail if you don't define the stream due to this issue: https://stackoverflow.com/questions/12731649/perforce-error-cannot-submit-from-non-stream-client Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50976) At end of build plugin is querying BuildMaster for apps deployable info
Title: Message Title Jon Starbird updated an issue Jenkins / JENKINS-50976 At end of build plugin is querying BuildMaster for apps deployable info Change By: Jon Starbird Somehow at the end of a build run the plugin will query BuildMaster. It first queries to get the applications, then it queries the app for it's releases and deployables. It does this over and over and over. For the same app, same deployable. At the point in the Job where this runs the plugin is not being used, it had already been ran earlier in the job. This doesn't happen all the time it seems to only occur if the job's configuration is changed and that change doesn't involve changing anything to do with BuildMaster plugin.Since we have a lot of apps on BuildMaster this causes a build run to take a lot of extra time. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-50976) At end of build plugin is querying BuildMaster for apps deployable info
Title: Message Title Jon Starbird updated an issue Jenkins / JENKINS-50976 At end of build plugin is querying BuildMaster for apps deployable info Change By: Jon Starbird Somehow at the end of a build run the plugin will query BuildMaster. It first queries to get all the applications, then it queries each the app for it's releases and deployables. It does this for Every over and over and over. For the same app on BuildMaster even though this job is configured for only 1 app , same deployable .This doesn't happen all the time it seems to only occur if the job's configuration is changed and that change doesn't involve changing anything to do with BuildMaster plugin.Since we have a lot of apps on BuildMaster this causes a build run to take a lot of extra time. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from
[JIRA] (JENKINS-50976) At end of build plugin is querying BuildMaster for apps deployable info
Title: Message Title Jon Starbird updated an issue Jenkins / JENKINS-50976 At end of build plugin is querying BuildMaster for apps deployable info Change By: Jon Starbird Summary: At end of build plugin is querying BuildMaster for every apps deployable info Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49183) Retry in Declarative options passes stage but causes false fail in pipeline
Title: Message Title Oleg Nenashev commented on JENKINS-49183 Re: Retry in Declarative options passes stage but causes false fail in pipeline According to the screenshot, it is an issue in Pipeline Stage view Plugin. CC Sam Van Oort Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49183) Retry in Declarative options passes stage but causes false fail in pipeline
Title: Message Title Oleg Nenashev assigned an issue to Sam Van Oort Jenkins / JENKINS-49183 Retry in Declarative options passes stage but causes false fail in pipeline Change By: Oleg Nenashev Assignee: Sam Van Oort Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49183) Retry in Declarative options passes stage but causes false fail in pipeline
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49183 Retry in Declarative options passes stage but causes false fail in pipeline Change By: Oleg Nenashev Component/s: pipeline-stage-view-plugin Component/s: pipeline-model-definition-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50976) At end of build plugin is querying BuildMaster for every apps deployable info
Title: Message Title Jon Starbird created an issue Jenkins / JENKINS-50976 At end of build plugin is querying BuildMaster for every apps deployable info Issue Type: Bug Assignee: Andrew Sumner Components: inedo-buildmaster-plugin Created: 2018-04-24 23:13 Environment: Jenkins 2.89.4 BuildMaster 5.8.3 Jenkins BuildMaster plugin - 1.6 Priority: Major Reporter: Jon Starbird Somehow at the end of a build run the plugin will query BuildMaster. It first queries to get all the applications, then it queries each app for it's releases and deployables. It does this for Every app on BuildMaster even though this job is configured for only 1 app. This doesn't happen all the time it seems to only occur if the job's configuration is changed and that change doesn't involve changing anything to do with BuildMaster plugin. Since we have a lot of apps on BuildMaster this causes a build run to take a lot of extra time. Add Comment
[JIRA] (JENKINS-50974) AWS CodeDeploy plug-in fails with new JEP-200 whitelist
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50974 AWS CodeDeploy plug-in fails with new JEP-200 whitelist Change By: Oleg Nenashev Labels: JEP-200 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50974) AWS CodeDeploy plug-in fails with new JEP-200 whitelist
Title: Message Title Oleg Nenashev commented on JENKINS-50974 Re: AWS CodeDeploy plug-in fails with new JEP-200 whitelist https://github.com/jenkinsci/aws-codedeploy-plugin , 1500 installations, active maintenance, recent Plugin POM. The fix should be pretty trivial: PrintStream in https://github.com/jenkinsci/aws-codedeploy-plugin/blob/master/src/main/java/com/amazonaws/codedeploy/AWSCodeDeployPublisher.java#L109 should be removed and passed to private methods as arguments Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50974) AWS CodeDeploy plug-in fails with new JEP-200 whitelist
Title: Message Title Oleg Nenashev commented on JENKINS-50974 Re: AWS CodeDeploy plug-in fails with new JEP-200 whitelist In JENKINS-50264 we fixed CodeBuild, but not CodeDeploy. I am not sure how the suggested whitelist solves the issue, "Caused by: java.lang.UnsupportedOperationException: Refusing to marshal java.io.PrintStream for security reasons; " explicitly points to PrintStream class (hich should not be persisted) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50975) Concurrent Groovy Shared Library syncs on different jobs use same workspace root
Title: Message Title Kurt Routley commented on JENKINS-50975 Re: Concurrent Groovy Shared Library syncs on different jobs use same workspace root Stuart Rowe mentioned it could be due to https://github.com/jenkinsci/workflow-cps-global-lib-plugin/blob/e080b501af942c15325fd17f974bec9cc04142c2/src/main/java/org/jenkinsci/plugins/workflow/libs/SCMSourceRetriever.java , specifically the doRetrive method. It could also be a knock-on from https://issues.jenkins-ci.org/browse/JENKINS-40408 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50975) Concurrent Groovy Shared Library syncs on different jobs use same workspace root
Title: Message Title Kurt Routley created an issue Jenkins / JENKINS-50975 Concurrent Groovy Shared Library syncs on different jobs use same workspace root Issue Type: Bug Assignee: Unassigned Attachments: job1.txt, job2.txt Components: p4-plugin, workflow-cps-global-lib-plugin Created: 2018-04-24 22:00 Environment: CloudBees Jenkins Enterprise 2.89.4.2-rolling Pipeline: Groovy (workflow-cps): 2.47 Pipeline: Shared Groovy Libraries (workflow-cps-global-lib): 2.9 P4 Plugin (p4): 1.7.3-DRE1.25 Operating System: CentOS release 6.7 (Final) Java version: java version "1.8.0_131" , Java(TM) SE Runtime Environment (build 1.8.0_131-b11) Labels: shared-groovy-libraries sync root Priority: Major Reporter: Kurt Routley We're encountering an issue where multiple jobs syncing a groovy shared library concurrently results in the wrong sync root being used for some of the jobs. For example, job1 and job2 are triggered at the same time and use the p4 plugin for syncing the groovy shared library. job1 will have the correct workspace root (e.g. /var/lib/jenkins/jobs/job1/workspace%40libs/LIBRARYNAME) for the groovy shared library sync, but job2 will sync the groovy shared library to the same workspace root as job1 (e.g. /var/lib/jenkins/jobs/job1/workspace%40libs/LIBRARYNAME). When job2 loads the groovy shared library, it references what the workspace root should be for
[JIRA] (JENKINS-39615) Global Pipeline Libraries triggers the 'poll SCM' of jobs
Title: Message Title SK commented on JENKINS-39615 Re: Global Pipeline Libraries triggers the 'poll SCM' of jobs Can someone finally fix this please? It is really annoying, especially because the "Include @Library changes in job recent changes" option has no effect. Everytime I work on my shared library all multibranch pipeline jobs are going to run. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32767) GitSCMSource can hang in branch indexing, blocking builds
Title: Message Title David Taylor commented on JENKINS-32767 Re: GitSCMSource can hang in branch indexing, blocking builds Similar errors are still popping up in 2018, no resolution yet: https://issues.jenkins-ci.org/browse/JENKINS-48933?attachmentViewMode=list Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50815) beside GIT_BRANCH also expose it as BRANCH
Title: Message Title Andrew Bayer updated JENKINS-50815 Merged, will be in 1.2.10. Jenkins / JENKINS-50815 beside GIT_BRANCH also expose it as BRANCH Change By: Andrew Bayer Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50645) Post failure condition should be evaluated after other conditions
Title: Message Title Andrew Bayer updated JENKINS-50645 Merged, will be in 1.2.10. Jenkins / JENKINS-50645 Post failure condition should be evaluated after other conditions Change By: Andrew Bayer Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-50815) beside GIT_BRANCH also expose it as BRANCH
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50815 Re: beside GIT_BRANCH also expose it as BRANCH Code changed in jenkins User: Andrew Bayer Path: pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/when/impl/BranchConditionalScript.groovy pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/BasicModelDefTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/WhenStageTest.java pipeline-model-definition/src/test/resources/whenBranchNotMultibranch.groovy pom.xml http://jenkins-ci.org/commit/pipeline-model-definition-plugin/7fb4f69e3cf4fb9bfcd5addd10f96febd1d0e4fc Log: [FIXED JENKINS-50815] Fallback to GIT_LOCAL_BRANCH for when branch If we're not on multibranch (meaning BRANCH_NAME is null), fallback to GIT_LOCAL_BRANCH for when branch condition. We can theoretically add other SCMs here too if needed. We're using GIT_LOCAL_BRANCH because it most closely matches BRANCH_NAME - i.e., GIT_BRANCH includes the remote, GIT_LOCAL_BRANCH does not. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50645) Post failure condition should be evaluated after other conditions
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50645 Re: Post failure condition should be evaluated after other conditions Code changed in jenkins User: Andrew Bayer Path: pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Failure.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Success.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Unstable.groovy pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/BuildConditionResponderTest.java pipeline-model-definition/src/test/resources/postFailureAfterSuccess.groovy pipeline-model-definition/src/test/resources/postFailureAfterUnstable.groovy http://jenkins-ci.org/commit/pipeline-model-definition-plugin/7e0eaf4b300cd98b6754d940dbad19c5d51de5b2 Log: [FIXED JENKINS-50645] Move failure to run after other status checks This way failure will still evaluate even if the actual failure doesn't occur until in the success or unstable blocks. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37575) Delays in FileMonitoringTask.WriteLog can cause process output to be resent indefinitely
Title: Message Title John Zila commented on JENKINS-37575 Re: Delays in FileMonitoringTask.WriteLog can cause process output to be resent indefinitely Any progress on this? We just started seeing this again yesterday, with multi-GB logs and interminable builds. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50974) AWS CodeDeploy plug-in fails with new JEP-200 whitelist
Title: Message Title Sriram Veeraraghavan created an issue Jenkins / JENKINS-50974 AWS CodeDeploy plug-in fails with new JEP-200 whitelist Issue Type: Bug Assignee: Andrew Fitz Gibbon Components: codedeploy-plugin Created: 2018-04-24 19:36 Priority: Minor Reporter: Sriram Veeraraghavan Jenkins version: 2.107.2 CodeDeploy plug-in version: 1.19 Amazon Web Services SDK plug-in version: 1.11.264 error message: ERROR: Failed to parse POMs java.io.IOException: java.lang.RuntimeException: Failed to serialize hudson.maven.MavenModuleSet#publishers for class hudson.maven.MavenModuleSet at hudson.XmlFile.write(XmlFile.java:200) at hudson.model.AbstractItem.save(AbstractItem.java:483) at hudson.model.Job.save(Job.java:196) at hudson.model.AbstractProject.save(AbstractProject.java:289) at hudson.model.AbstractProject.setJDK(AbstractProject.java:893) at com.datalex.jdkparameter.JavaParameterBuildWrapper$1.tearDown(JavaParameterBuildWrapper.java:60) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:902) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1727) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:544) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Caused by: java.lang.RuntimeException: Failed to serialize hudson.maven.MavenModuleSet#publishers for class hudson.maven.MavenModuleSet at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at
[JIRA] (JENKINS-12660) Fail to start the windows service when trying to launch slave node
Title: Message Title Justin Corbett commented on JENKINS-12660 Re: Fail to start the windows service when trying to launch slave node Manually setting the log on credentials within the service itself directly on the Win 7 box fixed it for me. Used the same creds, but when doing it manually Windows grants the Service Logon right to the user. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46878) Merge before build behavior isn't executed on slaves
Title: Message Title Samuel Gabriel commented on JENKINS-46878 Re: Merge before build behavior isn't executed on slaves We are also experiencing this issue for many years now. We have two projects that depend on each other. So sometimes we do push the dependent project before the dependency project. In that case the merge would happen merging the new branch and creating a merge commit that doesn't exist anywhere else. When the dependency project completes the next build of the dependent would lead to this error. The only solution is to delete the failed build and the one before it then it would build again. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50949) Track update levels properly in the backend datastore
Title: Message Title R. Tyler Croy updated JENKINS-50949 Jenkins / JENKINS-50949 Track update levels properly in the backend datastore Change By: R. Tyler Croy Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50973) Insufficient free memory triggers Java install attempt
Title: Message Title Theral Mackey created an issue Jenkins / JENKINS-50973 Insufficient free memory triggers Java install attempt Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: ssh-slaves-plugin Created: 2018-04-24 19:01 Labels: java memory install version Priority: Minor Reporter: Theral Mackey Recently Jenkins disconnected from one of our linux slaves. When we tried restarting it, it failed. Investigating found insufficient memory to start Java (runaway python processes). The Agent, however, decided this was a problem with java not being installed and tried to reinstall it. More: The log in jenkins shows the ssh agent connecting to the slave, verifying environment settings, then attempting to get the Java Version. Due to low-memory, it can't start Java to get its version (Java err12). After this failure it tries a few other locations for the Java bin that we do not use, then determines Java must not be installed. It then attempts to download and install Java, which fails due to Oracle's credential requirement for downloads (reported in other tickets, but not a bug, we install Java by puppet/hand). Expected: It finds that Java exists, but fails to start due to Memory (errno 12), reports this and exits. It does NOT try to install Java. The OOM condition is unrelated to Java (runaway python processes on the same machine), and we are addressing the xxMaxPermSize attribute though it should not have contributed here either. [04/24/18 09:47:25] [SSH] Opening SSH connection to ourslave.build.slaves:22. [04/24/18 09:47:25] [SSH] Authentication successful. [04/24/18 09:47:25]
[JIRA] (JENKINS-27457) deploy is completed however deployed ear(war) doesn't start with a error (SRVE0303E)
Title: Message Title Greg Peters stopped work on JENKINS-27457 Change By: Greg Peters Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27457) deploy is completed however deployed ear(war) doesn't start with a error (SRVE0303E)
Title: Message Title Greg Peters commented on JENKINS-27457 Re: deploy is completed however deployed ear(war) doesn't start with a error (SRVE0303E) After reviewing this issue, it was resolved by removing the IBM proprietary files from the WAR. 1) The attached EAR file will not deploy to WAS successfully because it contains the ibm-*.xml files 2) I extracted the WAR, removed all the ibm-*.xml files and repacked the WAR 3) I had to stop the defaultApplication (which conflicts with the "/" context) that is pre-packaged with WAS 4) In the WDP jenkins configuration, I specified "/" for the "Generated Context" 5) Deployment timeout (minutes) was set to "1" 6) Generated EAR Level was "Java EE 7" 7) Certified working on WAS ND v9.0.0.7 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27457) deploy is completed however deployed ear(war) doesn't start with a error (SRVE0303E)
Title: Message Title Greg Peters updated an issue Jenkins / JENKINS-27457 deploy is completed however deployed ear(war) doesn't start with a error (SRVE0303E) Change By: Greg Peters Attachment: Screen Shot 2018-04-24 at 2.34.42 PM.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50972) broken link to jira in top level readme.md
Title: Message Title Ben Sherman created an issue Jenkins / JENKINS-50972 broken link to jira in top level readme.md Issue Type: Bug Assignee: Jan Roehrich Components: amazon-ecs-plugin Created: 2018-04-24 18:09 Environment: Main page - no env needed. Labels: documentation Priority: Trivial Reporter: Ben Sherman https://github.com/jenkinsci/amazon-ecs-plugin/ has a broken link to this wiki. Fixed in https://github.com/jenkinsci/amazon-ecs-plugin/pull/60 Add Comment
[JIRA] (JENKINS-50949) Track update levels properly in the backend datastore
Title: Message Title R. Tyler Croy started work on JENKINS-50949 Change By: R. Tyler Croy Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50923) Blue Ocean: When step failed, the last step also marked failed
Title: Message Title Sverre Moe updated an issue Jenkins / JENKINS-50923 Blue Ocean: When step failed, the last step also marked failed Change By: Sverre Moe Issue Type: New Feature Bug Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50327) Update to 2.10.4 causes NullPointerException in HTTPDigestAuthentication.createDigest
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-50327 Re: Update to 2.10.4 causes NullPointerException in HTTPDigestAuthentication.createDigest Sysadmins MRM Do you use the AuthzSVNAccessFile apache module to authenticate? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50971) Projeto para rodar pipelines do Bitbucket com Docker.
Title: Message Title João Melo closed an issue as Fixed Jenkins / JENKINS-50971 Projeto para rodar pipelines do Bitbucket com Docker. Change By: João Melo Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50971) Projeto para rodar pipelines do Bitbucket com Docker.
Title: Message Title João Melo created an issue Jenkins / JENKINS-50971 Projeto para rodar pipelines do Bitbucket com Docker. Issue Type: New Feature Assignee: João Melo Components: docker Created: 2018-04-24 17:29 Priority: Minor Reporter: João Melo Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-50970) SLF4J logging not working in Jenkins Swarm plugin
Title: Message Title Kevin Phillips created an issue Jenkins / JENKINS-50970 SLF4J logging not working in Jenkins Swarm plugin Issue Type: Improvement Assignee: Oleg Nenashev Components: swarm-plugin Created: 2018-04-24 17:21 Environment: jenkins v2.108 swarm v3.12 JDK 1.8.0 Windows 7 / CentOS 7.4 host OSes Priority: Major Reporter: Kevin Phillips When launching the Jenkins swarm client, I see the following warning message in the console output: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder" SLF4J: Defaulting to no-operation (NOP) loger implementation Consequently, I am unable to generate log files for the service, making it impossible to debug errors and connection issues and such in production. This seems like a silly issue but it is debilitating and it would be great if someone could fix it or tell me how to work around the issue. I've looked up the slf4j.org website where it describes some workarounds to this error by placing one of the slf4j jars in the Java class path. I downloaded several different versions of slf4j, and copied different jar files contained therein to the default class path, all with no success. Even explicitly setting the java class path to a folder containing all the jars for slf4j didn't work. What am I doing wrong? Any help would be greatly appreciated.
[JIRA] (JENKINS-46809) Allow sequential stages inside parallel in Declarative syntax
Title: Message Title SCM/JIRA link daemon commented on JENKINS-46809 Re: Allow sequential stages inside parallel in Declarative syntax Code changed in jenkins User: Andrew Bayer Path: pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTStage.java pipeline-model-api/src/main/resources/ast-schema.json pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/Stage.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/JSONParser.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/ModelParser.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/RuntimeASTTransformer.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/validator/ModelValidatorImpl.groovy pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/Messages.properties pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/AbstractModelDefTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/AgentTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/BasicModelDefTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/DeclarativeUpgradeTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/EnvironmentTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/PostStageTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/ToolsTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/ValidatorTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/WhenStageTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/parser/ExecuteConvertedTest.java pipeline-model-definition/src/test/resources/agentOnGroup.groovy pipeline-model-definition/src/test/resources/environmentInGroup.groovy pipeline-model-definition/src/test/resources/errors/emptyStagesInGroup.groovy pipeline-model-definition/src/test/resources/errors/parallelStagesAndGroups.groovy pipeline-model-definition/src/test/resources/errors/parallelStagesGroupsDeepNesting.groovy pipeline-model-definition/src/test/resources/errors/parallelStagesStepsAndGroups.groovy pipeline-model-definition/src/test/resources/errors/parallelStepsAndGroups.groovy pipeline-model-definition/src/test/resources/errors/topLevelStageGroupsDeepNesting.groovy pipeline-model-definition/src/test/resources/json/agentOnGroup.json pipeline-model-definition/src/test/resources/json/errors/parallelStagesAndGroups.json pipeline-model-definition/src/test/resources/json/errors/parallelStagesGroupsDeepNesting.json pipeline-model-definition/src/test/resources/json/errors/parallelStagesStepsAndGroups.json pipeline-model-definition/src/test/resources/json/errors/parallelStepsAndGroups.json pipeline-model-definition/src/test/resources/json/errors/topLevelStageGroupsDeepNesting.json pipeline-model-definition/src/test/resources/json/parallelStagesGroupsAndStages.json pipeline-model-definition/src/test/resources/json/topLevelStageGroup.json
[JIRA] (JENKINS-47462) Gerrit trigger does not update review with SUCCESS status due to it waiting for the current job to complete twice.
Title: Message Title omri ifergan commented on JENKINS-47462 Re: Gerrit trigger does not update review with SUCCESS status due to it waiting for the current job to complete twice. Happend to me as well: OS:Ubuntu 16.04 Docker: Docker version 17.06.0-ce, build 02c1d87 Jenkins Version 2.107.1 Gerrit plugin Version :2.27.5 very annoing Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50327) Update to 2.10.4 causes NullPointerException in HTTPDigestAuthentication.createDigest
Title: Message Title Richard van der Klooster commented on JENKINS-50327 Re: Update to 2.10.4 causes NullPointerException in HTTPDigestAuthentication.createDigest I moved our archive from svn to git so this is not blocking for us anymore. Thanks for checking. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50781) Shiro Plugin - Refusing to marshal org.apache.shiro.authc.credential.AllowAllCredentialsMatcher for security reasons
Title: Message Title angel liang updated an issue Jenkins / JENKINS-50781 Shiro Plugin - Refusing to marshal org.apache.shiro.authc.credential.AllowAllCredentialsMatcher for security reasons Change By: angel liang Attachment: hudson.zip Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46476) Environment and Options blocks do not take effect from within groovy shared variable
Title: Message Title Brandon Parker commented on JENKINS-46476 Re: Environment and Options blocks do not take effect from within groovy shared variable Since this is actually supported in Jenkins, this is a serious issue that should be addressed. https://jenkins.io/doc/book/pipeline/shared-libraries/#defining-declarative-pipelines So I'd really like to see some movement on getting this solved. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50556) git polling succeeds even when origin/master has nothing new
Title: Message Title Jacob Keller commented on JENKINS-50556 Re: git polling succeeds even when origin/master has nothing new I submitted a pull request https://github.com/jenkinsci/git-plugin/pull/583 which should remove that restriction (as far as I can tell, it was inadvertently added and there's no reason that the extension "author in change log" depends on the workspace polling. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50969) core site build is broken, needed for core taglibs reference
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-50969 core site build is broken, needed for core taglibs reference Issue Type: Bug Assignee: Baptiste Mathus Components: core Created: 2018-04-24 16:58 Environment: Since core 2.79 Labels: regression Priority: Major Reporter: Daniel Beck It looks like https://github.com/jenkinsci/jenkins/pull/2998 by Baptiste Mathus broke the site build. We need this to publish the core taglibs documentation via https://github.com/jenkins-infra/core-taglibs-report-generator Add Comment
[JIRA] (JENKINS-50886) Declarative pipeline with pollSCM triggers 2 builds
Title: Message Title Mark Waite commented on JENKINS-50886 Re: Declarative pipeline with pollSCM triggers 2 builds @abayer since the polling interval is every 2 minutes, I assume the build must complete in much less than 2 minutes. If the build does not complete in 2 minutes, it seems there might be a risk that the same changes detected earlier might be detected again. I don't recall a similar bug being reported, though there are several open bugs related to polling scenarios. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50966) Git Plugin Error 128 (unpack-objects failed)
Title: Message Title Mark Waite resolved as Not A Defect The failure message is being reported by command line git. The failure is outside the influence of the git plugin and outside the influence of the git client plugin. You might refer to the following resources to investigate the command line git issue further: stackoverflow - unresolved deltas left after unpacking Git for human beings mailing list - fatal unresolved deltas error Git 2.11.0 failure pulling to Windows share Phabricator detected issue with corrupt repo Jenkins / JENKINS-50966 Git Plugin Error 128 (unpack-objects failed) Change By: Mark Waite Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50556) git polling succeeds even when origin/master has nothing new
Title: Message Title Phil Adams commented on JENKINS-50556 Re: git polling succeeds even when origin/master has nothing new Jacob, thanks for the info... it turns out that I did in fact have the "author in change log" option selected, and that was why workspace polling was being used. By disabling that option, the plugin started doing remote polling. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50968) DATA dissapear from Input with several textfields
Title: Message Title Igor Nikonov created an issue Jenkins / JENKINS-50968 DATA dissapear from Input with several textfields Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2018-04-24 15:41 Labels: input pipeline Priority: Minor Reporter: Igor Nikonov Hello. I'm faced with a problem - in my pipeline i have input step with 2 textboxes. I want to put there some links, for example, from browser. I entered first link in the first textbox, then I go and copy second link, open input in jenkins and the first field is already empty. Add Comment
