<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>4480</bug_id>
          
          <creation_ts>2013-05-10 08:32:16 +0000</creation_ts>
          <short_desc>Autobuilder emails are unreadable and pretty useless</short_desc>
          <delta_ts>2013-07-29 18:07:07 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>5</classification_id>
          <classification>Infrastructure</classification>
          <product>AutoBuilder</product>
          <component>autobuilder</component>
          <version>unspecified</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium+</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>1.5 M2</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Richard Purdie">richard.purdie</reporter>
          <assigned_to name="Beth Flanagan">elizabeth.flanagan</assigned_to>
          <cc>bluelightning</cc>
    
    <cc>elizabeth.flanagan</cc>
    
    <cc>infras.ab.watcher</cc>
    
    <cc>Infras.watcher</cc>
    
    <cc>ross.burton</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>---</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>33028</commentid>
    <comment_count>0</comment_count>
    <who name="Richard Purdie">richard.purdie</who>
    <bug_when>2013-05-10 08:32:16 +0000</bug_when>
    <thetext>The emails from the autobuilder are pretty shocking for usability. 

a) Trying to figure out that:
&quot;&quot;&quot;
Build Properties: Properties(**{u&apos;bb_trigger_meta-fsl-arm_poky-tiny&apos;: None, u&apos;branch_trigger_meta-intel_poky-tiny&apos;: None, u&apos;branch_trigger_meta-fsl-ppc_poky-tiny&apos;: None, &apos;repourl_poky&apos;: u&apos;git://git.yoctoproject.org/poky&apos;, &apos;got_revision&apos;: &apos;00ab7c884b614d23a4ce6c17f07c612ecc9c7319&apos;, u&apos;scheduler&apos;: u&apos;trigger_poky-tiny&apos;, &apos;branch_meta-qt3&apos;: u&apos;danny&apos;, u&apos;repo_trigger_meta-fsl-arm_poky-tiny&apos;: None, u&apos;repo_trigger_bitbake_poky-tiny&apos;: None, &apos;got_revision_poky&apos;: &apos;00ab7c884b614d23a4ce6c17f07c612ecc9c7319&apos;, u&apos;branch_trigger_meta-fsl-arm_poky-tiny&apos;: None, u&apos;branch_trigger_eclipse-poky_poky-tiny&apos;: None, &apos;commit_meta-qt3&apos;: u&apos;HEAD&apos;, u&apos;branch_trigger_meta-qt3_poky-tiny&apos;: u&apos;danny&apos;, u&apos;bb_trigger_oecore_poky-tiny&apos;: None, u&apos;branch_trigger_bitbake_poky-tiny&apos;: None, u&apos;commit_trigger_meta-fsl-ppc_poky-tiny&apos;: None, &apos;revision&apos;: u&apos;00ab7c884b614d23a4ce6c17f07c612ecc9c7319&apos;, u&apos;bb_trigger_bitbake_poky-tiny&apos;: None, u&apos;branch_trigger_poky_poky-tiny&apos;: u&apos;danny&apos;, u&apos;repo_trigger_poky_poky-tiny&apos;: u&apos;git://git.yoctoproject.org/poky&apos;, &apos;commit-description&apos;: &apos;1.3&apos;, u&apos;bb_trigger_meta-fsl-ppc_poky-tiny&apos;: None, &apos;slavename&apos;: &apos;ab04&apos;, u&apos;branch_trigger_oecore_poky-tiny&apos;: None, &apos;branch&apos;: u&apos;&apos;, u&apos;commit_trigger_poky_poky-tiny&apos;: u&apos;HEAD&apos;, &apos;buildnumber&apos;: 129, &apos;distroversion&apos;: &apos;1.3.2&apos;, u&apos;repo_trigger_meta-intel_poky-tiny&apos;: None, u&apos;bb_trigger_poky_poky-tiny&apos;: u&apos;1&apos;, &apos;workdir&apos;: &apos;/srv/home/pokybuild/yocto-autobuilder-new/yocto-slave/poky-tiny&apos;, u&apos;bb_trigger_meta-qt3_poky-tiny&apos;: u&apos;2&apos;, &apos;commit_poky&apos;: u&apos;HEAD&apos;, &apos;repository&apos;: &apos;&apos;, &apos;buildername&apos;: &apos;poky-tiny&apos;, u&apos;DEST&apos;: u&apos;/srv/www/vhosts/autobuilder.yoctoproject.org/pub/nightly/20130509-1&apos;, u&apos;commit_trigger_meta-intel_poky-tiny&apos;: None, &apos;codebase&apos;: &apos;&apos;, u&apos;commit_trigger_meta-qt3_poky-tiny&apos;: u&apos;HEAD&apos;, &apos;got_revision_meta-qt3&apos;: &apos;c86fb1727ae09526c442ec29fffde3f010aa70eb&apos;, u&apos;repo_trigger_meta-qt3_poky-tiny&apos;: u&apos;git://git.yoctoproject.org/meta-qt3&apos;, u&apos;commit_trigger_eclipse-poky_poky-tiny&apos;: None, u&apos;repo_trigger_eclipse-poky_poky-tiny&apos;: None, u&apos;repo_trigger_meta-fsl-ppc_poky-tiny&apos;: None, u&apos;commit_trigger_bitbake_poky-tiny&apos;: None, u&apos;bb_trigger_eclipse-poky_poky-tiny&apos;: None, u&apos;commit_trigger_meta-fsl-arm_poky-tiny&apos;: None, &apos;project&apos;: &apos;&apos;, u&apos;repo_trigger_oecore_poky-tiny&apos;: None, u&apos;commit_trigger_oecore_poky-tiny&apos;: None, u&apos;bb_trigger_meta-intel_poky-tiny&apos;: None, &apos;branch_poky&apos;: u&apos;danny&apos;, &apos;repourl_meta-qt3&apos;: u&apos;git://git.yoctoproject.org/meta-qt3&apos;}) 
means danny is much harder than it needs to be. This needs to be formatted somehow and to place the key information at the top of the email.

b) The emails don&apos;t say what failed in many cases. You have to follow the link to find out it was &quot;Publishing Layer Tarballs&quot; that failed for example, there is no indication in the email.

We can do better than this. I&apos;m filing a bug to ensure tit gets tracked/fixed.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>33033</commentid>
    <comment_count>1</comment_count>
    <who name="Paul Eggleton">bluelightning</who>
    <bug_when>2013-05-10 09:01:10 +0000</bug_when>
    <thetext>This has been bothering me as well - just deciphering which branch being built is a bit of a struggle.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>33034</commentid>
    <comment_count>2</comment_count>
    <who name="Ross Burton">ross.burton</who>
    <bug_when>2013-05-10 09:07:57 +0000</bug_when>
    <thetext>If the branches used could be pulled out and displayed in a nice way at the top, that would be useful.  Bonus points for putting them into headers for filtering too.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>33157</commentid>
    <comment_count>3</comment_count>
    <who name="Beth Flanagan">elizabeth.flanagan</who>
    <bug_when>2013-05-20 17:51:49 +0000</bug_when>
    <thetext>I agree. This is on my radar (as well as a lot of usability issues this release.)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>35126</commentid>
    <comment_count>4</comment_count>
    <who name="Beth Flanagan">elizabeth.flanagan</who>
    <bug_when>2013-07-29 18:07:07 +0000</bug_when>
    <thetext>I&apos;m going to mark this closed as the build emails are much better now. We will continue on improving this, but they&apos;re much better now.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>