Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
GERRIT_REFSPEC is always passed by the gerrit-trigger plugin when a job
is triggered by Gerrit. Because it is not explicily defined, there is no
way to manually trigger jobs, as the git clone looks up the list of refs
by GERRIT_REFSPEC.
Being able to manually trigger jobs (with node parameters so they can be
restricted) is very helpful in debugging CI issues.
Change-Id: I8a1d9ea380902fc95f30482e5acb616347709ab1
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: I3ca61f015c07cbf3bd67acd7972d9a1e0011f21d
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
1. add macro for report the provision result of installers
and try it in daisy
2. update according to TestAPI interface
Change-Id: Ic041744c917c37fcd84a12a92e927e39106cf18f
Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
|
|
|
|
Change-Id: I5193285493926fcf82779f12d491a118bc83baa7
Signed-off-by: 00184532 <lu.yao135@zte.com.cn>
|
|
In the initial formation of projects we found it easy to copy job
definitions to provide project a baseline job config to work off. This
has led to a lot of duplication and misalignment with the gerrit
triggers and default build server tag to be used.
Collapsing these jobs into a job-group containing the stream and a
verify job per-stream, should help reduce this duplication.
Change-Id: Icb366487590a145be4cbfc0637a8d86a6d9b7cec
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>
|
|
This change takes xci-verify-jobs as base and adjusts osa-periodic
jobs to ensure they do what they are supposed to.
The structure of periodic jobs is pretty similar to xci-verify-jobs and the
differences comparing to them are
- OPENSTACK_OSA_VERSION is set to master.
- SCM type changed to git-scm from gerrit
- Voting is removed.
- Triggering will be done using pollscm to ensure we only run jobs when something
changes upstream. Triggers are not enabled yet until the basics are verified
working.
This change requires https://gerrit.opnfv.org/gerrit/#/c/49275/ in order for
periodic jobs to work as expected.
Further changes are needed to finalize the structure.
Change-Id: I8f6519ccce93e6b8b65509638294419459fd36e8
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: Ifbe959d178781c14a9d32db78d84972d2505c8dc
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
Use an alpine container to mount the pharos_data volume and create a
backup in the home directory on the system.
Change-Id: If6700a8c4cd19a6c4b854efc54225d8f6b973aaa
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Send emails to Serena after weekly Anteater scans on the
releng-testresults repository.
Change-Id: Ic4d61137ea8e30985f5330651e8d2da37b71fca3
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
- Does not output the full scan to the console log
- Updates the email-ext defaults to include any *.log file in the root
of the workspace. This should include securityaudit.log
- Adds 'GERRIT_REFSPEC' to the list of job parameters as required by
'git-scm-gerrit'
- Fixes email-ptl macros so projects with extra repos have the proper
recipients.
Change-Id: Ibf22bf0683fc1f88de07ef3bb4717769c6ea0174
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
Completely replaces the current weekly security scan job. Instead of
publishing weekly security scan reports they will be emailed to
individual project PTLs.
Uses a modified copy of 'anteater-security-audit.sh' to ensure the
security scan job is not affected in this change. A later change will be
made to merge the file back in and update the jobs. This is why
'anteater-parameters' are added to both jobs-templates.
Change-Id: Ia8ebffbfce7a2d4feb83ef68ff0ab0c7bb4d2104
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: I65a2a3c6643cba870eec2f794199bb824c6b868c
Signed-off-by: Delia Popescu <delia.popescu@enea.com>
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
As far as I know the site that consumed this resource was never actually
published, and given this runs frequently on master, removing it should
save resources.
Change-Id: I383fcffcef98e0e12a38d15dcb1204419283b833
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
If one patch don't modify the "yml" or "yaml" file,
the script will exit with 1 at egrep "ya?ml$", then mark build as failure.
In my opinion, if not modify the "yml" or "yaml" file, the yamllint should be successful.
So we need mark the result of egrep "ya?ml$" as true, then judge the $YAML_FILES.
Change-Id: I8abcadc9e4c85935ac7b20cdf54713b9800108ba
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
|
|
JIRA: QTIP-282
Change-Id: If765bfa01a1dab987409c311f3a718bffea76797
Signed-off-by: Taseer Ahmed <taseer94@gmail.com>
|
|
not in a venv, so build fails if called by jenkins user without
sudo
Change-Id: I612a20777cc70a33542f767a63075939782e3201
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
|
|
|
|
old dir is no longer generated
grab dir created by tox -e docs
Change-Id: If52e931f6abdc8dcb39fbe7aac3c6b3342ce81c8
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
|
|
Ready for review (tested locally)
1) remove opnfvdocs-daily-{stream}:
We don't need a timed docs build. and it did not build anything usefull
2) remove opnfv-docs-verify-{stream}:
This uses depreciated and unmaintained opnfvdocs/scripts/docs-build.sh
It does not clone submodules and gives no usefull feedback
but it does post to artifacts and give a gerrit comment
move that functionality to docs-*-rtd-*
3) remove opnfv-docs-merge-{stream}:
does not upload anything meaningful
4) remove macro upload-generated-docs-to-opnfv-artifacts:
is no longer needed since we use read the docs
5) improve docs-verify-rtd-{stream}:
generate single page html and post to artifacts
send gerrit commment with location of single page html,
errors (like malformed table) are embedded nicely in the single
page output and give devs a single source of feedback on their work
6) improve docs-merge-rtd-{stream}:
this job now needs to remove review documenation created by
docs-verify-rtd-{stream}
TODO, after this is merged:
remove now unused opnfvdocs/scripts/docs-build.sh
Change-Id: I802eb11712d42555d34f986d061bf0dfc623c1e9
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
|
|
JIRA: QTIP-280
Change-Id: Ie588c3e38af82fe9b2de8bb01549a1c9249d54ff
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
We should be able to capture a tag creation event by triggering on
'ref-updated' but looking specifically at the 'refs/tags/' branch
prefix.
Though this will trigger a build against a specific tag, scripts will
still need to examine the GERRIT_REFSPEC to determine the tag name.
Change-Id: Ic18a3e11530fb71735431240f93d2074dacf4e1c
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
JIRA: DAISY-9
1. Trigger yardstick job in daisy-baremetal-daily-master on zte-pod3
2. Add daisy pods in yardstick
3. Add EXTERNAL_NETWORK in installer params
Change-Id: Ia8e69e503102c1fb282d6d2c5acac2ac3cbfe747
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
Intead of yamllint all files at once yamllint will only run against new
or modified yaml files.
Change-Id: I10b951427966409e15fb773b959adbd780497bad
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
1.6.0 is quite a bit out of date; Updating Yamllint to 1.8.2 will enable
some nicer feature of yamllint (like single line rule disables).
Change-Id: I88d1c14539516ccef4f5e2e7e95b0017503dd98f
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: Ic2c4a52d58a7fdced5acfb9a706583646af7e56e
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Cleanup some unused parameter overrides, which were never in effect
in the first place. For CI PODs, we inherit only installer specific
parameters, so slave-label based overrides are ignored.
PODs:
- arm-pod5;
- arm-virtual2;
- ericsson-pod1;
- lf-pod2;
This reverts commit bb22c8c02df3e9d030ff64c304536c31b78a37a6.
This reverts commit fc26623f9d7f211a9e29e246a2b13bdae5b3982b.
Change-Id: Iee80ad8357f5126c4aa7510ed66ab6e79c20f3fc
|
|
The external network was renamend with the MCP deploy to floating_net
Change-Id: I73f5f5d14b0b18a2e838dae163dcfd62edcb0c0b
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
Zte-pod2 is a little busy.
Change-Id: I7628a1a966552c5caf1706a2ac8c47952a11c095
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
Disables master daily. Just uses master labels for Euphrates jobs as
well.
Change-Id: I65b0eed528518c07d3ef4194a021004deabe2ed0
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
ericsson-pod1's jump host already has a static IP assigned to its
pxebr, which collides with the mcpcontrol network default settings
used by Fuel@OPNFV.
Instead of changing the existing network configuration on the jump
host to prevent CIDR collision, use a slightly different CIDR,
which is derived from INSTALLER_IP.
JIRA: FUEL-285
Change-Id: Ibea10b3f6528f3b34bc4ab12c3f9131932f6dc84
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
This information was previously fetched from securedlab, via a
POD-specific "local_env" file which was sourced at deploy time.
Since this information can't be parametrized via PDF, nor is it
sensitive enough to hide in securedlab, move it to releng.
Change-Id: Ia4e244ceb534c49b1ecda5be798470a81c68b494
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Add slave params for flex-pod1
Change-Id: I25e93fe2231e604321f8ea7ca18eba45ecc3ee13
Signed-off-by: Siddharth Gogar <siddharth.gogar@flex.com>
|
|
Fuel@OPNFV mcpcontrol network (equiv to old admin/PXE net) has been
configured to use 192.168.10.0/24 during E release cycle.
However, due to overlapping with Ericsson-pod1 networks, we decided
to re-use the old CIDR Fuel used before E release (10.20.0.0/24).
This allows reusing the INSTALLER_IP param instead of recently added
SALT_MASTER_IP param.
Current change refactors all usage of SALT_MASTER_IP in favor of old
INSTALLER_IP, thus reducing complexity and providing a familiar env
to leagcy Fuel users.
JIRA: FUEL-285
Change-Id: I1e89cca08ce4cb9bf3a82a06043c91ee26aa0794
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I34a555697d963efc38064a7b53f25191d6bf1382
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
JIRA: FUEL-280
Change-Id: I95559dcafbd179e5b7305dd0f23a7b3d89056888
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
JIRA: FUEL-278
Change-Id: I9f5496d02097c2a6ae1db73b8a5df20b75ce728d
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
JIRA: FUEL-280
Change-Id: Ia96986e3f289739914de6b7e63abfb0172b8e6b5
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Enable virtual deploy phase for verify multijob for both projects.
Since fuel-defaults already define SSH_KEY param, drop it from
individual jobs.
Fuel:
- drop merge jobs, which used to perform virtual deploys based on
ISO created during verify job;
- cleanup fuel-download-artifact (rm support for merge/verify);
Armband:
- while at it, remove "opnfv-build-enea-defaults", preparing for
arm-build2's retirement.
JIRA: FUEL-278
JIRA: FUEL-287
Change-Id: I354d72d88187e41070f44c723ccc651a0bb9b021
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I134feba421d12c4ca428b098aaa2bf52b3dec0ca
|