Files
id_configurator/tests/configs/Java.yaml.j2

48 lines
1.7 KiB
Django/Jinja

uuid: 6a1d4e2c-9f3b-4a5d-8c7e-2b1f9a6d4c3e
organisation: InterDiode
description: Java test configuration
configurations:
certificates:
- name: Test CA
content: |
{{ 'certs/test-ca.crt.pem' | file | indent(6, first=true) }}
apt:
sources: []
apk:
repositories: []
yum:
repositories: []
keys: []
python:
repositories: []
java:
repositories:
# First entry: named "central" so Maven's mirrorOf=* (built on
# repositories[0]) redirects everything here without invalidating the
# maven-dependency-plugin already cached under that repository id
# during the Dockerfile's warm-up step. All other tools just see it as
# an ordinary repository, and find the test artifact here.
- name: central
{% set scheme = 'JAVA_REPO_SCHEME' | env %}
url: {{ scheme }}://host.docker.internal:{{ ('JAVA_REPO_PORT' if scheme == 'https' else 'JAVA_REPO_HTTP_PORT') | env }}/
# Second entry: only SBT needs this. With
# -Dsbt.override.build.repos=true (the only way SBT actually consults
# this file for project dependencies, not just its own bootstrap), the
# repositories listed here become the *only* ones available - without a
# real Maven Central mirror among them, SBT can't resolve scala-library
# itself. Maven ignores it (mirrorOf=* already redirects everything to
# the first entry); Gradle/Ivy/Leiningen just see one more unused
# resolver, since the test artifact is already found via "central".
- name: maven-central-fallback
url: https://repo1.maven.org/maven2/
npm:
repositories: []
rust:
repositories: []
go:
repositories: []
ruby:
repositories: []
nuget:
repositories: []