Thanks for the hint. I find the debug-hooks documentation opaque. Some worked
examples would be good.
(I seem to recall something in a video I saw—I’ll go back and look for it).
Where is the new window created? Presumably on the server I’m
debugging—jenkins in my case. The one I saw ‘locally’ was an ssh session into
that machine (it looks like). Of course, since I’m ssh’ing into the machine
that runs the juju commands anyway, I’m running two steps away from it!
I re-executed the {remove,add}-relation commands (in another shell on my juju
host) and nothing happened in the window. What am I doing wrong?
Steve Powell
On 8 Jan 2014, at 13:03, Maarten Ectors <[email protected]> wrote:
> Hi Steve,
>
> You can do "juju debug-hooks jenkins/0". This will open a terminal. When you
> retry applying the relationship then you will see that the "hooks" are called
> in your debug window. By executing "hooks/name-of-the-hook" you can see what
> is going wrong.
>
> I included Antonio and Jorge from the Juju solutions team who are working on
> making sure our existing charms work out of the box.
>
> I also included Evan who is leading the Ubuntu CI team. His team is drying a
> lot of the developments around Jenkins and you should see many improvements
> coming soon...
>
>
> Thanks,
> Maarten Ectors
> Cloud Strategy Director
> Changing the Future of Cloud
> Ubuntu <http://ubuntu.com> / Canonical <http://canonical.com> UK LTD
> [email protected]
> Fixed: +44 (0) 207 630 2435
> Mobile: +44 (0) 791 860 8145
>
>
>
> On Wed, Jan 8, 2014 at 11:47 AM, Steve Powell <[email protected]> wrote:
> Hi,
> I’m a new user of juju, and am setting up a Jenkins instance and couple of
> slaves on ec2.
>
> Can anyone point me to some doc for the charms jenkins and jenkins-slave that
> explain the settings and/or config?
>
> I have issued the following commands (in this order — with suitable pauses to
> wait for completion):
>
> $ juju deploy jenkins
> $ juju deploy -n 2 jenkins-slave
> $ juju add-relation jenkins jenkins-slave
> $ juju set jenkins password=……
> $ juju set jenkins-slave tools="git gcc make bzr mercurial erlang"
> $ juju expose jenkins
>
> I can see the jenkins dashboard and log in with admin password, as expected.
> However, there are no slaves ‘connected’ to the master.
>
> There is a worrying message in status:
>
> services:
> jenkins:
> charm: cs:precise/jenkins-8
> exposed: true
> relations:
> master:
> - jenkins-slave
> units:
> jenkins/0:
> agent-state: error
> agent-state-info: 'hook failed: "master-relation-changed"'
> agent-version: 1.16.5
> machine: "1"
> open-ports:
> - 8080/tcp
> public-address: ……
>
> Which makes me think the relation wasn’t added correctly. Removing the
> relation and re-applying it seems to make no difference to the status at all
> (the error agent-state is there at all times).
>
> How do I find out what is supposed to happen and what has actually happened?
>
> Steve Powell
>
>
> --
> Juju mailing list
> [email protected]
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
>
--
Juju mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
