Issue Type: Bug Bug
Affects Versions: current
Assignee: Unassigned
Components: github
Created: 11/Jun/13 5:32 PM
Description:

I have the same issue as closed bug #594. There wasn't a resolution in the follow-up that resolves this issue for me.

I have several private GitHub repos that I need to build. I'm using deployment keys and a config file for SSH to let the Jenkins user know what key to use for each repo. In order to get Jenkins to work with GitHub in this fashion, I had to change the repository URL to point to the host alias. So, it looks like:

[email protected]:myorg/repo.git

This allows me to initiate a build from Jenkins, which is able to checkout the code from github successfully.

I need to initiate builds from GitHub when code is committed. I setup everything and tested the webhook. I saw the payload come in successfully in the logs. When I commit code to the repo, I get the following error: "FINE: Skipped <repo> because it doesn't have a matching repository."

If I change my repository URL back to [email protected]:myorg/repo.git I get a match on the repo after code commit, but then the jenkins user can't checkout the code from GitHub because it doesn't know what SSH key to use.

Is there a way to get this to work? Thanks.

Environment: Ubuntu 12.10
Project: Jenkins
Priority: Major Major
Reporter: IT Archmerc
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to