Jira (PDB-2877) Smoke test packages (PDB 1.1.0)

2016-07-20 Thread Andrew Roetker (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Roetker commented on  PDB-2877 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Smoke test packages (PDB 1.1.0)  
 
 
 
 
 
 
 
 
 
 
Tested on el7 with SSL and non-SSL requests. PDB installed via the module. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (PDB-2877) Smoke test packages (PDB 1.1.0)

2016-07-13 Thread Andrew Roetker (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Roetker created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2877 
 
 
 
  Smoke test packages (PDB 1.1.0)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Andrew Roetker 
 
 
 

Created:
 

 2016/07/13 1:51 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Andrew Roetker 
 
 
 
 
 
 
 
 
 
 
(Initial planned release date: 2016-07-20) 
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.