AJR/TechradarDev
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

update conventional commits

Browse Source
This commit is contained in:
Tolleiv Nietsch
2022-04-22 15:06:46 +02:00
committed by resah
parent b3ff93a0a9
commit bf279685b7
2 changed files with 10 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
radar/2017-03-01/pipeline-as-code.md
View File

@@ -1,8 +1,4 @@
---
title: "Pipeline as Code"
ring: assess
quadrant: methods-and-patterns
---
con
Continuous Integration and Delivery is a critical part of our development and deployment process at AOE. Using Jenkins for many years the "instructions" how to build, test and deploy applications were scattered between many custom scripts and the pipeline was often maintained by manual maintenance of Jenkins jobs. Soon, we realized that we need a more native way to express the full CI/CD pipeline process in code and manage it in version control.

9
radar/2022-03-28/conventionalcommits.md Normal file
View File

@@ -0,0 +1,9 @@
---
title: "Conventional Commits"
ring: adopt
quadrant: methods-and-patterns
---
Conventional commits are being widely used in our teams, therefore we're changing this to adopt. Using commit messages which follow the [conventional commits specification](https://www.conventionalcommits.org/en/v1.0.0/) helps us to easily process changes made within a software release. It also helps to reduce confusion around commit message requirements for new team members.
The [Semanticore](https://github.com/AOEpeople/semanticore) release bot is a tool we published, which utilizes conventional commits to maintain the release notes of our software and suggests the correct version of the upcoming release.