Skip to content

Use PostgreSQL with Nexus instead of In-Memory H2 #3368

Use PostgreSQL with Nexus instead of In-Memory H2

Use PostgreSQL with Nexus instead of In-Memory H2 #3368

Triggered via pull request December 16, 2025 12:17
Status Success
Total duration 3m 56s
Artifacts 1

test_code.yaml

on: pull_request
test_python
3m 52s
test_python
test_markdown_links
13s
test_markdown_links
Fit to window
Zoom out
Zoom in

Annotations

10 notices
test_python
Cannot post comment. This is probably because this is an external PR, so it's expected. Ensure you have an additional `workflow_run` step configured as explained in the documentation (or alternatively, give up on PR comments for external PRs).
test_python
HTTP Request: PATCH https://api.github.com/repos/alan-turing-institute/data-safe-haven/issues/comments/3656498334 "HTTP/1.1 403 Forbidden"
test_python
Update previous comment
test_python
HTTP Request: GET https://api.github.com/repos/alan-turing-institute/data-safe-haven/issues/2509/comments "HTTP/1.1 200 OK"
test_python
HTTP Request: GET https://api.github.com/user "HTTP/1.1 403 Forbidden"
test_python
HTTP Request: GET https://api.github.com/repos/alan-turing-institute/data-safe-haven/contents/data.json?ref=python-coverage-comment-action-data "HTTP/1.1 200 OK"
test_python
HTTP Request: GET https://api.github.com/repos/alan-turing-institute/data-safe-haven/pulls/2509 "HTTP/1.1 200 OK"
test_python
Generating comment for PR
test_python
HTTP Request: GET https://api.github.com/repos/alan-turing-institute/data-safe-haven "HTTP/1.1 200 OK"
test_python
Starting action

Artifacts

Produced during runtime
Name Size Digest
python-coverage-comment-action
3.17 KB
sha256:3ff295e924c87d3f6476b42b4b195722bad05f10bddd141f181b5d6f5daf48c9