Tuesday, September 3, 2013

Just run a new build in Jenkins to deal with dirtiness that occurs when a "rename" straddles two check-ins.

This WILL fix the build. My situation:

  1. I realized a file could have a better name.
  2. I made a new file and destroyed the old one.
  3. I checked in the delete locally to Mercurial, but not the addition.
  4. I then remembered the addition, and checked it in locally too.
  5. I then committed to my branch the two separate changesets.
  6. The build broke in Jenkins! Jenkins could not handle the “missing” file!
  7. I made some further unrelated changes and committed, first locally and then to my branch again.
  8. The build succeeded in Jenkins!

No comments:

Post a Comment