search

Strider-CD / strider-bitbucket

Bitbucket git provider for Strider
17 stars 15 forks source link

strider successfully executed, but sent failed to bitbucket #37

Closed arch0x closed 4 years ago

arch0x commented 8 years ago

I'm sorry, asked once again.

The error on the pull request comment and also commits is error. This is build success of strider:

2016-06-28 10-27-40

but, it is faild on bitbucket: 2016-06-28 10-28-37

2016-06-28 10-28-09

knownasilya commented 8 years ago

If you click(or hover over it) on that failed link in bitbucket, do you get more details about what the issue is?

arch0x commented 8 years ago

@knownasilya The code is correct,strider build success, but strider send failed message to bitbucket when strider build completed. strider build success: _2016-06-29_17-02 on bitbucket: _2016-06-29_17-06

oliversalzburg commented 8 years ago

The status reporting isn't part of strider-bitbucket, is it? Seems like this would be an issue with strider-webhooks, isn't it?

knownasilya commented 8 years ago

See https://github.com/Strider-CD/strider-bitbucket/pull/27

@nomean42 any thoughts here?

nomean42 commented 8 years ago

I got fix for this, but i don't have enough time. The best way is make this fix after refactor

ramirost commented 8 years ago

We can reproduce this problem every time we run a job that does not execute the deploy phase.

I provided PR #41 fixing this on master.

I also attach a patch that can be applied on version 1.4.2 which is the one we are using right now

knownasilya commented 4 years ago

Thanks for closing, this was fixed.