Skip to content
CI

Spike: Can we serve content directly from Publishing API? #917

Sign in to view logs

Spike: Can we serve content directly from Publishing API?

Spike: Can we serve content directly from Publishing API? #917

Triggered via pull request January 15, 2024 11:55
@aldavidsonaldavidson
synchronize #2602
spike-serve-content-directly
Status Failure
Total duration 2m 49s
Artifacts 3

ci.yml

on: pull_request
Test Ruby
1m 39s
Test Ruby
SNYK security analysis  /  sast
11s
SNYK security analysis / sast
SNYK security analysis  /  sca
10s
SNYK security analysis / sca
CodeQL SAST scan  /  Analyze
58s
CodeQL SAST scan / Analyze
Dependency Review scan  /  dependency-review-pr
4s
Dependency Review scan / dependency-review-pr
Dependency Review scan  /  dependency-review-push
0s
Dependency Review scan / dependency-review-push
Security Analysis  /  Run Brakeman
17s
Security Analysis / Run Brakeman
Lint Ruby  /  Run RuboCop
15s
Lint Ruby / Run RuboCop
Run GDS API Adapter Pact tests  /  Verify pact tests
53s
Run GDS API Adapter Pact tests / Verify pact tests
Check content schemas are built
2m 0s
Check content schemas are built
Run Content Store Pact tests  /  Verify pact tests
41s
Run Content Store Pact tests / Verify pact tests
publish-pacts
0s
publish-pacts
Delete Pact artifact
3s
Delete Pact artifact
Fit to window
Zoom out
Zoom in

Annotations

3 errors
SNYK security analysis / sast
Process completed with exit code 2.
SNYK security analysis / sca
Process completed with exit code 2.
Delete Pact artifact
HttpError: Resource not accessible by integration

Artifacts

Produced during runtime
Name Size
pacts Expired
1.15 KB
snyk-sast-file Expired
487 Bytes
snyk-sca-file Expired
244 Bytes