This plugin deploys any artifacts built on Jenkins to a weblogic target (managed server, cluster ...) as an application or a library component.
Before 1.4, the plugin is applicable only for maven 2/3 Job.
Before use it, the plugin has to be configured. It consists of loading the weblogic target configuration, choosing the default JDK to run a deployment task and adding the weblogic library path (i.e /pathtojar/weblogic.jar or/pathtojar/wlfullclient.jar for WL 10.3).
There are 2 kinds of authentication :
Since 2.3, the plugin also supports authentication by keystore. To use it, set authMode with BY_KEY value then set userconfigfile/userkeyfile elements. If you forget to specify authMode with BY_KEY value, the plugin uses the default authentication mode BY_LOGIN.
If no configuration has been set, the plugin will display an error message
If the plugin is already configured, jenkins will display the job plugin configuration form.
Some of parameters can also be tokenized with envrionment variables or even build parameters. Here are these parameters :
Use the build parameter plugin or add some environment variable to set these values
It's possible to set the JDK to use directly in the Job configuration. This option is available in advanced task section. By default if no jdk is specified, the plugin will use the global configuration
For advanced users, it can be useful to define the commands that the deployer has to run instead of the default ones, To enable this feature, the user will set different command lines into the 'Command line' field of Job advanced configuration.
These commands has to be ended by the ';' separator. The following plugin token can be added to the command line :
Note : only the arguments and parameters can be specified. The java executable used to run the command will be figure out by the plugin with the same algorithm than a default execution.
For instance : the user who prefers run deployment with 'distribute' instead of deploy could be set the following command lines:
NB : Environment variables and build parameters can also be used.
The build status will be modified according the following rules :
On the build dashboard a new icon will appear. It displays the deployment status
When you click on your job, a dashboard show a new icon with the date of the last successful deployment. If no deployment occurred or always failed. The date will be replaced by 'N/A' label.
You can view the deployment logs of each task. Simply click on the 'Deployments Statuses' link or 'Weblogic deployments' link. They will appear one by one in the deployment page.
Fixing bug issue #20970 : deployment failed due to an unexpected stream closed exception.
Handled exception when configuration file uploaded is incorrect.
Fixing bug issue #16007
Implementing issue #18685 Added support for customization of deployment targets/environment through build parameters.
Implementing issue #17300 and issue #18812 : Added new feature which allow the advanced user to define his own command to run
Implementing issue #17300 : Supports stage mode choice in job configuration.
Implementing issue #17301 : Supports jdk configuration per job.
Implementing issue #15696 : Supports freestyle project.
Implementing issue #14763 : English translation. The English language is the default plugin language.
Implementing issue #14646 : The old java class or resources prefixed by HudsonXXXX has been refactored to XXXX.
Forked from Hudson version.
Added JDK selection on global configuration.
Removed task abortion if no compatibility detected between the JDK and the weblogic.Deployer API (As of now, It displays a warning).
Fixed translation and spelling errors.
Added WebLogic Server 10.3 support.
Skip to end of metadata Go to start of metadata