Re: [nebula-dev] Problems beetween GitHub, Nebula and Jenkins

[Wim Jongman <wim.jongman@xxxxxxxxx>]

Hi Laurent,

 

The process is described in the Building section of our contribution guide [1].

 

In short. The builds only run automatically for trusted users because people can change the pom.xml in a pull request and inject all sorts of malicious code. So when you ok a PR for building, you have to make sure it is a trusted persona and preferably check for any pom.xml injection before you “okay to test”.

 

Committers may add themselves as admins by changing the Jenkins configuration job which also can be found at [1].

 

At the moment I believe Jonah and I are the admins. But every committer should be whitelisted.

 

I also whitelist frequent contributors.

 

Cheers,

 

Wim

 

[1] https://wiki.eclipse.org/Nebula/Contributions

On Sun, Apr 14, 2019 at 3:40 PM Laurent Caron <laurent.caron@xxxxxxxxx> wrote:

Good afternoon,

I've fixed a few old bugs on Nebula on last days, and I noticed 2 points :

a) When a PR is created on GitHub, there is only one check (ECA). There is no more building checks

b) When a PR is created, there is no more comment from Eclipse Genie that points to the PR URL on GitHub

Who is in charge of these "bridges" ?

Cheers,

Laurent

_______________________________________________
nebula-dev mailing list
nebula-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/nebula-dev