Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-18441

curator/curator-cli need to support artifacts that only have productization-version / productization-name

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • Undetermined
    • None
    • None
    • False
    • False
    • % %
    • Todo

      For Camel Spring Boot and for Camel Quarkus (and any future products) it would be nice to have the option of not doing a dev build and building only in CPaaS/PNC.    Once complication would be curator - which requires a dev build artifact-name/artifact-version for built artifacts :

      curator curate --release-name fuse-7.10 --milestone-name AR13 --state-name productization-completed --artifact-name fuse-components-7.10.0 --artifact-version 7.10.0.fuse-sb2-7_10_1-00006 --productization-name fuse-components-7.10.0 --productization-version 7.10.0.fuse-sb2-7_10_1-00006-redhat-00001 --artifact-type jar --state-name productization-completed 

      I'm not sure what the best option here would be - should we make artifact-name/artifact-version optional and leave them blank?    If you did something like 

      curator curate --release-name fuse-7.10 --milestone-name AR13 --state-name productization-completed --productization-name fuse-components-7.10.0 --productization-version 7.10.0.fuse-sb2-7_10_1-00006-redhat-00001 --artifact-type jar --state-name productization-completed

      should curator attempt to match artifact-name / artifact-version, and if not, just use the productization-name/productization-version in place of them or should they be left blank?    Are there other options for supporting both builds with dev-build portions and those without?

              var@redhat.com Vaishnavi R
              tcunning@redhat.com Thomas Cunningham
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: