What are /r/gitlab's favorite Products & Services?

From 3.5 billion Reddit comments

Also do "git remote -v" https://git-scm.com/docs/git-remote To see if you have both push an pull origins set correctly.

Check for spacing and protocols. It can be that a whitespace slipped in somewhere or a spelling mistake happened.

Hey u/c-digs, I am a product designer at GitLab and am excited to hear you are scoping out our product for your team. If it is helpful, the way we work is documented in our handbook. The short of it is we have product, design, and engineering all collaborating on issues in our main project GitLab. We use scoped labels to designate where in our workflow an issue stands.

GitLab's had a Docker Registry built-in since version 8.8. Each project automatically gets a corresponding registry namespace.

There's a good summary of the feature on the GitLab Container Registry blog post from May 2016.

In general i would recommend to use the commandline-client, as GUIs are often not transparent on what actions are taken. Some Clients even use their own vocabulary, which might add confusion.

Ignoring the above: here is an 'official' list of clients with information about their licence, price if any and a link to their official site. You can filter them by your preferred platform.

Hey OP - Everything I say here is not official word of my employer or advise on behalf of my employer.

That being said - Please report this to the GitLab Abuse team. They may not do anything, but keeping a record is better than nothing. In the event further issues happen. Trying to bully you into giving up your gitlab namespace isn't acceptable behavior.
https://about.gitlab.com/handbook/engineering/security/security-operations/trustandsafety/

What you're talking about is GitLab Geo - Where one instance is set to read only and the other is set to being the primary. There is _ALOT_ to making GitLab HA or DR using Geo. Many more services to consider than Postgres. I would use GitLab Geo for Disaster Recovery.

GitLab Geo | GitLab
Geo | GitLab

Do you mean this? https://about.gitlab.com/blog/2019/10/10/update-free-software-and-telemetry/

As mentioned in that article, GitLab Core / CE is unaffected and the opt-out for gitlab.com / EE will be enabling Do Not Track in your browser.

Let me know if you still have concerns and I'll be happy to dig up more details!

You can use Gitlab for free, unless you absolutely need the features of the Starter license. The free tier includes a lot of features that most small teams use.

https://about.gitlab.com/pricing/gitlab-com/feature-comparison/

Make sure all your markdown pages have a YAML Front Matter, even if it is blank. For example:

--- ---

# Why I Love Jekyll Lorem ipsum...

I moved my Jekyll site over to GitLab the other day and everything is working fine (including the markdown). Here's a link to the repo if you want to take a look. If you got more questions, don't hesitate to ask!

I am not aware of a way to do it in the UI.

However, renaming remote branches should always be done with care, see the following Stack Overflow answer: https://stackoverflow.com/questions/1526794/rename-master-branch-for-both-local-and-remote-git-repositories#1527004

So, if you're using the repo alone, it should be fine. If there are others working on it too, they should be noticed about the rename and should know what to do, to not run into issues.

Have you seen this? https://kubernetes.io/docs/concepts/containers/images/#updating-images

It sounds like you have an imagePullPolicy set.

I've re-read the terms regarding the education account and we are definitely eligible. According to a blog post from 2018 (https://about.gitlab.com/blog/2018/06/05/gitlab-ultimate-and-gold-free-for-education-and-open-source/) all features are unlocked for education accounts. I'm not sure if it's still the case and can't find anything contradicting that so I'll have to take another look.

Hi Bitruder! I’m a product designer at GitLab. That’s a good question and we have astewardship policy that provides guidance for contributions from the wider community.

> When someone contributes a not yet existing feature on the issue tracker that has a paid tier label, and it has met the contribution acceptance criteria, we will accept it under whatever license (open-source or source-available) they prefer, provided that GitLab Inc. has not already started working on the feature. (The contribution should not contain any already existing source-available features in it.) We encourage contributors to @-mention the relevant product manager earlier in the development process (in the issue or merge request) to ensure GitLab team-members are not already working on the feature in order to avoid conflicts.

Hey u/Baronlr, I'm a product designer at GitLab. Awesome video! I thoroughly enjoyed your humorous yet informative presentation style.

I wanted to share a friendly reminder that we want everyone to be able to contribute to GitLab. We welcome contributions from the community, and champion them. It would be pretty sweet to see Clouseau's charts native in GitLab!

I'm going to share your idea with our team since I work with the designer that is responsible for analytics.

That is just the version you are running but not the license. E.g. we are running the on-prem enterprise edition as well but do have the license:

>Plan: Starter

which is now phasing out because they will replace some license models: Announced in January

