Jira (PDB-5517) Don't fail upgrade_latest acceptance test between tagging and release

[Austin Blatt (Jira)]

Title: Message Title

Austin Blatt commented on PDB-5517   Re: Don't fail upgrade_latest acceptance test between tagging and release To do this work we must be able to codify, in beaker tests, the difference between "tagged and pre-release" and "tagged and post-release, but there's no new PuppetDB package available". Identifying, from our CI, whether or not the package should be available publicly is somewhat difficult. Otherwise this test may silently NOT be testing upgrade_latest if the PuppetDB packages are not released. Also random aside, I noticed that folks caught this because they added FOSS PuppetDB tests to the PE CI Triage command ! pipelines for 2019.8.x. If it is a requirement that components have a relevant CI job to track for that command, possibly the correct outcome is for there to be actual PE PuppetDB acceptance tests for the CI triage job to watch. PE 2019.8.x, or other PE version, doesn't actually care how our FOSS PuppetDB packages are performing in their CI. Add Comment   This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.457810.1659472823000.6587.1659477840177%40Atlassian.JIRA.