[JIRA] (JENKINS-60891) An illegal reflective access from EnvInject plugin
Title: Message Title Pavel Kudrys created an issue Jenkins / JENKINS-60891 An illegal reflective access from EnvInject plugin Issue Type: Improvement Assignee: Unassigned Components: envinject-plugin Created: 2020-01-28 12:01 Environment: Jenkins ver. 2.218 EnvInject API Plugin 1.7 Environment Injector Plugin 2.3.0 Priority: Major Reporter: Pavel Kudrys Hi, After starting Jenkins, there is displayed "An illegal reflective access" warning in console. WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.jenkinsci.plugins.envinject.service.En vInjectMasterEnvVarsSetter to field java.lang.reflect.Field.modifiers WARNING: Please consider reporting this to the maintainers of org.jenkinsci.plug ins.envinject.service.EnvInjectMasterEnvVarsSetter WARNING: Use --illegal-access=warn to enable warnings of further illegal reflect ive access operations WARNING: All illegal access operations will be denied in a future release Add Comment
[JIRA] (JENKINS-60521) missing changelog for 2.209
Title: Message Title Pavel Kudrys created an issue Jenkins / JENKINS-60521 missing changelog for 2.209 Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-12-18 07:14 Labels: changelog Priority: Minor Reporter: Pavel Kudrys Hi folks, Could you please post changelog for 2.209? Add Comment
[JIRA] (JENKINS-56751) missing changelog for 2.169
Title: Message Title Pavel Kudrys created an issue Jenkins / JENKINS-56751 missing changelog for 2.169 Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-03-26 07:43 Priority: Minor Reporter: Pavel Kudrys Hi guys, As with some past releases, 2.169 seems to be released without the changelog? Could you please fix it? Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56281) missing changelog for 2.166
Title: Message Title Pavel Kudrys created an issue Jenkins / JENKINS-56281 missing changelog for 2.166 Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-02-26 09:40 Priority: Minor Reporter: Pavel Kudrys Hi guys, I've reported this problem two releases back and there is again missing changelog for 2.166. Something's wrong with Jenkins release process? It's not the first time the changelog is missing. Please don't tell me that the changelog for JENKINS(!!!) is published manually? Add Comment
[JIRA] (JENKINS-55969) missing changelog for 2.163
Title: Message Title Pavel Kudrys created an issue Jenkins / JENKINS-55969 missing changelog for 2.163 Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-02-05 07:55 Priority: Minor Reporter: Pavel Kudrys Hi guys, It seems there is missing changelog for 2.163? I'm not comfortable installing new version, without knowing what's new or different BTW, Jenkins changelog is often released few hours behind the actual Jenkins release? Is there a problem with your release mechanism or the changelog is published manually? Thanks. Add Comment
[JIRA] (JENKINS-36085) vSphere 2.13 causes error while restarting VM
Title: Message Title Pavel Kudrys commented on JENKINS-36085 Re: vSphere 2.13 causes error while restarting VM Hi, I'm sorry to report that the problem is still present in recently released 2.14. Am I really alone with this kind of problem? 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-39379) missing 2.28 jenkins.war!
Title: Message Title Pavel Kudrys closed an issue as Duplicate Jenkins / JENKINS-39379 missing 2.28 jenkins.war! Change By: Pavel Kudrys Status: Open Closed Resolution: Duplicate 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-39379) missing 2.28 jenkins.war!
Title: Message Title Pavel Kudrys commented on JENKINS-39379 Re: missing 2.28 jenkins.war! This issue could be closed. There is already created an infrastructure ticket: https://issues.jenkins-ci.org/browse/INFRA-962 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-39379) missing 2.28 jenkins.war!
Title: Message Title Pavel Kudrys created an issue Jenkins / JENKINS-39379 missing 2.28 jenkins.war! Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Oct/31 8:44 AM Priority: Blocker Reporter: Pavel Kudrys Hi guys, It seems someone forgot to upload 2.28 war file? I just tried to download 2.28 from the main Jenkins page (where it says 2.28 is available) but the downloaded file seems to be 2.27 instead! And if I try to download/install 2.28 from Jenkins Configuration page, it throws an error "_Failed to download from http://updates.jenkins-ci.org/download/war/2.28/jenkins.war (redirected to: http://mirrors.jenkins-ci.org/war/2.28/jenkins.war)_". Thank you in advance for fixing this! Add Comment
[JIRA] (JENKINS-39232) unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave
Title: Message Title Pavel Kudrys commented on JENKINS-39232 Re: unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave Hi guys, It seems someone forgot to upload 2.28 war file? I just tried to download 2.28 from the main Jenkins page (where it says 2.28 is available) but the downloaded file seems to be 2.27 instead! And if I try to download/install 2.28 from Jenkins Configuration page, it throws an error "_Failed to download from http://updates.jenkins-ci.org/download/war/2.28/jenkins.war (redirected to: http://mirrors.jenkins-ci.org/war/2.28/jenkins.war)_". Thank you in advance for fixing 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 Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39232) unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave
Title: Message Title Pavel Kudrys commented on JENKINS-39232 Re: unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave Thanks for your effort guys! Do I understand it right that the fix should make the master/slave communication working, even without immediate update of affected plugins? Thanks! 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-39232) unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave
Title: Message Title
Pavel Kudrys edited a comment on JENKINS-39232
Re: unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave
Hi,Thanks for the feedback. Here is the system log... [^Jenkins2.27_SystemLog.txt] The slave is started (on VM start) via batch command like this:{quote}call "C:\Program Files (x86)\Java\jre1.8.0_111\bin\java.exe" -Xrs -jar "slave.jar" -jnlpUrl http://cpjen01:8090/computer/CPRAN03/slave-agent.jnlp -secret secretkey{quote}If you need Slave configuration from Jenkins GUI, here it is... !SlaveConfiguration.png|thumbnail! Thanks! BTW, I'm not using *Slave Setup Plugin* in my Jenkins configuration. Just *Windows Slaves Plugin*.
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-39232) unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave
Title: Message Title Pavel Kudrys commented on JENKINS-39232 Re: unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave Hi, Thanks for the feedback. Here is the system log... Jenkins2.27_SystemLog.txt The slave is started (on VM start) via batch command like this: call "C:\Program Files (x86)\Java\jre1.8.0_111\bin\java.exe" -Xrs -jar "slave.jar" -jnlpUrl http://cpjen01:8090/computer/CPRAN03/slave-agent.jnlp -secret secretkey If you need Slave configuration from Jenkins GUI, here it is... Thanks! 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-39232) unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave
Title: Message Title Pavel Kudrys updated an issue Jenkins / JENKINS-39232 unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave Change By: Pavel Kudrys Attachment: SlaveConfiguration.png 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-39232) unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave
Title: Message Title
Pavel Kudrys updated an issue
Jenkins / JENKINS-39232
unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave
Change By:
Pavel Kudrys
Hi,I'm unable to start/connect slave machine, using JNLP, after installing version 2.27 on master + new 3.0 slave.jar on slave computer. Installed Java 1.8.111. I've enabled Java Web Start agent 3 and 4 in Configure Global Security, but to no avail. All I'm getting is an error "Local headers refused by remote: *CPRAN03 is not a JNLP agent*" followed by number of exceptions and even version 3 and 2 of JNLP agent fails to start. Is there something else I need to configure in latest Jenkins 2.27? {quote}C:\Jenkins>call "C:\Program Files (x86)\Java\jre1.8.0_111\bin\java.exe" -Xrs -jar "slave.jar" -jnlpUrl http://cpjen01:8090/computer/CPRAN03/slave-agent.jnlp -secret "secretkey"Oct 25, 2016 7:58:00 AM hudson.remoting.jnlp.Main createEngineINFO: Setting up slave: CPRAN03Oct 25, 2016 7:58:00 AM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode.Oct 25, 2016 7:58:00 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among [http://cpjen01:8090/]Oct 25, 2016 7:58:00 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Agent discovery successful Agent address: cpjen01 Agent port:49274 Identity: ab:f2:5f:d6:32:a6:42:71:fc:d8:9f:9a:05:0c:77:d0Oct 25, 2016 7:58:00 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: HandshakingOct 25, 2016 7:58:00 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to cpjen01:49274Oct 25, 2016 7:58:00 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Trying protocol: JNLP4-connectOct 25, 2016 7:58:00 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Remote identity confirmed: ab:f2:5f:d6:32:a6:42:71:fc:d8:9f:9a:05:0c:77:d0Oct 25, 2016 7:58:00 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to cpjen01/10.8.32.77:49274] Local headers refused by remote: CPRAN03 is not a JNLP agentOct 25, 2016 7:58:00 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: CPRAN03 is not a JNLP agentat org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223)at hudson.remoting.Engine.innerRun(Engine.java:415)at hudson.remoting.Engine.run(Engine.java:280)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: CPRAN03 is not a JNLP agentat org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:377)at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:432)at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832)at
[JIRA] (JENKINS-39232) unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave
Title: Message Title Pavel Kudrys updated an issue Jenkins / JENKINS-39232 unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave Change By: Pavel Kudrys Attachment: jnlp_slave.png 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-39232) unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave
Title: Message Title
Pavel Kudrys updated an issue
Jenkins / JENKINS-39232
unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave
Change By:
Pavel Kudrys
Hi,I'm unable to start/connect slave machine, using JNLP, after installing version 2.27 on master + new 3.0 slave.jar on slave computer. Installed Java 1.8.111. I've enabled Java Web Start agent 3 and 4 in Configure Global Security, but to no avail. All I'm getting is an error "Local headers refused by remote: *CPRAN03 is not a JNLP agent*" followed by number of exceptions and even version 3 and 2 of JNLP agent fails to start. Is there something else I need to configure in latest Jenkins 2.27? {quote}C:\Jenkins>call "C:\Program Files (x86)\Java\jre1.8.0_111\bin\java.exe" -Xrs -jar "slave.jar" -jnlpUrl http://cpjen01:8090/computer/CPRAN03/slave-agent.jnlp -secret "secretkey"Oct 25, 2016 7:58:00 AM hudson.remoting.jnlp.Main createEngineINFO: Setting up slave: CPRAN03Oct 25, 2016 7:58:00 AM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode.Oct 25, 2016 7:58:00 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among [http://cpjen01:8090/]Oct 25, 2016 7:58:00 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Agent discovery successful Agent address: cpjen01 Agent port:49274 Identity: ab:f2:5f:d6:32:a6:42:71:fc:d8:9f:9a:05:0c:77:d0Oct 25, 2016 7:58:00 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: HandshakingOct 25, 2016 7:58:00 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to cpjen01:49274Oct 25, 2016 7:58:00 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Trying protocol: JNLP4-connectOct 25, 2016 7:58:00 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Remote identity confirmed: ab:f2:5f:d6:32:a6:42:71:fc:d8:9f:9a:05:0c:77:d0Oct 25, 2016 7:58:00 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to cpjen01/10.8.32.77:49274] Local headers refused by remote: CPRAN03 is not a JNLP agentOct 25, 2016 7:58:00 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: CPRAN03 is not a JNLP agentat org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223)at hudson.remoting.Engine.innerRun(Engine.java:415)at hudson.remoting.Engine.run(Engine.java:280)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: CPRAN03 is not a JNLP agentat org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:377)at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:432)at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832)at
[JIRA] (JENKINS-39232) unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave
Title: Message Title Pavel Kudrys created an issue Jenkins / JENKINS-39232 unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave Issue Type: Bug Assignee: Giuseppe Landolfi Components: remoting, slave-setup-plugin Created: 2016/Oct/25 8:15 AM Priority: Critical Reporter: Pavel Kudrys Hi, I'm unable to start/connect slave machine, using JNLP, after installing version 2.27 on master + new 3.0 slave.jar on slave computer. Installed Java 1.8.111. I've enabled Java Web Start agent 3 and 4 in Configure Global Security, but to no avail. All I'm getting is an error "Local headers refused by remote: CPRAN03 is not a JNLP agent" followed by number of exceptions and even version 3 and 2 of JNLP agent fails to start. Is there something else I need to configure in latest Jenkins 2.27? C:\Jenkins>call "C:\Program Files (x86)\Java\jre1.8.0_111\bin\java.exe" -Xrs -ja r "slave.jar" -jnlpUrl http://cpjen01:8090/computer/CPRAN03/slave-agent.jnlp -se cret "secretkey" Oct 25, 2016 7:58:00 AM hudson.remoting.jnlp.Main createEngine INFO: Setting up slave: CPRAN03 Oct 25, 2016 7:58:00 AM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode. Oct 25, 2016 7:58:00 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among http://cpjen01:8090/ Oct 25, 2016 7:58:00 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Agent discovery successful Agent address: cpjen01 Agent port: 49274 Identity: ab:f2:5f:d6:32:a6:42:71:fc:d8:9f:9a:05:0c:77:d0 Oct 25, 2016 7:58:00 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Handshaking Oct 25, 2016 7:58:00 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to cpjen01:49274 Oct 25, 2016 7:58:00 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Trying protocol: JNLP4-connect Oct 25, 2016 7:58:00 AM hudson.remoting.jnlp.Main$CuiListener
[JIRA] (JENKINS-36085) vSphere 2.13 causes error while restarting VM
Title: Message Title Pavel Kudrys commented on JENKINS-36085 Re: vSphere 2.13 causes error while restarting VM Am I alone who is experiencing this issue? I've just updated Jenkins with latest 2.25 and all plugins. vSphere plugin v. 2.13 still fails to restart VMs with this error: "ERROR: no workspace for 'name-of-job'". V 2.12 works as expected. 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-36085) vSphere 2.13 causes error while restarting VM
Title: Message Title Pavel Kudrys created an issue Jenkins / JENKINS-36085 vSphere 2.13 causes error while restarting VM Issue Type: Bug Assignee: Unassigned Components: vsphere-cloud-plugin Created: 2016/Jun/20 8:12 AM Labels: vsphere Priority: Major Reporter: Pavel Kudrys Hi, I have a very simple vSphere-based job, where I just shutdown and power-on a VM (on a daily basis). Since installing 2.13, the job started to fail somewhere after the shutdown step with error "ERROR: no workspace for 'name-of-job'". I've downgraded to 2.12 and it works fine again. This is what I see in console with 2.13: Started by user username Building remotely on CPRAN01 (CPRAN01_lbl) in workspace c:\Jenkins\workspace\Restart CPRAN01 [vSphere] [vSphere] Performing vSphere build step: "Power-Off VM" [vSphere] Attempting to use server configuration: "DCvSphere - wlcavc03" [vSphere] Shutting Down VM CPRAN01... [vSphere] Successfully shutdown "CPRAN01" ERROR: no workspace for Restart CPRAN01 #132 Finished: FAILURE And this is what I see with 2.12: Started by user username Building remotely on CPRAN01 (CPRAN01_lbl) in workspace c:\Jenkins\workspace\Restart CPRAN01 [vSphere] [vSphere] Performing vSphere build step: "Power-Off VM" [vSphere] Attempting to use server configuration: "DCvSphere - wlcavc03" [vSphere] Shutting Down VM CPRAN01... [vSphere] Successfully shutdown "CPRAN01" [vSphere] [vSphere] Performing vSphere build step: "Power-On/Resume VM" [vSphere] Attempting to use server configuration:
[JIRA] (JENKINS-35699) xunit hangs (on one particular slave) after upgrading Jenkins from 2.6 to 2.9
Title: Message Title Pavel Kudrys updated an issue Jenkins / JENKINS-35699 xunit hangs (on one particular slave) after upgrading Jenkins from 2.6 to 2.9 Change By: Pavel Kudrys Hi,I've recently updated Jenkins to 2.9 (from 2.6), including all slave.jars and all plugins with their most recent versions. All of suddenly, job started at one particular slave hangs at xunit processing, which worked OK so far. This is what I see in job console:...Build step 'Conditional steps (multiple)' marked build as failureArchiving artifacts\[xUnit\] \[INFO\] - Starting to record.\[xUnit\] \[INFO\] - Processing Custom Tool\[xUnit\] \[INFO\] - \[Custom Tool\] - 1 test report file(s) were found with the pattern 'Reports\unpacked\*_build-5481.rxlog.data' relative to 'c:\Jenkins\workspace\SecurexMonitoring' for the testing framework 'Custom Tool'.From time to time, the xunit processing finishes after unusually long period of time. But in most cases, I need to kill the job manually, because it blocks other jobs. Virtually the same works fine on two other slave machines. The only difference between the slaves is that the not-working one is located in different data center. But it was there also before. The response time of the problematic slave is around 150ms, so it should not be an issue either? Jenkins configuration should be the same on all three slaves. Once I kill the 'hanged' job, it throws this exception to master console:Jun 14, 2016 12:45:27 PM WARNING hudson.model.AbstractBuild$AbstractBuildExecution reportErrorStep ‘Publish xUnit test result report’ aborted due to exception: java.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:147) at hudson.remoting.Channel.call(Channel.java:780) at hudson.FilePath.act(FilePath.java:1007) at hudson.FilePath.act(FilePath.java:996) at org.jenkinsci.plugins.xunit.XUnitProcessor.performTests(XUnitProcessor.java:145) at org.jenkinsci.plugins.xunit.XUnitProcessor.performXUnit(XUnitProcessor.java:88) at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:142) at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:134) 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:1745) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Any idea what could be the cause of this problem or what to try to fix it? Feel free to let me know if you need more details.PS: added slave thread dump
[JIRA] (JENKINS-35699) xunit hangs (on one particular slave) after upgrading Jenkins from 2.6 to 2.9
Title: Message Title Pavel Kudrys updated an issue Jenkins / JENKINS-35699 xunit hangs (on one particular slave) after upgrading Jenkins from 2.6 to 2.9 Change By: Pavel Kudrys Attachment: cpran02_thread_dump.txt 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-35699) xunit hangs (on one particular slave) after upgrading Jenkins from 2.6 to 2.9
Title: Message Title Pavel Kudrys created an issue Jenkins / JENKINS-35699 xunit hangs (on one particular slave) after upgrading Jenkins from 2.6 to 2.9 Issue Type: Bug Assignee: Gregory Boissinot Components: xunit-plugin Created: 2016/Jun/14 1:05 PM Labels: xunit Priority: Major Reporter: Pavel Kudrys Hi, I've recently updated Jenkins to 2.9 (from 2.6), including all slave.jars and all plugins with their most recent versions. All of suddenly, job started at one particular slave hangs at xunit processing, which worked OK so far. This is what I see in job console: ... Build step 'Conditional steps (multiple)' marked build as failure Archiving artifacts [xUnit] [INFO] - Starting to record. [xUnit] [INFO] - Processing Custom Tool [xUnit] [INFO] - [Custom Tool] - 1 test report file(s) were found with the pattern 'Reports\unpacked*_build-5481.rxlog.data' relative to 'c:\Jenkins\workspace\SecurexMonitoring' for the testing framework 'Custom Tool'. From time to time, the xunit processing finishes after unusually long period of time. But in most cases, I need to kill the job manually, because it blocks other jobs. Virtually the same works fine on two other slave machines. The only difference between the slaves is that the not-working one is located in different data center. But it was there also before. The response time of the problematic slave is around 150ms, so it should not be an issue either? Jenkins configuration should be the same on all three slaves. Once I kill the 'hanged' job, it throws this exception to master console: Jun 14, 2016 12:45:27 PM WARNING hudson.model.AbstractBuild$AbstractBuildExecution reportError Step ‘Publish xUnit test result report’ aborted due to exception: java.lang.InterruptedException at java.lang.Object.wait(Native Method) at
[JIRA] [dashboard-view-plugin] (JENKINS-35268) Test Trend Chart - number of displayed days differ for each view
Title: Message Title Pavel Kudrys commented on JENKINS-35268 Re: Test Trend Chart - number of displayed days differ for each view Thanks for your investigation. Well, I have "Discard old builds" enabled in each job, however, Days to keep builds/Artifacts option is set to between 30 and 61 days (depending of project). And if I examine the build history, I still see at least one month old records. So the problem should not be caused by deleted build records? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view-plugin] (JENKINS-35298) Test Trend Chart and Statistics Chart shows "0" failed tests
Title: Message Title Pavel Kudrys created an issue Jenkins / JENKINS-35298 Test Trend Chart and Statistics Chart shows "0" failed tests Issue Type: Bug Assignee: Evan Van Dyke Attachments: TestTrendChart_history_3.png Components: dashboard-view-plugin Created: 2016/Jun/02 10:23 AM Priority: Major Reporter: Pavel Kudrys Test Trend Chart and Statistics Chart shows "0" failed tests but there were failures during the days displayed in both chart. Please see the screenshot, which shows dashboard's Test Trend chart compared to "Build History" and xUnit's "Test Result Trend" chart, which shows two failures... I'm experiencing also another problem (maybe related), which shows only small amount of days in Test Trend Chart. I've posted about it here: https://issues.jenkins-ci.org/browse/JENKINS-35268
[JIRA] [dashboard-view-plugin] (JENKINS-35268) Test Trend Chart - number of displayed days differ for each view
Title: Message Title Pavel Kudrys commented on JENKINS-35268 Re: Test Trend Chart - number of displayed days differ for each view Thanks for the reply. I've installed and configured the dashboard plugin yesterday and it showed range 31.5. to 1.6. Today, the graph shows range 31.5 to 2.6. This apply for all jobs, which runs 24/7. Some of them runs every 15 minutes, some of them every 30 minutes. So there is between 48 to 96 builds each day (per job) Could "too many builds" per day have something to do with this problem? The only graph, which now shows 8 days (9 today) is for job, which runs at least once a day (usually 2-3 times). But even this job runs each day and there is definitely history of builds longer than one month. But yes, in this case, builds for some days are skipped. For example, I see builds between 23-27.5 and then between 30.5.-1.6. However, the Test Trend Chart shows range between 25.5 to 2.6. (even though there are no builds for 28-29.5 and 2.6. yet?). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view-plugin] (JENKINS-35268) Test Trend Chart - number of displayed days differ for each view
Title: Message Title Pavel Kudrys updated an issue Jenkins / JENKINS-35268 Test Trend Chart - number of displayed days differ for each view Change By: Pavel Kudrys Attachment: TestTrendChart_history_2.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view-plugin] (JENKINS-35268) Test Trend Chart - number of displayed days differ for each view
Title: Message Title Pavel Kudrys created an issue Jenkins / JENKINS-35268 Test Trend Chart - number of displayed days differ for each view Issue Type: Bug Assignee: Evan Van Dyke Attachments: TestTrendChart_history.png Components: dashboard-view-plugin Created: 2016/Jun/01 2:19 PM Priority: Major Reporter: Pavel Kudrys I have 3 different views, each view contains between 1-3 test jobs. The Test Trend Chart shows just one day for two views (with 2 or 3 test jobs), while the Test Trend Chart in one particular view shows 8 days? However, neither number of days reflects "Number of (latest) days to display", which I have 14 days for each view? So based of which number/Jenkins setting does Test Trend Chart display its history? Add Comment
[JIRA] [dashboard-view-plugin] (JENKINS-35266) "Hide projects with no tests" option resets to unchecked state
Title: Message Title Pavel Kudrys created an issue Jenkins / JENKINS-35266 "Hide projects with no tests" option resets to unchecked state Issue Type: Bug Assignee: Evan Van Dyke Components: dashboard-view-plugin Created: 2016/Jun/01 1:12 PM Priority: Minor Reporter: Pavel Kudrys "Hide projects with no tests" option (in Test Statistics Grid) resets to unchecked state after each attempt to edit view. *Steps to reproduce: go to view settings in Test Statistics Grid check "Hide projects with no tests" option save view >> projects with 0 tests are hidden try to edit view again >> "Hide projects with no tests" option is unchecked
[JIRA] [core] (JENKINS-33048) add ability to archive artifacts only on FAILURE
Title: Message Title Pavel Kudrys commented on JENKINS-33048 Re: add ability to archive artifacts only on FAILURE Hi, I'm looking for such option (to archive artifacts only for FAILED builds) as well. Most of my Jenkins jobs are in fact automated tests, for which I don't really need to save 'success' artifacts (reports). Currently, there is no such option and stored artifacts make my jobs bloated with unnecessary files (only small fraction of daily test fail). Any chance to have such option? Thank you in advance! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-13663) Allow use of credentials from Credentials Plugin
Title: Message Title Pavel Kudrys commented on JENKINS-13663 Re: Allow use of credentials from Credentials Plugin Hi, Another vote for Credentials Plugin support! It would be really helpful and time saving to be able to use credentials stored in Jenkins. For me, it means I need to update each job every few months because of expiring domain password, which we are using also for TFS access. Credentials plugin support would allow me to change password just once. Thank you in advance for considering this request! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multiple-scms-plugin] (JENKINS-27582) TFS configuration not loaded/displayed in MultipleSCM configuration view
Pavel Kudrys created JENKINS-27582 TFS configuration not loaded/displayed in MultipleSCM configuration view Issue Type: Bug Assignee: Kevin Bell Attachments: TFS.png Components: multiple-scms-plugin Created: 25/Mar/15 8:44 AM Description: Hi, It seems that the previously saved TFS configuration is not loaded/displayed in the MultipleSCM configuration view? It's possible to add a new TFS configuration and it appears to be written to the job config. The job even runs OK. But when you reload the job configuration, the previously saved TFS settings are not displayed. See the attached screenshot. Have a nice day, Pavel Project: Jenkins Labels: plugin multiple-scms tfs Priority: Major Reporter: Pavel Kudrys This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multiple-scms-plugin] (JENKINS-27582) TFS configuration not loaded/displayed in MultipleSCM configuration view
Pavel Kudrys commented on JENKINS-27582 TFS configuration not loaded/displayed in MultipleSCM configuration view I just noticed there is a similar issue reported with GIT? See https://issues.jenkins-ci.org/browse/JENKINS-26645. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [slave-status] (JENKINS-22741) Slaves randomly not started/connected after updating Jenkins to 1.560 and slave.jar to 2.39
Pavel Kudrys created JENKINS-22741 Slaves randomly not started/connected after updating Jenkins to 1.560 and slave.jar to 2.39 Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: slave_connection_error.png Components: slave-status Created: 24/Apr/14 6:45 AM Description: Hi, After updating Jenkins with the latest 1.560 and slave.jar (on all slave machines) with latest 2.39, I'm experiencing some random connection problems. Slaves are either not started at all or they are started but not connected and jobs endlessly wait for available executors. Here are some screenshots with errors I see after examining the pending job slaves... The truth is, that the slave machine is long time turned off (turns off 5 minutes after last finished build), so the message about "ignoring connection attempt because the machine is being shut down" is completely senseless. In some cases, it helps to turn the machine ON manually. After that, the connection is (usually) established. But sometimes not. All worked OK with 1.559 and slave.jar 2.32. Environment: WinXP 32/64 Project: Jenkins Priority: Major Reporter: Pavel Kudrys This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [shelve-project-plugin] (JENKINS-8063) Seemingly harmless stacktrace when shelving/unshelving projects in Hudson 1.383 and 1.384
Pavel Kudrys commented on JENKINS-8063 Seemingly harmless stacktrace when shelving/unshelving projects in Hudson 1.383 and 1.384 Hi, Thanks for the superb news! Have a nice weekend, Pavel Kudrys This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [shelve-project-plugin] (JENKINS-8063) Seemingly harmless stacktrace when shelving/unshelving projects in Hudson 1.383 and 1.384
Pavel Kudrys commented on JENKINS-8063 Seemingly harmless stacktrace when shelving/unshelving projects in Hudson 1.383 and 1.384 Problem still reproducible with the actual release version of Shelve plugin (ver. 1.4.4) and Jenkins ver. 1.559. Any chance to see it fixed anytime soon? Thank you in advance! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-20750) Git plugin 2.0 sometimes fail to fetch (timeouts) with weird error
Pavel Kudrys commented on JENKINS-20750 Git plugin 2.0 sometimes fail to fetch (timeouts) with weird error I agree with Michael that this problem has something to do with concurrent processes. I guess it has something to do with GIT pooling? The solution that worked for me was switching to Jenkins Credentials! Previously, I did not use credential stored in Jenkins. Since I stored the GIT credentials in Jenkins and I set those credentials in GIT plugin, all works OK! So far, I experienced only one fetch timeout with the same error as before and sure enough, there was multiple instances of git running at the same time. Once I killed them, all operations returned back to normal. In my opinion, there is something wrong either in Jenskin or GIT plugin. A question worth of a million is, what could be a reason of such behavior? In any case, switching to Jenkins Credentials seems minimize the error rate to minimum. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20750) Git plugin 2.0 sometimes fail to fetch (timeouts) with weird error
Pavel Kudrys updated JENKINS-20750 Git plugin 2.0 sometimes fail to fetch (timeouts) with weird error Change By: Pavel Kudrys (08/Jan/14 7:02 AM) Attachment: GIT_proc.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20750) Git plugin 2.0 sometimes fail to fetch (timeouts) with weird error
Pavel Kudrys commented on JENKINS-20750 Git plugin 2.0 sometimes fail to fetch (timeouts) with weird error I've updated Jenkins as well as Jenkins GIT plugin and GIT itself, but nothing helped. I also increased the GIT plugin timeout to one hour (using -Dorg.jenkinsci.plugins.gitclient.Git.timeOut=60 parameter) but no change either. Simply, the jobs sometimes run, but most often, they fail with the above mentioned error. What I found really weird, and what's probably connected to this issue, is the number of git.exe/ssh.exe processes, which stay open (see the attached screenshot). All of these processes point to the (failed) Jenkins jobs. If I kill all these "hanged" processes, and then manually run the jobs, they all work! I found this discussion, where is mentioned a "workaround" to kill the SCM processes... http://stackoverflow.com/questions/10732940/git-operations-occasionally-hang-in-jenkins-on-windows The problem is that it kills all processes, so it's useless in my case, because I don't want to kill processes from working builds. Any other idea? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20750) Git plugin 2.0 sometimes fail to fetch (timeouts) with weird error
Pavel Kudrys created JENKINS-20750 Git plugin 2.0 sometimes fail to fetch (timeouts) with weird error Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git Created: 25/Nov/13 9:31 AM Description: Last week I started to experience some weird problems with the GIT fetch. As far as I remember, I did not update Jenkins or any of its plugins and I'm also not aware of any company GIT/networks changes. All of sudden, jobs started to fail fetching. And the problem is it happens randomly. Sometimes it works as before, sometimes it don't. Here is a typical error I'm getting: Started by timer Building on master in workspace C:\Documents and Settings\Tester\.jenkins\jobs\litebox3d_tiff_32_64\workspace Updating svn://krivan/Ranorex/trunk/xSpector at revision '2013-11-25T02:14:53.975 +0100' At revision 260 no change for svn://krivan/Ranorex/trunk/xSpector since the previous build Fetching changes from the remote Git repository Fetching upstream changes from git@swserv:litebox3d ERROR: Timeout after 10 minutes FATAL: Failed to fetch from git@swserv:litebox3d hudson.plugins.git.GitException: Failed to fetch from git@swserv:litebox3d at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:612) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:836) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:861) at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:117) at hudson.model.AbstractProject.checkout(AbstractProject.java:1412) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:557) at hudson.model.Run.execute(Run.java:1679) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:304) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) at hudson.model.OneOffExecutor.run(OneOffExecutor.java:43) Caused by: hudson.plugins.git.GitException: Command "fetch -t git@swserv:litebox3d +refs/heads/:refs/remotes/origin/" returned status code -1: stdout: stderr: Could not create directory 'c/Documents and Settings/Tester/.ssh'. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:981) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:920) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.fetch(CliGitAPIImpl.java:187) at hudson.plugins.git.GitAPI.fetch(GitAPI.java:229) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:610) ... 12 more It does not happen always! Just from time to time, but enought frequently to break our build/test workflow. What's really weird is this error: stderr: Could not create directory 'c/Documents and Settings/Tester/.ssh'. Please notice the missing colon character in the path! In any case, the pointed path exists (of course, only if the colon is available) so there should be no reason for such error, except if the reason is missing colon? But then why it does not happen always? I also noticed, that after this failure, it's impossible to manually delete the content of the workspace/.git folder, because of some locked files. And it does not help to just stop Jenkins. The machine must be restarted to be able to delete the remaining files. I'm aware of the issue JENKINS-20445 (too small Git plugin timeout) and while it appears to be also my problem, the reason/source of problem seems to something else? Up to last week, I never experienced such timeout problem. Please don't hesitate to contact me in case of questions regarding our jenkins/jobs setup. Project: Jenkins Priority: Major Reporter:
[JIRA] [slave-status] (JENKINS-19445) Jobs randomly stuck with building remotely on slave-name message
Pavel Kudrys commented on JENKINS-19445 Jobs randomly stuck with building remotely on slave-name message Hi Valentin, We are running it on Winstone. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-18995) GIT changelog shows all changes since first day
Pavel Kudrys created JENKINS-18995 GIT changelog shows all changes since first day Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Attachments: GITClientPlug.png Components: git-client Created: 30/Jul/13 6:37 AM Description: Since installing GIT Client plugin version 1.1 (and updated 1.1.1), Jenkins job now shows all changes since we started with GIT. See the attached picture (there is about 500 changes). It's quite annoying problem. All is OK after replacing the actual GIT Client plugin (1.1.1) with version 1.0.7. It's good workaround, but definitely not a permanent solution The job we are using consists of two building slaves. And the interesting point is, that the change log looks fine on 64bit slave (only changes since the previous build are shown), but on 32bit slave (and Jenkins Master machine) it shows all changes since start. Feel free to contact me in case you need more details. Project: Jenkins Priority: Major Reporter: Pavel Kudrys This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18332) Builds disappear from the history of slave builds (both from the HDD and GUI)
Pavel Kudrys updated JENKINS-18332 Builds disappear from the history of slave builds (both from the HDD and GUI) Change By: Pavel Kudrys (13/Jun/13 11:42 AM) Description: Hello,ImusingJenkinsv1.517andImexperiencingaproblemwithdisappearinghistoryofslavebuilds.Allbuildsareavailableinjobname\builds\folder,however,thehistoryofslavebuildsinjobname\configurations\axis-name\workspacename\builds\isperiodicallypurged.Someolderjobssimplydisappearsfromthelistofbuilds(physicallydisappearsfromtheHDDandGUI).Pleaseseetheattachedscreenshots(disappearedhistoryofbuildsonslavemachine)fromlastweekandfromtoday.Icheckedthehistoryyesterdayandtherewereallbuildsfrom8.6.to12.6.Today,thereareonlybuildsfrom11.6.to13.6.Icantfindanythingwronginthebuildlogspointingtothehistorypurge.Anyideawhatcouldbeacauseofthehistorydeletion?IsthereasettinginJenkinsthatcouldcausethepurgeofbuildhistory?Hereis a the listofinstalledpluginsandtheirversions...ant 1.2backup 1.6.1chucknorris 0.5conditional-buildstep 1.2.2credentials 1.4cvs 2.9email-ext 2.30.2external-monitor-job 1.1git 1.4.0git-client 1.0.6javadoc 1.1jira 1.35ldap 1.4mailer 1.5maven-plugin 1.517msbuild 1.17multiple-scms 0.2pam-auth 1.1run-condition 0.10ssh-credentials 0.3ssh-slaves 0.25subversion 1.50token-macro 1.7translation 1.10vmware 0.8vsphere-cloud 0.10Thankyouinadvance!PavelKudrys This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18332) Builds disappear from the history of slave builds (both from the HDD and GUI)
Pavel Kudrys created JENKINS-18332 Builds disappear from the history of slave builds (both from the HDD and GUI) Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: Jenkins_lost_build_history_10_06_13.png, Jenkins_lost_build_history_13_06_13.png Components: core Created: 13/Jun/13 11:41 AM Description: Hello, I'm using Jenkins v 1.517 and I'm experiencing a problem with disappearing history of slave builds. All builds are available in jobname\builds\ folder, however, the history of slave builds in jobname\configurations\axis-name\workspacename\builds\ is "periodically" purged. Some older jobs simply disappears from the list of builds (physically disappears from the HDD and GUI). Please see the attached screenshots (disappeared history of builds on slave machine) from last week and from today. I checked the history yesterday and there were all builds from 8.6. to 12.6. Today, there are only builds from 11.6. to 13.6. I can't find anything wrong in the build logs pointing to the history purge. Any idea what could be a cause of the history deletion? Is there a setting in Jenkins that could cause the purge of build history? Here is a list of installed plugins and their versions... ant 1.2 backup 1.6.1 chucknorris 0.5 conditional-buildstep 1.2.2 credentials 1.4 cvs 2.9 email-ext 2.30.2 external-monitor-job 1.1 git 1.4.0 git-client 1.0.6 javadoc 1.1 jira 1.35 ldap 1.4 mailer 1.5 maven-plugin 1.517 msbuild 1.17 multiple-scms 0.2 pam-auth 1.1 run-condition 0.10 ssh-credentials 0.3 ssh-slaves 0.25 subversion 1.50 token-macro 1.7 translation 1.10 vmware 0.8 vsphere-cloud 0.10 Thank you in advance! Pavel Kudrys Environment: VMWare VM WinXP 32/64 Project: Jenkins Labels: builds history slaves Priority: Critical Reporter: Pavel Kudrys This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15156) Builds disappear from build history after completion
Pavel Kudrys updated JENKINS-15156 Builds disappear from build history after completion This screenshot shows disappeared history of builds on slave machine. Change By: Pavel Kudrys (10/Jun/13 6:43 AM) Attachment: Jenkins_lost_build_history.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15156) Builds disappear from build history after completion
Pavel Kudrys edited a comment on JENKINS-15156 Builds disappear from build history after completion Hello, I'm using Jenkins v 1.517 and I'm experiencing a very similar (if not the same) problem. All builds are visible on the master machine but older builds, from time to time, simply disappears from the list of builds on the slave machine. Please see the attached screenshot (disappeared history of builds on slave machine). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15156) Builds disappear from build history after completion
Pavel Kudrys edited a comment on JENKINS-15156 Builds disappear from build history after completion Hello, I'm using Jenkins v 1.517 and I'm experiencing a very similar (if not the same) problem. All builds are visible on the master machine but older builds, from time to time, simply disappears from the list of builds on the slave machine. Is this problem fixed in actual or upcoming version? Please see the attached screenshot (disappeared history of builds on slave machine). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15156) Builds disappear from build history after completion
Pavel Kudrys commented on JENKINS-15156 Builds disappear from build history after completion @Jesse thanks for the reply. OK, I will keep an eye on this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13563) Attachment filepath does not support token reference
Pavel Kudrys commented on JENKINS-13563 Attachment filepath does not support token reference Hi, I'm sorry for bringing this subject back, but can I ask when we can see this feature back in a release version? Thank you in advance. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13563) Attachment filepath does not support token reference
Pavel Kudrys commented on JENKINS-13563 Attachment filepath does not support token reference Great news! Thanks for your effort. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13563) Attachment filepath does not support token reference
Pavel Kudrys commented on JENKINS-13563 Attachment filepath does not support token reference Hi, I'm new to Jenkins and I just hit on the same problem, as if some tokens are still not supported in the attachment field? Or maybe I'm using it in a wrong way? I'm using this path in the attachment field... Reports/Report_$BUILD_NUMBER.rxzlog where the $BUILD_NUMBER is supposed to translate to the build number. This variable works OK in other fields, but not in the attachment field. The file is correctly attached only if I replace the $BUILD_NUMBER variable with the number. But as you can imagine, it's not ideal solution as the number of the .rxzlog file changes with every build. I'm using Jenkins ver. 1.496. Thanks in advance! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13563) Attachment filepath does not support token reference
Pavel Kudrys commented on JENKINS-13563 Attachment filepath does not support token reference Hi, Thank you for the reply! So the BUILD_NUMBER token is not allowed in the way I used it? Could you please suggest me the correct ANT pattern using the BUILD_NUMBER token? Yes, there are multiple rxzlog in the workspace (new rxzlog is created with every new build). At the moment, I prefer to keep them all in the Reports folder. Therefore, I can't use path with *.rxzlog or similar wildcards. Have a nice day, Pavel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13563) Attachment filepath does not support token reference
Pavel Kudrys edited a comment on JENKINS-13563 Attachment filepath does not support token reference Hi, Thank you for the reply! So the BUILD_NUMBER token is not allowed in the way I used it? Could you please suggest me the correct ANT pattern using the BUILD_NUMBER token? Yes, there are multiple rxzlog in the workspace (new rxzlog is created with every build). At the moment, I prefer to keep them all in the Reports folder. Therefore, I can't use path with *.rxzlog or similar wildcard. Have a nice day, Pavel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
