Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

get failed: exit status 128 when using dev tag #89

Closed
echarrod opened this issue Mar 21, 2019 · 2 comments
Closed

get failed: exit status 128 when using dev tag #89

echarrod opened this issue Mar 21, 2019 · 2 comments

Comments

@echarrod
Copy link

I am getting get failed: exit status 128 when trying to run a pipeline, the relevant parts of which are here:

resource_types:
  - name: github-pr
    type: docker-image
    source: { repository: teliaoss/github-pr-resource, tag: "dev" }
    check_every: 720h

resources:
  - name: pr-src
    type: github-pr
    source:
      repository: myorg/myrepo
      access_token: ((my-access-token))

jobs:
  - name: pr-check
  plan:
      - get: pr-src
        trigger: true
        version: every

But the only output I'm getting is:

Initialized empty Git repository in /tmp/build/get/.git/
2019/03/21 12:14:37 get failed: exit status 128

I have made sure that the user associated with the access token has write permissions on the repo (not sure if this is actually needed)

I have looked through #35, which resulted in me attempting this with tags of: v0.6.0, v11.0.0 and dev

@echarrod echarrod changed the title get failed: exit status 128 when trying to run get failed: exit status 128 when using dev tag Mar 21, 2019
@itsdalmo
Copy link
Contributor

itsdalmo commented Apr 2, 2019

Hey and thanks for the issue! The exit status 128 suggests to me that it is an exit code from running git commands, but anything that can return an error usually adds some context via fmt.Errorf("something: %s", err). I.e., your error message should read something like get failed: <reason>: exit status 128 if you are running on the latest dev tag?

So I'm wondering, do you still have this issue or did Concourse suddenly discover a newer SHA for the resource? If so, are you hitting some kind of Docker hub cache? 😂

@echarrod
Copy link
Author

echarrod commented Apr 4, 2019

I think it was a problem with git configuration, as I can run it locally when not run though concourse. I'll close this, as it won't be a problem with github-pr-resource

@echarrod echarrod closed this as completed Apr 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants