Skip to content

Deploy API to Environment #83

Deploy API to Environment

Deploy API to Environment #83

Manually triggered March 10, 2026 02:37
Status Failure
Total duration 2m 39s
Artifacts 1

publish-api-select.yml

on: workflow_dispatch
Matrix: Build, Create and Push Image
Deploy to ENV
0s
Deploy to ENV
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 10 warnings
Build, Create and Push Image (10, 0)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c dotnet build \"api/api.csproj\" -c Release /p:ReleaseVersion=${RELEASE_VERSION}" did not complete successfully: exit code: 1
Build, Create and Push Image (10, 0)
Process completed with exit code 2.
Build, Create and Push Image (10, 0): api/Models/Dars/TranscriptSearchRequest.cs#L6
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build, Create and Push Image (10, 0): api/Models/Dars/TranscriptSearchRequest.cs#L5
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build, Create and Push Image (10, 0): pcss-client/Clients/PersonServicesClient.cs#L153
The result of the expression is always 'false' since a value of type 'int' is never equal to 'null' of type 'int?'
Build, Create and Push Image (10, 0): cso-client/Models/Order/OrderActionDto.cs#L38
Non-nullable property 'OrderTerms' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build, Create and Push Image (10, 0): cso-client/Models/Order/OrderTerm.cs#L8
Non-nullable property 'TermTxt' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build, Create and Push Image (10, 0): api/Models/Dars/TranscriptSearchRequest.cs#L6
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build, Create and Push Image (10, 0): api/Models/Dars/TranscriptSearchRequest.cs#L5
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build, Create and Push Image (10, 0): pcss-client/Clients/PersonServicesClient.cs#L153
The result of the expression is always 'false' since a value of type 'int' is never equal to 'null' of type 'int?'
Build, Create and Push Image (10, 0): cso-client/Models/Order/OrderActionDto.cs#L38
Non-nullable property 'OrderTerms' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build, Create and Push Image (10, 0): cso-client/Models/Order/OrderTerm.cs#L8
Non-nullable property 'TermTxt' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.

Artifacts

Produced during runtime
Name Size Digest
bcgov~jasper~KVIC6V.dockerbuild
31.4 KB
sha256:c04801d8032bb5e45f426398bf5b44313d0308828be85dfeaf1d1e5c39863e42