Posts made by jrasch

For completeness, I will also add that (without any connectors), the package returned by this Native API call will be the same:

https://<proget-server>/api/json/NuGetPackagesV2_GetLatest?key=<api-key>&Feed_Id=<feed-id>&PackageIds_Psv=<packages>

Psv stands for "pipe-separated values", and if that argument is omitted, the absolute latest versions of all packages are returned. An example value for <packages> would be Inedo.BuildMaster.SDK or Inedo.BuildMaster.SDK|Inedo.ProGet.SDK

That being said, the NuGet API endpoint is still the recommended one to use if possible :)

Hi Richard,

ProGet does not currently implement v3. The V2 designation for the tables was simply the 2nd implementation of NuGet feeds that replaced the quirks feeds.

If you want to get the latest version using the NuGet v2 API, use this URL format:

https://<proget-server>/nuget/<feed-name>/FindPackagesById()?id=<package-name>&$filter=IsAbsoluteLatestVersion&$format=json

The $format=json is specific to ProGet and may be omitted if you prefer NuGet v2's traditional XML response.

Hope this helps,
-John

Hi Philippe,

Apparently 6.2 has an unrelated issue that prevents infrastructure sync which I have logged here: https://inedo.myjetbrains.com/youtrack/issue/BM-3542

Are you seeing the error "Invalid resource type specified for infrastructure sync." in the diagnostic center by chance? If so, the above issue should resolve it in the next 6.2 maintenance release due out next Friday.

Once I fixed that, the infrastructure was imported as per this log:

DEBUG: 2020-02-19 16:02:52Z - Starting infrastructure import...
INFO : 2020-02-19 16:02:52Z - Mirroring enabled; infrastructure will be deleted if it is not defined in imported configuration.
DEBUG: 2020-02-19 16:02:52Z - Variables will be imported.
INFO : 2020-02-19 16:02:52Z - Creating role BASELINE-CONFIG-SERVEURS...
INFO : 2020-02-19 16:02:52Z - Creating variable Description=[hidden]...
INFO : 2020-02-19 16:02:52Z - Creating role AD-Controleurs...
INFO : 2020-02-19 16:02:52Z - Creating variable ModulesBaselineAD=[
{"Nom":"DFSDsc","Version":"4.3.0"},
{"Nom":"xSmbShare","Version":"2.2.0"}, {"Nom":"xDNSServer","Version":"1.12.0.0"}
]

