denied: requested access to the resource is denied
time="2020-07-24T12:58:24Z" level=fatal msg="exit status 1"
Build failing. Perhaps due to some sort of permissions error.
https://drone.autonomic.zone/autonomic-cooperative/autonomic.zone/106/1/2
```
denied: requested access to the resource is denied
time="2020-07-24T12:58:24Z" level=fatal msg="exit status 1"
```
Think that is related to the fact that the build is on another branch (policies branch from the fork in #34) and our .drone.yml still runs builds but doesn't expose the secrets necessary to push the container to docker hub. So, I guess the fix is just to disable builds in the .drone.yml configuration for now.
Think that is related to the fact that the build is on another branch (`policies` branch from the fork in https://git.autonomic.zone/autonomic-cooperative/autonomic.zone/pulls/34) and our [.drone.yml](https://git.autonomic.zone/autonomic-cooperative/autonomic.zone/src/branch/master/.drone.yml) still runs builds but doesn't expose the secrets necessary to push the container to docker hub. So, I guess the fix is just to disable builds in the `.drone.yml` configuration for now.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Build failing. Perhaps due to some sort of permissions error.
https://drone.autonomic.zone/autonomic-cooperative/autonomic.zone/106/1/2
Think that is related to the fact that the build is on another branch (
policiesbranch from the fork in #34) and our .drone.yml still runs builds but doesn't expose the secrets necessary to push the container to docker hub. So, I guess the fix is just to disable builds in the.drone.ymlconfiguration for now.Fixed in
2ae36bade9I think!