Unfortunately I don't know what is happening but signing trough script hang for me. Stopped working. :(
ant -f releasesteps.xml Release_Step_003_Sign -Drelease.version=0.9.6 Buildfile: d:\Work\royale-sources\royale-compiler\releasesteps.xml get-artifact-folder: [input] Enter the temporary folder to store the downloaded artifacts: royale096 Release_Step_003_Sign: sign-file: pt., 16 sie 2019 o 09:21 Piotr Zarzycki <piotrzarzyck...@gmail.com> napisał(a): > With "../../" or without ? I just run script with -DskiptTests="true" and > it passes, but failed on "compare-src-zips" - It looks like it is also > problem with paths. :( > > pt., 16 sie 2019 o 09:15 Alex Harui <aha...@adobe.com.invalid> napisał(a): > >> I would also need to see the output of the other two steps >> (Release_Step_003 and Release_Step_003_Sign) >> >> Thanks, >> -Alex >> >> On 8/15/19, 11:14 PM, "Piotr Zarzycki" <piotrzarzyck...@gmail.com> >> wrote: >> >> This console output is here [1], but it is version where script >> failing, >> cause there wasn't "../../". Let me know if it's enough actually. >> >> [1] >> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fzvxoi&data=02%7C01%7Caharui%40adobe.com%7Cfc8fed043b39436043f308d72210ef3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637015328440648351&sdata=VypdtAw9z%2Bs52VGupIzjXD5qHSZZWzw%2BrahQSCIa63o%3D&reserved=0 >> >> czw., 15 sie 2019 o 22:37 Alex Harui <aha...@adobe.com.invalid> >> napisał(a): >> >> > That's a possibility. I only used absolute paths. >> > >> > Piotr, it would nice to see the Windows console output including >> the paths >> > you gave to help make this process more robust. >> > >> > -Alex >> > >> > On 8/15/19, 1:21 PM, "Josh Tynjala" <joshtynj...@bowlerhat.dev> >> wrote: >> > >> > If it started working correctly after changing the path to >> include >> > ../../, >> > perhaps ${artifactfolder} is being set to a relative path, but >> the >> > script >> > expects the path to be absolute. I'm not familiar with the >> release >> > steps >> > yet, so I'm just guessing, but does that make sense? >> > >> > -- >> > Josh Tynjala >> > Bowler Hat LLC < >> > >> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.dev&data=02%7C01%7Caharui%40adobe.com%7Cfc8fed043b39436043f308d72210ef3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637015328440648351&sdata=hebWRJTdRMai7LejpO5aipHzmA9Qa9hBXXv0vfwrO78%3D&reserved=0 >> > > >> > >> > >> > On Wed, Aug 14, 2019 at 9:23 AM Alex Harui >> <aha...@adobe.com.invalid> >> > wrote: >> > >> > > Can you explain why that would be the right change? Doesn't >> make >> > sense to >> > > me. >> > > >> > > On 8/14/19, 3:36 AM, "Piotr Zarzycki" < >> piotrzarzyck...@gmail.com> >> > wrote: >> > > >> > > So far so good. I did tweak the script and was able to >> upload >> > > artifacts. I >> > > have changed in each script: >> > > Line from: >> > > >> > > <arg value="-Dwagon.fromDir=${artifactfolder} >> > > /artifacts/archive/target/checkout/release-dir" /> >> > > To >> > > <arg value="-Dwagon.fromDir=../../${artifactfolder} >> > > /artifacts/archive/target/checkout/release-dir" /> >> > > >> > > The very last thing was close repository, so I got some >> errors >> > you can >> > > check here by logging your Apache handle [1] related to >> > RoyaleUnit [2]. >> > > >> > > Missing Signature: >> > > >> > > >> > >> '/org/apache/royale/compiler/royaleunit-ant-tasks/0.9.6/royaleunit-ant-tasks-0.9.6.pom.asc' >> > > does not exist for 'royaleunit-ant-tasks-0.9.6.pom'. >> > > >> > > I will try to figure out what has happened, but if >> someone has >> > any >> > > clue to >> > > that let me know. >> > > >> > > [1] >> > > >> > >> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositories&data=02%7C01%7Caharui%40adobe.com%7Cfc8fed043b39436043f308d72210ef3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637015328440648351&sdata=8j%2B4do2p0hAp2Don5Y6tpvimJO%2FfErSxTXkKEjDD45w%3D&reserved=0 >> > > [2] >> > > >> > >> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpasteboard.co%2FIsDKVTe.png&data=02%7C01%7Caharui%40adobe.com%7Cfc8fed043b39436043f308d72210ef3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637015328440658346&sdata=xlKUmrK6QvJi27gghwjC7hq22bIPWE53dejwiLCErZQ%3D&reserved=0 >> > > >> > > Thanks, >> > > Piotr >> > > >> > > >> > > śr., 14 sie 2019 o 10:58 Carlos Rovira < >> carlosrov...@apache.org> >> > > napisał(a): >> > > >> > > > Hi Alex, >> > > > >> > > > El lun., 12 ago. 2019 a las 19:30, Alex Harui >> > > (<aha...@adobe.com.invalid>) >> > > > escribió: >> > > > >> > > > > Also, the other committers should be aware that an RC >> is >> > being >> > > created >> > > > > because they see the emails being sent by the CI >> server and >> > ask >> > > the RM to >> > > > > agree to accept a commit to the release branch >> instead of the >> > > develop >> > > > > branch. >> > > > >> > > > >> > > > AFAIK, we should always commit to dev branch and not to >> release >> > > branch. >> > > > Releases are cut from develop. Only hot-fixes use to be >> > branches >> > > that have >> > > > commits that fix something important in the release and >> then >> > use to >> > > be >> > > > merged back to develop and master. Making commits to >> release >> > > branches could >> > > > bring some confusion and problems. >> > > > >> > > > At least from is what I always learnt and used [1] >> > > > >> > > > [1] >> > > >> > >> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnvie.com%2Fposts%2Fa-successful-git-branching-model%2F&data=02%7C01%7Caharui%40adobe.com%7Cfc8fed043b39436043f308d72210ef3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637015328440658346&sdata=4JZc3LZBS2WgJ0YnPthnVXw31EaIHXnyjLUwButYbB0%3D&reserved=0 >> > > > >> > > > -- >> > > > Carlos Rovira >> > > > >> > > >> > >> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cfc8fed043b39436043f308d72210ef3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637015328440658346&sdata=r%2FRtASOGeG9R917H2qa%2BYuALV%2BEq1AQUAaCSGRIlMSU%3D&reserved=0 >> > > > >> > > >> > > >> > > -- >> > > >> > > Piotr Zarzycki >> > > >> > > Patreon: * >> > > >> > >> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cfc8fed043b39436043f308d72210ef3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637015328440658346&sdata=z4uxNCt9czce82lh2ZYmtpKAHSn52qTKGUQ09ONYN8I%3D&reserved=0 >> > > < >> > > >> > >> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cfc8fed043b39436043f308d72210ef3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637015328440658346&sdata=z4uxNCt9czce82lh2ZYmtpKAHSn52qTKGUQ09ONYN8I%3D&reserved=0 >> > > >* >> > > >> > > >> > > >> > >> > >> > >> >> -- >> >> Piotr Zarzycki >> >> Patreon: * >> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cfc8fed043b39436043f308d72210ef3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637015328440658346&sdata=z4uxNCt9czce82lh2ZYmtpKAHSn52qTKGUQ09ONYN8I%3D&reserved=0 >> < >> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cfc8fed043b39436043f308d72210ef3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637015328440658346&sdata=z4uxNCt9czce82lh2ZYmtpKAHSn52qTKGUQ09ONYN8I%3D&reserved=0 >> >* >> >> >> > > -- > > Piotr Zarzycki > > Patreon: *https://www.patreon.com/piotrzarzycki > <https://www.patreon.com/piotrzarzycki>* > -- Piotr Zarzycki Patreon: *https://www.patreon.com/piotrzarzycki <https://www.patreon.com/piotrzarzycki>*