Bug 7914 - toaster should start remote builds through a single script
Summary: toaster should start remote builds through a single script
Status: RESOLVED WONTFIX
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ minor
Target Milestone: Future
Assignee: Ed Bartosh
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-06-22 10:14 UTC by Alexandru Damian
Modified: 2015-10-01 15:47 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandru Damian 2015-06-22 10:14:42 UTC
Toaster should start remote builds (through SSH) by writing a script, transferring it to remote machine and executing it, instead of issue-ing interactive commands.

This is the base of being able to functionality to export a script from Toaster and have this script setup the project configuration, or to execute a build on Jenkins.
Comment 1 Ed Bartosh 2015-06-30 09:35:07 UTC
Copying here information I've got from Alex by e-mail:

Currently, the functionality is broken; what I think we should do is when a
build is triggered on a remote machine:

- get Toaster to write up a shell script that will automatically:
  * checkout needed layers
  * set up configuration files
  * trigger build execution
  * and upload bitbake event data to Toaster using the eventfile mechanism

- deploy said script over SSH and execute it
Comment 2 Ed Bartosh 2015-07-21 09:11:11 UTC
Sent working draft and asked for comments on the mailing list: https://lists.yoctoproject.org/pipermail/toaster/2015-July/002354.html
Comment 3 Ed Bartosh 2015-07-28 16:03:54 UTC
This functionality became out of scope of 1.9 during recent architecture discussion. We should concentrate on local builds.

Moving to feature.
Comment 4 Ed Bartosh 2015-10-01 15:47:44 UTC
This bug is out of scope of any planned work. I don't want it to show up in the list of bugs assigned to me.