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

OMR: Add new zos 3.1 systems #434

Merged
merged 1 commit into from
Mar 21, 2025
Merged

Conversation

AdamBrousseau
Copy link
Contributor

Issue runtimes/infrastructure 9263

@AdamBrousseau
Copy link
Contributor Author

@jdekonin for review since he is setting up the new nodes.

Copy link

gitguardian bot commented Feb 11, 2025

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
7356849 Triggered Generic Password 2a72e90 instances/technology.omr/jenkins/configuration.yml View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@fredg02
Copy link
Contributor

fredg02 commented Mar 19, 2025

@AdamBrousseau any news here?

@AdamBrousseau
Copy link
Contributor Author

AdamBrousseau commented Mar 19, 2025

I think we were having issues setting up the new machines. I will let you know when this is ready. Thanks for the bump.

@AdamBrousseau AdamBrousseau marked this pull request as draft March 19, 2025 17:07
@fredg02
Copy link
Contributor

fredg02 commented Mar 19, 2025

Ok. No problem.

@jdekonin
Copy link
Contributor

jdekonin commented Mar 19, 2025

I have 1 of the 2 setup, the second one will be done later today or tomorrow. Unless there is issue with jenkins attempting to connect to a node until its 100% online, I'd say go ahead and merge.

Edit: well, maybe take out of draft and rebase first.

@fredg02
Copy link
Contributor

fredg02 commented Mar 20, 2025

There is no hurry (at least from my side 🙂 ). So I can wait until you're done with both machines.

@AdamBrousseau AdamBrousseau marked this pull request as ready for review March 21, 2025 15:04
value: 'txt'
- key: "_TAG_REDIR_OUT"
value: 'txt'
- key: "LIBPATH"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rocket references can be removed

- key: "PATH"
value: '/u/user1/jenkins-zos:$PATH'
- key: "PERL5LIB"
value: '/openzdk/rocket/lib/perl5'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure we use perl anymore but this isn't the correct location if it is. remove and we'll re-add if it is needed later

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The builds looks for perl so I'm guessing it is being used.

10:41:44  -- Found Perl: /usr/bin/perl (found version "5.30.0") 

What should it be updated to?

- toolLocation:
locations:
- home: '/u/user1/jenkins-zos/git'
key: "hudson.plugins.git.GitTool$DescriptorImpl@Default"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using zopen version of git now which is found on the PATH. I believe this can just be removed.

Copy from existing zos machines.
Remove unneeded java8 tool.
Remove rocket tools and old cmake version from PATH.
Remove rocker from LIBPATH.
Update Perl lib path.
Remove git tool as it is now default on PATH.

Issue runtimes/infrastructure 9263

Signed-off-by: Adam Brousseau <[email protected]>
Copy link
Contributor

@jdekonin jdekonin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@AdamBrousseau
Copy link
Contributor Author

@fredg02 for merge please

@fredg02 fredg02 merged commit 4d71a8e into eclipse-cbi:master Mar 21, 2025
2 checks passed
@fredg02
Copy link
Contributor

fredg02 commented Mar 21, 2025

Change has been merged and deployed.

fredg02 added a commit that referenced this pull request Mar 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants