-
Notifications
You must be signed in to change notification settings - Fork 272
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
Update lib tester for unit test in https://github.com/opensearch-project/opensearch-build/pull/1748 #1758
Labels
enhancement
New Enhancement
Comments
tianleh
added
enhancement
New Enhancement
untriaged
Issues that have not yet been triaged
labels
Mar 15, 2022
kavilla
added a commit
to kavilla/opensearch-build
that referenced
this issue
Mar 17, 2022
Issue Resolved: opensearch-project#1758 Signed-off-by: Kawika Avilla <[email protected]>
1 task
1 task
kavilla
added a commit
to kavilla/opensearch-build
that referenced
this issue
Mar 19, 2022
Issue Resolved: opensearch-project#1758 Signed-off-by: Kawika Avilla <[email protected]>
1 task
kavilla
added a commit
that referenced
this issue
Mar 21, 2022
) * [Build][Test] OS and OSD improvements plus support for Playground While using a child folder 'Playground' in Jenkins I had to do a number of changes to support a successful test run. I also included the ability to skip publishing the notification not to spam channels from builds from for example `Playground`. Also ability to skip building docker because from what I could tell it was publishing docker images from `Playground` pipelines as well. If the user attempts to pass an empty string it will skip the integ tests. Finally, some cleanup to integ tests to use the input manifest to container image. Also, make integ tests run in docker container for OpenSearch. Use libtester for detectTestDockerAgent Issues Resolved * #1688 * #1687 * #1686 * #1758 Signed-off-by: Kawika Avilla <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe
follow up of
#1748 (review)
Describe the solution you'd like
address the PR comment
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: