On 07/30/2015 12:38 PM, Nikita Karetnikov wrote: > So I'm looking into Bake integration with Gitlab. Here's the rough > plan: > > 1. Setup web hooks as described here: > > https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/web_hooks/web_hooks.md > > 2. Parse that on the Bake side. > > 3. Give Bake push access to master. > > It'd be ideal if Bake could test merge requests, but there are some > challenges. There's only one object type for merge requests, which can > be in multiple states: open, updated, merged, closed. So there doesn't > seem to be a way to clearly indicate: "test this!" Bake could test and > merge sequentially, but that might result in weird history. There could > be a delay, say, 24 hours. But this is not how Bake is intended to be > used. Paraphrasing Neil: "Bake is for semi-trusted teams where people > can make mistakes but are not malicious." Which means giving access to > all regular contributors. Then, the workflow becomes: a user pushes to > a feature branch on the main repo, Bake takes that as "ready for merge" > and tests; merges if appropriate. Is it possible with Gitlab? >
Yes, we can give bake push permission for master and we could extend the permissions to more people to push to branches on the main repo that bake will watch. I'm not sure the details, but perhaps we ask contributors to open MRs that aren't MRs to master branch but to a bake-ready feature branch or something like that. I could also imagine new devs opening traditional MRs but devs that are trusted get permission to push to feature-branches on the main repo… > Right now, I'm just trying to run Gitlab locally and hoping to do some > simple testing. That's all for now. > _______________________________________________ > Dev mailing list > [email protected] > https://lists.snowdrift.coop/mailman/listinfo/dev > -- Aaron Wolf Snowdrift.coop <https://snowdrift.coop> _______________________________________________ Dev mailing list [email protected] https://lists.snowdrift.coop/mailman/listinfo/dev
