Skip to content
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

Incident: Jenkins misconfiguration for arm-fanned #1432

Closed
rvagg opened this issue Aug 8, 2018 · 1 comment
Closed

Incident: Jenkins misconfiguration for arm-fanned #1432

rvagg opened this issue Aug 8, 2018 · 1 comment

Comments

@rvagg
Copy link
Member

rvagg commented Aug 8, 2018

Tracked the build failures @MylesBorins was experiencing @ nodejs/node#22184 to a misconfiguration in Jenkins:

tmp_jenkins_env_inherit

There's too much activity in the config history to figure out who is responsible for this. It could be me from the last time I removed arm-fanned from CI due to an extended outage and then perhaps I put it back in again wrong but I think the last time I had to do that was in May? But regardless of who, here's the problem: "Parameters from properties file" is essential because it's the mechanism that's used to make parameters flow all the way down to these sub-jobs. Without these parameters we get the default. So from whenever this was enacted, arm-fanned has been testing master for every job submitted to it. Great for ccache, not so great for getting confidence around our tests on ARM!

Fixed now, this is just FYI and FTR.

@refack
Copy link
Contributor

refack commented Aug 8, 2018

  1. FYI & FTR, it should be "safer" to use the Disabled checkbox to disable a job during an outage. Alternativly, if possible try using the Restore old config image button.
  2. Seems like node-test-commit-arm was still disabled (after I disabled it on 2018-07-25 due to a packetnet outage 🤦‍♂️). I just now enabled it and testing that it hasn't rotted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants