Re: Discuss of release steps preparation

2019-08-13 Thread Alex Harui
I'm not sure you should skip the uploading. I'm not sure where typedefs and asjs will get its compiler artifacts if they haven't been uploaded. The output says that it is looking in the following folder for artifacts:

Re: Discuss of release steps preparation

2019-08-13 Thread Piotr Zarzycki
Sorry about that. I was going trough the steps but I have left steps for signing artifacts and uploading them at the end. When for all 3 repos I had build, comparison and sign in works I tried upload it using provided instructions. If you are not seeing any suspicious in that log I need to

Re: Discuss of release steps preparation

2019-08-13 Thread Alex Harui
There are a lot of intelligent things the Maven release plugin does. One is to remove the "SNAPSHOT" from the dependencies in the poms. So when builds are happening in the releases, it should not be using the SNAPSHOT version but rather, a release version from somewhere. It might look in

Re: Discuss of release steps preparation

2019-08-13 Thread Piotr Zarzycki
Wow that is good point. I think if build of asjs is being done by Maven it will be taken from 0.9.6-SNAPSHOT I think so. It definitely won't use staged compiler - You need to point such stuff explicitly using settings.xml On Tue, Aug 13, 2019, 10:20 PM Alex Harui wrote: > I'm not sure you

Jenkins build is back to normal : royale-asjs_jsonly #3383

2019-08-13 Thread Apache Royale CI Server
See

Build failed in Jenkins: royale-asjs_MXTests #1051

2019-08-13 Thread Apache Royale CI Server
See -- [...truncated 983.27 KB...] [mxmlc] scanning for overrides: ObjectUtil [mxmlc] scanning for overrides: SolidBorderUtil [mxmlc] scanning

Re: Discuss of release steps preparation

2019-08-13 Thread Alex Harui
I'm not sure what warnings you are referring to. If you look at releasesteps.xml, you can see that it is using Maven's wagon:upload goal to upload from a particular folder. Are there jars in that folder (or its subfolders)? Examine the output of the previous Ant release steps for step 003 to

Release Step 010 Succeeded

2019-08-13 Thread Apache Royale CI Server
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_010 and run the following commands: git push git push origin org.apache.royale.framework-0.9.6-rc1 You will need your Apache/Github username and 2FA token.

Release Step 011 Succeeded

2019-08-13 Thread Apache Royale CI Server
>From the royale-asjs repo: 1. Run ant -f releasesteps.xml Release_Step_011 -Drelease.version=0.9.6 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 -f releasesteps.xml

Build failed in Jenkins: royale-asjs_MXTests #1049

2019-08-13 Thread Apache Royale CI Server
See Changes: [aharui] need ICollectionView support for selected item in ADG. Fixes #442 [aharui] changes to support ADG column visibility. Fixes #446

Re: Discuss of release steps preparation

2019-08-13 Thread Piotr Zarzycki
Hi Alex, Thanks for information. I went today trough the steps again. I reached point where I'm trying to upload artifacts, but script keep saying me that there is nothing to upload. Is it because of those warnings at the beginnings ? [1] [1] https://paste.apache.org/zvxoi Thanks, Piotr pon.,

Jenkins build is back to normal : royale-typedefs #1537

2019-08-13 Thread Apache Royale CI Server
See

Build failed in Jenkins: royale-asjs_jsonly #3382

2019-08-13 Thread Apache Royale CI Server
See -- [...truncated 159.66 KB...] [delete] Deleting directory C:\Program Files (x86)\Jenkins\workspace\royale-compiler\compiler-externc\target clean:

Build failed in Jenkins: royale-asjs_MXTests #1050

2019-08-13 Thread Apache Royale CI Server
: Apache Ant(TM) version 1.9.9 compiled on February 2 2017 Ant Java Version: 1.8 thirdparty-downloads: thirdparty-downloads: create-description: [echo] build.number is 20190813 js-output-royale-description: swf-js-output-royale-description: create-config: playerglobal-setswfversion: