1. 08 Sep, 2017 1 commit
  2. 07 Sep, 2017 1 commit
  3. 06 Sep, 2017 4 commits
  4. 05 Sep, 2017 1 commit
  5. 04 Sep, 2017 1 commit
  6. 01 Sep, 2017 1 commit
  7. 31 Aug, 2017 1 commit
  8. 28 Aug, 2017 2 commits
  9. 25 Aug, 2017 2 commits
  10. 24 Aug, 2017 2 commits
  11. 18 Aug, 2017 2 commits
  12. 16 Aug, 2017 1 commit
  13. 15 Aug, 2017 1 commit
  14. 14 Aug, 2017 2 commits
  15. 11 Aug, 2017 3 commits
  16. 08 Aug, 2017 2 commits
  17. 04 Aug, 2017 1 commit
  18. 02 Aug, 2017 1 commit
  19. 01 Aug, 2017 1 commit
  20. 24 Jul, 2017 1 commit
  21. 20 Jul, 2017 2 commits
  22. 19 Jul, 2017 1 commit
  23. 18 Jul, 2017 1 commit
  24. 13 Jul, 2017 1 commit
  25. 10 Jul, 2017 1 commit
  26. 07 Jul, 2017 3 commits
    • Achilleas Pipinellis's avatar
      7bf9a3dd
    • Achilleas Pipinellis's avatar
      b5c7aad7
    • Timothy Andrew's avatar
      Test logging in via the Authentiq OAuth provider in a feature spec. · d7b22ce1
      Timothy Andrew authored
      - The `migration:path-pg` build was previously failing when the Authentiq
        feature spec was enabled by placing Authentiq configuration in the `test`
        section of `gitlab.yml`
      
      - The `migration:path-pg` task checks out an old revision of the
        codebase (`v8.14.10`) and runs a `schema:load`. It then checks out the commit
        under test, and runs `db:migrate`, to verify that migrations run without
        errors.
      
      - The problem here is that `v8.14.10` does not have the Authentiq module
        installed, but is run with the `gitlab.yml` for `master`, which would contain
        the `Authentiq` configuration in the `test` section.
      
      - The solution was to use the `v8.14.10` `gitlab.yml` for the `schema:load`,
        rather than the `gitlab.yml` from master.
      d7b22ce1