Age | Commit message (Collapse) | Author | Files | Lines |
|
as helm3 binary is no more available, helm repo init script must use
`$HELM_BIN` retrieved from prop file.
Issue-ID: OOM-1
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I56de1ddf62488ef8bd0b4a177263adeeb5149947
|
|
|
|
chartmuseum was killed by Jenkins when launched. By moving it's outputs
to /dev/null, it's no longer the case.
Issue-ID: OOM-1
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: Ie358e73a498106ac3abf3731f47a1cb8f01deace
|
|
Stable repo is not the right one and we also don't need it here for
linting.
So let's remove it at start.
Issue-ID: OOM-1
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I2cdd105bf40c588bcea536fcb4af54ba54cdac14
|
|
it seems that chartmuseum may block if place where it stores the results
is not fast enough.
We then create a small ramdisk in order to store these.
Issue-ID: OOM-1
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I36cad6e56f9390bb058beea08df0bf51eda97a09
|
|
|
|
As OOM supports helm2 and helm3, it's important to check that all new
additions don't break helm3 support.
Issue-ID: OOM-1
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I38307e3b105606eb3dded1933e3a90673078d4dc
[Add helm3 job template boilerplate]
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
|
|
When a release is created, we want to make and push the charts to a
place where everybody can retrieve them instead of making them in their
side.
Issue-ID: OOM-1238
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: Ibedfe874c76d4ae11f3f759737e550ba0e5e3d33
|
|
Publisher aimed at printing Docker Compose services
info at post build stage.
Change-Id: Iacad5239243101b91c2aa3d10017748f95b10bcb
Issue-ID: INT-1508
Signed-off-by: Bartek Grzybowski <b.grzybowski@partner.samsung.com>
|
|
Zipp just added a hard check for py36. This pins zipp to a version
that still works with py35.
Issue-ID: CIMAN-33
Change-Id: I01d20fb9cf7a5de6a4f78750b3ee71116dd674bb
Signed-off-by: Anil Belur <abelur@linuxfoundation.org>
|
|
|
|
Executing releasedockerhub command in lftools every week,
to ensure that not to many docker images needs to be copied every
time, as well as to keep cost down.
Signed-off-by: Bengt Thuree <bthuree@linuxfoundation.org>
Change-Id: I2ccdc236910960b3af3c1f6f1f0c5db062538c9c
Issue-ID: CIMAN-1
|
|
Related to RELENG-2422
Change-Id: I7d6a99a7fee7eb5a1db2879ecb4398640b836a20
Signed-off-by: Vijay Venkatesh Kumar <vv770d@att.com>
Issue-ID: DCAEGEN2-1893
Issue-ID: DCAEGEN2-1862
|
|
The python environment variable for virtualenv should be
$PYTHON not $PYTHON_VERSION.
Issue-ID: CIMAN-1
Signed-off-by: DW Talton <dtalton@contractor.linuxfoundation.org>
Change-Id: I975bc16efd572ae56b003fde134bed82178de6ff
|
|
Issue-ID: CIMAN-260
Signed-off-by: Artem Naluzhnyy <A.Naluzhnyy@samsung.com>
Change-Id: I6b02c57f03b6b8ff9576924e712ed517225822de
|
|
This is to avoid static code analysis of the Coverity Scan toolset itself.
Issue-ID: CIMAN-260
Signed-off-by: Artem Naluzhnyy <A.Naluzhnyy@samsung.com>
Change-Id: I32b6a42ce455ab5f7f5334921f6fde7e41d919f2
|
|
To save our Jenkins lab resources and Coverity Scan submission quota we
can run the scan if there were recent commits only.
At the moment the following JJB configuration does not work properly for
ONAP repositories:
triggers:
- pollscm:
cron: '@daily'
As a workaround a new job build parameter is introduced -
'max-git-repo-age-hours'. If set to non-zero run the code scan only if
there were no git repository commits last max-git-repo-age-hours hours.
It makes sense to set the value twice the 'cron' interval for the job
(e.g. if 'cron: @daily', then max-git-repo-age-hours=48).
Issue-ID: CIMAN-260
Signed-off-by: Artem Naluzhnyy <A.Naluzhnyy@samsung.com>
Change-Id: I82ce092e9b8bb423e9db8b3958d6cfa3b527b33b
|
|
Now the Jenkins job parameters are configurable on the WEB since it's
usefull for initial Coverity Scan job setup or tuning process.
Issue-ID: CIMAN-260
Signed-off-by: Artem Naluzhnyy <A.Naluzhnyy@samsung.com>
Change-Id: I6f2f59416966233c24c1b6bc1847d4ebe19a6985
|
|
The Jebkins job parameter can be used during Coverity Scan job initial
configuration or tuning process to avoid unnecessary submission quota
exhaustion.
Issue-ID: CIMAN-260
Signed-off-by: Artem Naluzhnyy <A.Naluzhnyy@samsung.com>
Change-Id: I4dfdf7441b8f31fffa2e4afd62bdd871126cdfd5
|
|
"cov-int/scm-untracked-files.txt" info may be used as a source for
'coverity-search-exclude-regexs' JJB config option to suppress analysis
of external 3rd-party and auto-generated sources.
Issue-ID: CIMAN-260
Signed-off-by: Artem Naluzhnyy <A.Naluzhnyy@samsung.com>
Change-Id: Ief208e3ac202f5494e9762902f0930890d8c01d8
|
|
Re-implement temporary(?) non-functional filter to ignore specific source
code parts by Coverity Scan using "--fs-capture-search-exclude-regex" CLI
parameter of "cov-build" tool. This functionality is important to
filter out e.g. node_modules or src/tests. Instead we can remove all
specified files after we got local build results but before we send them
to Coverity server.
Issue-ID: CIMAN-260
Signed-off-by: Artem Naluzhnyy <A.Naluzhnyy@samsung.com>
Change-Id: I1175b593966a8b8732aa3f6841e9c450766de752
|
|
Since the build process takes a lot of time and resources on our Jenkins
executors it had better try to resubmit our results to Coverity Scan
server if it replies with non-200 HTTP response.
Issue-ID: CIMAN-260
Signed-off-by: Artem Naluzhnyy <A.Naluzhnyy@samsung.com>
Change-Id: I8fd24d9f4f6181ff6e0817914ac649a140706b7e
|
|
Two JJB project parameters have been introduced:
* 'coverity-search-paths' - space separated list of paths that contain
source code to analyse;
* 'coverity-search-exclude-regexs' - space separated list of file name
regexps to exclude from analysis.
Example:
project:
name: 'sdc-coverity'
jobs:
- onap-gerrit-maven-coverity
...
coverity-search-paths: 'catalog-ui/src/ openecomp-ui/src/ dox-sequence-diagram-ui/src'
coverity-search-exclude-regexs: '/node_modules/'
Issue-ID: CIMAN-260
Signed-off-by: Artem Naluzhnyy <A.Naluzhnyy@samsung.com>
Change-Id: I8050a75a731c893ec2173f66d2e881fcc0877ed0
|
|
The list is stored in "cov-int/coverity-scan-analysed-files.log".
Issue-ID: CIMAN-260
Signed-off-by: Artem Naluzhnyy <A.Naluzhnyy@samsung.com>
Change-Id: Id27cb466977e0bd11e004fd819f66697ca16c26b
|
|
Issue-ID: CIMAN-260
Signed-off-by: Artem Naluzhnyy <A.Naluzhnyy@samsung.com>
Change-Id: I73dae5c4c5bd3dd73957809b4265009b529ebca0
|
|
Check if we are allowed to submit results to Coverity Scan service and have
not exceeded our upload quota limits. See also: https://scan.coverity.com/faq#frequency
Issue-ID: CIMAN-260
Signed-off-by: Artem Naluzhnyy <A.Naluzhnyy@samsung.com>
Change-Id: I71479cfdd8403e717e6c807a8afb5aadad25fdde
|
|
"onap-gerrit-maven-coverity" JJB template runs 'mvn clean install' and then
publishes results to Coverity Scan service for static code analysis.
Usage example:
- project:
name: so-coverity
jobs:
- onap-gerrit-maven-coverity
cron: '@daily'
build-node: 'ubuntu1604-builder-4c-4g'
project: 'so'
project-name: 'so'
branch: 'master'
mvn-settings: 'so-settings'
mvn-goals: 'clean install'
mvn-opts: '-Xmx1024m -XX:MaxPermSize=256m'
mvn-params: '-Dmaven.test.skip=true'
coverity-project-name: 'onap-so'
coverity-token: 'PUT COVERITY TOKEN HERE'
coverity-user-email: 'PUT USER EMAIL HERE'
Issue-ID: CIMAN-260
Signed-off-by: Artem Naluzhnyy <A.Naluzhnyy@samsung.com>
Change-Id: I6f4fa6359b5be91932c5a1a1ed7ba0a4068ac152
|
|
This new verify job will:
- Apply to code transfered outside OOM repo into the
tech team's repos.
- Get triggered by any submitted changes in
<component>/oom repos.
- Apply the change in oom/kubernetes/<component>
- Run a helm verify
Change-Id: I4bd60f946351623583589d7689343fbfc826237a
Issue-ID: CIMAN-250
Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
|
|
Issue-ID: CIMAN-223
Change-Id: Ieeaf53ef868ee60f30427d6bce6a7d44a5c4d9fd
Signed-off-by: Jeremy Phelps <jphelps@linuxfoundation.org>
|
|
Issue-ID: CIMAN-164
Change-Id: Iae6f765c2f8a7953a308f2ce81e79e4f633a1a2e
Signed-off-by: Jeremy Phelps <jphelps@linuxfoundation.org>
|
|
Issue-ID: CIMAN-164
Change-Id: I020e408c98af2b5ed3f50661f70b7fe2b2912199
Signed-off-by: Jeremy Phelps <jphelps@linuxfoundation.org>
|
|
ONAP community is not using the a separate repo for
storing snapshot and staging artifacts. The change
parameterises the docker build to be able to separately
control the target repository and the build artifact type
(snapshot / staging). It will also store the staging and
snapshots in the same repo (10003).
Change-Id: I505023a7cdab90fa8ecfeb540f6306f0e19c3d6d
Signed-off-by: Denes Nemeth <denes.nemeth@nokia.com>
Issue-ID: VFC-728
|
|
Change-Id: Ic9c47ab3792db1cd52f2a11d94d2d4414aef507b
Signed-off-by: Denes Nemeth <denes.nemeth@nokia.com>
Issue-ID: VFC-728
|
|
Fix Pypi build and publish scripts to run
virtualenv with the correct PYTHON_VERSION
specified in the job templates.
Change-Id: I71f61775380ae56c204854ddde254b467e5e16f3
Issue-ID: Issue-ID: CIMAN-137
Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
|
|
Global variables defined in Jenkins need
double quotes to be translated properly in the case
section.
Change-Id: Ida76cd90314ef59f24013f7da80a2b5364fc9480
Issue-ID: CIMAN-132
Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
|
|
Fix typo on variable used to extract the IMAGE_VERSION
number
Change-Id: I91d48836d697c90398a788769d16750f468de917
Issue-ID: CIMAN-132
Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
|
|
Add global build and push jobs for docker images
Set proper docker tag convention for snapshot and staging
binaries.
Change-Id: I0e805b5c9eebac6aaea627d855d7b542158b6a0f
Issue-ID: CIMAN-132
Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
Signed-off-by: Jeremy Phelps <jphelps@linuxfoundation.org>
|
|
This changes adds the following functionality for PyPI releases
- macros
- A PyPI server macro
- scripts
- A script to build artifacts
- A script to publish artifacts
- templates
- Templates for release
- jobs
- Jobs for release
- Nexus3 staging
- Nexus3 release
- PyPI index will be added at a later date
Issue-ID: CIMAN-137
Change-Id: I53522ed2fa2f462afebaac94c44fa2a9979e9c2a
Signed-off-by: Vanessa Rene Valderrama <vvalderrama@linuxfoundation.org>
Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
Signed-off-by: Jeremy Phelps <jphelps@linuxfoundation.org>
|