[ https://issues.apache.org/jira/browse/JAMES-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17138419#comment-17138419 ]
Ioan Eugen Stan commented on JAMES-3225: ---------------------------------------- I started removing the obsolete James builds on https://builds.apache.org/ . Then I decided to stop and wait if someone has something to add. Most of them have not run in 2-3 years. I believe they fail now since they are tracking SVN ?!?! These should be removed in the next days. https://builds.apache.org/view/All/job/james-mailet/ https://builds.apache.org/view/All/job/james-server-trunk-site/ https://builds.apache.org/view/All/job/james-server-v2.3/ https://builds.apache.org/view/All/job/james-server-v2.3-m2/ https://builds.apache.org/view/All/job/james-skin/ https://builds.apache.org/view/All/job/jdkim-trunk/ https://builds.apache.org/view/All/job/jdkim-trunk-site/ https://builds.apache.org/view/All/job/mime4j-trunk/ https://builds.apache.org/view/All/job/mime4j-trunk-site/ https://builds.apache.org/view/All/job/hupa-trunk/ https://builds.apache.org/view/All/job/hupa-trunk-site/ > 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 > Priority: Major > > 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. > -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org