On Thu, Oct 17, 2019 at 5:02 AM A Manzer <aman...@gmail.com> wrote: > On Wednesday, October 16, 2019 at 5:44:27 PM UTC-4, Morgan Rhodes wrote: >> >> >> Is your confusion mostly around the fact that one of them is built from >> source and one from package, or that 6.7 is more of a floating tag? I know >> I've seen that pattern in some other upstream repos like centos, postgres, >> mysql, etc, but for those it might be 6.7 points to the latest 6.7.x that >> was shipped, rather than more like head/nightly. >> >> > It's mostly the from source, from package distiction. I'm not familiar > enough with Puppet's release cycle to know the distinction between a from > source build and a from package build. Are "from source" builds > essentially just nightlys? I think people are more familiar with keywords > such as "head", "master", "edge", or "nightly" and the tag should include > something like that. If they're not exactly nightly, but based on a tag in > the source, what differentiates a from source build and a from package > build? >
The "from source" builds aren't quite nightlies, since they get built on every commit/PR into master, so depending on how much development is happening it could end up built more often, and there's certainly more risk of picking up bugs. In this model the source builds aren't built based on a tag. We use `git describe` to come up with the tag for the container, but the code is from head/master. If I were to look at these tags on Docker Hub, I'd expect them to represent > the following: > puppet/puppetserver:6.7 => The latest release in the 6.7 series, > moving from 6.7.0, through 6.7.1, etc. > puppet/puppetserver:6.7.0 => Exactly the release 6.7.0 and never changing > puppet/puppetserver:latest => The latest release of Puppet Server, moving > through minor *and* major versions. (Perhaps there's room for a > puppet/puppetserver:6 tag here) > puppet/puppetserver:edge => This one's less immediately obvious to me, > but after a moment I'd probably realize that it was some kind of nightly or > pre-release beta, especially given the tag date would be after the :latest > tag. > Do you have a feel for whether or not it would be valuable to have a `6.7-edge` in addition to `edge`, where `6.7-edge` would be HEAD of master from the time 6.7.0 is tagged until the last commit before 6.8.0 is pushed? Thinking about it more it might make sense to just have `edge` as the latest from-source build and save the more granular/versioned tags for builds from packages. > > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/a07de248-a5dd-4e95-a9ae-0798c2c8a8ce%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/a07de248-a5dd-4e95-a9ae-0798c2c8a8ce%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- Morgan Rhodes Release Engineering mor...@puppet.com she/her/hers -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CA%2BFnDv0DNrnL4rv2saRDCzLgUkSw0GX13KNmHYJB2%2Bm0WNy3fA%40mail.gmail.com.
