On 7/11/21 5:53 PM, Shawn McKinney wrote: > >> On Jul 11, 2021, at 9:42 AM, Emmanuel Lécharny <[email protected]> wrote: >> >> I do think that we need some faster way to validate the packages. It took me >> around 1h30 to do that last night, most of it being waiting for the tests to >> be ran. > > By tests you mean integration tests, i.e. junit? > > If yes, that’s surprising. It runs in about 7 or 8 minutes for me.
The tests against ApacheDS are quite slow and also take more than one hour for me. See also the Jenkins build [3] which most of the time only runs the IT once and fails with some timing issues. > What test suite are you running? > >> Can we design a script that does all the steps automatically, including the >> signature verifications and N&L checks? >> >> I mean, technically, it's a no brainer, but from the validation PoV, could >> we assume that running the script and get a positive response as a 'Good to >> Go' signal ? > > I don’t see why not. The question, is how to manage the platform specifics > of the target. > > I’ve been using Ansible which creates a new fortress env by scratch. > Currently, it sets up OpenLDAP for the run, adding apacheDS has been on my > todo list for some time. > > Could add a playbook for validating the packages. > > Open to ideas here. There already exist two scripts to run the fortress-core intgraion tests against ApacheDS [1] or OpenLDAP [2]. Those are also used in the Jenkins builds [3][4]. Both require a a Docker installation though. Kind Regards, Stefan [1] https://github.com/apache/directory-fortress-core/tree/master/src/docker/apacheds-for-apache-fortress-tests [2] https://github.com/apache/directory-fortress-core/tree/master/src/docker/openldap-for-apache-fortress-tests [3] https://ci-builds.apache.org/job/Directory/job/dir-fortress-core-docker-apacheds-test/ [4] https://ci-builds.apache.org/job/Directory/job/dir-fortress-core-docker-openldap-test/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
