Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec.committee] [External] : Re: TCK promotion CI job?
We'll need to do this one last time after all PRs in progress are merged.  I suggest we leave ourselves at least one additional business day after all ballots are closed before we announce.


-- 
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
310-633-3852

On Apr 8, 2022, at 4:09 PM, David Blevins <dblevins@xxxxxxxxxxxxx> wrote:

Thanks, Scott for merging #477.  

All, I've updated our promotion script with the new URL and tested it out.   All is working.

The final step is updating our specification pages so users are not being directed towards something that is rate-limited.  I've prepared a PR for that here:


Thanks, Ed for pointing this out and Ivar for finding the rate-limiting issue.


-- 
David Blevins
310-633-3852

On Apr 7, 2022, at 9:08 AM, David Blevins <dblevins@xxxxxxxxxxxxx> wrote:

Thanks for the rate limiting information, Ivar.

In light of that, I've created a PR so it is published in our specifications repository and will show up on the website:


After mentioning not using HTTP, I thought further and remembered the point of that part of the script was to do the verification steps as a user would need to do them to ensure they could successfully verify the downloads. If we're hitting github rate limit issues, they might hit them as well.  Having the key in the same location where it is referenced on the specification pages is ideal.  Basically, anywhere but the downloads area where the binaries live is viable.

Once we get this merged I'll update the CI scripts and send another PR to update the link we use for the public key in our specification pages.



On Apr 7, 2022, at 8:34 AM, Ed Bratt <ed.bratt@xxxxxxxxxx> wrote:

Ivar, thanks for getting it pushed. And thanks for looking into the root cause.

Maybe the .pub file could just be checked into the repo. that we are already checking out (jakartaee-specification-tools.git) -- then, perhaps we don't need to separately retrieve it. (Maybe this is what you are suggesting Ivar?)

Is there some greater design or function that is achieved by having the .pub file stored/retrieved separately? Originally, I liked the idea thinking we might update it from time to time but -- why not just check it in and then just pull it down via a GIT Sync. operation?

-- Ed

On 4/6/2022 9:26 PM, Ivar Grimstad wrote:
Hi,

It appears to be an issue with GitHub using rate limits for URLs like raw.githubusercontent.com.
Mikael has written a suggested workaround for this issue here:


Following this, the solution could be to replace the curl call to https://raw.githubusercontent.com/jakartaee/specification-committee/master/jakartaee-spec-committee.pub with an API call.

Ivar

On Thu, Apr 7, 2022 at 12:14 AM Ed Bratt <ed.bratt@xxxxxxxxxx> wrote:

Thanks David. Probably something isn't set correctly in the network config files. But, that's just a wild guess. Seems like the Git operations are working so ... it's curious.

-- Ed

On 4/6/2022 2:55 PM, David Blevins wrote:
This appears to be some kind of DNS error.  I’m not sure there’s much we can do with that other than try using something other than http.

I can take a peek when I get home in a few hours. 

On Wed, Apr 6, 2022 at 2:28 PM Ed Bratt <ed.bratt@xxxxxxxxxx> wrote:

Does anyone know the trick to getting the Promote-Release CI job to succeed? It seems to be failing when trying to pull the committee public key -- 


curl: (6) Could not resolve host: raw.githubusercontent.com; Unknown error
See console output here.

Is this an environment / network issue, or something with our script? I can click the link to the Public key and my browser has no problem retrieving the document. I can see that previous users have had to retry this operation a few times for it to work -- Does anyone have suggestions to get this to work?

-- Ed

_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
--
Sent from Gmail Mobile

_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee__;!!ACWV5N9M2RV99hQ!aZV1BqmrVEN-jAGUrXWjuNsNOu-jLa_kYypfwXqP_4k47d2jWgNdyej0BqBOZLk$
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee


--
Ivar Grimstad
Jakarta EE Developer Advocate | Eclipse Foundation Eclipse Foundation - Community. Code. Collaboration. 

_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee__;!!ACWV5N9M2RV99hQ!fuUxc8lOuRDj1f8wH_saP0fY6JBCgez2SlvGtSQR7Bt6caT3kADgUDkK1DVU3vw$
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee



Back to the top