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

Fix null/null repository URL #106

Merged
merged 1 commit into from
Feb 18, 2017
Merged

Conversation

arcadien
Copy link

On the latest version I started getting these errors in the logs and my jobs would trigger every minute and never flag the build as having run before.

POST state INPROGRESS to https://bitbucket.org/api/2.0/repositories/null/null/commit/b6f8169ce460/statuses/build with key 515f53a20bf37bd484f2be5cda6ab168cd194cee with response {"type": "error", "error": {"message": "Repository null/null not found"}}

Functionality in getOwnerName and getRepositoryName name changed from previous versions, moved to inside setFullName which is now doing the if on the wrong value. This causes null/null to be set as the owner name / repo name.

On the latest version I started getting these errors in the logs and my jobs would trigger every minute and never flag the build as having run before.

```
POST state INPROGRESS to https://bitbucket.org/api/2.0/repositories/null/null/commit/b6f8169ce460/statuses/build with key 515f53a20bf37bd484f2be5cda6ab168cd194cee with response {"type": "error", "error": {"message": "Repository null/null not found"}}
```

Functionality in `getOwnerName` and `getRepositoryName` name changed from previous versions, moved to inside `setFullName` which is now doing the `if` on the wrong value. This causes `null/null` to be set as the owner name / repo name.
@cocorossello
Copy link

Made a patch fixing the NPE problem as well
#107

@damovsky damovsky merged commit 325f247 into nishio-dens:master Feb 18, 2017
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

Successfully merging this pull request may close these issues.

3 participants