actions/actions-runner-controller
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity
579 Commits 33 Branches 147 Tags
88b8871830095a3c3e01b445be8c8188319f0db5
Commit Graph
6 Commits
Author SHA1 Message Date
Yusuke KuokaandGitHub b305e38b17 Add webhook-based autoscale for Enterprise runners (#906) 
Fixes #892
 2021-11-09 09:04:19 +09:00
Yusuke Kuoka 1a75b4558b Fix E2E test to actualy pass
Lint and Test Charts / lint-test (push) Has been cancelled
Details 
I have a dedicated GitHub organization and a private repository to run this E2E test. After a few fixes included in this change, it has successfully passed.
 2021-09-15 09:34:48 +09:00
Yusuke KuokaandGitHub c78116b0f9 e2e: Cover RunnerDeployment (#668) 
Previously the E2E test suite covered only RunnerSet. This refactors the existing E2E test code to extract the common test structure into a `env` struct and its methods, and use it to write two very similar tests, one for RunnerSet and another for RunnerDeployment.
 2021-06-29 17:52:43 +09:00
Yusuke KuokaandGitHub 7722730dc0 e2e: Concurrent workflow jobs (#667) 
Enhances out existing E2E test suite to additionally support triggering two or more concurrent workflow jobs and verifying all the results, so that you can ensure the runners managed by the controller are able to handle jobs reliably when loaded.
 2021-06-29 14:34:27 +09:00
Yusuke KuokaandGitHub 7a305d2892 e2e: Install and run workflow and verify the result (#661) 
This enhances the E2E test suite introduced in #658 to also include the following steps:

- Install GitHub Actions workflow
- Trigger a workflow run via a git commit
- Verify the workflow run result

In the workflow, we use `kubectl create cm --from-literal` to create a configmap that contains an unique test ID. In the last step we obtain the configmap from within the E2E test and check the test ID to match the expected one.

To install a GitHub Actions workflow, we clone a GitHub repository denoted by the TEST_REPO envvar, progmatically generate a few files with some Go code, run `git-add`, `git-commit`, and then `git-push` to actually push the files to the repository. A single commit containing an updated workflow definition and an updated file seems to run a workflow derived to the definition introduced in the commit, which was a bit surpirising and useful behaviour.

At this point, the E2E test fully covers all the steps for a GitHub token based installation. We need to add scenarios for more deployment options, like GitHub App, RunnerDeployment, HRA, and so on. But each of them would worth another pull request.
 2021-06-28 08:30:32 +09:00
Yusuke KuokaandGitHub 2703fa75d6 Add e2e test (#658) 
This is the initial version of our E2E test suite which is currently a subset of the acceptance test suite reimplemented in Go.

To run it, pass `-run ^TestE2E$` to `go test`, without `-short`, like `go test -timeout 600s -run ^TestE2E$ github.com/actions-runner-controller/actions-runner-controller/test/e2e -v`.

`make test` is modified to pass `-short` to `go test` by default to skip E2E tests.

The biggest benefit of rewriting the acceptance test in Go turned out to be the fact that you can easily rerun each step- a go-test "subtest"- individually from your IDE, for faster turnaround.  Both VS Code and IntelliJ IDEA/GoLand are known to work.

In the near future, we will add more steps to the suite, like actually git-comminting some Actions workflow and pushing some commit to trigger a workflow run, and verify the workflow and job run results, and finally run it on our `test` workflow to fully automated E2E testing. But that s another story.
 2021-06-27 16:28:07 +09:00