On 20.03.2012 Paritosh Ranjan wrote: > I don't have the privilege to view/edit the Jenkins job configuration, > so, I can not see the command from there.
http://wiki.apache.org/general/Jenkins <- explains how to get access as a committer. > Somehow, I am not able to figure out the command from the console, can > you help me here by telling the command ( for running the > Mahout-Examples-Cluster-Reuters build )? On the failed job click on "Console Output" - there click on "Full log" at the top. There I find ./examples/bin/cluster-reuters.sh 1 ./examples/bin/cluster-reuters.sh 2 > Can you also help by clarifying the protocols on the builds? i.e. which > builds to test before committing. How much time is allowed to fix > failing builds ( how much time for which build ), or is there something > like this? There are no hard and fast rules for that. General rule of thumb: Don't break the build. > Is it needed to run/build the Mahout-Examples-Cluster-Reuters ( along > with Mahout Quality i.e. mvn clean install on trunk ) before > committing, and if yes, is it a common practice? For me personally I at least run a mvn clean install - everything else depending on what parts of the project I changed. > Is this info about the builds documented somewhere? If the information > about the builds is not documented anywhere, then I would will like to > add it to the mahout wiki/site/somewhere i.e. which all builds do we > have, and which one is needed for what purpose and other rules for them. > If it is already documented, can you please share that link? I know of know link - having that documentation including links to how to get access to Jenkins. We have gone over build issues multiple times in the past - it might make sense for you to also check the mailing list archives for more information on the history of what you find in place right now. Isabel
signature.asc
Description: This is a digitally signed message part.
