|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Alright, i got to the end of it:
the probelm as i see it was in the fact that in .bashrc for the user under which the Jenkins and the slaves are operating i had the LD_LIBRARY_PATH specified incorrectly (it was missing the folder from which git executable was linking the libraries). In this case nothing can be done in Jenkins GUI on the configuration side in order to override this varaible on the slave. It is always last thing to run before the execution of the command.
So effectively i had a situation when if the job is rebuit on master node where the LD_LIBRARY_PATH was correct then the next poll of this project was successful. Now the interesting part is that as soon as the job was rebuilt on a slave with incorrrect LD_LIBRARY_PATH, then the next poll was failing!
So as far as i understand this behaviour contradicts to what is claimed - git polling seems to pick up latest known environment, but not the one from master node.
In order to check where the libraries are found by git executable you can run "ldd /path/to/git" It will show the list wof libraries used and where are they taken from, then if you will ovverride LD_LIBRARY_PATH and exclude one of the folders from the list it shoudl start failing with the error finding the libs.
hope that helps