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

[CI] Separate pipeline for packageing elastic-agent v 7.17 #37863

Merged
merged 16 commits into from
Feb 13, 2024

Conversation

pazone
Copy link
Contributor

@pazone pazone commented Feb 5, 2024

Proposed commit message

Separate packaging pipeline for elastic-agent v7.17

Relates: https://github.com/elastic/ingest-dev/issues/2644

@pazone pazone requested a review from a team as a code owner February 5, 2024 16:53
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Feb 5, 2024
@mergify mergify bot assigned pazone Feb 5, 2024
Copy link
Contributor

mergify bot commented Feb 5, 2024

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @pazone? 🙏.
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

@elasticmachine
Copy link
Collaborator

elasticmachine commented Feb 5, 2024

💚 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: 12 min 18 sec

❕ Flaky test report

No test was executed to be analysed.

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

@pierrehilbert pierrehilbert added the Team:Elastic-Agent Label for the Agent team label Feb 5, 2024
@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Feb 5, 2024
catalog-info.yaml Outdated Show resolved Hide resolved
catalog-info.yaml Outdated Show resolved Hide resolved
catalog-info.yaml Outdated Show resolved Hide resolved
catalog-info.yaml Outdated Show resolved Hide resolved
catalog-info.yaml Outdated Show resolved Hide resolved
catalog-info.yaml Outdated Show resolved Hide resolved
Copy link
Contributor

mergify bot commented Feb 6, 2024

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b ci_packaging_elastic_agent upstream/ci_packaging_elastic_agent
git merge upstream/main
git push upstream ci_packaging_elastic_agent

Copy link
Contributor

@belimawr belimawr left a comment

Choose a reason for hiding this comment

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

I know little about the CI part of Beats, but LGTM. Anyway I'll wait for the points raised by @v1v to be addressed and CI to be green.

@pazone pazone requested a review from a team as a code owner February 12, 2024 15:52
@pazone
Copy link
Contributor Author

pazone commented Feb 12, 2024

@v1v Corrected the branch configuration

catalog-info.yaml Outdated Show resolved Hide resolved
Copy link
Member

@v1v v1v left a comment

Choose a reason for hiding this comment

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

There are merge conflicts

catalog-info.yaml Outdated Show resolved Hide resolved
Copy link
Member

@v1v v1v left a comment

Choose a reason for hiding this comment

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

I'm a bit confused about the title and the changes.

If this is only for 7.17, what's the reason main and 8.x branches are in the list of supported branches?

@pazone
Copy link
Contributor Author

pazone commented Feb 13, 2024

@v1v the pipeline will be triggered remotely. Removed other branches from configuration just in case

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

💚 Build Succeeded

History

cc @pazone

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @pazone

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @pazone

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @pazone

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @pazone

@pazone
Copy link
Contributor Author

pazone commented Feb 13, 2024

@belimawr all set. could you take a look?

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @pazone

@pazone pazone merged commit be66efa into main Feb 13, 2024
24 checks passed
@pazone pazone deleted the ci_packaging_elastic_agent branch February 13, 2024 17:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Team:Elastic-Agent Label for the Agent team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants