Re: [helpWanted] Example integration with SonarCloud

Hi Phil, On Mon, 2019-04-22 at 21:26 +0200, P. Ottlinger wrote: > Hi guys, > > I'm trying to hook Tamaya into Sonarcloud.io via Travis . > https://github.com/apache/incubator-tamaya or > https://issues.apache.org/jira/browse/TAMAYA-277 > > At the moment the builds does not work can anyo

[helpWanted] Example integration with SonarCloud

Hi guys, I'm trying to hook Tamaya into Sonarcloud.io via Travis . https://github.com/apache/incubator-tamaya or https://issues.apache.org/jira/browse/TAMAYA-277 At the moment the builds does not work can anyone point my to a working Java-project at ASF that integrations with Sonarcloud?

Re: [osuosl-openpower] ACTION REQUIRED: 2019 OSL OpenPOWER Cluster Survey

Hi all, I wanted to resend this email again as a reminder. As of today, we only have almost 1/3 of projects having completed this survey. Thanks- On Fri, Mar 29, 2019 at 9:19 AM Lance Albertson wrote: > Hello OSU OpenPOWER development cluster users, > > In order to extend your usage of OSU res

Re: [osuosl-openpower] OpenStack Pike Upgrade - April 22, 2019 9am-11am PDT (1600-1800 UTC)

This upgrade has been completed. I believe everything is working now again. You might have noticed a few brief network outages with your virtual machines but no reboots should have happened. Please email powerdev-requ...@osuosl.org if you're having any issues related to the upgrade. Thanks! On Mo

Re: Gradle publish from Jenkins slaves

Right, there is nothing to fix here. Any 'externally' managed nodes that can have external users login to the nodes can not and will not have any asf credentials placed on them. This includes all of the 'Beam' nodes. All the internally hosted and managed jenkins nodes all do not accept logins from

Re: Gradle publish from Jenkins slaves

And to be clear, I think there are two issues, and perhaps no bug nor "fix" per se. The Beam issue is https://issues.apache.org/jira/browse/BEAM-6919 but then it sounds like having an easy way to identify which agents have the needed gradle.properties file is somewhat independent (but helpful for u

Re: Gradle publish from Jenkins slaves

It looks like your other thread has a part of the answer. There's no plan to get the credentials onto external VMs as it used to, but the publish command itself could run on ASF-managed instances. Kenn On Mon, Apr 22, 2019 at 8:37 AM Antoine Toulme wrote: > Got it. Is there a ticket open to fix

Re: Gradle publish from Jenkins slaves

Got it. Is there a ticket open to fix this? Alternatively, jenkins could store the credentials and inject them in the build. Where can I get more context? > On Apr 22, 2019, at 08:08, Kenneth Knowles wrote: > > Yes, this is because previously these boxes were managed by infra using > puppet. T

Re: Gradle publish from Jenkins slaves

Yes, this is because previously these boxes were managed by infra using puppet. They published snapshots for a very long time succesfully. Infra has changed how they accept these workers, so now they are not puppetized, hence do not have the private credentials. This is a very recent change. Kenn

Re: Gradle Config Settings for Snapshots

I’m glad I found this old email. It looks like not all slaves have the right gradle.properties file set. I just managed to get by with H24 just now. How were those files installed? Cheers, Antoine On 2017/01/10 03:37:30, "John D. Ament" wrote: > Hi All,> > > Just wanted to inform you that

Re: Gradle publish from Jenkins slaves

Hey folks, Actually your build fails just like mine: https://builds.apache.org/job/beam_Release_NightlySnapshot/415/console 10:05:31 > Failed to publish publication 'mavenJava' to repository 'maven' 10:05:31> Could not