Azure-devops-docs: Problem to find $(bake.manifestsBundle) for Kustomize in release pipeline

Created on 3 Apr 2020  Â·  3Comments  Â·  Source: MicrosoftDocs/azure-devops-docs

Hello,

I would like to ask, because we created similar tasks in release pipeline

But the result of second task is:

No manifest file(s) matching /our/path/to/working/$(bake.manifestsBundle) was found.

We used the same yaml file:

...
    manifests: $(bake.manifestsBundle)

Do we need specify this manifest before bake process ?
Is this manifest created in first (bake) task automatically moved to next steps, or do we need to move it ?

Thanks


Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Pri2 cba devops-cicd-ecosystemtech devopprod support-request

Most helpful comment

Hey Mishco, if you're using pure yaml, try adding a name just below displayName in the bake-action task. Can be any name. Then, in the deploy-action task, in manifests, use that name as reference for the manifestsBundle. For example: if you name it "myBake" in the bake task, then in the deploy task should have $(myBake.manifestsBundle) in manifests.

If you're using the UI Release Pipeline, that name is under the Output Variables dropdown in the kubernetes task. For the bake-action task, name it something (like in the yaml) in the text field of the Output Variables dropdown. Then in the next kubernetes task (the deploy), reference to it in the manifests field like you would do for the yaml.

The secrete, I believe, is the the name for the manifests after baking it. It follows $({nameYouWant}.manifestsBundle).

All 3 comments

Thanks for your question. It looks like you're working through an issue with your scenario or implementation, rather than an issue with the documentation. Here are a couple of options where you might consider asking your question:

Hey Mishco, if you're using pure yaml, try adding a name just below displayName in the bake-action task. Can be any name. Then, in the deploy-action task, in manifests, use that name as reference for the manifestsBundle. For example: if you name it "myBake" in the bake task, then in the deploy task should have $(myBake.manifestsBundle) in manifests.

If you're using the UI Release Pipeline, that name is under the Output Variables dropdown in the kubernetes task. For the bake-action task, name it something (like in the yaml) in the text field of the Output Variables dropdown. Then in the next kubernetes task (the deploy), reference to it in the manifests field like you would do for the yaml.

The secrete, I believe, is the the name for the manifests after baking it. It follows $({nameYouWant}.manifestsBundle).

cc @azooinmyluggage for awareness

Was this page helpful?
0 / 5 - 0 ratings