continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brent N Atkinson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CONTINUUM-2762) Computation of previous SCM changes sometimes includes entire history
Date Thu, 07 May 2015 17:00:00 GMT

    [ https://issues.apache.org/jira/browse/CONTINUUM-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533004#comment-14533004
] 

Brent N Atkinson commented on CONTINUUM-2762:
---------------------------------------------

While tracing through the code, I saw in section of code that was commented out a reference
to CONTINUUM-1871. The resemblance to this issue was striking.

> Computation of previous SCM changes sometimes includes entire history
> ---------------------------------------------------------------------
>
>                 Key: CONTINUUM-2762
>                 URL: https://issues.apache.org/jira/browse/CONTINUUM-2762
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.4.2
>            Reporter: Brent N Atkinson
>             Fix For: 1.5.0
>
>         Attachments: CONTINUUM-2762-evidence.zip
>
>
> As exhibited here:
> https://continuum-ci.apache.org/continuum/buildResult.action?buildId=39701&projectId=11
> There are times when Continuum incorrectly computes the changes since the prior build
to be the entire SCM history. In this case, a notification was also sent to all contributors
and contained the entire change log. It also worth noting that this also causes continuum
to store the information in the database, which can be considerable for projects with long
histories.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message