This could maybe be the problem in your case.

> I actually can't see the pricing when it comes to non cloud hosted alternatives.

There's a giant "Pricing" link at the top (and bottom, though not giant) of the page: https://about.gitlab.com/pricing/ and the only difference between cloud and on-prem is the name of their plans (the metals are for GitLab.com, the "adjectives" are for on-prem), but both pricing models are per-distinct User per month (regrettably, "User" is anything that can have a PAT assigned to it, and thus "service accounts" get billed at the full rate :-( although at the benefit of not nuking some deploy job if Awesome User 1 has a separation event)

Well, I shouldn't say "only difference," as there are certainly no billed CI minutes for the on-prem install, so in that way the pricing could be higher for cloud even for the same amount of Users

I'd recommend reading through the release blog posts for major/minor releases at https://about.gitlab.com/releases/categories/releases/

They also have a tool at https://gitlab-cs-tools.gitlab.io/what-is-new-since/?minVersion=11_05&selectedMinTier=core which can show the changes between two versions.

I'd echo /u/QuarterBall in recommending that yes you should always upgrade. But it's worth knowing on some level what changed, mostly so you can get excited about the change and start thinking about how you can take advantage of the new features.

Yes, I think I only receive mails for the security releases, not for the patch releases here: https://about.gitlab.com/blog/categories/releases/

There is an Atom feed for this category, maybe this is more useful for you.

Hackathon is now just a few days away! See the latest info. at https://about.gitlab.com/community/hackathon/.

If you're looking for issues to work on, you can also find them at https://gitlab.com/gitlab-com/marketing/community-relations/contributor-program/hackathon/issues/17#suggested-issues-list

Not to sound rude but it seems like this is not your field of expertise - I would suggest doing some research before tackling hosting your own GitLab instance.

