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

CDN public artifact locations needs to be managed #5

Closed
peternied opened this issue Sep 20, 2021 · 4 comments
Closed

CDN public artifact locations needs to be managed #5

peternied opened this issue Sep 20, 2021 · 4 comments

Comments

@peternied
Copy link
Member

For the existing instance we are hardcoding the path https://ci.opensearch.org/ci/dbc set as CDN_PUBLIC_ARTIFACT_PREFIX in the jenkins environment. Is this the correct way to set this and how can we make sure this is unique for all deployments?

@peternied peternied changed the title On a jenkins instance the public artifact locations needs to be managed CDN public artifact locations needs to be managed Sep 20, 2021
@gaiksaya
Copy link
Member

gaiksaya commented Apr 25, 2022

Hi @peternied, can you elaborate more on what is the problem statement here? Is this issue similar to #111 ?

Thanks!

@peternied
Copy link
Member Author

The non-public has a configured root path as https://ci.opensearch.org/ci/dbc, that dbc part of the path is an identifier to the jenkins cluster in operation via the CDN_PUBLIC_ARTIFACT_PREFIX variable.

This identifier is needed to redirect the ci.opensearch.org paths to the correct CDN bucket, see more details https://github.com/opensearch-project/opensearch-build/tree/main/deployment#overall-system

Ideally this value should be provided in the jenkins cluster setup since the account that controls ci.opensearch.org's cloudfront distribution needs to be updated to manage these resources.

@peternied
Copy link
Member Author

Please feel free to update the description if you'd like.

@rishabh6788
Copy link
Collaborator

Closing against #134

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

No branches or pull requests

3 participants