Jenkins pull request admin privileges

[Daniel Lee]

When we first went to a gitflow-like process, I added Bob and myself as admins. It was only meant to be a limited group until we kind of got the process down and understood the bottleneck and how it affected our build server.

I just added the whole stan-dev member list to the white list, so any pull request created by us will kick off a build. Any additional commits on existing pull requests will also create more test jobs. I added the organization, so hopefully any future changes will reflect on that list.

I added, by hand, all the existing members to the admin list on Jenkins. The commands to control Jenkins:

- "Jenkins, ok to test" -- accept to testing phase for a pull request by a member not on the white list. This should kick off a build automatically.

- "Jenkins, test this please" or "Jenkins, retest this please" -- will put a build on the testing queue.

Marcus, can you try the test phrase on the last pull request again? I didn't get around to updating Jenkins until just now.

Just a reminder, this is where Jenkins is located on the web:

http://d1m1s1b1.stat.columbia.edu:8080/

Daniel

[Marcus Brubaker]

Looks like that worked.  Thanks for the update Daniel!

Cheers,

Marcus

--
You received this message because you are subscribed to the Google Groups "stan development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to stan-dev+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.