projects / osm / devops.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 32b38a0) | patch
Use branch for charms 40/12840/1
authorMark Beierl <mark.beierl@canonical.com>
Thu, 12 Jan 2023 20:14:58 +0000 (15:14 -0500)
committerbeierlm <mark.beierl@canonical.com>
Mon, 16 Jan 2023 19:11:29 +0000 (20:11 +0100)
commitc3b743fef37b15333203d81f464a474199d18e1e
tree5974d1a097a4a7a5c67d0cca3535011b6afc9f22tree | snapshot
parent32b38a0d121a70a53446c3c8ed017986b223bec3commit | diff
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>
(cherry picked from commit 27da38deb3b184608a6d66ab6bc476506d8d7301)
jenkins/ci-pipelines/ci_stage_2.groovy diff | blob | history