jl-gitlab · HackerTrans

hace 7 añosdiscuss

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

hace 7 añosdiscuss

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

hace 7 añosdiscuss

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

hace 7 añosdiscuss

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

hace 7 añosdiscuss

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

hace 7 añosdiscuss

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

hace 7 añosdiscuss

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

hace 7 añosdiscuss

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

hace 7 añosdiscuss

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

hace 7 añosdiscuss

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.

jl-gitlab

hace 7 añosdiscuss

Ah, I understand. We do have users who prefer the stage model or hybrid DAG mixed with stages, but I get that that isn't your point of view. I do hope that after the next couple releases it becomes something more useful for you - your use case is important too.

Releasing early to get feedback on issues is important to us but we can do better communicating around what's an early preview vs. a mature feature. The maturity page that's linked to in this discussion is actually part of how we are trying to improve our communication around that. This is more at the stage and category level, but features have a maturity level as well and it's worth us reflecting on how that can be made more clear.

jl-gitlab

hace 7 añosdiscuss

We released DAG as an MVC, which helped a lot of people out even in its current state. We do release features here iteratively intentionally, with the idea that feedback will help make future iterations better in unexpected ways compared to if we released a big feature all at once.

The items you mention are scheduled for follow-ups in our epic https://gitlab.com/groups/gitlab-org/-/epics/1716. Your feedback on sequencing or how we are approaching the different improvements is more than welcome.

I would have loved for the feature to be useful for you too in the MVC iteration, and I'm sorry it wasn't. We are still working on it, though, and I hope that it does become valuable for you also. In the meantime you should still be able to use GitLab in the same way you always have - let me know if you're having trouble running pipelines without the DAG.

jl-gitlab

hace 7 añosdiscuss

Hey, I'm Jason - the PM director for this area. I really do appreciate the pings - you can @ me at my username jlenny in issues that are important to you. It's true in general, even for features, but especially for issues a heads up helps us make sure we are prioritizing things in the right order.

jl-gitlab

hace 7 añosdiscuss

I've created https://gitlab.com/gitlab-org/gitlab-ce/issues/64995 - please join us in the conversation there.

jl-gitlab

hace 7 añosdiscuss

Thanks for the super clear description! Doing some internal research on this.

jl-gitlab

hace 7 añosdiscuss

Hey there, PM for CI/CD here. Can you point me to an issue in either GitLab or the Jenkins Plugin repo that has more info specifically on what you're looking to do that isn't possible today? Or share specifically what you need here so I can make one? That other project seems to have a few different features and I'm not sure which use cases exactly are important for you.

In any case, we definitely want to make sure you have the right functionalities you need.

jl-gitlab

hace 7 añosdiscuss

Here at GitLab we're an all-remote company, and it's been that way since the beginning as I understand it. I've been here about a year now and I've heard so many great stories from people who had remote working change their life for the better. A while back I made a space to collect these, if you're interested in this topic you might find some of these inspring: https://about.gitlab.com/company/culture/all-remote/stories/

jl-gitlab

hace 7 añosdiscuss

Very nice! I'm the PM for CI/CD here at GitLab and think this is a wonderful idea. Feel free to reach out if you have any questions or need any support - my contact info can be found publicly on my GitLab profile: https://gitlab.com/jlenny

jl-gitlab

hace 7 añosdiscuss

For transparency I want to start by saying I'm a GitLab employee, but working for an all-remote company has changed my life. More time with family has been the most important, and I'm an expat so being able to travel and visit family overseas has been amazing.

It's hard to describe, but when the entire company is remote it's such a different experience than being one remote person or part of a remote sub-group. The whole company knows how to operate remotely and be effective in that way. I've never seen anything like it, but now I can't imagine working in any other way. If I started a company in the future, I am 100% confident it would be all-remote from day one.

We have a nice page up on our site with people's experiences with remote work. If you're interested in the topic it might be worth reading: https://about.gitlab.com/company/culture/all-remote/stories/

jl-gitlab

hace 7 añosdiscuss

I'm a GitLab employee, and before working here always struggled with remote work. There's a tipping point, though, at an all remote company where when everyone is remote, the communication structures of the company adapt to having clear communication through video, chat, and email. We do a lot of video chat here. It's hard to describe what it's like, but it certainly doesn't feel like we're all locked away in little boxes with only awkward or indirect ways to interact with each other.

comments