build: remove useless pipelines OH-67 (#201)

* build: remove useless pipeline files OH-67 * build: sonarcloud configuration exclude pipelines -folder * chore: pipeline info to readme
City-of-Helsinki · Mar 18, 2024 · b4c1969 · b4c1969
1 parent e0a80a0
commit b4c1969
Show file tree

Hide file tree

Showing 8 changed files with 26 additions and 321 deletions.
diff --git a/README.md b/README.md
@@ -146,12 +146,36 @@ pre-commit run --all-files
 
 ## Commit message format
 
-New commit messages must adhere to the [Conventional Commits](https://www.conventionalcommits.org/)
+!!!Note New commit messages must adhere to the [Conventional Commits](https://www.conventionalcommits.org/)
 specification, and line length is limited to 72 characters.
 
 When [`pre-commit`](https://pre-commit.com/) is in use, [`commitlint`](https://github.com/conventional-changelog/commitlint)
 checks new commit messages for the correct format.
 
+## Release
+
+### Publish to Dev environment
+
+#### Review environment
+
+New commit to PR will trigger review pipeline. Review pipeline builds application and deploys a dynamic environment to the Openshift dev. The review environment can be used to verify PR.
+
+#### Dev environment
+
+Deployment to dev environment is handled automatically from master branch. Updates to master branch triggers
+azure pipeline that will run tests, build and deploy to dev environment hosted by red hat openshift.
+Currently azure-pipeline is configured directly from version control, but red hat openshift configuration resides in openshift cluster.
+
+### Release to Test, Stage and Production environments
+
+Release is done by [release-please](https://helsinkisolutionoffice.atlassian.net/wiki/spaces/DD/pages/8278966368/Releases+with+release-please).
+It creates release PR based on commits messages. Merge of the PR will trigger a release pipeline that build and deploys to stage and test environments automatically.
+
+Release-please update the package.json version number automatically and it is included to release PR.
+
+#### Publish to production environments
+Publishing to production requires manual approval in the DevOps release pipeline.
+
 ## Importing data
 
 Currently, importing *resources* from Helsinki metropolitan area unit registry (TPREK) is supported. Import all resources from [TPREK API](https://www.hel.fi/palvelukarttaws/restpages/ver4.html) by

diff --git a/azure-pipelines-devtest.yml b/azure-pipelines-devtest.yml
diff --git a/azure-pipelines-master.yml b/azure-pipelines-master.yml
diff --git a/azure-pipelines-pull-request.yml b/azure-pipelines-pull-request.yml
diff --git a/azure-pipelines-release.yml b/azure-pipelines-release.yml
diff --git a/azure-pipelines-stageprod.yml b/azure-pipelines-stageprod.yml
diff --git a/azure-pipelines.yml b/azure-pipelines.yml
diff --git a/sonar-project.properties b/sonar-project.properties
@@ -3,4 +3,4 @@ sonar.organization=city-of-helsinki
 sonar.python.version=3.9
 sonar.python.coverage.reportPaths=coverage.xml
 sonar.test.inclusions=**/tests/**/*
-sonar.exclusions=**/tests/**/*,**/migrations/*,commitlint.config.js,**/load-tests/**/*
+sonar.exclusions=**/tests/**/*,**/migrations/*,commitlint.config.js,**/load-tests/**/*,pipelines/**