-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
post-build-status-update (maybe all pipeline jobs?) is broken #2413
Comments
"Pipeline: Nodes and Processes" doesn't show up in manage plugins, probably because it failed to load, so I can't roll it back via the Jenkins UI. |
there was a security release of jenkins yesterday so I did that during quiet hours and ran plugin updates afterward, I suppose this got tangled up during that process sorry, I really should remember to post in issues when I do these updates |
@rvagg anything I can do to help with this? |
What a tedious beast Jenkins has become. The number of plugins we use is partly to blame of course. So, the plugin named Pipeline: Nodes and Processes (a.k.a. "workflow-durable-task-step") has a new version that breaks with the LTS version of Jenkins. It's apparently fine with the latest release of Jenkins but we use LTS and it's incompatible, for whatever reason. I've had to manually downgrade the plugin (rename the workflow-durable-task-step.bak to workflow-durable-task-step.jpi in /var/lib/jenkins/plugins/ and restart) to make Jenkins work properly. While trying to fix this the Github Auth plugin even broke. It appears to be back to "normal" now, I'll do a bit of testing to make sure. @nodejs/jenkins-admins DO NOT UPGRADE "Pipeline: Nodes and Processes" in the plugin manager until we know the version works with the version of Jenkins we're running. |
seems to be working OK also ... post-build-status-update is up to build # 1,064,243, that's a lota builds. |
Looks like it's not working properly (not all machines are posting job status update): nodejs/node#34836 / https://ci.nodejs.org/job/node-test-pull-request/ nodejs/node#34862 / https://ci.nodejs.org/job/node-test-pull-request/32877/ Reopening, but if this is a different issue I can open a new one instead. |
I suspect it's another issue -- https://ci.nodejs.org/job/post-build-status-update/ runs are now passing. For nodejs/node#34836 https://ci.nodejs.org/job/node-test-pull-request/32876/ is a resumed build, so not all platforms were run (only the ones that didn't pass in the build that was being resumed). For nodejs/node#34862 I see: |
Right, on my PR it wasn't showing while running, and on the bot logs there were no start events for those platforms as well. I'll keep an eye tomorrow and if things are ok I'll close here, might've been an intermittent issue. |
Haven't seen this anymore and haven't seen anyone complaining, so closing. |
Was just on this week's release mentoring session and we noticed that starting CI's wasn't triggering comments/status back to the pull requests. I've dug into it and it looks like https://ci.nodejs.org/job/post-build-status-update/ (which posts status to the github-bot) is currently broken.
The console output for these jobs is useless (they're empty) but "Pipeline Steps"->"Start of pipeline" (e.g. https://ci.nodejs.org/job/post-build-status-update/1062413/execution/node/2/, but I don't expect that link to live long given that the job is executed multiple times for a requested CI):
On https://ci.nodejs.org/manage there's this big red box:
I've no idea how we got into this state (I assume it happened overnight as we were getting status updates in pull requests yesterday). We're on the most recent LTS version 2.235.5 (which is lower than 2.248).
The text was updated successfully, but these errors were encountered: