gitlab

问题 How to unignore folder with a particular name (e.g. Sync) that can be located anywhere inside the repository and Recursively allow everything inside it, violating every other rule of gitignore? 回答1: The solution proposed ( !/**/Sync/**/* ) would not work alone, because It is not possible to re-include a file if a parent directory of that file is excluded. So if you have a .gitignore with: * !.gitignore You must whitelist folders first ( !*/ ) and then exclude files ( !**/Sync/** , no need for

问题 I have a Gitlab 8.0 server(25 projects, 10 users, 30+ ssh keys), I want upgrade to newest version, but seems no easy way to do this. Following the upgrade guide, I have to upgrade step by step, means I may need 10+ hours to do this. :( Can any one teach me what's the easiest way to upgrade to last version ? 回答1: I had to do the exact same migration, and... I had to script it. That is because I needed to upgrade to 9.0, 9.1,9.2...10.0, 10.1, ...,11.0, ... to finally 11.5. So if you do an

问题 I'm familar with Bamboo but new to gitlab ci, I have tried several times with gitlab and found a key advantage of gitlab is the automatic cloning of git repository . The tricky part is gitlab ci can even clone repository into docker container automatically . my git repo: .git .gitlab-ci.yml foobar.sh this job: job1: stage: run image: name: my_image script: - ./foobar.sh - some other scripts within the docker can successfully run. The log shows after pulling my_image, there's a git clone

问题 I have set up a Bitnami GitLab stack as a running virtual machine instance using VMWare Workstation on my personal dedicated Windows server (host) running out of my home office. My dedicated Windows server host has a publicly visible static IP address. I have successfully gained public access to the GitLab application running as guest by setting up port forwarding within VMWare Workstation's Virtual Network Editor (using NAT translation, not bridging). I am able to access the GitLab web

问题 I'm building docker images for gitlab and I want to follow docker design – one process in one container. Is it possible to run gitlab shell in a separate container (with sshd)? Should I be aware of any pitfalls? 回答1: Seems it's not possible, according to these lines in gitlab.yml : ## GitLab Shell settings gitlab_shell: path: /home/git/gitlab-shell/ hooks_path: /home/git/gitlab-shell/hooks/ 来源： https://stackoverflow.com/questions/45057746/running-gitlab-and-gitlab-shell-separately

问题 I have 2 web servers. On server A I have a GitLab installed. On server B I just initialized a bare Git repo. Now I want to automatically push the GitLab repo to server B using GitLab's remote repository mirror function For this I need an HTTPS or SSH url, and I want to do it with SSH. Question 1: What is the url I need to insert there? I guess it should be something like ssh://ssh-user@server-b.com:path-to-git-repos/project.git . Is that right? Question 2: Since the user connecting to the url

问题 I have seen that the Gitlab WebUI allows to set-up mirroring for repositories from e.g. Github (under MyCoolRepository --> Settings --> Repository --> Mirroring repositories). I have seen that this is possible over the API, too: https://docs.gitlab.com/ee/api/projects.html#start-the-pull-mirroring-process-for-a-project Does anyone know how this works and which parameters the API needs for id ? I wanted to automate this process in a script because I do not want to set-up the automatic

问题 I'm pushing my Phoenix app to a Kubernetes cluster for review. I use GitLab to create a service for the web server and another service for a temporary postgres pod. What I would like to do is automate mix ecto.create and mix ecto.migrate . However, there is a timing issue - there's a short period of time when the postgres server is not ready yet. I could poll the postgres service in my deployment script before creating the web application service. But is this the most practical method? 回答1:

问题 I've been trying to pull down a repository from Gitlab using SSH keys. All done in command line on Windows 8 via a Ubuntu VM. I've added my public key to my Gitlab account and then added my private key to the ssh-agent and didn't seem to have any errors in doing so but when I try and do a git pull or push I run in to this error; fatal: unable to access 'https://git.mgmt.local/XXX/project-name.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: