Jira (PUP-6200) Smoke test packages (PUP 3.8.7)
Title: Message Title John Duarte commented on PUP-6200 Re: Smoke test packages (PUP 3.8.7) Validating 3.8.7 OS X dmg on OS X 10.11 Install facter gem cfopahywkgspq62:~ root# gem install facter Fetching: facter-2.4.6-universal-darwin.gem (100%) Successfully installed facter-2.4.6-universal-darwin Parsing documentation for facter-2.4.6-universal-darwin Installing ri documentation for facter-2.4.6-universal-darwin 1 gem installed Install dmg cfopahywkgspq62:~ root# curl -O http://builds.puppetlabs.lan/puppet/3.8.7/artifacts/apple/puppet-3.8.7.dmg % Total% Received % Xferd
Jira (PUP-6200) Smoke test packages (PUP 3.8.7)
Title: Message Title Glenn Sarti commented on PUP-6200 Re: Smoke test packages (PUP 3.8.7) All windows installs were done using the UI for MSI Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6200) Smoke test packages (PUP 3.8.7)
Title: Message Title
Glenn Sarti commented on PUP-6200
Re: Smoke test packages (PUP 3.8.7)
Windows 10 Ent - x64
Not a supported platform. Tested it anyway 32bit pkg
C:\Program Files (x86)\Puppet Labs\Puppet\bin>puppet apply -e "notify{ 'hello world' :}"
Could not retrieve fact='hostname', resolution='': Could not execute 'hostname': command not found
Could not retrieve fact='hostname', resolution='': Could not execute 'hostname': command not found
Could not retrieve fact='hostname', resolution='': Could not execute 'hostname': command not found
Could not retrieve fact='hostname', resolution='': Could not execute 'hostname': command not found
Warning: Could not retrieve fact fqdn
Could not retrieve fact='hostname', resolution='': Could not execute 'hostname': command not found
Could not retrieve fact='hostname', resolution='': Could not execute 'hostname': command not found
Jira (PUP-6200) Smoke test packages (PUP 3.8.7)
Title: Message Title
Glenn Sarti commented on PUP-6200
Re: Smoke test packages (PUP 3.8.7)
Windows 2012 R2 x64
32bit pkg
ruby 1.9.3p551 (2014-11-13) [i386-mingw32]
C:\Program Files (x86)\Puppet Labs\Puppet\bin>puppet apply -e "notify{ 'hello wo
rld' :}"
Notice: Compiled catalog for fmv536byzx7a7pp.delivery.puppetlabs.net in environm
ent production in 0.05 seconds
Notice: hello world
Notice: /Stage[main]/Main/Notify[hello world]/message: defined 'message' as 'hel
lo world'
Notice: Finished catalog run in 0.17 seconds
Jira (PUP-6200) Smoke test packages (PUP 3.8.7)
Title: Message Title
Glenn Sarti commented on PUP-6200
Re: Smoke test packages (PUP 3.8.7)
Win2008 R2 x64
32bit Agent
ruby 1.9.3p551 (2014-11-13) [i386-mingw32]
C:\Program Files (x86)\Puppet Labs\Puppet\bin>puppet apply -e "notify{ 'hello wo
rld' :}"
Notice: Compiled catalog for skhm60xyl6j8913.delivery.puppetlabs.net in environm
ent production in 0.03 seconds
Notice: hello world
Notice: /Stage[main]/Main/Notify[hello world]/message: defined 'message' as 'hel
lo world'
Notice: Finished catalog run in 0.02 seconds
Jira (PUP-6200) Smoke test packages (PUP 3.8.7)
Title: Message Title
Hailee Kenney commented on PUP-6200
Re: Smoke test packages (PUP 3.8.7)
Running on Debian 7 when installed from packages:
root@klk6ki5l5yss3px:~# puppet apply -e "notify{ 'hello world' :}"
Warning: Setting templatedir is deprecated. See http://links.puppetlabs.com/env-settings-deprecations
(at /usr/lib/ruby/vendor_ruby/puppet/settings.rb:1139:in `issue_deprecation_warning')
Notice: Compiled catalog for klk6ki5l5yss3px.delivery.puppetlabs.net in environment production in 0.01 seconds
Notice: hello world
Notice: /Stage[main]/Main/Notify[hello world]/message: defined 'message' as 'hello world'
Notice: Finished catalog run in 0.02 seconds
root@klk6ki5l5yss3px:~# puppet --version
3.8.7
root@klk6ki5l5yss3px:~# puppet help
Jira (PUP-6200) Smoke test packages (PUP 3.8.7)
Title: Message Title
Glenn Sarti commented on PUP-6200
Re: Smoke test packages (PUP 3.8.7)
Windows 2003 R2 x64
64bit - Fails to install with warning - Expected 32bit
C:\Program Files (x86)\Puppet Labs\Puppet\bin>puppet apply -e "notify{ 'hello wo
rld' :}"
Notice: Compiled catalog for iesaxx8xygka8pc.delivery.puppetlabs.net in environm
ent production in 0.05 seconds
Notice: hello world
Notice: /Stage[main]/Main/Notify[hello world]/message: defined 'message' as 'hel
lo world'
Notice: Finished catalog run in 0.02 seconds
C:\Program Files (x86)\Puppet Labs\Puppet\bin>puppet help
Jira (PUP-6200) Smoke test packages (PUP 3.8.7)
Title: Message Title
Hailee Kenney commented on PUP-6200
Re: Smoke test packages (PUP 3.8.7)
Running on CentOS 7 when installed from packages:
[root@i2uzzu73w5pdw5v ~]# puppet apply -e "notify{ 'hello world' :}"
Notice: Compiled catalog for i2uzzu73w5pdw5v.delivery.puppetlabs.net in environment production in 0.01 seconds
Notice: hello world
Notice: /Stage[main]/Main/Notify[hello world]/message: defined 'message' as 'hello world'
Notice: Finished catalog run in 0.01 seconds
[root@i2uzzu73w5pdw5v ~]# puppet --version
3.8.7
[root@i2uzzu73w5pdw5v ~]# puppet help
Usage: puppet [options] [options]
Jira (PUP-6200) Smoke test packages (PUP 3.8.7)
Title: Message Title
Hailee Kenney commented on PUP-6200
Re: Smoke test packages (PUP 3.8.7)
Running the gem on CentOS 7:
[root@qf7b2t9esb806a5 ~]# puppet apply -e 'notify{ 'hello world!' :}'
-bash: !': event not found
[root@qf7b2t9esb806a5 ~]# puppet apply -e "notify{ 'hello world!' :}"
-bash: !': event not found
[root@qf7b2t9esb806a5 ~]# puppet apply -e 'notify{ "hello world^C:}'
[root@qf7b2t9esb806a5 ~]# puppet apply -e "notify{ 'hello world' :}"
Notice: Compiled catalog for qf7b2t9esb806a5.delivery.puppetlabs.net in environment production in 0.01 seconds
Notice: hello world
Notice: /Stage[main]/Main/Notify[hello world]/message: defined 'message' as 'hello world'
Notice: Finished catalog run in 0.47 seconds
Jira (PUP-6200) Smoke test packages (PUP 3.8.7)
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6200 Smoke test packages (PUP 3.8.7) Change By: Kylo Ginsberg (Initial planned release date: 2016-04-21)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 limited to other package formats than deb and rpm.For the Puppet gem, we don't yet have automated acceptance testing, so some quick manual smoke testing should always be performed. Platform packages express their dependencies differently than gems, so it's possible to encounter a situation where the build pipeline produced packages out of sync with the gems.Lighter testing of Z releases is acceptable. * Add a link to the Packages repository that you receive from the "Tag and create packages" subtask * Ping folks on your team for help with different platforms. * When you pick up a platform, please leave a comment below that you are testing it. When it looks good, leave another comment, preferably with a code snippet showing the commands executed and their output. * When all platforms picked have been smoke tested, move this ticket to done.IMPORTANT: Please edit the description of this ticket and remove "Example:" below. Edit the platforms to smoke test on, and the smoke test procedure. Example: Smoke test platforms: * pick some platforms such as * gem - select one Linux for the universal gem, Windows with x64 platform-specific gem, and Windows with x86 platform-specific gem * Windows 2003/2008/2012 (msi) * Solaris 10/11 (tarball or gem?) * OSX (dmg) * (Note if you are smoke testing Puppet and pick an rpm or deb based platform, concentrate on testing a gem or tarball, since acceptance should have adequately smoke tested those packages.)* RHEL / 7 or CentOS 5/6/ 7* Fedora 19/20* Debian 6/ 7 * Ubuntu 10.04/12.04/14.04 Smoke test procedure: * Start/stop/restart a master (if the platform supports that) * Start/stop/restart an agent * Help/man * Write and run some manifestsDependencies: * Tag and create packages * For Windows MSIs - Push tag Add Comment
Jira (PUP-6200) Smoke test packages (PUP 3.8.7)
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-6200 Smoke test packages (PUP 3.8.7) Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2016/04/20 2:22 PM Priority: Normal Reporter: Kylo Ginsberg (Initial planned release date: 2016-04-21) 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 limited to other package formats than deb and rpm. For the Puppet gem, we don't yet have automated acceptance testing, so some quick manual smoke testing should always be performed. Platform packages express their dependencies differently than gems, so it's possible to encounter a situation where the build pipeline produced packages out of sync with the gems. Lighter testing of Z releases is acceptable. Add a link to the Packages repository that you receive from the "Tag and create packages" subtask Ping folks on your team for help with different platforms. When you pick up a platform, please leave a comment below that you are testing it. When it looks good, leave another comment, preferably with a code snippet showing the commands executed and their output.
