James Server
  1. James Server
  2. JAMES-1446 OSGI Love
  3. JAMES-1461

Make build faster - introduce Live Tests in profile

    Details

    • Type: Sub-task Sub-task
    • Status: In Progress
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      The current James build takes long. To speed developement we can move heavier tests and the ones that require an internet connection into a LiveTests. Onli basic unit tests should be run during normal build. Live tests should be configured to run on Jenkins.

        Activity

        Ioan Eugen Stan created issue -
        Ioan Eugen Stan made changes -
        Field Original Value New Value
        Component/s CLI [ 12319900 ]
        Component/s Deployment Modules [ 12312018 ]
        Component/s James Core [ 10632 ]
        Ioan Eugen Stan made changes -
        Assignee Ioan Eugen Stan [ ieugen ]
        Ioan Eugen Stan made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Hide
        Eric Charles added a comment -

        Hi Ioan,
        Which test depends on Internet?
        Eric

        Show
        Eric Charles added a comment - Hi Ioan, Which test depends on Internet? Eric
        Hide
        Ioan Eugen Stan added a comment -

        Hello Eric,

        This is one of them that fails without internet connection. There are about 10.

        testHeloResolv(org.apache.james.smtpserver.OioSMTPServerTest): james.apache.org domain currently cannot be resolved (check your DNS/internet connection/proxy settings to make test pass)

        With regard to speed issues, we have a few builds that take longer 30 sec an we should try to reduce that time during normal build as much as possible so we can get faster responses.

        First thing we can make the assembly a profile.

        [INFO] Apache James :: Server ............................ SUCCESS [2.437s]
        [INFO] Apache James :: Server :: Data :: API ............ SUCCESS [8.424s]
        [INFO] Apache James :: Server :: Lifecycle API ........... SUCCESS [2.408s]
        [INFO] Apache James :: Server :: Filesystem API .......... SUCCESS [4.731s]
        [INFO] Apache James :: Server :: Lifecycle Spring ........ SUCCESS [4.571s]
        [INFO] Apache James :: Server :: Mailetcontainer API ..... SUCCESS [2.552s]
        [INFO] Apache James :: Server :: Common Utilities ........ SUCCESS [5.539s]
        [INFO] Apache James :: Server :: Protocols Library ....... SUCCESS [3.883s]
        [INFO] Apache James :: Server :: Core .................... SUCCESS [15.357s]
        [INFO] Apache James :: Server :: Container Spring ........ SUCCESS [3.719s]
        [INFO] Apache James :: Server :: Client .................. SUCCESS [3.759s]
        [INFO] Apache James :: Server :: DNS Service :: API ...... SUCCESS [3.073s]
        [INFO] Apache James :: Server :: DNS Service :: Library .. SUCCESS [3.306s]
        [INFO] Apache James :: Server :: Mail Queue :: API ....... SUCCESS [2.136s]
        [INFO] Apache James :: Server :: Mailetcontainer Camel ... SUCCESS [15.563s]
        [INFO] Apache James :: Server :: Mailbox Adapter ......... SUCCESS [1.291s]
        [INFO] Apache James :: Server :: DNS Service :: Implementation SUCCESS [2.460s]
        [INFO] Apache James :: Server :: Data :: Library ......... SUCCESS [4.733s]
        [INFO] Apache James :: Server :: Data :: LDAP Implementation SUCCESS [1.106s]
        [INFO] Apache James :: Server :: SMTP .................... SUCCESS [21.055s]
        [INFO] Apache James :: Server :: IMAP .................... SUCCESS [9.081s]
        [INFO] Apache James :: Server :: LMTP .................... SUCCESS [4.044s]
        [INFO] Apache James :: Server :: POP3 .................... SUCCESS [14.010s]
        [INFO] Apache James :: Server :: FetchMail ............... SUCCESS [1.726s]
        [INFO] Apache James :: Server :: Mail Queue :: File ...... SUCCESS [1.242s]
        [INFO] Apache James :: Server :: Mail Queue :: JMS ....... SUCCESS [35.414s]
        [INFO] Apache James :: Server :: Mail Queue :: ActiveMQ .. SUCCESS [1:39.544s]
        [INFO] Apache James :: Server :: Mailets ................. SUCCESS [14.438s]
        [INFO] Apache James :: Server :: Data :: File Persistence SUCCESS [7.062s]
        [INFO] Apache James :: Server :: Data :: JPA Persistence . SUCCESS [13.883s]
        [INFO] Apache James :: Server :: Data :: JDBC Persistence SUCCESS [55.572s]
        [INFO] Apache James :: Server :: Data :: JCR Persistence . SUCCESS [13.908s]
        [INFO] Apache James :: Server :: App ..................... SUCCESS [1:58.275s]

        Show
        Ioan Eugen Stan added a comment - Hello Eric, This is one of them that fails without internet connection. There are about 10. testHeloResolv(org.apache.james.smtpserver.OioSMTPServerTest): james.apache.org domain currently cannot be resolved (check your DNS/internet connection/proxy settings to make test pass) With regard to speed issues, we have a few builds that take longer 30 sec an we should try to reduce that time during normal build as much as possible so we can get faster responses. First thing we can make the assembly a profile. [INFO] Apache James :: Server ............................ SUCCESS [2.437s] [INFO] Apache James :: Server :: Data :: API ............ SUCCESS [8.424s] [INFO] Apache James :: Server :: Lifecycle API ........... SUCCESS [2.408s] [INFO] Apache James :: Server :: Filesystem API .......... SUCCESS [4.731s] [INFO] Apache James :: Server :: Lifecycle Spring ........ SUCCESS [4.571s] [INFO] Apache James :: Server :: Mailetcontainer API ..... SUCCESS [2.552s] [INFO] Apache James :: Server :: Common Utilities ........ SUCCESS [5.539s] [INFO] Apache James :: Server :: Protocols Library ....... SUCCESS [3.883s] [INFO] Apache James :: Server :: Core .................... SUCCESS [15.357s] [INFO] Apache James :: Server :: Container Spring ........ SUCCESS [3.719s] [INFO] Apache James :: Server :: Client .................. SUCCESS [3.759s] [INFO] Apache James :: Server :: DNS Service :: API ...... SUCCESS [3.073s] [INFO] Apache James :: Server :: DNS Service :: Library .. SUCCESS [3.306s] [INFO] Apache James :: Server :: Mail Queue :: API ....... SUCCESS [2.136s] [INFO] Apache James :: Server :: Mailetcontainer Camel ... SUCCESS [15.563s] [INFO] Apache James :: Server :: Mailbox Adapter ......... SUCCESS [1.291s] [INFO] Apache James :: Server :: DNS Service :: Implementation SUCCESS [2.460s] [INFO] Apache James :: Server :: Data :: Library ......... SUCCESS [4.733s] [INFO] Apache James :: Server :: Data :: LDAP Implementation SUCCESS [1.106s] [INFO] Apache James :: Server :: SMTP .................... SUCCESS [21.055s] [INFO] Apache James :: Server :: IMAP .................... SUCCESS [9.081s] [INFO] Apache James :: Server :: LMTP .................... SUCCESS [4.044s] [INFO] Apache James :: Server :: POP3 .................... SUCCESS [14.010s] [INFO] Apache James :: Server :: FetchMail ............... SUCCESS [1.726s] [INFO] Apache James :: Server :: Mail Queue :: File ...... SUCCESS [1.242s] [INFO] Apache James :: Server :: Mail Queue :: JMS ....... SUCCESS [35.414s] [INFO] Apache James :: Server :: Mail Queue :: ActiveMQ .. SUCCESS [1:39.544s] [INFO] Apache James :: Server :: Mailets ................. SUCCESS [14.438s] [INFO] Apache James :: Server :: Data :: File Persistence SUCCESS [7.062s] [INFO] Apache James :: Server :: Data :: JPA Persistence . SUCCESS [13.883s] [INFO] Apache James :: Server :: Data :: JDBC Persistence SUCCESS [55.572s] [INFO] Apache James :: Server :: Data :: JCR Persistence . SUCCESS [13.908s] [INFO] Apache James :: Server :: App ..................... SUCCESS [1:58.275s]

          People

          • Assignee:
            Ioan Eugen Stan
            Reporter:
            Ioan Eugen Stan
          • Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:

              Development