jl-gitlab (u/jl-gitlab)

jl-gitlab commented on How to start a blog using Hugo flaviocopes.com/start-blo... · Posted by u/flaviocopes

netsharc · 6 years ago

I have the same use case and have been wondering about solutions too. I'm hosting on Netlify, and when I push to my gitlab repository, Netlify's CI fetches, builds and deploys the site. I've wondered if I can run a script somewhere that periodically checks a private Instagram account (so not my main one), and when it sees a new post, it would download the photo and caption, creates a Markdown post and pushes everything into the git repo.

jl-gitlab · 6 years ago

You could potentially use a regularly scheduled pipeline in GitLab CI to do this. You'd need to use a user token instead of the pipeline token since you want to push back into the repository, but this should be possible. Then, when GitLab CI updates the repo, Netlify CI should jump in.

jl-gitlab commented on Setting Up a Jenkins Home Lab gdcorner.com/2019/12/27/J... · Posted by u/boristsr

KaiserPro · 6 years ago

If one were to have a choice, I would steer clear of jenkins for home use, and use a gitlab runner instead

Jenkins is fine, if you commit to maintaining it, but thats a non trivial task.

THe joy and pain of the gitlab runner is that the job is tied directly to the git repo its attached to. This means that unlike jenkins, the setup is versioned, meaning disaster recovery is much more simple (spin up new runner, attach to project. Done.)

You do then sacrifice multi-project pipelines, but even in very large companies, I've only missed that feature once. It also in no way makes up for having to look after 60+ jenkins masters. (dont ask)

Yes, you gitlab gives you less control over environment, but I would put forward that this is only an advantage when running on windows.

jl-gitlab · 6 years ago

In GitLab we have shared group/instance runners now as well as multiproject pipelines.

https://docs.gitlab.com/ee/ci/multi_project_pipelines.html

https://docs.gitlab.com/ee/ci/runners/#shared-specific-and-g...

We are focusing on improving the new user experience here, so OP if you decide to try out GitLab I'd love to hear what works well and what doesn't.

jl-gitlab commented on Gitlab 12.6 about.gitlab.com/blog/201... · Posted by u/bjoko

orf · 6 years ago

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.

jl-gitlab · 6 years ago

One relatively easy way to debug is to set up a runner instance on your machine and then send jobs that you're working on there. In that way you are validating real jobs, but can also monitor and interact with what's happening in real time.

Features like https://gitlab.com/gitlab-org/gitlab/issues/39527 will make this easier and allow you to do similar troubleshooting in an interactive web terminal.

jl-gitlab commented on Gitlab 12.6 about.gitlab.com/blog/201... · Posted by u/bjoko

majkinetor · 6 years ago

Unfortunatelly 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.

jl-gitlab · 6 years ago

We have a new PM for the runner and this is on his agenda to research and improve. The reality is that the job execution environment is complex - each job does just have a simple script section which is just shell commands, but there is a lot of context that impacts behavior (to which environment are you deploying, what environment variables are set specific to that environment, is it a protected environment with variables that are shareable to any random user, are artifacts being passed, and so on.) Making iterating on pipelines easier is definitely on our agenda, and adding your thoughts to issues like https://gitlab.com/gitlab-org/gitlab-runner /issues/2226 or making new ones for your specific use case will help. We are also working on other oblique solutions to make pipelines easier to iterate on like https://gitlab.com/gitlab-org/gitlab/issues/39527, which help solve the problem in a different way where you don't need to try to replicate the state of the world on your local environment but can still find and fix problems quickly.

EDIT: I should also mention, https://gitlab.com/groups/gitlab-org/-/epics/2072 is a big priority for us where we want to reduce the time to first green pipeline (not just for new users, but for new projects too). Feedback is welcome there as well.

jl-gitlab commented on Gitlab 12.6 about.gitlab.com/blog/201... · Posted by u/bjoko

majkinetor · 6 years ago

One example that comes to mind is codefresh.io. It allows local run of the pipeline (and even debug via breakpoints) and only requires docker to be installed locally.

I currently use task system with Gitlab to make any job in 1-3 lines. Then I can easily replicate build locally. The task engine is either installed on runner's host itself or run inside docker container.

jl-gitlab · 6 years ago

We are looking to add breakpoints in an upcoming release, building on our interactive web terminals feature. If you're interested in providing feedback the public issue is https://gitlab.com/gitlab-org/gitlab/issues/39527.

