5 Commits

Include renames

Author	SHA1	Message	Date
3 people	aa6dab5a9a	Changes to folder structure to allow multigroups and changed go mod name (#2105) ... * Changed folder structure to allow multi group registration * included actions.github.com directory for resources and controllers * updated go module to actions/actions-runner-controller * publish arc packages under actions-runner-controller * Update charts/actions-runner-controller/docs/UPGRADING.md Co-authored-by: Yusuke Kuoka <ykuoka@gmail.com>	2022-12-28 09:38:34 +09:00
Yusuke KuokaandGitHub	ba4bd7c0db	e2e,acceptance: Cover enterprise runners (#1124) ... Adds various code and changes I have used while testing #1062	2022-02-17 09:16:28 +09:00
Yusuke Kuoka	1a75b4558b	Fix E2E test to actualy pass ... 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	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