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

workflows: remove AppVeyor from release workflow #8948

Merged
merged 1 commit into from
Jun 12, 2024

Conversation

patrick-stephens
Copy link
Contributor

No longer depend on AppVeyor builds completing for a release and no longer provide them officially.
Github built binaries are the recommended version for a while and the docs reflect this.
AppVeyor binaries are inconsistent with missing YAML support, etc.


Enter [N/A] in the box, if an item is not applicable to your change.

Testing
Before we can approve your change; please submit the following in a comment:

  • Example configuration file for the change
  • Debug log output from testing the change
  • Attached Valgrind output that shows no leaks or memory corruption was found

If this is a change to packaging of containers or native binaries then please confirm it works for all targets.

  • Run local packaging test showing all targets (including any new ones) build.
  • Set ok-package-test label to test for all targets (requires maintainer to do).

Documentation

  • Documentation required for this feature

Backporting

  • Backport to latest stable release.

Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.

Signed-off-by: Patrick Stephens <pat@chronosphere.io>
@patrick-stephens patrick-stephens merged commit 7c8a4bb into master Jun 12, 2024
29 checks passed
@patrick-stephens patrick-stephens deleted the workflows_remove_appveyor_release branch June 12, 2024 15:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants