![]() Notice that "JDICheckPrint" rev 26388 is present. "Figure_2.png" shows an excerpt of TeamCity's response to the following request: /httpAuth/app/nuget/feed/_Root/default/v2/FindPackagesById()?id='JDICheckPrint'."Figure_1.png" illustrates what revision 26388 looks like in TeamCity 2018.1.I tried querying the TeamCity NuGet feed directly using a web browser (taking everything but TeamCity out of the equation) and observed the same behavior.I also looked at teamcity-nuget.log and did NOT see "JDICM" rev 26388 getting indexed. I tried resetting the "buildsMetadata" cache.Here's what I tried - no affect on the problem: TeamCity will not list any "JDICM" package AFTER revision 26333. Please note that 26388 is not the only problematic revision."JDICheckPrint" revision 26388 was built by 2018.1 and IS visible in the NuGet feed and is visible in the TeamCity UI. "JDICheckPrint" revision 26333 was built by 2017.2.3 and is visible in the NuGet feed and in the TeamCity UI. One package unaffected by this problem is called "JDICheckPrint"."JDICM" revision 26388 was built by 2018.1 and is NOT visible in the NuGet feed but IS visible in the TeamCity UI. ![]() "JDICM" revision 26333 was built by 2017.2.3 and is visible in the NuGet feed and in the TeamCity UI. One package affected by this problem is called "JDICM".We did not observe this behavior on 2017.2.3. Since the upgrade, we've noticed that some packages built by 2018.1 are not visible in the internal TeamCity NuGet feed, while others are - even within the same build.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |