Bug 9586

Summary: document and verify production setup for jenkins ci interaction
Product: [Build System, Metadata & Runtime] Toaster Reporter: brian avery <brian.avery>
Component: toasterAssignee: David Reyna <david.reyna>
Status: NEW --- QA Contact:
Severity: normal    
Priority: Medium CC: belen.barros.pena, david.reyna, jessica.zhang, stanciux.mihail
Version: 2.2   
Target Milestone: 5.99   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Yes (doc changes required)
Bug Depends on: 9555    
Bug Blocks:    

Description brian avery 2016-05-04 17:11:18 UTC
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.
Comment 1 brian avery 2016-11-30 17:06:20 UTC
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'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.
Comment 2 brian avery 2016-11-30 17:08:58 UTC
One possible gotcha is that all command line builds show up as the project "Command line builds". It seems like it might be nice to be able to override this with a variable so I could see "Jenkins Slave 1 build" and "Jenkins Slave 2 build"
Comment 3 brian avery 2017-07-30 13:34:03 UTC
Moving to M3
Comment 4 brian avery 2017-08-24 15:25:17 UTC
lacking time :(
Comment 5 Randy MacLeod 2023-10-24 14:24:39 UTC
Bulk move from 4.99 or 0.00 to 5.99