Skip to content
This repository has been archived by the owner on May 1, 2024. It is now read-only.

[build] attempt at signing .nupkg #5

Merged
merged 1 commit into from
Jan 21, 2021
Merged

[build] attempt at signing .nupkg #5

merged 1 commit into from
Jan 21, 2021

Conversation

jonathanpeppers
Copy link
Member

Based on: xamarin/Xamarin.Android.FSharp.ResourceProvider#8

* Bump to Microsoft.NET.Workload.Android-11.0.200-ci.master.40 for consistency
@jonathanpeppers jonathanpeppers merged commit 6a1c596 into main Jan 21, 2021
@jonathanpeppers jonathanpeppers deleted the signing branch January 21, 2021 22:26
@@ -47,6 +66,13 @@ jobs:
artifact: windows
targetPath: bin
condition: succeededOrFailed()
# NOTE: that PublishBuildArtifacts is required for signing

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There was a PR to change this, or at least support the other way. I think a property was added. But, this is not required.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It failed when I used PublishPipelineArtifact in a weird way:

https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=4392505&view=logs&j=e24aea9e-642d-565f-0ea4-ee7a5a3b8fdc&t=6e777e80-cc0f-5ccb-1c72-bf4d88543f78&l=12

But I'm fine to use PublishBuildArtifacts, it works. 👍

Copy link

@mattleibow mattleibow Jan 22, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Again I don't have a link on my phone, but I found the PR and it was not merged yet. 🙃

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one: https://github.com/xamarin/yaml-templates/pull/96

But I'm fine to leave this as it is.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, but yeah. No need to change. Just was an FYI for future things.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants