On Sat, Nov 01, 2008 at 01:08:45PM -0400, Jesus M. Rodriguez wrote: > > I use > tag = spacewalk-5E-0.3-candidate > inherit = True > > when I tried tag = spacewalk-5E-0.3 I never could get spacewalk-java > to show up among others, so I switched to candidate. That's how I build > the repos for a release.
With Satellite 5.2.0, we have three tags -- satellite-5E-5.2-candidate, satellite-5E-5.2, and satellite-5E-5.2.0. The -candidate is the build target. But no composes are built from -candidate, the developer or the rel-eng person has to tag the builds to satellite-5E-5.2. This is to ensure that someone review the completed (and failed) builds and makes a decision about what should be used for composes, pushes, and further work. The QA composes were done from satellite-5E-5.2, but the latest "release candidates" were done from satellite-5E-5.2.0 which was cloned from satellite-5E-5.2, and it does not inherit from any other tag. The reason is to have a stable set of builds which will not change by new builds compiled, tagged to, or untagged from tags from which satellite-5E-5.2 inherits from. Of course, changes can be made to satellite-5E-5.2.0 but it is a manual step, to ensure as stable environment as possible. I wonder if we could use something similar for Spacewalk. Primarily, building composes from the -candidate tag sounds like a not very good idea -- people might fire a build --nowait and forget about the result, or assume that the build passed while it did not. Having that extra manual tag-pkg seems like a reasonable price for better control of the compose content. -- Jan Pazdziora | adelton at #satellite*, #brno Satellite Engineering, Red Hat _______________________________________________ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
