You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by chris snow <ch...@gmail.com> on 2014/03/05 22:01:33 UTC
jenkins job for the developer build
Is there a jenkins job for the developer's build, i.e. mvn clean
install -P developer,systemvm? As a newbie cloudstack developer, when
the build fails locally it's difficult to know whether the problem is
because I am doing something wrong, or if the problem is due to a bad
commit.
Re: jenkins job for the developer build
Posted by chris snow <ch...@gmail.com>.
Ah, thanks for the tip.
On Thu, Mar 6, 2014 at 9:21 AM, Hugo Trippaers <tr...@gmail.com> wrote:
> The Jenkins builds do mvn -Pawsapi,systemvm clean install.
>
> I'm not using the developer profile there thats just for Marvin and Apidocs. Those are built separately. You can have a fully functional cloud dev environment without the developer profile.
>
> Cheers,
>
> Hugo
>
> Sent from my iPhone
>
>> On 6 mrt. 2014, at 06:01, chris snow <ch...@gmail.com> wrote:
>>
>> Is there a jenkins job for the developer's build, i.e. mvn clean
>> install -P developer,systemvm? As a newbie cloudstack developer, when
>> the build fails locally it's difficult to know whether the problem is
>> because I am doing something wrong, or if the problem is due to a bad
>> commit.
--
Check out my professional profile and connect with me on LinkedIn.
http://lnkd.in/cw5k69
Re: jenkins job for the developer build
Posted by Hugo Trippaers <tr...@gmail.com>.
The Jenkins builds do mvn -Pawsapi,systemvm clean install.
I'm not using the developer profile there thats just for Marvin and Apidocs. Those are built separately. You can have a fully functional cloud dev environment without the developer profile.
Cheers,
Hugo
Sent from my iPhone
> On 6 mrt. 2014, at 06:01, chris snow <ch...@gmail.com> wrote:
>
> Is there a jenkins job for the developer's build, i.e. mvn clean
> install -P developer,systemvm? As a newbie cloudstack developer, when
> the build fails locally it's difficult to know whether the problem is
> because I am doing something wrong, or if the problem is due to a bad
> commit.