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

Move away from using jenkins as a CDN (dependency jobs) #3811

Open
Tracked by #3380
sxa opened this issue Nov 13, 2024 · 0 comments
Open
Tracked by #3380

Move away from using jenkins as a CDN (dependency jobs) #3811

sxa opened this issue Nov 13, 2024 · 0 comments
Labels

Comments

@sxa
Copy link
Member

sxa commented Nov 13, 2024

We have some jobs such as https://ci.adoptium.net/job/build.getDependency/ which are being used to store third party artifacts (for availability purposes). It is not ideal for us to be using jenkins as a software distribution mechanism for anyone using our scripts.

We have already started to take some actions to reduce this but we should catalogue where we are currently doing things like this in the main build and distribution process and look for ways to reduce it.

Ref: adoptium/temurin-build#3985 and the associated infrastructure PR to have CycloneDX installed on the build machines. Also see the associated slack discussion.

@sxa sxa added the Jenkins label Nov 13, 2024
@sxa sxa mentioned this issue Nov 13, 2024
21 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant