Re: problem with jenkins not able to access git

2017-01-12 Thread Phil Swenson 
Actually I don't think it has anything to do with git... i tried 
downgrading my git plugin and got this error:


   - Failed to resolve host name updates.jenkins-ci.org. Perhaps you need 
   to configure HTTP proxy? 
   


On Thursday, January 12, 2017 at 1:13:30 PM UTC-7, Phil Swenson wrote:
>
> I have a new jenkins server I'm trying to stand up 2.4 with all latest 
> plugins... it works for a day and then starts giving me errors like this:
>
> Started by timer
>  > git rev-parse --is-inside-work-tree # timeout=10
> Setting origin to g...@bitbucket.org:myco/ace-esni-datastore.git
>  > git config remote.origin.url 
> g...@bitbucket.org:mygo/ace-esni-datastore.git # timeout=10
> Fetching & pruning origin...
> Fetching upstream changes from origin
>  > git --version # timeout=10
> using GIT_SSH to set credentials 
>  > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* 
> --prune
> FATAL: Failed to recompute children of ace-esni-datastore-test
> hudson.plugins.git.GitException 
> :
>  Command "git fetch --tags --progress origin 
> +refs/heads/*:refs/remotes/origin/* --prune" returned status code 128:
> stdout: 
> stderr: ssh: Could not resolve hostname bitbucket.org: Name or service not 
> known
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
>
> at 
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1772)
> at 
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1516)
> at 
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:67)
> at 
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:318)
> at 
> jenkins.plugins.git.AbstractGitSCMSource.doRetrieve(AbstractGitSCMSource.java:203)
> at 
> jenkins.plugins.git.AbstractGitSCMSource.retrieve(AbstractGitSCMSource.java:233)
> at jenkins.scm.api.SCMSource.fetch(SCMSource.java:148)
> at 
> jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:294)
> at 
> com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:187)
> at 
> com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:139)
> at hudson.model.ResourceController.execute(ResourceController.java:98)
> at hudson.model.Executor.run(Executor.java:404)
> Finished: FAILURE
>
>
>
> All the jobs do this (all pipeline jobs)
>
> I had this problem yesterday as well and restored from a snapshot and got 
> it going again... then I upgraded to jenkins 2.4 and updated all the 
> plugins.  Everything was great, but all of a sudden this error popped up 
> again.
>
>
>
> Any ideas? 
>
> thanks,
> phil
>
>

-- 
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ef0c978f-a07e-43bf-b782-265840bb838d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

problem with jenkins not able to access git

2017-01-12 Thread Phil Swenson 
I have a new jenkins server I'm trying to stand up 2.4 with all latest 
plugins... it works for a day and then starts giving me errors like this:

Started by timer
 > git rev-parse --is-inside-work-tree # timeout=10
Setting origin to g...@bitbucket.org:myco/ace-esni-datastore.git
 > git config remote.origin.url g...@bitbucket.org:mygo/ace-esni-datastore.git 
 > # timeout=10
Fetching & pruning origin...
Fetching upstream changes from origin
 > git --version # timeout=10
using GIT_SSH to set credentials 
 > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* 
 > --prune
FATAL: Failed to recompute children of ace-esni-datastore-test
hudson.plugins.git.GitException 
:
 Command "git fetch --tags --progress origin 
+refs/heads/*:refs/remotes/origin/* --prune" returned status code 128:
stdout: 
stderr: ssh: Could not resolve hostname bitbucket.org: Name or service not known
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1772)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1516)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:67)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:318)
at 
jenkins.plugins.git.AbstractGitSCMSource.doRetrieve(AbstractGitSCMSource.java:203)
at 
jenkins.plugins.git.AbstractGitSCMSource.retrieve(AbstractGitSCMSource.java:233)
at jenkins.scm.api.SCMSource.fetch(SCMSource.java:148)
at 
jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:294)
at 
com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:187)
at 
com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:139)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:404)
Finished: FAILURE



All the jobs do this (all pipeline jobs)

I had this problem yesterday as well and restored from a snapshot and got 
it going again... then I upgraded to jenkins 2.4 and updated all the 
plugins.  Everything was great, but all of a sudden this error popped up 
again.



Any ideas? 

thanks,
phil

-- 
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/d03bc1a6-4ad1-4514-bd85-aa4bea47602e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.