greenled / portainer-stack-utils

CLI client for Portainer

Home Page:https://hub.docker.com/r/greenled/portainer-stack-utils/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Migration to GitLab

greenled opened this issue · comments

We are moving to GitLab. It offers integrated CI/CD, issue boards and project pages built on any website generator, not just Jekyll. This issue is for tracking the progress of such migration.

What will be migrated (see https://gitlab.com/help/user/project/import/github.md):

  • Repository
  • Issues and Merge Requests (with comments)
  • Milestones
  • Labels
  • Release note descriptions

There are previous related comments in #4.

I imported the project into GitLab, but only the repository was imported: no issues, no PRs....

Screenshot_2019-07-31 GitHub import

It actually failed importing

And it failed again

Ok, it finally worked (twice, about 10min to import each time). Looks good so far. Maybe should take some actions before migrating. See https://forum.gitlab.com/t/recommended-practices-for-moving-an-oss-project-from-github-to-gitlab/29068.

Hi @greenled,

What's your timeline for migrating this repository to GitLab, is it still in your plan?
Because the next psu bash version (1.0-next branch) is deeply integrated with GitLab CI, so maybe we can just have a mirror repository on GitLab and keep issues on this one...
Or split the project in two repositories, one on GitLab for the bash version and this one on GitHub for Go version, what do you think?

Have a good day,
Tortue Torche

Hi @greenled,

FYI, I just published the 1-0-stable branch 🚀 on GitLab : https://gitlab.com/psuapp/psu
Documentation: https://psuapp.gitlab.io/psu/1-0-stable
Docker images: https://hub.docker.com/r/psuapp/psu

With auto builds, tests, and push to Docker Hub.

Then we can add some explanations on this repository and the GitLab one, to get the correct version:

  • Go version (psu 2.0) => GitHub
  • Bash version (psu 1.0) => GitLab

Have a good day,
Tortue Torche