[JIRA] [git] (JENKINS-23985) Handle commits that are out of scope for sparse checkout

Sat, 26 Jul 2014 11:22:18 -0700

Mark Waite commented on Bug JENKINS-23985

Can you provide more details of the steps you're taking which show the failure?

I was unable to duplicate the problem with the following steps:

  1. Create a new multi-configuration job named JENKINS-23985-sparse-checkout-fails-multi
  2. Enable "Elastic axis" for configuration with value "windows,linux". In my environment, that means the job will run on CentOS 7 x64, Debian Testing x64, Debian Wheezy x86, Debian Wheezy x64, Windows 7 x64, Windows 7 x86, Windows 8 x64, and Windows Home Server 2011. Those machines tend to all have different git versions installed, so the configuration rapidly tests many different git versions
  3. Enable git for source control
  4. Add my git URL, git://wheezy64b/git/mwaite/bin.git
  5. Add the "Additional Behaviours" for "Sparse Checkout paths"
  6. Add the value "jobs" in the "Path" field of the "Sparse Checkout paths" addition
  7. Add an XShell build step to run the command "git status"
  8. Enable SCM polling, but with no schedule (so that my hook can cause it to poll at any time)
  9. Cause a poll, which runs the job. Confirm that the build is successful and the "jobs" directory is the only directory checked out
  10. Commit a change to the central repository in the "jobs" directory, confirm that the job builds again successfully
  11. Commit a change to the central repository outside the "jobs" directory, confirm that the job builds again, and the change is not visible in the working directory of each of the jobs

Please provide further information on the system configuration also, in case the issue is somehow specific to your system. Refer to what to put in an issue report for guidance on the types of data which help persuade open source developers to understand and fix bugs you've detected.
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.

Reply via email to