Alex just said we do. Apparently there were changes after the last release related to reproducible builds.
> On Jul 13, 2020, at 10:32 AM, Carlos Rovira <[email protected]> wrote: > > Hi Harbs, > also I don't think we require a Tools release this time. There's no change > in that part this time, so Tools can be skipped and just release compiler, > typedefs and asjs. In latest release we did a Tools release since there was > changes, and was good to test the process with that variant, but I guess no > more changes will be done to jburg and tools in long time, or should be > very rare. > > > El lun., 13 jul. 2020 a las 9:13, Harbs (<[email protected]>) escribió: > >> It’s probably that I didn’t roll back after trying to start the Royale >> release. I just reverted those changes and I’ll start this again... >> >>> On Jul 13, 2020, at 9:37 AM, Alex Harui <[email protected]> >> wrote: >>> >>> Maybe, but IIRC, it shouldn't be uploading to snapshots, it should be >> uploading to releases/staging. Look at the console output from the last >> known good build (#12). There may be something wrong with the tag. It may >> not have tagged the poms with the SNAPSHOT removed. >>> >>> HTH, >>> -Alex >>> >>> On 7/12/20, 11:27 PM, "Harbs" <[email protected]> wrote: >>> >>> I’m guessing it’s a permissions problem transferring to >> repository.a.o: >>> >>> [INFO] [ERROR] Failed to execute goal >> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) >> on project compiler-build-tools: Failed to deploy artifacts: Could not >> transfer artifact >> org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.055905-2 >> from/to apache.snapshots.https ( >> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7Cd35ca17c65d84c08f0cb08d826f5c7ea%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302184343571806&sdata=m1a99DxFrJIbyODBNguOcMRvXZKjcRBgs%2Ft%2FOtegZu8%3D&reserved=0 >> < >> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7Cd35ca17c65d84c08f0cb08d826f5c7ea%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302184343581803&sdata=jckuOGNwMWGJEqV9qrSXg4irz%2Bcmrm2GYwX5g9hFR7M%3D&reserved=0>): >> Failed to transfer file >> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.055905-2.jar&data=02%7C01%7Caharui%40adobe.com%7Cd35ca17c65d84c08f0cb08d826f5c7ea%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302184343581803&sdata=k8x%2BRzDjc1MthEACKBj0D7k3IKncHS2U%2BgxWRCKnNd8%3D&reserved=0 >> < >> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.055905-2.jar&data=02%7C01%7Caharui%40adobe.com%7Cd35ca17c65d84c08f0cb08d826f5c7ea%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302184343581803&sdata=k8x%2BRzDjc1MthEACKBj0D7k3IKncHS2U%2BgxWRCKnNd8%3D&reserved=0> >> with status code 401 -> [Help 1] >>> >>> Any ideas on how to fix? >>> >>>> On Jul 13, 2020, at 9:23 AM, Harbs <[email protected]> wrote: >>>> >>>> Can any Maven experts explain why this is failing? >>>> >> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Compiler_Build_Tools_Release_Step_002%2F13%2Fconsole&data=02%7C01%7Caharui%40adobe.com%7Cd35ca17c65d84c08f0cb08d826f5c7ea%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302184343581803&sdata=wplPRX1ZJ60KT%2FUVOsi8rWzcBoqe%2FJK74B2GrU7ZmKs%3D&reserved=0 >>>> >>>> FWIW, there’s this warning which should probably be fixed… >>>> >>>> [WARNING] Some problems were encountered while building the effective >> model for >> org.apache.royale.compiler:compiler-build-tools:maven-plugin:1.2.1-SNAPSHOT >>>> [WARNING] 'build.pluginManagement.plugins.plugin.(groupId:artifactId)' >> must be unique but found duplicate declaration of plugin >> org.apache.maven.plugins:maven-javadoc-plugin @ line 129, column 17 >>>> [WARNING] 'build.plugins.plugin.version' for >> com.theoryinpractise:reproducible-maven-plugin is missing. @ line 204, >> column 19 >>>> [WARNING] >>>> [WARNING] It is highly recommended to fix these problems because they >> threaten the stability of your build. >>>> [WARNING] >>>> [WARNING] For this reason, future Maven versions might no longer >> support building such malformed projects. >>>> >>>>> On Jul 13, 2020, at 8:59 AM, [email protected] wrote: >>>>> >>>>> Royale_Compiler_Build_Tools_Release_Step_002 - Build # 13 - Failure: >>>>> >>>>> Check console output at >> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Compiler_Build_Tools_Release_Step_002%2F13%2F&data=02%7C01%7Caharui%40adobe.com%7Cd35ca17c65d84c08f0cb08d826f5c7ea%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302184343581803&sdata=uAgptm0JU9X%2FAQiS3rKo%2FIYeoIoucD83JR9gJFmG%2B%2FM%3D&reserved=0 >> to view the results. >>>> >>> >>> >>> >> >> > > -- > Carlos Rovira > http://about.me/carlosrovira
