yannickre / vsts-sharepoint-alm

VSTS tasks that leverage the SharePoint ALM API's in a TFS/Team Services build or release definition

Heya, I'm Yannick Reekmans 🚀

Microsoft Cloud Solution Architect | Business Applications MVP | Microsoft 365 MVP

About me

Yannick (a Microsoft 365 MVP & Business Applications MVP) is born and raised in SharePoint, starting out his career in 2011 when SharePoint 2010 was still new and shiny. The changing reality of the cloud made him expand his knowledge to the whole of Microsoft 365, Azure, and Power Platform.

He is a Managing Partner and Cloud Solution Architect at Qubix, a Belgium-based consultancy firm, responsible for the technical underpinnings of products and solutions. He owns KEOS, a management company to support his independent work.

Problem solving and development are his passion, still working day to day with code.

He always asks the important questions: How does it work? What do you want to achieve? Does it have an API? Do we really need development for this? Where's the coffee?

About me, the tldr;

🇧🇪 Belgium-based
🏆 Microsoft 365 MVP & Business Applications MVP
🔭 Managing Partner and Cloud Solution Architect at Qubix
💰 Owner of KEOS
📝 Blog at https://blog.yannickreekmans.be
🐣 Tweet at @YannickReekmans
🎤 Speaks at wherever they give him a stage and an audience
💬 Ask me about Microsoft 365, SharePoint Development, Microsoft Teams (Development), Power Platform (Power Automate, Power Apps, Dataverse, ALM, ...)

Find me

                 

Github stats

vsts-sharepoint-alm's Issues

I can add but not deploy

I have built a pipeline that should take the newly build packge and update it in the app catalog.
I first do a "Add solution package" and this works fine.
Then I do a "Deploy solution package". This fails with a "403 forbidden" message. I use the same conenction/credentials as the first action.
If I go to powershell and do a publish-pnpapp -Identity it publishes the package nicely.

Any ideas as what the problem could be?

Error when trying to use the extension

Hi,
I'm trying to add a packaged application to my Sharepoint online instance using ADO. I've installed the extension from Marketplace and configured a Token based service connection.
When calling the Add action

- task: SharePointALMCatalogScoped@2
  inputs:
    spSiteConnection: 'Sharepoint-Connection'
    useTenantCatalog: false
    action: 'Add'
    appFilePath: 'apackage.sppkg'
    overwriteExisting: true
    packageIdOut: 'VarPackageId'

I'm getting the following error:

2022-06-07T09:05:01.3147959Z ##[section]Starting: SharePointALMCatalogScoped
2022-06-07T09:05:01.3157589Z ==============================================================================
2022-06-07T09:05:01.3157989Z Task         : SharePoint ALM: Catalog Scoped Actions
2022-06-07T09:05:01.3158385Z Description  : ALM actions in scope of the SharePoint Tenant or Site App Catalog.
2022-06-07T09:05:01.3158697Z Version      : 2.0.12
2022-06-07T09:05:01.3158936Z Author       : Yannick Reekmans
2022-06-07T09:05:01.3159142Z Help         : 
2022-06-07T09:05:01.3159420Z ==============================================================================
2022-06-07T09:05:02.4081398Z Action: Add
2022-06-07T09:05:02.4082414Z SharePoint Site Connection: cd54abf2-f4ed-491d-b949-16f026e4c864
2022-06-07T09:05:02.4088874Z SharePoint Site Connection Type: Token
2022-06-07T09:05:02.4089364Z SharePoint Site Url: https://crm861539.sharepoint.com/sites/appcatalog/
2022-06-07T09:05:02.4089818Z Parsing Token
2022-06-07T09:05:02.4092324Z ClientId: ***
2022-06-07T09:05:02.4093229Z SharePoint App Package File Path: /home/vsts/work/1/s/SPFx/ducacode/sharepoint/solution/duca-issues.sppkg
2022-06-07T09:05:02.4093808Z Overwrite Existing Package: true
2022-06-07T09:05:02.4094159Z Package Id Variable: VarPackageId
2022-06-07T09:05:02.4389756Z (node:2214) Warning: Use Cipheriv for counter mode of aes-256-ctr
2022-06-07T09:05:02.4391600Z (node:2214) Warning: Use Cipheriv for counter mode of aes-256-ctr
2022-06-07T09:05:02.4392738Z (node:2214) Warning: Use Cipheriv for counter mode of aes-256-ctr
2022-06-07T09:05:02.4394043Z (node:2214) Warning: Use Cipheriv for counter mode of aes-256-ctr
2022-06-07T09:05:02.4395169Z (node:2214) Warning: Use Cipheriv for counter mode of aes-256-ctr
2022-06-07T09:05:02.4396224Z (node:2214) Warning: Use Cipheriv for counter mode of aes-256-ctr
2022-06-07T09:05:02.4397348Z (node:2214) Warning: Use Cipheriv for counter mode of aes-256-ctr
2022-06-07T09:05:02.4398395Z (node:2214) Warning: Use Cipheriv for counter mode of aes-256-ctr
2022-06-07T09:05:02.4399591Z (node:2214) Warning: Use Cipheriv for counter mode of aes-256-ctr
2022-06-07T09:05:02.4400721Z (node:2214) Warning: Use Cipheriv for counter mode of aes-256-ctr
2022-06-07T09:05:02.4401761Z (node:2214) Warning: Use Cipheriv for counter mode of aes-256-ctr
2022-06-07T09:05:02.4402887Z (node:2214) Warning: Use Cipheriv for counter mode of aes-256-ctr
2022-06-07T09:05:02.4404006Z (node:2214) Warning: Use Cipheriv for counter mode of aes-256-ctr
2022-06-07T09:05:02.4405053Z (node:2214) Warning: Use Cipheriv for counter mode of aes-256-ctr
2022-06-07T09:05:02.4406223Z (node:2214) Warning: Use Cipheriv for counter mode of aes-256-ctr
2022-06-07T09:05:04.4558875Z ##[error]Error: GetDigestValue failed. StatusCode: 401. Result: Unauthorized.
2022-06-07T09:05:19.6020478Z ##[section]Finishing: SharePointALMCatalogScoped

Am I doing something wrong? Can you help?

Thanks,

Cannot install in Azure DevOps

I have tried to install this in our company's DevOps, and it appears to start the process but then hangs, even when left for long time. I have tried all the obvious debugging options, but nothing seems to help.

Issue in node-sp-auth

You have a dependency on node-sp-auth. We recently noticed a issue where resolving the tenantid when connecting with clientid&secret fails. It looks like the issue is a typo in the url when posting to client.svc. I submitted a issue to the author of node-sp-auth.

Because of this issue, uploading a spfx package using clientid and secret fails.
Please be aware of this issue, and when the author fixes it, can you update you're dependancy with this lib..