| Age | Commit message (Collapse) | Author | Files |
|---|
|
As requested by Marcin include the PR of the built package as well. This
is already included in the PF variable.
|
|
|
|
|
|
Fixup truncate to forget the the status of previous runs. We will
simply write("") to the file and empty it this way. int(f.read()) will
fail then
|
|
Using the continue option of BitBake can lead to some issues with the
Tinderbox. Even if one build failed the color of the result will be green
as the BuildCompleted event will be send by BitBake.
As a workaround we will store the failure in a tinder-status file in case
of failure (e.g. no Provider or PkgFailed) and will reread on the start.
When the build starts we will truncate the file and remove 'the' error
|
|
broken firewalls
Thanks to the firewall fascists of A???? longer HTTP requests were lost in the corporate firewall. Avoid this situation by sending the data in smaller chunks.
|
|
Reported by Richard, fixing the indention level
of this class.
|
|
Retry to connect the tinderbox a couple of times. This is needed
on machines behind broken routers.
When a package is broken (PackageFailed/TaskFailed) we will clean
the package so we can retry the next time.
|
|
-Exchange <--- and ---> to fix the tinderbox
view
-Add a new line to fix the tinderbox display
for multiple providers.
|
|
Use the MultipleProvider and NoProvider Event to create
reports to the TinderBox.
The message format can be improved now we at least know
if a build failed due a missing provider
|
|
Send the name of the to be build packages. Now
we can see what was intended to be build from
within the log
|
|
-Disable sending of the environment as this somehow
refuses to work from within a screen - dunno why
-The lines of the log messages are ended with a new line
no need to add another empty line.
|
|
-Have a none empty log messages when the build is
completed otherwise the log is not transfered
to the server.
Now the build turns green :)
|
|
Be less verbose do not print the results for now.
A proper fix/configurable one is pending.
|
|
Redo the changes... they were magically lost.
readlines is a sequence, we join them (we might
need to remove the \n)
|
|
-Send the right messages to the TinderBox
-Read the log from the logfiles and send it to the tinderbox
-Add the wish for a more sane and more featurefill reporting
(e.g. less data, less often)
|
|
-Save the assigned machine id to a file
and restore it when needed. BitBake does
not have a 'persistent' cache one could use
across files...
-Post the configuration directly to the server
|
|
Begin of the rewrite to support the tbox3 protocol
|
|
|
|
-Do not print that stuff... It was not meant to be pushed
|
|
classes/tinderclient.bbclass (which includes the de-reverted change) from
org.openembedded.dev
|
|
monotone merge :-(
|
|
-Document the TINDER_TZ Option. It can either be Europe/Berlin (no kidding)
or a timedelty (e.g. +0200)
openembedded/classes/tinderclient.bbclass:
-Send timenow as UTC + TINDER_TZ offset
-Parse and send starttime as time + UTC
(either set TINDER_START with gmtime or use the most recent
bitbake from trunk for having BUILDSTART as UTC time)
|
|
-Use spaces only, no more tabs to avoid issues with python
and level of indention
|
|
-No reason to include 'make' from bb. Specially as it was
removed some time ago...
|
|
-A beginning new line... makes process_builds... thanks
to mithro...
|
|
-Make the other part of this class work (finish the bb.data -> data. work)
|
|
-event.data -> data in tinder_send_email
-implement HTTP post (untested)
set TINDER_SENDLOG to 'http'
set TINDER_HOST to ewi....nl
set TINDER_URL to /OE_qa/cgi-bin/process_builds.cgi
|
|
-Prepare the way for HTTP post
|
|
-s/base_/tinder_/
|
|
-Use the BUILDSTART as the starttime for the tinderbox.
In every none malicious bbfile this variable should
have the same time.
|
|
-Fix indention of the final report mail. Now success or failure
should be mail to the tinderbox.
|
|
-setting and reading make.cfg can not work
conf/tinder.conf:
-set TINDER_START there for now...
|
|
-Add a TINDER_SUBJECT field, mails will carry that subject
tinder.conf:
-Mention TINDER_TREE and TINDER_SUBJECT. Without TINDER_TREE the
tinderbox will not know how to associate your report.
|
|
-Fix spacing and imports now we can test the tinderclient
|
|
|
|
turn OE into a tinderclient on its own. One can make any
oe build send tinder reports to a tinderbox.
BKrev: 42b9e243QjUOC_fqMR_9oUZFtmCf9Q
|
