Uploaded image for project: 'Service Design and Creation'
  1. Service Design and Creation
  2. SDC-2337

DCAE-DS image versions are not following the SDC naming convention

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Low Low
    • None
    • Dublin Release
    • SDC-DCAE-DS
    • As dcae-ds has been effectively abandoned, this affects all versions after casablanca at least.

      What

      The docker images produced by dcae-ds are not tagged using the same naming convention as the rest of the sdc. This makes it impossible to refer to SDC version in a simple way (like 1.5.0-SNAPSHOT-20190527T152116Z, which works for non-wfd, non-dcae-ds parts). It also makes it unnecessarily hard to get a set of image versions that are supposed to work together as they have been built together or searching for a set of matching images. 

      CSIT tests also currently expect same tag to apply to all SDC images, which does not work here. For this CSIT aspect there is a partial workaround in https://gerrit.onap.org/r/c/sdc/+/88549 but it is better to resolve this actual inconsistency rather than leave workaround all around.

      At the time of writing there are no 1.4* or 1.5* images in ONAP nexus (https://nexus3.onap.org/#browse/search=keyword%3Dworkflow%20AND%20version%3D1.5.0* https://nexus3.onap.org/#browse/search=keyword%3Ddcae)  In contrast rest of SDC has  daily SNAPSHOT versions on 1.5.0 (https://nexus3.onap.org/#browse/search=keyword%3Dsdc%20AND%20version%3D1.5.0-SNAPSHOT*) and had similar also for 1.4.0 snapshots and of course the release version 1.4.0.

      Having been left behind to 1.3.0 level means either that Dublin release versions are built using old oparent and all other dependencies or rebuilt using the same label but different dependencies invalidating the tagging scheme. 

       

      Expected Result

      All sdc images to use a the same tagging convention for more convenience and less version confusion.  

      Reproducible

      Yes, every time

            vasraz vasraz
            t.puha t.puha
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: