Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: Id789121634fc1a009878b61bcf4756ee4009c99d
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
|
|
Moves the jjb-version configuration from globals to releng CI jobs. This
was not being pulled into the '{project-name}-ci-jobs' configuration and
kept our JJB version at 2.2.1.
Change-Id: I33a62e639bbca6d519957515af591615543d27b7
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Has been offline for > 1 week
https://build.opnfv.org/ci/job/functest-core-docker-build-arm64-gambia/
is showing
There are no nodes with the label ‘Job triggered without a valid online
node, given where: arm-build6’)
Change-Id: Ia00281f9c05fac9b16bd914063ccffeca3fb135b
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
|
|
|
|
Change-Id: I36b2f245aa2044ebcdab5122d3b30ae1d9fb1788
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
Change-Id: I2c9c1f042b4b13af58526e23a44680304313cee9
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
A change to the NodeLabelParameter config in JJB caused any jobs using
the plugin to possibly have their jobs triggered on builders which
weren't online.
This in turn caused the queue to backup and newer jobs are blocked
waiting for older ones to complete, which never happens as they're never
queued on an online builder.
The 'all-nodes' parameter ensure jobs that are set to run concurrently
don't trigger across all available nodes at once, as this will include
offline nodes as well. As this is the default of the plugin, projects
which need it can enable it individually.
Change-Id: Ia690eef078209b6b056dad85613dda6868b18271
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Push OPNFV docker builds for clover-ns-modsecurity-crs image
Change-Id: I134108d78d84de8a04bb7372c49314d0491a1248
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
The dockerfile path is relative to the dockerdir, not the root of the
cloned repository.
Change-Id: I7836abf8f15d4d9f14cb8d39bc951ec9341d39ba
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Updates the docker builds for LaaS to share the same context but point
at different Dockerfiles. This way the dashboard code can be copied into
the container instead of requiring to be volume mounted.
Change-Id: I26fe345c8901b772a2e9da56fac71956a8a76583
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Similar to https://gerrit.opnfv.org/gerrit/63177 (done for x86_64).
It replaces the yardstick-docker-build-arm-push-fraser job, for the
same reasons.
Depends on https://gerrit.opnfv.org/gerrit/63179
Change-Id: I482bc05d4c6d1316bfde799a44360decacb60a5e
Signed-off-by: Patrice Buriez <patrice.buriez@intel.com>
|
|
Similar to https://gerrit.opnfv.org/gerrit/63047 (done for x86_64).
Change-Id: Ie61a11c60ce0fd7c724f308ecfdcca982ebdf3ec
Signed-off-by: Patrice Buriez <patrice.buriez@intel.com>
|
|
It replaces the yardstick-docker-build-push-fraser job, because the
logic in jjb/releng/opnfv-docker.sh L106-L119 has limited options for
docker image tags:
- 'latest', for git commits on master branch
- tag-name, for git tags
- 'stable' otherwise, i.e. for git commits on *any* stable branch.
This means we can have only one (stable) job building and pushing
docker images, in order to prevent the 'stable'-tagged image from
switching between fraser and gambia contents, depending on the stable
branch where the most recent change was cherry-picked and committed.
Unfortunately, disabling the yardstick-docker-build-push-fraser job
also means that further git tags on the stable/fraser branch will not
result anymore in building and pushing new docker images with the
intended tag-name and contents.
Change-Id: Ieec1cdc6230e4c000c159cd743c587561c788fc3
Signed-off-by: Patrice Buriez <patrice.buriez@intel.com>
|
|
|
|
LaaS is using the upstream rabbitmq container now, so there is no need
for this build.
Change-Id: I08d2dc07eb6cd9cc732b25fd6dee2f342117d857
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
- Push OPNFV docker builds for clover-controller, clover-collector,
clover-jmeter-master and clover-jmeter-slave.
Change-Id: I9541f9ca5e368c5e2ee833ce85948716f5dd66db
Signed-off-by: earrage <eddie.arrage@huawei.com>
|
|
Change-Id: Iac803fe18e6c1fcfcefb61dfb7ea03cbed5a51d1
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
This node has permissions for Google Storage to upload the archive while
master does not.
Also adds myself to list of recipients so I'll get notified when the job
fails.
Change-Id: I07a13dcc72c59854222f6e5ace9d1e18c24e6479
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Adds jobs for building the following LaaS containers:
- opnfv/pharos-tools-laas-dashboard
- opnfv/pharos-tools-laas-celery
- opnfv/pharos-tools-laas-mq
Having these containers built seperately from docker-compose decouples
the build and deployment phases for the dashboard.
Change-Id: I919066f5defd02fe1bbf96cfdf8ec2a6b3d8757d
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
This is still far from a clean and secure approach, as `pip install`
should not be ran with `sudo`.
However, `-H` limits the area we touch and also fixes some incompat
between disto-provided pip and pip-provided pip.
Change-Id: I0e19dfeaf66f6f453e3868c71016305ae050f0c8
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: Ic54f6fe21dc0e9d2b3a9a2f3db1ba82f08446b6c
Signed-off-by: xudan <xudan16@huawei.com>
|
|
Previously we created the branches over Gerrit's HTTPS interface. One or
two projects from the previous release did not have their stable
branches created at the correct place.
Switch to using ssh for branch creation will be more reliable and easier
for us to verify.
Change-Id: If7f24d2b19e74513b59889bd64d25919aa048e4c
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
* changes:
Create Gambia and Hunter Release Jobs
Create stable/hunter Branch for Functest repos
|
|
This will create the release jobs needed for the OPNFV Gambia
and Hunter stable-stream release process.
Change-Id: Icdb9a337dcbad26fccb0e1e2935f8082f17bb220
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
JIRA: RELENG-408
Change-Id: Ie6ac842ebd1bb6264c88a7f8ee0446d76fc3dbdd
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
|
|
|
|
As these only affect jobs defined in global-jjb (no other jobs used
these variable names) they should be safe to define at the global level.
Change-Id: I646c3afc73757bff561cc84b80df064e13680080
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: Iac612137bd4b1a45550849c3180525cfe74f4a7f
Signed-off-by: Junaid Ali <junaidali.yahya@gmail.com>
|
|
|
|
When the ansible-build-server job runs it helps to know which job ran on
which server without clicking through to the job description.
Change-Id: I2d5ef3b843fc839c8706837c74f00503de8808d5
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Sometimes the docker build fails and the docker process hangs on a container,
withouth being able to stop it. This causes spurious failures on other builds
that shouldn't fail. The prune job should cleanup the hanging containers and
images, but it fails when the docker process is hanged.
This change adds a docker restart to the prune job, in order to assure that the
hanged container is shut down and can be removed.
JIRA: ARMBAND-358
Change-Id: I9d04fa1099a6fc53bf773a2eba33be89db7d0aa1
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
Add 2 docker build jobs for the new repo dovetail-webportal.
One is dovetail-webportal-api, the other is dovetail-webportal-web.
Once there is a new patch merged, it will auto trigger the jobs to build
and upload the new docker images with tag 'latest'.
According to the Dovetail release plan and develpoment of the web, can tag
this repo and release with certain tag (e.g. ovp.2.0.0)
JIRA: DOVETAIL-671
Change-Id: I1becc084617bb52f8c8e23275202bd7be4a7b2b3
Signed-off-by: xudan <xudan16@huawei.com>
|
|
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>
|
|
git cat-file can't output the tag information for a tag, but it can
output the commit information a tag points to.
Change-Id: I147941e2c0ba6defe212dbd0fc8c8a3a1fe0c728
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
This was incorrectly set to GIT_BASE, which includes the Project name,
and should be set to GIT_URL, which does not. GIT_URL is used instead as
each release file can contain multiple repos.
Change-Id: I82b5e80f20f8999745cb5008c8057c81c4993574
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
|
|
By default the rtd jobs from global-jjb trigger against all projects.
Setting 'project-pattern' to releng will restrict it to just the releng
project.
Change-Id: I9586577e8d83c6bf189eaee9159b1e49726740a5
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
When the release job runs to tag the repos it should push the tags back
to Gerrit. This was originally a 'noop' for testing.
Change-Id: Ifbecbccda1ae123c7b8f0d59eefa727784d10acd
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
These jobs come from global-jjb[1]. On verify, 'tox -e docs' is ran
against releng, and on merge at webhook it curl-ed on RTD to build the
docs.
The merge job additionally requires jq installed to verify the build was
triggered.
[1] https://docs.releng.linuxfoundation.org/projects/global-jjb/en/latest/jjb/lf-rtd-jobs.html
Change-Id: Ib0d752a904a9fdda2ab13016509a0b82d34ec3ee
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
|
|
|
|
After an empty repo is cloned, and we attempt to pull in changes, git
fails due to not know which branch to pull from. Explicitily pulling
from origin into master should resolve this.
Change-Id: I6bed85779c1bb571559c263800e8ea55ece3aa62
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Use default $DOCKERFILE setting from downstream projects.
Change-Id: I0bfee5dcaef9a9eb7601548a1e5da5a5f8d51bb5
Signed-off-by: Yibo Cai <yibo.cai@arm.com>
|
|
Error log: https://build.opnfv.org/ci/job/compass-tasks-base-build-arm64-master/1/console
Change-Id: I47ef2ede64d63fb3e9a500dc48cdd510ee9ff235
Signed-off-by: Yibo Cai <yibo.cai@arm.com>
|
|
In order to support additonal features that have been added to
collectd since the 5.8 release, there needs to be a separate
stable and master container so we can support the new features
as well as the stable release.
This change will allow us to increment the version of collectd
as we add functest support, config guides and documentation,
while keeping the stable version container intact and available
for users to download.
JIRA: BAROMETER-102
Change-Id: I06ca84581a2e0f1a994cedf53aebc8f5cc3e7535
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
|