You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@continuum.apache.org by "Brent N Atkinson (JIRA)" <ji...@apache.org> on 2015/05/03 15:38:05 UTC

[jira] [Updated] (CONTINUUM-2762) Computation of previous SCM changes sometimes includes entire history

     [ https://issues.apache.org/jira/browse/CONTINUUM-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brent N Atkinson updated CONTINUUM-2762:
----------------------------------------
    Attachment: CONTINUUM-2762-evidence.zip

I have attached an exported copy of the result page from continuum-ci.a.o for reference.

> 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)