You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by ap...@gmail.com on 2020/07/13 07:33:13 UTC
Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still
Failing!
Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing:
Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/15/ to view the results.
Royale_Compiler_Build_Tools_Release_Step_002 - Build # 26 - Still
Failing!
Posted by ap...@gmail.com.
Royale_Compiler_Build_Tools_Release_Step_002 - Build # 26 - Still Failing:
Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/26/ to view the results.
Royale_Compiler_Build_Tools_Release_Step_002 - Build # 25 - Still
Failing!
Posted by ap...@gmail.com.
Royale_Compiler_Build_Tools_Release_Step_002 - Build # 25 - Still Failing:
Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/25/ to view the results.
Royale_Compiler_Build_Tools_Release_Step_002 - Build # 24 - Still
Failing!
Posted by ap...@gmail.com.
Royale_Compiler_Build_Tools_Release_Step_002 - Build # 24 - Still Failing:
Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/24/ to view the results.
Royale_Compiler_Build_Tools_Release_Step_002 - Build # 23 - Still
Failing!
Posted by ap...@gmail.com.
Royale_Compiler_Build_Tools_Release_Step_002 - Build # 23 - Still Failing:
Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/23/ to view the results.
Royale_Compiler_Build_Tools_Release_Step_002 - Build # 22 - Still
Failing!
Posted by ap...@gmail.com.
Royale_Compiler_Build_Tools_Release_Step_002 - Build # 22 - Still Failing:
Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/22/ to view the results.
Royale_Compiler_Build_Tools_Release_Step_002 - Build # 21 - Still
Failing!
Posted by ap...@gmail.com.
Royale_Compiler_Build_Tools_Release_Step_002 - Build # 21 - Still Failing:
Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/21/ to view the results.
Royale_Compiler_Build_Tools_Release_Step_002 - Build # 20 - Still
Failing!
Posted by ap...@gmail.com.
Royale_Compiler_Build_Tools_Release_Step_002 - Build # 20 - Still Failing:
Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/20/ to view the results.
Royale_Compiler_Build_Tools_Release_Step_002 - Build # 19 - Still
Failing!
Posted by ap...@gmail.com.
Royale_Compiler_Build_Tools_Release_Step_002 - Build # 19 - Still Failing:
Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/19/ to view the results.
Royale_Compiler_Build_Tools_Release_Step_002 - Build # 18 - Still
Failing!
Posted by ap...@gmail.com.
Royale_Compiler_Build_Tools_Release_Step_002 - Build # 18 - Still Failing:
Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/18/ to view the results.
Royale_Compiler_Build_Tools_Release_Step_002 - Build # 17 - Still
Failing!
Posted by ap...@gmail.com.
Royale_Compiler_Build_Tools_Release_Step_002 - Build # 17 - Still Failing:
Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/17/ to view the results.
Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still
Failing!
Posted by Harbs <ha...@gmail.com>.
Not sure.
It worked for Yishay when he did it, and I don’t think he put his credentials on the CI server.
There are manual steps for pushing the git. I did that.
Did something change in the compiler-build-tools between when Yishay did the release and now that might effect this?
> On Jul 13, 2020, at 12:21 PM, Christofer Dutz <ch...@c-ware.de> wrote:
>
> Yeah ... just wanted to say:
>
> If you want to deploy to the Apache Nexus, you need credentials. Usually I have them defined in my settings.xml but I wouldn't want that done on the CI server.
> Wasn't this what some of the steps were about? The RM downloads the bundle built on the CI server and then deploys on his local machine where he's got the credentials in his settings.xml?
>
> Chris
>
>
>
> Am 13.07.20, 11:10 schrieb "Yishay Weiss" <yi...@hotmail.com>:
>
> Good question. Let me see if I can figure this out.
>
> From: Harbs<ma...@gmail.com>
> Sent: Monday, July 13, 2020 12:05 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!
>
> Where am I supposed to put credential into the jenkins server?
>
>> On Jul 13, 2020, at 12:02 PM, Yishay Weiss <yi...@hotmail.com> wrote:
>>
>> Are you sure it’s not an Apache credentials problem? Last time I looked it looked like you were getting 401 from the server.
>>
>> From: Harbs<ma...@gmail.com>
>> Sent: Monday, July 13, 2020 11:58 AM
>> To: dev@royale.apache.org<ma...@royale.apache.org>
>> Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!
>>
>> Or maybe the issue is a few lines up?
>> [INFO] [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ compiler-build-tools ---
>> [INFO] [INFO] Downloading from apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml>
>> [INFO] [INFO] Downloaded from apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml> (796 B at 699 B/s)
>> [INFO] [INFO] Uploading to apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar>
>> [INFO] [INFO] Uploading to apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.pom <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.pom>
>> [INFO] [INFO] ------------------------------------------------------------------------
>> [INFO] [INFO] BUILD FAILURE
>> [INFO] [INFO] ------------------------------------------------------------------------
>> [INFO] [INFO] Total time: 54.801 s
>> [INFO] [INFO] Finished at: 2020-07-13T08:53:02Z
>> [INFO] [INFO] ------------------------------------------------------------------------
>> [INFO] [WARNING] The requested profile "pom.xml" could not be activated because it does not exist.
>> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.085259-2 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots <https://repository.apache.org/content/repositories/snapshots>): Failed to transfer file https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar> with status code 401 -> [Help 1]
>> Links 3 and 4 are not valid.
>>
>>> On Jul 13, 2020, at 11:54 AM, Harbs <ha...@gmail.com> wrote:
>>>
>>> Apparently the problem was not github being down:
>>> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.085259-2 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots <https://repository.apache.org/content/repositories/snapshots>): Failed to transfer file https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar> with status code 401 -> [Help 1]
>>> Suggestions?
>>>
>>>> On Jul 13, 2020, at 11:53 AM, apacheroyaleci@gmail.com <ma...@gmail.com> wrote:
>>>>
>>>> Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing:
>>>>
>>>> Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/16/ <http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/16/> to view the results.
>>>
>>
>
>
Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still
Failing!
Posted by Christofer Dutz <ch...@c-ware.de>.
Yeah ... just wanted to say:
If you want to deploy to the Apache Nexus, you need credentials. Usually I have them defined in my settings.xml but I wouldn't want that done on the CI server.
Wasn't this what some of the steps were about? The RM downloads the bundle built on the CI server and then deploys on his local machine where he's got the credentials in his settings.xml?
Chris
Am 13.07.20, 11:10 schrieb "Yishay Weiss" <yi...@hotmail.com>:
Good question. Let me see if I can figure this out.
From: Harbs<ma...@gmail.com>
Sent: Monday, July 13, 2020 12:05 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!
Where am I supposed to put credential into the jenkins server?
> On Jul 13, 2020, at 12:02 PM, Yishay Weiss <yi...@hotmail.com> wrote:
>
> Are you sure it’s not an Apache credentials problem? Last time I looked it looked like you were getting 401 from the server.
>
> From: Harbs<ma...@gmail.com>
> Sent: Monday, July 13, 2020 11:58 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!
>
> Or maybe the issue is a few lines up?
> [INFO] [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ compiler-build-tools ---
> [INFO] [INFO] Downloading from apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml>
> [INFO] [INFO] Downloaded from apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml> (796 B at 699 B/s)
> [INFO] [INFO] Uploading to apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar>
> [INFO] [INFO] Uploading to apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.pom <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.pom>
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Total time: 54.801 s
> [INFO] [INFO] Finished at: 2020-07-13T08:53:02Z
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [WARNING] The requested profile "pom.xml" could not be activated because it does not exist.
> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.085259-2 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots <https://repository.apache.org/content/repositories/snapshots>): Failed to transfer file https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar> with status code 401 -> [Help 1]
> Links 3 and 4 are not valid.
>
>> On Jul 13, 2020, at 11:54 AM, Harbs <ha...@gmail.com> wrote:
>>
>> Apparently the problem was not github being down:
>> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.085259-2 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots <https://repository.apache.org/content/repositories/snapshots>): Failed to transfer file https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar> with status code 401 -> [Help 1]
>> Suggestions?
>>
>>> On Jul 13, 2020, at 11:53 AM, apacheroyaleci@gmail.com <ma...@gmail.com> wrote:
>>>
>>> Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing:
>>>
>>> Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/16/ <http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/16/> to view the results.
>>
>
RE: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still
Failing!
Posted by Yishay Weiss <yi...@hotmail.com>.
This relates to issues I had with uploading to the Nexus server which only happens at a later stage. It ended up being a non-issue for me after we resolved some unnecessary loop in the upload process.
From: Harbs<ma...@gmail.com>
Sent: Monday, July 13, 2020 1:23 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!
https://lists.apache.org/thread.html/rf263801c4e33cc08f473bd6dd0f6c3f28b131c0a48612d70c7b36bc7%40%3Cdev.royale.apache.org%3E
> On Jul 13, 2020, at 1:13 PM, Yishay Weiss <yi...@hotmail.com> wrote:
>
> I don’t remember. Can you link the discussion from the archives?
>
> From: Harbs<ma...@gmail.com>
> Sent: Monday, July 13, 2020 12:47 PM
> To: Apache Royale Development<ma...@royale.apache.org>
> Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!
>
> There was a discussion on April 28, but I did not follow what you did.
>
> Did you release the compiler-build-tools from your local machine or from the CI server?
>
>> On Jul 13, 2020, at 12:26 PM, Yishay Weiss <yi...@hotmail.com> wrote:
>>
>> Based on
>>
>> cat C:\Users\ApacheRoyaleCI\.m2\settings.xml
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
>> https://maven.apache.org/xsd/settings-1.0.0.xsd">
>> <servers>
>> <server>
>> <id>apache.releases.https</id>
>> <username>${rm.username}</username>
>> <password>${rm.password}</password>
>> </server>
>> <server>
>> <id>apache.snapshots.https</id>
>> <username>${rm.username}</username>
>> <password>${rm.password}</password>
>> </server>
>> </servers>
>> </settings>
>>
>> there should be some command line params for rm.username and rm.password being passed as command line arguments. I may be missing something. I’ve sort of run out of time for the next few hours so it may be best to wait for Alex.
>>
>> From: Yishay Weiss<ma...@hotmail.com>
>> Sent: Monday, July 13, 2020 12:10 PM
>> To: dev@royale.apache.org<ma...@royale.apache.org>
>> Subject: RE: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!
>>
>> Good question. Let me see if I can figure this out.
>>
>> From: Harbs<ma...@gmail.com>
>> Sent: Monday, July 13, 2020 12:05 PM
>> To: dev@royale.apache.org<ma...@royale.apache.org>
>> Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!
>>
>> Where am I supposed to put credential into the jenkins server?
>>
>>> On Jul 13, 2020, at 12:02 PM, Yishay Weiss <yi...@hotmail.com> wrote:
>>>
>>> Are you sure it’s not an Apache credentials problem? Last time I looked it looked like you were getting 401 from the server.
>>>
>>> From: Harbs<ma...@gmail.com>
>>> Sent: Monday, July 13, 2020 11:58 AM
>>> To: dev@royale.apache.org<ma...@royale.apache.org>
>>> Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!
>>>
>>> Or maybe the issue is a few lines up?
>>> [INFO] [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ compiler-build-tools ---
>>> [INFO] [INFO] Downloading from apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml>
>>> [INFO] [INFO] Downloaded from apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml> (796 B at 699 B/s)
>>> [INFO] [INFO] Uploading to apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar>
>>> [INFO] [INFO] Uploading to apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.pom <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.pom>
>>> [INFO] [INFO] ------------------------------------------------------------------------
>>> [INFO] [INFO] BUILD FAILURE
>>> [INFO] [INFO] ------------------------------------------------------------------------
>>> [INFO] [INFO] Total time: 54.801 s
>>> [INFO] [INFO] Finished at: 2020-07-13T08:53:02Z
>>> [INFO] [INFO] ------------------------------------------------------------------------
>>> [INFO] [WARNING] The requested profile "pom.xml" could not be activated because it does not exist.
>>> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.085259-2 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots <https://repository.apache.org/content/repositories/snapshots>): Failed to transfer file https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar> with status code 401 -> [Help 1]
>>> Links 3 and 4 are not valid.
>>>
>>>> On Jul 13, 2020, at 11:54 AM, Harbs <ha...@gmail.com> wrote:
>>>>
>>>> Apparently the problem was not github being down:
>>>> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.085259-2 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots <https://repository.apache.org/content/repositories/snapshots>): Failed to transfer file https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar> with status code 401 -> [Help 1]
>>>> Suggestions?
>>>>
>>>>> On Jul 13, 2020, at 11:53 AM, apacheroyaleci@gmail.com <ma...@gmail.com> wrote:
>>>>>
>>>>> Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing:
>>>>>
>>>>> Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/16/ <http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/16/> to view the results.
>>>>
>>>
>>
>
Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still
Failing!
Posted by Harbs <ha...@gmail.com>.
https://lists.apache.org/thread.html/rf263801c4e33cc08f473bd6dd0f6c3f28b131c0a48612d70c7b36bc7%40%3Cdev.royale.apache.org%3E
> On Jul 13, 2020, at 1:13 PM, Yishay Weiss <yi...@hotmail.com> wrote:
>
> I don’t remember. Can you link the discussion from the archives?
>
> From: Harbs<ma...@gmail.com>
> Sent: Monday, July 13, 2020 12:47 PM
> To: Apache Royale Development<ma...@royale.apache.org>
> Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!
>
> There was a discussion on April 28, but I did not follow what you did.
>
> Did you release the compiler-build-tools from your local machine or from the CI server?
>
>> On Jul 13, 2020, at 12:26 PM, Yishay Weiss <yi...@hotmail.com> wrote:
>>
>> Based on
>>
>> cat C:\Users\ApacheRoyaleCI\.m2\settings.xml
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
>> https://maven.apache.org/xsd/settings-1.0.0.xsd">
>> <servers>
>> <server>
>> <id>apache.releases.https</id>
>> <username>${rm.username}</username>
>> <password>${rm.password}</password>
>> </server>
>> <server>
>> <id>apache.snapshots.https</id>
>> <username>${rm.username}</username>
>> <password>${rm.password}</password>
>> </server>
>> </servers>
>> </settings>
>>
>> there should be some command line params for rm.username and rm.password being passed as command line arguments. I may be missing something. I’ve sort of run out of time for the next few hours so it may be best to wait for Alex.
>>
>> From: Yishay Weiss<ma...@hotmail.com>
>> Sent: Monday, July 13, 2020 12:10 PM
>> To: dev@royale.apache.org<ma...@royale.apache.org>
>> Subject: RE: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!
>>
>> Good question. Let me see if I can figure this out.
>>
>> From: Harbs<ma...@gmail.com>
>> Sent: Monday, July 13, 2020 12:05 PM
>> To: dev@royale.apache.org<ma...@royale.apache.org>
>> Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!
>>
>> Where am I supposed to put credential into the jenkins server?
>>
>>> On Jul 13, 2020, at 12:02 PM, Yishay Weiss <yi...@hotmail.com> wrote:
>>>
>>> Are you sure it’s not an Apache credentials problem? Last time I looked it looked like you were getting 401 from the server.
>>>
>>> From: Harbs<ma...@gmail.com>
>>> Sent: Monday, July 13, 2020 11:58 AM
>>> To: dev@royale.apache.org<ma...@royale.apache.org>
>>> Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!
>>>
>>> Or maybe the issue is a few lines up?
>>> [INFO] [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ compiler-build-tools ---
>>> [INFO] [INFO] Downloading from apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml>
>>> [INFO] [INFO] Downloaded from apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml> (796 B at 699 B/s)
>>> [INFO] [INFO] Uploading to apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar>
>>> [INFO] [INFO] Uploading to apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.pom <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.pom>
>>> [INFO] [INFO] ------------------------------------------------------------------------
>>> [INFO] [INFO] BUILD FAILURE
>>> [INFO] [INFO] ------------------------------------------------------------------------
>>> [INFO] [INFO] Total time: 54.801 s
>>> [INFO] [INFO] Finished at: 2020-07-13T08:53:02Z
>>> [INFO] [INFO] ------------------------------------------------------------------------
>>> [INFO] [WARNING] The requested profile "pom.xml" could not be activated because it does not exist.
>>> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.085259-2 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots <https://repository.apache.org/content/repositories/snapshots>): Failed to transfer file https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar> with status code 401 -> [Help 1]
>>> Links 3 and 4 are not valid.
>>>
>>>> On Jul 13, 2020, at 11:54 AM, Harbs <ha...@gmail.com> wrote:
>>>>
>>>> Apparently the problem was not github being down:
>>>> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.085259-2 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots <https://repository.apache.org/content/repositories/snapshots>): Failed to transfer file https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar> with status code 401 -> [Help 1]
>>>> Suggestions?
>>>>
>>>>> On Jul 13, 2020, at 11:53 AM, apacheroyaleci@gmail.com <ma...@gmail.com> wrote:
>>>>>
>>>>> Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing:
>>>>>
>>>>> Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/16/ <http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/16/> to view the results.
>>>>
>>>
>>
>
RE: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still
Failing!
Posted by Yishay Weiss <yi...@hotmail.com>.
I don’t remember. Can you link the discussion from the archives?
From: Harbs<ma...@gmail.com>
Sent: Monday, July 13, 2020 12:47 PM
To: Apache Royale Development<ma...@royale.apache.org>
Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!
There was a discussion on April 28, but I did not follow what you did.
Did you release the compiler-build-tools from your local machine or from the CI server?
> On Jul 13, 2020, at 12:26 PM, Yishay Weiss <yi...@hotmail.com> wrote:
>
> Based on
>
> cat C:\Users\ApacheRoyaleCI\.m2\settings.xml
>
> <?xml version="1.0" encoding="UTF-8"?>
> <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
> https://maven.apache.org/xsd/settings-1.0.0.xsd">
> <servers>
> <server>
> <id>apache.releases.https</id>
> <username>${rm.username}</username>
> <password>${rm.password}</password>
> </server>
> <server>
> <id>apache.snapshots.https</id>
> <username>${rm.username}</username>
> <password>${rm.password}</password>
> </server>
> </servers>
> </settings>
>
> there should be some command line params for rm.username and rm.password being passed as command line arguments. I may be missing something. I’ve sort of run out of time for the next few hours so it may be best to wait for Alex.
>
> From: Yishay Weiss<ma...@hotmail.com>
> Sent: Monday, July 13, 2020 12:10 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: RE: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!
>
> Good question. Let me see if I can figure this out.
>
> From: Harbs<ma...@gmail.com>
> Sent: Monday, July 13, 2020 12:05 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!
>
> Where am I supposed to put credential into the jenkins server?
>
>> On Jul 13, 2020, at 12:02 PM, Yishay Weiss <yi...@hotmail.com> wrote:
>>
>> Are you sure it’s not an Apache credentials problem? Last time I looked it looked like you were getting 401 from the server.
>>
>> From: Harbs<ma...@gmail.com>
>> Sent: Monday, July 13, 2020 11:58 AM
>> To: dev@royale.apache.org<ma...@royale.apache.org>
>> Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!
>>
>> Or maybe the issue is a few lines up?
>> [INFO] [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ compiler-build-tools ---
>> [INFO] [INFO] Downloading from apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml>
>> [INFO] [INFO] Downloaded from apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml> (796 B at 699 B/s)
>> [INFO] [INFO] Uploading to apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar>
>> [INFO] [INFO] Uploading to apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.pom <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.pom>
>> [INFO] [INFO] ------------------------------------------------------------------------
>> [INFO] [INFO] BUILD FAILURE
>> [INFO] [INFO] ------------------------------------------------------------------------
>> [INFO] [INFO] Total time: 54.801 s
>> [INFO] [INFO] Finished at: 2020-07-13T08:53:02Z
>> [INFO] [INFO] ------------------------------------------------------------------------
>> [INFO] [WARNING] The requested profile "pom.xml" could not be activated because it does not exist.
>> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.085259-2 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots <https://repository.apache.org/content/repositories/snapshots>): Failed to transfer file https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar> with status code 401 -> [Help 1]
>> Links 3 and 4 are not valid.
>>
>>> On Jul 13, 2020, at 11:54 AM, Harbs <ha...@gmail.com> wrote:
>>>
>>> Apparently the problem was not github being down:
>>> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.085259-2 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots <https://repository.apache.org/content/repositories/snapshots>): Failed to transfer file https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar> with status code 401 -> [Help 1]
>>> Suggestions?
>>>
>>>> On Jul 13, 2020, at 11:53 AM, apacheroyaleci@gmail.com <ma...@gmail.com> wrote:
>>>>
>>>> Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing:
>>>>
>>>> Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/16/ <http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/16/> to view the results.
>>>
>>
>
Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still
Failing!
Posted by Harbs <ha...@gmail.com>.
There was a discussion on April 28, but I did not follow what you did.
Did you release the compiler-build-tools from your local machine or from the CI server?
> On Jul 13, 2020, at 12:26 PM, Yishay Weiss <yi...@hotmail.com> wrote:
>
> Based on
>
> cat C:\Users\ApacheRoyaleCI\.m2\settings.xml
>
> <?xml version="1.0" encoding="UTF-8"?>
> <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
> https://maven.apache.org/xsd/settings-1.0.0.xsd">
> <servers>
> <server>
> <id>apache.releases.https</id>
> <username>${rm.username}</username>
> <password>${rm.password}</password>
> </server>
> <server>
> <id>apache.snapshots.https</id>
> <username>${rm.username}</username>
> <password>${rm.password}</password>
> </server>
> </servers>
> </settings>
>
> there should be some command line params for rm.username and rm.password being passed as command line arguments. I may be missing something. I’ve sort of run out of time for the next few hours so it may be best to wait for Alex.
>
> From: Yishay Weiss<ma...@hotmail.com>
> Sent: Monday, July 13, 2020 12:10 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: RE: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!
>
> Good question. Let me see if I can figure this out.
>
> From: Harbs<ma...@gmail.com>
> Sent: Monday, July 13, 2020 12:05 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!
>
> Where am I supposed to put credential into the jenkins server?
>
>> On Jul 13, 2020, at 12:02 PM, Yishay Weiss <yi...@hotmail.com> wrote:
>>
>> Are you sure it’s not an Apache credentials problem? Last time I looked it looked like you were getting 401 from the server.
>>
>> From: Harbs<ma...@gmail.com>
>> Sent: Monday, July 13, 2020 11:58 AM
>> To: dev@royale.apache.org<ma...@royale.apache.org>
>> Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!
>>
>> Or maybe the issue is a few lines up?
>> [INFO] [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ compiler-build-tools ---
>> [INFO] [INFO] Downloading from apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml>
>> [INFO] [INFO] Downloaded from apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml> (796 B at 699 B/s)
>> [INFO] [INFO] Uploading to apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar>
>> [INFO] [INFO] Uploading to apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.pom <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.pom>
>> [INFO] [INFO] ------------------------------------------------------------------------
>> [INFO] [INFO] BUILD FAILURE
>> [INFO] [INFO] ------------------------------------------------------------------------
>> [INFO] [INFO] Total time: 54.801 s
>> [INFO] [INFO] Finished at: 2020-07-13T08:53:02Z
>> [INFO] [INFO] ------------------------------------------------------------------------
>> [INFO] [WARNING] The requested profile "pom.xml" could not be activated because it does not exist.
>> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.085259-2 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots <https://repository.apache.org/content/repositories/snapshots>): Failed to transfer file https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar> with status code 401 -> [Help 1]
>> Links 3 and 4 are not valid.
>>
>>> On Jul 13, 2020, at 11:54 AM, Harbs <ha...@gmail.com> wrote:
>>>
>>> Apparently the problem was not github being down:
>>> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.085259-2 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots <https://repository.apache.org/content/repositories/snapshots>): Failed to transfer file https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar> with status code 401 -> [Help 1]
>>> Suggestions?
>>>
>>>> On Jul 13, 2020, at 11:53 AM, apacheroyaleci@gmail.com <ma...@gmail.com> wrote:
>>>>
>>>> Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing:
>>>>
>>>> Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/16/ <http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/16/> to view the results.
>>>
>>
>
RE: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still
Failing!
Posted by Yishay Weiss <yi...@hotmail.com>.
Based on
cat C:\Users\ApacheRoyaleCI\.m2\settings.xml
<?xml version="1.0" encoding="UTF-8"?>
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
https://maven.apache.org/xsd/settings-1.0.0.xsd">
<servers>
<server>
<id>apache.releases.https</id>
<username>${rm.username}</username>
<password>${rm.password}</password>
</server>
<server>
<id>apache.snapshots.https</id>
<username>${rm.username}</username>
<password>${rm.password}</password>
</server>
</servers>
</settings>
there should be some command line params for rm.username and rm.password being passed as command line arguments. I may be missing something. I’ve sort of run out of time for the next few hours so it may be best to wait for Alex.
From: Yishay Weiss<ma...@hotmail.com>
Sent: Monday, July 13, 2020 12:10 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: RE: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!
Good question. Let me see if I can figure this out.
From: Harbs<ma...@gmail.com>
Sent: Monday, July 13, 2020 12:05 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!
Where am I supposed to put credential into the jenkins server?
> On Jul 13, 2020, at 12:02 PM, Yishay Weiss <yi...@hotmail.com> wrote:
>
> Are you sure it’s not an Apache credentials problem? Last time I looked it looked like you were getting 401 from the server.
>
> From: Harbs<ma...@gmail.com>
> Sent: Monday, July 13, 2020 11:58 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!
>
> Or maybe the issue is a few lines up?
> [INFO] [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ compiler-build-tools ---
> [INFO] [INFO] Downloading from apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml>
> [INFO] [INFO] Downloaded from apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml> (796 B at 699 B/s)
> [INFO] [INFO] Uploading to apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar>
> [INFO] [INFO] Uploading to apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.pom <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.pom>
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Total time: 54.801 s
> [INFO] [INFO] Finished at: 2020-07-13T08:53:02Z
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [WARNING] The requested profile "pom.xml" could not be activated because it does not exist.
> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.085259-2 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots <https://repository.apache.org/content/repositories/snapshots>): Failed to transfer file https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar> with status code 401 -> [Help 1]
> Links 3 and 4 are not valid.
>
>> On Jul 13, 2020, at 11:54 AM, Harbs <ha...@gmail.com> wrote:
>>
>> Apparently the problem was not github being down:
>> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.085259-2 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots <https://repository.apache.org/content/repositories/snapshots>): Failed to transfer file https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar> with status code 401 -> [Help 1]
>> Suggestions?
>>
>>> On Jul 13, 2020, at 11:53 AM, apacheroyaleci@gmail.com <ma...@gmail.com> wrote:
>>>
>>> Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing:
>>>
>>> Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/16/ <http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/16/> to view the results.
>>
>
RE: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still
Failing!
Posted by Yishay Weiss <yi...@hotmail.com>.
Good question. Let me see if I can figure this out.
From: Harbs<ma...@gmail.com>
Sent: Monday, July 13, 2020 12:05 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!
Where am I supposed to put credential into the jenkins server?
> On Jul 13, 2020, at 12:02 PM, Yishay Weiss <yi...@hotmail.com> wrote:
>
> Are you sure it’s not an Apache credentials problem? Last time I looked it looked like you were getting 401 from the server.
>
> From: Harbs<ma...@gmail.com>
> Sent: Monday, July 13, 2020 11:58 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!
>
> Or maybe the issue is a few lines up?
> [INFO] [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ compiler-build-tools ---
> [INFO] [INFO] Downloading from apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml>
> [INFO] [INFO] Downloaded from apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml> (796 B at 699 B/s)
> [INFO] [INFO] Uploading to apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar>
> [INFO] [INFO] Uploading to apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.pom <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.pom>
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Total time: 54.801 s
> [INFO] [INFO] Finished at: 2020-07-13T08:53:02Z
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [WARNING] The requested profile "pom.xml" could not be activated because it does not exist.
> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.085259-2 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots <https://repository.apache.org/content/repositories/snapshots>): Failed to transfer file https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar> with status code 401 -> [Help 1]
> Links 3 and 4 are not valid.
>
>> On Jul 13, 2020, at 11:54 AM, Harbs <ha...@gmail.com> wrote:
>>
>> Apparently the problem was not github being down:
>> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.085259-2 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots <https://repository.apache.org/content/repositories/snapshots>): Failed to transfer file https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar> with status code 401 -> [Help 1]
>> Suggestions?
>>
>>> On Jul 13, 2020, at 11:53 AM, apacheroyaleci@gmail.com <ma...@gmail.com> wrote:
>>>
>>> Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing:
>>>
>>> Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/16/ <http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/16/> to view the results.
>>
>
Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still
Failing!
Posted by Harbs <ha...@gmail.com>.
Where am I supposed to put credential into the jenkins server?
> On Jul 13, 2020, at 12:02 PM, Yishay Weiss <yi...@hotmail.com> wrote:
>
> Are you sure it’s not an Apache credentials problem? Last time I looked it looked like you were getting 401 from the server.
>
> From: Harbs<ma...@gmail.com>
> Sent: Monday, July 13, 2020 11:58 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!
>
> Or maybe the issue is a few lines up?
> [INFO] [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ compiler-build-tools ---
> [INFO] [INFO] Downloading from apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml>
> [INFO] [INFO] Downloaded from apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml> (796 B at 699 B/s)
> [INFO] [INFO] Uploading to apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar>
> [INFO] [INFO] Uploading to apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.pom <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.pom>
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Total time: 54.801 s
> [INFO] [INFO] Finished at: 2020-07-13T08:53:02Z
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [WARNING] The requested profile "pom.xml" could not be activated because it does not exist.
> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.085259-2 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots <https://repository.apache.org/content/repositories/snapshots>): Failed to transfer file https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar> with status code 401 -> [Help 1]
> Links 3 and 4 are not valid.
>
>> On Jul 13, 2020, at 11:54 AM, Harbs <ha...@gmail.com> wrote:
>>
>> Apparently the problem was not github being down:
>> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.085259-2 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots <https://repository.apache.org/content/repositories/snapshots>): Failed to transfer file https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar> with status code 401 -> [Help 1]
>> Suggestions?
>>
>>> On Jul 13, 2020, at 11:53 AM, apacheroyaleci@gmail.com <ma...@gmail.com> wrote:
>>>
>>> Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing:
>>>
>>> Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/16/ <http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/16/> to view the results.
>>
>
RE: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still
Failing!
Posted by Yishay Weiss <yi...@hotmail.com>.
Are you sure it’s not an Apache credentials problem? Last time I looked it looked like you were getting 401 from the server.
From: Harbs<ma...@gmail.com>
Sent: Monday, July 13, 2020 11:58 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!
Or maybe the issue is a few lines up?
[INFO] [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ compiler-build-tools ---
[INFO] [INFO] Downloading from apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml>
[INFO] [INFO] Downloaded from apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml> (796 B at 699 B/s)
[INFO] [INFO] Uploading to apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar>
[INFO] [INFO] Uploading to apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.pom <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.pom>
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] BUILD FAILURE
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Total time: 54.801 s
[INFO] [INFO] Finished at: 2020-07-13T08:53:02Z
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [WARNING] The requested profile "pom.xml" could not be activated because it does not exist.
[INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.085259-2 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots <https://repository.apache.org/content/repositories/snapshots>): Failed to transfer file https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar> with status code 401 -> [Help 1]
Links 3 and 4 are not valid.
> On Jul 13, 2020, at 11:54 AM, Harbs <ha...@gmail.com> wrote:
>
> Apparently the problem was not github being down:
> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.085259-2 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots <https://repository.apache.org/content/repositories/snapshots>): Failed to transfer file https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar> with status code 401 -> [Help 1]
> Suggestions?
>
>> On Jul 13, 2020, at 11:53 AM, apacheroyaleci@gmail.com <ma...@gmail.com> wrote:
>>
>> Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing:
>>
>> Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/16/ <http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/16/> to view the results.
>
Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still
Failing!
Posted by Harbs <ha...@gmail.com>.
Or maybe the issue is a few lines up?
[INFO] [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ compiler-build-tools ---
[INFO] [INFO] Downloading from apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml>
[INFO] [INFO] Downloaded from apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/maven-metadata.xml> (796 B at 699 B/s)
[INFO] [INFO] Uploading to apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar>
[INFO] [INFO] Uploading to apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.pom <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.pom>
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] BUILD FAILURE
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Total time: 54.801 s
[INFO] [INFO] Finished at: 2020-07-13T08:53:02Z
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [WARNING] The requested profile "pom.xml" could not be activated because it does not exist.
[INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.085259-2 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots <https://repository.apache.org/content/repositories/snapshots>): Failed to transfer file https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar> with status code 401 -> [Help 1]
Links 3 and 4 are not valid.
> On Jul 13, 2020, at 11:54 AM, Harbs <ha...@gmail.com> wrote:
>
> Apparently the problem was not github being down:
> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.085259-2 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots <https://repository.apache.org/content/repositories/snapshots>): Failed to transfer file https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar> with status code 401 -> [Help 1]
> Suggestions?
>
>> On Jul 13, 2020, at 11:53 AM, apacheroyaleci@gmail.com <ma...@gmail.com> wrote:
>>
>> Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing:
>>
>> Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/16/ <http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/16/> to view the results.
>
Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still
Failing!
Posted by Harbs <ha...@gmail.com>.
Apparently the problem was not github being down:
[INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.085259-2 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots <https://repository.apache.org/content/repositories/snapshots>): Failed to transfer file https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.085259-2.jar> with status code 401 -> [Help 1]
Suggestions?
> On Jul 13, 2020, at 11:53 AM, apacheroyaleci@gmail.com wrote:
>
> Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing:
>
> Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/16/ to view the results.
Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still
Failing!
Posted by ap...@gmail.com.
Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing:
Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/16/ to view the results.
Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still
Failing!
Posted by Christofer Dutz <ch...@c-ware.de>.
The Date-Versions you are seeing is how a SNAPSHOT is usually stored on a remote repository.
If you have a look at the content every new snapshot will be added to the remaining and each will have a different date and a counter at the end.
Maven uses this to detect if there is a newer version to fetch.
Chris
Am 13.07.20, 18:22 schrieb "Alex Harui" <ah...@adobe.com.INVALID>:
IMO, step 1 went sideways. The tag should not contain SNAPSHOT in the POM version. Compare the tag from 1.2.0.
Maven should also not be adding a timestamp to the artifact name. I don't remember why it does that, but I think there are internet articles about it.
Comparing output of successful jobs might shed some light on where things are going wrong.
HTH,
-Alex
On 7/13/20, 12:41 AM, "Harbs" <ha...@gmail.com> wrote:
It’s still having issues:
[INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.073309-2 from/to apache.snapshots.https (https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7C57ec6dcc28f446417ec108d8270015c5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302228604622818&sdata=3uslr50%2FZJnWgUddP%2Ffu%2FouYdB2ia8UeoH5oldtyqy0%3D&reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7C57ec6dcc28f446417ec108d8270015c5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302228604632779&sdata=UI3JrHWVEYwoDIUlpN26%2FsStLHRJi2zIhL0aCoocA%2FY%3D&reserved=0>): Failed to transfer file https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.073309-2.jar&data=02%7C01%7Caharui%40adobe.com%7C57ec6dcc28f446417ec108d8270015c5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302228604632779&sdata=n2oNYMf%2F0Nw2OxbdvM9gHo47yHVhqwlJKIC%2Bive0IA8%3D&reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.073309-2.jar&data=02%7C01%7Caharui%40adobe.com%7C57ec6dcc28f446417ec108d8270015c5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302228604632779&sdata=n2oNYMf%2F0Nw2OxbdvM9gHo47yHVhqwlJKIC%2Bive0IA8%3D&reserved=0> with status code 401 -> [Help 1]
I’m kind of stuck on this. Any suggestions would help.
Thanks.
> On Jul 13, 2020, at 10:33 AM, apacheroyaleci@gmail.com wrote:
>
> Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing:
>
> Check console output at https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Compiler_Build_Tools_Release_Step_002%2F15%2F&data=02%7C01%7Caharui%40adobe.com%7C57ec6dcc28f446417ec108d8270015c5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302228604632779&sdata=g%2BSNOJsTRBcSUTLMgKHAuX07aq4lnP0atrQUERXkStI%3D&reserved=0 to view the results.
Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still
Failing!
Posted by Alex Harui <ah...@adobe.com.INVALID>.
On 7/13/20, 9:51 PM, "Yishay Weiss" <yi...@hotmail.com> wrote:
I don’t recall removing credentials the CI server. The last successful build [2] shows I was the one who performed that step. One thing I couldn’t understand was how come these lines have my name in them [1]. Where does yishayw get retrieved from?
I didn't look to carefully, but some Release Steps jobs do ask for Github username.
HTH,
-Alex
[INFO] fetch url: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fyishayw%40gitbox.apache.org%2Frepos%2Fasf%2Froyale-compiler.git&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=cUo9%2F33M4SatU1m17xSuem08x4CkDCIMbRryPOYNvq4%3D&reserved=0
[INFO] push url: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fyishayw%40gitbox.apache.org%2Frepos%2Fasf%2Froyale-compiler.git&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=cUo9%2F33M4SatU1m17xSuem08x4CkDCIMbRryPOYNvq4%3D&reserved=0
[2] https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Compiler_Build_Tools_Release_Step_002%2FlastSuccessfulBuild%2Fconsole&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=Z3OkzFb65IgqJAPzzpbwTZ7fzk9jA0iOI5ID8FXq2zU%3D&reserved=0
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Monday, July 13, 2020 8:25 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing!
On 7/13/20, 9:32 AM, "Harbs" <ha...@gmail.com> wrote:
I’m trying to wrap my head around all the pieces here.
How does the uploading to the nexus server work?
It doesn't. After some snooping through the archives, I think that some credentials were (unsafely) stored on the CI Server. The archives indicate that after build-tools was released, we tried another way of setting credentials for the main Royale build and that resulted in build-tools not being able to directly upload to nexus anymore. Of course, I could be misreading the archives.
The main Royale release prevents the upload and the RM downloads the build results, verifies them, and uploads them. Someone would have to replicate that for build-tools.
Other options are:
A) to run Maven on CI and try the new Ant script that hides passwords that Yishay created
B) Run the build locally.
HTH,
-Alex
> On Jul 13, 2020, at 7:21 PM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>
> IMO, step 1 went sideways. The tag should not contain SNAPSHOT in the POM version. Compare the tag from 1.2.0.
>
> Maven should also not be adding a timestamp to the artifact name. I don't remember why it does that, but I think there are internet articles about it.
>
> Comparing output of successful jobs might shed some light on where things are going wrong.
>
> HTH,
> -Alex
>
> On 7/13/20, 12:41 AM, "Harbs" <ha...@gmail.com> wrote:
>
> It’s still having issues:
>
> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.073309-2 from/to apache.snapshots.https (https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=i%2FOkZOey8GSPknCmBV5wPtugIj3GFRHBd4EqhoeVHaw%3D&reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=i%2FOkZOey8GSPknCmBV5wPtugIj3GFRHBd4EqhoeVHaw%3D&reserved=0>): Failed to transfer file https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.073309-2.jar&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=2QojWSMN1QzB1wGyXNr8d15fN7ah7%2FXinHtV8qbYSwc%3D&reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.073309-2.jar&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=2QojWSMN1QzB1wGyXNr8d15fN7ah7%2FXinHtV8qbYSwc%3D&reserved=0> with status code 401 -> [Help 1]
>
> I’m kind of stuck on this. Any suggestions would help.
>
> Thanks.
>
>> On Jul 13, 2020, at 10:33 AM, apacheroyaleci@gmail.com wrote:
>>
>> Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing:
>>
>> Check console output at https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Compiler_Build_Tools_Release_Step_002%2F15%2F&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=A6xf6qyGH0s35rSUDbDx2wHWuwvdv0vBsGkIz48V%2F2Y%3D&reserved=0 to view the results.
>
>
>
RE: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still
Failing!
Posted by Yishay Weiss <yi...@hotmail.com>.
I’ve used mask passwords successfully on some dummy password. I didn’t want to test with my real Apache credentials so I don’t accidentally complete the step successfully with my user. Harbs, let me know if this is working for you. Thanks.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Tuesday, July 14, 2020 10:34 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing!
I guess it depends on the definition of "trivial". I'm not sure if the Maven runner does a whole bunch of stuff or not that couldn't be done in a script. Looking at the console output, it looks like it just runs "mvn". Some of the current jobs do use a script for other things if you want a starting point for a script.
On the other hand, I found this: https://plugins.jenkins.io/mask-passwords/
Maybe that will work.
I'm done for tonight. Good luck,
-Alex
On 7/14/20, 12:23 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>But we haven't tried passing in a password from Jenkins into Maven.
I’m not sure it’s possible to do trivially. These guys [1] want us to create a script snippet, but as I understand it we’re not using a script to invoke Maven.
[1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport.cloudbees.com%2Fhc%2Fen-us%2Farticles%2F203802500-Injecting-Secrets-into-Jenkins-Build-Jobs&data=02%7C01%7Caharui%40adobe.com%7Ca58254b69ccf41502fb108d827c6cfe8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637303082135753042&sdata=X9RYMm4Jd7iRdagCyTC01EXtfnOcz3BW%2F007ksYXqUQ%3D&reserved=0
On 7/13/20, 9:51 PM, "Yishay Weiss" <yi...@hotmail.com> wrote:
I don’t recall removing credentials the CI server. The last successful build [2] shows I was the one who performed that step. One thing I couldn’t understand was how come these lines have my name in them [1]. Where does yishayw get retrieved from?
[INFO] fetch url: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fyishayw%40gitbox.apache.org%2Frepos%2Fasf%2Froyale-compiler.git&data=02%7C01%7Caharui%40adobe.com%7Ca58254b69ccf41502fb108d827c6cfe8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637303082135753042&sdata=sljIairDHFp1cWbtM2N8rujQ15r2BSSxCMMVJmnXxs4%3D&reserved=0
[INFO] push url: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fyishayw%40gitbox.apache.org%2Frepos%2Fasf%2Froyale-compiler.git&data=02%7C01%7Caharui%40adobe.com%7Ca58254b69ccf41502fb108d827c6cfe8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637303082135763030&sdata=rvg8Z8oEcIbjPp32c5QyWkV6k6AKjmrM%2BJAPZw%2FiOaA%3D&reserved=0
[2] https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Compiler_Build_Tools_Release_Step_002%2FlastSuccessfulBuild%2Fconsole&data=02%7C01%7Caharui%40adobe.com%7Ca58254b69ccf41502fb108d827c6cfe8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637303082135763030&sdata=wMGekpW2aORwIDZ3iOY7g0kWgOZDVfHyBH%2Fdh%2FSEsRo%3D&reserved=0
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Monday, July 13, 2020 8:25 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing!
On 7/13/20, 9:32 AM, "Harbs" <ha...@gmail.com> wrote:
I’m trying to wrap my head around all the pieces here.
How does the uploading to the nexus server work?
It doesn't. After some snooping through the archives, I think that some credentials were (unsafely) stored on the CI Server. The archives indicate that after build-tools was released, we tried another way of setting credentials for the main Royale build and that resulted in build-tools not being able to directly upload to nexus anymore. Of course, I could be misreading the archives.
The main Royale release prevents the upload and the RM downloads the build results, verifies them, and uploads them. Someone would have to replicate that for build-tools.
Other options are:
A) to run Maven on CI and try the new Ant script that hides passwords that Yishay created
B) Run the build locally.
HTH,
-Alex
> On Jul 13, 2020, at 7:21 PM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>
> IMO, step 1 went sideways. The tag should not contain SNAPSHOT in the POM version. Compare the tag from 1.2.0.
>
> Maven should also not be adding a timestamp to the artifact name. I don't remember why it does that, but I think there are internet articles about it.
>
> Comparing output of successful jobs might shed some light on where things are going wrong.
>
> HTH,
> -Alex
>
> On 7/13/20, 12:41 AM, "Harbs" <ha...@gmail.com> wrote:
>
> It’s still having issues:
>
> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.073309-2 from/to apache.snapshots.https (https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7Ca58254b69ccf41502fb108d827c6cfe8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637303082135763030&sdata=GGqxC6G%2FNcGJqjkJgxvH1Yhmq0hWdIpx%2BFHBNJIBAew%3D&reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7Ca58254b69ccf41502fb108d827c6cfe8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637303082135763030&sdata=GGqxC6G%2FNcGJqjkJgxvH1Yhmq0hWdIpx%2BFHBNJIBAew%3D&reserved=0>): Failed to transfer file https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.073309-2.jar&data=02%7C01%7Caharui%40adobe.com%7Ca58254b69ccf41502fb108d827c6cfe8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637303082135763030&sdata=%2Fpo3WE8CbWq7K824N6cjc9BSIcNL36N8SAJzMIQ4QjY%3D&reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.073309-2.jar&data=02%7C01%7Caharui%40adobe.com%7Ca58254b69ccf41502fb108d827c6cfe8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637303082135763030&sdata=%2Fpo3WE8CbWq7K824N6cjc9BSIcNL36N8SAJzMIQ4QjY%3D&reserved=0> with status code 401 -> [Help 1]
>
> I’m kind of stuck on this. Any suggestions would help.
>
> Thanks.
>
>> On Jul 13, 2020, at 10:33 AM, apacheroyaleci@gmail.com wrote:
>>
>> Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing:
>>
>> Check console output at https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Compiler_Build_Tools_Release_Step_002%2F15%2F&data=02%7C01%7Caharui%40adobe.com%7Ca58254b69ccf41502fb108d827c6cfe8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637303082135763030&sdata=fQReWVWqZEfIJB909eB%2By96%2BgOo9PFZLXoOfloDxj9U%3D&reserved=0 to view the results.
>
>
>
Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still
Failing!
Posted by Alex Harui <ah...@adobe.com.INVALID>.
I guess it depends on the definition of "trivial". I'm not sure if the Maven runner does a whole bunch of stuff or not that couldn't be done in a script. Looking at the console output, it looks like it just runs "mvn". Some of the current jobs do use a script for other things if you want a starting point for a script.
On the other hand, I found this: https://plugins.jenkins.io/mask-passwords/
Maybe that will work.
I'm done for tonight. Good luck,
-Alex
On 7/14/20, 12:23 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>But we haven't tried passing in a password from Jenkins into Maven.
I’m not sure it’s possible to do trivially. These guys [1] want us to create a script snippet, but as I understand it we’re not using a script to invoke Maven.
[1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport.cloudbees.com%2Fhc%2Fen-us%2Farticles%2F203802500-Injecting-Secrets-into-Jenkins-Build-Jobs&data=02%7C01%7Caharui%40adobe.com%7Ca58254b69ccf41502fb108d827c6cfe8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637303082135753042&sdata=X9RYMm4Jd7iRdagCyTC01EXtfnOcz3BW%2F007ksYXqUQ%3D&reserved=0
On 7/13/20, 9:51 PM, "Yishay Weiss" <yi...@hotmail.com> wrote:
I don’t recall removing credentials the CI server. The last successful build [2] shows I was the one who performed that step. One thing I couldn’t understand was how come these lines have my name in them [1]. Where does yishayw get retrieved from?
[INFO] fetch url: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fyishayw%40gitbox.apache.org%2Frepos%2Fasf%2Froyale-compiler.git&data=02%7C01%7Caharui%40adobe.com%7Ca58254b69ccf41502fb108d827c6cfe8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637303082135753042&sdata=sljIairDHFp1cWbtM2N8rujQ15r2BSSxCMMVJmnXxs4%3D&reserved=0
[INFO] push url: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fyishayw%40gitbox.apache.org%2Frepos%2Fasf%2Froyale-compiler.git&data=02%7C01%7Caharui%40adobe.com%7Ca58254b69ccf41502fb108d827c6cfe8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637303082135763030&sdata=rvg8Z8oEcIbjPp32c5QyWkV6k6AKjmrM%2BJAPZw%2FiOaA%3D&reserved=0
[2] https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Compiler_Build_Tools_Release_Step_002%2FlastSuccessfulBuild%2Fconsole&data=02%7C01%7Caharui%40adobe.com%7Ca58254b69ccf41502fb108d827c6cfe8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637303082135763030&sdata=wMGekpW2aORwIDZ3iOY7g0kWgOZDVfHyBH%2Fdh%2FSEsRo%3D&reserved=0
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Monday, July 13, 2020 8:25 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing!
On 7/13/20, 9:32 AM, "Harbs" <ha...@gmail.com> wrote:
I’m trying to wrap my head around all the pieces here.
How does the uploading to the nexus server work?
It doesn't. After some snooping through the archives, I think that some credentials were (unsafely) stored on the CI Server. The archives indicate that after build-tools was released, we tried another way of setting credentials for the main Royale build and that resulted in build-tools not being able to directly upload to nexus anymore. Of course, I could be misreading the archives.
The main Royale release prevents the upload and the RM downloads the build results, verifies them, and uploads them. Someone would have to replicate that for build-tools.
Other options are:
A) to run Maven on CI and try the new Ant script that hides passwords that Yishay created
B) Run the build locally.
HTH,
-Alex
> On Jul 13, 2020, at 7:21 PM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>
> IMO, step 1 went sideways. The tag should not contain SNAPSHOT in the POM version. Compare the tag from 1.2.0.
>
> Maven should also not be adding a timestamp to the artifact name. I don't remember why it does that, but I think there are internet articles about it.
>
> Comparing output of successful jobs might shed some light on where things are going wrong.
>
> HTH,
> -Alex
>
> On 7/13/20, 12:41 AM, "Harbs" <ha...@gmail.com> wrote:
>
> It’s still having issues:
>
> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.073309-2 from/to apache.snapshots.https (https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7Ca58254b69ccf41502fb108d827c6cfe8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637303082135763030&sdata=GGqxC6G%2FNcGJqjkJgxvH1Yhmq0hWdIpx%2BFHBNJIBAew%3D&reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7Ca58254b69ccf41502fb108d827c6cfe8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637303082135763030&sdata=GGqxC6G%2FNcGJqjkJgxvH1Yhmq0hWdIpx%2BFHBNJIBAew%3D&reserved=0>): Failed to transfer file https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.073309-2.jar&data=02%7C01%7Caharui%40adobe.com%7Ca58254b69ccf41502fb108d827c6cfe8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637303082135763030&sdata=%2Fpo3WE8CbWq7K824N6cjc9BSIcNL36N8SAJzMIQ4QjY%3D&reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.073309-2.jar&data=02%7C01%7Caharui%40adobe.com%7Ca58254b69ccf41502fb108d827c6cfe8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637303082135763030&sdata=%2Fpo3WE8CbWq7K824N6cjc9BSIcNL36N8SAJzMIQ4QjY%3D&reserved=0> with status code 401 -> [Help 1]
>
> I’m kind of stuck on this. Any suggestions would help.
>
> Thanks.
>
>> On Jul 13, 2020, at 10:33 AM, apacheroyaleci@gmail.com wrote:
>>
>> Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing:
>>
>> Check console output at https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Compiler_Build_Tools_Release_Step_002%2F15%2F&data=02%7C01%7Caharui%40adobe.com%7Ca58254b69ccf41502fb108d827c6cfe8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637303082135763030&sdata=fQReWVWqZEfIJB909eB%2By96%2BgOo9PFZLXoOfloDxj9U%3D&reserved=0 to view the results.
>
>
>
RE: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still
Failing!
Posted by Yishay Weiss <yi...@hotmail.com>.
>But we haven't tried passing in a password from Jenkins into Maven.
I’m not sure it’s possible to do trivially. These guys [1] want us to create a script snippet, but as I understand it we’re not using a script to invoke Maven.
[1] https://support.cloudbees.com/hc/en-us/articles/203802500-Injecting-Secrets-into-Jenkins-Build-Jobs
On 7/13/20, 9:51 PM, "Yishay Weiss" <yi...@hotmail.com> wrote:
I don’t recall removing credentials the CI server. The last successful build [2] shows I was the one who performed that step. One thing I couldn’t understand was how come these lines have my name in them [1]. Where does yishayw get retrieved from?
[INFO] fetch url: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fyishayw%40gitbox.apache.org%2Frepos%2Fasf%2Froyale-compiler.git&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=cUo9%2F33M4SatU1m17xSuem08x4CkDCIMbRryPOYNvq4%3D&reserved=0
[INFO] push url: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fyishayw%40gitbox.apache.org%2Frepos%2Fasf%2Froyale-compiler.git&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=cUo9%2F33M4SatU1m17xSuem08x4CkDCIMbRryPOYNvq4%3D&reserved=0
[2] https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Compiler_Build_Tools_Release_Step_002%2FlastSuccessfulBuild%2Fconsole&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=Z3OkzFb65IgqJAPzzpbwTZ7fzk9jA0iOI5ID8FXq2zU%3D&reserved=0
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Monday, July 13, 2020 8:25 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing!
On 7/13/20, 9:32 AM, "Harbs" <ha...@gmail.com> wrote:
I’m trying to wrap my head around all the pieces here.
How does the uploading to the nexus server work?
It doesn't. After some snooping through the archives, I think that some credentials were (unsafely) stored on the CI Server. The archives indicate that after build-tools was released, we tried another way of setting credentials for the main Royale build and that resulted in build-tools not being able to directly upload to nexus anymore. Of course, I could be misreading the archives.
The main Royale release prevents the upload and the RM downloads the build results, verifies them, and uploads them. Someone would have to replicate that for build-tools.
Other options are:
A) to run Maven on CI and try the new Ant script that hides passwords that Yishay created
B) Run the build locally.
HTH,
-Alex
> On Jul 13, 2020, at 7:21 PM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>
> IMO, step 1 went sideways. The tag should not contain SNAPSHOT in the POM version. Compare the tag from 1.2.0.
>
> Maven should also not be adding a timestamp to the artifact name. I don't remember why it does that, but I think there are internet articles about it.
>
> Comparing output of successful jobs might shed some light on where things are going wrong.
>
> HTH,
> -Alex
>
> On 7/13/20, 12:41 AM, "Harbs" <ha...@gmail.com> wrote:
>
> It’s still having issues:
>
> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.073309-2 from/to apache.snapshots.https (https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=i%2FOkZOey8GSPknCmBV5wPtugIj3GFRHBd4EqhoeVHaw%3D&reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=i%2FOkZOey8GSPknCmBV5wPtugIj3GFRHBd4EqhoeVHaw%3D&reserved=0>): Failed to transfer file https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.073309-2.jar&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=2QojWSMN1QzB1wGyXNr8d15fN7ah7%2FXinHtV8qbYSwc%3D&reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.073309-2.jar&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=2QojWSMN1QzB1wGyXNr8d15fN7ah7%2FXinHtV8qbYSwc%3D&reserved=0> with status code 401 -> [Help 1]
>
> I’m kind of stuck on this. Any suggestions would help.
>
> Thanks.
>
>> On Jul 13, 2020, at 10:33 AM, apacheroyaleci@gmail.com wrote:
>>
>> Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing:
>>
>> Check console output at https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Compiler_Build_Tools_Release_Step_002%2F15%2F&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=A6xf6qyGH0s35rSUDbDx2wHWuwvdv0vBsGkIz48V%2F2Y%3D&reserved=0 to view the results.
>
>
>
RE: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still
Failing!
Posted by Yishay Weiss <yi...@hotmail.com>.
Yes, I’m doing some testing with dummy credentials. So expect some more failed release steps…
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Tuesday, July 14, 2020 8:55 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing!
I have a vague recollection of removing credentials. But also, I think the Maven/Nexus credentials might have been stored in a password manager when we last release compiler-build-tools. You may have run Maven from the command line and typed in credentials and they got stored.
Later, we replaced the tokens that result in using the password manager in settings.xml with rm.username and rm.password so we can run Ant jobs on the CI from the command prompt. But we haven't tried passing in a password from Jenkins into Maven. I'd recommend trying on a test job before trying it on these jobs to make sure the credentials don’t end up in the logs.
-Alex
On 7/13/20, 9:51 PM, "Yishay Weiss" <yi...@hotmail.com> wrote:
I don’t recall removing credentials the CI server. The last successful build [2] shows I was the one who performed that step. One thing I couldn’t understand was how come these lines have my name in them [1]. Where does yishayw get retrieved from?
[INFO] fetch url: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fyishayw%40gitbox.apache.org%2Frepos%2Fasf%2Froyale-compiler.git&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=cUo9%2F33M4SatU1m17xSuem08x4CkDCIMbRryPOYNvq4%3D&reserved=0
[INFO] push url: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fyishayw%40gitbox.apache.org%2Frepos%2Fasf%2Froyale-compiler.git&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=cUo9%2F33M4SatU1m17xSuem08x4CkDCIMbRryPOYNvq4%3D&reserved=0
[2] https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Compiler_Build_Tools_Release_Step_002%2FlastSuccessfulBuild%2Fconsole&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=Z3OkzFb65IgqJAPzzpbwTZ7fzk9jA0iOI5ID8FXq2zU%3D&reserved=0
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Monday, July 13, 2020 8:25 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing!
On 7/13/20, 9:32 AM, "Harbs" <ha...@gmail.com> wrote:
I’m trying to wrap my head around all the pieces here.
How does the uploading to the nexus server work?
It doesn't. After some snooping through the archives, I think that some credentials were (unsafely) stored on the CI Server. The archives indicate that after build-tools was released, we tried another way of setting credentials for the main Royale build and that resulted in build-tools not being able to directly upload to nexus anymore. Of course, I could be misreading the archives.
The main Royale release prevents the upload and the RM downloads the build results, verifies them, and uploads them. Someone would have to replicate that for build-tools.
Other options are:
A) to run Maven on CI and try the new Ant script that hides passwords that Yishay created
B) Run the build locally.
HTH,
-Alex
> On Jul 13, 2020, at 7:21 PM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>
> IMO, step 1 went sideways. The tag should not contain SNAPSHOT in the POM version. Compare the tag from 1.2.0.
>
> Maven should also not be adding a timestamp to the artifact name. I don't remember why it does that, but I think there are internet articles about it.
>
> Comparing output of successful jobs might shed some light on where things are going wrong.
>
> HTH,
> -Alex
>
> On 7/13/20, 12:41 AM, "Harbs" <ha...@gmail.com> wrote:
>
> It’s still having issues:
>
> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.073309-2 from/to apache.snapshots.https (https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=i%2FOkZOey8GSPknCmBV5wPtugIj3GFRHBd4EqhoeVHaw%3D&reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=i%2FOkZOey8GSPknCmBV5wPtugIj3GFRHBd4EqhoeVHaw%3D&reserved=0>): Failed to transfer file https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.073309-2.jar&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=2QojWSMN1QzB1wGyXNr8d15fN7ah7%2FXinHtV8qbYSwc%3D&reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.073309-2.jar&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=2QojWSMN1QzB1wGyXNr8d15fN7ah7%2FXinHtV8qbYSwc%3D&reserved=0> with status code 401 -> [Help 1]
>
> I’m kind of stuck on this. Any suggestions would help.
>
> Thanks.
>
>> On Jul 13, 2020, at 10:33 AM, apacheroyaleci@gmail.com wrote:
>>
>> Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing:
>>
>> Check console output at https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Compiler_Build_Tools_Release_Step_002%2F15%2F&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=A6xf6qyGH0s35rSUDbDx2wHWuwvdv0vBsGkIz48V%2F2Y%3D&reserved=0 to view the results.
>
>
>
Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still
Failing!
Posted by Alex Harui <ah...@adobe.com.INVALID>.
I have a vague recollection of removing credentials. But also, I think the Maven/Nexus credentials might have been stored in a password manager when we last release compiler-build-tools. You may have run Maven from the command line and typed in credentials and they got stored.
Later, we replaced the tokens that result in using the password manager in settings.xml with rm.username and rm.password so we can run Ant jobs on the CI from the command prompt. But we haven't tried passing in a password from Jenkins into Maven. I'd recommend trying on a test job before trying it on these jobs to make sure the credentials don’t end up in the logs.
-Alex
On 7/13/20, 9:51 PM, "Yishay Weiss" <yi...@hotmail.com> wrote:
I don’t recall removing credentials the CI server. The last successful build [2] shows I was the one who performed that step. One thing I couldn’t understand was how come these lines have my name in them [1]. Where does yishayw get retrieved from?
[INFO] fetch url: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fyishayw%40gitbox.apache.org%2Frepos%2Fasf%2Froyale-compiler.git&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=cUo9%2F33M4SatU1m17xSuem08x4CkDCIMbRryPOYNvq4%3D&reserved=0
[INFO] push url: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fyishayw%40gitbox.apache.org%2Frepos%2Fasf%2Froyale-compiler.git&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=cUo9%2F33M4SatU1m17xSuem08x4CkDCIMbRryPOYNvq4%3D&reserved=0
[2] https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Compiler_Build_Tools_Release_Step_002%2FlastSuccessfulBuild%2Fconsole&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=Z3OkzFb65IgqJAPzzpbwTZ7fzk9jA0iOI5ID8FXq2zU%3D&reserved=0
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Monday, July 13, 2020 8:25 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing!
On 7/13/20, 9:32 AM, "Harbs" <ha...@gmail.com> wrote:
I’m trying to wrap my head around all the pieces here.
How does the uploading to the nexus server work?
It doesn't. After some snooping through the archives, I think that some credentials were (unsafely) stored on the CI Server. The archives indicate that after build-tools was released, we tried another way of setting credentials for the main Royale build and that resulted in build-tools not being able to directly upload to nexus anymore. Of course, I could be misreading the archives.
The main Royale release prevents the upload and the RM downloads the build results, verifies them, and uploads them. Someone would have to replicate that for build-tools.
Other options are:
A) to run Maven on CI and try the new Ant script that hides passwords that Yishay created
B) Run the build locally.
HTH,
-Alex
> On Jul 13, 2020, at 7:21 PM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>
> IMO, step 1 went sideways. The tag should not contain SNAPSHOT in the POM version. Compare the tag from 1.2.0.
>
> Maven should also not be adding a timestamp to the artifact name. I don't remember why it does that, but I think there are internet articles about it.
>
> Comparing output of successful jobs might shed some light on where things are going wrong.
>
> HTH,
> -Alex
>
> On 7/13/20, 12:41 AM, "Harbs" <ha...@gmail.com> wrote:
>
> It’s still having issues:
>
> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.073309-2 from/to apache.snapshots.https (https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=i%2FOkZOey8GSPknCmBV5wPtugIj3GFRHBd4EqhoeVHaw%3D&reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=i%2FOkZOey8GSPknCmBV5wPtugIj3GFRHBd4EqhoeVHaw%3D&reserved=0>): Failed to transfer file https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.073309-2.jar&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=2QojWSMN1QzB1wGyXNr8d15fN7ah7%2FXinHtV8qbYSwc%3D&reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.073309-2.jar&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=2QojWSMN1QzB1wGyXNr8d15fN7ah7%2FXinHtV8qbYSwc%3D&reserved=0> with status code 401 -> [Help 1]
>
> I’m kind of stuck on this. Any suggestions would help.
>
> Thanks.
>
>> On Jul 13, 2020, at 10:33 AM, apacheroyaleci@gmail.com wrote:
>>
>> Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing:
>>
>> Check console output at https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Compiler_Build_Tools_Release_Step_002%2F15%2F&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=A6xf6qyGH0s35rSUDbDx2wHWuwvdv0vBsGkIz48V%2F2Y%3D&reserved=0 to view the results.
>
>
>
RE: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still
Failing!
Posted by Yishay Weiss <yi...@hotmail.com>.
I don’t recall removing credentials the CI server. The last successful build [2] shows I was the one who performed that step. One thing I couldn’t understand was how come these lines have my name in them [1]. Where does yishayw get retrieved from?
[INFO] fetch url: https://yishayw@gitbox.apache.org/repos/asf/royale-compiler.git
[INFO] push url: https://yishayw@gitbox.apache.org/repos/asf/royale-compiler.git
[2] http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/lastSuccessfulBuild/console
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Monday, July 13, 2020 8:25 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing!
On 7/13/20, 9:32 AM, "Harbs" <ha...@gmail.com> wrote:
I’m trying to wrap my head around all the pieces here.
How does the uploading to the nexus server work?
It doesn't. After some snooping through the archives, I think that some credentials were (unsafely) stored on the CI Server. The archives indicate that after build-tools was released, we tried another way of setting credentials for the main Royale build and that resulted in build-tools not being able to directly upload to nexus anymore. Of course, I could be misreading the archives.
The main Royale release prevents the upload and the RM downloads the build results, verifies them, and uploads them. Someone would have to replicate that for build-tools.
Other options are:
A) to run Maven on CI and try the new Ant script that hides passwords that Yishay created
B) Run the build locally.
HTH,
-Alex
> On Jul 13, 2020, at 7:21 PM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>
> IMO, step 1 went sideways. The tag should not contain SNAPSHOT in the POM version. Compare the tag from 1.2.0.
>
> Maven should also not be adding a timestamp to the artifact name. I don't remember why it does that, but I think there are internet articles about it.
>
> Comparing output of successful jobs might shed some light on where things are going wrong.
>
> HTH,
> -Alex
>
> On 7/13/20, 12:41 AM, "Harbs" <ha...@gmail.com> wrote:
>
> It’s still having issues:
>
> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.073309-2 from/to apache.snapshots.https (https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7C26c2782d4ddb465d15b108d8274a5371%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302547476010011&sdata=Q0G3j8IFrTWOtwAnykNS1A1OnGryUT4zmDP1AOkZH3w%3D&reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7C26c2782d4ddb465d15b108d8274a5371%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302547476010011&sdata=Q0G3j8IFrTWOtwAnykNS1A1OnGryUT4zmDP1AOkZH3w%3D&reserved=0>): Failed to transfer file https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.073309-2.jar&data=02%7C01%7Caharui%40adobe.com%7C26c2782d4ddb465d15b108d8274a5371%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302547476010011&sdata=oMses8byLKLvx1LdGfowVbiU4%2FRtgki%2B7lz51WfPkks%3D&reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.073309-2.jar&data=02%7C01%7Caharui%40adobe.com%7C26c2782d4ddb465d15b108d8274a5371%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302547476010011&sdata=oMses8byLKLvx1LdGfowVbiU4%2FRtgki%2B7lz51WfPkks%3D&reserved=0> with status code 401 -> [Help 1]
>
> I’m kind of stuck on this. Any suggestions would help.
>
> Thanks.
>
>> On Jul 13, 2020, at 10:33 AM, apacheroyaleci@gmail.com wrote:
>>
>> Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing:
>>
>> Check console output at https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Compiler_Build_Tools_Release_Step_002%2F15%2F&data=02%7C01%7Caharui%40adobe.com%7C26c2782d4ddb465d15b108d8274a5371%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302547476010011&sdata=Tb4j2zZ6g9YbnT05%2Fziudia5K6dD8klkPfdetG4ui9A%3D&reserved=0 to view the results.
>
>
>
RE: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still
Failing!
Posted by Yishay Weiss <yi...@hotmail.com>.
I’m going to try to change the job on Jenkins so it accepts Apache credentials as params and propagates them to the mvn command. I don’t know if Jenkins forms have a password element that hides the password though.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Monday, July 13, 2020 8:34 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing!
Another option is to find a way for Jenkins to securely pass the credentials to maven without it showing up in the logs. Yishay I think found a way to do that with Ant, but not sure about Jenkins jobs.
HTH,
-Alex
On 7/13/20, 10:25 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
On 7/13/20, 9:32 AM, "Harbs" <ha...@gmail.com> wrote:
I’m trying to wrap my head around all the pieces here.
How does the uploading to the nexus server work?
It doesn't. After some snooping through the archives, I think that some credentials were (unsafely) stored on the CI Server. The archives indicate that after build-tools was released, we tried another way of setting credentials for the main Royale build and that resulted in build-tools not being able to directly upload to nexus anymore. Of course, I could be misreading the archives.
The main Royale release prevents the upload and the RM downloads the build results, verifies them, and uploads them. Someone would have to replicate that for build-tools.
Other options are:
A) to run Maven on CI and try the new Ant script that hides passwords that Yishay created
B) Run the build locally.
HTH,
-Alex
> On Jul 13, 2020, at 7:21 PM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>
> IMO, step 1 went sideways. The tag should not contain SNAPSHOT in the POM version. Compare the tag from 1.2.0.
>
> Maven should also not be adding a timestamp to the artifact name. I don't remember why it does that, but I think there are internet articles about it.
>
> Comparing output of successful jobs might shed some light on where things are going wrong.
>
> HTH,
> -Alex
>
> On 7/13/20, 12:41 AM, "Harbs" <ha...@gmail.com> wrote:
>
> It’s still having issues:
>
> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.073309-2 from/to apache.snapshots.https (https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7C2a6c6127ed734987e2e508d82751c7d1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302579487383171&sdata=4hwVFzmW8JXfy6z838X7aVsP9RXpzMEhGjDOta5ahtY%3D&reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7C2a6c6127ed734987e2e508d82751c7d1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302579487383171&sdata=4hwVFzmW8JXfy6z838X7aVsP9RXpzMEhGjDOta5ahtY%3D&reserved=0>): Failed to transfer file https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.073309-2.jar&data=02%7C01%7Caharui%40adobe.com%7C2a6c6127ed734987e2e508d82751c7d1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302579487383171&sdata=veQ9LjfFpTz2%2BufQ8JwxOuyQLyxo%2FS8JUVvGwkZAsmM%3D&reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.073309-2.jar&data=02%7C01%7Caharui%40adobe.com%7C2a6c6127ed734987e2e508d82751c7d1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302579487383171&sdata=veQ9LjfFpTz2%2BufQ8JwxOuyQLyxo%2FS8JUVvGwkZAsmM%3D&reserved=0> with status code 401 -> [Help 1]
>
> I’m kind of stuck on this. Any suggestions would help.
>
> Thanks.
>
>> On Jul 13, 2020, at 10:33 AM, apacheroyaleci@gmail.com wrote:
>>
>> Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing:
>>
>> Check console output at https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Compiler_Build_Tools_Release_Step_002%2F15%2F&data=02%7C01%7Caharui%40adobe.com%7C2a6c6127ed734987e2e508d82751c7d1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302579487383171&sdata=H3xwVjFh3bAhOGsfHM6KJEm7BigUmRKhIUfUzX3g%2FkI%3D&reserved=0 to view the results.
>
>
>
Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still
Failing!
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Another option is to find a way for Jenkins to securely pass the credentials to maven without it showing up in the logs. Yishay I think found a way to do that with Ant, but not sure about Jenkins jobs.
HTH,
-Alex
On 7/13/20, 10:25 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
On 7/13/20, 9:32 AM, "Harbs" <ha...@gmail.com> wrote:
I’m trying to wrap my head around all the pieces here.
How does the uploading to the nexus server work?
It doesn't. After some snooping through the archives, I think that some credentials were (unsafely) stored on the CI Server. The archives indicate that after build-tools was released, we tried another way of setting credentials for the main Royale build and that resulted in build-tools not being able to directly upload to nexus anymore. Of course, I could be misreading the archives.
The main Royale release prevents the upload and the RM downloads the build results, verifies them, and uploads them. Someone would have to replicate that for build-tools.
Other options are:
A) to run Maven on CI and try the new Ant script that hides passwords that Yishay created
B) Run the build locally.
HTH,
-Alex
> On Jul 13, 2020, at 7:21 PM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>
> IMO, step 1 went sideways. The tag should not contain SNAPSHOT in the POM version. Compare the tag from 1.2.0.
>
> Maven should also not be adding a timestamp to the artifact name. I don't remember why it does that, but I think there are internet articles about it.
>
> Comparing output of successful jobs might shed some light on where things are going wrong.
>
> HTH,
> -Alex
>
> On 7/13/20, 12:41 AM, "Harbs" <ha...@gmail.com> wrote:
>
> It’s still having issues:
>
> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.073309-2 from/to apache.snapshots.https (https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7C2a6c6127ed734987e2e508d82751c7d1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302579487383171&sdata=4hwVFzmW8JXfy6z838X7aVsP9RXpzMEhGjDOta5ahtY%3D&reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7C2a6c6127ed734987e2e508d82751c7d1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302579487383171&sdata=4hwVFzmW8JXfy6z838X7aVsP9RXpzMEhGjDOta5ahtY%3D&reserved=0>): Failed to transfer file https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.073309-2.jar&data=02%7C01%7Caharui%40adobe.com%7C2a6c6127ed734987e2e508d82751c7d1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302579487383171&sdata=veQ9LjfFpTz2%2BufQ8JwxOuyQLyxo%2FS8JUVvGwkZAsmM%3D&reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.073309-2.jar&data=02%7C01%7Caharui%40adobe.com%7C2a6c6127ed734987e2e508d82751c7d1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302579487383171&sdata=veQ9LjfFpTz2%2BufQ8JwxOuyQLyxo%2FS8JUVvGwkZAsmM%3D&reserved=0> with status code 401 -> [Help 1]
>
> I’m kind of stuck on this. Any suggestions would help.
>
> Thanks.
>
>> On Jul 13, 2020, at 10:33 AM, apacheroyaleci@gmail.com wrote:
>>
>> Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing:
>>
>> Check console output at https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Compiler_Build_Tools_Release_Step_002%2F15%2F&data=02%7C01%7Caharui%40adobe.com%7C2a6c6127ed734987e2e508d82751c7d1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302579487383171&sdata=H3xwVjFh3bAhOGsfHM6KJEm7BigUmRKhIUfUzX3g%2FkI%3D&reserved=0 to view the results.
>
>
>
Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still
Failing!
Posted by Alex Harui <ah...@adobe.com.INVALID>.
On 7/13/20, 9:32 AM, "Harbs" <ha...@gmail.com> wrote:
I’m trying to wrap my head around all the pieces here.
How does the uploading to the nexus server work?
It doesn't. After some snooping through the archives, I think that some credentials were (unsafely) stored on the CI Server. The archives indicate that after build-tools was released, we tried another way of setting credentials for the main Royale build and that resulted in build-tools not being able to directly upload to nexus anymore. Of course, I could be misreading the archives.
The main Royale release prevents the upload and the RM downloads the build results, verifies them, and uploads them. Someone would have to replicate that for build-tools.
Other options are:
A) to run Maven on CI and try the new Ant script that hides passwords that Yishay created
B) Run the build locally.
HTH,
-Alex
> On Jul 13, 2020, at 7:21 PM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>
> IMO, step 1 went sideways. The tag should not contain SNAPSHOT in the POM version. Compare the tag from 1.2.0.
>
> Maven should also not be adding a timestamp to the artifact name. I don't remember why it does that, but I think there are internet articles about it.
>
> Comparing output of successful jobs might shed some light on where things are going wrong.
>
> HTH,
> -Alex
>
> On 7/13/20, 12:41 AM, "Harbs" <ha...@gmail.com> wrote:
>
> It’s still having issues:
>
> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.073309-2 from/to apache.snapshots.https (https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7C26c2782d4ddb465d15b108d8274a5371%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302547476010011&sdata=Q0G3j8IFrTWOtwAnykNS1A1OnGryUT4zmDP1AOkZH3w%3D&reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7C26c2782d4ddb465d15b108d8274a5371%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302547476010011&sdata=Q0G3j8IFrTWOtwAnykNS1A1OnGryUT4zmDP1AOkZH3w%3D&reserved=0>): Failed to transfer file https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.073309-2.jar&data=02%7C01%7Caharui%40adobe.com%7C26c2782d4ddb465d15b108d8274a5371%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302547476010011&sdata=oMses8byLKLvx1LdGfowVbiU4%2FRtgki%2B7lz51WfPkks%3D&reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.073309-2.jar&data=02%7C01%7Caharui%40adobe.com%7C26c2782d4ddb465d15b108d8274a5371%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302547476010011&sdata=oMses8byLKLvx1LdGfowVbiU4%2FRtgki%2B7lz51WfPkks%3D&reserved=0> with status code 401 -> [Help 1]
>
> I’m kind of stuck on this. Any suggestions would help.
>
> Thanks.
>
>> On Jul 13, 2020, at 10:33 AM, apacheroyaleci@gmail.com wrote:
>>
>> Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing:
>>
>> Check console output at https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Compiler_Build_Tools_Release_Step_002%2F15%2F&data=02%7C01%7Caharui%40adobe.com%7C26c2782d4ddb465d15b108d8274a5371%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302547476010011&sdata=Tb4j2zZ6g9YbnT05%2Fziudia5K6dD8klkPfdetG4ui9A%3D&reserved=0 to view the results.
>
>
>
Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still
Failing!
Posted by Harbs <ha...@gmail.com>.
I’m trying to wrap my head around all the pieces here.
How does the uploading to the nexus server work?
> On Jul 13, 2020, at 7:21 PM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>
> IMO, step 1 went sideways. The tag should not contain SNAPSHOT in the POM version. Compare the tag from 1.2.0.
>
> Maven should also not be adding a timestamp to the artifact name. I don't remember why it does that, but I think there are internet articles about it.
>
> Comparing output of successful jobs might shed some light on where things are going wrong.
>
> HTH,
> -Alex
>
> On 7/13/20, 12:41 AM, "Harbs" <ha...@gmail.com> wrote:
>
> It’s still having issues:
>
> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.073309-2 from/to apache.snapshots.https (https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7C57ec6dcc28f446417ec108d8270015c5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302228604622818&sdata=3uslr50%2FZJnWgUddP%2Ffu%2FouYdB2ia8UeoH5oldtyqy0%3D&reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7C57ec6dcc28f446417ec108d8270015c5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302228604632779&sdata=UI3JrHWVEYwoDIUlpN26%2FsStLHRJi2zIhL0aCoocA%2FY%3D&reserved=0>): Failed to transfer file https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.073309-2.jar&data=02%7C01%7Caharui%40adobe.com%7C57ec6dcc28f446417ec108d8270015c5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302228604632779&sdata=n2oNYMf%2F0Nw2OxbdvM9gHo47yHVhqwlJKIC%2Bive0IA8%3D&reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.073309-2.jar&data=02%7C01%7Caharui%40adobe.com%7C57ec6dcc28f446417ec108d8270015c5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302228604632779&sdata=n2oNYMf%2F0Nw2OxbdvM9gHo47yHVhqwlJKIC%2Bive0IA8%3D&reserved=0> with status code 401 -> [Help 1]
>
> I’m kind of stuck on this. Any suggestions would help.
>
> Thanks.
>
>> On Jul 13, 2020, at 10:33 AM, apacheroyaleci@gmail.com wrote:
>>
>> Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing:
>>
>> Check console output at https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Compiler_Build_Tools_Release_Step_002%2F15%2F&data=02%7C01%7Caharui%40adobe.com%7C57ec6dcc28f446417ec108d8270015c5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302228604632779&sdata=g%2BSNOJsTRBcSUTLMgKHAuX07aq4lnP0atrQUERXkStI%3D&reserved=0 to view the results.
>
>
>
Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still
Failing!
Posted by Alex Harui <ah...@adobe.com.INVALID>.
IMO, step 1 went sideways. The tag should not contain SNAPSHOT in the POM version. Compare the tag from 1.2.0.
Maven should also not be adding a timestamp to the artifact name. I don't remember why it does that, but I think there are internet articles about it.
Comparing output of successful jobs might shed some light on where things are going wrong.
HTH,
-Alex
On 7/13/20, 12:41 AM, "Harbs" <ha...@gmail.com> wrote:
It’s still having issues:
[INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.073309-2 from/to apache.snapshots.https (https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7C57ec6dcc28f446417ec108d8270015c5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302228604622818&sdata=3uslr50%2FZJnWgUddP%2Ffu%2FouYdB2ia8UeoH5oldtyqy0%3D&reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7C57ec6dcc28f446417ec108d8270015c5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302228604632779&sdata=UI3JrHWVEYwoDIUlpN26%2FsStLHRJi2zIhL0aCoocA%2FY%3D&reserved=0>): Failed to transfer file https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.073309-2.jar&data=02%7C01%7Caharui%40adobe.com%7C57ec6dcc28f446417ec108d8270015c5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302228604632779&sdata=n2oNYMf%2F0Nw2OxbdvM9gHo47yHVhqwlJKIC%2Bive0IA8%3D&reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.073309-2.jar&data=02%7C01%7Caharui%40adobe.com%7C57ec6dcc28f446417ec108d8270015c5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302228604632779&sdata=n2oNYMf%2F0Nw2OxbdvM9gHo47yHVhqwlJKIC%2Bive0IA8%3D&reserved=0> with status code 401 -> [Help 1]
I’m kind of stuck on this. Any suggestions would help.
Thanks.
> On Jul 13, 2020, at 10:33 AM, apacheroyaleci@gmail.com wrote:
>
> Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing:
>
> Check console output at https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Compiler_Build_Tools_Release_Step_002%2F15%2F&data=02%7C01%7Caharui%40adobe.com%7C57ec6dcc28f446417ec108d8270015c5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302228604632779&sdata=g%2BSNOJsTRBcSUTLMgKHAuX07aq4lnP0atrQUERXkStI%3D&reserved=0 to view the results.
Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still
Failing!
Posted by Harbs <ha...@gmail.com>.
It’s still having issues:
[INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.073309-2 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots <https://repository.apache.org/content/repositories/snapshots>): Failed to transfer file https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.073309-2.jar <https://repository.apache.org/content/repositories/snapshots/org/apache/royale/compiler/compiler-build-tools/1.2.1-SNAPSHOT/compiler-build-tools-1.2.1-20200713.073309-2.jar> with status code 401 -> [Help 1]
I’m kind of stuck on this. Any suggestions would help.
Thanks.
> On Jul 13, 2020, at 10:33 AM, apacheroyaleci@gmail.com wrote:
>
> Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing:
>
> Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/15/ to view the results.