Repository navigation
GitLab CI/CD (porting Github Action) #1920
Description
Description
Hello, we are using GitLab. It doesn't have integration for vite-plus CI/CD.
Suggested solution
Create equivalent of Github Actions on GitLab CI/CD, under voidzero org, in a public repo, where MRs could be made.
Alternative
Vibe code our own in our own org.
Additional context
No response
Validations
- Read the Contributing Guidelines.
- Confirm this request is for Vite+ itself and not for Vite, Vitest, tsdown, Rolldown, or Oxc.
- Check that there isn't already an issue requesting the same feature.
Activity
naokihaba commentedon Jun 24, 2026
@varna
Thanks for the request. I just wanted to clarify what you're looking for. Are you thinking of a GitLab CI equivalent to
voidzero-dev/setup-vp?https://github.com/voidzero-dev/setup-vp
Essentially, something we can reuse in
.gitlab-ci.ymlthat handles the Vite+ installation, Node and package manager setup, and dependency caching, just like the GitHub Action does now.varna commentedon Jun 25, 2026
Yep ✅
naokihaba commentedon Jun 25, 2026
@fengmk2
We've received a request for a GitLab CI version of setup-vp.
To support this properly, I think we'd need to set up an official place for reusable configs or components under the voidzero-dev organization, much like how setup-vp works for GitHub Actions. It probably means we'd have to create and maintain a new repository for it.
What do you think about providing official support for this?
fengmk2 commentedon Jun 25, 2026
Should this new repository be hosted on GitHub or GitLab? If it's on GitHub, will it be impossible to automate testing and verify GitLab's functionality?
naokihaba commentedon Jun 25, 2026
I'm not too familiar with GitLab CI/CD, but I checked their docs and it looks like include:remote lets you pull in a YAML file from any public URL via HTTP or HTTPS.
So if we put a GitLab CI template in
voidzero-dev/setup-vpand make sure the repo is public, GitLab users can just point to the raw GitHub URL like thiThis way, we don't actually have to host the source on GitLab.
The only catch is that hosting it on GitHub only covers distribution. To ensure the template actually works, we’d likely need a GitLab project or a mirror somewhere to run the pipelines and verify it.
fengmk2 commentedon Jun 25, 2026
@naokihaba Can you implement this feature? I can test it out in our internal GitLab CI environment 🤗
naokihaba commentedon Jun 25, 2026
Leave it to me!
naokihaba commentedon Jun 25, 2026
We will handle this in the repository below.
I will create the issue soon.
https://github.com/voidzero-dev/setup-vp
naokihaba commentedon Jul 6, 2026
Once the pull request is merged or a tag is released, we will run a final smoke test using include:remote.
At this point, we just need to run the smoke test, so I will go ahead and close this task for now.
voidzero-dev/setup-vp#97