Additionally, the bot is no longer reporting back to the PR that the build failed to merge.
On Mon, Jul 7, 2014 at 11:11 AM, David Cheney <david.che...@canonical.com> wrote: > The lander is broken > > + exit 0 > All passed, sending merge > /tmp/hudson6791049747065303228.sh: line 44: > /home/ubuntu/jenkins-github-lander/bin/lander-merge-result: No such > file or directory > /tmp/hudson6791049747065303228.sh: line 44: > /home/ubuntu/jenkins-github-lander/bin/lander-merge-result: No such > file or directory > Build step 'Execute shell' marked build as failure > Description set: davecheney 128-update-ssh-terminal > > On Sat, Jul 5, 2014 at 9:56 PM, Martin Packman > <martin.pack...@canonical.com> wrote: >> I have switched the jenkins landing bot to a new job, as part of the >> work on getting it faster and more reliable. If you want to check back >> on old results, they are preserved for now under a different job name: >> >> <http://juju-ci.vapour.ws:8080/job/github-merge-juju-old/> >> >> I'm actually having second thoughts in writing this, maybe just >> renaming the job to keep the links in existing prs correct would have >> been better. I can still do that if anyone has strong opinions. >> >> Martin >> >> -- >> Juju-dev mailing list >> Juju-dev@lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju-dev -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
