[Enhancement] Branch Cut workflow to have the intelligence to detect version bump before cutting branch. about opensearch-build HOT 3 OPEN

Hi Sushma,

Based on the original code of branch cut.
It does not use any jenkins lib nor does it engage build python code.
It is simply a couple of git commands doing the checkout and push again with new branch name:
https://github.com/opensearch-project/opensearch-build/blob/opensearch-2.14.0/jenkins/release-branch/release-branch.jenkinsfile

Probably a few tweaks to branch cut workflow to help improve the version enforcing:

1. Add a param / option to enforce the version check: VERSION_CHECK: <VERSION>.
2. Use either gradle or yarn based on the input manifest provided to do a simple version check.
3. If version mismatch, do not fail the entire run but rather save the component in a list and report later without cutting that specific branch.

We can also add a version check standalone workflow if needed and use it as a pre-requisite of branch cut, tho that might be an overkill at the moment.

Thanks.

from opensearch-build.

Trying to monitor the version bump in potential central release dashboards improvements:

• opensearch-project/opensearch-metrics#51

from opensearch-build.

Hi @5u5hma,

Creating a release branch via automation is something that we added recently. Please note that we take this action only on the day of first release candidate creation. This is more of a proactive measure instead to avoid build failures. As @peterzhuamazon mentioned, we can add a check to make sure versions are bumped before a branch is cut via automation workflow. However, each repo has its own maintainers and codeowners that might decide to cut branch when they want which includes before the version bump, etc which we or the automation workflow has no control over whatsoever. I believe this will be still be an edge case for automation mentioned in issue description.

@dblock @prudhvigodithi Please add your thoughts if any.

from opensearch-build.