CI docker build failed - could not find project Gopkg.toml
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4k
- Forks
- 818
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 1
Description
the previues changes that made on the repo cause me the following issue, any suggestion how to fix it?
Step 4/14 : RUN git clone https://github.com/linkedin/Burrow.git $GOPATH/src/github.com/linkedin/Burrow/
---> Running in 0e37dde4917f
Cloning into '/go/src/github.com/linkedin/Burrow'...
---> 915585e71d47
Removing intermediate container 0e37dde4917f
Step 5/14 : RUN cd $GOPATH/src/github.com/linkedin/Burrow && dep ensure && go build -o /tmp/burrow .
---> Running in 5cb0437eb73d
**could not find project Gopkg.toml, use dep init to initiate a manifest**
The command '/bin/sh -c cd $GOPATH/src/github.com/linkedin/Burrow && dep ensure && go build -o /tmp/burrow .' returned a non-zero code: 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Docker build step that runs `dep ensure` in the cloned Burrow repository, then inspect the repository contents used by that command. Confirm the dependency setup works and that `go build -o /tmp/burrow .` completes successfully in the CI image.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100