Skip to content

Conversation

@v1v
Copy link
Member

@v1v v1v commented Sep 12, 2022

What does this PR do?

Use setupAPMGitEmail within the release context

Why

withGitRelease configures the git user pointed to the last committer, but in this case we want to force the user

@v1v v1v requested review from a team September 12, 2022 11:59
@ghost
Copy link

ghost commented Sep 12, 2022

💚 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: 2022-09-12T13:39:14.110+0000

  • Duration: 56 min 26 sec

Test stats 🧪

Test Results
Failed 0
Passed 3143
Skipped 36
Total 3179

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

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

  • /test : Re-trigger the build.

  • run benchmark tests : Run the benchmark tests.

  • run jdk compatibility tests : Run the JDK Compatibility tests.

  • run integration tests : Run the Agent Integration tests.

  • run end-to-end tests : Run the APM-ITs.

  • run windows tests : Build & tests on windows.

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

@v1v v1v changed the title release: configure git user globally release: configure git user Sep 12, 2022
@v1v v1v merged commit df96649 into elastic:main Sep 12, 2022
@eyalkoren
Copy link
Contributor

that was a race condition and you won @v1v 😄

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.

5 participants