+
+The maintainers of the OpenSearch-build Repo seek to promote an inclusive and engaged community of contributors. In order to facilitate this, bi-weekly triage meetings are open-to-all and attendance is encouraged for anyone who hopes to contribute, discuss an issue, or learn more about the project. To learn more about contributing to the OpenSearch-build Repo visit the [Contributing](./CONTRIBUTING.md) documentation.
+
+### Do I need to attend the meeting for my issue to be addressed/triaged?
+
+Attendance is not required for your issue to be triaged or addressed. All new issues are triaged bi-weekly.
+
+### What happens if my issue does not get covered this time?
+
+Each meeting we seek to address all new issues. However, should we run out of time before your issue is discussed, you are always welcome to attend the next meeting or to follow up on the issue post itself.
+
+### How do I join the Backlog & Triage meeting?
+
+Meetings are hosted regularly at 9 AM Pacific Time and can be joined via the links posted on the [OpenSearch Meetup Group](https://www.meetup.com/opensearch/events/) list of events. The event will be titled `Engineering Effectiveness Triage Meeting`.
+
+After joining the Zoom meeting, you can enable your video / voice to join the discussion. If you do not have a webcam or microphone available, you can still join in via the text chat.
+
+If you have an issue you'd like to bring forth please consider getting a link to the issue so it can be presented to everyone in the meeting.
+
+### Is there an agenda for each week?
+
+Meetings are 45 minutes and structured as follows:
+
+1. Initial Gathering: As we gather, feel free to turn on video and engage in informal and open-to-all conversation. After a bit a volunteer will share their screen and proceed with the agenda.
+2. Announcements: If there are any announcements to be made they will happen at the start of the meeting.
+3. Review of New Issues: The meetings always start with reviewing all untriaged [issues](https://github.com/orgs/opensearch-project/projects/208/views/2) for below repositories:
+ 1. [opensearch-build](https://github.com/opensearch-project/opensearch-build)
+ 1. [opensearch-ci](https://github.com/opensearch-project/opensearch-ci)
+ 1. [opensearch-build-libraries](https://github.com/opensearch-project/opensearch-build-libraries)
+ 1. [helm-charts](https://github.com/opensearch-project/helm-charts)
+ 1. [terraform-provider-opensearch](https://github.com/opensearch-project/terraform-provider-opensearch)
+ 1. [ansible-playbook](https://github.com/opensearch-project/ansible-playbook)
+ 1. [opensearch-cluster-cdk](https://github.com/opensearch-project/opensearch-cluster-cdk)
+ 1. [opensearch-devops](https://github.com/opensearch-project/opensearch-devops)
+4. Member Requests: Opportunity for any meeting member to ask for consideration of an issue or pull request.
+5. Untriaged Items: Review any [issues](https://github.com/orgs/opensearch-project/projects/208/views/2) that might have had the 'untriaged' label removed but require additional triage discussion.
+6. Open Discussion: Allow for members of the meeting to surface any topics without issues filed or pull request created.
+
+
+There is no specific ordering within each category.
+
+If you have an issue you would like to discuss but do not have the ability to attend the entire meeting, please attend when is best for you and signal that you have an issue to discuss when you arrive.
+
+### Is prior contribution to the project required to attend a triage meeting?
+
+No, all are welcome and encouraged to attend. Attending the Backlog & Triage meetings is a great way for a new contributor to learn about the project as well as explore different avenues of contribution.
+
+### What if I have an issue that is almost a duplicate, should I open a new one to be triaged?
+
+You can always open an [issue](https://github.com/opensearch-project/opensearch-build/issues/new/choose) including one that you think may be a duplicate. However, in cases where you believe there is an important distinction to be made between an existing issue and your newly created one, you are encouraged to attend the triaging meeting to explain.
+
+### What if I have follow-up questions on an issue?
+
+If you have an existing issue you would like to discuss, you can always comment on the issue itself. Alternatively, you are welcome to come to the triage meeting to discuss.
+
+### What are the issue labels associated with triaging?
+
+Yes, there are several labels that are used to identify the 'state' of issues filed.
+
+| Label | When applied | Meaning |
+| ----- | ------------ | ------- |
+| Untriaged | When issues are created or re-opened. | Issues labeled as 'Untriaged' require the attention of the repository maintainers and may need to be prioritized for quicker resolution. |
+| Help Wanted | Anytime. | Issues marked as 'Help Wanted' signal that they are actionable and not the current focus of the project maintainers. Community contributions are especially encouraged for these issues. |
+| Good First Issue | Anytime. | Issues labeled as 'Good First Issue' are small in scope and can be resolved with a single pull request. These are recommended starting points for newcomers looking to make their first contributions. |
+
+### Who should I contact if I have further questions?
+
+You can always file an [issue](https://github.com/opensearch-project/opensearch-build/issues/new/choose) for any question you have about the project. Alternatively, you can use [opensearch slack](https://opensearch.org/slack.html) channels such as #infra #devops for any related queries.
diff --git a/build.gradle b/build.gradle
index f6146b45a9..f51deaa84e 100644
--- a/build.gradle
+++ b/build.gradle
@@ -41,6 +41,10 @@ configurations.all {
force group: 'com.google.code.gson', name: 'gson', version: '2.8.9'
force group: 'commons-codec', name: 'commons-codec', version: '1.15'
force group: 'com.google.protobuf', name: 'protobuf-java', version: '3.21.7'
+ force group: 'com.google.errorprone', name: 'error_prone_annotations', version: '2.18.0'
+ force group: 'org.checkerframework', name: 'checker-qual', version: '3.33.0'
+ force group: 'com.google.j2objc', name: 'j2objc-annotations', version: '2.8'
+ force group: 'org.jenkins-ci.plugins', name: 'durable-task', version: '547.vd1ea_007d100c'
}
}
@@ -60,19 +64,18 @@ sourceSets {
}
sharedLibrary {
- coreVersion = '2.387.1' // https://repo.jenkins-ci.org/public/org/jenkins-ci/main/jenkins-core/
+ coreVersion = '2.426.3' // https://repo.jenkins-ci.org/public/org/jenkins-ci/main/jenkins-core/
testHarnessVersion = '2085.va_c531db_287b_d' // https://mvnrepository.com/artifact/org.jenkins-ci.main/jenkins-test-harness?repo=jenkins-releases
pluginDependencies {
// see https://mvnrepository.com/artifact/org.jenkins-ci.plugins/Test Summary
+
+
+
+
+|
+
+
+
|
+
+
+
+100%
+successful + |
+
+
+
+
+
+
+
+
+
+Packages
+| Package | +Tests | +Failures | +Ignored | +Duration | +Success rate | +
|---|---|---|---|---|---|
| +org.opensearch.geospatial.index.mapper.xypoint + | +6 | +0 | +0 | +2.874s | +100% | +
| +org.opensearch.geospatial.index.mapper.xyshape + | +3 | +0 | +0 | +0.858s | +100% | +
| +org.opensearch.geospatial.index.query.xypoint + | +8 | +0 | +0 | +3.058s | +100% | +
| +org.opensearch.geospatial.index.query.xyshape + | +8 | +0 | +0 | +2.764s | +100% | +
| +org.opensearch.geospatial.ip2geo.action + | +3 | +0 | +0 | +5.068s | +100% | +
| +org.opensearch.geospatial.ip2geo.processor + | +2 | +0 | +0 | +1.448s | +100% | +
| +org.opensearch.geospatial.plugin + | +1 | +0 | +0 | +0.092s | +100% | +
| +org.opensearch.geospatial.processor + | +2 | +0 | +0 | +0.493s | +100% | +
| +org.opensearch.geospatial.rest.action.upload.geojson + | +4 | +0 | +0 | +4.717s | +100% | +
| +org.opensearch.geospatial.search.aggregations.bucket.geogrid + | +3 | +0 | +0 | +0.645s | +100% | +
| +org.opensearch.geospatial.stats.upload + | +2 | +0 | +0 | +1.238s | +100% | +
+
+