The CI will be locked down to start the generation of the security releases starting at 12 EST today and will be unlocked once the security releases go out (Ideally Tuesday Morning)
This will mean that only those working on the release and the jenkins admins will be able to access/use the CI for this period.
Sorry for any inconvenience.
mhdawson
All 9 comments
@nodejs/collaborators FYI.
mhdawson
on 10 Jul 2017
Jenkins is now locked down. Only releasers and Jenkins admins should have access.
joaocgreis
on 10 Jul 2017
Good morning (in EST) 馃寘
refack
on 11 Jul 2017
@refack all involved are working as fast as we can.
jbergstroem
on 11 Jul 2017
@refack all involved are working as fast as we can.
I did not assume otherwise 馃憤
refack
on 11 Jul 2017
Jenkins is now available again.
joaocgreis
on 11 Jul 2017
There are a lot of canceled and failed Jenkins jobs, is this related?
Here is a PR CI job I created and didn't cancel: https://ci.nodejs.org/job/node-test-pull-request/9082/
AndreasMadsen
on 12 Jul 2017
Was it the ppcbe linux subjobs that were cancelled? They've been hanging since yesterday: https://github.com/nodejs/build/issues/789
gibfahn
on 12 Jul 2017
@gibfahn Thanks, I think that is it.
AndreasMadsen
on 12 Jul 2017
Related issues
Brekmister
路
3Comments
ksushilmaurya
路
3Comments
srl295
路
3Comments
filipesilvaa
路
3Comments
danialkhansari
路
3Comments
Most helpful comment
Jenkins is now available again.