Hi Major Shao(?),
we have the following pattern, to avoid this problem (and other problems).
* Each team has its own "teamA-integration-local" repo.
* There is a "libs-release-local" repo for chosen releases of shared libraries,
from all teams.
* Each team also has its own "teamA-integration" virtual repo, which includes
- libs-release-local
- teamA-integration-local
When a team as a version they're ready to share, they promote (copy/move) it
from their integration repo into libs-release-local. A copy/move is quick and
copies use very little extra disk space, so this is fairly easy. It can be
harder if you want to promote a library which has dependencies on several
versions of other libraries you've written, but you can write scripts to follow
the graph of dependencies to tell you what needs done and (if you have a Pro
license) do the promotion via the REST API. (If you don't have Pro, you can
still achieve the copy via the REST API by downloading the files and then
re-uploading them with checksums. Artifactory will spot that they are the same
as existing files, and not duplicate storage.)
In fact our system is more complex because we have several shared repos with
different permissions, different guarantees about what will/won't be deleted,
etc. But the idea is clear, I hope.
Another problem this solves is that, if all teams can see all versions of every
other team's libraries, teamA may end up making a release using a version of
some teamB library which teamB doesn't want to support, or hasn't fully tested,
etc. If release must be promoted to be shared, the owning team has control
over what is used by other teams.
Hope that helps,
Hugh Greene, Senior Software Developer
Toshiba Medical Visualization Systems Europe, Ltd
Bonnington Bond, 2 Anderson Place, Edinburgh EH6 5NP, UK
Tel + 44 (0)131 472 4792 / Fax + 44 (0) 131 472 4799
http://www.tmvse.com / mailto:[email protected]
DISCLAIMER
Unless indicated otherwise, the information contained in this message is
privileged and confidential, and is intended only for the use of the
addressee(s) named above and others who have been specifically authorized to
receive it. If you are not the intended recipient, you are hereby notified that
any dissemination, distribution or copying of this message and/or attachments
is strictly prohibited. The company accepts no liability for any damage caused
by any virus transmitted by this email. Furthermore, the company does not
warrant a proper and complete transmission of this information, nor does it
accept liability for any delays. If you have received this message in error,
please contact the sender and delete the message.
-----Original Message-----
From: cs [mailto:[email protected]]
Sent: 13 December 2014 05:02
To: [email protected]
Subject: [Artifactory-users] artifactory jars in different repo access issue
Here is the issue:
We have 2 big teams. We created them each as a separate repo.
Now when we have a jar in team2 (which is not in team1 repo), and dev team from
team 1 want to refer to that jar in team 2 repo; what we should do now?
We put the 2 repos to one virtual repo; now we got error when the jar not found
in team 1 repo and stop! (since the team 1 repo is the 1st in the list); ok if
we switch the order to make the team2 repo to be the 1st, this issue can be
resolved. But this is not a good solution, what if tomorrow we have another
different jar from team 1 and team2 want it.
Thanks
--
View this message in context:
http://forums.jfrog.org/artifactory-jars-in-different-repo-access-issue-tp7580094.html
Sent from the Artifactory - Users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate!
Instantly Supercharge Your Business Reports and Dashboards with Interactivity,
Sharing, Native Excel Exports, App Integration & more Get technology previously
reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
