Re: [keycloak-dev] Keycloak Node.js adapter integration tests on Travis
I agree it should test with something at least close to master. Question is
should all the repos build Keycloak themselves?
We could have Docker images automatically built/hosted on Docker hub?
There's already a nightly (seems to be broken atm, but that's fixable).
That may be more efficient than building, especially considering Maven
dependencies.
On Mon, 13 Aug 2018 at 14:13, Sebastien Blanc <sblanc(a)redhat.com> wrote:
+1 , we should always rely on master.
On Mon, Aug 13, 2018 at 3:23 PM, Bruno Oliveira <bruno(a)abstractj.org>
wrote:
> Good morning,
>
> Last week Pedro submitted a PR to the Node.js adapter, but the build is
> failing because it depends on the changes from Keycloak server master
> branch.
>
> Today we download the latest stable release from Keycloak to run the
> integration tests for this adapter. I would like to change it and follow
> the same approach from the Quickstarts, which means clone/build/run
> Keycloak server from master. In this way, we can always it test against
> the latest changes.
>
> Thoughts?
>
>
> --
>
> abstractj
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev