Custom logo is blocked NotSameOriginAfterDefaultedToSameOriginByCoep

SonarQube Server / Community Build
21

Wow. That’s 6 months without e.g. SonarQube badges working. We’ll contact our AM then.
This does not work for us. We are missing some very basic functionality of SonarQube.

Update:
Spoke with our AM just now. He asked me to follow up here as he could not give me an answer on a few thing.

How does SonarSource work with releases of SonarQube?

I found this info on LTA(LTS).
And looking at the releases on GitHub I drew the conclusion that SonarSource do semantic versioning and release patch versions for SonarQube.

So, my questions are:

  1. How often do SonarSource release a new major version and likewise for minor of SonarQube?
  2. What decides when a patch version is released and what goes into a patch release, security fixes and bug fixes?

The CORS issue is in fact a bug and it even broke existing functionality and our daily DevOps experience. I’m flabbergasted that this is not fixed in a patch but a minor release several months later. What is the reason for this?

It honestly worries me because how can we rely on SonarSource fixing future bugs in reasonable time?

Regards,
Jimisola

1 Like
23

@ganncamp Can you please confirm that the CORS fix released with 10.7?

24

Hi @lfvjimisola,

The ticket is linked above. It shows Closed / Fixed / 10.7.

It’s in there. And other users have confirmed that in other threads.

 
Ann

1 Like