Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Machine requirement: Replacement for C3jenkins #3340

Closed
Tracked by #3292
sxa opened this issue Jan 10, 2024 · 11 comments
Closed
Tracked by #3292

New Machine requirement: Replacement for C3jenkins #3340

sxa opened this issue Jan 10, 2024 · 11 comments

Comments

@sxa
Copy link
Member

sxa commented Jan 10, 2024

I need to request a new machine:

  • New machine operating system (e.g. linux/windows/macos/solaris/aix): Potentially any, but linux preferred
  • New machine architecture (e.g. x64/aarch32/arm32/ppc64/ppc64le/sparc): n/a
  • Provider (leave blank if it does not matter):
  • Desired usage: Replacement for C3jenkins node which is currently hosted on an Equinix x86 server
  • Any unusual specification/setup required:
  • How many of them are required: 1

Please explain what this machine is needed for:

@sxa
Copy link
Member Author

sxa commented Jan 15, 2024

Testing on an OSUOSL aarch64 machine - 2 core, 4GB, 30Gb with a 250GB volume attached for the jenkins workspace - 140.211.169.21

@sxa
Copy link
Member Author

sxa commented Jan 15, 2024

Steps taken:

  1. apt-get update && apt-get upgrade plus apt install joe because I use it a lot, but that's not strictly required
  2. Edit /etc/motd to add a file indicating what the machine is used for that will be displayed on login
  3. Create jenkins user and add it's public key to ~jenkins/.ssh/authorized_keys
  4. Use 250GB disk to create a 4GB swap partition (/dev/sdb1) and the remainer as an ext4 file system mounted on /home/jenkins/workspace. Prior to mounting I created a file /home/jenkins/workspace/ - add both to /etc/fstab
  5. Install temurin-21-jdk using the instructions in https://adoptium.net/installation/linux#_deb_installation_on_debian_or_ubuntu
  6. Attach to jenkins as jenkins-worker with git-hg gpgsignworker master labels (Not added yet as we're entering a release cycle.

@sxa sxa self-assigned this Jan 19, 2024
@sxa
Copy link
Member Author

sxa commented Jan 29, 2024

@sxa
Copy link
Member Author

sxa commented Jan 31, 2024

Ref the issue linked above I've got the key accepted now but there is a potential security concern as discussed in my DM with @andrew-m-leonard that I'd like to get clarity on first.

@sxa
Copy link
Member Author

sxa commented Feb 1, 2024

Inventory PR for this system: #3367
I've added it to Bastillion, @steelhead31 is managing Nagios installation prior to merging that PR

@steelhead31
Copy link
Contributor

Nagios & Wazuh now installed and working correctly on this host.

@andrew-m-leonard
Copy link
Contributor

The Adoptium mirror needs the local git config user/email set so it can push the merge commits, so i’ve set them on jenkins-worker as per the old node:
println "git config --global user.email [email protected]".execute().text
println "git config --global user.name eclipse-temurin-bot".execute().text

@sxa
Copy link
Member Author

sxa commented Feb 9, 2024

Increased executors from 10 to 12 as we were experiencing a deadlock with about six regenerators for each release, plus a betaTrigger job for several releases which was in total locking out all ten. The extra two has freed up enough to allow the pipelines to progress Slack thread link

@sxa
Copy link
Member Author

sxa commented Feb 12, 2024

Increased executors from 10 to 12

Noting that adoptium/ci-jenkins-pipelines#920 should have partially resolved this and significantly reduced the executor requirement now.

@sxa
Copy link
Member Author

sxa commented Feb 21, 2024

I'm going to close this as I don't believe we have had any problems with this so far.

@sxa
Copy link
Member Author

sxa commented Apr 30, 2024

Added jq and unzip from apt (which installed jq libjq1 libonig5 to order to support the download_and_sbom_validation job which is best tied to that node (was previously tied to aarch64&&dockerhost which didn't work on the OSUOSL machine which didn't have jq

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

3 participants