> On Aug 28, 2018, at 1:27 PM, Stefan Seelmann <m...@stefan-seelmann.de> wrote: > >> https://builds.apache.org/view/D/view/Directory/job/dir-fortress-core-docker-openldap-test/configure >> >> It doesn't use the run-tests.sh script at all. All the instructions are >> duplicated there. I guess I did that, not a nice move, but I don't >> remember why... >> >> Probably the easiest change is to use that script in Jenkins, I'll try.. > > I created a 2nd one for now, which works when setting maven and java > home env variables (there is no global maven configured which is fine) > https://builds.apache.org/view/D/view/Directory/job/dir-fortress-core-docker-openldap-test-2 > > If you want we can delete the old one and rename this. Using the old one > won't work because that's a "Maven" job type while the other is just a > "Freestyle" job type.
A new test is fine, assuming the old one is disabled. Or, we can rename it. Either way works for me. > > On Aug 28, 2018, at 1:27 PM, Stefan Seelmann <m...@stefan-seelmann.de> wrote: > > Using the shell script is not optimal because it may leave back the > running OpenLDAP container in case something fails in the middle. I > think the cleanest solution would be to specify the build in a > Jenkinsfile. I started to create one for the LDAP API and the server, > but they need to be reworked, I'm still learning. Agreed. Anything I can do to help? —Shawn
