Allan Lei commented on Bug JENKINS-24516

Was there a preceding job for the failing job? If so, was the preceding job executed on a different platform?

This problem didn't cause failing jobs as it was not triggering jobs at all. It was failing when there was a github webhook and scheduled git polling. Yes there were preceding jobs. Yes, it was executed on a Windows 7 slave node launched via Java Web Start.

Are you using the EnvInject plugin? If so, could you insert a step in the build which reports the value of the PATH environment variable and post its value here?

Yes, 1.89. I will have to try out the PATH env at a later time.

Master Node (Ubuntu 14.04, Jenkins 1.579, git 2.2.5, envinject 1.89)
Slave Node (Windows 7, via Java Web start)

Things I tried/observed:

  • After upgrading to git plugin 2.2.5 and Jenkins 1.579, this problem did not initially happen, and everything worked as expected.
  • I had 3 separate jobs building from the same git repo, but with a different build script(production, staging, development). After the upgrades, I changed the credentials for development and staging jobs. Those jobs had an error in the build script which caused the job to fail. At this time, git polling for these 2 jobs will result in this error, but the production job still polled correctly. Jobs duplicated from the production job will work correctly until there's a build error.
  • Copied the ssh*.sh and ssh*key files that are generated from "git ls-remote -h ...", set GIT_SSH to ssh*.sh and ran it as the jenkins process user successfully
  • Manually triggering a build via Build Now button works fine
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/d/optout.

Reply via email to