Version Control on your Server. Visit https://gitlab.com/gitlab-org/gitlab for more information
While the cache could be configured to pass intermediate build results between stages, this should be done with artifacts instead.
. However, this doesn't needs to be an artifact that's saved and stored in some place because it is only needed for the consecutive stage. Hence I am confused a little
allow_failure: true
on the previous step instead?
rules:
- if: $CI_COMMIT_BRANCH =~ /^release\/v\d+.\d+.\d+$/
when: manual
allow_failure: true
Hi, wondering if anybody could help me with an issue with using trigger / bridge jobs.
I have Project A which contains global variables in the CI YAML. Project B downstream also contains global variables which I do NOT want to override. I understand upstream variables have precedence over downstream vars, so I want to avoid passing Project A's global vars to Project B.
My .gitlab-ci.yml for Project A looks like:
variables:
MY_VAR: "set in the upstream job"
downstream_project_b:
stage: trigger_downstream
variables: {}
trigger: myprojects/project_b
In Project B I have:
variables:
MY_VAR: "set in the downstream job"
test:
stage: test
script:
- echo "$MY_VAR"
As you can see I have attempted to unset the global vars in Project A by using variables: {}
in the job, however $MY_VAR is still being passed to Project B and overriding $MY_VAR there. Is there any way I can unset it? Thanks in advance for any tips!
environment:
name: review/$PROJECT_NAME-$CI_COMMIT_REF_NAME
url: http://$CI_PROJECT_ID-$CI_ENVIRONMENT_SLUG.$KUBE_INGRESS_BASE_DOMAIN
on_stop: reviewApiStop
that works because Gitlab respects review/*
as part of AutoDevops and provides the magic sauce to let it work, but if I try the same with staging like so:
environment:
name: staging/$PROJECT_NAME
url: http://$CI_PROJECT_PATH_SLUG-staging-api.$KUBE_INGRESS_BASE_DOMAIN
It doesn't work cause it only works for staging
and not staging/*
CI_ENVIRONMENT_*
vars -.-
CI_ENVIRONMENT_NAME
to webpack during the auto devops build step. I'm using the automatically detected buildpack and I've set AUTO_DEVOPS_BUILD_IMAGE_FORWARDED_CI_VARIABLES
to CI_ENVIRONMENT_NAME,CI_COMMIT_SHA
at the organization level. However, when I log out process.env
, I can only see CI_COMMIT_SHA
present.
It looks like the environment name is set in the review step itself. What would folks recommend as the conventional way to use an environment config to point to other services from a static JS project? A dynamic environment such as an API can pull in environment variables or config files at run time, but I would think the static file project would need those configs built in, at build time.
I'm not afraid to write my own ci/cd scripts, but I'm curious if there is an auto devops convention here.
Hello,
I'm having trouble while trying to sign-in with my github account.
It says I need to confirm my email, so i click "resend confirmation email" but I got the following error:
Could not authenticate you from GitHub because "Csrf detected".
I've tried on firefox and chrome (with and without incognito mode) same things happens.
Any idea on how I can login ?
Hello, I'm trying to upload an image to a project - not as part of the repo, but so I can use it in a comment - is it possible to A) do that from a datauri, and B) use fetch or XHR to send it?
I've been beating my head against this for a few hours now. Every example I ever see is with cURL.
I can send the file, but I either get file is missing
or file is invalid
. I can successfully send via cURL. I've tried sending it with datauri URL escaped and also not. Am I missing something, or is this just not a possibility? I'd have to think there'd be a way, since the comment form turns pasted images into an uploaded file
ssh -Tvvv git@gitlab.com
OpenSSH_8.3p1, OpenSSL 1.1.1g FIPS 21 Apr 2020
debug1: Reading configuration data /home/user/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug3: /etc/ssh/ssh_config line 54: Including file /etc/ssh/ssh_config.d/50-redhat.conf depth 0
debug1: Reading configuration data /etc/ssh/ssh_config.d/50-redhat.conf
debug2: checking match for 'final all' host gitlab.com originally gitlab.com
debug3: /etc/ssh/ssh_config.d/50-redhat.conf line 3: not matched 'final'
debug2: match not found
debug3: /etc/ssh/ssh_config.d/50-redhat.conf line 5: Including file /etc/crypto-policies/back-ends/openssh.config depth 1 (parse only)
debug1: Reading configuration data /etc/crypto-policies/back-ends/openssh.config
debug3: gss kex names ok: [gss-curve25519-sha256-,gss-nistp256-sha256-,gss-group14-sha256-,gss-group16-sha512-,gss-gex-sha1-,gss-group14-sha1-,gss-group1-sha1-]
debug3: kex names ok: [curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1]
debug1: configuration requests final Match pass
debug1: re-parsing configuration
debug1: Reading configuration data /home/user/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug3: /etc/ssh/ssh_config line 54: Including file /etc/ssh/ssh_config.d/50-redhat.conf depth 0
debug1: Reading configuration data /etc/ssh/ssh_config.d/50-redhat.conf
debug2: checking match for 'final all' host gitlab.com originally gitlab.com
debug3: /etc/ssh/ssh_config.d/50-redhat.conf line 3: matched 'final'
debug2: match found
debug3: /etc/ssh/ssh_config.d/50-redhat.conf line 5: Including file /etc/crypto-policies/back-ends/openssh.config depth 1
debug1: Reading configuration data /etc/crypto-policies/back-ends/openssh.config
debug3: gss kex names ok: [gss-curve25519-sha256-,gss-nistp256-sha256-,gss-group14-sha256-,gss-group16-sha512-,gss-gex-sha1-,gss-group14-sha1-,gss-group1-sha1-]
debug3: kex names ok: [curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1]
debug2: resolving "gitlab.com" port 22
debug2: ssh_connect_direct
debug1: Connecting to gitlab.com [172.65.251.78] port 22.
debug1: Connection established.
debug1: identity file /home/user/.ssh/id_rsa type -1
debug1: identity file /home/user/.ssh/id_rsa-cert type -1
debug1: identity file /home/user/.ssh/id_dsa type -1
debug1: identity file /home/user/.ssh/id_dsa-cert type -1
debug1: identity file /home/user/.ssh/id_ecdsa type -1
debug1: identity file /home/user/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/user/.ssh/id_ecdsa_sk type -1
debug1: identity file /home/user/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /home/user/.ssh/id_ed25519 type -1
debug1: identity file /home/user/.ssh/id_ed25519-cert type -1
debug1: identity file /home/user/.ssh/id_ed25519_sk type -1
debug1: identity file /home/user/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /home/user/.ssh/id_xmss type -1
debug1: identity file /home/user/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.3
Seems to be working now
Hello, I'm having this problem with SSH where my SSH connection hangs after establishing connection and sending the SSH version its using, I searched the problem and it seems Gitlab's SSH server is not responding to my connection. I can do same things with HTTPS fine but SSH hangs and after very long period timeout.
namespace
slug in that URL or am I supposed to send a JSON payload with this API request?