ofbiz-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacques Le Roux (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OFBIZ-9196) Regression: the Gradle tasks shoud not use/block the ports
Date Sat, 18 Mar 2017 17:38:41 GMT

    [ https://issues.apache.org/jira/browse/OFBIZ-9196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15931302#comment-15931302

Jacques Le Roux commented on OFBIZ-9196:

Like I answered to Taher in the thread above, we are not yet sure that it's due to changes
related to Gradle (refactoring). What we know for sure is branches before R16 have not this

> Regression: the Gradle tasks 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

View raw message