[JIRA] (JENKINS-53691) "Execute script on Matrix" not working after upgraing from 0.18.1 to 1.0.0+
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-53691 "Execute script on Matrix" not working after upgraing from 0.18.1 to 1.0.0+ Change By: Rick Liu Attachment: config-0.17.xml Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194186.153748074.1288.1566954480275%40Atlassian.JIRA.
[JIRA] (JENKINS-53691) "Execute script on Matrix" not working after upgraing from 0.18.1 to 1.0.0+
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-53691 "Execute script on Matrix" not working after upgraing from 0.18.1 to 1.0.0+ Change By: Rick Liu Attachment: config-2.8.1.xml Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194186.153748074.1290.1566954480299%40Atlassian.JIRA.
[JIRA] (JENKINS-56223) Jenkins discard-old-build caused open file handles
Title: Message Title
Rick Liu updated an issue
Jenkins / JENKINS-56223
Jenkins discard-old-build caused open file handles
Change By:
Rick Liu
After Jenkins upgraded from 2.46.2 to 2.138.4 on Jan 5. 2019, I started to see many (deleted) open file handles.Those (deleted) open file handles seem caused by "discard old build" rotate. The "{{builds/.${old-build-number}}}" folder doesn't exist anymore, but when using "{{lsof}}" command to check, it showed up . : {{sudo lsof -a -p $(pgrep -P $(sudo cat /var/run/jenkins/jenkins.pid)) | grep '(deleted)'}} egbq. java34189 jenkins 5199r REG 252,0 1818111 17044616 /var/lib/jenkins/jobs/Projects/jobs/FortiClientEMS/jobs/br_6_Branch_Build/builds/.1394/log (deleted)bq. java34189 jenkins 5200r REG 252,0 1813394 17052273 /var/lib/jenkins/jobs/Projects/jobs/FortiClientEMS/jobs/br_6_Branch_Build/builds/.1388/log (deleted)bq. java34189 jenkins 5201r REG 252,0 1813394 17052273 /var/lib/jenkins/jobs/Projects/jobs/FortiClientEMS/jobs/br_6_Branch_Build/builds/.1388/log (deleted)bq. java34189 jenkins 5212r REG 252,0 1815212 17053470 /var/lib/jenkins/jobs/Projects/jobs/FortiClientEMS/jobs/br_6_Branch_Build/builds/.1398/log (deleted)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you
[JIRA] (JENKINS-56223) Jenkins discard-old-build caused open file handles
Title: Message Title
Rick Liu created an issue
Jenkins / JENKINS-56223
Jenkins discard-old-build caused open file handles
Issue Type:
Bug
Assignee:
nkns165
Attachments:
lsof_deleted.list
Components:
core, discard-old-build-plugin
Created:
2019-02-20 22:53
Environment:
Ubuntu 16.04 Java 1.8.0_191 Jenkins 2.138.4
Priority:
Major
Reporter:
Rick Liu
After Jenkins upgraded from 2.46.2 to 2.138.4 on Jan 5. 2019, I started to see many (deleted) open file handles. Those (deleted) open file handles seem caused by "discard old build" rotate. The "builds/.${old-build-number}" folder doesn't exist anymore, but when using "lsof" command to check, it showed up. sudo lsof -a -p $(pgrep -P $(sudo cat /var/run/jenkins/jenkins.pid)) | grep '(deleted)'
Add Comment
[JIRA] (JENKINS-55780) User property LastGrantedAuthoritiesProperty is not updated when LDAP user is login
Title: Message Title
Rick Liu updated an issue
Jenkins / JENKINS-55780
User property LastGrantedAuthoritiesProperty is not updated when LDAP user is login
Change By:
Rick Liu
When a new user *FIRST-TIME* using LDAP credential to login,Jenkins will create{{*/users//config.xml* file,}}{{and update *LastGrantedAuthoritiesProperty* attribute with the current timestamp:}} {{ }} {{ }} {{ authenticated }} {{ }} {{ *1548376473889* }} {{ }} But any subsequent LDAP login,the *timestamp* of {{*LastGrantedAuthoritiesProperty*}} is not updated anymore.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55780) User property LastGrantedAuthoritiesProperty is not updated when LDAP user is login
Title: Message Title
Rick Liu created an issue
Jenkins / JENKINS-55780
User property LastGrantedAuthoritiesProperty is not updated when LDAP user is login
Issue Type:
Bug
Assignee:
Oleg Nenashev
Components:
core, ldap-plugin, role-strategy-plugin
Created:
2019-01-25 17:54
Environment:
Ubuntu 16.04.5 OpenJDK 1.8.0.191 Jenkins 2.138.4 LDAP plugin 1.20 Role-based Authorization Strategy 2.9.0
Priority:
Major
Reporter:
Rick Liu
When a new user FIRST-TIME using LDAP credential to login, Jenkins will create /users//config.xml file, and update LastGrantedAuthoritiesProperty attribute with the current timestamp: {{ LastGrantedAuthoritiesProperty>}} {{ }} {{ authenticated}} {{ }} {{ 1548376473889}} {{ }} But any subsequent LDAP login, the timestamp of LastGrantedAuthoritiesProperty is not updated anymore.
Add Comment
[JIRA] (JENKINS-38316) Entering, then cancelling, quiet mode causes builds to hang
Title: Message Title Rick Liu commented on JENKINS-38316 Re: Entering, then cancelling, quiet mode causes builds to hang This still happened to Jenkins v*2.138.4* LTS Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52946) Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2
Title: Message Title Rick Liu edited a comment on JENKINS-52946 Re: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2 *Environment:**Ubuntu 16.04 (both master ans slaves)**Jenkins vers: 2.138.4**EnvInject 2.1.6**EnvInject API 1.5* All I did was disconnect the slave and reconnect again.The warning would always show up right before the line "Agent successfully connected and online". Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52946) Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2
Title: Message Title Rick Liu reopened an issue Environment: Ubuntu 16.04 (both master ans slaves) Jenkins vers: 2.138.4 EnvInject 2.1.6 EnvInject API 1.5 Jenkins / JENKINS-52946 Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2 Change By: Rick Liu 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-52946) Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-52946 Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2 Change By: Rick Liu Attachment: Selection_010.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-52946) Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2
Title: Message Title
Rick Liu edited a comment on JENKINS-52946
Re: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2
I still see the warning below in all of my Jenkins slave log:{quote}WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2; see: [https://jenkins.io/redirect/serialization-of-anonymous-classes/]{quote}*Environment:* *Ubuntu 16.04* *Jenkins vers: 2.138.4* *EnvInject 2.1.6* *EnvInject API 1.5* Jenkins slave connection log snippet:{quote}[12/21/18 15:44:08] [SSH] Checking java version of /home/devops/jenkins_robot_slave/jdk/bin/javaCouldn't figure out the Java version of /home/devops/jenkins_robot_slave/jdk/bin/javabash: /home/devops/jenkins_robot_slave/jdk/bin/java: No such file or directory[12/21/18 15:44:08] [SSH] Checking java version of java [12/21/18 15:44:08] [SSH] java -version returned 1.8.0_162. [12/21/18 15:44:08] [SSH] Starting sftp client. [12/21/18 15:44:08] [SSH] Copying latest remoting.jar... [12/21/18 15:44:08] [SSH] Copied 776,265 bytes. Expanded the channel window size to 4MB{color:#172b4d}[12/21/18 15:44:08] [SSH] Starting agent process: cd "/home/devops/jenkins_robot_slave" && java -jar remoting.jar -workDir /home/devops/jenkins_robot_slave {color}Dec 21, 2018 3:44:09 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir INFO: Using /home/devops/jenkins_robot_slave/remoting as a remoting work directory Both error and output logs will be printed to /home/devops/jenkins_robot_slave/remoting <===[JENKINS REMOTING CAPACITY]===>channel started Remoting version: 3.25 This is a Unix agent Evacuated stdout Dec 21, 2018 3:44:18 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2; see:[https://jenkins.io/redirect/serialization-of-anonymous-classes/]Agent successfully connected and online {quote}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-52946) Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2
Title: Message Title
Rick Liu edited a comment on JENKINS-52946
Re: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2
I still see the warning below in all of my Jenkins slave log:{quote}WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2; see: [https://jenkins.io/redirect/serialization-of-anonymous-classes/]{quote}*Environment:* *Ubuntu 16.04* *Jenkins vers: 2.138.4* *EnvInject 2.1.6* *EnvInject API 1.5* Jenkins slave connection log snippet: { { quote} [12/21/18 15:44:08] [SSH] Checking java version of /home/devops/jenkins_robot_slave/jdk/bin/java Couldn't figure out the Java version of /home/devops/jenkins_robot_slave/jdk/bin/java bash: /home/devops/jenkins_robot_slave/jdk/bin/java: No such file or directory [12/21/18 15:44:08] [SSH] Checking java version of java[12/21/18 15:44:08] [SSH] java -version returned 1.8.0_162.[12/21/18 15:44:08] [SSH] Starting sftp client.[12/21/18 15:44:08] [SSH] Copying latest remoting.jar...[12/21/18 15:44:08] [SSH] Copied 776,265 bytes. Expanded the channel window size to 4MB {color:#172b4d} [12/21/18 15:44:08] [SSH] Starting agent process: cd "/home/devops/jenkins_robot_slave" && java -jar remoting.jar -workDir /home/devops/jenkins_robot_slave {color} Dec 21, 2018 3:44:09 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDirINFO: Using /home/devops/jenkins_robot_slave/remoting as a remoting work directoryBoth error and output logs will be printed to /home/devops/jenkins_robot_slave/remoting<===[JENKINS REMOTING CAPACITY]===>channel startedRemoting version: 3.25This is a Unix agentEvacuated stdoutDec 21, 2018 3:44:18 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2; see: }}{{ [https://jenkins.io/redirect/serialization-of-anonymous-classes/] }}{{ Agent successfully connected and online {quote } }
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-52946) Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2
Title: Message Title
Rick Liu edited a comment on JENKINS-52946
Re: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2
I still see the warning below in all of my Jenkins slave log:{quote}WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2; see: [https://jenkins.io/redirect/serialization-of-anonymous-classes/]{quote} * Environment: * * Ubuntu 16.04 * * Jenkins vers: 2.138.4 * * EnvInject 2.1.6 * * EnvInject API 1.5 * Jenkins slave connection log snippet:{{[12/21/18 15:44:08] [SSH] Checking java version of /home/devops/jenkins_robot_slave/jdk/bin/java }}{{ Couldn't figure out the Java version of /home/devops/jenkins_robot_slave/jdk/bin/java }}{{ bash: /home/devops/jenkins_robot_slave/jdk/bin/java: No such file or directory }}{{ [12/21/18 15:44:08] [SSH] Checking java version of java }}{{ [12/21/18 15:44:08] [SSH] java -version returned 1.8.0_162. }}{{ [12/21/18 15:44:08] [SSH] Starting sftp client. }}{{ [12/21/18 15:44:08] [SSH] Copying latest remoting.jar... }}{{ [12/21/18 15:44:08] [SSH] Copied 776,265 bytes. }}{{ Expanded the channel window size to 4MB }}{{ [12/21/18 15:44:08] [SSH] Starting agent process: cd "/home/devops/jenkins_robot_slave" && java -jar remoting.jar -workDir /home/devops/jenkins_robot_slave }}{{ Dec 21, 2018 3:44:09 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir }}{{ INFO: Using /home/devops/jenkins_robot_slave/remoting as a remoting work directory }}{{ Both error and output logs will be printed to /home/devops/jenkins_robot_slave/remoting }}{{ <===[JENKINS REMOTING CAPACITY]===>channel started }}{{ Remoting version: 3.25 }}{{ This is a Unix agent }}{{ Evacuated stdout }}{{ Dec 21, 2018 3:44:18 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warn }}{{ WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2; see: }}{{ [https://jenkins.io/redirect/serialization-of-anonymous-classes/]}} {{ Agent successfully connected and online}}
Add Comment
This message was sent by Atlassian Jira
[JIRA] (JENKINS-52946) Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2
Title: Message Title
Rick Liu edited a comment on JENKINS-52946
Re: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2
I still see the warning below in all of my Jenkins slave log:{quote}WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2; see: [https://jenkins.io/redirect/serialization-of-anonymous-classes/]{quote}*Environment:* *Ubuntu 16.04* *Jenkins vers: 2.138.4* *EnvInject 2.1.6* *EnvInject API 1.5* Jenkins slave connection log snippet:{{[12/21/18 15:44:08] [SSH] Checking java version of /home/devops/jenkins_robot_slave/jdk/bin/java Couldn't figure out the Java version of /home/devops/jenkins_robot_slave/jdk/bin/java bash: /home/devops/jenkins_robot_slave/jdk/bin/java: No such file or directory [12/21/18 15:44:08] [SSH] Checking java version of java [12/21/18 15:44:08] [SSH] java -version returned 1.8.0_162. [12/21/18 15:44:08] [SSH] Starting sftp client. [12/21/18 15:44:08] [SSH] Copying latest remoting.jar... [12/21/18 15:44:08] [SSH] Copied 776,265 bytes. Expanded the channel window size to 4MB [12/21/18 15:44:08] [SSH] Starting agent process: cd "/home/devops/jenkins_robot_slave" && java -jar remoting.jar -workDir /home/devops/jenkins_robot_slave Dec 21, 2018 3:44:09 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir INFO: Using /home/devops/jenkins_robot_slave/remoting as a remoting work directory Both error and output logs will be printed to /home/devops/jenkins_robot_slave/remoting <===[JENKINS REMOTING CAPACITY]===>channel started Remoting version: 3.25 This is a Unix agent Evacuated stdout Dec 21, 2018 3:44:18 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2; see: }}{{[https://jenkins.io/redirect/serialization-of-anonymous-classes/]}}{{Agent successfully connected and online}}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-52946) Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2
Title: Message Title
Rick Liu commented on JENKINS-52946
Re: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2
I still see the warning below in all of my Jenkins slave log:
WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/
Environment: Ubuntu 16.04 Jenkins vers: 2.138.4 EnvInject 2.1.6 EnvInject API 1.5 Jenkins slave connection log snippet: [12/21/18 15:44:08] [SSH] Checking java version of /home/devops/jenkins_robot_slave/jdk/bin/java {{ Couldn't figure out the Java version of /home/devops/jenkins_robot_slave/jdk/bin/java}} {{ bash: /home/devops/jenkins_robot_slave/jdk/bin/java: No such file or directory}}[12/21/18 15:44:08] [SSH] Checking java version of java {{ [12/21/18 15:44:08] [SSH] java -version returned 1.8.0_162.}} {{ [12/21/18 15:44:08] [SSH] Starting sftp client.}} {{ [12/21/18 15:44:08] [SSH] Copying latest remoting.jar...}} {{ [12/21/18 15:44:08] [SSH] Copied 776,265 bytes.}} {{ Expanded the channel window size to 4MB}} {{ [12/21/18 15:44:08] [SSH] Starting agent process: cd "/home/devops/jenkins_robot_slave" && java -jar remoting.jar -workDir /home/devops/jenkins_robot_slave}} {{ Dec 21, 2018 3:44:09 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir}} {{ INFO: Using /home/devops/jenkins_robot_slave/remoting as a remoting work directory}} {{ Both error and output logs will be printed to /home/devops/jenkins_robot_slave/remoting}} {{ <===[JENKINS REMOTING CAPACITY]===>channel started}} {{ Remoting version: 3.25}} {{ This is a Unix agent}} {{ Evacuated stdout}} {{ Dec 21, 2018 3:44:18 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warn}} {{ WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/}} {{ Agent successfully connected and online}}
Add Comment
[JIRA] (JENKINS-54149) Ability to add HTML text on login page
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-54149 Ability to add HTML text on login page Change By: Rick Liu Currently, when Global Security Access Control is enable,the login page displays only "User" and "Password" textbox textfield form.It'd be great if "Configure System" or "Configure Global Security"could provide a section for Admin user to add HTML-style text,which would show up on the login page before user login. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54149) Ability to add HTML text on login page
Title: Message Title Rick Liu created an issue Jenkins / JENKINS-54149 Ability to add HTML text on login page Issue Type: New Feature Assignee: Unassigned Components: core Created: 2018-10-18 18:38 Environment: Jenkins 2.121.3 Priority: Major Reporter: Rick Liu Currently, when Global Security Access Control is enable, the login page displays only "User" and "Password" textbox form. It'd be great if "Configure System" or "Configure Global Security" could provide a section for Admin user to add HTML-style text, which would show up on the login page before user login. Add Comment
[JIRA] (JENKINS-44958) File handle leaks in *.log after hard kill
Title: Message Title Rick Liu commented on JENKINS-44958 Re: File handle leaks in *.log after hard kill What's JEP-210? Is it this JEP-210: http://openjdk.java.net/jeps/210 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51734) sessionTimeout isn't be honoured
Title: Message Title Rick Liu edited a comment on JENKINS-51734 Re: sessionTimeout isn't be honoured I see the same issue after upgrading to Jenkins core v.2.121.3.On Ubuntu 16.04.4 LTS under /etd/default/jenkins,I have set JENKINS_ARG with --sessionTimeout=1440, which is 24 hours.But with a logged-in Jenkins page openned in a browser tab (both Firefox and Chrome),after about 1 hour inactivity to the tab,the session would be gone.Any click to the page would be redirected to the login page to login again. this --sessionEvicition setting should be added to the document page. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51734) sessionTimeout isn't be honoured
Title: Message Title Rick Liu commented on JENKINS-51734 Re: sessionTimeout isn't be honoured I see the same issue after upgrading to Jenkins core v.2.121.3. On Ubuntu 16.04.4 LTS under /etd/default/jenkins, I have set JENKINS_ARG with --sessionTimeout=1440, which is 24 hours. But with a logged-in Jenkins page openned in a browser tab (both Firefox and Chrome), after about 1 hour inactivity to the tab, the session would be gone. Any click to the page would be redirected to the login page to login again. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53880) Build step trigger pipeline job hangs when master node set to zero executors
Title: Message Title
Rick Liu updated an issue
Jenkins / JENKINS-53880
Build step trigger pipeline job hangs when master node set to zero executors
Change By:
Rick Liu
When master node is set to zero exectuors,a matrix job triggers a pipeline job (with blocking) doesn't work.From Matrix job console, it would show:{{Waiting for the completion of "".}}But the pipeline job doesn't start and it doesn't have queue jobs either.It's just like the trigger was not sent,but the matrix job is waiting for return indefinitely.Only from Jenkins master jenkins.log, you can see:bq. Oct 02, 2018 1:27:29 PM hudson.model.Executor resetWorkUnitbq. WARNING: Executor #-1 for master grabbed hudson.model.queue.WorkUnit@2cbaff74[work=PIPELINE_JOB] from queue but master went off-line before the task's worker thread started. No termination trace available. Jenkins either should queued the job to wait for master executors to be available,or should returns trigger error back to the matrix jobinstead of letting the job wait for the return indefinitely.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
[JIRA] (JENKINS-53880) Build step trigger pipeline job hangs when master node set to zero executors
Title: Message Title Rick Liu created an issue Jenkins / JENKINS-53880 Build step trigger pipeline job hangs when master node set to zero executors Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-10-02 20:57 Environment: Ubuntu 16.04 Jenkins Core v2.121.3 Priority: Minor Reporter: Rick Liu When master node is set to zero exectuors, a matrix job triggers a pipeline job (with blocking) doesn't work. From Matrix job console, it would show: Waiting for the completion of "". But the pipeline job doesn't start and it doesn't have queue jobs either. It's just like the trigger was not sent, but the matrix job is waiting for return indefinitely. Only from Jenkins master jenkins.log, you can see: Oct 02, 2018 1:27:29 PM hudson.model.Executor resetWorkUnit WARNING: Executor #-1 for master grabbed hudson.model.queue.WorkUnit@2cbaff74[work=PIPELINE_JOB] from queue but master went off-line before the task's worker thread started. No termination trace available.
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title
Rick Liu edited a comment on JENKINS-52810
Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Job Jenkins server:Jenkins core. v.2.121.3Parameterized Remote Trigger Plugin v.3.0.6Remote Jenkins server:Jenkins core. v.2.121.3I still see this error from the job console:[Pipeline] triggerRemoteJob Parameterized Remote Trigger Configuration:- job: https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test - auth:'Credentials Authentication' as user ' devops xx ' (Credentials ID ' a14c5dae-94e0-4b12-991b-6f7d8620120e x ')- parameters: [BUILD=5098, LABEL=ECO_130206, ENV=SMOKE_PRODUCTION]- blockBuildUntilComplete: false- connectionRetryLimit:5fail to accquire lock because of timeout, skip locking...Triggering parameterized remote job 'https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test' Using job-level defined 'Credentials Authentication' as user ' devops xx ' (Credentials ID 'x')Triggering remote job now.fail to accquire lock because of timeout, skip locking...CSRF protection is disabled on the remote server.fail to accquire lock because of timeout, skip locking...Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #1 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #2 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #3 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #4 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #5 out of 5ERROR: Remote build failed with 'ExceedRetryLimitException' for the following reason: 'Max number of connection retries have been exeeded.'.Pipeline code:triggerRemoteJob auth: CredentialsAuth(credentials: 'x'), blockBuildUntilComplete: false, job: 'https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test', parameters: """BUILD=${build}\nLABEL=ECO_${ECO_ID}\nENV=SMOKE_PRODUCTION""", pollInterval: 300
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title
Rick Liu edited a comment on JENKINS-52810
Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Job Jenkins server:Jenkins core. v.2.121.3Parameterized Remote Trigger Plugin v.3.0.6Remote Jenkins server:Jenkins core. v.2.121.3I still see this error from the job console:[Pipeline] triggerRemoteJob Parameterized Remote Trigger Configuration:- job: https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test - auth:'Credentials Authentication' as user 'devops' (Credentials ID 'a14c5dae-94e0-4b12-991b-6f7d8620120e')- parameters: [BUILD=5098, LABEL=ECO_130206, ENV=SMOKE_PRODUCTION]- blockBuildUntilComplete: false- connectionRetryLimit:5fail to accquire lock because of timeout, skip locking...Triggering parameterized remote job 'https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test' Using job-level defined 'Credentials Authentication' as user 'devops' (Credentials ID ' a14c5dae-94e0-4b12-991b-6f7d8620120e x ')Triggering remote job now.fail to accquire lock because of timeout, skip locking...CSRF protection is disabled on the remote server.fail to accquire lock because of timeout, skip locking...Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #1 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #2 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #3 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #4 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #5 out of 5ERROR: Remote build failed with 'ExceedRetryLimitException' for the following reason: 'Max number of connection retries have been exeeded.'.Pipeline code:triggerRemoteJob auth: CredentialsAuth(credentials: 'x'), blockBuildUntilComplete: false, job: 'https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test', parameters: """BUILD=${build}\nLABEL=ECO_${ECO_ID}\nENV=SMOKE_PRODUCTION""", pollInterval: 300
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title
Rick Liu edited a comment on JENKINS-52810
Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Job Jenkins server:Jenkins core. v.2.121.3 Parameterized Remote Trigger Plugin v.3.0.6 Remote Jenkins server:Jenkins core. v.2.121.3 I still see this error from the job console:[Pipeline] triggerRemoteJob Parameterized Remote Trigger Configuration:- job: https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test - auth:'Credentials Authentication' as user 'devops' (Credentials ID 'a14c5dae-94e0-4b12-991b-6f7d8620120e')- parameters: [BUILD=5098, LABEL=ECO_130206, ENV=SMOKE_PRODUCTION]- blockBuildUntilComplete: false- connectionRetryLimit:5fail to accquire lock because of timeout, skip locking...Triggering parameterized remote job 'https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test' Using job-level defined 'Credentials Authentication' as user 'devops' (Credentials ID 'a14c5dae-94e0-4b12-991b-6f7d8620120e')Triggering remote job now.fail to accquire lock because of timeout, skip locking...CSRF protection is disabled on the remote server.fail to accquire lock because of timeout, skip locking...Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #1 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #2 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #3 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #4 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #5 out of 5ERROR: Remote build failed with 'ExceedRetryLimitException' for the following reason: 'Max number of connection retries have been exeeded.'.Pipeline code:triggerRemoteJob auth: CredentialsAuth(credentials: 'x'), blockBuildUntilComplete: false, job: 'https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test', parameters: """BUILD=${build}\nLABEL=ECO_${ECO_ID}\nENV=SMOKE_PRODUCTION""", pollInterval: 300
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title
Rick Liu edited a comment on JENKINS-52810
Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Jenkins core. v.2.121.3 Parameterized Remote Trigger Plugin v.3.0.6I still see this error from the job console:[Pipeline] triggerRemoteJob Parameterized Remote Trigger Configuration:- job: https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test - auth:'Credentials Authentication' as user 'devops' (Credentials ID 'a14c5dae-94e0-4b12-991b-6f7d8620120e')- parameters: [BUILD=5098, LABEL=ECO_130206, ENV=SMOKE_PRODUCTION]- blockBuildUntilComplete: false- connectionRetryLimit:5fail to accquire lock because of timeout, skip locking...Triggering parameterized remote job 'https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test' Using job-level defined 'Credentials Authentication' as user 'devops' (Credentials ID 'a14c5dae-94e0-4b12-991b-6f7d8620120e')Triggering remote job now.fail to accquire lock because of timeout, skip locking...CSRF protection is disabled on the remote server.fail to accquire lock because of timeout, skip locking...Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #1 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #2 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #3 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #4 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #5 out of 5ERROR: Remote build failed with 'ExceedRetryLimitException' for the following reason: 'Max number of connection retries have been exeeded.'. Pipeline code:triggerRemoteJob auth: CredentialsAuth(credentials: 'x'), blockBuildUntilComplete: false, job: 'https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test', parameters: """BUILD=${build}\nLABEL=ECO_${ECO_ID}\nENV=SMOKE_PRODUCTION""", pollInterval: 300
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title Rick Liu commented on JENKINS-52810 Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins I'm sorry. I was trying to re-open the issue, but clicked the wrong butto to resolve the issue. Could anyone help me to revert my action? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title Rick Liu updated JENKINS-52810 Jenkins / JENKINS-52810 Parameterized Remote Trigger Plugin is not triggering job in remote jenkins Change By: Rick Liu Status: Resolved In 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-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title Rick Liu updated JENKINS-52810 Jenkins / JENKINS-52810 Parameterized Remote Trigger Plugin is not triggering job in remote jenkins Change By: Rick Liu 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-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title
Rick Liu edited a comment on JENKINS-52810
Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Jenkins core. v.2.121.3 Parameterized Remote Trigger Plugin v.3.0.6I still see this error from the job console:[Pipeline] {[Pipeline] triggerRemoteJob Parameterized Remote Trigger Configuration:- job: https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test - auth:'Credentials Authentication' as user 'devops' (Credentials ID 'a14c5dae-94e0-4b12-991b-6f7d8620120e')- parameters: [BUILD=5098, LABEL=ECO_130206, ENV=SMOKE_PRODUCTION]- blockBuildUntilComplete: false- connectionRetryLimit:5fail to accquire lock because of timeout, skip locking...Triggering parameterized remote job 'https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test' Using job-level defined 'Credentials Authentication' as user 'devops' (Credentials ID 'a14c5dae-94e0-4b12-991b-6f7d8620120e')Triggering remote job now.fail to accquire lock because of timeout, skip locking...CSRF protection is disabled on the remote server.fail to accquire lock because of timeout, skip locking...Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #1 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #2 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #3 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #4 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #5 out of 5ERROR: Remote build failed with 'ExceedRetryLimitException' for the following reason: 'Max number of connection retries have been exeeded.'. [Pipeline] }
Add Comment
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title
Rick Liu edited a comment on JENKINS-52810
Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Jenkins core. v.2.121.3 Parameterized Remote Trigger Plugin v.3.0.6I still see this error from the job console: {quote} [Pipeline] {[Pipeline] triggerRemoteJob Parameterized Remote Trigger Configuration:- job: https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test - auth:'Credentials Authentication' as user 'devops' (Credentials ID 'a14c5dae-94e0-4b12-991b-6f7d8620120e')- parameters: [BUILD=5098, LABEL=ECO_130206, ENV=SMOKE_PRODUCTION]- blockBuildUntilComplete: false- connectionRetryLimit:5fail to accquire lock because of timeout, skip locking...Triggering parameterized remote job 'https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test' Using job-level defined 'Credentials Authentication' as user 'devops' (Credentials ID 'a14c5dae-94e0-4b12-991b-6f7d8620120e')Triggering remote job now.fail to accquire lock because of timeout, skip locking...CSRF protection is disabled on the remote server.fail to accquire lock because of timeout, skip locking...Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #1 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #2 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #3 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #4 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #5 out of 5ERROR: Remote build failed with 'ExceedRetryLimitException' for the following reason: 'Max number of connection retries have been exeeded.'.[Pipeline] } {quote}
Add Comment
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title
Rick Liu edited a comment on JENKINS-52810
Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Jenkins core. v.2.121.3Parameterized Remote Trigger Plugin v.3.0.6I still see this error from the job console:{ { quote} [Pipeline] {[Pipeline] triggerRemoteJob Parameterized Remote Trigger Configuration:- job: https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test - auth:'Credentials Authentication' as user 'devops' (Credentials ID 'a14c5dae-94e0-4b12-991b-6f7d8620120e')- parameters: [BUILD=5098, LABEL=ECO_130206, ENV=SMOKE_PRODUCTION]- blockBuildUntilComplete: false- connectionRetryLimit:5fail to accquire lock because of timeout, skip locking...Triggering parameterized remote job 'https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test' Using job-level defined 'Credentials Authentication' as user 'devops' (Credentials ID 'a14c5dae-94e0-4b12-991b-6f7d8620120e')Triggering remote job now.fail to accquire lock because of timeout, skip locking...CSRF protection is disabled on the remote server.fail to accquire lock because of timeout, skip locking...Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #1 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #2 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #3 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #4 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #5 out of 5ERROR: Remote build failed with 'ExceedRetryLimitException' for the following reason: 'Max number of connection retries have been exeeded.'.[Pipeline] } {quote } }
Add Comment
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title
Rick Liu commented on JENKINS-52810
Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Jenkins core. v.2.121.3 Parameterized Remote Trigger Plugin v.3.0.6 I still see this error from the job console: {{[Pipeline] { [Pipeline] triggerRemoteJob Parameterized Remote Trigger Configuration: - job: https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test - auth: 'Credentials Authentication' as user 'devops' (Credentials ID 'a14c5dae-94e0-4b12-991b-6f7d8620120e') - parameters: [BUILD=5098, LABEL=ECO_130206, ENV=SMOKE_PRODUCTION] - blockBuildUntilComplete: false - connectionRetryLimit: 5 fail to accquire lock because of timeout, skip locking... Triggering parameterized remote job 'https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test' Using job-level defined 'Credentials Authentication' as user 'devops' (Credentials ID 'a14c5dae-94e0-4b12-991b-6f7d8620120e') Triggering remote job now. fail to accquire lock because of timeout, skip locking... CSRF protection is disabled on the remote server. fail to accquire lock because of timeout, skip locking... Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #1 out of 5 Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #2 out of 5 Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #3 out of 5 Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #4 out of 5 Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/, parameters: Retry attempt #5 out of 5 ERROR: Remote build failed with 'ExceedRetryLimitException' for the following reason: 'Max number of connection retries have been exeeded.'. [Pipeline] } }}
Add Comment
[JIRA] (JENKINS-53691) "Execute script on Matrix" not working after upgraing from 0.18.1 to 1.0.0+
Title: Message Title Rick Liu commented on JENKINS-53691 Re: "Execute script on Matrix" not working after upgraing from 0.18.1 to 1.0.0+ Thank you very much for such a prompt fix! Attached my job config.xml when using v0.17 plugin and v2.8.1 plugin. The solution works! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53691) "Execute script on Matrix" not working after upgraing from 0.18.1 to 1.0.0+
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-53691 "Execute script on Matrix" not working after upgraing from 0.18.1 to 1.0.0+ Change By: Rick Liu Attachment: config-0.17.xml Attachment: config-2.8.1.xml Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53691) "Execute script on Matrix" not working after upgraing from 0.18.1 to 1.0.0+
Title: Message Title Rick Liu created an issue Jenkins / JENKINS-53691 "Execute script on Matrix" not working after upgraing from 0.18.1 to 1.0.0+ Issue Type: Bug Assignee: Daniel Heid Attachments: Selection_022.png, Selection_023.png, Selection_024.png Components: postbuildscript-plugin Created: 2018-09-20 21:59 Environment: Ubuntu 16.04.5 LTS OpenJDK 1.8.0_181 Jenkins core. v121.3 Postbuildscript plugin v1.0.0 Priority: Blocker Reporter: Rick Liu I have about 100+ matrix jobs using "Execute Scripts" with "Execute script on Matrix". After upgrding the Post-Build-Script plugin from 0.18.1 to 1.0.0 or newer, the "Execute script on Matrix" is missing and not working (the step will be executed on both Matrix and axis). I saw there are a new Post-Build step named "Execute Scripts on Matrix" with option to select "Execute script on Matrix". The upgrade should correctly migrate the previous old configuration with "Execute script on Matrix" to the new job step "Execute Scripts on Matrix". or at least provide a transition period that both regular "Execute Scripts" and "Execute Scripts on Matrix" steps could support the options to select "Execute script on Matrix/Axis/both".
[JIRA] (JENKINS-52684) Configuration Job-Watching in jobA affects all of other job's Job-Watching
Title: Message Title Rick Liu commented on JENKINS-52684 Re: Configuration Job-Watching in jobA affects all of other job's Job-Watching agree with you~ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52684) Configuration Job-Watching in jobA affects all of other job's Job-Watching
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-52684 Configuration Job-Watching in jobA affects all of other job's Job-Watching Change By: Rick Liu Attachment: EditableEmailNotificationt.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-52684) Configuration Job-Watching in jobA affects all of other job's Job-Watching
Title: Message Title Rick Liu commented on JENKINS-52684 Re: Configuration Job-Watching in jobA affects all of other job's Job-Watching I believe you need to at least add "Editable Email Notification" step in Post-Build section. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52684) Configuration Job-Watching in jobA affects all of other job's Job-Watching
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-52684 Configuration Job-Watching in jobA affects all of other job's Job-Watching Change By: Rick Liu Steps:1. Create 2 free-style jobs with "Watch Job" enabled: *Test1 and Test2* (To enable "Watch Job" you need to add "Editable Email Notification" step in Post-Build) 2. Click "*Watch Job*" link to configure job watching for *Test1* joband "*SUBMIT*" and the link becomes "*Configure Job Watching*"3. Open *Test2* job and "Watch Job" link becomes "*Configure Job Watching*" too!4. Under "*User > Configure > Extended Email Job Watching*" setcion,it shows "*No configuration available*"--At this point, only *Test1* watch job email notification is really working--5. Open *Test2* job and click "*Configure Job Watching*" and "*SUBMIT*"--Now both Test1 and Test2 watch job email notification is working.But job wtach configuration in one job affects configurations in other jobs,and "*User > Configure > Extended Email Job Watching*" setcion still shows "*No configuration available*".--6. Open "*Test1*" job and stop job watching.--This would stop all of job watching including "*Test2*"."*Test2*" job link becomes "*Watch Job*" and no more emails-- Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-52085) Jobs in queue are not sorted
Title: Message Title Rick Liu closed an issue as Not A Defect the behavior in queue is caused by not enabling concurrent build. Jenkins / JENKINS-52085 Jobs in queue are not sorted Change By: Rick Liu Status: Open Closed Resolution: Not A Defect 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-52925) postbuildscript-plugin is unable to limit execution on matrix parent only
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-52925 postbuildscript-plugin is unable to limit execution on matrix parent only Change By: Rick Liu Attachment: Selection_021.png 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-52925) postbuildscript-plugin is unable to limit execution on matrix parent only
Title: Message Title Rick Liu closed an issue as Not A Defect I just found a separate postbuild step called "Execute Scripts on Matrix": this allowed "Matrix target" selection for: MATRIX AXES BOTH Jenkins / JENKINS-52925 postbuildscript-plugin is unable to limit execution on matrix parent only Change By: Rick Liu Status: Open Closed Resolution: Not A Defect 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-52925) postbuildscript-plugin is unable to limit execution on matrix parent only
Title: Message Title Rick Liu created an issue Jenkins / JENKINS-52925 postbuildscript-plugin is unable to limit execution on matrix parent only Issue Type: Bug Assignee: Daniel Heid Attachments: Selection_019.png, Selection_020.png Components: postbuildscript-plugin Created: 2018-08-07 21:48 Environment: Ubuntu 16.04 Jenkins core: 2.107.3 postbuildscript-plugin: upgraded from 0.17 to 2.7.0 Priority: Critical Reporter: Rick Liu I just upgraded the plugin from 0.17 to the latest 2.7.0. For a matrix job (multi-configuration job), back in 0.17, I was able to select "Execute script on": MATRIX - executed for matrix parent job only AXES - executed for each matrix axes jobs BOTH - executed for both matrix parent and axes jobs But in 2.7.0, I don't see such configuration anymore. I see only "Execution is limited to": Master Slave Both When selecting "Master", the execution still runs for both matrix parent and axes jobs.
[JIRA] (JENKINS-52684) Configuration Job-Watching in jobA affects all of other job's Job-Watching
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-52684 Configuration Job-Watching in jobA affects all of other job's Job-Watching Change By: Rick Liu Attachment: Selection_007.png Attachment: Selection_008.png Attachment: Selection_009.png 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-52684) Configuration Job-Watching in jobA affects all of other job's Job-Watching
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-52684 Configuration Job-Watching in jobA affects all of other job's Job-Watching Change By: Rick Liu Steps:1. Create 2 free-style jobs with "Watch Job" enabled: *Test1 and Test2*2. Click "*Watch Job*" link to configure job watching for *Test1* joband "*SUBMIT*" and the link becomes "*Configure Job Watching*"3. Open *Test2* job and "Watch Job" link becomes "*Configure Job Watching*" too!4. Under "*User > Configure > Extended Email Job Watching*" setcion,it shows "*No configuration available*"--At this point, only *Test1* watch job email notification is really working--5. Open *Test2* job and click " * Configure Job Watching * " and "*SUBMIT*"--Now both Test1 and Test2 watch job email notification is working.But job wtach configuration in one job affects configurations in other jobs,and "*User > Configure > Extended Email Job Watching*" setcion still shows "*No configuration available*".--6. Open "*Test1*" job and stop job watching.--This would stop all of job watching including "*Test2*"."*Test2*" job link becomes "*Watch Job*" and no more emails-- Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received
[JIRA] (JENKINS-52684) Configuration Job-Watching in jobA affects all of other job's Job-Watching
Title: Message Title Rick Liu created an issue Jenkins / JENKINS-52684 Configuration Job-Watching in jobA affects all of other job's Job-Watching Issue Type: Bug Assignee: David van Laatum Components: email-ext-plugin Created: 2018-07-21 00:49 Environment: Ubuntu 16.04.4 OpenJDK 8u171-b11-0ubuntu0.16.04.1 Jenkins core 2.107.3 | 2.46.2 Email Extension 2.62 | 2.57.2 Priority: Critical Reporter: Rick Liu Steps: 1. Create 2 free-style jobs with "Watch Job" enabled: Test1 and Test2 2. Click "Watch Job" link to configure job watching for Test1 job and "SUBMIT" and the link becomes "Configure Job Watching" 3. Open Test2 job and "Watch Job" link becomes "Configure Job Watching" too! 4. Under "User > Configure > Extended Email Job Watching" setcion, it shows "No configuration available" -- At this point, only Test1 watch job email notification is really working -- 5. Open Test2 job and click "Configure Job Watching" and "SUBMIT" -- Now both Test1 and Test2 watch job email notification is working. But job wtach configuration in one job affects configurations in other jobs, and "User > Configure > Extended Email Job Watching" setcion still shows "No configuration available". -- 6. Open "Test1" job and stop job watching. -- This would stop all of job watching including "Test2". "Test2" job link becomes "Watch Job" and no more emails --
[JIRA] (JENKINS-52684) Configuration Job-Watching in jobA affects all of other job's Job-Watching
Title: Message Title Rick Liu commented on JENKINS-52684 Re: Configuration Job-Watching in jobA affects all of other job's Job-Watching I can reproduce on: Jenkins core 2.107.3 Email Extension 2.62 and Jenkins core 2.46.2 Email Extension 2.57.2 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-52684) Configuration Job-Watching in jobA affects all of other job's Job-Watching
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-52684 Configuration Job-Watching in jobA affects all of other job's Job-Watching Change By: Rick Liu Steps:1. Create 2 free-style jobs with "Watch Job" enabled: *Test1 and Test2*2. Click "*Watch Job*" link to configure job watching for *Test1* joband "*SUBMIT*" and the link becomes "*Configure Job Watching*"3. Open *Test2* job and "Watch Job" link becomes " * Configure Job Watching * " too!4. Under "*User > Configure > Extended Email Job Watching*" setcion,it shows "*No configuration available*"--At this point, only *Test1* watch job email notification is really working--5. Open *Test2* job and click "Configure Job Watching" and "*SUBMIT*"--Now both Test1 and Test2 watch job email notification is working.But job wtach configuration in one job affects configurations in other jobs,and "*User > Configure > Extended Email Job Watching*" setcion still shows "*No configuration available*".--6. Open "*Test1*" job and stop job watching.--This would stop all of job watching including "*Test2*"."*Test2*" job link becomes "*Watch Job*" and no more emails-- Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received
[JIRA] (JENKINS-48850) Random java.io.IOException: Unexpected termination of the channel
Title: Message Title Rick Liu commented on JENKINS-48850 Re: Random java.io.IOException: Unexpected termination of the channel Owen Mehegan No, I don't have any solution or workaround yet. Right now, it still happens once a while. We improveed our pipeline script to self-retry when we enecounter the interruption. 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-49488) promotion conditions to support OR condition
Title: Message Title Rick Liu commented on JENKINS-49488 Re: promotion conditions to support OR condition Pull request prepared: https://github.com/jenkinsci/promoted-builds-plugin/pull/115 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-49486) Approvers field doesn't expand variable in the build
Title: Message Title Rick Liu commented on JENKINS-49486 Re: Approvers field doesn't expand variable in the build Pull-request prepared: https://github.com/jenkinsci/promoted-builds-plugin/pull/114 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-49488) promotion conditions to support OR condition
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-49488 promotion conditions to support OR condition Change By: Rick Liu Summary: Document that all promotion conditions have to be met to start the promotion support OR condition 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-49486) Approvers field doesn't expand variable in the build
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-49486 Approvers field doesn't expand variable in the build Change By: Rick Liu Comment: [~samsun387]test 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-49486) Approvers field doesn't expand variable in the build
Title: Message Title Rick Liu commented on JENKINS-49486 Re: Approvers field doesn't expand variable in the build Kevin Yu test 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-49486) Approvers field doesn't expand variable in the build
Title: Message Title
Rick Liu updated an issue
Jenkins / JENKINS-49486
Approvers field doesn't expand variable in the build
Change By:
Rick Liu
Comment:
[~oleg_nenashev]Hi Oleg,If I want to develop this feature,what approach would you recommand?1. Try to bring in Token Macro plugin's {{TokenMacro.expandAll(build, listener, approval.name)}}in File "*conditions/ManualCondition.java*" [Line118|https://github.com/jenkinsci/promoted-builds-plugin/blob/master/src/main/java/hudson/plugins/promoted_builds/conditions/ManualCondition.java#L118], [Line140|https://github.com/jenkinsci/promoted-builds-plugin/blob/master/src/main/java/hudson/plugins/promoted_builds/conditions/ManualCondition.java#L140]2.Or try something similar in File "*conditions/ParameterizedSelfPromotionCondition.java*"[Line49|https://github.com/jenkinsci/promoted-builds-plugin/blob/master/src/main/java/hudson/plugins/promoted_builds/conditions/ParameterizedSelfPromotionCondition.java#L49] to use {{build.getBuildVariables()}} to cross-reference the variable
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop
[JIRA] (JENKINS-49486) Approvers field doesn't expand variable in the build
Title: Message Title
Rick Liu edited a comment on JENKINS-49486
Re: Approvers field doesn't expand variable in the build
[~oleg_nenashev]Hi Oleg,If I want to develop this feature,what approach would you recommand?1. Try to bring in Token Macro plugin's {{TokenMacro.expandAll( build, listener, approval.name ) }}in File "*conditions/ManualCondition.java*" [Line118|https://github.com/jenkinsci/promoted-builds-plugin/blob/master/src/main/java/hudson/plugins/promoted_builds/conditions/ManualCondition.java#L118], [Line140|https://github.com/jenkinsci/promoted-builds-plugin/blob/master/src/main/java/hudson/plugins/promoted_builds/conditions/ManualCondition.java#L140]2.Or try something similar in File "*conditions/ParameterizedSelfPromotionCondition.java*"[Line49|https://github.com/jenkinsci/promoted-builds-plugin/blob/master/src/main/java/hudson/plugins/promoted_builds/conditions/ParameterizedSelfPromotionCondition.java#L49] to use {{build.getBuildVariables()}} to cross-reference the variable
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-49486) Approvers field doesn't expand variable in the build
Title: Message Title
Rick Liu edited a comment on JENKINS-49486
Re: Approvers field doesn't expand variable in the build
[~oleg_nenashev]Hi Oleg,If I want to develop this feature,what approach would you recommand?1. Try to bring in Token Macro plugin's {{ TokenMacro.expandAll( build, listener, approval.name )}} in File "*conditions/ManualCondition.java*" [Line118|https://github.com/jenkinsci/promoted-builds-plugin/blob/master/src/main/java/hudson/plugins/promoted_builds/conditions/ManualCondition.java#L118], [Line140|https://github.com/jenkinsci/promoted-builds-plugin/blob/master/src/main/java/hudson/plugins/promoted_builds/conditions/ManualCondition.java#L140]2.Or try something similar in File " * conditions/ParameterizedSelfPromotionCondition.java * "[Line49|https://github.com/jenkinsci/promoted-builds-plugin/blob/master/src/main/java/hudson/plugins/promoted_builds/conditions/ParameterizedSelfPromotionCondition.java#L49] to use {{ build.getBuildVariables() }} to cross-reference the variable
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-49486) Approvers field doesn't expand variable in the build
Title: Message Title Rick Liu commented on JENKINS-49486 Re: Approvers field doesn't expand variable in the build Oleg Nenashev Hi Oleg, If I want to develop this feature, what approach would you recommand? 1. Try to bring in Token Macro plugin's TokenMacro.expandAll( build, listener, approval.name ) in File "conditions/ManualCondition.java" Line118, Line140 2. Or try something similar in File "conditions/ParameterizedSelfPromotionCondition.java" Line49 to use build.getBuildVariables() to cross-reference the variable 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-49488) Document that all promotion conditions have to be met to start the promotion
Title: Message Title Rick Liu commented on JENKINS-49488 Re: Document that all promotion conditions have to be met to start the promotion ok I agree with you ~ In addition to document improvement, maybe add a new feature to choose AND or OR for promote conditions. 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-49488) Document that all promotion conditions have to be met to start the promotion
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-49488 Document that all promotion conditions have to be met to start the promotion Change By: Rick Liu Issue Type: Improvement New Feature 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-49488) Promote immediately once the build is complete based on build parameters not working
Title: Message Title Rick Liu edited a comment on JENKINS-49488 Re: Promote immediately once the build is complete based on build parameters not working Hi Oleg~After some job config cleanup and retry,now I'm able to see:***Met Qualification Automatically promoted immediately after the build because parameter was matched***Unmet QualificationManual Approval***Refer to the screensot attachment.I'd think the issue right now it's the code is using boolean ' * AND * ' to chain-up the criterias.But it should use boolean ' * OR * ' to meet the description meaning of " * Promote immediately once the build is complete based on build parameters * " . 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-49488) Promote immediately once the build is complete based on build parameters not working
Title: Message Title Rick Liu commented on JENKINS-49488 Re: Promote immediately once the build is complete based on build parameters not working Hi Oleg~ After some job config cleanup and retry, now I'm able to see: *** Met Qualification Automatically promoted immediately after the build because parameter was matched *** Unmet Qualification Manual Approval *** Refer to the screensot attachment. I'd think the issue right now it's the code is using boolean 'AND' to chain-up the criterias. But it should use boolean 'OR' to meet the description of "Promote immediately once the build is complete based on build parameters" 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-49488) Promote immediately once the build is complete based on build parameters not working
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-49488 Promote immediately once the build is complete based on build parameters not working Change By: Rick Liu Attachment: Selection_003.png Attachment: Selection_004.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-49488) Promote immediately once the build is complete based on build parameters not working
Title: Message Title Rick Liu edited a comment on JENKINS-49488 Re: Promote immediately once the build is complete based on build parameters not working Attached build.xml build-97 is a rebuild from build#96.build-97 is a fresh clean build. 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-49488) Promote immediately once the build is complete based on build parameters not working
Title: Message Title Rick Liu edited a comment on JENKINS-49488 Re: Promote immediately once the build is complete based on build parameters not working Attached build.xmlbuild-97 is a rebuild from build#96.build-97 is a fresh clean build. Both have the same issue. 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-49488) Promote immediately once the build is complete based on build parameters not working
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-49488 Promote immediately once the build is complete based on build parameters not working Change By: Rick Liu Attachment: build.xml 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-49488) Promote immediately once the build is complete based on build parameters not working
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-49488 Promote immediately once the build is complete based on build parameters not working Change By: Rick Liu Attachment: build-97.xml Attachment: build-98.xml 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-49488) Promote immediately once the build is complete based on build parameters not working
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-49488 Promote immediately once the build is complete based on build parameters not working Change By: Rick Liu Attachment: build.xml 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-49488) Promote immediately once the build is complete based on build parameters not working
Title: Message Title Rick Liu commented on JENKINS-49488 Re: Promote immediately once the build is complete based on build parameters not working Attached build.xml 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-49488) Promote immediately once the build is complete based on build parameters not working
Title: Message Title
Rick Liu updated an issue
Jenkins / JENKINS-49488
Promote immediately once the build is complete based on build parameters not working
Change By:
Rick Liu
emphasized textI I have selected "*Promote immediately once the build is complete based on build parameters*" with:Parameter Name: $\{AUTO_APPROVE}Parameter Value: trueorParameter Name: AUTO_APPROVEParameter Value: trueIn the build, when Boolean paramter AUTO_APPROVE is set to true,the promotion job doesn't start.
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-49488) Promote immediately once the build is complete based on build parameters not working
Title: Message Title
Rick Liu updated an issue
Jenkins / JENKINS-49488
Promote immediately once the build is complete based on build parameters not working
Change By:
Rick Liu
I emphasized textI have selected "*Promote immediately once the build is complete based on build parameters*" with:Parameter Name: \ ${AUTO_APPROVE}Parameter Value: trueorParameter Name: AUTO_APPROVEParameter Value: trueIn the build, when Boolean paramter AUTO_APPROVE is set to true,the promotion job doesn't start.
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-49488) Promote immediately once the build is complete based on build parameters not working
Title: Message Title
Rick Liu updated an issue
Jenkins / JENKINS-49488
Promote immediately once the build is complete based on build parameters not working
Change By:
Rick Liu
emphasized textI have selected "*Promote immediately once the build is complete based on build parameters*" with:Parameter Name: \ $ \ {AUTO_APPROVE}Parameter Value: trueorParameter Name: AUTO_APPROVEParameter Value: trueIn the build, when Boolean paramter AUTO_APPROVE is set to true,the promotion job doesn't start.
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-49488) Promote immediately once the build is complete based on build parameters not working
Title: Message Title
Rick Liu updated an issue
Jenkins / JENKINS-49488
Promote immediately once the build is complete based on build parameters not working
Change By:
Rick Liu
I have selected "*Promote immediately once the build is complete based on build parameters*" with:Parameter Name: ${AUTO_APPROVE}Parameter Value: true or Parameter Name: AUTO_APPROVEParameter Value: true In the build, when Boolean paramter AUTO_APPROVE is set to true,the promotion job doesn't start.
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-49488) Promote immediately once the build is complete based on build parameters not working
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-49488 Promote immediately once the build is complete based on build parameters not working Change By: Rick Liu Attachment: Selection_028.png Attachment: Selection_029.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-49488) Promote immediately once the build is complete based on build parameters not working
Title: Message Title
Rick Liu created an issue
Jenkins / JENKINS-49488
Promote immediately once the build is complete based on build parameters not working
Issue Type:
Bug
Assignee:
Oleg Nenashev
Attachments:
Selection_026.png, Selection_027.png
Components:
promoted-builds-plugin
Created:
2018-02-10 03:51
Environment:
Ubuntu 16.04 Jenkins ver. 2.46.2 LTS promoted builds plugin v2.28.1
Priority:
Major
Reporter:
Rick Liu
I have selected "Promote immediately once the build is complete based on build parameters" with: Parameter Name: $ {AUTO_APPROVE} Parameter Value: true In the build, when Boolean paramter AUTO_APPROVE is set to true, the promotion job doesn't start.
Add Comment
[JIRA] (JENKINS-49487) Groovy Postbuild under Promotion Actions always opens empty "Classpath entry" resulting "Save" exception
Title: Message Title Rick Liu created an issue Jenkins / JENKINS-49487 Groovy Postbuild under Promotion Actions always opens empty "Classpath entry" resulting "Save" exception Issue Type: Bug Assignee: Oleg Nenashev Attachments: Selection_023.png, Selection_024.png, Selection_025.png Components: promoted-builds-plugin Created: 2018-02-10 03:42 Environment: Ubuntu 16.04 Jenkins ver. 2.46.2 LTS promoted builds plugin v2.28.1 Groovy Postbuild v2.3.1 Priority: Major Reporter: Rick Liu Under "Promotion Actions", when using "Groovy Postbuild" action, by default, it always opens an empty "Classpath entry" field everytime. If I forgot to click "x" to remove the field, and click "Save" or "Apply" button, then Jenkins would throw exception error. Add Comment
[JIRA] (JENKINS-49486) Approvers field doesn't expand variable in the build
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-49486 Approvers field doesn't expand variable in the build Change By: Rick Liu Attachment: Selection_020.png Attachment: Selection_021.png Attachment: Selection_022.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-49486) Approvers field doesn't expand variable in the build
Title: Message Title Rick Liu created an issue Jenkins / JENKINS-49486 Approvers field doesn't expand variable in the build Issue Type: Bug Assignee: Oleg Nenashev Components: promoted-builds-plugin Created: 2018-02-10 03:30 Environment: Ubuntu 16.04 Jenkins ver. 2.46.2 LTS promoted builds plugin v2.28.1 Priority: Major Reporter: Rick Liu Under "Criteria" section, when select "Only when manually approved", Approvers field doesn't expand variable in the build. Add Comment
[JIRA] (JENKINS-43146) java.lang.NullPointerException when publish JUnit.xml result to Zephyr for Jira
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-43146 java.lang.NullPointerException when publish JUnit.xml result to Zephyr for Jira Change By: Rick Liu Attachment: test2.png Attachment: test1.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-43146) java.lang.NullPointerException when publish JUnit.xml result to Zephyr for Jira
Title: Message Title
Rick Liu updated an issue
Jenkins / JENKINS-43146
java.lang.NullPointerException when publish JUnit.xml result to Zephyr for Jira
Change By:
Rick Liu
I have a Robot Framework test result file "output.xml", and I convert this test result file into JUnit format by command below in Build step:{code:java}rebot -x junit.xml -l NONE -r NONE output.xml {code} Under Post-Build, I have 2 post-build actions (refer to file Selection_003.png):1. Publish Junit test result report2. Publish test result to Zephyr for JIRAAnd I'll get:{code:java}+ rebot -x junit junit1 .xml -l NONE -r NONE output output1 .xmlXUnit: /var/lib/Jenkins_Backup/jenkins/jobs/Publish_Test_Result_JIRA/workspace/ junit junit1 .xmlRecording test results[ZapiTestResultReporter] [INFO] Examining test results...Build result is SUCCESSTotal Test Cases : 8ERROR: Build step failed with exceptionjava.lang.NullPointerException at com.thed.zephyr.jenkins.utils.rest.TestCaseUtil.executeTests(TestCaseUtil.java:424) at com.thed.zephyr.jenkins.utils.rest.TestCaseUtil.processTestCaseDetails(TestCaseUtil.java:564) at com.thed.zephyr.jenkins.reporter.ZfjReporter.perform(ZfjReporter.java:99) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665) at hudson.model.Run.execute(Run.java:1753) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404)Build step 'Publish test result to Zephyr for JIRA' marked build as failure{code} {code:java}+ rebot -x junit junit2 .xml -l NONE -r NONE output output2 .xmlXUnit: /var/lib/Jenkins_Backup/jenkins/jobs/Publish_Test_Result_JIRA/workspace/ junit junit2 .xmlBuild step 'Execute shell' marked build as failureRecording test results[ZapiTestResultReporter] [INFO] Examining test results...Build result is FAILURETotal Test Cases : 8ERROR: Build step failed with exceptionjava.lang.NullPointerException at com.thed.zephyr.jenkins.utils.rest.TestCaseUtil.executeTests(TestCaseUtil.java:404) at com.thed.zephyr.jenkins.utils.rest.TestCaseUtil.processTestCaseDetails(TestCaseUtil.java:564) at com.thed.zephyr.jenkins.reporter.ZfjReporter.perform(ZfjReporter.java:99) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665) at hudson.model.Run.execute(Run.java:1753) at
[JIRA] (JENKINS-43146) java.lang.NullPointerException when publish JUnit.xml result to Zephyr for Jira
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-43146 java.lang.NullPointerException when publish JUnit.xml result to Zephyr for Jira Change By: Rick Liu Attachment: junit2.xml Attachment: junit1.xml 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-43146) java.lang.NullPointerException when publish JUnit.xml result to Zephyr for Jira
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-43146 java.lang.NullPointerException when publish JUnit.xml result to Zephyr for Jira Change By: Rick Liu Attachment: output2.xml Attachment: output1.xml 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-43146) java.lang.NullPointerException when publish JUnit.xml result to Zephyr for Jira
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-43146 java.lang.NullPointerException when publish JUnit.xml result to Zephyr for Jira Change By: Rick Liu Attachment: Selection_003.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-43146) java.lang.NullPointerException when publish JUnit.xml result to Zephyr for Jira
Title: Message Title Rick Liu created an issue Jenkins / JENKINS-43146 java.lang.NullPointerException when publish JUnit.xml result to Zephyr for Jira Issue Type: Bug Assignee: Zephyr Developer Attachments: Selection_003.png Components: zephyr-for-jira-test-management-plugin Created: 2017/Mar/28 1:40 AM Environment: Ubuntu 14.04.05 x64 Jenkins 2.32.3 zephyr-for-jira-test-management 1.4 Priority: Major Reporter: Rick Liu I have a Robot Framework test result file "output.xml", and I convert this test result file into JUnit format by command below in Build step: rebot -x junit.xml -l NONE -r NONE output.xml Under Post-Build, I have 2 post-build actions (refer to file Selection_003.png): 1. Publish Junit test result report 2. Publish test result to Zephyr for JIRA And I'll get: + rebot -x junit.xml -l NONE -r NONE output.xml XUnit: /var/lib/Jenkins_Backup/jenkins/jobs/Publish_Test_Result_JIRA/workspace/junit.xml Recording test results [ZapiTestResultReporter] [INFO] Examining test results... Build result is SUCCESS Total Test Cases : 8ERROR: Build step failed with exception
[JIRA] (JENKINS-39593) Performance slow in 1.5 release
Title: Message Title Rick Liu commented on JENKINS-39593 Re: Performance slow in 1.5 release Thanks Bruno~ I'll try to setup a test Jenkins instance for 1.5.4.0001.hpi next week to test One suggestion regarding to the LRU cache with 10 items. In the final release, is it possible to make it configurable through WebUI? 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-35351) Rerun the running job to other availalbe slaves if connection channel lost in current slave
Title: Message Title Rick Liu edited a comment on JENKINS-35351 Re: Rerun the running job to other availalbe slaves if connection channel lost in current slave But Naginator plugin would re-trigger the build after the build failure,so you would still get a build failure first.I was thinking if this can be handled in the core,then when the it's a Jenkins system type of failure,it would automatic retry the next slave available or goes back to queue. And instead of let the build failed, reschedule the build to use next new build number,we get to use the same build number. 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-35351) Rerun the running job to other availalbe slaves if connection channel lost in current slave
Title: Message Title Rick Liu commented on JENKINS-35351 Re: Rerun the running job to other availalbe slaves if connection channel lost in current slave But Naginator plugin would re-trigger the build after the build failure, so you would still get a build failure first. I was thinking if this can be handled in the core, then when the it's a Jenkins system type of failure, it would automatic retry the next slave available or goes back to queue. And instead of let the build failed, reschedule the build to use next new build number, we get to use the same build number. 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-41722) Job folder loading performance scalability
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-41722 Job folder loading performance scalability Change By: Rick Liu Summary: Job folder loading performance is worse when folder contains fewer items scalability Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41722) Job folder loading performance is worse when folder contains fewer items
Title: Message Title Rick Liu commented on JENKINS-41722 Re: Job folder loading performance is worse when folder contains fewer items And if the total number items (job) is critical to the overall Jenkins performance, it'd be good if Jenkins could suggest an upper bound limit number. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41722) Job folder loading performance is worse when folder contains fewer items
Title: Message Title Rick Liu commented on JENKINS-41722 Re: Job folder loading performance is worse when folder contains fewer items Refer to jenkins_open_AC_folder_Current_Thread.log file. The Thread "Handling GET /view/All/job/Projects/job/AC/ from 172.18.25.141 : RequestHandlerThread9 (133)" was process item "Projects/AC" at beginning correctly. Until Thread "Handling GET /view/All/job/Projects/job/AC/ from 172.18.25.141 : RequestHandlerThread9 View/index.jelly View/sidepanel.jelly AbstractFolder/tasks-bottom.jelly (133)" starts to process item "Build_Steps", which is totally outside of current view context: INFO: OUT: RoleBasedAuthorizationStrategy.getACL(AbstractItem project=com.cloudbees.hudson.plugins.folder.Folder@2e820a2b[Build_Steps]): start Feb 24, 2017 6:06:21 PM com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy getACL INFO: OUT: RoleBasedAuthorizationStrategy.getACL(AbstractItem project=com.cloudbees.hudson.plugins.folder.Folder@2e820a2b[Build_Steps]): Thread.getAllStackTraces()= Current Thread: Handling GET /view/All/job/Projects/job/AC/ from 172.18.25.141 : RequestHandlerThread9 View/index.jelly View/sidepanel.jelly AbstractFolder/tasks-bottom.jelly (133) Thread Handling GET /view/All/job/Projects/job/AC/ from 172.18.25.141 : RequestHandlerThread9 View/index.jelly View/sidepanel.jelly AbstractFolder/tasks-bottom.jelly at java.lang.Thread.dumpThreads(Native Method) at java.lang.Thread.getAllStackTraces(Thread.java:1607) at com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy.printAllStackTraces(RoleBasedAuthorizationStrategy.java:94) at com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy.getACL(RoleBasedAuthorizationStrategy.java:176) at hudson.model.AbstractItem.getACL(AbstractItem.java:498) at hudson.model.AbstractItem.hasPermission(AbstractItem.java:512) at jenkins.model.Jenkins.getItems(Jenkins.java:1719) at jenkins.model.Jenkins.getItems(Jenkins.java:325) at hudson.model.Items.getAllItems(Items.java:363) at hudson.model.Items.getAllItems(Items.java:359) at jenkins.model.Jenkins.getAllItems(Jenkins.java:1753) at jenkins.model.Jenkins.getAllItems(Jenkins.java:1762) at com.cloudbees.hudson.plugins.folder.relocate.StandardHandler.validDestinations(StandardHandler.java:85) at com.cloudbees.hudson.plugins.folder.relocate.StandardHandler.applicability(StandardHandler.java:54) at com.cloudbees.hudson.plugins.folder.relocate.DefaultRelocationUI.isAvailable(DefaultRelocationUI.java:67) at com.cloudbees.hudson.plugins.folder.relocate.RelocationAction.getIconClassName(RelocationAction.java:99) If the caller function can filter out the un-needed items based upon the path first, this could save the time to process hasPermission()/getACL for the un-needed items. Add Comment
[JIRA] (JENKINS-41722) Job folder loading performance is worse when folder contains fewer items
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-41722 Job folder loading performance is worse when folder contains fewer items Change By: Rick Liu Attachment: jenkins_open_AC_folder_Current_Thread.log Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41722) Job folder loading performance is worse when folder contains fewer items
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-41722 Job folder loading performance is worse when folder contains fewer items Change By: Rick Liu Attachment: jenkins_open_AC_folder.log.tgz Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41722) Job folder loading performance is worse when folder contains fewer items
Title: Message Title Rick Liu commented on JENKINS-41722 Re: Job folder loading performance is worse when folder contains fewer items The whole point here is it shouldn't always call getAllItems(). Back in old days when there is no Folder-plugin, every item is at root level. It probably makes no difference if you call getAllItems() or getItems(). With folder structure, Jenkins would need an API similar to getItems() but with the ability to get items at a specified path, and to return only the immediate children items. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41722) Job folder loading performance is worse when folder contains fewer items
Title: Message Title Rick Liu commented on JENKINS-41722 Re: Job folder loading performance is worse when folder contains fewer items I also uploaded the file jenkins-open-folder.tar.gz, which contains the log when I repeat the benchmark test procedures: 1. Open Project folder (jenkins_open_Projects_folder01.log) - contains 2 folders (AC and SB) 2. Open AC folder (jenkins_open_AC_folder.log) contains "releas_trunk" folder and 2 multibranch-matrix projects (Projects/AC/br_4-1 and Projects/AC/br_4-2) 3. Open Project folder again (jenkins_open_Projects_folder02.log) 4. Open SB folder (jenkins_open_SB_folder.log) contains "releas_trunk" folder and 2 multibranch-matrix projects (Projects/SB/br_2-3 and Projects/SB/br_2-4) 5. Open Project folder again (jenkins_open_Projects_folder03.log) For each step, I intentionally avoid to start at round minute to prevent the log been polluted by unknown calling of getACL(). But you could still find from the log that, after it processed the permission for the required items to display in the current view page, it continues to process the permission for all of non-required items. Should I open another JIRA ticket for this? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the
[JIRA] (JENKINS-41722) Job folder loading performance is worse when folder contains fewer items
Title: Message Title Rick Liu commented on JENKINS-41722 Re: Job folder loading performance is worse when folder contains fewer items Uploaded file jenkins-startup.tar.gz: This tarball contains the first 5 minutes of logs (including stack trace) after Jenkins service start-up. I put the stack trace call inside RoleBasedAuthorizationStrategy.getACL(AbstractItem) RoleBasedAuthorizationStrategy.getACL(roleMapName, itemName, roleType, item) At each round minute, RoleBasedAuthorizationStrategy.getACL(AbstractItem) was called twice at beginning, and then RoleBasedAuthorizationStrategy.getACL(roleMapName, itemName, roleType, item) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41722) Job folder loading performance is worse when folder contains fewer items
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-41722 Job folder loading performance is worse when folder contains fewer items Change By: Rick Liu Attachment: jenkins-startup.tar.gz Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41722) Job folder loading performance is worse when folder contains fewer items
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-41722 Job folder loading performance is worse when folder contains fewer items Change By: Rick Liu Attachment: jenkins-open-folder.tar.gz Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41722) Job folder loading performance is worse when folder contains fewer items
Title: Message Title Rick Liu commented on JENKINS-41722 Re: Job folder loading performance is worse when folder contains fewer items While trying to collect the data, I added debug lines to role-strategy-plugin, and found out that for every minute, jenkins is repeatedly calling RoleBasedProjectNamingStrategy.getACL() itself. even when there's no user interaction. It's repeatedly doing the same thing everything minute after Jenkins is fully up and running. Refer to jenkins-starup.log This is the full log containing the first 5 minutes since Jenkins service started. Jenkins is fully up and running at "Feb 22, 2017 6:26:26 PM". Then after 6:26:26, for every whole minute (6:27:00, 6:28:00, 6:29:00, etc), it's calling getACL(), regenerate roleMap (RoleMap.newMatchingRoleMap(), etc. I have separate those log out into separate log files as "jenkins-startup-repeat01-0627.log" Right now I'm using a test server to collect logs. Hence, I have only minimal amount of jobs items: Folder@775f8b29[Build_Steps] contains 3 freestyle jobs: FreeStyleProject@251a4167[Build_Steps/Chroot_Build] FreeStyleProject@40694780[Build_Steps/Post_Build] FreeStyleProject@54a632cd[Build_Steps/Transfer_Artifacts] Folder@bbc939b[Projects] contains: Folder@13d4d234[Projects/AC] MatrixMultiBranchProject@78bace4f[Projects/AC/br_4-1] MatrixProject@39f19408[Projects/AC/br_4-1/br_4-1_offline_otp] MatrixProject@308cb740[Projects/AC/br_4-1/br_4-1_oracle] MatrixMultiBranchProject@3dc34516[Projects/AC/br_4-2] MatrixProject@d4632cf[Projects/AC/br_4-2/br_4-2_chained_auth] MatrixProject@201a8451[Projects/AC/br_4-2/br_4-2_cli] Folder@20c9d46[Projects/AC/release_trunk] MatrixProject@4fc557c7[Projects/AC/release_trunk/trunk] Folder@17434e36[Projects/SB] MatrixMultiBranchProject@71c70c6a[Projects/SB/br_2-3] MatrixProject@1d5024d4[Projects/SB/br_2-3/br_2-3_dev_fortitracer] MatrixProject@428d3556[Projects/SB/br_2-3/br_2-3_dev_pkgtools] MatrixMultiBranchProject@7afa044c[Projects/SB/br_2-4] MatrixProject@657e8516[Projects/SB/br_2-4/br_2-4_AWS] Folder@700e5985[Projects/SB/release_trunk] MatrixProject@49691c7b[Projects/SB/release_trunk/trunk] Why it's repeatedly doing the same thing every minute? On production server, I have much more job items. could this be the performance impact factor? Add Comment
[JIRA] (JENKINS-41722) Job folder loading performance is worse when folder contains fewer items
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-41722 Job folder loading performance is worse when folder contains fewer items Change By: Rick Liu Attachment: jenkins-startup-repeat01-0627.log Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
