Build Automation Add Licenses to Deployable Package, No license(s) found

(0) Share

Report

Posted on by HAIRUL HAZRI

1,214

Hi,

my journey to configure build automation continues. Here's my previous threads:

https://community.dynamics.com/365/financeandoperations/f/dynamics-365-for-finance-and-operations-forum/401765/build-automation-add-nuget-package-to-azure-artifacts-feed

https://community.dynamics.com/365/financeandoperations/f/dynamics-365-for-finance-and-operations-forum/402407/build-automation-custom-model-reference-error

In Add Licenses to Deployable Package task, I got No license(s) found error:

Where can I find this license(s)?

Are they downloadable from somewhere?

Thank you.

I have the same question (0)

All responses (7)

Answers (2)

nmaenpaa 101,162 Moderator on at

Like (0)

Report

What do you mean by "Where can I find this license(s)"?

Are you trying to add some ISV licenses into the deployable package? Did you get the licenses from your ISV solution provider?

Was this reply helpful? Yes No
HAIRUL HAZRI 1,214 on at

Like (0)

Report

Because I got the error & the task is by default inside the pipeline, I assumed we are missing the license.

Supposedly we do not have any ISV solutions.

So we can just disable this task?

Was this reply helpful? Yes No
Verified answer

nmaenpaa 101,162 Moderator on at

Like (0)

Report

This task is only needed if you want to add ISV licenses automatically in your deployable package.

docs.microsoft.com/.../pipeline-add-license-package

You should only use such features that you need, not add every available task in your pipeline.

Was this reply helpful? Yes No
HAIRUL HAZRI 1,214 on at

Like (0)

Report

Noted on that.

I have some quick questions if you don't mind to answer here:

How can we download the created deployable package manually? For now, we plan to just download & upload the package to LCS manually, before learning to configure release pipeline.

Where exactly is the "drop/Packages" path located? I thought it would be in the project Artifacts where the NuGet packages are, but that doesn't seem to be the case.

Was this reply helpful? Yes No
HAIRUL HAZRI 1,214 on at

Like (0)

Report

Found it. I just noticed this.

Cheers! :)

Was this reply helpful? Yes No
Verified answer

Joris dG 17,775 on at

Like (0)

Report

The default templates on GitHub have the license step disabled for this reason. We wanted to provide the example, but we know not everyone needs it or has ISV/licenses, so the step is disabled by default.

For the package, it's in the log but also on the build's overview page, you'll see a full list at the top right.

Was this reply helpful? Yes No
HAIRUL HAZRI 1,214 on at

Like (0)

Report

Thank you Joris for the screenshot.

This is just my opinion, but I think that link is too small to the eyes and it doesn't look like it's clickable at first glance.

Maybe Microsoft can do something about it. Just a minor experience issue though.

Cheers.

Was this reply helpful? Yes No