DoD - is it a good idea to build against a DoD in the same project?

15 Sep 2021

      Hello List,

Is it a good idea to build against the DoD that is defined in the same project?
For example, consider a project with the following meta:

   <project name="ProjectA">
  <title>Packages for ProjectA</title>
  <description/>
  <person userid="srinidhi" role="maintainer"/>
  <build>
    <disable/>
    <enable repository="SLE_15_SP3"/>
  </build>
  <publish>
    <disable/>
    <enable repository="SLE_15_SP3"/>
  </publish>
  <debuginfo>
    <enable/>
  </debuginfo>
  <repository name="my_dod">
    <download arch="x86_64" url="http://my-example.com/repo/" repotype="rpmmd">
      <archfilter>noarch,x86_64</archfilter>
    </download>
    <download arch="i586" url="http://my-example.com/repo/" repotype="rpmmd">
      <archfilter>noarch,i586</archfilter>
    </download>
    <path project="ProjectB" repository="standard"/>
    <arch>i586</arch>
    <arch>x86_64</arch>
  </repository>
  <repository name="SLE_15_SP3">
    <path project="ProjectA" repository="my_dod"/>
       <path project="ProjectB" repository="standard"/>
    <path project="openSUSE.org:SUSE:SLE-15-SP3:GA" repository="pool"/>
    <arch>i586</arch>
    <arch>x86_64</arch>
  </repository>
</project>

The reason I'm asking this question is because we have another project called
"ProjectB" that requires the built binaries from "ProjectA/SLE_15_SP3"
repository:

   <project name="ProjectB">
     <title>Packages for ProjectB</title>

   <description/>
     <person userid="srinidhi" role="maintainer"/>
     <build>

   <disable/>
       <enable repository="standard"/>
     </build>
     <publish>

   <disable/>
       <enable repository="standard"/>
     </publish>
     <debuginfo>

   <enable/>
     </debuginfo>
     <repository name="standard">
       <path
   project="ProjectA" repository="SLE_15_SP3"/>
       <path
   project="openSUSE.org:SUSE:SLE-15-SP3:GA" repository="pool"/>

   <arch>i586</arch>
       <arch>x86_64</arch>
     </repository>
   </project>

Please note that both the ProjectA and ProjectB projects show up in their
corresponding project meta. Because of these inter-dependencies between ProjectA
and ProjectB, we are ending up with cycles in the scheduler:

   # grep "^cycle:" /bs/log/scheduler_x86_64.log
   ...
   cycle: ProjectB/standard -> ProjectA/SLE_15_SP3
   ...

This issues gets amplified for every repository snapshot we create and whenever
we create the Maintenance projects for both ProjectA and ProjectB!

In this case, would it be better to move the DoD repository configuration into a
completely separate project? Any other suggestions or critique on how we are
setting up our projects?

Regards,
Srinidhi.

DoD - is it a good idea to build against a DoD in the same project?

Srinidhi B