Add a CI job running with a 32bits build of PHP #12366
Conversation
|
I'm a little unsure if this is justified, that'll spend a lot of cpu cycles for a one-off issue with 32bit which is really quite rare these days.. |
|
Maybe this can be a separate workflow running in a cron (maybe once a week). I think it still make sense to be able to discover issues with 32bits compat in composer before it reaches released versions, given how composer is a fundamental tool in the ecosystem. |
|
Yeah, cron wouldn't have caught this though as I released too quick after merge.. So rather run this only on main, it'll limit the noise/cpu waste while still keeping the safeguard. |
|
Idea: run it weekly and anytime the composer.lock changes. Also add the ability to trigger it manually from the github interface to allow on-demand runs if needed. |
|
I think running on merge whenever something reaches main is ok, if we update dependencies that'll run it anyway.. |
|
Merging now to make sure it fails before I update json-schema |
* Add a CI job running with a 32bits build of PHP * Move to a run that only happens on main branch --------- Co-authored-by: Jordi Boggiano <j.boggiano@seld.be>
Refs #12365