From dev-return-8489-archive-asf-public=cust-asf.ponee.io@tamaya.incubator.apache.org Mon Apr 29 20:24:12 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id B799518061A for ; Mon, 29 Apr 2019 22:24:11 +0200 (CEST) Received: (qmail 20550 invoked by uid 500); 29 Apr 2019 20:24:11 -0000 Mailing-List: contact dev-help@tamaya.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tamaya.incubator.apache.org Delivered-To: mailing list dev@tamaya.incubator.apache.org Received: (qmail 20538 invoked by uid 99); 29 Apr 2019 20:24:11 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Apr 2019 20:24:11 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 8F002C044D for ; Mon, 29 Apr 2019 20:24:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -107.201 X-Spam-Level: X-Spam-Status: No, score=-107.201 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id uszJR_QTNdMj for ; Mon, 29 Apr 2019 20:24:04 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id 3736361191 for ; Mon, 29 Apr 2019 20:24:03 +0000 (UTC) Received: (qmail 19694 invoked by uid 99); 29 Apr 2019 20:24:02 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Apr 2019 20:24:02 +0000 Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 97E53E2B5B for ; Mon, 29 Apr 2019 20:24:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id AB8952581C for ; Mon, 29 Apr 2019 20:24:00 +0000 (UTC) Date: Mon, 29 Apr 2019 20:24:00 +0000 (UTC) From: "Philipp Ottlinger (JIRA)" To: dev@tamaya.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (TAMAYA-277) Integrate Tamaya with SonarCloud as ASF's Sonarcube is deprecated MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/TAMAYA-277?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger updated TAMAYA-277: ------------------------------------- Description:=20 Before closing TAMAYA-12 I had a look at Apache's SonarCube and could not f= ind our projects there. Task is to find out why we lost them and if so, to readd them. Target environment: [https://builds.apache.org/analysis] h2. Target links * [https://sonarcloud.io/dashboard?id=3Dincubator-tamaya_180410] ** apache_incubator-tamaya =3D project-key ** apache =3D organization key ** generate badge in README.md of each project * [https://sonarcloud.io/dashboard?id=3Dapache_incubator-tamaya-extensions= ] ** apache_incubator-tamaya-extensions =3D project-key * [https://sonarcloud.io/dashboard?id=3Dapache_incubator-tamaya-sandbox] ** apache_incubator-tamaya-sandbox =3D project-key * In order to spot problems with the build file you need to check: ** [https://travis-ci.org/apache/incubator-tamaya-sandbox/requests] for ea= ch repo/Travis integration :)=20 h2. Links * [https://docs.travis-ci.com/user/sonarcloud/] - Integration with Travis/= Sonarcloud ** does not work as it needs a proper login to encryp tokens .... * Run manual analysis: TOKENGOESHERE =3D manually generated after logging = in to sonarcloud.io {code:java} mvn sonar:sonar \ =C2=A0 -Dsonar.projectKey=3Dapache_incubator-tamaya \ =C2=A0 -Dsonar.organization=3Dapache \ =C2=A0 -Dsonar.host.url=3Dhttps://sonarcloud.io \ =C2=A0 -Dsonar.login=3DTOKENGOESHERE goes through =C2=A0mvn clean org.jacoco:jacoco-maven-plugin:prepare-agent install sonar:= sonar \ =C2=A0 -Dsonar.projectKey=3Dapache_incubator-tamaya \ =C2=A0 -Dsonar.organization=3Dapache \ =C2=A0 -Dsonar.host.url=3Dhttps://sonarcloud.io \ =C2=A0 -Dsonar.login=3DTOKENGOESHERE {code} =C2=A0 * (/) Settings in Travis itself - thanks [~acoburn] The second approach involves adjusting the settings in the Travis-CI web interface: [https://travis-ci.org/apache/incubator-tamaya/settings] Under the "Environment Variables" section, you'd need to add an entry with the Name set to SONAR_TOKEN and the Value set to the value of the token from Sonarcloud. Make sure that "Display value in build log" is set to "false". was: Before closing TAMAYA-12 I had a look at Apache's SonarCube and could not f= ind our projects there. Task is to find out why we lost them and if so, to readd them. Target environment: [https://builds.apache.org/analysis]=20 h2. Target links * [https://sonarcloud.io/dashboard?id=3Dincubator-tamaya_180410] ** apache_incubator-tamaya =3D project-key ** apache =3D organization key ** generate badge in README.md of each project * [https://sonarcloud.io/dashboard?id=3Dapache_incubator-tamaya-extensions= ] ** TODO * [https://sonarcloud.io/dashboard?id=3Dapache_incubator-tamaya-sandbox] ** TODO =C2=A0 h2. Links * [https://docs.travis-ci.com/user/sonarcloud/] - Integration with Travis/= Sonarcloud ** does not work as it needs a proper login to encryp tokens .... * Run manual analysis: TOKENGOESHERE =3D manually generated after logging = in to sonarcloud.io {code:java} mvn sonar:sonar \ =C2=A0 -Dsonar.projectKey=3Dapache_incubator-tamaya \ =C2=A0 -Dsonar.organization=3Dapache \ =C2=A0 -Dsonar.host.url=3Dhttps://sonarcloud.io \ =C2=A0 -Dsonar.login=3DTOKENGOESHERE goes through =C2=A0mvn clean org.jacoco:jacoco-maven-plugin:prepare-agent install sonar:= sonar \ =C2=A0 -Dsonar.projectKey=3Dapache_incubator-tamaya \ =C2=A0 -Dsonar.organization=3Dapache \ =C2=A0 -Dsonar.host.url=3Dhttps://sonarcloud.io \ =C2=A0 -Dsonar.login=3DTOKENGOESHERE {code} =C2=A0 * (/) Settings in Travis itself - thanks [~acoburn] The second approach involves adjusting the settings in the Travis-CI web interface: [https://travis-ci.org/apache/incubator-tamaya/settings] Under the "Environment Variables" section, you'd need to add an entry with the Name set to SONAR_TOKEN and the Value set to the value of the token from Sonarcloud. Make sure that "Display value in build log" is set to "false". > Integrate Tamaya with SonarCloud as ASF's Sonarcube is deprecated > ----------------------------------------------------------------- > > Key: TAMAYA-277 > URL: https://issues.apache.org/jira/browse/TAMAYA-277 > Project: Tamaya > Issue Type: Improvement > Components: Infrastructure > Reporter: Oliver B. Fischer > Assignee: Philipp Ottlinger > Priority: Major > Fix For: 0.4-incubating > > Time Spent: 4h 10m > Remaining Estimate: 0h > > Before closing TAMAYA-12 I had a look at Apache's SonarCube and could not= find our projects there. > Task is to find out why we lost them and if so, to readd them. > Target environment: > [https://builds.apache.org/analysis] > h2. Target links > * [https://sonarcloud.io/dashboard?id=3Dincubator-tamaya_180410] > ** apache_incubator-tamaya =3D project-key > ** apache =3D organization key > ** generate badge in README.md of each project > * [https://sonarcloud.io/dashboard?id=3Dapache_incubator-tamaya-extensio= ns] > ** apache_incubator-tamaya-extensions =3D project-key > * [https://sonarcloud.io/dashboard?id=3Dapache_incubator-tamaya-sandbox] > ** apache_incubator-tamaya-sandbox =3D project-key > * In order to spot problems with the build file you need to check: > ** [https://travis-ci.org/apache/incubator-tamaya-sandbox/requests] for = each repo/Travis integration :)=20 > h2. Links > * [https://docs.travis-ci.com/user/sonarcloud/] - Integration with Travi= s/Sonarcloud > ** does not work as it needs a proper login to encryp tokens .... > * Run manual analysis: TOKENGOESHERE =3D manually generated after loggin= g in to sonarcloud.io > {code:java} > mvn sonar:sonar \ > =C2=A0 -Dsonar.projectKey=3Dapache_incubator-tamaya \ > =C2=A0 -Dsonar.organization=3Dapache \ > =C2=A0 -Dsonar.host.url=3Dhttps://sonarcloud.io \ > =C2=A0 -Dsonar.login=3DTOKENGOESHERE > goes through > =C2=A0mvn clean org.jacoco:jacoco-maven-plugin:prepare-agent install sona= r:sonar \ > =C2=A0 -Dsonar.projectKey=3Dapache_incubator-tamaya \ > =C2=A0 -Dsonar.organization=3Dapache \ > =C2=A0 -Dsonar.host.url=3Dhttps://sonarcloud.io \ > =C2=A0 -Dsonar.login=3DTOKENGOESHERE > {code} > =C2=A0 > * (/) Settings in Travis itself - thanks [~acoburn] > The second approach involves adjusting the settings in the Travis-CI web > interface: [https://travis-ci.org/apache/incubator-tamaya/settings] > Under the "Environment Variables" section, you'd need to add an entry wi= th > the Name set to SONAR_TOKEN and the Value set to the value of the token > from Sonarcloud. Make sure that "Display value in build log" is set to > "false". -- This message was sent by Atlassian JIRA (v7.6.3#76005)