Hi, Jose
Thanks for the hint. Should RELEASE_VERSION be *`1.0`* or *`danube.1.0`*.
It seems the release name is automatically prefixed in jjb.
# Get tag version
echo "Current branch: $BRANCH"
if [[ "$BRANCH" == "master" ]]; then
DOCKER_TAG="latest"
else
if [[ -n "${RELEASE_VERSION-}" ]]; then
release=${BRANCH##*/}
DOCKER_TAG=${release}.${RELEASE_VERSION}
# e.g. colorado.1.0, colorado.2.0, colorado.3.0
else
DOCKER_TAG="stable"
fi
fi
On Sat, Apr 1, 2017 at 1:52 AM Jose Lausuch <[email protected]>
wrote:
> Hi,
>
>
>
> I did it manually from the latest built “stable” image when I tagged the
> repo. The Jenkins job we have allows you to do that automatically
> specifying the tag in the RELEASE_VERSION field (see below).
>
>
>
> You might need rights in Jenkins to run this job. If you have problems let
> me know and I can trigger the build for you.
>
>
>
>
>
>
>
>
>
> *From:* Yujun Zhang (ZTE) [mailto:[email protected]]
> *Sent:* Friday, March 31, 2017 17:22 PM
> *To:* Jose Lausuch; TECH-DISCUSS OPNFV
> *Subject:* Re: [opnfv-tech-discuss] [Functest] Tagging and docker build
> completed for Danube.1.0
>
>
>
> Hi, Jose,
>
>
>
> When will the docker build with tag be triggered?
>
>
>
> Besides tagging in git, is there anything else required to make it
> happen?
>
>
>
> On Fri, Mar 31, 2017 at 10:44 PM Jose Lausuch <[email protected]>
> wrote:
>
> Hi,
>
>
>
> Functest repo ready with tags:
>
> danube.1.0 :
> https://gerrit.opnfv.org/gerrit/gitweb?p=functest.git;a=tag;h=refs/tags/danube.1.0
>
> danube.1.RC1:
> https://gerrit.opnfv.org/gerrit/gitweb?p=functest.git;a=tag;h=refs/tags/danube.1.RC1
>
>
>
> Docker image built with tag “danube.1.0”
>
> https://hub.docker.com/r/opnfv/functest/tags/
>
>
>
>
>
> Thanks,
>
> Jose
>
> _______________________________________________
> opnfv-tech-discuss mailing list
> [email protected]
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
> --
>
> Yujun Zhang
>
--
Yujun Zhang
_______________________________________________
opnfv-tech-discuss mailing list
[email protected]
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
