Supply build dependencies as artifacts built by another project?
I have a number of projects (not MSBUILD-based) which need to use a custom deployment library ( a mixture of PS scripts and a DLL) which is built in another project.
This might be the wrong way to approach this, but I was wondering if my "tool builder" project could push those as artifacts, which I could then install in the pre-build script of the dependent projects? As far as I can see artifact storage is private to the project, not shared across the account?
Or would it be better to push them to S3 or Azure blob and install from there?
Or even wrap in a private nuget?
Any guidance much appreciated...
Julian
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Feodor Fitsner on 05 Dec, 2014 05:37 PM
I would definitely go the NuGet way! You get all benefits with it like VS/cmd integration, versioning, updates.
2 Posted by julian.elve on 05 Dec, 2014 05:42 PM
Thanks - I think yuo are probably right!
I was getting hung up on the fact that the dependent projects are not msbuild, but of course I can do a nuget restore and it will pull the package in...
thanks Feodor
julian.elve closed this discussion on 05 Dec, 2014 05:42 PM.