-
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 jenkins job seems to be broken #3159
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
I suspect this is related to the Script Security plugin update from yesterday (#3158) 😞. The bot is still posting comments from other webhook triggers, (e.g. nodejs/node#46365 (comment) from 2 hours ago) so it looks like the issue is specifically with the post-build-status-update job. I am seeing errors in the main Jenkins system log (https://ci.nodejs.org/log/all) relating to the post-build-status-update job:
|
There's a note in https://www.jenkins.io/security/advisory/2023-01-24/ about map constructors but AFAICT we're not using those in https://github.com/nodejs/build/blob/main/jenkins/pipelines/post-build-status-update.jenkinsfile. |
This is probably the more pertinent error from the Jenkins system log:
and on the server there is indeed no log file:
|
I copied log.gz to /tmp, uncompressed it, and got:
|
I'm going to try updating the Groovy plugin from 442.v817e6d937d6c to 453.vcdb_a_c5c99890. |
Still getting the same error in the compressed job log from recent post-build-status-update job runs. |
Looks like Jenkins does backup plugins when updating -- the backups have a
Going to try rolling back the Script Security plugin as a stop gap 🤞. My suspicion is that we'll need to update some of the pipeline plugins that we currently cannot until we move to the current Jenkins LTS. We should be able to move to current Jenkins LTS now (#3030 (comment)) with the loss of End-of-Life Linux distros (e.g. Debian 8, 9) although I'd rather do that in a more planned fashion (i.e. not right at the end of my working hours). |
Downgrading the Script Security plugin appears to have got the job working again. |
A few of the other jobs started failing since the downgraded security plugin with
e.g. https://ci.nodejs.org/job/node-test-commit-freebsd/47893/console |
Looks like the failure is back after the issues with today's failed Jenkins update (https://github.com/nodejs/build/issues/3176#issuecomment-1462642773)😞 |
Looks like this has fixed itself once all plugins were updated and Jenkins updated to 2.387.1. I have a test CI build running https://ci.nodejs.org/job/node-test-pull-request/50307/ which is posting "CI started" comments and build status to the GitHub PR. |
https://ci.nodejs.org/job/post-build-status-update/buildTimeTrend
The text was updated successfully, but these errors were encountered: