This would require Jenkins and the SCM to share permissions, wouldn't it?
For Jenkins to be configured to "follow forks" it needs permission to
access any other user's repositories as they may be a fork of the
originally monitored repository?
Doesn't Bamboo do this? Or did I misread this feature?
>
>
> Don't use forks, use branches.
>
> Forks are good to allow people to contribute w/o being members of a
> projects (i.o.w. w/o granting them push permission). This is not the case
> for GH Enterprise, where all your devs are members of your project, aren't
> they?
>
>
Access control to the rep
Validate GH PRs, work in forks, when fork will be ready for merge - PR to
target branch, wait verification/do review. Pretty simple and easy.
On Wednesday, September 2, 2015 at 2:40:13 PM UTC+3, Eric Fontana wrote:
>
> I'm new to Jenkins, I have the GitHub plugin installed and its connected
> to
@Dirk, yes and that’s why lots of people / projects prefer to use Gerrit on top
of GitHub (e.g. Eclipse foundation, Openstack, …).
Have you tried using GerritHub? You can have the branch-level access control +
Jenkins integration for your continuous delivery pipeline.
HTH
Luca.
> On 2 Sep 20
Am 02.09.2015 um 15:20 schrieb Eric Fontana:
> we want to have certain branches restricted to certain contributors,
> which isn't supported by GHE.
Yep, lack of proper access control is a big problem of GH.
Bye...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*R
Well, they aren't. There are multiple groups, and we want to have certain
branches restricted to certain contributors,
which isn't supported by GHE.The fork model allows for this, which is
why we are in this position in the first place.
If you want to ensure that master and develop are alw
Am 02.09.2015 um 13:40 schrieb Eric Fontana:
> My question is, with GitHub's "Fork a Repo" flow, when a user forks a
> repo (which was currently being tracked by Jenkins), it no longer
> gets builds by Jenkins, since its a new repo now.If we want the
> forked repo to get built upon commit/push
I'm new to Jenkins, I have the GitHub plugin installed and its connected to
our GitHub Enterprise. I'm able to have it watch a Repo and build
upon an agreed upon schedule.
My question is, with GitHub's "Fork a Repo" flow, when a user forks a repo
(which was currently being tracked by Jenkins),
