-Re: permanant builds on jenkins
Jay Vyas 2013-07-07, 16:03
1) I've noticed that https://builds.apache.org/view/A-F/view/Bigtop/ is not
valid but "https://builds.apache.org/job/Bigtop-trunk/" seems to work. Is
this an error on the website?
2) http://bigtop01.cloudera.org:8080/job/Bigtop-VM-matrix/ Seems to build
direct from HEAD.
Are there actual bigtop releases which aren't on jenkins? Everything seems
to be centered around the build server, rather than actual frozen,
3) Regarding testing the VMs. Maybe to start some simple virt-install
scripts could help confirm that the KVM builds, at least, are working. If
we could get them working with static IPs then we could even clone down the
bigtop source code and run bigtop hadoop tests on the VMs after
construction as a validation step.
On Sat, Jul 6, 2013 at 8:58 PM, Bruno Mahé <[EMAIL PROTECTED]> wrote:
> On 07/06/2013 07:33 AM, Jay Vyas wrote:
>> Hi bigtop:
>> Are there any permanant builds saved on jenkins (for the VM matrix)?
>> If not it would be nice to add them for certain known well tested,
>> working disk images .
>> (for context, I'm currently running Mr2 build of the KVM box and it
>> appears to have some intermittent write issues on the DataNode path, and
>> also, my namenode appears to really like being in safe mode. these
>> could just be due to VM setup though, as im changing some things like
>> adding static IPs and data node write paths... so nothing to be alarmed
>> Jay Vyas
> Hi Jay,
> Could you defined "permanent build" ?
> I am not sure if this fits your requirement, but jenkins has a link to the
> latest successful build (ex: http://bigtop01.cloudera.org:**
> We do not store convenient artifacts of VMs since no one has asked about
> it before.
> So ideally, known well tested working disk images would be the ones from
> Apache Bigtop releases. But right now, there is not much testing of our
> VMs. But any help on that front would be welcome!
> Note also that I added that VM more as a base VM for an Apache Hadoop
> cloud image than a developer VM. That's why there is not much in it as well
> as no desktop pre-configured.
> So depending on your needs, we may want to add a new VM or enhance the
> current one (also, boxgrinder enables inheritance between appliances).
> Also Boxgrinder is apparently not being maintained anymore. So we may want
> to look into other VM builders (Oz, etc.)