-
Notifications
You must be signed in to change notification settings - Fork 305
Added jenkins job for running release notes generation using LLM workflow. #5669
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
Conversation
Signed-off-by: Rishabh Singh <[email protected]>
Signed-off-by: Rishabh Singh <[email protected]>
Signed-off-by: Rishabh Singh <[email protected]>
Signed-off-by: Rishabh Singh <[email protected]>
Signed-off-by: Rishabh Singh <[email protected]>
Signed-off-by: Rishabh Singh <[email protected]>
Signed-off-by: Rishabh Singh <[email protected]>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5669 +/- ##
=======================================
Coverage 96.47% 96.47%
=======================================
Files 404 404
Lines 18372 18372
=======================================
Hits 17724 17724
Misses 648 648 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great to see this integrated. Can you also please create an issue to add this to release chore jenkinsFile?
Will see if I can add it for 3.2.
Thanks!
name: 'INPUT_MANIFEST', | ||
description: 'Release version number to fetch input manifest path', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Description and parameters seems to be mismatched. Let's just take version number from the user.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would keep it as manifest and fix description, as taking in version will mean I need to process OS and OSD in the same run, spawning ~50 agents in a single run. I want to be flexible to be able to process one product at a time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So we will be running this per manifest?
name: 'MODEL_ID', | ||
description: 'AWS Bedrock model id to use, defaults to Anthropic Claude 3.7v2', | ||
trim: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to add default value here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is already one in python code.
def currentIndex = component_index | ||
def currentWaitSeconds = wait_seconds | ||
|
||
if (!(currentComponent in ['notifications-core', 'functionalTestDashboards'])) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add dashboards core too? We can remove from python part and add here.
} | ||
println("Filename is ${filename}") | ||
println("Component object: ${componentObj.name}, ${componentObj.ref}, ${componentObj.repository}") | ||
echo "Current workspace is $WORKSPACE}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Debug statement or is it required?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will remove.
git remote set-url origin "https://opensearch-ci:${GITHUB_TOKEN}@github.com/opensearch-project/\$REPO_NAME" | ||
git config user.email "[email protected]" | ||
git config user.name "opensearch-ci" | ||
git checkout -b release/release-notes-${version} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I dont think its a good idea to create new branch for each version. They would be kept lingering. How about always push to releaseNotes
branch? Hard reset to base branch everytime and then proceed?
We do the same for update-manifest
and create-pull-request
which is for version increments. https://github.com/opensearch-project/opensearch-build/blob/main/.github/workflows/os-increment-plugin-versions.yml#L161
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Assuming this workflow has to be run once for every release, it makes sense.
throw new Exception("Error running workflow for component ${currentComponent}", e) | ||
} | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a postCleanUp within parallel stages as well? Example: https://github.com/opensearch-project/opensearch-build/blob/main/jenkins/opensearch/integ-test.jenkinsfile#L260
Co-authored-by: Sayali Gaikawad <[email protected]> Signed-off-by: Rishabh Singh <[email protected]>
Co-authored-by: Sayali Gaikawad <[email protected]> Signed-off-by: Rishabh Singh <[email protected]>
Co-authored-by: Sayali Gaikawad <[email protected]> Signed-off-by: Rishabh Singh <[email protected]>
binding.setVariable('INPUT_MANIFEST', 'tests/jenkins/data/opensearch-2.2.0.yml') | ||
binding.setVariable('GITHUB_USER', "GITHUB_USER") | ||
binding.setVariable('GITHUB_TOKEN', "GITHUB_TOKEN") | ||
//binding.setVariable('COMPONENTS', 'OpenSearch') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Required?
Signed-off-by: Rishabh Singh <[email protected]>
Description
Added jenkins job for running release notes generation using LLM workflow.
Issues Resolved
List any issues this PR will resolve, e.g. Closes [...].
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.