Azure DevOps Pipeline Setup

I need a complete Azure DevOps CI/CD workflow that builds and deploys our entire solution from a single repo. Proposals. Please start your proposal with the word "OUAzure" so we know you have read everything, else your proposal wont even be read. I know the time needed so the price are really important. Build pipeline • Source contains 3 C# libraries (Fortnox, BL, Shared), 2 ASP .NET sites (Auth, API), 1 Windows Service, 3 React front-ends and an SSDT database project. • A pull request into the develop branch must automatically compile everything, publish artefacts and then trigger the Test deployment. We are not adding SonarQube or NUnit at this stage, so the default Azure DevOps tasks are enough. Release pipeline • Two stages today: Test (automatic from develop) and Prod (manual approval). Later we will add a UAT stage for release branches, so leave the YAML ready for an easy insert. • Deploy the two web sites and the three React apps to IIS. Each web site (not the reactsites) must be created with its own AppPool that runs under our dedicated service account so Integrated Windows authentication continues to work. • Deploy the Windows Service via a standard service installation step. • Publish the SSDT database project to SQL Server 2019 using the existing [login to view URL] profile to control drift and permissions. Infrastructure hooks • The pipeline will push to three on-prem servers: – testSQL (SQL only) – testIIS (IIS only) – prod (combined SQL + IIS) I have no Puppet or Chef in place, so please install manually the code (From Azure you need for those machines so the release pipeline can reach them. Secrets & configuration A new Azure Key Vault must be created and wired into the pipelines; the service-account password and any connection strings should be fetched directly from the vault at deploy time. Deliverables 1. YAML (or classic pipeline JSON) files for both Build and Release, committed back to the repo. 2. Configured self-hosted agents / deployment targets on the three servers. 3. Key Vault set-up script and sample secret import. 4. A short read-me explaining how to add the upcoming UAT stage and how to rotate secrets. Acceptance I will consider the job complete when a pull request to develop automatically deploys a functioning build to the Test servers, and a manual promotion publishes the very same artefacts to Prod with zero manual tweaks.

Projektin tunnus (ID): 40234952