Use a special node tag for processing nightlies

[j-rivero]

Part of #644 as suggested by @scpeters.

We have Bionic, Focal and Jammy, I've setup temporary the tags in docker (need permanent configuration) as follow:

• optimus: focal
• r2d2: bionic
• linux-ip-172-30-1-216: jammy (not large-memory but can probably handle the existing jammys)

[j-rivero]

linux-ip-172-30-1-216: jammy (not large-memory but can probably handle the existing jammys)

At some point the node got disconnected and the label was lost. It needs infra deployment, will do it today.

[j-rivero]

We have Bionic, Focal and Jammy, I've setup temporary the tags in docker (need permanent configuration) as follow:

* optimus: focal

* r2d2: bionic

* linux-ip-172-30-1-216: jammy (not large-memory but can probably handle the existing jammys)

Following this up, permanent documentation to be hosted here https://github.com/ignition-tooling/release-tools/pull/661/files#diff-69577e743717475e65611cd7bdd197f8a3fa038ec1e3dee2eae96c48c4593cfb

[azeey]

I ran into an issue today trying to test a nightly build using release.py for Ionic. The JENKINS_NODE_TAG was being set to linux-nightly-jammy, but we currently only have the label linux-nightly-focal on the node designated to run nightlies.

[j-rivero]

I ran into an issue today trying to test a nightly build using release.py for Ionic. The JENKINS_NODE_TAG was being set to linux-nightly-jammy, but we currently only have the label linux-nightly-focal on the node designated to run nightlies.

we do have the linux-nightly-jammy tag in the buildfarm: https://build.osrfoundation.org/label/linux-nightly-jammy/ . Could it be that at some point the node was destroyed by the AWS spot assignation. To regenerate it automatically, we have the nightly job labeler that should assign a new node to that tag, feel free to run it manually anytime you need a new node.