Hi Navid, On 06/17/2015 11:20 AM, Navid Shaikh wrote: > Hi, > > There was a discussion to move kubernetes package under virt7-docker-*, > earlier the kubernetes used to get updated under virt7-testing tag. > > Added the package in `virt7-docker-common-testing` tag, and tried > building it for target `virt7-docker-common-el7`, however it failed with > error: > > 15144 build (virt7-docker-common-el7, > kubernetes-0.19.0-0.4.gita8269e3.el7.src.rpm): FAILED: BuildError: > package kubernetes not in list for tag virt7-docker-common-candidate > > Then, I added the package in tag `virt7-docker-common-candidate` and the > build [1] is green. Correct you need to define which package are whitelisted on a destination tag. > > I could see the built packages in repo `virt7-docker-common-candidate` [2]. > > Is kubernetes package populated in correct repo? > > I was expecting it go in testing repo `virt7-docker-common-testing` [3] > first. > > Please correct me if I am missing something here. The package are going to -candidate by default, the goal being ultimately that on successful CI the package is tagged to -testing. We added this step in the workflow to include CI automation tasks : CI check for -candidate repo updates, detect changes, execute CI jobs, tag package to -testing. However, you can tag it to -testing if needed. > > > [1] http://cbs.centos.org/koji/buildinfo?buildID=1330 > [2] > http://cbs.centos.org/repos/virt7-docker-common-candidate/x86_64/os/Packages/ > > [3] > http://cbs.centos.org/repos/virt7-docker-common-testing/x86_64/os/Packages/ > -- Thomas.