My build configuration creates a war artifact in a subdirectory of the workspace root. As the description says (A single WAR or EAR file to deploy, packaged with the appropriate bindings (if applicable). Relative to the workspace root.), I enter a relative path (in my case: mcmod-server/build/libs/missioncontrol.war).

When I run a build, everything is fine. When I run it again, it failes, because Jenkins says "missioncontrol.war cannot be found" and that's correct, since it's in a subdirectory.

So I set the filepath again and successfully run the build. When I have a look at the configuration after the build, the filepath has been truncated to the filename. I can reproduce that after each build.