jl-gitlab commented on Gitlab 12.6 about.gitlab.com/blog/201... · Posted by u/bjoko

robbya · 6 years ago

> 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.

jl-gitlab · 6 years ago

Thanks, that's really great to hear. Release evidence, and where we plan to take that feature long term (https://about.gitlab.com/direction/release/release_governanc...) is really exciting to me, having spent a lot of my career in release management. Would be great to get your feedback on where we are headed - even if you aren't a GitLab user today, may you will be in the future.

jl-gitlab commented on Gitlab 12.6 about.gitlab.com/blog/201... · Posted by u/bjoko

rumanator · 6 years ago

Yes, that's very odd as it would be relatively trivial to extend packaging support to handle DEB or RPM packages, for example.

jl-gitlab · 6 years ago

We are looking at adding many new kinds of packages, including potentially Linux package types such as thesehttps://about.gitlab.com/direction/package/package_registry/...

jl-gitlab commented on How to fuck up software releases drewdevault.com/2019/10/1... · Posted by u/zdw

vortico · 6 years ago

Here's a somewhat redacted version. `m` is my alias for `make`.

    - Finalize source
     - Legal check `LICENSE-dist.txt`
     - Update `CHANGELOG.md`
     - Bump version in `Makefile` and `Core.json`
     - Commit "Bump version".
    - Build (three OS's can be done in parallel)
     - `m clean`
     - `git pull`
     - Make sure you have the latest `Fundamental.zip` package in source root.
     - `m dist`
     - Manually test installer and fragile features (audio drivers, patch loading) for ~10 minutes.
     - `m notarize` (on Mac)
     - `m upload`
     - `git tag vX.Y.Z`
     - `git push --tags`
    - Release
     - Update version title and URLs in `Rack.pug`
      - `m upload`
      - At this point, normal users have access to new version.
     - Update server version in `config.coffee`
      - `m restart`
      - At this point, normal users will swarm to download new version. Keep an eye on server bandwidth.
    - Publicize
     - Twitter https://twitter.com/home
     - Facebook https://www.facebook.com/vcvrack/
      - Share on group
     - Forum https://community.vcvrack.com/c/announcements

jl-gitlab · 6 years ago

Interesting list, thanks for sharing. I'm the PM for CI/CD at GitLab, and I don't mean to hijack the topic, but wanted to give a heads up that we are looking at building a feature for these kinds of procedures that aren't quite pipelines, based on Jupyter Runbooks. Would love to hear your feedback: https://gitlab.com/gitlab-org/gitlab/issues/9427

jl-gitlab commented on Gitlab More Than Doubles Valuation to $2.75B Ahead of Planned 2020 IPO forbes.com/sites/alexkonr... · Posted by u/andygcook

harrisonjackson · 6 years ago

I am a huge fan of gitlab. We are in the process of moving our github org over. We love!! the gitlab ci tools. We use them extensively for mobile cicd. The gitlab ci runner is super easy to get running and coordinates well with a host and vm setup. We run it on a mac min sitting on my desk and have never had any issues with it.

My only nitpick is the regex matching they do to mask protected environment variables from ci logs is not sufficient. It won't match + scrub aws secret keys in the logs, which seems like a pretty glaring problem in a cicd setup.

> masked so they are hidden in job logs, though they must match certain regexp requirements to do so

We've been able to work around it, but it did make that particular automation more difficult.

jl-gitlab · 6 years ago

Hey, CI/CD PM here. I'd love to learn more about how you're using GitLab for mobile, if you're up for it ping me at @jlenny on gitlab.com. It's an area of focus for us, and it's always great to get to know another person who is using that use case.

jl-gitlab commented on Gitlab More Than Doubles Valuation to $2.75B Ahead of Planned 2020 IPO forbes.com/sites/alexkonr... · Posted by u/andygcook

Townley · 6 years ago

I want to say it's the freedom to self-host, but really it's the CI.

Throwing a .gitlab-ci.yml file into my repo is by far the easiest way to get CI/CD incorporated into a product. The configuration of test runners (or lack thereof) is both a breeze and extremely powerful.

I'm not even talking about the auto-devops thing that I haven't tried; writing your own gitlab-ci file worked in frictionless ways that CircleCI, Travis, and (especially) Jenkins didn't.

jl-gitlab · 6 years ago

PM for CI/CD here, thanks so much for your feedback! As much as I'm excited about how much you love the product, we can always do better and I'd love to hear your thoughts. Ping me any time (@jlenny) on any issues that are important to you that would make things better.