[
https://issues.jenkins-ci.org/browse/JENKINS-9714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162163#comment-162163
]
Adam Vollmer commented on JENKINS-9714:
---------------------------------------
I ran into a build issue recently because one of our build scripts changed, so
a now-vestigal directory was causing problems because it was no longer being
cleaned up. the execution was
Jenkins runs old-build-script clean which cleans foo/lib
Jenkins runs old-build-script build which creates foo/lib and populates it
build script change is checked in
Jenkins runs new-build-script clean which no longer cleans foo/lib
Jenkins runs new-build-script build which no longer creates foo/lib, but the
old content is there.
The only real workaround on my end is to always be vigilant for all possible
places that code could possibly affect my build and preemptively clean them in
all cases, regardless of whether I'd place anything there. That puts a huge
burden on me.
> In "Check-out Strategy" there are separate "revert" and "clean" options, but
> there is no "clean and revert" option.
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JENKINS-9714
> URL: https://issues.jenkins-ci.org/browse/JENKINS-9714
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Affects Versions: current
> Environment: Tested on Windows 32 bits running as a service, but it
> should occur on any environment.
> Reporter: Jader Dias
>
> My project needs to have all new files deleted and existing files to be
> reverted before each update. I can only choose one or the other, I need both.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
