[Buildkite] Update condition to check whether or not a build is a PR

[mrodm]

Proposed commit message

Fix method to check if a build is part of a Pull Request or not.

Checked in this build from main: https://buildkite.com/elastic/integrations/builds/7057#018c3421-022d-4242-b582-fdaa028454df

In that build, Publish benchmarks step must not run since it is a build triggered from main branch.

Author's Checklist

• [ ]

Related issues

• Relates [buildkite] Add new Buildkite pipelines to test packages with Serverless #8072

[mrodm]

Merging since CI failures are unrelated to this change.

[elasticmachine]

💔 Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-12-04T12:59:02.601+0000

• Duration: 367 min 12 sec

Test stats 🧪

Test	Results
Failed	0
Passed	4873
Skipped	9
Total	4882

Steps errors

Expand to view the steps failures

Show only the first 10 steps failures

Shell Script

• Took 0 min 0 sec . View more details here
• Description: ../../build/elastic-package stack up -d -v --version 8.11.0

Shell Script

• Took 0 min 0 sec . View more details here
• Description: ../../build/elastic-package stack up -d -v --version 7.14.1

Shell Script

• Took 0 min 0 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package benchmark pipeline -v --report-format json --report-output file

Test integration: tanium

• Took 16 min 55 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

Shell Script

• Took 0 min 0 sec . View more details here
• Description: ../../build/elastic-package stack up -d -v --version 8.2.1

Shell Script

• Took 0 min 0 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

Shell Script

• Took 0 min 0 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

Shell Script

• Took 0 min 0 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

Test integration: websphere_application_server

• Took 21 min 23 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

elastic-package report benchmark

• Took 0 min 0 sec . View more details here
• Description: elastic-package report benchmark --fail-on-missing=false --new="build/benchmark-results" --old="build/main/benchmark-results" --threshold=15 --report-output-path="report.md" --full=false

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

💔 Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-12-04T13:49:48.260+0000

• Duration: 365 min 0 sec

Test stats 🧪

Test	Results
Failed	0
Passed	4860
Skipped	9
Total	4869

Steps errors

Expand to view the steps failures

Show only the first 10 steps failures

Print Message

• Took 0 min 0 sec . View more details here
• Description: �[39;49m[INFO] getVaultSecret: Getting secrets�[0m

Test integration: cisco_umbrella

• Took 24 min 9 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

Shell Script

• Took 0 min 0 sec . View more details here
• Description: go build -o build/elastic-package github.com/elastic/elastic-package

Checks if running on a Unix-like node

• Took 0 min 5 sec . View more details here

Verify if file exists in workspace

• Took 0 min 0 sec . View more details here
• Description: source.tgz

Google Storage Download

• Took 6 min 44 sec . View more details here
• Description: [2023-12-04T14:23:14.969Z] fleet-ci-immutable-ubuntu-2004-1701699529244428792 was marked offline: No

Shell Script

• Took 0 min 0 sec . View more details here
• Description: go build -o build/elastic-package github.com/elastic/elastic-package

elastic-package report benchmark

• Took 0 min 0 sec . View more details here
• Description: elastic-package report benchmark --fail-on-missing=false --new="build/benchmark-results" --old="build/main/benchmark-results" --threshold=15 --report-output-path="report.md" --full=false

Error signal

• Took 0 min 0 sec . View more details here
• Description: untar: step failed with error Required context class hudson.Launcher is missingPerhaps you forgot to surround the code with a step that provides this, such as: node

Recursively delete the current directory from the workspace

• Took 0 min 0 sec . View more details here
• Description: [2023-12-04T14:25:11.644Z] fleet-ci-immutable-ubuntu-2004-1701699598442702871 was marked offline: No

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.