Age | Commit message (Collapse) | Author | Files | Lines |
|
Docker image building script opnfv-docker.sh tries to remove existing
images before and after building. It simply uses grep to matching image
names, which may cause partial name matching problems.
Ex. opnfv/compass-tasks will match both opnfv/compass-tasks and
opnfv/compass-tasks-base, and may lead to accidentally removing of
images still in use when several building tasks run concurrently.
Error log:
https://build.opnfv.org/ci/job/compass-tasks-build-arm64-master/6/console
Change-Id: I1a83f801c5e0cc889cd9e17b8d1b4d895f1f68a9
Signed-off-by: Yibo Cai <yibo.cai@arm.com>
|
|
When manually triggering a docker job (or even through timed builds),
GERRIT_EVENT_TYPE will not get set. This does gets set when the job is
triggered by a Gerrit event (ex: ref-updated, comment-added).
Specifying the variable lookup to default to nothing (ex: "${FOO:-}")
should allow non-Gerrit triggered jobs to complete successfully.
Change-Id: Ic1ba8ebef0967b0f20a2d6385ce0e0b4876901dc
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Builds triggered by tags have a typo in the extraction of the tag name.
This change includes a method for retriggering a tag build with the
comment "retag TAG_NAME".
Change-Id: Ie035e0922f8c073d3e360917ea7ccd6fa76d7b20
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: I534c14f4415c16661fb95966077621497c6f9cdc
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
Its helpful to know which version of docker is being used to build a
project when debugging build failures.
Change-Id: I2bb9c5386d1d69e61c4477913f5f0162acd0c47d
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
Facilitates the creation of docker images from tags pushed to Gerrit,
which should remove the need to manually trigger 'tagged' builds.
Fixes a typo in the 'gerrit-trigger-tag-created' macro,
replaces 'RELEASE_VERSION' with 'GERRIT_REFNAME', and adds the
tag-trigger to docker builds.
Change-Id: I6d8f8f34b1c51d74bb98211dfae21c37cf9356fa
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: Iab40fc2c719050d36a614fe529ca22634b59b7bc
Signed-off-by: Yujun Zhang <zhangyujun@gmail.com>
|
|
This is required for StorPerf multi-arch and causes all the StorPerf
ARM builds to fail if it is not present.
Change-Id: I302c0471a52759cd9c051741e2b0bb086b87e8eb
Signed-off-by: mbeierl <mark.beierl@dell.com>
|
|
JIRA: COMPASS-567
Add compass4nfv-docker.yml
compass-tasks-k8s and compass-tasks-osa are dependent on compass-compass-tasks.
So we have to phase to build docker images
phase 1. execute the multijob 'build compass-tasks images'
Only the phase 1 is successful then excute the phase 2
phase 2. execute the multijob 'build all compass images'
Modify the opnfv-docker.sh
1. Add a function remove_containers_images
2. call the remove_containers_images when beginning and finishing build
to solve the problem of rmove of images due to dependancy
Change-Id: I66fb27260cf114da96417361e80c8183db3233bd
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
Change-Id: I955479b8bc33c4a7445292901aa4228a413aa4c1
Signed-off-by: Delia Popescu <delia.popescu@enea.com>
|
|
CHANGE: Obsolete "Dockerfile.aarch64" support,
only "Dockerfile.$(uname -m).patch" mechanism is to be used
from now on.
It is correlated with https://gerrit.opnfv.org/gerrit/#/c/46797/
Change-Id: If765550681d283dea7e3522f21080ea2c5e2fda4
Signed-off-by: Delia Popescu <delia.popescu@enea.com>
|
|
Change-Id: I3c4d71239dfe66773931f5f5b9349faab443aa2d
Signed-off-by: Jose Lausuch <jalausuch@suse.com>
|
|
There is a possiblity of multiple docker builds of a docker repo being
scheduled on the same host:
1) Patch is merged
2) Docker build is triggered
3) New patch is merged before the Docker build/push finishes triggering
a second build
4) First build fails as second build starts by cleaning image from
first build
Reintroducing the check for builds in progress, but specific to the
Docker repo, should allow mulitiple Docker builds on a node to run,
while keeping multiple builds on a per-repo basis from thrashing each
other.
JIRA: RELENG-315
Change-Id: I74c01850a036c831b93a8cd5fa8522337abb9ff4
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
The docker build script will only allow one docker build at a time. As
docker builds are now restricted to one per-node by project through the
throttle-build plugin, this restriction can be lifted.
JIRA: RELENG-315
Change-Id: I4c430f99eaaed831fa0c49284280a8fa9fbe13c8
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Jenkins does not set ARCH_TAG to an empty string; instead it does
not set that variable at all when the input is empty.
Fix this by providing a default empty string in the script.
Change-Id: Iec4c38068b1ab3e8dd124f49b36759eedb084f4a
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Enables optional argument to specify the architecture to use
when building and pushing the image. If project defines it,
the arch is added to the docker version like so: arch-version.
This matches the tag convention used by multiarch/alpine.
Change-Id: I699c2aba05c55291b5f8c48bcc1daacceae6154b
JIRA: STORPERF-210
Signed-off-by: mbeierl <mark.beierl@dell.com>
|
|
Instead of defining docker build jobs in terms of projects, we define
them in terms of dockerrepos. Each dockerrepo is associated with a
specific project and may have a seperate Dockerfile (which defaults to
'Dockerfile' if unspecified), and location for files needed by the
Dockerfile (default: 'docker').
This should allow for running multiple docker builds out of a single
project repository without having to modify the current docker build
scripts.
The output of this job configuration should match what is currently in
Jenkins.
Change-Id: I9089d57a0c7cc56be4225b56e96bec56be258f1f
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
JIRA: DOVETAIL-447
this support dovetail to make tag/container snapshot at some
commit id
this will also used for functest/yardstick if needed, since their danube.2.0/3.0
may not satisfy dovetail requirements, while their snapshots at some commit id
satisfy.
Change-Id: I76cf6df586d1c9f0f563c6bfc039e3e271dc3de8
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: DOVETAIL-419
since dovetal has no A/B/C/D branch, only have master,
need docker image name sth like opnfv/dovetail:plugfest_april_2017
rather than opnfv/dovetail:<release>.1.0, etc.
then when RELEASE_VERSION is empty, generate opnfv/dovetail:latest
ortherwise opnfv/dovetail:<RELEASE_VERSION>
Change-Id: I92573bee35da16305074393401e5e5da65aaa22c
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
By default, if a docker build job triggers and
there is another one running at the same time,
it will abort the job.
This adds a wait method with a timeout to avoid that.
Change-Id: Ica86885c60ce4137c85474ec4b7441ac5bab600c
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
|
|
'RELEASE_VERSION: unbound variable' popped up when building stable docker image
Change-Id: I5d4582aea2f154e0bc34cdccdd05b9df64032ed2
Signed-off-by: helenyao <yaohelan@huawei.com>
|
|
When building an aarch64 docker image an Dockerfile.aarch64 file is
expected to exist. With this patch we may create it from the x86
Dockerfile by applying an aarch64 patch
This feature can be used with qtip, via
https://gerrit.opnfv.org/gerrit/#/c/30185/
JIRA: ARMBAND-219
Change-Id: I71e1e1852e31f92fb1f1947542f7f397b996541f
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
|
|
JIRA: DOVETAIL-354
1)in https://build.opnfv.org/ci/view/dovetail/job/dovetail-compass-baremetal-debug-master/200/artifact/results/dovetail_report.txt
Version isn't correct, version should be obtained from https://git.opnfv.org/dovetail/tree/setup.cfg
2)since dovetail not have A/B/C/D branches such as Danube, no need to set branch parameter
when doing "docker build", if branch parameter settled, the "version" info in setup.cfg will not obtained.
3)related patch https://gerrit.opnfv.org/gerrit/#/c/29045/
Change-Id: I2b2880e417460a4a3da3e108bb83800e2acb3a83
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
If we use tags, when there are remaining images without
the tag <none> it fails and get the following error:
Removing docker image opnfv/functest:<none>...
Error response from daemon: Error parsing reference:
"opnfv/functest:<none>" is not a valid repository/tag
By using IDs we make sure we delete the images.
Change-Id: Ib336dc73168bac909c42dd4a9681ef07d477dc7b
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
Jenkins slave arm-build3 was added to build the docker image on arm
This commit adds jobs to use that jenkins slave.
JIRA: ARMBAND-108
Change-Id: I7b293d119ca3347983940639fe0cfea1098b18f3
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
GIT_BRANCH parameter is different; master or stable/danube in daily
jobs, but 'refs/changes/57/27657/6' in verify jobs. This breaks some
job builders triggered by the both types of jobs. We have GERRIT_BRANCH
parameter for verify jobs to identify stream and expected branch into
the patch will be merged after it got +2 and submitted.
To avoid further confusion and to have common job builders for daily
and verify jobs, this patch introduce BRANCH parameter.
GERRIT_BRANCH is now deprecated.
Change-Id: Ibcd42c1cd8a0be0f330878b21d3011f1ec97043b
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
Change-Id: Iff8145eec8946355fd92ebfeacbc0a7661af4b1b
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
New flag that if it's not empty, it will build the
image with the given tag instead of using master/stable.
These release builds will need to be triggered manually
by a Jenkins user with rights to build jobs.
The respective projects take the responsability to
build the release docker image whenever they
consider it is the right time.
Change-Id: I49b087e80eb134b8b3ddef8399f61eeac9b29619
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
Individual project jobs can now be tested using:
jenkins-jobs test -r jjb/global:jjb/$project
- Rename '.yaml' files to '.yml' so they get checked by the
verify-releng.sh script, and update the script to include checking of
'.yaml' files.
- Move parameter and macro files under new 'global' directory.
Change-Id: I6b74f5d8af2bced3256a7f4a33983df5310511a2
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|