Links section of my SonarQube configuration page is completely blank and no links are automatically populated here. Any help on how to populate default links on this page which are supposed to be retrieved from project pom?
The CI management URL is automatically fed during SonarQube analysis:
either using the value of the value of the <url> tag of the <ciManagement> section of the POM:
<ciManagement>
<system>Jenkins</system>
<url>the_url_of_your_ci_system</url>
</ciManagement>
or more generally (if you're not using Maven) using the property sonar.links.ci
Related
When I log in "user-portal" of WSO2 Identity Server (the url is "https://localhost:9443/user-portal/overview"), I can see four options to change the language (english, portuguese, sinhalese or tamil).
I need to add more options in this section. How can I do this? I can't see a "Resource.properties" inside the folder "/repository/deployment/server/webapps/user-portal" to do something like in the following link https://is.docs.wso2.com/en/latest/develop/localization-support-in-identity-server/#localization-support-in-identity-server.
Thanks in advance.
Gonzalo.
WSO2IS UserPortal is a React-based application and in there what is done is to combine all the configurations in i118 to react config mappings if you want to change anything you need to do it at the code level.
https://github.com/wso2/identity-apps/blob/v1.0.72/apps/user-portal/src/configs/i18n.ts
you can map all the configs to your preferred language and map them to the configurations used in UserPortal by building the package.
I've been looking for a way to directly access a widget from my SonarQube instance with a direct URL, the way it's possible to access a Dashboard. Is it possible to do that adding the respective metrics from the configuration of the Widget? The problem I found is that I can only "build" a widget and it takes the filter parameter, sizes, but when it comes to the metrics, they are ignored and it builds it with the default ones for the respective widget.
I have the following Widget configured (with metrics: Classes, Comment_Density and size - Complexity):
When building the URL to get directly this widget, I found it impossible to access it by its Id. So, I added all configuration details, but the widget I get is this, holding the default metrics - Lines of Code, Issues and Technical Debt. Built widget:
Is accessing directly a configured Widget even possible with the current versions of the SonarQube?
The URL I used is :
<sonarqubeinstance>/widget?id=measure_filter_bubble_chart&filter=1&chartTitle=Measure%20Bubble%20Chart&chartHeight=400&widget_width=1279px&metric1=classes&metric2=comment_lines_density&metric3=complexity
Thanks in advance for your help!
What you try to achieve is not possible.
What's more, keep in mind that those widgets do not exist any more starting with SonarQube 6.2. And there is no plan to reintroduce them.
silverstripe has main page, which after every rebuild is created new (as home page not always suits).
How and where can i see/change this after rebuilt in mysql level (table?).
I have looked however could not find place/table/field which denotes that this is "link of home page, etc."
Any help would be nice.
This is created based of requireDefaultRecords in SiteTree, this indicates that this can be stopped with a yml config (in _config/config.yml)
SiteTree:
'create_default_pages' : 'false'
In old and deprecated SilverStripe 2.4 you could define any page as homepage for a domain. However this was refactored to a module in 3.x and by default the page with URLSegment "home" is the default home page.
But you can install the functionality with the homepage for domain module, best using composer:
composer require silverstripe/homepagefordomain
which will add an input field to the cms where you can define that page as homepage for a specific domain.
I have successfully added a data set for the CKAN site. It enables to preview the data set as well.
Below is the URL for the data set
testckan.com:5000/dataset/my-data1/resource/4c2647ca-a4ab-4d20-8119-5c3da9d4ae14
By adding api/rest/ to the URL as below enables to expose data sets as a JSON service.
testckan.com:5000/api/rest/dataset/my-data1/resource/4c2647ca-a4ab-4d20-8119-5c3da9d4ae14
All I want to do is add an button so that user can view the data set as a JSON rather than typing it in the URL which is not user friendly.
I have seen similar button in the
http://data.gov.uk/dataset/bona-vacantia-estates-advertisements
under API & APPS. Please see the image below.
How to enable API button for CKAN data set like above?
You will have to modify the front-end templating for the package (aka dataset) view. You can either add this change to your own copy of CKAN source code, or like Hendrik mentioned and data.gov.uk people have done, create a CKAN extension to modify the templates.
Your example of the feature is implemented for the data.gov.uk site which is open source and available in GitHub. The specific part is in the read_common.html:
<b>API: </b><a href="${h.url_for(controller='api', register='package', action='show', id=c.pkg.name, ver='2')}">
${h.url_for(controller='api', register='package', action='show', id=c.pkg.name, ver='2')}
</a>
The url_for function is from the ckan.lib.helpers module which "is available for templates as 'h'" according to the CKAN docs, so you should be able to use it directly in the template as in the code above.
AFAIK that's no feature of CKAN itself, thus it can not be enabled. You can, however, easily add it yourself in an extension.
Our build has a variety of generated HTML reports. I would like to have those reported and accessible on the build page, like JavaDoc entries. Is there a generic way to expose these reports without writing a custom plug ins ?
If that isn't available, is there a way to post an HTTP link on the page ?
You can choose "archive the artifacts" and archive for example "reports/*.html"
These will appear under the project page under the heading "Last successful artifacts".
Even if you clear your workspace before each build, these artifacts are moved to a separate directory.
You could also add a build script which will modify or update a file in your userContent directory (since Hudson 1.299), and link to these build artifacts in yet another location.