activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "clebert suconic (JIRA)" <>
Subject [jira] [Closed] (ARTEMIS-555) Run `mvn -Pexamples verify` in the CI
Date Wed, 29 Jun 2016 22:27:39 GMT


clebert suconic closed ARTEMIS-555.
       Resolution: Fixed
         Assignee: clebert suconic
    Fix Version/s: 1.4.0

I am adding a script under ./artemis-distribution/src/tests/scripts

Where developers can run this individually.

I have my own personal CI where I keep some of my jobs, to help me with me with my daily tasks.
I'm not sure the apache CI is a good place for this. I think developers and release managers
can make sure this won't be broken before a release. The apache CI is already clouded, I don't
want to add something that will take some extra time.

> Run `mvn -Pexamples verify` in the CI
> -------------------------------------
>                 Key: ARTEMIS-555
>                 URL:
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Jiri Danek
>            Assignee: clebert suconic
>             Fix For: 1.4.0
> I believe that Artemis examples should be verified as part of the CI process. This would
ensure that examples are always in a working state. 
> Examples that do not require manual interaction can be all executed by the following
two commands
> {{cd examples}}
> {{mvn -Pexamples verify}}
> as a practical consideration, second command may need to be adapted to
> {noformat}
> mvn -Pexamples verify -pl \!:large-message
> {noformat}
> because example large-message creates 4GB garbage on disk that is not cleaned up and
because it runs as long as all the other examples combined.
> In case examples are already part of CI, I apologize for this Jira and would like to
ask for a link to Jenkins results.

This message was sent by Atlassian JIRA

View raw message