Hello,
I have some requirement so when i am working on RHEL7.2 OS release, i sync repos daily night and run some CI jobs and publish and promote CV version as per success of jobs. now when RHEL7.3 OS is ready to release, i want to freeze sync for RHEL7.2 CV and below is what i think i should be doing 1) i will create filter with "Include all rmps" and "include all errata up to today's date" ... 2) publish CV, and promote it to all life cycle envs 3) now i will start updating 7.3 CV till 7.4 releases .. 4) if any bug fix or erratas comes in, i will "include" that in 7.2 CV (filters) and publish. Now question i have is, when i do step 1 above, is it good step to freeze CV? is that CV version will be same as earlier version (before filters) ? Do i need to include "package groups" or it automatically include those ? whenever new erratas come in, i will change "Errata" date or include another filter to include errata date to today, and publish CV, when i publish CV will it change any RPM version as well ? ( apart from errata? , for example kernel rpm version ) Does anyone have some better way of doing it? Thanks, DJ -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
