Uploaded image for project: 'Drools'
  1. Drools
  2. DROOLS-1357

Container resolved release id version is not changed after auto updated by scanner

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.0.0.Final
    • 7.0.0.Beta2
    • kie server
    • None
    • Hide
      1. Create and build project with version 1.0.0
      2. On kie server deploy container with version 1.0.0
      3. Change in release-id version to LATEST - now can be container auto updated by scanner
      4. Start scanner
      5. Create and build same project with new version 1.0.1
      6. In server console is displayed that: "The following artifacts have been updated {org.kie.example:project:1.0.0=org.kie.example:project:jar:1.0.1}

        "

      7. In container status (or at REST endpoint ...server/containers) is resolved-release-id with version 1.0.0

      Actual result:
      resolved-release-id has version 1.0.0
      Expected result:
      resolved-release-id has version 1.0.1

      Show
      Create and build project with version 1.0.0 On kie server deploy container with version 1.0.0 Change in release-id version to LATEST - now can be container auto updated by scanner Start scanner Create and build same project with new version 1.0.1 In server console is displayed that: "The following artifacts have been updated {org.kie.example:project:1.0.0=org.kie.example:project:jar:1.0.1} " In container status (or at REST endpoint ...server/containers) is resolved-release-id with version 1.0.0 Actual result: resolved-release-id has version 1.0.0 Expected result: resolved-release-id has version 1.0.1
    • NEW
    • NEW

      On kie server container can be auto updated by scanner. When is scanner started and new version of container is deployed in maven repository, then in kie server should be old version replaced by new one.

              psiroky_jira Petr Široký (Inactive)
              psiroky_jira Petr Široký (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: