fatal: repository 'http://jenkins:8080/jenkins/workflowLibs.git/' not found

[Kenneth Baltrinic]

I feel I am missing something obvious here.  I have a test bed Jenkins server v 1.592 with workflow 1.0 plugins installed, this includes the Workflow: Global Shared Library for CPS workflow plugin.  All the workflow plugins are installed and enabled.

Given that, attempting to do git clone http://jenkins:8080/jenkins/workflowLibs.git  where jenkins resolves to the test bed server, I get:

Cloning into 'workflowLibs'...

fatal: repository 'http://jenkins:8080/jenkins/workflowLibs.git/' not found

I am looking everywhere to see if there is a checkbox that I need to check to turn this feature on but I can find one and none seem mentioned in the docs. What am I missing?

--Ken

[Kenneth Baltrinic]

Is there anyone out there successfully using the Global Shared Library?

[Kenneth Baltrinic]

I figured out my primary mistake.  All the docs give urls of the form http:/server/jenkins/workflowLibs.git.  This format assumed that the Jenkins server itself was not located at server root but at the jenkins endpoint beneath the server root.  To the contrary my install has Jenkins at the server root, making the correct URL http://jenkins:8080/workflowLibs.git. A quick look at the source helped to figure that out.

The repo seems to behave oddly though.  I can push to it and I can see my changes actually on the server if I ssh into the server and look at the /home/jenkins/workflow-lib folder but I cannot clone or pull from the repo.  Git tells me I tried to clone an empty repo.  Its like the repo is write only or some such.  

Anyway the initial issue is resolved.  I'll look into the empty-repo business later.

On Friday, December 12, 2014 2:08:51 PM UTC-5, Kenneth Baltrinic wrote:

[Mark Waite]

On Mon, Dec 15, 2014 at 7:48 AM, Kenneth Baltrinic <ken...@baltrinic.com> wrote:

I figured out my primary mistake.  All the docs give urls of the form http:/server/jenkins/workflowLibs.git.  This format assumed that the Jenkins server itself was not located at server root but at the jenkins endpoint beneath the server root.  To the contrary my install has Jenkins at the server root, making the correct URL http://jenkins:8080/workflowLibs.git. A quick look at the source helped to figure that out.

The repo seems to behave oddly though.  I can push to it and I can see my changes actually on the server if I ssh into the server and look at the /home/jenkins/workflow-lib folder but I cannot clone or pull from the repo.  Git tells me I tried to clone an empty repo.  Its like the repo is write only or some such.  

I wonder if you're seeing another instance of JENKINS-25212?

[https://issues.jenkins-ci.org/browse/JENKINS-25212]

Mark Waite

 

Anyway the initial issue is resolved.  I'll look into the empty-repo business later.

On Friday, December 12, 2014 2:08:51 PM UTC-5, Kenneth Baltrinic wrote:

I feel I am missing something obvious here.  I have a test bed Jenkins server v 1.592 with workflow 1.0 plugins installed, this includes the Workflow: Global Shared Library for CPS workflow plugin.  All the workflow plugins are installed and enabled.

Given that, attempting to do git clone http://jenkins:8080/jenkins/workflowLibs.git  where jenkins resolves to the test bed server, I get:

Cloning into 'workflowLibs'...

fatal: repository 'http://jenkins:8080/jenkins/workflowLibs.git/' not found

I am looking everywhere to see if there is a checkbox that I need to check to turn this feature on but I can find one and none seem mentioned in the docs. What am I missing?

--Ken

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/a048f0ba-6e1c-475d-a4e6-17a77db513bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Thanks!

Mark Waite

[Kenneth Baltrinic]

I am slaying other dragons right now but will circle back and investigate the possibility at some point.  Good tip though.  Thanks.

[Kohsuke Kawaguchi]

Mark was correct, this was JENKINS-25212. I've fixed this problem in git-server plugin 1.6.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d073d042-f03e-4de1-84b1-0f854d43cea2%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Kohsuke Kawaguchi