1. Нам важно Ваше мнение!
    и обсуждайте вместе! Нажимайте "мне нравится" и рекомендуйте друзьям ;)
    Понравилось тема? Напишите в ней свой отзыв.
    Считаете что тема не достаточно полно раскрыта? Расскажите свою точку зрения!
    С Вашей помощью сделаем форум еще лучше!
OxnardEn

News on - REMMONT.COM

Тема в разделе 'Свободное общение и OFF-топик', создана пользователем OxnardEn, 19 май 2021.

  1. OxnardEn

    OxnardEn Member

    Azure devops linux - Eduard Kabrinskiy


    <h1>Azure devops linux</h1>
    <p>[youtube]</p>
    Azure devops linux <a href="http://remmont.com">America latest news</a> Azure devops linux
    <h1>Scott Hanselman</h1>
    <h2>Deploying a MSDeploy-packaged Web application to a Linux Azure App Service with Azure DevOps</h2>
    <p>For bizarre and unknown historical reasons, when using MSDeploy to make a ZIP package to upload a website to a web server you get a massively deep silly path like yada/yada/C_C/Temp/package/WebApplication1/obj/Release/Package/PackageTmp. I use .NET Core so I usually do a "dotnet publish" and get a sane path for my build artifacts in my CI/CD (Continues Integration/Continuous Deployment) pipeline.</p>
    <p>I'm using the original pipeline editor on free Azure DevOps (I'm still learning DevOps YAML for this, and this visual pipeline editor IMHO is more friendly for getting started.</p>
    <p>However, I'm using a "Visual Studio Build" task which is using MSDeploy and these MSBuild arguments.</p>
    <p style="clear: both"><img style="float: left; margin: 0 10px 5px 0;" src="https://hanselmanblogcontent.azuree...mage_1222b321-d78b-474c-9823-13b703c82892.png" />Later on in the process I'm taking this package/artifact - now named "drop.zip" and I'm publishing it to Azure App Service.</p>
    <p>I'm using the "Azure App Service Deploy" task in the DevOps release pipeline and it works great when publishing to a <em>Windows</em> Azure App Service Plan. Presumably because it's using, again, MSDeploy and it knows about these folders.</p>
    <p>However, I wanted to also deploy to a <em>Linux</em> Azure App Service. Recently there was a massive (near 35%) price drop for Premium App Services. I'm running an S1 and I can move to a P1V2 and get double the memory, move to SSDs, and get double the perf for basically the same money. I may even be able to take TWO of my S1s and pack all my websites (19 at this point) into just one Premium. It'll be faster and way cheaper.</p>
    <p>Trick is, I'll need to move my Windows web apps to Linux web app. That's cool, since I'm using .NET Core - in my case 2.1 and 2.2 - then I'll just republish. I decided to take my existing Azure DevOps release pipeline and just add a second task to publish to Linux for testing. If it works I'll just disable the Windows one. No need to rebuild the whole pipeline from scratch.</p>
    <p>Unfortunately the Linux Azure App Service has its deployment managed as a straight ZIP deployment; it was ending up with a TON of nested folders from MSDeploy!</p>
    <blockquote><p><strong>NOTE:</strong> If I'm giving bad advice or I am missing something obvious, please let me know in the comments! Perhaps there's a "this zip file has a totally bonkers directory structure, fix it for Linux" checkbox that I missed?</p></blockquote>
    <p>I could redo the whole build pipeline and build differently, but I'd be changing two variables and it already works today on Windows.</p>
    <p>I could make another build pipeline for Linux and build differently, but that sounds tedious and again, a second variable. I have a build artifact now, it's just in a weird structure.</p>
    <p>How did I know the build artifact had a weird folder structure? I remember that I could just download any build artifact and look at it! Seems obvious when you say it but it's a good reminder that all these magical black box processes that move data from folder to folder are not black boxes - you can always check the result of a step. The output of one step becomes the input to the next.</p>
    <p style="clear: both"><img src="https://hanselmanblogcontent.azuree...mage_d12330ec-2bef-48fd-b6d0-8f0aa31a1919.png" /></p>
    <p>I should probably have a Windows Build and Linux Build (two separate build agents) but the site isn't complex enough and it doesn't do anything that isn't clearly cross-platform friendly.</p>
    <p>Anthony Chu suggested that I just remove the folders by restructuring the zip file (unzipping/zipping it). Could be a simple way to get both Windows and Linux publishing from a single artifact. I can fix it all up with a fresh build and release pipeline another time when I have the energy to learn this YAML format. (Speaking of the Azure DevOps YAML which doesn't have a friendly editor or validator, not speaking of YAML as a generic concept)</p>
    <p style="clear: both"> <img src="https://hanselmanblogcontent.azuree...mage_fadd22e9-b43e-444c-b778-9f42c32384d5.png" /></p>
    <p>I unzip the weird folder structure, then zip it back up from a new root. It then cleanly deploys to the Linux Azure App Service from the same artifact I made built for the Windows App Service.</p>
    <p>Ironically here's a YAML view of the tasks, although I build them with the visual editor.</p>
    <p>Just to be clear, this isn't standard and it's a pretty rare edge case and it may not work for everyone but isn't it nice to google for a super rare edge case and instead of feeling all alone you find an answer?</p>
    <p><strong>Sponsor:</strong> Looking for a tool for performance profiling, unit test coverage, and continuous testing that works cross-platform on Windows, macOS, and Linux? Check out the latest JetBrains Rider! </p>
    <h4>About Scott</h4>
    <p>Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.</p>
    <h2>Azure devops linux</h2>

    <h3>Azure devops linux</h3>
    <p>[youtube]</p>
    Azure devops linux <a href="http://remmont.com">New news today</a> Azure devops linux
    <h4>Azure devops linux</h4>
    For bizarre and unknown historical reasons, when using MSDeploy to make a ZIP ...
    <h5>Azure devops linux</h5>
    Azure devops linux <a href="http://remmont.com">Azure devops linux</a> Azure devops linux
    SOURCE: <h6>Azure devops linux</h6> <a href="https://dev-ops.engineer/">Azure devops linux</a> Azure devops linux
    #tags#[replace: -,-Azure devops linux] Azure devops linux#tags#
    https://ssylki.info/?who=insr.remmont.com https://ssylki.info/?who=money-lenders.remmont.com https://ssylki.info/?who=state-farm-insurance.remmont.com https://ssylki.info/?who=best-car-insurance.remmont.com https://ssylki.info/?who=foreclosed-homes-for-sale.remmont.com

Поделиться этой страницей