Skip to content
Snippets Groups Projects
Commit 3ab2af08 authored by MJB's avatar MJB
Browse files

#88 updates to readme for protected branches

parent db24c19b
No related branches found
No related tags found
No related merge requests found
...@@ -132,7 +132,7 @@ lxc init ...@@ -132,7 +132,7 @@ lxc init
Follow the interactive prompts, use the defaults apart from the storage pool type, use `dir` type Follow the interactive prompts, use the defaults apart from the storage pool type, use `dir` type
Configure ip table persistence Now configure ip table persistence, this is needed for the fixtures script to work but not for CI
``` ```
echo iptables-persistent iptables-persistent/autosave_v4 boolean true | sudo debconf-set-selections echo iptables-persistent iptables-persistent/autosave_v4 boolean true | sudo debconf-set-selections
...@@ -147,22 +147,4 @@ cp /tmp/install-git-runner.sh /var/lib/lxd/containers/clmc-ci/rootfs/tmp ...@@ -147,22 +147,4 @@ cp /tmp/install-git-runner.sh /var/lib/lxd/containers/clmc-ci/rootfs/tmp
chmod 755 /var/lib/lxd/containers/clmc-ci/rootfs/tmp chmod 755 /var/lib/lxd/containers/clmc-ci/rootfs/tmp
``` ```
Note that the branch must be "protected" for the secret repo rc variables to be passed to the CI script
\ No newline at end of file
The VM is started using a libvirt vagrant file through the following command:
`VAGRANT_VAGRANTFILE=Vagrantfile.libvirt vagrant up`
The VM has gitlab-runner installed::
```
VAGRANT_VAGRANTFILE=Vagrantfile.libvirt vagrant up
VAGRANT_VAGRANTFILE=Vagrantfile.libvirt vagrant ssh -- -tt "sudo /vagrant/scripts/test/install-git-runner.sh"
```
Runners can be installed on developers virtualbox VMs if necessary, in that case you can just use
```
vagrant up
vagrant ssh -- -tt "sudo /vagrant/scripts/test/install-git-runner.sh"
```
\ No newline at end of file
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment