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,752
    • Issues 46,752
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,520
    • Merge requests 1,520
  • 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
  • #201458
Closed (moved) (moved)
Open
Issue created Feb 02, 2020 by Mark Pundsack@markpundsackContributor

Automate the transformation of a codebase into a build

Problem to solve

Developers want to focus on writing code to solve their business problem. But there's a ton of other work needed to get that code transformed into an executable build and then more work needed to get that build running in production. We already have Auto DevOps to help streamline that process. If there's no Dockerfile present, Auto DevOps leverages Heroku Buildpacks via Herokuish to automatically transform a codebase into a build. There are some problems with this approach:

  1. It only works for a handful of languages
  2. It's from a legacy generation and doesn't leverage Docker very efficiently
  3. Some buildpacks understand how to run CI tests, but not all
  4. The Heroku buildpack specification knows nothing about how to run security scanning, code quality, and other types of scans that should be part of your CI/CD configuration.

Intended users

  • Delaney (Development Team Lead)
  • Sasha (Software Developer)
  • Devon (DevOps Engineer)

Further details

There's a new effort, Cloud Native Buildpacks, buildpacks.io, which aims to address some of the above, but not all of it. We could augment Cloud Native Buildpacks to support the missing pieces, and contribute those changes upstream. We could also explore other third-party efforts to see if they have a better fundamental approach. We could also develop something ourselves to handle this.

Proposal

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Links / references

Assignee
Assign to
Time tracking