<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace">Alex,</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">That is just a short report that QA team needs for their convenience. Please consider this letter as just FYI, nothing more. </div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">'shotgun report' allows you to see commit SHA from which a package was built. It is even more information than it was available in version.yaml and this information is actual unlike the content of version.yaml.</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">I know you were opposing getting rid of version.yaml but the thing is Fuel now can be installed on any CentOS 7.2 node directly from RPM repository. You don't even need the Fuel ISO, and thus version.yaml could not be an artifact that we could rely on (no ISO build id any more, no sha sums). Instead, now we rely on packages that are currently installed on the master node. The only issue with this approach is the ability to easily reproduce the env having just this list of packages attached to a bug. But it is not worse that it was with version.yaml. </div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">I'm currently working on design draft about modular data driven functional testing. This could also help for troubleshooting. In a nutshell the developer experience will be like: </div><div class="gmail_default" style="font-family:monospace,monospace"> 1) you look at log files (`shotgun dump`) and roughly locate the issue (that allows you to choose respective test case) </div><div class="gmail_default" style="font-family:monospace,monospace"> 2) you run script passing some data to it (data are to come from 'shotgun report --machinereadable' or smth like this) </div><div class="gmail_default" style="font-family:monospace,monospace"> 3) this script builds testing/experimental env for you (env is to include only those components that are respective to chosen test case)</div><div class="gmail_default" style="font-family:monospace,monospace"> 5) you run some tests against this lab and manually do some experiments to kill the bug</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace"> <br></div><div class="gmail_default" style="font-family:monospace,monospace"><br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div>Vladimir Kozhukalov</div></div></div>
<br><div class="gmail_quote">On Mon, Mar 21, 2016 at 5:28 PM, Alex Schultz <span dir="ltr"><<a href="mailto:aschultz@mirantis.com" target="_blank">aschultz@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Mon, Mar 21, 2016 at 7:21 AM, Volodymyr Shypyguzov <span dir="ltr"><<a href="mailto:vshypyguzov@mirantis.com" target="_blank">vshypyguzov@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div><div><div><div>Hi, all<br><br></div>Just wanted to inform you, that shotgun2 now has new command short-report, which allows you to receive shorter and cleaner output for attaching to bug description, sharing, etc.<br><br></div>Usage: shotgun2 short-report<br></div>Example output: <a href="http://paste.openstack.org/show/491256/" target="_blank">http://paste.openstack.org/show/491256/</a><br><br></div></div></div></div></blockquote><div><br></div></span><div>How will we be able to find those specific packages and how will we be able to correlate them with the equivalent commit in the git repository?<br></div><div><br></div><div>Thanks,</div><div>-Alex</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div></div><div>Regards,<br></div><div>Volodymyr<br></div></div></div></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>