feature/DEV-6278-dotnetpipelines

[JakubDziurdziewicz]

Pull Request Template

Description

We created a comprehensive set of reusable Azure DevOps and GitHub Actions templates for standardizing CI/CD pipelines across different technology stacks. The templates include job-level configurations for Python, Frontend (npm/yarn), .NET, and SQL projects, with each template supporting flexible parameterization for project-specific requirements. Key features include package manager support (npm/yarn for frontend), Azure integration capabilities, and deployment script handling, while maintaining backward compatibility with existing pipeline configurations. The templates follow best practices with conditional execution, proper caching mechanisms, and centralized maintenance to reduce duplication and ensure consistency across all projects.

New Features

• DEV-6278

Fixes

N/A

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Dependent Releases

• Dependent Releases ...

Required Configuration on CI/CD platform

Project need to be edited to use templates in pipelines/workflows.

Example project level pipeline that utilize template:

name: Build on master & push to octopus

on:
  workflow_dispatch:
    branches:
      - master
    paths: 
        - "src/**"
  push:
    branches:
      - master
    paths: 
        - "src/**"

jobs:
  build-and-deploy:
    uses: ./.github/workflows/build-and-deploy-to-octopus.yml
    with:
      project_name: ${{ github.event.repository.name }}
      timeout_minutes: 15
      runner: 'self-hosted'
      base_path: './'
      files_pattern: '**/*'
      overwrite_mode: 'OverwriteExisting'
    secrets:
      octopus_url: ${{ secrets.OCTOPUS_URL }}
      octopus_api_key: ${{ secrets.OCTOPUS_API_KEY }}
      octopus_space: ${{ secrets.OCTOPUS_SPACE }} 

How Has This Been Tested?

Testing can be done by creating/comparing artifacts produces by initial pipeline/workflows and new, templated one.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• My changes fulfill the acceptance criteria for the story or bug
• I made/planned the required configuration changes on CI/CD