Issue Summary

Once VCS_LOCATION primary key surpasses 32bit int, Source code checkout task cannot be added or edited on deployment plans.

Steps to Reproduce

1. When vcs_location_id reaches 2,147,483,648 (max int + 1), edit a deployment plan
2. Attempt to add and save a source-code checkout task (or view an existing one)

Expected Results

Source-code checkout task can be added.

Actual Results

An error is shown in the UI upon hitting save:
For input string: "2548170753" (where the # is the ID of the repository)

No exception is found in the atlassian-bamboo.log.

Workaround

The only workaround is to modify or add the source-code checkout via Bamboo Specs instead of the UI.

1. Export the deployment project as a Bamboo Spec: Edit Deployment Project >> ... >> View Project as Bamboo Spec
2. Take the exported spec and create a Bamboo Specs project using that code: Tutorial: Create a simple plan with Bamboo Java Specs
3. Add or modify the Source-code checkout task. Example:

   ...
               .environments(new Environment("QA")
                       .tasks(new CleanWorkingDirectoryTask(),
                           new ScriptTask()
                               .inlineBody("pwd;"),
                               new VcsCheckoutTask()
                               .checkoutItems(new CheckoutItem()
                                       .repository(new VcsRepositoryIdentifier()
                                               .name("linked-repository-name")))));
   ...
   

4. Push the spec to the server:

   mvn -Ppublish-specs