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

bump npcap version to 1.78 (backport #360) #361

Merged
merged 1 commit into from
Dec 7, 2023

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Dec 6, 2023

This is an automatic backport of pull request #360 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

(cherry picked from commit 43b3528)
@mergify mergify bot mentioned this pull request Dec 6, 2023
@efd6 efd6 requested a review from v1v December 6, 2023 09:45
@efd6 efd6 enabled auto-merge (squash) December 6, 2023 09:47
@efd6 efd6 self-assigned this Dec 6, 2023
@v1v
Copy link
Member

v1v commented Dec 6, 2023

This PR uses the legacy Jenkins pipelines. BK pipelines were migrated to 1.20 but 1.20.11 was updated before their backports. I guess that's the reason for the above error messages in the GH comments

@elasticmachine
Copy link

elasticmachine commented Dec 6, 2023

💚 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

  • Duration: 6 min 6 sec

🤖 GitHub comments

Expand to view the GitHub comments

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

  • /test : Re-trigger the build.

@efd6
Copy link
Contributor

efd6 commented Dec 6, 2023

/test

@elasticmachine
Copy link

💔 Build Failed

Failed CI Steps

History

cc @efd6

@elasticmachine
Copy link

💔 Build Failed

Failed CI Steps

History

cc @efd6

@elasticmachine
Copy link

💚 Build Succeeded

History

cc @efd6

@efd6
Copy link
Contributor

efd6 commented Dec 6, 2023

@v1v The build does not appear to be running "Staging/Ubuntu {ARM,X84_64}". Are you able to look into that?

@v1v
Copy link
Member

v1v commented Dec 7, 2023

Are you able to look into that?

I think that's certainly related to the missing backports for the BK PRs in the 1.20.11.x branch.

I can figure out how to solve it, although this project is now owned by the @elastic/ingest-eng-prod

@v1v v1v disabled auto-merge December 7, 2023 08:45
@v1v v1v merged commit cd905d3 into 1.20.11.x Dec 7, 2023
20 of 22 checks passed
@v1v v1v deleted the mergify/bp/1.20.11.x/pr-360 branch December 7, 2023 08:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants