Anything interesting in the build logs when this occurred? How do you know the file wasn't updated, did you view the file in the workspace?
On 07.08.2013, at 21:50, DAVID HO <[email protected]> wrote: > Hi all, > > I am very new to Jenkins and also to the build process. I have just started > using Jenkins at my workplace. For our build process, we have the source code > store in a remote SVN server and use Maven for the build. For the build > configuration, we had Checkout Strategy as "Use SVN update as much as > possible" to save time. > > Recently, we ran into the problem when updating the POM file. For some > reasons, the new POM files, which located on SVN, was not updated in the > Jenkins' work space even though the source code was. So, to fixed this > problem, I have to clear out the work space folder and start the build again. > This fixed the problem. To prevent this problem from happening in the future, > I have set Checkout Strategy to "Always check out a fresh copy". Does anyone > know why this happens? > > Thanks, > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
