Transfer a project from one organisation to another

[ganncamp (G Ann Campbell)]

Hi,

@0neel

I’d like to save as much as possible. So ideally I’d like to keep both project’s evolution and issue manipulations. I assume you say that saving (or recreating/restoring) the latter is not possible. Is that correct?

It’s not. Not natively. It would be possible to use the APIs to pull a list of FP/WF issues. Then you would have to map them to the issues created in the new clone by file/line number/rule id. From there you could re-FP/WF the clone’s issues, but you’re still going to lose the context of who and when they were initially marked (unless you want to stuff that into an issue comment).

@0neel

Does it mean we’ll have to manually run analysis on every version we’d like to add to the history?

Yes. In order. So checkout the initial commit. Set sonar.projectDate to that value`. Analyze. Increment the date. GoTo 1. Note that housekeeping cleans old analyses out automatically, so you should skip selectively through history.

@0neel

would SonarCloud order analysis runs according to it if don’t specify the sonar.projectDate parameter?

No. sonar.projectVersion is just a string.

@0neel

Does it mean there is no way (even manual) to rebind the project?

That’s correct. That’s why you want to vote for that feature.

@0neel

what would happen to the SonarCloud project once we transfer our repo to a different GitHub organisation?

Ehm… I think it would just languish, unanalyzed in SonarCloud. You would probably need to clean it out manually when you were done with any data transfer you wanted to do.

 
HTH,
Ann