Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bots Initial Integrations Are Not Triggered #129

Closed
grantjk opened this issue Sep 25, 2015 · 4 comments
Closed

Bots Initial Integrations Are Not Triggered #129

grantjk opened this issue Sep 25, 2015 · 4 comments

Comments

@grantjk
Copy link

grantjk commented Sep 25, 2015

With our setup, a bot is created fine for each PR, but the first integration is never created. We have to manually trigger the first integration, at which point, future integrations are handled perfect.

I've attached an image of our Bot config below and we're using SSH to access GH.

screenshot 2015-09-24 22 09 11

@czechboy0
Copy link
Member

Hmm, that's weird.

  1. What is your sync interval? Did you keep it at 15 seconds or did you make it longer? There is a caveat that actually the bot creation and the kick-off of its first integration are not done in the same sync pass, so you'd have to wait another sync interval seconds for Buildasaur to kick it off. Please make sure you waited at least that long and let me know if no integration is still kicked off (you can see it in Xcode in the Report Navigator).

@czechboy0
Copy link
Member

Wait, I just remembered - are you sure you don't have the lttm barrier enabled? That would cause Buildasaur to wait for a comment saying lttm to start testing. You can verify by hovering over the orange dot and reading the message. If it shows something like this below, you have the lttm barrier enabled - which you can disable easily in Buildasaur's UI (at the bottom, right below the Start button).

screenshot 2015-09-25 11 39 48

@czechboy0 czechboy0 removed their assignment Sep 25, 2015
@grantjk
Copy link
Author

grantjk commented Sep 25, 2015

That was it! Oops! Thanks!

That wasn't the default on the previous versions of the app, so I wasn't expecting it. Glad to see #130 go in!

👍

@grantjk grantjk closed this as completed Sep 25, 2015
@czechboy0
Copy link
Member

Okay, sorry about that. But at least #130 fixes that for others. To be honest, I should have realized this earlier, but I was just closed in my little world where lttm was commonplace.

Anyway, the default is off now, so this shouldn't happen again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants