Support for Gitlab CI externals
Bernard Pratz
If gitlab support is not a priority, to enable support implemented by the user, we'd need to have a couple of features added:
• have all the webhooks also available as script hooks (like eas-build-pre-install), I made a request for submit hooks: https://expo.canny.io/feature-requests/p/add-hooks-on-submit-lifecycle-events.
• have an eas-build-failure hook as well.
https://expo.canny.io/feature-requests/p/add-a-failure-build-hook
And an
$EAS_PLATFORM
variable, that alike $EAS_PROFILE
exposes the target platform (ios or android). And finally make the links to the artifact and the builds on the stores available as env at the success hooks.Bernard Pratz
I did a prototype of that working using existing hooks cf https://forums.expo.dev/t/using-gitlab-ci-externals-to-get-feedback-for-eas/60692
but it lacks several hooks and variables to make it complete. So either a good way would be to add the missing pieces (missing hooks and environment) or to directly implement a full support for gitlab ci.