Plugin v1.12.0 incompatible with SonarQube v9.7.0 #674

stevehipwell · 2022-10-18T09:09:51Z

Describe the bug
The v1.12.0 version of this plugin doesn't seem to be compatible with SonarQube v9.7.0.

To Reproduce
Install v1.12.0 to SonarQube v9.7.0.

Expected behavior
I'd expect the plugin to load as it does for v9.6.1.

Screenshots

2022.10.18 09:01:53 INFO app[][o.s.a.ProcessLauncherImpl] Launch process[WEB_SERVER] from [/opt/sonarqube]: /usr/lib/jvm/java-11-openjdk/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=/opt/sonarqube/temp -XX:-OmitStackTraceInFastThrow --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED --add-exports=java.base/jdk.internal.ref=ALL-UNNAMED --add-opens=java.base/java.nio=ALL-UNNAMED --add-opens=java.base/sun.nio.ch=ALL-UNNAMED --add-opens=java.management/sun.management=ALL-UNNAMED --add-opens=jdk.management/com.sun.management.internal=ALL-UNNAMED -Dcom.redhat.fips=false -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -javaagent:./extensions/plugins/sonarqube-community-branch-plugin.jar=web -Dhttp.nonProxyHosts=localhost|127.*|[::1] -cp ./lib/sonar-application-9.7.0.61563.jar:/opt/sonarqube/lib/jdbc/h2/h2-2.1.214.jar org.sonar.server.app.WebServer /opt/sonarqube/temp/sq-process11500539336540629664properties
09:01:53.624 [main] INFO com.github.mc1arke.sonarqube.plugin.CommunityBranchAgent - Loading agent
Exception in thread "main" java.lang.reflect.InvocationTargetException
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:513)
at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:525)
Caused by: java.lang.ClassNotFoundException: org.sonar.server.almsettings.MultipleAlmFeatureProvider
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581)
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
at java.base/java.lang.Class.forName0(Native Method)
at java.base/java.lang.Class.forName(Class.java:315)
at com.github.mc1arke.sonarqube.plugin.CommunityBranchAgent.redefineEdition(CommunityBranchAgent.java:93)
at com.github.mc1arke.sonarqube.plugin.CommunityBranchAgent.premain(CommunityBranchAgent.java:56)
... 6 more
*** java.lang.instrument ASSERTION FAILED ***: "result" with message agent load/premain call failed at src/java.instrument/share/native/libinstrument/JPLISAgent.c line: 422
FATAL ERROR in native method: processing of -javaagent failed, processJavaStart failed
2022.10.18 09:01:53 WARN app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [Web Server]: 134
2022.10.18 09:01:53 INFO app[][o.s.a.SchedulerImpl] Process[Web Server] is stopped
2022.10.18 09:01:53 WARN app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [ElasticSearch]: 143
2022.10.18 09:01:53 INFO app[][o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2022.10.18 09:01:53 INFO app[][o.s.a.SchedulerImpl] SonarQube is stopped

Software Versions

SonarQube Version: v9.7.0
Plugin Version: v1.12.0

Additional context

pablosguajardo · 2022-10-18T21:19:45Z

It does not work for me either:
18:16:54.109 [main] INFO com.github.mc1arke.sonarqube.plugin.CommunityBranchAgent - Loading agent
Exception in thread "main" java.lang.reflect.InvocationTargetException
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:513)
at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:525)
Caused by: java.lang.ClassNotFoundException: org.sonar.server.almsettings.MultipleAlmFeatureProvider
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581)
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
at java.base/java.lang.Class.forName0(Native Method)
at java.base/java.lang.Class.forName(Class.java:315)
at com.github.mc1arke.sonarqube.plugin.CommunityBranchAgent.redefineEdition(CommunityBranchAgent.java:93)
at com.github.mc1arke.sonarqube.plugin.CommunityBranchAgent.premain(CommunityBranchAgent.java:56)
... 6 more
*** java.lang.instrument ASSERTION FAILED ***: "result" with message agent load/premain call failed at ./src/java.instru
ment/share/native/libinstrument/JPLISAgent.c line: 422
FATAL ERROR in native method: processing of -javaagent failed, processJavaStart failed

mc1arke · 2022-10-19T07:07:37Z

SonarSource/sonarqube@57a8a41 has moved MultipleAlmFeatureProvider to MultipleAlmFeature so that will need an update to the Java Agent to use the new class and method name. I've not analysed the other changes in Sonarqube in this last release to see if there are any other breaking changes yet.

pablosguajardo · 2022-10-19T10:01:37Z

Thanks for answering. what should we do? do you have to create a new version of the plugin?

4n4n4s · 2022-10-20T12:24:57Z

Thanks for answering. what should we do? do you have to create a new version of the plugin?

Yes for now stick to 9.6 and don't update until there is a new version of the plugin available.

Example for docker you can use this tag 9.6-community

scholz-afis · 2022-10-20T13:54:40Z

@mc1arke Maybe you should highlight the 9.7 issue in der Compatibilitysection of https://github.com/mc1arke/sonarqube-community-branch-plugin/blob/master/README.md ?

Plugin does not work with SonarQube 9.7+ yet, adjusted the compatability table to have a max plugin version for 1.12. mc1arke#674

lorirava · 2022-10-21T12:48:52Z

Thanks for answering. what should we do? do you have to create a new version of the plugin?

Yes for now stick to 9.6 and don't update until there is a new version of the plugin available.

Example for docker you can use this tag 9.6-community

if you use kubernetes helm chart, is it possible to use 9.6 version? I got a server error that say me to use the latest version...

scholz-afis · 2022-10-21T12:52:50Z

@lorirava you might find these commands helpful:

helm search repo sonarqube -l
helm upgrade --install sonarqube sonarqube/sonarqube --namespace sonarqube --version 5.0.6+370

Mistic92 · 2022-10-24T09:48:05Z

I can't downgrade from 9.7. Do we have any ETA for fix?

mgexm · 2022-10-25T18:43:39Z

We backup the storage that is used so we were lucky. However to your point @Mistic92 I was getting the exact "cannot downgrade a node from version [7.17.5] to version [7.17.4]" which was caused by an attempt to upgrade to SQ 9.7.0. The issue happens for some people and due to its nature they can't recover from it.

2022.10.25 16:58:09 INFO  es[][o.e.e.NodeEnvironment] using [1] data paths, mounts [[/opt/sonarqube/data (/dev/xvdb)]], net usable_space [91.7gb], net total_space [97.8gb], types [ext4]
2022.10.25 16:58:09 INFO  es[][o.e.e.NodeEnvironment] heap size [512mb], compressed ordinary object pointers [true]
2022.10.25 16:58:09 ERROR es[][o.e.b.ElasticsearchUncaughtExceptionHandler] uncaught exception in thread [main]
org.elasticsearch.bootstrap.StartupException: java.lang.IllegalStateException: cannot downgrade a node from version [7.17.5] to version [7.17.4]
	at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:170) ~[elasticsearch-7.17.4.jar:7.17.4]
	at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:157) ~[elasticsearch-7.17.4.jar:7.17.4]
	at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:77) ~[elasticsearch-7.17.4.jar:7.17.4]
	at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:112) ~[elasticsearch-cli-7.17.4.jar:7.17.4]
	at org.elasticsearch.cli.Command.main(Command.java:77) ~[elasticsearch-cli-7.17.4.jar:7.17.4]
	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:122) ~[elasticsearch-7.17.4.jar:7.17.4]
	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:80) ~[elasticsearch-7.17.4.jar:7.17.4]
Caused by: java.lang.IllegalStateException: cannot downgrade a node from version [7.17.5] to version [7.17.4]
	at org.elasticsearch.env.NodeMetadata.upgradeToCurrentVersion(NodeMetadata.java:95) ~[elasticsearch-7.17.4.jar:7.17.4]
	at org.elasticsearch.env.NodeEnvironment.loadNodeMetadata(NodeEnvironment.java:484) ~[elasticsearch-7.17.4.jar:7.17.4]
	at org.elasticsearch.env.NodeEnvironment.<init>(NodeEnvironment.java:356) ~[elasticsearch-7.17.4.jar:7.17.4]
	at org.elasticsearch.node.Node.<init>(Node.java:429) ~[elasticsearch-7.17.4.jar:7.17.4]
	at org.elasticsearch.node.Node.<init>(Node.java:309) ~[elasticsearch-7.17.4.jar:7.17.4]
	at org.elasticsearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:234) ~[elasticsearch-7.17.4.jar:7.17.4]
	at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:234) ~[elasticsearch-7.17.4.jar:7.17.4]
	at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:434) ~[elasticsearch-7.17.4.jar:7.17.4]
	at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:166) ~[elasticsearch-7.17.4.jar:7.17.4]
	... 6 more
uncaught exception in thread [main]
java.lang.IllegalStateException: cannot downgrade a node from version [7.17.5] to version [7.17.4]
	at org.elasticsearch.env.NodeMetadata.upgradeToCurrentVersion(NodeMetadata.java:95)
	at org.elasticsearch.env.NodeEnvironment.loadNodeMetadata(NodeEnvironment.java:484)
	at org.elasticsearch.env.NodeEnvironment.<init>(NodeEnvironment.java:356)
	at org.elasticsearch.node.Node.<init>(Node.java:429)
	at org.elasticsearch.node.Node.<init>(Node.java:309)
	at org.elasticsearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:234)
	at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:234)
	at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:434)
	at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:166)
	at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:157)
	at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:77)
	at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:112)
	at org.elasticsearch.cli.Command.main(Command.java:77)
	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:122)
	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:80)
For complete error details, refer to the log at /opt/sonarqube/logs/sonarqube.log

pablosguajardo · 2022-10-27T00:31:16Z

I have sonar 9.7 installed with mssql, can I downgrade from version 9.7 to version 9.6? should I delete the base and start from scratch?

githubcdr · 2022-10-27T07:25:22Z

The downgrade issue does not seem to be related to the Postgres database, we restored a previous version and still receive this error.

githubcdr · 2022-10-27T07:52:55Z

I got it working by removing the Elasticsearch data created by Sonarqube, after this it will start with v9.6.

aminoacidity · 2022-10-27T09:06:08Z

I got it working by removing the Elasticsearch data created by Sonarqube, after this it will start with v9.6.

Hi, Can you explain how did you remove the data. I am stuck as well but with MS SQL Server as the backend.

pablosguajardo · 2022-10-27T10:31:40Z

I got it working by removing the Elasticsearch data created by Sonarqube, after this it will start with v9.6.

thanks for your answer. How did you removing this data?

aminoacidity · 2022-10-28T02:31:22Z

thanks for your answer. How did you removing this data?

If you dont care about your current data you can just drop your sonarqube database and recreate it with the right privileges (as mentioned in the docs).

