BigW Consortium Gitlab

  1. 28 Apr, 2017 1 commit
  2. 24 Apr, 2017 2 commits
  3. 03 Apr, 2017 2 commits
  4. 23 Mar, 2017 1 commit
  5. 06 Mar, 2017 2 commits
  6. 22 Feb, 2017 1 commit
  7. 06 Feb, 2017 2 commits
  8. 18 Jan, 2017 1 commit
  9. 03 Jan, 2017 2 commits
  10. 11 Dec, 2016 1 commit
  11. 04 Dec, 2016 2 commits
  12. 02 Dec, 2016 1 commit
  13. 30 Nov, 2016 1 commit
  14. 28 Nov, 2016 1 commit
    • Speed up Project security access specs · 13ad9a74
      Robert Speicher authored
      Prior, every single test was creating four `ProjectMember` objects, each
      of which created one `User` record, even though each test only used
      _one_ of those Users, if any.
      
      Now each test only creates the single user record it needs, if it needs
      one. This shaves minutes off of each spec file changed here.
  15. 05 Nov, 2016 1 commit
    • Add missing security specs for raw snippet access · 80a2e3a9
      the-undefined authored
      Each project visibility type (Public, Internal, Private) has an access
      feature spec to catch security regressions. This commit adds relevent
      tests for the raw snippet path in each of these project access specs.
      
      Refacotrings:
      
      - Use an empty project factory for access specs
  16. 11 Oct, 2016 1 commit
  17. 19 Aug, 2016 1 commit
    • Support integration with Koding (online IDE) · a927a9bf
      Gokmen Goksel authored
      Koding: #index: landing page for Koding integration
      
      If enabled it will provide a link to open remote Koding instance url
      for now we are also providing the sneak preview video for how
      integration works in detail.
      
      Repository: check whether .koding.yml file exists on repository
      
      Projects: landing page: show Run in IDE (Koding) button if repo has stack file
      
      Projects: MR: show Run in IDE Koding button if repo has stack file on active branch
      
      ProjectHelpers: add_koding_stack: stack generator for provided project
      
      With this helper we will auto-generate the required stack template
      for a given project. For the feature we can request this base template
      from the running Koding instance on integration.
      
      Currently this will provide users to create a t2.nano instance on aws
      and it'll automatically configures the instance for basic requirements.
      
      Projects: empty state and landing page provide shortcuts to create stack
      
      projects_helper: use branch on checkout and provide an entry point
      
      This ${var.koding_queryString_branch} will be replaced with the branch
      provided in query string which will allow us to use same stack template
      for different branches of the same repository.
      
      ref: https://github.com/koding/koding/pull/8597/commits/b8c0e43c4c24bf132670aa8a3cfb0d634acfd09b
      
      projects_helper: provide sha info in query string to use existing vms
      
      With this change we'll be able to query existing vms on Koding side
      based on the commit id that they've created.
      
      ref: https://github.com/koding/koding/pull/8597/commits/1d630fadf31963fa6ccd3bed92e526761a30a343
      
      Integration: Docs: Koding documentation added
      
      Disable /koding route if integration is disabled
      
      Use application settings to enable Koding
      
      Projects_helper: better indentation with strip_heredoc usage
      
      Projects_helper: return koding_url as is if there is no project provided
      
      current_settings: set koding_enabled: false by default
      
      Koding_Controller: to render not_found once integration is disabled
      
      Dashboard_specs: update spec for Koding enabled case
      
      Projects_Helper: make repo dynamic
      
      ref: https://github.com/koding/koding/pull/8597/commits/4d615242f45aaea4c4986be84ecc612b0bb1514c
      
      Updated documentation to have right format
  18. 15 Jul, 2016 1 commit
  19. 01 Jul, 2016 1 commit
  20. 23 Jun, 2016 1 commit
  21. 16 Jun, 2016 2 commits
  22. 14 Jun, 2016 1 commit
  23. 03 Jun, 2016 2 commits
  24. 18 Apr, 2016 1 commit
  25. 25 Mar, 2016 1 commit
  26. 21 Mar, 2016 1 commit
  27. 20 Mar, 2016 1 commit
  28. 19 Mar, 2016 1 commit
  29. 17 Mar, 2016 1 commit
  30. 16 Mar, 2016 1 commit
  31. 13 Mar, 2016 2 commits