Alkane will now PULL files from Jenkins, instead of Jenkins pushing to the relevant server.

The issue with this idea is we've to load balance more than HTTP:

Resolved by db-B-001 deployment: MySQL server doesn't have a public IP anymore

DRP merged, so we're good :)

Rebased. This is stable enough now to be merged.

Update during test deployment

We've a correct no-op change deployed, but perhaps should we consider to modernize it a little bit:

It has been done manually some years ago, but it seems we don't provision the configuration file settings.json automatically.

In T1627#23666, @dereckson wrote:

Perhaps replace references here too: https://code.nasqueron.org/?q=equatower&i=nope&literal=nope&files=&excludeFiles=&repos=

ChatGPT haiku of the day:

As all tasks are done, excepted the portsearch -u issue, which is not a blocker (it correctly indexes the ports), we're done here.

We've a Salt approach in two phases:

• deploy with deploy user and a specific deployment key (GitHub / it could be a read-only one) or access key (BitBucket), or bot user key (DevCentral)
• fix user/group to the required one (like the chown)