[Commotion-dev] getting MeshTether to build from git

[Ben West]

I've used Jenkins for continuous integration in the past, and I would
handily recommend it.  It's also great for github integration, and
especially for archiving previous builds.

What sort of security layers would be desirable for a Jenkins instance?
The web UI can do basic username/password-based auth, which I would
recommend only serving over SSL.

On Tue, Jul 23, 2013 at 7:16 PM, Hans-Christoph Steiner <
hans at guardianproject.info> wrote:

>
> Hey Will,
>
> I'd be happy to advise on the process of setting up a Jenkins box, its not
> too
> complicated.  I recommend running it on Debian/stable.  The first question
> to
> ask about your Jenkins box is whether you want to use it for build feedback
> and tests only, or whether you want to make trusted builds from it.  I
> would
> not trust a public Jenkins to make release builds, period.  Its not secure
> enough.  A public Jenkins might be OK to make public test builds, if its
> closely watched.  We need our Jenkins to produce trusted test builds, so
> its
> not publicly available.
>
> We have heard about the possibility of having a private Jenkins instance
> sync
> its info with a public Jenkins instance, so you can have the best of both
> worlds.  We hope to try this out some day in the not too distant future.
>
> That said, at this point running the MeshTether job is basically zero
> pressure
> on our build server or me.  Once its setup, it mostly just runs.  I have
> found
> that using build slaves to be the opposite though, they can be quite
> unstable.
>
> .hc
>
> On 07/23/2013 07:42 PM, Will Hawkins wrote:
> > Hey Hans!
> >
> > Thanks for getting this set up on your build server. We now have
> > Jordan back in the office (he's back from his school year at Stanford)
> > and he is leading the charge to get our build server up and running.
> > We've got all the physical components here and they are going to go
> > online in the next few days.
> >
> > If possible, we'd like to replicate your MeshTether build system on
> > that server. That will relieve some pressure on you from having to
> > host it and it will give us a good sense of the Jenkins system and its
> > configuration.
> >
> > Would you be willing to help us do that? I know you've spent lots of
> > time working with Jenkins and we could benefit from your expertise.
> >
> > Thanks so much!
> > Will
> >
> > On 07/23/2013 02:05 PM, Hans-Christoph Steiner wrote:
> >
> >> Hey all,
> >
> >> I've added Commotion MeshTether to the official Guardian build
> >> server, this is a hardened build server that we use to make
> >> automatic, trusted test builds. The box itself is not publicly
> >> online, but it posts its results here:
> >
> >> https://guardianproject.info/builds/CommotionMeshTether/
> >
> >> I recently did some work to get it closer to building straight from
> >> git.  It will now automatically build whenever anyone pushes a
> >> commit, and if there is a problem, it will email the email
> >> addresses found in the commits.
> >
> >> I just got it building, but I haven't tested it at all.  Feedback
> >> appreciated. I'd like to add MeshTether to F-Droid to get it out
> >> there.
> >
> >> .hc
> >
> >
> >
> >> _______________________________________________ Commotion-dev
> >> mailing list Commotion-dev at lists.chambana.net
> >> https://lists.chambana.net/mailman/listinfo/commotion-dev
> >
> >
>
> --
> PGP fingerprint: 5E61 C878 0F86 295C E17D  8677 9F0F E587 374B BE81
>
>
> _______________________________________________
> Commotion-dev mailing list
> Commotion-dev at lists.chambana.net
> https://lists.chambana.net/mailman/listinfo/commotion-dev
>
>


-- 
Ben West
http://gowasabi.net
ben at gowasabi.net
314-246-9434
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.chambana.net/pipermail/commotion-dev/attachments/20130724/b88848be/attachment.html>