Uploaded image for project: 'Red Hat CodeReady Studio (devstudio)'
  1. Red Hat CodeReady Studio (devstudio)
  2. JBDS-3298

Push changes to Existing OpenShift Project



    • Feature Request
    • Resolution: Done
    • Blocker
    • 9.0.0.Beta2
    • 8.0.0.GA
    • openshift, requirements
    • None


      Use Case #2 Push changes to Existing OpenShift Project
      a) assumes the steps in Use Case #1 JBDS-3297
      b) assumes the end-user has uploaded his SSH keys (to allow for git push)
      c) Eclipse user will add, edit and delete files from the originally downloaded/imported set of files - leveraging Eclipse specialized editors, content-assist, etc
      d) Eclipse user will run (deploy) Maven-based Java projects on a local EAP
      e) Eclipse user will test (JUnit, Arquillian)
      f) Eclipse user will debug with the local EAP (run on localhost or from Docker Image)
      g) Eclipse user will git add and git commit as appropriate
      h) Eclipse user will git push to the original URL provided in Use Case #1
      i) Eclipse user will await the automatic rebuild of a new image, deployment of the same
      j) Eclipse user will then be provided a URL and the browser can be opened automatically

      i) auto-build=true, auto-deploy=true
      assumes the auto-build (.war and docker image) upon git push enabled in Use Case #1c (JBDS-3297). This step also assumes the auto-deploy upon build is enabled in 1c.

      A future variation of #2 should allow for "auto-build=false" and "auto-deploy=true" with hot deployment of the binary .war or .ear.

      If auto-build=false and auto-deploy=false then the Eclipse user will simply receive a message that his git push was successful, no URL, no browser opening.


        Issue Links



              manderse@redhat.com Max Andersen
              bsutter@redhat.com Burr Sutter
              0 Vote for this issue
              6 Start watching this issue