* When a tag occurs the repo tool use the reference to the tag instead
of the head of the MASTER_BRANCH

* The two distros need to have a separate sstate cache

* Waiting for a stable release of the Intel Apollo Lake distro

* Add condition to use public container to store report when a tag
occurs

* The SSH key and configs are no more needed since migrated everything
to https

* Adding support to Edgehog Embedded base and full image

* Separate caches folder to be used for the two distros
* Avoid using cache and downloads for tagged builds
* Reduce expiration policy of the build to 24 hours

Luca Romoli authored 2 years ago and Lorenzo Pagliai committed 2 years ago

- replace some variable in order to make them general and usable for custom projects

* The description shall be filled by the Release Notes file

* This change allows to build on schedule not only on the MASTER_BRANCH
but also on different branches (those on which the schedule is
programmed)

* This is necessary because the SRCBRANCH of the BSP repositories is
forced to be the master in recipe and this would create conflicts
with the SRCREV
* Remove the SSH related config commands since using https with token
* Restiling of the build commands that are moved to two separated bash scripts

* The removed script was necessary as long as the BSP
repositories were in a different group

* Update new stages description in manifest pipeline file
* Update layers integration description in a different file
* Update images
* Remove unused yaml files

* The command is necessary as long as all Edgehog repositories are
private

* Each CPU processor is suggested to have a different sstate-cache folder
* The 'downloads' folder remains unique for all edgehog projects

* For Edgehog embedded images the fs was not deployed and so a fix was
necessary

* This is necessary to guarantee write access to edgehog folder in build
server containing sstate and downloads caches
* Move env initizialization to .initenv
* Reduce build artifacts expiration time to 1 week

* Insert in the local.conf the reference to a common sstate and
downloads folder containing the sstate-cache and downloads to speed up
Yocto build (see https://www.thegoodpenguin.co.uk/blog/improving-yocto-build-time/)
* The folders are loaded as volume in the Docker image by the dedicated
runner

* The artifacts from the weekly release are deployed in an Azure folder
referring to the week of the year
* Change name of the job and link report so that they refer to the
IMAGE_NAME variable insead of RECIPE_NAME
* Full edgehog image is now built as the other on a weekly schedule
* Fix on link report for Apollo Lake products

* The filesystem artifact name now match the image name
* Fix on artifacts name from build and deploy stage

* Insert further variable inheritance for edgehog-embedded jobs
* Insert echo messages for debug

* Fix also on artifacts name construction

* The fix introduce the RECIPE_NAME variable in the job/link log name,
necessary when compiling also embedded distro

* Change "edgehog-base-image" label to "edgehog-things-image" one
* Fix on intel_apl config file
* Fix on AZURE_PATH variable (the edgehog folder is necessary
for the public container release)

* Insert edgehog embedded build/deploy for base and full image for supported
boards
* Full image shall be built only when a tag occurs
* Remove c43 and c26 config files (not yet supported)
* Fix on Link_report.txt

* Change all occurrencies of 'yocto_ng' with 'edgehog' due to group
 rename
* Change all occurrencies of 'kirkstone/develop' with 'kirkstone' due
to master branch rename
* Update documentation references accordingly
* Changelog script loops over MR opened both to 'kirkstone/develop' and
'kirkstone' branch
* Minor fix in notify job