jl-gitlab

8 ms·

1. 1.▲
   by jl-gitlab 7y 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 Git
2. 2.▲
   by jl-gitlab 7y 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/runner
3. 3.▲
   by jl-gitlab 7y 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
4. 4.▲
   by jl-gitlab 7y 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 l
5. 5.▲
   by jl-gitlab 7y 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/
6. 6.▲
   by jl-gitlab 7y 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
7. 7.▲
   by jl-gitlab 7y ago

   We are looking at adding many new kinds of packages, including potentially Linux package types such as these https://about.gitlab.com/direction/package/package_registry/...
8. 8.▲
   by jl-gitlab 7y 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'
9. 9.▲
   by jl-gitlab 7y 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 anot
10. 10.▲
    by jl-gitlab 7y 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 im
11. 11.▲
    by jl-gitlab 7y ago

    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
12. 12.▲
    by jl-gitlab 7y ago

    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
13. 13.▲
    by jl-gitlab 7y ago

    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
14. 14.▲
    by jl-gitlab 7y ago

    I've created https://gitlab.com/gitlab-org/gitlab-ce/issues/64995 - please join us in the conversation there.
15. 15.▲
    by jl-gitlab 7y ago

    Thanks for the super clear description! Doing some internal research on this.
16. 16.▲
    by jl-gitlab 7y ago

    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 nee
17. 17.▲
    by jl-gitlab 7y ago

    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 th
18. 18.▲
    by jl-gitlab 7y ago

    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:/&#x
19. 19.▲
    by jl-gitlab 7y ago

    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 fam
20. 20.▲
    by jl-gitlab 7y ago

    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
21. 21.▲
    by jl-gitlab 7y ago

    These are personal anecdotes, but here at GitLab we recently started recording our personal stories about how remote working changed our lives. If you're interested in remote work you may also find this interesting: https://
22. 22.▲
    by jl-gitlab 7y ago

    Thanks for sharing, this is really great feedback.
23. 23.▲
    by jl-gitlab 7y ago

    You can actually use it standalone, for example with GitHub repos: https://docs.gitlab.com/ee/ci/ci_cd_for_external_repos/githu... (Disclaimer: GitLab employee here)
24. 24.▲
    by jl-gitlab 7y ago

    GitLab CI/CD product director here - we're working towards making includes more flexible to give you a lot more control. Would love your feedback on the small primitives we're looking at here: https://about.gitlab.
25. 25.▲
    by jl-gitlab 7y ago

    Hey there, CI/CD product director here. We do allow scheduling/editing/deleting pipelines via code, at least via an API: https://docs.gitlab.com/ee/api/pipeline_schedules.html Or are you looking mor
26. 26.▲
    by jl-gitlab 7y ago

    Thanks for the incredible feedback! CI/CD product director here. A few thoughts: - Templates We actually have done a lot here recently, we've improved includes so that they have a lot more flexibility ( https://docs.gitl
27. 27.▲
    by jl-gitlab 7y ago

    You may find our direction page for CI/CD at GitLab interesting if you're looking to learn more about the possibilities involved here. We do all of our planning and roadmapping in public so you read a bit about our overall technic
28. 28.▲
    by jl-gitlab 7y ago

    GitLab product director for CI/CD here - thanks so much for the feedback, everyone. It's really great to read how much you're getting value out of what we built. We have an overall CI/CD direction page up at https:&#x2F
29. 29.▲
    by jl-gitlab 7y ago

    We're building some similar tech at GitLab, though without the dependency analysis yet. Merge Requests now combine the source and target branches before building, as an optimization: https://docs.gitlab.com/ee/ci&#
30. 30.▲
    by jl-gitlab 7y ago

    Yes, this is something we're definitely investigating! We have an issue open at https://gitlab.com/gitlab-org/gitlab-ce/issues/55840 , please join us in the conversation there if you have thoughts on how