Starting a new CI test

I just added a cheaty way of getting started on a new CI test. $ make new-assess name=new_feature With 'new_feature' as the name you want for your test. This generates a new test script, and some unit tests to go along with it, which you can run as normal with: $ make test p=*new_feature* The

gomaasapi moved to github

The gomaasapi project has been moved from launchpad to the juju organisation on github: As part of this, the project is using the standard juju gating, so add the magic string $$merge$$ to a github comment after review to merge. Martin -- Juju-dev mailing

Re: 1st time builder

Usually if there are compile time issues, it's because you haven't run godeps yet. Make sure you've done the steps under this section of the docs: https://github.com/juju/juju/blob/master/CONTRIBUTING.md#godeps go-get by default pulls from the head of every git repo, but to keep our builds

Re: Starting a new CI test

That is amazing and awesome. Thanks, Martin and everyone else who helped with this! Lowering the barrier of entry to writing CI tests can only be a good thing. On Thu, Dec 17, 2015 at 1:00 PM Martin Packman wrote: > I just added a cheaty way of getting started on

1st time builder

I am attempting to build juju for the 1st time using the instructions at https://github.com/juju/juju and appear to have all the dependencies installed. I am using golang 1.5. I have searched this month¹s mailing list archives (juju and juju-dev) and googled the symptoms and got nothing. I am