Directory not cleaned if symbolic links exist
I have a build(runs on RHEL5) that creates symbolic links to files when it runs, I also have
the "Delete directory before loading" box checked in my Build Definition, however, the sym links
are not removed at the start of each build.
Does anybody know how this can be fixed?
or if there are any workarounds?
Thanks,
Patrick
the "Delete directory before loading" box checked in my Build Definition, however, the sym links
are not removed at the start of each build.
Does anybody know how this can be fixed?
or if there are any workarounds?
Thanks,
Patrick
One answer
Hi Patrick,
I think that in the upcoming version 2.0.0.2 you can manage the sym links in RTC directly, so you won't have to create or delete those manually or in a builkd script.
I think that one solution would be to delete explicitly in your build scripts those sym links as the last task of your build script, once you've builded the required artficats.
This issue is discussed at the following location (https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=97455) and is supposed to be fixed with the upcoming 2.0.0.2 release
I think that in the upcoming version 2.0.0.2 you can manage the sym links in RTC directly, so you won't have to create or delete those manually or in a builkd script.
I think that one solution would be to delete explicitly in your build scripts those sym links as the last task of your build script, once you've builded the required artficats.
This issue is discussed at the following location (https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=97455) and is supposed to be fixed with the upcoming 2.0.0.2 release
I have a build(runs on RHEL5) that creates symbolic links to files when it runs, I also have
the "Delete directory before loading" box checked in my Build Definition, however, the sym links
are not removed at the start of each build.
Does anybody know how this can be fixed?
or if there are any workarounds?
Thanks,
Patrick