ASP.NET Core Build fails on build server because of project references
Hi all,
I'm just getting my feet with with CI/CD, we're using a self-hosted version of gitlab and I have a project that references class libraries (we use these libraries in many of our projects) that are internal to my organization.
What we've done in the past is just check out the code for the libraries to our local machines and include them as project references in the .csproj file, but I'm getting errors when trying to build using gitlab-runner because obviously, the code and binaries don't exist on the build server.
So, what do other people do to get around this problem? I had the idea that I could probably fix this by packaging our libraries and hosting them somewhere internally, then adding them as package references, but I don't know what the standard operating procedure is.
Google hasn't given me any answers that aren't buzzword-stuffed blog posts. I just want the damn thing to build without too much hassle.
Thanks in advance.
0 comments:
Post a Comment