Royale Compiler Build Tools Release Step 001 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_001 and run the following commands: git push --set-upstream origin develop git push origin org.apache.royale.compiler-build-tools-0.9.8-rc2 You will need your Apache/Github username and 2FA token.
Royale Compiler Build Tools Release Step 001 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_001 and run the following commands: git push --set-upstream origin develop git push origin org.apache.royale.compiler-build-tools-0.9.8-rc2 You will need your Apache/Github username and 2FA token.
Royale Compiler Build Tools Release Step 001 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_001 and run the following commands: git push --set-upstream origin develop git push origin org.apache.royale.compiler-build-tools-1.2.1-rc1 You will need your Apache/Github username and 2FA token.
Royale Compiler Build Tools Release Step 001 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_001 and run the following commands: git push --set-upstream origin develop git push origin org.apache.royale.compiler-build-tools-1.2.1-rc1 You will need your Apache/Github username and 2FA token.
Re: Royale Compiler Build Tools Release Step 001 Succeeded
Technically you are correct, but then you should go delete the tag. And by
using a different RC number we can compare what he produces against the folder
I produced.
-Alex
On 4/13/20, 12:30 AM, "Carlos Rovira" wrote:
Don't it's needed to increase rc number if it didn't go to a vote. I think
rc versions is just to indicate voters are voting a different version than
before that corrects the problems in the previous rc.
thanks
El dom., 12 abr. 2020 a las 20:13, Alex Harui ()
escribió:
> I think you will have to revert:
>
> 6382da0137fc16df15804df6c7233c3a0307b520
>
> 982933da3c7cc195e437292ac83df713092544b9
>
> 61eb66e2a98ed0592315a4c490b193469f794958
>
> 7a5d97802c15ce25bd5a7b5c791071324e1e9e00
>
> 1266488e1beb98ac1bb794f67f60391ef8e8500a
>
> 1958f8aee2e5fb662dd22861fe2e115d3b85d0b2
>
> And then use 3 as the RC number. I used 2 in my testing and I think
> Carlos might have used 1.
>
> Sorry about that,
> -Alex
>
> From: Yishay Weiss
> Reply-To: "dev@royale.apache.org"
> Date: Sunday, April 12, 2020 at 10:39 AM
> To: "dev@royale.apache.org"
> Subject: RE: Royale Compiler Build Tools Release Step 001 Succeeded
>
> Not sure what you mean. This one?
>
> commit 1266488e1beb98ac1bb794f67f60391ef8e8500a
>
> Author: aharui <
> aha...@apache.org>
>
>Date: Tue Apr 7 07:35:14 2020 +
>
>
>
>
> [maven-release-plugin]
> prepare for next development iteration
>
>
>
>diff --git
> a/compiler-build-tools/pom.xml b/compiler-build-tools/pom.xml
>
>index 76850efe8..62844bcbd 100644
>
>
> --- a/compiler-build-tools/pom.xml
>
> +++
> b/compiler-build-tools/pom.xml
>
> @@ -28,7 +28,7 @@
>
>org.apache.royale.compiler
>compiler-build-tools
> - 1.2.0
> + 1.2.1-SNAPSHOT^M
>maven-plugin
>
>Apache Royale: Build Tools
> @@ -37,7 +37,7 @@
> scm:git:
>
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-compiler.gitdata=02%7C01%7Caharui%40adobe.com%7C607f9cfee3484112438508d7df7c8a66%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637223598305539383sdata=0lfPWN3sn7scWPmKbzHG0rNV%2Bj%2BzeWsdbpMr24Nf73I%3Dreserved=0
> scm:git:
>
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-compiler.gitdata=02%7C01%7Caharui%40adobe.com%7C607f9cfee3484112438508d7df7c8a66%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637223598305539383sdata=0lfPWN3sn7scWPmKbzHG0rNV%2Bj%2BzeWsdbpMr24Nf73I%3Dreserved=0
>
>
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-compilerdata=02%7C01%7Caharui%40adobe.com%7C607f9cfee3484112438508d7df7c8a66%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637223598305539383sdata=Z%2Be4I0lhszwVKR7KKpvZ5yG8sask8xIXrsywUvc17AA%3Dreserved=0
> -org.apache.royale.compiler-build-tools-1.2.0-rc2
> +HEAD^M
>
>
>
> @@ -316,4 +316,4 @@
>
>
>
>
>
-2020-04-07T07:34:27Z
> +^M
>
>
> From: Alex Harui
> Sent: Sunday, April 12, 2020 7:12:26 PM
> To: dev@royale.apache.org
> Subject: Re: Royale Compiler Build Tools Release Step 001 Succeeded
>
> Argh, I forgot to revert the version number change commit. Otherwise the
> release will be 1.2.1. Can you revert and start over? Let me know if you
> need help with the revert.
>
> -Alex
>
> On 4/12/20, 5:19 AM, "Yishay Weiss" wrote:
>
> I used remote dektop. PMC members should see the correct access info
> now.
>
> From: Andrew Wetmore<mailto:cottag...@gmail.com>
> Sent: Sunday, April 12, 2020 1:40 PM
> To: Apache Royale Development<mailto:dev@royale.apache.org>
> Subject: Re: Royale Compiler Build Tools Release Step 001 Succeeded
>
> Oh, thank you! I was too shy to ask that.
>
> On Sun, Apr 12, 2020 at 7:21 AM Yishay Weiss
> wrote:
>
> > Pardon the silly question but how do
Re: Royale Compiler Build Tools Release Step 001 Succeeded
Don't it's needed to increase rc number if it didn't go to a vote. I think rc versions is just to indicate voters are voting a different version than before that corrects the problems in the previous rc. thanks El dom., 12 abr. 2020 a las 20:13, Alex Harui () escribió: > I think you will have to revert: > > 6382da0137fc16df15804df6c7233c3a0307b520 > > 982933da3c7cc195e437292ac83df713092544b9 > > 61eb66e2a98ed0592315a4c490b193469f794958 > > 7a5d97802c15ce25bd5a7b5c791071324e1e9e00 > > 1266488e1beb98ac1bb794f67f60391ef8e8500a > > 1958f8aee2e5fb662dd22861fe2e115d3b85d0b2 > > And then use 3 as the RC number. I used 2 in my testing and I think > Carlos might have used 1. > > Sorry about that, > -Alex > > From: Yishay Weiss > Reply-To: "dev@royale.apache.org" > Date: Sunday, April 12, 2020 at 10:39 AM > To: "dev@royale.apache.org" > Subject: RE: Royale Compiler Build Tools Release Step 001 Succeeded > > Not sure what you mean. This one? > > commit 1266488e1beb98ac1bb794f67f60391ef8e8500a > > Author: aharui < > aha...@apache.org> > >Date: Tue Apr 7 07:35:14 2020 + > > > > > [maven-release-plugin] > prepare for next development iteration > > > >diff --git > a/compiler-build-tools/pom.xml b/compiler-build-tools/pom.xml > >index 76850efe8..62844bcbd 100644 > > > --- a/compiler-build-tools/pom.xml > > +++ > b/compiler-build-tools/pom.xml > > @@ -28,7 +28,7 @@ > >org.apache.royale.compiler >compiler-build-tools > - 1.2.0 > + 1.2.1-SNAPSHOT^M >maven-plugin > >Apache Royale: Build Tools > @@ -37,7 +37,7 @@ > scm:git: > https://gitbox.apache.org/repos/asf/royale-compiler.git > scm:git: > https://gitbox.apache.org/repos/asf/royale-compiler.git > > https://github.com/apache/royale-compiler > -org.apache.royale.compiler-build-tools-1.2.0-rc2 > + HEAD^M > > > > @@ -316,4 +316,4 @@ > > > > > -2020-04-07T07:34:27Z > +^M > > > From: Alex Harui > Sent: Sunday, April 12, 2020 7:12:26 PM > To: dev@royale.apache.org > Subject: Re: Royale Compiler Build Tools Release Step 001 Succeeded > > Argh, I forgot to revert the version number change commit. Otherwise the > release will be 1.2.1. Can you revert and start over? Let me know if you > need help with the revert. > > -Alex > > On 4/12/20, 5:19 AM, "Yishay Weiss" wrote: > > I used remote dektop. PMC members should see the correct access info > now. > > From: Andrew Wetmore<mailto:cottag...@gmail.com> > Sent: Sunday, April 12, 2020 1:40 PM > To: Apache Royale Development<mailto:dev@royale.apache.org> > Subject: Re: Royale Compiler Build Tools Release Step 001 Succeeded > > Oh, thank you! I was too shy to ask that. > > On Sun, Apr 12, 2020 at 7:21 AM Yishay Weiss > wrote: > > > Pardon the silly question but how do I login tp the server and open a > > command prompt? > > > > From: apacheroyal...@gmail.com<mailto:apacheroyal...@gmail.com> > > Sent: Sunday, April 12, 2020 12:45 PM > > To: dev@royale.apache.org<mailto:dev@royale.apache.org> > > Subject: Royale Compiler Build Tools Release Step 001 Succeeded > > > > Log in to the server, open a command prompt, change directory to > > C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_001 > and run > > the following commands: > > git push --set-upstream origin develop > > git push origin org.apache.royale.compiler-build-tools-1.2.0-rc1 > > > > You will need your Apache/Github username and 2FA token. > > > > > > -- > Andrew Wetmore > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.blogspot.com%2Fdata=02%7C01%7Caharui%40adobe.com%7C6ed261ad0ce842bbb61608d7dedbcddc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637222907944479562sdata=OMdWUHO%2FZYabLs5Wzs5MFNXVuDk5Zyk7JL33oxZHiFc%3Dreserved=0 > < > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.blogspot.com%2F=02%7C01%7Caharui%40adobe.com%7C97615f101f73461757ad08d7df0863ae%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637223099447876131=wKKdgOZG5Iz9bb75EPJzWL9XOy1tgaUSL4d5xMxDMzg%3D=0 > > > > > Fro
Royale Compiler Build Tools Release Step 001 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_001 and run the following commands: git push --set-upstream origin develop git push origin org.apache.royale.compiler-build-tools-1.2.0-rc3 You will need your Apache/Github username and 2FA token.
Re: Royale Compiler Build Tools Release Step 001 Succeeded
I think you will have to revert:
6382da0137fc16df15804df6c7233c3a0307b520
982933da3c7cc195e437292ac83df713092544b9
61eb66e2a98ed0592315a4c490b193469f794958
7a5d97802c15ce25bd5a7b5c791071324e1e9e00
1266488e1beb98ac1bb794f67f60391ef8e8500a
1958f8aee2e5fb662dd22861fe2e115d3b85d0b2
And then use 3 as the RC number. I used 2 in my testing and I think Carlos
might have used 1.
Sorry about that,
-Alex
From: Yishay Weiss
Reply-To: "dev@royale.apache.org"
Date: Sunday, April 12, 2020 at 10:39 AM
To: "dev@royale.apache.org"
Subject: RE: Royale Compiler Build Tools Release Step 001 Succeeded
Not sure what you mean. This one?
commit 1266488e1beb98ac1bb794f67f60391ef8e8500a
Author: aharui
Date:
Tue Apr 7 07:35:14 2020 +
[maven-release-plugin] prepare for next development iteration
diff
--git a/compiler-build-tools/pom.xml b/compiler-build-tools/pom.xml
index 76850efe8..62844bcbd 100644
---
a/compiler-build-tools/pom.xml
+++ b/compiler-build-tools/pom.xml
@@ -28,7
+28,7 @@
org.apache.royale.compiler
compiler-build-tools
- 1.2.0
+ 1.2.1-SNAPSHOT^M
maven-plugin
Apache Royale: Build Tools
@@ -37,7 +37,7 @@
scm:git:https://gitbox.apache.org/repos/asf/royale-compiler.git
scm:git:https://gitbox.apache.org/repos/asf/royale-compiler.git
https://github.com/apache/royale-compiler
-org.apache.royale.compiler-build-tools-1.2.0-rc2
+HEAD^M
@@ -316,4 +316,4 @@
-2020-04-07T07:34:27Z
+^M
From: Alex Harui
Sent: Sunday, April 12, 2020 7:12:26 PM
To: dev@royale.apache.org
Subject: Re: Royale Compiler Build Tools Release Step 001 Succeeded
Argh, I forgot to revert the version number change commit. Otherwise the
release will be 1.2.1. Can you revert and start over? Let me know if you need
help with the revert.
-Alex
On 4/12/20, 5:19 AM, "Yishay Weiss" wrote:
I used remote dektop. PMC members should see the correct access info now.
From: Andrew Wetmore<mailto:cottag...@gmail.com>
Sent: Sunday, April 12, 2020 1:40 PM
To: Apache Royale Development<mailto:dev@royale.apache.org>
Subject: Re: Royale Compiler Build Tools Release Step 001 Succeeded
Oh, thank you! I was too shy to ask that.
On Sun, Apr 12, 2020 at 7:21 AM Yishay Weiss wrote:
> Pardon the silly question but how do I login tp the server and open a
> command prompt?
>
> From: apacheroyal...@gmail.com<mailto:apacheroyal...@gmail.com>
> Sent: Sunday, April 12, 2020 12:45 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: Royale Compiler Build Tools Release Step 001 Succeeded
>
> Log in to the server, open a command prompt, change directory to
> C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_001 and run
> the following commands:
> git push --set-upstream origin develop
> git push origin org.apache.royale.compiler-build-tools-1.2.0-rc1
>
> You will need your Apache/Github username and 2FA token.
>
>
--
Andrew Wetmore
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.blogspot.com%2Fdata=02%7C01%7Caharui%40adobe.com%7C6ed261ad0ce842bbb61608d7dedbcddc%7Cfa7b1b5a7b34438794aed2c178decee1%7
RE: Royale Compiler Build Tools Release Step 001 Succeeded
Not sure what you mean. This one?
commit 1266488e1beb98ac1bb794f67f60391ef8e8500a
Author: aharui
Date:
Tue Apr 7 07:35:14 2020 +
[maven-release-plugin] prepare for next development iteration
diff
--git a/compiler-build-tools/pom.xml b/compiler-build-tools/pom.xml
index 76850efe8..62844bcbd 100644
---
a/compiler-build-tools/pom.xml
+++ b/compiler-build-tools/pom.xml
@@ -28,7
+28,7 @@
org.apache.royale.compiler
compiler-build-tools
- 1.2.0
+ 1.2.1-SNAPSHOT^M
maven-plugin
Apache Royale: Build Tools
@@ -37,7 +37,7 @@
scm:git:https://gitbox.apache.org/repos/asf/royale-compiler.git
scm:git:https://gitbox.apache.org/repos/asf/royale-compiler.git
https://github.com/apache/royale-compiler
-org.apache.royale.compiler-build-tools-1.2.0-rc2
+HEAD^M
@@ -316,4 +316,4 @@
-2020-04-07T07:34:27Z
+^M
From: Alex Harui
Sent: Sunday, April 12, 2020 7:12:26 PM
To: dev@royale.apache.org
Subject: Re: Royale Compiler Build Tools Release Step 001 Succeeded
Argh, I forgot to revert the version number change commit. Otherwise the
release will be 1.2.1. Can you revert and start over? Let me know if you need
help with the revert.
-Alex
On 4/12/20, 5:19 AM, "Yishay Weiss" wrote:
I used remote dektop. PMC members should see the correct access info now.
From: Andrew Wetmore<mailto:cottag...@gmail.com>
Sent: Sunday, April 12, 2020 1:40 PM
To: Apache Royale Development<mailto:dev@royale.apache.org>
Subject: Re: Royale Compiler Build Tools Release Step 001 Succeeded
Oh, thank you! I was too shy to ask that.
On Sun, Apr 12, 2020 at 7:21 AM Yishay Weiss wrote:
> Pardon the silly question but how do I login tp the server and open a
> command prompt?
>
> From: apacheroyal...@gmail.com<mailto:apacheroyal...@gmail.com>
> Sent: Sunday, April 12, 2020 12:45 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: Royale Compiler Build Tools Release Step 001 Succeeded
>
> Log in to the server, open a command prompt, change directory to
> C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_001 and run
> the following commands:
> git push --set-upstream origin develop
> git push origin org.apache.royale.compiler-build-tools-1.2.0-rc1
>
> You will need your Apache/Github username and 2FA token.
>
>
--
Andrew Wetmore
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.blogspot.com%2Fdata=02%7C01%7Caharui%40adobe.com%7C6ed261ad0ce842bbb61608d7dedbcddc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637222907944479562sdata=OMdWUHO%2FZYabLs5Wzs5MFNXVuDk5Zyk7JL33oxZHiFc%3Dreserved=0
From: Alex Harui<mailto:aha...@adobe.com.INVALID>
Sent: Sunday, April 12, 2020 7:12 PM
Subject: Re: Royale Compiler Build Tools Release Step 001 Succeeded
Argh, I forgot to revert the version number change commit. Otherwise the
release will be 1.2.1. Can you revert and start over? Let me know if you need
help with the revert.
-Alex
On 4/12/20, 5:19 AM, "Yishay Weiss" wrote:
I used remote dektop. PMC members should see the correct access info now.
From: Andrew Wetmore<mailto:cottag...@gmail.com>
Sent: Sun
Re: Royale Compiler Build Tools Release Step 001 Succeeded
Argh, I forgot to revert the version number change commit. Otherwise the
release will be 1.2.1. Can you revert and start over? Let me know if you need
help with the revert.
-Alex
On 4/12/20, 5:19 AM, "Yishay Weiss" wrote:
I used remote dektop. PMC members should see the correct access info now.
From: Andrew Wetmore<mailto:cottag...@gmail.com>
Sent: Sunday, April 12, 2020 1:40 PM
To: Apache Royale Development<mailto:dev@royale.apache.org>
Subject: Re: Royale Compiler Build Tools Release Step 001 Succeeded
Oh, thank you! I was too shy to ask that.
On Sun, Apr 12, 2020 at 7:21 AM Yishay Weiss wrote:
> Pardon the silly question but how do I login tp the server and open a
> command prompt?
>
> From: apacheroyal...@gmail.com<mailto:apacheroyal...@gmail.com>
> Sent: Sunday, April 12, 2020 12:45 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: Royale Compiler Build Tools Release Step 001 Succeeded
>
> Log in to the server, open a command prompt, change directory to
> C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_001 and run
> the following commands:
> git push --set-upstream origin develop
> git push origin org.apache.royale.compiler-build-tools-1.2.0-rc1
>
> You will need your Apache/Github username and 2FA token.
>
>
--
Andrew Wetmore
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.blogspot.com%2Fdata=02%7C01%7Caharui%40adobe.com%7C6ed261ad0ce842bbb61608d7dedbcddc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637222907944479562sdata=OMdWUHO%2FZYabLs5Wzs5MFNXVuDk5Zyk7JL33oxZHiFc%3Dreserved=0
RE: Royale Compiler Build Tools Release Step 001 Succeeded
I used remote dektop. PMC members should see the correct access info now. From: Andrew Wetmore<mailto:cottag...@gmail.com> Sent: Sunday, April 12, 2020 1:40 PM To: Apache Royale Development<mailto:dev@royale.apache.org> Subject: Re: Royale Compiler Build Tools Release Step 001 Succeeded Oh, thank you! I was too shy to ask that. On Sun, Apr 12, 2020 at 7:21 AM Yishay Weiss wrote: > Pardon the silly question but how do I login tp the server and open a > command prompt? > > From: apacheroyal...@gmail.com<mailto:apacheroyal...@gmail.com> > Sent: Sunday, April 12, 2020 12:45 PM > To: dev@royale.apache.org<mailto:dev@royale.apache.org> > Subject: Royale Compiler Build Tools Release Step 001 Succeeded > > Log in to the server, open a command prompt, change directory to > C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_001 and run > the following commands: > git push --set-upstream origin develop > git push origin org.apache.royale.compiler-build-tools-1.2.0-rc1 > > You will need your Apache/Github username and 2FA token. > > -- Andrew Wetmore http://cottage14.blogspot.com/
Re: Royale Compiler Build Tools Release Step 001 Succeeded
Oh, thank you! I was too shy to ask that. On Sun, Apr 12, 2020 at 7:21 AM Yishay Weiss wrote: > Pardon the silly question but how do I login tp the server and open a > command prompt? > > From: apacheroyal...@gmail.com<mailto:apacheroyal...@gmail.com> > Sent: Sunday, April 12, 2020 12:45 PM > To: dev@royale.apache.org<mailto:dev@royale.apache.org> > Subject: Royale Compiler Build Tools Release Step 001 Succeeded > > Log in to the server, open a command prompt, change directory to > C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_001 and run > the following commands: > git push --set-upstream origin develop > git push origin org.apache.royale.compiler-build-tools-1.2.0-rc1 > > You will need your Apache/Github username and 2FA token. > > -- Andrew Wetmore http://cottage14.blogspot.com/
RE: Royale Compiler Build Tools Release Step 001 Succeeded
Pardon the silly question but how do I login tp the server and open a command prompt? From: apacheroyal...@gmail.com<mailto:apacheroyal...@gmail.com> Sent: Sunday, April 12, 2020 12:45 PM To: dev@royale.apache.org<mailto:dev@royale.apache.org> Subject: Royale Compiler Build Tools Release Step 001 Succeeded Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_001 and run the following commands: git push --set-upstream origin develop git push origin org.apache.royale.compiler-build-tools-1.2.0-rc1 You will need your Apache/Github username and 2FA token.
Royale Compiler Build Tools Release Step 001 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_001 and run the following commands: git push --set-upstream origin develop git push origin org.apache.royale.compiler-build-tools-1.2.0-rc1 You will need your Apache/Github username and 2FA token.
Royale Compiler Build Tools Release Step 001 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_001 and run the following commands: git push --set-upstream origin develop git push origin org.apache.royale.compiler-build-tools-1.2.0-rc2 You will need your Apache/Github username and 2FA token.
Royale Compiler Build Tools Release Step 001 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_001 and run the following commands: git push --set-upstream origin develop git push origin org.apache.royale.compiler-build-tools-1.2.0-rc2 You will need your Apache/Github username and 2FA token.
Royale Compiler Build Tools Release Step 001 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_001 and run the following commands: git push --set-upstream origin develop git push origin org.apache.royale.compiler-build-tools-1.2.0-rc2 You will need your Apache/Github username and 2FA token.
Royale Compiler Build Tools Release Step 001 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_001 and run the following commands: git push --set-upstream origin develop git push origin org.apache.royale.compiler-build-tools-1.2.0-rc2 You will need your Apache/Github username and 2FA token.
Royale Compiler Build Tools Release Step 001 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_001 and run the following commands: git push git push origin org.apache.royale.compiler-build-tools-1.2.0-rc1 You will need your Apache/Github username and 2FA token.