...
INFO : 2020-02-19 16:02:52Z - Creating role PLATEFORMES...
INFO : 2020-02-19 16:02:52Z - Creating role PLATEFORMES-MAESTRO...
INFO : 2020-02-19 16:02:52Z - Creating role PLATEFORMES-MAESTRO-PDQ...
INFO : 2020-02-19 16:02:52Z - Creating variable ModulesPlateformesMaestroPDQ=[ {"Nom":"VMware.PowerCLI","Version":"11.2.0.12780525"},{"Nom":"DSI","Version":"1.0.0"}  ]	...
INFO : 2020-02-19 16:02:52Z - Creating role AD-PKI...
INFO : 2020-02-19 16:02:52Z - Creating role BASELINE-100-IIS...
INFO : 2020-02-19 16:02:52Z - Creating variable SitesIIS=%(GLPI-INTEGRATION: %(Bindings: @(%(IPAddress: *, Port: 8000, HostName: *, Protocol: http))), GLPI-EXPLOITATION: %(Bindings: @(%(IPAddress: *, Port: 8001, HostName: *, Protocol: http))), KANBOARD-INTEGRATION: %(Bindings: @(%(IPAddress: *, Port: 8003, HostName: *, Protocol: http))), ANNUAIRE-EXPLOITATION: %(Bindings: @(%(IPAddress: *, Port: 80, HostName: annuaire.ocapiat.fr, Protocol: http))), ANNUAIRE-INTEGRATION: %(Bindings: @(%(IPAddress: *, Port: 80, HostName: annuaire-dev.ocapiat.fr, Protocol: http))))...
INFO : 2020-02-19 16:02:52Z - Creating variable WindowsFeature-IIS=@(Web-Server, Web-WebServer, Web-Common-Http, Web-Static-Content, Web-Default-Doc, Web-Http-Errors, Web-Dir-Browsing, Web-Http-Redirect, Web-Health, Web-Http-Logging, Web-Request-Monitor, Web-Log-Libraries, Web-Performance, Web-Stat-Compression, Web-Dyn-Compression, Web-Security, Web-Filtering, Web-Basic-Auth, Web-Windows-Auth, Web-App-Dev, Web-CGI, Web-ISAPI-Ext, Web-Includes, Web-ISAPI-Filter, Web-Mgmt-Tools, Web-Mgmt-Compat, Web-Metabase, Web-WMI, Web-Lgcy-Scripting, Web-Scripting-Tools, Web-Mgmt-Service)...
INFO : 2020-02-19 16:02:52Z - Creating role PLATEFORMES-MAESTRO-DFS...
INFO : 2020-02-19 16:02:52Z - Creating role BASELINE-FICHIERS...
INFO : 2020-02-19 16:02:52Z - Creating variable LecteurDFS=D:...
INFO : 2020-02-19 16:02:52Z - Creating variable ModulesBaselineFichiers=[ {"Nom":"DFSDsc","Version":"4.3.0"},
{"Nom":"xSmbShare","Version":"2.2.0"} ]...
INFO : 2020-02-19 16:02:52Z - Creating variable WindowsFeature-Fichiers=@(FS-Resource-Manager, FS-DFS-Namespace, FS-DFS-Replication, FS-DATA-Deduplication, FS-VSS-Agent)...
INFO : 2020-02-19 16:02:52Z - Creating role PLATEFORMES-EXCHANGE...
INFO : 2020-02-19 16:02:52Z - Creating role BASELINE...
INFO : 2020-02-19 16:02:52Z - Creating variable ModulesBaseline=[{"Nom":"PSDscResources","Version":"2.10.0.0"} ,
 {"Nom":"Carbon","Version":"2.9.0"},
 {"Nom":"StorageDSC","Version":"4.6.0.0"},
{"Nom":"xActiveDirectory","Version":"3.0.0.0"},
{"Nom":"NetworkingDSC","Version":"7.1.0.0"}
]...
INFO : 2020-02-19 16:02:52Z - Creating variable WindowsFeaturesBaseline=@(RSAT-AD-PowerShell, RSAT-DNS-Server)...
INFO : 2020-02-19 16:02:52Z - Creating role PLATEFORMES-MAESTRO-GLPI...
INFO : 2020-02-19 16:02:52Z - Creating role BASELINE-010-IIS-MODULES...
INFO : 2020-02-19 16:02:52Z - Creating variable ModulesBaselineIIS=[
 {"Nom":"xWebAdministration","Version":"2.5.0.0"},
 {"Nom":"PSDscResources","Version":"2.10.0.0"}
]...
INFO : 2020-02-19 16:02:52Z - Creating variable SourceNetFx35=\\ocapiat.fr\MAESTRO\Logiciels\Entreprise\Microsoft\.Net Framework\3.5...
INFO : 2020-02-19 16:02:52Z - Creating role BASELINE-110-IIS-PHP...
INFO : 2020-02-19 16:02:52Z - Creating variable ModulesPHP=[ {"Nom":"PhpManager","Version":"1.17.2.210"} ]...
INFO : 2020-02-19 16:02:52Z - Creating variable PHPPAthRoot=D:\PHP...
INFO : 2020-02-19 16:02:52Z - Creating variable PHPVersions=@(7.3.4)...
INFO : 2020-02-19 16:02:52Z - Creating role PLATEFORMES-METAANNUAIRE...
INFO : 2020-02-19 16:02:52Z - Creating variable MetaAnnuaire=%(EXP: %(InstanceDescription: Exploitation, LocalLDAPPortToListenOn: 50000, LocalSSLPortToListenOn: 50100))...
INFO : 2020-02-19 16:02:52Z - Creating variable NomDomaine=ldap...
INFO : 2020-02-19 16:02:52Z - Creating variable WindowsFeature-ADLDS=@(ADLDS)...
INFO : 2020-02-19 16:02:52Z - Creating role PLATEFORMES-WAC...
INFO : 2020-02-19 16:02:52Z - Creating variable CName=wac.ocapiat.fr...
INFO : 2020-02-19 16:02:52Z - Creating variable WindowsFeaturesWAC=@(RSAT-DNS-Server)...
INFO : 2020-02-19 16:02:52Z - Creating role PLATEFORMES-MAESTRO-KANBOARD...
INFO : 2020-02-19 16:02:52Z - Creating role PLATEFORMES-MAESTRO-LANSWEEPER...
INFO : 2020-02-19 16:02:52Z - Creating role PLATEFORMES-MAESTRO-MDT...
INFO : 2020-02-19 16:02:52Z - Creating role PLATEFORMES-MAESTRO-IIS...
INFO : 2020-02-19 16:02:52Z - Creating role PLATEFORMES-MAESTRO-SNIPEIT...
INFO : 2020-02-19 16:02:52Z - Creating role PLATEFORMES-RH...
INFO : 2020-02-19 16:02:52Z - Creating role PLATEFORMES-RH-ANNUAIRE...
INFO : 2020-02-19 16:02:52Z - Creating role BASELINE-SQL...
INFO : 2020-02-19 16:02:52Z - Creating variable ModulesBaselineSQL=[
{"Nom":"dbatools","Version":"1.0.38"},{"Nom":"SQLServerDSC","Version":"13.1.0.0"},
{"Nom":"SQLServer","Version":"21.1.18147"}
]...
INFO : 2020-02-19 16:02:52Z - Creating variable SQL-Maintenance-Checksum=-2101817452...
INFO : 2020-02-19 16:02:52Z - Creating variable SQL-Maintenance-Get-Script=Get-InstanceName.sql...
INFO : 2020-02-19 16:02:52Z - Creating variable SQL-Maintenance-Set-Script=MaintenanceSolution.sql...
INFO : 2020-02-19 16:02:52Z - Creating variable SQL-Maintenance-Test-Script=ObjectChecksum.sql...
INFO : 2020-02-19 16:02:52Z - Creating variable SQL-Scripts-Folder=c:\dsi\sql...
INFO : 2020-02-19 16:02:52Z - Creating variable SQLInstances=@()...
INFO : 2020-02-19 16:02:52Z - Creating variable SQLInstancesConfig=%(MAESTRODEV: %(RAM: 2048, StaticPort: 1450), TEST: %(RAM: 2048, StaticPort: 1451), PAIE: %(RAM: 4096, StaticPort: 1450), MAESTROPRD: %(RAM: 2048, StaticPort: 1450), LANSWEEPER: %(RAM: 4096, StaticPort: 1451), TESTPUB: %(RAM: 4096, StaticPort: 1451), TESTABO: %(RAM: 4096, StaticPort: 1452))...
INFO : 2020-02-19 16:02:52Z - Creating variable WindowsFeaturesBaselineSQL=@(NET-Framework-45-Core)...
INFO : 2020-02-19 16:02:52Z - Creating role PLATEFORMES-WORKSPACE...
INFO : 2020-02-19 16:02:52Z - Creating role PLATEFORMES-MAESTRO-GIT...
INFO : 2020-02-19 16:02:52Z - Creating role PLATEFORMES-RDS...
INFO : 2020-02-19 16:02:52Z - Creating role LINUX-BASELINE...
INFO : 2020-02-19 16:02:52Z - Creating variable APT-MARIADB=mariadb-server mariadb-client...
INFO : 2020-02-19 16:02:52Z - Creating role LINUX-HAPROXY...
INFO : 2020-02-19 16:02:52Z - Creating variable APT-Modules=haproxy keepalived git wget...
INFO : 2020-02-19 16:02:52Z - Creating role PLATEFORMES-WORDPRESS-HAPROXI...
INFO : 2020-02-19 16:02:52Z - Creating role LINUX-MARIADB...
INFO : 2020-02-19 16:02:52Z - Creating variable APT-MARIADB=mariadb-server mariadb-client...
INFO : 2020-02-19 16:02:52Z - Creating role PLATEFORMES-WORDPRESS...
INFO : 2020-02-19 16:02:52Z - Creating variable APT-WP-PHP=php7.2 php7.2-cli php7.2-mysql php7.2-json php7.2-opcache php7.2-mbstring php7.2-xml php7.2-gd php7.2-curl...
INFO : 2020-02-19 16:02:52Z - Creating role PLATEFORMES-MAESTRO-SQL...
INFO : 2020-02-19 16:02:52Z - Creating role PLATEFORMES-PAIE...
INFO : 2020-02-19 16:02:53Z - Creating role PLATEFORMES-WORKFOLDER...
INFO : 2020-02-19 16:02:53Z - Creating variable ModulesWorkFolders=[{"Nom":"xDNSServer","Version":"1.16.0.0"},{"Nom":"CertificateDsc","Version":"4.7.0.0"}]...
INFO : 2020-02-19 16:02:53Z - Creating variable WindowsFeature-WorkFolders=@(FS-SyncShareService, Web-WHC, FS-Data-Deduplication)...
INFO : 2020-02-19 16:02:53Z - Creating variable WorkFolder-DossierBase=D:\WKFLD...
INFO : 2020-02-19 16:02:53Z - Creating role PLATEFORMES-WORKFOLDER-SETUP...
INFO : 2020-02-19 16:02:53Z - Creating role PLATEFORMES-SOR-HAPROXI...
INFO : 2020-02-19 16:02:53Z - Creating environment DEVELOPPEMENT...
INFO : 2020-02-19 16:02:53Z - Updating environment INTEGRATION (id=1)...
INFO : 2020-02-19 16:02:53Z - Creating variable RootDrive=D:\...
INFO : 2020-02-19 16:02:53Z - Creating variable RootEnv=INT...
INFO : 2020-02-19 16:02:53Z - Updating environment PRODUCTION (id=3)...
INFO : 2020-02-19 16:02:53Z - Creating variable RootDrive=D:\...
INFO : 2020-02-19 16:02:53Z - Creating variable RootEnv=DEV...
INFO : 2020-02-19 16:02:53Z - Deleting environment Testing...
INFO : 2020-02-19 16:02:53Z - Creating server VM121007...
INFO : 2020-02-19 16:02:53Z - Creating server VM121004...
INFO : 2020-02-19 16:02:53Z - Creating server VM121010...
INFO : 2020-02-19 16:02:53Z - Creating server VM121001...
INFO : 2020-02-19 16:02:53Z - Creating server VM121002...
INFO : 2020-02-19 16:02:53Z - Creating server VM120001...
INFO : 2020-02-19 16:02:53Z - Creating server VM121009...
INFO : 2020-02-19 16:02:53Z - Creating server VM121012...
INFO : 2020-02-19 16:02:53Z - Creating server VM121011...
INFO : 2020-02-19 16:02:53Z - Creating server VM121008...
INFO : 2020-02-19 16:02:53Z - Creating server VM121003...
INFO : 2020-02-19 16:02:53Z - Creating server VM121006...
INFO : 2020-02-19 16:02:53Z - Creating server VM121005...
INFO : 2020-02-19 16:02:53Z - Creating server VM120002...
INFO : 2020-02-19 16:02:53Z - Creating server VM121013...
INFO : 2020-02-19 16:02:53Z - Creating variable PHPVersion=7.3.4...
INFO : 2020-02-19 16:02:53Z - Creating server VM121014...
INFO : 2020-02-19 16:02:53Z - Creating server VM120003...
INFO : 2020-02-19 16:02:53Z - Creating server VM120004...
INFO : 2020-02-19 16:02:53Z - Creating server VM120005...
INFO : 2020-02-19 16:02:53Z - Creating server VM121016...
INFO : 2020-02-19 16:02:53Z - Creating variable SQLInstances=@(TEST)...
INFO : 2020-02-19 16:02:53Z - Creating server VM121015...
INFO : 2020-02-19 16:02:53Z - Creating server VM121018...
INFO : 2020-02-19 16:02:53Z - Creating server VM121017...
INFO : 2020-02-19 16:02:53Z - Creating server VM121019...
INFO : 2020-02-19 16:02:53Z - Creating server VM121023...
INFO : 2020-02-19 16:02:53Z - Creating server VM121024...
INFO : 2020-02-19 16:02:53Z - Creating server VM121025...
INFO : 2020-02-19 16:02:53Z - Creating variable SQLInstances=@(MAESTROPRD,LANSWEEPER)...
INFO : 2020-02-19 16:02:53Z - Creating variable SQLSourcePath=\\ocapiat.fr\maestro\Logiciels\Entreprise\Microsoft\SQL Server\Standard\2016-FR-SP2...
INFO : 2020-02-19 16:02:53Z - Creating server VM121026...
INFO : 2020-02-19 16:02:53Z - Creating server VM121028...
INFO : 2020-02-19 16:02:53Z - Creating server VM121030...
INFO : 2020-02-19 16:02:53Z - Creating server VM121031...
INFO : 2020-02-19 16:02:53Z - Creating server VM121032...
INFO : 2020-02-19 16:02:53Z - Creating server VM120006...
INFO : 2020-02-19 16:02:53Z - Creating server VM121036...
INFO : 2020-02-19 16:02:53Z - Creating server VM121034...
INFO : 2020-02-19 16:02:53Z - Creating server VM121037...
INFO : 2020-02-19 16:02:53Z - Creating server VM121035...
INFO : 2020-02-19 16:02:53Z - Creating server VM111001...
INFO : 2020-02-19 16:02:53Z - Creating variable WPSITES=@(wpliv)...
INFO : 2020-02-19 16:02:53Z - Creating server VM121029...
INFO : 2020-02-19 16:02:53Z - Creating variable SQLInstances=@(PAIE)...
INFO : 2020-02-19 16:02:53Z - Creating variable SQLSourcePath=\\ocapiat.fr\maestro\Logiciels\Entreprise\Microsoft\SQL Server\Standard\2016-FR-SP2...
INFO : 2020-02-19 16:02:53Z - Creating server VM121038...
INFO : 2020-02-19 16:02:53Z - Creating server VM121040...
INFO : 2020-02-19 16:02:53Z - Creating server VM121039...
INFO : 2020-02-19 16:02:53Z - Creating server VM121027...
INFO : 2020-02-19 16:02:53Z - Creating server VM111002...
INFO : 2020-02-19 16:02:53Z - Creating server VM111003...
INFO : 2020-02-19 16:02:53Z - Creating server VM111005...
INFO : 2020-02-19 16:02:53Z - Creating variable WPSITES=@(wpsbx)...
INFO : 2020-02-19 16:02:53Z - Creating server VM121041...
INFO : 2020-02-19 16:02:53Z - Creating server VM120009...
INFO : 2020-02-19 16:02:53Z - Creating variable SQLInstances=@(TESTABO)...
INFO : 2020-02-19 16:02:53Z - Creating server VM120008...
INFO : 2020-02-19 16:02:53Z - Creating variable SQLInstances=@(TESTPUB)...
INFO : 2020-02-19 16:02:53Z - Creating server VM111007...
INFO : 2020-02-19 16:02:53Z - Creating variable WPSITES=@(WPDEV)...
INFO : 2020-02-19 16:02:53Z - Deleting server localhost...
DEBUG: 2020-02-19 16:02:53Z - Committing transaction...
INFO : 2020-02-19 16:02:53Z - Import complete.

