GitLab team member here. One thing that stood out to me in this release is the strength of contributions from the wider GitLab community.<p>Among the 299 community contributions in this release:<p>- GPU and smart scheduling support for GitLab Runner [1]<p>- The ability to follow other GitLab users [2]<p>- 1 line installer for the GitLab Kubernetes Agent [3]<p>- An activity filter on Vulnerability Reports [4]<p>1 - <a href="https://about.gitlab.com/releases/2021/02/22/gitlab-13-9-released/#gpu-and-smart-scheduling-support-for-gitlab-runner" rel="nofollow">https://about.gitlab.com/releases/2021/02/22/gitlab-13-9-rel...</a><p>2 - <a href="https://about.gitlab.com/releases/2021/02/22/gitlab-13-9-released/#follow-user-activity" rel="nofollow">https://about.gitlab.com/releases/2021/02/22/gitlab-13-9-rel...</a><p>3 - <a href="https://gitlab.com/gitlab-org/cluster-integration/gitlab-agent/-/merge_requests/281#note_507445139" rel="nofollow">https://gitlab.com/gitlab-org/cluster-integration/gitlab-age...</a><p>4 - <a href="https://about.gitlab.com/releases/2021/02/22/gitlab-13-9-released/#vulnerability-report-activity-filter" rel="nofollow">https://about.gitlab.com/releases/2021/02/22/gitlab-13-9-rel...</a>
There are some very nice features in this release:<p>1. VSCode MR viewing and CI autocomplete of env vars (and in next version adding comments) which finally means I can totally stop using clanky browser GUI for that but people that like it can.<p>2. PowerShell Core as shell runner on Linux<p>3. Suggestion in MR like on GH<p>4. Follow user like on GH<p>5. Automatic changelog via push tags<p>6. Recursive view of parent child pipelines (still some murky UI elements tho, like not being able to expand child on parent, something that worked previously). Unfortunately doesn't seem to be working with includes on trigger...<p>7. Reviewer follow up and viewed items. So far IMO, GH PR was much more pleasurable experience, maybe those 2 features will fix those problems for me - I am not sure if its just some quirk on my standalone or what but on GL I can't really understand what is going on after first review and provided fix. On GH PR, it simply hides changed lines that were previously reported as problematic but not on GL, several times it even didn't show commits that came afterwards. Rebasing also seem to mess the process up. Maybe I am just dumb.<p>I wish pipelines will get some filtering love, like viewing jobs by name and/or their status. Not really sure why this basic and very important stuff was never implemented. I sometimes have to scan several pages to find last instance of the job I am interested in (note that I use monorepo and each sub-service has its own standalone pipeline and parent triggers only specific ones based on code changes)<p>Another wish is option to select subset of all possible child pipelines when manually creating pipeline - now it triggers all of them.
Of all the features, I am extremely happy about this one: reference tags in CI configuration <a href="https://docs.gitlab.com/ee/ci/yaml/README.html#reference-tags" rel="nofollow">https://docs.gitlab.com/ee/ci/yaml/README.html#reference-tag...</a><p>I've had some pains when creating base job definitions that I had to modify later (one of them is that after_script doesn't fail the job if it fails, for example) and I think I can solve almost all of them with this new feature.<p>Gitlab is one of the few programs I use where I'm actually looking forward to updates: things rarely break in updates and I have actual, useful improvements every month.
I have to use GitLab. But I really quite don’t get some features like:<p>Multiple published html pages per job. Seems not possible: You have to have a special job name “pages” and your build artifacts have to be in a special directory “public” in order for this job to work correctly.<p>Also collecting test coverage reports by grepping with a regex through your build stdout feels weird.<p>These 2 examples leave a weird feeling - a feeling that some easily applicable features are just bolted onto GitLab and the underlying architecture is not capable of incorporating these features an a better way (multiple html websites, specialized coverage report parsers).<p>Also extended/sharing pipelines between multiple teams without duplicating code or having stages “leaking into teams code” feels weird.
Between Gitlab,Gitea and bare-git repos, which one should I use for personal (1-man) projects? Here are my thoughts:<p>Gitlab is resource-hungry but provides CI solutions and is kind of a setup-once-then-forget solution.<p>Gitea is light weight but for any additional functionality third-party utilities are needed.
Very welcome improvements in Code Review department. Really like the explicit Viewed checkbox (even though I noticed that the bolding in the sidebar with the file tree tried to solve the same problem) and really nice with the suggestions.<p>My two top wishlist leftover items in that regard are<p>1. Marking whether a comment requests changes or not. This is of course straight out of GitHub, but I think their flow better matches what I found to be happening a in a lot of changes. I see such states for a Code review of a MR: Changes approved, Reviewer requests changes, reviewer leaves feedback (like "nice implementation", "good refactor", "minor: maybe you can refactor this?"). The last one is the most blurry in the GitLab approach since the way we can solve it is by starting a comment thread that is not resolved and approving a MR at the same time but it feels clunky. Maybe they can take a page out of GitHub's book.<p>2. Personal slack notifications. I would love to have first-party support for the notification system around MR, MR Comments, Being assigned, pipeline failing that messages me privately on slack. Jira recently had a revamp in their slack app and all notification moved there and overall I welcomed these changes since the only other way it seems to be email which speaks for itself - limited interactivity and it's becoming less of a notification medium anyway. [1]<p>[1]: <a href="https://gitlab.com/gitlab-org/gitlab/-/issues/17958" rel="nofollow">https://gitlab.com/gitlab-org/gitlab/-/issues/17958</a>
Is there a RSS feed for Gitlab (Community) releases?<p>I found the releases page here <a href="https://gitlab.com/gitlab-org/gitlab-foss/-/releases" rel="nofollow">https://gitlab.com/gitlab-org/gitlab-foss/-/releases</a><p>But /rss or /atom (or .atom like GitHub does) do not have the feed.