Re: Jenkins ASF + Pull Requests + webhooks

2019-01-06 Thread Tibor Digana
disabled logs, workspace and artifacts for anonymous Jenkins users, but available for PMC and Maven committers. On Sun, Jan 6, 2019 at 8:41 PM Mickael Istria wrote: > On Sun, Jan 6, 2019 at 8:32 PM Tibor Digana > wrote: > > > I meant Bitcoins. Without network access bitcoins can be loaded but

Re: Jenkins ASF + Pull Requests + webhooks

2019-01-06 Thread Mickael Istria
On Sun, Jan 6, 2019 at 8:32 PM Tibor Digana wrote: > I meant Bitcoins. Without network access bitcoins can be loaded but nobody > can use them. An access to Workspace and archived artifacts should be > disabled for users. That would be sad since those are actually super helpful when trying to

Re: Jenkins ASF + Pull Requests + webhooks

2019-01-06 Thread Tibor Digana
@Stephen Connolly I meant Bitcoins. Without network access bitcoins can be loaded but nobody can use them. An access to Workspace and archived artifacts should be disabled for users. On Sun, Jan 6, 2019 at 5:51 PM Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > That is not the

Re: Jenkins ASF + Pull Requests + webhooks

2019-01-06 Thread Stephen Connolly
That is not the problem you think it is. Bitcoin mining is the current issue. And through Jenkinsfile or Process.exec you can bypass JVM permissions On Sun 6 Jan 2019 at 16:44, Tibor Digana wrote: > Regarding "pull/1234/head" refs and the security, I think allowing only the > permission to

Re: Jenkins ASF + Pull Requests + webhooks

2019-01-06 Thread Tibor Digana
Regarding "pull/1234/head" refs and the security, I think allowing only the permission to Maven Central IP address is needed and nowhere else. This can be accomplished by the java policy in JRE. WDYT? On Sun, Jan 6, 2019 at 11:09 AM Hervé BOUTEMY wrote: > I didn't know about these special

Re: Jenkins ASF + Pull Requests + webhooks

2019-01-06 Thread Hervé BOUTEMY
I didn't know about these special "pull/1234/head" refs, that are not real branches: if these pseudo-branches were synchronized to Gitbox like any branch, the Gitpubsub mechanism could happen at Apache of course, the security implications of running code from these PR branches would still have

Jenkins ASF + Pull Requests + webhooks

2019-01-05 Thread Enrico Olivelli
Hi Stephen, I am not a Jenkins expert, but I want to share this idea, maybe it can help. Can we use GitHub webhooks in order to trigger the creation of a Job inside Maven-Box ? This way we don't have to continuously use Github API. When an user creates/updates a PR we can import the PR and create