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

[8.14](backport #39506) Remove hardcoded module definitions in CI #39529

Merged
merged 1 commit into from
May 13, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented May 13, 2024

Proposed commit message

For reasons described in 1, we hard coded aws or kubernetes for the env var MODULE, when no file changes were detected under modules/ per project.

This commit reverts this and allows all module tests to run if no changesets apply. As discussed in 1, for the tests to run properly (and not go into an infinite loop)
if there are no module changes the MODULE env var should not be set, rather than set to an empty string.

This commit is an important fix as it covers a major delta in test coverage between Jenkins and Buildkite.

Related issues

Closes https://github.com/elastic/ingest-dev/issues/2993

Screenshots

Logs/Tests


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

Footnotes

  1. https://github.com/elastic/ingest-dev/issues/2993#issuecomment-2104741977 2

For reasons described in [^1], we hard coded `aws` or `kubernetes` for the env var `MODULE`, when no file changes were detected under `modules/` per project.

This commit reverts this and allows all module tests to run if no changesets apply. As discussed in [^1], for the tests to run properly (and not go into an infinite loop)
if there are no module changes the `MODULE` env var should **not** be set, rather than set to an empty string.

This commit is an important fix as it covers a major delta in test coverage between Jenkins and Buildkite.

Closes https://github.com/elastic/ingest-dev/issues/2993

[^1]: https://github.com/elastic/ingest-dev/issues/2993#issuecomment-2104741977

(cherry picked from commit c91503b)
@mergify mergify bot requested a review from a team as a code owner May 13, 2024 09:41
@mergify mergify bot added the backport label May 13, 2024
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label May 13, 2024
@dliappis dliappis removed the needs_team Indicates that the issue/PR needs a Team:* label label May 13, 2024
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label May 13, 2024
@dliappis dliappis added Team:Ingest-EngProd ci and removed needs_team Indicates that the issue/PR needs a Team:* label labels May 13, 2024
Copy link
Contributor

@dliappis dliappis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM as it's a clean backport. Will merge once ci is green.

@dliappis dliappis enabled auto-merge (squash) May 13, 2024 10:31
@dliappis dliappis merged commit 619e51f into 8.14 May 13, 2024
106 of 108 checks passed
@dliappis dliappis deleted the mergify/bp/8.14/pr-39506 branch May 13, 2024 11:16
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.

1 participant