<?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>9586</bug_id>
          
          <creation_ts>2016-05-04 17:11:18 +0000</creation_ts>
          <short_desc>document and verify production setup for jenkins ci interaction</short_desc>
          <delta_ts>2025-06-11 08:59:23 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>Toaster</product>
          <component>toaster</component>
          <version>2.2</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>NEW</bug_status>
          <resolution></resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard>   </status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>5.99</target_milestone>
          <dependson>9555</dependson>
          
          <everconfirmed>1</everconfirmed>
          <reporter name="brian avery">brian.avery</reporter>
          <assigned_to name="David Reyna">david.reyna</assigned_to>
          <cc>belen.barros.pena</cc>
    
    <cc>david.reyna</cc>
    
    <cc>jessica.zhang</cc>
    
    <cc>stanciux.mihail</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>Yes (doc changes required)</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>61952</commentid>
    <comment_count>0</comment_count>
    <who name="brian avery">brian.avery</who>
    <bug_when>2016-05-04 17:11:18 +0000</bug_when>
    <thetext>Document and verify that we can set up a Toaster production instance to listen to a jenkins build cluster (say 1 master, 2 slaves) running bitbake builds via scripts.  I would hold off on the doc part until bug 9555 is done so that it can all be documented once.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>68740</commentid>
    <comment_count>1</comment_count>
    <who name="brian avery">brian.avery</who>
    <bug_when>2016-11-30 17:06:20 +0000</bug_when>
    <thetext>There are a couple of ways to structure this.  Toaster should be able to do this without any code changes, but we should test it out to make sure there aren&apos;t any gotchas and add some instructions.

Way 1)
** Jenkins master - Has a production toaster instance set up using mysql as the db.
* Each slave - When the slave starts up the bitbake environment it would also start a toaster instance and point it at the master db:
$source poky/oe-init-build-env
$source toaster start (having the DATABASES var in settings.py set to master-mysql)
** NFS, to allow toaster to see the build artifacts, the build dirs would  probably need to be on a shared nfs drive, if that functionality is important, otherwise, the jenkins ui could be used to accesing those files.
Way 2) Use the EventReplay mechanism to send the events to a Toaster instance running on the Jenkins master. The eventreplay mechanism was recently fixed and is being used for some developer testing:
Bug 9585 and Bug 9852.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>68741</commentid>
    <comment_count>2</comment_count>
    <who name="brian avery">brian.avery</who>
    <bug_when>2016-11-30 17:08:58 +0000</bug_when>
    <thetext>One possible gotcha is that all command line builds show up as the project &quot;Command line builds&quot;. It seems like it might be nice to be able to override this with a variable so I could see &quot;Jenkins Slave 1 build&quot; and &quot;Jenkins Slave 2 build&quot;</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>75469</commentid>
    <comment_count>3</comment_count>
    <who name="brian avery">brian.avery</who>
    <bug_when>2017-07-30 13:34:03 +0000</bug_when>
    <thetext>Moving to M3</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>76135</commentid>
    <comment_count>4</comment_count>
    <who name="brian avery">brian.avery</who>
    <bug_when>2017-08-24 15:25:17 +0000</bug_when>
    <thetext>lacking time :(</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>96895</commentid>
    <comment_count>5</comment_count>
    <who name="Randy MacLeod">randy.macleod</who>
    <bug_when>2023-10-24 14:24:39 +0000</bug_when>
    <thetext>Bulk move from 4.99 or 0.00 to 5.99</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>