Hope this helps,
-John

Hello,

@mhull_0872 your timing is perfect. While currently it requires custom headers, we are implementing a simple REST API right now that will be allow you to add custom deployment records. Here is the associated issue: https://inedo.myjetbrains.com/youtrack/issue/PG-1666

It's planned to be included in the 5.2.26 release due out next Friday.

Hope this helps,
-John

Hi Phillipe,

The bug should have been resolved in both lines (it was fixed in 6.1 but merged into 6.2). I had originally used the infrastructure you sent in testing it, I will try again tomorrow or Wednesday in 2 clean instances to see what I find and report back.

Thanks,
-John

Hi Ali,

By default, an artifact retention policy operates on artifacts alone and does not consider builds/releases/etc.

There is no current way to say "500MB of artifacts per release", however, you can combine 2 retention policies that should be close to what you want:

• Build retention policy:
  • Only purge builds in deployed releases
  • Only purge rejected builds
  • Keep last (whatever you want)
• Artifact retention policy:
  • Only purge artifacts in deployed releases
  • Only purge artifacts in rejected builds
  • Purge orphaned artifacts

The key is "purge orphaned artifacts" which will only delete artifacts after its corresponding build is deleted. This allows you to provide the necessary granularity on the builds themselves, and let the artifact policy come in after and clean up the artifacts that no longer have an existing build. This can be extended to releases in a way, since any releases that get deleted will also have all their builds deleted.

Hope this helps,
-John

Hi Philipe,

Thank you for the export. Using it to perform an import, I was able to determine the root cause for the "item with the same key has already been added" error and have submitted a fix for it.

If you would like a pre-release version with the fix included let me know and I'll make one available, otherwise it will be included in 6.1.26 due out next Friday.

Thanks,
-John

Hi Philipe,

I am getting back to investigating this issue now. Are you able to send over an example export (Admin > Export Configuration) that exhibits the error? Please make sure to sanitize any agent connection information from the export :)

Thanks,
-John

Hi Philip,

The next TFS extension v1.4.0 now has a TFVC monitor included. It's a little rough around the edges i.e. it monitors separate paths instead of branches for the time being.

Let me know if you run into any issues with it.

Thanks,
-John

Hi Philip,

Sorry for the delay, most (i.e. all) of our dev resources were assigned to the BuildMaster v6.2 release this week. Now that it's out, I have been assigned the implementation for this, scheduled for Jan 31, however I expect to get to it a lot sooner than that.

Thank you for your patience,
-John

Hi Philippe,

I will look into this again as soon as I can, unfortunately all our resources at the moment are dedicated to getting BuildMaster v6.2 out the door.

Thanks,
-John

No problem! Barring any unforeseen issues, we expect to have this available no later than next Friday.

Hi Philip,

At this time, we don't have a specific TFVC Repository Monitor but I have created a GitHub issue to add one: https://github.com/Inedo/inedox-tfs/issues/30

Hope this helps,
-John

You'll need a separate policy for Artifacts since the policy for Releases will orphan them (i.e. remove them from the DB) but not delete them from disk.

Hi Joseph,

You are correct. Separate rules consider their target items to delete independently.

Thanks,
-John

Hi Philippe,

The logs of the actual sync are actually on the executions page (in your case, https://buildmaster.ocapiat.fr/executions?Mode=M)

I suspect you will see an error like:

627`14`1`ServerRoles_CreateOrUpdateServerRole`19`Violation of UNIQUE KEY constraint 'UQ__ServerRoles__ServerRole_Name'

If you do, that's why it doesn't work. I have fixed this specific issue internally (and was then able to sync) and the fix will be included with the next maintenance release. If this is not the error you see, let me know and I will continue to investigate.

Thanks,
-John

Thanks for the heads up... so much for the invite link that "doesn't expire" :)

Anyway, here's a new one: https://join.slack.com/t/inedo/shared_invite/enQtNTU3NzQwMzM4NDM3LTdkZDczYTJkNmY0NjdiNDEyNWIxZDRmMTBiYzdhYmQ3M2NkNDkwZTYxODA2NzRlYmY1OWRlZjE1MDFiMjY3ODk

I think by default all you need is to set the host to "localhost" and the port to "8888".

If that doesn't work, check the Tools > Options > Connections tab within Fiddler for the port number.

Hi Philipe,

Thanks for the report, I've added an issue to fix this: https://inedo.myjetbrains.com/youtrack/issue/OT-345

It should be included in Friday's release, but it may get delayed to next week because there aren't any other issues scheduled for it yet :)

Thanks,
-John

Hello,

There was a regression for the PowerShell agents that was introduced in the previous version of Otter, and not caught until recently, that has been fixed in the release we just did.

Let me know if this resolves your issue!

Thanks,
-John

Hello,

We just did a massive docs migration, and our marketing team is monitoring for these missing pages.

Here is the correct page: https://docs.inedo.com/docs/inedoagent/installation/installation-guide

Hope this helps,
-John

@ssuenaga_1020 said in PyPI upload endpoint:

curl https://{proget}/pypi/Python/upload --user <user>:<password> --upload-file <file-path>

Sorry about that, it appears the actual upload URL is:

curl https://{proget}/pypi/Python/upload/<packageName-version.tar.gz> --user <user>:<password> --upload-file <file-path>

I will update the documentation to reflect this on both the website and in the software.

Thanks,
-John

I fixed this incidentally in this commit: https://github.com/Inedo/inedox-git/commit/325562db2ea5996a1dc559f5997dca49cc9452df

The fix is available as of v1.3.1 of the Git(Hub|Lab)? extensions :)

Hi Mark,

This bugfix will be included in v6.1.11 due out this Friday. Thank you for your patience.

Thanks,
-John

Hi David,

It's a bit verbose, but you should be able to get away with something like this:

##AH:UseTextMode
module CheckBuildCriteria<out $validBuild>
{
    set $validBuild = false;
}

call CheckBuildCriteria
(
    validBuild => $IsValidBuild
);

try
{
    if !$IsValidBuild
    {
        Log-Error Build criteria is invalid...;
        throw;
    }
    
    # normal plan operations go here...
}
catch
{
    if !$IsValidBuild
    {
        force normal;
    }
}

Aha, it will also be included in BuildMaster... not sure why I got stuck on Otter. I guess it was on my mind because we just had a maintenance release today :)

This feature is also scheduled for BuildMaster v6.1.10 on July 19

Hi Philippe,

I know it's been a while since this question was posted, but just wanted to let you know that we will soon be supporting the behavior in Otter of allowing multiple resource credentials of the same name that differ only by environment.

We are still in the process of determining the UI (e.g. allowing selection of multiple environments at once) but at least the core functionality you described will work.

This is being targeted for Otter v2.2.5 due out July 26.

Hope this helps,
-John

Hi David,

You can view the results of a monitor that triggers a plan in the Admin > Executions page, filtering by "Build Trigger".

You can also add some hack debugging to the plan that logs the built-in monitor variables to a file so you can see if it's triggering.

If it's still not triggering, try configuring the monitor to a public instance of something on GitHub like https://github.com/Inedo/git-test.git to see if that works since GitHub supports the SVN protocols as well.

Hope this helps,
-John

Resolved via ticket:

If you want to call PowerShell functions, you need to wrap them in a PowerShell Module, then import that module in your PowerShell script asset. That's the only way I can think of that this will consistently work. I've implemented something like this before:

set $ModuleName = Hello-World;
Get-Asset $ModuleName.ps1
(
    Type: Script    
);
set $ModulePath = $PathCombine($WorkingDirectory, $ModuleName.ps1);

PSEnsure
(
    Key: Test,
    Value: True,
    Collect: "$false",
    Configure: >>
    Import-Module -Name "$ModulePath" -Verbose
    
    Hello-World "Testing 123"
    >>
);

which just writes a Hello-World script out and imports it as a PS module. You could probably figure out a better way than this e.g. creating a "PsModule" role that ensures the module is installed on any servers you're working with, then you'd only need the Import-Module command in your scripts to gain access to all your shared functions.

Apologies, I had seen the StackOverflow post first, so I responded here: https://stackoverflow.com/questions/56338757/proget-symbols-and-source-server-download-pdb-correctly-but-source-not-found/56397293#56397293

Typically this is caused by a Windows extension that hasn't been updated to the latest version following a BuildMaster v6 upgrade.

In what context would this protocol be used? My understanding is that BITS is used for background/asynchronous transfers, and in the common Otter use-case, the package needs to be available on the server in order to progress through a configuration plan, therefore the only benefit I can see is the network throttling.

FYI this has been added (in Subversion extension v1.1.0) and the available variables are documented here: https://inedo.com/support/documentation/buildmaster/builds/continuous-integration/source-control/svn#automatic-builds-continuous-integration-with-subversion

Hi Patrick,

As of ProGet v5.2, we have a new Management API that makes this much simpler.

I've added a Configure Retention example to the Update Entity docs here that shows how to add retention rules: https://inedo.com/support/documentation/proget/reference/api/feed-management#update

This was an oversight, we'll add this ASAP. The tracking issue is: https://github.com/Inedo/inedox-subversion/issues/3

I actually added this but it wasn't released as part of the beta; it will be an option in the Status filter e.g. "Agent error", "Collect/remediate error", and "Any error"

I'm not sure why that response says that (I believe it was written when ProGet was still in Beta), but it is in fact inaccurate.

The rules for closed testing or DR instances is that a separate license is required as per the licensing agreement: https://inedo.com/proget/license-agreement

In order to clarify this with some examples, I've added the following documentation that will release when 5.2 goes live:

https://github.com/Inedo/inedo-docs/blob/proget-5.2/ProGet/administration/license.md#examples

Thanks for the suggestion, I've filed this to be done here: https://github.com/Inedo/inedox-inedocore/issues/112

The problem is that OtterScript attempts to parse those variables first. Just use quotes:

set $foo = true;
set $bar = true;
set $foobar = $PSEval("$foo -and $bar");

Log-Information `$foobar = $foobar; # prints: $foobar = True

This appears to be a bug with the ProxyRequest property, i.e. if it's true (the default), the response variable is not set.

The tracking issue for this is here: https://github.com/Inedo/inedox-inedocore/issues/91

It does not exist yet, I've filed BM-3326 to add it in v6.1.2

We will make this change for the next minor version (i.e. the next version unless there is pressing need to do a maintenance release before then).

The tracking issue for this is: OT-291

Thank you for the report, I have filed OT-290 to get this fixed.

Apologies for the delay, I had to reach out to gather this information. What I learned was that this was a custom operation. Below is the link to its source:

Yes, I made that operation to accommodate DSC Configuration scripts (multiple DSC operations encapsulated in a PowerShell script).

I had built this on a fork of of inedox-windows. I just merged in the latest changes for the main master (it has been 6 months, so there quite a few changes). I have built it, but have not tested it since the merge.

https://github.com/MarkRobertJohnson/inedox-windows/blob/dsc-ensure-config/Windows/InedoExtension/Operations/EnsurePSDscScriptOperation.cs

Thanks, I've filed this as a bug here: BM-3307

Both are supposed to be supported, and quickly inspecting the code itself, I see both as possible arguments:

isMatch("builds") || isMatch("packages")

and

BuildId = AH.ParseInt(request["buildId"] ?? request["packageId"]),
BuildNumber = request["buildNumber"] ?? request["packageNumber"],

Perhaps it's JSON parsing related? Are you POSTing as application/json?

Both of these package types will be supported in 5.2.

PyPI support has now been added and published as a pre-release version of 5.2.0. Visit the ProGet Versions page to download, or get it from the Inedo Hub download.

PyPI support has now been added and published as a pre-release version of 5.2.0. Visit the ProGet Versions page to download, or get it from the Inedo Hub download.

PyPI support has been added and published as a pre-release version of 5.2.0. Visit the ProGet Versions page to download, or get it from the Inedo Hub download.

There are 2 ways to go about this:

1. Allow $PsCredentials() to support credential names as an argument

This is easiest, but would still require the "allow $CredentialProperty usage" option because you could always just write out the password in PowerShell regardless:

 $credentials = Get-Credential
 [Runtime.InteropServices.Marshal]::PtrToStringAuto([Runtime.InteropServices.Marshal]::SecureStringToBSTR(($credentials.Password))) | Write-Host

2. Create a new PowerShellCredentials type

While the same "exploit" would still be available, at least it would be limited to PowerShell, e.g. you couldn't just Log-Information $CredentialProperty(secret, Password);

This though means we're just duplicating what UserNamePassword credentials already do, and it could cause confusion as to which one to use.

If you have any other feedback on this, we are all ears!