Summary

When we use VCS branching and VCS tagging tasks and upgrade Bamboo to 6.7 and later, the plans having these tasks (renamed to Repository Branch and Repository Tag will fail with the error svn: E155007: 'build-dir/PROJ-PLAN-JOB' is not a working copy

Steps to Reproduce

1. Define a Subversion repository in a plan.
2. Create 2 jobs - one with Source code checkout task and Repository tagging and other job with just Repository tagging
3. Run this plan

Expected Results

The plan should introduce 2 tags and both the jobs must get successfully executed/built.

Actual Results

The plan fails with the below exception in the build log file:

com.atlassian.bamboo.task.TaskException: An error occurred while tagging a repository
at com.atlassian.bamboo.plugins.vcs.task.VcsTagTask.execute(VcsTagTask.java:64)
at com.atlassian.bamboo.task.TaskExecutorImpl.lambda$executeTasks$3(TaskExecutorImpl.java:319)
...
...
at java.lang.Thread.run(Unknown Source)
error	04-Apr-2019 10:42:03	Caused by: com.atlassian.bamboo.repository.RepositoryException: An error occurred while trying to obtain repository working copy status
at com.atlassian.bamboo.repository.svn.v2.SvnWorkingCopyManager.getWorkingCopyInfo(SvnWorkingCopyManager.java:84)
at com.atlassian.bamboo.plugins.vcs.task.VcsTagTask.execute(VcsTagTask.java:59)
... 16 more
error	04-Apr-2019 10:42:03	Caused by: org.tmatesoft.svn.core.SVNException: svn: E155007: 'C:\bamboo-agent-home\xml-data\build-dir\PROJ-PLAN-JOB' is not a working copy

Workaround

For build plans introduce a Source code checkout task in every job wherever we have Repository Tag or Repository Branch is defined.

For deployment plans add a Source code checkout task to every environment, a script task that uses a native SVN client to check out the correct revision used in the build plan in the same directory as the source code task and then the Repository tag task.
(The reason for the extra script task with a checkout is the fact that the source code checkout task always checks out the latest changes which may differ from the revision that was used in the build plan.)