Re: Releasing: Finally giving up

Hi Alex, after run CI Server 007 we get this email: >From the royale-typedefs repo: 1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.7 -DskipTests=true This will download the artifacts then unzip and compile the source artifact. 2. Validate that the compiled artifacts match

Re: Releasing: Finally giving up

We imposed ourselves a need to release building with two build systems. That's the biggest issue and that's a requirement of this PMC. That's what makes the need of the actual CI steps and the complex and intricate process. For the rest of Apache a release is: "For an *Apache* project, that

Re: Releasing: Finally giving up

> > > > > We are passing in the timestamp (slightly different format, however still > correct as we also adjusted the format-string). When building locally, the > timestamp is exactly as the timestamp string tells the compiler. On the CI > however there’s this 60 minute offset. I have explicitly

Re: Releasing: Finally giving up

I'm sorry, I must have missed something. Where was Ant involved in any of the problems reported so far? AFAICT, it was all Maven plugins driving our compiler and we couldn't get reproducible binaries. I suggested in one reply that Chris fills a staging repo using his local machine just to

Re: Releasing: Finally giving up

That has nothing to do with the Ant build of release artifacts. That is just using Ant to run command line commands to download and verify Maven release artifacts. I'm pretty sure you can just look at the steps and type them in manually at the command line and you'll get the same results.

Re: Releasing: Finally giving up

Hi, Alex El mié., 25 mar. 2020 a las 19:23, Alex Harui () escribió: > That has nothing to do with the Ant build of release artifacts. That is > just using Ant to run command line commands to download and verify Maven > release artifacts. I'm pretty sure you can just look at the steps and type

Re: Releasing: Finally giving up

Hi Yiashay, I agree ... but I didn't create Maven ... haven't even provided a single PR to it ;-) I think my only noticeable contribution was that they changed their website to forbid the usage of "maven-{something}-plugin" to Apache Maven Core modules (It initially said Apache Maven Plugins

RE: Releasing: Finally giving up

I think the focus should be to agree on the requirements. Whether an RM uses the tool created by Chris or Alex can be a matter of choice. From: Carlos Rovira Sent: Wednesday, March 25, 2020 5:18 PM To: Apache Royale Development

Control over export/rename: Finally giving up

(With credit to Chris for the subject name ) Some of you may know that over the last 2-3 months I've been looking into ways to add more control over how the compiler handles renaming and exporting APIs in the generated JS. Ideally, my work would have culminated in a variety of options that would

Re: Releasing: Finally giving up

Hi Alex, El mié., 25 mar. 2020 a las 22:43, Alex Harui () escribió: > Carlos, > > When I wrote "from a local machine" that means to use whatever computer > you want to use and not the CI server or steps. ç maybe I there's a communication problem, but what I said is that I used my local

Re: Releasing: Finally giving up

'It could be an issue when the US and Europe have different daylight savings time settings. When we saw it work, we were not at one of those transition points.' Southern hemisphere and northern hemisphere differences pivot by 2 hours through these transition gaps, which are typically 2

Re: Releasing: Finally giving up

Carlos, When I wrote "from a local machine" that means to use whatever computer you want to use and not the CI server or steps. What I want to know is what the Maven commands should be to create a release in this "conventional process" you are referring to. Maybe someone else can explain

Build failed in Jenkins: Verify_Royale_Config #826

See Changes: -- Started by upstream project "royale-asjs" build number 952 originally caused by: Started by upstream project "royale-asjs_jsonly"

Re: Releasing: Finally giving up

Hi Alex, El mié., 25 mar. 2020 a las 21:26, Alex Harui () escribió: > Carlos, > > I'm pretty sure that part of the "conventional process" you want to try > requires filling the staging repo from a local machine. > This is what we already did. If you go to [1] will see [2]. That was the upload

Re: Releasing: Finally giving up

Carlos, I'm pretty sure that part of the "conventional process" you want to try requires filling the staging repo from a local machine. I am suggesting that Chris and/or you do exactly that and document the steps and have someone else try those steps, so we can understand what that portion of

Re: Releasing: Finally giving up

Reproducible builds for Royale is certainly new. There could be bugs in North vs South hemispheres. Don't know. Volunteers are welcome to improve this portion of our code. I believe one (maybe the only one) of the challenges is to figure out how to choose a timestamp that can be used in the

Jenkins build is back to normal : Verify_Royale_Config #827

See

Re: Releasing: Finally giving up

On 3/25/20, 4:46 PM, "Carlos Rovira" wrote: > What I want to know is what the Maven commands should be to create a > release in this "conventional process" you are referring to. > If you want to know what's the conventional maven process is, I think I can ask

Re: Releasing: Finally giving up

Hi, first of all, many thanks for all the time invested by Chris this days. We almost didn't have any normal life this latest 2'5 days, but as well many other work (spliced in many hours in the several previous days) was prepared to start this release, so for a person out side this project, I

Re: Findings and Changed to the release steps and the CI configuration.

I'm not quite sure whether the problem you want to solve is that the timestamp of ZipFileEntru is not matching or the timestamps in the catalog.xml are not matching. I could be wrong, but I believe ZipFileEntry problem is different from what is described in the linked article. IIRC, the issue

Royale_Release_Step_005 - Build # 6 - Failure!

Royale_Release_Step_005 - Build # 6 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_005/6/ to view the results.

Royale_Release_Step_005 - Build # 7 - Still Failing!

Royale_Release_Step_005 - Build # 7 - Still Failing: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_005/7/ to view the results.

Royale_Release_Step_005 - Build # 8 - Still Failing!

Royale_Release_Step_005 - Build # 8 - Still Failing: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_005/8/ to view the results.

Release Step 005 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_005 and run the following commands: git push You will need your Apache/Github username and 2FA token.

Release Step 005a Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_005a_If_Utils and run the following commands: git push You will need your Apache/Github username and 2FA token.

Release Step 005 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_005 and run the following commands: git push You will need your Apache/Github username and 2FA token.

Release Step 004 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_004 and run the following commands: git push git checkout release/0.9.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.

Royale_Release_Step_005 - Build # 10 - Still Failing!

Royale_Release_Step_005 - Build # 10 - Still Failing: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_005/10/ to view the results.

Royale_Release_Step_005 - Build # 9 - Still Failing!

Royale_Release_Step_005 - Build # 9 - Still Failing: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_005/9/ to view the results.

Release Step 005a Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_005a_If_Utils and run the following commands: git push You will need your Apache/Github username and 2FA token.

Release Step 007 Succeeded

>From the royale-typedefs repo: 1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.7 -DskipTests=true This will download the artifacts then unzip and compile the source artifact. 2. Validate that the compiled artifacts match the downloaded artifacts. 3. If they do, then run ant

Release Step 004 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_004 and run the following commands: git push git checkout release/0.9.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.

Release Step 007 Succeeded

>From the royale-typedefs repo: 1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.7 -DskipTests=true This will download the artifacts then unzip and compile the source artifact. 2. Validate that the compiled artifacts match the downloaded artifacts. 3. If they do, then run ant

Release Step 002a Succeeded

Continue on to Release Step 003

Release Step 003 Succeeded

>From the royale-compiler repo: 1. If you are releasing the utils jars (compiler-jburg-types and compiler-build-tools) - you have set in previous step for mentioned projects version ex. 1.1.0 not snapshot, run: ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.7

Release Step 001 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_001 and run the following commands: git push git checkout release/0.9.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.

Release Step 002 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_002 and run the following commands: git push git push origin org.apache.royale.compiler-0.9.7-rc1 You will need your Apache/Github username and 2FA token.

Release Step 001a Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_001a_If_Utils and run the following commands: (Push the local changes to develop) git push origin develop (Get the commit id of the last change (The output is considered COMMIT_ID)) git log

Releasing: Finally giving up

Hi all, after 3-4 days of some times 10-16 hours of working on getting the “process” running, I’m finally giving up. We managed to fix a lot of issues in the way the steps were setup and managed to get to step 7 however there’s no getting past that. The problem are the reproducible builds.