Skip to content
This repository was archived by the owner on Nov 16, 2023. It is now read-only.

Add link to walkthrough pipeline creation #83

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add link to walkthrough pipeline creation #83

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion docs/buildAndReleasePipelines.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,4 +40,9 @@ The release pipeline for the API was built with Azure Dev Ops, under `Pipelines`

## Client Release Pipeline

Like the build pipeline, the release pipeline for the UI is almost identical to the API release pipeline, with key differences being that only the `pj-client` App Service is deployed to and that the docker image being pulled from ACR is from the `pj-client` repository. Only a single environment variable is defined in `Application settings` and it is named `WEBSITES_PORT` with a value of `8080`. In a similar fashion to the API, when there is a build on the master branch of the UI repository, a new release deployment is kicked off.
Like the build pipeline, the release pipeline for the UI is almost identical to the API release pipeline, with key differences being that only the `pj-client` App Service is deployed to and that the docker image being pulled from ACR is from the `pj-client` repository. Only a single environment variable is defined in `Application settings` and it is named `WEBSITES_PORT` with a value of `8080`. In a similar fashion to the API, when there is a build on the master branch of the UI repository, a new release deployment is kicked off.


### Walkthrough

A walkthrough release pipeline video can be found [here](https://msit.microsoftstream.com/video/9dab7948-d167-4ec1-b210-bc07f81a1d25).