<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/bitbake/lib/toaster/bldcontrol, branch krogoth</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=krogoth</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=krogoth'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2016-04-06T22:10:30+00:00</updated>
<entry>
<title>bitbake: toaster: get bitbake location from BBBASEDIR</title>
<updated>2016-04-06T22:10:30+00:00</updated>
<author>
<name>Ed Bartosh</name>
<email>ed.bartosh@linux.intel.com</email>
</author>
<published>2016-04-06T16:46:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=52c8740e1be75f8817f47d0769728920c80e52b4'/>
<id>urn:sha1:52c8740e1be75f8817f47d0769728920c80e52b4</id>
<content type='text'>
It was incorrectly assumed in the current code that bitbake is in
../bitbake/bin/ directory. It's not always the case.
Using bitbake from $BBBASEDIR should be .

(Bitbake rev: 6c9e3375d278bee712c41f07428bc82108b9aaae)

Signed-off-by: Ed Bartosh &lt;ed.bartosh@linux.intel.com&gt;
Signed-off-by: Michael Wood &lt;michael.g.wood@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: toaster: use empty token</title>
<updated>2016-04-06T22:10:30+00:00</updated>
<author>
<name>Ed Bartosh</name>
<email>ed.bartosh@linux.intel.com</email>
</author>
<published>2016-04-06T16:46:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=4aafcae5e4dbf74767c185ca79f1c5969b7b1516'/>
<id>urn:sha1:4aafcae5e4dbf74767c185ca79f1c5969b7b1516</id>
<content type='text'>
If client xmlrpc token is not provided in the command line, bitbake
generates random token. Server token in --server-only mode is always
empty. This doesn't allow clients with non-empty tokens to connect
to the server. Specifying empty token should stop generation of
random token and make it possible for clients to communicate with
the server.

(Bitbake rev: b54ec2d7cb9f2fb4ff1e8af11b6ecf97d181272c)

Signed-off-by: Ed Bartosh &lt;ed.bartosh@linux.intel.com&gt;
Signed-off-by: Michael Wood &lt;michael.g.wood@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: toaster: runbuilds Clean up runbuilds</title>
<updated>2016-04-06T22:10:30+00:00</updated>
<author>
<name>Michael Wood</name>
<email>michael.g.wood@intel.com</email>
</author>
<published>2016-04-06T16:46:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=5ce4665f2624f29054891fe8128109d6102ca2f3'/>
<id>urn:sha1:5ce4665f2624f29054891fe8128109d6102ca2f3</id>
<content type='text'>
- Organise the imports into logical groups
- Fix 80 col wrapping
- Remove catch all exceptions
- Log to the toaster log
- Use QuerySet functions such as .first() and Q()

(Bitbake rev: c382f550c62437954205c7dd9c7e1891d5d03945)

Signed-off-by: Michael Wood &lt;michael.g.wood@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: toaster: runbuilds Make runbuilds aware of the build CANCELLED state</title>
<updated>2016-04-06T22:10:30+00:00</updated>
<author>
<name>Michael Wood</name>
<email>michael.g.wood@intel.com</email>
</author>
<published>2016-04-06T16:46:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=55b6fabd75a66a4d3b3ee07525cd5a4dc33ca98e'/>
<id>urn:sha1:55b6fabd75a66a4d3b3ee07525cd5a4dc33ca98e</id>
<content type='text'>
Add handlers to make sure we remove the BuildEnvironment LOCK when we
have cancelled a build.

(Bitbake rev: 23d0a7f9664450a09c2610631b38590a09b33744)

Signed-off-by: Michael Wood &lt;michael.g.wood@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: toaster: bldcontrol models Add a cancelling state the BuildRequest</title>
<updated>2016-04-06T22:10:29+00:00</updated>
<author>
<name>Michael Wood</name>
<email>michael.g.wood@intel.com</email>
</author>
<published>2016-04-06T16:46:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=9dcb9cb2ccf52fa846ce1462e01f045253959328'/>
<id>urn:sha1:9dcb9cb2ccf52fa846ce1462e01f045253959328</id>
<content type='text'>
To accurately reflect the state of a build request we also need a
cancelling state. This is set when we've started a build and then for
whatever reason cancel it, cancelling is not instantaneous so we have
this state to indicate that a cancel is in progress.

Also add a state transition guard. As the state of a BuildRequest can
currently be modified by three processes; Toastergui,
Runbuilds/bldcontrol and the buildinofhelper we cannot say for sure
which process will be running at the time of cancellation so in order to
avoid one of these processes making an incorrect transition only allow
transitions of state to increase.

e.g. CREATED -&gt; QUEUED -&gt; INPROGRESS
And to ignore such requested changes such as
INPROGRESS -&gt; CREATED

(Bitbake rev: 449598c8e6be75bd0c9d59e7bdf859d1d6f83858)

Signed-off-by: Michael Wood &lt;michael.g.wood@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: toaster: update BuildEnvironmentController and BitbakeController</title>
<updated>2016-04-06T22:10:29+00:00</updated>
<author>
<name>Sujith H</name>
<email>sujith.h@gmail.com</email>
</author>
<published>2016-04-06T16:46:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=5f862bb5674b9db54d07c87b9505ce23acae07cb'/>
<id>urn:sha1:5f862bb5674b9db54d07c87b9505ce23acae07cb</id>
<content type='text'>
Remove getBBController function from BuildEnvironmentController.
The constructor of BitbakeController is updated appropriately so that
call can be made to connect to running server.
The call to startBBServer is removed from bbcontroller and  handledin
localhostbecontroller.

[YOCTO #6787]

(Bitbake rev: e15151106aae21d3b164ca868be42bd63905f0a1)

Signed-off-by: Sujith H &lt;sujith.h@gmail.com&gt;
Signed-off-by: Michael Wood &lt;michael.g.wood@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: toaster: bldcontrol Add forceShutDown function to BitbakeController</title>
<updated>2016-04-06T22:10:28+00:00</updated>
<author>
<name>Sujith H</name>
<email>sujith.h@gmail.com</email>
</author>
<published>2016-04-06T16:46:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=f5aa97067f0955b6be5e69b5859d1f3c5624c2da'/>
<id>urn:sha1:f5aa97067f0955b6be5e69b5859d1f3c5624c2da</id>
<content type='text'>
Add forceShutDown function to BitbakeController class. This function
provides a mechanism to cancel the build from toaster. An API which
can be used safely to cancel build and hence shutdown running bitbake
server.

[YOCTO #6787]

(Bitbake rev: 89dc2ee8f5b7255538082ce4f6cb5277839875a8)

Signed-off-by: Sujith H &lt;sujith.h@gmail.com&gt;
Signed-off-by: Michael Wood &lt;michael.g.wood@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: toaster: use bash explicitly</title>
<updated>2016-04-06T22:10:28+00:00</updated>
<author>
<name>Ed Bartosh</name>
<email>ed.bartosh@linux.intel.com</email>
</author>
<published>2016-04-06T16:46:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=c4ae028209c17dae523c1b582276050959ef74de'/>
<id>urn:sha1:c4ae028209c17dae523c1b582276050959ef74de</id>
<content type='text'>
Toaster can't run builds on Ubuntu as default /bin/sh points
to dash there. The reason is that oe-init-build-env can't
be sourced under dash for various reasons. It can be fixed
or work arounded, but it wouldn't fix builds for older releases.
Explicitly using bash to start builds should fix the issue.

(Bitbake rev: e4352603b21d43a8b5d9ee417c036fff0a263d40)

Signed-off-by: Ed Bartosh &lt;ed.bartosh@linux.intel.com&gt;
Signed-off-by: Michael Wood &lt;michael.g.wood@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: toaster: stop bitbake server after the build</title>
<updated>2016-04-06T22:10:28+00:00</updated>
<author>
<name>Ed Bartosh</name>
<email>ed.bartosh@linux.intel.com</email>
</author>
<published>2016-04-06T16:46:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=590a8159aa975db7c22879dddf47211136923feb'/>
<id>urn:sha1:590a8159aa975db7c22879dddf47211136923feb</id>
<content type='text'>
Bitbake server is used only during the build. There is no need
in keeping server running after the build.

Running bitbake -m in the subshell after the build should stop
the server.

(Bitbake rev: 062c68e3e7d00834118fe07ceb0899874be714ae)

Signed-off-by: Ed Bartosh &lt;ed.bartosh@linux.intel.com&gt;
Signed-off-by: Michael Wood &lt;michael.g.wood@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: toaster: add new parameter to _shellcmd</title>
<updated>2016-04-06T22:10:28+00:00</updated>
<author>
<name>Ed Bartosh</name>
<email>ed.bartosh@linux.intel.com</email>
</author>
<published>2016-04-06T16:46:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=a8f6001e0f910bcf60531fca1b1c5ce375390a76'/>
<id>urn:sha1:a8f6001e0f910bcf60531fca1b1c5ce375390a76</id>
<content type='text'>
Added 'nowait' parameter to _shellcmd method to support
running chain of commands in a subshell.

This is going to be used to stop bitbake server after
the build.

(Bitbake rev: 89fae3c8712bfaac48686c58b480e40c1abdcfdc)

Signed-off-by: Ed Bartosh &lt;ed.bartosh@linux.intel.com&gt;
Signed-off-by: Michael Wood &lt;michael.g.wood@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
