BigW Consortium Gitlab

  1. 06 Apr, 2017 2 commits
  2. 05 Apr, 2017 1 commit
  3. 20 Mar, 2017 2 commits
    • Simplify Ci::Build#dependencies method · 45f1975d
      Tomasz Maczukin authored
    • Send only defined dependencies · c191c110
      Tomasz Maczukin authored
      In APIv1 we've been sending all jobs from previous stages and
      a `dependencies` list with names of jobs that user want to download
      artifacts from. This was selected on Runners side.
      
      In APIv1 we've planned to send only jobs that were defined (if any; and
      all previous jobs by default). However I've missed the fact that
      it was Runner who selected jobs, not GitLab. And now current version
      of APIV4 sends all jobs everytime.
      
      This commit fixes this. If user will define `dependencies` in his job,
      then GitLab will send only selected jobs.
  4. 17 Mar, 2017 1 commit
  5. 07 Mar, 2017 3 commits
  6. 06 Mar, 2017 7 commits
  7. 02 Mar, 2017 2 commits
  8. 01 Mar, 2017 1 commit
  9. 23 Feb, 2017 8 commits
  10. 16 Feb, 2017 1 commit
  11. 15 Feb, 2017 3 commits
  12. 14 Feb, 2017 1 commit
  13. 13 Feb, 2017 2 commits
  14. 06 Feb, 2017 2 commits
  15. 03 Feb, 2017 1 commit
    • Skip or retain project while deleting the project: · aaf382d5
      Lin Jen-Shin authored
      * Skip Ci::Build#update_project_statistics whenever there's no
        project (i.e. we're deleting the project!)
      * Retain the unscoped_project before deleting the build,
        so that we could use the data to delete the artifacts.
        Note that carrierwave uses `after_commit` for this,
        so we need to retain it in the memory.
      
      Closes #15005
  16. 31 Jan, 2017 2 commits
    • Add GitLab Pages · 120f9aba
      Kamil Trzcinski authored
      - The pages are created when build artifacts for `pages` job are uploaded
      - Pages serve the content under: http://group.pages.domain.com/project
      - Pages can be used to serve the group page, special project named as host: group.pages.domain.com
      - User can provide own 403 and 404 error pages by creating 403.html and 404.html in group page project
      - Pages can be explicitly removed from the project by clicking Remove Pages in Project Settings
      - The size of pages is limited by Application Setting: max pages size, which limits the maximum size of unpacked archive (default: 100MB)
      - The public/ is extracted from artifacts and content is served as static pages
      - Pages asynchronous worker use `dd` to limit the unpacked tar size
      - Pages needs to be explicitly enabled and domain needs to be specified in gitlab.yml
      - Pages are part of backups
      - Pages notify the deployment status using Commit Status API
      - Pages use a new sidekiq queue: pages
      - Pages use a separate nginx config which needs to be explicitly added
  17. 25 Jan, 2017 1 commit