Route WildFly archives through MASS

[bric3]

What Does This Do

When MASS_READ_URL is present, the WildFly smoke-test Ivy repositories resolve the server ZIP through MASS at /internal/artifact/github.com/wildfly/wildfly/releases/download/. Without that environment variable, local builds keep using the original GitHub release URL.

Motivation

CI should send build-time archive downloads through MASS when the upstream host is already allowed. WildFly release assets come from github.com, which is already covered by the MASS egress allow-list.

Additional Notes

Contributor Checklist

• Format the title according to the contribution guidelines.
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels.
• Avoid using linking keywords when referencing an issue.
• Update CODEOWNERS on source file addition, migration, or deletion. Not applicable.
• Update public documentation with any new configuration flags or behaviors. Not applicable.

Jira ticket: APMLP-1405, [APMLP-1402]

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	13.90 s	14.07 s	[-2.3%; +0.0%] (no difference)
startup:insecure-bank:tracing:Agent	12.79 s	13.00 s	[-2.5%; -0.8%] (maybe better)
startup:petclinic:appsec:Agent	16.42 s	15.49 s	[-2.8%; +14.8%] (unstable)
startup:petclinic:iast:Agent	16.52 s	16.46 s	[-1.2%; +1.9%] (no difference)
startup:petclinic:profiling:Agent	16.36 s	16.47 s	[-2.2%; +0.9%] (no difference)
startup:petclinic:tracing:Agent	14.94 s	15.11 s	[-12.9%; +10.7%] (unstable)

Commit: 8bacee91 · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

[bric3]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-06-04 17:11:08 UTC ℹ️ Start processing command /merge

---

2026-06-04 17:11:18 UTC ℹ️ MergeQueue: waiting for PR to be ready

This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
It will be added to the queue as soon as checks pass and/or get approvals. View in MergeQueue UI.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

---

2026-06-04 17:16:12 UTC ℹ️ MergeQueue: merge request added to the queue

The expected merge time in master is approximately 1h (p90).

---

2026-06-04 18:34:43 UTC ℹ️ MergeQueue: This merge request was merged