Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-18812

Redeployment feature

    XMLWordPrintable

Details

    Description

      I think it would be interesting to add the redeploy feature in the plugin. I'm new in it, so I'm afraid I cannot develope it by now, but I'm missing this feature in the work I am on charge of.

      By console in my local machine I can do that with de command

      java -cp C:\Oracle\Middleware\wlserver_10.3\server\lib\weblogic.jar weblogic.Deployer -adminurl t3://192.168.100.221:7001 -user weblogic -password weblogic -redeploy -name UniVicWorkspace -source "C:\Users\516230\.jenkins\jobs\PGU PRODUCTIU\workspace\UniVic.ear" -targets AdminServer -upload

      by no way to do the same with the plugin. I'm affraid i will need to create an script to do the task by now.

      My ant build file creates me and ear file with the version able to being redeployed without stopping service to clients.

      Thanks!

      Attachments

        Activity

          miquelserralta Miquel Serralta created issue -

          Hi,

          The plugin execute undeploy then deploy weblogic tasks which seems to be an equivalent of redeploy task. Is there a specific behavior for the redeploy task ?

          raphc Raphael CHAUMIER added a comment - Hi, The plugin execute undeploy then deploy weblogic tasks which seems to be an equivalent of redeploy task. Is there a specific behavior for the redeploy task ?

          Hi and thanks for answering.

          Yes, the redeploy feature allows you to deploy a new version of app without any offline time of the application as current users use old version and new connections use the new version. When no one is using the old version, it is definetly retired and undeployed.

          Thanks

          miquelserralta Miquel Serralta added a comment - Hi and thanks for answering. Yes, the redeploy feature allows you to deploy a new version of app without any offline time of the application as current users use old version and new connections use the new version. When no one is using the old version, it is definetly retired and undeployed. Thanks

          Thanks for this explanation.
          I'll add a new feature which allow the user to set what kind of execution he wants in the next version.

          raphc Raphael CHAUMIER added a comment - Thanks for this explanation. I'll add a new feature which allow the user to set what kind of execution he wants in the next version.
          raphc Raphael CHAUMIER made changes -
          Field Original Value New Value
          Status Open [ 1 ] In Progress [ 3 ]

          I've just released the 2.4 version with a new feature. See 'Override deployment execution' chapter in the plugin documentation

          raphc Raphael CHAUMIER added a comment - I've just released the 2.4 version with a new feature. See 'Override deployment execution' chapter in the plugin documentation
          raphc Raphael CHAUMIER made changes -
          Resolution Fixed [ 1 ]
          Status In Progress [ 3 ] Resolved [ 5 ]

          Gorgeous!! I will try it as soon I can. I let you know.
          Thanks!

          miquelserralta Miquel Serralta added a comment - Gorgeous!! I will try it as soon I can. I let you know. Thanks!

          Hi Raphael. I think it does not work 100%.

          I'm not able to use the

          {wl.source}

          variable. When I use it, it is not replaced by the proper string.

          Moreover, I tried to specify the absolute path where my ear file is created, but it is treated as relative path.

          The custom command I use looks like:

          -debug -remote -verbose -upload -name UniVicWorkspace -source "/root/.jenkins/jobs/PGU TEST/workspace/UniVic.ear" -targets

          {wl.targets}

          -adminurl t3://

          {wl.host}

          :

          {wl.port}

          -user

          {wl.login}

          -password

          {wl.password}

          -redeploy

          It chashes and in the log you can see weblogic.deploy.api.internal.utils.DeployerHelperException: The source file '/home/oracle/Oracle/Middleware/user_projects/domains/uvic/"/root/.jenkins/jobs/PGU' does not exist and cannot be deployed.

          Thanks again. Nice job!

          miquelserralta Miquel Serralta added a comment - Hi Raphael. I think it does not work 100%. I'm not able to use the {wl.source} variable. When I use it, it is not replaced by the proper string. Moreover, I tried to specify the absolute path where my ear file is created, but it is treated as relative path. The custom command I use looks like: -debug -remote -verbose -upload -name UniVicWorkspace -source "/root/.jenkins/jobs/PGU TEST/workspace/UniVic.ear" -targets {wl.targets} -adminurl t3:// {wl.host} : {wl.port} -user {wl.login} -password {wl.password} -redeploy It chashes and in the log you can see weblogic.deploy.api.internal.utils.DeployerHelperException: The source file '/home/oracle/Oracle/Middleware/user_projects/domains/uvic/"/root/.jenkins/jobs/PGU' does not exist and cannot be deployed. Thanks again. Nice job!
          miquelserralta Miquel Serralta made changes -
          Resolution Fixed [ 1 ]
          Status Resolved [ 5 ] Reopened [ 4 ]

          Sorry. I didn't see the issue #JENKINS-18940.

          miquelserralta Miquel Serralta added a comment - Sorry. I didn't see the issue # JENKINS-18940 .
          miquelserralta Miquel Serralta added a comment - # JENKINS-18940
          miquelserralta Miquel Serralta made changes -
          Resolution Fixed [ 1 ]
          Status Reopened [ 4 ] Resolved [ 5 ]

          The bug has been fixed in 2.5

          The plugin finds the resource file to deploy according to the job configuration whatever the command line you set.
          Even if you specify the resource directly, the plugin tries to detect the resource file to deploy before executing task in the same way as you didn't ovveride command.

          Let see the documentation for further information.

          Regards

          raphc Raphael CHAUMIER added a comment - The bug has been fixed in 2.5 The plugin finds the resource file to deploy according to the job configuration whatever the command line you set. Even if you specify the resource directly, the plugin tries to detect the resource file to deploy before executing task in the same way as you didn't ovveride command. Let see the documentation for further information. Regards
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 150162 ] JNJira + In-Review [ 193440 ]
          raphc Raphael CHAUMIER made changes -
          Status Resolved [ 5 ] Closed [ 6 ]

          People

            raphc Raphael CHAUMIER
            miquelserralta Miquel Serralta
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: