[JIRA] (JENKINS-59636) timestamper shows wrong time on [View as plain text] link
Title: Message Title Vassilena Treneva commented on JENKINS-59636 Re: timestamper shows wrong time on [View as plain text] link Basil Crow, which version of the plugin stands for 52? We are currently using 1.10 and I see an update to 1.11 is available (so I am assuimg 52 maps to some other release version ) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202318.1570086045000.6817.1582705200258%40Atlassian.JIRA.
[JIRA] (JENKINS-59636) timestamper shows wrong time on [View as plain text] link
Title: Message Title
Vassilena Treneva updated an issue
Jenkins / JENKINS-59636
timestamper shows wrong time on [View as plain text] link
Change By:
Vassilena Treneva
The plugin shows correct timestamp when looking at the [Console Output:2019-10-03 01:28:35 Started by upstream project "10.7_release_pipeline" build number 89 2019-10-03 01:28:35 originally caused by: 2019-10-03 01:28:35 Started by timer 2019-10-03 01:28:36 Running in Durability level: PERFORMANCE_OPTIMIZED 2019-10-03 01:28:42 [Pipeline] Start of Pipeline 2019-10-03 01:28:42 [Pipeline] properties 2019-10-03 01:28:43 [Pipeline] timestamps 2019-10-03 01:28:43 The timestamps step is unnecessary when timestamps are enabled for all Pipeline builds. 2019-10-03 01:28:43 [Pipeline] { 2019-10-03 01:28:43 [Pipeline] library 2019-10-03 01:28:43 WARNING: Unknown parameter(s) found for class type 'jenkins.scm.impl.subversion.SubversionSCMSource': ignoreExternalsOption 2019-10-03 01:28:43 Loading library templates@branches/rel/10.7.0.x/build/change-management/jenkinsfiles/templatesBut when looking at the same build instance using [View as plain text] the timestamp is wrong:[2019-10-02T22:28:35.925Z] Started by upstream project "10.7_release_pipeline" build number 89 [2019-10-02T22:28:35.925Z] originally caused by: [2019-10-02T22:28:35.925Z] Started by timer [2019-10-02T22:28:36.043Z] Running in Durability level: PERFORMANCE_OPTIMIZED [2019-10-02T22:28:42.245Z] [Pipeline] Start of Pipeline [2019-10-02T22:28:42.703Z] [Pipeline] properties [2019-10-02T22:28:43.191Z] [Pipeline] timestamps [2019-10-02T22:28:43.191Z] The timestamps step is unnecessary when timestamps are enabled for all Pipeline builds. [2019-10-02T22:28:43.192Z] [Pipeline] { [2019-10-02T22:28:43.404Z] [Pipeline] library [2019-10-02T22:28:43.416Z] WARNING: Unknown parameter(s) found for class type 'jenkins.scm.impl.subversion.SubversionSCMSource': ignoreExternalsOption [2019-10-02T22:28:43.448Z] Loading library templates@branches/rel/10.7.0.x/build/change-management/jenkinsfiles/templatesThe timestamper is enabled for all pipeline build and has the following formating: ''-MM-dd HH:mm:ss' ' which appears correct in the [Console Output] but not in [View as plain text]We have the following java argument added to our master configuration: JAVA_ARGS="-Dorg.apache.commons.jelly.tags.fmt.timeZone=Europe/Sofia" The hardware clock of the VM on which the master is hosted ouputs correct timing as well: sudo hwclock --showThu 03 Oct 2019 10:03:11 AM EEST -0.355352 seconds dateThu Oct 3 10:04:14 EEST 2019 I wonder where is the wrong timestamp read from?Perhaps, if I knew I would be able to work around the issue by changing some system settings. Browsing the console text with correct timestamps is quite important especially when you have big outputs in general...
[JIRA] (JENKINS-59636) timestamper shows wrong time on [View as plain text] link
Title: Message Title
Vassilena Treneva updated an issue
Jenkins / JENKINS-59636
timestamper shows wrong time on [View as plain text] link
Change By:
Vassilena Treneva
The plugin shows correct timestamp when looking at the [Console Output:2019-10-03 01:28:35 Started by upstream project "10.7_release_pipeline" build number 892019-10-03 01:28:35 originally caused by:2019-10-03 01:28:35 Started by timer2019-10-03 01:28:36 Running in Durability level: PERFORMANCE_OPTIMIZED2019-10-03 01:28:42 [Pipeline] Start of Pipeline2019-10-03 01:28:42 [Pipeline] properties2019-10-03 01:28:43 [Pipeline] timestamps2019-10-03 01:28:43 The timestamps step is unnecessary when timestamps are enabled for all Pipeline builds.2019-10-03 01:28:43 [Pipeline] {2019-10-03 01:28:43 [Pipeline] library2019-10-03 01:28:43 WARNING: Unknown parameter(s) found for class type 'jenkins.scm.impl.subversion.SubversionSCMSource': ignoreExternalsOption2019-10-03 01:28:43 Loading library templates@branches/rel/10.7.0.x/build/change-management/jenkinsfiles/templates But when looking at the same build instance using [View as plain text] the timestamp is wrong:[2019-10-02T22:28:35.925Z] Started by upstream project "10.7_release_pipeline" build number 89[2019-10-02T22:28:35.925Z] originally caused by:[2019-10-02T22:28:35.925Z] Started by timer[2019-10-02T22:28:36.043Z] Running in Durability level: PERFORMANCE_OPTIMIZED[2019-10-02T22:28:42.245Z] [Pipeline] Start of Pipeline[2019-10-02T22:28:42.703Z] [Pipeline] properties[2019-10-02T22:28:43.191Z] [Pipeline] timestamps[2019-10-02T22:28:43.191Z] The timestamps step is unnecessary when timestamps are enabled for all Pipeline builds.[2019-10-02T22:28:43.192Z] [Pipeline] {[2019-10-02T22:28:43.404Z] [Pipeline] library[2019-10-02T22:28:43.416Z] WARNING: Unknown parameter(s) found for class type 'jenkins.scm.impl.subversion.SubversionSCMSource': ignoreExternalsOption[2019-10-02T22:28:43.448Z] Loading library templates@branches/rel/10.7.0.x/build/change-management/jenkinsfiles/templatesThe timestamper is enabled for all pipeline build and has the following formating: ''-MM-dd HH:mm:ss' ' which appears correct in the [Console Output] but not in [View as plain text]We have the following java argument added to our master configuration: JAVA_ARGS="-Dorg.apache.commons.jelly.tags.fmt.timeZone=Europe/Sofia" The hardware clock of the VM on which the master is hosted ouputs correct timing as well: sudo hwclock --showThu 03 Oct 2019 10:03:11 AM EEST -0.355352 seconds dateThu Oct 3 10:04:14 EEST 2019
[JIRA] (JENKINS-59636) timestamper shows wrong time on [View as plain text] link
Title: Message Title
Vassilena Treneva created an issue
Jenkins / JENKINS-59636
timestamper shows wrong time on [View as plain text] link
Issue Type:
Bug
Assignee:
Steven G Brown
Components:
timestamper-plugin
Created:
2019-10-03 07:00
Environment:
CentOS Linux release 7.6.1810 Jenkins ver. 2.195 Timestamper plugin v1.10
Priority:
Major
Reporter:
Vassilena Treneva
The plugin shows correct timestamp when looking at the [Console Output: 2019-10-03 01:28:35 Started by upstream project "10.7_release_pipeline" build number 89 2019-10-03 01:28:35 originally caused by: 2019-10-03 01:28:35 Started by timer 2019-10-03 01:28:36 Running in Durability level: PERFORMANCE_OPTIMIZED 2019-10-03 01:28:42 [Pipeline] Start of Pipeline 2019-10-03 01:28:42 [Pipeline] properties 2019-10-03 01:28:43 [Pipeline] timestamps 2019-10-03 01:28:43 The timestamps step is unnecessary when timestamps are enabled for all Pipeline builds. 2019-10-03 01:28:43 [Pipeline] { 2019-10-03 01:28:43 [Pipeline] library 2019-10-03 01:28:43 WARNING: Unknown parameter(s) found for class type 'jenkins.scm.impl.subversion.SubversionSCMSource': ignoreExternalsOption 2019-10-03 01:28:43 Loading library templates@branches/rel/10.7.0.x/build/change-management/jenkinsfiles/templates But when looking at the same build instance using [View as plain text] the timestamp is wrong: [2019-10-02T22:28:35.925Z] Started by upstream project "10.7_release_pipeline" build number 89 [2019-10-02T22:28:35.925Z] originally caused by: [2019-10-02T22:28:35.925Z] Started by timer [2019-10-02T22:28:36.043Z] Running in Durability level: PERFORMANCE_OPTIMIZED [2019-10-02T22:28:42.245Z] [Pipeline] Start of Pipeline [2019-10-02T22:28:42.703Z] [Pipeline] properties [2019-10-02T22:28:43.191Z] [Pipeline] timestamps [2019-10-02T22:28:43.191Z] The
[JIRA] (JENKINS-44808) Unable to print stacktrace on jenkins pipeline
Title: Message Title Vassilena Treneva commented on JENKINS-44808 Re: Unable to print stacktrace on jenkins pipeline Peter Wein, The reason I wanted to catch the exception was a weird SVN checkout issue that I had – so I wanted to have a retry piece based on whether I have SVN exception or not. Thus I needed to know the type of the exception that occurs. Catching throwable is a bad approach but I did it initially until I figure out what is going in. (throwable covers exceptions as well as errors). Do not do it like me Try without a catch is probably another error in my script. workspaceDir is something that I set at the beginning of my script. Do you have a specific problem that you are trying to solve by asking me these questions? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.182865.1497172331000.1848.1568980860215%40Atlassian.JIRA.
[JIRA] (JENKINS-59201) jenkins shared libarry checkout causes [hudson.util.IOException2: revision check failed]
Title: Message Title
Vassilena Treneva updated an issue
Jenkins / JENKINS-59201
jenkins shared libarry checkout causes [hudson.util.IOException2: revision check failed]
Change By:
Vassilena Treneva
Every now and then, we get errors like the one below:{{ ERROR: Checkout failedERROR: Checkout failedorg.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:70) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:57) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:760) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:352) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:340) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:910) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:363) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:353) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.logImpl(DAVRepository.java:1003) at org.tmatesoft.svn.core.io.SVNRepository.log(SVNRepository.java:1041) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:181) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1239) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:968) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:873) at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:190)Caused: hudson.util.IOException2: revision check failed on http:///um/branches/rel/10.5.0.x/build/change-management/jenkinsfiles/templates at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:204) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:124) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:757) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:898) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.doRetrieve(SCMSourceRetriever.java:116) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.retrieve(SCMSourceRetriever.java:86) at org.jenkinsci.plugins.workflow.libs.LibraryAdder.retrieve(LibraryAdder.java:157) at org.jenkinsci.plugins.workflow.libs.LibraryStep$Execution.run(LibraryStep.java:207) at org.jenkinsci.plugins.workflow.libs.LibraryStep$Execution.run(LibraryStep.java:156) at
[JIRA] (JENKINS-59201) jenkins shared libarry checkout causes [hudson.util.IOException2: revision check failed]
Title: Message Title
Vassilena Treneva updated an issue
Jenkins / JENKINS-59201
jenkins shared libarry checkout causes [hudson.util.IOException2: revision check failed]
Change By:
Vassilena Treneva
Every now and then, we get errors like the one below: {{ Started by upstream project "10.5_release_pipeline" build number 266Started by upstream project "10.5_release_pipeline" build number 266originally caused by: Started by timerChecking out svn [http://svndae.apama.com:80/um/branches/rel/10.5.0.x//build/change-management/jenkinsfiles/sonar_cpp|http://svndae.apama.com/um/branches/rel/10.5.0.x//build/change-management/jenkinsfiles/sonar_cpp] into /FS/fslocal/jenkinsWorkspace/jobs/10.5_sonar_cpp/workspace@script to read JenkinsfileChecking out a fresh workspace because the workspace is not http://:80/um/branches/rel/10.5.0.x/build/change-management/jenkinsfiles/sonar_cppCleaning local Directory .Checking out http://:80/um/branches/rel/10.5.0.x/build/change-management/jenkinsfiles/sonar_cpp at revision '2019-09-03T03:36:12.694 +0200'A JenkinsfileAt revision 123796 No changes for http:///um/branches/rel/10.5.0.x/build/change-management/jenkinsfiles/sonar_cpp since the previous buildRunning in Durability level: PERFORMANCE_OPTIMIZED[Pipeline] properties[Pipeline] echoJenkins template functions will check out revision: @123796[Pipeline] libraryLoading library templates@branches/rel/10.5.0.x/build/change-management/jenkinsfiles/templates@123796Opening connection to http:///um/Updating http:///um/branches/rel/10.5.0.x/build/change-management/jenkinsfiles/templates@123796 at revision 123796U vars/pipelineBuilder.groovyAt revision 123796 ERROR: Checkout failedERROR: Checkout failedorg.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:70) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:57) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:760) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:352) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:340) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:910) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:363) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:353) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.logImpl(DAVRepository.java:1003) at org.tmatesoft.svn.core.io.SVNRepository.log(SVNRepository.java:1041) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:181) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at
[JIRA] (JENKINS-59201) jenkins shared libarry checkout causes [hudson.util.IOException2: revision check failed]
Title: Message Title Vassilena Treneva updated an issue Jenkins / JENKINS-59201 jenkins shared libarry checkout causes [hudson.util.IOException2: revision check failed] Change By: Vassilena Treneva Every now and then, we get errors like the one below: Started by upstream project "10.5_release_pipeline" build number 266Started by upstream project "10.5_release_pipeline" build number 266originally caused by: Started by timerChecking out svn [ http://svndae.apama.com:80/um/branches/rel/10.5.0.x//build/change-management/jenkinsfiles/sonar_cpp |http://svndae.apama.com/um/branches/rel/10.5.0.x//build/change-management/jenkinsfiles/sonar_cpp] into /FS/fslocal/jenkinsWorkspace/jobs/10.5_sonar_cpp/workspace@script to read JenkinsfileChecking out a fresh workspace because the workspace is not http://:80/um/branches/rel/10.5.0.x/build/change-management/jenkinsfiles/sonar_cppCleaning local Directory .Checking out http://:80/um/branches/rel/10.5.0.x/build/change-management/jenkinsfiles/sonar_cpp at revision '2019-09-03T03:36:12.694 +0200'A JenkinsfileAt revision 123796No changes for http:///um/branches/rel/10.5.0.x/build/change-management/jenkinsfiles/sonar_cpp since the previous buildRunning in Durability level: PERFORMANCE_OPTIMIZED[Pipeline] properties[Pipeline] echoJenkins template functions will check out revision: @123796[Pipeline] libraryLoading library templates@branches/rel/10.5.0.x/build/change-management/jenkinsfiles/templates@123796Opening connection to http:///um/Updating http:///um/branches/rel/10.5.0.x/build/change-management/jenkinsfiles/templates@123796 at revision 123796U vars/pipelineBuilder.groovyAt revision 123796ERROR: Checkout failedorg.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:70) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:57) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:760) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:352) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:340) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:910) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:363) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:353) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.logImpl(DAVRepository.java:1003) at org.tmatesoft.svn.core.io.SVNRepository.log(SVNRepository.java:1041) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:181) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1239)
[JIRA] (JENKINS-59201) jenkins shared libarry checkout causes [hudson.util.IOException2: revision check failed]
Title: Message Title Vassilena Treneva updated an issue Jenkins / JENKINS-59201 jenkins shared libarry checkout causes [hudson.util.IOException2: revision check failed] Change By: Vassilena Treneva Every now and then, we get errors like the one below: Started by upstream project "10.5_release_pipeline" build number 266Started by upstream project "10.5_release_pipeline" build number 266originally caused by: Started by timerChecking out svn [http://svndae.apama.com:80/um/branches/rel/10.5.0.x//build/change-management/jenkinsfiles/sonar_cpp|http://svndae.apama.com/um/branches/rel/10.5.0.x//build/change-management/jenkinsfiles/sonar_cpp] into /FS/fslocal/jenkinsWorkspace/jobs/10.5_sonar_cpp/workspace@script to read JenkinsfileChecking out a fresh workspace because the workspace is not http://:80/um/branches/rel/10.5.0.x/build/change-management/jenkinsfiles/sonar_cppCleaning local Directory .Checking out http://:80/um/branches/rel/10.5.0.x/build/change-management/jenkinsfiles/sonar_cpp at revision '2019-09-03T03:36:12.694 +0200'A JenkinsfileAt revision 123796 No changes for http:///um/branches/rel/10.5.0.x/build/change-management/jenkinsfiles/sonar_cpp since the previous buildRunning in Durability level: PERFORMANCE_OPTIMIZED[Pipeline] properties[Pipeline] echoJenkins template functions will check out revision: @123796[Pipeline] libraryLoading library templates@branches/rel/10.5.0.x/build/change-management/jenkinsfiles/templates@123796Opening connection to http:///um/Updating http:///um/branches/rel/10.5.0.x/build/change-management/jenkinsfiles/templates@123796 at revision 123796U vars/pipelineBuilder.groovyAt revision 123796 ERROR: Checkout failedorg.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:70) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:57) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:760) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:352) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:340) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:910) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:363) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:353) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.logImpl(DAVRepository.java:1003) at org.tmatesoft.svn.core.io.SVNRepository.log(SVNRepository.java:1041) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:181) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1239) at
[JIRA] (JENKINS-59201) jenkins shared libarry checkout causes [hudson.util.IOException2: revision check failed]
Title: Message Title Vassilena Treneva created an issue Jenkins / JENKINS-59201 jenkins shared libarry checkout causes [hudson.util.IOException2: revision check failed] Issue Type: Bug Assignee: Ivan Fernandez Calvo Attachments: consoleFull.txt, Jenkinsfile.txt Components: pipeline, subversion-plugin Created: 2019-09-03 08:31 Environment: Jenkins ver. 2.140 Subversion plugin 2.12.1 Other plugins: Pipeline: API Plugin that defines Pipeline API. 2.33Pipeline: Basic Steps Commonly used steps for Pipelines. 2.13Pipeline: Build Step Adds the Pipeline step build to trigger builds of other jobs. 2.7 Pipeline: Declarative An opinionated, declarative Pipeline. 1.3.3 Pipeline: Declarative Agent API Replaced by Pipeline: Declarative Extension Points API plugin. 1.1.1 Pipeline: Declarative Extension Points API APIs for extension points used in Declarative Pipelines. 1.3.3Pipeline: Groovy Pipeline execution engine based on continuation passing style transformation of Groovy scripts. 2.61Pipeline: Input Step Adds the Pipeline step input to wait for human input or approval. 2.8 Pipeline: Job Defines a new job type for pipelines and provides their generic user interface. 2.29Pipeline: Milestone Step Plugin that provides the milestone step 1.3.1 Pipeline: Model API Model API for Declarative Pipeline. 1.3.3Pipeline: Multibranch Enhances Pipeline plugin to handle branches better by automatically grouping builds from different branches. 2.20 Pipeline: Multibranch with defaults Enhances Pipeline plugin to handle branches better by automatically grouping builds from different branches. Supports enable one default pipeline 2.0 Pipeline: Nodes and Processes Pipeline steps locking agents and workspaces, and running external processes that may survive a Jenkins restart or slave reconnection. 2.26Pipeline: REST API Provides a REST API to access pipeline and pipeline run data. 2.10 Pipeline: SCM Step Adds a Pipeline step to check out or update working sources from various SCMs (version control). 2.7Pipeline: Shared Groovy Libraries Shared libraries for Pipeline scripts. 2.12 Pipeline: Stage Step Adds the Pipeline step stage to delineate portions of a build. 2.3 Pipeline: Stage Tags Metadata Library plugin for Pipeline stage tag metadata. 1.3.3Pipeline: Stage View Pipeline Stage View Plugin. 2.10 Pipeline: Step API API for
[JIRA] (JENKINS-58702) Wrong [Standard Output/Standard Error] published for test methods executed on different OS
Title: Message Title Vassilena Treneva updated an issue Jenkins / JENKINS-58702 Wrong [Standard Output/Standard Error] published for test methods executed on different OS Change By: Vassilena Treneva 1) We execute all our java classes on at least one windows and one linux platform. The platform type is echoed in the Standard Output of the junit xml file:Check files TEST-com.pcbsys.nirvana.client.durable.serial.nSerialDurableMiscTests-linux.xml and TEST-com.pcbsys.nirvana.client.durable.serial.nSerialDurableMiscTests-windows.xml and string search for: Starting Suite : The OS name is always printed out in Standard Output of the file2) Then we collect the results and publish them in a single place. Publication seems to work for the Stacktrace element, which shows the correct value, but not for the Standard Output/Standard Error elements which seem to be messed up. The screenshots attached here are showing how the aggreagated results view is shoding one and the same Standart Out/Err field, while the Stacktrace is unique. I think this is wrong and it should be showing unique Standart Out and Standart Error 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
[JIRA] (JENKINS-58702) Wrong [Standard Output/Standard Error] published for test methods executed on different OS
Title: Message Title Vassilena Treneva created an issue Jenkins / JENKINS-58702 Wrong [Standard Output/Standard Error] published for test methods executed on different OS Issue Type: Bug Assignee: Unassigned Attachments: aggregated-junitResult.xml, TEST-com.pcbsys.nirvana.client.durable.serial.nSerialDurableMiscTests-linux.xml, TEST-com.pcbsys.nirvana.client.durable.serial.nSerialDurableMiscTests-windows.xml, view_level_1_aggregared.png, view_level_2_linux_wrong.png, view_level_2_windows.png Components: junit-plugin Created: 2019-07-29 09:45 Environment: Master Jenkins ver. 2.140 JUnit plugin 1.24 Priority: Major Reporter: Vassilena Treneva 1) We execute all our java classes on at least one windows and one linux platform. The platform type is echoed in the Standard Output of the junit xml file: Check files TEST-com.pcbsys.nirvana.client.durable.serial.nSerialDurableMiscTests-linux.xml and TEST-com.pcbsys.nirvana.client.durable.serial.nSerialDurableMiscTests-windows.xml and string search for: Starting Suite: The OS name is always printed out in Standard Output of the file 2) Then we collect the results and publish them in a single place. Publication seems to work for the Stacktrace element, which shows the correct value, but not for the Standard Output/Standard Error elements which seem to be messed up.
[JIRA] (JENKINS-51979) subversion checkout fails with SAXException
Title: Message Title
Vassilena Treneva edited a comment on JENKINS-51979
Re: subversion checkout fails with SAXException
We are seeing quite often this (or maybe other?) problem.Jenkins ver. 2.140 Subversion Plug-in 2.12.1checkout([ $class: 'SubversionSCM', additionalCredentials: [[ credentialsId: 'TEST_USER', realm: 'http://:80/' ]], excludedCommitMessages: '', excludedRegions: '', excludedRevprop: '', excludedUsers: '', filterChangelog: false, ignoreDirPropChanges: false, includedRegions: '', locations: [[ cancelProcessOnExternalsFail: true, credentialsId: 'TEST_USER', depthOption: 'infinity', ignoreExternalsOption: true, local: '.', remote: "${svnBranch}@${buildNumber}" ]], quietOperation: false, workspaceUpdater: [$class: 'CheckoutUpdater']])11:48:15 Caught Throwable. Retrying operation... [Pipeline] echo 11:48:15 Exception type: class hudson.util.IOException2 [Pipeline] echo 11:48:15 Exception message: revision check failed on [Pipeline] echo Staktrace Stacktrace : [ hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:204) hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:124) hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:757) hudson.scm.SubversionSCM.checkout(SubversionSCM.java:898) org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50) hudson.security.ACL.impersonate(ACL.java:290) org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47) java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) java.util.concurrent.FutureTask.run(FutureTask.java:266) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) java.lang.Thread.run(Thread.java:748) ]
Add Comment
[JIRA] (JENKINS-51979) subversion checkout fails with SAXException
Title: Message Title
Vassilena Treneva edited a comment on JENKINS-51979
Re: subversion checkout fails with SAXException
We are seeing quite often this (or maybe other?) problem.Jenkins ver. 2.140 Subversion Plug-in 2.12.1checkout([ \{{ $class: 'SubversionSCM', }} \{{additionalCredentials: [[ }} \{{ credentialsId: 'TEST_USER', }} \{{realm: 'http://:80/' }} \{{ ]], }} \{{excludedCommitMessages: '', }} \{{excludedRegions: '', }} \{{excludedRevprop: '', }} \{{excludedUsers: '', }} \{{filterChangelog: false, }} \{{ignoreDirPropChanges: false, }} \{{includedRegions: '', }} \{{locations: [[ }} \{{ cancelProcessOnExternalsFail: true, }} \{{credentialsId: 'TEST_USER', }} \{{depthOption: 'infinity', }} \{{ignoreExternalsOption: true, }} \{{local: '.', }} \{{remote: "${svnBranch}@${buildNumber}" }} \{{ ]], }} \{{quietOperation: false, }} \{{workspaceUpdater: [$class: 'CheckoutUpdater'] }} ])11:48:15 Caught Throwable. Retrying operation... [Pipeline] echo 11:48:15 Exception type: class hudson.util.IOException2 [Pipeline] echo 11:48:15 Exception message: revision check failed on [Pipeline] echoStaktrace:[hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:204) hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:124) hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:757) hudson.scm.SubversionSCM.checkout(SubversionSCM.java:898) org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50) hudson.security.ACL.impersonate(ACL.java:290) org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47) java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) java.util.concurrent.FutureTask.run(FutureTask.java:266) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) java.lang.Thread.run(Thread.java:748)]
Add Comment
[JIRA] (JENKINS-51979) subversion checkout fails with SAXException
Title: Message Title
Vassilena Treneva commented on JENKINS-51979
Re: subversion checkout fails with SAXException
We are seeing quite often this (or maybe other?) problem. Jenkins ver. 2.140 Subversion Plug-in 2.12.1 checkout([ {{ $class: 'SubversionSCM', }} {{ additionalCredentials: [[}} {{ credentialsId: 'TEST_USER', }} {{ realm: 'http://:80/'}} {{ ]], }} {{ excludedCommitMessages: '', }} {{ excludedRegions: '', }} {{ excludedRevprop: '', }} {{ excludedUsers: '', }} {{ filterChangelog: false, }} {{ ignoreDirPropChanges: false, }} {{ includedRegions: '', }} {{ locations: [[}} {{ cancelProcessOnExternalsFail: true, }} {{ credentialsId: 'TEST_USER', }} {{ depthOption: 'infinity', }} {{ ignoreExternalsOption: true, }} {{ local: '.', }} {{ remote: "${svnBranch}@${buildNumber}"}} {{ ]], }} {{ quietOperation: false, }} {{ workspaceUpdater: [$class: 'CheckoutUpdater']}} ]) 11:48:15 Caught Throwable. Retrying operation... [Pipeline] echo 11:48:15 Exception type: class hudson.util.IOException2 [Pipeline] echo 11:48:15 Exception message: revision check failed on [Pipeline] echo Staktrace: [hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:204) hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:124) hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:757) hudson.scm.SubversionSCM.checkout(SubversionSCM.java:898) org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50) hudson.security.ACL.impersonate(ACL.java:290) org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47) java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) java.util.concurrent.FutureTask.run(FutureTask.java:266) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) java.lang.Thread.run(Thread.java:748)]
Add Comment
[JIRA] (JENKINS-51979) subversion checkout fails with SAXException
Title: Message Title
Vassilena Treneva edited a comment on JENKINS-51979
Re: subversion checkout fails with SAXException
We are seeing quite often this (or maybe other?) problem.Jenkins ver. 2.140Subversion Plug-in 2.12.1 {{^ checkout([ ^}} \ {{ ^ $class: 'SubversionSCM', ^ }} \ {{ ^ additionalCredentials: [[ ^ }} \ {{ ^ credentialsId: 'TEST_USER', ^ }} \ {{ ^ realm: 'http://:80/' ^ }} \ {{ ^ ]], ^ }} \ {{ ^ excludedCommitMessages: '', ^ }} \ {{ ^ excludedRegions: '', ^ }} \ {{ ^ excludedRevprop: '', ^ }} \ {{ ^ excludedUsers: '', ^ }} \ {{ ^ filterChangelog: false, ^ }} \ {{ ^ ignoreDirPropChanges: false, ^ }} \ {{ ^ includedRegions: '', ^ }} \ {{ ^ locations: [[ ^ }} \ {{ ^ cancelProcessOnExternalsFail: true, ^ }} \ {{ ^ credentialsId: 'TEST_USER', ^ }} \ {{ ^ depthOption: 'infinity', ^ }} \ {{ ^ ignoreExternalsOption: true, ^ }} \ {{ ^ local: '.', ^ }} \ {{ ^ remote: "${svnBranch}@${buildNumber}" ^ }} \ {{ ^ ]], ^ }} \ {{ ^ quietOperation: false, ^ }} \ {{ ^ workspaceUpdater: [$class: 'CheckoutUpdater'] ^ }} {{^ ]) ^}} 11:48:15 Caught Throwable. Retrying operation...[Pipeline] echo11:48:15 Exception type: class hudson.util.IOException2[Pipeline] echo11:48:15 Exception message: revision check failed on [Pipeline] echoStaktrace:[hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:204) hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:124) hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:757) hudson.scm.SubversionSCM.checkout(SubversionSCM.java:898) org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50) hudson.security.ACL.impersonate(ACL.java:290) org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47) java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) java.util.concurrent.FutureTask.run(FutureTask.java:266) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) java.lang.Thread.run(Thread.java:748)]
Add Comment
[JIRA] (JENKINS-44808) Unable to print stacktrace on jenkins pipeline
Title: Message Title
Vassilena Treneva commented on JENKINS-44808
Re: Unable to print stacktrace on jenkins pipeline
Constantin Bugneac, I managed to get this info like this: try {try { ws("${workspaceDirectory}") { checkout() } } catch (Throwable th) { echo 'Caught Throwable' echo 'Exception type: ' + th.getClass() echo 'Exception message: ' + th.getMessage() echo 'Exception stacktrace: ' + th.getStackTrace() as String[] }
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-44808) Unable to print stacktrace on jenkins pipeline
Title: Message Title
Vassilena Treneva edited a comment on JENKINS-44808
Re: Unable to print stacktrace on jenkins pipeline
Hey,What is the right way to redirect the stacktrace so that a user can see in the console log?I have this code: {code:java} // code placeholder try \ { try { checkout([$class: 'SubversionSCM', additionalCredentials: [], excludedCommitMessages: '', excludedRegions: '', excludedRevprop: '', excludedUsers: '', filterChangelog: false, ignoreDirPropChanges: false, includedRegions: '', locations: [[cancelProcessOnExternalsFail: true, credentialsId: 'nirdevadm', depthOption: 'infinity', ignoreExternalsOption: true, local: '.', remote: "${params.branch}@${params.revision}"], [cancelProcessOnExternalsFail: true, credentialsId: 'bgqatest', depthOption: 'infinity', ignoreExternalsOption: true, local: 'gradle', remote: "${external}"]], quietOperation: false, workspaceUpdater: [$class: 'CheckoutUpdater']]) } catch (Throwable ex) \ { echo 'Caught Throwable. Retrying operation...' echo 'Exception message: ' + ex.getMessage() ex.printStackTrace() retry(5) { checkout([$class: 'SubversionSCM', additionalCredentials: [], excludedCommitMessages: '', excludedRegions: '', excludedRevprop: '', excludedUsers: '', filterChangelog: false, ignoreDirPropChanges: false, includedRegions: '', locations: [[cancelProcessOnExternalsFail: true, credentialsId: 'nirdevadm', depthOption: 'infinity', ignoreExternalsOption: true, local: '.', remote: "${params.branch}@${params.revision}"], [cancelProcessOnExternalsFail: true, credentialsId: 'bgqatest', depthOption: 'infinity', ignoreExternalsOption: true, local: 'gradle', remote: "${external}"]], quietOperation: false, workspaceUpdater: [$class: 'CheckoutUpdater']]) } } {color:#505f79}{color} {code :java } // code placeholder{code} But I cannot see the stacktrace as it goes in the error stream that I do not see in the console build log.Is there a way to copy this info to the console log?(My use case: I have many SVN checkout issues and I would like to be able to retry the checkout only when I get SVN related exceptions)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-44808) Unable to print stacktrace on jenkins pipeline
Title: Message Title
Vassilena Treneva edited a comment on JENKINS-44808
Re: Unable to print stacktrace on jenkins pipeline
Hey,What is the right way to redirect the stacktrace so that a user can see in the console log?I have this code: {color:#505f79}{{ try \{try { checkout([$class: 'SubversionSCM', additionalCredentials: [], excludedCommitMessages: '', excludedRegions: '', excludedRevprop: '', excludedUsers: '', filterChangelog: false, ignoreDirPropChanges: false, includedRegions: '', locations: [[cancelProcessOnExternalsFail: true, credentialsId: 'nirdevadm', depthOption: 'infinity', ignoreExternalsOption: true, local: '.', remote: "${params.branch}@${params.revision}"], [cancelProcessOnExternalsFail: true, credentialsId: 'bgqatest', depthOption: 'infinity', ignoreExternalsOption: true, local: 'gradle', remote: "${external}"]], quietOperation: false, workspaceUpdater: [$class: 'CheckoutUpdater']])} catch (Throwable ex) \{ echo 'Caught Throwable. Retrying operation...' echo 'Exception message: ' + ex.getMessage() ex.printStackTrace() retry(5) { checkout([$class: 'SubversionSCM', additionalCredentials: [], excludedCommitMessages: '', excludedRegions: '', excludedRevprop: '', excludedUsers: '', filterChangelog: false, ignoreDirPropChanges: false, includedRegions: '', locations: [[cancelProcessOnExternalsFail: true, credentialsId: 'nirdevadm', depthOption: 'infinity', ignoreExternalsOption: true, local: '.', remote: "${params.branch}@${params.revision}"], [cancelProcessOnExternalsFail: true, credentialsId: 'bgqatest', depthOption: 'infinity', ignoreExternalsOption: true, local: 'gradle', remote: "${external}"]], quietOperation: false, workspaceUpdater: [$class: 'CheckoutUpdater']]) }} {color:#505f79 } } {color} {code:java} // code placeholder {code} But I cannot see the stacktrace as it goes in the error stream that I do not see in the console build log.Is there a way to copy this info to the console log?(My use case: I have many SVN checkout issues and I would like to be able to retry the checkout only when I get SVN related exceptions)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-44808) Unable to print stacktrace on jenkins pipeline
Title: Message Title
Vassilena Treneva edited a comment on JENKINS-44808
Re: Unable to print stacktrace on jenkins pipeline
Hey,What is the right way to redirect the stacktrace so that a user can see in the console log? {quote} I have this snippet code : { color:#505f79} { { try \ { }} try { { checkout([$class: 'SubversionSCM', additionalCredentials: [], excludedCommitMessages: '', excludedRegions: '', excludedRevprop: '', excludedUsers: '', filterChangelog: false, ignoreDirPropChanges: false, includedRegions: '', locations: [[cancelProcessOnExternalsFail: true, credentialsId: 'nirdevadm', depthOption: 'infinity', ignoreExternalsOption: true, local: '.', remote: "${params.branch}@${params.revision}"], [cancelProcessOnExternalsFail: true, credentialsId: 'bgqatest', depthOption: 'infinity', ignoreExternalsOption: true, local: 'gradle', remote: "${external}"]], quietOperation: false, workspaceUpdater: [$class: 'CheckoutUpdater']])} } \{{ } catch (Throwable ex) {}} \{ { echo 'Caught Throwable. Retrying operation...' }} \{{ echo 'Exception message: ' + ex.getMessage() }} \{{ ex.printStackTrace() }} \{{ retry(5) { }} {{ checkout([$class: 'SubversionSCM', additionalCredentials: [], excludedCommitMessages: '', excludedRegions: '', excludedRevprop: '', excludedUsers: '', filterChangelog: false, ignoreDirPropChanges: false, includedRegions: '', locations: [[cancelProcessOnExternalsFail: true, credentialsId: 'nirdevadm', depthOption: 'infinity', ignoreExternalsOption: true, local: '.', remote: "${params.branch}@${params.revision}"], [cancelProcessOnExternalsFail: true, credentialsId: 'bgqatest', depthOption: 'infinity', ignoreExternalsOption: true, local: 'gradle', remote: "${external}"]], quietOperation: false, workspaceUpdater: [$class: 'CheckoutUpdater']])}} \{{ }} } \ { { color } }} {quote} But I cannot see the stacktrace as it goes in the error stream that I do not see in the console build log.Is there a way to copy this info to the console log?(My use case: I have many SVN checkout issues and I would like to be able to retry the checkout only when I get SVN related exceptions)
Add Comment
This message was sent by Atlassian
[JIRA] (JENKINS-44808) Unable to print stacktrace on jenkins pipeline
Title: Message Title
Vassilena Treneva edited a comment on JENKINS-44808
Re: Unable to print stacktrace on jenkins pipeline
Hey,What is the right way to redirect the stacktrace so that a user can see in the console log?I have this snippet:{{try {}}{{ checkout([$class: 'SubversionSCM', additionalCredentials: [], excludedCommitMessages: '', excludedRegions: '', excludedRevprop: '', excludedUsers: '', filterChangelog: false, ignoreDirPropChanges: false, includedRegions: '', locations: [[cancelProcessOnExternalsFail: true, credentialsId: 'nirdevadm', depthOption: 'infinity', ignoreExternalsOption: true, local: '.', remote: "${params.branch}@${params.revision}"], [cancelProcessOnExternalsFail: true, credentialsId: 'bgqatest', depthOption: 'infinity', ignoreExternalsOption: true, local: 'gradle', remote: "${external}"]], quietOperation: false, workspaceUpdater: [$class: 'CheckoutUpdater']])}} \ {{ } catch (Throwable ex) {}} \ {{ echo 'Caught Throwable. Retrying operation...'}} \ {{ echo 'Exception message: ' + ex.getMessage()}} \ {{ ex.printStackTrace()}} \ {{ retry(5) {}}{{ checkout([$class: 'SubversionSCM', additionalCredentials: [], excludedCommitMessages: '', excludedRegions: '', excludedRevprop: '', excludedUsers: '', filterChangelog: false, ignoreDirPropChanges: false, includedRegions: '', locations: [[cancelProcessOnExternalsFail: true, credentialsId: 'nirdevadm', depthOption: 'infinity', ignoreExternalsOption: true, local: '.', remote: "${params.branch}@${params.revision}"], [cancelProcessOnExternalsFail: true, credentialsId: 'bgqatest', depthOption: 'infinity', ignoreExternalsOption: true, local: 'gradle', remote: "${external}"]], quietOperation: false, workspaceUpdater: [$class: 'CheckoutUpdater']])}} \ {{ }}} \ {{ }}}But I cannot see the stacktrace as it goes in the error stream that I do not see in the console build log.Is there a way to copy this info to the console log?(My use case: I have many SVN checkout issues and I would like to be able to retry the checkout only when I get SVN related exceptions)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-44808) Unable to print stacktrace on jenkins pipeline
Title: Message Title
Vassilena Treneva edited a comment on JENKINS-44808
Re: Unable to print stacktrace on jenkins pipeline
Hey,What is the right way to redirect the stacktrace so that a user can see in the console log? {quote} I have this snippet:{{try {}} {{ checkout([$class: 'SubversionSCM', additionalCredentials: [], excludedCommitMessages: '', excludedRegions: '', excludedRevprop: '', excludedUsers: '', filterChangelog: false, ignoreDirPropChanges: false, includedRegions: '', locations: [[cancelProcessOnExternalsFail: true, credentialsId: 'nirdevadm', depthOption: 'infinity', ignoreExternalsOption: true, local: '.', remote: "${params.branch}@${params.revision}"], [cancelProcessOnExternalsFail: true, credentialsId: 'bgqatest', depthOption: 'infinity', ignoreExternalsOption: true, local: 'gradle', remote: "${external}"]], quietOperation: false, workspaceUpdater: [$class: 'CheckoutUpdater']])}} \{{ } catch (Throwable ex) {}} \{{ echo 'Caught Throwable. Retrying operation...'}} \{{ echo 'Exception message: ' + ex.getMessage()}} \{{ ex.printStackTrace()}} \{{ retry(5) {}} {{ checkout([$class: 'SubversionSCM', additionalCredentials: [], excludedCommitMessages: '', excludedRegions: '', excludedRevprop: '', excludedUsers: '', filterChangelog: false, ignoreDirPropChanges: false, includedRegions: '', locations: [[cancelProcessOnExternalsFail: true, credentialsId: 'nirdevadm', depthOption: 'infinity', ignoreExternalsOption: true, local: '.', remote: "${params.branch}@${params.revision}"], [cancelProcessOnExternalsFail: true, credentialsId: 'bgqatest', depthOption: 'infinity', ignoreExternalsOption: true, local: 'gradle', remote: "${external}"]], quietOperation: false, workspaceUpdater: [$class: 'CheckoutUpdater']])}} \{{ }}} \{{ }}} {quote} But I cannot see the stacktrace as it goes in the error stream that I do not see in the console build log.Is there a way to copy this info to the console log?(My use case: I have many SVN checkout issues and I would like to be able to retry the checkout only when I get SVN related exceptions)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-44808) Unable to print stacktrace on jenkins pipeline
Title: Message Title
Vassilena Treneva commented on JENKINS-44808
Re: Unable to print stacktrace on jenkins pipeline
Hey, What is the right way to redirect the stacktrace so that a user can see in the console log? I have this snippet: try { checkout([$class: 'SubversionSCM', additionalCredentials: [], excludedCommitMessages: '', excludedRegions: '', excludedRevprop: '', excludedUsers: '', filterChangelog: false, ignoreDirPropChanges: false, includedRegions: '', locations: [[cancelProcessOnExternalsFail: true, credentialsId: 'nirdevadm', depthOption: 'infinity', ignoreExternalsOption: true, local: '.', remote: "${params.branch}@${params.revision}"], [cancelProcessOnExternalsFail: true, credentialsId: 'bgqatest', depthOption: 'infinity', ignoreExternalsOption: true, local: 'gradle', remote: "${external}"]], quietOperation: false, workspaceUpdater: [$class: 'CheckoutUpdater']]) } catch (Throwable ex) { echo 'Caught Throwable. Retrying operation...' echo 'Exception message: ' + ex.getMessage() ex.printStackTrace() retry(5) { checkout([$class: 'SubversionSCM', additionalCredentials: [], excludedCommitMessages: '', excludedRegions: '', excludedRevprop: '', excludedUsers: '', filterChangelog: false, ignoreDirPropChanges: false, includedRegions: '', locations: [[cancelProcessOnExternalsFail: true, credentialsId: 'nirdevadm', depthOption: 'infinity', ignoreExternalsOption: true, local: '.', remote: "${params.branch}@${params.revision}"], [cancelProcessOnExternalsFail: true, credentialsId: 'bgqatest', depthOption: 'infinity', ignoreExternalsOption: true, local: 'gradle', remote: "${external}"]], quietOperation: false, workspaceUpdater: [$class: 'CheckoutUpdater']]) } } But I cannot see the stacktrace as it goes in the error stream that I do not see in the console build log. Is there a way to copy this info to the console log? (My use case: I have many SVN checkout issues and I would like to be able to retry the checkout only when I get SVN related exceptions)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-44808) Unable to print stacktrace on jenkins pipeline
Title: Message Title
Vassilena Treneva edited a comment on JENKINS-44808
Re: Unable to print stacktrace on jenkins pipeline
Hey,What is the right way to redirect the stacktrace so that a user can see in the console log?I have this snippet: {{ try { }} {{ checkout([$class: 'SubversionSCM', additionalCredentials: [], excludedCommitMessages: '', excludedRegions: '', excludedRevprop: '', excludedUsers: '', filterChangelog: false, ignoreDirPropChanges: false, includedRegions: '', locations: [[cancelProcessOnExternalsFail: true, credentialsId: 'nirdevadm', depthOption: 'infinity', ignoreExternalsOption: true, local: '.', remote: "${params.branch}@${params.revision}"], [cancelProcessOnExternalsFail: true, credentialsId: 'bgqatest', depthOption: 'infinity', ignoreExternalsOption: true, local: 'gradle', remote: "${external}"]], quietOperation: false, workspaceUpdater: [$class: 'CheckoutUpdater']]) }} {{ } catch (Throwable ex) { }} {{ echo 'Caught Throwable. Retrying operation...' }} {{ echo 'Exception message: ' + ex.getMessage() }} {{ ex.printStackTrace() }} {{ retry(5) { }} {{ checkout([$class: 'SubversionSCM', additionalCredentials: [], excludedCommitMessages: '', excludedRegions: '', excludedRevprop: '', excludedUsers: '', filterChangelog: false, ignoreDirPropChanges: false, includedRegions: '', locations: [[cancelProcessOnExternalsFail: true, credentialsId: 'nirdevadm', depthOption: 'infinity', ignoreExternalsOption: true, local: '.', remote: "${params.branch}@${params.revision}"], [cancelProcessOnExternalsFail: true, credentialsId: 'bgqatest', depthOption: 'infinity', ignoreExternalsOption: true, local: 'gradle', remote: "${external}"]], quietOperation: false, workspaceUpdater: [$class: 'CheckoutUpdater']]) }} {{ } }} {{ } }} But I cannot see the stacktrace as it goes in the error stream that I do not see in the console build log.Is there a way to copy this info to the console log?(My use case: I have many SVN checkout issues and I would like to be able to retry the checkout only when I get SVN related exceptions)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-53923) Collecting build job results using [.result] property returns null
Title: Message Title Vassilena Treneva assigned an issue to Andrew Bayer Jenkins / JENKINS-53923 Collecting build job results using [.result] property returns null Change By: Vassilena Treneva Assignee: Andrew Bayer 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-53923) Collecting build job results using [.result] property returns null
Title: Message Title Vassilena Treneva updated an issue Jenkins / JENKINS-53923 Collecting build job results using [.result] property returns null Change By: Vassilena Treneva Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41575) PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException
Title: Message Title Vassilena Treneva edited a comment on JENKINS-41575 Re: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException I am seeing a very similar problem that shows up whenever I try to edit content under "Manage Jenkins" pages. I am basically unable to save any change... :( Jenkins ver. 2.140 A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened.Stack tracesun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.provider.certpath.SunCertPathBuilder.build(SunCertPathBuilder.java:141) at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:126) at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:280) at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:392)Caused: sun.security.validator.ValidatorException: PKIX path building failed at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:397) at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:302) at sun.security.validator.Validator.validate(Validator.java:260) at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324) at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:281) at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:136) at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1601)Caused: javax.net.ssl.SSLHandshakeException: General SSLEngine problem at sun.security.ssl.Alerts.getSSLException(Alerts.java:192) at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1728) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:330) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:322) at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1614) at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216) at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1052) at sun.security.ssl.Handshaker$1.run(Handshaker.java:992) at sun.security.ssl.Handshaker$1.run(Handshaker.java:989) at java.security.AccessController.doPrivileged(Native Method) at sun.security.ssl.Handshaker$DelegatedTask.run(Handshaker.java:1467) at org.apache.http.nio.reactor.ssl.SSLIOSession.doRunTask(SSLIOSession.java:281) at org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSLIOSession.java:351)Caused: javax.net.ssl.SSLHandshakeException: General SSLEngine problem at sun.security.ssl.Handshaker.checkThrown(Handshaker.java:1529) at sun.security.ssl.SSLEngineImpl.checkTaskThrown(SSLEngineImpl.java:535) at sun.security.ssl.SSLEngineImpl.writeAppRecord(SSLEngineImpl.java:1214) at sun.security.ssl.SSLEngineImpl.wrap(SSLEngineImpl.java:1186) at javax.net.ssl.SSLEngine.wrap(SSLEngine.java:469) at org.apache.http.nio.reactor.ssl.SSLIOSession.doWrap(SSLIOSession.java:263) at org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSLIOSession.java:303) at org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady(SSLIOSession.java:507) at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:122) at
[JIRA] (JENKINS-41575) PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException
Title: Message Title Vassilena Treneva edited a comment on JENKINS-41575 Re: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException I am seeing a very similar problem that shows up whenever I try to edit contend over content under "Manage Jenkins" pages. I am basically unable to save any change... :( A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened.Stack tracesun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.provider.certpath.SunCertPathBuilder.build(SunCertPathBuilder.java:141) at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:126) at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:280) at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:392)Caused: sun.security.validator.ValidatorException: PKIX path building failed at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:397) at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:302) at sun.security.validator.Validator.validate(Validator.java:260) at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324) at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:281) at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:136) at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1601)Caused: javax.net.ssl.SSLHandshakeException: General SSLEngine problem at sun.security.ssl.Alerts.getSSLException(Alerts.java:192) at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1728) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:330) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:322) at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1614) at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216) at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1052) at sun.security.ssl.Handshaker$1.run(Handshaker.java:992) at sun.security.ssl.Handshaker$1.run(Handshaker.java:989) at java.security.AccessController.doPrivileged(Native Method) at sun.security.ssl.Handshaker$DelegatedTask.run(Handshaker.java:1467) at org.apache.http.nio.reactor.ssl.SSLIOSession.doRunTask(SSLIOSession.java:281) at org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSLIOSession.java:351)Caused: javax.net.ssl.SSLHandshakeException: General SSLEngine problem at sun.security.ssl.Handshaker.checkThrown(Handshaker.java:1529) at sun.security.ssl.SSLEngineImpl.checkTaskThrown(SSLEngineImpl.java:535) at sun.security.ssl.SSLEngineImpl.writeAppRecord(SSLEngineImpl.java:1214) at sun.security.ssl.SSLEngineImpl.wrap(SSLEngineImpl.java:1186) at javax.net.ssl.SSLEngine.wrap(SSLEngine.java:469) at org.apache.http.nio.reactor.ssl.SSLIOSession.doWrap(SSLIOSession.java:263) at org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSLIOSession.java:303) at org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady(SSLIOSession.java:507) at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:122) at
[JIRA] (JENKINS-41575) PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException
Title: Message Title Vassilena Treneva commented on JENKINS-41575 Re: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException I am seeing a very similar problem that shows up whenever I try to edit contend over "Manage Jenkins" pages. I am basically unable to save any change... A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.provider.certpath.SunCertPathBuilder.build(SunCertPathBuilder.java:141) at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:126) at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:280) at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:392) Caused: sun.security.validator.ValidatorException: PKIX path building failed at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:397) at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:302) at sun.security.validator.Validator.validate(Validator.java:260) at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324) at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:281) at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:136) at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1601) Caused: javax.net.ssl.SSLHandshakeException: General SSLEngine problem at sun.security.ssl.Alerts.getSSLException(Alerts.java:192) at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1728) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:330) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:322) at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1614) at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216) at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1052) at sun.security.ssl.Handshaker$1.run(Handshaker.java:992) at sun.security.ssl.Handshaker$1.run(Handshaker.java:989) at java.security.AccessController.doPrivileged(Native Method) at sun.security.ssl.Handshaker$DelegatedTask.run(Handshaker.java:1467) at org.apache.http.nio.reactor.ssl.SSLIOSession.doRunTask(SSLIOSession.java:281) at org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSLIOSession.java:351) Caused: javax.net.ssl.SSLHandshakeException: General SSLEngine problem at sun.security.ssl.Handshaker.checkThrown(Handshaker.java:1529) at sun.security.ssl.SSLEngineImpl.checkTaskThrown(SSLEngineImpl.java:535) at sun.security.ssl.SSLEngineImpl.writeAppRecord(SSLEngineImpl.java:1214) at sun.security.ssl.SSLEngineImpl.wrap(SSLEngineImpl.java:1186) at javax.net.ssl.SSLEngine.wrap(SSLEngine.java:469) at org.apache.http.nio.reactor.ssl.SSLIOSession.doWrap(SSLIOSession.java:263) at org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSLIOSession.java:303) at org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady(SSLIOSession.java:507) at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:122) at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:164) at
[JIRA] (JENKINS-53923) Collecting build job results using [.result] property returns null
Title: Message Title Vassilena Treneva updated an issue Jenkins / JENKINS-53923 Collecting build job results using [.result] property returns null Change By: Vassilena Treneva Attachment: pipelineBuilder.groovy 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-53923) Collecting build job results using [.result] property returns null
Title: Message Title
Vassilena Treneva created an issue
Jenkins / JENKINS-53923
Collecting build job results using [.result] property returns null
Issue Type:
Bug
Assignee:
Daniel Spilker
Attachments:
pipelineBuilder.groovy
Components:
job-dsl-plugin, pipeline, pipeline-model-definition-plugin, pipeline-stage-step-plugin
Created:
2018-10-05 12:59
Environment:
Jenkins ver. 2.140
Priority:
Minor
Reporter:
Vassilena Treneva
I would like to collect all triggered jobs results. My script looks like this: stage('Integration Tests') { steps { script { def jobs = [:] def childJob def childJobName pipelineIntegrationJobs.each { i -> jobs["${nirvanaMajor}.${nirvanaMinor}_${i}"] = { childJob = build (job: "${nirvanaMajor}.${nirvanaMinor}_${i}", parameters: [ string(name: 'branch', value: "${svnBranch}", description: 'svn repository url'), string(name: 'buildmajor', value: '10', description: 'release major identifier'), string(name: 'buildminor', value: '4', description: 'release minor identifier'), string(name: 'fix', value: "${env.fix}", description: 'fix level'), string(name: 'buildnumber', value: "${env.buildNumber}", description: 'artifacts build number'), string(name: 'revision', value: "${env.buildNumber}", description: 'checkout revision'), string(name: 'joblabel', value: "${pipelineName}", description: "optional job description") ], quietPeriod: 0, propagate: false, wait: true).result } childJobName = "${nirvanaMajor}.${nirvanaMinor}_${i}" results.put(childJobName, childJob) } parallel jobs } } } In the post section of the pipeline I have this: script { println
[JIRA] (JENKINS-53652) InterruptedException during slave workspace groovy clean up pipeline
Title: Message Title Vassilena Treneva commented on JENKINS-53652 Re: InterruptedException during slave workspace groovy clean up pipeline A side question (hope I am not spoiling the issue) – is there a way to check and kill all remaining process in the workspace without using OS commands, but instead using Jenkins Groovy Api for this? Something like an alternative to kill -9 for all processes in the workspace… This check (!node.getComputer().isOffline()) is good for figuring out if the node is currently building, but if by any chance some process has been left alive, the script would eventually fail. 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-53652) InterruptedException during slave workspace groovy clean up pipeline
Title: Message Title
Vassilena Treneva commented on JENKINS-53652
Re: InterruptedException during slave workspace groovy clean up pipeline
Okay, so I think I do not need the loop at all! This script works: import hudson.model.Node import hudson.model.Slave import jenkins.model.Jenkins import hudson.FilePath; pipeline { triggers { cron('H 1 * * *') } agent { node { label 'master' } } options { timeout(time: 3, unit: 'HOURS') buildDiscarder(logRotator(daysToKeepStr: '30', numToKeepStr: '30', artifactDaysToKeepStr:'1', artifactNumToKeepStr: '30')) timestamps() } stages { stage ('Wipe Out Slave Workspaces') { steps { script { Jenkins jenkins = Jenkins.instance def jenkinsNodes = jenkins.nodes for (Node node in jenkinsNodes) { if (!node.getComputer().isOffline()) { if(node.getComputer().countBusy()==0) { FilePath fp = node.getRootPath().child("workspace"); println("Processing: " + node.getDisplayName()) println ("Wiping out: " + fp) def now = new Date() println now.format("-MM-dd HH:mm:ss", TimeZone.getTimeZone('GMT+2')) println("--") try { fp.deleteRecursive(); } catch (InterruptedException e) { println "InterruptedException caught!" e.printStackTrace(); } } } } } } } } } Michael Mrozek Many thanks again! Jeff Thompson Thank you for your detailed answers and ideas and most of all - for not ignoring my problem
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-53652) InterruptedException during slave workspace groovy clean up pipeline
Title: Message Title
Vassilena Treneva commented on JENKINS-53652
Re: InterruptedException during slave workspace groovy clean up pipeline
Michael Mrozek, Many thanks for this hint! I will try to adjust my script in the same way. I will attempt something like this: int counter = 0; while (counter < 10) { try { fp.deleteRecursive(); } catch (InterruptedException e) { counter ++; e.printStackTrace(); } } I am not clear what the exit condition of the while should be? What is yours? Just some counter or some other condition? If you can share a snippet with me - that would be helpful.
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-51491) Remoting Thread Terminated Randomly
Title: Message Title Vassilena Treneva commented on JENKINS-51491 Re: Remoting Thread Terminated Randomly I added the JVM argument as advised. There is no effect however - the pipeline still fails with InterruptedException 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-51491) Remoting Thread Terminated Randomly
Title: Message Title Vassilena Treneva commented on JENKINS-51491 Re: Remoting Thread Terminated Randomly Hey, Just read the defect you mention. So, you want me to add: -Dhudson.slaves.ChannelPinger.pingIntervalSeconds=120 to JENKINS_JAVA_OPTIONS under /etc/sysconfig/jenkins on the master, right? I will try what you suggest. How is that going to help me? 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-53652) InterruptedException during slave workspace groovy clean up pipeline
Title: Message Title Vassilena Treneva commented on JENKINS-53652 Re: InterruptedException during slave workspace groovy clean up pipeline Hey, The job does not complete. It fails. I cannot see a pattern when it tends to fail. Sometimes it takes ~10 minutes, sometimes less. And it happens when working with different slaves I have added timestamps to the execution and I am attaching the console output with timestamps (https://issues.jenkins-ci.org/secure/attachment/44537/ConsoleOutputWithTimestamps.txt) as well as the threads I see immediately after the job has failed (https://issues.jenkins-ci.org/secure/attachment/44536/ThreadsAfterJobFailure.txt) I was also thinking if it makes sense that I log a bit more data about the threads from the pipeline itself? I am not sure however what is the context and how to access the current thread... 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-53652) InterruptedException during slave workspace groovy clean up pipeline
Title: Message Title Vassilena Treneva updated an issue Jenkins / JENKINS-53652 InterruptedException during slave workspace groovy clean up pipeline Change By: Vassilena Treneva Attachment: ThreadsAfterJobFailure.txt Attachment: ConsoleOutputWithTimestamps.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53652) InterruptedException during slave workspace groovy clean up pipeline
Title: Message Title Vassilena Treneva commented on JENKINS-53652 Re: InterruptedException during slave workspace groovy clean up pipeline Attached a list of the active threads during the job execution (https://issues.jenkins-ci.org/secure/attachment/44535/ThreadsDuringTheRun.txt) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53652) InterruptedException during slave workspace groovy clean up pipeline
Title: Message Title Vassilena Treneva updated an issue Jenkins / JENKINS-53652 InterruptedException during slave workspace groovy clean up pipeline Change By: Vassilena Treneva Attachment: ThreadsDuringTheRun.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53652) InterruptedException during slave workspace groovy clean up pipeline
Title: Message Title Vassilena Treneva commented on JENKINS-53652 Re: InterruptedException during slave workspace groovy clean up pipeline What kind of information would be helpful? It is 100% reproducible on our side, so I can try to collect whatever is needed... 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-53652) InterruptedException during slave workspace groovy clean up pipeline
Title: Message Title
Vassilena Treneva updated an issue
Jenkins / JENKINS-53652
InterruptedException during slave workspace groovy clean up pipeline
Change By:
Vassilena Treneva
We use a declarative pipeline to wipe out all slaves workspaces (attached here - Jenkinsfile)It generally does some processing and attempts to delete the workspace like this:FilePath fp = node.getRootPath().child("workspace");fp.deleteRecursive(); It starts working well and fails with InterruptedException at some point: Started by timerLightweight checkout support not available, falling back to full checkout.Checking out svn http://svndae.apama.com/um/branches/dev/jenkins2_2/build/change-management/jenkinsfiles/wipeout_slave_workspace into /FS/fslocal/jenkinsWorkspace/jobs/admin_wipeout_workspaces/workspace@script to read JenkinsfileUpdating http://svndae.apama.com/um/branches/dev/jenkins2_2/build/change-management/jenkinsfiles/wipeout_slave_workspace at revision '2018-09-19T01:47:00.338 +0200' --quietAt revision 112786No changes for http://svndae.apama.com/um/branches/dev/jenkins2_2/build/change-management/jenkinsfiles/wipeout_slave_workspace since the previous buildRunning in Durability level: MAX_SURVIVABILITYLoading library templates@branches/dev/jenkins2_2/build/change-management/jenkinsfiles/templatesOpening connection to http://svndae.apama.com/um/Updating http://svndae.apama.com/um/branches/dev/jenkins2_2/build/change-management/jenkinsfiles/templates@112786 at revision 112786At revision 112786No changes for http://svndae.apama.com/um/branches/dev/jenkins2_2/build/change-management/jenkinsfiles/templates since the previous build[Pipeline] nodeRunning on Jenkins in /FS/fslocal/jenkinsWorkspace/jobs/admin_wipeout_workspaces/workspace[Pipeline] {[Pipeline] stage[Pipeline] { (Declarative: Checkout SCM)[Pipeline] checkoutUpdating http://svndae.apama.com/um/branches/dev/jenkins2_2/build/change-management/jenkinsfiles/wipeout_slave_workspace at revision '2018-09-19T01:47:00.338 +0200' --quietAt revision 112786No changes for http://svndae.apama.com/um/branches/dev/jenkins2_2/build/change-management/jenkinsfiles/wipeout_slave_workspace since the previous build[Pipeline] }[Pipeline] // stage[Pipeline] withEnv[Pipeline] {[Pipeline] stage[Pipeline] { (Wipe Out Slave Workspaces)[Pipeline] script[Pipeline] {[Pipeline] echoProcessing: daeosx109v04.eur.ad.sag[Pipeline] echoWiping out: /Users/nirdevadm/workspace/workspace[Pipeline] echo--[Pipeline] echoProcessing: daeosx109v05.eur.ad.sag[Pipeline] echoWiping out: /Users/nirdevadm/jenkinsWorkspace/workspace[Pipeline] echo--[Pipeline] echoProcessing: daeosx109v11.eur.ad.sag[Pipeline] echoWiping out: /Users/nirdevadm/workspace/workspace[Pipeline] echo--[Pipeline] echoProcessing: sofum01.eur.ad.sag[Pipeline] echoWiping out: /home/nirdevadm/jenkins/workspace[Pipeline] echo--[Pipeline] echoProcessing: umlinuxbuild10.eur.ad.sag[Pipeline] echoWiping out: /FS/fslocal/jenkins_slave/workspace[Pipeline]
[JIRA] (JENKINS-53652) InterruptedException during slave workspace groovy clean up pipeline
Title: Message Title Vassilena Treneva created an issue Jenkins / JENKINS-53652 InterruptedException during slave workspace groovy clean up pipeline Issue Type: Bug Assignee: Jeff Thompson Attachments: Jenkinsfile Components: pipeline, remoting Created: 2018-09-19 08:36 Environment: Jenkins ver. 2.140 Labels: remoting groovy-script pipeline slave Priority: Minor Reporter: Vassilena Treneva We use a declarative pipeline to wipe out all slaves workspaces (attached here - Jenkinsfile) It starts working well and fails with InterruptedException at some point: Started by timer Lightweight checkout support not available, falling back to full checkout. Checking out svn http://svndae.apama.com/um/branches/dev/jenkins2_2/build/change-management/jenkinsfiles/wipeout_slave_workspace into /FS/fslocal/jenkinsWorkspace/jobs/admin_wipeout_workspaces/workspace@script to read Jenkinsfile Updating http://svndae.apama.com/um/branches/dev/jenkins2_2/build/change-management/jenkinsfiles/wipeout_slave_workspace at revision '2018-09-19T01:47:00.338 +0200' --quiet At revision 112786 No changes for http://svndae.apama.com/um/branches/dev/jenkins2_2/build/change-management/jenkinsfiles/wipeout_slave_workspace since the previous build Running in Durability level: MAX_SURVIVABILITY Loading library templates@branches/dev/jenkins2_2/build/change-management/jenkinsfiles/templates Opening
[JIRA] (JENKINS-51854) LinkageError while performing UserRequest:hudson.scm.SubversionSCM
Title: Message Title Vassilena Treneva edited a comment on JENKINS-51854 Re: LinkageError while performing UserRequest:hudson.scm.SubversionSCM I have also added a comment in the issue that you pointed me to. This is breaking quite a few jobs on our side :(Is there any workaround?I am using Jenkins ver. 2.140 *This is in the slave log:*WARNING: LinkageError while performing UserRequest:hudson.scm.SubversionSCM$CheckOutTask@6c161e48WARNING: LinkageError while performing UserRequest:hudson.scm.SubversionSCM$checkoutt...@6c161e48java.lang.ExceptionInInitializerError at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:1003) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:980) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3084) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)Caused by: hudson.remoting.RemotingSystemException: java.lang.InterruptedException at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:299) at com.sun.proxy.$Proxy5.getResource2(Unknown Source) at hudson.remoting.RemoteClassLoader.findResource(RemoteClassLoader.java:426) at java.lang.ClassLoader.getResource(Unknown Source) at java.lang.Class.getResource(Unknown Source) at org.jvnet.localizer.ResourceBundleHolder.get(ResourceBundleHolder.java:107) at org.jvnet.localizer.Localizable.toString(Localizable.java:67) at hudson.security.PermissionGroup.(PermissionGroup.java:64) at hudson.scm.SCM.(SCM.java:719) ... 11 moreCaused by: java.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:177) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:286) ... 19 moreSep 13, 2018 7:27:52 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: Attempt to (de-)serialize anonymous class hudson.plugins.nunit.NUnitPublisher$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/Sep 13, 2018 7:27:52 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: Attempt to (de-)serialize anonymous class hudson.tasks.Ant$AntInstallation$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/Sep 13, 2018 8:15:47 AM hudson.remoting.UserRequest performWARNING: LinkageError while performing UserRequest:hudson.scm.SubversionSCM$checkoutt...@6be2e14bjava.lang.NoClassDefFoundError: Could not initialize class hudson.scm.SubversionSCM at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:1003) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:980) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3084) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)*This is console output taken from the job:*08:15:47 Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call
[JIRA] (JENKINS-51854) LinkageError while performing UserRequest:hudson.scm.SubversionSCM
Title: Message Title Vassilena Treneva commented on JENKINS-51854 Re: LinkageError while performing UserRequest:hudson.scm.SubversionSCM I have also added a comment in the issue that you pointed me to. This is breaking quite a few jobs on our side Is there any workaround? This is in the slave log: WARNING: LinkageError while performing UserRequest:hudson.scm.SubversionSCM$CheckOutTask@6c161e48WARNING: LinkageError while performing UserRequest:hudson.scm.SubversionSCM$checkoutt...@6c161e48java.lang.ExceptionInInitializerError at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:1003) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:980) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3084) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)Caused by: hudson.remoting.RemotingSystemException: java.lang.InterruptedException at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:299) at com.sun.proxy.$Proxy5.getResource2(Unknown Source) at hudson.remoting.RemoteClassLoader.findResource(RemoteClassLoader.java:426) at java.lang.ClassLoader.getResource(Unknown Source) at java.lang.Class.getResource(Unknown Source) at org.jvnet.localizer.ResourceBundleHolder.get(ResourceBundleHolder.java:107) at org.jvnet.localizer.Localizable.toString(Localizable.java:67) at hudson.security.PermissionGroup.(PermissionGroup.java:64) at hudson.scm.SCM.(SCM.java:719) ... 11 moreCaused by: java.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:177) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:286) ... 19 more Sep 13, 2018 7:27:52 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: Attempt to (de-)serialize anonymous class hudson.plugins.nunit.NUnitPublisher$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/Sep 13, 2018 7:27:52 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: Attempt to (de-)serialize anonymous class hudson.tasks.Ant$AntInstallation$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/Sep 13, 2018 8:15:47 AM hudson.remoting.UserRequest performWARNING: LinkageError while performing UserRequest:hudson.scm.SubversionSCM$checkoutt...@6be2e14bjava.lang.NoClassDefFoundError: Could not initialize class hudson.scm.SubversionSCM at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:1003) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:980) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3084) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) This is console output taken from the job: 08:15:47 Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to umwintest16.eur.ad.sag 08:15:47 at
[JIRA] (JENKINS-51491) Remoting Thread Terminated Randomly
Title: Message Title Vassilena Treneva edited a comment on JENKINS-51491 Re: Remoting Thread Terminated Randomly I hope I am not spoiling this issue, but I think we are seeing quite often the same problem (using [Jenkins ver. 2.140|https://jenkins.io/]).Any workaround? It is breaking quite a few jobs :( *This is in the slave log:* WARNING: LinkageError while performing UserRequest:hudson.scm.SubversionSCM$CheckOutTask@6c161e48WARNING: LinkageError while performing UserRequest:hudson.scm.SubversionSCM$checkoutt...@6c161e48java.lang.ExceptionInInitializerError at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:1003) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:980) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3084) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)Caused by: hudson.remoting.RemotingSystemException: java.lang.InterruptedException at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:299) at com.sun.proxy.$Proxy5.getResource2(Unknown Source) at hudson.remoting.RemoteClassLoader.findResource(RemoteClassLoader.java:426) at java.lang.ClassLoader.getResource(Unknown Source) at java.lang.Class.getResource(Unknown Source) at org.jvnet.localizer.ResourceBundleHolder.get(ResourceBundleHolder.java:107) at org.jvnet.localizer.Localizable.toString(Localizable.java:67) at hudson.security.PermissionGroup.(PermissionGroup.java:64) at hudson.scm.SCM.(SCM.java:719) ... 11 moreCaused by: java.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:177) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:286) ... 19 moreSep 13, 2018 7:27:52 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: Attempt to (de-)serialize anonymous class hudson.plugins.nunit.NUnitPublisher$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/Sep 13, 2018 7:27:52 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: Attempt to (de-)serialize anonymous class hudson.tasks.Ant$AntInstallation$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/Sep 13, 2018 8:15:47 AM hudson.remoting.UserRequest performWARNING: LinkageError while performing UserRequest:hudson.scm.SubversionSCM$checkoutt...@6be2e14bjava.lang.NoClassDefFoundError: Could not initialize class hudson.scm.SubversionSCM at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:1003) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:980) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3084) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) *This is console output taken from the job:*08:15:47 Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to
[JIRA] (JENKINS-51491) Remoting Thread Terminated Randomly
Title: Message Title Vassilena Treneva edited a comment on JENKINS-51491 Re: Remoting Thread Terminated Randomly I hope I am not spoiling this issue, but I think we are seeing quite often the same problem (using [Jenkins ver. 2.140|https://jenkins.io/]).Any workaround? It is breaking quite a few jobs :( *This is in the slave log:*WARNING: LinkageError while performing UserRequest:hudson.scm.SubversionSCM$CheckOutTask@6c161e48WARNING: LinkageError while performing UserRequest:hudson.scm.SubversionSCM$checkoutt...@6c161e48java.lang.ExceptionInInitializerError at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:1003) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:980) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3084) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)Caused by: hudson.remoting.RemotingSystemException: java.lang.InterruptedException at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:299) at com.sun.proxy.$Proxy5.getResource2(Unknown Source) at hudson.remoting.RemoteClassLoader.findResource(RemoteClassLoader.java:426) at java.lang.ClassLoader.getResource(Unknown Source) at java.lang.Class.getResource(Unknown Source) at org.jvnet.localizer.ResourceBundleHolder.get(ResourceBundleHolder.java:107) at org.jvnet.localizer.Localizable.toString(Localizable.java:67) at hudson.security.PermissionGroup.(PermissionGroup.java:64) at hudson.scm.SCM.(SCM.java:719) ... 11 moreCaused by: java.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:177) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:286) ... 19 moreSep 13, 2018 7:27:52 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: Attempt to (de-)serialize anonymous class hudson.plugins.nunit.NUnitPublisher$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/Sep 13, 2018 7:27:52 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: Attempt to (de-)serialize anonymous class hudson.tasks.Ant$AntInstallation$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/Sep 13, 2018 8:15:47 AM hudson.remoting.UserRequest performWARNING: LinkageError while performing UserRequest:hudson.scm.SubversionSCM$checkoutt...@6be2e14bjava.lang.NoClassDefFoundError: Could not initialize class hudson.scm.SubversionSCM at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:1003) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:980) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3084) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)*This is console output taken from the job:* 08:15:47 Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to
[JIRA] (JENKINS-51491) Remoting Thread Terminated Randomly
Title: Message Title Vassilena Treneva commented on JENKINS-51491 Re: Remoting Thread Terminated Randomly I hope I am not spoiling this issue, but I think we are seeing quite often the same problem (using Jenkins ver. 2.140). Any workaround? It is breaking quite a few jobs WARNING: LinkageError while performing UserRequest:hudson.scm.SubversionSCM$CheckOutTask@6c161e48WARNING: LinkageError while performing UserRequest:hudson.scm.SubversionSCM$checkoutt...@6c161e48java.lang.ExceptionInInitializerError at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:1003) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:980) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3084) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)Caused by: hudson.remoting.RemotingSystemException: java.lang.InterruptedException at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:299) at com.sun.proxy.$Proxy5.getResource2(Unknown Source) at hudson.remoting.RemoteClassLoader.findResource(RemoteClassLoader.java:426) at java.lang.ClassLoader.getResource(Unknown Source) at java.lang.Class.getResource(Unknown Source) at org.jvnet.localizer.ResourceBundleHolder.get(ResourceBundleHolder.java:107) at org.jvnet.localizer.Localizable.toString(Localizable.java:67) at hudson.security.PermissionGroup.(PermissionGroup.java:64) at hudson.scm.SCM.(SCM.java:719) ... 11 moreCaused by: java.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:177) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:286) ... 19 more Sep 13, 2018 7:27:52 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: Attempt to (de-)serialize anonymous class hudson.plugins.nunit.NUnitPublisher$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/Sep 13, 2018 7:27:52 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: Attempt to (de-)serialize anonymous class hudson.tasks.Ant$AntInstallation$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/Sep 13, 2018 8:15:47 AM hudson.remoting.UserRequest performWARNING: LinkageError while performing UserRequest:hudson.scm.SubversionSCM$checkoutt...@6be2e14bjava.lang.NoClassDefFoundError: Could not initialize class hudson.scm.SubversionSCM at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:1003) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:980) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3084) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)
[JIRA] (JENKINS-25858) java.io.IOException: Unexpected termination of the channel
Title: Message Title Vassilena Treneva commented on JENKINS-25858 Re: java.io.IOException: Unexpected termination of the channel Francois Aichelbaum, do you know which version of the server/ssh plugin does NOT have this 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-25858) java.io.IOException: Unexpected termination of the channel
Title: Message Title Vassilena Treneva commented on JENKINS-25858 Re: java.io.IOException: Unexpected termination of the channel Using Jenkins ver. 2.113 with SSH Slaves plugin 1.26. All our UNIX, Windows and OSX slaves are using SSH connection. We are seeing a lot of these. Is it the same issue? Slave JVM has not reported exit code. Is it still running? ERROR: Connection terminated java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2671) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3146) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:858) at java.io.ObjectInputStream.(ObjectInputStream.java:354) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63) Caused: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77) ERROR: Connection terminated java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2671) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3146) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:858) at java.io.ObjectInputStream.(ObjectInputStream.java:354) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63) Caused: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77) ERROR: Socket connection to SSH server was lost java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:210) at java.net.SocketInputStream.read(SocketInputStream.java:141) at com.trilead.ssh2.crypto.cipher.CipherInputStream.fill_buffer(CipherInputStream.java:41) at com.trilead.ssh2.crypto.cipher.CipherInputStream.internal_read(CipherInputStream.java:52) at com.trilead.ssh2.crypto.cipher.CipherInputStream.getBlock(CipherInputStream.java:79) at com.trilead.ssh2.crypto.cipher.CipherInputStream.read(CipherInputStream.java:108) at com.trilead.ssh2.transport.TransportConnection.receiveMessage(TransportConnection.java:232) at com.trilead.ssh2.transport.TransportManager.receiveLoop(TransportManager.java:706) at com.trilead.ssh2.transport.TransportManager$1.run(TransportManager.java:502) at java.lang.Thread.run(Thread.java:748) Slave JVM has not reported exit code before the socket was lost [04/05/18 17:10:24] [SSH] Connection closed.
[JIRA] (JENKINS-47844) Repeatable intermittent svn update failures due to NPE
Title: Message Title Vassilena Treneva edited a comment on JENKINS-47844 Re: Repeatable intermittent svn update failures due to NPE We often see the same issue in our environments.Running on Jenkins ver. 2.113 and Subversion Plug-in 2.10.5 *05:46:48* java.lang.NullPointerException *05:46:48* at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:123) *05:46:48* at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:757) *05:46:48* at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:892) *05:46:48* at hudson.scm.SCM.checkout(SCM.java:504) *05:46:48* at hudson.model.AbstractProject.checkout(AbstractProject.java:1208) *05:46:48* at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) *05:46:48* at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) *05:46:48* at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) *05:46:48* at hudson.model.Run.execute(Run.java:1727) *05:46:48* at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) *05:46:48* at hudson.model.ResourceController.execute(ResourceController.java:97) *05:46:48* at hudson.model.Executor.run(Executor.java:429) 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-47844) Repeatable intermittent svn update failures due to NPE
Title: Message Title Vassilena Treneva commented on JENKINS-47844 Re: Repeatable intermittent svn update failures due to NPE We often see the same issue in our environments. Running on Jenkins ver. 2.113 and Subversion Plug-in 2.10.5 05:46:48 java.lang.NullPointerException*05:46:48* at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:123)05:46:48 at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:757)05:46:48 at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:892)05:46:48 at hudson.scm.SCM.checkout(SCM.java:504)05:46:48 at hudson.model.AbstractProject.checkout(AbstractProject.java:1208)05:46:48 at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)05:46:48 at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)05:46:48 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)05:46:48 at hudson.model.Run.execute(Run.java:1727)05:46:48 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)05:46:48 at hudson.model.ResourceController.execute(ResourceController.java:97)05:46:48 at hudson.model.Executor.run(Executor.java:429) 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] [credentials-plugin] (JENKINS-35122) Job configuration screen stuck on LOADING
Title: Message Title Vassilena Treneva commented on JENKINS-35122 Re: Job configuration screen stuck on LOADING OK. Got it. I will update the version of the plugin. Thanks a lot for the quick response! 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] [credentials-plugin] (JENKINS-35122) Job configuration screen stuck on LOADING
Title: Message Title Vassilena Treneva commented on JENKINS-35122 Re: Job configuration screen stuck on LOADING Credentials Plugin is 2.0.5 and I don't see newer version available under plugin manager (although the iwiki page says there is version 2.0.6) What is wrong? 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] [credentials-plugin] (JENKINS-35122) Job configuration screen stuck on LOADING
Title: Message Title Vassilena Treneva updated an issue Jenkins / JENKINS-35122 Job configuration screen stuck on LOADING Change By: Vassilena Treneva Attachment: wait.jpg 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] [credentials-plugin] (JENKINS-35122) Job configuration screen stuck on LOADING
Title: Message Title Vassilena Treneva reopened an issue Jenkins / JENKINS-35122 Job configuration screen stuck on LOADING Change By: Vassilena Treneva Resolution: Fixed Status: Closed Reopened 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] [credentials-plugin] (JENKINS-35122) Job configuration screen stuck on LOADING
Title: Message Title Vassilena Treneva commented on JENKINS-35122 Re: Job configuration screen stuck on LOADING I upgraded to 2.6 and I run into this problem where I am not able to edit the job configuration - it simply get stuck on loading... Uploading a picture (wait.jpg) 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] [core] (JENKINS-34871) After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?)
Title: Message Title Vassilena Treneva edited a comment on JENKINS-34871 Re: After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?) My master Jenkins (unfortunately) is hosted on windows platform and I cannot make it work. I tried adding this line:-Dhudson.model.ParametersAction.safeParameters=true -jar "%BASE%\jenkins.war"in %JENKINS_HOME%/jenkins.xml, so after I edited the tag it looks like this: %BASE%\jre\bin\java -Dhudson.model.ParametersAction.safeParameters=true -jar "%BASE%\jenkins.war" -Xrs -Xmx256m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar "%BASE%\jenkins.war" --httpPort=8080I also tried adding JENKINS_JAVA_OPTIONS & JENKINS_ARGS as windows environment variables.No success with either approaches. Any ideas? EDIT: I was putting the wrong parameter ( hudson.model.ParametersAction. safeParameters instead hudson.model.ParametersAction. undefinedParameters)Switched to the right one and it works as before. 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] [core] (JENKINS-34871) After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?)
Title: Message Title Vassilena Treneva edited a comment on JENKINS-34871 Re: After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?) My master Jenkins (unfortunately) is hosted on windows platform and I cannot make it work. I tried adding this line:-Dhudson.model.ParametersAction.safeParameters=true -jar "%BASE%\jenkins.war"in %JENKINS_HOME%/jenkins.xml, so after I edited the tag it looks like this: %BASE%\jre\bin\java -Dhudson.model.ParametersAction.safeParameters=true -jar "%BASE%\jenkins.war" -Xrs -Xmx256m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar "%BASE%\jenkins.war" --httpPort=8080I also tried adding JENKINS_JAVA_OPTIONS & JENKINS_ARGS as windows environment variables.No success with either approaches. Any ideas? EDIT: I was putting the wrong parameter (safeParameters instead undefinedParameters)Switched to the right one and it works as before. 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] [core] (JENKINS-34871) After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?)
Title: Message Title Vassilena Treneva commented on JENKINS-34871 Re: After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?) My master Jenkins (unfortunately) is hosted on windows platform and I cannot make it work. I tried adding this line: -Dhudson.model.ParametersAction.safeParameters=true -jar "%BASE%\jenkins.war" in %JENKINS_HOME%/jenkins.xml, so after I edited the tag it looks like this: %BASE%\jre\bin\java -Dhudson.model.ParametersAction.safeParameters=true -jar "%BASE%\jenkins.war" -Xrs -Xmx256m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar "%BASE%\jenkins.war" --httpPort=8080 I also tried adding JENKINS_JAVA_OPTIONS & JENKINS_ARGS as windows environment variables. No success with either approaches. Any ideas? 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] [core] (JENKINS-34871) After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?)
Title: Message Title Vassilena Treneva assigned an issue to Vassilena Treneva Jenkins / JENKINS-34871 After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?) Change By: Vassilena Treneva Assignee: huybrechts Vassilena Treneva 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] [core] (JENKINS-34871) After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?)
Title: Message Title Vassilena Treneva commented on JENKINS-34871 Re: After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?) Okay. Thanks. Another question then - typically we start Jenkins using command line args in Jenkins home like: or and these commands on their turn invoke jenkins.war file. How exactly did you set hudson.model.ParametersAction.keepUndefinedParameters=true? Started Jenkins by invoking the .war file directly? How do you know all the arguments that are typically passed to it? 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] [core] (JENKINS-34871) After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?)
Title: Message Title Vassilena Treneva commented on JENKINS-34871 Re: After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?) Hi Lars, Where did you set this to resolve the problem everywhere? Slave level? And a side comment - we have quite a lot of parameters and I cannot imagine passing explicitly all of them. This completely throws away the ability to start builds with prop files... 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] [core] (JENKINS-34871) After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?)
Title: Message Title Vassilena Treneva updated an issue Jenkins / JENKINS-34871 After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?) Change By: Vassilena Treneva Summary: After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file ( maybe due to SECURITY-170 / CVE-2016-3721?) 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] [core] (JENKINS-34871) After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (due to SECURITY-170 / CVE-2016-3721?)
Title: Message Title Vassilena Treneva updated an issue Jenkins / JENKINS-34871 After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (due to SECURITY-170 / CVE-2016-3721?) Change By: Vassilena Treneva Priority: Blocker Major 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] [core] (JENKINS-34871) After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (due to SECURITY-170 / CVE-2016-3721?)
Title: Message Title Vassilena Treneva updated an issue Jenkins / JENKINS-34871 After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (due to SECURITY-170 / CVE-2016-3721?) Change By: Vassilena Treneva Environment: win server hostJenkins version 2.3 Parameterized Trigger plugin version 2.30 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] [core] (JENKINS-34871) After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (due to SECURITY-170 / CVE-2016-3721?)
Title: Message Title Vassilena Treneva updated an issue Jenkins / JENKINS-34871 After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (due to SECURITY-170 / CVE-2016-3721?) Change By: Vassilena Treneva Summary: After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (due to SECURITY-170 / CVE-2016-3721?) 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] [core] (JENKINS-34871) After upgrading to Jenkins 2.3 we are unable to trigger parametrized build (due to SECURITY-170 / CVE-2016-3721?)
Title: Message Title Vassilena Treneva updated an issue Jenkins / JENKINS-34871 After upgrading to Jenkins 2.3 we are unable to trigger parametrized build (due to SECURITY-170 / CVE-2016-3721?) Change By: Vassilena Treneva After upgrading to Jenkins 2.3 we are not able to pass a custom parameter specified in a property file. It looks like there is a security feature in this versions (https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11) that disables simply passing build parameters.This makes no sense to me since in my configuration (attached picture - config.jpg) I explicitly specify that I need to trigger the build with predefined properties. Maybe I am missing something?I tried to get the suggested solution working on slave level (passed java -Dhudson.model.ParametersAction.safeParameters=myParam) to slave start-up but this does not work. It looks like this needs to be passed when we start the master but this is no workaround. We simply have a lot of parameters and we cannot pass them to master at start-up.Again - maybe I am missing something in this workaround? 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] [core] (JENKINS-34871) After upgrading to Jenkins 2.3 we are unable to trigger parametrized build (due to SECURITY-170 / CVE-2016-3721?)
Title: Message Title Vassilena Treneva updated an issue Jenkins / JENKINS-34871 After upgrading to Jenkins 2.3 we are unable to trigger parametrized build (due to SECURITY-170 / CVE-2016-3721?) Change By: Vassilena Treneva Environment: win hostJenkins version 2.3 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] [core] (JENKINS-34871) After upgrading to Jenkins 2.3 we are unable to trigger parametrized build (due to SECURITY-170 / CVE-2016-3721?)
Title: Message Title Vassilena Treneva updated an issue Jenkins / JENKINS-34871 After upgrading to Jenkins 2.3 we are unable to trigger parametrized build (due to SECURITY-170 / CVE-2016-3721?) Change By: Vassilena Treneva After upgrading to Jenkins 2.3 we are not able to pass a custom parameter specified in a property file. It looks like there is a security feature in this versions (https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11) that disables simply passing build parameters.This makes no sense to me since in my configuration (attached picture - config.jpg) I explicitly specify that I need to trigger the build with predefined properties. Maybe I am missing something?I tried to get the suggested solution working on slave level (passed java -Dhudson.model.ParametersAction.safeParameters=myParam) to slave start-up but this does not work. It looks like this needs to be passed when we start the master but this is no workaround. We simply have a lot of parameters and we cannot pass them to master at start-up.Again - maybe I am missing something in this workaround? 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] [core] (JENKINS-34871) After upgrading to Jenkins 2.3 we are unable to trigger parametrized build (due to SECURITY-170 / CVE-2016-3721?)
Title: Message Title Vassilena Treneva updated an issue Jenkins / JENKINS-34871 After upgrading to Jenkins 2.3 we are unable to trigger parametrized build (due to SECURITY-170 / CVE-2016-3721?) Change By: Vassilena Treneva Attachment: config.jpg 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] [core] (JENKINS-34871) After upgrading to Jenkins 2.3 we are unable to trigger parametrized build (due to SECURITY-170 / CVE-2016-3721?)
Title: Message Title Vassilena Treneva created an issue Jenkins / JENKINS-34871 After upgrading to Jenkins 2.3 we are unable to trigger parametrized build (due to SECURITY-170 / CVE-2016-3721?) Issue Type: Bug Assignee: huybrechts Components: core, parameterized-trigger-plugin, security Created: 2016/May/17 7:42 AM Priority: Blocker Reporter: Vassilena Treneva After upgrading to Jenkins 2.3 we are not able to pass a custom parameter specified in a property file. It looks like there is a security feature in this versions (https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11) that disables simply passing build parameters. This makes no sense to me since in my configuration I explicitly specify that I need to trigger the build with predefined properties. Maybe I am missing something? I tried to get the suggested solution working on slave level (passed java -Dhudson.model.ParametersAction.safeParameters=myParam) to slave start-up but this does not work. It looks like this needs to be passed when we start the master but this is no workaround. We simply have a lot of parameters and we cannot pass them to master at start-up. Again - maybe I am missing something in this workaround?
[JIRA] [rebuild-plugin] (JENKINS-16932) Exception: net.sf.json.JSONException: JSONObject["tag"] not found when doing a rebuild
Title: Message Title Vassilena Treneva commented on JENKINS-16932 Re: Exception: net.sf.json.JSONException: JSONObject["tag"] not found when doing a rebuild We get much the same in our environments (running on 1.645): javax.servlet.ServletException: net.sf.json.JSONException: JSONObject["tag"] not found. at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:59) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at
[JIRA] [core] (JENKINS-30030) Failed to upgrade to Jenkins 1.625
Title: Message Title Vassilena Treneva created an issue Jenkins / JENKINS-30030 Failed to upgrade to Jenkins 1.625 Issue Type: Bug Assignee: Unassigned Components: core Created: 19/Aug/15 12:44 PM Priority: Critical Reporter: Vassilena Treneva When attempting to upgrade the version of Jenkins from 1.624 to 1.625: jenkins.war Failure - hudson.util.IOException2: Failed to download from http://updates.jenkins-ci.org/download/war/1.625/jenkins.war (redirected to: http://mirrors.jenkins-ci.org/war/1.625/jenkins.war) at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:797) at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1148) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1126) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Unknown Source) Caused by: java.io.FileNotFoundException: http://mirrors.jenkins-ci.org/war/1.625/jenkins.war at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection$10.run(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection$10.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at
[JIRA] [core] (JENKINS-30030) Failed to upgrade to Jenkins 1.625
Title: Message Title Vassilena Treneva updated an issue Jenkins / JENKINS-30030 Failed to upgrade to Jenkins 1.625 Change By: Vassilena Treneva Attachment: screenshot-1.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] [core] (JENKINS-30030) Failed to upgrade to Jenkins 1.625
Title: Message Title Vassilena Treneva updated an issue Jenkins / JENKINS-30030 Failed to upgrade to Jenkins 1.625 Change By: Vassilena Treneva WhenattemptingtoupgradetheversionofJenkinsfrom1.624to1.625: http://mirrors.jenkins-ci.org/war/doesnotcontaintheproperwarfile. Ithinktherewasaverysimilardefectwiththepreviousversion jenkins.war Failure-hudson.util.IOException2:Failedtodownloadfromhttp://updates.jenkins-ci.org/download/war/1.625/jenkins.war(redirectedto:http://mirrors.jenkins-ci.org/war/1.625/jenkins.war) athudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:797) athudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1148) athudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1126) atjava.util.concurrent.Executors$RunnableAdapter.call(UnknownSource) atjava.util.concurrent.FutureTask.run(UnknownSource) athudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) atjava.lang.Thread.run(UnknownSource)Causedby:java.io.FileNotFoundException:http://mirrors.jenkins-ci.org/war/1.625/jenkins.war atsun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeMethod) atsun.reflect.NativeConstructorAccessorImpl.newInstance(UnknownSource) atsun.reflect.DelegatingConstructorAccessorImpl.newInstance(UnknownSource) atjava.lang.reflect.Constructor.newInstance(UnknownSource) atsun.net.www.protocol.http.HttpURLConnection$10.run(UnknownSource) atsun.net.www.protocol.http.HttpURLConnection$10.run(UnknownSource) atjava.security.AccessController.doPrivileged(NativeMethod) atsun.net.www.protocol.http.HttpURLConnection.getChainedException(UnknownSource) atsun.net.www.protocol.http.HttpURLConnection.getInputStream0(UnknownSource) atsun.net.www.protocol.http.HttpURLConnection.getInputStream(UnknownSource) athudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:757) ...6moreCausedby:java.io.FileNotFoundException:http://mirrors.jenkins-ci.org/war/1.625/jenkins.war atsun.net.www.protocol.http.HttpURLConnection.getInputStream0(UnknownSource) atsun.net.www.protocol.http.HttpURLConnection.getInputStream(UnknownSource) atsun.net.www.protocol.http.HttpURLConnection.getHeaderField(UnknownSource) atjava.net.URLConnection.getHeaderFieldLong(UnknownSource) atjava.net.URLConnection.getContentLengthLong(UnknownSource) atjava.net.URLConnection.getContentLength(UnknownSource) athudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:756) ...6more Add Comment
[JIRA] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]
Title: Message Title Vassilena Treneva commented on JENKINS-28155 Re: Job fails with [An existing connection was forcibly closed by the remote host] I have no actual solution for this problem but after doing many different experiments we managed to configure our windows slaves with a scheduled task (Jenkins Slave.xml attached here) and so far they are quite stable. A prerequisite is to have the test user automatically login at OS boot. 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] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]
Title: Message Title Vassilena Treneva updated an issue Jenkins / JENKINS-28155 Job fails with [An existing connection was forcibly closed by the remote host] Change By: Vassilena Treneva Attachment: JenkinsSlave.xml 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] [core] (JENKINS-29583) Unable to update to Jenkins 1.621
Title: Message Title Vassilena Treneva created an issue Jenkins / JENKINS-29583 Unable to update to Jenkins 1.621 Issue Type: Bug Assignee: Unassigned Attachments: update.jpg Components: core Created: 23/Jul/15 7:50 AM Environment: Win Server Priority: Major Reporter: Vassilena Treneva In Jenkins I get a message that a new version 1.621 is available but when I try to update I get an error. Seems that after the redirect, there is no war file there... jenkins.war Failure - hudson.util.IOException2: Failed to download from http://updates.jenkins-ci.org/download/war/1.621/jenkins.war (redirected to: http://archives.jenkins-ci.org/war/1.621/jenkins.war) at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:797) at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1148) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1126) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at
[JIRA] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]
Title: Message Title Vassilena Treneva edited a comment on JENKINS-28155 Re: Job fails with [An existing connection was forcibly closed by the remote host] Ihavenoactualsolutionforthisproblembutafterdoingmanydifferentexperimentswemanagedtoconfigureourwindowsslaves (winserver2012R2standart) withascheduledtask(JenkinsSlave.xmlattachedhere)andsofartheyarequitestable.Aprerequisiteistohavethetestuserautomatically login logged atOSboot. 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] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]
Title: Message Title Vassilena Treneva commented on JENKINS-28155 Re: Job fails with [An existing connection was forcibly closed by the remote host] On my slave where I see this error in the server management console I see this: TCP/IP failed to establish an outgoing connection because the selected local endpoint was recently used to connect to the same remote endpoint. This error typically occurs when outgoing connections are opened and closed at a high rate, causing all available local ports to be used and forcing TCP/IP to reuse a local port for an outgoing connection. To minimize the risk of data corruption, the TCP/IP standard requires a minimum time period to elapse between successive connections from a given local endpoint to a given remote endpoint. I guess Jenkins is abusing the connection somehow Any ideas how to resolve it? 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] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]
Title: Message Title Vassilena Treneva updated an issue Jenkins / JENKINS-28155 Job fails with [An existing connection was forcibly closed by the remote host] Change By: Vassilena Treneva Component/s: remoting Priority: Major Critical 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] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]
Title: Message Title Vassilena Treneva updated an issue Jenkins / JENKINS-28155 Job fails with [An existing connection was forcibly closed by the remote host] SQL server that I have installed on this slave, has some TCP settings. By default it listens to 1433. Could that be some kind of a problem? Any ideas? SQL killing some connection? The post here: http://www.redmountainsw.com/wordpress/864/tcp-provider-error-0-an-existing-connection-was-forcibly-closed-by-the-remote-host/ provides a lot of information, but my error is not on SQL side and I don’t want to turn connection pooling off… Change By: Vassilena Treneva Attachment: sql-server-manager.jpg 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] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]
Title: Message Title Vassilena Treneva commented on JENKINS-28155 Re: Job fails with [An existing connection was forcibly closed by the remote host] Hi Daniel, I will rephrase - I am sure that pinging the master from the slave is fine as I initially suspect some kind of network failure. Do you have some suggestion that can help me debug or resolve my problem? 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] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]
Vassilena Treneva created JENKINS-28155 Job fails with [An existing connection was forcibly closed by the remote host] Issue Type: Bug Assignee: Unassigned Components: core, slave-utilization Created: 29/Apr/15 1:17 PM Description: Our Windows slaves are JNLP connected using scheduled tasks (like this: https://wiki.jenkins-ci.org/display/JENKINS/Launch+Java+Web+Start+slave+agent+via+Windows+Scheduler). When a job starts working with a slave it suddenly fails because the connection was lost. It says something on slave side killed the connection. Few minutes afterwards the slave is back on-line. I am sure it is not a network issue as I tried pinging the network from system start-up till the problem occurs. I could not find find what kills the connection and disable TCP chimney (advice from google) did not work. The exception is below. I think proper behaviour would be not to fail the job but attempt to reconnect. Any hints of additional configuration that will help me resolve this issue is appreciated. Building remotely on vmbam32.eur.ad.sag (R2 Server 2012 Enterprise Windows) in workspace c:\jenkins\workspace\optimize-install FATAL: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@b7add1name=vmbam32.eur.ad.sag hudson.remoting.RequestAbortedException: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@b7add1name=vmbam32.eur.ad.sag at hudson.remoting.Request.abort(Request.java:296) at hudson.remoting.Channel.terminate(Channel.java:815) at hudson.remoting.Channel$2.terminate(Channel.java:492) at hudson.remoting.AbstractByteArrayCommandTransport$1.terminate(AbstractByteArrayCommandTransport.java:72) at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:628) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) at ..remote call to vmbam32.eur.ad.sag(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1361) at hudson.remoting.Request.call(Request.java:171) at hudson.remoting.Channel.call(Channel.java:752) at hudson.FilePath.act(FilePath.java:980) at hudson.FilePath.act(FilePath.java:969) at hudson.FilePath.mkdirs(FilePath.java:1152) at hudson.model.AbstractProject.checkout(AbstractProject.java:1269) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532) at hudson.model.Run.execute(Run.java:1744) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Caused by: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@b7add1name=vmbam32.eur.ad.sag at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:628) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.io.IOException: An existing connection was forcibly closed by the remote host at sun.nio.ch.SocketDispatcher.read0(Native Method) at
[JIRA] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]
Vassilena Treneva updated JENKINS-28155 Job fails with [An existing connection was forcibly closed by the remote host] Change By: Vassilena Treneva (29/Apr/15 1:20 PM) Component/s: windows-slaves-plugin 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] (JENKINS-17151) Jenkins fails to start after upgrading to 1.505
Vassilena Treneva created JENKINS-17151 Jenkins fails to start after upgrading to 1.505 Issue Type: Bug Assignee: Unassigned Components: core, update-center Created: 11/Mar/13 12:20 PM Description: I updated Jenkins CI from 1.503 to 1.505 and Jenkins failed to start. When trying to start it manually I get: bambpmsauto:/etc/init.d # ./jenkins start Starting Jenkins dirname: extra operand `/proc/3355/exe' Try `dirname --help' for more information. basename: missing operand Try `basename --help' for more information. Any idea? Some configuration? Project: Jenkins Priority: Major Reporter: Vassilena Treneva 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-17080) Jenkins fails to start after restart
Vassilena Treneva created JENKINS-17080 Jenkins fails to start after restart Issue Type: Bug Assignee: Unassigned Components: core Created: 05/Mar/13 5:35 PM Description: After restarting the machine, I started seeing this error when trying to start Jenkins. Any ideas what went wrong? Perhaps some configuration? bambpmsauto:/etc/init.d # ./jenkins start Starting Jenkins startproc -n 0 -s -e -l /var/log/jenkins.rc -p /var/run/jenkins .pid -t 1 /bin/su -l -s /bin/bash -c /usr/local/jdk1.7.0_17/bin/java -Djava.awt. headless=true -XX:MaxPermSize=512M -DJENKINS_HOME=/var/lib/jenkins -jar /usr/lib /jenkins/jenkins.war --javaHome=/usr/local/jdk1.7.0_17 --logfile=/var/log/jenkin s/jenkins.log --webroot=/var/cache/jenkins/war --httpPort=8080 --ajp13Port=8009 --debug=5 --handlerCountMax=100 --handlerCountMaxIdle=20 jenkins failed Project: Jenkins Priority: Critical Reporter: Vassilena Treneva 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-16546) NPE when creating job from another job
Vassilena Treneva created JENKINS-16546 NPE when creating job from another job Issue Type: Bug Assignee: Unassigned Components: core Created: 30/Jan/13 11:58 AM Description: Once we upgraded to Jenkins ver. 1.500 the option to create a job from existing job stopped working. Whenever I try to use it I get: Status Code: 500 Exception: java.lang.NullPointerException Stacktrace: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:615) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:202) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:175) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at
[JIRA] (JENKINS-16546) NPE when creating job from another job
Vassilena Treneva updated JENKINS-16546 NPE when creating job from another job Change By: Vassilena Treneva (30/Jan/13 11:59 AM) Description: OnceweupgradedtoJenkinsver.1.500theoptiontocreateajobfromexistingjobstoppedworking. Thenewjobgetscreatedbutthecontentfromtheoriginaljobisnevercopied.Basicallythewholeoptionisuselesslikethis. WheneverItrytouseitIget:StatusCode:500Exception:java.lang.NullPointerExceptionStacktrace:javax.servlet.ServletException:java.lang.NullPointerException atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:615) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:658) atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:658) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:487) atorg.kohsuke.stapler.Stapler.service(Stapler.java:164) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:45) atwinstone.ServletConfiguration.execute(ServletConfiguration.java:248) atwinstone.RequestDispatcher.forward(RequestDispatcher.java:333) atwinstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) atnet.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:202) atnet.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:175) atnet.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) atorg.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) athudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) atwinstone.FilterConfiguration.execute(FilterConfiguration.java:194) atwinstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) atwinstone.FilterConfiguration.execute(FilterConfiguration.java:194) atwinstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) athudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) athudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) athudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) atwinstone.FilterConfiguration.execute(FilterConfiguration.java:194) atwinstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
[JIRA] (JENKINS-16546) NPE when creating job from another job
Vassilena Treneva updated JENKINS-16546 NPE when creating job from another job Change By: Vassilena Treneva (30/Jan/13 12:00 PM) Environment: Linuxbambpmsauto2.6.34.7-0.4-desktop#1SMPPREEMPT2010-10-0719:07:51+0200x86_64x86_64x86_64GNU/Linux 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-16346) Upgrade to Jenkins ver. 1.499 breaks master/slave connection
Vassilena Treneva created JENKINS-16346 Upgrade to Jenkins ver. 1.499 breaks master/slave connection Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: core, slave-setup Created: 15/Jan/13 1:21 PM Description: After the upgrade all our Windows slaves could not be reached: C:\jenkinsjava -jar slave.jar -jnlpUrl http://bambpmsauto.eur.ad.sag:8080/compu ter/vmbam04.eur.ad.sag/slave-agent.jnlp Failing to obtain http://bambpmsauto.eur.ad.sag:8080/computer/vmbam04.eur.ad.sag /slave-agent.jnlp java.io.IOException: Failed to load http://bambpmsauto.eur.ad.sag:8080/computer/ vmbam04.eur.ad.sag/slave-agent.jnlp: 403 Forbidden at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:228) at hudson.remoting.Launcher.run(Launcher.java:190) at hudson.remoting.Launcher.main(Launcher.java:166) Waiting 10 seconds before retry Failing to obtain http://bambpmsauto.eur.ad.sag:8080/computer/vmbam04.eur.ad.sag /slave-agent.jnlp I also tried headless slave: CouldNotLoadArgumentException[ Could not load file/URL specified: http://bambpmsauto.eur.ad.sag:8080/computer/vmbam04.eur.ad.sag/slave-agent.jnlp] at com.sun.javaws.Main.launchApp(Unknown Source) at com.sun.javaws.Main.continueInSecureThread(Unknown Source) at com.sun.javaws.Main$1.run(Unknown Source) at java.lang.Thread.run(Unknown Source) java.io.IOException: Server returned HTTP response code: 403 for URL: http://bambpmsauto.eur.ad.sag:8080/computer/vmbam04.eur.ad.sag/slave-agent.jnlp at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) at com.sun.deploy.net.HttpUtils.followRedirects(Unknown Source) at com.sun.deploy.net.BasicHttpRequest.doRequest(Unknown Source) at com.sun.deploy.net.BasicHttpRequest.doRequest(Unknown Source) at com.sun.deploy.net.BasicHttpRequest.doGetRequest(Unknown Source) at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source) at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source) at com.sun.javaws.Main.launchApp(Unknown Source) at com.sun.javaws.Main.continueInSecureThread(Unknown Source) at com.sun.javaws.Main$1.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Environment: Linux bambpmsauto 2.6.34.7-0.4-desktop #1 SMP PREEMPT 2010-10-07 19:07:51 +0200 x86_64 x86_64 x86_64 GNU/Linux Project: Jenkins Priority: Blocker Reporter: Vassilena Treneva 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-16346) Upgrade to Jenkins ver. 1.499 breaks master/slave connection
Vassilena Treneva updated JENKINS-16346 Upgrade to Jenkins ver. 1.499 breaks master/slave connection Change By: Vassilena Treneva (15/Jan/13 1:22 PM) Description: AftertheupgradeallourWindowsslavescouldnotbereached:C:\jenkinsjava-jarslave.jar-jnlpUrlhttp://bambpmsauto.eur.ad.sag:8080/computer/vmbam04.eur.ad.sag/slave-agent.jnlpFailingtoobtainhttp://bambpmsauto.eur.ad.sag:8080/computer/vmbam04.eur.ad.sag/slave-agent.jnlpjava.io.IOException:Failedtoloadhttp://bambpmsauto.eur.ad.sag:8080/computer/vmbam04.eur.ad.sag/slave-agent.jnlp:403Forbiddenathudson.remoting.Launcher.parseJnlpArguments(Launcher.java:228)athudson.remoting.Launcher.run(Launcher.java:190)athudson.remoting.Launcher.main(Launcher.java:166)Waiting10secondsbeforeretryFailingtoobtainhttp://bambpmsauto.eur.ad.sag:8080/computer/vmbam04.eur.ad.sag/slave-agent.jnlpIalsotriedheadlessslave:CouldNotLoadArgumentException[Couldnotloadfile/URLspecified:http://bambpmsauto.eur.ad.sag:8080/computer/vmbam04.eur.ad.sag/slave-agent.jnlp] atcom.sun.javaws.Main.launchApp(UnknownSource) atcom.sun.javaws.Main.continueInSecureThread(UnknownSource) atcom.sun.javaws.Main$1.run(UnknownSource) atjava.lang.Thread.run(UnknownSource)java.io.IOException:ServerreturnedHTTPresponsecode:403forURL:http://bambpmsauto.eur.ad.sag:8080/computer/vmbam04.eur.ad.sag/slave-agent.jnlp atsun.net.www.protocol.http.HttpURLConnection.getInputStream(UnknownSource) atcom.sun.deploy.net.HttpUtils.followRedirects(UnknownSource) atcom.sun.deploy.net.BasicHttpRequest.doRequest(UnknownSource) atcom.sun.deploy.net.BasicHttpRequest.doRequest(UnknownSource) atcom.sun.deploy.net.BasicHttpRequest.doGetRequest(UnknownSource) atcom.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(UnknownSource) atcom.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(UnknownSource) atcom.sun.javaws.Main.launchApp(UnknownSource) atcom.sun.javaws.Main.continueInSecureThread(UnknownSource) atcom.sun.javaws.Main$1.run(UnknownSource) atjava.lang.Thread.run(UnknownSource) Thismustbearegressionofsomekindbecausealltheslaveswerefinebeforetheupgradeoftheversion(wewereon1.497as1.498hadsimilarproblems) 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-16346) Upgrade to Jenkins ver. 1.499 breaks master/slave connection
Vassilena Treneva commented on JENKINS-16346 Upgrade to Jenkins ver. 1.499 breaks master/slave connection I will try both options now but will hold off that version for the moment If I have to explicitly pass -jnlpCredentials username:password then I guess Jenkins needs to generate the proper command line when configuring the slaves. I mean those: Run from slave command line: javaws http://bambpmsauto.eur.ad.sag:8080/computer/vmbam04.eur.ad.sag/slave-agent.jnlp Or if the slave is headless: java -jar slave.jar -jnlpUrl http://bambpmsauto.eur.ad.sag:8080/computer/vmbam04.eur.ad.sag/slave-agent.jnlp We have quite a lot of slaves and it will take a while to go tru all of them for reconfiguration 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-16338) Jenkins fails to keep connection alive on Windows 8
Vassilena Treneva created JENKINS-16338 Jenkins fails to keep connection alive on Windows 8 Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: core, slave-setup, slave-status Created: 14/Jan/13 2:52 PM Description: Launch slave agent via Java Web Start is the connection option. At some point of time, Jenkins fails to reach the slave. The error I see is: java Please wait while the installer processes files, 30 out of 39 modules done java FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Socket closed hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Socket closed at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:672) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158) at $Proxy46.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:915) at hudson.Launcher$ProcStarter.join(Launcher.java:360) at hudson.tasks.Ant.perform(Ant.java:217) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:592) at hudson.model.Run.execute(Run.java:1543) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: hudson.remoting.RequestAbortedException: java.net.SocketException: Socket closed at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:732) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.net.SocketException: Socket closed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:237) at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2248) at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2541) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2551) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1296) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Environment: Master Jenkins: Linux bambpmsauto 2.6.34.7-0.4-desktop #1 SMP PREEMPT 2010-10-07 19:07:51 +0200 x86_64 x86_64 x86_64 GNU/Linux Jenkins ver. 1.497 Slave: Windows 8 Pro 64-bit edition Project: Jenkins Priority: Major Reporter: Vassilena Treneva 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-16338) Jenkins fails to keep connection alive on Windows 8
Vassilena Treneva updated JENKINS-16338 Jenkins fails to keep connection alive on Windows 8 Change By: Vassilena Treneva (14/Jan/13 2:53 PM) Description: LaunchslaveagentviaJavaWebStartistheconnectionoption.Atsomepointoftime,Jenkinsfailstoreachtheslave.TheerrorIseeis:[java]Pleasewaitwhiletheinstallerprocessesfiles,30outof39modulesdone[java]FATAL:hudson.remoting.RequestAbortedException:java.net.SocketException:Socketclosedhudson.remoting.RequestAbortedException:hudson.remoting.RequestAbortedException:java.net.SocketException:Socketclosed athudson.remoting.Request.call(Request.java:174) athudson.remoting.Channel.call(Channel.java:672) athudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158) at$Proxy46.join(UnknownSource) athudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:915) athudson.Launcher$ProcStarter.join(Launcher.java:360) athudson.tasks.Ant.perform(Ant.java:217) athudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810) athudson.model.Build$BuildExecution.build(Build.java:199) athudson.model.Build$BuildExecution.doRun(Build.java:160) athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:592) athudson.model.Run.execute(Run.java:1543) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:236)Causedby:hudson.remoting.RequestAbortedException:java.net.SocketException:Socketclosed athudson.remoting.Request.abort(Request.java:299) athudson.remoting.Channel.terminate(Channel.java:732) athudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69)Causedby:java.net.SocketException:Socketclosed atjava.net.SocketInputStream.socketRead0(NativeMethod) atjava.net.SocketInputStream.read(SocketInputStream.java:129) atjava.io.BufferedInputStream.fill(BufferedInputStream.java:218) atjava.io.BufferedInputStream.read(BufferedInputStream.java:237) atjava.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2248) atjava.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2541) atjava.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2551) atjava.io.ObjectInputStream.readObject0(ObjectInputStream.java:1296) atjava.io.ObjectInputStream.readObject(ObjectInputStream.java:350) athudson.remoting.Command.readFrom(Command.java:92) athudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59) athudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Thelastlogentryunder/var/lib/jenkins/logs/slaves/vmbam08.eur.ad.sagshowsthis:JNLPagentconnectedfrom/10.74.21.234===[HUDSONREMOTINGCAPACITY]===rO0ABXNyABpodWRzb24ucmVtb3RpbmcuQ2FwYWJpbGl0eQABAgABSgAEbWFza3hwAAY= 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-15978) NPE on job-import plugin: impossible to import
Vassilena Treneva created JENKINS-15978 NPE on job-import plugin: impossible to import Issue Type: Bug Assignee: jieryn Components: job-import Created: 29/Nov/12 1:02 PM Description: When I selected the job I wanted to import I got: Status Code: 500 Exception: java.lang.NullPointerException Stacktrace: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:615) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:202) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:175) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at
[JIRA] (JENKINS-15978) NPE on job-import plugin: impossible to import
Vassilena Treneva updated JENKINS-15978 NPE on job-import plugin: impossible to import Change By: Vassilena Treneva (29/Nov/12 1:05 PM) Attachment: o.jpg 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-15754) Jenkins fails to save configuration when using Invoke Gradle with net.sf.json.JSONException: null object
Vassilena Treneva updated JENKINS-15754 Jenkins fails to save configuration when using Invoke Gradle with net.sf.json.JSONException: null object Change By: Vassilena Treneva (07/Nov/12 9:49 AM) Attachment: JenkinsIsYourFriend.jpg 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-15754) Jenkins fails to save configuration when using Invoke Gradle with net.sf.json.JSONException: null object
Vassilena Treneva
created JENKINS-15754
Jenkins fails to save configuration when using Invoke Gradle with net.sf.json.JSONException: null object
Issue Type:
Bug
Affects Versions:
current
Assignee:
Gregory Boissinot
Attachments:
JenkinsIsYourFriend.jpg
Components:
gradle, gradle-jpi-plugin
Created:
07/Nov/12 9:48 AM
Description:
Error
Failed to parse form data. Please report this problem as a bug
JSON={"":"","builder":{antName:(Default),antOpts:,buildFile:trunk/test-automation/Tools/EDATools/event-generator.xml,kind:hudson.tasks.Ant,properties:cis.tools.home=${WORKSPACE}/CISTools","stapler-class":"hudson.tasks.Ant","targets":""},{"antName":"(Default)","antOpts":"","buildFile":"trunk/test-automation/Tools/EDATools/broker.configs/build.xml","kind":"hudson.tasks.Ant","properties":"eda.broker.config.modules=\ncom.softwareag.install.root=${installdir}\ncis.tools.home=${WORKSPACE}/CISTools,stapler-class:hudson.tasks.Ant,targets:create},{"antName":"(Default)","antOpts":"","buildFile":"trunk/test-automation/Tools/EDATools/create.eda.xml.configs.xml","kind":"hudson.tasks.Ant","properties":"","stapler-class":"hudson.tasks.Ant","targets":"parse.xml.configs"},{antName:(Default),antOpts:,buildFile:trunk/test-automation/Tools/EDATools/generate.properties.xml,kind:hudson.tasks.Ant,properties:property.file=${WORKSPACE}/trunk/test-automation/Tests/QFT/${testfolder}/shared/TestsExecutionDefault.properties\nproperty.file.resolved=${WORKSPACE}/trunk/test-automation/Tests/QFT/${testfolder}/shared/ResolvedTestsExecutionDefault.properties\ncis.tools.home=${WORKSPACE}/CISTools\nqft.tests.home=${WORKSPACE}/trunk/test-automation/Tests/QFT\neda.tools.home=${WORKSPACE}/trunk/test-automation/Tools/EDATools","stapler-class":"hudson.tasks.Ant","targets":"load.properties"},{"antName":"(Default)","antOpts":"","buildFile":"./CISTools/ant_targets/qftest/build.xml","kind":"hudson.tasks.Ant","properties":"task.home=${WORKSPACE}/CISTools\nreportdir=${WORKSPACE}/trunk/test-automation/Tests/QFT/output/edaconsole\nlogdir=${WORKSPACE}/trunk/test-automation/Tests/QFT/output/edaconsole\n\n#Test files separated by space\nsuite=${WORKSPACE}/trunk/test-automation/Tests/QFT/${testfolder}/shared/qft/startEclipse.qft ${WORKSPACE}/trunk/test-automation/Tests/QFT/${testfolder}/designer/edaconsole/edacons_2consoles.qft ${WORKSPACE}/trunk/test-automation/Tests/QFT/${testfolder}/designer/edaconsole/edacons_2consoles100th.qft ${WORKSPACE}/trunk/test-automation/Tests/QFT/${testfolder}/designer/edaconsole/edacons_createCons_applyRevertAllTabs.qft ${WORKSPACE}/trunk/test-automation/Tests/QFT/${testfolder}/designer/edaconsole/edacons_createCons_CheckTabs.qft ${WORKSPACE}/trunk/test-automation/Tests/QFT/${testfolder}/designer/edaconsole/edacons_dispFormatNoTopicNoType.qft ${WORKSPACE}/trunk/test-automation/Tests/QFT/${testfolder}/designer/edaconsole/edacons_dispFormatTopicOnly.qft ${WORKSPACE}/trunk/test-automation/Tests/QFT/${testfolder}/designer/edaconsole/edacons_dispFormatType100th.qft ${WORKSPACE}/trunk/test-automation/Tests/QFT/${testfolder}/shared/qft/stopEclipse.qft \n\n#Arguments passed for execution:\nqftest.arguments=-batch -runlog ${WORKSPACE}/trunk/test-automation/Tests/QFT/output/edaconsole/+b.qrl -report.xml ${WORKSPACE}/trunk/test-automation/Tests/QFT/output/edaconsole -report.html ${WORKSPACE}/trunk/test-automation/Tests/QFT/output/edaconsole","stapler-class":"hudson.tasks.Ant","targets":"run.testsuite.witharguments"},{"antName":"(Default)","antOpts":"","buildFile":"./CISTools/ant_targets/qftest/build.xml","kind":"hudson.tasks.Ant","properties":"task.home=${WORKSPACE}/CISTools\nreportdir=${WORKSPACE}/trunk/test-automation/Tests/QFT/output/eventTypeEditor\nlogdir=${WORKSPACE}/trunk/test-automation/Tests/QFT/output/eventTypeEditor\n\n#Test files separated by space\nsuite=${WORKSPACE}/trunk/test-automation/Tests/QFT/${testfolder}/shared/qft/startEclipse.qft
