Bump com.avast.gradle:gradle-docker-compose-plugin from 0.14.5 to 0.17.4

[dependabot]

Bumps com.avast.gradle:gradle-docker-compose-plugin from 0.14.5 to 0.17.4.

Release notes

Sourced from com.avast.gradle:gradle-docker-compose-plugin's releases.

0.17.4

Ensure the -f parameters go right after docker compose.

0.17.3

Revert of a change introduced in 0.17.0 that introduced stderr reading when executing docker command. It leads to an unexpected output if Docker is not fully correctly installed and prints warnings to stderr (while stdout is valid).

0.17.2

Safer JSON parsing of docker compose ps output.

0.17.1

Update to Gradle v8.

0.17.0

• Migrated to the latest Gradle 7.x
• As Docker Compose V1 is deprecated, default value of useDockerComposeV2 property was changed from false to true, so docker compose is used by default (instead of docker-compose).
• More version formats handled in the VersionNumber.parse method.
• Durations stripped from cache key.

useDockerComposeV2 introduced

No release notes provided.

Gradle 8 compatibility

Usage of deprecated internal VersionNumber class removed #399

0.16.11

Project name lowercased #386

0.16.10

Performance optimization #382

0.16.9

The level of a log message changed from lifecycle to info.

setProjectName accepts null to fallback to Docker default

No release notes provided.

setProjectName accepts null or empty value to reset to default

No release notes provided.

New Gradle Publish plugin used

No release notes provided.

MacOS-specific defaults for executable and dockerExecutable removed

The defaults used to be /usr/local/bin/docker-compose and /usr/local/bin/docker, now it is just plain docker-compose and docker (for all platforms).

isRequiredBy changed in order not to break configuration avoidance

This release changes the behavior of isRequiredBy so the Up tasks should be executed as the last dependency of the configured task. Till now, we have this optimization for classes tasks only.

As reported in #352

... (truncated)

Commits

• 101f4ce fix: -f always comes directly after docker compose Fixes #414
• 1c4d194 fix: stderr of executed docker command ignored again
• 129275f fix: safer JSON parsing for cache key
• c01c75c chore: safer closure call for nested settings
• 8912074 chore: Gradle deprecations warnings handled
• ae4742c chore: unused import removed
• ea8f5e1 chore: Gradle updated to v8
• 178316b conf: useDockerComposeV2 defaults to true (#412)
• 20b1700 chore: Gradle updated to v7 (#411)
• 1615aee fix: more version format handled, fixes #407
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[Mex7180]

Hi, is this still an issue which has to be solved? If yes, the problem for the failure may be in the siren-rest-api build.gradle file. The function dockerCompose sets the property of removeImages to a String, but it should be com.avast.gradle.dockercompose.RemoveImages.None because RemoveImages is an enum.
Greetings

[JohannesLichtenberger]

Can you make a PR with your fix and the new plugin version? Furthermore, I think in the longer run maybe TestContainers is the better approach...

[Mex7180]

I'll look into it this weekend or next week. Thank you.

[dependabot]

Superseded by #659.