standalone deployment pipeline for Jenkins #376

thadbeeraf · 2025-11-27T11:26:09Z

standalone deployment pipeline template for Jenkins

dennis-behm

@thadbeeraf please take a look to my initial review. FYI @M-DLB

dennis-behm · 2025-11-28T15:14:50Z

Templates/Deploy_Pipeline/Jenkins/Jenkinsfile

+        string(name: 'releaseVersion', defaultValue: '', description: 'Release version to deploy (only for release eg: rel-1.6.1 )')
+        string(name: 'buildId', defaultValue: '', description: 'Build pipeline ID (e.g., 00000018)')
+        choice(name: 'targetEnvironment', choices: ['integration', 'acceptance', 'production'], description: 'Deployment target environment')
+        string(name: 'branchName', defaultValue: 'main', description: 'Branch name (e.g., main, feature/test-utility-script)')


We should not need to have the branchName reference here.

The releaseVersion and the branchName mean the same while they are both pointing to the "packageReference".

Please take a look to this documentation at: https://github.com/IBM/dbb/tree/main/Templates/Common-Backend-Scripts#packagebuildoutputssh

dennis-behm · 2025-11-28T15:17:09Z

Templates/Deploy_Pipeline/Jenkins/Jenkinsfile

+        string(name: 'buildId', defaultValue: '', description: 'Build pipeline ID (e.g., 00000018)')
+        choice(name: 'targetEnvironment', choices: ['integration', 'acceptance', 'production'], description: 'Deployment target environment')
+        string(name: 'branchName', defaultValue: 'main', description: 'Branch name (e.g., main, feature/test-utility-script)')
+        choice(name: 'pipelineType', choices: ['build', 'release'], description: 'Pipeline type: build or release')


This is rather the "Package Type", that the user wants to deploy.

Description could be like "Package Type - a preliminary build or release candidate"

dennis-behm · 2025-11-28T15:18:14Z

Templates/Deploy_Pipeline/Jenkins/Jenkinsfile

+                    echo "==============================="
+                    echo "Deployment Pipeline Parameters"
+                    echo "==============================="
+                    echo "[INFO] Application: ${params.application}"


I would re-order this by:

Application, Package Type, Build Id, Target Environment.

Templates/Deploy_Pipeline/Jenkins/Jenkinsfile

dennis-behm · 2025-11-28T15:29:31Z

Templates/Deploy_Pipeline/Jenkins/README.md

+
+This Jenkins pipeline implements the [Git-based process and branching model for mainframe development](https://ibm.github.io/z-devops-acceleration-program/docs/git-branching-model-for-mainframe-dev) and leverages [Common Backend Scripts](https://github.com/IBM/dbb/blob/main/Templates/Common-Backend-Scripts/README.md) along with **IBM Wazi Deploy** to automate deployments of pre-built application packages from an artifact repository into integration, acceptance, and production environments on z/OS.
+
+The pipeline supports **manual or automated triggers** and implements the following stages:


Isn't it just manual?

dennis-behm · 2025-11-28T15:29:55Z

Templates/Deploy_Pipeline/Jenkins/README.md

+* **Validate Parameters**  
+  - Validates pipeline input parameters passed during manual trigger or via API.  
+  - Determines the appropriate environment configuration file based on the selected target environment.  
+  - Ensures required parameters (e.g., `application`, `buildId`, `pipelineType`) are defined.


adjust according to above comments about the parameters

Templates/Deploy_Pipeline/Jenkins/README.md

dennis-behm · 2025-11-28T15:31:39Z

Templates/Deploy_Pipeline/Jenkins/README.md

+| ------------------- | ----------------------------- | ------------------------------------------------------------------------- |
+| `application`       | Yes                           | Application name to deploy.                                                |
+| `buildId`           | Yes                           | Build pipeline ID corresponding to the artifact.                           |
+| `releaseVersion`    | Only for release pipelines    | Release version (e.g., `rel-2.6.0`).                                       |


Please update based on earlier comments.

dennis-behm · 2025-11-28T15:32:33Z

Templates/Deploy_Pipeline/README.md

 This folder contains templates for standalone deployment pipelines.

-Refer to [Deploy_Pipeline/REDME.md](../Deploy_Pipeline/README.md)
+Refer to [Gitlab/REDME.md](./Gitlab/README.md)


Can this be probably rather a list?

Co-authored-by: Dennis Behm <[email protected]>

M-DLB · 2025-12-01T15:37:35Z

I would suggest restructuring the Templates folders. Right now, each CI orchestrator has its own subfolder, and we've introduced the Deploy_Pipeline subfolder, where we also have subfolder per orchestrator.
My suggestion would be to move the deployment pipeline templates into each orchestrator subfolder, into their own sub-sub-folders.

It would look like this:

Templates
-> Jenkins
   -> CICD (this is where the full pipeline with Build & Deploy is located)
   -> CD (The Deploy on pipeline)
-> Azure
   -> CICD (this is where the full pipeline with Build & Deploy is located)
   -> CD (The Deploy on pipeline)

Same for GitHub and GitLab (for both z/OS and distributed runners).

What do you think @dennis-behm @thadbeeraf ?

dennis-behm · 2025-12-02T10:22:09Z

Thanks for the suggestion @M-DLB . I like the idea, and think this is worth to restructure.

thadbeeraf · 2025-12-03T06:03:43Z

Okay, I think we can go ahead with the new structure then.
I'll update the PR with changes.

dennis-behm · 2025-12-08T15:42:29Z

Templates/Deploy_Pipeline/Jenkins/Jenkinsfile

+            }
+        }
+
+        stage('Generate Plan') {


@thadbeeraf - The stages need a when condition to manage scenarios when a previous stage failed.

Today, they just continue to execute.

dennis-behm

@thadbeeraf Thank you for continuing on the template. I have a few comments, please see them below.

dennis-behm · 2025-12-17T10:27:02Z

Templates/Deploy_Pipeline/Jenkins/Jenkinsfile

+                    echo "==============================="
+                    echo "[INFO] Application:        ${application}"
+                    echo "[INFO] Package Type:       ${PackageType}"
+                    echo "[INFO] Build ID:           ${buildId}"


Can we change the order and have Package Reference before the Build ID?

dennis-behm · 2025-12-17T10:28:30Z

Templates/Deploy_Pipeline/Jenkins/Jenkinsfile

+    parameters {
+        string(name: 'application',       defaultValue: '', description: 'Application name')
+        choice(name: 'PackageType',       choices: ['build', 'release'], description: 'Package type')
+        string(name: 'buildId',           defaultValue: '', description: 'Build pipeline ID')


Can we switch the order and have packageReference before the buildId, please?

dennis-behm · 2025-12-17T10:29:12Z

Templates/Deploy_Pipeline/Jenkins/Jenkinsfile

+        deployOutputDirectory = "${WORKSPACE}/${application}/DEPLOY-OUTPUT"
+    }
+
+    parameters {


In a previous version the description of the input parms were more details. Can we please add that back in?

Templates/Deploy_Pipeline/Jenkins/README.md

dennis-behm · 2025-12-17T10:30:59Z

Templates/Deploy_Pipeline/Jenkins/Jenkinsfile

+
+    parameters {
+        string(name: 'application',       defaultValue: '', description: 'Application name')
+        choice(name: 'PackageType',       choices: ['build', 'release'], description: 'Package type')


Please use consistent casing of the variables.

dennis-behm · 2025-12-17T10:35:59Z

Templates/Deploy_Pipeline/Jenkins/Jenkinsfile

+                }
+            }
+
+            post {


Please upload the the deployment-report.html. I don't see this happening when testing the template -

It's generated here:

But the archive step is not there:

I think it needs to use ${uniqueWorkspaceId} instead of ${WORKSPACE}

dennis-behm · 2025-12-17T10:38:27Z

Templates/Deploy_Pipeline/Jenkins/Jenkinsfile

+                    echo "[INFO] Generating deployment report"
+
+                    def evidenceCmd = "wazideploy-evidence.sh -w ${uniqueWorkspaceId} -l ${wdEvidencePath}/evidence.yaml -o deploy/deployment-report.html"
+                    sh evidenceCmd


I would prefer to separate this into two stages:

It's the report of the current deployment (and btw line 152 requires some error handling)

It's storing the the yaml file to the shared evidence folder.

Co-authored-by: Dennis Behm <[email protected]>

Thadbeera Farhath and others added 5 commits November 11, 2025 14:32

Gitlab cd pipeline

4cfe856

Merge branch 'IBM:main' into main

391587d

cleanup

1e4cf8e

standalone deployment pipeline for Jenkins

eb31867

Update README.md

66d806e

dennis-behm reviewed Nov 28, 2025

View reviewed changes

thadbeeraf and others added 3 commits November 30, 2025 23:49

Apply suggestions from code review

7dc4cfe

Co-authored-by: Dennis Behm <[email protected]>

cleanup

a600d2f

cleanup

6b39572

revert the changes

fb62a5e

thadbeeraf force-pushed the feature/CTTM-1508 branch from 8bf6517 to fb62a5e Compare December 3, 2025 11:28

cleanup

db6d0b0

dennis-behm reviewed Dec 8, 2025

View reviewed changes

Thadbeera Farhath added 3 commits December 16, 2025 14:01

corrected jenkinsfile

12456c1

cleanup

2387082

cleanup

5db8f5d

dennis-behm requested changes Dec 17, 2025

View reviewed changes

thadbeeraf and others added 2 commits December 17, 2025 16:56

Update Templates/Deploy_Pipeline/Jenkins/README.md

0ced6de

Co-authored-by: Dennis Behm <[email protected]>

PR changes

3b8007e


		This Jenkins pipeline implements the [Git-based process and branching model for mainframe development](https://ibm.github.io/z-devops-acceleration-program/docs/git-branching-model-for-mainframe-dev) and leverages [Common Backend Scripts](https://github.com/IBM/dbb/blob/main/Templates/Common-Backend-Scripts/README.md) along with IBM Wazi Deploy to automate deployments of pre-built application packages from an artifact repository into integration, acceptance, and production environments on z/OS.

		The pipeline supports manual or automated triggers and implements the following stages:

+                              }
+                          }
+                          post {

standalone deployment pipeline for Jenkins #376

Are you sure you want to change the base?

standalone deployment pipeline for Jenkins #376

Uh oh!

Conversation

thadbeeraf commented Nov 27, 2025

Uh oh!

dennis-behm left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

M-DLB commented Dec 1, 2025

Uh oh!

dennis-behm commented Dec 2, 2025

Uh oh!

thadbeeraf commented Dec 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

dennis-behm left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

thadbeeraf commented Dec 3, 2025 •

edited

Loading