-
Notifications
You must be signed in to change notification settings - Fork 282
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
[BUG] Migrate modern build.gradle into 1.x branches #2535
Comments
@opensearch-project/security Our list of blocked features is only getting longer and its preventing us from following best practices in one of our primarily maintained branches 1.3. According to the release schedule we will at least maintain 1.3 until December 31, 2023. But that window could be extended. On the difficulty of this work, working on gradle is not often a task we perform, but its relatively simple once in the space with structured example of how the 2.1 migration occurred. It would require gumption, but I think even first time contributors could take this on. |
Agreed and agreed. Should we take this as a high priority task and update the gradle to second iteration on 1.3 to unblock feature backporting? |
Opened this issue in the wrong repo - but it impacts security dashboard plugin too |
Closing this issue. The changes to |
Background
There are many features of OpenSearch and its related ecosystem of tools that are java code as well as gradle plugins. When security was initially [migrated to gradle] the connection to gradle plugins provided by OpenSearch were not included.
After mounting issues such as aligning transitive dependency versions [1], publishing plugin zip files [2], and running OpenSearch's integration tests[3], a [second gradle migration] was performed. This build change was involved.
The security plugin codebase is running this second iteration on its
main
branches, in addition to the2.X
, and2.1+
branches.Problem
1.x and 1.3 branches are using the first iteration of the gradle build, leaving many features are locked away from being backported.
Blocked features backports
Related Issues
The text was updated successfully, but these errors were encountered: