Add rw-root group
Some hosts, such as the Raspberry Pis built using default Fedora images, do not have proper filesystem separation, but use a single volume for the entire filesystem. These hosts cannot have the root filesystem mounted read-only, since all the writable data are also stored there. When Jenkins runs configuration policy jobs, it always tries to remount the root filesystem as read-only on every machine that it configured. For these hosts with a single volume, this step fails, causing the job to be marked as failed. To avoid this, I have added a new group, *rw-root*; hosts in this group will be omitted from the final remount step.jenkins-master
parent
b32b4a2c99
commit
276ac7e5fb
4
hosts
4
hosts
|
@ -107,6 +107,10 @@ dns0.pyrocufflink.blue
|
||||||
[radius:children]
|
[radius:children]
|
||||||
samba-dc
|
samba-dc
|
||||||
|
|
||||||
|
[rw-root]
|
||||||
|
build1-aarch64.pyrocufflink.blue
|
||||||
|
build2-armv7hl.pyrocufflink.blue
|
||||||
|
|
||||||
[samba-dc]
|
[samba-dc]
|
||||||
dc0.pyrocufflink.blue
|
dc0.pyrocufflink.blue
|
||||||
|
|
||||||
|
|
|
@ -83,7 +83,7 @@ def stageRemountRO(limit) {
|
||||||
stage('Remount R/O') {
|
stage('Remount R/O') {
|
||||||
ansiblePlaybook \
|
ansiblePlaybook \
|
||||||
playbook: 'remount.yml',
|
playbook: 'remount.yml',
|
||||||
limit: limit,
|
limit: limit + ':!rw-root',
|
||||||
become: true,
|
become: true,
|
||||||
vaultCredentialsId: 'ansible-vault',
|
vaultCredentialsId: 'ansible-vault',
|
||||||
extras: '--diff'
|
extras: '--diff'
|
||||||
|
|
Loading…
Reference in New Issue