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

Refactor the usage of index.json file for both OS and OSD. #4151

Closed
3 tasks done
Divyaasm opened this issue Oct 19, 2023 · 0 comments
Closed
3 tasks done

Refactor the usage of index.json file for both OS and OSD. #4151

Divyaasm opened this issue Oct 19, 2023 · 0 comments
Assignees
Labels
enhancement New Enhancement

Comments

@Divyaasm
Copy link
Collaborator

Divyaasm commented Oct 19, 2023

Is your feature request related to a problem? Please describe

Currently we are updating the index.json file at the end of the distribution-build job. In this case latest is updated at a time for all the distributions. Instead we want to maintain a separate latest for each distribution in individual index.json files. These files are responsible to maintain the latest build number for each distribution type individually for both x64 and arm64 architecture types.

Describe the solution you'd like

Make code enhancements to call the updateIndexFile Groovy library at distribution stage level after building and assembling the artifacts to update the latest with build number each time the distribution stage succeeds. This way we can maintain distribution-level-latest build numbers along unlike the the overall latest which we are currently supporting.

Sub Issues:

Acceptance Criteria:

  • Create and maintain individual index.json files for each distribution (Example: tar, rpm, deb, windows)
  • Update the latest of each distribution at stage level if the build and assemble steps are successful by calling the updateIndexFile Groovy library at each distribution stage to update corresponding distribution latest w.r.t. architecture.
  • Change the cf-url-rewriter logic to retrieve the latest successful distribution build which we are individually maintaining.

Describe alternatives you've considered

No response

Additional context

No response

@Divyaasm Divyaasm added enhancement New Enhancement untriaged Issues that have not yet been triaged labels Oct 19, 2023
@bbarani bbarani moved this from Backlog to In Progress in OpenSearch Engineering Effectiveness Oct 24, 2023
@bbarani bbarani removed the untriaged Issues that have not yet been triaged label Oct 24, 2023
@Divyaasm Divyaasm moved this from In Progress to In review in OpenSearch Engineering Effectiveness Feb 7, 2024
@Divyaasm Divyaasm closed this as completed Mar 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New Enhancement
Projects
None yet
Development

No branches or pull requests

2 participants