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

Onboard repository in Buildkite #35777

Merged
merged 3 commits into from
Jun 15, 2023
Merged

Onboard repository in Buildkite #35777

merged 3 commits into from
Jun 15, 2023

Conversation

mrodm
Copy link
Contributor

@mrodm mrodm commented Jun 15, 2023

What does this PR do?

This PR onboards this repository into Buildkite and creates the skeleton for the main pipeline.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Related issues

@mrodm mrodm added the ci label Jun 15, 2023
@mrodm mrodm requested review from alexsapran and jlind23 June 15, 2023 10:53
@mrodm mrodm self-assigned this Jun 15, 2023
@mrodm mrodm requested a review from a team as a code owner June 15, 2023 10:53
@mrodm mrodm requested a review from faec June 15, 2023 10:53
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jun 15, 2023
@botelastic
Copy link

botelastic bot commented Jun 15, 2023

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

@mergify
Copy link
Contributor

mergify bot commented Jun 15, 2023

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @mrodm? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

@mrodm
Copy link
Contributor Author

mrodm commented Jun 15, 2023

@jlind23 @alexsapran do we need to backport this PR to another version ?

alexsapran
alexsapran reviewed Jun 15, 2023
View reviewed changes
Copy link
Contributor

@alexsapran alexsapran left a comment

Choose a reason for hiding this comment

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

we might want to set backport targets for the active branches here.

catalog-info.yaml Show resolved Hide resolved
@elasticmachine
Copy link
Collaborator

elasticmachine commented Jun 15, 2023 •
edited by jenkins-beats-ci bot
Loading

💚 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: 2023-06-15T11:02:04.597+0000

  • Duration: 12 min 38 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!)

@jlind23 jlind23 added backport-7.17 Automated backport to the 7.17 branch with mergify backport-v8.8.0 Automated backport with mergify labels Jun 15, 2023
@jlind23
Copy link
Collaborator

jlind23 commented Jun 15, 2023

@mrodm just added backport labels for 8.8 and 7.17

@mrodm mrodm added the release-note:skip The PR should be ignored when processing the changelog label Jun 15, 2023
@mrodm mrodm merged commit 77c2119 into elastic:main Jun 15, 2023
@mrodm mrodm deleted the onboard_repository_buildkite branch June 15, 2023 13:48
mergify bot pushed a commit that referenced this pull request Jun 15, 2023
@mrodm @mergify
Onboard repository in Buildkite (#35777)
d470e38 
(cherry picked from commit 77c2119)
@mergify mergify bot mentioned this pull request Jun 15, 2023
Merged
mergify bot pushed a commit that referenced this pull request Jun 15, 2023
@mrodm @mergify
Onboard repository in Buildkite (#35777)
d09f96e 
(cherry picked from commit 77c2119)
@mergify mergify bot mentioned this pull request Jun 15, 2023
Merged
mrodm added a commit that referenced this pull request Jun 19, 2023
@mergify @mrodm
Onboard repository in Buildkite (#35777) (#35782)
601ee04 
(cherry picked from commit 77c2119)

Co-authored-by: Mario Rodriguez Molins <[email protected]>
mrodm added a commit that referenced this pull request Jun 19, 2023
@mergify @mrodm
Onboard repository in Buildkite (#35777) (#35781)
f83260a 
(cherry picked from commit 77c2119)

Co-authored-by: Mario Rodriguez Molins <[email protected]>
@reakaleek reakaleek mentioned this pull request Jul 19, 2023
Closed
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@alexsapran alexsapran alexsapran left review comments

@jlind23 jlind23 jlind23 approved these changes

@faec faec faec approved these changes

Assignees

@mrodm mrodm

Labels
backport-7.17 Automated backport to the 7.17 branch with mergify backport-v8.8.0 Automated backport with mergify ci needs_team Indicates that the issue/PR needs a Team:* label release-note:skip The PR should be ignored when processing the changelog
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@mrodm @elasticmachine @jlind23 @alexsapran @faec