| Re: [egit-dev] Hudson CI bot verifying all EGit changes pushed for review |
Now we have the following issue: [1] http://egit.eclipse.org/r/#change,2646 wants to do an incompatible change. [2] http://egit.eclipse.org/r/#change,2888 wants to react on this by adapting the EGit code to the JGit change. The egit.gerrit job does not “see” the correct jgit change as long as it is not submitted, so we can’t verify [2] before submitting [1], right? Question: what’s the correct way of doing this? Submit [1], wait until the “real” jgit build is through and then verify [2] again? When is the right time to submit [2] anyway? Von: egit-dev-bounces@xxxxxxxxxxx [mailto:egit-dev-bounces@xxxxxxxxxxx] Im Auftrag von Matthias Sohn 2011/3/22 Matthias Sohn <matthias.sohn@xxxxxxxxxxxxxx> I configured Hudson to also run verification builds for all EGit changes pushed for review. Find these builds here [1]. In case you want to rerun a build for a given patchset, go to [2] and run a Gerrit query to find the patchset you want to rebuild, select it and click "Trigger Selected" -- |