<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>GitLab on widerin</title><link>http://widerin.net/tags/gitlab/</link><description>Recent content in GitLab on widerin</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 07 Sep 2026 18:30:36 +0200</lastBuildDate><atom:link href="http://widerin.net/tags/gitlab/index.xml" rel="self" type="application/rss+xml"/><item><title>Gitlab Security Products with Java and Gradle</title><link>http://widerin.net/posts/2020/gitlab-security-products-with-java-and-gradle/</link><pubDate>Sun, 08 Mar 2020 00:00:00 +0000</pubDate><guid>http://widerin.net/posts/2020/gitlab-security-products-with-java-and-gradle/</guid><description>&lt;p&gt;GitLab security products have been constantly improving support for different
build tools and programming languages.&lt;/p&gt;
&lt;p&gt;My &lt;a href="https://gitlab.com/gitlab-org/security-products/license-management/merge_requests/7"&gt;recent contribution&lt;/a&gt;
to &lt;a href="https://docs.gitlab.com/ee/user/compliance/license_compliance/#license-compliance"&gt;License compliance&lt;/a&gt; allows now to inject commands &lt;code&gt;SETUP_CMD&lt;/code&gt; environment
variable to the core to bypass the package manager auto-detection and make use
of the &lt;code&gt;./gradlew&lt;/code&gt; &lt;a href="https://gradle.org"&gt;Gradle&lt;/a&gt; wrapper script.&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;include:
- template: Security/License-Scanning.gitlab-ci.yml
variables:
SETUP_CMD: sh my-custom-install-script.sh
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;In this example, my-custom-install-script.sh is a shell script at the root
directory of your project.&lt;/p&gt;</description></item><item><title>Gitlab License Management with Java 11</title><link>http://widerin.net/posts/2018/gitlab-license-management-with-java-11/</link><pubDate>Fri, 21 Dec 2018 00:00:00 +0000</pubDate><guid>http://widerin.net/posts/2018/gitlab-license-management-with-java-11/</guid><description>&lt;p&gt;If built-in &lt;a href="https://docs.gitlab.com/ee/user/project/merge_requests/license_management.html"&gt;License Management&lt;/a&gt; functionality does not support the programming
language requirements you have, you can customize the &lt;a href="https://docs.gitlab.com/ee/user/project/merge_requests/license_management.html"&gt;License Management&lt;/a&gt;
docker image.&lt;/p&gt;
&lt;p&gt;This guide shows you how to use &lt;a href="https://docs.gitlab.com/ee/user/project/merge_requests/license_management.html"&gt;License Management&lt;/a&gt; with &lt;a href="https://openjdk.java.net/"&gt;OpenJDK&lt;/a&gt; 11 or
later.&lt;/p&gt;
&lt;h2 id="license-management-definition"&gt;License Management definition&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://docs.gitlab.com/ee/user/project/merge_requests/license_management.html"&gt;License Management&lt;/a&gt; helps you find what licenses your project uses in its
dependencies and decide for each of then whether to allow it or forbid it.&lt;/p&gt;
&lt;div class="gallery shadow" itemscope itemtype="https://schema.org/ImageGallery"&gt;
&lt;figure itemprop="associatedMedia" itemscope itemtype="https://schema.org/ImageObject"&gt;
&lt;a class="glightbox" href="https://docs.gitlab.com/ee/user/compliance/license_compliance/img/license_compliance_v13_0.png" data-gallery="gallery-0" data-glightbox="description: License Compliance report under pipelines" itemprop="contentUrl"&gt;
&lt;img loading="lazy" src="https://docs.gitlab.com/ee/user/compliance/license_compliance/img/license_compliance_v13_0.png" alt="License Compliance report under pipelines" itemprop="thumbnail"&gt;
&lt;/a&gt;
&lt;figcaption&gt;&lt;p&gt;License Compliance report under pipelines&lt;/p&gt;</description></item><item><title>GitLab SAST and Java 11</title><link>http://widerin.net/posts/2018/gitlab-sast-and-java-11/</link><pubDate>Wed, 19 Dec 2018 00:00:00 +0000</pubDate><guid>http://widerin.net/posts/2018/gitlab-sast-and-java-11/</guid><description>&lt;p&gt;If built-in &lt;a href="https://docs.gitlab.com/ee/user/project/merge_requests/sast.html"&gt;Static Application Security Testing&lt;/a&gt;
functionality does not support the programming language requirements you have,
you can customize the analyzer docker images in [GitLab]&amp;rsquo;s &lt;code&gt;sast&lt;/code&gt; pipeline job.&lt;/p&gt;
&lt;p&gt;This guide shows you how to use &lt;a href="https://docs.gitlab.com/ee/user/project/merge_requests/sast.html"&gt;SAST&lt;/a&gt; with &lt;a href="https://openjdk.java.net/"&gt;OpenJDK&lt;/a&gt; 11 or later.&lt;/p&gt;
&lt;h2 id="sast-definition"&gt;SAST definition&lt;/h2&gt;
&lt;p&gt;Static Application Security Testing provides you information if&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;your application is vulnerable by using an external library in a specific
version which is known to be vulnerable or&lt;/li&gt;
&lt;li&gt;your code has a potentially dangerous attribute in a class, or unsafe code
that can lead to unintended code execution.&lt;/li&gt;
&lt;/ul&gt;
&lt;div class="gallery shadow" itemscope itemtype="https://schema.org/ImageGallery"&gt;
&lt;figure itemprop="associatedMedia" itemscope itemtype="https://schema.org/ImageObject"&gt;
&lt;a class="glightbox" href="https://docs.gitlab.com/ee/user/application_security/security_dashboard/img/pipeline_security_dashboard_v13_3.png" data-gallery="gallery-0" data-glightbox="description: Project Security Dashboard" itemprop="contentUrl"&gt;
&lt;img loading="lazy" src="https://docs.gitlab.com/ee/user/application_security/security_dashboard/img/pipeline_security_dashboard_v13_3.png" alt="Project Security Dashboard" itemprop="thumbnail"&gt;
&lt;/a&gt;
&lt;figcaption&gt;&lt;p&gt;Project Security Dashboard&lt;/p&gt;</description></item><item><title>Continuous integration with GitLab and Docker</title><link>http://widerin.net/posts/2016/continuous-integration-with-gitlab-and-docker/</link><pubDate>Tue, 11 Oct 2016 00:00:00 +0000</pubDate><guid>http://widerin.net/posts/2016/continuous-integration-with-gitlab-and-docker/</guid><description>&lt;p&gt;I&amp;rsquo;ve given a talk about continuous integration with &lt;a href="https://about.gitlab.com"&gt;GitLab&lt;/a&gt; and &lt;a href="https://www.docker.com"&gt;Docker&lt;/a&gt; on
Developer Meetup &lt;a href="https://twitter.com/VlbgWebDev"&gt;VlbgWebDev&lt;/a&gt;. The Meetup takes
place every second Tuesday every Month and i&amp;rsquo;ve met some old colleagues there.&lt;/p&gt;
&lt;p&gt;It was a nice Meetup with lots of discussions, that&amp;rsquo;s why i published my sample
code to GitLab and my slides to Speakerdeck. First intention was to do some
&lt;a href="http://www.pylonsproject.org/"&gt;Pyramid&lt;/a&gt; demo but after I&amp;rsquo;ve heard there are
some &lt;a href="http://flask.pocoo.org/"&gt;Flask&lt;/a&gt; people, I&amp;rsquo;ve added
&lt;a href="http://flask.pocoo.org/"&gt;Flask&lt;/a&gt; demos as well :-)&lt;/p&gt;</description></item><item><title>GitLab as OAuth provider for Weblate</title><link>http://widerin.net/posts/2016/gitlab-as-oauth-provider-for-weblate/</link><pubDate>Thu, 28 Apr 2016 00:00:00 +0000</pubDate><guid>http://widerin.net/posts/2016/gitlab-as-oauth-provider-for-weblate/</guid><description>&lt;p&gt;&lt;a href="http://weblate.org"&gt;Weblate&lt;/a&gt; is built on &lt;a href="https://www.djangoproject.com"&gt;Django&lt;/a&gt; and you can use a lot of authentication plugins.
After &lt;a href="https://github.com/pennersr/django-allauth/pull/1231"&gt;my contribution&lt;/a&gt;
to &lt;a href="https://github.com/pennersr/django-allauth"&gt;django-allauth&lt;/a&gt; and the
backporting work of &lt;a href="https://github.com/python-social-auth/social-core/issues/2"&gt;glensc and omab&lt;/a&gt;
to &lt;a href="https://github.com/python-social-auth/social-core"&gt;django-social-auth&lt;/a&gt; it&amp;rsquo;s very easy
to integrate [GitLab]&amp;rsquo;s &lt;a href="http://doc.gitlab.com/ce/integration/oauth_provider.html"&gt;authentication provider&lt;/a&gt;
with &lt;a href="http://weblate.org"&gt;Weblate&lt;/a&gt;&lt;/p&gt;
&lt;h2 id="gitlab"&gt;GitLab&lt;/h2&gt;
&lt;p&gt;All you have to do on &lt;a href="http://about.gitlab.com"&gt;GitLab&lt;/a&gt; is configuration
through webinterface. Go to &lt;a href="https://gitlab.com/profile/applications"&gt;https://gitlab.com/profile/applications&lt;/a&gt;
and register a new application.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Name: Weblate&lt;/li&gt;
&lt;li&gt;Redirect URI: `&lt;a href="https://weblate.yourdomain.tld/accounts/complete/GitLab/%60%60"&gt;https://weblate.yourdomain.tld/accounts/complete/GitLab/``&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;figure itemprop="associatedMedia" itemscope itemtype="https://schema.org/ImageObject"&gt;
&lt;a class="glightbox" href="http://widerin.net/posts/2016/weblate_gitlab_register_application.png" data-gallery="gallery-page" itemprop="contentUrl"&gt;
&lt;img loading="lazy" src="http://widerin.net/posts/2016/weblate_gitlab_register_application.png" alt="" itemprop="thumbnail"&gt;
&lt;/a&gt;
&lt;/figure&gt;
&lt;p&gt;After registering your new application you&amp;rsquo;ll get your &lt;strong&gt;Application
Key&lt;/strong&gt; and &lt;strong&gt;Secret&lt;/strong&gt;. You&amp;rsquo;ll need this later for configuration&lt;/p&gt;</description></item><item><title>Maintaining manual gitlab installation with ansible</title><link>http://widerin.net/posts/2016/maintaining-manual-gitlab-installation-with-ansible/</link><pubDate>Sun, 03 Jan 2016 00:00:00 +0000</pubDate><guid>http://widerin.net/posts/2016/maintaining-manual-gitlab-installation-with-ansible/</guid><description>&lt;p&gt;A long time ago we started using &lt;a href="http://about.gitlab.com"&gt;GitLab&lt;/a&gt;. It was a greate step forward and definitly the right decision to switch from SVN to a distributed version control system. If you want to try &lt;a href="http://about.gitlab.com"&gt;GitLab&lt;/a&gt; you should definitly install it using &lt;a href="https://about.gitlab.com/downloads/"&gt;GitLab Omnibus distribution&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id="manual-installation"&gt;Manual installation&lt;/h2&gt;
&lt;p&gt;But this long time ago there was no omnibus installation available so we installed &lt;a href="http://about.gitlab.com"&gt;GitLab&lt;/a&gt; with a manual &lt;code&gt;git&lt;/code&gt; checkout. Their monthly release cycle brought some upgrade effort every month - there was an upgrade tool available which was &lt;a href="https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/update/upgrader.md#gitlab-upgrader-deprecated"&gt;marked as discontinued&lt;/a&gt; - so i started to write some anisble scripts to handle the upgrade process.&lt;/p&gt;</description></item></channel></rss>