a97f6ce Use jinja templates to provide 'full-jobs'

Authored and Committed by mkovarik 4 years ago
40 files changed. 596 lines added. 1123 lines removed.
openshift/integration/koji/containers/jenkins-slave/Dockerfile
file modified
+1 -1
openshift/integration/koji/pipelines/Makefile
file modified
+1 -1
openshift/integration/koji/pipelines/jobs/mbs-backend-greenwave-promote-to-prod.env
file modified
+3 -1
openshift/integration/koji/pipelines/jobs/mbs-backend-greenwave-promote-to-stage.env
file modified
+3 -1
openshift/integration/koji/pipelines/jobs/mbs-backend-promoting-to-prod.env
file removed
-5
openshift/integration/koji/pipelines/jobs/mbs-backend-promoting-to-prod.tmpl
file removed
-1
openshift/integration/koji/pipelines/jobs/mbs-backend-promoting-to-stage.env
file removed
-5
openshift/integration/koji/pipelines/jobs/mbs-backend-promoting-to-stage.tmpl
file removed
-1
openshift/integration/koji/pipelines/jobs/mbs-dev-integration-test.env
file removed
-1
openshift/integration/koji/pipelines/jobs/mbs-dev-integration-test.tmpl
file removed
-1
openshift/integration/koji/pipelines/jobs/mbs-frontend-greenwave-promote-to-prod.env
file modified
+3 -1
openshift/integration/koji/pipelines/jobs/mbs-frontend-greenwave-promote-to-stage.env
file modified
+3 -1
openshift/integration/koji/pipelines/jobs/mbs-frontend-promoting-to-prod.env
file removed
-5
openshift/integration/koji/pipelines/jobs/mbs-frontend-promoting-to-prod.tmpl
file removed
-1
openshift/integration/koji/pipelines/jobs/mbs-frontend-promoting-to-stage.env
file removed
-5
openshift/integration/koji/pipelines/jobs/mbs-frontend-promoting-to-stage.tmpl
file removed
-1
openshift/integration/koji/pipelines/jobs/mbs-prod-integration-test.env
file removed
-2
openshift/integration/koji/pipelines/jobs/mbs-prod-integration-test.tmpl
file removed
-1
openshift/integration/koji/pipelines/jobs/mbs-stage-integration-test.env
file removed
-2
openshift/integration/koji/pipelines/jobs/mbs-stage-integration-test.tmpl
file removed
-1
openshift/integration/koji/pipelines/jobs/mbs-trigger-on-latest-tag.env
file modified
+1 -1
openshift/integration/koji/pipelines/jobs/mbs-trigger-on-stage-tag.env
file modified
+1 -1
openshift/integration/koji/pipelines/templates/mbs-build-template.yaml
file modified
+15 -16
openshift/integration/koji/pipelines/templates/mbs-build.Jenkinsfile
file modified
+17 -73
openshift/integration/koji/pipelines/templates/mbs-greenwave-trigger.Jenkinsfile
file modified
+118 -75
openshift/integration/koji/pipelines/templates/mbs-greenwave-trigger.yaml
file modified
+26 -9
openshift/integration/koji/pipelines/templates/mbs-image-promotion-template.yaml
file removed
-120
openshift/integration/koji/pipelines/templates/mbs-image-promotion.Jenkinsfile
file removed
-125
openshift/integration/koji/pipelines/templates/mbs-integration-test-template.yaml
file removed
-143
openshift/integration/koji/pipelines/templates/mbs-integration-test.Jenkinsfile
file removed
-267
openshift/integration/koji/pipelines/templates/mbs-polling-pagure.Jenkinsfile
file added
+103
openshift/integration/koji/pipelines/templates/mbs-polling-pagure.yaml
file modified
+9 -135
openshift/integration/koji/pipelines/templates/mbs-repotracker-trigger.Jenkinsfile
file modified
+51 -105
openshift/integration/koji/pipelines/templates/mbs-repotracker-trigger.yaml
file modified
+21 -15
openshift/integration/koji/pipelines/templates/snippets/c3i-library-parameters.yaml
file added
+8
openshift/integration/koji/pipelines/templates/snippets/c3i-library.groovy
file added
+2
openshift/integration/koji/pipelines/templates/snippets/default-agent.groovy
file added
+29
openshift/integration/koji/pipelines/templates/snippets/functions.groovy
file added
+64
openshift/integration/koji/pipelines/templates/snippets/get_paas_domain.groovy
file added
+14
openshift/integration/koji/pipelines/templates/snippets/mbs-integration-test.groovy
file added
+103
    Use jinja templates to provide 'full-jobs'
    
    Reduce number of jobs from 20 to 12 by merging them and using
    templating to avoid code duplicity.
    Jenkinsfile are directly put into jobs as a script - not pulled from
    repository - avoiding issue with not clean workspace.
    Secrets are taken from openshift using service account intead of
    refering them in environment which caused that secret had to exist and
    could be empty.
    Job execution is straitforward - one jobs is repsonsible for each
    process, only triggered jobs are c3iaas request and
    pipeline-as-a-service job, everything else is managed by one job.