[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Amir Barkal commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub Liam Newman Not really sure how to reproduce this - can you post instructions? We’re using Multibranch pipeline repository with GitHub branch source configured to build PRs, branches and tags. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.23042.1557466141245%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Amir Barkal edited a comment on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub Suffering from the same issue here.Jenkins core 2.164.1GitHub branch source 2. 4.2 5 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Amir Barkal commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub Suffering from the same issue here. Jenkins core 2.164.1 GitHub branch source 2.4.2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41392) disableConcurrentBuilds should take an optional boolean parameter that defaults to "true"
Title: Message Title
Amir Barkal commented on JENKINS-41392
Re: disableConcurrentBuilds should take an optional boolean parameter that defaults to "true"
Joining Op's request, our use case is very similar: Using the same Jenkinsfile for different jobs with declarative syntax. This can be implemented by either having the options{} block accept a when{} clause, or (preferably) by having all the options support configurable parameters. IMO this ticket should be reopened with a definition of done like Op's subject.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52900) Invalid refspec in pull request. Doesn't check for changes in origin branch
Title: Message Title
Amir Barkal edited a comment on JENKINS-52900
Re: Invalid refspec in pull request. Doesn't check for changes in origin branch
Same problem here with jenkins core version 2.150.Our use case is setting up a nightly job that can auto-discover newly created branches and trigger builds only if there were SCM changes. I thought I can achieve this by:1. Create a multi-branch pipeline job that has the "suppress auto SCM triggering" = on (To disable merge/push web hooks)2. Enable the "Scan periodically if not otherwise run"(To add/remove new/deleted branches)3. Add {quote} " triggers { pollSCM('H 22 * * *') } {quote} " to the pipeline JenkinsfileUnfortunately I'm getting the same behavior reported by OP. Very annoying...
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52900) Invalid refspec in pull request. Doesn't check for changes in origin branch
Title: Message Title
Amir Barkal edited a comment on JENKINS-52900
Re: Invalid refspec in pull request. Doesn't check for changes in origin branch
Same problem here with jenkins core version 2.150. Our use case is setting up a nightly job that can auto-discover newly created branches and trigger builds only if there were SCM changes. I thought I can achieve this by:1. Create a multi-branch pipeline job that has the "suppress auto SCM triggering" = on (To disable merge/push web hooks)2. Enable the "Scan periodically if not otherwise run"(To add/remove new/deleted branches)3. Add {quote}triggers { pollSCM('H 22 * * *') }{quote} to the pipeline JenkinsfileUnfortunately I'm getting the same behavior reported by OP. Very annoying...
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52900) Invalid refspec in pull request. Doesn't check for changes in origin branch
Title: Message Title
Amir Barkal edited a comment on JENKINS-52900
Re: Invalid refspec in pull request. Doesn't check for changes in origin branch
Same problem here with jenkins core version 2.150.Our use case is setting up a nightly job that can auto-discover newly created branches and trigger builds only if there were SCM changes. I thought I can achieve this by:1. Create a multi-branch pipeline job that has the "suppress auto SCM triggering" = on (To disable merge/push web hooks) 2. Enable the "Scan periodically if not otherwise run"(To add/remove new/deleted branches) 3. Add "triggers { pollSCM('H 22 * * *') }" to the pipeline JenkinsfileUnfortunately I'm getting the same behavior reported by OP. Very annoying...
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52900) Invalid refspec in pull request. Doesn't check for changes in origin branch
Title: Message Title Amir Barkal commented on JENKINS-52900 Re: Invalid refspec in pull request. Doesn't check for changes in origin branch Same problem here with jenkins core version 2.150. Very annoying... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49707) Auto retry for elastic agents after channel closure
Title: Message Title
Amir Barkal edited a comment on JENKINS-49707
Re: Auto retry for elastic agents after channel closure
The problem is Jenkins not aborting / cancelling / stopping / whatever the build when the agent is terminated in the middle of a build.There's an infinite loop that's easy to reproduce:1. Start Jenkins slave with remoting jnlp and give it a label jar :{code}java -jar agent.jar -jnlpUrl "http://jenkins:8080/computer/agent1/slave-agent.jnlp" -secret 123{code}2. Run the following pipeline:{code}node('agent1') {sh('sleep 1') }{code}3. Kill the agent (Ctrl+C)4. Jenkins output in job console log:{code}Started by user adminReplayed #23Running as adminRunning in Durability level: MAX_SURVIVABILITY[Pipeline] nodeRunning on agent1-805fa9fd in /workspace/Pipeline-1[Pipeline] {[Pipeline] sh[Pipeline-1] Running shell script+ sleep 1Cannot contact agent-805fa9fd: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from 2163fbb04240.jenkins/172.20.0.3:43902 failed. The channel is closing down or has closed down{code} [^threadDump.txt] System info:Jenkins ver. 2.138Durable Task: 1.25What I would like is a way to configure a maximum timeout for the Jenkins master to wait for the agent to respond, and then just abort the build. It's absolutely unacceptable that builds will hang due to dead agents.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49707) Auto retry for elastic agents after channel closure
Title: Message Title
Amir Barkal edited a comment on JENKINS-49707
Re: Auto retry for elastic agents after channel closure
The problem is Jenkins not aborting / cancelling / stopping / whatever the build when the agent is terminated in the middle of a build.There's an infinite loop that's easy to reproduce:1. Start Jenkins slave with remoting jnlp and give it a label:{code}java -jar agent.jar -jnlpUrl "http://jenkins:8080/computer/agent1/slave-agent.jnlp" -secret 123{code}2. Run the following pipeline:{code}node('agent1') {sh('sleep 1') }{code}3. Kill the agent (Ctrl+C)4. Jenkins output in job console log:{code}Started by user adminReplayed #23Running as adminRunning in Durability level: MAX_SURVIVABILITY[Pipeline] nodeRunning on agent1-805fa9fd in /workspace/Pipeline-1[Pipeline] {[Pipeline] sh[Pipeline-1] Running shell script+ sleep 1Cannot contact agent-805fa9fd: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from 2163fbb04240.jenkins/172.20.0.3:43902 failed. The channel is closing down or has closed down{code} [^threadDump.txt] System info:Jenkins ver. 2.138Durable Task: 1.25 What I would like is a way to configure a maximum timeout for the Jenkins master to wait for the agent to respond, and then just abort the build. It's absolutely unacceptable that builds will hang due to dead agents.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49707) Auto retry for elastic agents after channel closure
Title: Message Title
Amir Barkal edited a comment on JENKINS-49707
Re: Auto retry for elastic agents after channel closure
The problem is Jenkins not aborting / cancelling / stopping / whatever the build when the agent is terminated in the middle of a build.There's an infinite loop that's easy to reproduce:1. Start Jenkins slave with remoting jnlp and give it a label:{code}java -jar agent.jar -jnlpUrl "http://jenkins:8080/computer/ jnlp1 agent1 /slave-agent.jnlp" -secret 123{code}2. Run the following pipeline:{code}node('agent1') {sh('sleep 1') }{code}3. Kill the agent (Ctrl+C)4. Jenkins output in job console log:{code}Started by user adminReplayed #23Running as adminRunning in Durability level: MAX_SURVIVABILITY[Pipeline] nodeRunning on agent1-805fa9fd in /workspace/Pipeline-1[Pipeline] {[Pipeline] sh[Pipeline-1] Running shell script+ sleep 1Cannot contact agent-805fa9fd: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from 2163fbb04240.jenkins/172.20.0.3:43902 failed. The channel is closing down or has closed down{code} [^threadDump.txt] System info:Jenkins ver. 2.138Durable Task: 1.25
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49707) Auto retry for elastic agents after channel closure
Title: Message Title
Amir Barkal commented on JENKINS-49707
Re: Auto retry for elastic agents after channel closure
The problem is Jenkins not aborting / cancelling / stopping / whatever the build when the agent is terminated in the middle of a build. There's an infinite loop that's easy to reproduce: 1. Start Jenkins slave with remoting jnlp and give it a label:
java -jar agent.jar -jnlpUrl "http://jenkins:8080/computer/jnlp1/slave-agent.jnlp" -secret 123
2. Run the following pipeline:
node('agent1') {
sh('sleep 1')
}
3. Kill the agent (Ctrl+C) 4. Jenkins output in job console log:
Started by user admin
Replayed #23
Running as admin
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] node
Running on agent1-805fa9fd in /workspace/Pipeline-1
[Pipeline] {
[Pipeline] sh
[Pipeline-1] Running shell script
+ sleep 1
Cannot contact agent-805fa9fd: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from 2163fbb04240.jenkins/172.20.0.3:43902 failed. The channel is closing down or has closed down
threadDump.txt System info: Jenkins ver. 2.138 Durable Task: 1.25
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-49707) Auto retry for elastic agents after channel closure
Title: Message Title Amir Barkal updated an issue Jenkins / JENKINS-49707 Auto retry for elastic agents after channel closure Change By: Amir Barkal Attachment: threadDump.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-50559) Authorization Folder property for Multibranch jobs
Title: Message Title Amir Barkal commented on JENKINS-50559 Re: Authorization Folder property for Multibranch jobs Any progress on this one? I have a very basic use case requiring this feature: Store and sync job definitions from scm (GitHub for example) using jobDSL syntax. Currently this seems to be impossible. For the jobDSL() step to work without forcing an administrator to approve changes manually, you need to run the jobDSL in sandbox mode. Sandbox mode works only when you configure a job to run as a specific user. Unfortunately the Authorize Project Plugin does not seem to support Multi-Branch pipeline job definition. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51928) Timeout is caught by the most internal try-catch, but should be caught by the try-catch that surrounds the timeout step
Title: Message Title
Amir Barkal commented on JENKINS-51928
Re: Timeout is caught by the most internal try-catch, but should be caught by the try-catch that surrounds the timeout step
Another simple reproduction of the timeout() step not throwing an exception:
node() {
try {
timeout(time: 3 as Integer, unit: 'SECONDS') {
int result = sh(returnStatus: true, script:'sleep 5')
}
}
catch(e) {
println "TIMEOUT" // Will never get here
throw e
}
}
Env details: Jenkins 2.138 workflow-basic-steps 2.9
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40839) pipeline timeout doesn't kill the job
Title: Message Title
Amir Barkal edited a comment on JENKINS-40839
Re: pipeline timeout doesn't kill the job
Another simple reproduction of the timeout() step not throwing an exception: {code :java }node() { try { timeout(time: 3 as Integer, unit: 'SECONDS') { int result = sh(returnStatus: true, script:'sleep 5') }}catch(e) { println "TIMEOUT" // Will never get here throw e }}{code} Env details:Jenkins [2.138|https://jenkins.io/]workflow-basic-steps 2.9
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40839) pipeline timeout doesn't kill the job
Title: Message Title
Amir Barkal edited a comment on JENKINS-40839
Re: pipeline timeout doesn't kill the job
Another simple reproduction of the timeout() step not throwing an exception:{code}node() { try { timeout(time: 3 as Integer, unit: 'SECONDS') { int result = sh(returnStatus: true, script:'sleep 5')} } catch(e) { println "TIMEOUT" // Will never get here throw e }}{code} Env details:Jenkins [2.138|https://jenkins.io/]workflow-basic-steps 2.9
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40839) pipeline timeout doesn't kill the job
Title: Message Title
Amir Barkal edited a comment on JENKINS-40839
Re: pipeline timeout doesn't kill the job
Another simple reproduction of the timeout() step not throwing an exception:{code}node() { try { timeout(time: 3 as Integer, unit: 'SECONDS') { int result = sh(returnStatus: true, script:'sleep 5') }}catch(e) { println "TIMEOUT" // Will never get here throw e }}{code} Env details:Jenkins [2.138|https://jenkins.io/]workflow-basic-steps 2.9
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40839) pipeline timeout doesn't kill the job
Title: Message Title
Amir Barkal edited a comment on JENKINS-40839
Re: pipeline timeout doesn't kill the job
Another simple reproduction of the timeout() step not throwing an exception: { quote code } node() { try{ {quote} {quote} timeout(time : 3 as Integer, unit: 'SECONDS') { int result = sh(returnStatus: true, script:'sleep 5') }} catch(e) { {quote} {quote} println "TIMEOUT" // will Will never get here ! throw e } } { quote code } Env details:Jenkins [2.138|https://jenkins.io/]workflow-basic-steps 2.9
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40839) pipeline timeout doesn't kill the job
Title: Message Title
Amir Barkal edited a comment on JENKINS-40839
Re: pipeline timeout doesn't kill the job
Another simple reproduction of the timeout() step not throwing an exception: {quote}node() { try { timeout(time: 3 as Integer, unit: 'SECONDS') {quote} {quote} int result = sh timeout ( returnStatus time }} catch(e) { {quote} Unknown macro: \ { quote} println "TIMEOUT" // will never get here! throw e }} {quote} Env details:Jenkins [2.138|https://jenkins.io/]workflow-basic-steps 2.9
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40839) pipeline timeout doesn't kill the job
Title: Message Title
Amir Barkal edited a comment on JENKINS-40839
Re: pipeline timeout doesn't kill the job
Another simple reproduction of the timeout() step not throwing an exception: {quote}node() { try { timeout(time: 3 as Integer, unit: 'SECONDS') { int result = sh(returnStatus : true, script: 'sleep 5') } }catch(e) { Unknown macro: \{ println "TIMEOUT" // will never get here! throw e }}{quote} Env details:Jenkins [2.138|https://jenkins.io/]workflow-basic-steps 2.9
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40839) pipeline timeout doesn't kill the job
Title: Message Title
Amir Barkal commented on JENKINS-40839
Re: pipeline timeout doesn't kill the job
Another simple reproduction of the timeout() step not throwing an exception:
node() { try { timeout(time: 3 as Integer, unit: 'SECONDS')
Unknown macro: { int result = sh(returnStatus}
} catch(e)
Unknown macro: { println "TIMEOUT" // will never get here! throw e }
}
Env details: Jenkins 2.138 workflow-basic-steps 2.9
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39838) CHANGE_ variables are missing
Title: Message Title Amir Barkal edited a comment on JENKINS-39838 Re: CHANGE_ variables are missing When configuring a multibranch pipeline repository to detect Pull Requests from GitHub, I get only the following CHANGE_* env variables populated properly :CHANGE_AUTHORCHANGE_AUTHOR_DISPLAY_NAMECHANGE_BRANCHCHANGE_IDCHANGE_TARGETCHANGE_TITLECHANGE_URL The +* CHANGE_AUTHOR_EMAIL *+ var is critically missing from this list, which is paramount to alert users about regressions in their pull requests. Environment:Jenkins ver. 2.128 GitHub Branch Source Plugin 2.3.6 (latest)Pipeline: Multibranch 2.19 (latest) Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39838) CHANGE_ variables are missing
Title: Message Title Amir Barkal commented on JENKINS-39838 Re: CHANGE_ variables are missing When configuring a multibranch pipeline repository to detect Pull Requests from GitHub, I get only the following CHANGE_* env variables populated: CHANGE_AUTHOR CHANGE_AUTHOR_DISPLAY_NAME CHANGE_BRANCH CHANGE_ID CHANGE_TARGET CHANGE_TITLE CHANGE_URL The CHANGE_AUTHOR_EMAIL var is critically missing from this list, which is paramount to alert users about regressions in their pull requests. Environment: Jenkins ver. 2.128 GitHub Branch Source Plugin 2.3.6 (latest) Pipeline: Multibranch 2.19 (latest) Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title
Amir Barkal edited a comment on JENKINS-50867
Re: SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Suffering from the same issue with s3FindFiles pipeline step. After an plugin upgrade (email-ext) + Jenkins restart, problem solved.Why update email-ext? Because it depends on "analysis-core-plugin" which was found to be using the org.xml.sax.driver, so I though I'd give it a refresh. I have a feeling that just a Jenkins restart is enough. By anyway this is not acceptable and very non-deterministic behavior. {code :java }java.lang.ClassNotFoundException: org.apache.xerces.parsers.SAXParser at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:565) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.xml.sax.helpers.NewInstance.newInstance(NewInstance.java:82) at org.xml.sax.helpers.XMLReaderFactory.loadClass(XMLReaderFactory.java:228)Caused: org.xml.sax.SAXException: SAX2 driver class org.apache.xerces.parsers.SAXParser not foundjava.lang.ClassNotFoundException: org.apache.xerces.parsers.SAXParser at org.xml.sax.helpers.XMLReaderFactory.loadClass(XMLReaderFactory.java:230) at org.xml.sax.helpers.XMLReaderFactory.createXMLReader(XMLReaderFactory.java:191) at com.amazonaws.services.s3.model.transform.XmlResponsesSaxParser.(XmlResponsesSaxParser.java:115)Caused: com.amazonaws.SdkClientException: Couldn't initialize a SAX driver to create an XMLReader at com.amazonaws.services.s3.model.transform.XmlResponsesSaxParser.(XmlResponsesSaxParser.java:118) at com.amazonaws.services.s3.model.transform.Unmarshallers$ListObjectsUnmarshaller.unmarshall(Unmarshallers.java:69) at com.amazonaws.services.s3.model.transform.Unmarshallers$ListObjectsUnmarshaller.unmarshall(Unmarshallers.java:59) at com.amazonaws.services.s3.internal.S3XmlResponseHandler.handle(S3XmlResponseHandler.java:62) at com.amazonaws.services.s3.internal.S3XmlResponseHandler.handle(S3XmlResponseHandler.java:31) at com.amazonaws.http.response.AwsResponseHandlerAdapter.handle(AwsResponseHandlerAdapter.java:70) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleResponse(AmazonHttpClient.java:1554) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1272) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1056) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:743) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:717) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:699) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:667) at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:649) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:513) at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4325) at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4272) at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4266) at com.amazonaws.services.s3.AmazonS3Client.listObjects(AmazonS3Client.java:834) at de.taimos.pipeline.aws.S3FindFilesStep$Execution.run(S3FindFilesStep.java:216) at de.taimos.pipeline.aws.S3FindFilesStep$Execution.run(S3FindFilesStep.java:148) at
[JIRA] (JENKINS-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title
Amir Barkal edited a comment on JENKINS-50867
Re: SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Suffering from the same issue with s3FindFiles pipeline step.After an plugin upgrade (email-ext) + Jenkins restart, problem solved.Why update email-ext? Because it depends on "analysis-core-plugin" which was found to be using the org.xml.sax.driver, so I though I'd give it a refresh. I have a feeling that just a Jenkins restart is enough. By anyway In any case this is not acceptable and very non-deterministic behavior. {code:java}java.lang.ClassNotFoundException: org.apache.xerces.parsers.SAXParser at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:565) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.xml.sax.helpers.NewInstance.newInstance(NewInstance.java:82) at org.xml.sax.helpers.XMLReaderFactory.loadClass(XMLReaderFactory.java:228)Caused: org.xml.sax.SAXException: SAX2 driver class org.apache.xerces.parsers.SAXParser not foundjava.lang.ClassNotFoundException: org.apache.xerces.parsers.SAXParser at org.xml.sax.helpers.XMLReaderFactory.loadClass(XMLReaderFactory.java:230) at org.xml.sax.helpers.XMLReaderFactory.createXMLReader(XMLReaderFactory.java:191) at com.amazonaws.services.s3.model.transform.XmlResponsesSaxParser.(XmlResponsesSaxParser.java:115)Caused: com.amazonaws.SdkClientException: Couldn't initialize a SAX driver to create an XMLReader at com.amazonaws.services.s3.model.transform.XmlResponsesSaxParser.(XmlResponsesSaxParser.java:118) at com.amazonaws.services.s3.model.transform.Unmarshallers$ListObjectsUnmarshaller.unmarshall(Unmarshallers.java:69) at com.amazonaws.services.s3.model.transform.Unmarshallers$ListObjectsUnmarshaller.unmarshall(Unmarshallers.java:59) at com.amazonaws.services.s3.internal.S3XmlResponseHandler.handle(S3XmlResponseHandler.java:62) at com.amazonaws.services.s3.internal.S3XmlResponseHandler.handle(S3XmlResponseHandler.java:31) at com.amazonaws.http.response.AwsResponseHandlerAdapter.handle(AwsResponseHandlerAdapter.java:70) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleResponse(AmazonHttpClient.java:1554) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1272) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1056) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:743) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:717) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:699) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:667) at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:649) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:513) at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4325) at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4272) at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4266) at com.amazonaws.services.s3.AmazonS3Client.listObjects(AmazonS3Client.java:834) at de.taimos.pipeline.aws.S3FindFilesStep$Execution.run(S3FindFilesStep.java:216) at de.taimos.pipeline.aws.S3FindFilesStep$Execution.run(S3FindFilesStep.java:148) at
[JIRA] (JENKINS-51960) ClassNotFoundException: org.apache.xerces.parsers.SAXParser
Title: Message Title Amir Barkal commented on JENKINS-51960 Re: ClassNotFoundException: org.apache.xerces.parsers.SAXParser Same error here with s3FindFiles() pipeline step... Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title Amir Barkal commented on JENKINS-50867 Re: SAX2 driver class org.apache.xerces.parsers.SAXParser not found Suffering from the same issue with s3FindFiles pipeline step. java.lang.ClassNotFoundException: org.apache.xerces.parsers.SAXParser at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:565) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.xml.sax.helpers.NewInstance.newInstance(NewInstance.java:82) at org.xml.sax.helpers.XMLReaderFactory.loadClass(XMLReaderFactory.java:228) Caused: org.xml.sax.SAXException: SAX2 driver class org.apache.xerces.parsers.SAXParser not found java.lang.ClassNotFoundException: org.apache.xerces.parsers.SAXParser at org.xml.sax.helpers.XMLReaderFactory.loadClass(XMLReaderFactory.java:230) at org.xml.sax.helpers.XMLReaderFactory.createXMLReader(XMLReaderFactory.java:191) at com.amazonaws.services.s3.model.transform.XmlResponsesSaxParser.(XmlResponsesSaxParser.java:115) Caused: com.amazonaws.SdkClientException: Couldn't initialize a SAX driver to create an XMLReader at com.amazonaws.services.s3.model.transform.XmlResponsesSaxParser.(XmlResponsesSaxParser.java:118) at com.amazonaws.services.s3.model.transform.Unmarshallers$ListObjectsUnmarshaller.unmarshall(Unmarshallers.java:69) at com.amazonaws.services.s3.model.transform.Unmarshallers$ListObjectsUnmarshaller.unmarshall(Unmarshallers.java:59) at com.amazonaws.services.s3.internal.S3XmlResponseHandler.handle(S3XmlResponseHandler.java:62) at com.amazonaws.services.s3.internal.S3XmlResponseHandler.handle(S3XmlResponseHandler.java:31) at com.amazonaws.http.response.AwsResponseHandlerAdapter.handle(AwsResponseHandlerAdapter.java:70) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleResponse(AmazonHttpClient.java:1554) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1272) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1056) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:743) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:717) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:699) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:667) at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:649) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:513) at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4325) at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4272) at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4266) at com.amazonaws.services.s3.AmazonS3Client.listObjects(AmazonS3Client.java:834) at de.taimos.pipeline.aws.S3FindFilesStep$Execution.run(S3FindFilesStep.java:216) at de.taimos.pipeline.aws.S3FindFilesStep$Execution.run(S3FindFilesStep.java:148) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50) at hudson.security.ACL.impersonate(ACL.java:290) at
[JIRA] (JENKINS-47617) CHANGE_BRANCH no longer reporting branch name, but instead PR
Title: Message Title Amir Barkal commented on JENKINS-47617 Re: CHANGE_BRANCH no longer reporting branch name, but instead PR +1 Another problem this issue is causing happens when you open the pull requests tab, you don't see the name of the branch anymore, you only see the PR number: In blue ocean you see the PR name which is nice, but it would be nicer to also clearly see the branch name of the PR. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47617) CHANGE_BRANCH no longer reporting branch name, but instead PR
Title: Message Title Amir Barkal updated an issue Jenkins / JENKINS-47617 CHANGE_BRANCH no longer reporting branch name, but instead PR Change By: Amir Barkal Attachment: Screenshot from 2018-05-23 16-25-19.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34042) Git exception message is null when using workflow checkout step
Title: Message Title Amir Barkal edited a comment on JENKINS-34042 Re: Git exception message is null when using workflow checkout step (+)1 on this issue.Trying to create a mechanism to alert users when their branch cannot be merged into master, or any other problem with the checkout - but the try-catch block of checkout scm isn't working. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34042) Git exception message is null when using workflow checkout step
Title: Message Title Amir Barkal commented on JENKINS-34042 Re: Git exception message is null when using workflow checkout step (+)1 on this issue. Trying to create a mechanism to alert users when their branch cannot be merged into master, or any other problem with the checkout - but the try-catch block of checkout scm isn't working. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40695) Allow running Pipeline shared library functions on executor
Title: Message Title
Amir Barkal edited a comment on JENKINS-40695
Re: Allow running Pipeline shared library functions on executor
I concur. Here's another use case for this request:When we're developing our CI pipeline, we want to make sure we don't introduce regressions to Jenkins shared libraries, so we have a pipeline that's defined as a gate for our shared library changes. We want to be able to checkout the same library version of the tested branch, and run it for verification. In the below example we want to test have usefulMethod without cluttering that does some linting on our master groovy code inside the shared library repo. The method will fail because it expects the shared library code to be available on "builder1" but the code was checked-out to the Jenkins maser node : . {quote}node("builder1") \{ // This will checkout the shared library into the master node, despite being inside an //explicit node block: lib = library("jenkins-shared-library@$\{env.BRANCH_NAME}") // test that usefulMethod did not break: lib.usefulMethod() }{quote} In order to workaround this we need to checkout the shared library code twice, first time to load the library classes and methods and a second time to bring the code to the current workspace. This of course is not very efficient and puts unnecessary stress on our source control system.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-40695) Allow running Pipeline shared library functions on executor
Title: Message Title
Amir Barkal commented on JENKINS-40695
Re: Allow running Pipeline shared library functions on executor
I concur. Here's another use case for this request: When we're developing our CI pipeline, we want to make sure we don't introduce regressions to Jenkins shared libraries, so we have a pipeline that's defined as a gate for our shared library changes. We want to be able to checkout the same library version of the tested branch, and run it for verification. In the below example we want to test usefulMethod without cluttering our master node:
node("builder1") {
// This will checkout the shared library into the master node, despite being inside an //explicit node block: lib = library("jenkins-shared-library@${env.BRANCH_NAME}")
// test that usefulMethod did not break: lib.usefulMethod() }
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
