I too had noticed one of the recent complaints and agree with your reasons against creating repo versions with no changes.
We discussed at PulpCon that we created a new version anyway as a way to tell that things ran successfully, but as you say, you can look at the tasks if you suspect something is amiss. Dana Walker She / Her / Hers Software Engineer, Pulp Project Red Hat <https://www.redhat.com> dawal...@redhat.com <https://www.redhat.com> On Mon, Nov 4, 2019 at 3:51 PM David Davis <davidda...@redhat.com> wrote: > Currently in pulp, syncs always create repository versions regardless of > whether or not any content changed. One of the tasks[0] for 3.0 GA is to > document this behavior. However, I've heard several complaints about this > from users so I wonder if it's worth reconsidering. > > Here are some reasons against always creating repo versions: > - They were meant to serve as a historical record but this information is > available by looking at the tasks api > - It creates additional, unnecessary versions and bumps the latest version > number of the repo > - If we ever have a feature to retain only the latest X repo versions, > it'll be less useful since some repo versions may not have any changes > > Any thoughts? I'd like to get this on the sprint by Wednesday so it can be > changed before the dev freeze date of Nov 12. > > [0] https://pulp.plan.io/issues/3308 > > David > _______________________________________________ > Pulp-dev mailing list > Pulp-dev@redhat.com > https://www.redhat.com/mailman/listinfo/pulp-dev >
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev