I belive that we don't need mvn settings.
[ci-management.git] / jjb / ric-plt-xapp-frame-py / ric-plt-xapp-frame-py.yaml
1 ---
2 - project:
3     name: ric-plt-xapp-frame-py-project-view
4     project-name: ric-plt-xapp-frame-py
5     views:
6       - project-view
7
8 - project:
9     name: ric-plt-xapp-frame-py-info
10     project: ric-plt/xapp-frame-py
11     project-name: ric-plt-xapp-frame-py
12     build-node: centos7-builder-1c-1g
13     jobs:
14       - gerrit-info-yaml-verify
15
16 - py_common: &py_common
17     name: xapp-frame-py-common
18     # git repo
19     project: ric-plt/xapp-frame-py
20     # jenkins job name prefix
21     project-name: ric-plt-xapp-frame-py
22     # dont run docs on verify
23     tox-envs: code,flake8
24     build-node: ubuntu1804-builder-2c-2g
25     pre-build-script: !include-raw-escape:
26       - ../shell/install-deb-nng-rmr.sh
27
28 # verify distribution and publish to test.pypi.org
29 - project:
30     name: ric-plt-xapp-frame-py-pypi
31     <<: *py_common
32     jobs:
33       - '{project-name}-gerrit-pypi-jobs'
34     stream:
35       - master:
36           branch: master
37
38 # promote distribution from test.pypi.org to pypi.org
39 - project:
40     name: ric-plt-xapp-frame-py-release
41     <<: *py_common
42     # release requires sigul which requires centos
43     build-node: centos7-builder-1c-1g
44     jobs:
45       - '{project-name}-gerrit-pypi-release-jobs'
46
47 # analyze unit test coverage
48 - project:
49     name: ric-plt-xapp-frame-py-sonar
50     <<: *py_common
51     sonarcloud: true
52     sonarcloud-api-token: '{sonarcloud_api_token}'
53     sonarcloud-project-key: '{sonarcloud_project_organization}_{project-name}'
54     sonarcloud-project-organization: '{sonarcloud_project_organization}'
55     jobs:
56       - gerrit-tox-sonar