-
Notifications
You must be signed in to change notification settings - Fork 12
Update buildkite script to look for new logstash releases location #358
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
Conversation
This pull request does not have a backport label. Could you fix it @donoghuc? 🙏
|
b3fc29d
to
6355586
Compare
Looks like there is no ruby interpreter on the path for this test runner. @mashhurs why do we use logstash-filter-elastic_integration/.buildkite/scripts/pull-request-pipeline/generate-steps.py Lines 62 to 67 in 6a03524
|
We didn't have range of our custom VMs when we setup these pipelines :) The only reason (as I remember) was docker compose was available in this VM type. |
Great! Thank you. |
"machineType": "n2-standard-4", | ||
"imageProject": "elastic-images-prod", | ||
"image": "family/platform-ingest-logstash-multi-jdk-ubuntu-2204", | ||
"diskSizeGb": 120 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you what is the default disk size?
I did increase in the E2E since we need to spin up elastic-package but I am thinking here the default (32 or 64) should be sufficient.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just copy pasted from the other. I'll remove it and see if default works (which i suspect it will). Good catch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pushed a commit to check if default is sufficient. Thanks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM if you please clarify disk size and make sure we are not allocating over resource.
|
||
export JAVA_HOME="/opt/buildkite-agent/.java/adoptiumjdk_21" | ||
export PATH="/opt/buildkite-agent/.rbenv/bin:/opt/buildkite-agent/.pyenv/bin:/opt/buildkite-agent/.java/bin:$JAVA_HOME:$PATH" | ||
eval "$(rbenv init -)" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah right, this was a requirement!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, i will be re-visiting this as part of https://github.com/elastic/ingest-dev/issues/5827
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
This commit updates the buildkite scripts to look in the `.ci` repo in the logstash-plugins org for the new location of logstash releases.
Use images we are building for LS testing for all BK pipelines.
b11baaf
to
03643ad
Compare
💚 Build Succeeded
History
|
Green! |
@Mergifyio backport 8.17 8.18 8.19 9.0 9.1 |
✅ Backports have been created
|
) (cherry picked from commit febb207) # Conflicts: # .buildkite/scripts/build-pipeline/generate-steps.py # .buildkite/scripts/e2e-pipeline/generate-steps.py # .buildkite/scripts/pull-request-pipeline/generate-steps.py # .buildkite/scripts/run_tests.sh
) (cherry picked from commit febb207) # Conflicts: # .buildkite/scripts/build-pipeline/generate-steps.py # .buildkite/scripts/e2e-pipeline/generate-steps.py # .buildkite/scripts/pull-request-pipeline/generate-steps.py # .buildkite/scripts/run_tests.sh
) (cherry picked from commit febb207) # Conflicts: # .buildkite/scripts/build-pipeline/generate-steps.py # .buildkite/scripts/e2e-pipeline/generate-steps.py # .buildkite/scripts/pull-request-pipeline/generate-steps.py # .buildkite/scripts/run_tests.sh
) (cherry picked from commit febb207)
) (cherry picked from commit febb207)
…sh releases location (#359) * Update buildkite script to look for new logstash releases location (#358) (cherry picked from commit febb207) # Conflicts: # .buildkite/scripts/build-pipeline/generate-steps.py # .buildkite/scripts/e2e-pipeline/generate-steps.py # .buildkite/scripts/pull-request-pipeline/generate-steps.py # .buildkite/scripts/run_tests.sh * fix merge conflict --------- Co-authored-by: Cas Donoghue <[email protected]>
…sh releases location (#360) * Update buildkite script to look for new logstash releases location (#358) (cherry picked from commit febb207) # Conflicts: # .buildkite/scripts/build-pipeline/generate-steps.py # .buildkite/scripts/e2e-pipeline/generate-steps.py # .buildkite/scripts/pull-request-pipeline/generate-steps.py # .buildkite/scripts/run_tests.sh * fix merge conflicts --------- Co-authored-by: Cas Donoghue <[email protected]>
…sh releases location (#361) * Update buildkite script to look for new logstash releases location (#358) (cherry picked from commit febb207) # Conflicts: # .buildkite/scripts/build-pipeline/generate-steps.py # .buildkite/scripts/e2e-pipeline/generate-steps.py # .buildkite/scripts/pull-request-pipeline/generate-steps.py # .buildkite/scripts/run_tests.sh * fix merge conflicts --------- Co-authored-by: Cas Donoghue <[email protected]>
) (#362) (cherry picked from commit febb207) Co-authored-by: Cas Donoghue <[email protected]>
) (#363) (cherry picked from commit febb207) Co-authored-by: Cas Donoghue <[email protected]>
This commit updates the buildkite scripts to look in the
.ci
repo in the logstash-plugins org for the new location of logstash releases.Thanks for contributing to Logstash! If you haven't already signed our CLA, here's a handy link: https://www.elastic.co/contributor-agreement/