<?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>9727</bug_id>
          
          <creation_ts>2016-06-07 21:50:56 +0000</creation_ts>
          <short_desc>Add autobuilder support to publish sstate objects for releases</short_desc>
          <delta_ts>2017-03-14 18:22:03 +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>2.2</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>VERIFIED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>High</priority>
          <bug_severity>enhancement</bug_severity>
          <target_milestone>2.3 M1</target_milestone>
          
          <blocked>9596</blocked>
          <everconfirmed>1</everconfirmed>
          <reporter name="Bill Randle">bill.randle</reporter>
          <assigned_to name="Joshua Lock">joshuagloe</assigned_to>
          <cc>bluelightning</cc>
    
    <cc>infras.ab.watcher</cc>
    
    <cc>Infras.watcher</cc>
    
    <cc>jose.perez.carranza</cc>
    
    <cc>joshuagloe</cc>
    
    <cc>sgw</cc>
          
          <qa_contact name="Juan Ramos">juan.fernandox.ramos.frayle</qa_contact>
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>Don&apos;t know</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>62731</commentid>
    <comment_count>0</comment_count>
    <who name="Bill Randle">bill.randle</who>
    <bug_when>2016-06-07 21:50:56 +0000</bug_when>
    <thetext>It would be useful and beneficial to the Yocto community to add support on the Autobuilder for building and publishing eSDK package artifacts.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>62751</commentid>
    <comment_count>1</comment_count>
    <who name="Paul Eggleton">bluelightning</who>
    <bug_when>2016-06-08 04:37:39 +0000</bug_when>
    <thetext>I&apos;m not quite sure what you mean here. We build the eSDK installer itself; as far as things you can install using devtool sdk-install, that&apos;s simply done from the shared state cache (or more precisely, a mirror set up via SSTATE_MIRRORS).</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>62820</commentid>
    <comment_count>2</comment_count>
    <who name="Bill Randle">bill.randle</who>
    <bug_when>2016-06-09 14:55:39 +0000</bug_when>
    <thetext>Yes, when I said packages earlier that was incorrect. What we want to create are SSTATE objects, as Paul indicated.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>66706</commentid>
    <comment_count>3</comment_count>
    <who name="Joshua Lock">joshuagloe</who>
    <bug_when>2016-09-28 22:41:21 +0000</bug_when>
    <thetext>The goal is to provide publicly usable sstate objects for consumption both by users of the project (eSDK and general builds) and for use by our automated QA.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>68443</commentid>
    <comment_count>4</comment_count>
    <who name="Joshua Lock">joshuagloe</who>
    <bug_when>2016-11-18 16:43:25 +0000</bug_when>
    <thetext>Brain dumping some thoughts:

We need to publish not only sstate objects generated by the build, but also sstate objects used by the build.

A slightly hacky approach would be that when the custom_release_me property is set we set up a separate, empty, SSTATE_DIR and set up an http mirror of the cluster&apos;s shared sstate directory. Then when any hits in the mirror are found they will be fetched to the new SSTATE_DIR and we can then publish the entire contents of that directory for the build.

The reason we would set up a http mirror, instead of using a file mirror, is because in the case of file mirrors files in the mirror aren&apos;t fetched/copied. It might be worth investigating file mirrors as a slightly cleaner approach.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>68715</commentid>
    <comment_count>5</comment_count>
    <who name="Joshua Lock">joshuagloe</who>
    <bug_when>2016-11-30 13:33:14 +0000</bug_when>
    <thetext>Implementation has begun on an approach which uses the autobuilders published sstate mirror with a per-release sstate directory.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>68862</commentid>
    <comment_count>6</comment_count>
    <who name="Joshua Lock">joshuagloe</who>
    <bug_when>2016-12-06 16:32:28 +0000</bug_when>
    <thetext>http://git.yoctoproject.org/clean/cgit.cgi/yocto-autobuilder/commit/?id=c8e7a8ce382139dde534b533134a4445c25f0d98</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>71274</commentid>
    <comment_count>7</comment_count>
    <who name="Juan Ramos">juan.fernandox.ramos.frayle</who>
    <bug_when>2017-03-14 18:22:03 +0000</bug_when>
    <thetext>http://sstate.yoctoproject.org/dev/2.3/</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>