<div dir="ltr">+1 Main thing is we need it to run on Central CI. If you can also make it easy to run it on a workstation that'd be great. Maybe with a Docker image?<div><br></div><div>Even if you could manage to get it running on Travis we'd probably not want to as there's a tradeoff on how long it takes to test a PR and the amount of tests to run.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 13 September 2016 at 04:42, Marek Posolda <span dir="ltr"><<a href="mailto:mposolda@redhat.com" target="_blank">mposolda@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Bruno,<br>
<br>
the question is if we really need FreeIPA on Travis CI? The thing is<br>
that Travis is currently just the CI for run "mvn clean install" when<br>
you send PR to find regressions early. However we have already lots of<br>
tests, which are not executed during default travis build. For example:<br>
- Adapter tests in new testsuite.<br>
- Tests with Keycloak on real Wildfly server (by default testsuite uses<br>
just embedded undertow)<br>
- Test with other DBs than embedded H2<br>
- Test with other LDAPs than embedded ApacheDS<br>
<br>
IMO It's fine if FreeIPA tests are executed just when you run the build<br>
with some special maven profile. Hence we will have job on central CI,<br>
which will test FreeIPA on daily basis. However those tests won't be<br>
executed during default "mvn clean install" build and hence also not<br>
executed on travis during every build. So defacto approach 1 from what<br>
you mentioned.<br>
<br>
But maybe it's just me :)<br>
<span class="HOEnZb"><font color="#888888"><br>
Marek<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On 12/09/16 23:02, Bruno Oliveira wrote:<br>
> Ahoy, this week I will start to look at the integration tests for<br>
> FreeIPA/SSSD with Ilya from QE. He already started some work here[1].<br>
> The tricky part for me is to spin up a FreeIPA server on Travis CI.<br>
><br>
> For those not familiar with this environment, to run the<br>
> integration tests, freeipa-server must be installed/configured.<br>
> Unfortunately, Ubuntu Precise (the distro running on Travis)<br>
> have only freeipa-client and python-freeipa[2].<br>
><br>
> Some ideas to make this happen:<br>
><br>
> 1. Do nothing and let people run the integration tests locally. This is not awesome.<br>
> 2. Spin up a FreeIPA docker instance on Travis before the build, plus<br>
> install and configure a freeipa-client. The downside is: more steps,<br>
> more slowness on Travis.<br>
> 3. Move the CI to our own server and have FreeIPA installed and<br>
> configured.<br>
><br>
> Ideas?<br>
><br>
> [1] - <a href="https://github.com/abstractj/keycloak/commit/534569a9b6082a9674a33149519b06d1218d4807" rel="noreferrer" target="_blank">https://github.com/abstractj/<wbr>keycloak/commit/<wbr>534569a9b6082a9674a33149519b06<wbr>d1218d4807</a><br>
> [2] - <a href="https://launchpad.net/ubuntu/precise/+source/freeipa" rel="noreferrer" target="_blank">https://launchpad.net/ubuntu/<wbr>precise/+source/freeipa</a><br>
><br>
> --<br>
><br>
> abstractj<br>
> PGP: 0x84DC9914<br>
> ______________________________<wbr>_________________<br>
> keycloak-dev mailing list<br>
> <a href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/keycloak-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/keycloak-dev</a><br>
<br>
<br>
______________________________<wbr>_________________<br>
keycloak-dev mailing list<br>
<a href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/keycloak-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/keycloak-dev</a><br>
</div></div></blockquote></div><br></div>