29 lines
1.7 KiB
Markdown
29 lines
1.7 KiB
Markdown
# Engineering Portal
|
|
|
|
This space is for the engineering team to share knowledge, resources, and best practices.
|
|
|
|
## Sructure of the repository
|
|
|
|
We are trying to keep the repositories small and structured. The following overview shows the general structure and the most important repositories.
|
|
|
|
|
|
|
|
### Documentation repositories
|
|
|
|
The documentation repositories should help to find best know how, practices and guidelines. No matter if you are new to the team or if you have been working in an different area in the past, you should be able to find the information you need.
|
|
|
|
- [docs-onboarding](https://xwr.visualstudio.com/jambor.pro/_git/docs-onboarding): the current repository you are reading. It should contain all information needed to get started.
|
|
|
|
- [docs-agile-working](https://xwr.visualstudio.com/jambor.pro/_git/docs-agile-working): information about how we work with Azure Borads in the team and how we use the agile methodology.
|
|
|
|
### Infrastructure repositories
|
|
|
|
The infrastructure repositories should contain all information about the infrastructure we are using and it's configuration.
|
|
|
|
- [infra-terraform-modulelibrary](https://xwr.visualstudio.com/jambor.pro/_git/infra-terraform-modulelibrary): We are maintaining Terraform modules which should ensure constant quality and improvement.
|
|
|
|
### CI/CD repositories
|
|
|
|
The CI/CD repositories should contain all information about the CI/CD pipelines we are using.
|
|
|
|
- [cicd-pipeline-library](https://xwr.visualstudio.com/jambor.pro/_git/cicd-pipeline-library): We are maintaining Azure DevOps Pipeline templates which should ensure constant quality and improvement.
|