[release] Don't rely on koji for the default pipeline

... and add a Pipeline definition for those specifically using Koji. Most of new users trying distro-factory won't have a koji setup to begin with. This makes it easier for newcomers to try out this project. Signed-off-by: Murilo Belluzzo <[email protected]>
clearlinux · May 22, 2019 · 9aaaf60 · 9aaaf60
1 parent 87f9394
commit 9aaaf60
Show file tree

Hide file tree

Showing 2 changed files with 50 additions and 1 deletion.
diff --git a/release/ReleaseKojiPipeline b/release/ReleaseKojiPipeline
@@ -0,0 +1,50 @@
+pipeline {
+    agent { label 'clr-builders' }
+
+    environment {
+        NAMESPACE = "${JOB_NAME}"
+        WORK_DIR = "${WORKSPACE}/work"
+    }
+
+    stages {
+        stage('Prologue') {
+            steps {
+                sh 'release/prologue.sh'
+            }
+        }
+        stage('Setup Content') {
+            steps {
+                sh 'release/koji.sh'
+                sh 'release/content.sh'
+            }
+        }
+        stage('Create Update Stream') {
+            steps {
+                sh 'release/mixer.sh'
+                sh 'release/mca-check.sh'
+            }
+        }
+        stage('Create Images') {
+            steps {
+                sh 'release/images.sh'
+            }
+        }
+        stage('Stage') {
+            steps {
+                sh 'release/release_notes.sh'
+                sh 'release/stage.sh'
+            }
+        }
+        stage('Publish') {
+            steps {
+                sh 'release/publish.sh'
+            }
+        }
+    }
+
+    post {
+        always {
+            echo "Release Pipeline OUT - ${env.BUILD_TAG}"
+        }
+    }
+}
diff --git a/release/ReleasePipeline b/release/ReleasePipeline
@@ -14,7 +14,6 @@ pipeline {
         }
         stage('Setup Content') {
             steps {
-                sh 'release/koji.sh'
                 sh 'release/content.sh'
             }
         }