On 10 June 2014 11:29, Richard Harding wrote:
> It uses itself to land. Just submit a pull request and it'll get pulled
> into our CI http://ci.jujugui.org:8080/ and I can review/land it.
>
> To update it, you'll have to log into the jenkins server and git pull the
> updated codebase if it was de
It uses itself to land. Just submit a pull request and it'll get pulled
into our CI http://ci.jujugui.org:8080/ and I can review/land it.
To update it, you'll have to log into the jenkins server and git pull the
updated codebase if it was deployed to the jenkins server as a git clone to
start with
I'm happy to make the change and test it, but what's the process for
getting it merged and deployed?
On 9 June 2014 19:22, Andrew Wilkins wrote:
> On Mon, Jun 9, 2014 at 1:39 PM, Menno Smits
> wrote:
>
>> I've noticed that the commit messages for the merges performed by the
>> Juju bot don't i
OK, this has gone WAY beyond any reasonable work for this work item.
I agree that we may well want to change how we store things on disk, but
I won't be doing that for this work. If we are going to do this, and I
can see some benefits of doing it, it needs to be spec'ed out as an
independent piec
I did something like this though I didnt use the python-django charm
https://github.com/battlemidget/juju-apache-gunicorn-django
You may be able to get some ideas from that
On Sun, Jun 8, 2014 at 11:32 PM, Tim Penhey wrote:
> Hi all,
>
> I'm looking at using the subordinate charm method for del
Tim,
Have you reached out to the charm author with these questions as well? That
would be where I would start. They are great questions that deserve an
answer, as I'm sure you're not the only user that will have them. This is
an area that the python-django charm (in series trusty - to be clear and
On 6 June 2014 14:20, William Reade wrote:
Thanks for these very useful and constructive remarks. I now
understand better where the original proposal was coming from.
> On Fri, Jun 6, 2014 at 11:34 AM, roger peppe wrote:
>>
>> On 5 June 2014 23:16, Tim Penhey wrote:
>> >> Addressing the concer
On Mon, Jun 9, 2014 at 1:39 PM, Menno Smits
wrote:
> I've noticed that the commit messages for the merges performed by the Juju
> bot don't include the PR title. This can lead to some slightly odd commit
> logs.
>
> For example, have a look at PR #13. The merge commit (d8a2c54) message
> starts l
