An error occurred fetching the project authors.
  1. 11 Sep, 2017 1 commit
  2. 08 Sep, 2017 1 commit
    • Rubén Dávila's avatar
      Revert "Merge branch... · 52a2423e
      Rubén Dávila authored
      Revert "Merge branch '35012-navigation-add-option-to-change-navigation-color-palette' into 'master'"
      
      This reverts merge request !13619
      52a2423e
  3. 06 Sep, 2017 5 commits
  4. 04 Sep, 2017 1 commit
  5. 30 Aug, 2017 1 commit
  6. 16 Aug, 2017 1 commit
    • Bob Van Landuyt's avatar
      Use better higher threshold settings for storage access in tests · 93d56eb2
      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
      93d56eb2
  7. 07 Aug, 2017 1 commit
  8. 04 Aug, 2017 1 commit
  9. 31 Jul, 2017 1 commit
  10. 26 Jul, 2017 4 commits
  11. 17 Jul, 2017 1 commit
  12. 07 Jul, 2017 2 commits
    • Jacob Vosmaer's avatar
      78089d11
    • Timothy Andrew's avatar
      Test logging in via the Authentiq OAuth provider in a feature spec. · d53690b6
      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.
      d53690b6
  13. 06 Jul, 2017 6 commits
  14. 05 Jul, 2017 1 commit
  15. 04 Jul, 2017 4 commits
  16. 03 Jul, 2017 2 commits
    • Timothy Andrew's avatar
      Fix build for !11963. · 9a0f5bd5
      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`
      9a0f5bd5
    • Timothy Andrew's avatar
      Add Omniauth OAuth config to the test section of `gitlab.yml` · a931ead0
      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.
      a931ead0
  17. 20 Jun, 2017 2 commits
  18. 19 Jun, 2017 1 commit
  19. 07 Jun, 2017 1 commit
  20. 02 Jun, 2017 2 commits
  21. 01 Jun, 2017 1 commit