IBX-12374: Used PHP Behat configuration as behat.php when the edition ships one - #147
Merged
Merged
Conversation
…145) * Used the PHP Behat configuration as behat.php when the edition ships one * Fixed missing semicolon before then in the valkey branch of the 6.0 prepare script * [TEMP] Listed Behat configuration files after copying * Removed recipe-provided Behat configuration files before creating behat.php * Fixed missing semicolon before then in the valkey branch of the stable prepare script * Relied on the ibexabehat default configuration instead of removing recipe files (cherry picked from commit f00b423)
|
ibexa-workflow-automation-1
Bot
requested review from
KamilSznajdrowicz,
juskora,
katarzynazawada,
micszo,
pawlakadrian and
tomaszszopinski
and removed request for
a team
September 9, 2026 07:20
barbaragr
requested review from
a team and
ibexa-yuna
and removed request for
KamilSznajdrowicz,
juskora,
katarzynazawada,
micszo,
pawlakadrian and
tomaszszopinski
September 9, 2026 07:20
ibexa-workflow-automation-1
Bot
requested review from
KamilSznajdrowicz,
juskora,
katarzynazawada,
micszo,
pawlakadrian and
tomaszszopinski
and removed request for
a team
September 9, 2026 07:20
ViniTou
approved these changes
Sep 9, 2026
KamilSznajdrowicz
approved these changes
Sep 9, 2026
micszo
approved these changes
Sep 9, 2026
ibexa-yuna
approved these changes
Sep 9, 2026
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
5 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.
Description:
Sync of the YAML→PHP Behat configuration migration from
mainontok8s-satis: cherry-pick of #145 (f00b423d). Bothprepare_project_edition.shvariants now copybehat_ibexa_<edition>.phptobehat.phpwhen the edition ships one, falling back tobehat.yamlotherwise.This is the sibling of ibexa/gh-workflows#116, which cherry-picks the same migration onto the
k8s-satisbranch of the workflows repository. That PR covers the multirepository setup steps; this one covers the project setup step that runs before them, so both are needed for browser jobs pinned tok8s-satis.Without it, every regression using
ci-scripts-branch: "k8s-satis"fails inSet up whole project using the tested dependency (dev version)now that ibexa/recipes-dev#262 stopped copying the YAML files out of theibexa/behat6.0 recipe:Observed on https://github.com/ibexa/commerce/actions/runs/34150225832 — the same four jobs were green on 07.09 and failed 4/4 on re-run on 09.09, 22 minutes after #262 was merged.
The cherry-pick applied cleanly and carries the
elif [[ ... ]] then→elif [[ ... ]]; thensyntax fix from the original commit. The twok8s-satis-only commits (43ebb2a6private Satis server,befda8d4composer dump ordering) are untouched.bash -npasses on both scripts.For QA:
Browser jobs pinned to
k8s-satismust get past the project setup step on 6.0 (Behat 4, PHP configuration) and stay green on 5.0/4.x (Behat 3, YAML configuration) via the fallback.Documentation:
N/A