summaryrefslogtreecommitdiffstats
path: root/scripts/.aglsetup_genconfig.bash
AgeCommit message (Collapse)AuthorFilesLines
2019-07-23aglsetup: add -t|--topic and -V|--version optionsStephane Desneux1-8/+44
New options are: * -t|--topic : add a 'topic' to current setup (default: empty) * -V|--version : display aglsetup version The topic value can be any string and it is propagated to aglsetup.manifest, which in turn is used by distro-build-manifest to put it in DIST_BUILD_TOPIC variable in all build manifests (deploy dir, target image, sdk) Using the --topic option to specify a unique identifier will help to provide a common ID for all builds in the same "family" even if features and layers differ. For this purpose, a topic could be: * a gerrit review id + a patchset number * a project name (git repo) + a Change-Id * a random UUID * ... When run with -V or --version, aglsetup writes its version on stdout and sets the variable AGLSETUP_VERSION then exits. As aglsetup can only be called by being sourced, the AGLSETUP_VERSION variable is finally set in the caller environment. The version can be used for various purposes. The immediate goal is to detect if --topic option is supported or not. Bug-AGL: SPEC-2646 Cherry-picked-from: master (8cbd61a838bfa3f46f66b5641c27c0492ceba2d8) Change-Id: I28184f6b922bac23cc0cdb6892acd36783d18f06 Signed-off-by: Stephane Desneux <stephane.desneux@iot.bzh>
2019-07-22Append a new empty line to features' local template file when setting up AGLBechir Mghirbi1-0/+1
A missing empty line at the end of a feature's local template file will lead to a ParseError error. This patchset will automatically append a new line at the end of the feature's local template file when setting up AGL. Bug-AGL: SPEC-2563 (cherry picked from commit 416600ed6dfd4462a3d8bea770e5fdf5e074ce2f) Signed-off-by: Bechir Mghirbi <bechir.mghirbi@grammer.com> Change-Id: Ica9decdb0bda182de7e25ace4fca6a9f6f7db5ff
2018-11-22distro-build-manifest: don't use BB_ENV_EXTRAWHITEStephane Desneux1-8/+8
To keep the workflow compliant with upstream Yocto projects, it's better to not use BB_ENV_EXTRAWHITE to pass variables to recipes. This commit updates aglsetup to generate the file agl-init-build-env as 'before' (=before the addition of distro-build-manifest) Bug-AGL: SPEC-720, SPEC-1741 Change-Id: I96df245e099c15a1d2425052c4d8cc64363042c8 Signed-off-by: Stephane Desneux <stephane.desneux@iot.bzh>
2018-10-09aglsetup: generate setup manifest fileStephane Desneux1-0/+49
This patch modifies aglsetup to output the execution context in a "setup manifest" located in $builddir/aglsetup.manifest This file can then be processed by another script (distro-manifest-generator.sh) to generate a complete distro manifest at build time. Bug-AGL: SPEC-720, SPEC-1741 Change-Id: I1f9bc8a6d8bc4c659e59ed0025f71ad9e1c86355 Signed-off-by: Stephane Desneux <stephane.desneux@iot.bzh>
2018-09-28Add an AGL revision to the RPM packageRonan Le Martret1-17/+29
* To update a rpm file (with dnf) we need to have a valid rpm revision. Let 2 packages pkg_1 and pkg_2 (built in yocto). If pkg_2 is newer than pkg_1, and one wants to be able to update it with dnf, it must respect some rpm naming rules. if ${pkg_2_name} > ${pkg_1_name} -> pkg_2 is newer than pkg_1 elif ${pkg_2_name} = ${pkg_1_name} and ${pkg_2_revision} > ${pkg_1_revision} -> pkg_2 is newer than pkg_1 else -> pkg_2 is equal or older than pkg_1 Currently, the Yocto build process (used by AGL, so whithout special service) doesn't change revisions for a build. So packages are not updatable from a repository with dnf. * This patch adds an option -r|--rpm-revision <schema> to aglsetup.sh so that RPMs produced by bitbake will have correct revisions suitable for binary publishing. <schema> can be: 'prservice[:<address>]' : Use a PR service daemon. if <address> is not specified, the default value 'localhost:0' is used (shortcut for a PR service started by bitbake) 'timestamp' : Use a generated time stamp (UTC). 'value:<revision>' : Use <revision> explicitly. 'none' : Do nothing. p16: change --rpm-revision options parsing, use UTC timestamps, refactor code p19: remove smart parsing of host:port for prservice option - back to dumb option Bug-AGL: SPEC-920 Change-Id: I1f4c9fd093fa350d19450a12ac1847885740596d Signed-off-by: Ronan Le Martret <ronan.lemartret@iot.bzh> Signed-off-by: Johann CAHIER <johann.cahier@iot.bzh> Signed-off-by: Ronan Le Martret <ronan.lemartret@iot.bzh> Signed-off-by: Stephane Desneux <stephane.desneux@iot.bzh>
2017-11-23aglsetup: exit with error if fragment script failsStephane Desneux1-1/+1
Bug-AGL: SPEC-1002 Change-Id: I93407ca24c67b6b7c4e9aa09325fbf78d01f1c64 Signed-off-by: Stephane Desneux <stephane.desneux@iot.bzh> Reviewed-on: https://gerrit.automotivelinux.org/gerrit/12111 Tested-by: Jenkins Job builder account <agl-jobbuilder@automotivelinux.org> ci-image-build: Jenkins Job builder account <agl-jobbuilder@automotivelinux.org> Reviewed-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
2017-03-01aglsetup: check build dir integrity (no spaces)Stephane Desneux1-1/+9
The absolute build path shouldn't contain any space. Discussion: https://lists.linuxfoundation.org/pipermail/automotive-discussions/2017-February/003522.html Change-Id: If3de580a2a8fd0f944c40f669a9fcd2de7e1f04b Signed-off-by: Stephane Desneux <stephane.desneux@iot.bzh>
2017-01-27scripts/aglsetup: remove duplicate features before generating configStephane Desneux1-2/+2
With features dependencies, it may happen that the final list of features to handle contains duplicates. With recent changes on configuration fragments, this produces some WARNINGS due to multiple inclusions of the same file in the generated local.conf . This commit cleans up the features list resolved internally by removing duplicates before generating local.conf Change-Id: I009c41108086e76b76272e62c8ba9101fcc45437 Signed-off-by: Stephane Desneux <stephane.desneux@iot.bzh>
2016-11-24Convert feature.inc to feature.depJan-Simon Möller1-21/+0
This converts the included features used for CI purposes to use the dependency format introduced. Change-Id: I405af9ffbd6954d0e78b5f738e762a80687337d7 Signed-off-by: Jan-Simon Möller <jsmoeller@linuxfoundation.org>
2016-11-16Add feature shortcuts matching ci systemJan-Simon Möller1-0/+21
These features (shortcuts) do activate the feature set for: - the changeset builds (agl-ci-change-features) - the snapshot builds (agl-ci-snapshot-features) Change-Id: I4972f61b070836fedef8e06d32deaf07b8978dfb Signed-off-by: Jan-Simon Möller <jsmoeller@linuxfoundation.org>
2016-11-08allow dependency between agl featureRonan1-9/+40
* you can add included.inc file for each feature * if features is include into an other feature, they are print during the --help command #source meta-agl/scripts/aglsetup.sh -h ... Available features: [meta-agl] agl-all-features :( agl-demo agl-appfw-smack agl-devel agl-netboot agl-sota ) agl-archiver agl-devel agl-isafw agl-netboot [meta-agl-devel] agl-renesas-kernel [meta-agl-extra] agl-appfw-smack agl-demo :( agl-appfw-smack agl-devel) Change-Id: I4a72abd48f70a9262203acba84fac24d9dd4dce0 Signed-off-by: Ronan <ronan.lemartret@iot.bzh>
2016-10-19Add shortcut to enable all featuresJan-Simon Möller1-0/+9
This change introduces an agl-all-features flag. It is basically a feature that will enable a list of 'known-good' features from an included file. It is meant to serve two purposes: - simplify automation scripts - ease-of-use for users building the whole set of features Change-Id: Ia962d6ec8a6c6345fb27e303cabbf805e729a8ca Signed-off-by: Jan-Simon Möller <jsmoeller@linuxfoundation.org>
2016-10-18Fix aglsetup always succeeded regardless of whether errors or notTadao Tanikawa1-11/+11
The aglsetup is always succeeded regardless of whether got errors while executing sub scripts or not. This is caused by following script. call_func 2>&1 | tee xxxx.log The result of this line always becomes 0 (succeeded) by result of command 'tee'. The '$PIPESTATUS[]' should be used for this case. Change-Id: I67bf0dbc86331ec7858bd8edb4739a5e7729275b Signed-off-by: Tadao Tanikawa <tanikawa.tadao@jp.panasonic.com>
2016-09-09aglsetup.sh: handle machines/features from any layerStephane Desneux1-12/+45
This patch allows the setup script called by scripts/aglsetup.sh to search for available machines and features in all repositories located in the meta directory (the directory where meta-agl has been cloned). In particular, this now allows to specify a machine or a feature located in meta-agl-devel. Important note: duplicate machines or features in different layers are detected and forbidden (script fails with error) to avoid any ambiguity. Change-Id: If55105a05889ca95da856d65986a86f4ef5f4b2c Signed-off-by: Stephane Desneux <stephane.desneux@iot.bzh>
2016-07-08aglsetup script: fix interactive execution of the script generated from ↵Stephane Desneux1-1/+1
fragments This fixes the problem with Qualcomm boards where EULA approval is required. See: https://lists.linuxfoundation.org/pipermail/automotive-discussions/2016-July/002279.html Change-Id: Ifad216bf559a246d6883e7c2828dacd7bd225075 Signed-off-by: Stephane Desneux <stephane.desneux@iot.bzh>
2016-07-05new configuration templates based on fragmentsStephane Desneux1-0/+400
This is the application of the process proposed here: https://lists.linuxfoundation.org/pipermail/automotive-discussions/2016-June/002232.html Bug-AGL: SPEC-180 Change-Id: I5a7015fa810547a9ecf4fb096367323af3cdc670 Signed-off-by: Stephane Desneux <stephane.desneux@iot.bzh>