Issue #6594 has been updated by Daniel Pittman.
I would prefer `git describe` rather than the SHA1, since it has more human information, but is usable the same way. The easy path would be to emit that command in the git setup "test" script, after we do the checkout and all. ---------------------------------------- Bug #6594: SHA1 info should be stored with the test run https://projects.puppetlabs.com/issues/6594 Author: Matt Robinson Status: Unreviewed Priority: Normal Assignee: Category: Target version: Patch: None Keywords: Branch: If you're running the tests against git you can specify a SHA1, but I don't think that gets recorded in the test output. At least not in the summary file in a way that's easy to find. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
