If I run manually, the slave with 1.7.9.5 is able to fetch the changes.
Only the polling is an issue. With the problem job switched to running on a
different slave with 1.8+, I am not currently seeing the issue.
On Friday, February 13, 2015 at 12:00:10 PM UTC-5, Mark Waite wrote:
>
> I haven't d
I haven't done the detailed review of the git capabilities, but I thought
that credentials support only first arrived in git 1.7.9 (or possibly
1.7.10). Your 1.7.9 machine may have a git version which is too old for
that use model.
Does the 1.7.9 based machine checkout successfully from a single
I'm able to reproduce the error with my test job if I have it restricted to
the same slave that the problem job is using. It happens with the single
SCM job that has multiple branches, but I haven't been able to reproduce
with just a single branch configurations, so I'm thinking it has to do wit
I forgot that this job tries to check all branches as well and I wonder if
that is more of the cause. The credentials are stored within the local
repository so multiple Git repos probably wouldn't cause conflicts.
However, if a single repo checks out multiple branches, it of course does a
git c
You might be able to test the theory by creating a multi-scm job which uses
10 or 20 authenticated git repositories, then run that job multiple times.
If it fails, then it is probably the file delete condition we're theorizing
might be there.
If it does not fail, then it is likely something else.
I was kinda thinking that, any suggestions on how I could debug this? Or
does someone know where the numbered credential file is named? If it is
based on a timestamp and the SCM plug-in checks both repos with the same
credential file, I could see how that could be a problem if one deletes it
an
The message indicates that a file which the plugin expects to be on the
file system is not there. That stack trace might hint that there is a
race condition in the multiple SCM plugin / git plugin interaction.
I don't know if the file is missing because the git plugin performed some
cleanup, or
I should add I'm using Jenkins 1.554.2, Git client plug-in 1.16.1 and Git
plug-in 2.2.12. It seems like this used to work, but I'm not sure what
version of each plug-in I had.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe fro
I get this result from polling sometimes. This is a multiple SCMs
configuration. I don't believe I see this with single SCM setups. I see that it
cannot find the temporary credential path, but how is that even supposed to be
created?
Started on Feb 12, 2015 9:26:36 AM
Polling SCM changes on
