Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Snippets
  • Sign up now
  • Login
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 46,617
    • Issues 46,617
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,533
    • Merge requests 1,533
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #10229
Closed
Open
Issue created Mar 06, 2019 by Francisco Javier López@fjsanpedro🔴Contributor

Package CI build services for the Web IDE

In order to ship CI build services, we need to decide how are we going to deliver them. I think we have several alternatives:

  • Build a global docker image with all the services. Sincerely, I'm not a fan of this option because:
    • we need to build a big docker image
    • all the services ports will be under the image section
    • we have to tweak every service because otherwise, we can have a lot of port collisions.
    • if we add a new service we need to rebuild the image
  • Build a custom image per each service. This is the option I like most because it's more simple
  • Use a default image and use script, entrypoint, and command to clone the service repo and run it. I think this is more complicated and we will force the users to add more info by themselves to the .gitlab-webide.yml.

/cc @ayufan @steveazz @jramsay

Edited Mar 06, 2019 by Francisco Javier López
Assignee
Assign to
Time tracking