Those are the steps from the script which need to be done still: 1) <antcall target="update.versions" /> 2) <antcall target="merge_rc_to_develop" /> 3) <antcall target="release.maven.staging.repo" />
Number #1 is failing. czw., 3 paź 2019 o 10:41 Piotr Zarzycki <[email protected]> napisał(a): > It looks like we already have: > 1) Successfully published npm: > https://www.npmjs.com/package/@apache-royale/royale-js > 2) Successfully published which can be updated on the website: > https://www.apache.org/dyn/closer.lua/royale/0.9.6/binaries/apache-royale-0.9.6-bin-js.tar.gz > > Thanks, > Piotr > > czw., 3 paź 2019 o 10:33 Piotr Zarzycki <[email protected]> > napisał(a): > >> I have used npm password from private and went trough publishing npm and >> it's failed on next step update.version with the same error. Here you go >> full log [1]. >> >> What will happen if I run publish npm stuff again ? I can omit that part >> in the next attempt. >> >> Om can you check whether my npm publish stuff went ok ? >> >> [1] https://paste.apache.org/yl06d >> >> Thanks, >> Piotr >> >> Thanks, >> Piotr >> >> śr., 2 paź 2019 o 18:40 Alex Harui <[email protected]> napisał(a): >> >>> Responses inline... >>> >>> On 10/2/19, 1:37 AM, "Piotr Zarzycki" <[email protected]> >>> wrote: >>> >>> Just to understand something. releasecandidate script is using tag >>> instead >>> release branch to whole operation of increase version ? >>> >>> No, the "get_head_of_rc_branches" target should get you the head. >>> >>> > Hi, >>> > >>> > I just tried releasecandidate script. It contains following steps. >>> > >>> > <antcall target="release.tag" /> >>> > <!-- this is intended to merge the tag to master because >>> it should >>> > have the right versions in it --> >>> > <antcall target="merge_rc_to_master" /> >>> > <antcall target="get_head_of_rc_branches" /> >>> > <antcall target="release.npm" /> >>> > <antcall target="update.versions" /> >>> > <antcall target="merge_rc_to_develop" /> >>> > <antcall target="release.maven.staging.repo" /> >>> > >>> > One step previous was move in svn binaries from dev folder to >>> release - I >>> > omit that cause I did it already manually. Launching following >>> steps I >>> > reached release.npm - Which requires login and password to npm - I >>> > omitted that as well. Next was update.versions and it failed with >>> following >>> > stack trace [1] >>> > >>> >>> The login and password is available in the private@ archives. >>> >>> >>> > In mentioned lines in the stacktrace I have: >>> > >>> > Line 1088: >>> > <antcall target="update.versions" /> >>> > >>> > Line 1216: >>> > <exec executable="${git}" dir="${compiler}" failonerror="true" > >>> > <arg value="commit" /> >>> > <arg value="-m" /> >>> > <arg value="update version to ${new.release.version}" >>> /> >>> > </exec> >>> > >>> > [1] >>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F15biu&data=02%7C01%7Caharui%40adobe.com%7Ca6fd586ab1f044a4b2c408d74713bf65%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056022453516542&sdata=usDOkcnLx4HhZJSYsMde5pnvgQMDyKLSIKeOccmCJkc%3D&reserved=0 >>> >>> You did not post the whole log, so it is possible you missed a step. >>> There is almost no way there shouldn't be changes and the head should not >>> be detached. >>> >>> -Alex >>> >>> >> >> -- >> >> 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>* > -- Piotr Zarzycki Patreon: *https://www.patreon.com/piotrzarzycki <https://www.patreon.com/piotrzarzycki>*
