Uploaded image for project: 'GENIVI Development Platform'
  1. GENIVI Development Platform
  2. GDP-414 GDP 11 RC3 release
  3. GDP-416

Pre-deployment: prepare images and metadata of GDP 11 RC3



    • Type: Sub-task
    • Status: Done
    • Priority: Low
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: GDP 11 RC3
    • Component/s: None
    • Labels:


      Task description

      Deployment preparation and execution of the GDP 11 Release images and metadata. :

      • RPi3


      This task is fully described in the GDP Release Howto document.

      • Create a fresh checkout of the genivi-dev-platform repo using the release branch, `source init.sh`, tar the whole thing up as oe-source.tar.gz and put it in the staging area.
        • This can be simplified to wiping out gdp-src-build/tmp and tarring up the whole thing while excluding everything in gdp-src-build except gdp-src-build/conf bitbake genivi-dev-platform
      • Copy tmp/deploy/licenses/genivi-dev-platform-*/license.manifest into the staging area, through go.cd.
      • Tar up the whole tmp/deploy/source dir as sources.tar.gz and put it in the staging area, through go.cd..
      • Tar up the whole tmp/deploy/licenses dir as licenses.tar.gz and put in the staging area, through go.cd..
      • Copy the image manifest to the staging area.
      • Copy the kernel to the staging area.
      • gzip the rootfs into the staging area.
      • Notify GENIVI IT where they can find all the archives to deploy (in go.cd) through a ticket, inclluding the checksums

      oe sources tarball needs re-deployment

      Changes in the process

      For those interested in the go.cd template currently being used to generate the artifacts, it can be found here: http://go.genivi.org/go/admin/templates/Yocto_GDP_generic_release/stages/build/job/init_and_bitbake/tasks

      For now the go server has to act as the staging area, but I believe it should be possible to directly upload to the genivi ftp server by having a mounted directory, set here: http://go.genivi.org/go/admin/templates/Yocto_GDP_generic_release/stages/build/job/init_and_bitbake/artifacts

      The pipelines are also generating a checksum list of all the artifacts created by the specific pipeline execution (e.g http://go.genivi.org/go/files/Release-RaspberryPi3/2/build/1/init_and_bitbake/raspberrypi3/checksums.txt) This should add more automation to the release cycle.


          Issue Links



              tom.pollard Tom Pollard [X] (Inactive)
              toscalix Agustin Benito Bethencourt [X] (Inactive)
              0 Vote for this issue
              3 Start watching this issue