GitLab CI/CD (porting Github Action)

[varna]

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.

https://docs.gitlab.com/ci/migration/github_actions/#:~:text=GitHub%20Actions%20and%20GitLab%20CI,stored%20in%20the%20project%20repository.

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.

[naokihaba]

@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.yml that handles the Vite+ installation, Node and package manager setup, and dependency caching, just like the GitHub Action does now.

[varna]

@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.yml that handles the Vite+ installation, Node and package manager setup, and dependency caching, just like the GitHub Action does now.

Yep ✅

[naokihaba]

@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]

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]

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.

• https://docs.gitlab.com/ci/yaml/#includeremote
• https://docs.gitlab.com/ci/migration/github_actions/

So if we put a GitLab CI template in voidzero-dev/setup-vp and make sure the repo is public, GitLab users can just point to the raw GitHub URL like thi

include:
  - remote: 'https://raw.githubusercontent.com/voidzero-dev/setup-vp/v1/gitlab/setup-vp.yml'

This 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]

@naokihaba Can you implement this feature? I can test it out in our internal GitLab CI environment 🤗

[naokihaba]

Leave it to me!

[naokihaba]

We will handle this in the repository below.
I will create the issue soon.
https://github.com/voidzero-dev/setup-vp