You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+40-30Lines changed: 40 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,17 @@
1
-
# app-devops-gitlab-docker
1
+
# app-devops-gitlab
2
2
3
3
New repository for developing a plugin to integrate between ITSM DevOps and GitLab pipelines
4
4
5
+
### Owners
6
+
7
+
> ramachandrarao.p
8
+
9
+
### How to build on Jenkins
10
+
* Create a `pom.xml` file at the root level
11
+
* Go to the [BT1 Service Catalog](https://buildtools1.service-now.com/nav_to.do?uri=%2Fcom.glideapp.servicecatalog_cat_item_view.do%3Fv%3D1%26sysparm_id%3D9dbd0c54db1acb403a3d5dd5ce961948%26sysparm_link_parent%3Dad2fecb72bfc310052f7c71317da157e%26sysparm_catalog%3De0d08b13c3330100c8b837659bba8fb4%26sysparm_catalog_view%3Dess%26sysparm_view%3Dess) to request a Jenkins job
12
+
13
+
Once the request is processed, a multi-branch job is created on https://buildmaster-hotel.devsnc.com and will build any branches that match [ServiceNow branch naming convention](https://buildtools1.service-now.com/kb_view_customer.do?sysparm_article=KB0528607).
- sndevopscli create change -p '{"changeStepDetails":{"timeout":3600,"interval":100},"attributes":{"short_description":"Automated Software Deployment","description":"Automated Software Deployment.","assignment_group":"XXXXXXX","implementation_plan":"Software update is tested and results can be found in Test Summaries Tab.","backout_plan":"When software fails in production, the previous software release will be re-deployed.","test_plan":"Testing if the software was successfully deployed or not"}}'
This specifies the branch on which the Sonar scan was executed. By default, it matches the branch for which the build was run. Note, for Harness, the branch option is required if CI_COMMIT_BRANCH is not provided.
205
+
This specifies the branch on which the Sonar scan was executed. By default, it matches the branch for which the build was run. Note, for Harness, the branch option is required if COMMIT_BRANCH is not provided.
It the payload of security result attributes. The payload will have attributes as follows:
216
-
buildNumber: CI_PIPELINE_ID (mandatory)
217
-
pipelineExecutionUrl: CI_PIPELINE_URL (mandatory)
226
+
buildNumber: This specifies ID of the Job (mandatory)
227
+
pipelineExecutionUrl: This specifies the pipeline execution URL (mandatory)
218
228
scanner: Scanning tool and is required e.g. Checkmarx One.
219
229
projectName/projectId: Name/Id of your Checkmarx One project and is required. This attribute is applicable only for Checkmarx One.
220
230
applicationName: Name of your Veracode application and is required. This attribute is applicable only for Veracode.
@@ -234,11 +244,11 @@ stages:
234
244
235
245
ServiceNow DevOps Get Change:
236
246
stage: DevOpsGetChange
237
-
image: servicenowdocker/sndevops:5.1.0
247
+
image: servicenowdocker/sndevops:6.0.0
238
248
script:
239
-
- sndevopscli get change -p "{\"buildNumber\":${CHG_JOB_ID},\"stageName\":\"ServiceNow DevOps Change Step\",\"pipelineName\":\"GitlabDockerGetAndUpdateChange\"}"
249
+
- sndevopscli get change -p "{\"buildNumber\":\"buildNumber\",\"stageName\":\"ServiceNow DevOps Change Step\",\"pipelineName\":\"GitlabDockerGetAndUpdateChange\"}"
240
250
241
-
-p: It stands for changeDetails. The change details to be used for identifying change request in ServiceNow instance. The change details is a JSON object surrounded by curly braces {} containing key-value pair separated by a comma ,. A key-value pair consists of a key and a value separated by a colon :. The keys supported in key-value pair are buildNumber, pipelineName, stageName
251
+
-p: It stands for changeDetails. The change details to be used for identifying change request in ServiceNow instance. The change details is a JSON object surrounded by curly braces {} containing key-value pair separated by a comma ,. A key-value pair consists of a key and a value separated by a colon :. The keys supported in key-value pair are buildNumber, pipelineName, stageName. All fields in the Change Request table are supported except risk, impact and risk_impact_analysis. For more information, [see documentation](https://docs.servicenow.com/bundle/vancouver-it-service-management/page/product/enterprise-dev-ops/concept/dev-ops-config-change-details.html).
242
252
243
253
buildNumber: [mandatory]
244
254
This specifies ID of the Job where we have created change request.
@@ -270,7 +280,7 @@ stages:
270
280
271
281
ServiceNow DevOps Update Change:
272
282
stage: DevOpsUpdateChangeStage
273
-
image: servicenowdocker/sndevops:5.1.0
283
+
image: servicenowdocker/sndevops:6.0.0
274
284
script:
275
285
- sndevopscli update change -n 'CHGXXXXXX' -p "{\"short_description\":\"Automated Software Deployment\",\"description\":\"Automated Software Deployment.\",\"assignment_group\":\"XXXXX\",\"implementation_plan\":\"Software update is tested and results can be found in Test Summaries Tab.\",\"backout_plan\":\"When software fails in production, the previous software release will be re-deployed.\",\"test_plan\":\"Testing if the software was successfully deployed or not\"}"
276
286
@@ -297,7 +307,7 @@ stages:
297
307
298
308
ServiceNow DevOps Change Step:
299
309
stage: changeapproval
300
-
image: servicenowdocker/sndevops:5.1.0
310
+
image: servicenowdocker/sndevops:6.0.0
301
311
script:
302
312
- sndevopscli create change -p "{\"changeStepDetails\":{\"timeout\":3600,\"interval\":100},\"autoCloseChange\":true,\"attributes\":{\"short_description\":\"Automated Software Deployment\",\"description\":\"Automated Software Deployment.\",\"assignment_group\":\"xxxxxxxx\",\"implementation_plan\":\"Software update is tested and results can be found in Test Summaries Tab.\",\"backout_plan\":\"When software fails in production, the previous software release will be re-deployed.\",\"test_plan\":\"Testing if the software was successfully deployed or not\"}}"
0 commit comments