Adding FreeBSD/arm64 Jenkins build / QEMU job

[Li-Wen Hsu]

On Monday, June 29, 2015, Julio Merino <jmmv at freebsd.org> wrote:

> On Apr 18, 2015, at 15:13 , Li-Wen Hsu <lwhsu at FreeBSD.org> wrote:
> >
> > On Fri, Apr 17, 2015 at 16:47:45 -0400, Ed Maste wrote:
> >> On 17 April 2015 at 11:27, Li-Wen Hsu <lwhsu at freebsd.org <javascript:;>>
> wrote:
> >>>
> >>> That will be great.  And I am interested to know what do you plan for
> >>> booting QEMU machine, running test inside VM then getting results
> >>> archived to outside.  There are many approaches, and I wanted to know
> >>> the most suitable one for us.
> >>
> >> Good question. Are we doing this for other targets today (QEMU, bhyve,
> >> or metal)?
> >
> > Yes.
> >
> > For kuya/QEMU, it builds a image which executes tests upon launch:
> >
> >
> https://svnweb.freebsd.org/base/user/jmmv/autotest/node/iterate.sh?view=markup&pathrev=271564#l154
> >
> > and mounts the image to extract results:
> >
> >
> https://svnweb.freebsd.org/base/user/jmmv/autotest/node/iterate.sh?view=markup&pathrev=271564#l284
>
> I just came across this email and I’m wondering: are you currently using
> the autotest code within Jenkinsto perform regular test runs?  (That’d be
> nice to hear!)
>

Unfortunately, not yet, but I think this is a good way, and we
absolutely can do that in the future.

For the arm64 tests, as I discussed with Ed in BSDCan, the first step we
can do may just use QEMU for simple boot test.  We cannot run full kyua
tests at this point due to implementation is not complete.

What I'm thinking about the test steps in the future might be:
- Build the ISO/memstick image just as the same way we do the
official release
- Use the artifact from above to build or install the test VM image
- Boot the machine, run tests
- Extract results from the VM and feed to Jenkins to track the result

Most of these steps already exist and are running on jenkins.freebsd.org.
Only fist two steps are slightly different. I thought it would be good to
also provide snapshot ISO/images for external users to do more tests.

If anybody is interested in this and want to help. The easiest way is just
write some scripts for doing these steps.  And I am happy to convert them
to a jenkins job to run periodically.

Li-Wen


-- 
Li-Wen Hsu
http://lwhsu.org