Skip to content

Use service containers for test databases #30

@dennisvang

Description

@dennisvang

The maven-verify workflow currently uses third-party actions to set up postgres etc.

For example:

uses: ikalnytskyi/action-setup-postgres@v7

At the moment, this postgres action is causing failure in the FDP repo:

Details


Run ikalnytskyi/action-setup-postgres@v7
Run if [[ ! "17" =~ ^(14|15|16|17)$ ]]; then
Chocolatey v2.5.1
Installing the following packages:
postgresql17
By installing, you accept licenses for the packages.
Failed to fetch results from V2 feed at 'https://community.chocolatey.org/api/v2/Packages(Id='postgresql17',Version='17.6.0')' with following message : Response status code does not indicate success: 504 (Gateway Time-out).
Need to add specific handling for exception type NuGetResolverInputException
Unable to find package 'postgresql17'. Existing packages must be restored before performing an install or update.

Chocolatey installed 0/0 packages. 
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
D:\a\_temp\1b21f7ee-60ca-4499-a194-c72583b97a14.sh: line 33: C:\Program Files/PostgreSQL/17/bin/pg_config.exe: No such file or directory
Error: Process completed with exit code 127.

We should replace these actions by service containers:

https://docs.github.com/en/actions/tutorials/use-containerized-services/create-postgresql-service-containers

However, there is one drawback: According to the docs, this only works with Ubuntu (linux) runners.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingenhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions