Best posts made by NanciCalo

Hi @Stephen-Schaff,

The renewal contact at your organization should have been receiving emails about 60 days ago, and then someone was supposed to be manually following up... but something clearly fell through the cracks. I already escalated it internally.

But not to worry! In a case like this, please just go to my.inedo.com, and request a 30-day trial license key. It has all the functionality of ProGet Basic, so your service won't be interrupted at all.

Changing the expiration warning in the software to 30 days is really good idea to prevent problems like this, so I'll request that as a feature internally :)

Cheers,

Nanci

@Stephen-Schaff thanks so much Stephen, that's great! It's not so hard for us to add this api key back, but your code works just the same mostly i think! let us know...

Anyway I've updated the documentation :)

Hi @mihajlo_7906 ,

It looks like you're using legacy functionality (i.e. from BuildMaster v4 and earlier) within a legacy version (v5) of BuildMaster.

Re-execute from last failed action button is re-executing the whole pipeline stage (from the beginning) instead of the current action of which the deployment failed.

The "Re-execute from Last Failed Action" is only displayed on some Legacy Plan executions, and it can't work on all plans. I'm not sure why it doesn't work in your case, but we no longer have such functionality on for non-legacy (OtterScript) executions, so I can't guess why it doesn't work.

An unhandled exception occurred while executing this action: System.IO.FileNotFoundException: Could not load file or assembly 'Windows' or one of its dependencies. The system cannot find the file specified.

This error is saying that the "Windows" extension file (Windows.upack or Windows.bmx, depending on the configuration) didn't load.

This is why why deployments fail. The most common reason for this is file locking (anti virus, etc.), but you can use tools like Procmon to see what's going on. Loading an extension involves unzipping it and loading the enclosed .dll from disk.

Cheers,
Alana