[
https://issues.apache.org/jira/browse/OFBIZ-9196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904737#comment-15904737
]
Jacques Le Roux commented on OFBIZ-9196:
----------------------------------------
Ok, this problem persists but at least now tests passes on Buildbot, despite
still having the ports owned but who knows what (see INFRA-13573 about that)
This problem is minor has the only drawback is you have to close a trunk or
R16.11 runnin instance before runing tests (from trunk or any other branches)
> Regression: the testIntegration Gradle taks shoud not use/block the ports
> -------------------------------------------------------------------------
>
> Key: OFBIZ-9196
> URL: https://issues.apache.org/jira/browse/OFBIZ-9196
> Project: OFBiz
> Issue Type: Bug
> Components: Gradle
> Affects Versions: Trunk, Release Branch 16.11
> Reporter: Jacques Le Roux
> Priority: Minor
> Fix For: Upcoming Release, 16.11.02
>
>
> We got an issue on Buildbot because of a Puppet misconfiguration which was
> always using the port 8080. Pre-gradle OFBiz tests were still running fine on
> Buildbot.
> Before the Puppet misconfiguration fix by infra (INFRA-13402), to bypass this
> issue I tried last weekend to use portoffset in Gradle versions. From the
> documentation, it's theoretically possible but does not work.
> Taher suggested, to get back to the previous behaviour were tests were not
> using/blocking the 8080 port, and to have a look into Config.java...
> It's a regression because it was nice to not have ports blocked during tests,
> as it was before Gradle. So you can use another (or more) OFBiz instance
> while running tests, and vice-versa.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