Here are a few tips and pointers: - First you need to understand how an URL is structured. You can find a brief overview here. Basically, a URL is made up of an protocol (since you want to reach it over the web this will be https, I would strongly advise against using http since it is not secure), a subdomain (which is not always necessary), your root Domain (basically your company's domain), a TLD (this is the .com, .co.uk or whatever part) and a subdirectory after that. Something like companydomain.gitlab.com will NOT be possible since the root domain gitlab.com is obviously owned by GitLab. What you are probably looking for is a creating a subdomain for your root domain, i.e. git.companyname.com - Check out what a DNS is and how it works. Oversimplified: if you enter a domain like reddit.com into the address field of your browser a request to a DNS Server is made which knows to which IP the domain belongs. This information is then used to request the corresponding resources from the Server. So you need to create a DNS record for your subdomain which points to the Server where your GitLab instance is running. - You obviously need to install your GitLab instance on your server. This can be done in a multitude of ways which are documented on the official website - choose the method which works best for your setup. This might be tricky if you don't have a good understanding of Unix and how the web works but doable if you follow the instructions and are not afraid to read a lot.

Hope this helps.

gitlab.io is a free static hosting service for repos in gitlab.com:

• files that can be hosted statically are HTML files and MD (markdown syntax) files.
  
• most of the time, repos are not equivalent to a static web site. you need a transformation task (static site generation) script instructions in a file .gitlab-ci.yml
• without explicit transformation script, the site automatically output the index.html or index.md or readme.md as the default page of the site. Without these, the static site has no default page (=404 page not found error)

[https://about.gitlab.com/2016/04/07/gitlab-pages-setup/]https://about.gitlab.com/2016/04/07/gitlab-pages-setup/

Guests don't count toward the user count in Ultimate. I thought something similar applied to Reporters, but I may have imagined that.

Also, licensing is based on “Maximum Users”, not a literal user count. For example, my installation currently has 42 users, but a maximum users count of 33. So, I need licenses for 33 users, not 42.

I did a quick search a found a good link for this...

https://about.gitlab.com/roi/replace/

Yes, its on GitLab's website, so grain of salt and all that, but I don't think you can dispute the numbers too much (except for the variety of security tools available).

And don't underestimate the cost and need for support. Sure your 5 man operation can do without, but Enterprise level companies and their devops departments have internal demands to meet (uptime requirements and SLA's for their internal "customers"), so support is a critical component to running an Enterprise scale set of tools.

If your project is open source, you can apply for a year renewable license for GitLab Gold/Ultimate. You can find out more here!

I don't understand what's unreliable about git. Also, as you said, git is literally in their name, not using git would be ridiculous.

also btw, I don't know whether they're done yet but they started moving from azure to google cloud services https://about.gitlab.com/2018/06/25/moving-to-gcp/

For self-hosted installations Core is CE, and CE is Core. They are not two different things.

The way it works is GitLab CE has one licensing option—Core—which is free.

GitLab EE has three options: Starter, Premium, and Ultimate.

Have a look at the Feature Comparison page for details about the differences between the options.

I managed to get in a email list for security updates. I would have to assume there is one for general. But I've just marked in my calendar for the large monthly releases as they are scheduled for 22nd of the month.

https://about.gitlab.com/direction/#future-releases

For even more info:

> They cannot have ASCII control characters (i.e. bytes whose values are lower than \040, or \177 DEL), space, tilde ~, caret ^, or colon : anywhere.

https://git-scm.com/docs/git-check-ref-format

Git commits form a Directed Acyclic Graph. So it may diverge and rejoin, but there can be no loops.

Regarding branches, the Git Book explains pretty well how they actually work.

We have about 20 users on 2 cores and 4GB of RAM without any issues. Allegedly we could make it up to 100 users with those specs.

I would not recommend Digital Ocean from a performance standpoint though.

Here’s a bunch of benchmarks I ran when I was doing the research https://www.notion.so/521dimensions/Benchmark-Results-for-Self-hosted-Gitlab-Server-c6eca7c5f16d4bb8aeb989174fc58ffe

Hope this helps!

Not an NGINX issue. It's a CDN issue.

As reported by TechCrunch

> A Cloudflare outage has hit several popular services including Discord, Omegle, DoorDash, Crunchyroll, NordVPN, and Feedly

And confirmed by GitLab:

> We are continuing to monitor connectivity issues from some regions due to connectivity problems from our CDN provider.

To add on, a lot of documentation puts remote there because, rarely, people have multiple remotes defined. This allows you to pull from various branches and various remote repositories. The only time I’ve ever used this was when I was switching from GitHub to Gitlab.

But as @coffeecup1978 said, most people follow the convention as origin. git remote is where you can find more info on setting the remote. Then in documentation when you see things like

$ git fetch <remote>

You just substitute whatever you set the remote as for <remote>. In the traditional convention it’s origin as in

$ git fetch origin

Those are submodules, not normal directories.

They refer to another repository at a particular commit.

To clone a repository with submodules use

git clone --recurse-submodules [url]

Or if you've already cloned it ...

git submodule update --init

If you have CI jobs that rely on submodules remember to set GIT_SUBMODULE_STRATEGY to recursive in the job variables.

More info on submodules: https://git-scm.com/book/en/v2/Git-Tools-Submodules

Well, I don't think I misunderstood. The issue isn't in Gitlab, it's with eslint. One of your parameters causes an exit 0, one of your parameters causes an exit non-zero. Gitlab is doing exactly what it's supposed to do.

> Fixing problems: > --fix Automatically fix problems > --fix-dry-run Automatically fix problems without saving the changes to the file system > --fix-type Array Specify the types of fixes to apply (directive, problem, suggestion, layout)

https://eslint.org/docs/user-guide/command-line-interface

--fix is fixing your issues, correctly making it pass (zero code). Without, it's not, you have problems, ergo, non-zero code.

Anything in here you see that you like that is not available as Free but is as Premium? https://about.gitlab.com/pricing/gitlab-com/feature-comparison/

I'd think maybe code search, but if you have all your code locally because it's all on your laptop anyway, you can just use a tool like ack or grep. Pipelines dashboard?

https://about.gitlab.com/pricing/

You'll be missing out on:

• multiple approvers
• Code owners
• Code Review Analytics
• Merge Request reviews
• Pipelines for Merged Results
• Code quality reports
• Comments in Review apps

When it comes to code reviews.

Are you using shallow clone? I was under the impression that aside from not fetching all history, it also implies --single-branch which would not fetch all refs?

https://docs.gitlab.com/ee/ci/large_repositories/

https://git-scm.com/docs/git-clone

Latest version of git client also has some cloning performance improvements.

Pull or Merge Requests are possible by e-mail but a bit unusual in the context of this sub (r/gitlab). If the maintainer actually meant by e-mail perhaps he meant the way Pull Requests are done for the Linux Kernel (https://www.kernel.org/doc/html/v5.9/process/submitting-patches.html). Git diffs are then sent in a plain-text e-mail as if they were a commit with the subject line usually being the PR title and the diff being sent as plain text, just as it is outputted on the command line.

Silver is now Premium (and Gold is now Ultimate) as of almost a year ago.

Pre-existing Silver/Gold plans may still have those names, though I think that ends at renewal time. There's also an option to switch to the new names immediately, and I think there may be an incentive to do so, though I don't remember the details.

> Default configurations for SAST and Dependency Scanning are fully patched

> GitLab.com and self-managed customers who are running the default configurations for SAST and Dependency Scanning are fully patched. No action is required.

To summarize. If you did not futz with the SAST settings it auto-updated and you are fine.

https://about.gitlab.com/blog/2021/12/15/updates-and-actions-to-address-logj-in-gitlab/#default-configurations-for-sast-and-dependency-scanning-are-fully-patched

Hey! I’m the product manager for snippets at GitLab and while I don’t have an immediate solution, it is something we’re thinking about: https://gitlab.com/groups/gitlab-org/-/epics/3204

I’d love to learn more about your use case, so if you’re interested in chatting setup some time https://calendly.com/gitlabkai

Most GUIs just use the default git config files. If you’re starting fresh, just clone your repo using the ssh url. If you have added your ssh public key to your gitlab.com account, the rest is automatic.

If you have an exiting local repo, you need to update your .git/config file. https://git-scm.com/docs/git-config

To start a new project from an existing repo, like from github.com, add project from url. Give the github url and it will be cloned to GitLab.

To properly remove something from git, have a look at Rewriting History in the Pro Git book, specifically, the section "Removing a File from Every Commit".

You have a few options...

1) If there aren’t any new changes in the testing branch, you could remove it and re-create it. 2) if you do have changes you want to keep, then you can merge “master” into your testing branch.

https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging

I'm a noob at GitLab also - and found that I can use Git Clean

https://git-scm.com/docs/git-clean

I would be careful though as It cleared out my local repository for all the committed / pushed files... which is what I was trying to do but it's good to know.

Is the PF product open source? MIT? Will they merge back? Will there be profit share / a fee for technical expertize / EE usage? What is the exact deal with GitLab Inc.? Perforce dev said some things at: https://www.quora.com/What-is-the-real-story-between-GitSwarm-and-GitLab

1. Yes, your kubernetes deployment spec can specify the “command” and/or “args” to run. https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.19/#container-v1-core If specified, these supersede the “CMD” and/or “ENTRYPOINT” in your Dockerfile, so there is no need to do this list with “$ARG1 ARG2…” (which is a very ugly way to pass args in my opinion). You can also specify “env” and “envFrom”: there is a variety of ways to pass in environment variables.

2. Yes of course, you should deploy a Service and anything else you need like ConfigMaps, LoadBalancer, Ingress, etc. This is getting beyond GitLab into Kubernetes tutorial, but let me know if you have questions.

Edit: grammar and clarify “and/or”

stuff like Required Merge Request Approvals, Push Rules, Restrict push and merge access, Code Owners etc

https://about.gitlab.com/pricing/self-managed/feature-comparison/ full feature comparison here

I've had good experiences with a two pronged approach:

• https://about.gitlab.com/security-releases.xml
• https://gitlab.com/gitlab-org/gitlab/-/tags?format=atom

With the first being the write up and exclusively security centric, and the second being the indication that there's something coming, security or not. It's usually also an indicator of severity when they tag multiple patch releases at once, because then whatever they found has been around for a while and affects multiple versions

https://about.gitlab.com/blog/2014/07/10/feature-highlight-ldap-sync/

It is a GitLab feature. I don't know the technical bits. This would be commercial license that my company uses.

I don't understand the question:

>If I decide I’m happy with GitLab SaaS, how expensive is hosting?

It is literary on the top of the pricing page : https://about.gitlab.com/pricing/

19$ or 99$ per user

GitLab team member here. Omibnus is currently at the Lovable maturity level. Our maturity plan is to stay Lovable by making it even easier to manage a GitLab instance and continuing to provide the best possible experience when deploying GitLab with Omnibus.

>Who is doing the certification? I don’t recall a 101 and 102 from the GitLab company

https://about.gitlab.com/handbook/people-group/learning-and-development/certifications/

Who is doing the certification? I don’t recall a 101 and 102 from the GitLab company https://about.gitlab.com/handbook/customer-success/professional-services-engineering/gitlab-technical-certifications/

Ah, of all the things I thought could have happened, I never thought of the "what's new" not getting updated in time. Thanks :)

As for the CI config, it appears that it's deployment_tier, not type. https://web.archive.org/web/20210322164026/https://about.gitlab.com/releases/2021/03/22/gitlab-13-10-released/ shows that it did use type in the original release blog, though, so they must have corrected this after I tried to use it…

I would recommend opening an MR with your concerns. Especially if you are considering adopting GitLab with your company, you will also need to start adopting GitLabs values and processes to fully be able to use GitLab to its fullest.

Someone may respond here from the company, but in all reality, your best bet is to adhere to the values and open an MR. More eyes will see it and you will experience the actual collaboration that happens. It's pretty cool.

I would also recommend reading their Values and see if they are a good fit for you and your colleagues.

https://about.gitlab.com/handbook/values/

Also, hosting your runners is the way to go in your situation.

While you've got some great advice already, just to add - enable 2FA where available and practical. Partially because it's just good hygiene, and partially just in case insulting you isn't the worst idea they've had.

https://about.gitlab.com/blog/2018/08/09/keeping-your-account-safe/

This is a bit of an older blog post but I think its still relevant
https://about.gitlab.com/blog/2016/04/05/shared-runners/

I think the main thing for security with docker+machine is the `MaxBuilds = 1`. The whole docker socket/privileged container security risk is still there. But each instance is terminated after one build.

You can include the label quick action in the template so that it's applied on issue creation.

Another approach would be to have a bot regularly review issues and auto apply labels. The GL Quality department has written a handbook page detailing how this works within GitLab.

-James H, GitLab Product Manager, Verify:Testing

Are you following the install guide? https://about.gitlab.com/install/#ubuntu

If you want to jump straight to the install script, find the part in here that curls in the key for your install. Look for the line with gpg_key_url and work from there for the repo install. https://packages.gitlab.com/gitlab/gitlab-ce/install

when you push to a branch on the command line, the message will have a link to create a merge request.

To use the Gitlab Workflow extension you need to create an API token and configure it. Here is a video on how to do this: https://about.gitlab.com/blog/2018/03/01/gitlab-vscode-extension/

Greetings from Gitlab Community Coimbatore,

First of all we would like to appreciate your inquisitiveness to learn the Gitlab.

Going through your post, we wish to share one of the Certification courses that would suit your interest, helping you advance your learning journey with Gitlab.

https://about.gitlab.com/handbook/people-group/learning-and-development/certifications/gitlab-101/

Hope you find it helpful!

Happy learning,

Gitlab Community Coimbatore

We do, but it's due to GitLab.com's infrastructure being hosted mostly on GCP, which blocks traffic from, among others, Iran at the network level.

https://about.gitlab.com/blog/2018/07/19/gcp-move-update/

We do not, however, block access to GitLab from TOR exit nodes, and neither does GCP AFAIK.

Contributors on the Github repo who do not access GitLab will not count as users under your GitLab plan. Only individual end-users who access GitLab under your plan count as a user for the "active users" subscription costs.

For more details, see the FAQ's on GitLab's Pricing page, particularly the answers to questions:

• What is a user?
• The True-Up model seems complicated, can you illustrate?

That's what I thought. But according to this page, they increased the minutes to 2000 in march 2020. May be I am missing something.

Right now our team is running a series of tests on our pricing page, if you'd like to view the control page, please visit: https://about.gitlab.com/pricing/gitlab-com/feature-comparison/?experiment-review-control

Thanks!

- SL, Community Advocate at GitLab

Hey thanks for the question! I am designer at GitLab and would love to hear any feedback you have.

You can type in the search bar the issue number, which will bring back a variety of results including issues but it does not directly open the issue unless you click it. However, that probably isn't as fast as using the url to jump to it.

I personally use Alfred to search for things like a specific issue. So my way of finding that issue would be cmd+space, then enter "issue 241727" and that would open a new tab in my browser with that issue.

Great question! Please note that I currently work at GitLab. The answer really depends on what you are trying to do. The previous response was correct in that our Core offering (free tier) has some incredible features and functionality for SCM and CI. Tons of people use this tier everyday for successfully deploying software.

The paid tiers really expand what you can do as far as the rest of the DevOps Lifecycle. If Security of your code is a concern, (as it should be for everyone), then you may want to consider the integrated SAST, DAST, license and dependency scanning that the Gold/Ultimate tiers offer. Having that information up front before any code gets released can improve quality and also time to market. We’re also in the process of adding Fuzz testing as well.

If you are doing any deployments to Kubernetes, regardless of Cloud Provider, the higher tiers provide insight into Monitoring and Defending of deployments.

If you are interested in seeing high level planning work like Epics and releases and how they are completed by developer issues, you may also want take a look at Ultimate/Gold.

So, really, the bottom line is what I mentioned at the beginning. It all depends on what your needs are and what is valuable to you. I definitely encourage you to take a look at our roadmap, which is open to all, to see the direction we’re going in all aspects of the SDLC. https://about.gitlab.com/upcoming-releases/

You can find some example projects here for you to explore: https://docs.gitlab.com/ee/ci/examples/#cicd-examples

I hope that helps and thanks so much for considering GitLab. I’m happy to any additional questions you may have.

Have a great day!

They are a premium/ultimate (silver/gold) feature: https://about.gitlab.com/releases/2019/04/22/gitlab-11-10-released/#scoped-labels

There's a GitLab blog about this and hosting the report on gitlab pages. Custom text for coverage badges was a contribution in the latest release so you can customize that text some more.

-James H, GitLab PM

GitLab Product Manager here. CodeClimate is the engine that is running when you include the CodQuality template in your gitlab-ci.yml file and can be extended with SonarQube plugins. We are moving the Merge Request widget that details changes in quality to Core later this year. I'm always interested in hearing feedback on the existing implementation as we continue to add features in this area.

Good Luck with your evaluation!

-James H - Gitlab PM

In addition to what has already been shared here, we have a page that lists categories of the product. That's often useful as plenty of people are listed with each group (e.g. product manager or frontend/backend engineer(s)) and they usually can provide help/direct to someone who can.

The GitLab Remote Playbook Covering Fundamentals to Long-Term Strategy

u/whereisthetom - I wanted to make sure you saw this blog post today about some features moving into Core, including the Code Quality Merge Request Widget. We don't have the work scheduled but hope to get there soon so everyone on Core can use that functionality.

-JH

Your feedback is valuable, and this shouldn't go unnoticed. I work in Support at GitLab and I'm also personally involved in efforts to improve the availability of support and solutions for Core/Community/Free GitLab users (which is how I found this thread).

Support Engineers at GitLab have Customer Satisfaction as our [top performance indicator](https://about.gitlab.com/job-families/engineering/support-engineer/#performance-indicators). If you message me with details of your negative Support experience(s) and any suggestions on how we can improve, I will make sure this doesn't go unnoticed.

They moved a version of epics down to Premium/Silver in 12.8 last month and looks like a Roadmap view is coming in 12.9:

https://about.gitlab.com/releases/2020/02/22/gitlab-12-8-released/#single-level-epics-now-available-in-premium

Using GitHub + GitLab CI/CD is just giving you "more trouble", but essentially you don't loose anything.

Here are some GitLab strengths.

Awesome, thanks for your reply!
Small still at 2 full time developers (one being me) and 2 freelancers, want to grow in 2020 and possibly with remote positions so we're more flexible.

The big difference here is that you are really shipping an application that needs to be packaged vs us building a website, so we have the possibility to truly do continues delivery in every sense of the word. But as you also say, there's downsides to that and we'll have to find out if this actually works well.
Thanks for linking that milestone, that gives me a starting point to have a better look at your workflow. I've been looking (not very hard) for something like that but all I have found so far is this article: https://docs.gitlab.com/ee/topics/gitlab_flow.html which is a little outdated it seems, but that may just be the screenshots.
Googling a bit now I think I'll read some of your handbooks to get a better grip on how you work, this seems like a good start too: https://about.gitlab.com/handbook/engineering/workflow/#basics

> We were running GitHub and a tapestry of third party tools which made implementing review apps infeasible for us.

This is really recognisable. And one of the reasons my love for gitlab flared so much these past weeks. Originally I was given the assignment to "build a pipeline so we can work more efficiently" and I had started to look at other solutions, using something like Jenkins and building an entire infrastructure for this. But every step I took, every thing I googled, somewhere there was a result which said "Gitlab can do this" :)

Why have an approximate number, when you can have the exact one?

https://about.gitlab.com/handbook/people-group/global-compensation/calculator/

For those interested in Hashicorp Vault and GitLab CI, Here’s our issue regarding upcoming integration: https://gitlab.com/gitlab-org/gitlab/issues/28321. We absolutely welcome any comments or contributions to that issue. Additionally, here’s a link to our Category Vision in Secret Management: https://about.gitlab.com/direction/release/secrets_management/. In there you can see our Maturity in this space and what we are planning.

This links to the 12.5.1 update, but new security updates have been released already, 12.5.2, 12.4.5, and 12.3.8: https://about.gitlab.com/blog/2019/11/27/security-release-gitlab-12-5-2-released/

From what I remember, she'd had some pretty strong objections to this issue, as well as this one: https://about.gitlab.com/blog/2019/10/10/update-free-software-and-telemetry/

Wonder if there's something rotten going on with GitLab's culture.

GitLab offers free Ultimate and Gold for education and open source projects. That's the top-tiers for gitlab.com and self-hosted.

You can check out the differences on the Features Comparison page.

Thanks for the feedback.

> GitHub is designed (and works best) for FOSS projects.

Would you mind elaborating on that? I'd be interested to hear where GitLab could improve to be more useful to FOSS projects.

> Your needs for a public open source project are usually very different than private Enterprise software. Public OSS usually just needs source code, an issue tracker, and a place to store compiled binaries.

I see this differently. I would agree from the point of view that different projects have different needs, but I would not draw the line specifically between proprietary (or closed) source vs. open source. In my experience DevOps practices and collaboration are used across the board. GitLab is being used by large Open Source projects such as Debian, GNOME, KDE, Haskell, Drupal and more. They all have their own feature usage, but certainly automation, CI/CD and planning features are also essential to the way some of them work with contributors.

To the OP, if you are hosting Open Source projects, you can also benefit from the GitLab for Open Source program, which offers you GitLab's top tiers for free.

Thanks.

So I added when: on_failure after script in the build section.

image: nixos/nix

before_script: - nix-channel --add https://nixos.org/channels/nixpkgs-unstable - nix-channel --update

build: stage: build script: nix-shell --run make when: on_failure artifacts: paths: - public

pages: stage: deploy script: ":" artifacts: paths: - public only: - master

But outputs the following when I edited a file and run -- make/click commit.

> unpacking channels...
created 2 symlinks in user environment
$ :
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
Job succeeded

&#x200B;

Thanks.

So I added when: on_failure after script in the build section.

image: nixos/nix

before_script: - nix-channel --add https://nixos.org/channels/nixpkgs-unstable - nix-channel --update

build: stage: build script: nix-shell --run make when: on_failure artifacts: paths: - public

pages: stage: deploy script: ":" artifacts: paths: - public only: - master

But outputs the following when I edited a file and run -- make/click commit.

> unpacking channels...
created 2 symlinks in user environment
$ :
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
Job succeeded

&#x200B;

Thanks.

So I added when: on_failure after script in the build section.

image: nixos/nix

before_script: - nix-channel --add https://nixos.org/channels/nixpkgs-unstable - nix-channel --update

build: stage: build script: nix-shell --run make when: on_failure artifacts: paths: - public

pages: stage: deploy script: ":" artifacts: paths: - public only: - master

But outputs the following when I edited a file and run -- make/click commit.

> unpacking channels...
created 2 symlinks in user environment
$ :
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
Job succeeded

&#x200B;

Thanks.

So I added when: on_failure after script in the build section.

image: nixos/nix

before_script: - nix-channel --add https://nixos.org/channels/nixpkgs-unstable - nix-channel --update

build: stage: build script: nix-shell --run make when: on_failure artifacts: paths: - public

pages: stage: deploy script: ":" artifacts: paths: - public only: - master

But outputs the following when I edited a file and run -- make/click commit.

> unpacking channels...
created 2 symlinks in user environment
$ :
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
Job succeeded

&#x200B;

Thanks.

So I added when: on_failure after script in the build section.

image: nixos/nix

before_script: - nix-channel --add https://nixos.org/channels/nixpkgs-unstable - nix-channel --update

build: stage: build script: nix-shell --run make when: on_failure artifacts: paths: - public

pages: stage: deploy script: ":" artifacts: paths: - public only: - master

But outputs the following when I edited a file and run -- make/click commit.

> unpacking channels...
created 2 symlinks in user environment
$ :
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
Job succeeded

&#x200B;

Thanks.

So I added when: on_failure after script in the build section.

image: nixos/nix

&#x200B;

before_script:

- nix-channel --add https://nixos.org/channels/nixpkgs-unstable

- nix-channel --update

&#x200B;

build:

stage: build

script: nix-shell --run make

when: on_failure

artifacts:

paths:

- public

&#x200B;

pages:

stage: deploy

script: ":"

artifacts:

paths:

- public

only:

- master

But outputs the following when I edited a file and run -- make/click commit.

unpacking channels...
created 2 symlinks in user environment
$ :
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
Job succeeded

&#x200B;

Thanks.

So I added when: on_failure after script in the build section.

>image: nixos/nix
>
>
>
>before_script:
>
> - nix-channel --add https://nixos.org/channels/nixpkgs-unstable
>
> - nix-channel --update
>
>
>
>build:
>
> stage: build
>
> script: nix-shell --run make
>
> when: on_failure
>
> artifacts:
>
>paths:
>
>- public
>
>
>
>pages:
>
> stage: deploy
>
> script: ":"
>
> artifacts:
>
>paths:
>
>- public
>
> only:
>
> - master

But outputs the following when I edited a file and run -- make/click commit.

> unpacking channels...
created 2 symlinks in user environment
$ :
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
Job succeeded

&#x200B;

Thanks.

So I added when: on_failure after script in the build section.

image: nixos/nix

before_script: - nix-channel --add https://nixos.org/channels/nixpkgs-unstable - nix-channel --update

build: stage: build script: nix-shell --run make when: on_failure artifacts: paths: - public

pages: stage: deploy script: ":" artifacts: paths: - public only: - master

But outputs the following when I edited a file and run -- make/click commit.

> unpacking channels...
created 2 symlinks in user environment
$ :
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
Job succeeded

&#x200B;

Thanks.

So I added when: on_failure after script in the build section.

image: nixos/nix

before_script: - nix-channel --add https://nixos.org/channels/nixpkgs-unstable - nix-channel --update

build: stage: build script: nix-shell --run make when: on_failure artifacts: paths: - public

pages: stage: deploy script: ":" artifacts: paths: - public only: - master

But outputs the following when I edited a file and run -- make/click commit.

> unpacking channels...
created 2 symlinks in user environment
$ :
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
Job succeeded

&#x200B;

Thanks.

So I added when: on_failure after script in the build section.

image: nixos/nix

before_script: - nix-channel --add https://nixos.org/channels/nixpkgs-unstable - nix-channel --update

build: stage: build script: nix-shell --run make when: on_failure artifacts: paths: - public

pages: stage: deploy script: ":" artifacts: paths: - public only: - master

But outputs the following when I edited a file and run -- make/click commit.

> unpacking channels...
created 2 symlinks in user environment
$ :
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
Job succeeded

&#x200B;

Thanks.

So I added when: on_failure after script in the build section.

image: nixos/nix

before_script: - nix-channel --add https://nixos.org/channels/nixpkgs-unstable - nix-channel --update

build: stage: build script: nix-shell --run make when: on_failure artifacts: paths: - public

pages: stage: deploy script: ":" artifacts: paths: - public only: - master

But outputs the following when I edited a file and run -- make/click commit.

> unpacking channels...
created 2 symlinks in user environment
$ :
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
Job succeeded

Thanks.

So I added when: on_failure after script in the build section.

image: nixos/nix

before_script: - nix-channel --add https://nixos.org/channels/nixpkgs-unstable - nix-channel --update

build: stage: build script: nix-shell --run make when: on_failure artifacts: paths: - public

pages: stage: deploy script: ":" artifacts: paths: - public only: - master

But outputs the following when I edited a file and run -- make/click commit.

> unpacking channels...
created 2 symlinks in user environment
$ :
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
Job succeeded

&#x200B;

Thanks.

So I added when: on_failure after script in the build section.

image: nixos/nix

before_script: - nix-channel --add https://nixos.org/channels/nixpkgs-unstable - nix-channel --update

build: stage: build script: nix-shell --run make when: on_failure artifacts: paths: - public

pages: stage: deploy script: ":" artifacts: paths: - public only: - master

But outputs the following when I edited a file and run -- make/click commit.

> unpacking channels...
created 2 symlinks in user environment
$ :
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
Job succeeded

&#x200B;

Thanks.

So I added when: on_failure after script in the build section.

image: nixos/nix

before_script: - nix-channel --add https://nixos.org/channels/nixpkgs-unstable - nix-channel --update

build: stage: build script: nix-shell --run make when: on_failure artifacts: paths: - public

pages: stage: deploy script: ":" artifacts: paths: - public only: - master

But outputs the following when I edited a file and run -- make/click commit.

> unpacking channels...
created 2 symlinks in user environment
$ :
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
Job succeeded

&#x200B;

Thanks.

So I added when: on_failure after script in the build section.

image: nixos/nix

before_script: - nix-channel --add https://nixos.org/channels/nixpkgs-unstable - nix-channel --update

build: stage: build script: nix-shell --run make when: on_failure artifacts: paths: - public

pages: stage: deploy script: ":" artifacts: paths: - public only: - master

But outputs the following when I edited a file and run -- make/click commit.

> unpacking channels...
created 2 symlinks in user environment
$ :
Uploading artifacts...
WARNING: public: no matching files
ERROR: No files to upload
Job succeeded

&#x200B;

https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.16/#podspec-v1-core

Leads me to believe it's expected you create multiple secrets and then supply them as need on the ImagePullSecrets line.