On 4/22/24 10:45, Scott Marlow wrote:
Maybe try updating the CI job that does the
promotion to "rm" the ^ concurrency-tck-3.1.0.zip +
tck-3.1.0.info
files via a "ssh" command prior to where you do the "scp" the
new TCK. That has worked for us on the Platform TCK team in the
past.
For example, one of the Platform TCK CI jobs contains the
following currently:
"
scp -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
jakarta-jakartaeetck-10.0.4.zip
genie.jakartaee-tck@xxxxxxxxxxxxxxxxxxxxxxxxxxxx:/home/data/httpd/download.eclipse.org/ee4j/jakartaee-tck/jakartaee10/staged/eftl/
scp -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
$WORKSPACE/jakartaeetck.version
genie.jakartaee-tck@xxxxxxxxxxxxxxxxxxxxxxxxxxxx:/home/data/httpd/download.eclipse.org/ee4j/jakartaee-tck/jakartaee10/staged/eftl/
scp -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
$WORKSPACE/jakarta-jakartaeetckinfo.txt
genie.jakartaee-tck@xxxxxxxxxxxxxxxxxxxxxxxxxxxx:/home/data/httpd/download.eclipse.org/ee4j/jakartaee-tck/jakartaee10/staged/eftl/
ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
genie.jakartaee-tck@xxxxxxxxxxxxxxxxxxxxxxxxxxxx ls -lt
/home/data/httpd/download.eclipse.org/ee4j/jakartaee-tck/jakartaee10/staged/eftl/
"
If I update the above to the following, it will delete the
specified files before doing the "scp":
"
# remove old jakarta-jakartaeetck-10.0.4.zip file before copying
updated jakarta-jakartaeetck-10.0.4.zip
ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
genie.jakartaee-tck@xxxxxxxxxxxxxxxxxxxxxxxxxxxx rm
/home/data/httpd/download.eclipse.org/ee4j/jakartaee-tck/jakartaee10/staged/eftl/jakarta-jakartaeetck-10.0.4.zip
scp -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
jakarta-jakartaeetck-10.0.4.zip
genie.jakartaee-tck@xxxxxxxxxxxxxxxxxxxxxxxxxxxx:/home/data/httpd/download.eclipse.org/ee4j/jakartaee-tck/jakartaee10/staged/eftl/
scp -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
$WORKSPACE/jakartaeetck.version
genie.jakartaee-tck@xxxxxxxxxxxxxxxxxxxxxxxxxxxx:/home/data/httpd/download.eclipse.org/ee4j/jakartaee-tck/jakartaee10/staged/eftl/
scp -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
$WORKSPACE/jakarta-jakartaeetckinfo.txt
genie.jakartaee-tck@xxxxxxxxxxxxxxxxxxxxxxxxxxxx:/home/data/httpd/download.eclipse.org/ee4j/jakartaee-tck/jakartaee10/staged/eftl/
ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
genie.jakartaee-tck@xxxxxxxxxxxxxxxxxxxxxxxxxxxx ls -lt
/home/data/httpd/download.eclipse.org/ee4j/jakartaee-tck/jakartaee10/staged/eftl/
"
Scott
Hello Everyone,
Thanks for the suggestion Ivar. I think I ran into
this before where the site says that committers can do
these things, but really it is only someone on the
steering committee for Jakarta EE that can.
I get the following error if I try to archive these
artifacts
Thanks again,
Kyle Jon Aure
Hi Kyle,
Tip: You can also create a jenkins job that does it
for you, but if it's only occasionally, doing it
manually is just as convenient.
Ivar
Hello Everyone,
I ran the Jenkins job to do this before
realizing the job needed to be updated.
I need someone who has access to delete the
3.1.0 TCK from the jakartaee10 staging site.
Thank you,
Kyle Jon Aure
_______________________________________________
cu-dev mailing list
cu-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cu-dev
--
Ivar Grimstad
Jakarta EE Developer Advocate | Eclipse Foundation
Eclipse
Foundation - Community. Code. Collaboration.
_______________________________________________
cu-dev mailing list
cu-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cu-dev
_______________________________________________
cu-dev mailing list
cu-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cu-dev