You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@royale.apache.org by ca...@apache.org on 2019/11/20 15:51:48 UTC
[royale-asjs.wiki] branch master updated: Update CI server url to
the new one
This is an automated email from the ASF dual-hosted git repository.
carlosrovira pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/royale-asjs.wiki.git
View the commit online:
https://github.com/apache/royale-asjs.wiki/commit/b5e48a42b93defbd0821406a120b6c25921a3f57
The following commit(s) were added to refs/heads/master by this push:
new b5e48a4 Update CI server url to the new one
b5e48a4 is described below
commit b5e48a42b93defbd0821406a120b6c25921a3f57
Author: Carlos Rovira <ca...@apache.org>
AuthorDate: Wed Nov 20 16:51:43 2019 +0100
Update CI server url to the new one
---
Release-Manager-Notes.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Release-Manager-Notes.md b/Release-Manager-Notes.md
index c6a0f9c..5680277 100644
--- a/Release-Manager-Notes.md
+++ b/Release-Manager-Notes.md
@@ -286,7 +286,7 @@ Also make sure that your SVN repos for dist/dev/Royale are updated without confl
Assuming you have set up properly, creating a release candidate involves:
-1) Run each [Release Steps job on the CI Server](http://apacheroyaleci.westus2.cloudapp.azure.com:8080/view/Royale%20Release/) in order. As each job completes, it will send an email to dev@royale.apache.org explaining what to do next. The final steps should generate the packages and set up emails to send to the list for vote and discussion.
+1) Run each [Release Steps job on the CI Server](http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/view/Royale%20Release/) in order. As each job completes, it will send an email to dev@royale.apache.org explaining what to do next. The final steps should generate the packages and set up emails to send to the list for vote and discussion.
For details on each job see: [Release Steps Jobs on Jenkins](Release-Steps-Jobs-On-Jenkins)
When the vote passes, do
Re: [royale-asjs.wiki] branch master updated: Update CI server url to
the new one
Posted by Carlos Rovira <ca...@apache.org>.
Hi,
this url:
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/view/Royale%20Release/
seems
not valid anymore
Maybe we can just put this one:
http://apacheroyaleci.westus2.cloudapp.azure.com:8080
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/view/Royale%20Release/>
?
El mié., 20 nov. 2019 a las 16:51, <ca...@apache.org> escribió:
> This is an automated email from the ASF dual-hosted git repository.
>
> carlosrovira pushed a commit to branch master
> in repository https://gitbox.apache.org/repos/asf/royale-asjs.wiki.git
>
>
> View the commit online:
>
> https://github.com/apache/royale-asjs.wiki/commit/b5e48a42b93defbd0821406a120b6c25921a3f57
>
> The following commit(s) were added to refs/heads/master by this push:
> new b5e48a4 Update CI server url to the new one
> b5e48a4 is described below
>
> commit b5e48a42b93defbd0821406a120b6c25921a3f57
> Author: Carlos Rovira <ca...@apache.org>
> AuthorDate: Wed Nov 20 16:51:43 2019 +0100
>
> Update CI server url to the new one
> ---
> Release-Manager-Notes.md | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Release-Manager-Notes.md b/Release-Manager-Notes.md
> index c6a0f9c..5680277 100644
> --- a/Release-Manager-Notes.md
> +++ b/Release-Manager-Notes.md
> @@ -286,7 +286,7 @@ Also make sure that your SVN repos for dist/dev/Royale
> are updated without confl
>
> Assuming you have set up properly, creating a release candidate involves:
>
> -1) Run each [Release Steps job on the CI Server](
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/view/Royale%20Release/)
> in order. As each job completes, it will send an email to
> dev@royale.apache.org explaining what to do next. The final steps should
> generate the packages and set up emails to send to the list for vote and
> discussion.
> +1) Run each [Release Steps job on the CI Server](
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/view/Royale%20Release/)
> in order. As each job completes, it will send an email to
> dev@royale.apache.org explaining what to do next. The final steps should
> generate the packages and set up emails to send to the list for vote and
> discussion.
>
> For details on each job see: [Release Steps Jobs on
> Jenkins](Release-Steps-Jobs-On-Jenkins)
> When the vote passes, do
>
>
--
Carlos Rovira
http://about.me/carlosrovira