update bot configuration for EESSI 2023.06

[boegel]

Updated bot configuration by @trz42 .

WIP because needs a change for aarch64/* targets, where we should switch to using aarch64/neoverse_n1 rather than aarch64/graviton2 and aarch64/neoverse_v1 instead of aarch64/graviton3, see archspec/archspec-json#41 + archspec/archspec-json#57 .

We should also get rid of 2023.04, since we won't be using that anymore (see #257 + #258)

[eessi-bot]

Instance eessi-bot-citc-aws is configured to build:

• arch x86_64/generic for repo eessi-2021.12
• arch x86_64/generic for repo eessi-2023.04
• arch x86_64/generic for repo eessi-2023.06-compat
• arch x86_64/generic for repo eessi-2023.06-software
• arch x86_64/intel/haswell for repo eessi-2021.12
• arch x86_64/intel/haswell for repo eessi-2023.04
• arch x86_64/intel/haswell for repo eessi-2023.06-compat
• arch x86_64/intel/haswell for repo eessi-2023.06-software
• arch x86_64/intel/skylake_avx512 for repo eessi-2021.12
• arch x86_64/intel/skylake_avx512 for repo eessi-2023.04
• arch x86_64/intel/skylake_avx512 for repo eessi-2023.06-compat
• arch x86_64/intel/skylake_avx512 for repo eessi-2023.06-software
• arch x86_64/amd/zen2 for repo eessi-2021.12
• arch x86_64/amd/zen2 for repo eessi-2023.04
• arch x86_64/amd/zen2 for repo eessi-2023.06-compat
• arch x86_64/amd/zen2 for repo eessi-2023.06-software
• arch x86_64/amd/zen3 for repo eessi-2021.12
• arch x86_64/amd/zen3 for repo eessi-2023.04
• arch x86_64/amd/zen3 for repo eessi-2023.06-compat
• arch x86_64/amd/zen3 for repo eessi-2023.06-software
• arch aarch64/generic for repo eessi-2021.12
• arch aarch64/generic for repo eessi-2023.04
• arch aarch64/generic for repo eessi-2023.06-compat
• arch aarch64/generic for repo eessi-2023.06-software
• arch aarch64/graviton2 for repo eessi-2021.12
• arch aarch64/graviton2 for repo eessi-2023.04
• arch aarch64/graviton2 for repo eessi-2023.06-compat
• arch aarch64/graviton2 for repo eessi-2023.06-software
• arch aarch64/graviton3 for repo eessi-2021.12
• arch aarch64/graviton3 for repo eessi-2023.04
• arch aarch64/graviton3 for repo eessi-2023.06-compat
• arch aarch64/graviton3 for repo eessi-2023.06-software

[trz42]

I think this should go into a different repository. Maybe one that captures information about the setup of our infrastructure.

[boegel]

I think this should go into a different repository. Maybe one that captures information about the setup of our infrastructure.

It used to be in a bot repo, but since the configuration is specific to the repo for which it's being used, we moved it here.

If we move it somewhere else, don't we re-introduce that problem, and create a disconnect between the config and the repo for which it is used?

That said, there's also stuff missing here (the repos.cfg)...

[trz42]

It used to be in a bot repo, but since the configuration is specific to the repo for which it's being used, we moved it here.

Partially true (if the bot would only build for a specific repository).

If we move it somewhere else, don't we re-introduce that problem, and create a disconnect between the config and the repo for which it is used?

Possibly. Eventually one might want to split the configuration into settings which a specific to a bot instance (and store that in some infrastructure repository) and settings which are specific to the target repository (and store that in the target repository).

That said, there's also stuff missing here (the repos.cfg)...

Those are probably target repo specific settings and could be moved there easily.

[trz42]

Instead of blocking this, we can leave it (bot-eessi-aws-citc.cfg) in the software-layer repository.

Possibly one could add the repos directory which includes CVMFS config files and settings for different target repositories. Could also be done in a follow up PR.