Age | Commit message (Collapse) | Author |
|
Signed-off-by: Quentin Schulz <foss@0leil.net>
|
|
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
|
|
Specifically, add more information about various config settings,
add a few important points to README, and remove config file specifics
from README, so that there's only one source for what the settings are
(the sample config file).
Also comment out everything from the config file, so that those in a
hurry can take it into use immediately. Most settings are specific to
a maintainer, and so can't be provided in a 'generic' way.
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
|
|
Signed-off-by: Chang Rebecca Swee Fun <rebecca.swee.fun.chang@intel.com>
|
|
This adds enormously to run time, and is not particularly necessary
when running locally. If something fails, it's best to let the maintainer sort
it out as soon as possible, rather than try to guess what needs to be excluded.
Also, do not build a separate ptest image; ptests will be added
to the standard integration testimage.
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
|
|
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
|
|
directories.
This should help e.g. with the following issue:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7174
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
|
|
Particularly, musl is a notorious source of failures and so it's
very useful to do at least one build against it by default.
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
|
|
It wasn't clear what the option does, and why it need to be on the command line,
so the replacement is a 'global_maintainer_override' config file setting which
does the same thing, in a cleaner fashion.
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
|
|
No longer used since migration to devtool: all upgrades are automatic
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
|
|
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
|
|
[YOCTO #8962]
Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
|
|
Since recipe upgrades are done in isolate manner cleaning the repo
for every recipe [1] the drop_previous_commits becomes deprecated.
Also now we have Testimage integration phase that handles/reports
this kind of errors.
[1] http://git.yoctoproject.org/cgit/cgit.cgi/auto-upgrade-helper/commit/?h=boot_images_v2&id=8769030a02753f09ed6b5e7c98ed1c442a51a466
Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
|
|
Instead of add manually the ptest packages use IMAGE_FEATURE to
install ptest packages this save time validating if ptest pkg
exist.
Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
|
|
Before this commit core-image-sato was hardcoded for image
to test with this commit image name can be specified in
the upgrade-helper.conf.
Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
|
|
Publish setting helps to point the url where the AUH patches and
logs are saved, this url is included into AUH upgrade status email.
Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
|
|
The workdir setting is useful for store the AUH generated patches
into another directory than $BULDDIR/upgrade-helper/work this will
be used to publish AUH work.
Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
|
|
Testimage feature will provide the ability to run testimage
class over a set of succesful upgrades.
Also it will run ptest on recipes that support ptest and retrive
the result for store/send to maintainer.
Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
|
|
Make consistent the enablement for this feature it need to be
explicit enable into upgrade-helper.conf and also needs configuration
in local.conf.
Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
|
|
Add section zero for point that needs Yocto dependencies also git
configured.
Add description about the buildhistory output if upgrade succeed.
Remove mode usage for upgrade two recipes in automatic now is
deprecated the available modes are automatic for all recipes and manual
for one.
[YOCTO #7439]
Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
|
|
Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
|
|
Emails only get sent when "all" is used (at least at the moment).
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Signed-off-by: Marius Avram <marius.avram@intel.com>
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
We want to avoid spamming maintainers, so I've tried to spell out what
will happen if you configure things blindly here.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
The help output shouldn't be too long or it becomes difficult to read.
We can always expand upon it in the accompanying documentation.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|