Jira (PUP-3214) Smoke test packages
Title: Message Title Melissa Stone commented on an issue Re: Smoke test packages packages available at http://builds.puppetlabs.lan/puppet/3.7.1/ Add Comment Puppet / PUP-3214 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). Lighter testing of Z releases is acceptable. * Add a link to the Packages repository that you receive from the Tag and create package... 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.
Jira (PUP-3214) Smoke test packages
Title: Message Title Andy Parker commented on an issue Re: Smoke test packages Description contains what we are going to check. Add Comment Puppet / PUP-3214 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). Lighter testing of Z releases is acceptable. * Add a link to the Packages repository that you receive from the Tag and create pa... 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.
Jira (PUP-3214) Smoke test packages
Title: Message Title Andy Parker updated an issue Puppet / PUP-3214 Smoke test packages Change By: Andy Parker Proceduremayvarybyprojectandpointinthereleasecycle.Askaround. Ingeneralthisshouldhappenonavarietyofplatforms,i.e.oneortwoeachofkindofpackagewecreate(i.e.,gem,dmg,msi,deb,rpm,etc). LightertestingofZreleasesisacceptable. *AddalinktothePackagesrepositorythatyoureceivefromtheTagandcreatepackagessubtask *Pingfolksonyourteamforhelpwithdifferentplatforms. *Whenyoupickupaplatform,pleaseleaveacommentbelowthatyouaretestingit.Whenitlooksgood,leaveanothercomment,preferablywithacodesnippetshowingthecommandsexecutedandtheiroutput. *IfyoursmoketestingincludesMSIs,youwillgenerallytestonotherplatformsfirstandwhenthatislookinggood,pingtheReleaseEngineerthatbuilttheotherpackagestomoveforwardwithMSIs(theyrequiretagstobepushed).Thisticketdoesn'tcloseuntilallchosenplatforms(includingMSIs)havebeentested. *Whenallplatformspickedhavebeensmoketested,movethistickettodone. IMPORTANT:PleaseeditthedescriptionofthisticketandremoveExample:below.Edittheplatformstosmoketeston,andthesmoketestprocedure.Example: Smoketestplatforms: * picksomeplatformssuchas* RHEL 5/ 6/7 (RPMinstall) * CentOS5/6* Windows 2003/ 2008/2012 (MSIinstall) * Debian6/7/*Ubuntu10.04/12.04/14.04 Anything(Geminstall) Smoketestprocedure: *Start/stop/restartamasterwiththeinitscripts( onDebiantrythepassengermaster RHELonly ) *Start/stop/restartanagent (WindowsandRHEL) *Help/man (All) *Writeandrunsomemanifests Dependencies:*Tagandcreatepackages*ForWindowsMSIs-Pushtag (All) Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the
Jira (PUP-3214) Smoke test packages
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-3214 Smoke test packages Change By: Andy Parker Assignee: HaileeKenney AndyParker Add Comment 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.
Jira (PUP-3214) Smoke test packages
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3214 Smoke test packages Change By: Josh Cooper Proceduremayvarybyprojectandpointinthereleasecycle.Askaround.Ingeneralthisshouldhappenonavarietyofplatforms,i.e.oneortwoeachofkindofpackagewecreate(i.e.,gem,dmg,msi,deb,rpm,etc).LightertestingofZreleasesisacceptable.*AddalinktothePackagesrepositorythatyoureceivefromtheTagandcreatepackagessubtask*Pingfolksonyourteamforhelpwithdifferentplatforms.*Whenyoupickupaplatform,pleaseleaveacommentbelowthatyouaretestingit.Whenitlooksgood,leaveanothercomment,preferablywithacodesnippetshowingthecommandsexecutedandtheiroutput.*IfyoursmoketestingincludesMSIs,youwillgenerallytestonotherplatformsfirstandwhenthatislookinggood,pingtheReleaseEngineerthatbuilttheotherpackagestomoveforwardwithMSIs(theyrequiretagstobepushed).Thisticketdoesn'tcloseuntilallchosenplatforms(includingMSIs)havebeentested.*Whenallplatformspickedhavebeensmoketested,movethistickettodone.Smoketestplatforms:*RHEL6/7(RPMinstall)*Windows2008/2012(MSIinstall x86x64 )*Anything(Geminstall)Smoketestprocedure:*Start/stop/restartamasterwiththeinitscripts(RHELonly)*Start/stop/restartanagent(WindowsandRHEL)*Help/man(All)*Writeandrunsomemanifests(All) Add Comment 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
Jira (PUP-3214) Smoke test packages
Title: Message Title Rob Reynolds commented on an issue Re: Smoke test packages Windows 2008 / 2012 x86 Add Comment Puppet / PUP-3214 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). Lighter testing of Z releases is acceptable. * Add a link to the Packages repository that you receive from the Tag and create pa... 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.
Jira (PUP-3214) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages RedHat 6/7. Add Comment Puppet / PUP-3214 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). Lighter testing of Z releases is acceptable. * Add a link to the Packages repository that you receive from the Tag and create pa... 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.
Jira (PUP-3214) Smoke test packages
Title: Message Title Andy Parker commented on an issue Re: Smoke test packages Gem, non-windows. Add Comment Puppet / PUP-3214 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). Lighter testing of Z releases is acceptable. * Add a link to the Packages repository that you receive from the Tag and create pa... 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.
Jira (PUP-3214) Smoke test packages
Title: Message Title Andy Parker updated an issue Puppet / PUP-3214 Smoke test packages Change By: Andy Parker Proceduremayvarybyprojectandpointinthereleasecycle.Askaround. Ingeneralthisshouldhappenonavarietyofplatforms,i.e.oneortwoeachofkindofpackagewecreate(i.e.,gem,dmg,msi,deb,rpm,etc). LightertestingofZreleasesisacceptable. *AddalinktothePackagesrepositorythatyoureceivefromtheTagandcreatepackagessubtask *Pingfolksonyourteamforhelpwithdifferentplatforms. *Whenyoupickupaplatform,pleaseleaveacommentbelowthatyouaretestingit.Whenitlooksgood,leaveanothercomment,preferablywithacodesnippetshowingthecommandsexecutedandtheiroutput. *IfyoursmoketestingincludesMSIs,youwillgenerallytestonotherplatformsfirstandwhenthatislookinggood,pingtheReleaseEngineerthatbuilttheotherpackagestomoveforwardwithMSIs(theyrequiretagstobepushed).Thisticketdoesn'tcloseuntilallchosenplatforms(includingMSIs)havebeentested. *Whenallplatformspickedhavebeensmoketested,movethistickettodone. Smoketestplatforms: * RHEL6/7(RPMinstall) OSX *Windows2008/2012(MSIinstallx86x64) *Anything(Geminstall) Smoketestprocedure: *Start/stop/restart amasterwiththeinitscripts(RHELonly)*Start/stop/restart anagent(Windows andRHEL ) *Help/man(All) *Writeandrunsomemanifests(All) Add Comment 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
Jira (PUP-3214) Smoke test packages
Title: Message Title Andy Parker commented on an issue Re: Smoke test packages Handing gems over to Joshua Partlow. I'm picking up OSX. Add Comment Puppet / PUP-3214 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). Lighter testing of Z releases is acceptable. * Add a link to the Packages repository that you receive from the Tag and create package... 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.
Jira (PUP-3214) Smoke test packages
Title: Message Title
Andy Parker commented on an issue
Re: Smoke test packages
OSX package looks good.
Caveat: you have to install facter separately.
Commands run:
puppet help
man puppet
man puppet-apply
puppet apply -e '[1,2,3].each |$x| { notice($x) }' --parser future
Add Comment
Puppet / PUP-3214
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). Lighter testing of Z releases is acceptable. * Add a link to the Packages repository that you receive from the Tag and create package...
Jira (PUP-3214) Smoke test packages
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3214 Smoke test packages Change By: Joshua Partlow Proceduremayvarybyprojectandpointinthereleasecycle.Askaround.Ingeneralthisshouldhappenonavarietyofplatforms,i.e.oneortwoeachofkindofpackagewecreate(i.e.,gem,dmg,msi,deb,rpm,etc).LightertestingofZreleasesisacceptable.*AddalinktothePackagesrepositorythatyoureceivefromtheTagandcreatepackagessubtask*Pingfolksonyourteamforhelpwithdifferentplatforms.*Whenyoupickupaplatform,pleaseleaveacommentbelowthatyouaretestingit.Whenitlooksgood,leaveanothercomment,preferablywithacodesnippetshowingthecommandsexecutedandtheiroutput.*IfyoursmoketestingincludesMSIs,youwillgenerallytestonotherplatformsfirstandwhenthatislookinggood,pingtheReleaseEngineerthatbuilttheotherpackagestomoveforwardwithMSIs(theyrequiretagstobepushed).Thisticketdoesn'tcloseuntilallchosenplatforms(includingMSIs)havebeentested.*Whenallplatformspickedhavebeensmoketested,movethistickettodone.Smoketestplatforms:* -- OSX -- *Windows2008/2012(MSIinstallx86x64)*--Anything(Geminstall):onrhel7--Smoketestprocedure:*Start/stop/restartanagent(Windows)*Help/man(All)*Writeandrunsomemanifests(All) Add Comment 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.
Jira (PUP-3214) Smoke test packages
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3214 Smoke test packages Change By: Joshua Partlow Proceduremayvarybyprojectandpointinthereleasecycle.Askaround. Ingeneralthisshouldhappenonavarietyofplatforms,i.e.oneortwoeachofkindofpackagewecreate(i.e.,gem,dmg,msi,deb,rpm,etc). LightertestingofZreleasesisacceptable. *AddalinktothePackagesrepositorythatyoureceivefromtheTagandcreatepackagessubtask *Pingfolksonyourteamforhelpwithdifferentplatforms. *Whenyoupickupaplatform,pleaseleaveacommentbelowthatyouaretestingit.Whenitlooksgood,leaveanothercomment,preferablywithacodesnippetshowingthecommandsexecutedandtheiroutput. *IfyoursmoketestingincludesMSIs,youwillgenerallytestonotherplatformsfirstandwhenthatislookinggood,pingtheReleaseEngineerthatbuilttheotherpackagestomoveforwardwithMSIs(theyrequiretagstobepushed).Thisticketdoesn'tcloseuntilallchosenplatforms(includingMSIs)havebeentested. *Whenallplatformspickedhavebeensmoketested,movethistickettodone. Smoketestplatforms: *OSX *Windows2008/2012(MSIinstallx86x64) * -- Anything(Geminstall) :onrhel7-- Smoketestprocedure: *Start/stop/restartanagent(Windows) *Help/man(All) *Writeandrunsomemanifests(All) Add Comment 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.
Jira (PUP-3214) Smoke test packages
Title: Message Title
Joshua Partlow commented on an issue
Re: Smoke test packages
Gem on RHEL7 seems fine:
wget http://builds.puppetlabs.lan/puppet/3.7.1/artifacts/puppet-3.7.1.gem
gem install puppet-3.7.1.gem
puppet --version
puppet help
puppet apply -e notify { hello: }
puppet resource group puppet ensure=present
puppet resource user puppet ensure=present groups=puppet
puppet master --autosign true --certname localhost
puppet agent -t --server localhost
Add Comment
Puppet / PUP-3214
Smoke test packages
Procedure may vary by project
Jira (PUP-3214) Smoke test packages
Title: Message Title Rob Reynolds commented on an issue Re: Smoke test packages Windows 2008 x86 === Versions === PS C:\puppet --version 3.7.1 — Operation time for (puppet --version): 00:00:05.5750697 — --- PS C:\facter --version 2.2.0 — Operation time for (facter --version): 00:00:00.7378932 — --- PS C:\hiera --version 1.3.4 — Operation time for (hiera --version): 00:00:00.4904785 — --- PS C:\cmd /c environment.bat where ruby ruby --version c:\Program Files (x86)\Puppet Labs\Puppet\sys\ruby\bin\ruby.exe ruby 1.9.3p484 (2013-11-22) [i386-mingw32] — Operation time for (cmd /c environment.bat where ruby ruby --version): 00:00:00.3106295 — --- === Help Commands === PS C:\puppet help Usage: puppet subcommand [options] action [options] Available subcommands: agent The puppet agent daemon apply Apply Puppet manifests locally ca Local Puppet Certificate Authority management. catalog Compile, save, view, and convert catalogs. cert Manage certificates and requests certificate Provide access to the CA for certificate management. certificate_request Manage certificate requests. certificate_revocation_list Manage the list of revoked certificates. config Interact with Puppet's settings. describe Display help about resource types device Manage remote network devices doc Generate Puppet documentation and references facts Retrieve and store facts. file Retrieve and store files in a filebucket filebucket Store and retrieve files in a filebucket help Display Puppet help. inspect Send an inspection report instrumentation_data Manage instrumentation listener accumulated data. DEPRECATED. instrumentation_listener Manage instrumentation listeners. DEPRECATED. instrumentation_probe Manage instrumentation probes. Deprecated key Create, save, and remove certificate keys. kick Remotely control puppet agent man Display Puppet manual pages. master The puppet master daemon module Creates, installs and searches for modules on the Puppet Forge. node View and manage node definitions. parser Interact directly with the parser. plugin Interact with the Puppet plugin system. queue Deprecated queuing daemon for asynchronous storeconfigs report Create, display, and submit reports. resource The resource abstraction layer shell resource_type View classes, defined resource types, and nodes from all manifests. secret_agent Mimics puppet agent. status View puppet server status. See 'puppet help subcommand action' for help on a specific subcommand action. See 'puppet help subcommand' for help on a specific subcommand. Puppet v3.7.1 — Operation time for (puppet help): 00:00:04.0080380 — --- PS C:\puppet help apply puppet-apply(8) – Apply Puppet manifests locally SYNOPSIS Applies a standalone Puppet manifest to the local system. USAGE puppet apply [-h|--help] [-V|--version] [-d|--debug] [-v|--verbose] [-e|--execute] [--detailed-exitcodes] [-L|--loadclasses] [-l|--logdest syslog|eventlog|FILE|console] [--noop] [--catalog catalog] [--write-catalog-summary] file DESCRIPTION --- This is the standalone puppet execution tool; use it to apply individual manifests. When provided with a modulepath, via command line or config file, puppet apply can effectively
Jira (PUP-3214) Smoke test packages
Title: Message Title
Rob Reynolds commented on an issue
Re: Smoke test packages
Windows 2012 x86
=== Versions === PS C:\puppet --version 3.7.1 — Operation time for (puppet --version): 00:00:04.7047321 — --- PS C:\facter --version 2.2.0 — Operation time for (facter --version): 00:00:00.6450812 — --- PS C:\hiera --version 1.3.4 — Operation time for (hiera --version): 00:00:00.5027400 — --- PS C:\cmd /c environment.bat where ruby ruby --version c:\Program Files (x86)\Puppet Labs\Puppet\sys\ruby\bin\ruby.exe ruby 1.9.3p484 (2013-11-22) [i386-mingw32] — Operation time for (cmd /c environment.bat where ruby ruby --version): 00:00:00.3874584 — --- PS C:\puppet apply -e user
Unknown macro: {'Administrator'}
[mNotice: Compiled catalog for win-e5k8tm30719 in environment production in 1.10 seconds [0m [mNotice: /Stage[main]/Main/User[Administrator]/ensure: created [0m [mNotice: Finished catalog run in 0.43 seconds [0m — Operation time for (puppet apply -e user
Unknown macro: {'Administrator'}
): 00:00:36.2892072 — --- === Help === PS C:\puppet help
Usage: puppet subcommand [options] action [options]
Available subcommands:
agent The puppet agent daemon apply Apply Puppet manifests locally ca Local Puppet Certificate Authority management. catalog Compile, save, view, and convert catalogs. cert Manage certificates and requests certificate Provide access to the CA for certificate management. certificate_request Manage certificate requests. certificate_revocation_list Manage the list of revoked certificates. config Interact with Puppet's settings. describe Display help about resource types device Manage remote network devices doc Generate Puppet documentation and references facts Retrieve and store facts. file Retrieve and store files in a filebucket filebucket Store and retrieve files in a filebucket help Display Puppet help. inspect Send an inspection report instrumentation_data Manage instrumentation listener accumulated data. DEPREC ATED. instrumentation_listener Manage instrumentation listeners. DEPRECATED. instrumentation_probe Manage instrumentation probes. Deprecated key Create, save, and remove certificate keys. kick Remotely control puppet agent man Display Puppet manual pages. master The puppet master daemon module Creates, installs and searches for modules on the Puppet For ge. node View and manage node definitions. parser Interact directly with the parser. plugin Interact with the Puppet plugin system. queue Deprecated queuing daemon for asynchronous storeconfigs report Create, display, and submit reports. resource The resource abstraction layer shell resource_type View classes, defined resource types, and nodes from all man ifests. secret_agent Mimics puppet agent. status View puppet server status.
See 'puppet help subcommand action' for help on a specific subcommand action . See 'puppet help subcommand' for help on a specific subcommand. Puppet v3.7.1
=== Module Tests === PS C:\puppet module install puppetlabs-acl [mNotice: Preparing to install into C:/ProgramData/PuppetLabs/puppet/etc/modules ... [0m
Jira (PUP-3214) Smoke test packages
Title: Message Title Rob Reynolds commented on an issue Re: Smoke test packages Windows 2012 x64 === Versions === PS C:\puppet --version 3.7.1 --- Operation time for (puppet --version): 00:00:01.2289636 --- --- PS C:\facter --version 2.2.0 --- Operation time for (facter --version): 00:00:00.1734688 --- --- PS C:\hiera --version 1.3.4 --- Operation time for (hiera --version): 00:00:00.1743495 --- --- PS C:\cmd /c environment.bat where ruby ruby --version c:\Program Files\Puppet Labs\Puppet\sys\ruby\bin\ruby.exe ruby 2.0.0p481 (2014-05-08) [x64-mingw32] --- Operation time for (cmd /c environment.bat where ruby ruby --version): 00:00:00.1490819 --- --- === Help Commands === PS C:\puppet help Usage: puppet subcommand [options] action [options] Available subcommands: agent The puppet agent daemon apply Apply Puppet manifests locally caLocal Puppet Certificate Authority management. catalog Compile, save, view, and convert catalogs. cert Manage certificates and requests certificate Provide access to the CA for certificate management. certificate_request Manage certificate requests. certificate_revocation_list Manage the list of revoked certificates. configInteract with Puppet's settings. describe Display help about resource types deviceManage remote network devices doc Generate Puppet documentation and references facts Retrieve and store facts. file Retrieve and store files in a filebucket filebucketStore and retrieve files in a filebucket help Display Puppet help. inspect Send an inspection report instrumentation_data Manage instrumentation listener accumulated data. DEPRECATED. instrumentation_listener Manage instrumentation listeners. DEPRECATED. instrumentation_probe Manage instrumentation probes. Deprecated key Create, save, and remove certificate keys. kick Remotely control puppet agent man Display Puppet manual pages. masterThe puppet master daemon moduleCreates, installs and searches for modules on the Puppet Forge. node View and manage node definitions. parserInteract directly with the parser. pluginInteract with the Puppet plugin system. queue Deprecated queuing daemon for asynchronous storeconfigs reportCreate, display, and submit reports. resource The resource abstraction layer shell resource_type View classes, defined resource types, and nodes from all manifests. secret_agent Mimics puppet agent. statusView puppet server status. See 'puppet help subcommand action' for help on a specific subcommand action. See 'puppet help subcommand' for help on a specific subcommand. Puppet v3.7.1 --- Operation time for (puppet help): 00:00:09.5820659 --- --- PS C:\puppet help apply puppet-apply(8) -- Apply Puppet manifests locally SYNOPSIS Applies a standalone Puppet manifest to the local system. USAGE - puppet apply [-h|--help] [-V|--version] [-d|--debug] [-v|--verbose] [-e|--execute] [--detailed-exitcodes] [-L|--loadclasses] [-l|--logdest syslog|eventlog|FILE|console] [--noop] [--catalog catalog] [--write-catalog-summary] file DESCRIPTION --- This is the standalone puppet execution tool; use it to apply individual manifests. When provided with a modulepath, via command line or config file, puppet apply can effectively mimic the catalog that would be served by puppet
Jira (PUP-3214) Smoke test packages
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-3214 Smoke test packages Change By: Rob Reynolds Proceduremayvarybyprojectandpointinthereleasecycle.Askaround.Ingeneralthisshouldhappenonavarietyofplatforms,i.e.oneortwoeachofkindofpackagewecreate(i.e.,gem,dmg,msi,deb,rpm,etc).LightertestingofZreleasesisacceptable.*AddalinktothePackagesrepositorythatyoureceivefromtheTagandcreatepackagessubtask*Pingfolksonyourteamforhelpwithdifferentplatforms.*Whenyoupickupaplatform,pleaseleaveacommentbelowthatyouaretestingit.Whenitlooksgood,leaveanothercomment,preferablywithacodesnippetshowingthecommandsexecutedandtheiroutput.*IfyoursmoketestingincludesMSIs,youwillgenerallytestonotherplatformsfirstandwhenthatislookinggood,pingtheReleaseEngineerthatbuilttheotherpackagestomoveforwardwithMSIs(theyrequiretagstobepushed).Thisticketdoesn'tcloseuntilallchosenplatforms(includingMSIs)havebeentested.*Whenallplatformspickedhavebeensmoketested,movethistickettodone.Smoketestplatforms:*--OSX--* -- Windows2008/2012(MSIinstallx86x64) -- *--Anything(Geminstall):onrhel7--Smoketestprocedure:*Start/stop/restartanagent(Windows)*Help/man(All)*Writeandrunsomemanifests(All) Add Comment 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.
Jira (PUP-3214) Smoke test packages
Title: Message Title Rob Reynolds commented on an issue Re: Smoke test packages Windows 2008 x64 === Versions === PS C:\puppet --version 3.7.1 --- Operation time for (puppet --version): 00:00:01.0210807 --- --- PS C:\facter --version 2.2.0 --- Operation time for (facter --version): 00:00:00.2730952 --- --- PS C:\hiera --version 1.3.4 --- Operation time for (hiera --version): 00:00:00.1806556 --- --- PS C:\cmd /c environment.bat where ruby ruby --version c:\Program Files\Puppet Labs\Puppet\sys\ruby\bin\ruby.exe ruby 2.0.0p481 (2014-05-08) [x64-mingw32] --- Operation time for (cmd /c environment.bat where ruby ruby --version): 00:00:00.8621649 --- --- === Help Commands === PS C:\puppet help Usage: puppet subcommand [options] action [options] Available subcommands: agent The puppet agent daemon apply Apply Puppet manifests locally caLocal Puppet Certificate Authority management. catalog Compile, save, view, and convert catalogs. cert Manage certificates and requests certificate Provide access to the CA for certificate management. certificate_request Manage certificate requests. certificate_revocation_list Manage the list of revoked certificates. configInteract with Puppet's settings. describe Display help about resource types deviceManage remote network devices doc Generate Puppet documentation and references facts Retrieve and store facts. file Retrieve and store files in a filebucket filebucketStore and retrieve files in a filebucket help Display Puppet help. inspect Send an inspection report instrumentation_data Manage instrumentation listener accumulated data. DEPRECATED. instrumentation_listener Manage instrumentation listeners. DEPRECATED. instrumentation_probe Manage instrumentation probes. Deprecated key Create, save, and remove certificate keys. kick Remotely control puppet agent man Display Puppet manual pages. masterThe puppet master daemon moduleCreates, installs and searches for modules on the Puppet Forge. node View and manage node definitions. parserInteract directly with the parser. pluginInteract with the Puppet plugin system. queue Deprecated queuing daemon for asynchronous storeconfigs reportCreate, display, and submit reports. resource The resource abstraction layer shell resource_type View classes, defined resource types, and nodes from all manifests. secret_agent Mimics puppet agent. statusView puppet server status. See 'puppet help subcommand action' for help on a specific subcommand action. See 'puppet help subcommand' for help on a specific subcommand. Puppet v3.7.1 --- Operation time for (puppet help): 00:00:01.3906886 --- --- PS C:\puppet help apply puppet-apply(8) -- Apply Puppet manifests locally SYNOPSIS Applies a standalone Puppet manifest to the local system. USAGE - puppet apply [-h|--help] [-V|--version] [-d|--debug] [-v|--verbose] [-e|--execute] [--detailed-exitcodes] [-L|--loadclasses] [-l|--logdest syslog|eventlog|FILE|console] [--noop] [--catalog catalog] [--write-catalog-summary] file DESCRIPTION --- This is the standalone puppet execution tool; use it to apply individual manifests. When provided with a modulepath, via command line or config file, puppet apply can effectively mimic the catalog that would be served by puppet
Jira (PUP-3214) Smoke test packages
Title: Message Title Rob Reynolds commented on an issue Re: Smoke test packages The sheer speed of the x64 on windows is crazy. It's about 2x as fast in compiling and running catalogs locally. Add Comment Puppet / PUP-3214 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). Lighter testing of Z releases is acceptable. * Add a link to the Packages repository that you receive from the Tag and create pa... 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.
Jira (PUP-3214) Smoke test packages
Title: Message Title Andy Parker assigned an issue to Hailee Kenney Puppet / PUP-3214 Smoke test packages Change By: Andy Parker Assignee: AndyParker HaileeKenney Add Comment 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.
Jira (PUP-3214) Smoke test packages
Title: Message Title Andy Parker created an issue Puppet / PUP-3214 Smoke test packages Issue Type: Sub-task Assignee: Andy Parker Created: 09/Sep/14 10:43 AM Priority: Normal Reporter: Andy Parker 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). 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. If your smoke testing includes MSIs, you will generally test on other platforms first and when that is looking good, ping the Release Engineer that built the other packages to move forward with MSIs (they require tags to be pushed). This ticket doesn't close until all chosen platforms (including MSIs) have been tested. When all platforms picked have been smoke tested, move this ticket to done.
