[JIRA] (JENKINS-60458) Pipeline failed with "com.thoughtworks.xstream.io.StreamException : null" and then resumed after Jenkins restart
Title: Message Title
Ivan Udovichenko updated an issue
Jenkins / JENKINS-60458
Pipeline failed with "com.thoughtworks.xstream.io.StreamException : null" and then resumed after Jenkins restart
Change By:
Ivan Udovichenko
The job failed mostly instantly. And after jenkins restart it started the job again for unknown reason: # Job failed for unknown reason (could please someone explain, why ?) # Job was started after jenkins restart although if finished with `FAILURE` state. # After following `Pipeline Steps` link of the job leads to stackrace. (posted text below)Jenkins ver. 2.190.3workflow-cps@2.76workflow-cps-global-lib@2.15 {code} Started by upstream project "create-product-env" build number 14922 originally caused by: Started by upstream project "test-offline-weekly" build number 123 originally caused by: Started by timer Started by user degorenko Started by upstream project "create-product-env" build number 14902 originally caused by: Started by upstream project "test-offline-weekly" build number 123Checking out git ssh://product-jenk...@git.repo.local:29418/product-env/pipelines into /var/lib/jenkins/jobs/rollout-product-env/workspace@script to read rollout-product-env.groovyusing credential gerritWiping out workspace first.Cloning the remote Git repositoryCloning repository ssh://product-jenk...@git.repo.local:29418/product-env/pipelines > git init /var/lib/jenkins/jobs/rollout-product-env/workspace@script # timeout=10Fetching upstream changes from ssh://product-jenk...@git.repo.local:29418/product-env/pipelines > git --version # timeout=10using GIT_SSH to set credentials > git fetch --tags --progress ssh://product-jenk...@git.repo.local:29418/product-env/pipelines +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url ssh://product-jenk...@git.repo.local:29418/product-env/pipelines # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url ssh://product-jenk...@git.repo.local:29418/product-env/pipelines # timeout=10Fetching upstream changes from ssh://product-jenk...@git.repo.local:29418/product-env/pipelinesusing GIT_SSH to set credentials > git fetch --tags --progress ssh://product-jenk...@git.repo.local:29418/product-env/pipelines stable # timeout=10 > git rev-parse origin/FETCH_HEAD^ { commit} # timeout=10 > git rev-parse FETCH_HEAD^{commit} # timeout=10Checking out Revision 5f9556f36f6a3782a95b851600841eeb7b06b6db (FETCH_HEAD) > git config core.sparsecheckout # timeout=10 > git checkout -f 5f9556f36f6a3782a95b851600841eeb7b06b6db # timeout=10Commit message: "Merge branch 'master' into stable" > git rev-list --no-walk c345783c54f675add123293994bbfef93ec4c35c # timeout=10Running in Durability level: PERFORMANCE_OPTIMIZEDLoading library pipeline-library@masterAttempting to resolve master from remote references... > git --version # timeout=10using GIT_SSH to set credentials > git ls-remote -h ssh://product-jenk...@git.repo.local:29418/product-ci/pipeline-library # timeout=10Found
[JIRA] (JENKINS-60458) Pipeline failed with "com.thoughtworks.xstream.io.StreamException : null" and then resumed after Jenkins restart
Title: Message Title
Ivan Udovichenko updated an issue
Jenkins / JENKINS-60458
Pipeline failed with "com.thoughtworks.xstream.io.StreamException : null" and then resumed after Jenkins restart
Change By:
Ivan Udovichenko
The job failed mostly instantly. And after jenkins restart it started the job again for unknown reason: # Job failed for unknown reason (could please someone explain, why ?) # Job was started after jenkins restart although if finished with `FAILURE` state. # After following `Pipeline Steps` link of the job leads to stackrace. (posted text below)Jenkins ver. 2.190.3workflow-cps@2.76workflow-cps-global-lib@2.15 {code} Started by upstream project "create-product-env" build number 14922 originally caused by: Started by upstream project "test-offline-weekly" build number 123 originally caused by: Started by timer Started by user degorenko Started by upstream project "create-product-env" build number 14902 originally caused by: Started by upstream project "test-offline-weekly" build number 123Checking out git ssh://product-jenk...@git.repo.local29418/product-env/pipelines into /var/lib/jenkins/jobs/rollout-product-env/workspace@script to read rollout-product-env.groovyusing credential gerritWiping out workspace first.Cloning the remote Git repositoryCloning repository ssh://product-jenk...@git.repo.local29418/product-env/pipelines > git init /var/lib/jenkins/jobs/rollout-product-env/workspace@script # timeout=10Fetching upstream changes from ssh://product-jenk...@git.repo.local29418/product-env/pipelines > git --version # timeout=10using GIT_SSH to set credentials > git fetch --tags --progress ssh://product-jenk...@git.repo.local29418/product-env/pipelines +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url ssh://product-jenk...@git.repo.local29418/product-env/pipelines # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url ssh://product-jenk...@git.repo.local29418/product-env/pipelines # timeout=10Fetching upstream changes from ssh://product-jenk...@git.repo.local29418/product-env/pipelinesusing GIT_SSH to set credentials > git fetch --tags --progress ssh://product-jenk...@git.repo.local29418/product-env/pipelines stable # timeout=10 > git rev-parse origin/FETCH_HEAD^ { commit} # timeout=10 > git rev-parse FETCH_HEAD^{commit} # timeout=10Checking out Revision 5f9556f36f6a3782a95b851600841eeb7b06b6db (FETCH_HEAD) > git config core.sparsecheckout # timeout=10 > git checkout -f 5f9556f36f6a3782a95b851600841eeb7b06b6db # timeout=10Commit message: "Merge branch 'master' into stable" > git rev-list --no-walk c345783c54f675add123293994bbfef93ec4c35c # timeout=10Running in Durability level: PERFORMANCE_OPTIMIZEDLoading library pipeline-library@masterAttempting to resolve master from remote references... > git --version # timeout=10using GIT_SSH to set credentials > git ls-remote -h ssh://product-jenk...@gerrit.product.git.local:29418/product-ci/pipeline-library # timeout=10Found
[JIRA] (JENKINS-60458) Pipeline failed with "com.thoughtworks.xstream.io.StreamException : null" and then resumed after Jenkins restart
Title: Message Title Ivan Udovichenko updated an issue Jenkins / JENKINS-60458 Pipeline failed with "com.thoughtworks.xstream.io.StreamException : null" and then resumed after Jenkins restart Change By: Ivan Udovichenko Attachment: screenshot-1.png 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.203536.1576150122000.6290.1576150320238%40Atlassian.JIRA.
[JIRA] (JENKINS-60458) Pipeline failed with "com.thoughtworks.xstream.io.StreamException : null" and then resumed after Jenkins restart
Title: Message Title Ivan Udovichenko created an issue Jenkins / JENKINS-60458 Pipeline failed with "com.thoughtworks.xstream.io.StreamException : null" and then resumed after Jenkins restart Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2019-12-12 11:28 Priority: Major Reporter: Ivan Udovichenko The job failed mostly instantly. And after jenkins restart it started the job again for unknown reason: Job failed for unknown reason (could please someone explain, why ?) Job was started after jenkins restart although if finished with `FAILURE` state. After following `Pipeline Steps` link of the job leads to stackrace. (posted text below) Jenkins ver. 2.190.3 workflow-cps@2.76 workflow-cps-global-lib@2.15 Started by upstream project "create-product-env" build number 14922 originally caused by: Started by upstream project "test-offline-weekly" build number 123 originally caused by: Started by timer Started by user degorenko Started by upstream project "create-product-env" build number 14902 originally caused by: Started by upstream project "test-offline-weekly" build number 123 Checking out git ssh://product-jenk...@git.repo.local29418/product-env/pipelines into /var/lib/jenkins/jobs/rollout-product-env/workspace@script to read rollout-product-env.groovy using credential gerrit Wiping out workspace first. Cloning the remote Git repository Cloning repository ssh://product-jenk...@git.repo.local29418/product-env/pipelines > git init
[JIRA] (JENKINS-46961) Unable to abort job: "Resuming build at [...] after Jenkins restart"
Title: Message Title Ivan Udovichenko commented on JENKINS-46961 Re: Unable to abort job: "Resuming build at [...] after Jenkins restart" Faced the issues today: Jenkins ver. 2.190.3 workflow-cps@2.76 workflow-cps-global-lib@2.15 It happened after Jenkins restart. 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.185333.1505825436000.6184.1576145220696%40Atlassian.JIRA.
