1. 04 Sep, 2017 1 commit
  2. 29 Aug, 2017 1 commit
  3. 13 Aug, 2017 1 commit
    • Bob Van Landuyt's avatar
      Use better higher threshold settings for storage access in tests · 676788ea1bb1
      Bob Van Landuyt authored
      `failure_count_threshold`: We should never need this, but we don't
      want to block access in tests because of this.
      
      `failure_wait_time`: Setting it to 0 now allows each storage attempt
      
      `storage_timeout`: Try a bit longer to access storage on CI in case
      the slow machines take a bit longer to spin up the process to perfom
      the check
      676788ea1bb1
  4. 07 Aug, 2017 1 commit
  5. 17 May, 2017 1 commit
  6. 31 Jul, 2017 1 commit
  7. 13 Jun, 2017 1 commit
  8. 12 Jun, 2017 1 commit
  9. 09 Jun, 2017 1 commit
  10. 06 Jun, 2017 1 commit
  11. 19 Jul, 2017 1 commit
  12. 17 Jul, 2017 1 commit
  13. 11 Jul, 2017 1 commit
  14. 04 Jul, 2017 1 commit
  15. 03 Jul, 2017 2 commits
  16. 07 Jul, 2017 2 commits
  17. 06 Jul, 2017 1 commit
  18. 03 Jul, 2017 1 commit
  19. 21 Jun, 2017 1 commit
  20. 07 Jul, 2017 3 commits
    • Douwe Maan's avatar
      Merge branch '34737-authentiq-oauth-feature-spec' into 'master' · aafcbac10623
      Douwe Maan authored
      Test logging in via the Authentiq OAuth provider in a feature spec
      
      Closes #34737
      
      See merge request !12694
      aafcbac10623
    • Timothy Andrew's avatar
      Test logging in via the Authentiq OAuth provider in a feature spec. · b5902e2b6f26
      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.
      b5902e2b6f26
    • Sean McGivern's avatar
      Merge branch 'gitaly-mandatory' into 'master' · 7c324912173c
      Sean McGivern authored
      Remove option to disable Gitaly in Rails
      
      See merge request !12677
      7c324912173c
  21. 06 Jul, 2017 3 commits
  22. 03 Jul, 2017 1 commit
    • Timothy Andrew's avatar
      Fix build for !11963. · 64e359e5139a
      Timothy Andrew authored
      - Don't use `request.env['omniauth.params']` if it isn't present.
      
      - Remove the `saml` section from the `gitlab.yml` test section. Some tests
        depend on this section not being initially present, so it can be overridden
        in the test. This MR doesn't add any tests for SAML, so we didn't really need
        this in the first place anyway.
      
      - Clean up the test -> omniauth section of `gitlab.yml`
      64e359e5139a
  23. 19 Jun, 2017 1 commit
    • Timothy Andrew's avatar
      Add Omniauth OAuth config to the test section of `gitlab.yml` · 02026f8a65da
      Timothy Andrew authored
      - I tried to get this to work by stubbing out portions of the config within the
        test. This didn't work as expected because Devise/Omniauth loaded before the
        stub could run, and the stubbed config was ignored.
      
      - I attempted to fix this by reloading Devise/Omniauth after stubbing the
        config. This successfully got Devise to load the stubbed providers, but failed
        while trying to access a route such as `user_gitlab_omniauth_authorize_path`.
      
      - I spent a while trying to figure this out (even trying
        `Rails.application.reload_routes!`), but nothing seemed to work.
      
      - I settled for adding this config directly to `gitlab.yml` rather than go down
        this path any further.
      02026f8a65da
  24. 05 Jul, 2017 2 commits
  25. 03 Jul, 2017 1 commit
    • Timothy Andrew's avatar
      Fix build for !11963. · 3bd94c69c503
      Timothy Andrew authored
      - Don't use `request.env['omniauth.params']` if it isn't present.
      
      - Remove the `saml` section from the `gitlab.yml` test section. Some tests
        depend on this section not being initially present, so it can be overridden
        in the test. This MR doesn't add any tests for SAML, so we didn't really need
        this in the first place anyway.
      
      - Clean up the test -> omniauth section of `gitlab.yml`
      3bd94c69c503
  26. 19 Jun, 2017 1 commit
    • Timothy Andrew's avatar
      Add Omniauth OAuth config to the test section of `gitlab.yml` · d4e515989c78
      Timothy Andrew authored
      - I tried to get this to work by stubbing out portions of the config within the
        test. This didn't work as expected because Devise/Omniauth loaded before the
        stub could run, and the stubbed config was ignored.
      
      - I attempted to fix this by reloading Devise/Omniauth after stubbing the
        config. This successfully got Devise to load the stubbed providers, but failed
        while trying to access a route such as `user_gitlab_omniauth_authorize_path`.
      
      - I spent a while trying to figure this out (even trying
        `Rails.application.reload_routes!`), but nothing seemed to work.
      
      - I settled for adding this config directly to `gitlab.yml` rather than go down
        this path any further.
      d4e515989c78
  27. 04 Jul, 2017 1 commit
  28. 20 Jun, 2017 2 commits
  29. 16 Jun, 2017 1 commit
  30. 06 Jun, 2017 1 commit
  31. 19 May, 2017 2 commits