ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Duffy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IVY-1429) ivy report should contain "branch" info
Date Wed, 17 Aug 2016 17:26:20 GMT

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

Chris Duffy commented on IVY-1429:
----------------------------------

"Me too" 

We're using a gitflow-esq branching model for all of our many components. Branch information
is a *need* for the integration team. I've got no way to give that to them in the report the
way things are now. 

> ivy report should contain "branch" info
> ---------------------------------------
>
>                 Key: IVY-1429
>                 URL: https://issues.apache.org/jira/browse/IVY-1429
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: unspecified, master
>         Environment: windows
>            Reporter: Greg Creager
>
> Currently the ivy report mechanism does not show 'branch' info, not having this vital
information makes it very hard to see what went into a build when you have the same version
on a different branch.
> example:
> compA branch="proto" revision="1.0"
> compA branch="integration" revision="1.0"
> Looking at the report for two products that use these components you get only the info
on revision and module, not the branch (the key factor).
> compA revision 1.0 (which 1.0 was pulled? proto or integration?
> Adding 'branch' to the report information just makes sense as it is a major factor when
deciding what to pull.



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

Mime
View raw message