Uploaded image for project: 'Red Hat Decision Manager'
  1. Red Hat Decision Manager
  2. RHDM-422

Maven artifacts are not updated in openshift for every new build&deploy

    XMLWordPrintable

Details

    • User Experience
    • GA
    • Hide

      "* create a new project on decision central running on openshift

      • add an asset, for example, a drl rule to the project
      • save, build&deploy the project
      • run a rest client, such as curl to fire the rule in the project creaeted in the previous steps
      • everything works fine so far
      • make the changes in the project, stop/remove the container created in the previous build&deploy
      • do another build&depoy
      • run the same curl client to fire the rule through rest api. The old rule created earlier is invoked. not the latest rule
      • go to openshift terminal check the maven repository, e.g.(/home/jboss/.m2/repository/) and find out the maven artifacts are not updated for the new build"
      Show
      "* create a new project on decision central running on openshift add an asset, for example, a drl rule to the project save, build&deploy the project run a rest client, such as curl to fire the rule in the project creaeted in the previous steps everything works fine so far make the changes in the project, stop/remove the container created in the previous build&deploy do another build&depoy run the same curl client to fire the rule through rest api. The old rule created earlier is invoked. not the latest rule go to openshift terminal check the maven repository, e.g.(/home/jboss/.m2/repository/) and find out the maven artifacts are not updated for the new build"

    Description

      "* create a new project on decision central running on openshift

      • add an asset, for example, a drl rule to the project
      • save, build&deploy the project
      • run a rest client, such as curl to fire the rule in the project creaeted in the previous steps
      • everything works fine so far
      • make the changes in the project, stop/remove the container created in the previous build&deploy
      • do another build&depoy
      • run the same curl client to fire the rule through rest api. The old rule created earlier is invoked. not the latest rule
      • go to openshift terminal check the maven repository, e.g.(/home/jboss/.m2/repository/) and find out the maven artifacts are not updated for the new build"

      Attachments

        Issue Links

          Activity

            People

              rhn-support-fspolti Filippe Spolti
              rhn-gps-cyates christopher yates
              Karel Suta Karel Suta
              Karel Suta Karel Suta
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: