Alfredo Moralejo

So, IIUC, each dlrn run will require diferent projects.ini config to point to different branches, releases, right?, in that case i'd say it's like running two different instances of dlrn....

So, IIUC what we want is: 1. The build-test-package role takes care of checking out the commit for branch stable/A. 2. The build-test-package role creates a projects.ini config for release...

I think i got it now. We need to use --dev to get delorean repos added from trunk.r.o to the mock config. So i think the best solution here is...

But, we'd we want to clone the repos upstream?, my understanding is that the whole point of building packages in the job is to build patches wich are still unmerged,...

Note that the koji instance for CentOS SIGs builds, the right koji instance is CBS https://cbs.centos.org/koji/ , not https://kojihub.stream.centos.org/koji/ Builds in CBS can be based on srpms or from source,...

Note, this capping is breaking builds for distro based deployments as fedora. Could this be fixed?

I've been discussing with @evallesp and I'd say that a simple enough implementation would be to make metrics api to return the running time of current dlrn process working or...