Hi, we'd like to migrate some of our workloads into
Kubernetes jobs; see for example:
https://github.com/projectatomic/papr/pull/70/commits/bdaabc975b6770e2c6826…
What are the available resources in apps.ci versus Duffy?
A lot of our jobs want basically a "classic Docker"
environment with e.g. uid 0, but not CAP_SYS_ADMIN. And with seccomp disabled, etc.
I was trying to create the test pod below, but it fails. It looks like our accounts
use the default SCC. Can we lift these restrictions?
BTW, I'd also like oci-kvm-hook installed, with this patch: https://github.com/stefwalter/oci-kvm-hook/pull/4
apiVersion: v1
kind: DeploymentConfig
metadata:
labels:
run: cgwalters-shell
name: cgwalters-shell
spec:
replicas: 1
selector:
run: cgwalters-shell
strategy:
resources: {}
template:
metadata:
labels:
run: cgwalters-shell
spec:
containers:
- args:
- sleep
- 24h
image: registry.fedoraproject.org/fedora:27
name: cgwalters-shell
# Run as uid 0
securityContext:
runAsUser: 0
Hi all,
we[1] have jobs triggered by every new or updated PR, configured
accordingly to [2] - Mode 2.
The jobs are triggered properly for people listed in the "Admin list" or
"White list" section, but not for people from "List of organizations.
Their members will be whitelisted.".
The relevant part of JJB configuration:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
triggers:
- github-pull-request:
admin-list:
- dahorak
org-list:
- Tendrl
allow-whitelist-orgs-as-admins: false
trigger-phrase: '.*run build.*'
skip-build-phrase: 'no build'
github-hooks: true
cancel-builds-on-update: true
status-context: 'CentOS CI - package build'
status-add-test-results: false
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Is there any other configuration needed, to enable the "List of
organizations" functionality?
Also the "cancel-builds-on-update: true" configuration seems not to
work, but I didn't debug it more.
[1] https://github.com/Tendrl
[2] https://wiki.centos.org/QaWiki/CI/GithubIntegration
Thanks,
Daniel