Skip to content
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

[7.17](backport #38814) Dedicated script for detecting changesets on Buildkite #38821

Merged
merged 2 commits into from
Apr 10, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Apr 10, 2024

Proposed commit message

After the introduction of a centralized beats pipeline and statically
defined changeset rules in #38783, we still need a way to grab
changes for modules for IT tests.

Currently this is done in common.sh#defineModuleFromTheChangeSet().
This commit adds a new script that has only the changeset related
functionality, required to build the MODULE env var.

The functions themselves, are copied from common.sh (with minor
enhancements in documentation), paving the way to sunset common.sh
in the future.

Related issues

Logs

When changing e.g. metricbeat/modules/windows/module.yml (see 4165994), invoking the script returns:

$ pwd
beats/metricbeat
$ source .buildkite/scripts/changesets.sh
$ defineModuleFromTheChangeSet metricbeat
$ echo $MODULE 
windows

otherwise, with no changes, returns:

$ defineModuleFromTheChangeSet metricbeat
$ echo $MODULE 

This is an automatic backport of pull request #38814 done by [Mergify](https://mergify.com).

After the introduction of a centralized beats pipeline and statically
defined changeset rules in #38783, we still need a way to grab
changes for modules for IT tests.

Currently this is done in common.sh#defineModuleFromTheChangeSet().
This commit adds a new script that has only the changeset related
functionality, required to build the `MODULE` env var.

The functions themselves, are copied from common.sh (with minor
enhancements in documentation), paving the way to sunset common.sh
in the future.

Relates: https://github.com/elastic/ingest-dev/issues/3072
(cherry picked from commit d0dda41)
@mergify mergify bot requested a review from a team as a code owner April 10, 2024 11:34
@mergify mergify bot added the backport label Apr 10, 2024
@mergify mergify bot requested review from faec and leehinman and removed request for a team April 10, 2024 11:34
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Apr 10, 2024
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Apr 10, 2024
@dliappis dliappis requested review from alexsapran and removed request for faec and leehinman April 10, 2024 11:34
@dliappis dliappis added the needs_team Indicates that the issue/PR needs a Team:* label label Apr 10, 2024
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Apr 10, 2024
@elasticmachine
Copy link
Collaborator

elasticmachine commented Apr 10, 2024

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2024-04-10T12:32:21.390+0000

  • Duration: 12 min 14 sec

Test stats 🧪

Test Results
Failed 0
Passed 3
Skipped 0
Total 3

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

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

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@dliappis dliappis enabled auto-merge (squash) April 10, 2024 12:32
@dliappis dliappis merged commit 9204578 into 7.17 Apr 10, 2024
11 of 12 checks passed
@dliappis dliappis deleted the mergify/bp/7.17/pr-38814 branch April 10, 2024 12:44
michel-laterman pushed a commit to michel-laterman/beats that referenced this pull request Apr 17, 2024
elastic#38821)

After the introduction of a centralized beats pipeline and statically
defined changeset rules in elastic#38783, we still need a way to grab
changes for modules for IT tests.

Currently this is done in common.sh#defineModuleFromTheChangeSet().
This commit adds a new script that has only the changeset related
functionality, required to build the `MODULE` env var.

The functions themselves, are copied from common.sh (with minor
enhancements in documentation), paving the way to sunset common.sh
in the future.

Relates: elastic/ingest-dev#3072
(cherry picked from commit d0dda41)

Co-authored-by: Dimitrios Liappis <dimitrios.liappis@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants