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

Jenkinsfiles to have an input BUILD_BRANCH. #2558

Closed
prudhvigodithi opened this issue Sep 6, 2022 · 3 comments
Closed

Jenkinsfiles to have an input BUILD_BRANCH. #2558

prudhvigodithi opened this issue Sep 6, 2022 · 3 comments
Assignees
Labels
enhancement New Enhancement

Comments

@prudhvigodithi
Copy link
Member

prudhvigodithi commented Sep 6, 2022

Is your feature request related to a problem? Please describe

Part of #2549

Jenkinsfiles to have an input BUILD_BRANCH. Once the branching strategy in place, Jenkinsfiles should be able to checkout the right branch as per release to make sure release specific code is executed.

Describe the solution you'd like

  • Add a new input BUILD_BRANCH.
  • Add a new stage that checks out the build repo with specific BUILD_BRANCH.
  • Stash the repo files.
  • Unstash in every required stage to make sure the stage uses the right code specific to BUILD_BRANCH

Describe alternatives you've considered

No response

Additional context

More useful info on stash and unstash https://www.youtube.com/watch?v=0GQZzLlnUws

@prudhvigodithi prudhvigodithi added enhancement New Enhancement untriaged Issues that have not yet been triaged and removed untriaged Issues that have not yet been triaged labels Sep 6, 2022
@prudhvigodithi prudhvigodithi self-assigned this Sep 6, 2022
@prudhvigodithi
Copy link
Member Author

prudhvigodithi commented Sep 9, 2022

PR converted to draft #2559, until a solution is finalized that satisfies the version/branching requirement with OpenSearch and OpenSearch Dashboards version being offset
More details on comments: #2549

@bbarani
Copy link
Member

bbarani commented Oct 3, 2022

Can we also close this issue until we finalize a solution @prudhvigodithi

@prudhvigodithi
Copy link
Member Author

Hey @bbarani yes we can close this. I'm going to close this as not planned, related META issue #2549, which also needs to be updated with new acceptance criteria.

@prudhvigodithi prudhvigodithi closed this as not planned Won't fix, can't repro, duplicate, stale Oct 3, 2022
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