gocd | Main repository for GoCD Continuous Delivery server | Continuous Deployment library

I've got a job that's failing and I think the problem is that I've misunderstood what the layout of the directory structure for the running job.

How can I see what's actually on disk so I can diagnose what's happening? Can I do it from the GoCD UI, or am I going to have to connect to the agent box and look at things that way?

In Jenkins, I'd just use the "workspace" link to eyeball the layout.

I've got a requirement to move from our existing terraform/gocd deployment structure for our lambdas to using codepipeline and cloudformation.

The main obstacle I've hit is cloudformation can't deploy a lambda with an existing name meaning I currently need to delete the existing lambda, for our test environment and lesser used lambdas not a huge problem but there are a few critical ones I'd rather have a cleaner way of moving across, is there a way to replace it in place?

I am wondering how I would configure a material in GoCD to trigger a build when a commit is made on the linked GitHub account.

I am using gocd for ci/cd. Result is tar archive. I need to copy resulting tar to GCE bucket.

I have gocd-agent docker image with included google sdk.

I know how to use gcloud with service account from local machine, but not from inside pod.

How to use service account assigned to pod with gcloud auth on pod?

Final goal is to use gsutil to copy above mentioned archive to bucket in same project.

I'm evaluating GoCD if we would be able to use it instead of Jenkins.

Is there any way how to create a parameterized pipeline like parametrized jobs in Jenkins?

In Jenkins, we're using these parameters in some jobs which are executed manually to configure "full-rebuild" of the project:

This bool value is passed as ENV variable to the job. I have found that GoCD has ENVs but I didn't find if there is a way how such ENV can be selected before manual executing.

Thanks

I have build a CI/CD with gitlab and docker. In my gitlab-ci.yml i just write commands to build and launch container to run test and that's it.

Now i m looking for a way to do the same thing with a GOCD ci/cd server. But the official documentation from gocd directly come to kubernetees or Docker in Docker or Docker outside Docker. I don't need this.

I have one GOCD-server and two GOCD-agents.

I want to build and run ONE container and perhaps deploy it. I m not able to find a simple tutorial to make a pipeline with three stages on GOCD:

1. build the image;
2. run container and test it;
3. deploy.

I have had a good amount of experience using GoCD. I previously used bash scripts to generate builds and was successful as well. For some reason, I have to use basic linux commands as individual tasks.

What I have done successfully:

1. Pipeline1 - > Stage1 > Job1 > Task 1 : git clone my-project

2. Pipeline1 - > Stage1 > Job1 > Task 2 : bash my-project/script.sh

What I want to achieve:

1. Pipeline1 - > Stage1 > Job1 > Task 1 : git clone my-project2

2. Pipeline1 - > Stage1 > Job1 > Task 2 : cd my-project2

3. Pipeline1 - > Stage1 > Job1 > Task 3 : build package (*tar.gz file)

4. Pipeline1 - > Stage1 > Job1 > Task 4 : mkdir newDirectory/

5. Pipeline1 - > Stage1 > Job1 > Task 5 : mv *tar.gz newDirectory/

Whilst I am able to achieve task 1,3,4; but for commands like cd, mv, I get error like check if agent can run cd, cannot find the file (when I run the mv cmd as it is in terminal it works!) respectively.

I came across GoCD Command Respository, but I am not sure how would it help me. Can anyone help if you faced the same situation earlier?

GoCD Version: 19.12.0

I'm trying to get environment variables defined in the Kubernetes deployment (system) in my GoCD YAML config in order to pass the GitHub authentication when pulling the resource. I've confirmed that I'm able to call the repository using a personal access token. (via https://[TOKEN]@github.com/[COMPANY]/[REPO].git)

This, of course, also works if I do the same for the actual YAML git field.

The GoCD secrets in K8s:

The GoCD deployment gets the secrets:

I've exec'd into the pod and echoed the variable, which returns the decoded value.

The YAML:

I'd half expect that to work, but it doesn't, it actually just gets $GITHUB_ACCESS_KEY as the value. The jobs defined in the pipeline stages are run using an elastic agent pod which also has the required secrets defined. I've tried a few

Setting env variables -

and then using that variable

Setting env variables and no quotes -

and then using that variable

No quotes - git: https://$GITHUB_ACCESS_KEY@github.com/[COMPANY]/[REPO].git

No quotes with brackets - git: https://${GITHUB_ACCESS_KEY}@github.com/[COMPANY]/[REPO].git

I've seen from some YAML documentation that it is recommended to use encrypted_password for the GitHub password, but this seems unnecessary since the GUI hides the token, and that its running in Kubernetes with secrets.