[JIRA] (JENKINS-39143) Stage view disappears after restarting jenkins
Title: Message Title Christian Schneider commented on JENKINS-39143 Re: Stage view disappears after restarting jenkins I can confirm this as well. And upgrading plus deleting all builds does not help permanently. After a while these issues come back. It seems unexpected aborts and even unexecuted stages due to 'when' conditions can cause these issues. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53088) Node Xml is not valid to updateAlmEntity Rest Service. (Testset)
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-53088 Node Xml is not valid to updateAlmEntity Rest Service. (Testset) Change By: Daniel Gront Labels: ALM Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53088) Node Xml is not valid to updateAlmEntity Rest Service. (Testset)
Title: Message Title Daniel Gront assigned an issue to Roy Lu Jenkins / JENKINS-53088 Node Xml is not valid to updateAlmEntity Rest Service. (Testset) Change By: Daniel Gront Assignee: Daniel Gront Roy Lu Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21986) RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Setting Test Execution Duration
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-21986 RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Setting Test Execution Duration Change By: Daniel Gront Labels: ALM UFT Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21987) RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Using Timeout Parameter
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-21987 RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Using Timeout Parameter Change By: Daniel Gront Labels: ALM UFT Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53514) 'Keep me signed in' combobox do not visible in compatibility mode ie11
Title: Message Title Maksim Butor created an issue Jenkins / JENKINS-53514 'Keep me signed in' combobox do not visible in compatibility mode ie11 Issue Type: Bug Assignee: Maksim Butor Attachments: 1.jpg, 2.jpg, 3.jpg Components: _unsorted Created: 2018-09-12 05:12 Environment: Jenkins ver. 2.141 Priority: Major Reporter: Maksim Butor 'Keep me signed in' combobox do not visible in compatibility mode ie11 (see 1.jpg, 2.jpg) If delete site from compatibility mode list then all ok. (see 3.jpg). Add Comment
[JIRA] (JENKINS-53513) kins erorrs
Title: Message Title karthick n updated an issue Jenkins / JENKINS-53513 kins erorrs Change By: karthick n Summary: java.lang.SecurityException: Rejected: com.sun.org.apache.xerces.internal.dom.DocumentImpl; see https://jenkins.io/redirect/class-filter/ kins erorrs Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50772) Content type not set reasonably
Title: Message Title Jarrad Whitaker commented on JENKINS-50772 Re: Content type not set reasonably RobustHttpClient.uploadFile also has no way of setting a content type, which is another blocker for this I think? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32485) Extension Point for contributing usage statistics
Title: Message Title Baptiste Mathus stopped work on JENKINS-32485 Change By: Baptiste Mathus Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53513) java.lang.SecurityException: Rejected: com.sun.org.apache.xerces.internal.dom.DocumentImpl; see https://jenkins.io/redirect/class-filter/
Title: Message Title karthick n closed an issue as Not A Defect Jenkins / JENKINS-53513 java.lang.SecurityException: Rejected: com.sun.org.apache.xerces.internal.dom.DocumentImpl; see https://jenkins.io/redirect/class-filter/ Change By: karthick n Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53513) java.lang.SecurityException: Rejected: com.sun.org.apache.xerces.internal.dom.DocumentImpl; see https://jenkins.io/redirect/class-filter/
Title: Message Title karthick n updated an issue Jenkins / JENKINS-53513 java.lang.SecurityException: Rejected: com.sun.org.apache.xerces.internal.dom.DocumentImpl; see https://jenkins.io/redirect/class-filter/ Change By: karthick n java.lang.SecurityException: Rejected: com.sun.org.apache.xerces.internal.dom.DocumentImpl; see https://jenkins.io/redirect/class-filter/ at hudson.remoting.ClassFilter.check(ClassFilter.java:77) at hudson.remoting.MultiClassLoaderSerializer$Input.resolveClass(MultiClassLoaderSerializer.java:135) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1868) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1751) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2042) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1573) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:431) at hudson.remoting.UserRequest.deserialize(UserRequest.java:291) at hudson.remoting.UserRequest$NormalResponse.retrieve(UserRequest.java:326) at hudson.remoting.Channel.call(Channel.java:955)Caused: java.io.IOException: Failed to deserialize response to UserRequest:com.abc.jenkins.plugins.util.BuilderCallable@6dd0bad6 at hudson.remoting.Channel.call(Channel.java:963) at hudson.FilePath.act(FilePath.java:1036) at hudson.FilePath.act(FilePath.java:1025) at com.bosch.jenkins.plugins.sdom.checkout.ChangeLogBuilder.createChangeLog(NBC.java:35) at com.bosch.jenkins.plugins.sdom.checkout.SdomConnector.changeLogFileWrite(ABC.java:984) at com.bosch.jenkins.plugins.sdom.checkout.SdomConnector.checkout(XYZ.java:772) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:113) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:85) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:75) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)Finished: FAILURE
[JIRA] (JENKINS-53513) java.lang.SecurityException: Rejected: com.sun.org.apache.xerces.internal.dom.DocumentImpl; see https://jenkins.io/redirect/class-filter/
Title: Message Title karthick n created an issue Jenkins / JENKINS-53513 java.lang.SecurityException: Rejected: com.sun.org.apache.xerces.internal.dom.DocumentImpl; see https://jenkins.io/redirect/class-filter/ Issue Type: Task Assignee: karthick n Components: owl-reporter-plugin Created: 2018-09-12 04:40 Environment: Jenkins ver. 2.121.3 Priority: Major Reporter: karthick n java.lang.SecurityException: Rejected: com.sun.org.apache.xerces.internal.dom.DocumentImpl; see https://jenkins.io/redirect/class-filter/ at hudson.remoting.ClassFilter.check(ClassFilter.java:77) at hudson.remoting.MultiClassLoaderSerializer$Input.resolveClass(MultiClassLoaderSerializer.java:135) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1868) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1751) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2042) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1573) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:431) at hudson.remoting.UserRequest.deserialize(UserRequest.java:291) at hudson.remoting.UserRequest$NormalResponse.retrieve(UserRequest.java:326) at hudson.remoting.Channel.call(Channel.java:955) Caused: java.io.IOException: Failed to deserialize response to UserRequest:com.abc.jenkins.plugins.util.BuilderCallable@6dd0bad6 at hudson.remoting.Channel.call(Channel.java:963) at hudson.FilePath.act(FilePath.java:1036) at hudson.FilePath.act(FilePath.java:1025) at com.bosch.jenkins.plugins.sdom.checkout.ChangeLogBuilder.createChangeLog(NBC.java:35) at com.bosch.jenkins.plugins.sdom.checkout.SdomConnector.changeLogFileWrite(ABC.java:984) at com.bosch.jenkins.plugins.sdom.checkout.SdomConnector.checkout(XYZ.java:772) at
[JIRA] (JENKINS-39143) Stage view disappears after restarting jenkins
Title: Message Title Martin Reinhardt commented on JENKINS-39143 Re: Stage view disappears after restarting jenkins We're seeing this issue also: java.lang.IllegalStateException: Matching start node 2 lost from deserializationjava.lang.IllegalStateException: Matching start node 2 lost from deserialization at org.jenkinsci.plugins.workflow.graph.BlockEndNode.getStartNode(BlockEndNode.java:65) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.isParallelEnd(ForkScanner.java:170) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.setHeads(ForkScanner.java:474) at org.jenkinsci.plugins.workflow.graphanalysis.AbstractFlowScanner.setup(AbstractFlowScanner.java:141) at org.jenkinsci.plugins.workflow.graphanalysis.AbstractFlowScanner.setup(AbstractFlowScanner.java:152) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.visitSimpleChunks(ForkScanner.java:632) at com.cloudbees.workflow.rest.external.RunExt.createNew(RunExt.java:321) at com.cloudbees.workflow.rest.external.RunExt.create(RunExt.java:309) at com.cloudbees.workflow.rest.external.JobExt.create(JobExt.java:131) at com.cloudbees.workflow.rest.endpoints.JobAPI.doRuns(JobAPI.java:69) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343)Caused: java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:347) at com.cloudbees.workflow.util.ServeJson$Processor.invoke(ServeJson.java:30)Caused: java.lang.RuntimeException: Unexpected exception while serving JSON at com.cloudbees.workflow.util.ServeJson$Processor.invoke(ServeJson.java:34) 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:734) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:864) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:734) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:864) 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:734) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:864) 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:734) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:864) 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:734) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:864) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:860) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650) at
[JIRA] (JENKINS-52922) slave is getting disconnected in the middle of the job
Title: Message Title sumanthnath gangavarapu commented on JENKINS-52922 Re: slave is getting disconnected in the middle of the job Jenkins Slave Logs: Sep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusSep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Agent discovery successful Agent address: ci.kantarworldpanel.com Agent port: 49187 Identity: 2b:ec:57:ae:00:0c:10:39:59:ca:a4:1c:a7:05:46:dcSep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: HandshakingSep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to ci.kantarworldpanel.com:49187Sep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Trying protocol: JNLP4-connectSep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Remote identity confirmed: 2b:ec:57:ae:00:0c:10:39:59:ca:a4:1c:a7:05:46:dcSep 12, 2018 2:56:01 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to ci.kantarworldpanel.com/:49187] Local headers refused by remote: jenkins2-win-slave is already connected to this master. Rejecting this connection.Sep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: jenkins2-win-slave is already connected to this master. Rejecting this connection. at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: jenkins2-win-slave is already connected to this master. Rejecting this connection. at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:378) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:433) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1500(BIONetworkLayer.java:48) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:247) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Unknown Source) Suppressed: java.nio.channels.ClosedChannelException ... 7 more Sep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to ci.kantarworldpanel.com:49187Sep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP4-plaintext not supported, skippingSep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP3-connect not supported, skippingSep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP2-connect not supported, skippingSep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP-connect not supported, skippingSep 12, 2018
[JIRA] (JENKINS-52922) slave is getting disconnected in the middle of the job
Title: Message Title
sumanthnath gangavarapu commented on JENKINS-52922
Re: slave is getting disconnected in the middle of the job
Hi Jeff Thompson, Thanks for your reply. Here is what I did as a part of troubleshooting. I ran the powershell script which attempted to connect to the Linux server via 443 over and over and over again. I also changed it to 49187 after a reboot. The entire time we ran this we did not see it drop once. I believe we have layer 4 communication down. while ($true) { "$(Get-Date);$(Test-netconnection -ComputerName -port 443 -informationlevel quiet)" } Next I went ahead and pushed a 5GB file via SCP from the Windows slave server to the Linux master server. The data was able to arrive on the server without an issue. I believe we have layer 7 communication down as well. I also ran the job and did some netstat information on both ends, seeing communication back and forth. As you have suggested I have checked for CPU memory issues and disc space issues and they are normal. I have captured logs can you please take a look at them. Java Log from Slave node: Java Web Start 11.181.2.13 x86Java Web Start 11.181.2.13 x86Using JRE version 1.8.0_181-b13 Java HotSpot(TM) Client VMUser home directory = C:\Users\saadmin---c: clear console windowf: finalize objects on finalization queueg: garbage collecth: display this help messagem: print memory usageo: trigger loggingp: reload proxy configurationq: hide consoler: reload policy configurations: dump system and deployment propertiest: dump thread listv: dump thread stack0-5: set trace level to ---Sep 10, 2018 2:07:12 PM hudson.remoting.jnlp.Main createEngineINFO: Setting up agent: jenkins2-win-slaveSep 10, 2018 2:07:12 PM hudson.remoting.Engine startEngineINFO: Using Remoting version: 3.25Sep 10, 2018 2:07:12 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDirINFO: Using C:\Jenkins\remoting as a remoting work directoryBoth error and output logs will be printed to C:\Jenkins\remotingSep 10, 2018 2:07:12 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]Sep 10, 2018 2:07:12 PM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to ci.kantarworldpanel.com/:49187] Local headers refused by remote: jenkins2-win-slave is already connected to this master. Rejecting this connection.Sep 10, 2018 2:07:12 PM hudson.remoting.jnlp.GuiListener$1 runINFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: jenkins2-win-slave is already connected to this master. Rejecting this connection. at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: jenkins2-win-slave is already connected to this master. Rejecting this connection. at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:378) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:433) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at
[JIRA] (JENKINS-52922) slave is getting disconnected in the middle of the job
Title: Message Title sumanthnath gangavarapu updated an issue Jenkins / JENKINS-52922 slave is getting disconnected in the middle of the job Change By: sumanthnath gangavarapu Attachment: MasterNode-Logs.txt Attachment: SlaveNode-Logs.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila updated an issue Jenkins / JENKINS-53468 Since 1.27 update Channel is closing or has closed down Change By: John Zila Attachment: config.xml Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down Which Jenkins core version do you use? Jenkins 2.141 Which OS do you use on your SSH agents? Debian Jessie. admin@ip-10-0-0-211:~$ uname -a Linux ip-10-0-0-211 4.9.0-0.bpo.6-amd64 #1 SMP Debian 4.9.88-1+deb9u1~bpo8+1 (2018-05-13) x86_64 GNU/Linux Which OpenSSH version do you have installed on your SSH agents? admin@ip-10-0-0-211:~$ ssh -V OpenSSH_6.7p1 Debian-5+deb8u4, OpenSSL 1.0.1t 3 May 2016 Do it happen only on the SSH agents? yes Do it happen on all SSH agents or only on a few? Is there something in common between those SSH agents? randomly, most of them Are your SSH agents static or provisioned by a cloud plugin (k8s, Mesos, Docker, EC2, Azure, ...)? EC2 spot fleet plugin Could you attach the agent connection log (JENKINS_URL/computer/NODENAME/log)? No, because I'd have to switch my cluster to use the broken plugin Could you attach the logs inside the remoting folder (see https://github.com/jenkinsci/remoting/blob/master/docs/workDir.md#remoting-work-directory)? No, as above I'd have to switch my cluster to use the broken plugin Could you attach the agent configuration (JENKINS_URL/computer/NODENAME/config.xml) file? attached config.xml Do you see if it happens always with the same job or type of job? any job Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-53237) Maven Surefire Report XSD requires a fix
Title: Message Title Tibor Digana commented on JENKINS-53237 Re: Maven Surefire Report XSD requires a fix Oleg Nenashev It seems you agree since you have not reply. I am going to push it to master in ASF Maven. Any objections? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53506) Update all installed plugins to latest version
Title: Message Title Jesse Glick commented on JENKINS-53506 Re: Update all installed plugins to latest version I think my suggestion at the time was to require essentials.yaml to declare all plugins explicitly, but add a boolean transitive flag to each plugin entry and then fail the build if there are any plugins marked as transitive which do not have a hard (~ not optional) dependency chain from at least one nontransitive plugin in the list. Thus you can see at a glance which plugins are there because they offer some important feature, vs. being just along for the ride, and if you accidentally “orphan” some transitive dependency (for example because some routine plugin update finally picks up the holy grail of dropping the last hard dep on maven-plugin) then you will be alerted to the situation immediately and can delete the now-obsolete plugin (or decide you really wanted to keep it after all, and mark it nontransitive). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53511) Improve discovery / readability of WebClient tricks in test
Title: Message Title Wadeck Follonier updated JENKINS-53511 Jenkins / JENKINS-53511 Improve discovery / readability of WebClient tricks in test Change By: Wadeck Follonier Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53511) Improve discovery / readability of WebClient tricks in test
Title: Message Title Wadeck Follonier started work on JENKINS-53511 Change By: Wadeck Follonier Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50795) jenkins search java.lang.NullPointerException at hudson.search.FixedSet.find(FixedSet.java:53)
Title: Message Title Oleg Nenashev commented on JENKINS-50795 Re: jenkins search java.lang.NullPointerException at hudson.search.FixedSet.find(FixedSet.java:53) Hmm: https://github.com/jenkinsci/jenkins/blob/22aa2e6e766074d11249893e3f35e0b99e20d3d0/core/src/main/java/hudson/model/AbstractModelObject.java#L117 Some getDisplayName() methods may return null I believe we need document/annotate nulls and getDisplayName() methods in a follow-up task. Otherwise there will be a risk when such "hidden items" somehow get to the search output Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53512) unable to pass params values to shared library vars .groovy
Title: Message Title
Daniel Hsueh updated an issue
Jenkins / JENKINS-53512
unable to pass params values to shared library vars .groovy
Change By:
Daniel Hsueh
(probably/likely related to JENKINS-51166) in a scripted pipeline using a shared library "vars" .groovy file, passing "params.*" values results in an exception {code:java}java.lang.NullPointerException: Cannot get property (property) on null object{code}but if I define an intermediary variable and pass that, it worksI'm not sure how to explain it in groovy parlance, but an example should demonstrate:shared-test/vars/paramEcho.groovy (provided via filesystem_scm 2.1): {code:java}#!/usr/bin/env groovydef call(body) {def config = [:]body.resolveStrategy = Closure.DELEGATE_FIRSTbody.delegate = configbody()node {echo "config=${config}"}}{code} failing Jenkinsfile {code:java}#!groovy@Library('shared-test') _properties( [parameters([ booleanParam(name:'truefalse', defaultValue:true, description:'boolean'),string(name:'stringthing', defaultValue:'mary had a little lamb', description:'string')])] )paramEcho {booleanvalue = params.truefalsestringvalue = params.stringthing}{code} result{code:java}[Pipeline] properties[Pipeline] End of Pipelinejava.lang.NullPointerException: Cannot get property 'truefalse' on null object at org.codehaus.groovy.runtime.NullObject.getProperty(NullObject.java:60) at org.codehaus.groovy.runtime.InvokerHelper.getProperty(InvokerHelper.java:174) at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:456) at org.kohsuke.groovy.sandbox.impl.Checker$6.call(Checker.java:290) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:292) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:29) at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20) at WorkflowScript.run(WorkflowScript:14) at paramEcho.call(/var/lib/jenkins/jobs/test-jobs/jobs/test-paramEcho/builds/1/libs/shared-test/vars/paramEcho.groovy:7) at WorkflowScript.run(WorkflowScript:13) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:74) at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30) at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:66) at sun.reflect.GeneratedMethodAccessor341.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) at com.cloudbees.groovy.cps.Next.step(Next.java:83) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174) at
[JIRA] (JENKINS-53512) unable to pass params values to shared library vars .groovy
Title: Message Title
Daniel Hsueh created an issue
Jenkins / JENKINS-53512
unable to pass params values to shared library vars .groovy
Issue Type:
Bug
Assignee:
vjuranek
Components:
groovy-plugin
Created:
2018-09-11 20:31
Environment:
jenkins 2.140 pipeline (workflow-aggregator) 2.5 workflow-api 2.29 workflow-cps 2.54 workflow-cps-global-lib 2.10
Priority:
Minor
Reporter:
Daniel Hsueh
(probably/likely related to JENKINS-51166) in a scripted pipeline using a shared library "vars" .groovy file, passing "params.*" values results in an exception
java.lang.NullPointerException: Cannot get property (property) on null object
but if I define an intermediary variable and pass that, it works I'm not sure how to explain it in groovy parlance, but an example should demonstrate: shared-test/vars/paramEcho.groovy (provided via filesystem_scm 2.1):
#!/usr/bin/env groovy
def call(body) {
def config = [:]
body.resolveStrategy = Closure.DELEGATE_FIRST
body.delegate = config
body()
node {
echo "config=${config}"
}
}
failing Jenkinsfile
[JIRA] (JENKINS-50176) Locked resources using the variable parameter do not get reset to the variable once released to another requester and only appear as null on subsequent locks
Title: Message Title Jagadeesh Inugunti edited a comment on JENKINS-50176 Re: Locked resources using the variable parameter do not get reset to the variable once released to another requester and only appear as null on subsequent locks [~jbogers] We are still seeing this issue with lockable resource plugin , I dont see changes in PR #87 merged to master either . Please let us know if someone is working/looking into this issue , it will be really helpful if this gets resolved . Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50176) Locked resources using the variable parameter do not get reset to the variable once released to another requester and only appear as null on subsequent locks
Title: Message Title Jagadeesh Inugunti commented on JENKINS-50176 Re: Locked resources using the variable parameter do not get reset to the variable once released to another requester and only appear as null on subsequent locks Jeroen Bogers We are still seeing this issue with lockable resource plugin , I dont see changes in PR #87 merged to master either . Please let us know if someone is working/looking into this issue , it will be really helpful if this gets resolved . Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52922) slave is getting disconnected in the middle of the job
Title: Message Title Jeff Thompson commented on JENKINS-52922 Re: slave is getting disconnected in the middle of the job sumanthnath gangavarapu, there isn't enough information in your report to perform a meaningful diagnosis. A ClosedChannelException merely indicates that the channel the agent and master were communicating on has been closed. Nothing in the report provides any indication as to how or why the channel was closed. Generally, these sorts of failures are due to system or environment issues. It isn't a problem in the code but something external that causes the connection to close. You should investigate your systems and networks so that you can isolate and determine the cause of the failure. A short, abbreviated sample of the things you should examine: Check agent logs. Check master logs. Check system logs, such as Windows Event logs. Look for high resource usage (CPU, disk, network, etc.) on master and agent machines. Investigate network issues. Look for any commonalities among the failures such as Time of day Duration of job Operating system System uptime Check the health and logs of the hosting environments. Match all of the timestamps and events up together with the failures to try and develop a picture of what is occurring. As a simple example, I saw some similar behavior on my Windows machine when it decided it was time to go to sleep. (Windows server OSes don't usually have this behavior.) I'm sorry that I'm not able to solve this problem for you, but the investigation needs to be performed at your end. If you manage to figure out the cause, I'd be curious to learn what you discovered. Add Comment
[JIRA] (JENKINS-33596) Disable DNSMultiCast & UDPBroadcastThread by default
Title: Message Title Jesse Glick commented on JENKINS-33596 Re: Disable DNSMultiCast & UDPBroadcastThread by default For example, this could be discarded once the baseline version of core supported by the POM has this stuff detached. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33596) Disable DNSMultiCast & UDPBroadcastThread by default
Title: Message Title Jesse Glick commented on JENKINS-33596 Re: Disable DNSMultiCast & UDPBroadcastThread by default Please just add a link here to whatever you wind up doing in Evergreen, so that if we revisit in Jenkins itself we remember what to clean up. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50816) Disable DNS Multicast by default (and detach it to a plugin)
Title: Message Title Jesse Glick started work on JENKINS-50816 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50816) Disable DNS Multicast by default (and detach it to a plugin)
Title: Message Title Jesse Glick stopped work on JENKINS-50816 Change By: Jesse Glick Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50816) Disable DNS Multicast by default (and detach it to a plugin)
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-50816 Disable DNS Multicast by default (and detach it to a plugin) Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53511) Improve discovery / readability of WebClient tricks in test
Title: Message Title Wadeck Follonier created an issue Jenkins / JENKINS-53511 Improve discovery / readability of WebClient tricks in test Issue Type: Task Assignee: Wadeck Follonier Components: jenkins-test-harness Created: 2018-09-11 19:21 Priority: Minor Reporter: Wadeck Follonier When reviewing tests code, so often the developer is not aware of the WebClient#getOptions()#setThrowExceptionOnFailingStatusCode(false) trick and that implies the use of ugly try/catch. To ease the discovery of such options, the method should be only one-level depth. Add Comment
[JIRA] (JENKINS-52684) Configuration Job-Watching in jobA affects all of other job's Job-Watching
Title: Message Title Rick Liu commented on JENKINS-52684 Re: Configuration Job-Watching in jobA affects all of other job's Job-Watching agree with you~ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33596) Disable DNSMultiCast & UDPBroadcastThread by default
Title: Message Title R. Tyler Croy assigned an issue to Unassigned Whatever then, this can be stalled somewhere else other than my backlog Jenkins / JENKINS-33596 Disable DNSMultiCast & UDPBroadcastThread by default Change By: R. Tyler Croy Sprint: Evergreen - Milestone 1 Assignee: R. Tyler Croy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33596) Disable DNSMultiCast & UDPBroadcastThread by default
Title: Message Title Jesse Glick commented on JENKINS-33596 Re: Disable DNSMultiCast & UDPBroadcastThread by default Please either leave it open or file a separate issue with split-plugins-from-core. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52636) Gerrit triggered jobs getting delayed
Title: Message Title Marco Miller edited a comment on JENKINS-52636 Re: Gerrit triggered jobs getting delayed Thx [~scoheb]! ;)Btw, a colleague of ours noticed [1] recently, if need be, or there might be other /related PRs too:[1] [https://github.com/jenkinsci/gerrit-trigger-plugin/pull/363|https://github.com/jenkinsci/gerrit-trigger-plugin/pull/363/commits] Note: not sure how close [1] is to [~hugares]' well-detailed findings above, though (did not check myself). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52636) Gerrit triggered jobs getting delayed
Title: Message Title Marco Miller commented on JENKINS-52636 Re: Gerrit triggered jobs getting delayed Thx Scott Hebert! Btw, a colleague of ours noticed [1] recently, if need be, or there might be other /related PRs too: [1] https://github.com/jenkinsci/gerrit-trigger-plugin/pull/363 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33596) Disable DNSMultiCast & UDPBroadcastThread by default
Title: Message Title R. Tyler Croy started work on JENKINS-33596 Change By: R. Tyler Croy Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33596) Disable DNSMultiCast & UDPBroadcastThread by default
Title: Message Title R. Tyler Croy commented on JENKINS-33596 Re: Disable DNSMultiCast & UDPBroadcastThread by default I will be disabling this for Jenkins Evergreen and then closing this ticket since it's clearly stalled/dead. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52684) Configuration Job-Watching in jobA affects all of other job's Job-Watching
Title: Message Title Daniel Gront commented on JENKINS-52684 Re: Configuration Job-Watching in jobA affects all of other job's Job-Watching Rick Liu, I successfully reproduced it, it seems that you need to login in order to have this feature visible. Anyway as far as I can see all the design of this is flawed, the triggers are bound by the user and not by the job. I think it will require a redesign of the feature itself, which I lack the experience on how. If circumstances allow, David van Laatum could advise me on how to approach to it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47792) Job with in queue with status "pending description" do not start
Title: Message Title Jon Starbird commented on JENKINS-47792 Re: Job with in queue with status "pending description" do not start Ok. I seemed to have fixed my issue. I went into the parent job and enabled the block until upstream and downstream, saved. Reopened and disabled them. Then opened each job it was calling and then all of them showed they were being blocked while upstream job was building. I then disabled that flag on all of those jobs and then the build would run properly. It appears that somehow the block upstream flag is set but not shown to be set for the downstream jobs or something along those lines. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53477) Ensure the client marks itself at the latest update level even if no updates were applied
Title: Message Title R. Tyler Croy updated JENKINS-53477 Jenkins / JENKINS-53477 Ensure the client marks itself at the latest update level even if no updates were applied Change By: R. Tyler Croy Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47792) Job with in queue with status "pending description" do not start
Title: Message Title Jon Starbird commented on JENKINS-47792 Re: Job with in queue with status "pending description" do not start I'm still having this issue. It does only seem to impact new jobs as I do have other jobs that have not been edited in long time that still work. I am currently up to Jenkins 2.121.3. Also, I had not noticed this before but in the Job queue if I hover over the pending job it says Upstream project of Full Build is already building. That seems like it's not executing because it's waiting for it's parent job to finish. I do not have anything set for any job to wait for upstream jobs. The parent job is set to wait for the downstream job to finish before it continues. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53140) Intermittent Random Stage Failures - No Changes Detected - Parallel Stages
Title: Message Title jerry wiltse commented on JENKINS-53140 Re: Intermittent Random Stage Failures - No Changes Detected - Parallel Stages I have some new information that might be relevant to isolating the problem. I moved the pipline out of jenkinsfile and into the GUI. The duplicates in the changelog have gone away. Thus, the recipe for at least one problem is simple: Pipeline from SCM SVN being the SCM used for this Multiple Stages? Unfortunately, we can't currently find a workaround here without more help. It seems that when not using "pipeline script from SCM", the stages all run in different subdirectories rather than the directory the "checkout" stage ran in. For some reason, the first stage after "checkout" runs in the same directory, but the others choose different directories. our existing scripts all count on the files being there from a checkout. Also, obviously, we want to use "pipeline script from scm", and it's really crazy if we cant. Thanks again for any feedback. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53477) Ensure the client marks itself at the latest update level even if no updates were applied
Title: Message Title R. Tyler Croy commented on JENKINS-53477 Re: Ensure the client marks itself at the latest update level even if no updates were applied So the problem is more of an oversight on my part. The client's basically never tell the backend what update level they're currently at. The UL set in the dashboard is really whatever they got when they originally started. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39988) Support Build Management Tools - Thresholding
Title: Message Title Arslan javaid edited a comment on JENKINS-39988 Re: Support Build Management Tools - Thresholding when this will be available? Any progress? Furthermore, if no one is working on it. I would love to work on this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53477) Ensure the client marks itself at the latest update level even if no updates were applied
Title: Message Title R. Tyler Croy started work on JENKINS-53477 Change By: R. Tyler Croy Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53477) Ensure the client marks itself at the latest update level even if no updates were applied
Title: Message Title R. Tyler Croy stopped work on JENKINS-53477 Change By: R. Tyler Croy Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53477) Ensure the client marks itself at the latest update level even if no updates were applied
Title: Message Title R. Tyler Croy started work on JENKINS-53477 Change By: R. Tyler Croy Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53110) Incorporate the version of the backend container into the homepage
Title: Message Title R. Tyler Croy updated JENKINS-53110 Jenkins / JENKINS-53110 Incorporate the version of the backend container into the homepage Change By: R. Tyler Croy Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53109) Store version information inside of the container
Title: Message Title R. Tyler Croy updated JENKINS-53109 Jenkins / JENKINS-53109 Store version information inside of the container Change By: R. Tyler Croy Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53510) Nested podTemplate doesn't work correctly with yaml
Title: Message Title Carlos Sanchez commented on JENKINS-53510 Re: Nested podTemplate doesn't work correctly with yaml The yaml is never merged, expected Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53510) Nested podTemplate doesn't work correctly with yaml
Title: Message Title Henrique Barcellos created an issue Jenkins / JENKINS-53510 Nested podTemplate doesn't work correctly with yaml Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2018-09-11 16:35 Priority: Minor Reporter: Henrique Barcellos Nested podTemplate doesn't work as expected with yaml in the latest version of jenkins and kubernetes plugin. Pod is created with the images that are only defined in the most inner podTemplate. Seems it is not merging pods correctly when yaml is used. Using containers instead of yaml on podTemplate works correctly. Add Comment
[JIRA] (JENKINS-39988) Support Build Management Tools - Thresholding
Title: Message Title Arslan javaid commented on JENKINS-39988 Re: Support Build Management Tools - Thresholding when this will be available? Any progress? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53509) Job created inside a view inside a folder does not give the option to add the job to the view
Title: Message Title Bill Bagdon created an issue Jenkins / JENKINS-53509 Job created inside a view inside a folder does not give the option to add the job to the view Issue Type: Bug Assignee: Devin Nusbaum Components: cloudbees-folder-plugin, core Created: 2018-09-11 16:05 Environment: Jenkins 2.121.3 Cloudbees Folders Plugin 6.5.1 Priority: Minor Reporter: Bill Bagdon Typically when creating a new job inside a view, the URL for the "New Job" button will be: JENKINS_HOME/view//newJob Inside a folder the URL becomes: JENKINS_HOME/job//newJob The expectation would be that a view inside that folder would have the "New Job" button point to: JENKINS_HOME/job//view//newJob However, it continues to use: JENKINS_HOME/job//newJob Add Comment
[JIRA] (JENKINS-42192) permissive-security-script plugin should not log full stacktrace
Title: Message Title Alexander Komarov commented on JENKINS-42192 Re: permissive-security-script plugin should not log full stacktrace I'm still seeing this today with plugin version 0.3 and Jenkins 2.141 : Sep 11, 2018 8:51:24 AM INFO org.jenkinsci.plugins.permissivescriptsecurity.PermissiveWhitelist$Mode$2 act Unsecure signature found: staticMethod org.jenkinsci.plugins.workflow.cps.Safepoint safepoint org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use staticMethod org.jenkinsci.plugins.workflow.cps.Safepoint safepoint No matter how many times I've approved this signature in scriptApproval, this still keeps appearing. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53110) Incorporate the version of the backend container into the homepage
Title: Message Title R. Tyler Croy updated JENKINS-53110 Jenkins / JENKINS-53110 Incorporate the version of the backend container into the homepage Change By: R. Tyler Croy Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53109) Store version information inside of the container
Title: Message Title R. Tyler Croy updated JENKINS-53109 Jenkins / JENKINS-53109 Store version information inside of the container Change By: R. Tyler Croy Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53508) new User API tooling not available to plugins.
Title: Message Title James Nord created an issue Jenkins / JENKINS-53508 new User API tooling not available to plugins. Issue Type: Improvement Assignee: Unassigned Components: core Created: 2018-09-11 15:54 Priority: Minor Reporter: James Nord The new APIToken system is not available for plugins to hook into as they can not create tokens that they control as ApiTokenStore.addToken is private. a possible use case is: replicating tokens from a central system to masters for ease of administration (think using the same token on all Jenkins in your system) Add Comment
[JIRA] (JENKINS-53507) it is possible to create two API tokens with the same name.
Title: Message Title James Nord created an issue Jenkins / JENKINS-53507 it is possible to create two API tokens with the same name. Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-09-11 15:47 Priority: Minor Reporter: James Nord It is possible with the new token system to create 2 tokens with the same name. This causes harm for any code trying to identify a token and take some action for a user as all the user is able to see is the name (and not the token) Either the tokens should be displayed with their UUID or you must not be able to create tokens with duplicate names. Add Comment
[JIRA] (JENKINS-39154) Can not edit Pipeline script - text not visible on Configure Page
Title: Message Title Jesse Glick commented on JENKINS-39154 Re: Can not edit Pipeline script - text not visible on Configure Page Most plugins keep changelogs in the wiki, some keep a changelog in Git, but you should always be able to find the canonical page from the plugins.jenkins.io permalink: https://plugins.jenkins.io/workflow-cps → https://wiki.jenkins.io/display/JENKINS/Pipeline+Groovy+Plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39154) Can not edit Pipeline script - text not visible on Configure Page
Title: Message Title Sergey Avseyev commented on JENKINS-39154 Re: Can not edit Pipeline script - text not visible on Configure Page Jesse Glick is there change log for workflow-cps plugin? I don't see anything attached to the SCM tags, nor the changes file in the source repository. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33596) Disable DNSMultiCast & UDPBroadcastThread by default
Title: Message Title R. Tyler Croy assigned an issue to R. Tyler Croy Jenkins / JENKINS-33596 Disable DNSMultiCast & UDPBroadcastThread by default Change By: R. Tyler Croy Assignee: Keith Zantow R. Tyler Croy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33596) Disable DNSMultiCast & UDPBroadcastThread by default
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-33596 Disable DNSMultiCast & UDPBroadcastThread by default Change By: R. Tyler Croy Sprint: Evergreen - Milestone 1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52320) Be able to skip only the plugins selection Wizard but not the security setup
Title: Message Title R. Tyler Croy closed an issue as Done Jenkins / JENKINS-52320 Be able to skip only the plugins selection Wizard but not the security setup Change By: R. Tyler Croy Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51059) Ensure that seeds are idempotent
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-51059 Ensure that seeds are idempotent Change By: R. Tyler Croy Sprint: Evergreen - Milestone 1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39154) Can not edit Pipeline script - text not visible on Configure Page
Title: Message Title Jesse Glick commented on JENKINS-39154 Re: Can not edit Pipeline script - text not visible on Configure Page “Pipeline 2.5” is meaningless. Possibly you are looking at the version of the workflow-aggregator plugin, which does nothing and can simply be uninstalled. This issue is about the workflow-cps plugin (current version 2.55), and perhaps its dependencies. Make sure you are running all plugin updates before reporting an issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39154) Can not edit Pipeline script - text not visible on Configure Page
Title: Message Title Sergey Avseyev commented on JENKINS-39154 Re: Can not edit Pipeline script - text not visible on Configure Page Jenkins ver. 2.121.3 with Pipeline 2.5 is also broken It says "Module load failure: Please verify that the plugin 'jquery-detached' is installed, and that it registers a module named 'jqueryui1'" in jira console Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53110) Incorporate the version of the backend container into the homepage
Title: Message Title R. Tyler Croy started work on JENKINS-53110 Change By: R. Tyler Croy Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53345) The evergreen UI constantly redirects to http:/// instead of http://:8080
Title: Message Title R. Tyler Croy resolved as Fixed Jenkins / JENKINS-53345 The evergreen UI constantly redirects to http:/// instead of http://:8080 Change By: R. Tyler Croy Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53109) Store version information inside of the container
Title: Message Title R. Tyler Croy started work on JENKINS-53109 Change By: R. Tyler Croy Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53040) Allow tainting an Update via Git revert
Title: Message Title R. Tyler Croy updated JENKINS-53040 Jenkins / JENKINS-53040 Allow tainting an Update via Git revert Change By: R. Tyler Croy Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53140) Intermittent Random Stage Failures - No Changes Detected - Parallel Stages
Title: Message Title jerry wiltse commented on JENKINS-53140 Re: Intermittent Random Stage Failures - No Changes Detected - Parallel Stages Also of note, I've discovered that we'll never really be able to use: skip_default_checkout() as any part of a workaround because then we don't get SVN_REVISION_1 and SVN_REPOSITORY_URL environment variable which we require. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53503) More test coverage for Snapshotter.git()
Title: Message Title R. Tyler Croy commented on JENKINS-53503 Re: More test coverage for Snapshotter.git() I was most interested in testing some of the error branches in git() fwi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52227) Cannot Connect to a Git repository using ssh
Title: Message Title zentarim zentarim commented on JENKINS-52227 Re: Cannot Connect to a Git repository using ssh Hi all! Got the same problem with last clean docker image jenkinsci/blueocean (7df0299d5d7b). I suppose, clean docker image shouldn't has problem with .gitconfig or something else. This case i using local SSH git repo (URL: ssh://git@127.0.0.1). Error log in attachement (err.log): Thanks in advance! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52227) Cannot Connect to a Git repository using ssh
Title: Message Title zentarim zentarim updated an issue Jenkins / JENKINS-52227 Cannot Connect to a Git repository using ssh Change By: zentarim zentarim Attachment: err.log Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41660) JIRA Issue linking in build Changelog doesn't work
Title: Message Title Andreas Kühle updated an issue Jenkins / JENKINS-41660 JIRA Issue linking in build Changelog doesn't work Change By: Andreas Kühle Environment: Jenkins 2.19.4 /2.121.2 Jira-Plugin 2.0.2/2.3 /3.0.0 JIRA-Version 7.2.3Subversion-Server 1.8.9Subversion Plug-in 2.7.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41660) JIRA Issue linking in build Changelog doesn't work
Title: Message Title Andreas Kühle commented on JENKINS-41660 Re: JIRA Issue linking in build Changelog doesn't work Any update on this?? I'm facing the same issue using Jenkins 2.121.2, Jira Plugin 3.0.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-4816) Allow for grepping console output
Title: Message Title Ethan Spoelstra commented on JENKINS-4816 Re: Allow for grepping console output Dallas Clement The email-ext plugin allows you to select a portion of the failed build log to include in an email, and you can also attach the entire log if you so desire. One thing to note is that adding colorized output via the Ansi colors plugin can greatly expand the size of your logs vs uncolored, so if you have that turned on you may not be able to attach complete logs without using the "compress and attach build.log" option. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53506) Update all installed plugins to latest version
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53506 Update all installed plugins to latest version Issue Type: Bug Assignee: R. Tyler Croy Components: evergreen Created: 2018-09-11 10:53 Labels: evergreen Priority: Critical Reporter: Baptiste Mathus problem statement Currently, the plugins that are only transitive dependencies in essentials.yaml and ingest.json can be chosen on older versions. This leads, for instance, to generating warning or error logs that have actually been fixed already, sometimes long ago. This is very easy to fix, we just have to declare all transitive dependencies directly under the spec.plugins node in essentials.yaml, but I'm a bit reluctant to do that: we would lose a bit the main plugins we do depend on and want installed, and the ones we only put there to force a specific version (and that we do not really care about if it had to be removed, say). Expected behavior Evergreen installed plugins should (strive to be) always be latest. So that we do not see error logs or behaviors in production that are already fixed in the given plugin.
[JIRA] (JENKINS-53247) Support JCasC in Config File Provider Plugin
Title: Message Title Nicolas De Loof commented on JENKINS-53247 Re: Support JCasC in Config File Provider Plugin see https://github.com/jenkinsci/config-file-provider-plugin/pull/54 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53280) add BasicSSHUserPrivateKey support
Title: Message Title James Nord closed an issue as Fixed Jenkins / JENKINS-53280 add BasicSSHUserPrivateKey support Change By: James Nord Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53280) add BasicSSHUserPrivateKey support
Title: Message Title James Nord updated JENKINS-53280 Jenkins / JENKINS-53280 add BasicSSHUserPrivateKey support Change By: James Nord Status: Fixed but Unreleased Resolved Released As: kubernetes-credentials-provider-0.10 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53194) InfluxDB error failed to collect data after updates
Title: Message Title Aleksi Simell commented on JENKINS-53194 Re: InfluxDB error failed to collect data after updates Grzegorz Dziegielewski Marco Jacob Joe Bob Does this error occur only on a Windows slave? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52058) Provide report filename as variable to Groovy parser
Title: Message Title Ulli Hafner commented on JENKINS-52058 Re: Provide report filename as variable to Groovy parser Yes, I understand that this feature makes sense in your case. I think this requires changes in the UI as well, so this cannot be implemented in the Groovy parser component. I think such a feature needs to be implemented in Java (e.g. as a new plug-in that depends on the warnings plugin). The DRY parser does something similar. It creates issues that have references to other source code (the duplications). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53247) Support JCasC in Config File Provider Plugin
Title: Message Title Nicolas De Loof commented on JENKINS-53247 Re: Support JCasC in Config File Provider Plugin Unfortunately as GlobalConfigFiles is not extending GlobalConfiguration there's no way for CasC to discover this component and use it as a candidate for yaml configuration. And ConfigFilesManagement isn't just a link to a valid Descriptor, it owns a dedicated UI. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53280) add BasicSSHUserPrivateKey support
Title: Message Title James Nord updated JENKINS-53280 Jenkins / JENKINS-53280 add BasicSSHUserPrivateKey support Change By: James Nord Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48167) Support gerrit trigger configuration in pipeline syntax
Title: Message Title Sunny Donnie commented on JENKINS-48167 Re: Support gerrit trigger configuration in pipeline syntax Hi All, Where can I find the documentation/sytax for gerrit configuration for pipleline? I want to enable the silent mode for gerrit trigger in pipeline! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53505) Remove Restriction on DownloadSettings
Title: Message Title Antonio Muñiz started work on JENKINS-53505 Change By: Antonio Muñiz Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53505) Remove Restriction on DownloadSettings
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-53505 Remove Restriction on DownloadSettings Issue Type: Task Assignee: Antonio Muñiz Components: core Created: 2018-09-11 08:46 Priority: Minor Reporter: Antonio Muñiz jenkins.model.DownloadSettings is Restricted, however: It is using the Symbol annotation which means it is used externally The information held by the extension is potentially useful for other extensions working with user data. In my use case, I need to read useBrowser to be able replicate that in another Jenkins instance. Add Comment
[JIRA] (JENKINS-53184) Plugins and Core versions are redacted when they have 4 groups of digits
Title: Message Title Evaristo Gutierrez updated JENKINS-53184 Jenkins / JENKINS-53184 Plugins and Core versions are redacted when they have 4 groups of digits Change By: Evaristo Gutierrez Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44141) Define a resource pool
Title: Message Title Xavier Dury commented on JENKINS-44141 Re: Define a resource pool My ideal poolable/lockable resources plugin would look like this: Be able to define separate resources Each resource can contain parameters (host, port, path, database parameters...) that can be retrieved at runtime in the pipeline Resources can belong to a group/pool: when you ask for one resource from the group/pool, you get the first free one With such a plugin, I could define a 'farm' of integration testing servers where each resource/server would contain parameters like host, linked db settings... Before running integration tests, I could ask for one free server instance from the pool/farm, extract the needed parameters (host for selenium, db settings so my tests can fill/clean/assert the db content...), run my tests, then release that instance. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53504) Add a link/way to back to Jenkins from the embedded docs
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53504 Add a link/way to back to Jenkins from the embedded docs Issue Type: Task Assignee: R. Tyler Croy Components: evergreen Created: 2018-09-11 08:16 Priority: Trivial Reporter: Baptiste Mathus As I was testing https://github.com/jenkins-infra/evergreen/pull/235/files and the fact /pluginManager was correctly unreachable, I was redirected as expected to .../evergreen/docs/#managing-plugins. Then, I was lazily looking for somewhere to click to "go back" to Jenkins, and saw there was no link. I think it would be nice to have for instance the usual "Jenkins" link on the top left to back to Jenkins root. Workaround: just use the back button of the browser. Add Comment
[JIRA] (JENKINS-51938) After updating jenkins....its show this warning to me..... [WARNING] Attempt to (de-)serialize anonymous class hudson.maven.reporters.SurefireArchiver$2; see: https://jenkins.io
Title: Message Title jm rg commented on JENKINS-51938 Re: After updating jenkinsits show this warning to me. [WARNING] Attempt to (de-)serialize anonymous class hudson.maven.reporters.SurefireArchiver$2; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ what can i do now? +1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31803) Pipeline support for TFS plugin
Title: Message Title Andrew Gray commented on JENKINS-31803 Re: Pipeline support for TFS plugin Hi Kellie Jos, Hope you are well. Are you able to provide an update regarding applying a TFS label from a declarative pipeline? What is the syntax? I understand it has been under investigation since 21st February 2018. Regards, Andrew Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
