CI/CD Stages

Scope
  • Define the stages for CI/CD Pipelines and criteria’s for each stage
  • Common Templates to be used for implementation
  • Compliance checks to be done in tribes
CI/CD Pipeline Architecture

在这里插入图片描述

CI/CD Stages
Sequence #StageNaming ConventionDescriptionStage Gate CriteriaTools Used
1RequirementreqCheck if all requirements are documented
Epic and User story created in JIRA
JIRA User story linked with Infrastructure requirement, GitLab standards, Coding Standards, Security Standards
Check if all requirements are fulfilled
Epic and User story Mapping
Jira
VersionOne
Jama
Trello
Azure DevOps
2DesigndesignDesign documents are in place according to requirements
Repository structure defined
Traceability established by having required IDs for Test suites
JIRA User story should have Links to validate stages:
GitLab Repository
Unit Test Suite ID
Integration Test Suite ID
Performance Test Suite ID
Smoke Test Suit ID
Confluence Docs
Sharepoint
3CodecodeEvery Check-In should have JIRA User story or Defect or incident ID
Version Management as per guidelines
Branching strategy as per guidelines
Artifacts checked in and compiled successfully
Version Management Check for increment
Link to JIRA User story or Defect or incident
GitLab
AWS codeCommit
GitHub
Azure DevOps
HelixTeamHub
IBM gitRepository
ClearCase
4Code Reviewcode-reviewManual Code review is done
Automated code review done using tools
Defects are reported in JIRA and closed
Defined the exit criteria for Code Quality
Defect Reported > 0
Open Defect = 0 (Each tribe to customize as per Quality guidelines)
Resource Tagging done for AWS infrastructure components
Manual Code review
Blackduck
SonarQube
SCA
Checkmarx OSA
5Unit Testunit-testManual Test Scripts Run
Automated Test Scripts Run
Pass rate for Non-Critical Test Cases> 90% for
Pass Rate for Critical Test Cases = 100%
6Security - SASTsast-scanIDE using SAST tool integration
Run on Dev environment if not integrated in IDE
Open Critical and High Priority Defects = 0 (Refer Latest Security guidelines)SonarQube
Blackduck
Coverity
Synopsys
Internal Tools
Checkmarx
7BuildbuildBuilds are complied successfully
Artifacts used should be in central repos
Artifacts checked in and compiled successfully
IaC Checks
GitLab
Jenkins
AWS CloudFormation
AWS-CDK
Cloudfoundry
AWS CodeBuild
Azure DevOps
AWS Artifactory
jfrog
IBM-CCD
8DeploydeployDeploy code on different Environments based on Variable
DEV/QA/PRE-PROD/PROD
Full/partial Deployments
Deployment with 0 Errors
Compliance with Infrastructure code
AWS CloudFormation
AWS-CDK
Cloudfoundry
9E2E Teste2e-testManual Test Scripts Run
Automated Test Scripts Run
DEV/QA/PRE-PROD
Open Critical and High Priority Defects = 0
Pass rate for Non-Critical Test Cases> 90% for
Pass Rate for Critical Test Cases = 100%
Jenkins
Robotic framework
Robot framework
squish framework
postman for API
jmeter
10Smoke Testsmoke-testOnly Automation to be supported
QA/PRE-PROD/PROD
Automated Test Scripts Run and pass rate = 100% Test Cases
11Performance Testperf-testOnly Automation to be supported
Only on PRE-PROD
Performance Test Pass rate = 100%jmeter
12Security - DASTdast-scanManual Review and ApprovalReport reviewed and approved by Tech Architect or Security ArchitectQualys WAS
OWASP ZAP
Burp Suite
IrisRisk
Qualys Vulnerability
NMAP
BitSight
Defensics
13MonitoringmonitorSet Up monitoring and hand over to monitoring teamsMonitoring is setup and Reports are workingKiTOC
Splunk
Cloudwatch
Google Analytics
Guard Duty
Security Hub
Trusted Advisor
Common Template
  • Master Template with all stages defined with exist criteria
  • Child pipelines implementing hooks for tools
Implementation Guidelines
  • Implement the master template
  • Implement child templates as per customization required in Tribes
Compliance Checks
  • GitLab Repository will be scanned every month against the pipeline runs for all SRD project
  • Report will be created fir each Tribe and application comparing against common standard pipelines
  • Refer this page for details - CI/CD Pipeline Compliance
CI/CD Pipeline Compliance
TribeProjectreqdesigncodecode-reviewunit-testsast-scandev-buildint-testqa-deployqa-teststage-deployqa-smoke-teststage-testperf-testprod-deployprod-smoke-testdast-scanmonitor
  • 17
    点赞
  • 6
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器学习模型机器
要使用GitLab的CI/CD功能,你可以按照以下步骤进行操作: 1. 首先,确保你已经安装了GitLab Runner。你可以使用以下命令来安装GitLab Runner: ``` curl -L https://packages.gitlab.com/install/repositories/runner/gitlab-ci-multi-runner/script.rpm.sh | sudo bash sudo yum install gitlab-runner ``` 如果你在Ubuntu系统上使用,请使用`apt-get`命令来安装。 2. 安装完成后,你可以使用`gitlab-runner -v`命令来验证安装是否成功,并查看GitLab Runner的版本号。 3. 接下来,你需要将GitLab Runner注册到GitLab CI/CD Coordinator上。在终端中输入以下命令: ``` gitlab-runner register ``` 在提示中,你需要提供GitLab CI/CD Coordinator的URL(例如https://gitlab.com/),以及访问权限验证的Token。 4. 注册成功后,你可以配置`.gitlab-ci.yml`文件来定义CI/CD的流程。这个文件包含了一系列的任务(jobs)和阶段(stages),你可以根据自己的项目需求进行配置。具体的语法和配置参考可以在GitLab官方文档中找到。 5. 当你的代码提交到GitLab仓库时,GitLab CI/CD会自动触发流水线(pipeline)的执行。流水线中的任务会按照`.gitlab-ci.yml`文件中定义的顺序和规则进行执行。 总结:要使用GitLab的CI/CD功能,你需要先安装GitLab Runner,并将其注册到GitLab CI/CD Coordinator上。然后,在项目中配置`.gitlab-ci.yml`文件来定义CI/CD流程。最后,当代码提交到GitLab仓库时,GitLab CI/CD会自动执行流水线中的任务。详细的使用方法和配置参考可以查阅GitLab官方文档。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值