2017-release | Old version of Learn Anything | Theme library

I'm using the Nuget package Nerdbank.GitVersioning to version my C# .Net DLL project and it is all working for local builds (tried within VS2017).

However when I try with the Gitlab runner to obtain the version number for use during my Nuget packaging steps none of the environment variables have been set regardless of what I have in my version.json file and/or using the nbgv cloud tool

My version.json file looks like this and is in the root of the repo;

Related to TFS 2017 release management artifact files from version control

I'm asking a new question because I believe I have an edge case the answers don't directly address and I don't want to derail that OP. Specifically, how do I allow an independent, offsite team building required supporting scripts in a separate TFS Team Project supply their scripts as an artifact in the Release definition of a separate TFS Team Project? The separate team projects are built by independent customers and we are not allowed to append content to their source control. Further, updates to the scripts must automatically spread to all Release definitions using them on the TFS.

We have about 40 team projects in TFS all running on different schedules. A separate operations team handles all build and release management tasks in TFS.

Because of the constant bouncing between team projects and because ops also wanted to use the version control and work item tracking features in TFS, we created a separate team project for them to store scripts, installers, and license files. These are referenced in other projects' RM tasks for automatic installation/execution. There is also a separate version control folder tree for tracking project specific scripts - like this:

• Common
• Applications
  • App1
  • App2 ...
  • App43

This makes it significantly easier for them to manage their scripts and associate them with work items themselves without having to shuffle across all the other team projects. The dev teams do not have access to the ops project.

However, when linking a version control artifact in RM from their project, it will only bind to the root and appears to copy the entirety of the version control structure to the agent, even though most of this content is not relevant to the app being deployed.

Is there a way to add specific, not all, folders from their project in version control as artifacts to a release definition in a separate project? We have our QA release start the process to production and it pulls in the artifacts from the ops project and the project being released. All subsequent releases reuse the artifacts that succeeded in the QA build instead of going back to the server for new versions of the artifacts.

Build definitions don't let us pick workspace paths outside of the team project so I don't see a way to pull in their scripts in a build step, either.

Is there a way to do this? How are other organizations handling this issue?