Single Branch Mode does not appear to work for sub-branches in Plastic SCM

Continua CI Bugs
1

Hi,

I’ve created a /main branch and a /main/integration branch in plastic.

The integration branch is used to merge feature/task branches into which will cause an integration/test build and subsequently a deploy.

The structure looks like this


I have successfully set the repository on my build configuration to single branch monitoring mode for /main which works fine.

The issue is when setting it to /main/integration, the build fails with the following error Unable to start build - no changesets found in repository ‘’ for branch ‘/main/integration’ (default branch path)

I’ve tried numerous configurations including setting the branch name to “/integration” and "integration"

I’ve again sent a debug log to your support email.

Regards,
Sean

2

Hi Sean,

In the log file that you sent, this appears to be related to the issue you reported yesterday . Did you install the updated version 1.8.0.230 I sent you yesterday? 

3

I haven’t sorry. Your message got moved out of my inbox by a filter. Sorry about that. I’ll install it and check both issues again now.

Cheers,
Sean

4

Dave,

This is still a problem on 1.8.0.230. Please continue to investigate.

Thanks,
Sean

5

Hi Sean,

Please reset the repository on the Administration -> Repositories page and try again. We should be doing this automatically when you edit the branch - like we do with other repositories. I’ll update the code to do this. Meanwhile let us know if the reset fixes your issue.

6

Dave,

I’ve reset the repository and it’s still happening.

I have have found a way to replicate it and a simple work-around for the time being though.

To Replicate

  1. Create A new build configuration
  2. Add a configuration level repository. When adding the repository, set it to Plastic SCM in single branch mode and set the branch to /main
  3. After adding the repository, save and complete the wizard.
  4. Run the build and it will work
  5. Now edit the build and set the branch on the repository to be /main/[ASubBranchOfYourChoice]
  6. Save and complete the wizard
  7. Run the build and it will fail with the error I mentioned previously.

I think it’s got something to do with the default branch setting. If you edit the build and click on the “Mappings” for the repository you will notice the Default branch is still set to /main and cannot be changed to any other values.

The simple fix is to delete the repo and create it again with /main/integration as the initial value for the branch. You’ll notice if you do this and view the mappings section again that it is set as you would expect to /main/integration

Further to this, I’d like to mention that the default branch setting in single branch mode seems a little redundant and confusing. If I’ve told it specifically what branch to use in the edit>branches section I’m not sure it makes a lot of sense to have to do it in the mappings as well.

Please let me know if you need more information.

Cheers,
Sean
7

Hi Sean,

We have now reproduced this. It seems to be related to a race condition when the repository is reset. We’ll work toward getting a new version out with a fix on Monday. 

Yes, the branch mappings are redundant for a configuration-scoped repository in single branch mode. You should not however need to change this, when things are working correclty.