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.

Sign up for GitHub

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

Jump to bottom

[Heartbeat] Use stack_release label for synthetics npm install (backport #33362) #33392

Merged
merged 1 commit into from
Nov 1, 2022
Merged

[Heartbeat] Use stack_release label for synthetics npm install (backport #33362) #33392

merged 1 commit into from
Nov 1, 2022

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Oct 18, 2022

This is an automatic backport of pull request #33362 done by Mergify.

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

@andrewvc @mergify
[Heartbeat] Use stack_release label for synthetics npm install (#33362)
22f20ad 
Fixes #31732

Always use the `stack_release` label for `npm i`

(cherry picked from commit f3302cd)
@mergify mergify bot requested a review from a team as a code owner October 18, 2022 20:32
@mergify mergify bot requested review from belimawr and rdner and removed request for a team October 18, 2022 20:32
@mergify mergify bot mentioned this pull request Oct 18, 2022
Merged
6 tasks
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Oct 18, 2022
@botelastic
Copy link

botelastic bot commented Oct 18, 2022

This pull request doesn't have a Team:<team> label.

@elasticmachine
Copy link
Collaborator

💚 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-10-18T20:32:56.528+0000

  • Duration: 124 min 6 sec

Test stats 🧪

Test Results
Failed 0
Passed 23656
Skipped 1950
Total 25606

💚 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!)

@rdner rdner merged commit da04ef5 into 8.5 Nov 1, 2022
@rdner rdner deleted the mergify/bp/8.5/pr-33362 branch November 1, 2022 09:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@rdner rdner rdner approved these changes

@belimawr belimawr Awaiting requested review from belimawr belimawr is a code owner automatically assigned from elastic/elastic-agent-data-plane

Assignees
No one assigned
Labels
needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@elasticmachine @rdner @andrewvc