On Mon, Feb 14, 2022 at 04:34:20PM +0800, Cao Xueliang wrote:

# auto submit cci-makepkg before run test suite

example:

• job.yaml

---

'#! rpmbuild.yaml': suite: rpmbuild category: functional rpmbuild: repo_addr: https://vault.centos.org/6.10/os/Source/SPackages/ed-1.1-3.3.el6.src.rpm arch: aarch64 custom_repo_name: unstable/compatible/6 mount_repo_addr: https://api.compass-ci.openeuler.org:20018/rpm/testing/openeuler-20.03-LTS-S... 1/compat-centos6/standard_$basearch/$basearch mount_repo_name: compatible-6 docker_image: openeuler:20.03-LTS-SP1

- generate cci-makepkg.yaml
# detect $LKP_SRC/pkg/rpmbuild/PKGBUILD first
# detect /srv/initrd/pkg/container/openeuler/aarch64/20.03-LTS-SP1/rpmbuild/latest.cgz

suite: cci-makepkg category: functional

cci-makepkg: benchmark: rpmbuild # from rpmbuild.yaml os: # from rpmbuild.yaml os_arch: # from rpmbuild.yaml os_mount: # from rpmbuild.yaml

Looks good.

• submit cci-makepkg.yaml & rpmbuild.yaml
• if cci-makepkg job success and exists latest.cgz then submit rpmbuild.yaml
• if cci-makepkg job not success then echo error & no need submit rpmbuild.yaml

Just to make it clear:

Here "submit cci-makepkg.yaml" should not mean "cci submit". The scheduler should - check and setup job depends - auto create and dispatch cci-makepkg.yaml - continue dispatch rpmbuild.yaml, when the above job succeeded

Thanks, Fengguang