search

SHyx0rmZ / bitbucket-build-status-resource

A Concourse resource for interacting with Bitbucket servers
Other
19 stars 14 forks source link

build-status check error 'file not found' #6

Open vorotech opened 6 years ago

vorotech commented 6 years ago

Hello, I'd like to report an issue which I continuously receive when restart local concourse set up with docker-compose. Unfortunately it is not recoverable (at least I didn't find the way), so the only workaround is to set-pipeline from scratch.

How it looks in Concourse 4.0.0 image

The error from the log

concourse-web_1     | {"timestamp":"1537084382.970843792","source":"atc","message":"atc.syncer.foundation-ci:radar.scan-resource.interval-runner.tick.failed-to-initialize-new-container","log_level":2,"data":{"error":"file not found","pipeline-scoped-name":"foundation-ci:resource:build-status","session":"39.1.14.1.2"}}

Tbh, I'm not 100% sure it is related to this resource, but among all resources in my pipeline this one is only not recovering, after the stale workers are being pruned.

vorotech commented 6 years ago

My resource config:

- name: build-status
  type: bitbucket-build-status
  source:
    driver: Bitbucket Cloud
    repository: my/repo
    client_id: ((bitbucket-app-oauth-key))
    client_secret: ((bitbucket-app-oauth-secret))
SatadruBhattacharjee commented 5 years ago

I also faced the exact same problem, only way solve is to set the pipeline from scratch.