-
Notifications
You must be signed in to change notification settings - Fork 288
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]: 2.12.0 build.sh missing #4350
Comments
Similar issue for main/3.0.0: 2024-01-17 12:39:19 INFO Executing "bash /var/jenkins/workspace/distribution-build-opensearch-dashboards@2/scripts/default/opensearch-dashboards/build.sh -v 3.0.0 -p linux -a x64 -s false -o builds" in /tmp/tmpqpkioqxq/securityDashboards
|
Thanks @derek-ho, this is coming from the PR #4343. @peterzhuamazon can you please take a look. |
Seems like the cleanup is still not fully in effect: https://build.ci.opensearch.org/blue/rest/organizations/jenkins/pipelines/distribution-build-opensearch-dashboards/runs/7117/nodes/70/steps/297/log/?start=0
But obs already get removed and gantt still having issues:
Will need to take a deeper look on this. |
Then right after gantt, dashboards-assistant also shows issues related to gantt and obs:
|
Think I find the issue now:
|
Describe the bug
I am seeing the following error log from the autocut:
C:\Users\Administrator\jenkins\workspace\distribution-build-opensearch-dashboards\scripts\default\opensearch-dashboards\build.sh: line 13: ../../../lib/shell/file_management.sh: No such file or directory
Found a similar line for tar builds as well. I am suspecting something went wrong with the build process and the default script build.sh is not present
To reproduce
Logs: https://build.ci.opensearch.org/blue/rest/organizations/jenkins/pipelines/distribution-build-opensearch-dashboards/runs/7113/nodes/76/log/?start=0
Expected behavior
No response
Screenshots
If applicable, add screenshots to help explain your problem.
Host / Environment
No response
Additional context
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: