dnsmichi

21 ms·

121.
by dnsmichi 5y ago
I figured that the HN handbook does not link the Zapier workflows page. Fixed in https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_request...
122.
by dnsmichi 5y ago
Sharing my personal experience, not speaking for GitLab here: One thing I did when I was excited about the Developer Evangelist role: I started writing a document in the open, collecting thoughts what I learned, what I want to do, and which
123.
by dnsmichi 5y ago
More on Zapier workflows: https://about.gitlab.com/handbook/marketing/community-relati... I saw your message in Slack, GitLab Developer Evangelist waving from Germany :)
124.
by dnsmichi 5y ago
Opstrace has published a blog post: https://opstrace.com/blog/gitlab :)
125.
by dnsmichi 5y ago
For the GitLab pipeline editor, this experience should be built-in. Currently discussing to e.g. detect the source code and come up with tips and template suggestions automatically. Without context switching. https://gitlab.com&#
126.
by dnsmichi 5y ago
Shared this thread into a new community forum topic for valuable resources: https://forum.gitlab.com/t/ci-cd-pipeline-efficiency-resourc...
127.
by dnsmichi 5y ago
Can you share more details about the size of the project (files count, build file size) and which caching settings you are using? I assume it is ccache and am curious how you use it.
128.
by dnsmichi 5y ago
True, CI caches are only one way to look at slow pipelines. When you are in control of the infrastructure where jobs and runners consume resources, other strategies might also help. Package dependency installs taking some time? Move the run
129.
Migrating a Dockerized Gitlab Chat Bot to ARM Graviton2 in an Afternoon(medium.com)
1 points by dnsmichi 5y ago|0 comments
130.
by dnsmichi 5y ago
The dependency proxy in GitLab can help with caching the Docker images. https://docs.gitlab.com/ee/user/packages/dependency_proxy/ When Docker Hub introduced rate limits last year, one way to mitigate it
131.
by dnsmichi 5y ago
Thank you for the great thoughts :) > And maybe only cache the downloads on the main branch. $CI_COMMIT_REF_SLUG resolves into the branch when executed in a pipeline. Using it as value for the cache key, Git branches (and related MRs) us
132.
by dnsmichi 5y ago
Great tips, thank you! > Instead, use multi stage Docker builds. This way you can also run your pipeline locally and all your GitLab jobs will consist of "docker build ..." There's a section in the pipeline efficiency docs
133.
by dnsmichi 5y ago
I went ahead and blogged about the workshop, thanks y'all for the inspiration :) https://dev.to/dnsmichi/efficient-devsecops-pipelines-in-a-c... If you learn a new trick or gem, please blog and share with our comm
134.
by dnsmichi 5y ago
> We should link that in the Pipeline Efficiency docs I've shared the resources and this HN topic with GitLab's technical writing team to make tutorials more visible on docs.gitlab.com https://gitlab.com/gitlab-
135.
by dnsmichi 5y ago
Yep, in the pipeline view at the top right. https://docs.gitlab.com/ee/ci/caching/#clearing-the-cache
136.
by dnsmichi 5y ago
Cache keys are unique identifier names for a cache, as otherwise a global cache is used by all jobs, 'key: default'. https://docs.gitlab.com/ee/ci/yaml/index.html#cache https://docs.gitla
137.
by dnsmichi 5y ago
Great post, thanks for sharing. We should link that in the Pipeline Efficiency docs: https://docs.gitlab.com/ee/ci/pipelines/pipeline_efficiency.... I've given a talk about similar ideas for efficient pi
138.
by dnsmichi 5y ago
Thanks, I have forwarded your question. The current selection for the affected component automatically selects the `locations` entry. The `website` component selects the Google Compute Engine in this case. Agreed that this can be confusing,
139.
by dnsmichi 5y ago
Sorry for the slow update, incident was triggered and analysis continues. You can follow at https://gitlab.com/gitlab-com/gl-infra/production/-/issues/5... > Where else do people go for confirmat
140.
Git: Moving from Master to Main(jumpingrivers.com)
1 points by dnsmichi 5y ago|0 comments
141.
Atlas: Secure communication for a distributed Thanos Deployment for Prometheus(github.com)
2 points by dnsmichi 5y ago|0 comments
142.
Falco Plugins Early Access(falco.org)
2 points by dnsmichi 5y ago|0 comments
143.
Infrastructure Observability for Changing the Spend Curve at Slack(slack.engineering)
1 points by dnsmichi 5y ago|0 comments
144.
How open source made observability mainstream(youtube.com)
2 points by dnsmichi 5y ago|0 comments
145.
by dnsmichi 5y ago
Great analysis, thanks! Slack support says that users should tell their ISPs to invalidate the DNS cache for slack.com https://status.slack.com/2021-09/06c1e17de93e7dc2 (access with 8.8.8.8 as resolver - fallback http
146.
by dnsmichi 5y ago
Recommend checking out the CI/CD workflow improvements in GitLab 14.3 - Conditional includes Docs: https://docs.gitlab.com/ee/ci/yaml/#rules-with-include Screenshots: https://twitter.com&#x2F
147.
by dnsmichi 5y ago
Thanks. Now I also get a better understanding of why .patch for MRs or .keys for user names as file extension work on both Rails platforms. I always found these file extension hacks very useful for quick access and automation. Examples: ht
148.
by dnsmichi 5y ago
Went ahead and created a MR to emphasize on 'reserved file extension' in the error message: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/70427 Thanks for the suggestion :)
149.
by dnsmichi 5y ago
Hi, how would you address this in GitLab's code? Maybe you'd like to create a merge request with suggested fixes :) https://news.ycombinator.com/item?id=28540665 has all URLs and issues available to get started in
150.
by dnsmichi 5y ago
Hi, the error message is a bit confusing - certain file type extensions may cause the user profile page not to load. Disallowing specific extensions in the username helps prevent that problem - it is not to prevent an injection attack or si

More ›