3

I didn't get what's wrong with webhooks You just create a webhook on Gitlab CI side and provide this URL to your Jira account. https://gitlab.com/api/v4/projects/PROJECT_ID/ref/REF_NAME/trigger/pipeline?token=TOKEN PROJECT_ID - unique project id on Gitlab REF_NAME - your qa / stage / beta branches within repository TOKEN - uniquely generated access token (...


3

Are you sure that your registry is publicly available? Checklist: Check if the domain is reachable and responding the right IP address -- nslookup myregistry Check if your port is open or not blocked any kind of software (let's say via firewalls or AWS security group) -- telnet myregistry 5050 Check if your registry is not restricted for a particular CIDR ...


2

CI token used for code checkout is not allowed to do writes to the git repository (unlike GitHub Actions). You need to generate a new personal token and add it to secrets. See our integration project here as a sample: https://gitlab.com/taleodor/sample-helm-cd Note, if you search through StackOverflow, you may find several other ways to achieve this but in ...


2

Combining the answer of https://devops.stackexchange.com/a/3854/10932 and the comment of Overbryd along with a slight modification worked for me. Here, instead of using using git remote set-url command, I used git remote add. The code will look like this: image: maven stages: - build - deploy - tag maven_build: stage: build script: - mvn clean ...


2

What you need is not to checkout both projects side by side, but to add the library as a Git submodule in your application repository. Then set up GitLab CI to checkout submodules before build. This will not only make your CI work, but as an added benefit each commit from application repository will reference a specific commit from library repository, so ...


2

Runners are machines (typically containers) where your jobs run. Gitlab offers shared runners, and you can also bring in your own runners (machines that you register against Gitlab to run your jobs). The main difference between Gitlab shared runners and the ones you bring is that the shared runners are, well, shared, so sometimes you have to wait for a bit ...


2

When you use public IP the traffic exits your VPC and comes back in, at which point it is no longer identified as coming from that security group. So you can adjust your ssh connection and use private IP


2

This is likely because your requests were dropped before they landed on the GitLab host. Check your firewalls and other security rules after assured that the 1234 port is open


1

The answer to this question is no. I merely forgot to export the AWS_SECRET_ACCESS_KEY variable in the before_script section.


1

Yes, you can use the rules syntax. You can use this in combination with regex for commit message, ci_pipeline_source or any other available CI variables. job1: script: - do something on schedule only rules: - if: '"$CI_PIPELINE_SOURCE" == "schedule"' when: always job2: script: - runs on Merge request pipeline ...


1

I needed to change the distribution type. Thanks!


1

Can you explain the reason for why the "step_script" installs the dependencies and not use a prebuild images that has all the dependencies installed? Solution Based on the information you provided, Your test infrastucture rebuild even the test container from scratch. You tests take a long time to be done as those lines indicate also a fresh ...


1

One option for doing this is to create a database trigger. In Mysql In MySQL and MariaDB, you can do this with mysql-udf-http. From perodriguezl answer from Stack Overflow: You can use a mysql-udf-http and then create a trigger like this: delimiter $$ CREATE TRIGGER upd_check BEFORE UPDATE ON account FOR EACH ROW BEGIN IF NEW.amount > 0 THEN ...


1

Installing kubernetes integration on gitlab In Admin Area -> Overview -> Runners, the instructions they give are: Install GitLab Runner Specify the following URL during the Runner setup: https://<your gitlab hostname>/ Use the following registration token during setup: <insert-token-here> Start the Runner! I'm on version 13.13.0 but I don'...


1

You could use dynamic child pipelines. (https://docs.gitlab.com/ee/ci/parent_child_pipelines.html#dynamic-child-pipelines). You could create a job for triggering your job "buildArtifact" in a yml-file created with jsonnet in your "checkArtifactPresent". With using "--ext-str" or "--ext-code" in jsonnet. You can control ...


1

The image acts as a foundation for each container that you start from it. You might do the update in your 'fashion' way, but containers are ephemeral - let's say it got restarted, you updates are lost and you are back to the previous version. If you want to handle this process by yourself, how would you track your versions ? Essentially you would have a root ...


1

Instead of hard-coding your branch name in .gitlab-ci.yml use $CI_COMMIT_REF_NAME. There are a bunch of pre-set environment variables you can use to get info about the current job. The gitlab documentation has a list of them: https://docs.gitlab.com/ee/ci/variables/predefined_variables.html


1

I image you have used the dockerExecutor in gitlab-runner. This means you try to use docker-in-docker. https://docs.gitlab.com/ee/ci/docker/using_docker_build.html I suggest to configure the docker socket binding which might be less secure but very easy to handle. To register a runner with docker-in-docker support mount the /var/run/docker.sock:/var/run/...


1

I switched to using a production build for testing by use of a local webserver. I leveraging the [jest-puppeteer][1] library which allows you to start a webserver with your tests. jest-puppeteer.config.js /** * find all flags at the following site @jkr * https://jestjs.io/docs/en/cli */ module.exports = { launch: { devtools: true, // allows ...


1

You can specify that you want gitlab to execute your CI job on a windows machine using tags. Gitlab made Windows Shared Runners available as Beta in Jan 2020. Their announcement shows how to use the tags key in your .gitlab-ci file to specify Windows machines. You can also run in a docker container in windows: https://docs.gitlab.com/runner/executors/...


1

I want to share the solution! just add image = docker:stable and privileged = true and that's all! enjoy!


1

You are not able to create multiple .gitlab-ci.yml but you can manage to have what you want. You currently have multiple software in the same repository with the same CI/CD Pipeline or jobs for your softwares. You can use include in order to include local files from your repository, so you would get include: - local: 'my_folder/.gitlab-ci.yml' You can ...


1

If you prefer ssh connection use this: after_script: - git --version - git remote remove origin - git remote add origin git@gitlab.com:$CI_PROJECT_PATH.git - git tag -a v-$CI_COMMIT_SHORT_SHA -m "Version created by gitlab-ci Build" - git push --tags


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