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

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

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • 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

    Description

      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.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. RHBPMS-4437 (6.4.0)Container resolved release id version is not changed after auto updated by scanner

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: