joshlambert

6 ms·

1. 1.▲
   by joshlambert 4y ago

   > "Advanced" search is completely useless as you can't really search for code. @deng - thanks for the feedback. I am on the Product team for our Search service, code search is not where we would like it to be. We are in-p
2. 2.▲
   by joshlambert 6y ago

   @cmckn - PM @ GitLab here - sorry to hear you had a poor experience with running our GitLab chart on k8s. We've been trying really hard to make this easier, but there is still some room to go especially on the documentation front: htt
3. 3.▲
   by joshlambert 6y ago

   Hi, GitLab product manager here. I'm sorry that we haven't provided a good experience. We try really hard to make sure GitLab deployments "just work", and clearly it does not for either of you. Both Puma and Unicorn shou
4. 4.▲
   by joshlambert 6y ago

   Thanks for the feedback entha_saava. GitLab.com is indeed slower than GitHub.com today, and we need to provide a better experience for our users. Improving frontend performance is a key focus area for us, and while we started this specific
5. 5.▲
   by joshlambert 6y ago

   Please read through the upgrade notes for 13.0 as there are some important changes like PG11 being a minimum requirement. As for the actual upgrade, you should be able to follow the standard process outlined here since you are persisting yo
6. 6.▲
   by joshlambert 7y ago

   The breakdown is probably close to the percentage of paying versus open source customers that we have. We are working to better educate our users on the value that our paid version can offer, but it is very important for us to be good stewa
7. 7.▲
   by joshlambert 7y ago

   Hi, we do believe in the single application offering the best long term user experience and outcomes, but do understand that all of our features may not work for everyone. This is happens for a variety of reasons (completeness, migrations,
8. 8.▲
   by joshlambert 7y ago

   Hi - I'm sorry for the experience you had. I'm the PM for our Runner team, and we're focusing our next milestone purely on fixing some high priority outstanding bugs, that have been open for longer than they should have. Is t
9. 9.▲
   by joshlambert 7y ago

   Hi - thanks for the feedback, we aren't where we want to be with performance. We are working hard to improve responsiveness and memory consumption, and have a recently started a team focused on just these aspects to accelerate the impr
10. 10.▲
    by joshlambert 7y ago

    Hi - just wanted to confirm that this issue has been addressed and will be included in our 12.4 runner release. MR: https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/1...
11. 11.▲
    by joshlambert 7y ago

    Hi - we've been discussing how to better anchor these on quantitative data, rather than the subjective opinion of GitLab PM's. You can see some of the discussion here ( https://gitlab.com/gitlab-com/Product&#x2
12. 12.▲
    by joshlambert 7y ago

    Thanks for the additional information. The `git_data_dir` and gitaly configuration changes are indeed why we've started requiring moving to the last minor version first. The 10.x to 11.x upgrade was the first major upgrade with these c
13. 13.▲
    by joshlambert 7y ago

    Hi, I'm a PM for our linux packages. I'd love to learn more about the cryptic issues and vague errors mention. We've put a lot of effort towards making the upgrades as painless as possible, with few surprises. One way we&#x27
14. 14.▲
    by joshlambert 7y ago

    Thanks, and please keep up the feedback. =)
15. 15.▲
    by joshlambert 7y ago

    Merge request to link to our definition of PNPS: https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/... . Should be merged momentarily.
16. 16.▲
    by joshlambert 7y ago

    Thank you for the feedback. We aren't happy with performance and we are working hard to improve it. We have two major projects under way, switching to Puma ( https://docs.gitlab.com/omnibus/settings/puma.html )
17. 17.▲
    by joshlambert 8y ago

    We have established teams for each of our DevOps stages: https://about.gitlab.com/stages-devops-lifecycle/ Package encompasses both the Container Registry, as well as other repository types like Maven, NPM, etc.
18. 18.▲
    by joshlambert 8y ago

    I'm sorry this has taken so long, but we are working on some foundational API's to manage and list images right now: https://gitlab.com/gitlab-org/gitlab-ce/issues/55978 . I've also added your f
19. 19.▲
    by joshlambert 8y ago

    slap_shot one of our major goals is to provide a solution that startups and small companies can utilize to start putting their data to work. It shouldn't take weeks of effort, a data engineer, multiple proprietary solutions, and tens o
20. 20.▲
    by joshlambert 8y ago

    Thanks for watching mfer! Kaniko certainly doesn't address all of the challenges with building containers securely, but I think it's the best solution available _today_ that supports the common Dockerfile workflow. There are a num
21. 21.▲
    by joshlambert 8y ago

    We've had Mattermost integrated for quite some time, it predates the gitter acquisition. It's in use by around 5% of our installations and has a passionate userbase.
22. 22.▲
    by joshlambert 8y ago

    samm we are indeed making all components that are not core gitlab services optional. You will be able to turn them off with a simple `prometheus.enabled=false`. Thanks for giving the charts a try in alpha/beta, please pass along any fe
23. 23.▲
    by joshlambert 8y ago

    jancsika, totally understand the forking workflow is not ideal right now. Thanks for sharing your use case and using GitLab. We are tracking more formal support for this here: https://gitlab.com/gitlab-org/gitlab-ce&#x2
24. 24.▲
    by joshlambert 8y ago

    If it is a forked project, CI should run in their own project I believe. It should not run on your Runners.
25. 25.▲
    by joshlambert 8y ago

    Quick note, the existing Let's Encrypt integration does not support Pages. We are working on it, but it's worth noting Pages has multiple modes it can run in. One is by setting up wildcard domains at the server level, like we have
26. 26.▲
    by joshlambert 8y ago

    Thanks for the report @theptip. Did you happen to open an issue? It would be great to ensure this one is being tracked appropriately.
27. 27.▲
    by joshlambert 8y ago

    @jancsika you could implement a whitelist using this feature, by having jobs only run for specific usernames. Keep in mind though that these variables can be overridden, so it probably shouldn't be used for security reasons: https:&#x
28. 28.▲
    by joshlambert 8y ago

    In my experience the GitLab Runner on k8s should utilized the cache. Are you using Docker-in-Docker by chance? By default, I don't think it can cache data between jobs.
29. 29.▲
    by joshlambert 8y ago

    I agree, that would be awesome! While it's not a single button, GitLab is getting closer to that goal with the addition of our cluster integration feature: https://docs.gitlab.com/ee/user/project/clusters
30. 30.▲
    by joshlambert 8y ago

    Thanks, glad you are finding it helpful! We have a lot of improvements coming as well: https://about.gitlab.com/direction/#ci--cd