RE: [higgins-dev] Running autobuild from local machine

[Jeesmon Jacob <JJacob@xxxxxxxxxxxxx>]

I slightly disagree with this. We discovered many missing required components when cp.jndi is added to autobuild by running it locally. Otherwise we need to wait for autobuild to trigger everytime we make changes (especially for those who don't have access to build machine). Moreover, IMHO there should be a way to test locally whatever we commit instead of spamming with failure emails to component owners from build machine. We are not trying to build the component, but we are trying to test whether the changes we made to autobuild script works.

Thanks,
Jeesmon

-----Original Message-----
From: higgins-dev-bounces@xxxxxxxxxxx [mailto:higgins-dev-bounces@xxxxxxxxxxx] On Behalf Of Peter Kimlach
Sent: Wednesday, October 17, 2007 5:13 AM
To: Higgins (Trust Framework) Project developer discussions
Subject: Re: [higgins-dev] Running autobuild from local machine

Running autobuild on local machine is bad idea. It  was created to get
all required resources to build component and than just run specified
targets from build.xml of the project. So you may just type for example
d:\workspace\project_name> ant plugin to start build plugin process.
This is the same as autobuilder do.
Besides autobuild will fail during  pushing build results to webHome ;)


Jeesmon Jacob wrote:
>
> I added a wiki page at
> http://wiki.eclipse.org/How_To_Test_Autobuild_On_Local_Machine with
> the steps to test run auto build from eclipse IDE. Please test it out
> and let me know if you see any issues in the instructions.
>
>
>
> -Jeesmon
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> higgins-dev mailing list
> higgins-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/higgins-dev
>

_______________________________________________
higgins-dev mailing list
higgins-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/higgins-dev