-
Bug
-
Resolution: Fixed
-
Major
-
Linux, java 1.7, Jenkins 1.594, weblogic deployer 2.13
Specifying the full path in base directory is very error prone. I'm trying to utilize the update that allows for not specifying the basedirectory as a full path to an artifact.
This is a for a freestyle project built entirely in the workspace with Gradle.
The artifact is in a sub folder of workspace. The folder is found, however the artifact is not. It doesn't seem to be searching recursively.
Specifying the path to the workspace folder as base directory does recurse and find the war.
File structure:
workspace
- build
- libs
- my.war
- libs
Console snippet:
[WeblogicDeploymentPlugin] - The JDK /usr/java/jdk1.7.0_45/jre will be used.
[WeblogicDeploymentPlugin] - ArtifactSelector used : org.jenkinsci.plugins.deploy.weblogic.FreeStyleJobArtifactSelectorImpl@6c55b99a
[WeblogicDeploymentPlugin] - Retrieving artifacts recorded [filtered resources on (.*).war]...
[WeblogicDeploymentPlugin] - 1 files found under workspace
[WeblogicDeploymentPlugin] - the following resource build doesn't match (.*).war
java.lang.RuntimeException: [WeblogicDeploymentPlugin] - No artifact to deploy [(.*).war] found.
at org.jenkinsci.plugins.deploy.weblogic.FreeStyleJobArtifactSelectorImpl.selectArtifactRecorded(FreeStyleJobArtifactSelectorImpl.java:77)
at org.jenkinsci.plugins.deploy.weblogic.task.DeploymentTaskServiceImpl.perform(DeploymentTaskServiceImpl.java:152)