Use branch for charms 36/12836/2
authorMark Beierl <mark.beierl@canonical.com>
Thu, 12 Jan 2023 20:14:58 +0000 (15:14 -0500)
committerbeierlm <mark.beierl@canonical.com>
Fri, 13 Jan 2023 16:06:28 +0000 (17:06 +0100)
commit27da38deb3b184608a6d66ab6bc476506d8d7301
tree5974d1a097a4a7a5c67d0cca3535011b6afc9f22
parentda3c1c0ef7999562fbbcd81e0fff6c2ef632165e
Use branch for charms

When merging changes for charms in a development branch (ie: not v10.0, etc),
we want to publish it to latest/edge/branch-name so that it can be kept
separate from the other branches of development

Change-Id: I8f2ec65057d2029d7cda83b9b607a0474a801455
Signed-off-by: Mark Beierl <mark.beierl@canonical.com>
jenkins/ci-pipelines/ci_stage_2.groovy