If you have different versions for each build, then you wouldn't have a problem with artifact collisions. However, it would be difficult to tell which version of the artifact came from which branch. A resolve on an ivy.xml with a dependency on a specific branch would not be locked down to just that branch, and could bring in versions that were not published on that branch (at least this is my understanding of how ivy works due to how the patterns work).
James Davis * QA Engineer II/Software Engineer Applied Technical Systems, Inc. * Information Engineering web: www.atsid.com * e-mail: [email protected] (p) 360.698.7100 x241 * (f) 360.698.7200 From: Eric Anderson [mailto:[email protected]] Sent: Wednesday, August 04, 2010 8:44 AM To: [email protected] Subject: Re: Any advice / documention on how to use branches in Ivy? We publish each artifact with a unique version per build so we wouldn't get colliding in that sense. So if Ivy checks the ivy.xml file to make sure its the right branch, then we would be okay? _________________________________________________________ Eric Anderson Palantir Technologies | Engineering Team Lead [email protected]<mailto:[email protected]> | 520.440.3773 _________________________________________________________ On Aug 4, 2010, at 8:26 AM, James Davis wrote: If you don't change the artifact pattern, your artifacts will collide with each other. One thing that we have done is make the branch optional in the pattern. An example of an optional branch identifier in the previous example would be [module]/([branch])/[revision]/[type]/[artifact](.[ext]). If there branch is specified, it will be used, if not it will be ignored in the pattern. James Davis * QA Engineer II/Software Engineer Applied Technical Systems, Inc. * Systems Division web: www.atsid.com<http://www.atsid.com> * e-mail: [email protected]<mailto:[email protected]> (p) 360.698.7100 x241 * (f) 360.698.7200 ________________________________________ From: Eric Anderson [[email protected]] Sent: Tuesday, August 03, 2010 3:18 PM To: [email protected]<mailto:[email protected]> Subject: Re: Any advice / documention on how to use branches in Ivy? Im really interested in using the branch attribute but not interested in changing my artifact pattern. What problems did you hit by not changing it? _________________________________________________________ Eric Anderson Palantir Technologies | Engineering Team Lead [email protected]<mailto:[email protected]> _________________________________________________________ On Jul 27, 2010, at 8:49 AM, Shawn Castrianni wrote: That is what I have done with my artifact pattern for the repository: [module]/[branch]/[revision]/[type]/[artifact](.[ext]) --- Shawn Castrianni -----Original Message----- From: Phillip Rhodes [mailto:[email protected]] Sent: Tuesday, July 27, 2010 10:46 AM To: [email protected]<mailto:[email protected]> Subject: Any advice / documention on how to use branches in Ivy? I see that the <info> and <dependency> elements have a "branch" attribute, and I can see that it sorta-kinda works the way I would naively expect... if I publish an artifact with branch set to "foo" and then try to resolve with a dependency of the same name, but with the branch set to "bar" then it doesn't match and the resolve fails. So far, so good. But my real question is how to best take advantage of this? If I just change the branch and publish, winding up with different revisions with different branches commingle together, things don't seem to work so smoothly. Is the idea that we are to make "branch" part of the repository pattern, so that artifacts are segregated on a per branch basis? Or something else? Any and all advice or pointers to documentation are much appreciated. Thanks, Phil ---------------------------------------------------------------------- This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution, or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message.
