Ernesto Puerta

@djgalloway as this is causing some fuss in other teams, for the soak testing period, can we just make it run for dashboard-labeled PRs? Thanks!

@djgalloway something I just realized: and I don't wanna sound like a killjoy, but it'll 'slightly' increment the time taken to finish (10-15 min), as here `make check` unit tests...

@djgalloway just started to experiment with pipelines (https://github.com/ceph/ceph/pull/37265) and it seems it might not require too much rework...

> Okay. Are we going that route instead, then? I guess the multibranch pipeline should be enable on ceph/ceph, and that configuration could still be a jenkins-job-builder YAML file, right?...

> I would suggest logging in to Jenkins, getting an API key, and using `jenkins-job-builder` manually to test and upload your JJB YAMLs. > > ``` > $ cat ~/.jenkins_jobs.jenkins.ceph.com.ini...

> @epuertat it pains me to still see us building Ceph binaries twice for every PR. What do you think about merging this next week? @djgalloway omd, completely forgot about...

BTW, @baum [this change](https://github.com/ceph/ceph-nvmeof/commit/d441ee09222608a0c3d33e1c3538021dfe1d93bc) broke support for `ceph-devel` and other use cases of this make + docker-compose. I was planning to fork this repo and revert that commit.

https://review.spdk.io/gerrit/c/spdk/spdk/+/16451

Partially tackled by https://github.com/ceph/ceph-nvmeof/pull/125.

Duplicate of #74