Example on Postgresql:
CREATE USER sonar WITH ENCRYPTED PASSWORD '************'; -- Skip if you already have a user.
DROP DATABASE sonarqube;
CREATE database sonarqube;
GRANT ALL PRIVILEGES ON DATABASE sonarqube TO sonar;
Warning: Do it only if you are ready to loose your current sonarqube data!

If you're running Sonarqube using Docker and want a full reset, you can in addition, delete your volumes docker-compose down -v

Hi, I was referring to elasticsearch data cleanup that was referred to by the poster. I am guessing deleting the es folder should suffice.

aminoacidity · 2022-10-28T05:02:59Z

After reverting to the 9.6 version, deleted the ES data which in my case was mapped to /var/sonarqube/data/es7. Sonarqube started just fine.

Mistic92 · 2022-11-02T09:25:47Z

Hi, any ETA for that for people who can't delete history?:)

mgexm · 2022-11-09T17:34:16Z

9.7.1 is out ... does the plugin work with 9.7.1 ?

MCMicS · 2022-11-09T17:36:21Z

Don't think so.
It should be fixed on plugin side i guess

9.7.1 was only a security release

nkd-nkd · 2022-11-11T14:00:14Z

Plugin does not work with 9.7.1 either

jeremytbrun · 2022-11-16T15:26:13Z

@mc1arke any ETA on an update to the plugin to be compatible with SonarQube 9.7.x?

henrypham299 · 2022-11-23T06:48:43Z

@mc1arke do we have any update for this issue?

EdmundMorris · 2022-11-29T17:39:24Z

Does anyone know of a patched fork while we wait for the fix here?

marcelloceschia · 2022-12-03T14:59:51Z

If someone helps me to test it later, I can try to do a working version for next week

Sonarqube has removed the use of the same external component key and differing database IDs for different branches on the same projects and now use different IDs in all cases. The pull request web service endpoints have also been removed from community edition. To allow the plugin to work with the new version of Sonarqube, the component key generation for branches has been modified to save branch DTOs whenever a new branch is created, and to remove the conditions around re-using the same branch if the target branch details matched an existing branch. The Pull Request endpoint actions have been copied from the old community edition sources, and tidied up to use a cleaner abstraction model. As the front-end only shows branch features if the implementation of `BranchFeatureExtension` returns the name 'branch-support', the `CommunityBranchFeatureExtension` has been altered to follow this requirement, and an additional `MonoRepoFeature` has been implemented to allow the mono-repo switches to be shown against the front-end. Includes the migration of any altered unit tests to JUnit 5.

mathijs-dumon · 2022-12-13T11:30:16Z

Just hit this issue as well - great to see this is already fixed!
Is there a timeline for the next release?

AHagemannCK · 2022-12-17T16:06:20Z

Just hit this issue as well - great to see this is already fixed! Is there a timeline for the next release?

You can just download the snapshot: https://github.com/mc1arke/sonarqube-community-branch-plugin/actions/runs/3669639838 and install it manually.

dgokcin · 2022-12-19T09:14:46Z

@AHagemannCK I just hit this issue and trying with the plugin you suggested, Although sonarqube boots succesfully, I can not change branches from the project menu. Can you browse different branches thropugh the UI?

AHagemannCK · 2022-12-19T09:21:46Z

@AHagemannCK I just hit this issue and trying with the plugin you suggested, Although sonarqube boots succesfully, I can not change branches from the project menu. Can you browse different branches thropugh the UI?

Yes I can do that.
How do you host sonarqube?
I needed to change the plugin version in my environment variables (k8s deployment).
Maybe you need to change your plugin path from 1.12.... to 1.13.SNAPSHOT.jar?

EdmundMorris · 2022-12-19T09:31:44Z

Just hit this issue as well - great to see this is already fixed! Is there a timeline for the next release?

You can just download the snapshot: https://github.com/mc1arke/sonarqube-community-branch-plugin/actions/runs/3669639838 and install it manually.

The snapshot is working on my v9.7.1 build. Many thanks to those involved.

dgokcin · 2022-12-19T12:20:24Z

@AHagemannCK I figured it out. I am hosting sonarqube on AWS ECS Fargate. During my version update from 8.9 LTS to 9.7, I forgot about the required java additional options. Once I enabled them back, it worked like a charm.

Thank you everyone!

OneCyrus · 2022-12-19T18:10:45Z

did anyone try 9.8 already? it just released today

Elanis · 2022-12-19T18:54:58Z

Just upgraded to 9.7.1 (62043), and using the latest snapshot from master branch.
I get a "Current edition does not support branch feature" in background tasks :/

I can browse through branches, and removing data/es7 like Mistic92 didn't fix things.

