Start a build through Bitrise.io

Archive Issues
1

Something seems to be down on website.

Indeed, I cannot create new build anymore through “Start/ Schedule a Build” button.

Same issue when I run curl command.

2

Damn it, dummy mistake.

I would like to close this issue :\

3

No problem at all :slight_smile: Just curious, what was the issue @jessyhanzo?

4

We have an issue with one of our bot which runs curl :

<html><body>You are being <a href="https://app.bitrise.io/app/APP_ID/build/start.json">redirected</a>.</body></html>.

For finding the issue, I tried to compare curl generated in Bitrise.io and curl generated by bot.

But by doing some tests, I forget to fill Workflow field and an error occured. Thus it’s not really blocking because we always specify the workflow parameter.

Anyway, I continue trying to understand why command is redirected.

5

@jessyhanzo thanks for the info!

I can help with that: DEPRECATION of Build Trigger API on 'www' subdomain (use 'app' subdomain or the public API instead)

1 Like
6

Finally, answer is pretty simple.

We have to use : app.bitrise.io and not www.bitrise.io … :sweat_smile:

1 Like
7

Well, that’s indeed one solution but if possible I’d suggest you to switch to api.bitrise.io instead. Same params are supported there, but the authentication is different - you have to use Personal Access Token there as for any other api endpoint. Advantage of PAT is that it also identifies the user the PAT is registered for, while the old app. endpoint uses a repo specific token (instead of a user specific one).

1 Like
8

Okay, it’s very clear, thanks !

Since curl is launched by bot and we don’t have a bot user in Bitrise.io, maybe we could keep app keyword for now.

9

Sure, feel free to! We’re not removing/deprecating that endpoint and we don’t plan to either, we just move it to the new app. domain (more info about this move will be published soon :wink: ).

One note: if you’re around the curl command make sure to specify the -L flag, that would make curl to follow the redirect. With -L even the old www. one will work / properly redirect :slight_smile: (but please don’t use the www. one, that endpoint is actually deprecated, use the app. one instead which is not deprecated).

1 Like
10

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.