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

Automate asset upload when creating a release #517

Merged
merged 1 commit into from
Mar 25, 2020

Conversation

antoninbas
Copy link
Contributor

When creating a release, the necessary assets (yaml manifests and antctl
binaries) will now be added to the release automatically by a Github
workflow. This reduces the potential for human error.

For antctl, we build and upload the following binaries:

  • linux: amd64, arm64, arm (arm/v7)
  • darwin: amd64
  • windows: amd64

Fixes #312

@antrea-bot
Copy link
Collaborator

Thanks for your PR.
Unit tests and code linters are run automatically every time the PR is updated.
E2e, conformance and network policy tests can only be triggered by a member of the vmware-tanzu organization. Regular contributors to the project should join the org.

The following commands are available:

  • /test-e2e: to trigger e2e tests.
  • /skip-e2e: to skip e2e tests.
  • /test-conformance: to trigger conformance tests.
  • /skip-conformance: to skip conformance tests.
  • /test-networkpolicy: to trigger networkpolicy tests.
  • /skip-networkpolicy: to skip networkpolicy tests.
  • /test-all: to trigger all tests.
  • /skip-all: to skip all tests.

These commands can only be run by members of the vmware-tanzu organization.

@antoninbas
Copy link
Contributor Author

jianjuns
jianjuns previously approved these changes Mar 23, 2020
Copy link
Contributor

@jianjuns jianjuns left a comment

Choose a reason for hiding this comment

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

This is great!

@antoninbas
Copy link
Contributor Author

Thanks @jianjuns. I will merge this shortly before the release, in case we include GKE support in 0.5.

weiqiangt
weiqiangt previously approved these changes Mar 24, 2020
abhiraut
abhiraut previously approved these changes Mar 25, 2020
Copy link
Contributor

@abhiraut abhiraut left a comment

Choose a reason for hiding this comment

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

nice.. do you plan to update it for any of the gke assets?

When creating a release, the necessary assets (yaml manifests and antctl
binaries) will now be added to the release automatically by a Github
workflow. This reduces the potential for human error.

For antctl, we build and upload the following binaries:
 * linux: amd64, arm64, arm (arm/v7)
 * darwin: amd64
 * windows: amd64

Fixes antrea-io#312
@antoninbas
Copy link
Contributor Author

/skip-all

@antoninbas
Copy link
Contributor Author

Updated the PR with the following:

  • add antrea-eks.yml to assets (but not the node-init DS yaml)
  • improve antctl documentation (Windows installation steps) based on feedback from @weiqiangt

@antoninbas antoninbas merged commit 47700ae into antrea-io:master Mar 25, 2020
@antoninbas antoninbas deleted the upload-assets-for-release branch March 25, 2020 23:54
@tnqn tnqn mentioned this pull request Feb 29, 2024
3 tasks
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.

Publish antctl binaries for different platforms in releases
6 participants