Sacramento - Todays hot news - REMMONT.COM

[DAVIDEa]

Devops extensions - Eduard Kabrinskiy


<h1>Devops extensions</h1>
<p>[youtube]</p>
Devops extensions <a href="http://remmont.com">Breaking news</a> Devops extensions
<h1>Quick tips when developing and publishing extensions for Azure DevOps</h1>
<h2>Save time while developing your extensions</h2>
<p>In this article I would like to share with you a list of quick tips that I personally find useful when developing Azure DevOps extensions. Probably, this will help you save some time while debugging or publishing your extension.</p>
<h2>Development</h2>
<p>To develop your <strong>Azure DevOps</strong> extension it is recommended to start by following the official Microsoft documentation; it contains illustrative examples which makes it a very good start. Feel free to checkout the official Git repository to see how the current tasks were built.</p>
<h3>Use Npm packages</h3>
<p>When you develop an Azure DevOps extension you use Typescript. The Typescript will be transpile into Javascript using the tsc command line. This command will compile <strong>all</strong> your .ts files in your project and generate a js file for each one. What is interesting about Typescript is that you can use all the npm packages you need!</p>
<h3>Speed up the development</h3>
<p>It is always recommended to compile your own extension locally to test its results during developing period. If your task needs to have some variable as entry point you need to export it.</p>
<p>To do that, the basic steps are:</p>
<p><ul>
<li>Export your variables one by one using command line</li>
<li>Compile the extension</li>
<li>Execute the extension by running the .js file generated</li>
</ul>
</p>
<p>This is repetitive and time consuming process. To resolve this problem it is recommanded to create a script. A real example for that is a Shell Script that contains all your variables, compiles and executes your extension. You will find below an example of a script; kindly notice that the variable are export for a <strong>Mac</strong> the Windows syntax is available on Microsoft documentation:</p>
<p>The benefits of this file are:</p>
<p><ul>
<li>can save it in your Git repository</li>
<li>know exactly what are the variables you used for your test</li>
<li>save some time when you are running the extension</li>
</ul>
</p>
<h3>Access files in your Azure DevOps extension</h3>
<p>When you want to access specific file in your Azure DevOps extension such as font you can load it directly using a relative path like this:</p>
<p>However, this would work locally but if you deploy your extension in the Azure DevOps environment it will neither work and it will tell you that your file is not found. To resolve this problem you need to use absolute path. To do that just load your file like this:</p>
<p>It will work locally and online.</p>
<h2>Publication</h2>
<h3>Create a package</h3>
<p>To generate a package for your extension it?s always the same thing you need to: install the npm packages, build and generate the .vsix file. You will also need to update the version inside the vss-extension.json . Here is an example:</p>
<p>You can optimize this script to modify the version of your extension, by dynamically change the version key inside the vss-extension.json file.</p>
<h3>Update package during development</h3>
<p>Your extension should be uploaded online in order to test it in a pipeline manner. It is recommended to do your tests by publishing your extension in private mode. So you can do all your development safely. To do that just specify it inside your vss-extension.json like this:</p>
<p><em>By default your extension status is private but you will need to set the public property to true when you will definitely publish your extension, so it will be already there.</em></p>
<p>You will then just share with your own organisation to be able to test it. When you do all your testing you will update your extension. I noticed that sometimes my build agent keeps the previous version of my extension instead of getting the new one I recently uploaded. To avoid losing time just remove and reinstall your extension then reshare it with your organisation and you will assure that you are using the correct version.</p>
<h3>Set the icon of your extension</h3>
<p>If you do a task for Azure DevOps you will need to add an icon. The task need multiple images:</p>
<p><ul>
<li>One icon.svg</li>
<li>One icon.png with 32x32 dimensions</li>
</ul>
</p>
<p>If you do not set the dimensions to 32x32 for your icon it will never be displayed inside Azure DevOps.</p>
<h2>Final touch</h2>
<p>Hope these tips will help you develop your own Azure DevOps extensions. Also, feel free to checkout my previous tasks available here:</p>
<h2>Devops extensions</h2>

<h3>Devops extensions</h3>
<p>[youtube]</p>
Devops extensions <a href="http://remmont.com">News page</a> Devops extensions
<h4>Devops extensions</h4>
Save time while developing your extensions
<h5>Devops extensions</h5>
Devops extensions <a href="http://remmont.com">Devops extensions</a> Devops extensions
SOURCE: <h6>Devops extensions</h6> <a href="https://dev-ops.engineer/">Devops extensions</a> Devops extensions
#tags#[replace: -,-Devops extensions] Devops extensions#tags#
https://ssylki.info/?who=senior-life-in ... emmont.com https://ssylki.info/?who=buy-land.remmont.com https://ssylki.info/?who=car-dealerships.remmont.com https://ssylki.info/?who=remmont.com/mu ... e-prison-3 https://ssylki.info/?who=loan-meaning.remmont.com