JDK11u repository and tagging

[yangfei at iscas.ac.cn]

Hello,

Thanks for the details. 
And I have just pushed a repo-specific tag (jdk-11.0.25+4-riscv64-20240825) which is equivalent to the latest tag of jdk11u-dev repo (jdk-11.0.25+4) [1][2]. 
Hope that resolves your current issue. I will try to keep syncing and adding these repo-specific tags regularly.

[1] https://github.com/openjdk/riscv-port-jdk11u/releases/tag/jdk-11.0.25%2B4-riscv64-20240825
[2] https://github.com/openjdk/riscv-port-jdk11u/releases/tag/jdk-11.0.25%2B4

Regards,
- Fei Yang


-----Original Messages-----
From:"Stewart X Addison" <sxa at redhat.com>
Sent Time:2024-08-21 19:52:30 (Wednesday)
To: yangfei at iscas.ac.cn
Cc: "Ludovic Henry" <ludovic at rivosinc.com>, riscv-port-dev <riscv-port-dev at openjdk.org>, fyang at openjdk.org
Subject: Re: JDK11u repository and tagging

> --  Not sure if I understand your requirements correctly. Are these tags here https://github.com/openjdk/riscv-port-jdk11u/tags you are looking for?
>   This should be the same as the tags of jdk11u-dev upstream (https://github.com/openjdk/jdk11u-dev/tags)  
  
  That is correct and exactly describes the problem. They are pointing at the same commits as upstream so they cannot be used to build on riscv64 as they do not include the riscv64 commits from the riscv-port branch. We are looking for an equivalent tag that we can reference in our CI which equates to the current tag but including the riscv64 patches which make that tag build on the platform (which is what is done in https://github.com/openjdk/aarch32-port-jdk8u/tags for example) or to have the existing tags in that repository overwritten by an equivalent tag that includes the commits for riscv64 support (that option would make our automation easier but there are reasons to choose both approaches).  
  
  To see the problem in action you can look at the logs of the jobs in our CI at https://ci.adoptium.net/job/build-scripts/job/jobs/job/evaluation/job/jobs/job/jdk11u/job/jdk11u-evaluation-linux-riscv64-temurin/ - a similar set of jobs are initiated by us across all platforms when a new jdk-11.0.x+y tag appears on the main jdk11u repository, and then the builds on each platform (such as the one in that link) are kicked off to build that specific tag. This does not work for riscv64 at present so all of those jobs fail (#40 on there is an exception as it was manually triggered without a tag being passed in so built successfully as it came from the HEAD of the default riscv-port branch). Our goal here is to have a way to perform a riscv64 build of something equivalent to the upstream tags. Hopefully that explains the requirement. Let us know if there are any further questions on this.

Regards,      
      
      Stewart...      
      --      
      Working for Red Hat on Adoptium Temurin and Node.js
https://fosstodon.org/@sxa        
      
https://github.com/sxa


On Mon, 19 Aug 2024 at 15:50, <yangfei at iscas.ac.cn> wrote:
Hello,

-----Original Messages-----
From:"Ludovic Henry" <ludovic at rivosinc.com>
Sent Time:2024-08-16 21:35:37 (Friday)
To: riscv-port-dev <riscv-port-dev at openjdk.org>, fyang at openjdk.org
Cc: "Stewart Addison" <sxa at redhat.com>
Subject: JDK11u repository and tagging

Hi,  

As we are trying to have testing and releasing of riscv-port-jdk11u at Adoptium, we are running into the issue that the way we are tagging this repo is inconsistent with jdk11u-dev (see adoptium/temurin-build#3911 for more details) For example, the latest merge from `jdk11u-dev:master` into `riscv-port-jdk11u:riscv-port` with eff8723 merges jdk-11.0.25+2 but no equivalent tag is created on eff8723.  

--  Not sure if I understand your requirements correctly. Are these tags here https://github.com/openjdk/riscv-port-jdk11u/tags you are looking for?
This should be the same as the tags of jdk11u-dev upstream (https://github.com/openjdk/jdk11u-dev/tags)

Taking aarch32-port-jdk8u as an example, the solution has been to tag the merge of the jdk8u-dev tag with an equivalent name. For example, the merge commit of `jdk8u422-ga` is tagged with `jdk8u422-ga-aarch32-20240725`.  

Fei, I understand you've been doing it. Has it been a manual process for you? Are you looking at automating some of the merging process?  

-- I have been doing merge of jdk11u-dev upstream into this repo irregularly, which is done manually. There isn't such an automating of the merging process for now. 
Do you have any suggesion from your side when doing releases? Or shall I delegate this merging work to you guys?

Regards,
- Fei Yang



</sxa at redhat.com></riscv-port-dev at openjdk.org></ludovic at rivosinc.com>


</yangfei at iscas.ac.cn></riscv-port-dev at openjdk.org></ludovic at rivosinc.com></sxa at redhat.com>