Jira (PUP-3417) Smoke test packages

[Eric Sorenson (JIRA)]

Title: Message Title

Eric Sorenson commented on an issue   Re: Smoke test packages I did a pretty thorough smoke test on Ubuntu Trusty by combining the Puppet 3.7.2 packages with yesterday's Puppet-Server 0.3.0 release ; the master started up properly (once I fixed my VM to have enough memory) and I was able to fetch catalogs through the puppet-server. Notice: /Stage[main]/Main/Notify[default]/message: defined 'message' as 'this is puppet 3.7.2, in environment production ' Notice: Finished catalog run in 0.01 seconds root@glutch:/etc/puppet/environments/production/manifests# cat site.pp   notify { "default": message => "this is puppet ${::serverversion}, in environment ${::environment}" } Add Comment   Puppet / PUP-3417 Smoke test packages Procedure may vary by project and point in the release cycle. Ask around. In general this should happen on a variety of platforms, i.e. one or two each of kind of package we create (i.e., gem, dmg, msi, deb, rpm, etc). For Puppet, our acceptance suite now tests service scripts, and on debian, a passenger master. Manual smoke testing can therefore be li... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.