Version Control on your Server. Visit https://gitlab.com/gitlab-org/gitlab for more information
Hey all
I'm looking for options of automating a deploy token - I already have some script that creates a subgroup off our variables/forks another repo into the subgroup.
I'm looking at options as far as creating a deploy token and i'm struggling with the script - I think It may require admin access to my generated token id which I don't currently have but it'd be nice to have a second set of eyes on it
var code = "formatted";
import gitlab
import sys
# tokenauthentification
# token = 'my token'
gl = gitlab.Gitlab(private_token='my_private_key')
#
group_parent_id = 'my_created_parent_id_from_prior_script'
# %%
deploy_tokens = gl.deploytokens.create({
'name': 'name',
'scopes': ['read_repository'],
'username': 'username',
'expires_at' : ''})The error is 'DeployTokenManager' object has no attribute 'create' which to me means the deploytokens path isn't correct but it's what's current on readthedocs :/
2 replies
- Effective June 1, 2022, all free tier public projects will be included in the 400 minutes per month CI/CD minutes quota.
- Before July 1, 2022, all free tier public open source projects will need to enroll in GitLab's Open Source Program to continue to receive GitLab Ultimate benefits.
4 replies
release_job:
stage: release
needs:
- job: build-web
artifacts: true
image: registry.gitlab.com/gitlab-org/release-cli:latest
rules:
- if: $CI_COMMIT_TAG
- if: $CI_COMMIT_BRANCH == 'master'
script:
- echo "Running the release job."
release:
tag_name: '$CI_COMMIT_TAG'
ref: '$CI_COMMIT_TAG'
name: 'Release $CI_COMMIT_TAG'
description: 'Release created using the release-cli.'$ echo "Running the release job."
Running the release job.
Executing "step_release" stage of the job script
00:01
$ release-cli create --name "Release $CI_COMMIT_TAG" --description "Release created using the release-cli." --tag-name "$CI_COMMIT_TAG" --ref "$CI_COMMIT_TAG"
time="2022-05-07T19:01:08Z" level=info msg="Creating Release..." cli=release-cli command=create name="Release " project-id=32201481 ref= server-url="https://gitlab.com" tag-name= version=0.11.0
time="2022-05-07T19:01:08Z" level=fatal msg="run app" cli=release-cli error="failed to create release: API Error Response status_code: 422 message: Ref is not specified" version=0.11.0
Cleaning up project directory and file based variables
00:01
ERROR: Job failed: exit code 1
Hi, I come here because I have a problem with a self-hosted runner and GitLab SaaS (gitlab.com). My runner can’t clone our private repositories anymore due to a SSL error.
Here is the error:
fatal: unable to access 'https://gitlab.com/company/group/subgroup/project.git/': SSL certificate problem: unable to get local issuer certificateDoes anyone else have this error ? I can see that the certificate of gitlab.com is expirating in 3 days, but I’m not sure it’s linked…
Checking for jobs... nothing. And it never actually picks up the job unless I pause/resume the runner, or delete the pod in K8s so it creates a new runner pod. I'm not finding much about this on the internet, and been debugging it for a few hours. Currently using gitlab-runner:alpine3.15-14.9.2 for the runner
Checking for jobs... nothing. And it never actually picks up the job unless I pause/resume the runner, or delete the pod in K8s so it creates a new runner pod. I'm not finding much about this on the internet, and been debugging it for a few hours. Currently using gitlab-runner:alpine3.15-14.10.0 for the runner. Gitlab is running 14.10.0 currently
Hi,
I added container scanning to my GItlab pipeline, but I dont see this stp in the pipeline nor their is any error.
FYI: My repo is private and weuploade our images to Gitlab COntainer registry.
THough doing this would suffice:
include:
- template: Jobs/Build.gitlab-ci.yml
- template: Security/Container-Scanning.gitlab-ci.yml
Let me know if i am missing something
hey yeall
is downloading release assets from private repos via the API still busted? gitlab-org/gitlab#28978
curious what the right way to do this is
Hi all, I’m a recruiter at GitLab and wanted to let you know about a new team we are building here called Contributor Success. Our mission is to increase the efficiency, incentive & reward of our contribution process in order to achieve our ambition of supporting & achieving over 1000 community contributors to the Gitlab project!
We're looking for backend engineers today that have experience with contributing to open source projects like GitLab. You’ll have an opportunity to grow our community, make it easier to contribute and support various open-source initiatives across the wider ecosystem.
If you’re open to discussing a new full-time position with me or have any questions, feel free to drop me a message at mangell@gitlab.com or DM me here in Gitter!
Thank you and have a great day.
2 replies
Hi Guys... need a hint.
In a gitlab runner I try to set SSH_COMMAND. for win machine (no docker)
If I set it in beforescript part as${env:GIT_SSH_COMMAND} = 'ssh -vvv -i "C:\\Users\\te\\.ssh\\id_rsa" -o UserKnownHostsFile=C:/Users/te/.ssh/known_hosts'
it works.
however I would like to set it in variables (as we do for linux pipelines)env:GIT_SSH_COMMAND : 'ssh -vvv -o UserKnownHostsFile=c:/Users/te/.ssh/known_hosts -i "c:\Users\te\.ssh\id_rsa"'
It works only partially. UserKnownHostFile is just ignored. Everything else works.
What happens?
By trial and error I discovered that it might depend on how I pass the paths ( \ vs / vs \\, what quation marks I use...)
But I am unable to figure out how to make it work.
Hi there, I come here because we just experienced a severe issue regarding GitLab SaaS issues (free tier).
We created a project 4 days ago, along with an issue that was given the id 1. Today, we couldn’t find the issue on the project at all.
One of our developer had the issue page still opened in his browser, so he shared the link with us, but it gave us a 404 page when trying to open it.
The same developer just hit the refresh button and also got a 404.
In order to narrow down the problem and see if we deleted the issue by error, we created a new issue, which was also given the id 1 (weird).
We intentionnaly deleted this issue, and created a new one, which was given the id 2 (better).
This behavior strongly suggests that the problem is on GitLab and not on us. There isn’t any issue reported on status.gitlab.com.
I see that GitLab 15.0 was released recently, could it be the source of the issue ?
Also, we found another weird thing: there is no activity log when deleting an issue, and the issue creation log is also deleted ! This behavior seems off, why purposefuly rewrite activity logs rather than append to it ?