yoctoabb is currently hardcode so clone repo there.
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This means we get more commit information in the UI. It won't trigger
builds unless we configure it to. It also won't import any history,
just new commits while buildbot is running/polling.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The got_revision trick, whilst quite neat, doesn't quite work and is a bit of
a hack breaking other buildbot internals. It gets et late in the builds leaving
a confusing build display in the meantime.
Use a dedicated property to store the "Yocto" build revision instead. This
property will be used by our own custom console UI.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This means the display will show the correct revision before triggering and waiting
for all the builds to complete making the display less confusing.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add the releases subdirectory to the release publishing destination path.
Signed-off-by: Graydon, Tracy <tracy.graydon@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
By default, since the yocto-autobuilder-helper repository is the only
one that buildbot actually checks out in a step, the revision of that is
the one that gets associated with the build; however, it's much more
useful to have the revision set to the poky revision, so add a step that
does that.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If you can't clobber the build directory, check out the helper source
or unpack the repos successfully there's really not much point in
continuing, so stop the build immediately if they fail.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Various errors resulted from not having been able to test the initial
implmentation of get_publish_dest():
* incorrect logic to determine whether a build was a release
* passing a filename rather than a string representing file contents to
json.loads()
* missing parameter on a call to buildbot's IProperties.setProperty()
Further we update the properties passed to the triggered builds via the
Trigger build steps to include the deploy_artefacts and publish_destination
properties.
This patch is able to succesfully supply required information for the
helper scripts to publish artefacts.
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
The deployment instructions assume buildbot is already installed on the
target system.
Furthermore note that a copy of the yocto-autobuilder-helper is required.
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
Based on the SetDest step in the old codebase this function is used to
determine where the artefacts of a build should be published. In order to
avoid overwriting previously published content the function keeps a list of
destinations which have already been created and written to on the
controller and avoids reusing them.
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
Uses the values submitted to the scheduler to determtine the major number
of the release for the purposes of publishing per-major release
shared-state artefacts.
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
Removing the build directory (with rm -fr) can take a significant amount
of time, longer than the standard buildbot timeout, which delays the
builds. Instead, we use the clobberdir script from the helper repository.
This script moves the directory contents out of the way to a location which
is reaped by a background process.
Unfortunately this assumes/requires a copy of the repository is kept in the
home directory of the user running buildbot.
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
Ensure triggered builds have all of the branch_, commit_ and repo_
properties set. Most builders won't use them, but it's simpler to set them
all for all triggered builds than to special case specific builders.
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
A missing comma resulted in the nightly-ppc-lsb and nightly-x86-64 builders
being merged into one.
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
