Add support for nektos/act

[jgrumboe]

Description

This PR adds support for nektos/act to run github actions locally.

Checklist

• End user documentation updated

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: login-issues@jira.linuxfoundation.org

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[jgrumboe]

I signed it

[jgrumboe]

@vinny-sabatini could you please review

[Raffo]

@jgrumboe I haven't used nektos/act myself, so I don't really have an opinion on that, but I do have a question: given that in CI we basically just run builds and tests, which are cross platform and can be natively run locally, what is the benefit of being able to run those locally?

[jgrumboe]

@Raffo It gives you the possibility to test the usage of github actions before committing and waiting for failed or successful CI runs.

And it is convenient for me to just run "act" and the CI pipeline kicksoff like after git push.

[Raffo]

@jgrumboe "it's convenient" is good enough for me. I will approve once you get a LGTM. One thing I don't understand: why is there no check for actions in this PR?

[seanmalloy]

One thing I don't understand: why is there no check for actions in this PR?

We need to figure this out before it can be merged. Other recent pull requests have the GH actions running. Does this change somehow prevent/break the GH actions?

[jgrumboe]

Found the error: invalid syntax
https://github.com/kubernetes-sigs/external-dns/actions/runs/283763068
🤦‍♂️
Will look into it the next days.

[jgrumboe]

/hold

[jgrumboe]

/unhold

The if: expression needs single quotes when doing string comparison.

[jgrumboe]

@Raffo @seanmalloy
Now it should be fine to merge. Thx

[seanmalloy]

/lgtm
/assign @Raffo @njuettner

[Raffo]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jgrumboe, Raffo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [Raffo]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jgrumboe]

/label hacktoberfest-accepted

[k8s-ci-robot]

@jgrumboe: The label(s) /label hacktoberfest-accepted cannot be applied. These labels are supported: api-review, community/discussion, community/maintenance, community/question, cuj/build-train-deploy, cuj/multi-user, platform/aws, platform/azure, platform/gcp, platform/minikube, platform/other, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash

In response to this:

/label hacktoberfest-accepted

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.