1342965 - signingworker docs incomplete & out-of-date

Status: RESOLVED WONTFIX

(Release Engineering :: General, defect)

Description

[Hal Wine [:hwine] use NI!]

An AWS retirement message showed that most of us don't know:
 - how to restart a signingworker (all automatic, or manual needed?)
 - will it self recover from an AWS retirement?

Also, the repo was moved from mozilla to mozilla-releng, and both the travis & coverage badges in the README.rst file need updating.

Comment 1

[Jordan Lund (:jlund)]

I wish we had workers that sang about our releases

Comment 2

[Nick Thomas [:nthomas] (UTC+12)]

(In reply to Hal Wine [:hwine] (use NI) from comment #0)
> An AWS retirement message showed that most of us don't know:
>  - how to restart a signingworker (all automatic, or manual needed?)
>  - will it self recover from an AWS retirement?

I asked again on IRC, and got a 'it should come back up by itself' from jlund, which turned out to be true.

Comment 3

[Hal Wine [:hwine] use NI!]

Great! We have an answer! Now where do we put it?

:rail - you did most of the commits -- where should the ops docs be?

Comment 4

[Rail Aliiev [:rail]]

Sorry for the tardy reply.

Do we still use mana as the source of truth? We can probably use mana in any case.

FTR, these workers will be obsoleted by the scriptworker based signing workers, when we completely switch to TC and CoT.