You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Andrew Williams (JIRA)" <ji...@codehaus.org> on 2006/07/03 14:27:22 UTC
[jira] Created: (CONTINUUM-753) buildNumber is incorrectly reported
if a build fails after a build has suceedded
buildNumber is incorrectly reported if a build fails after a build has suceedded
--------------------------------------------------------------------------------
Key: CONTINUUM-753
URL: http://jira.codehaus.org/browse/CONTINUUM-753
Project: Continuum
Type: Bug
Components: XMLRPC Interface
Versions: 1.0.3
Environment: debian linux / ubuntu linux
Reporter: Andrew Williams
Priority: Minor
Fix For: 1.1
Attachments: buildnumber.patch
If buildNumber is 0 then it is blanked by the python.
Unfortunately the buildNumber is reported as the last successful, so we need to blank it if the build nwas not successful, not if the number is 0
Attatched patch on continuum-core-it does just that
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-753) buildNumber is incorrectly
reported if a build fails after a build has suceedded
Posted by "Andrew Williams (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-753?page=comments#action_71778 ]
Andrew Williams commented on CONTINUUM-753:
-------------------------------------------
any chance of getting this applied?
> buildNumber is incorrectly reported if a build fails after a build has suceedded
> --------------------------------------------------------------------------------
>
> Key: CONTINUUM-753
> URL: http://jira.codehaus.org/browse/CONTINUUM-753
> Project: Continuum
> Issue Type: Bug
> Components: XMLRPC Interface
> Affects Versions: 1.0.3
> Environment: debian linux / ubuntu linux
> Reporter: Andrew Williams
> Priority: Minor
> Fix For: 1.1
>
> Attachments: buildnumber.patch
>
>
> If buildNumber is 0 then it is blanked by the python.
> Unfortunately the buildNumber is reported as the last successful, so we need to blank it if the build nwas not successful, not if the number is 0
> Attatched patch on continuum-core-it does just that
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CONTINUUM-753) buildNumber is incorrectly reported
if a build fails after a build has suceedded
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-753?page=all ]
Jason van Zyl closed CONTINUUM-753.
-----------------------------------
Resolution: Fixed
Patch applied.
> buildNumber is incorrectly reported if a build fails after a build has suceedded
> --------------------------------------------------------------------------------
>
> Key: CONTINUUM-753
> URL: http://jira.codehaus.org/browse/CONTINUUM-753
> Project: Continuum
> Issue Type: Bug
> Components: XMLRPC Interface
> Affects Versions: 1.0.3
> Environment: debian linux / ubuntu linux
> Reporter: Andrew Williams
> Assigned To: Jason van Zyl
> Priority: Minor
> Fix For: 1.1
>
> Attachments: buildnumber.patch
>
>
> If buildNumber is 0 then it is blanked by the python.
> Unfortunately the buildNumber is reported as the last successful, so we need to blank it if the build nwas not successful, not if the number is 0
> Attatched patch on continuum-core-it does just that
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira