-
-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate to GitLab #406
Comments
@claytonrcarter @rsteube @prarit for visibility (if there's any opposition to moving over nows the time to voice it ;) |
I have a copy of lab on gitlab FWIW. https://gitlab.com/prarit/lab I will nuke it if necessary to free up the namespace. |
Nah, makes sense as it will tend to more usage of it during development (EYODF). |
Welcome @mocha and @leipert -- they'll be aiding us on the GitLab side to get everything over. @leipert to post his thoughts on best approach. So far we've talked about getting the project imported and with a 1way mirror (github -> gitlab) to start, with the ultimate goal of reversing the direction or even severing the mirror. |
@rsteube Good point There are some small things we can do (called out on the issue) to make this work nicer. I imagine many of us will have private instances and need to work with gitlab.com -- Long term I want to redo the config for 1.0 and support this sensibly |
Quick fix would be to just look at the origin remote domain of the current project (if any) to load configuration for that and fall back to the default otherwise. |
I have had a look, (as you already have seen by MR) and wanted to leave a proposal for an updated plan on the move with added responsibilities.
@rsteube Interesting, I think #151 is a good idea to focus on, I wouldn't see it as an impediment though for the move, given that it "only" affects collaborators on
Seems like we can "artificially" limit concurrency in GitLab to one, with the help of Resource Groups. Thanks for the tip though, I will add it to the MR right away. |
@leipert Plan looks good, a couple notes:
I've updated #409 so the tests are working now, I'm going to continue on to see if I can get some of the release functionality working too. I've added you to the https://gitlab.com/zaquestion/test repo and to the
The import should handle this, I can see the releases made it over in this import already: https://gitlab.com/gitlab-org/ecosystem-team/lab/-/releases |
@leipert @mocha Reminder that lab currently uses the CC0 license: https://github.com/zaquestion/lab/blob/master/LICENSE Any friction there? |
Any progress on this? Can see some work for gitlab-ci on gitlab.com but seems the jobs still fail. |
Need to fix the tests on GitLab, which all broke when the config changes happened I believe, but #455 should be enough for us to make the cutover once that's done. We'll probably need to poke @leipert on the actual GitLab issue, since I think over here is probably less visible for them https://gitlab.com/gitlab-org/gitlab/-/issues/14448 |
What about now ? Is the migration still planned as before ? |
@Atralb I need to reengage the folks at GitLab, to get this actually moving again, which I'm planning to do in the new year. That said, I'm planning to sort out the |
Hey folks! Sorry for the long time with no movement. I was on a long leave until just before the holidays (👶 🥳). Let's pick this up in the new year. I will figure out what stuff that we need from you @zaquestion, I think some access to some projects was missing, but otherwise we should be good to go 😄 |
Hey @leipert , I think @zaquestion was planning on releasing 0.18 this week. @zaquestion ,what do you think of creating a 0.19 release that only had this issue in it? ie) all 0.19 would be is the move to GitLab? I know in some ways it would be a throwaway release but I think that being able to point to a specific release would be good for future debugging and testing. |
FYI, I would love to see a new version released, especially to fix some bugs. But, for information, I've tried to built So, it could be cool to check this is working in other OS before doing a release because it can be worse for some case. BTW, if you need help to migrate to GitLab, as a GitLab Hero, I can help if you want, 👍. |
Released |
Installed and working, 👍 |
@leipert -- any update here? Just curious if you've made any progress. I'd really like for this issue to be the focus of the next release. |
It looks like GitLab has chosen to go with |
Makes sense going for glab. Haven't been working with gitlab for quite a while, but when i did i was favoring it myself as well. |
I like In any event as a distro packager I was just looking around for what the future of this project was looking like. I got a lot of millage out of it myself and thank the contributors. Going forward it would probably be nice to have a plan—either migrate and continue development or call it unmaintained or something. |
Hi folks, thanks for the kind words it means a lot. GitLab didn't communicate anything with me about it, but I would make the same guess as above, they wanted to adopt I'm very proud of this project, and while I wish that we had been allowed to live alongside |
Oh one final note, this tool lives on in |
GitLab has had an open issue for a while now desiring a "Lab CLI for GitLab", and we've made ourselves known. More recently we've started talking about officially making the move into GitLab's official namespace.
See: https://gitlab.com/gitlab-org/gitlab/-/issues/14448#note_399479784
This issue aims to capture the immediate todos to get
lab
fully re-homed functionally speaking. (no particular order).goreleaser
to upload artifacts as GitLab release artifactshomebrew-core
install.sh
to look for GitLab homed artifacts./docs
) in GitLab PagesGOPATH
)0.18.0
out (good forcing function for this stuff)Longer Term
v1
branch so gitlabers andlab
maintainers alike can start introducing new vision, rehauls, and other breaking changes (Starting with items in the 1.0 project)The text was updated successfully, but these errors were encountered: