-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
bugSomething isn't workingSomething isn't workingenhancementNew feature or requestNew feature or request
Description
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:
However, there is one drawback: According to the docs, this only works with Ubuntu (linux) runners.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingenhancementNew feature or requestNew feature or request