Proposal to Extend JPLEphemeridesLoader to Support Libration Data

Orekit development
21

Strange, it seems to me that your account is a member of the group that allows you to create and administer a project. I just changed the key for your project.

22

Hi @xzguo,

I performed a test with a non-privileged account. To my surprise, I found that only SonarQube application administrators can modify the project settings like the project key. :confused:

The method I suggested for creating the project is therefore not suitable for non-privileged accounts.

Another approach is possible, but I realize that, once again, in order to properly link the project to GitLab afterwards, you need to be a SonarQube administrator. It’s a pain, but I’m not going to give admin rights to all contributors—that wouldn’t be reasonable.

In any case, since I have updated your project key, you can restart the CI/CD job. The analysis report will now be pushed to SonarQube.

23

Hi, @sdinot ,

thanks for your information. Still, the sonarQube is not working for me, and complains You're not authorized to run analysis. Please contact the project administrator., which is from the latest log in the CI/CD build process.

24

I checked two points on SonarQube:

  • Your account (xiaozhongguo) is member of sonar-users
  • Members of the sonar-users group are allowed to create projects and to run analysis

image

image
image957×105 13 KB

I created another account on GitLab, which has the same rights as your account on GitLab and SonarQube. Then I cloned the GitLab repository into this account’s namespace and created a project in SonarQube. I then launched a CI/CD pipeline in GitLab, and it successfully published a quality report in SonarQube.

There is one thing I cannot verify, which is the validity of the token. Could you renew this token and update the SONAR_TOKEN variable in your project’s CI/CD variables?

25

hi, @sdinot ,

thanks for your advisement.

it was my fault. i missed one of settings about SONAR_HOST_URL, which should be visiable and not masked. Anyway, i also updated the token. And sonarQube is fine.

Now i passed the pipelines of changelog & verify, but failed at coverage-import, which echos " ERROR: Job failed (system failure): prepare environment: setting up trapping scripts on emptyDir: error dialing backend: EOF."

i hope this is not vital for my MR.