Run the integration tests if the event that triggered them is a push to
main. Previous changes to skip these tests on pull requests from forks
or dependabot had the unintended impact of disabling them on merges into
main.
Updates #cleanup
Signed-off-by: Mario Minardi <mario@tailscale.com>
Check that the full name of the repo from pull request events matches
the repo from the GitHub context to ensure we are properly skipping
integration tests coming from forks.
Updates #cleanup
Signed-off-by: Mario Minardi <mario@tailscale.com>
Disable integration tests for dependabot PRs since it does not have
access to the integration testing tailnet.
Updates https://github.com/tailscale/corp/issues/33791
Signed-off-by: Mario Minardi <mario@tailscale.com>
On macOS, `tailscaled` does not manage DNS. Configure it manually in the GitHub action to make
sure MagicDNS name resolution works.
Updates tailscale/corp#32821
Signed-off-by: Percy Wegmann <percy@tailscale.com>
Documented new features:
- Logout functionality
- Ping functionality
Also removed speed-comparison CI flow in preparation for replacing the official GitHub
action with this one.
Updates tailscale/corp#32820
Signed-off-by: Percy Wegmann <percy@tailscale.com>
Even if we just have DERP connectivity, stop pinging so that action can continue sooner.
Updates tailscale/corp#32862
Signed-off-by: Percy Wegmann <percy@tailscale.com>
`oauth-client-secret` is renamed to `oauth-secret` to match the original action.
Not all of the descriptions matched exactly, but this attempts to take the best from both versions.
Default Tailscale version is updated to 1.88.3.
Updates tailscale/corp#32814
Signed-off-by: Percy Wegmann <percy@tailscale.com>
The new argument `ping` allows users to specify a comma-seperated list
of hosts (IP or hostname) to ping in order to verify connectivity.
Ping is considered successful as soon as the peer is reachable either
directly or via DERP.
Updates tailscale/corp#32817
Signed-off-by: Percy Wegmann <percy@tailscale.com>
The tailscale repo does not get tagged for unstable builds, so the best we can do when
building macOS from source is to build from the HEAD of `main`.
Updates tailscale/corp#32813
Signed-off-by: Percy Wegmann <percy@tailscale.com>
Change the default matrix test to use an OAuth client which has the new
set of more granular minimal OAuth scopes necessary to successfully use
the action.
Add a new job that uses the previous OAuth client to ensure that we
don't break legacy clients.
Fixes https://github.com/tailscale/github-action/issues/184
Signed-off-by: Mario Minardi <mario@tailscale.com>
Add the `--unattended` flag when running the action on windows-based
machines. This allows the action to properly connect on windows machines
that do not have full GUI support under the hood (e.g., for the current
batch of `windows-11-arm` runners).
Fixes https://github.com/tailscale/github-action/issues/180
Signed-off-by: Mario Minardi <mario@tailscale.com>
Remove `.tgz` and `.msi` files after they have been downloaded. This was
the behaviour of the action previous to `v3.2.0`, but our logic for
caching removed the deletion of these files.
Can look at downloading these to temp folders to avoid the more complex
logic here as a follow up, but this should unblock / fix the immediate
regression.
Also, on Windows, write `tailscale.log` to the temp dir.
Also, on MacOS, delete the `tailscale` directory that was used to build the `tailscale(d)` commands.
Updates: #170
Co-authored-by: Mario Minardi <mario@tailscale.com>
Signed-off-by: Percy Wegmann <percy@tailscale.com>
Checking for hello is not the best way to verify that Tailscale is connected, and it recently broke because we stopped giving ephemeral nodes access to hello.
Instead, check for connection by parsing the status output as recommended in our KB article https://tailscale.com/kb/1073/hello
If package or SHA download from pkgs.tailscale.com fails with a non-200
repsonse code, make the whole action fail. This catches things like
incorrect versions.
Updates #118
We periodically have reports of failures in the GitHub Action
where there has been no recent change in Tailscale infrastructure
and no indication of a problem in metrics or monitoring.
Right now we have to generate a pull request to get this test
workflow to run. Allow it to be run manually whenever desired.
Signed-off-by: Denton Gentry <dgentry@tailscale.com>
