[
https://issues.jboss.org/browse/JBIDE-26161?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-26161:
---------------------------------------
I wanted to figure out what was the problem with the mac slaves so that Nick had to use
mac_xhyve.
So I set the job to use dev-platform-mac-1 or 2. And I saw errors like these:
{code}
11:59:26 [ERROR] Invalid extension descriptor for
org.eclipse.tycho:tycho-maven-plugin:1.2.0: error in opening zip file
11:59:26 java.util.zip.ZipException: error in opening zip file
{code}
It felt familiar, I thought I was dealing with something similar not that long ago, but
couldn't find it. And then it hit me: It was a problem with wrong maven repo setup.
For example see this:
{code}
11:59:57 [WARNING] Could not validate integrity of download from
https://maven.repository.redhat.com/org/jboss/tools/parent/4.9.0.AM1-SNAP...
{code}
If you look at the url, it will redirect you to this page:
https://access.redhat.com/maven-repository
The main issue here is that there was a repo defined with this url:
http://maven.repository.redhat.com/
Instead of:
http://maven.repository.redhat.com/ga
I fixed it for all the slaves by replacing the settings.xml files with this:
https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/b...
{code}
$ for i in
domek.tpb.lab.eng.brq.redhat.com dev-platform-mac2.mw.lab.eng.rdu2.redhat.com
bigmek.tpb.lab.eng.brq.redhat.com zamek.tpb.lab.eng.brq.redhat.com
dev-platform-mac1.mw.lab.eng.rdu2.redhat.com; do scp /Users/rasp/Downloads/settings.xml
jbossqa@${i}:.m2/; done
{code}
Update Mac OS machines (deps, os, java, maven, etc.) and verify its
usability in jenkins environment
----------------------------------------------------------------------------------------------------
Key: JBIDE-26161
URL:
https://issues.jboss.org/browse/JBIDE-26161
Project: Tools (JBoss Tools)
Issue Type: Task
Components: qa
Affects Versions: 4.9.0.AM1
Reporter: Ondrej Dockal
Assignee: Martin Malina
Fix For: 4.9.0.AM2
Take a look and update/repair Mac os machines used in our infra, especially zamek and
check out the others:
* domek
* bigmek
* dev-platform-mac1
* dev-platform-mac2
Make dev-platform-macX machines capable to run cdk
* add them to mac_xhyve label
Should not be dev-platform-macX upgraded to High Sierra?
cc: [~nickboldt] [~mmalina]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)