IBX-11778: Updated GitHub Actions workflows to org standard - #119
Merged
Conversation
- Renamed the CI workflow to Backend CI and added a bare workflow_dispatch trigger (IBX-12062 PoC follow-up, without the Slack notification parts) - Updated actions/checkout to v7 - Standardized runners to ubuntu-26.04 - Dropped non-existent main branch from push triggers - Removed the deprecated pr-assign.yaml workflow - Passed the PHP version to the composer-install action explicitly; the implicit matrix.php fallback inside the action is kept only for backwards compatibility (IBX-11907, gh-workflows#115) - Dropped the redundant standalone setup-php step from the Solr integration tests job, superseded by the action's own PHP setup - Guarded the code style check against masked pipe failures; without pipefail the check-cs exit code was swallowed by the pipe into cs2pr (IBX-11853, bundle-generator#45)
The ubuntu-26.04 runner image ships Java 25, which neither Solr 7.7.3 nor 9.8.1 can start under, failing all eight of their matrix legs in the "Init Solr" step. Set up Temurin 17 explicitly instead, the LTS release supported by every Solr version in the matrix. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Solr 7.7.3 does not start on Java 17 either: its bin/solr passes the CMS garbage collector flags, which JDK 14 removed, so the JVM exits before writing solr.log. Solr 7.7 supports Java 8 and 11 only. Moved java-version into the matrix so 7.7.3 runs on Temurin 11, while 8.11.2 and 9.8.1 stay on 17, where they are already green. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
konradoboza
approved these changes
Sep 9, 2026
mikadamczyk
approved these changes
Sep 9, 2026
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related PRs:
Description:
Part of the fleet-wide GHA workflow standardization (wave 10; sample: ibexa/taxonomy#444). Changes:
Backend CIand added a bareworkflow_dispatchtrigger (IBX-12062, per the admin-ui#1999 PoC — without Slack notification parts).ubuntu-26.04.main/masterbranches from push triggers.pr-assign.yamlworkflow.set -euo pipefailsocheck-csfailures are no longer masked (canonical fix from IBX-11853 / bundle-generator#45).integration-tests.yaml(Solr integration): no PHP matrix, so its composer-install step got a concretephp-version: '7.4'(what its standalone setup-php step used); that now-redundant setup-php step was removed.actions/setup-javabeforeInit Solr. Theubuntu-26.04image ships Java 25 as the default JDK, which Solr 7.7.3 and 9.8.1 do not support, so all 8 of their matrix legs died inInit Solr(run 34035174326):Java 25 detected. Enabled workaround for SOLR-16463...Still not seeing Solr listening on 8983 after 180 seconds.ubuntu-24.04(last green 4.6 run, 2026-05-21) shipped Java 17. Pinning the JDK instead of the runner keeps the standardizedubuntu-26.04in place. 8.11.2 was green on Java 25 already, 17 is closer to what that version officially supports anyway.For QA:
Verify CI is green. Backend CI can now also be run manually via workflow dispatch.
Documentation:
No documentation required.
🤖 Generated with Claude Code