Skip to content

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

Merged
merged 4 commits into from
Aug 7, 2025

Conversation

donoghuc
Copy link
Member

@donoghuc donoghuc commented Aug 6, 2025

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/

Copy link

mergify bot commented Aug 6, 2025

This pull request does not have a backport label. Could you fix it @donoghuc? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit.
  • If no backport is necessary, please add the backport-skip label

@donoghuc donoghuc added the backport-active-all Automated backport with mergify to all the active branches label Aug 6, 2025
@donoghuc donoghuc force-pushed the logstash-releases-update branch 3 times, most recently from b3fc29d to 6355586 Compare August 6, 2025 23:35
@donoghuc
Copy link
Member Author

donoghuc commented Aug 6, 2025

Looks like there is no ruby interpreter on the path for this test runner. @mashhurs why do we use

"agents": {
"provider": "gcp",
"machineType": "n1-standard-4",
"image": "family/core-ubuntu-2204"
},
"steps": []}
a vanilla gcp image instead of the ones we build for logstash ci https://github.com/elastic/logstash/blob/3b13df1d6aa21f5d47828df4d93e61a1c07019e2/.buildkite/pull_request_pipeline.yml#L45

@mashhurs
Copy link
Collaborator

mashhurs commented Aug 7, 2025

Looks like there is no ruby interpreter on the path for this test runner. @mashhurs why do we use

"agents": {
"provider": "gcp",
"machineType": "n1-standard-4",
"image": "family/core-ubuntu-2204"
},
"steps": []}

a vanilla gcp image instead of the ones we build for logstash ci https://github.com/elastic/logstash/blob/3b13df1d6aa21f5d47828df4d93e61a1c07019e2/.buildkite/pull_request_pipeline.yml#L45

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.
I think now, we can change to platform-ingest-logstash-multi-jdk-ubuntu-2204 (as used in E2E tests)?!

@donoghuc
Copy link
Member Author

donoghuc commented Aug 7, 2025

@mashhurs I think i have this working (now its just failing due to #357

@donoghuc donoghuc requested a review from mashhurs August 7, 2025 18:57
@mashhurs
Copy link
Collaborator

mashhurs commented Aug 7, 2025

@mashhurs I think i have this working (now its just failing due to #357

Great! Thank you.
Let's also land #357 if you don't have any concern. I have added more context under the PR and more work will be covered with move-to-bridge (working with my branch)

"machineType": "n2-standard-4",
"imageProject": "elastic-images-prod",
"image": "family/platform-ingest-logstash-multi-jdk-ubuntu-2204",
"diskSizeGb": 120
Copy link
Collaborator

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.

Copy link
Member Author

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.

Copy link
Member Author

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

mashhurs
mashhurs previously approved these changes Aug 7, 2025
Copy link
Collaborator

@mashhurs mashhurs left a 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 -)"
Copy link
Collaborator

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!

Copy link
Member Author

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

Copy link
Collaborator

@mashhurs mashhurs left a 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.
@donoghuc donoghuc force-pushed the logstash-releases-update branch from b11baaf to 03643ad Compare August 7, 2025 20:05
@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

@donoghuc
Copy link
Member Author

donoghuc commented Aug 7, 2025

Green!

@donoghuc donoghuc merged commit febb207 into elastic:main Aug 7, 2025
4 checks passed
Copy link
Contributor

github-actions bot commented Aug 7, 2025

@Mergifyio backport 8.17 8.18 8.19 9.0 9.1

Copy link

mergify bot commented Aug 7, 2025

backport 8.17 8.18 8.19 9.0 9.1

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Aug 7, 2025
)

(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
mergify bot pushed a commit that referenced this pull request Aug 7, 2025
)

(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
mergify bot pushed a commit that referenced this pull request Aug 7, 2025
)

(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
mergify bot pushed a commit that referenced this pull request Aug 7, 2025
mergify bot pushed a commit that referenced this pull request Aug 7, 2025
donoghuc added a commit that referenced this pull request Aug 8, 2025
…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]>
donoghuc added a commit that referenced this pull request Aug 8, 2025
…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]>
donoghuc added a commit that referenced this pull request Aug 8, 2025
…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]>
donoghuc added a commit that referenced this pull request Aug 8, 2025
donoghuc added a commit that referenced this pull request Aug 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-active-all Automated backport with mergify to all the active branches
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants