Gitlab 12.6
about.gitlab.com
Gitlab 12.6
1–10 of 30 posts
Re: Gitlab 12.6
#2> Streamline Audits with Release Evidence
I've seen companies with overly painful audit requirements, and making the process of generating artifacts for audit as easy as possible is a great way forward. Box ticking exercises should take minimal engineering time.
My current project doesn't use gitlab, but I love the constant innovation Gitlab pushes out.
Re: Gitlab 12.6
#3Unfortunatelly there is still no way to run CI file locally which is major turn down. Deprecated `exec` command is hell to use.
I should be able to install runner on developers machine and just run and debug pipeline there, with or without Gitlab server present.
Re: Gitlab 12.6
#4Interesting addition of Conan support right into GitLab.
> For any development organization, having an easy and secure way to manage dependencies is critical. Package management tools, such as Conan for C/C++ developers, provide a standardized way to share and version control these libraries across projects.
> In GitLab 12.6, we are proud to offer Conan repositories built directly into GitLab. Developers can now publish their packaged libraries to their project’s Conan repository. Simply set the Conan remote to the GitLab Package Registry and start uploading, installing, and deleting packages today.
Re: Gitlab 12.6
#5Unfortunatelly there is still no way to run CI file locally which is major turn down. Deprecated `exec` command is hell to use. I should be able to install runner on developers machine and just run and debug pipeline there, with or without Gitlab server present.
Deprecated `exec` command is hell to use
Unfortunatelly there is still no way to run CI file locally which is major turn down
Re: Gitlab 12.6
#6I am thankful for this release. It finally fixed two major issues that had plagued Gitlab for us for a long time:
- The "Rebase" button now actually seems to work reliably with no cases of endless spinning to report in the few tens of button presses so far for me (we merge fast-forward only). Hoping this is not a fluke and will not regress in the future.
- The "Hide whitespace changes" button works again after breaking what feels like some time in 2018.
These 2 sound like really basic functionality, so it also represents the sad state of Gitlab development - a priority on useless fluff on top of regressions in each release, while hundreds of bugs that actually affect users go unaddressed.
This is a good release.
Edit: Their issue tracker [1] actually lists 37.8k issues with 23.9k "open", which represents 63% of all issues ever created. As a project matures and ages, you would expect this metric to start to go down naturally, as you "plateau" on a sustainable level of open issues. If this were my project, I would be freaking out.
Re: Gitlab 12.6
#7Unfortunatelly there is still no way to run CI file locally which is major turn down. Deprecated `exec` command is hell to use. I should be able to install runner on developers machine and just run and debug pipeline there, with or without Gitlab server present.
I am particular about how I code my builds so they are portable. I like debugging locally, its faster. Gitlab-Ci does not encourage this and I usually end up refactoring my colleagues code all the time to this end.
Not sure if having a runner is the proper solution to this problem. Off the cuff I feel like there are better ways to go about it if I where making a CI server from scratch. Like only allowing single Docker commands per action? Then you would just those and have a nice portable and consistent environment. But Docker isn't very friendly as development tooling as you have to go through length to persist file artifacts and such. Would seem like there is some room in the space...
Re: Gitlab 12.6
#8I am thankful for this release. It finally fixed two major issues that had plagued Gitlab for us for a long time: - The "Rebase" button now actually seems to work reliably with no cases of endless spinning to report in the few tens of button presses so far for me (we merge fast-forward only). Hoping this is not a fluke and will not regress in the future. - The "Hide whitespace changes" button works again after breaki…
[deleted]
Re: Gitlab 12.6
#9I am thankful for this release. It finally fixed two major issues that had plagued Gitlab for us for a long time: - The "Rebase" button now actually seems to work reliably with no cases of endless spinning to report in the few tens of button presses so far for me (we merge fast-forward only). Hoping this is not a fluke and will not regress in the future. - The "Hide whitespace changes" button works again after breaki…
Not all of those issues are bugs though. Only 4,000 are labeled as bugs, with many more being labeled as improvements or product direction discussions.
Gitlab’s development runs through those issues, so there are a _lot_ that are related to that.
Re: Gitlab 12.6
#10Unfortunatelly there is still no way to run CI file locally which is major turn down. Deprecated `exec` command is hell to use. I should be able to install runner on developers machine and just run and debug pipeline there, with or without Gitlab server present.
I am particular about how I code my builds so they are portable. I like debugging locally, its faster. Gitlab-Ci does not encourage this and I usually end up refactoring my colleagues code all the time to this end. Not sure if having a runner is the proper solution to this problem. Off the cuff I feel like there are better ways to go about it if I where making a CI server from scratch. Like only allowing single Docke…
Gitlab executes shell commands, you can and should run those locally to debug. If your putting complex build logic inside gitlab definitions then perhaps you’re doing it wrong - “make test” or “make release” should be all that Gitlab runs.