Support exporting Jenkinsfiles

kptdev · Jul 10, 2020 · fa9abdf · fa9abdf
1 parent 86129fb
commit fa9abdf
Show file tree

Hide file tree

Showing 2 changed files with 67 additions and 2 deletions.
diff --git a/internal/cmdexport/cmdexport.go b/internal/cmdexport/cmdexport.go
@@ -135,6 +135,7 @@ func supportedOrchestrators() map[string]orchestrators.Pipeline {
 		"github-actions": new(orchestrators.GitHubActions),
 		"cloud-build":    new(orchestrators.CloudBuild),
 		"gitlab-ci":      new(orchestrators.GitLabCI),
+		"jenkins":        new(orchestrators.Jenkins),
 	}
 }
 

diff --git a/internal/cmdexport/cmdexport_test.go b/internal/cmdexport/cmdexport_test.go
@@ -45,12 +45,12 @@ var testCases = []TestCase{
 	{
 		description: "fails on not providing working orchestrator",
 		params:      []string{"dir"},
-		err:         "--workflow flag is required. It must be one of cloud-build, github-actions, gitlab-ci",
+		err:         "--workflow flag is required. It must be one of cloud-build, github-actions, gitlab-ci, jenkins",
 	},
 	{
 		description: "fails on an unsupported workflow orchestrator",
 		params:      []string{".", "--workflow", "random-orchestrator"},
-		err:         "unsupported orchestrator random-orchestrator. It must be one of cloud-build, github-actions, gitlab-ci",
+		err:         "unsupported orchestrator random-orchestrator. It must be one of cloud-build, github-actions, gitlab-ci, jenkins",
 	},
 	{
 		description: "exports a GitHub Actions pipeline",
@@ -212,6 +212,70 @@ kpt:
       - docker:dind
     script: docker run -v $PWD:/app -v /var/run/docker.sock:/var/run/docker.sock gongpu/kpt:latest
         fn run /app/resources --fn-path /app/functions
+`,
+	},
+	{
+		description: "exports a Jenkinsfile",
+		params: []string{
+			"resources",
+			"-w",
+			"jenkins",
+		},
+		expected: `
+pipeline {
+    agent any
+
+    stages {
+        stage('Run kpt functions') {
+            steps {
+                // This requires that docker is installed on the agent.
+                // And your user, which is usually "jenkins", should be added to the "docker" group to access "docker.sock".
+                sh '''
+                    docker run \
+                    -v $PWD:/app \
+                    -v /var/run/docker.sock:/var/run/docker.sock \
+                    gongpu/kpt:latest \
+                    fn run /app/resources
+                '''
+            }
+        }
+    }
+}
+`,
+	},
+	{
+		description: "exports a Jenkinsfile with --fn-path",
+		params: []string{
+			"resources",
+			"-w",
+			"jenkins",
+			"--fn-path",
+			"functions/label-namespace.yaml",
+			"--fn-path",
+			"functions/gate-keeper.yaml",
+		},
+		expected: `
+pipeline {
+    agent any
+
+    stages {
+        stage('Run kpt functions') {
+            steps {
+                // This requires that docker is installed on the agent.
+                // And your user, which is usually "jenkins", should be added to the "docker" group to access "docker.sock".
+                sh '''
+                    docker run \
+                    -v $PWD:/app \
+                    -v /var/run/docker.sock:/var/run/docker.sock \
+                    gongpu/kpt:latest \
+                    fn run /app/resources \
+                    --fn-path /app/functions/label-namespace.yaml \
+                    --fn-path /app/functions/gate-keeper.yaml
+                '''
+            }
+        }
+    }
+}
 `,
 	},
 }