Episode #125 of the Stack Overflow podcast is here. We talk Tilde Club and mechanical keyboards. Listen now
5

I tried to change docker image and added couple steps for git tag. Below is the answer worked for me, image: maven stages: - build - deploy - tag maven_build: stage: build script: - mvn clean package artifacts: paths: - target/*.jar after_script: - ls -a - cd target && ls -a - git --version - git remote remove origin ...


3

This is a glibc dependency issue on Alpine. This azcopy binary is compatible with Linux distributions that use glibc, GNU's C standard library. Alpine Linux uses a different libc implementation, musl-libc, which is generally not compatible to glibc. When trying to run non-Alpine-built binaries on Alpine, they'll usually fail to link since the glibc shared ...


3

It might not be obvious now, but usually as projects advance full regression costs (resources/time) grow much faster than static analysis ones. You'll also find that static analysis alone isn't a sufficiently solid bug gate, it must be complemented with regression testing as well. So I'd place the full regression after the static analysis in the CI/CD ...


3

I dealt with the same issue. Some people recommended using the Gitlab group "secrets" and using before_script. Since I knew I was also going to deploy and would need other tools on my runner like "helm", I made my own docker container. I still keep my config for my clusters in a base64 encoded group secret but I set it like this in the dockerfile. ENV ...


3

No, you can't have multiple gitlab-ci files per repository. You can see more information in the following links : https://gitlab.com/gitlab-org/gitlab-foss/issues/18157 https://gitlab.com/gitlab-org/gitlab-foss/issues/28592 Now, there are some work in progress about this, but it's not available yet. For example, you can see here ( https://gitlab.com/...


3

You're missing the --non-interactive tag to your registration command. Full command should be: gitlab-runner register --non-interactive --locked false --run-untagged true --tag-list java --name foo --registration-token %token% --url https://myurl --executor shell Relevant documentation for non-interactive registration.


2

There currently isn't a solution for building on a specific runner in GitLab, but there is an issue open for Sticky Runners, which hopefully will be out in the next 3-6 months according to the Milestones! The work around I've done so far to build a project on a specific runner is to use the GitLab Runner API, in a rather hacky way, along the lines of: Get ...


2

Surprisingly indeed GitLab works weirdly with the env vars. It evaluates them internally, though it shouldn't in my view. Value set as (in project Settings > CI/CD > Variables): 'aaa$bbb*%' becomes 'aaa*%' (with single quotes left!) Couple of of proof links: https://gitlab.com/gitlab-org/gitlab-ce/issues/45173#note_101659865 https://gitlab.com/gitlab-org/...


2

GitLab and GitLab CI are not two servers: they are softwares installed on a server. Now, while both can be installed on the same server, they can be split for scaling reason. Now your question: it all depends on what type of services your are running. Bear in mind that CI can take CPU/memory and disk bandwidth while running your CI (docker image build, ...


2

I might have skipped the optional installation of docker in my Ubuntu instance, so if the gitlab runner is going to use Docker, remember to install it: curl -sSL https://get.docker.com/ | sh I got back to this issue and seem to have partially fixed it by checking it the gitlab runner is running gitlab-runner status systemctl is-enabled gitlab-runner ...


1

Gitlab CI/CD offers Docker Engine. If you can create a docker image, you can serve the application the same way as you were doing with Jenkins. You can find more details on how to integrate both here. Hope it helps.


1

There are some fundamental misunderstandings in your bullets which makes your question unclear: Apple will not allow you to develop/build using a virtual system. I believe this is a legal constraint. That said, you can run pretty much anything in VirtualBox as long as you have a legally provided image (e.g. a Linux image). You can only run the Windows ...


1

This is not answering only the question but also a bit more (I put this here for reference): I found out a decent way to tackle this and some complications coming afterwards... (after hours and hours of fiddling) - e.g. to execute the script in an SSH session: deploy job: variables: # the variables could come from anywhere (e.g. GitLab Settings - ...


1

Well this seems to be a docker issue. It’s keeping a whole lot of dangling volumes. check if you have some : docker volume ls -qf dangling=true Get rid of them with : docker volume rm $(docker volume ls -qf dangling=true)


1

No, jobs (which rust-latest and rust-nightly are examples of) will run in parallel if they are in the same stage (of which you only have one, build).


1

AFAIK there are only 2 ways of deploying GAE apps: using the gcloud app deploy command: gcloud app deploy - deploy the local code and/or configuration of your app to App Engine using the Admin API. From Deploying Your Apps with the Admin API: To deploy a version of your app with the Admin API: Upload your app's resources to Cloud Storage. ...


1

Your second link just use the official cookbook. This official cookbook still uses the LWRP syntax, so you need to check in the provider directory for the resource action code -- which for register is basically just two execute commands (extract from the file linked above): converge_by("Register runner #{new_resource.description}") do execute "#{env} ...


1

For a specific GitLab runner tied to a project, the token can be found in Step 3; in Project -> Settings -> CI/CD -> Runners in the Setup a specific Runner manually section. You will also be able to find the URL which you need to use to register the runner in Step 2.


1

The answer is that all Auto Dev-Ops deployments at present use Helm to package and deploy your application. In order to make changes to the deployment, such as adding a persistent volume claim, you should download and modify the Helm chart that GitLab uses. The files in this repo should go into a new directory chart/, or you can link to another location by ...


1

git push origin 1.0.15 should work and a new tag should be added to the tags in gitlab https://docs.gitlab.com/ee/university/training/topics/tags.html git checkout master # Lightweight tag git tag my_lightweight_tag # Annotated tag git tag -a v1.0 -m ‘Version 1.0’ git tag git push origin --tags


1

Note: I didn't use this yet, the answer is based solely on documentation. A GitlabCI pipeline can be triggered via API, see Triggering pipelines through the API. Triggers can be used to force a pipeline rerun of a specific ref (branch or tag) with an API call. You would first need to create a trigger for that pipeline. Then you can activate that ...


Only top voted, non community-wiki answers of a minimum length are eligible