I use Azure DevOps in order to make continuous integration (CI). I would like to push the binaries (artifacts) to a one drive sharepoint folder whose url is like this : https://foo.sharepoint.com/personal/bar/_layouts/15/onedrive.aspx .
Thank you very much for your help !
I make some research and i attempt to do it with microsoft graph. But i don't understand how to make url....
I see also that many of customers like me want to do this : https://developercommunity.visualstudio.com/t/onedrive-support-for-devops-pipeline-release/548731.
I saw that it is possible to do this with a powershell script. But i don't know at all how to manage all this mess !
I suppose that you could follow this document for Continuous Integration and Continuous deployment using Azure DevOps
After you create the artifacts, you could follow the steps below to publish it to share point in a Release Pipeline.
1.Adding a stage.
2.Install the Node.JS tool in your stage with node.js installer with the version 10.x.
If your project is based on SharePoint Framework version 1.7.1 or earlier, use version 8.X.
3.Installing the CLI for Microsoft 365.
Add a npm task, select a Custom command and type install -g #pnp/cli-microsoft365 in the Command and Arguments field. Learn more about the CLI for Microsoft 365
4.Connecting to SharePoint Online
Before using the App Catalog in your deployment environment, you first need to authenticate against the App Catalog of your tenant. To do so, add a Command Line task and paste in the following command into the script field m365 login -t password -u $(username) -p $(password).
note
If you are using CLI for Microsoft 365 to connect to your tenant for the first time, you need to perform an interactive logon with the account first. This is required to grant access to PnP Office 365 Management Shell application which is used by CLI for Microsoft 365 to access your tenant on the account's behalf. Your task will otherwise fail to logon non-interactively. Details available on CLI for Microsoft 365 User Guide.
5.Adding the Solution Package to the App Catalog
Upload the solution package to your App Catalog by adding another Command Line task and pasting the following command line in the Script field m365 spo app add -p $(System.DefaultWorkingDirectory)/SpFxDevOps/drop/SharePoint/solution/sp-fx-devops.sppkg --overwrite
The path of the package depends on your solution name (see your project configuration) as well as the Source Alias you defined earlier, make sure they match.
Note
You can upload a solution to a site collection app catalog by adding --appCatalogUrl https://$(tenant).sharepoint.com/$(catalogsite) --scope sitecollection
6.Deploying the Application
The final step in the setup is to deploy the application to the App Catalog to make it available to all site collections within the tenant as its latest version. Add another Command Line task and paste the following command line in the Script field m365 spo app deploy --name sp-fx-devops.sppkg
Note
You can deploy a solution from a site collection app catalog by adding --appCatalogUrl https://$(tenant).sharepoint.com/$(catalogsite) --scope sitecollection
Related
I have a problem with exporting and customizing work items in Azure DevOps
when I try to export work items I get this error "The feature is disabled. Contact your Azure DevOps Server administrator. process ID x Project ID x."
I'm the only user in azure DevOps
I tried with tftp tools and witadmin command and both errors were the same.
can anyone help me
Notice: I use Azure DevOps On-premise
when I try to export work items I get this error "The feature is
disabled. Contact your Azure DevOps Server administrator. process ID x
Project ID x
To achieve the above requirement ,
As you are user,
First of all you need to have an administrator permissions to your project.
Then we can export the project .
Based on this Prequisite as described on MS DOC well: -
To get those permissions you can refer this MS DOC.
For more information please refer this MICROSOFT DOCUMENTATION
I am developing an outlook add-in using the Yeoman Office generator (Office Add-in Task Pane project supporting single sign-on).
All documentation on using this program says to run "npm run configure-sso" after Yeoman has finished and it builds the AAD instance for you.
My problem is "npm run configure-sso" saves the client secret in Microsoft's Credential Manager (on the PC), but I want to host my add-in on Azure. Is there a way to move the client secret from Credential Manager into an Azure instance, or into an environment variable in the add-in?
This setup likely won't work on Azure deployment because office-addin-sso package SSO code is attempting to store and get the app secret in Windows credential manager so you have to remove that package and then add the code yourself to handle SSO so that you can deploy to Azure.
Here are some workaround . However, Microsoft team have plan to document this sometime in August, so hopefully will have guidance around this soon.
I'm trying to create a build in Team Services (Visual Studio Online) but am having a few issues.
My first step is to create a new build and I've selected the template Deployment -> Azure Web App
Then in the build step for Azure Deployment I need to select my Azure subscription. This list is currently empty so I select Manage to add a new one.
Following the instructions here I try to add a new endpoint but it says to select the one called 'Azure' but in my list I've got 'Azure Classic' and 'Azure Resource Manager'. Which one should I use?
I've tried 'Azure Resource Manager' and used the details to generate service key etc using the Powershell script as said in the previous link. Now the status just stay at 'Connecting to service using Service Principal' and is not selectable in the list.
How do I get Team Services to see my Azure subscription?
I must say, I've found the documentation for this a bit lacking in that a lot of the Microsoft sites still use the classic portal or older versions for the sites.
Starting from the end of your question, one of the reasons of that is that some functionality is not available yet on the new portal. As far as i know, all of the functionality should migrate to the new portal in a future.
For Azure Web App, please add the New Service Endpoint using classic mode (and i prefer to do that using certificate - very simple). Then, when adding the web site as the build step (for example), select your added subscription and you should be good to go.
I'm following the procedure to create a Xamarin app with a mobile app backend in Azure.
https://azure.microsoft.com/en-us/documentation/articles/app-service-mobile-dotnet-backend-xamarin-android-get-started-preview/
I've create the mobile app in the portal and downloaded the backend runtime and xamarin solutions. When I try to publish the backend runtime, the instructions indicate that the one I just created should show up 'Existing Web Apps'. Mine shows nothing.
My questions are:
1) How can I troubleshoot what shows up in the 'Existing Web Apps'?
2) Is it reasonable to just create a new web app from the VS Publish dialog?
3) If not, where should I place the publish profile that I can download from the azure portal?
Regards,
Rajesh
1.a. Ensure you're using the right azure suscription from VS
1.b. Logout and add your subscription login again
Yes it's reasonable
You can put it wherever you want. From VS website project goto publish settings
4. Then select import
5.And Finally browse the publish settings file
I have had issues with Visual Studio finding the existing apps. I tend to download the publish settings and use that instead. This works fine.
Alternatively, create a git repository and check the code into the git repository. Check out this article for instructions: https://azure.microsoft.com/en-us/documentation/articles/web-sites-publish-source-control/
Personally, I post my code to a branch of my git repository on GitHub and link the continuous deployment option of the Azure App Service to that. You can find my blog about this topic here: http://shellmonger.com/2015/08/29/continuous-deployment-nodejs-and-microsoft-azure/ - it's for NodeJS but the concept and methodology is the same.
My problem is that I have a NuGet server on an Azure website using Azure AD for auth. It works as expected if I hit the NuGet URL in Chrome (requires the login, which accepts appropriate credentials), but if I try to access it in Visual Studio 2013 (through manage NuGet packages) it won't accept the account/password as appropriate credentials (the prompt just pops up again). My approach was as follows:
With the goal of creating a simple internal NuGet server, I largely followed the instructions in this article to deploy one on an Azure website: http://www.codeproject.com/Articles/872230/Create-Your-Own-Private-NuGet-Server-in-Windows-Az
The NuGet server works just fine, but I wanted to add some basic auth since we'll be hosting some of our code there. I decided to try to use Azure AD for this. I added a couple Microsoft accounts (mine and a coworker's) to our otherwise empty default Azure active directory. Through the management portal, I then selected the 'configure' tab in the website dashboard and added the default directory in the auth section.
Since the developers who will be pulling down our packages will do so through Visual Studio, I need to figure this out or find an alternative. I would like (if possible) to avoid writing my own auth module, since this feature is supposed to be baked into Azure.
It turns out that NuGet does not currently support Azure AD. However, they are working on it and progress can be tracked here: https://github.com/NuGet/Home/issues/708