puppetdb 3.2.1 2015-11-09 Release
(PDB-2134)
|
|
Status: | Closed |
Project: | PuppetDB |
Component/s: | None |
Affects Version/s: | None |
Fix Version/s: | PDB 3.2.1 |
Type: | Sub-task | Priority: | Normal |
Reporter: | Wyatt Alt | Assignee: | Russell Mull |
Resolution: | Fixed | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Template: | customfield_10700 104125 |
Sprint: | PuppetDB 2015-11-18 |
Description |
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. Lighter testing of Z releases is acceptable.
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 procedure:
Dependencies:
|