Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
A
Ansible GAP CI runner
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Jira
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
GÉANT Orchestration and Automation Team
Development Playbooks
Ansible GAP CI runner
Commits
c8311fad
Verified
Commit
c8311fad
authored
2 years ago
by
Karel van Klink
Browse files
Options
Downloads
Patches
Plain Diff
Update readme
parent
4c22e66e
Branches
42-add-missing-application-tutorials-2
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+13
-5
13 additions, 5 deletions
README.md
with
13 additions
and
5 deletions
README.md
+
13
−
5
View file @
c8311fad
# Ansible playbook for deploying a GAP GitLab CI runner
# Ansible playbook for deploying a GAP GitLab CI runner
This playbook is used to install the gitlab-runner package on a VM.
This playbook is used to install the gitlab-runner package on a VM, and register it as such for a GAP repository of
your choice.
To run this playbook:
1.
Provision a 'nat_ci' VM in Puppet
## Running this playbook
1.
Provision a VM somewhere, anywhere
2.
Get the ip address of the new VM, and configure your ssh environment
2.
Get the ip address of the new VM, and configure your ssh environment
3.
Create & activate a python virtual environment and install ansible
3.
Create & activate a python virtual environment and install ansible
4.
Update inventory.yml so that your VM is defined in the "gitlab-runner" group
4.
Update inventory.yml so that your VM is defined in the "gitlab-runner" group
5.
Update group_vars/ci-runners.yml with your gitlab.geant.net username and personal access token
5.
Create the file
`group_vars/ci-runners.yml`
following the
[
example file
](
group_vars/ci-runners.yml.example
)
given
6.
Install the
`community.general`
collection from Ansible galaxy with the following command:
`ansible-galaxy collection install community.general`
*
Consider the type of executor you want/need (docker, shell, etc.)
*
More info on GitLab runner executors can be found
[
here
](
https://docs.gitlab.com/runner/executors/
)
*
This requires acquiring an access token to the GitLab instance for which you want to set up a runner
6.
Install the
`community.general`
collection from Ansible galaxy with the following command:
`ansible-galaxy collection install community.general`
7.
Run the following command to execute the playbook:
`ansible-playbook -i inventory.yml playbook.yml`
7.
Run the following command to execute the playbook:
`ansible-playbook -i inventory.yml playbook.yml`
8.
A new runner should now be available, please ensure that you also set up CI/CD pipelines that make use of this new
runner
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment