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

Deprecate release label #2651

Closed
wants to merge 3 commits into from

Conversation

jsoriano
Copy link
Member

@jsoriano jsoriano commented Feb 8, 2022

Update elastic-package to include the changes to deprecate the release label.

Part of elastic/package-spec#225.

@jsoriano jsoriano self-assigned this Feb 8, 2022
go.mod Outdated
@@ -159,3 +159,5 @@ require (
sigs.k8s.io/structured-merge-diff/v4 v4.2.1 // indirect
sigs.k8s.io/yaml v1.3.0 // indirect
)

replace github.com/elastic/elastic-package v0.36.0 => github.com/jsoriano/elastic-package v0.0.0-20220208130905-7470651f3b01
Copy link
Member Author

Choose a reason for hiding this comment

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

To be replaced with a proper elastic-package version after elastic/elastic-package#647 is merged and released.

@elasticmachine
Copy link

elasticmachine commented Feb 8, 2022

💔 Build Failed

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-02-10T17:43:21.308+0000

  • Duration: 96 min 28 sec

Test stats 🧪

Test Results
Failed 0
Passed 3957
Skipped 7
Total 3964

Steps errors 2

Expand to view the steps failures

Test integration: tenable_sc
  • Took 2 min 50 sec . View more details here
  • Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage
Take down the Elastic stack
  • Took 0 min 11 sec . View more details here
  • Description: build/elastic-package stack down -v

🤖 GitHub comments

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

  • /test : Re-trigger the build.

@jsoriano
Copy link
Member Author

/test

2 similar comments
@jsoriano
Copy link
Member Author

/test

@jsoriano
Copy link
Member Author

/test

@jsoriano
Copy link
Member Author

Different packages have failed on different executions, so I guess that problems are not related to this change.

@jsoriano
Copy link
Member Author

Closing this and waiting for the automated bump

@jsoriano jsoriano closed this Feb 11, 2022
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.

2 participants