You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Performance-analyzer is commented out in the InputManifest for 1.0.
This component should be included with all the others but its build is currently failing if uncommented.
This component requires performance-analyzer-rca to also be assembled and included within performance-analyzer-rca.zip. Example of it being required during bundle assembly.
This component's snapshot build by passing -Dbuild.snapshot=true needs to work and output -SNAPSHOT artifacts.
The text was updated successfully, but these errors were encountered:
About this build fail, it is because spotless in RCA(when build PA, it will by default build RCA internal) required two branch to compare(for example main and 1.0).
* What went wrong:
A problem occurred configuring root project 'tmp3gn5llmf'.
> No such reference 'origin/main'
After fix RCA by skip the spotless step, it can build successful.
We can get by that when building RCA directly, but when we build the main plugin repo it is always cloning and building the main branch of RCA internally as part of its build scripts. opensearch-project/performance-analyzer#45
This means we cannot bypass this step and the build fails.
This means that any build of perf analyzer fails, even for 1.1, until the above PR is merged.
with the following snippet we can get by the spotless check in build.sh for each repo.
# remove this script when https://github.com/opensearch-project/performance-analyzer/issues/44 is fixed
git fetch origin main
git checkout main
# move back to initial ref
git checkout -
without the spotbugs fix we have no way of producing a successful build.
Currently Performance-analyzer is commented out in the InputManifest for 1.0.
This component should be included with all the others but its build is currently failing if uncommented.
The text was updated successfully, but these errors were encountered: