Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cu-dev] TCK re-spin needed and Jenkins job does not appear to be overwriting promoted
  • From: "Steve Millidge (Payara)" <steve.millidge@xxxxxxxxxxx>
  • Date: Tue, 26 Apr 2022 17:12:11 +0000
  • Accept-language: en-GB, en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=payara.fish; dmarc=pass action=none header.from=payara.fish; dkim=pass header.d=payara.fish; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=MFfQAtvLav1aabIdatatcMDVDU6USM9Zwk0iqkESV5g=; b=BNO2mUFD0VGnJm/uEFF2fD2SdnxFQ403DwpbDnSiy1V2FKS6B335WUH1lZVAt9fFk3bi1dqG5JFY9U/5MMOH2kKtvdkd11ThqJGpQqp0626cYRONIS83LHw1/rACMpZH9iOwVxciMStEMefsm5u6R7xqbnTZ4zmVxGR6ktoM7X73tWF4FJdeom+UP2iPROqMbLsVbkz3q0nodZQgRIZC39mitekr5beSivJIqVjbCWABDrfxXkykl/20nXWx7a0u3H/T5v5D+oCHEdBs+jCWfRPrIaKsoYMTUXhzcWNi1uZy0lsBhzfqFps0LJADbDEsG4Qra3fMT3szMhHXAzlWwQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=lKn2fBYRxMs4EGDTjLVYIlVIU9WnFiqw9JkDY9KTXlHOq2GBIcHv+QjLq/GuxD/uHXPX+2+/M/wNnCeYDlmI28ol+Ifrf0L9PQNjOEJSyldbIAWzxr1al6UfM7i7unhVCaY5MKUjxk1cvAWL1jc3imgkACkq4uE0Gw1DixtNoYXTRDJ1yc9ZBcjmvIkMi5g5mCrupyF68KIVW+ay0B+AjwMIorNoK8f+vmjTzfaw3lFnfIzfJoNqeDkb1bJC/C01fTlzn50uVKI8IJ4g1TJ9TgWN7f9Mq96gVjet1J5iOVNL17IlIajh6Fc7OJkQMkxFxvjQbwQPxtltLZRKbpYoww==
  • Delivered-to: cu-dev@xxxxxxxxxxx
  • List-archive: <https://www.eclipse.org/mailman/private/cu-dev/>
  • List-help: <mailto:cu-dev-request@eclipse.org?subject=help>
  • List-subscribe: <https://www.eclipse.org/mailman/listinfo/cu-dev>, <mailto:cu-dev-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://www.eclipse.org/mailman/options/cu-dev>, <mailto:cu-dev-request@eclipse.org?subject=unsubscribe>
  • Thread-index: AQHYWY9/r50begfMFEKnafQZSzBdOq0CbkOQ
  • Thread-topic: [cu-dev] TCK re-spin needed and Jenkins job does not appear to be overwriting promoted

I’ll take a look at the job to see what it is doing. I now Petr has some other TCK challenges he is working on.

 

From: Nathan Rauh <nathan.rauh@xxxxxxxxxx>
Sent: 26 April 2022 18:03
To: cu developer discussions <cu-dev@xxxxxxxxxxx>; Petr Aubrecht <aubrecht@xxxxxxxxxxxx>; Steve Millidge (Payara) <steve.millidge@xxxxxxxxxxx>; arjan tijms <arjan.tijms@xxxxxxxxx>
Subject: Re: [cu-dev] TCK re-spin needed and Jenkins job does not appear to be overwriting promoted

 

Petr found a copy/paste error that needed to be fixed in the TCK, and so I had to re-build the TCK.
Both builds claimed to be successful, however, it appears that the Promote Staged TCK didn’t actually overwrite the artifacts at the promoted location

 

Staged:

https://download.eclipse.org/ee4j/cu/jakartaee10/staged/eftl/concurrency-tck-3.0.0.info

2fe905b8adfab903a6c5954453e67fbc3ed583b0e313edef7f09d18b7eddd0ee  concurrency-tck-3.0.0-dist.zip

-rw-r--r--. 1 jenkins 1001550000 398136 Apr 26 16:27 concurrency-tck-3.0.0-dist.zip

 

Promoted:

https://download.eclipse.org/ee4j/cu/jakartaee10/promoted/eftl/concurrency-tck-3.0.0.info

93fdfc808fff4e2fbd52883c7378b369d8ee81c87964ca8d3b6dfc20eb03e1d4  concurrency-tck-3.0.0-dist.zip
-rw-r--r--. 1 jenkins 1001550000 398134 Apr 25 18:21 concurrency-tck-3.0.0-dist.zip

 

Note the date and SHA under promoted still match the original, not the updated from staged.

 

We can probably go ahead with the release approval based only on the staged location, assuming that it will be possible to fix the Promote Staged TCK build to do an overwrite (Arjan and Steve – your help is needed with this).  However, if we do that, it will be important that no one submits any further Concurrency TCK Master Builds or merges changes to the spec (which will trigger a Concurrency TCK Master Build) in the meantime because doing so would overwrite the staged copy that we are attempting to use for approval.

 

 

 

From: cu-dev <cu-dev-bounces@xxxxxxxxxxx> on behalf of "Steve Millidge (Payara)" <steve.millidge@xxxxxxxxxxx>
Reply-To: cu developer discussions <cu-dev@xxxxxxxxxxx>
Date: Monday, April 25, 2022 at 1:36 PM
To: cu developer discussions <cu-dev@xxxxxxxxxxx>
Subject: [EXTERNAL] [cu-dev] Promoted and Staged TCKs on our downloads

 

Hi All, Thanks for the assistance from various people. We now have both staged and promoted TCK zip files on Eclipse Downloads Project download area | The Eclipse Foundation Project download area | The Eclipse Foundation ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍

ZjQcmQRYFpfptBannerStart

This Message Is From an External Sender

This message came from outside your organization.

ZjQcmQRYFpfptBannerEnd

Hi All,

 

Thanks for the assistance from various people.

 

We now have both staged and promoted TCK zip files on Eclipse Downloads

Project download area | The Eclipse Foundation

Project download area | The Eclipse Foundation

 

I have modified the TCK Build job Jakarta Concurrency - Concurrency TCK Master Build [Jenkins] (eclipse.org) to automatically upload to the staged directory on downloads if the build succeeds. This job is triggered by a commit in the repo which means that if there is a change a new TCK zip will appear in the staged directory with likely a new SHA.

 

I have also created a Jenkins job Jakarta Concurrency - Promote Staged TCK [Jenkins] (eclipse.org) which copies the zip file from the staged directory to the promoted directory. This job is manually triggered so we have control if we want to “promote” a specific “staged” zip file.

 

I’m sure these jobs could be done better if I had a better view of what an ideal workflow would be for releasing the TCK but should suffice to get us to ballot.

 

Any problems give me a shout.

 

Steve Millidge

 

Back to the top