General

This feature request forum allows you to submit, comment on and vote for GitLab CE/EE/CI features.

I suggest you ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can vote and comment on it.

If it doesn't exist, you can post your idea so others can vote on it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  1. Maybe it should be possible to have a build script per branch if needed

    By having different build scripts for branches (if activated) you can do different Build Jobs on e.g. the development branch and the release branch. (E.g. normally build and code checks on development branch and build, packing and deployment on release branch)

    249 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      7 comments  ·  GitLab CI  ·  Admin →
    • Store build configuration in the repo (like .travis.yml)

      Travis CI's .travis.yml files are a godsend when maintaining large numbers of repositories, and GitLab CI would really benefit from a similar system (maybe .gitlab.yml). We have an in-house framework with many small components that are all tested/built in exactly the same fashion. If we make changes to our build scripts, a web interface becomes a tedious bottleneck in the process. This would also solve the current most popular idea ("Maybe it should be possible to have a build script per branch if needed") because each branch can simply have a different .gitlab.yml as required.

      170 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        I agree to the terms of service
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        9 comments  ·  GitLab CI  ·  Admin →
      • Display timeline of build metrics like coverage e.t.c.

        I use Gitlab CI for hardware synthesis. There are a number of metrics that characterize the build, e.g. test coverage, maximum frequency of the circuit, resource usage, number of tests and possibly others.

        It would be nice to see a timeline for those metrics over the build numbers like here:

        http://www.legup.org:9100/perf/dashboard/overview.html

        There should be some mechanism to extract the metrics either directly from the logfile (maybe like grep?) or the build must produce a file with some t.b.d format which contains the metrics for that build.

        sidekiq uses rickshaw for displaying a graph. That could be the way for the…

        150 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          I agree to the terms of service
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          7 comments  ·  GitLab CI  ·  Admin →
        • Allow access to build artifacts of GitLab CI

          We have an Git-Repro witth tex-Files and let them compile by gitlab-ci, it would be cool if we could access the generated pdfs or a zip folder of the result, or any compiled file directly when viewing it in Gitlab and get so more user-friendly, maybe you can select one file or designate its name that will be uploaded as result of the build script

          114 votes
          Vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            I agree to the terms of service
            Signed in as (Sign out)
            You have left! (?) (thinking…)
            12 comments  ·  GitLab CI  ·  Admin →

            We thinking about allowing the runners to upload build artifacts to the GitLab CI coordinators. These files can than be linked from the build page. We’re open to proposals on how to design this. We’re also open to proposals that just upload the complete working directory.

          • Several independent build projects should be possible per Gitlab project

            Gitlab CI should allow to add the same Gitlab project several times (with different titles)

            We would like to see the possibility of separating builds that do unit tests from builds that run integration tests in Gitlab CI.

            In our specific use case, we always have a passing and a failing test suite. The failing test suite represents our roadmap (e.g. as soon as all these tests pass, the new release is done). It is impractical to run both suites in the same build project, because it would never be successful.

            Also, that would make it possible to have the…

            110 votes
            Vote
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              I agree to the terms of service
              Signed in as (Sign out)
              You have left! (?) (thinking…)
              2 comments  ·  GitLab CI  ·  Admin →
            • GitLab CI should push successful builds to an external repo

              Sometimes the production environment uses a different repo. To have continues delivery we could push to that repo automatically.

              We could just add a push target and generate a public/private key for each project. The public key would be added to the external repo.

              People that want to promote each build would just run a command that always exists successfully, so use "ls" instead of "bundle exec rake spec".

              The push command can be something like `git push --mirror --force remote_push_url`.

              73 votes
              Vote
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                I agree to the terms of service
                Signed in as (Sign out)
                You have left! (?) (thinking…)
                8 comments  ·  GitLab CI  ·  Admin →
              • Add support for test results parsing

                I think is very useful to read the test results.
                A support for parsing/view xml-junit-compliant will cover many tools that use the junit-xml format.

                72 votes
                Vote
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  I agree to the terms of service
                  Signed in as (Sign out)
                  You have left! (?) (thinking…)
                  4 comments  ·  GitLab CI  ·  Admin →
                • Build project on all runners instead of only one

                  Gitlab CI triggers a build only on a single runner from the pool of available runners. This does not fit our needs since we have multiple runners for different operating systems and want to test whether the project builds well on all the different systems.

                  Another idea would be to allow creating multiple Gitlab CI projects for a Gitlab Repo/Project and manually assign the appropriate runners to those projects. But this feels like a workaround and brings a lot of additional configuration overhead.

                  69 votes
                  Vote
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    I agree to the terms of service
                    Signed in as (Sign out)
                    You have left! (?) (thinking…)
                    1 comment  ·  GitLab CI  ·  Admin →
                  • preview / render static html pages pushed to repositories (or gl-pages equivalent to gh-pages)?

                    For our working group we have a git-first-steps repo which contains an html presentation with "first steps"... Not only for presentations, but also for js demos, etc. it would be cool if gitlab allowed to "host" this out of the box.

                    Security needs some thought in this case though... (think about pushing a specially crafted html and sending a link to an admin). Maybe have it on a subdomain like "preview."... ?

                    63 votes
                    Vote
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      I agree to the terms of service
                      Signed in as (Sign out)
                      You have left! (?) (thinking…)
                      8 comments  ·  GitLab CI  ·  Admin →
                    • PDF download for .md and .tex files from blob and blob edit view

                      Let users download PDF versions of .md or .tex files from the:

                      - blob view
                      - blob edit view for the current textarea content they are editing (serving as a preview).

                      ---------------------------------------------

                      Proposed implementation:

                      Convert `.md` to `.tex` via kramdown.

                      PDF is compiled from tex via texlive 2009 at push time (there would be a compile queue).

                      Add links to the compilation logs, and new views with the logs.

                      Preprocess logs to filter / highlight errors.

                      We can introduce only the kramdown dependency, and let interested users install texlive themselves.

                      ----------------------------------

                      **Economic Viability Analysis**

                      I know this is a big…

                      42 votes
                      Vote
                      Sign in
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        I agree to the terms of service
                        Signed in as (Sign out)
                        You have left! (?) (thinking…)
                        12 comments  ·  GitLab CI  ·  Admin →
                      • GitLab CI should push notifications to configured services

                        Right now our GitLab is configured to push all activity to HipChat. However GitLab CI activity is not pushed to HipChat. Can GitLab CI do this?

                        41 votes
                        Vote
                        Sign in
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          I agree to the terms of service
                          Signed in as (Sign out)
                          You have left! (?) (thinking…)
                          6 comments  ·  GitLab CI  ·  Admin →
                        • Ability to customize Issue tracker fields

                          For example adding custom fields like a REAL issue tracker. I'm using gitlab for our web development company and sometimes we need custom fields, for example:

                          - The user is logged in?
                          - Which browser?
                          - Which device?

                          Things like that :) Thanks

                          32 votes
                          Vote
                          Sign in
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            I agree to the terms of service
                            Signed in as (Sign out)
                            You have left! (?) (thinking…)
                            0 comments  ·  GitLab CI  ·  Admin →
                          • Build slave projects

                            What i like to see is if the parent project build succeed.
                            Build a other project after that.
                            If there is some sort of command for that we can put in the "Build steps"
                            that would be great!

                            28 votes
                            Vote
                            Sign in
                            Check!
                            (thinking…)
                            Reset
                            or sign in with
                            • facebook
                            • google
                              Password icon
                              I agree to the terms of service
                              Signed in as (Sign out)
                              You have left! (?) (thinking…)
                              1 comment  ·  GitLab CI  ·  Admin →
                            • Merge requests should trigger a build on the main project

                              When you create a merge request it should trigger a build on the main project + the merge request changes and show build status on the merge request page.

                              26 votes
                              Vote
                              Sign in
                              Check!
                              (thinking…)
                              Reset
                              or sign in with
                              • facebook
                              • google
                                Password icon
                                I agree to the terms of service
                                Signed in as (Sign out)
                                You have left! (?) (thinking…)
                                10 comments  ·  GitLab CI  ·  Admin →
                              • autorefresh to see build results

                                On several pages you can see outdated data. The page should constantly ask the server for updates and show the updated values

                                22 votes
                                Vote
                                Sign in
                                Check!
                                (thinking…)
                                Reset
                                or sign in with
                                • facebook
                                • google
                                  Password icon
                                  I agree to the terms of service
                                  Signed in as (Sign out)
                                  You have left! (?) (thinking…)
                                  3 comments  ·  GitLab CI  ·  Admin →
                                • Build time estimate (and/or load bar) based on previous build time.

                                  It would be nice for example the last 3 or 5 build took average 8 minutes CI can display an approximately build time estimate.

                                  22 votes
                                  Vote
                                  Sign in
                                  Check!
                                  (thinking…)
                                  Reset
                                  or sign in with
                                  • facebook
                                  • google
                                    Password icon
                                    I agree to the terms of service
                                    Signed in as (Sign out)
                                    You have left! (?) (thinking…)
                                    0 comments  ·  GitLab CI  ·  Admin →
                                  • Allowing the build pages to be viewed publicly.

                                    Gitlab CI should allow non-registered users to view the build pages of public projects. Currently public projects only allow non-registered users to view the build list but not the more detailed build pages.

                                    20 votes
                                    Vote
                                    Sign in
                                    Check!
                                    (thinking…)
                                    Reset
                                    or sign in with
                                    • facebook
                                    • google
                                      Password icon
                                      I agree to the terms of service
                                      Signed in as (Sign out)
                                      You have left! (?) (thinking…)
                                      7 comments  ·  GitLab CI  ·  Admin →
                                    • Make runners available to limited users or teams.

                                      I'd like to be able to configure permissions to make runners assignable to projects owned by specific users or teams only. For example, some teams own specialized hardware (with GPUs, etc) that other teams should not be able to run tests on.

                                      If this is already possible, then my suggestion is for documentation to enable this.

                                      19 votes
                                      Vote
                                      Sign in
                                      Check!
                                      (thinking…)
                                      Reset
                                      or sign in with
                                      • facebook
                                      • google
                                        Password icon
                                        I agree to the terms of service
                                        Signed in as (Sign out)
                                        You have left! (?) (thinking…)
                                        2 comments  ·  GitLab CI  ·  Admin →
                                      • build from custom commit

                                        It would be nice to create a build on a specific commit(id) which the user can select. This would be very helpful to reconstruct userscenarios especially if you combine the buildprocess with a deploy-process

                                        17 votes
                                        Vote
                                        Sign in
                                        Check!
                                        (thinking…)
                                        Reset
                                        or sign in with
                                        • facebook
                                        • google
                                          Password icon
                                          I agree to the terms of service
                                          Signed in as (Sign out)
                                          You have left! (?) (thinking…)
                                          6 comments  ·  GitLab CI  ·  Admin →
                                        • build omnibus packages for gitlab ci as well as for gitlab CE

                                          Would be nice to install Gitlab CI beside the Gitlab Omnibus package as package as well ...

                                          14 votes
                                          Vote
                                          Sign in
                                          Check!
                                          (thinking…)
                                          Reset
                                          or sign in with
                                          • facebook
                                          • google
                                            Password icon
                                            I agree to the terms of service
                                            Signed in as (Sign out)
                                            You have left! (?) (thinking…)
                                            1 comment  ·  GitLab CI  ·  Admin →
                                          ← Previous 1 3
                                          • Don't see your idea?

                                          Feedback and Knowledge Base