แสดงกระทู้

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Pearlandrist

หน้า: [1]
1
Around Suannan / Corona : devops fusion - Kabrinskiy Eduard
« เมื่อ: พฤษภาคม 23, 2021, 05:43:30 pm »
Эдуард Кабринский - Azure devops updates  - Кабринский Эдуард


<h1>Azure devops updates</h1>
<p>[youtube]</p>
Azure devops updates <a href="http://remmont.com">Headline news</a> Azure devops updates
<h1>Microsoft DevOps & Azure Functions: Implement recursive updates</h1>
<p>I have a task to implement an Azure Function which is triggered by an HTTP-Webhook defined in Microsoft DevOps (VSTS).</p>
<p><strong>The idea is as follows:</strong> </p>
<p><ul>
  <li>We have a backlog-structure (let's say: Epic > Feature > User Story > Task)</li>
  <li>If i set the state of any of those items to 'Done', all underlying items should also change to 'Done'</li>
</ul>
</p>
<p><strong>What i have done so far</strong></p>
<p><ul>
  <li>I have enabled a webhook in DevOps which triggers on update of any workitem and sends this item as JSON to an Azure Function</li>
  <li>I have written the Azure Function which is invoked by an HTTP-request and get's the URL of the item which has triggered the request <ul>
  <li>The function then gets all items which are a child of the first workitem</li>
  <li>The function patches all found child items with the state of the first item</li>
  <li>All direct children are updated on DevOps</li>
</ul>
</li>
</ul>
</p>
<p><strong>What i need</strong> <br />I'm trying to figure out an option to enable recursive update. Not only direct children should be updated, but also all their children (if they have some) and so on. I thought about the following ways to accomplish this and need your guidance:</p>
<p>Get all direct children as JSON and then send HTTP-request's to the same function, passing all child item's</p>
<p>call the function within the function (don't even know if this works) and pass the children as JSON</p>
<p>find a way to handle all the logic in this single function (dumb foreach-nesting to ensure all backlog-hierarchy levels are processed)</p>
<p>If any code snippets are needed just tell me and i will provide the requested parts (right now i'm quite unsure what part of my code i should publish and would be helpful)</p>
<h2>Azure devops updates</h2>

<h3>Azure devops updates</h3>
<p>[youtube]</p>
Azure devops updates <a href="http://remmont.com">New news today</a> Azure devops updates
<h4>Azure devops updates</h4>
Microsoft DevOps & Azure Functions: Implement recursive updates I have a task to implement an Azure Function which is triggered by an HTTP-Webhook defined in Microsoft DevOps (VSTS). The idea
<h5>Azure devops updates</h5>
Azure devops updates <a href="http://remmont.com">Azure devops updates</a> Azure devops updates
SOURCE: <h6>Azure devops updates</h6> <a href="https://dev-ops.engineer/">Azure devops updates</a> Azure devops updates
#tags#[replace: -,-Azure devops updates] Azure devops updates#tags#
Кабринский Эдуард
top news

2
Around Suannan / Philadelphia : ai devops - Кабринский Эдуард
« เมื่อ: พฤษภาคม 15, 2021, 05:21:43 am »
Эдуард Кабринский - Azure devops sharepoint  - Эдуард Кабринский


<h1>Azure devops sharepoint</h1>
<p>[youtube]</p>
Azure devops sharepoint <a href="http://remmont.com">Important news today</a> Azure devops sharepoint
<h1>Azure DevOps: increase the speed of your SharePoint Framework continuous integration and delivery</h1>
<p style="clear: both"> <img src="https://delucagiuliano.com/assets/img/SPFxAzureDevOps.jpg" /></p>
<p>Azure DevOps is the next step in terms of evolution for Visual Studio Team Services (VSTS). I can summarize the benefit with a bullet list:</p>
<p>In this article, I talked about how to configure the continuous integration and delivery for a SharePoint Framework solution. Now I’d like to provide some tip in order to speed up the time during the build and release phase.</p>
<h3>Build definition overview</h3>
<p>Before to start, I show you how looks like the build and release definition with all tasks:</p>
<p style="clear: both"> <img src="https://delucagiuliano.com/assets/img/BuildDefinition.jpg" /></p>
<p>The SharePoint Framework 1.6 has been released, the latter supports Node 8. Starting with this assumption, I defined the installation of Node 8.x as the first step, in fact, this will increase the velocity during the command “NPM Install”. Normally when we run the command NPM install locally without errors, there are good probabilities that this command will succeed on Azure DevOps build as well. Considering that, we can disable the log during the “NPM install” by creating the task “NPM set progress=false”, this will make us earn about 40 seconds. Then we have the classic tasks to build and package a SharePoint Framework solution:</p>
<p><ul>
  <li>Npm Install</li>
  <li>Clean Bundle</li>
  <li>Create Bundle</li>
  <li>Package Solution</li>
</ul>
</p>
<p>It’s time to finalize the build by copying the files and publishing the artifact. All we need are the following files SPPKG, package-solution.json, VSTS.DeploySPFxToAppCatalog.ps1. The first one is necessary in order to deploy the solution in the App Catalog. If you decide to adopt the release across Powershell you need to include the package-solution.json to read parameters like “includeClientSideAssets, zippedPackage, skipFeatureDeployment”. Finally, the last one (VSTS.DeploySPFxToAppCatalog.ps1) that you can include in your solution with the Powershell command:</p>
<p>This script will help you to automate the deploy, we will see it later (more info are available on my GitHub repo). The total duration of my build is:</p>
<p style="clear: both"> <img src="https://delucagiuliano.com/assets/img/duration.jpg" /></p>
<p>Below every steps for the build definition:</p>
<p style="clear: both"> <img src="https://delucagiuliano.com/assets/img/SPFxDevOps1.jpg" /></p>
<p style="clear: both"> <img src="https://delucagiuliano.com/assets/img/SPFxDevOps2.jpg" /></p>
<p style="clear: both"> <img src="https://delucagiuliano.com/assets/img/SPFxDevOps3.jpg" /></p>
<p style="clear: both"> <img src="https://delucagiuliano.com/assets/img/SPFxDevOps4.jpg" /></p>
<p style="clear: both"> <img src="https://delucagiuliano.com/assets/img/SPFxDevOps5.jpg" /></p>
<p style="clear: both"> <img src="https://delucagiuliano.com/assets/img/SPFxDevOps6.jpg" /></p>
<p style="clear: both"> <img src="https://delucagiuliano.com/assets/img/SPFxDevOps7.jpg" /></p>
<p style="clear: both"> <img src="https://delucagiuliano.com/assets/img/SPFxDevOps8.jpg" /></p>
<h3>Release definition overview</h3>
<p>The release definition offers several possibilities of usage. In fact, we can use different approaches:</p>
<p>I’ll show you two scenarios with Office 365 CLI and Powershell. Before to start with the second scenario, remember to use Office 365 CLI at least one time on your tenant. It’s necessary to grant the permissions to this amazing cross-platform tool in order to use it, as explained by Waldek Mastykarz in this article:</p>
<p style="clear: both"> <img src="https://delucagiuliano.com/assets/img/consent.png" /></p>
<p>Once granted the permissions we can start to configure the release definition that will be something like that:</p>
<p style="clear: both"> <img src="https://delucagiuliano.com/assets/img/Office-365-CLI.jpg" /></p>
<p>Here the result:</p>
<p style="clear: both"> <img src="https://delucagiuliano.com/assets/img/Office-365-CLI-Result.jpg" /></p>
<p>Regarding the other approach with Powershell, I can say that is fastest, but can only be adopted if you are using a Windows environment:</p>
<p style="clear: both"> <img src="https://delucagiuliano.com/assets/img/PnP-Powershell-Release.jpg" /></p>
<p>As you can see we have only two tasks, with the first is possible to install PnP Powershell with the second I’m going to deploy the sppkg file to the App Catalog by following the instructions in the file <strong>package-solution.json.</strong></p>
<p>Here you can see the result:</p>
<p style="clear: both"> <img src="https://delucagiuliano.com/assets/img/PnP-Powershell-Release-result.jpg" /></p>
<p>Both scenarios are valid, therefore feel free to use what you prefer.</p>
<p>Below every single steps for the release definition:</p>
<h2>Azure devops sharepoint</h2>

<h3>Azure devops sharepoint</h3>
<p>[youtube]</p>
Azure devops sharepoint <a href="http://remmont.com">Today's news headlines in english</a> Azure devops sharepoint
<h4>Azure devops sharepoint</h4>
Azure DevOps is the next step in terms of evolution for Visual Studio Team Services (VSTS). I can summarize the benefit with a bullet list: Pipelines Boards Artifacts Repos Test Plans Please take a look at the official Azure blog in order to go deeper.
<h5>Azure devops sharepoint</h5>
Azure devops sharepoint <a href="http://remmont.com">Azure devops sharepoint</a> Azure devops sharepoint
SOURCE: <h6>Azure devops sharepoint</h6> <a href="https://dev-ops.engineer/">Azure devops sharepoint</a> Azure devops sharepoint
#tags#[replace: -,-Azure devops sharepoint] Azure devops sharepoint#tags#
Eduard Kabrinskiy
online news

หน้า: [1]