Jenkins doesn't update origin/master

[mgeisler]

Triggering a build in Jenkins and asking for origin/master doesn't actually rebuild the latest version. Instead, origin/master seems to have been left behind at a commit a few weeks old. The ref was probably last updated when someone ran git fetch by hand.

Is this normal or should Jenkins update the ref? If it shouldn't update it, then how do we trigger a build without adding a "retest this please" comment?

[larsbutler]

I think the answer is to clean the workspace after each build. In general, this is a good practice.

Regardless, can you point me to an example build in Jenkins (http://ci.oslab.cc/job/zpm/) where this issue occurred? I'd like to look at the log, just to be sure.

[mgeisler]

I feel we can do nightly builds in a clean workspace, but it should be possible to do the builds per pull request without cleaning it. That way we both ensure that things can be built from scratch (important for new contributors) and that you can build incrementally (important for existing developers).

An example: build 136 was started due to #76 and used 60d58cb876e91f4bfb0b631f760a650381be7f1c (the result of merging b10d18d). I triggered build 138 using origin/master as the commit to build, and jenkins checked f8e87d8 out.

[larsbutler]

With the recent rebuild of http://ci.zerovm.org, this is no longer an issue. On every build, the workspace is wiped clean (as I suggested above).