Release Step 001 Succeeded
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.9 git push -u origin release/0.9.9 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.9 git push -u origin release/0.9.9 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.9 git push -u origin release/0.9.9 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.9 git push -u origin release/0.9.9 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.9 git push -u origin release/0.9.9 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.9 git push -u origin release/0.9.9 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.8 git push -u origin release/0.9.8 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.8 git push -u origin release/0.9.8 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.8 git push -u origin release/0.9.8 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.8 git push -u origin release/0.9.8 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.8 git push -u origin release/0.9.8 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.8 git push -u origin release/0.9.8 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-0.9.8-rc2 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.8 git push -u origin release/0.9.8 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.
Release Step 001 Succeeded
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.8 git push -u origin release/0.9.8 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
Release Step 001 Succeeded
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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.7 git push -u origin release/0.9.7 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-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
Release Step 001 Succeeded
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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.
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.
Release Step 001 Succeeded
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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.7 git push -u origin release/0.9.7 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.
Release Step 001 Succeeded
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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.
Re: Release Step 001 Succeeded
It's not a dependency, it is the version of a build tool/plugin. -Alex On 11/24/19, 10:33 AM, "Carlos Rovira" wrote: Hi Alex, don't know how we can release with a SNAPSHOT in dependencies, I think it was impossible to do that from my experience. El dom., 24 nov. 2019 a las 17:07, Alex Harui () escribió: > We released 0.9.6 using snapshot. I was told they would not look at my > patch unless I added tests. I have not had time to figure out their test > system. You are welcome to do that. > > Get Outlook for Android<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fghei36data=02%7C01%7Caharui%40adobe.com%7Cc738283153c54cea733108d7710cd59a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637102172246506795sdata=ZBoImmXo1qkWpESSL1LhvU3TN0AwzBorYJzMkYbB%2FfA%3Dreserved=0> > > > From: Carlos Rovira > Sent: Sunday, November 24, 2019 3:00:43 AM > To: dev@royale.apache.org > Subject: Re: Release Step 001 Succeeded > > Hi Alex, > > If we rely on SNAPSHOT, then we'll not be able to release right? > If the patch show in the ticket (SCM-921) solved the issue, why don't > report it? > They could bring a release working version that allow us to release right? > Don't know how it worked in the past with a SNAPSHOT version since maven > should not allow to release with SNAPSHOT included. > Another issue is using our own patched version seems to me something that > could bring problems since is something out the eye of everybody but the > person(s) that knows about this particularity. > thanks > > El dom., 24 nov. 2019 a las 6:24, Alex Harui () > escribió: > > > I manually installed the other 1.11.2-SNAPSHOT maven artifacts in the > > local maven repository on the CI server. > > > > -Alex > > > > On 11/23/19, 1:50 AM, "Carlos Rovira" wrote: > > > > Thanks Alex, > > I finally get the RS#1 finally complete. > > About dependencies you mentioned, I didn't see any commit from you to > > repo > > to modify a pom, are you referring to some external dependencies, > > maybe in > > the windows machine? > > Going with RS#2 > > Thanks! > > > > El vie., 22 nov. 2019 a las 20:56, Alex Harui > > () > > escribió: > > > > > OK, looks l forgot to copy some dependencies. I just added some > > more. > > > Try it again and see if it works or there are new errors. > > > > > > On 11/22/19, 11:41 AM, "Carlos Rovira" > > wrote: > > > > > > Hi Alex, > > > > > > I updated the pom to exactly the same we had for JGIT, with the > > > 1.11.2-SNAPSHOT. But is failing [1] > > > > > > [WARNING] The POM for > > > org.apache.maven.scm:maven-scm-api:jar:1.11.2-SNAPSHOT is > > missing, no > > > dependency information available > > > > > > > > > [ERROR] Failed to execute goal > > > org.apache.maven.plugins:maven-release-plugin:2.5.3:branch > > > (default-cli) on project royale-compiler-parent: Execution > > default-cli > > > of goal > > org.apache.maven.plugins:maven-release-plugin:2.5.3:branch > > > failed: Plugin > > org.apache.maven.plugins:maven-release-plugin:2.5.3 or > > > one of its dependencies could not be resolved: Failed to > collect > > > dependencies at > > > org.apache.maven.plugins:maven-release-plugin:jar:2.5.3 -> > > > > org.apache.maven.scm:maven-scm-provider-jgit:jar:1.11.2-SNAPSHOT: > > > Failed to read artifact descriptor for > > > > org.apache.maven.scm:maven-scm-provider-jgit:jar:1.11.2-SNAPSHOT: > > > Failure to find > > > > org.apache.maven.scm:maven-scm-providers-git:pom:1.11.2-SNAPSHOT > > in > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Frepository.apache.org%2Fsnapshotsdata=02%7C01%7Caharui%40adobe.com%7Cc738283153c54cea733108d7710cd59a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637102172246506795sdata=94XBL%2FogKj%2BuJGoc8qr%
Re: Release Step 001 Succeeded
Hi Alex, don't know how we can release with a SNAPSHOT in dependencies, I think it was impossible to do that from my experience. El dom., 24 nov. 2019 a las 17:07, Alex Harui () escribió: > We released 0.9.6 using snapshot. I was told they would not look at my > patch unless I added tests. I have not had time to figure out their test > system. You are welcome to do that. > > Get Outlook for Android<https://aka.ms/ghei36> > > > From: Carlos Rovira > Sent: Sunday, November 24, 2019 3:00:43 AM > To: dev@royale.apache.org > Subject: Re: Release Step 001 Succeeded > > Hi Alex, > > If we rely on SNAPSHOT, then we'll not be able to release right? > If the patch show in the ticket (SCM-921) solved the issue, why don't > report it? > They could bring a release working version that allow us to release right? > Don't know how it worked in the past with a SNAPSHOT version since maven > should not allow to release with SNAPSHOT included. > Another issue is using our own patched version seems to me something that > could bring problems since is something out the eye of everybody but the > person(s) that knows about this particularity. > thanks > > El dom., 24 nov. 2019 a las 6:24, Alex Harui () > escribió: > > > I manually installed the other 1.11.2-SNAPSHOT maven artifacts in the > > local maven repository on the CI server. > > > > -Alex > > > > On 11/23/19, 1:50 AM, "Carlos Rovira" wrote: > > > > Thanks Alex, > > I finally get the RS#1 finally complete. > > About dependencies you mentioned, I didn't see any commit from you to > > repo > > to modify a pom, are you referring to some external dependencies, > > maybe in > > the windows machine? > > Going with RS#2 > > Thanks! > > > > El vie., 22 nov. 2019 a las 20:56, Alex Harui > > () > > escribió: > > > > > OK, looks l forgot to copy some dependencies. I just added some > > more. > > > Try it again and see if it works or there are new errors. > > > > > > On 11/22/19, 11:41 AM, "Carlos Rovira" > > wrote: > > > > > > Hi Alex, > > > > > > I updated the pom to exactly the same we had for JGIT, with the > > > 1.11.2-SNAPSHOT. But is failing [1] > > > > > > [WARNING] The POM for > > > org.apache.maven.scm:maven-scm-api:jar:1.11.2-SNAPSHOT is > > missing, no > > > dependency information available > > > > > > > > > [ERROR] Failed to execute goal > > > org.apache.maven.plugins:maven-release-plugin:2.5.3:branch > > > (default-cli) on project royale-compiler-parent: Execution > > default-cli > > > of goal > > org.apache.maven.plugins:maven-release-plugin:2.5.3:branch > > > failed: Plugin > > org.apache.maven.plugins:maven-release-plugin:2.5.3 or > > > one of its dependencies could not be resolved: Failed to > collect > > > dependencies at > > > org.apache.maven.plugins:maven-release-plugin:jar:2.5.3 -> > > > > org.apache.maven.scm:maven-scm-provider-jgit:jar:1.11.2-SNAPSHOT: > > > Failed to read artifact descriptor for > > > > org.apache.maven.scm:maven-scm-provider-jgit:jar:1.11.2-SNAPSHOT: > > > Failure to find > > > > org.apache.maven.scm:maven-scm-providers-git:pom:1.11.2-SNAPSHOT > > in > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Frepository.apache.org%2Fsnapshotsdata=02%7C01%7Caharui%40adobe.com%7Ca568ac087510493c93a208d770cd9793%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637101900658191131sdata=9r4M9hpZlQNOPBFKUi7MPK74aLBs9Wwt3YbbyFEWHuo%3Dreserved=0 > > > was cached in the local > > > repository, resolution will not be reattempted until the update > > > interval of apache.snapshots has elapsed or updates are forced > -> > > > [Help 1] > > > > > > > > > Caused by: > org.eclipse.aether.transfer.ArtifactNotFoundException: > > > Failure to find > > > > org.apache.maven.scm:maven-scm-providers-git:pom:1.11.2-SNAPSHOT > > in > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Frepository.apache.org%2Fsnapshotsdata=02%7C01%7Caharui%40adobe.com%7Ca568ac087510493c93a208d770cd9793%7Cfa7b1b5a7b34438794
Re: Release Step 001 Succeeded
We released 0.9.6 using snapshot. I was told they would not look at my patch unless I added tests. I have not had time to figure out their test system. You are welcome to do that. Get Outlook for Android<https://aka.ms/ghei36> From: Carlos Rovira Sent: Sunday, November 24, 2019 3:00:43 AM To: dev@royale.apache.org Subject: Re: Release Step 001 Succeeded Hi Alex, If we rely on SNAPSHOT, then we'll not be able to release right? If the patch show in the ticket (SCM-921) solved the issue, why don't report it? They could bring a release working version that allow us to release right? Don't know how it worked in the past with a SNAPSHOT version since maven should not allow to release with SNAPSHOT included. Another issue is using our own patched version seems to me something that could bring problems since is something out the eye of everybody but the person(s) that knows about this particularity. thanks El dom., 24 nov. 2019 a las 6:24, Alex Harui () escribió: > I manually installed the other 1.11.2-SNAPSHOT maven artifacts in the > local maven repository on the CI server. > > -Alex > > On 11/23/19, 1:50 AM, "Carlos Rovira" wrote: > > Thanks Alex, > I finally get the RS#1 finally complete. > About dependencies you mentioned, I didn't see any commit from you to > repo > to modify a pom, are you referring to some external dependencies, > maybe in > the windows machine? > Going with RS#2 > Thanks! > > El vie., 22 nov. 2019 a las 20:56, Alex Harui > () > escribió: > > > OK, looks l forgot to copy some dependencies. I just added some > more. > > Try it again and see if it works or there are new errors. > > > > On 11/22/19, 11:41 AM, "Carlos Rovira" > wrote: > > > > Hi Alex, > > > > I updated the pom to exactly the same we had for JGIT, with the > > 1.11.2-SNAPSHOT. But is failing [1] > > > > [WARNING] The POM for > > org.apache.maven.scm:maven-scm-api:jar:1.11.2-SNAPSHOT is > missing, no > > dependency information available > > > > > > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-release-plugin:2.5.3:branch > > (default-cli) on project royale-compiler-parent: Execution > default-cli > > of goal > org.apache.maven.plugins:maven-release-plugin:2.5.3:branch > > failed: Plugin > org.apache.maven.plugins:maven-release-plugin:2.5.3 or > > one of its dependencies could not be resolved: Failed to collect > > dependencies at > > org.apache.maven.plugins:maven-release-plugin:jar:2.5.3 -> > > org.apache.maven.scm:maven-scm-provider-jgit:jar:1.11.2-SNAPSHOT: > > Failed to read artifact descriptor for > > org.apache.maven.scm:maven-scm-provider-jgit:jar:1.11.2-SNAPSHOT: > > Failure to find > > org.apache.maven.scm:maven-scm-providers-git:pom:1.11.2-SNAPSHOT > in > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Frepository.apache.org%2Fsnapshotsdata=02%7C01%7Caharui%40adobe.com%7Ca568ac087510493c93a208d770cd9793%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637101900658191131sdata=9r4M9hpZlQNOPBFKUi7MPK74aLBs9Wwt3YbbyFEWHuo%3Dreserved=0 > > was cached in the local > > repository, resolution will not be reattempted until the update > > interval of apache.snapshots has elapsed or updates are forced -> > > [Help 1] > > > > > > Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: > > Failure to find > > org.apache.maven.scm:maven-scm-providers-git:pom:1.11.2-SNAPSHOT > in > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Frepository.apache.org%2Fsnapshotsdata=02%7C01%7Caharui%40adobe.com%7Ca568ac087510493c93a208d770cd9793%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637101900658191131sdata=9r4M9hpZlQNOPBFKUi7MPK74aLBs9Wwt3YbbyFEWHuo%3Dreserved=0 > > was cached in the local > > repository, resolution will not be reattempted until the update > > interval of apache.snapshots has elapsed or updates are forced > > > > > > Don't know why it's not capapble to find that SNAPSHOT version. > I look > > for > > some snapshot repo removed but didn't found. > > > > Another separate issue I finding is that I need to restart > Jenkins many > > times due to the process failing to not find Java8. Restarting > solves &
Re: Release Step 001 Succeeded
Hi Alex, If we rely on SNAPSHOT, then we'll not be able to release right? If the patch show in the ticket (SCM-921) solved the issue, why don't report it? They could bring a release working version that allow us to release right? Don't know how it worked in the past with a SNAPSHOT version since maven should not allow to release with SNAPSHOT included. Another issue is using our own patched version seems to me something that could bring problems since is something out the eye of everybody but the person(s) that knows about this particularity. thanks El dom., 24 nov. 2019 a las 6:24, Alex Harui () escribió: > I manually installed the other 1.11.2-SNAPSHOT maven artifacts in the > local maven repository on the CI server. > > -Alex > > On 11/23/19, 1:50 AM, "Carlos Rovira" wrote: > > Thanks Alex, > I finally get the RS#1 finally complete. > About dependencies you mentioned, I didn't see any commit from you to > repo > to modify a pom, are you referring to some external dependencies, > maybe in > the windows machine? > Going with RS#2 > Thanks! > > El vie., 22 nov. 2019 a las 20:56, Alex Harui > () > escribió: > > > OK, looks l forgot to copy some dependencies. I just added some > more. > > Try it again and see if it works or there are new errors. > > > > On 11/22/19, 11:41 AM, "Carlos Rovira" > wrote: > > > > Hi Alex, > > > > I updated the pom to exactly the same we had for JGIT, with the > > 1.11.2-SNAPSHOT. But is failing [1] > > > > [WARNING] The POM for > > org.apache.maven.scm:maven-scm-api:jar:1.11.2-SNAPSHOT is > missing, no > > dependency information available > > > > > > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-release-plugin:2.5.3:branch > > (default-cli) on project royale-compiler-parent: Execution > default-cli > > of goal > org.apache.maven.plugins:maven-release-plugin:2.5.3:branch > > failed: Plugin > org.apache.maven.plugins:maven-release-plugin:2.5.3 or > > one of its dependencies could not be resolved: Failed to collect > > dependencies at > > org.apache.maven.plugins:maven-release-plugin:jar:2.5.3 -> > > org.apache.maven.scm:maven-scm-provider-jgit:jar:1.11.2-SNAPSHOT: > > Failed to read artifact descriptor for > > org.apache.maven.scm:maven-scm-provider-jgit:jar:1.11.2-SNAPSHOT: > > Failure to find > > org.apache.maven.scm:maven-scm-providers-git:pom:1.11.2-SNAPSHOT > in > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Frepository.apache.org%2Fsnapshotsdata=02%7C01%7Caharui%40adobe.com%7C16736f1395054385590508d76ffa8369%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637100994052243873sdata=59%2BkAYzD8rURGlN%2F65Ae%2FUMQL6HIQlh1rfF6Lqrdh8w%3Dreserved=0 > > was cached in the local > > repository, resolution will not be reattempted until the update > > interval of apache.snapshots has elapsed or updates are forced -> > > [Help 1] > > > > > > Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: > > Failure to find > > org.apache.maven.scm:maven-scm-providers-git:pom:1.11.2-SNAPSHOT > in > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Frepository.apache.org%2Fsnapshotsdata=02%7C01%7Caharui%40adobe.com%7C16736f1395054385590508d76ffa8369%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637100994052243873sdata=59%2BkAYzD8rURGlN%2F65Ae%2FUMQL6HIQlh1rfF6Lqrdh8w%3Dreserved=0 > > was cached in the local > > repository, resolution will not be reattempted until the update > > interval of apache.snapshots has elapsed or updates are forced > > > > > > Don't know why it's not capapble to find that SNAPSHOT version. > I look > > for > > some snapshot repo removed but didn't found. > > > > Another separate issue I finding is that I need to restart > Jenkins many > > times due to the process failing to not find Java8. Restarting > solves > > the > > issue, but don't understand why it needs to be restart so many > times in > > short periods of time. > > > > [1] > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Release_Step_001%2F10%2Fconsoledata=02%7C01%7Caharui%40adobe.com%7C16736f1395054385590508d76ffa8369%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637100994052253870sdata=txIMrFC1rYNaKXcxzVyOvhq7YUrL6ATygrylfdqoXRA%3Dreserved=0 > > > > El vie., 22 nov. 2019 a las 2:54, Alex Harui > ( > >) > > escribió: > > > > > Due to this bug: > > >
Re: Release Step 001 Succeeded
I manually installed the other 1.11.2-SNAPSHOT maven artifacts in the local maven repository on the CI server. -Alex On 11/23/19, 1:50 AM, "Carlos Rovira" wrote: Thanks Alex, I finally get the RS#1 finally complete. About dependencies you mentioned, I didn't see any commit from you to repo to modify a pom, are you referring to some external dependencies, maybe in the windows machine? Going with RS#2 Thanks! El vie., 22 nov. 2019 a las 20:56, Alex Harui () escribió: > OK, looks l forgot to copy some dependencies. I just added some more. > Try it again and see if it works or there are new errors. > > On 11/22/19, 11:41 AM, "Carlos Rovira" wrote: > > Hi Alex, > > I updated the pom to exactly the same we had for JGIT, with the > 1.11.2-SNAPSHOT. But is failing [1] > > [WARNING] The POM for > org.apache.maven.scm:maven-scm-api:jar:1.11.2-SNAPSHOT is missing, no > dependency information available > > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-release-plugin:2.5.3:branch > (default-cli) on project royale-compiler-parent: Execution default-cli > of goal org.apache.maven.plugins:maven-release-plugin:2.5.3:branch > failed: Plugin org.apache.maven.plugins:maven-release-plugin:2.5.3 or > one of its dependencies could not be resolved: Failed to collect > dependencies at > org.apache.maven.plugins:maven-release-plugin:jar:2.5.3 -> > org.apache.maven.scm:maven-scm-provider-jgit:jar:1.11.2-SNAPSHOT: > Failed to read artifact descriptor for > org.apache.maven.scm:maven-scm-provider-jgit:jar:1.11.2-SNAPSHOT: > Failure to find > org.apache.maven.scm:maven-scm-providers-git:pom:1.11.2-SNAPSHOT in > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Frepository.apache.org%2Fsnapshotsdata=02%7C01%7Caharui%40adobe.com%7C16736f1395054385590508d76ffa8369%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637100994052243873sdata=59%2BkAYzD8rURGlN%2F65Ae%2FUMQL6HIQlh1rfF6Lqrdh8w%3Dreserved=0 > was cached in the local > repository, resolution will not be reattempted until the update > interval of apache.snapshots has elapsed or updates are forced -> > [Help 1] > > > Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: > Failure to find > org.apache.maven.scm:maven-scm-providers-git:pom:1.11.2-SNAPSHOT in > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Frepository.apache.org%2Fsnapshotsdata=02%7C01%7Caharui%40adobe.com%7C16736f1395054385590508d76ffa8369%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637100994052243873sdata=59%2BkAYzD8rURGlN%2F65Ae%2FUMQL6HIQlh1rfF6Lqrdh8w%3Dreserved=0 > was cached in the local > repository, resolution will not be reattempted until the update > interval of apache.snapshots has elapsed or updates are forced > > > Don't know why it's not capapble to find that SNAPSHOT version. I look > for > some snapshot repo removed but didn't found. > > Another separate issue I finding is that I need to restart Jenkins many > times due to the process failing to not find Java8. Restarting solves > the > issue, but don't understand why it needs to be restart so many times in > short periods of time. > > [1] > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Release_Step_001%2F10%2Fconsoledata=02%7C01%7Caharui%40adobe.com%7C16736f1395054385590508d76ffa8369%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637100994052253870sdata=txIMrFC1rYNaKXcxzVyOvhq7YUrL6ATygrylfdqoXRA%3Dreserved=0 > > El vie., 22 nov. 2019 a las 2:54, Alex Harui ( >) > escribió: > > > Due to this bug: > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FSCM-921data=02%7C01%7Caharui%40adobe.com%7C16736f1395054385590508d76ffa8369%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637100994052253870sdata=%2BcwHnJQ3nJgxfE31nsaEDkABQx3KgGml9rsoDIUCoZ8%3Dreserved=0 > > I think you have to use 1.11.2-SNAPSHOT which I installed on the VM. > > > > If you look at the console output, it looks like the commit > happened, but > > it didn't happen which is why the git status still shows modified > files. > > > > I also changed the developbranchname in build.properties. > > > > -Alex > > > > On 11/21/19, 3:56 PM, "Carlos Rovira" > wrote: > > > > Hi, > > > > restarting Jenkins make Java8 work again mysteriously. > > Now, following this steps from Remote Desktop in CI Server, I'm
Re: Release Step 001 Succeeded
Thanks Alex, I finally get the RS#1 finally complete. About dependencies you mentioned, I didn't see any commit from you to repo to modify a pom, are you referring to some external dependencies, maybe in the windows machine? Going with RS#2 Thanks! El vie., 22 nov. 2019 a las 20:56, Alex Harui () escribió: > OK, looks l forgot to copy some dependencies. I just added some more. > Try it again and see if it works or there are new errors. > > On 11/22/19, 11:41 AM, "Carlos Rovira" wrote: > > Hi Alex, > > I updated the pom to exactly the same we had for JGIT, with the > 1.11.2-SNAPSHOT. But is failing [1] > > [WARNING] The POM for > org.apache.maven.scm:maven-scm-api:jar:1.11.2-SNAPSHOT is missing, no > dependency information available > > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-release-plugin:2.5.3:branch > (default-cli) on project royale-compiler-parent: Execution default-cli > of goal org.apache.maven.plugins:maven-release-plugin:2.5.3:branch > failed: Plugin org.apache.maven.plugins:maven-release-plugin:2.5.3 or > one of its dependencies could not be resolved: Failed to collect > dependencies at > org.apache.maven.plugins:maven-release-plugin:jar:2.5.3 -> > org.apache.maven.scm:maven-scm-provider-jgit:jar:1.11.2-SNAPSHOT: > Failed to read artifact descriptor for > org.apache.maven.scm:maven-scm-provider-jgit:jar:1.11.2-SNAPSHOT: > Failure to find > org.apache.maven.scm:maven-scm-providers-git:pom:1.11.2-SNAPSHOT in > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Frepository.apache.org%2Fsnapshotsdata=02%7C01%7Caharui%40adobe.com%7C1a2678c85cee422a6c6908d76f83e74a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637100484624802842sdata=BJ5910IacaunwKbzt1eKiiztlD%2FhXCX6aYrmhbtFLew%3Dreserved=0 > was cached in the local > repository, resolution will not be reattempted until the update > interval of apache.snapshots has elapsed or updates are forced -> > [Help 1] > > > Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: > Failure to find > org.apache.maven.scm:maven-scm-providers-git:pom:1.11.2-SNAPSHOT in > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Frepository.apache.org%2Fsnapshotsdata=02%7C01%7Caharui%40adobe.com%7C1a2678c85cee422a6c6908d76f83e74a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637100484624812838sdata=xhVIDs9lydPLwtFTNjs73jsD6DtA7aSI8B7e%2F1dmDX8%3Dreserved=0 > was cached in the local > repository, resolution will not be reattempted until the update > interval of apache.snapshots has elapsed or updates are forced > > > Don't know why it's not capapble to find that SNAPSHOT version. I look > for > some snapshot repo removed but didn't found. > > Another separate issue I finding is that I need to restart Jenkins many > times due to the process failing to not find Java8. Restarting solves > the > issue, but don't understand why it needs to be restart so many times in > short periods of time. > > [1] > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Release_Step_001%2F10%2Fconsoledata=02%7C01%7Caharui%40adobe.com%7C1a2678c85cee422a6c6908d76f83e74a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637100484624812838sdata=KlAKy4PzkngLvql3hH%2FNwhjqqT7qrUZnb0iuRXt0ZBQ%3Dreserved=0 > > El vie., 22 nov. 2019 a las 2:54, Alex Harui ( >) > escribió: > > > Due to this bug: > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FSCM-921data=02%7C01%7Caharui%40adobe.com%7C1a2678c85cee422a6c6908d76f83e74a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637100484624812838sdata=0hJg3AhN3Iu0OqS4VGoTo0%2FFLk3HtgbaDIclDBUnjj4%3Dreserved=0 > > I think you have to use 1.11.2-SNAPSHOT which I installed on the VM. > > > > If you look at the console output, it looks like the commit > happened, but > > it didn't happen which is why the git status still shows modified > files. > > > > I also changed the developbranchname in build.properties. > > > > -Alex > > > > On 11/21/19, 3:56 PM, "Carlos Rovira" > wrote: > > > > Hi, > > > > restarting Jenkins make Java8 work again mysteriously. > > Now, following this steps from Remote Desktop in CI Server, I'm > having > > trouble and don't know what to do. Any suggestions? This the > output in > > CMD: > > > > > cd C:\jenkins\workspace\Royale_Release_Step_001 > > > git push > > > > fatal: The current branch release/0.9.7 has no upstream branch. > > To push the current branch and set the remote as upstream, use > > > > git push --set-upstream origin release/0.9.7 > > > > Thanks > > > > El vie., 22 nov. 2019 a las 0:13, > escribió: > > > > > Log in to the
Release Step 001 Succeeded
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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.
Re: Release Step 001 Succeeded
OK, looks l forgot to copy some dependencies. I just added some more. Try it again and see if it works or there are new errors. On 11/22/19, 11:41 AM, "Carlos Rovira" wrote: Hi Alex, I updated the pom to exactly the same we had for JGIT, with the 1.11.2-SNAPSHOT. But is failing [1] [WARNING] The POM for org.apache.maven.scm:maven-scm-api:jar:1.11.2-SNAPSHOT is missing, no dependency information available [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.3:branch (default-cli) on project royale-compiler-parent: Execution default-cli of goal org.apache.maven.plugins:maven-release-plugin:2.5.3:branch failed: Plugin org.apache.maven.plugins:maven-release-plugin:2.5.3 or one of its dependencies could not be resolved: Failed to collect dependencies at org.apache.maven.plugins:maven-release-plugin:jar:2.5.3 -> org.apache.maven.scm:maven-scm-provider-jgit:jar:1.11.2-SNAPSHOT: Failed to read artifact descriptor for org.apache.maven.scm:maven-scm-provider-jgit:jar:1.11.2-SNAPSHOT: Failure to find org.apache.maven.scm:maven-scm-providers-git:pom:1.11.2-SNAPSHOT in https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Frepository.apache.org%2Fsnapshotsdata=02%7C01%7Caharui%40adobe.com%7C1a2678c85cee422a6c6908d76f83e74a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637100484624802842sdata=BJ5910IacaunwKbzt1eKiiztlD%2FhXCX6aYrmhbtFLew%3Dreserved=0 was cached in the local repository, resolution will not be reattempted until the update interval of apache.snapshots has elapsed or updates are forced -> [Help 1] Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Failure to find org.apache.maven.scm:maven-scm-providers-git:pom:1.11.2-SNAPSHOT in https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Frepository.apache.org%2Fsnapshotsdata=02%7C01%7Caharui%40adobe.com%7C1a2678c85cee422a6c6908d76f83e74a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637100484624812838sdata=xhVIDs9lydPLwtFTNjs73jsD6DtA7aSI8B7e%2F1dmDX8%3Dreserved=0 was cached in the local repository, resolution will not be reattempted until the update interval of apache.snapshots has elapsed or updates are forced Don't know why it's not capapble to find that SNAPSHOT version. I look for some snapshot repo removed but didn't found. Another separate issue I finding is that I need to restart Jenkins many times due to the process failing to not find Java8. Restarting solves the issue, but don't understand why it needs to be restart so many times in short periods of time. [1] https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Release_Step_001%2F10%2Fconsoledata=02%7C01%7Caharui%40adobe.com%7C1a2678c85cee422a6c6908d76f83e74a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637100484624812838sdata=KlAKy4PzkngLvql3hH%2FNwhjqqT7qrUZnb0iuRXt0ZBQ%3Dreserved=0 El vie., 22 nov. 2019 a las 2:54, Alex Harui () escribió: > Due to this bug: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FSCM-921data=02%7C01%7Caharui%40adobe.com%7C1a2678c85cee422a6c6908d76f83e74a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637100484624812838sdata=0hJg3AhN3Iu0OqS4VGoTo0%2FFLk3HtgbaDIclDBUnjj4%3Dreserved=0 > I think you have to use 1.11.2-SNAPSHOT which I installed on the VM. > > If you look at the console output, it looks like the commit happened, but > it didn't happen which is why the git status still shows modified files. > > I also changed the developbranchname in build.properties. > > -Alex > > On 11/21/19, 3:56 PM, "Carlos Rovira" wrote: > > Hi, > > restarting Jenkins make Java8 work again mysteriously. > Now, following this steps from Remote Desktop in CI Server, I'm having > trouble and don't know what to do. Any suggestions? This the output in > CMD: > > > cd C:\jenkins\workspace\Royale_Release_Step_001 > > git push > > fatal: The current branch release/0.9.7 has no upstream branch. > To push the current branch and set the remote as upstream, use > > git push --set-upstream origin release/0.9.7 > > Thanks > > El vie., 22 nov. 2019 a las 0:13, escribió: > > > 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.7 > > git push -u origin release/0.9.7 > > > > You will need your Apache/Github username and 2FA token. > > > > -- > Carlos Rovira > >
Re: Release Step 001 Succeeded
Hi Alex, I updated the pom to exactly the same we had for JGIT, with the 1.11.2-SNAPSHOT. But is failing [1] [WARNING] The POM for org.apache.maven.scm:maven-scm-api:jar:1.11.2-SNAPSHOT is missing, no dependency information available [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.3:branch (default-cli) on project royale-compiler-parent: Execution default-cli of goal org.apache.maven.plugins:maven-release-plugin:2.5.3:branch failed: Plugin org.apache.maven.plugins:maven-release-plugin:2.5.3 or one of its dependencies could not be resolved: Failed to collect dependencies at org.apache.maven.plugins:maven-release-plugin:jar:2.5.3 -> org.apache.maven.scm:maven-scm-provider-jgit:jar:1.11.2-SNAPSHOT: Failed to read artifact descriptor for org.apache.maven.scm:maven-scm-provider-jgit:jar:1.11.2-SNAPSHOT: Failure to find org.apache.maven.scm:maven-scm-providers-git:pom:1.11.2-SNAPSHOT in http://repository.apache.org/snapshots was cached in the local repository, resolution will not be reattempted until the update interval of apache.snapshots has elapsed or updates are forced -> [Help 1] Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Failure to find org.apache.maven.scm:maven-scm-providers-git:pom:1.11.2-SNAPSHOT in http://repository.apache.org/snapshots was cached in the local repository, resolution will not be reattempted until the update interval of apache.snapshots has elapsed or updates are forced Don't know why it's not capapble to find that SNAPSHOT version. I look for some snapshot repo removed but didn't found. Another separate issue I finding is that I need to restart Jenkins many times due to the process failing to not find Java8. Restarting solves the issue, but don't understand why it needs to be restart so many times in short periods of time. [1] http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_001/10/console El vie., 22 nov. 2019 a las 2:54, Alex Harui () escribió: > Due to this bug: https://issues.apache.org/jira/browse/SCM-921 > I think you have to use 1.11.2-SNAPSHOT which I installed on the VM. > > If you look at the console output, it looks like the commit happened, but > it didn't happen which is why the git status still shows modified files. > > I also changed the developbranchname in build.properties. > > -Alex > > On 11/21/19, 3:56 PM, "Carlos Rovira" wrote: > > Hi, > > restarting Jenkins make Java8 work again mysteriously. > Now, following this steps from Remote Desktop in CI Server, I'm having > trouble and don't know what to do. Any suggestions? This the output in > CMD: > > > cd C:\jenkins\workspace\Royale_Release_Step_001 > > git push > > fatal: The current branch release/0.9.7 has no upstream branch. > To push the current branch and set the remote as upstream, use > > git push --set-upstream origin release/0.9.7 > > Thanks > > El vie., 22 nov. 2019 a las 0:13, escribió: > > > 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.7 > > git push -u origin release/0.9.7 > > > > You will need your Apache/Github username and 2FA token. > > > > -- > Carlos Rovira > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7Cc46ddf8a48f84d65d54c08d76ede77b5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637099774084757226sdata=xCzKIudmOHpvJoP26sEiUgLG1nIjiJ5NpMvGCowX2ac%3Dreserved=0 > > > -- Carlos Rovira http://about.me/carlosrovira
Re: Release Step 001 Succeeded
Due to this bug: https://issues.apache.org/jira/browse/SCM-921 I think you have to use 1.11.2-SNAPSHOT which I installed on the VM. If you look at the console output, it looks like the commit happened, but it didn't happen which is why the git status still shows modified files. I also changed the developbranchname in build.properties. -Alex On 11/21/19, 3:56 PM, "Carlos Rovira" wrote: Hi, restarting Jenkins make Java8 work again mysteriously. Now, following this steps from Remote Desktop in CI Server, I'm having trouble and don't know what to do. Any suggestions? This the output in CMD: > cd C:\jenkins\workspace\Royale_Release_Step_001 > git push fatal: The current branch release/0.9.7 has no upstream branch. To push the current branch and set the remote as upstream, use git push --set-upstream origin release/0.9.7 Thanks El vie., 22 nov. 2019 a las 0:13, escribió: > 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.7 > git push -u origin release/0.9.7 > > You will need your Apache/Github username and 2FA token. -- Carlos Rovira https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7Cc46ddf8a48f84d65d54c08d76ede77b5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637099774084757226sdata=xCzKIudmOHpvJoP26sEiUgLG1nIjiJ5NpMvGCowX2ac%3Dreserved=0
Re: Release Step 001 Succeeded
Hi, restarting Jenkins make Java8 work again mysteriously. Now, following this steps from Remote Desktop in CI Server, I'm having trouble and don't know what to do. Any suggestions? This the output in CMD: > cd C:\jenkins\workspace\Royale_Release_Step_001 > git push fatal: The current branch release/0.9.7 has no upstream branch. To push the current branch and set the remote as upstream, use git push --set-upstream origin release/0.9.7 Thanks El vie., 22 nov. 2019 a las 0:13, escribió: > 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.7 > git push -u origin release/0.9.7 > > You will need your Apache/Github username and 2FA token. -- Carlos Rovira http://about.me/carlosrovira
Release Step 001 Succeeded
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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.
Release Step 001 Succeeded
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.
Release Step 001 Succeeded
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.
Release Step 001 Succeeded
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.
Release Step 001 Succeeded
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.
Release Step 001 Succeeded
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.
Release Step 001 Succeeded
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.
Release Step 001 Succeeded
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.
Release Step 001 Succeeded
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.
Release Step 001 Succeeded
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.
Release Step 001 Succeeded
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.
Release Step 001 Succeeded
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.
Release Step 001 Succeeded
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.
Release Step 001 Succeeded
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.
Release Step 001 Succeeded
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.
Release Step 001 Succeeded
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.
Release Step 001 Succeeded
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.
Release Step 001 Succeeded
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.
Release Step 001 Succeeded
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.
Release Step 001 Succeeded
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.
Release Step 001 Succeeded
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.
Release Step 001 Succeeded
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.
Re: Release Step 001 Succeeded
Note to self: Installed custom maven-scm-provider.jgit jar per https://issues.apache.org/jira/browse/SCM-921 On 2/19/19, 9:28 PM, "Apache Royale CI Server" wrote: 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.
Release Step 001 Succeeded
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.
Release Step 001 Succeeded
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.
Release Step 001 Succeeded
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.
Release Step 001 Succeeded
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.
Release Step 001 Succeeded
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.
Release Step 001 Succeeded
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.
Release Step 001 Succeeded
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 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
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.
