-
Bug
-
Resolution: Fixed
-
Blocker
-
Jenkins 2.29
Pipeline: Stage Step 2.2
Pipeline: Stage View Plugin 2.2
After having updated today (Nov/07/2016) morning, all the stage views are suddenly empty?
the project is a MultiBranch pipeline job with the Jenkinsfile in the git repository
even the console looks now empty?
> git rev-list 244a7c01507c7379fbd100355d378c9e6a8a743f # timeout=10 [Pipeline] properties [Pipeline] node [Pipeline] node [Pipeline] sh [Pipeline] ws [Pipeline] ws [Pipeline] stage [Pipeline] stage [Pipeline] checkout [Pipeline] sh [Pipeline] // stage [Pipeline] // stage [Pipeline] load [Pipeline] load [Pipeline] // load [Pipeline] // load [Pipeline] stage [Pipeline] stage [Pipeline] sh [Pipeline] stage [Pipeline] stage [Pipeline] step [Pipeline] step [Pipeline] step [Pipeline] step [Pipeline] step [Pipeline] fileExists [Pipeline] step [Pipeline] // stage [Pipeline] // stage [Pipeline] // stage [Pipeline] // stage [Pipeline] // ws [Pipeline] // ws [Pipeline] // node [Pipeline] // node [Pipeline] End of Pipeline Finished: SUCCESS
which was before
[Pipeline] properties [Pipeline] node Still waiting to schedule task Waiting for next available executor Running on master in /var/lib/jenkins/workspace/cloud_master-IBS37M5ZPUHZSAAHBJJ6Q4WJM5EKXZ3OYKCVP663I3GWGSPUSPQA [Pipeline] { [Pipeline] sh [cloud_master-IBS37M5ZPUHZSAAHBJJ6Q4WJM5EKXZ3OYKCVP663I3GWGSPUSPQA] Running shell script + mkdir -p /var/lib/jenkins/releases/master/cloud/ [Pipeline] ws Running in /var/lib/jenkins/releases/master/cloud [Pipeline] { [Pipeline] stage [Pipeline] { (Checkout) [Pipeline] checkout > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url /***/cloud.git # timeout=10 Pruning obsolete local branches Fetching upstream changes from /***/cloud.git > git --version # timeout=10 using GIT_SSH to set credentials > git fetch --tags --progress /***/cloud.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 244a7c01507c7379fbd100355d378c9e6a8a743f (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 244a7c01507c7379fbd100355d378c9e6a8a743f [Pipeline] sh [cloud] Running shell script + git checkout master Switched to branch 'master' Your branch is up-to-date with 'origin/master'. + git pull Already up-to-date. [Pipeline] } [Pipeline] load [Pipeline] { (/var/lib/jenkins/releases/master/cloud/../shared_jenkins_php) [Pipeline] } [Pipeline] // load [Pipeline] stage [Pipeline] { (Building) [Pipeline] sh [cloud] Running shell script + nice -n19 ant -f build/build.xml jenkinsBuild Buildfile: /var/lib/jenkins/releases/master/cloud/build/build.xml jenkinsBuild: ciSetup:
<< cut long build steps of ANT >>
[Pipeline] step [ANALYSIS-COLLECTOR] Computing warning deltas based on reference build #89 [Pipeline] fileExists [Pipeline] step Publishing Javadoc [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // ws [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Finished: SUCCESS
is this a known issue that i have not found, or did some of the triggers have changed ?
- blocks
-
JENKINS-39599 Pipeline graph not rendering for a simple Pipeline
-
- Closed
-
- is blocked by
-
JENKINS-42969 Computer.addAction will throw UnsupportedOperationException
-
- Resolved
-
-
JENKINS-39404 Actionable should have methods for removing actions
-
- Closed
-
- is related to
-
JENKINS-39541 Pipeline Stage View No Longer Shown After Plugin Upgrade
-
- Closed
-
- links to
[JENKINS-39555] Stage view is empty
Description |
Original:
After having updated today (Nov/07/2016) morning, all the stage views are suddenly empty? the project is a MultiBranch pipeline job with the Jenkinsfile in the git repository even the console looks now empty? {{ > git rev-list 244a7c01507c7379fbd100355d378c9e6a8a743f # timeout=10 [Pipeline] properties [Pipeline] node [Pipeline] node [Pipeline] sh [Pipeline] ws [Pipeline] ws [Pipeline] stage [Pipeline] stage [Pipeline] checkout [Pipeline] sh [Pipeline] // stage [Pipeline] // stage [Pipeline] load [Pipeline] load [Pipeline] // load [Pipeline] // load [Pipeline] stage [Pipeline] stage [Pipeline] sh [Pipeline] stage [Pipeline] stage [Pipeline] step [Pipeline] step [Pipeline] step [Pipeline] step [Pipeline] step [Pipeline] fileExists [Pipeline] step [Pipeline] // stage [Pipeline] // stage [Pipeline] // stage [Pipeline] // stage [Pipeline] // ws [Pipeline] // ws [Pipeline] // node [Pipeline] // node [Pipeline] End of Pipeline Finished: SUCCESS }} which was before {{ [Pipeline] load [Pipeline] { (/var/lib/jenkins/releases/master/cloud/../shared_jenkins_php) [Pipeline] } [Pipeline] // load [Pipeline] stage [Pipeline] { (Building) [Pipeline] sh [cloud] Running shell script + nice -n19 ant -f build/build.xml jenkinsBuild Buildfile: /var/lib/jenkins/releases/master/cloud/build/build.xml jenkinsBuild: ciSetup: }} << cut long build steps of ANT >> {{ [Pipeline] step [ANALYSIS-COLLECTOR] Computing warning deltas based on reference build #89 [Pipeline] fileExists [Pipeline] step Publishing Javadoc [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // ws [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Finished: SUCCESS }} is this a known issue that i have not found, or did some of the triggers have changed ? |
New:
After having updated today (Nov/07/2016) morning, all the stage views are suddenly empty? the project is a MultiBranch pipeline job with the Jenkinsfile in the git repository even the console looks now empty? {noformat} > git rev-list 244a7c01507c7379fbd100355d378c9e6a8a743f # timeout=10 [Pipeline] properties [Pipeline] node [Pipeline] node [Pipeline] sh [Pipeline] ws [Pipeline] ws [Pipeline] stage [Pipeline] stage [Pipeline] checkout [Pipeline] sh [Pipeline] // stage [Pipeline] // stage [Pipeline] load [Pipeline] load [Pipeline] // load [Pipeline] // load [Pipeline] stage [Pipeline] stage [Pipeline] sh [Pipeline] stage [Pipeline] stage [Pipeline] step [Pipeline] step [Pipeline] step [Pipeline] step [Pipeline] step [Pipeline] fileExists [Pipeline] step [Pipeline] // stage [Pipeline] // stage [Pipeline] // stage [Pipeline] // stage [Pipeline] // ws [Pipeline] // ws [Pipeline] // node [Pipeline] // node [Pipeline] End of Pipeline Finished: SUCCESS {noformat} which was before {noformat} [Pipeline] load [Pipeline] { (/var/lib/jenkins/releases/master/cloud/../shared_jenkins_php) [Pipeline] } [Pipeline] // load [Pipeline] stage [Pipeline] { (Building) [Pipeline] sh [cloud] Running shell script + nice -n19 ant -f build/build.xml jenkinsBuild Buildfile: /var/lib/jenkins/releases/master/cloud/build/build.xml jenkinsBuild: ciSetup: {noformat} << cut long build steps of ANT >> {noformat} [Pipeline] step [ANALYSIS-COLLECTOR] Computing warning deltas based on reference build #89 [Pipeline] fileExists [Pipeline] step Publishing Javadoc [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // ws [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Finished: SUCCESS {noformat} is this a known issue that i have not found, or did some of the triggers have changed ? |
Description |
Original:
After having updated today (Nov/07/2016) morning, all the stage views are suddenly empty? the project is a MultiBranch pipeline job with the Jenkinsfile in the git repository even the console looks now empty? {noformat} > git rev-list 244a7c01507c7379fbd100355d378c9e6a8a743f # timeout=10 [Pipeline] properties [Pipeline] node [Pipeline] node [Pipeline] sh [Pipeline] ws [Pipeline] ws [Pipeline] stage [Pipeline] stage [Pipeline] checkout [Pipeline] sh [Pipeline] // stage [Pipeline] // stage [Pipeline] load [Pipeline] load [Pipeline] // load [Pipeline] // load [Pipeline] stage [Pipeline] stage [Pipeline] sh [Pipeline] stage [Pipeline] stage [Pipeline] step [Pipeline] step [Pipeline] step [Pipeline] step [Pipeline] step [Pipeline] fileExists [Pipeline] step [Pipeline] // stage [Pipeline] // stage [Pipeline] // stage [Pipeline] // stage [Pipeline] // ws [Pipeline] // ws [Pipeline] // node [Pipeline] // node [Pipeline] End of Pipeline Finished: SUCCESS {noformat} which was before {noformat} [Pipeline] load [Pipeline] { (/var/lib/jenkins/releases/master/cloud/../shared_jenkins_php) [Pipeline] } [Pipeline] // load [Pipeline] stage [Pipeline] { (Building) [Pipeline] sh [cloud] Running shell script + nice -n19 ant -f build/build.xml jenkinsBuild Buildfile: /var/lib/jenkins/releases/master/cloud/build/build.xml jenkinsBuild: ciSetup: {noformat} << cut long build steps of ANT >> {noformat} [Pipeline] step [ANALYSIS-COLLECTOR] Computing warning deltas based on reference build #89 [Pipeline] fileExists [Pipeline] step Publishing Javadoc [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // ws [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Finished: SUCCESS {noformat} is this a known issue that i have not found, or did some of the triggers have changed ? |
New:
After having updated today (Nov/07/2016) morning, all the stage views are suddenly empty? the project is a MultiBranch pipeline job with the Jenkinsfile in the git repository even the console looks now empty? {noformat} > git rev-list 244a7c01507c7379fbd100355d378c9e6a8a743f # timeout=10 [Pipeline] properties [Pipeline] node [Pipeline] node [Pipeline] sh [Pipeline] ws [Pipeline] ws [Pipeline] stage [Pipeline] stage [Pipeline] checkout [Pipeline] sh [Pipeline] // stage [Pipeline] // stage [Pipeline] load [Pipeline] load [Pipeline] // load [Pipeline] // load [Pipeline] stage [Pipeline] stage [Pipeline] sh [Pipeline] stage [Pipeline] stage [Pipeline] step [Pipeline] step [Pipeline] step [Pipeline] step [Pipeline] step [Pipeline] fileExists [Pipeline] step [Pipeline] // stage [Pipeline] // stage [Pipeline] // stage [Pipeline] // stage [Pipeline] // ws [Pipeline] // ws [Pipeline] // node [Pipeline] // node [Pipeline] End of Pipeline Finished: SUCCESS {noformat} which was before {noformat} [Pipeline] properties [Pipeline] node Still waiting to schedule task Waiting for next available executor Running on master in /var/lib/jenkins/workspace/cloud_master-IBS37M5ZPUHZSAAHBJJ6Q4WJM5EKXZ3OYKCVP663I3GWGSPUSPQA [Pipeline] { [Pipeline] sh [cloud_master-IBS37M5ZPUHZSAAHBJJ6Q4WJM5EKXZ3OYKCVP663I3GWGSPUSPQA] Running shell script + mkdir -p /var/lib/jenkins/releases/master/cloud/ [Pipeline] ws Running in /var/lib/jenkins/releases/master/cloud [Pipeline] { [Pipeline] stage [Pipeline] { (Checkout) [Pipeline] checkout > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url /***/cloud.git # timeout=10 Pruning obsolete local branches Fetching upstream changes from /***/cloud.git > git --version # timeout=10 using GIT_SSH to set credentials > git fetch --tags --progress /***/cloud.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 244a7c01507c7379fbd100355d378c9e6a8a743f (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 244a7c01507c7379fbd100355d378c9e6a8a743f [Pipeline] sh [cloud] Running shell script + git checkout master Switched to branch 'master' Your branch is up-to-date with 'origin/master'. + git pull Already up-to-date. [Pipeline] } [Pipeline] load [Pipeline] { (/var/lib/jenkins/releases/master/cloud/../shared_jenkins_php) [Pipeline] } [Pipeline] // load [Pipeline] stage [Pipeline] { (Building) [Pipeline] sh [cloud] Running shell script + nice -n19 ant -f build/build.xml jenkinsBuild Buildfile: /var/lib/jenkins/releases/master/cloud/build/build.xml jenkinsBuild: ciSetup: {noformat} << cut long build steps of ANT >> {noformat} [Pipeline] step [ANALYSIS-COLLECTOR] Computing warning deltas based on reference build #89 [Pipeline] fileExists [Pipeline] step Publishing Javadoc [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // ws [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Finished: SUCCESS {noformat} is this a known issue that i have not found, or did some of the triggers have changed ? |
I came to report the exact same issue; today I upgraded from 2.23 to 2.29, including all plugins, and stages seem to be broken now. Downgrading plugins didn't help, downgrading Jenkins back to 2.23 worked (both with previous plugin versions and all plugins at latest version). I did not try any Jenkins versions between 2.23 and 2.29... (the devs were getting annoyed by me restarting the production Jenkins
)