[JBoss JIRA] (JBIDE-26312) Windows 7 slaves stall for 7 hours while recording test results?
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26312?page=com.atlassian.jira.plugi... ]
Josef Kopriva reassigned JBIDE-26312:
-------------------------------------
Assignee: Josef Kopriva (was: Jan Richter)
> Windows 7 slaves stall for 7 hours while recording test results?
> ----------------------------------------------------------------
>
> Key: JBIDE-26312
> URL: https://issues.jboss.org/browse/JBIDE-26312
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.9.0.AM3
> Reporter: Nick Boldt
> Assignee: Josef Kopriva
> Fix For: 4.9.0.Final
>
>
> This has been happening for a while now.
> {code}
> 20:24:20 Archiving artifacts
> 20:50:34 Recording test results
> (nothing happens for like 7 hours)
> 04:09:55 Agent went offline during the build
> 04:09:55 ERROR: Connection was broken: java.nio.channels.ClosedChannelException
> 04:09:55 at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)
> 04:09:55 at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:179)
> 04:09:55 at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:721)
> 04:09:55 at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
> 04:09:55 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> 04:09:55 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> 04:09:55 at java.lang.Thread.run(Thread.java:748)
> {code}
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i...
> Anyone have a clue why collecting junit results should take >7hrs on win7, but work fine on other OSes?
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (JBIDE-26312) Windows 7 slaves stall for 7 hours while recording test results?
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26312?page=com.atlassian.jira.plugi... ]
Josef Kopriva reassigned JBIDE-26312:
-------------------------------------
Assignee: Jan Richter (was: Josef Kopriva)
> Windows 7 slaves stall for 7 hours while recording test results?
> ----------------------------------------------------------------
>
> Key: JBIDE-26312
> URL: https://issues.jboss.org/browse/JBIDE-26312
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.9.0.AM3
> Reporter: Nick Boldt
> Assignee: Jan Richter
> Fix For: 4.9.0.Final
>
>
> This has been happening for a while now.
> {code}
> 20:24:20 Archiving artifacts
> 20:50:34 Recording test results
> (nothing happens for like 7 hours)
> 04:09:55 Agent went offline during the build
> 04:09:55 ERROR: Connection was broken: java.nio.channels.ClosedChannelException
> 04:09:55 at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)
> 04:09:55 at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:179)
> 04:09:55 at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:721)
> 04:09:55 at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
> 04:09:55 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> 04:09:55 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> 04:09:55 at java.lang.Thread.run(Thread.java:748)
> {code}
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i...
> Anyone have a clue why collecting junit results should take >7hrs on win7, but work fine on other OSes?
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (JBIDE-26180) TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26180?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-26180:
------------------------------------
:code}
[WARNING] Found 12 duplicate jbosstools plugins:
[WARNING] [1] jbosstools-multiple.target.repo/plugins/com.google.guava_21.0.0.v20170206-1425.jar
[WARNING] [1] jbosstools-multiple.target.repo/plugins/com.google.guava_15.0.0.v201403281430.jar
[WARNING] [2] jbosstools-multiple.target.repo/plugins/org.apache.batik.css_1.7.0.v201011041433.jar
[WARNING] [2] jbosstools-multiple.target.repo/plugins/org.apache.batik.css_1.10.0.v20180703-1553.jar
[WARNING] [3] jbosstools-multiple.target.repo/plugins/org.apache.batik.util_1.7.0.v201011041433.jar
[WARNING] [3] jbosstools-multiple.target.repo/plugins/org.apache.batik.util_1.10.0.v20180703-1553.jar
[WARNING] [4] jbosstools-multiple.target.repo/plugins/org.apache.commons.logging_1.2.0.v20180409-1502.jar
[WARNING] [4] jbosstools-multiple.target.repo/plugins/org.apache.commons.logging_1.1.1.v201101211721.jar
[WARNING] [5] jbosstools-multiple.target.repo/plugins/org.apache.lucene.analyzers-common_7.1.0.v20180122-2126.jar
[WARNING] [5] jbosstools-multiple.target.repo/plugins/org.apache.lucene.analyzers-common_6.1.0.v20161115-1612.jar
[WARNING] [6] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_6.1.0.v20170814-1820.jar
[WARNING] [6] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_3.5.0.v20120725-1805.jar
[WARNING] [6] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_7.1.0.v20171214-1510.jar
[WARNING] [7] jbosstools-multiple.target.repo/plugins/org.apache.lucene.queryparser_7.1.0.v20180828-2118.jar
[WARNING] [7] jbosstools-multiple.target.repo/plugins/org.apache.lucene.queryparser_6.1.0.v20161115-1612.jar
[WARNING] [8] jbosstools-multiple.target.repo/plugins/org.eclipse.jdt.annotation_2.2.100.v20180626-0953.jar
[WARNING] [8] jbosstools-multiple.target.repo/plugins/org.eclipse.jdt.annotation_1.1.300.v20180612-0641.jar
[WARNING] [9] jbosstools-multiple.target.repo/plugins/org.objectweb.asm_5.0.1.v201404251740.jar
[WARNING] [9] jbosstools-multiple.target.repo/plugins/org.objectweb.asm_6.2.0.v20180807-1520.jar
[WARNING] [9] jbosstools-multiple.target.repo/plugins/org.objectweb.asm_6.2.1.v20180823-1831.jar
[WARNING] [10] jbosstools-multiple.target.repo/plugins/org.objectweb.asm.tree_6.2.0.v20180807-1520.jar
[WARNING] [10] jbosstools-multiple.target.repo/plugins/org.objectweb.asm.tree_6.2.1.v20180823-1831.jar
[WARNING] [11] jbosstools-multiple.target.repo/plugins/org.slf4j.api_1.7.2.v20121108-1250.jar
[WARNING] [11] jbosstools-multiple.target.repo/plugins/org.slf4j.api_1.7.10.v20170428-1633.jar
[WARNING] [12] jbosstools-multiple.target.repo/plugins/org.w3c.dom.smil_1.0.1.v200903091627.jar
[WARNING] [12] jbosstools-multiple.target.repo/plugins/org.w3c.dom.smil_1.0.0.v200806040011.jar
{code}
p2diffs:
* [^p2diff.am2.am3.all.txt]
* [^p2diff.am2.am3.all.ignoreVersions.txt]
> TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)
> ----------------------------------------------------------------
>
> Key: JBIDE-26180
> URL: https://issues.jboss.org/browse/JBIDE-26180
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, upstream
> Affects Versions: 4.9.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Labels: releasework
> Fix For: 4.9.0.AM3, 4.9.0.Final
>
> Attachments: am1-vs-am2.p2diff.txt, p2diff.am2.am3.all.ignoreVersions.txt, p2diff.am2.am3.all.txt
>
>
> In order to start Eclipse 4.9-based builds, we need an updated target platform.
> For sprint 152 / AM1: simrel M1
> For sprint 153 / AM2: simrel M2
> For sprint 154 / AM3: simrel M3
> For sprint 155 / GA: simrel RC2/GA
> Coming in the next update, some orbit changes:
> * batik, icu4j, platform, felix gogo, httpclient (due 27 Aug)
> Also:
> * reddeer 2.3
> * m2e http://download.eclipse.org/technology/m2e/milestones/1.9/1.9.1.20180829-...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (JBIDE-26180) TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26180?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-26180 at 8/30/18 11:08 PM:
--------------------------------------------------------------
{code}
[WARNING] Found 12 duplicate jbosstools plugins:
[WARNING] [1] jbosstools-multiple.target.repo/plugins/com.google.guava_21.0.0.v20170206-1425.jar
[WARNING] [1] jbosstools-multiple.target.repo/plugins/com.google.guava_15.0.0.v201403281430.jar
[WARNING] [2] jbosstools-multiple.target.repo/plugins/org.apache.batik.css_1.7.0.v201011041433.jar
[WARNING] [2] jbosstools-multiple.target.repo/plugins/org.apache.batik.css_1.10.0.v20180703-1553.jar
[WARNING] [3] jbosstools-multiple.target.repo/plugins/org.apache.batik.util_1.7.0.v201011041433.jar
[WARNING] [3] jbosstools-multiple.target.repo/plugins/org.apache.batik.util_1.10.0.v20180703-1553.jar
[WARNING] [4] jbosstools-multiple.target.repo/plugins/org.apache.commons.logging_1.2.0.v20180409-1502.jar
[WARNING] [4] jbosstools-multiple.target.repo/plugins/org.apache.commons.logging_1.1.1.v201101211721.jar
[WARNING] [5] jbosstools-multiple.target.repo/plugins/org.apache.lucene.analyzers-common_7.1.0.v20180122-2126.jar
[WARNING] [5] jbosstools-multiple.target.repo/plugins/org.apache.lucene.analyzers-common_6.1.0.v20161115-1612.jar
[WARNING] [6] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_6.1.0.v20170814-1820.jar
[WARNING] [6] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_3.5.0.v20120725-1805.jar
[WARNING] [6] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_7.1.0.v20171214-1510.jar
[WARNING] [7] jbosstools-multiple.target.repo/plugins/org.apache.lucene.queryparser_7.1.0.v20180828-2118.jar
[WARNING] [7] jbosstools-multiple.target.repo/plugins/org.apache.lucene.queryparser_6.1.0.v20161115-1612.jar
[WARNING] [8] jbosstools-multiple.target.repo/plugins/org.eclipse.jdt.annotation_2.2.100.v20180626-0953.jar
[WARNING] [8] jbosstools-multiple.target.repo/plugins/org.eclipse.jdt.annotation_1.1.300.v20180612-0641.jar
[WARNING] [9] jbosstools-multiple.target.repo/plugins/org.objectweb.asm_5.0.1.v201404251740.jar
[WARNING] [9] jbosstools-multiple.target.repo/plugins/org.objectweb.asm_6.2.0.v20180807-1520.jar
[WARNING] [9] jbosstools-multiple.target.repo/plugins/org.objectweb.asm_6.2.1.v20180823-1831.jar
[WARNING] [10] jbosstools-multiple.target.repo/plugins/org.objectweb.asm.tree_6.2.0.v20180807-1520.jar
[WARNING] [10] jbosstools-multiple.target.repo/plugins/org.objectweb.asm.tree_6.2.1.v20180823-1831.jar
[WARNING] [11] jbosstools-multiple.target.repo/plugins/org.slf4j.api_1.7.2.v20121108-1250.jar
[WARNING] [11] jbosstools-multiple.target.repo/plugins/org.slf4j.api_1.7.10.v20170428-1633.jar
[WARNING] [12] jbosstools-multiple.target.repo/plugins/org.w3c.dom.smil_1.0.1.v200903091627.jar
[WARNING] [12] jbosstools-multiple.target.repo/plugins/org.w3c.dom.smil_1.0.0.v200806040011.jar
{code}
p2diffs:
* [^p2diff.am2.am3.all.txt]
* [^p2diff.am2.am3.all.ignoreVersions.txt]
was (Author: nickboldt):
:code}
[WARNING] Found 12 duplicate jbosstools plugins:
[WARNING] [1] jbosstools-multiple.target.repo/plugins/com.google.guava_21.0.0.v20170206-1425.jar
[WARNING] [1] jbosstools-multiple.target.repo/plugins/com.google.guava_15.0.0.v201403281430.jar
[WARNING] [2] jbosstools-multiple.target.repo/plugins/org.apache.batik.css_1.7.0.v201011041433.jar
[WARNING] [2] jbosstools-multiple.target.repo/plugins/org.apache.batik.css_1.10.0.v20180703-1553.jar
[WARNING] [3] jbosstools-multiple.target.repo/plugins/org.apache.batik.util_1.7.0.v201011041433.jar
[WARNING] [3] jbosstools-multiple.target.repo/plugins/org.apache.batik.util_1.10.0.v20180703-1553.jar
[WARNING] [4] jbosstools-multiple.target.repo/plugins/org.apache.commons.logging_1.2.0.v20180409-1502.jar
[WARNING] [4] jbosstools-multiple.target.repo/plugins/org.apache.commons.logging_1.1.1.v201101211721.jar
[WARNING] [5] jbosstools-multiple.target.repo/plugins/org.apache.lucene.analyzers-common_7.1.0.v20180122-2126.jar
[WARNING] [5] jbosstools-multiple.target.repo/plugins/org.apache.lucene.analyzers-common_6.1.0.v20161115-1612.jar
[WARNING] [6] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_6.1.0.v20170814-1820.jar
[WARNING] [6] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_3.5.0.v20120725-1805.jar
[WARNING] [6] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_7.1.0.v20171214-1510.jar
[WARNING] [7] jbosstools-multiple.target.repo/plugins/org.apache.lucene.queryparser_7.1.0.v20180828-2118.jar
[WARNING] [7] jbosstools-multiple.target.repo/plugins/org.apache.lucene.queryparser_6.1.0.v20161115-1612.jar
[WARNING] [8] jbosstools-multiple.target.repo/plugins/org.eclipse.jdt.annotation_2.2.100.v20180626-0953.jar
[WARNING] [8] jbosstools-multiple.target.repo/plugins/org.eclipse.jdt.annotation_1.1.300.v20180612-0641.jar
[WARNING] [9] jbosstools-multiple.target.repo/plugins/org.objectweb.asm_5.0.1.v201404251740.jar
[WARNING] [9] jbosstools-multiple.target.repo/plugins/org.objectweb.asm_6.2.0.v20180807-1520.jar
[WARNING] [9] jbosstools-multiple.target.repo/plugins/org.objectweb.asm_6.2.1.v20180823-1831.jar
[WARNING] [10] jbosstools-multiple.target.repo/plugins/org.objectweb.asm.tree_6.2.0.v20180807-1520.jar
[WARNING] [10] jbosstools-multiple.target.repo/plugins/org.objectweb.asm.tree_6.2.1.v20180823-1831.jar
[WARNING] [11] jbosstools-multiple.target.repo/plugins/org.slf4j.api_1.7.2.v20121108-1250.jar
[WARNING] [11] jbosstools-multiple.target.repo/plugins/org.slf4j.api_1.7.10.v20170428-1633.jar
[WARNING] [12] jbosstools-multiple.target.repo/plugins/org.w3c.dom.smil_1.0.1.v200903091627.jar
[WARNING] [12] jbosstools-multiple.target.repo/plugins/org.w3c.dom.smil_1.0.0.v200806040011.jar
{code}
p2diffs:
* [^p2diff.am2.am3.all.txt]
* [^p2diff.am2.am3.all.ignoreVersions.txt]
> TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)
> ----------------------------------------------------------------
>
> Key: JBIDE-26180
> URL: https://issues.jboss.org/browse/JBIDE-26180
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, upstream
> Affects Versions: 4.9.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Labels: releasework
> Fix For: 4.9.0.AM3, 4.9.0.Final
>
> Attachments: am1-vs-am2.p2diff.txt, p2diff.am2.am3.all.ignoreVersions.txt, p2diff.am2.am3.all.txt
>
>
> In order to start Eclipse 4.9-based builds, we need an updated target platform.
> For sprint 152 / AM1: simrel M1
> For sprint 153 / AM2: simrel M2
> For sprint 154 / AM3: simrel M3
> For sprint 155 / GA: simrel RC2/GA
> Coming in the next update, some orbit changes:
> * batik, icu4j, platform, felix gogo, httpclient (due 27 Aug)
> Also:
> * reddeer 2.3
> * m2e http://download.eclipse.org/technology/m2e/milestones/1.9/1.9.1.20180829-...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (JBIDE-26180) TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26180?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-26180:
-------------------------------
Attachment: p2diff.am2.am3.all.ignoreVersions.txt
p2diff.am2.am3.all.txt
> TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)
> ----------------------------------------------------------------
>
> Key: JBIDE-26180
> URL: https://issues.jboss.org/browse/JBIDE-26180
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, upstream
> Affects Versions: 4.9.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Labels: releasework
> Fix For: 4.9.0.AM3, 4.9.0.Final
>
> Attachments: am1-vs-am2.p2diff.txt, p2diff.am2.am3.all.ignoreVersions.txt, p2diff.am2.am3.all.txt
>
>
> In order to start Eclipse 4.9-based builds, we need an updated target platform.
> For sprint 152 / AM1: simrel M1
> For sprint 153 / AM2: simrel M2
> For sprint 154 / AM3: simrel M3
> For sprint 155 / GA: simrel RC2/GA
> Coming in the next update, some orbit changes:
> * batik, icu4j, platform, felix gogo, httpclient (due 27 Aug)
> Also:
> * reddeer 2.3
> * m2e http://download.eclipse.org/technology/m2e/milestones/1.9/1.9.1.20180829-...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (JBIDE-26299) [Red Hat Central] Update to latest Sonarlint 3.6
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26299?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-26299 at 8/30/18 9:35 PM:
-------------------------------------------------------------
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... ... 5, 142, 132, 10 issues
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... ... 3, 107, 132, 10 issues
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... ... 142, 132, 10 issues
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... ... 107, 132, 10 issues
So that actually made things worse. So much for "new is better". :(
Seems to be a change in *sonar-php-plugin-2.13.0.3107.jar* vs. *sonar-php-plugin-2.11.0.2485.jar*
was (Author: nickboldt):
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... ... 5, 142, 132, 10 issues
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... ... 3, 107, 132, 10 issues
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... ... 142, 132, 10 issues
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... ... 107, 132, 10 issues
So that actually made things worse. So much for "new is better". :(
> [Red Hat Central] Update to latest Sonarlint 3.6
> ------------------------------------------------
>
> Key: JBIDE-26299
> URL: https://issues.jboss.org/browse/JBIDE-26299
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central-update
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.9.0.AM3
>
>
> Pull 3.6.0 from https://eclipse-uc.sonarlint.org/
> Check if we have fewer CVEs after update:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... vs. #103
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... vs. build #87
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (JBIDE-26299) [Red Hat Central] Update to latest Sonarlint 3.6
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26299?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-26299:
------------------------------------
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... ... 5, 142, 132, 10 issues
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... ... 3, 107, 132, 10 issues
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... ... 142, 132, 10 issues
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... ... 107, 132, 10 issues
So that actually made things worse. So much for "new is better". :(
> [Red Hat Central] Update to latest Sonarlint 3.6
> ------------------------------------------------
>
> Key: JBIDE-26299
> URL: https://issues.jboss.org/browse/JBIDE-26299
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central-update
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.9.0.AM3
>
>
> Pull 3.6.0 from https://eclipse-uc.sonarlint.org/
> Check if we have fewer CVEs after update:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... vs. #103
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... vs. build #87
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22138:
-------------------------------------
Description:
This is a follow up on JBIDE-22128.
The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
steps:
# EXEC: follow steps outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... (deploying with fabric8 maven plugin doesn't work, you end up having the pod failing with ImagePullBack error. You need to take the alternative road where you deploy via "oc new-build", "oc new-app", "oc expose" etc.)
# EXEC: import the app into your Eclipse workspace
# EXEC: "hello" (workspace) project: Properties > Maven > Active Maven Profile: set "openshift"
# EXEC: create a server adapter and start it
# ASSERT: adapter starts syncing, verify what war is used
Result:
The war that's created locally and then synced to the pod is "hello.war" even though the profile specifies "ROOT.war"
Expected result:
If you start the server adapter the maven profile "openshift" should be activated and the war that's published should be "ROOT.war". If you stop the server adapter the "openshift" maven profile should be deactivated for the "hello" project.
was:
This is a follow up on JBIDE-22128.
The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
steps:
# EXEC: follow steps outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... (deploying with fabric8 maven plugin doesn't work, you end up having the pod failing with ImagePullBack error. You need to take the alternative road where you deploy via "oc new-build", "oc new-app", "oc expose" etc.)
# EXEC: import the app into your Eclipse workspace
# EXEC: "hello" (workspace) project: Properties > Maven > Active Maven Profile: set "openshift"
# EXEC: create a server adapter and start it
# ASSERT: adapter starts syncing, verify what war is used
Result:
The war that's created locally and then synced to the pod is "hello.war" even though the profile specifies "ROOT.war"
> Server adapter: doesn't respect openshift maven profile
> -------------------------------------------------------
>
> Key: JBIDE-22138
> URL: https://issues.jboss.org/browse/JBIDE-22138
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
> Openshift plugin 3.1.0.Final-v20160401-2357-B263
> Reporter: Rafael Benevides
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.9.0.AM3
>
> Attachments: image-2018-06-22-19-02-57-247.png
>
>
> This is a follow up on JBIDE-22128.
> The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
> steps:
> # EXEC: follow steps outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... (deploying with fabric8 maven plugin doesn't work, you end up having the pod failing with ImagePullBack error. You need to take the alternative road where you deploy via "oc new-build", "oc new-app", "oc expose" etc.)
> # EXEC: import the app into your Eclipse workspace
> # EXEC: "hello" (workspace) project: Properties > Maven > Active Maven Profile: set "openshift"
> # EXEC: create a server adapter and start it
> # ASSERT: adapter starts syncing, verify what war is used
> Result:
> The war that's created locally and then synced to the pod is "hello.war" even though the profile specifies "ROOT.war"
> Expected result:
> If you start the server adapter the maven profile "openshift" should be activated and the war that's published should be "ROOT.war". If you stop the server adapter the "openshift" maven profile should be deactivated for the "hello" project.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months