Danger: Is it possible to use danger within the Xcode bots CI?

Created on 11 Apr 2016  路  7Comments  路  Source: danger/danger

I'm not sure If I'm doing something wrong.
But my script trigger fails with the message
Could not find a CI source

Thanks.

Help Wanted Integration Question

Most helpful comment

@czechboy0 amazing, I'm using Buildasaur.
I think I could do a pr to make danger support Xcode Server CI later soon.

All 7 comments

No-one has worked on adding Xcode Bots support, I imagine you'll need to set it up like jenkins?

Thanks for the quick reply.

Probably that's should be like jenkins, I'll try to take a look on it later.

I guess that's where @czechboy0 is an expert :rocket:

It should be easy or super easy to get danger working with Xcode Server.

_Super easy_ version:
If you're using Buildasaur, the automatically created bots for each PR already follow a scheme which contains both the repo name and the PR number (it's BuildaBot [danger/danger] PR #17, meaning BuildaBot [REPO_SLUG] PR #PR_NUMBER). So all you need to do in the danger adapter is to read the bot name from the XCS_BOT_NAME envvar and parse out the repo slug and the PR number. AFAIR danger takes care of the rest.

_Easy_ version:
If you're not using Buildasaur and for some reason you manually create Bots for each PR, you would need to manually inject the environment variables in the prebuild/postbuild script with something like export REPO_SLUG=danger/danger and export PR_NUMBER=17, which you'd detect in the danger adapter. It's a stretch, tbh I think the first version using Buildasaur is just much simpler.

In both cases, you'd trigger danger from the prebuild script.

@czechboy0 amazing, I'm using Buildasaur.
I think I could do a pr to make danger support Xcode Server CI later soon.

@Antondomashnev that'd be great!

fixed by #172

Was this page helpful?
0 / 5 - 0 ratings