Re: Github Pull Request Builder only status, no comments

2013-11-02 Thread John Russell
Ah, thank you so much. Now that you mention it the doc for that setting does clearly explain that although the name of the setting could probably be more helpful. Thanks again. On Sat, Nov 2, 2013 at 9:07 AM, wrote: > On Thursday, 31 October 2013 13:57:41 UTC, John Russell wrote: > >> Is there

Re: Unable to connect EC2 slaves to remote Git repository

2013-11-02 Thread David V
I see that GIT_SSH is an environment variable which changes the command which Git uses to connect to the remote host. Maybe this is the wrong path to search down, but is how can I find out what this value is? Or perhaps what dependencies it might have. Maybe the AMI is missing something that I

Unable to connect EC2 slaves to remote Git repository

2013-11-02 Thread David V
I'm trying to use the Jenkins Amazon EC2 plugin to start and use AWS EC2 instances for slaves. Jenkins will start the slave, and the slave connects to the master, but my builds are not able to connect to our Git repositories over SSH. The slave is running on the Amazon Linux AMI. I created a Gl

Re: Github Pull Request Builder only status, no comments

2013-11-02 Thread hugh
On Thursday, 31 October 2013 13:57:41 UTC, John Russell wrote: > Is there a way to configure GHPRB to only set the github status for a PR > and not put any comments on the PR at all? I have the box to use comments > if status fails unchecked and status is being set, but I get a lot of > complai

Re: distribution build configuration

2013-11-02 Thread Mark Waite
It seems like you'd use the credentials plugin[1] to configure one or more ssh keys copied from the Gitlab UI to the Jenkins credential, then the jobs would be configured to use one of those credentials and to use ssh based access to read from the git repositories hosted on the Gitlab server. We u

Re: LDAP without group access

2013-11-02 Thread Philipp Kraus
Am Samstag, 2. November 2013 08:57:53 UTC+1 schrieb Stephen Connolly: > > Unless you specify the group names in your authorization strategy, the > group info will not be used, so it should not matter at all that the group > information is being discovered because you would need to define permis

distribution build configuration

2013-11-02 Thread Philipp Kraus
Hello, I run a Jenkins master on an Ubuntu server, in the firewall only SSH, HTTP, HTTPS ports are openend for incomming communication. I have read https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds for distribution builds, but on my master I use LDAP for user authentification. On

Re: LDAP without group access

2013-11-02 Thread Stephen Connolly
Unless you specify the group names in your authorization strategy, the group info will not be used, so it should not matter at all that the group information is being discovered because you would need to define permission assignments that use these groups in order for it to be relevant On Friday,