gobin | : ok_hand : tiny docker image generator for go bin | Continuous Deployment library

Just run

Found the issue. Turns out that my user didn't have write permissions on ~/Library/Caches/go-build/, so I ran the command below and it fixed the issue.

Running this command:

So I deleted github.com/golang/protobuf folder, and seems like google.golang.org/protobuf has started indexing, and everything just started working.

and thank-you for answering..

As I figure out earlier, it was a configuration mistake and, after having made some deep excavations on Go Terratest Azure module, I've found these lines that gives all the explanations :

• https://github.com/gruntwork-io/terratest/blob/master/modules/azure/authorizer.go#L11 leading to
• https://docs.microsoft.com/en-us/azure/developer/go/azure-sdk-authorization#use-environment-based-authentication

So I change my pipeline to this :

import cycle not allowed tells me you have circular references for imports. A imports B which imports A, or even A imports A.

I am guessing the error message comes from https://github.com/golang/go/blob/release-branch.go1.16/src/cmd/go/internal/modload/init.go#L207-L210

In the last line of your ~/.bashrc, you meant export GOPATH=$GOPATH:..., not export GOPATH=$gopath:.... Since $gopath is not set, your GOPATH would end up being :/home/santiagoquinteros/code. The above code doesn't like it.

As others said, you don't need to set GOROOT. With go1.16, the module mode is the default, so you probably don't need to set GOPATH but live with the default GOPATH which is $HOME/go.

Many things have changed recently. I recommend newer sets of materials like https://golang.org/doc/#getting-started, https://learn.go.dev, https://play-with-go.dev/ , ...

I like to share also the answer here for a template that builds a go modules package correctly. Maybe this is just for your inspiration what needs to be considered. It took me some time to get there.

The main pain point is that the the default template sets the GOPATH to the pipeline workingdirectory which is just wrong if you will download modules via go mod download into it. This would lead to inaccesible files in the next pipeline run, making the pipeline failing during repository checkout.

The following approach just sets GOPATH to the Agent.HomeDirectory which also makes downloaded modules available for subsequent pipeline runs.

Maybe it helps someone

You need to source and persist changes to your PATH env variable. If you using bash you can add next changes to .bashrc or .bash_profile (it's up to OS).