To follow-up on the original topics, I have approved all SonarCloud GitHub
app requests by plugin maintainers. If it addresses the use-case, no need
to setup the official organization for the moment.
Custom project setups are going to be a mess in the case of plugin
adoption, because we won't
I'm looking to track progress in areas like:
- code coverage by automated tests
- spotbugs warnings
- style checker warnings like checkstyle and pmd
- security check results
- dependency check results
I want something that persists longer than jobs in a Jenkins instance and
allows
Hi Mark,
What kind of metrics are you looking for? Are you talking about code
quality metrics? from what components?
Yes, you should be able to re-use it simply from our repositories. If you
are talking about visualising non-code-quality metrics, then probably
Grafana would be a better choice.
I would like to know how to publish a better set of metrics to SonarCloud
from the jobs that I run on ci.jenkins.io. If that isn't feasible, then
I'd like to know how to publish a better set of metrics from jobs that I
run on my own CI servers. I think that I can probably extract the
techniques
Hi all,
For future reference, I made it work with my personal organisation on SC,
here are the relevant changes:
https://github.com/jenkinsci/jira-plugin/commit/56cbe1d54eacfed207a7c6bfa04ce56cccfd604c
https://github.com/jenkinsci/jira-plugin/commit/87c75543e8c8827e704beb7ea9427558c45cfb1a
I am not sure what specific kind of integration are you guys looking
for, but I managed to get sonar publishing to work a while ago[1][2].
- There is no requirement to have a centralized "jenkins" sonarcloud org
nor having it connected to "jenkinsci" github org to have projects in
that org
Thanks for raising this in their community forum! I often meet with
SonarSource engineers and PMs at meetups in Switzerland, and I will make
sure to bring up this topic with them
On Sun, Feb 2, 2020, 12:26 Radosław Antoniuk
wrote:
> Hi Oleg,
>
> Thanks for picking this up. Yes, I totally agree
Hi Oleg,
Thanks for picking this up. Yes, I totally agree that the requirement for
the organisation admin to link to specific repository won't work in the
Jenkins OSS forking approach.
I already asked the same question in the help forum and let's see where it
goes from there:
Hi all,
UPD: it looks like we cannot really add projects to SonarCloud without
linking the entire organization there.
Not going to happen without explicit approval by the security team and the
governance meeting.
I suggest other alternate options:
- Use personal forks for analysis. It
Looks like the project IDs are already used for jenkins:
https://sonarcloud.io/dashboard?id=jenkins
"jenkinsci" is a registered organization, I believe. We have 3 repos with
enabled SonarCloud app:
[image: sonarcloud.PNG]
> Additionally, apparently I need organisation admin permissions on
>
Hey,
I'm trying to hook jira-plugin into SonarCloud, but when I'm trying to
create jenkins or jenkinsci organisation, it shows me that the organisation
already exists.
Additionally, apparently I need organisation admin permissions on
github.com/jenkinsci organisation to be able to link it
11 matches
Mail list logo
