You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2016/09/20 23:37:20 UTC

[jira] [Created] (BIGTOP-2536) tarball.destination is ignored when set

Konstantin Boudnik created BIGTOP-2536:
------------------------------------------

             Summary: tarball.destination is ignored when set
                 Key: BIGTOP-2536
                 URL: https://issues.apache.org/jira/browse/BIGTOP-2536
             Project: Bigtop
          Issue Type: Bug
          Components: build
    Affects Versions: 1.1.0
            Reporter: Konstantin Boudnik
            Assignee: Konstantin Boudnik
             Fix For: 1.2.0


There seems to be a bug in the current logic, assigning the destination filename of  a component artifact. Current logic does this
{code}
        if (!config.bigtop.components[target].tarball.source.isEmpty())
          config.bigtop.components[target].downloaddst = DL_DIR + '/' + config.bigtop.components[target].tarball.source
{code}
which effectively ignores the destination filename. The potential issues could come if we build more than one component of a git repo (say GH), and all of those are downloading the master branch archive. In this case, the first component artifact will be stored as {{dl/master.zip}}, but the consequent component builds will simply skip the download part (as the {{master.zip}} is already present) and try to proceed with building a wrong source code.




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