5 ms·

I think there are some areas where GitLab can improve their CI story, but I agree that having a One Stop Shop for that is actually very compelling.

• sytse 9y ago
  This month we're coming out with scheduled CI builds and next month with multi-project builds. What improvement would you like to see in our CI?
  • jancsika 9y ago
    * compatibility with msys2. It's one of the best environments on Windows for building cross-platform apps (where cross-platform is Windows, OSX, and Linux). Ideally, I'd like to run a Windows VM for the CI build and have artifact uploads, all through the msys2 shell. I see a single rumbling here: https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/issues/1699 https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/issues/...
    • sytse 9y ago
      Great idea, I've marked it Accepting Merge Requests https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/issues/1699#note_29833535 https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/issues/...
  • elygre 9y ago
    > What improvement would you like to see in our CI? The ability to view build reports, such as test results and the like. Tracked many times, in various forms: https://gitlab.com/gitlab-org/gitlab-ce/issues/13227 https://gitlab.com/gitlab-org/gitlab-ce/issues/13227 (73 votes), https://gitlab.com/gitlab-org/gitlab-ce/issues/18664 https://gitlab.com/gitlab-org/gitlab-ce/issues/18664 (67 votes), https://gitlab.com/gitlab-org/gitlab-ce/issues/10982 https://gitlab.com/gitlab-org/gitlab-ce/issues/10982 (53 votes), https://gitlab.com/gitlab-org/gitlab-ce/issues/17081 https://gitlab.com/gitlab-org/gitlab-ce/issues/17081 (22 votes), https://gitlab.com/gitlab-org/gitlab-ce/issues/23618 https://gitlab.com/gitlab-org/gitlab-ce/issues/23618 (a mere 5 votes).
    • bikebilly 9y ago
      Thank you for sharing your thoughts: you're totally right, this feature has much interest by the community and is an high priority. By the way, this is also a very complex topic, as you need to provide great flexibility but at the same time the best UX. As usual, we move by iterating on the issue by little steps: first of all we need the basic building blocks, on top of them we can create the final feature. I mostly agree that test results and other "custom" information must be extracted automatically from logs, but we need to provide a generic model that can be easily adapted to everyone. Iterations on that brought us code coverage information, artifacts for failed jobs and browsing and online display of artifacts (ready to be released in 9.2), and we provide also workarounds, like using GitLab Pages, that can solve some scenario until the work is completed. I'd like also to mention our current effort in supporting CodeClimate (https://gitlab.com/gitlab-org/gitlab-ce/issues/4044 https://gitlab.com/gitlab-org/gitlab-ce/issues/4044). We will continue on this path (one of the issues you mentioned has the "direction" label), always open in receiving feedback and promoting collaboration at any level.