Traceability-Foss - Rename Repository name & Sonar project key reorganisation

changed title from Traceability-Foss - Rename Repository and Sonar project key reorganisation to Traceability-Foss - Rename Repository name & Sonar project key reorganisation

changed the description

added IT-prioritylow IT-severitylow labels

@fgurr i will talk to you about sonarcloud on friday because that topic came up: I'm sonarcloud admin on our side and we have eclipse tractus-x added to ours but if you support this anyway, could you do it and i remove our integration?

Otherwise lets talk about it on friday.

Tx!

@sigi okay the sonarcloud could be discussed on friday. The renaming of respos is a more urgent issue. Could we please spit the different concerns and have the renaming and clarify afterwards how we will manage this in sonarcloud.

@mkanal i would not have assumed this would be blocking the repo rename. But i'm not from EF and don't know if they are waiting because of this or because of something else.

Repo traceability-foss-frontend has been renamed to traceability-foss.

Adapt repository: https://sonarcloud.io/project/overview?id=eclipse-tractusx_traceability-foss-frontend >> eclipse-tractusx_traceability-foss

Adapt repository: https://sonarcloud.io/project/overview?id=eclipse-tractusx_traceability-foss-backend >> eclipse-tractusx_traceability-foss

@mkanal I'm not sure what you mean by "Adapt repository" here. Please elaborate.

Hello @fgurr

Background Information: In the past we had two different repositories:

One for backend -> https://github.com/eclipse-tractusx/traceability-foss-backend
One for frontend -> https://github.com/eclipse-tractusx/traceability-foss-frontend

What is done so far:

You have renamed the frontend repository for us and we have merged the backend into the renamed repository. As those are still two different code languages which should have own quality gates we still would like to have two different sonar projects.

What needs to be done from your side: We already have a good solution in the catena network. There we use a sonar project which is configured as monorepo and has two different projects in it. Please see here: https://jira.catena-x.net/browse/A1ODT-1288

Create a project in SonarCloud compatible with monorepo: https://docs.sonarcloud.io/advanced-setup/monorepo-support/
Adapt the secrets / vars on the repository: https://github.com/eclipse-tractusx/traceability-foss

vars:

SONAR_PROJECT_KEY_BACKEND=eclipse-tractusx_traceability-foss-backend

SONAR_PROJECT_KEY_FRONTEND=eclipse-tractusx_traceability-foss-frontend

secrets:

SONAR_TOKEN_BACKEND=<Please_add_token>

SONAR_TOKEN_FRONTEND=<Please_add_token>

That should be everything.

I hope I could make that understandable.

Thank you very much in advance.

Kind regards

Maximilian Wesener Trace-X Developer

assigned to @fgurr

@mwesener Thanks for the explanation. I was not aware of the monorepo capabilities of SonarCloud. Even with the official documentation it was hard to find the right option the first time around.

SonarCloud projects have been created:

Both point to the https://github.com/eclipse-tractusx/traceability-foss monorepo.

Secrets and Variables in https://github.com/eclipse-tractusx/traceability-foss have been created as requested.

I have removed the old SONAR_PROJECT_KEY and SONAR_TOKEN var/secret.

Please reopen if something is still missing.

closed

Hi @fgurr thank you very much for the quick solution provided. I will verify as soon as possible and let you know.

mentioned in issue #2834 (closed)

mentioned in issue #2881 (closed)

Traceability-Foss - Rename Repository name & Sonar project key reorganisation

Designs

Child items ...

Activity