Trigger Apple Connect store and Google Play and Expo builds from Bitbucket?#15

If this isn’t already available, and also if it’s at all feasible, it would be great to trigger EAS builds, and to create builds for Android and iPhone builds from git commits. This would be for Expo/managed react native apps. With this, we can go end-to-end, starting with a hotfix out of Jira Service Management, move tickets to Jira, test, merge to the releae repo and have the OAT build out in a very short time.

Hi @Greg.elofson - thank you for submitting this request and for adding the additional detail in the description! Do you know if EAS Build has a public API? I’d be happy to arrange a quick call with you, myself and our Lead Engineer to discuss this use case and any others you might have in mind so we can help you get started with Stitch It! You can book a slot directly in my calendar for whenever suits you: https://meetings.hubspot.com/madeleine-vironda

Hi Madeleine,

Let me check whether EAS build had a public API…will be back shortly. Thanks for your attention!

cheers,

Greg

Hi Madeleine,

I sent out the following on the Expo forum:

“Hi, does EAS build had a public API? I ask because we’re using a new Adaptavist tool called “Stitch it” that is in Beta, and we want to run a build for Android and iOS based on an end-to-end CI/CD process that runs from Jira Service Management over to Jira, and then builds to an OTA update. Thanks!”

And received this reply:

“you can use eas-cli as an api client: run eas build:list –json –non-interactive – for example – to get a list of builds. our graphql api currently isn’t public.”

Thus is appears that there is not public API, but perhaps a way to work around that–based on the above. Please advise whether you recomment meeting with support.

Thanks,

Greg

Hi again,

Great to hear that you managed to get an answer so quickly!

Since they don’t have a public HTTP based API, it’s a bit difficult to interface with them, an option is to use their private GraphQL API from Stitch It that their CLI uses under the hood, but this would be a rather hacky and unreliable approach, since they can change their private API at any time. An alternative is to setup a BitBucket pipeline that makes use of their CLI to kick off builds, and then to call the BitBucket API from Stitch It to initiate that pipeline whenever needed (as a response to events being emitted from JSM).

I hope this helps, if not we can definitely jump on a call with our lead engineer to discuss this further. Do you have any other integration use cases in mind?

Thank you,

Madeleine