Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cu-dev] Gitlab issue for uploads

Hi,

On Mon, Apr 25, 2022 at 5:20 PM Nathan Rauh <nathan.rauh@xxxxxxxxxx> wrote:

Staging to the Concurrency project is fine with me.  To report the TCK results, we just need to list a link to staging somewhere (and the SHA).


What exactly is the "staging in the concurrency project" location? 

I tried:

ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null genie.cu@xxxxxxxxxxxxxxxxxxxxxxxxxxxx mkdir /home/data/httpd/download.eclipse.org/ee4j/concurrency

But that results in:

mkdir: cannot create directory ‘/home/data/httpd/download.eclipse.org/ee4j/concurrency’: Permission denied

Some of the existing projects in /home/data/httpd/download.eclipse.org/ee4j/ indeed dit put their TCKs there.


To report the TCK results, we just need to list a link to staging somewhere (and the SHA).

That one can be done at the GlassFish project or in the Concurrency RI project. See e.g. https://glassfish.org/certifications/jakarta-concurrency/2.0/TCK-Results

 For the Open Liberty results I guess Concurrency RI would be best.

Kind regards,
Arjan Tijms
 

Back to the top