To ???: A few quick thoughts (since I don't have access to your machine and environment):
- You said you ran the command-line job on the Jenkins server itself? Is this the same physical box where the build ran that's causing problems? Most people are set up with a Jenkins server and then agent machines to actually do the build jobs. - How is your agent configured? If as a service, is it set to interact with the desktop? If it's a manual start agent, is it running under the same user as you did the successful test build? - Can you search the Jenkins build log for that $ character to see if you can tell where it's getting used, and compare that output to your manual job that was successful? If nothing is found, you may want to see about increasing debug output to see where your build differences are. - Are there any environment variable differences between the Jenkins and manual jobs that might impact your build's logic? Hope this helps, Scott On Thu, Apr 10, 2014 at 8:44 AM, liltitus27 . <liltitu...@gmail.com> wrote: > Hi All, > > I'm using Jenkins v1.546, hosted on a Windows Server 2008 R2 SP1 machine. > > I've set up a fairly simple job for building a Maven Java project. It > polls the SCM with no schedule and picks up remote build triggers, > requiring an authentication token. It uses Subversion and performs clean > checkouts with svn update. Additionally, it has a post-build step that > archives some build artifacts (i.e., the resulting WAR and WSDLs). > > The issue I'm experiencing is that the builds that it stores on the > filesystem itself contain invalid characters in their filenames. This > causes our automatic backup process to blow up, it being unable to alter or > remove those directories/files with the '$'. I myself cannot move/delete > those folders or files either, but if I rename it and remove the $, then > things work fine. Oh, and if I try to follow one of these links with the $ > in it, it doesn't resolve. None of the other jobs seem to do this - just > my job, of course. Anyone know why this may be occurring and what I can do > to resolve this? > > > > I've attached multiple screenshots that show the bad filename and my > Jenkins job setup. I had to white out some company information, but if I > can provide any additional information to help troubleshoot this, just let > me know. > > From the command line, on the Jenkins server itself, I ran 'mvn clean > install' on the project workspace as it's hosted in the Jenkins > workspace. This ran fine, produced all needed artifacts, and all tests > passed. None of the resulting files or folders from the maven build > created anything with invalid characters or anything similar to the folders > I'm seeing that are causing issues. > > Also, I did some additional research, looking through the changelogs for > each released version of Jenkins since my version (latest is 1.557). I saw > three possible issues in the changelogs that could be related, but it's > hard for me to tell. I cannot simply upgrade our Jenkins to test out this > theory, since I'll need to provide a reason for upgrading beyond a hunch. > > https://issues.jenkins-ci.org/browse/JENKINS-21023 > https://issues.jenkins-ci.org/browse/JENKINS-20534 > https://issues.jenkins-ci.org/browse/JENKINS-21958 > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