(Scanning using dotnet-sonarscanner, if that's important)
Am I the only one ?

EDIT: See below, wrong configuration, I forgot to add additionalOpts to CE process

LocalHeroPro · 2022-12-19T19:13:28Z

did anyone try 9.8 already? it just released today

For me, SQ v9.8 don't start with v1.12 plugin.

brother · 2022-12-20T10:36:40Z

did anyone try 9.8 already? it just released today

For me, SQ v9.8 don't start with v1.12 plugin.

Given the explanation of what's change in 9.7 I am not at all surprised by this. Try the snapshot instead.

psini · 2022-12-20T10:55:30Z

When it will be released ?

dgokcin · 2022-12-20T19:17:51Z

Just upgraded to 9.7.1 (62043), and using the latest snapshot from master branch. I get a "Current edition does not support branch feature" in background tasks :/

I can browse through branches, and removing data/es7 like Mistic92 didn't fix things.

(Scanning using dotnet-sonarscanner, if that's important) Am I the only one ?

I use the same sonarqube version with dotnet sonar scanner. Did you also update the versions of the plugin in the sonarqube run command? Adding my config for reference. Note that I renamed the snapshot as 1.13.0.jar and put it inside my docker container at the specified paths in the README of this repo.

  app_command = ["-Dsonar.search.javaAdditionalOpts=-Dnode.store.allow_mmap=false",
    "-Dsonar.web.javaAdditionalOpts=-javaagent:./extensions/plugins/sonarqube-community-branch-plugin-1.13.0.jar=web",
    "-Dsonar.ce.javaAdditionalOpts=-javaagent:./extensions/plugins/sonarqube-community-branch-plugin-1.13.0.jar=ce"
  ]

Elanis · 2022-12-20T20:12:45Z

Just upgraded to 9.7.1 (62043), and using the latest snapshot from master branch. I get a "Current edition does not support branch feature" in background tasks :/
I can browse through branches, and removing data/es7 like Mistic92 didn't fix things.
(Scanning using dotnet-sonarscanner, if that's important) Am I the only one ?

I use the same sonarqube version with dotnet sonar scanner. Did you also update the versions of the plugin in the sonarqube run command? Adding my config for reference. Note that I renamed the snapshot as 1.13.0.jar and put it inside my docker container at the specified paths in the README of this repo.
  app_command = ["-Dsonar.search.javaAdditionalOpts=-Dnode.store.allow_mmap=false",
    "-Dsonar.web.javaAdditionalOpts=-javaagent:./extensions/plugins/sonarqube-community-branch-plugin-1.13.0.jar=web",
    "-Dsonar.ce.javaAdditionalOpts=-javaagent:./extensions/plugins/sonarqube-community-branch-plugin-1.13.0.jar=ce"
  ]

Seeing your config made me instantly understand my mistake, I forgot to add additionalOpts for CE (I only did for web) when I did migrate to 9.7.1, my bad. It's working now, thanks !

AdamMcIntosh · 2022-12-21T14:17:01Z

confirmed that using the snapshot works with 9.7 thanks!

AmitBaranes · 2022-12-22T09:27:01Z

can you publish this version so we'll not need to build it manually?

scholz-afis · 2022-12-22T09:31:12Z

can you publish this version so we'll not need to build it manually?

... and update the README.md regarding the current situation. Newcomers shouldn't get trapped with a broken 9.7+ installation in the first place.

alexis-gruet-deel · 2022-12-26T16:16:21Z

can you publish this version so we'll not need to build it manually?

Any updates ?

nixel2007 · 2022-12-26T17:05:11Z

You can grab snapshot from github actions build

alexis-gruet-deel · 2022-12-26T17:30:02Z

Hey @nixel2007,

You can grab snapshot from github actions build

Any reason to not get release and only -snap version ?

nixel2007 · 2022-12-26T17:31:56Z

Any reason to not get release and only -snap version ?

Real life maybe? :)

Let's wait for author's response

mc1arke · 2022-12-26T17:36:56Z

As suggested, it's the balance of time between the work, life, and open source. I'll get a release out sometime soon, but my priority has to be the things that provide my income.

mc1arke · 2022-12-31T14:11:30Z

This has been released as part of 1.13.0

* Bump mockito-core from 4.0.0 to 4.1.0 Bumps [mockito-core](https://github.com/mockito/mockito) from 4.0.0 to 4.1.0. - [Release notes](https://github.com/mockito/mockito/releases) - [Commits](mockito/mockito@v4.0.0...v4.1.0) --- updated-dependencies: - dependency-name: org.mockito:mockito-core dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> * Bump logging-interceptor from 4.9.2 to 4.9.3 Bumps [logging-interceptor](https://github.com/square/okhttp) from 4.9.2 to 4.9.3. - [Release notes](https://github.com/square/okhttp/releases) - [Changelog](https://github.com/square/okhttp/blob/master/CHANGELOG.md) - [Commits](square/okhttp@parent-4.9.2...parent-4.9.3) --- updated-dependencies: - dependency-name: com.squareup.okhttp3:logging-interceptor dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> * Bump bcpkix-jdk15on from 1.69 to 1.70 Bumps [bcpkix-jdk15on](https://github.com/bcgit/bc-java) from 1.69 to 1.70. - [Release notes](https://github.com/bcgit/bc-java/releases) - [Changelog](https://github.com/bcgit/bc-java/blob/master/docs/releasenotes.html) - [Commits](https://github.com/bcgit/bc-java/commits) --- updated-dependencies: - dependency-name: org.bouncycastle:bcpkix-jdk15on dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> * Bump actions/setup-java from 2.3.1 to 2.4.0 Bumps [actions/setup-java](https://github.com/actions/setup-java) from 2.3.1 to 2.4.0. - [Release notes](https://github.com/actions/setup-java/releases) - [Commits](actions/setup-java@v2.3.1...v2.4.0) --- updated-dependencies: - dependency-name: actions/setup-java dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> * Bump junit-bom from 5.8.1 to 5.8.2 Bumps [junit-bom](https://github.com/junit-team/junit5) from 5.8.1 to 5.8.2. - [Release notes](https://github.com/junit-team/junit5/releases) - [Commits](junit-team/junit5@r5.8.1...r5.8.2) --- updated-dependencies: - dependency-name: org.junit:junit-bom dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> * Add missing base url while using bitbucket client * Bump mockito-core from 4.1.0 to 4.2.0 Bumps [mockito-core](https://github.com/mockito/mockito) from 4.1.0 to 4.2.0. - [Release notes](https://github.com/mockito/mockito/releases) - [Commits](mockito/mockito@v4.1.0...v4.2.0) --- updated-dependencies: - dependency-name: org.mockito:mockito-core dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> * Initiate release 1.10.0 * [Gradle Release Plugin] - new version commit: '1.10.1'. * Return to SNAPSHOT version post release * Update version numbers in README * Upgrade to the latest version of Gradle Updates Gradle to 7.3. Includes a modification to the Docker builder image to use a Gradle image rather than a JDK and the Gradle wrapper, as this allows caching of the Gradle image and possibly any interim steps rather than having to use the wrapper to download the full Gradle distribution on every build. * Bump actions/setup-java from 2.4.0 to 2.5.0 Bumps [actions/setup-java](https://github.com/actions/setup-java) from 2.4.0 to 2.5.0. - [Release notes](https://github.com/actions/setup-java/releases) - [Commits](actions/setup-java@v2.4.0...v2.5.0) --- updated-dependencies: - dependency-name: actions/setup-java dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> * Bump jackson-datatype-jsr310 from 2.13.0 to 2.13.1 Bumps jackson-datatype-jsr310 from 2.13.0 to 2.13.1. --- updated-dependencies: - dependency-name: com.fasterxml.jackson.datatype:jackson-datatype-jsr310 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> * Bump assertj-core from 3.21.0 to 3.22.0 Bumps [assertj-core](https://github.com/assertj/assertj-core) from 3.21.0 to 3.22.0. - [Release notes](https://github.com/assertj/assertj-core/releases) - [Commits](assertj/assertj@assertj-core-3.21.0...assertj-core-3.22.0) --- updated-dependencies: - dependency-name: org.assertj:assertj-core dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> * Bump mockito-core from 4.2.0 to 4.3.0 Bumps [mockito-core](https://github.com/mockito/mockito) from 4.2.0 to 4.3.0. - [Release notes](https://github.com/mockito/mockito/releases) - [Commits](mockito/mockito@v4.2.0...v4.3.0) --- updated-dependencies: - dependency-name: org.mockito:mockito-core dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> * Bump actions/setup-java from 2.5.0 to 3 Bumps [actions/setup-java](https://github.com/actions/setup-java) from 2.5.0 to 3. - [Release notes](https://github.com/actions/setup-java/releases) - [Commits](actions/setup-java@v2.5.0...v3) --- updated-dependencies: - dependency-name: actions/setup-java dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]> * Bump actions/checkout from 2 to 3 Bumps [actions/checkout](https://github.com/actions/checkout) from 2 to 3. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v2...v3) --- updated-dependencies: - dependency-name: actions/checkout dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]> * Bump jackson-datatype-jsr310 from 2.13.1 to 2.13.2 Bumps jackson-datatype-jsr310 from 2.13.1 to 2.13.2. --- updated-dependencies: - dependency-name: com.fasterxml.jackson.datatype:jackson-datatype-jsr310 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> * Bump mockito-core from 4.3.0 to 4.4.0 Bumps [mockito-core](https://github.com/mockito/mockito) from 4.3.0 to 4.4.0. - [Release notes](https://github.com/mockito/mockito/releases) - [Commits](mockito/mockito@v4.3.0...v4.4.0) --- updated-dependencies: - dependency-name: org.mockito:mockito-core dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> * Bump actions/cache from 2 to 3 Bumps [actions/cache](https://github.com/actions/cache) from 2 to 3. - [Release notes](https://github.com/actions/cache/releases) - [Commits](actions/cache@v2...v3) --- updated-dependencies: - dependency-name: actions/cache dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]> * mc1arke#91: Add ability to donate to the project maintainer * mc1arke#523: Add auto-detection for all CIs in Sonarqube commercial editions The plugin previously only provided support for auto-detecting and configuring the scanner properties for a Pull Request in Azure Devops and a Merge Request or Branch in Gitlab CI. The Sonarqube documentation also stated that Bitbucket Pipelines, Github Actions, CodeMagic, Jenkins Branch API, and Cirrus CI could also be used to auto-discover Pull Request or Branch information although the plugin did not provide these. This change adds support for detecting these additional CIs based on the various environment variables they provide, and to auto-configure Pull Request or Branch parameters in the scanner when a suitable build job is detected. Includes the general clean-up of the creation of Branch and Pull Request configuration to force fail-fast behaviour where target branches are not provided or can't be matched against known branches, to ensure the correct reference branch is selected for Pull Request analysis, and to force an error to be displayed if a user mixes Pull Rrequest and Branch parameters in their launch properties. * Refactor Bitbucket operations to prevent leaking scope The Bitbucket clients require different properties to be used from the relevant configuration DTOs depending on whether Bitbucket cloud or server are being used, with the management of the property retrieval being delegated to the relevant client implementation. However, this requires each client to reference DTO classes from Sonarqube core, where the clients should really only interact with their own models. As the work on retrieving the relevant details has already been performed in the `DefaultBitbucketClientFactory`, the logic for performing the retrieval has been removed from each client implementations, and the calculated values are passed into the constructor for each client instead. This does make each client instance constrained to a single repository, but given the way the clients are used within the decorators and validators, this isn't an issue. The client API has therefore been altered to remove the references to project and repository in any method signatures since the client now retrieves this internally from the client configuration. The clients have also been altered now to depend directly on the status from the Quality Gate, with a new enum being used by the client to indicate the report status, and the decorator performing the mapping between the Quality Gate and report status. Finally, to allow for the `DefaultBitbucketClientFactory` to have a single constructor rather than a test-specific constructor, the facility for creating an Http Client has been moved into an `HttpClientBuilderFactory` and this new class configured for injection in both the Compute Engine and server components. * Refactor Github operations to prevent leaking scope The GithubClient interface exposes a method that takes various Sonarqube core classes and plugin constructed data as arguments and returns a `DecorationResult`, all of which are items that the upstream decorator should be aware of, but not the client responsible for communicating with Github. Similarly, the `GraphqlGithubClient` had locally constructed a `MarkdownFormatterFactory`, `DefaultGraphqlProvider`, and `Clock` as well as requiring a Sonarqube `Server` instance for instantiation, with the local construction requiring a second constructor to be included purely for testing, and the `Server` instance requiring the client have knowledge of Sonarqube's structure rather than being passed a client configuration that had no external dependencies in it. This change alters the GithubClient implementation to use dependency injection for all re-usable objects, and introduces a Github specific object for submitting a check run, rather than relying on the `AnlaysisDetails` object used in the plugin. The use of the settings DTOs has been removed from the client, with the details being used in the client factory and the relevant details being persisted in the client from the constructor invocation. To support this, the `MarkdownFormatterFactory` has been setup to be exposed for constructor injection in Compute Engine components, and the `DefaultGraphqlProvider` exposed in both Compute Engine and Server scopes. The requirement of passing a `projectPath` inside the GithubClient has also been removed, with the repository name and owner login being extracted during the authentication phase and stored in the token for the client to use them where needed. * Remove cyclic dependency in Formatters The Formatters for generating the analysis report are created by a FormatterFactory, but then need a formatter factory passed into them during execution. This allows a potential scenario where a Formatter could be passed a FormatterFactory for a different output type so generate invalid content type, as well as causing a non-optimal API. This change alters the FormatterFactory to be the component that is aware of how to create Formatters for child components, rather than the formatters doing this, therefore removing the need for a FormatterFactory to be made available in formatters. * mc1arke#421: Don't trim whitespace during Markdown rendering The text renderer for the `MarkdownFormatterFactory` had been performing a `trim` on any inputs, which caused the single whitespace entries being added as spacers after some inline images to be removed. As the structure of the document should be presumed to match what the generating component requires, it's unnecessary for the renderer to attempt to alter this structure whilst rendering to a relevant document format. Instead, any constraints on formatting should be left to the system rendering the generated output. * Move report generation out of AnalysisDetails The access to metrics from a Pull Request analysis is exposed through an `AnalysisDetails` instance, which also provides the ability to extract a formatted report. As a number of the metrics used in the summary report need to be retrieved through various additional DAOs, and as the resolution of URLs for links and images requiring access to core Sonarqube configuration, `AnalysisDetails` holds references to a high number of classes from Sonarqube's core. Some of those core Sonarqube classes are also referenced directly in some decorators which don't make use of the summary report but need equivalent metrics to those shown in the summary which means some searching logic is duplicated across the plugin. This change pulls the report generation into a `ReportGenerator` class, with the report being an interim set of collected metrics that each decorator can extract required information, or generate a formatted report from. * Allow mono-repo decoration for Bitbucket The key for the Code Insights report uses a static value which results in any report submitted by Sonarqube overwriting any existing report, even where reports are submitted from different projects, such as would happen in a mono-report setup. The report key is therefore being changed to use the project key, so that repeated scans from a single project continue to overwrite each other, whilst scans against the same repository from different projects will allow new reports to be submitted without altering existing reports. * Bump actions/upload-artifact from 2 to 3 Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 2 to 3. - [Release notes](https://github.com/actions/upload-artifact/releases) - [Commits](actions/upload-artifact@v2...v3) --- updated-dependencies: - dependency-name: actions/upload-artifact dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]> * Fix unit tests on Windows The character encoding is being set in Gradle to ensure that the build doesn't use Operating system specific encodings that will cause differences between builds of the same code on different machines. * Decoration issue fails due invalid project id when branch is in fork * Initiate release 1.11.0 * [Gradle Release Plugin] - new version commit: '1.11.1'. * Return to SNAPSHOT version post release * Update version numbers in README * Bump github/codeql-action from 1 to 2 Bumps [github/codeql-action](https://github.com/github/codeql-action) from 1 to 2. - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](github/codeql-action@v1...v2) --- updated-dependencies: - dependency-name: github/codeql-action dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]> * Bump javassist from 3.28.0-GA to 3.29.0-GA Bumps [javassist](https://github.com/jboss-javassist/javassist) from 3.28.0-GA to 3.29.0-GA. - [Release notes](https://github.com/jboss-javassist/javassist/releases) - [Commits](https://github.com/jboss-javassist/javassist/commits) --- updated-dependencies: - dependency-name: org.javassist:javassist dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> * Bump jackson-datatype-jsr310 from 2.13.2 to 2.13.3 Bumps jackson-datatype-jsr310 from 2.13.2 to 2.13.3. --- updated-dependencies: - dependency-name: com.fasterxml.jackson.datatype:jackson-datatype-jsr310 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> * Bump mockito-core from 4.4.0 to 4.6.0 Bumps [mockito-core](https://github.com/mockito/mockito) from 4.4.0 to 4.6.0. - [Release notes](https://github.com/mockito/mockito/releases) - [Commits](mockito/mockito@v4.4.0...v4.6.0) --- updated-dependencies: - dependency-name: org.mockito:mockito-core dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> * Improve test stability The wiremock based tests currently fail if another service is running on on port 8080, and other tests fail with newer dependencies due to changes in recursive comparisons. The wiremock tests are being altered to use a random port for runs to prevent port conflict, and the tests comparing HTTP entities are being altered to extract the InputStream for comparing the contents from. * Bump assertj-core from 3.22.0 to 3.23.1 Bumps [assertj-core](https://github.com/assertj/assertj-core) from 3.22.0 to 3.23.1. - [Release notes](https://github.com/assertj/assertj-core/releases) - [Commits](assertj/assertj@assertj-core-3.22.0...assertj-core-3.23.1) --- updated-dependencies: - dependency-name: org.assertj:assertj-core dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> * mc1arke#585 Register ObjectMapper modules so timestamps can be processed * Swap repo slug and project key Repository slug and project key got mixed up for the Bitbucket server config causing Sonar to not find the repo defined in the ui on Bitbucket * Replace null values in Bitbucket analysis report Bitbucket throws an error when a report contains a percentage element with a null value. The code coverage and duplication metrics are now nullable in the report data passed around the plugin, bit the Bitbucket decorator does not check or replace nulls from these fields. This change alters the report publishing to check for nulls in either of the coverage or duplication fields and uses Zero in their place. * Bump mockito-core from 4.6.0 to 4.6.1 Bumps [mockito-core](https://github.com/mockito/mockito) from 4.6.0 to 4.6.1. - [Release notes](https://github.com/mockito/mockito/releases) - [Commits](mockito/mockito@v4.6.0...v4.6.1) --- updated-dependencies: - dependency-name: org.mockito:mockito-core dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> * Bump logging-interceptor from 4.9.3 to 4.10.0 Bumps [logging-interceptor](https://github.com/square/okhttp) from 4.9.3 to 4.10.0. - [Release notes](https://github.com/square/okhttp/releases) - [Changelog](https://github.com/square/okhttp/blob/master/CHANGELOG.md) - [Commits](square/okhttp@parent-4.9.3...parent-4.10.0) --- updated-dependencies: - dependency-name: com.squareup.okhttp3:logging-interceptor dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> * Add instructions for official SonarQube Helm Chart * Cleanup README contents Re-formats the README to limit the line lengths to improve editing and readability of the raw format, and fixes some references to paths and configuration that has changed in recent versions of Sonarqube but is no longer accurate in the README. * mc1arke#601 Strip user info from Azure DevOps repository link When creating the link from Sonarqube to an Azure Devops Pull Request, the URL of the owning repository is used as a base for the URL. If the Azure DevOps API returns a URL containing user authentication details then this is included in the resulting link, even though the details may not be valid for a front-end user. The authentication detail is therefore being stripped from the URL before the Pull Request URL is generated. * Initiate release 1.12.0 * [Gradle Release Plugin] - new version commit: '1.12.1'. * Return to SNAPSHOT version post release * Update version numbers in README for LTS and mainline releases * Bump javassist from 3.29.0-GA to 3.29.2-GA Bumps [javassist](https://github.com/jboss-javassist/javassist) from 3.29.0-GA to 3.29.2-GA. - [Release notes](https://github.com/jboss-javassist/javassist/releases) - [Changelog](https://github.com/jboss-javassist/javassist/blob/master/Changes.md) - [Commits](https://github.com/jboss-javassist/javassist/commits) --- updated-dependencies: - dependency-name: org.javassist:javassist dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> * Bump junit-bom from 5.8.2 to 5.9.1 Bumps [junit-bom](https://github.com/junit-team/junit5) from 5.8.2 to 5.9.1. - [Release notes](https://github.com/junit-team/junit5/releases) - [Commits](junit-team/junit5@r5.8.2...r5.9.1) --- updated-dependencies: - dependency-name: org.junit:junit-bom dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> * Bump mockito-core from 4.6.1 to 4.9.0 Bumps [mockito-core](https://github.com/mockito/mockito) from 4.6.1 to 4.9.0. - [Release notes](https://github.com/mockito/mockito/releases) - [Commits](mockito/mockito@v4.6.1...v4.9.0) --- updated-dependencies: - dependency-name: org.mockito:mockito-core dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> * Bump jackson-datatype-jsr310 from 2.13.3 to 2.14.1 Bumps jackson-datatype-jsr310 from 2.13.3 to 2.14.1. --- updated-dependencies: - dependency-name: com.fasterxml.jackson.datatype:jackson-datatype-jsr310 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> * mc1arke#508: Support Pagination over AppInstallation When more than a single page worth of app installation is present in the Github API, the plugin does not currently fetch beyond the initial page, and therefore doesn't find the access tokens for the required installation. By loading all pages of installations before searching for the current application we ensure that we don't ignore any relevant installation. * Update ${version} on Manual Install in order to avoid confusion Moves away from using a fixed version number in the installation instructions to prevent issues with users copy-pasting an old version number. * mc1arke#674: Add support for Sonarqube 9.7 Sonarqube has removed the use of the same external component key and differing database IDs for different branches on the same projects and now use different IDs in all cases. The pull request web service endpoints have also been removed from community edition. To allow the plugin to work with the new version of Sonarqube, the component key generation for branches has been modified to save branch DTOs whenever a new branch is created, and to remove the conditions around re-using the same branch if the target branch details matched an existing branch. The Pull Request endpoint actions have been copied from the old community edition sources, and tidied up to use a cleaner abstraction model. As the front-end only shows branch features if the implementation of `BranchFeatureExtension` returns the name 'branch-support', the `CommunityBranchFeatureExtension` has been altered to follow this requirement, and an additional `MonoRepoFeature` has been implemented to allow the mono-repo switches to be shown against the front-end. Includes the migration of any altered unit tests to JUnit 5. * Bump mockito-core from 4.9.0 to 4.11.0 Bumps [mockito-core](https://github.com/mockito/mockito) from 4.9.0 to 4.11.0. - [Release notes](https://github.com/mockito/mockito/releases) - [Commits](mockito/mockito@v4.9.0...v4.11.0) --- updated-dependencies: - dependency-name: org.mockito:mockito-core dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> * Initiate release 1.13.0 * [Gradle Release Plugin] - new version commit: '1.13.1'. * Return to SNAPSHOT version post release * mc1arke#704: Add support for Sonarqube 9.8 The retrieval of the list of pull requests has been removed from the scanner engine, as well as the issue metrics on the Pull Request web service. The scanner has therefore been altered to implement the updated APIs and drop the classes that implemented the removed interfaces, and the Pull Request web service has had the gathering and population of the issue metrics removed. * Initiate release 1.14.0 * Apply PayPay-specific changes * Allow release from GitHub CI * [Gradle Release Plugin] - new version commit: '1.14.1-paypay'. * Revert "[Gradle Release Plugin] - new version commit: '1.14.1-paypay'." This reverts commit 650003d. --------- Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Konrad Czaja <[email protected]> Co-authored-by: Michael Clarke <[email protected]> Co-authored-by: GitHub <[email protected]> Co-authored-by: Michael Clarke <[email protected]> Co-authored-by: MrNighty <[email protected]> Co-authored-by: Johno Crawford <[email protected]> Co-authored-by: Miguel Canavidez <[email protected]> Co-authored-by: Jochim Van Dijck <[email protected]> Co-authored-by: RG <[email protected]> Co-authored-by: Brendan Nolan <[email protected]> Co-authored-by: Serhii Klymoshenko <[email protected]>

stevehipwell added the bug Something isn't working label Oct 18, 2022

brother mentioned this issue Oct 21, 2022

Add note about lack of support SonarQube 9.7+ at this moment. #679

Closed

mgexm mentioned this issue Oct 25, 2022

java.lang.ClassNotFoundException: org.sonar.server.almsettings.MultipleAlmFeatureProvider #682

Closed

brother mentioned this issue Nov 10, 2022

Sonarqube-9.x logging Current edition does not support branch feature #687

Closed

brother mentioned this issue Nov 16, 2022

Plugin Not Working with SonarQube 9.7.1-community #689

Closed

mc1arke added the awaiting release Merged but not currently in release vesrion label Dec 11, 2022

brother mentioned this issue Dec 22, 2022

sonarqube-community-branch-plugin not compatible with the versions 9.7.0.61563 and 9.7.1.62043 #705

Closed

mc1arke closed this as completed Dec 31, 2022

mc1arke removed the awaiting release Merged but not currently in release vesrion label Dec 31, 2022

Plugin v1.12.0 incompatible with SonarQube v9.7.0 #674

Plugin v1.12.0 incompatible with SonarQube v9.7.0 #674

Comments

stevehipwell commented Oct 18, 2022

pablosguajardo commented Oct 18, 2022

mc1arke commented Oct 19, 2022

pablosguajardo commented Oct 19, 2022

4n4n4s commented Oct 20, 2022

scholz-afis commented Oct 20, 2022 • edited Loading

lorirava commented Oct 21, 2022

scholz-afis commented Oct 21, 2022

Mistic92 commented Oct 24, 2022

mgexm commented Oct 25, 2022 • edited Loading

pablosguajardo commented Oct 27, 2022

githubcdr commented Oct 27, 2022

githubcdr commented Oct 27, 2022

aminoacidity commented Oct 27, 2022

pablosguajardo commented Oct 27, 2022

aminoacidity commented Oct 28, 2022

aminoacidity commented Oct 28, 2022

Mistic92 commented Nov 2, 2022

mgexm commented Nov 9, 2022

MCMicS commented Nov 9, 2022 • edited Loading

nkd-nkd commented Nov 11, 2022

jeremytbrun commented Nov 16, 2022

henrypham299 commented Nov 23, 2022

EdmundMorris commented Nov 29, 2022

marcelloceschia commented Dec 3, 2022

mathijs-dumon commented Dec 13, 2022

AHagemannCK commented Dec 17, 2022

dgokcin commented Dec 19, 2022

AHagemannCK commented Dec 19, 2022

EdmundMorris commented Dec 19, 2022

dgokcin commented Dec 19, 2022

OneCyrus commented Dec 19, 2022

Elanis commented Dec 19, 2022 • edited Loading

LocalHeroPro commented Dec 19, 2022

brother commented Dec 20, 2022

psini commented Dec 20, 2022

dgokcin commented Dec 20, 2022 • edited Loading

Elanis commented Dec 20, 2022

AdamMcIntosh commented Dec 21, 2022

AmitBaranes commented Dec 22, 2022

scholz-afis commented Dec 22, 2022

alexis-gruet-deel commented Dec 26, 2022

nixel2007 commented Dec 26, 2022

alexis-gruet-deel commented Dec 26, 2022

nixel2007 commented Dec 26, 2022

mc1arke commented Dec 26, 2022

mc1arke commented Dec 31, 2022

scholz-afis commented Oct 20, 2022 •

edited

Loading

mgexm commented Oct 25, 2022 •

edited

Loading

MCMicS commented Nov 9, 2022 •

edited

Loading

Elanis commented Dec 19, 2022 •

edited

Loading

dgokcin commented Dec 20, 2022 •

edited

Loading