You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "ASF GitHub Bot (Jira)" <se...@james.apache.org> on 2021/02/03 08:42:00 UTC
[jira] [Commented] (JAMES-3225) Provide automated builds for Apache
James - (restore builds.apache.org ?)
[ https://issues.apache.org/jira/browse/JAMES-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17277809#comment-17277809 ]
ASF GitHub Bot commented on JAMES-3225:
---------------------------------------
jeantil commented on pull request #264:
URL: https://github.com/apache/james-project/pull/264#issuecomment-772336138
After :
- using a unique name for the cassandra singleton image to avoid clashes between parallel maven runs overwriting each other's docker cache
- dropping fork reuse entirely to get rid of memory leaks inducing `OutOfMemoryError: Direct buffer memory`
last failure is :
```
23:31:06.935 [ERROR] ?.3.2] - Could not start container
java.lang.IllegalStateException: Container exited with code 1
at org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:469)
at org.testcontainers.containers.GenericContainer.lambda$doStart$0(GenericContainer.java:325)
at org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:81)
at org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:323)
at org.testcontainers.containers.GenericContainer.start(GenericContainer.java:311)
at org.apache.james.linshare.Linshare.start(Linshare.java:71)
at org.apache.james.linshare.LinshareSingleton.<clinit>(LinshareSingleton.java:27)
at org.apache.james.linshare.LinshareExtension.<clinit>(LinshareExtension.java:62)
at org.apache.james.modules.LinshareGuiceExtension.<init>(LinshareGuiceExtension.java:39)
at org.apache.james.LinshareBlobExportMechanismProvidingTest.<clinit>(LinshareBlobExportMechanismProvidingTest.java:29)
23:31:06.973 [ERROR] ?.3.2] - Log output from the failed container:
wait-for-it.sh: waiting 15 seconds for ${LS_SERVER_HOST}:${LS_SERVER_PORT}
wait-for-it.sh: timeout occurred after waiting 15 seconds for ${LS_SERVER_HOST}:${LS_SERVER_PORT}
INFO:init.sh: Checking all required env variables...
LS_SERVER_HOST : backend
LS_SERVER_PORT : 8080
LS_LDAP_URL : ldap://ldap:389
LS_USER_URL : https://user.linshare.local
LS_EXTERNAL_URL : https://user.linshare.local
LS_PASSWORD : admi...
LS_NO_REPLY_ADDRESS : no-reply@linshare.org
INFO:init.sh: All env variables checked
INFO:init.sh: Checking all optional env variables...
LS_LDAP_DN : cn=linshare,dc=linshare,dc=org
LS_LDAP_PW : lins...
LS_LDAP_BASE_DN : ou=People,dc=linshare,dc=org
LS_LDAP_NAME : ldap-local
LS_FORCE_INIT : 0
LS_DOMAIN_PATTERN_NAME : openldap-local
LS_DOMAIN_PATTERN_MODEL : 868400c0-c12e-456a-8c3c-19e985290586
LS_EXTRA_INIT_SCRIPT :
LS_JWT_PUB_KEY : /linagora/data/public.pem
LS_JWT_PUB_KEY_NAME :
INFO:init.sh: All env variables checked
23:21:22 WARNING : Current password is not valid.
23:21:22 INFO : Trying to authenticate with the new provided password
23:21:22 ERROR : Can't update the current password.
```
Since Linshare is yet another singleton which generates a docker image, I'll try assigning it a unique image name just in case.
see you tonight for the results (build takes >6h)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
> Provide automated builds for Apache James - (restore builds.apache.org ?)
> --------------------------------------------------------------------------
>
> Key: JAMES-3225
> URL: https://issues.apache.org/jira/browse/JAMES-3225
> Project: James Server
> Issue Type: Task
> Reporter: Ioan Eugen Stan
> Assignee: Ioan Eugen Stan
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> For a long time we had builds that ran on the Apache Infrastructure https://builds.apache.org/view/All/job/james-mailet/ .
> The build infrastructure is not running for ~ 3 years now.
> I believe it is important for us to have automated builds.
> This ticket should gather the work needed to make this a reality.
> There are lots of things to take into consideration.
> My ( [~ieugen] ) opinions on how to handle this.
> * builds should run automatically
> * builds should run fast < 10 min
> * there are several things they should do (not exhaustive)
> ** verify the source code
> ** compile the source code
> ** run the unit tests
> ** run the integration tests
> ** publish SNAPSHOTS (only from master or develop ?!)
> ** run code analytics
> ** publish reports relating to build
> ** provide build status for other services
> For smaller projects this is a no-brainer.
> For the current state of Apache James this is a challange, especially in the context of
> - multiple git branches and PR's
> - the distributed integration tests which take a long time
> Given the limited resources available for us on the Apache infrastructure we will have to be selective of what we do.
> Personally I don't see how we can run the current (40mni +) integration suite on each push / build. I'm pretty sure we will get banned :) or throttled.
> So a discussion should be in order on how to solve these issues but some options regarding what we can do:
> - make integration tests OPT-IN
> - run (distributed) integration tests once a day or once every 6h / 12h
> - have build profiles that build a common subset all the time and run
> The nuclear option: prune some of the components we have in James and we don't want to support or move them out of the common project.
> This is something we should consider especially for buggy components or for components that don't have a maintainer.
> We have limited time and resources.
> We can't maintain everything for everybody.
> We should be mindful of this.
> We can take inspiration from the OFBiz project https://builds.apache.org/view/All/job/Apache%20OFBiz/ .
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org