1. 26 Apr, 2016 7 commits
  2. 25 Apr, 2016 2 commits
  3. 20 Apr, 2016 1 commit
  4. 19 Apr, 2016 2 commits
  5. 07 Apr, 2016 4 commits
  6. 05 Apr, 2016 3 commits
  7. 17 Mar, 2016 3 commits
  8. 12 Jan, 2016 3 commits
  9. 11 Jan, 2016 11 commits
  10. 10 Jan, 2016 2 commits
  11. 08 Jan, 2016 1 commit
    • Stan Hu's avatar
      Merge branch 'suppress-allow-failure-builds' into 'master' · 34d0f226
      Stan Hu authored
      Suppress e-mails on failed builds if allow_failure is set
      
      Every time I push to GitLab, I get > 2 emails saying a spec failed when I don't care about the benchmarks and others that have `allow_failure` set to `true`.
      
      @ayufan mentioned creating a summary e-mail to prevent getting one e-mail per build, but the latter might actually be desirable. For example, I do want to know if Rubocop errors fail right away.
      
      See merge request !2178
      34d0f226
  12. 06 Jan, 2016 1 commit
    • Robert Speicher's avatar
      Merge branch 'merge-when-build-succeeds-unchecked' into 'master' · f076e4eb
      Robert Speicher authored
      Get "Merge when build succeeds" to work when commits were pushed to MR
      target branch while builds were running
      
      The Merge when build succeeds service only merges when the MR is
      mergeable (open, not WIP, no conflicts).
      
      When the target branch is updated, all affected MRs have their merge
      status set to `unchecked`, and the conflicts check will only happen
      when `check_if_can_be_merged` is called, which happens when the MR page
      is viewed.
      
      When someone enables the automatic merge, the target branch is updated,
      no-one views the MR page again, and the build succeeds, the mergeability
      check will fail and the MR will not in fact be merged.
      
      This MR makes sure `check_if_can_be_merged` is always called when MR
      mergeability is checked.
      
      See merge request !2304
      f076e4eb