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.6
git push -u origin release/0.9.6
You will need your Apache/Github username and 2FA token.
Hi Alex,
Thanks it's working. I'm moving forward with that stuff let's see how far I
go with it.
Piotr
pt., 19 lip 2019 o 05:49 Alex Harui napisał(a):
> I am using the token generated this way:
>
> https://help.github.com/en/articles/creating-a-personal-access-token-for-the-command-line
>
> Th
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:
git push
You will need your Apache/Github username and 2FA token.
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.6-rc1
You will need your Apache/Github username and 2FA token.
Continue on to Release Step 003
>From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools), Run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6
Otherwise, Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.6
This will d
So far so good. I'm on a step 3, where I need build artifacts on my sight
and compare them with what Jenkins produce.
I will get back to that probably on Monday.
On Fri, Jul 19, 2019, 1:40 PM Piotr Zarzycki
wrote:
> Hi Alex,
>
> Thanks it's working. I'm moving forward with that stuff let's see
Please update the wiki in a way that the next person will know which 2FA token
to use.
Thanks,
-Alex
On 7/19/19, 9:08 AM, "Piotr Zarzycki" wrote:
So far so good. I'm on a step 3, where I need build artifacts on my sight
and compare them with what Jenkins produce.
I will get b
