Skip to content

Investigate if embargo/lockdown can be better communicated #4203

@richardlau

Description

@richardlau

Currently, when we lock down the CI for security release preparation we add a "System message" explaining that access is restricted:

build/doc/jenkins-guide.md

Lines 101 to 106 in de38bc6

Add a Jenkins "system message" in https://ci.nodejs.org/configure. Something like:
```html
<h1 style="color:red">system is under embargo for a security release</h1>
<h2>For solidarity, even if you have access, please don't start unrelated jobs</h2>
<p>Refs: <a href="https://github.com/nodejs/build/issues/xxx">https://github.com/nodejs/build/issues/xxx</a></p>
```

Unfortunately:

I did come across https://plugins.jenkins.io/customizable-header/, which may be worth investigating to improve the user experience during a CI lockdown. If it would work, it would mean adding a new plugin to the public CI.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions