Open GoogleCodeExporter opened 9 years ago
I have made a first implementation of the integration with the Claim plugin.
The grid displays the user who claimed the last failed build as well as the
provided reason. I also added an entry to the context menu to claim a build.
The issue is, when I post the "claim", even with HTTP authentication headers,
the Claim plugin does not read the username. Therefore, the claim is attached
to "anonymous", which isn't really helpful.
I will release this version. Then, perhaps we can report the issue to the
maintainers of the plugin.
Original comment by Alexis.S...@gmail.com
on 15 Jul 2010 at 12:23
Thanks for the quick turnaround Alexis. This feature adds a lot of value to
the tool. I'm seeing a small problem where the claim information stays visible
even after the job has been fixed but this is not critical.
Original comment by sean.hou...@gmail.com
on 15 Jul 2010 at 8:50
Yes, I was wondering about that too. I don't know how people use this plugin
and I saw that you could claim "old" builds, so I supposed this information
might be useful to someone.
If you have ideas or suggestions on how to make the integration better, don't
hesitate!
Thanks.
Original comment by Alexis.S...@gmail.com
on 16 Jul 2010 at 7:44
Option to sign up for a build from the tracker app is a useful feature.
Original comment by sriggu...@gmail.com
on 6 Aug 2010 at 1:09
Claiming a builds is very useful indeed. However, it would be really useful to
ensure that once a build goes green the claim reason gets cleared again to
accurately reflect the current status of the build. It's not very helpful to
see a green build and the claim reason says something like "Hugo broke it.
Looking into it."
Original comment by asga...@gmail.com
on 4 Nov 2010 at 6:15
Any more success regarding the claim functionality. As mentioned above I have
noticed that the user name is not getting resolved, asways shows up as
'Anonymous'.
Was wondering if this had been fixed or if anyone had expanded on the
funtionality of the claim feature.
Thanks,
Mark Q
Original comment by markquin...@gmail.com
on 27 Apr 2011 at 1:49
Original issue reported on code.google.com by
sean.hou...@gmail.com
on 29 Jun 2010 at 9:52