1. 21 Jan, 2016 1 commit
  2. 20 Jan, 2016 12 commits
  3. 19 Jan, 2016 10 commits
  4. 18 Jan, 2016 9 commits
  5. 17 Jan, 2016 1 commit
    • Dmitriy Zaporozhets's avatar
      Merge branch 'issue-page-keeps-jumping-up' into 'master' · cd3f27b9
      Dmitriy Zaporozhets authored
      Issue page keeps jumping up
      
      This happens when the discussion side is smaller than the sidebar and the sidebar will need to scroll. When this happens I calculate the height of the two and see if the discussion panel is smaller and make them the same height and add a class `no-affix` which makes the sidebar relative positioning so it won't stick to the top.
      
      See merge request !2417
      cd3f27b9
  6. 16 Jan, 2016 1 commit
  7. 15 Jan, 2016 6 commits
    • Robert Speicher's avatar
      Merge branch 'rs-silence-statemachine-in-cron' into 'master' · 1c233ff5
      Robert Speicher authored
      Prevent StateMachine warnings from outputting during a cron task
      
      [ci skip]
      
      Closes #5931
      
      See merge request !2458
      1c233ff5
    • Robert Speicher's avatar
      Merge branch 'fix-autocomplete-new-issues' into 'master' · 1f1eed47
      Robert Speicher authored
      Fix autocomplete for new issues/MRs/snippets
      
      Fixes gitlab-org/gitlab-ce#8067
      
      See merge request !2446
      1f1eed47
    • Robert Speicher's avatar
      Merge branch 'master' into 8-4-stable · afda4835
      Robert Speicher authored
      afda4835
    • Jacob Schatz's avatar
      Merge branch 'fix-alignment-issue' into 'master' · d04eadf8
      Jacob Schatz authored
      Fix alignment issues after a fix on titles weight
      
      Fixes #8102. Fixes #3956. This fixes an alignment regression introduced by !2422. Sorry about that! :/
      
      ## Commit title alignment fixed
      
      ![Screen_Shot_2016-01-14_at_16.10.01](/uploads/8fdc08dca379bc551f5872de910c7149/Screen_Shot_2016-01-14_at_16.10.01.png)
      
      **The fact that the first row has a smaller height than the other rows was not introduced by !2422 (I've checked by reverting 818607f0 on `master`).**
      
      ## Tags name in list
      
      ![Screen_Shot_2016-01-14_at_16.10.09](/uploads/fba3978037677bb8855f374b5f38dde0/Screen_Shot_2016-01-14_at_16.10.09.png)
      
      See merge request !2431
      d04eadf8
    • Douwe Maan's avatar
      Merge branch 'ci/build_dependencies' into 'master' · c19795df
      Douwe Maan authored
      Let the CI runner know about builds that this build depends on
      
      This allows us to implement artifacts passing: runner will download artifacts from all prior builds. It will happen automatically, and always, as long as artifacts are enabled.
      
      ## The changes:
      
      This MR exposes list of prior builds in CI::API::Builds.
      
      **The API response when asking for builds**
      
      ```json
      {
        "id": 48584,
        "ref": "0.1.1",
        "tag": true,
        "sha": "d63117656af6ff57d99e50cc270f854691f335ad",
        "status": "success",
        "name": "pages",
        "token": "9dd60b4f1a439d1765357446c1084c",
        "stage": "test",
        "project_id": 479,
        "project_name": "test",
        "commands": "echo commands",
        "repo_url": "http://gitlab-ci-token:token@gitlab.example/group/test.git",
        "before_sha": "0000000000000000000000000000000000000000",
        "allow_git_fetch": false,
        "options": {
          "image": "docker:image",
          "artifacts": {
            "paths": [
              "public"
            ]
          },
          "cache": {
            "paths": [
              "vendor"
            ]
          }
        },
        "timeout": 3600,
        "variables": [
          {
            "key": "CI_BUILD_TAG",
            "value": "0.1.1",
            "public": true
          }
        ],
        "dependencies": {
          "builds": [
            {
              "id": 48584,
              "ref": "0.1.1",
              "tag": true,
              "sha": "d63117656af6ff57d99e50cc270f854691f335ad",
              "status": "success",
              "name": "build",
              "token": "9dd60b4f1a439d1765357446c1084c",
              "stage": "build",
              "project_id": 479,
              "project_name": "test",
              "artifacts_file": {
                "filename": "artifacts.zip",
                "size": 0
              }
            }
          ]
        }
      }
      ```
      
      ## How it will work?
      
      **Example:**
      ```
      build:
        type: build
        script:
        - echo TEST > test_file
        artifacts:
          untracked: true
      
      rspec:
        type: test
        script:
        - test-my-project
      
      staging:
        type: deploy
        script:
        - scp test_file root@server.com:
      ```
      
      **The flow:**
      1. We run `build`. The `build` creates a file `test_file`. This file gets archived and send us build artifacts.
      2. We run `rspec`. The `rspec` downloads build artifacts from `build`. Uses the `test_file`.
      3. We run `staging`. The `staging` downloads build artifacts from `build` and `rspec`, but since the `rspec` doesn't have build artifacts we skip that build. Deploys the `test_file`.
      
      This partially implements the https://gitlab.com/gitlab-org/gitlab-ce/issues/3423.
      
      In the next release we will introduce option to configure what artifacts are received.
      
      /cc @grzesiek @DouweM @sytse @rspeicher
      
      
      See merge request !2437
      c19795df
    • Douwe Maan's avatar
      Merge branch 'feature/allow-artifacts-for-reporters' into 'master' · 57d8faf6
      Douwe Maan authored
      Allow access to artifacts for users with reporter role
      
      This is originally introduced by @ajohnsn in this merge request: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/2259
      
      I've added and refactored specs, original commit by @ajohnsn has been cherry picked here.
      
      See merge request !2448
      57d8faf6