I'll be attending Devops Days 2015 here in my back yard of Pittsburgh PA.
http://www.devopsdays.org/events/2015-pittsburgh/
If anyone is attending, feel free to hit me up and we can sync at the
conference. Perhaps you're doing something interesting with Juju that we'd
love to talk about :)
At
On 12 August 2015 at 05:02, Jeff Pihach jeff.pih...@canonical.com wrote:
Version checking for features can be dangerous because a commands output or
availability may change in the future and now your charm also needs a
max-version, or version-range etc. A more robust solution could be
Small comment while mentioning charm-helpers:
What I would really like to see is the project's tests running in CI,
before things start moving around. The last few times we ran them we
discovered many were broken (I suspect people need to put out fires
and don't bother running the tests before
I personally don't care where the CI runs, as long as it runs :)
Adding to that, it should run *for every merge proposal*, not just on
trunk (when it's too late). Travis is a time and cost effective way to
achieve this, but I'd be more than happy with whatever alternative
solution.
- Chris
On
On 12 August 2015 at 03:56, Tim Penhey tim.pen...@canonical.com wrote:
It would be trivial for the Juju version to be exported in the hook
context as environment variables.
Perhaps something like this:
JUJU_VERSION=1.24.4
JUJU_VERSION_MAJOR=1
JUJU_VERSION_MINOR=24
JUJU_VERSION_PATCH=4
#
On Wed, 12 Aug 2015 at 12:12 Marco Ceppi marco.ce...@canonical.com wrote:
Working with the Juju QA team to add a Jenkins job for test landing is a
great idea, one we should certainly do now while we figure the rest of this
out.
FYI there's an already an outstanding request with Juju QA team
On Wed, Aug 12, 2015 at 7:17 AM Adam Collard adam.coll...@canonical.com
wrote:
On Wed, 12 Aug 2015 at 12:12 Marco Ceppi marco.ce...@canonical.com
wrote:
Working with the Juju QA team to add a Jenkins job for test landing is a
great idea, one we should certainly do now while we figure the
On Wed, Aug 12, 2015 at 6:11 AM Stuart Bishop stuart.bis...@canonical.com
wrote:
On 11 August 2015 at 20:42, Marco Ceppi marco.ce...@canonical.com wrote:
# Trimming down charm-helpers
The first item, and arguably the largest is a complete reorganization of
the
current charm-helpers
+ 1. https://bugs.launchpad.net/charms/+bug/1478771 Apache Flume HDFS
+ 2. https://bugs.launchpad.net/charms/+bug/1478770 Apache Flume Syslog
+ 3. https://bugs.launchpad.net/charms/+bug/1478772 Apache Flume Twitter
All three were quality releases, and have been promulgated to the charm
store.
