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

Fix missing docker staging DRA artifacts #39297

Merged
merged 1 commit into from
Apr 30, 2024

Conversation

dliappis
Copy link
Contributor

@dliappis dliappis commented Apr 30, 2024

Proposed commit message

The DRA staging release is failing because the Buildkite step isn't capturing the right artifacts.
This commit fixes the issue by adjusting the artifact_paths to match the other steps.

Logs

Example of failure: https://buildkite.com/elastic/beats-packaging-pipeline/builds/96#018f2e52-8eda-4311-91fc-662353604f29

The DRA staging release is failing because the Buildkite step isn't
capturing the right artifacts.
This commit fixes the issue by adjusting the artifact_paths to match
the other steps.
@dliappis dliappis self-assigned this Apr 30, 2024
@dliappis dliappis requested a review from a team as a code owner April 30, 2024 11:20
@botelastic botelastic bot added needs_team Indicates that the issue/PR needs a Team:* label and removed needs_team Indicates that the issue/PR needs a Team:* label labels Apr 30, 2024
Copy link
Contributor

mergify bot commented Apr 30, 2024

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

@dliappis dliappis added backport-7.17 Automated backport to the 7.17 branch with mergify backport-v8.13.0 Automated backport with mergify backport-v8.14.0 Automated backport with mergify labels Apr 30, 2024
@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: 2024-04-30T11:20:29.996+0000

  • Duration: 15 min 48 sec

Test stats 🧪

Test Results
Failed 0
Passed 2
Skipped 0
Total 2

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

@dliappis dliappis merged commit 85c9d14 into elastic:main Apr 30, 2024
12 checks passed
mergify bot pushed a commit that referenced this pull request Apr 30, 2024
The DRA staging release is failing because the Buildkite step isn't capturing the right artifacts.
This commit fixes the issue by adjusting the artifact_paths to match the other steps.

(cherry picked from commit 85c9d14)

# Conflicts:
#	.buildkite/packaging.pipeline.yml
mergify bot pushed a commit that referenced this pull request Apr 30, 2024
The DRA staging release is failing because the Buildkite step isn't capturing the right artifacts.
This commit fixes the issue by adjusting the artifact_paths to match the other steps.

(cherry picked from commit 85c9d14)

# Conflicts:
#	.buildkite/packaging.pipeline.yml
mergify bot pushed a commit that referenced this pull request Apr 30, 2024
The DRA staging release is failing because the Buildkite step isn't capturing the right artifacts.
This commit fixes the issue by adjusting the artifact_paths to match the other steps.

(cherry picked from commit 85c9d14)
dliappis added a commit that referenced this pull request Apr 30, 2024
The DRA staging release is failing because the Buildkite step isn't capturing the right artifacts.
This commit fixes the issue by adjusting the artifact_paths to match the other steps.

(cherry picked from commit 85c9d14)

Co-authored-by: Dimitrios Liappis <dimitrios.liappis@gmail.com>
pazone pushed a commit that referenced this pull request Apr 30, 2024
The DRA staging release is failing because the Buildkite step isn't capturing the right artifacts.
This commit fixes the issue by adjusting the artifact_paths to match the other steps.
pazone pushed a commit that referenced this pull request Apr 30, 2024
The DRA staging release is failing because the Buildkite step isn't capturing the right artifacts.
This commit fixes the issue by adjusting the artifact_paths to match the other steps.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-7.17 Automated backport to the 7.17 branch with mergify backport-v8.13.0 Automated backport with mergify backport-v8.14.0 Automated backport with mergify ci Team:Ingest-EngProd
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants