[JIRA] (JENKINS-53303) unable to connect to to jenkins on port 8080
Title: Message Title Maneesh Abraham created an issue Jenkins / JENKINS-53303 unable to connect to to jenkins on port 8080 Issue Type: Bug Assignee: Unassigned Components: jenkins-cloudformation Created: 2018-08-29 07:09 Priority: Major Reporter: Maneesh Abraham unable to connect to port 8080 after starting jenkins container whereas it works for port 5 Download metadata.log jenkins@jenkins01-dev2:/logs/tasks$ more Download\ metadata.logjenkins@jenkins01-dev2:/logs/tasks$ more Download\ metadata.logStarted at Wed Aug 29 06:56:03 UTC 2018FATAL: connect timed outjava.net.SocketTimeoutException: connect timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:589) at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:673) at sun.net.NetworkClient.doConnect(NetworkClient.java:175) at sun.net.www.http.HttpClient.openServer(HttpClient.java:463) at sun.net.www.http.HttpClient.openServer(HttpClient.java:558) at sun.net.www.protocol.https.HttpsClient.(HttpsClient.java:264) at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:367) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191) at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1156) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1050) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:177) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1564) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnect
[JIRA] (JENKINS-53303) unable to connect to to jenkins on port 8080
Title: Message Title
Maneesh Abraham commented on JENKINS-53303
Re: unable to connect to to jenkins on port 8080
JENKINS]# docker logs -f 48a616450067ENKINS]# docker logs -f 48a616450067 Running from: /usr/share/jenkins/jenkins.warwebroot: EnvVars.masterEnvVars.get("JENKINS_HOME")Aug 29, 2018 6:53:44 AM org.eclipse.jetty.util.log.Log initializedINFO: Logging initialized @407ms to org.eclipse.jetty.util.log.JavaUtilLogAug 29, 2018 6:53:44 AM winstone.Logger logInternalINFO: Beginning extraction from war fileAug 29, 2018 6:53:44 AM org.eclipse.jetty.server.handler.ContextHandler setContextPathWARNING: Empty contextPathAug 29, 2018 6:53:44 AM org.eclipse.jetty.server.Server doStartINFO: jetty-9.4.z-SNAPSHOT, build timestamp: 2017-11-21T21:27:37Z, git hash: 82b8fb23f757335bb3329d540ce37a2a2615f0a8Aug 29, 2018 6:53:44 AM org.eclipse.jetty.webapp.StandardDescriptorProcessor visitServletINFO: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServletAug 29, 2018 6:53:44 AM org.eclipse.jetty.server.session.DefaultSessionIdManager doStartINFO: DefaultSessionIdManager workerName=node0Aug 29, 2018 6:53:44 AM org.eclipse.jetty.server.session.DefaultSessionIdManager doStartINFO: No SessionScavenger set, using defaultsAug 29, 2018 6:53:44 AM org.eclipse.jetty.server.session.HouseKeeper startScavengingINFO: Scavenging every 60msJenkins home directory: /var/jenkins_home found at: EnvVars.masterEnvVars.get("JENKINS_HOME")Aug 29, 2018 6:53:44 AM org.eclipse.jetty.server.handler.ContextHandler doStartINFO: Started w.@1a4927d6{/,file:///var/jenkins_home/war/,AVAILABLE} {/var/jenkins_home/war}Aug 29, 2018 6:53:45 AM org.eclipse.jetty.server.AbstractConnector doStartINFO: Started ServerConnector@ddaf7f{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}Aug 29, 2018 6:53:45 AM org.eclipse.jetty.server.Server doStartINFO: Started @1269msAug 29, 2018 6:53:45 AM winstone.Logger logInternalINFO: Winstone Servlet Engine v4.0 running: controlPort=disabledAug 29, 2018 6:53:46 AM jenkins.InitReactorRunner$1 onAttainedINFO: Started initializationAug 29, 2018 6:53:46 AM jenkins.InitReactorRunner$1 onAttainedINFO: Listed all pluginsAug 29, 2018 6:53:46 AM jenkins.InitReactorRunner$1 onAttainedINFO: Prepared all pluginsAug 29, 2018 6:53:46 AM jenkins.InitReactorRunner$1 onAttainedINFO: Started all pluginsAug 29, 2018 6:53:46 AM jenkins.InitReactorRunner$1 onAttainedINFO: Augmented all extensionsAug 29, 2018 6:53:47 AM jenkins.InitReactorRunner$1 onAttainedINFO: Loaded all jobsAug 29, 2018 6:53:47 AM hudson.model.AsyncPeriodicWork$1 runINFO: Started Download metadataAug 29, 2018 6:53:47 AM jenkins.util.groovy.GroovyHookScript executeINFO: Executing /var/jenkins_home/init.groovy.d/tcp-slave-agent-port.groovyAug 29, 2018 6:53:47 AM org.springframework.context.support.AbstractApplicationContext prepareRefreshINFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@432b437c: display name [Root WebApplicationContext]; startup date [Wed Aug 29 06:53:47 UTC 2018]; root of context hierarchyAug 29, 2018 6:53:47 AM org.springframework.context.support.AbstractApplicationContext obtainFreshBeanFactoryINFO: Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@432b437c]: org.springframework.beans.factory.support.DefaultListableBeanFactory@65e898f4Aug 29, 2018 6:53:47 AM org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletonsINFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@65e898f4: defining beans [authenticationManager]; root of factory hierarchyAug 29, 2018 6:53:47 AM org.springframework.conte
[JIRA] (JENKINS-53303) unable to connect to to jenkins on port 8080
Title: Message Title Maneesh Abraham commented on JENKINS-53303 Re: unable to connect to to jenkins on port 8080 noticed this issue while running the container from a server, where proxy is used to connect to internet. Works fine when running the container from laptop Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53299) Cloud does not exist: kubernetes
Title: Message Title Carlos Sanchez commented on JENKINS-53299 Re: Cloud does not exist: kubernetes https://github.com/jenkinsci/kubernetes-plugin/#pod-and-container-template-configuration cloud The name of the cloud as defined in Jenkins settings. Defaults to kubernetes Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53299) Cloud does not exist: kubernetes
Title: Message Title Carlos Sanchez resolved as Not A Defect Jenkins / JENKINS-53299 Cloud does not exist: kubernetes Change By: Carlos Sanchez Status: Open Resolved 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-47501) 2 pods are started instead of 1 after update to version 1.1
Title: Message Title Carlos Sanchez reopened an issue Jenkins / JENKINS-47501 2 pods are started instead of 1 after update to version 1.1 Change By: Carlos Sanchez Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53250) Gerrit Trigger plugin compatibility with Jenkins As Code plugin (JEP-201)
Title: Message Title Ewelina Wilkosz assigned an issue to rsandell Jenkins / JENKINS-53250 Gerrit Trigger plugin compatibility with Jenkins As Code plugin (JEP-201) Change By: Ewelina Wilkosz Assignee: Ewelina Wilkosz rsandell Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53250) Gerrit Trigger plugin compatibility with Jenkins As Code plugin (JEP-201)
Title: Message Title Ewelina Wilkosz updated an issue Jenkins / JENKINS-53250 Gerrit Trigger plugin compatibility with Jenkins As Code plugin (JEP-201) Change By: Ewelina Wilkosz Component/s: configuration-as-code-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-49903) Stack Trace Error on Global Configration Tool
Title: Message Title Oleg Nenashev updated JENKINS-49903 No response from the reporter, I assume this is just a Java 9+ issue Jenkins / JENKINS-49903 Stack Trace Error on Global Configration Tool Change By: Oleg Nenashev Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51741) [jep-200] http-request-plugin
Title: Message Title
Klaus Wienert commented on JENKINS-51741
Re: [jep-200] http-request-plugin
We did not use HTTP request module anymore. But we were either not able to reproduce the problem on our systems. The Exception has been gone.
def createIssueUrl = 'https://jira-server/jira/rest/api/2/issue'
def createIssueRequestBody = 'body'
node('linux') {
def responseCreateIssue = httpRequest contentType: 'APPLICATION_JSON', timeout: 30, httpMode: 'POST', requestBody: createIssueRequestBody, url: createIssueUrl
}
Started by user Me
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] node
Running on hv-t-lxidac001 in /home/jenkins/agent/workspace/http-request-plugin-test
[Pipeline] {
[Pipeline] httpRequest
HttpMethod: POST
URL: https://jira-server/jira/rest/api/2/issue
Content-type: application/json
Sending request to url: https://jira-server/jira/rest/api/2/issue
Response Code: HTTP/1.1 400 Bad Request
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
...
I will close this issue. Thanks for your support.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49903) Stack Trace Error on Global Configration Tool
Title: Message Title Oleg Nenashev updated JENKINS-49903 Jenkins / JENKINS-49903 Stack Trace Error on Global Configration Tool Change By: Oleg Nenashev Status: Fixed but Unreleased 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-51741) [jep-200] http-request-plugin
Title: Message Title Klaus Wienert updated JENKINS-51741 Jenkins / JENKINS-51741 [jep-200] http-request-plugin Change By: Klaus Wienert Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51741) [jep-200] http-request-plugin
Title: Message Title Klaus Wienert updated JENKINS-51741 Jenkins / JENKINS-51741 [jep-200] http-request-plugin Change By: Klaus Wienert Status: Fixed but Unreleased 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-53304) Data loss when running on newly pulled version of the evergreen image
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53304 Data loss when running on newly pulled version of the evergreen image Issue Type: Task Assignee: R. Tyler Croy Components: evergreen Created: 2018-08-29 07:38 Labels: evergreen Priority: Blocker Reporter: Baptiste Mathus Issue Reproducer: run Evergreen using the current docs, mounting /evergreen/jenkins/home for data stop the container run a new one builds are lost, registration is redone Expected behavior Builds should not be lost The instance should be registering anew like it's a first startup Tentative cause This comes from mounting /evergreen/jenkins/home instead of /evergreen. Builds are under /evergreen/jenkins/var, keys (including uuid.json) are under /evergreen/keys.
[JIRA] (JENKINS-53304) Data loss when running on newly pulled version of the evergreen image
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-53304 Data loss when running on newly pulled version of the evergreen image Change By: Baptiste Mathus Assignee: R. Tyler Croy Baptiste Mathus Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53304) Data loss when running on newly pulled version of the evergreen image
Title: Message Title Baptiste Mathus started work on JENKINS-53304 Change By: Baptiste Mathus 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-53300) test
Title: Message Title Oleg Nenashev commented on JENKINS-53300 Re: test Please use another Jira for testing. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53304) Data loss when running on newly pulled version of the evergreen image
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-53304
Data loss when running on newly pulled version of the evergreen image
Change By:
Baptiste Mathus
h3. IssueReproducer:* run Evergreen using the current docs, mounting /evergreen/jenkins/home for data* stop the container* run a new one* builds are lost, registration is redoneh3. Expected behavior* Builds should not be lost* The instance should be registering anew like it's a first startuph3. Tentative causeThis comes from mounting /evergreen/jenkins/home instead of /evergreen. Builds are under {{/evergreen/jenkins/var}}, keys (including {{uuid.json}}) are under {{/evergreen/keys}}. Thanks for [~jglick] for seeing this first.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53304) Data loss when running on newly pulled version of the evergreen image
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-53304
Data loss when running on newly pulled version of the evergreen image
Change By:
Baptiste Mathus
h3. IssueReproducer:* run Evergreen using the current docs, mounting /evergreen/jenkins/home for data* stop the container* run a new one* builds are lost, registration is redoneh3. Expected behavior* Builds should not be lost* The instance should be registering anew like it's a first startuph3. Tentative causeThis comes from mounting /evergreen/jenkins/home instead of /evergreen. Builds are under {{/evergreen/jenkins/var}}, keys (including {{uuid.json}}) are under {{/evergreen/keys}}.Thanks for to [~jglick] for seeing this first.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49720) NVM wrapper hard-coded path
Title: Message Title Pavel Novak commented on JENKINS-49720 Re: NVM wrapper hard-coded path @Tomas Salazar 0.1.6 Thanks, Tom. We will try to check that once I'll find some time Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53305) javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed;
Title: Message Title
Mykola Ulianytskyi created an issue
Jenkins / JENKINS-53305
javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed;
Issue Type:
Bug
Assignee:
Unassigned
Components:
mailer-plugin
Created:
2018-08-29 07:58
Environment:
Docker image jenkins/jenkins:2.121.2
Priority:
Critical
Reporter:
Mykola Ulianytskyi
Hello We use docker image jenkins/jenkins:2.121.2 and sometimes pipelines in Jenkins fails with next exception: {{javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed; }} {{ boundary="=_Part_232_854096954.1535491539067"}} {{ at javax.activation.ObjectDataContentHandler.writeTo(DataHandler.java:896)}} {{ at javax.activation.DataHandler.writeTo(DataHandler.java:317)}} {{ at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyPart.java:1476)}} {{ at javax.mail.internet.MimeMessage.writeTo(MimeMessage.java:1772)}} {{ at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1099)}} Caused: javax.mail.MessagingException: IOException while sending message; {{ nested exception is:}} {{ javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed; }} {{ boundary="=_Part_232_854096954.1535491539067"}} {{ at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1141)}} {{ at javax.mail.Transport.send0(Transport.java:195)}} {{ at javax.mail.Transport.send(Transport.java:124)}} {{ at org.jenkinsci.plugins.workflow.steps.MailStep$MailStepExecution.run(MailStep.java:142)}} {{ at org.jenkinsci.plugins.workflow.steps.MailStep$MailStepExecution.run(MailStep.java:128)}} {{ at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50)}} {{ at hudson.security.ACL.impersonate(
[JIRA] (JENKINS-53002) Resource request in declarative pod template ignored
Title: Message Title Matt Buckland commented on JENKINS-53002 Re: Resource request in declarative pod template ignored By, "not overriding the requests nor limits fields", you mean I'm not overriding them using containerTemplate, yes? That's because for declarative pipelines this is deprecated[1] so I was trying to avoid using that. It does work, however, so that's what I'm using in the end. I understand it's hard to merge all the combinations, but since this is supported for containerTemplate, and since containerTemplate is deprecated, does this then mean that overriding limits will not be supported for declarative pipelines? [1] https://github.com/jenkinsci/kubernetes-plugin#declarative-pipeline Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53304) Data loss when running on newly pulled version of the evergreen image
Title: Message Title Baptiste Mathus commented on JENKINS-53304 Re: Data loss when running on newly pulled version of the evergreen image OK, better. Running from: /evergreen/jenkins/home/jenkins.war [INFO][2018-08-29 08:01:38] Logging initialized @1381ms to org.eclipse.jetty.util.log.JavaUtilLog (from org.eclipse.jetty.util.log.Log initialized) [INFO][2018-08-29 08:01:39] Beginning extraction from war file (from winstone.Logger logInternal) 2018-08-29 08:01:39,108 INFO success: evergreen-client entered RUNNING state, process has stayed up for > than 2 seconds (startsecs) [WARNING][2018-08-29 08:01:39] Empty contextPath (from org.eclipse.jetty.server.handler.ContextHandler setContextPath) [INFO][2018-08-29 08:01:39] jetty-9.4.z-SNAPSHOT; built: 2018-06-05T18:24:03.829Z; git: d5fc0523cfa96bfebfbda19606cad384d772f04c; jvm 1.8.0_171-b11 (from org.eclipse.jetty.server.Server doStart) info: Starting the evergreen-client.. info: Configuring the client to use the endpoint https://evergreen.jenkins.io/ info: Configuring the client for socket.io off https://evergreen.jenkins.io/ info: Registering listener for event: `update created` info: Registering listener for event: `status ping` info: Checking registration status.. info: We have keys and a UUID already Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53305) javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed;
Title: Message Title
Mykola Ulianytskyi updated an issue
Jenkins / JENKINS-53305
javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed;
Change By:
Mykola Ulianytskyi
Hello We use docker image jenkins/jenkins: * Jenkins 2.121.2 and sometimes (official Docker image) * Mailer Plugin 1.21 Sometimes pipelines in Jenkins fails with next exception: { \ {javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed; }} \ {{ boundary="=_Part_232_854096954.1535491539067"}} \ {{ at javax.activation.ObjectDataContentHandler.writeTo(DataHandler.java:896)}} \ {{ at javax.activation.DataHandler.writeTo(DataHandler.java:317)}} \ {{ at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyPart.java:1476)}} \ {{ at javax.mail.internet.MimeMessage.writeTo(MimeMessage.java:1772)}} \ {{ at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1099)}}{{Caused: javax.mail.MessagingException: IOException while sending message;}} \ {{ nested exception is:}} \ {{ javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed; }} \ {{ boundary="=_Part_232_854096954.1535491539067"}} \ {{ at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1141)}} \ {{ at javax.mail.Transport.send0(Transport.java:195)}} \ {{ at javax.mail.Transport.send(Transport.java:124)}} \ {{ at org.jenkinsci.plugins.workflow.steps.MailStep$MailStepExecution.run(MailStep.java:142)}} \ {{ at org.jenkinsci.plugins.workflow.steps.MailStep$MailStepExecution.run(MailStep.java:128)}} \ {{ at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50)}} \ {{ at hudson.security.ACL.impersonate(ACL.java:290)}} \ {{ at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47)}} \ {{ 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)}} Example of pipeline:{{node {}} \ {{ mail(to: "x...@example.com", subject: "test", body: "test")}}{{}}} Settings: * SMTP server: mail.example.com * Default user e-mail suffix: @example.com Restart of Jenkins temporary solve the issue. Please fix the bug.Thank you
[JIRA] (JENKINS-53305) javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed;
Title: Message Title
Mykola Ulianytskyi updated an issue
Jenkins / JENKINS-53305
javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed;
Change By:
Mykola Ulianytskyi
Hello * Jenkins 2.121.2 (official Docker image) * Mailer Plugin 1.21 Sometimes pipelines in Jenkins fails with next exception: {\{ javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed; }} \{{boundary="=_Part_232_854096954.1535491539067" }} \{{ at javax.activation.ObjectDataContentHandler.writeTo(DataHandler.java:896) }} \{{ at javax.activation.DataHandler.writeTo(DataHandler.java:317) }} \{{ at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyPart.java:1476) }} \{{ at javax.mail.internet.MimeMessage.writeTo(MimeMessage.java:1772) }} \{{ at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1099) }} {{ Caused: javax.mail.MessagingException: IOException while sending message; }} \{{ nested exception is: }} \{{ javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed; }} \{{boundary="=_Part_232_854096954.1535491539067" }} \{{ at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1141) }} \{{ at javax.mail.Transport.send0(Transport.java:195) }} \{{ at javax.mail.Transport.send(Transport.java:124) }} \{{ at org.jenkinsci.plugins.workflow.steps.MailStep$MailStepExecution.run(MailStep.java:142) }} \{{ at org.jenkinsci.plugins.workflow.steps.MailStep$MailStepExecution.run(MailStep.java:128) }} \{{ at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50) }} \{{ at hudson.security.ACL.impersonate(ACL.java:290) }} \{{ at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47) }} \{{ 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) }} Example of pipeline:{{node {}} \{{ mail(to: "x...@example.com", subject: "test", body: "test") }} {{}}} Settings: * SMTP server: mail.example.com * Default user e-mail suffix: @example.com Restart of Jenkins temporary solve the issue. Please fix the bug.Thank you
[JIRA] (JENKINS-53285) Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages
Title: Message Title Baptiste Mathus commented on JENKINS-53285 Re: Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages OK, done yesterday through https://github.com/jenkins-infra/evergreen/pull/205/files. Do not see run-condition there BTW, possibly someone just removed it earlier. Spawning a brand new instance just now didn't get run-condition installed at least. But https://github.com/jenkins-infra/evergreen/pull/205/files didn't percolate yet to being consumed by the fleet. Once done, I'll have another look, I think we will just want to have another look at Sentry in a few days to see if/which messages for this still come in (if any). Going to mark this as 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-53285) Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-53285 Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages Change By: Baptiste Mathus Assignee: R. Tyler Croy Baptiste Mathus Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53285) Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages
Title: Message Title Baptiste Mathus resolved as Fixed Jenkins / JENKINS-53285 Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages Change By: Baptiste Mathus Status: Open 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-53306) Support plugin deletion from Essentials.yaml
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53306 Support plugin deletion from Essentials.yaml Issue Type: Task Assignee: R. Tyler Croy Components: evergreen Created: 2018-08-29 08:20 Priority: Major Reporter: Baptiste Mathus Issue We currently support only adding plugins, by enriching essentials.yaml. We cannot remove plugins (or anything). With the recent rebrand, it would have come handy to be able to remove a given plugin. In that case, it was a simple rename. But there could more convoluted cases, with plugin split, a better one to achieve some feature, etc. Expected As Evergreen developers, we want to be able to instruct that a given (set of) plugin(s) be uninstalled to cover our various use cases Add Comment
[JIRA] (JENKINS-53306) Support plugin deletion from Essentials.yaml
Title: Message Title Baptiste Mathus commented on JENKINS-53306 Re: Support plugin deletion from Essentials.yaml Another obvious case is for instance the maven-plugin: right now, for historical reasons, it is installed because pulled in by many plugins. But we filter out its descriptor, hence it's not even visible from the UI. So if some day we were able to break those transitive dependencies, it would be nice to be able to uninstall it seamlessly from instances running out there. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53306) Support plugin deletion from Essentials.yaml
Title: Message Title Baptiste Mathus commented on JENKINS-53306 Re: Support plugin deletion from Essentials.yaml BTW, R. Tyler Croy what are you thoughts about that. Somehow as a followup to our discussioon yesterday, did you mean you think we should actually remove any plugin that is not explictly listed in essentials.yaml, or should we support adding some specific delete field or so? (I guess the former, but better check ) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48912) Regression: empty "host: " header causes "400 Bad Request"
Title: Message Title Victor Ott commented on JENKINS-48912 Re: Regression: empty "host: " header causes "400 Bad Request" Can't wait to see the fix released... This is such a blocker issue for us! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1
Title: Message Title Andreas Sieferlinger assigned an issue to Andreas Sieferlinger Jenkins / JENKINS-48300 Pipeline shell step aborts prematurely with ERROR: script returned exit code -1 Change By: Andreas Sieferlinger Assignee: Jesse Glick Andreas Sieferlinger Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1
Title: Message Title Andreas Sieferlinger assigned an issue to Unassigned Jenkins / JENKINS-48300 Pipeline shell step aborts prematurely with ERROR: script returned exit code -1 Change By: Andreas Sieferlinger Assignee: Andreas Sieferlinger Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1
Title: Message Title Andreas Sieferlinger assigned an issue to Jesse Glick Jenkins / JENKINS-48300 Pipeline shell step aborts prematurely with ERROR: script returned exit code -1 Change By: Andreas Sieferlinger Assignee: Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25858) java.io.IOException: Unexpected termination of the channel
Title: Message Title shraddha Magar commented on JENKINS-25858 Re: java.io.IOException: Unexpected termination of the channel Thanks for your quick reply. Yes. Those logs were from Jenkins side. Actually, slave goes offline for very short time and comes back online immediately. so not able to get the logs from agent. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25858) java.io.IOException: Unexpected termination of the channel
Title: Message Title shraddha Magar edited a comment on JENKINS-25858 Re: java.io.IOException: Unexpected termination of the channel Thanks for your quick reply.Yes. Those logs were from Jenkins side.Actually, slave goes offline for very short time and comes back online immediately. so not able to get the logs from agent. But due to that short time job is getting failed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50338) Groovy closure composition doesn't work properly in scripted pipeline
Title: Message Title Hari Dara commented on JENKINS-50338 Re: Groovy closure composition doesn't work properly in scripted pipeline I hit this same issue trying to use composition after verifying that it worked in script console. There is actually nothing odd about the result, it just stops at the first closure in the chain. This is true even for rightshift composition. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52509) WARNING: Attempt to (de-)serialize anonymous class hudson.plugins.selenium.PluginImpl$1
Title: Message Title Oleg Nenashev commented on JENKINS-52509 Re: WARNING: Attempt to (de-)serialize anonymous class hudson.plugins.selenium.PluginImpl$1 https://github.com/jenkinsci/selenium-plugin/blob/master/src/main/java/hudson/plugins/selenium/PluginImpl.java#L328 . It sounds like an issue to be fixed IMHO. It's a really bad idea to serialize Plugin class instances over the channel Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50338) Groovy closure composition doesn't work properly in scripted pipeline
Title: Message Title Hari Dara commented on JENKINS-50338 Re: Groovy closure composition doesn't work properly in scripted pipeline The composition is implemented by org.codehaus.groovy.runtime.ComposedClosure and I can see that this is the type that gets created, so it may not be a problem with leftshit and rightshift not being implemented. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25858) java.io.IOException: Unexpected termination of the channel
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-25858 Re: java.io.IOException: Unexpected termination of the channel Which SSH Slaves Plugin version do you use? Did you add the `-workDir AGENT_WORK_DIR` parameter to your suffix command configuration to grab the logs? https://github.com/jenkinsci/remoting/blob/master/docs/workDir.md Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53307) Transform o.j.p.g.RemoteGitImpl$CommandInvocationHandler$1 into a non anonymous class
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53307 Transform o.j.p.g.RemoteGitImpl$CommandInvocationHandler$1 into a non anonymous class Issue Type: Task Assignee: Mark Waite Components: git-plugin Created: 2018-08-29 09:45 Labels: evergreen-triggered sentry Priority: Major Reporter: Baptiste Mathus Issue The Git plugin triggers the following warnings currently: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1 in file:/evergreen/jenkins/var/plugins/git-client/WEB-INF/lib/git-client.jar; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ Expected The anonymous class should be extracted to a full blown one so that this warning (and more importantly remoting works as fine as possible) goes away. Thanks!
[JIRA] (JENKINS-53308) [URLTrigger] - plugin does not working with multiple url monitor
Title: Message Title Narendra Jha created an issue Jenkins / JENKINS-53308 [URLTrigger] - plugin does not working with multiple url monitor Issue Type: Bug Assignee: Gregory Boissinot Components: urltrigger-plugin Created: 2018-08-29 09:46 Environment: Jenkins version: Jenkins ver. 2.107.3 Plugin Name: URLTrigger Plug-in Plugin version: 0.41 Labels: URLTrigger Priority: Blocker Reporter: Narendra Jha **[URLTrigger] - plugin does not working if we add multiple monitor url for polling while single url monitor work Jenkins version: Jenkins ver. 2.107.3 Plugin Name: URLTrigger Plug-in Plugin version: 0.41 Add Comment
[JIRA] (JENKINS-53309) Flavor should be pushed into Sentry
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53309 Flavor should be pushed into Sentry Issue Type: Task Assignee: R. Tyler Croy Components: evergreen Created: 2018-08-29 09:52 Labels: evergreen sentry Priority: Minor Reporter: Baptiste Mathus I think it would be very helpful to have directly the flavor pushed with log entries into Sentry. For instance, it would help understand where a message is coming from and capturing context. If something is going wrong, like an EC2 plugin message for a docker-cloud flavor, we would understand it much quicker. (Technically: we do have that information in the DB, from the UUID, but it's not accessible to anyone and would require one more hop each time). Add Comment
[JIRA] (JENKINS-53194) InfluxDB error failed to collect data after updates
Title: Message Title Marco Jacob commented on JENKINS-53194 Re: InfluxDB error failed to collect data after updates We also get this on Windows Jenkins 2.107.2 with InfluxDb Plugin 1.1.8, but not on Solaris with Jenkins 2.107.3 and InfluxDB 1.1.8. Strange. I just stored global Jenkins config and Job config on Windows again to see if this might fix 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-51979) subversion checkout fails with SAXException
Title: Message Title Ivan Fernandez Calvo updated JENKINS-51979 Jenkins / JENKINS-51979 subversion checkout fails with SAXException Change By: Ivan Fernandez Calvo 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-51854) LinkageError while performing UserRequest:hudson.scm.SubversionSCM
Title: Message Title Ivan Fernandez Calvo assigned an issue to Unassigned Jenkins / JENKINS-51854 LinkageError while performing UserRequest:hudson.scm.SubversionSCM Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52596) subversion checkout broken symbolic link as text file
Title: Message Title Ivan Fernandez Calvo assigned an issue to Unassigned Jenkins / JENKINS-52596 subversion checkout broken symbolic link as text file Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51979) subversion checkout fails with SAXException
Title: Message Title Ivan Fernandez Calvo updated JENKINS-51979 Jenkins / JENKINS-51979 subversion checkout fails with SAXException Change By: Ivan Fernandez Calvo Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51979) subversion checkout fails with SAXException
Title: Message Title Ivan Fernandez Calvo assigned an issue to Unassigned Jenkins / JENKINS-51979 subversion checkout fails with SAXException Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51006) Subversion plugin ignores affected paths for multibranch pipeline trigger
Title: Message Title Ivan Fernandez Calvo assigned an issue to Unassigned Jenkins / JENKINS-51006 Subversion plugin ignores affected paths for multibranch pipeline trigger Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51698) Failed to check out svn ....svn: E200030: FULL
Title: Message Title Ivan Fernandez Calvo assigned an issue to Unassigned Jenkins / JENKINS-51698 Failed to check out svn svn: E200030: FULL Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52977) Failed to check repository revision
Title: Message Title Ivan Fernandez Calvo assigned an issue to Unassigned Jenkins / JENKINS-52977 Failed to check repository revision Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50894) Checkout of svn:externals hangs silently
Title: Message Title Ivan Fernandez Calvo assigned an issue to Unassigned Jenkins / JENKINS-50894 Checkout of svn:externals hangs silently Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50503) Jenkins job does not list latest SVN change
Title: Message Title Ivan Fernandez Calvo assigned an issue to Unassigned Jenkins / JENKINS-50503 Jenkins job does not list latest SVN change Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52472) SVN Polling produce sometimes ones more build with no changes
Title: Message Title Ivan Fernandez Calvo assigned an issue to Unassigned Jenkins / JENKINS-52472 SVN Polling produce sometimes ones more build with no changes Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51127) java.io.NotSerializableException: org.tmatesoft.svn.core.auth.SVNPasswordAuthentication
Title: Message Title Ivan Fernandez Calvo assigned an issue to Unassigned Jenkins / JENKINS-51127 java.io.NotSerializableException: org.tmatesoft.svn.core.auth.SVNPasswordAuthentication Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51979) subversion checkout fails with SAXException
Title: Message Title Ivan Fernandez Calvo stopped work on JENKINS-51979 Change By: Ivan Fernandez Calvo 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-53307) Transform anonymous classes sent over remoting into non anonymous classes
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53307 Transform anonymous classes sent over remoting into non anonymous classes Change By: Baptiste Mathus Summary: Transform o.j.p.g.RemoteGitImpl$CommandInvocationHandler$1 anonymous classes sent over remoting into a non anonymous class classes Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53307) Transform anonymous classes sent over remoting into non anonymous classes
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-53307
Transform anonymous classes sent over remoting into non anonymous classes
Change By:
Baptiste Mathus
h3. IssueThe Git plugin triggers the following warnings currently:{noformat}Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1 in file:/evergreen/jenkins/var/plugins/git-client/WEB-INF/lib/git-client.jar; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/{noformat} And{noformat}Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.Git$1 in file:/evergreen/jenkins/var/plugins/git-client/WEB-INF/lib/git-client.jar; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/{noformat} h3. ExpectedThe anonymous class should be extracted to a full blown one so that this warning (and more importantly remoting works as fine as possible) goes away.Thanks!
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49720) NVM wrapper hard-coded path
Title: Message Title Pavel Novak commented on JENKINS-49720 Re: NVM wrapper hard-coded path Hi, so I made some testing. I can see there appeared "Customize NVM Installation Settings", in the job configuration, under that you moved NVM Install URL and added NVM_DIR installation dir. I can confirm, when we use this setting to custom path for node installations (new option), then it works, and the given value is taken But, I tried to configure NVM_DIR in global variables (jenkins global config), and its NOT working I didn't found the way how to define it on global level, maybe, can you advise with this? Thanks in advance, and anyway, thanks for fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50379) Jenkins kills long running sh script with no output
Title: Message Title swarnendu roy commented on JENKINS-50379 Re: Jenkins kills long running sh script with no output Hi Guys, This issue is due to Durable Task Pluggin, In the latest release of Durable task Pluggin 1.25 this has been resolved. reference Link : https://issues.jenkins-ci.org/browse/JENKINS-52881 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46961) Unable to abort job: "Resuming build at [...] after Jenkins restart"
Title: Message Title Eslam ElHusseiny commented on JENKINS-46961 Re: Unable to abort job: "Resuming build at [...] after Jenkins restart" I have the same issue Jenkins ver. 2.140 Pipeline: Groovy/workflow-cps v2.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-47792) Job with in queue with status "pending description" do not start
Title: Message Title Petr Prochazka commented on JENKINS-47792 Re: Job with in queue with status "pending description" do not start It looks like that somebody should fix this issue or remove wrong version from repository: https://updates.jenkins-ci.org/download/plugins/parameterized-trigger/2.35.2/parameterized-trigger.hpi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49597) Scripts not permitted to use staticMethod
Title: Message Title Tobias Richter updated an issue Jenkins / JENKINS-49597 Scripts not permitted to use staticMethod Change By: Tobias Richter Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53147) Rebrand from Essentials to Evergreen
Title: Message Title Baptiste Mathus updated JENKINS-53147 Jenkins / JENKINS-53147 Rebrand from Essentials to Evergreen Change By: Baptiste Mathus 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-53304) Data loss when running on newly pulled version of the evergreen image
Title: Message Title Baptiste Mathus updated JENKINS-53304 Jenkins / JENKINS-53304 Data loss when running on newly pulled version of the evergreen image Change By: Baptiste Mathus 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-52881) durable-task plugin v1.23 kills jobs on Cygwin/MSys agents
Title: Message Title Daniel Beck commented on JENKINS-52881 Re: durable-task plugin v1.23 kills jobs on Cygwin/MSys agents Jesse Glick Is this the same issue as JENKINS-50379? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13709) ClassCast Exception when parsing JUnit surefire reports during website generation
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-13709 ClassCast Exception when parsing JUnit surefire reports during website generation This is neither a problem in dom4j nor a bug in the junit plugin. It is a fundamental design flaw in maven-plugin. If you encounter issues like this, simply run mvn as an external process. Change By: Jesse Glick Component/s: maven-plugin Component/s: junit-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-53194) InfluxDB error failed to collect data after updates
Title: Message Title Grzegorz Dziegielewski commented on JENKINS-53194 Re: InfluxDB error failed to collect data after updates Marco Jacob Do you have same set of plugins installed on both Solaris and Windows? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53310) Documentation: "to retrieve the generated administrator" info is wrong for Mac OS
Title: Message Title vikram vi created an issue Jenkins / JENKINS-53310 Documentation: "to retrieve the generated administrator" info is wrong for Mac OS Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-08-29 11:01 Environment: Mac OS 10.13.5, Jenkins 2.140 Priority: Minor Reporter: vikram vi Steps: Installed jenkins per https://jenkins.io/doc/book/installing/#macos Opened http://localhost:8080 and observed setup wizard As per https://jenkins.io/doc/book/installing/#macos > Once Jenkins is running, consult the log (/var/svc/log/network-http:jenkins.log) Actual Result: This file is not present on Mac OS 4. On installation wizard, there is link which takes to https://wiki.jenkins.io/display/JENKINS/Logging#Logging-MacOSX but here as well var/log/jenkins/jenkins.log is missing on Mac OS Expected Result: 1. Mac OS specific correct path for admin password is needed
[JIRA] (JENKINS-45571) "likely stuck" job is not actually stuck.
Title: Message Title Anna Tikhonova commented on JENKINS-45571 Re: "likely stuck" job is not actually stuck. Devin Nusbaum unfortunately, I don't. I've got a few 1000+ LOC pipelines running continuously. I do not know how to tell with one leaves executors and when. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53311) [Blue Ocean] New sequential stage likes completed when it is executed
Title: Message Title
Denis Zakharov created an issue
Jenkins / JENKINS-53311
[Blue Ocean] New sequential stage likes completed when it is executed
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
jenkinsBug.jpg
Components:
blueocean-plugin
Created:
2018-08-29 11:04
Environment:
Jenkins LTS 2.121.3 Blue ocean 1.8.2
Labels:
windows pipeline
Priority:
Minor
Reporter:
Denis Zakharov
We have a visualisation problem in new "Sequential Stages". Stage likes completed when it is executed. Minimal pipeline example: pipeline { agent any stages { stage('Parallel') { failFast false parallel { stage('Nested B') { stages { stage('Nested B-1') { steps { echo 'Nested A-1' } } stage('Nested B-2') { steps { sleep time: 5, unit: 'MINUTES' } } } } stage('Nested C') { when { _expression_ { false == true } } stages { stage('Nested C-1') { steps { echo 'Nested C-1' } } stage('Nested C-2') { steps { echo 'Nested C-2' } } } } stage('Nested A') { steps { sleep time: 5, unit: 'MINUTES' } } } } } }
[JIRA] (JENKINS-26883) SEVERE: Restarting VM as requested by username
Title: Message Title Victor Martinez commented on JENKINS-26883 Re: SEVERE: Restarting VM as requested by username I'll close this ticket as duplicated by JENKINS-53282. There is already a PR for that particular Jira and therefore I'd prefer to close this ticket on benefits of the other one. Please feel free to reopen it in case you think that ticket is not related with this one. Thanks Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53312) Scheduled builds for Pipeline jobs don't appear in Calendar View
Title: Message Title Sven Schoenung created an issue Jenkins / JENKINS-53312 Scheduled builds for Pipeline jobs don't appear in Calendar View Issue Type: Bug Assignee: Sven Schoenung Components: calendar-view-plugin Created: 2018-08-29 11:06 Priority: Minor Reporter: Sven Schoenung Jobs of type WorkflowJob don't extend AbstractProject and therefore don't have a getTriggers() method. That's why scheduled builds for pipeline jobs don't appear. Plug-in needs to support getting the cron trigger information from the job properties. Originally reported here. Add Comment
[JIRA] (JENKINS-26883) SEVERE: Restarting VM as requested by username
Title: Message Title Victor Martinez updated JENKINS-26883 Jenkins / JENKINS-26883 SEVERE: Restarting VM as requested by username Change By: Victor Martinez Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45571) "likely stuck" job is not actually stuck.
Title: Message Title
Anna Tikhonova edited a comment on JENKINS-45571
Re: "likely stuck" job is not actually stuck.
[~dnusbaum] unfortunately, I don't. I've got a few 1000+ LOC pipelines running continuously. I do not know how to tell with one leaves executors and when. Pipeline build that has such "likelyStuck" executor looks completed on its build page (no progress bars, build status is set). But I still can see a matching OneOffExecutor on master:{code:java} "_class" : "hudson.model.Hudson$MasterComputer", "oneOffExecutors" : [{ "currentExecutable" : {"_class" : "org.jenkinsci.plugins.workflow.job.WorkflowRun","building" : false,// always false for these lost executors"result" : "SUCCESS",// always set to some valid build status != null"url" : "JENKINS/job/PIPELINE/BUILD_NUMBER/" }, "likelyStuck" : false// can be true or false}, ...{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53313) kubernetes-plugin does not honer instance cap
Title: Message Title
Dietmar Scheidl created an issue
Jenkins / JENKINS-53313
kubernetes-plugin does not honer instance cap
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2018-08-29 11:15
Priority:
Critical
Reporter:
Dietmar Scheidl
When requesting lots of slaves (e.g. when used in pipeline parallel), the instance cap of the pod template is not honored. Unit test to reproduce:
@Test
public void testLimit() {
KubernetesCloud cloud = new KubernetesCloud("name");
cloud.setContainerCapStr("100");
PodTemplate podTemplate = new PodTemplate();
podTemplate.setName("test");
podTemplate.setLabel("test");
podTemplate.setInstanceCap(5);
cloud.addTemplate(podTemplate);
Label test = Label.get("test");
assertTrue(cloud.canProvision(test));
Collection plannedNodes = cloud.provision(test, 200);
assertEquals(5, plannedNodes.size());
}
which fails with:
junit.framework.AssertionFailedError:
Expected :5
Actual :200
Both, container cap on cloud and pod instance cap, are not honored.
[JIRA] (JENKINS-53313) kubernetes-plugin does not honor instance cap
Title: Message Title Dietmar Scheidl updated an issue Jenkins / JENKINS-53313 kubernetes-plugin does not honor instance cap Change By: Dietmar Scheidl Summary: kubernetes-plugin does not honer honor instance cap Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42197) Job import plugin refreshes the page after clicking on "Query" button
Title: Message Title omri ifergan commented on JENKINS-42197 Re: Job import plugin refreshes the page after clicking on "Query" button on my station: jenkins 2.121.2 plugin ver 3.0 i get the folowing page without posibility to add remote server: Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42197) Job import plugin refreshes the page after clicking on "Query" button
Title: Message Title omri ifergan edited a comment on JENKINS-42197 Re: Job import plugin refreshes the page after clicking on "Query" button on my station: jenkins 2.121.2plugin ver 3.0 i get the folowing following page without posibility possibility to add remote server: !Screen Shot 2018-08-29 at 14.15.43.png! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53251) Review Sentry issues
Title: Message Title Baptiste Mathus updated JENKINS-53251 Jenkins / JENKINS-53251 Review Sentry issues Change By: Baptiste Mathus 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-53251) Review Sentry issues
Title: Message Title Baptiste Mathus commented on JENKINS-53251 Re: Review Sentry issues This will never be really finished, but I filed a bunch of issues and PRs around. Marked progressively everything as resolved. We will for sure see some issues coming back, but hopefully less and less. Or at least not the same . Currently, for the record, I've marked all issues as 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-53251) Review Sentry issues
Title: Message Title Baptiste Mathus updated JENKINS-53251 Jenkins / JENKINS-53251 Review Sentry issues Change By: Baptiste Mathus 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-43976) Support Gitlab in Blue Ocean
Title: Message Title Marius Gripsgard commented on JENKINS-43976 Re: Support Gitlab in Blue Ocean Any status on this? I would love to have gitlab supported Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52923) Error Signal Description not displayed in Blue Ocean
Title: Message Title Saad Azam commented on JENKINS-52923 Re: Error Signal Description not displayed in Blue Ocean I am facing a similar 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-53313) kubernetes-plugin does not honor instance cap
Title: Message Title Carlos Sanchez commented on JENKINS-53313 Re: kubernetes-plugin does not honor instance cap debug logs? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25858) java.io.IOException: Unexpected termination of the channel
Title: Message Title shraddha Magar commented on JENKINS-25858 Re: java.io.IOException: Unexpected termination of the channel Also I have restarted Jenkins instance then agent which is configured on windows with JNLP got offline and its not coming online, its showing below error. Aug 29, 2018 1:43:04 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among http://x.x.x.x:x/jenkins/ Aug 29, 2018 1:43:04 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping] Aug 29, 2018 1:43:04 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Agent discovery successful Agent address: x.x.x.x Agent port: 37091 Identity: 51:a8:0d:a8:18:dd:db:d8:ea:18:b7:98:da:76:b2:ae Aug 29, 2018 1:43:04 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Handshaking Aug 29, 2018 1:43:04 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to x.x.x.x:37091 Aug 29, 2018 1:43:35 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to x.x.x.x:37091 (retrying:2) java.io.IOException: Failed to connect to x.x.x.x:37091 at org.jenkinsci.remoting.engine.JnlpAgentEndpoint.open(JnlpAgentEndpoint.java:242) at hudson.remoting.Engine.connect(Engine.java:686) at hudson.remoting.Engine.innerRun(Engine.java:547) at hudson.remoting.Engine.run(Engine.java:469) Caused by: java.net.ConnectException: Connection timed out: connect at sun.nio.ch.Net.connect0(Native Method) at sun.nio.ch.Net.connect(Unknown Source) at sun.nio.ch.Net.connect(Unknown Source) at sun.nio.ch.SocketChannelImpl.connect(Unknown Source) at java.nio.channels.SocketChannel.open(Unknown Source) at org.jenkinsci.remoting.engine.JnlpAgentEndpoint.open(JnlpAgentEndpoint.java:203) ... 3 more Could you please help me out please? just replaced master IP with x.x.x.x. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Iss
[JIRA] (JENKINS-25858) java.io.IOException: Unexpected termination of the channel
Title: Message Title shraddha Magar edited a comment on JENKINS-25858 Re: java.io.IOException: Unexpected termination of the channel Also I have restarted Jenkins instance then agent which is configured on windows with JNLP got offline and its not coming online, its showing below error.Aug 29, 2018 1:43:04 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among [http://x.x.x.x:x/jenkins/]Aug 29, 2018 1:43:04 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]Aug 29, 2018 1:43:04 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: Agent discovery successful Agent address: x.x.x.x Agent port: 37091 Identity: 51:a8:0d:a8:18:dd:db:d8:ea:18:b7:98:da:76:b2:aeAug 29, 2018 1:43:04 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: HandshakingAug 29, 2018 1:43:04 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to x.x.x.x:37091Aug 29, 2018 1:43:35 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to x.x.x.x:37091 (retrying:2)java.io.IOException: Failed to connect to x.x.x.x:37091 at org.jenkinsci.remoting.engine.JnlpAgentEndpoint.open(JnlpAgentEndpoint.java:242) at hudson.remoting.Engine.connect(Engine.java:686) at hudson.remoting.Engine.innerRun(Engine.java:547) at hudson.remoting.Engine.run(Engine.java:469)Caused by: java.net.ConnectException: Connection timed out: connect at sun.nio.ch.Net.connect0(Native Method) at sun.nio.ch.Net.connect(Unknown Source) at sun.nio.ch.Net.connect(Unknown Source) at sun.nio.ch.SocketChannelImpl.connect(Unknown Source) at java.nio.channels.SocketChannel.open(Unknown Source) at org.jenkinsci.remoting.engine.JnlpAgentEndpoint.open(JnlpAgentEndpoint.java:203) ... 3 more Could you please help me out please?just replaced master IP with x.x.x.x. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubsc
[JIRA] (JENKINS-53314) how to parameterize default "workspace" folder name, jenkins on Tomcat on windows
Title: Message Title
Muralidhar Ranganathan created an issue
Jenkins / JENKINS-53314
how to parameterize default "workspace" folder name, jenkins on Tomcat on windows
Issue Type:
Task
Assignee:
Oleg Nenashev
Components:
_unsorted
Created:
2018-08-29 12:00
Environment:
Jenkins v2.121.3
Priority:
Minor
Reporter:
Muralidhar Ranganathan
I am using Jenkins on TomCat. I have custom workspace folder set to d:\j which I achieved by setting the variable JENKINS_HOME on Tomcat\conf\context.xml. `` I want to keep my workspace folder name as short as possible, I would like my workspace folder to be D:\J\W. I find the below value D:\J\config.xml, ${JENKINS_HOME}/workspace/${ITEM_FULL_NAME} Can I somehow pass a parameter name like JENKINS_HOME so that I can achieve my required workspace folder name to D:\J\W?
Add Comment
[JIRA] (JENKINS-53315) Timeout step should support a closure to execute prior to killing body
Title: Message Title
Alexander Komarov created an issue
Jenkins / JENKINS-53315
Timeout step should support a closure to execute prior to killing body
Issue Type:
Improvement
Assignee:
Unassigned
Components:
workflow-basic-steps-plugin
Created:
2018-08-29 12:01
Priority:
Minor
Reporter:
Alexander Komarov
Currently, the timeout step simply kills whatever processes were launched during execution of its body, and then throws an exception. This makes it difficult to perform any automated debugging on these processes, since they are killed by the time the user finds out that they are hung (or slow). You can argue that this should be done outside of Jenkins, but, too often, Jenkins is the only place this is visible due to frequency of execution or differences in the environment. Currently:
try {
timeout(time: 1, unit: 'HOURS') {
sh "java IntermittentlySlowProcess"
}
} catch (t) {
//It's too late to, for example, send a "kill -3" to the slow/hung java process
}
What I'd propose (and I'm willing to try to make a PR if this seems reasonable):
timeout(time: 1, unit: 'HOURS', beforeKill: {
sh "killall -3 java" //for example
}) {
sh "java IntermittentlySlowProcess"
}
"beforeKill" can be used for clean shutdown of complex tasks, analysis of problems, etc. Thoughts welcome.
[JIRA] (JENKINS-53315) Timeout step should support a closure to execute prior to killing body
Title: Message Title
Alexander Komarov updated an issue
Jenkins / JENKINS-53315
Timeout step should support a closure to execute prior to killing body
Change By:
Alexander Komarov
Currently, the timeout step simply kills whatever processes were launched during execution of its body, and then throws an exception. This makes it *difficult to perform any automated debugging* on these processes, since they are killed by the time the user finds out that they are hung (or slow). You can argue that this should be done outside of Jenkins, but, too often, Jenkins is the only place this is visible due to frequency of execution or differences in the environment.h3. Currently: {code:java}try { timeout(time: 1, unit: 'HOURS') { sh "java IntermittentlySlowProcess" }} catch (t) { //It's too late to, for example, send a "kill -3" to the slow/hung java process}{code} h3. What I'd propose(and I'm willing to try to make a PR if this seems reasonable):{code:java}timeout(time: 1, unit: 'HOURS', beforeKill: { sh "killall -3 java" //for example}) { sh "java IntermittentlySlowProcess"}{code}The new "beforeKill" closure can be used for clean shutdown of complex tasks, analysis of problems, etc.Thoughts welcome.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issue
[JIRA] (JENKINS-53315) Timeout step should support a closure to execute prior to killing body
Title: Message Title
Alexander Komarov updated an issue
Jenkins / JENKINS-53315
Timeout step should support a closure to execute prior to killing body
Change By:
Alexander Komarov
Currently, the timeout step simply kills whatever processes were launched during execution of its body, and then throws an exception. This makes it *difficult to perform any automated debugging* on these processes, since they are killed by the time the user finds out that they are hung (or slow). You can argue that this should be done outside of Jenkins, but, too often, Jenkins is the only place this is visible due to frequency of execution or differences in the environment.h3. Currently: {code:java}try { timeout(time: 1, unit: 'HOURS') { sh "java IntermittentlySlowProcess" }} catch (t) { //It's too late to, for example, send a "kill -3" to the slow/hung java process}{code} h3. What I'd propose(and I'm willing to try to make a PR if this seems reasonable): {code:java}timeout(time: 1, unit: 'HOURS', beforeKill: { sh "killall -3 java" //for example}) { sh "java IntermittentlySlowProcess"}{code} The new "beforeKill" closure can be used for clean shutdown of complex tasks, analysis of problems, etc.Thoughts welcome.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenk
[JIRA] (JENKINS-53316) Use Jackson 2.8.11 in Declarative
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-53316 Use Jackson 2.8.11 in Declarative Issue Type: Bug Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2018-08-29 12:24 Priority: Major Reporter: Andrew Bayer Finally figured out how to switch us to using the jackson2-api plugin in Declarative rather than the shaded monstrosity I'd been using. Woo! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-53187) Exception when using deleteDir() from pipeline
Title: Message Title Marco Steffan commented on JENKINS-53187 Re: Exception when using deleteDir() from pipeline Thanks for the hint of configurable retry/timeout limits - did not know that. In that case that issue can be closed. I have reported some other issues which all seem to be related. By disabling the AV-Scanner these issues also seem to be resolved (as fas as I can see now) (JENKINS-52416 JENKINS-52404 , JENKINS-52402) Thanks for the support!! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53316) Use Jackson 2.8.11 in Declarative
Title: Message Title Andrew Bayer commented on JENKINS-53316 Re: Use Jackson 2.8.11 in Declarative PR up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/286 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53316) Use Jackson 2.8.11 in Declarative
Title: Message Title Andrew Bayer started work on JENKINS-53316 Change By: Andrew Bayer 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-53316) Use Jackson 2.8.11 in Declarative
Title: Message Title Andrew Bayer updated JENKINS-53316 Jenkins / JENKINS-53316 Use Jackson 2.8.11 in Declarative Change By: Andrew Bayer 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-53306) Support plugin deletion from Essentials.yaml
Title: Message Title Baptiste Mathus commented on JENKINS-53306 Re: Support plugin deletion from Essentials.yaml Seems like Tyler actually filed JENKINS-53256 two days. Going to close this in favor of this older reported 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-53306) Support plugin deletion from Essentials.yaml
Title: Message Title Baptiste Mathus closed an issue as Duplicate Jenkins / JENKINS-53306 Support plugin deletion from Essentials.yaml Change By: Baptiste Mathus Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
