Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-24322

Openshift publisher keeps getting more nested

XMLWordPrintable

    • devex #131 April 2017
    • 8
    • Hide

      0) Windows operating system
      1) Remove rsync from the PATH. To check if rsync cannot be detected, simply try to run rsync command in the cmd cli. You can do it via multiple ways: a) go to the installation directory of the sygwin -> to the bin directory -> find there rsync binary and rename it. b) if you have cwRsync installed separately, then uninstall it, or also simply remove it. Finally, command which rsync must output "which: no rsync in <PATH env var>".
      2) Create openshift connection in Openshift Explorer
      3) create any eap application, e.g. jboss-eap70-openshift
      4) wait till pod is built and run.
      5) create server adapter
      6) make changes in the sources and save them.

      Publish will happen. If you continue to do publishes, it will lead to the nested directories.

      Show
      0) Windows operating system 1) Remove rsync from the PATH. To check if rsync cannot be detected, simply try to run rsync command in the cmd cli. You can do it via multiple ways: a) go to the installation directory of the sygwin -> to the bin directory -> find there rsync binary and rename it. b) if you have cwRsync installed separately, then uninstall it, or also simply remove it. Finally, command which rsync must output "which: no rsync in <PATH env var>" . 2) Create openshift connection in Openshift Explorer 3) create any eap application, e.g. jboss-eap70-openshift 4) wait till pod is built and run. 5) create server adapter 6) make changes in the sources and save them. Publish will happen. If you continue to do publishes, it will lead to the nested directories.
    • Workaround Exists
    • Hide

      Make sure to have rsync installed and added to the PATH env variable.

      Show
      Make sure to have rsync installed and added to the PATH env variable.

      During a POC, one of the requirements is that developers want to deploy/test their local changes inside a pod before to commit.

      We noticed that during the publishing or local change.

      ​

      The Publish function, always creates a nested deploy directory inside an existing one.

      For instance inside /opt/eap/standalone/deployments/

      1st Publish:
      deploy/server.war/

      2nd Publish:
      deploy/deploy/server.war/

      3nd Publish:
      deploy/deploy/deploy/server.war/

      So with 3 publish, you end up with 3 deployed same application.

      This happen also inside the local workspaces for the synchronisation:

      .metadata/.plugins/org.jboss.ide.eclipse.as.core/poc-dev@jboss-eap70-openshift

      The EAP7 images is the jboss-eap70-openshift:latest.

      Do you have any idea why this happen?

              dbocharo@redhat.com Dmitrii Bocharov (Inactive)
              rob.stryker Rob Stryker (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: