Running maintenance on self-hosted Azure DevOps agentsADB RSA key fingerprint changes on Azure DevOps (vsts) self hosted agentAzure DevOps Hosted Agents - Add Tool (PS Module) to agentUnable to download artifacts from Azure DevOps git repository from Linux agentNo analysable projects were found - Azure DevOps/Self hosted agentRemoving Agent from Pool in Azure DevOpsAzure Devops - How to restrict custom build task to run only on a self hosted agent?Azure Devops (VSTS) Different between Agent Pool and Deployment poolAzure Devops - Multiple repositoriesError while configuring Self-hosted ARM agent for Azure DevOpsHow to change user account for a pipeline running in Azure Pipelines

Is there a way, while dragging, to "snap" to the nearest guide?

What can I do with a research project that is my university’s intellectual property?

What could exist inside and between the walls of a Dyson Sphere?

Can humans ever directly see a few photons at a time? Can a human see a single photon?

How is hair tissue mineral analysis performed?

Who are the remaining King/Queenslayers?

Why don't countries like Japan just print more money?

How can I politely work my way around not liking coffee or beer when it comes to professional networking?

Is this proposal by U.S. presidential candidate Pete Buttigieg to change the composition of the Supreme Court constitutional?

When can you leave off “le/la” to say “it” in French?

Why do all the teams that I have worked with always finish a sprint without completion of all the stories?

How do I handle a table mixing up the DM and the players' roles too often?

How would modern naval warfare have to have developed differently for battleships to still be relevant in the 21st century?

Non-flat partitions of a set

Can Ogre clerics use Purify Food and Drink on humanoid characters?

Explain why a line can never intersect a plane in exactly two points.

If I wouldn't want to read the story, is writing it still a good idea?

Why do even high-end cameras often still include normal (non-cross-type) AF sensors?

Is it damaging to turn off a small fridge for two days every week?

Array initialization optimization

Can there be an UN resolution to remove a country from the UNSC?

Do I have any obligations to my PhD supervisor's requests after I have graduated?

What happens to Cessna electric flaps that are moving when power is lost?

Unusual mail headers, evidence of an attempted attack. Have I been pwned?



Running maintenance on self-hosted Azure DevOps agents


ADB RSA key fingerprint changes on Azure DevOps (vsts) self hosted agentAzure DevOps Hosted Agents - Add Tool (PS Module) to agentUnable to download artifacts from Azure DevOps git repository from Linux agentNo analysable projects were found - Azure DevOps/Self hosted agentRemoving Agent from Pool in Azure DevOpsAzure Devops - How to restrict custom build task to run only on a self hosted agent?Azure Devops (VSTS) Different between Agent Pool and Deployment poolAzure Devops - Multiple repositoriesError while configuring Self-hosted ARM agent for Azure DevOpsHow to change user account for a pipeline running in Azure Pipelines






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








0















I have several self-hosted Azure DevOps agents (each installed on a dedicated on-prem server) and I need to perform reoccurring maintenance on them (i.e. patching, etc.). Is there's a good way to define those maintenance windows within Azure DevOps so that server admins could do their job without worrying to interrupt any ongoing build/release task?



There seem to be a setting related to configuring reoccurring maintenance (Organization Settings -> Agent Pools -> <Pool Name>-> Settings [tab]) but it seems as if it would apply to the whole pool and it's hard to tell which of the agents will be considered offline at which time slot.
Unfortunately I couldn't find any documentation about it and not sure if there's something that Azure DevOps would also be doing on the agent machines (i.e. running cleanup, updating agents and so on)



Currently, the process involves a person with admin permissions in Azure DevOps to disable an agent allowing a server admin to perform regular maintenance and to re-enable it back when server admin is done. It would be great if a server admin could not involve an Azure DevOps Admin every time for such routines.










share|improve this question

















  • 1





    please confirm if you are satisfied with my answer or not. thanks in advance!

    – Eriawan Kusumawardhono
    Mar 27 at 10:26

















0















I have several self-hosted Azure DevOps agents (each installed on a dedicated on-prem server) and I need to perform reoccurring maintenance on them (i.e. patching, etc.). Is there's a good way to define those maintenance windows within Azure DevOps so that server admins could do their job without worrying to interrupt any ongoing build/release task?



There seem to be a setting related to configuring reoccurring maintenance (Organization Settings -> Agent Pools -> <Pool Name>-> Settings [tab]) but it seems as if it would apply to the whole pool and it's hard to tell which of the agents will be considered offline at which time slot.
Unfortunately I couldn't find any documentation about it and not sure if there's something that Azure DevOps would also be doing on the agent machines (i.e. running cleanup, updating agents and so on)



Currently, the process involves a person with admin permissions in Azure DevOps to disable an agent allowing a server admin to perform regular maintenance and to re-enable it back when server admin is done. It would be great if a server admin could not involve an Azure DevOps Admin every time for such routines.










share|improve this question

















  • 1





    please confirm if you are satisfied with my answer or not. thanks in advance!

    – Eriawan Kusumawardhono
    Mar 27 at 10:26













0












0








0








I have several self-hosted Azure DevOps agents (each installed on a dedicated on-prem server) and I need to perform reoccurring maintenance on them (i.e. patching, etc.). Is there's a good way to define those maintenance windows within Azure DevOps so that server admins could do their job without worrying to interrupt any ongoing build/release task?



There seem to be a setting related to configuring reoccurring maintenance (Organization Settings -> Agent Pools -> <Pool Name>-> Settings [tab]) but it seems as if it would apply to the whole pool and it's hard to tell which of the agents will be considered offline at which time slot.
Unfortunately I couldn't find any documentation about it and not sure if there's something that Azure DevOps would also be doing on the agent machines (i.e. running cleanup, updating agents and so on)



Currently, the process involves a person with admin permissions in Azure DevOps to disable an agent allowing a server admin to perform regular maintenance and to re-enable it back when server admin is done. It would be great if a server admin could not involve an Azure DevOps Admin every time for such routines.










share|improve this question














I have several self-hosted Azure DevOps agents (each installed on a dedicated on-prem server) and I need to perform reoccurring maintenance on them (i.e. patching, etc.). Is there's a good way to define those maintenance windows within Azure DevOps so that server admins could do their job without worrying to interrupt any ongoing build/release task?



There seem to be a setting related to configuring reoccurring maintenance (Organization Settings -> Agent Pools -> <Pool Name>-> Settings [tab]) but it seems as if it would apply to the whole pool and it's hard to tell which of the agents will be considered offline at which time slot.
Unfortunately I couldn't find any documentation about it and not sure if there's something that Azure DevOps would also be doing on the agent machines (i.e. running cleanup, updating agents and so on)



Currently, the process involves a person with admin permissions in Azure DevOps to disable an agent allowing a server admin to perform regular maintenance and to re-enable it back when server admin is done. It would be great if a server admin could not involve an Azure DevOps Admin every time for such routines.







azure-devops azure-devops-self-hosted-agent






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 25 at 8:22









IvanIvan

1




1







  • 1





    please confirm if you are satisfied with my answer or not. thanks in advance!

    – Eriawan Kusumawardhono
    Mar 27 at 10:26












  • 1





    please confirm if you are satisfied with my answer or not. thanks in advance!

    – Eriawan Kusumawardhono
    Mar 27 at 10:26







1




1





please confirm if you are satisfied with my answer or not. thanks in advance!

– Eriawan Kusumawardhono
Mar 27 at 10:26





please confirm if you are satisfied with my answer or not. thanks in advance!

– Eriawan Kusumawardhono
Mar 27 at 10:26












1 Answer
1






active

oldest

votes


















1














Due to the fact that you have your own Azure Pipelines agents, then the maintenance should be easier and you will have total control of either having automatic maintenance or not. If you use Microsoft's hosted agents, you could not update the hosted agents from Microsoft because these agents are maintained by Microsoft exclusively.



The best way to do this is by having more than one agent on one machine instance then organize the agents on one pool. If you have multiple pools, then you can configure Azure DevOps to have different maintenance window schedule on each pool to have different time, and give some time to download and configure itself.



For example, I usually configure the maintenance window on weekend days such as Sunday early morning once a month on certain date. And for any pools I have I gave them intervals of 40 minutes on each pool to have maintenance to give enough time for the agent to download, update and restart itself.



Please consult these documentation further for detailed explanation and use cases:



For Azure DevOps Server:



  1. https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=azure-devops-2019

  2. https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/pools-queues?view=azure-devops-2019

For Azure DevOps Service (on cloud TFS, formerly Visual Studio Team Services):



  1. https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=azure-devops

  2. https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/pools-queues?view=azure-devops





share|improve this answer

























    Your Answer






    StackExchange.ifUsing("editor", function ()
    StackExchange.using("externalEditor", function ()
    StackExchange.using("snippets", function ()
    StackExchange.snippets.init();
    );
    );
    , "code-snippets");

    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "1"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55333695%2frunning-maintenance-on-self-hosted-azure-devops-agents%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    Due to the fact that you have your own Azure Pipelines agents, then the maintenance should be easier and you will have total control of either having automatic maintenance or not. If you use Microsoft's hosted agents, you could not update the hosted agents from Microsoft because these agents are maintained by Microsoft exclusively.



    The best way to do this is by having more than one agent on one machine instance then organize the agents on one pool. If you have multiple pools, then you can configure Azure DevOps to have different maintenance window schedule on each pool to have different time, and give some time to download and configure itself.



    For example, I usually configure the maintenance window on weekend days such as Sunday early morning once a month on certain date. And for any pools I have I gave them intervals of 40 minutes on each pool to have maintenance to give enough time for the agent to download, update and restart itself.



    Please consult these documentation further for detailed explanation and use cases:



    For Azure DevOps Server:



    1. https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=azure-devops-2019

    2. https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/pools-queues?view=azure-devops-2019

    For Azure DevOps Service (on cloud TFS, formerly Visual Studio Team Services):



    1. https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=azure-devops

    2. https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/pools-queues?view=azure-devops





    share|improve this answer



























      1














      Due to the fact that you have your own Azure Pipelines agents, then the maintenance should be easier and you will have total control of either having automatic maintenance or not. If you use Microsoft's hosted agents, you could not update the hosted agents from Microsoft because these agents are maintained by Microsoft exclusively.



      The best way to do this is by having more than one agent on one machine instance then organize the agents on one pool. If you have multiple pools, then you can configure Azure DevOps to have different maintenance window schedule on each pool to have different time, and give some time to download and configure itself.



      For example, I usually configure the maintenance window on weekend days such as Sunday early morning once a month on certain date. And for any pools I have I gave them intervals of 40 minutes on each pool to have maintenance to give enough time for the agent to download, update and restart itself.



      Please consult these documentation further for detailed explanation and use cases:



      For Azure DevOps Server:



      1. https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=azure-devops-2019

      2. https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/pools-queues?view=azure-devops-2019

      For Azure DevOps Service (on cloud TFS, formerly Visual Studio Team Services):



      1. https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=azure-devops

      2. https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/pools-queues?view=azure-devops





      share|improve this answer

























        1












        1








        1







        Due to the fact that you have your own Azure Pipelines agents, then the maintenance should be easier and you will have total control of either having automatic maintenance or not. If you use Microsoft's hosted agents, you could not update the hosted agents from Microsoft because these agents are maintained by Microsoft exclusively.



        The best way to do this is by having more than one agent on one machine instance then organize the agents on one pool. If you have multiple pools, then you can configure Azure DevOps to have different maintenance window schedule on each pool to have different time, and give some time to download and configure itself.



        For example, I usually configure the maintenance window on weekend days such as Sunday early morning once a month on certain date. And for any pools I have I gave them intervals of 40 minutes on each pool to have maintenance to give enough time for the agent to download, update and restart itself.



        Please consult these documentation further for detailed explanation and use cases:



        For Azure DevOps Server:



        1. https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=azure-devops-2019

        2. https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/pools-queues?view=azure-devops-2019

        For Azure DevOps Service (on cloud TFS, formerly Visual Studio Team Services):



        1. https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=azure-devops

        2. https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/pools-queues?view=azure-devops





        share|improve this answer













        Due to the fact that you have your own Azure Pipelines agents, then the maintenance should be easier and you will have total control of either having automatic maintenance or not. If you use Microsoft's hosted agents, you could not update the hosted agents from Microsoft because these agents are maintained by Microsoft exclusively.



        The best way to do this is by having more than one agent on one machine instance then organize the agents on one pool. If you have multiple pools, then you can configure Azure DevOps to have different maintenance window schedule on each pool to have different time, and give some time to download and configure itself.



        For example, I usually configure the maintenance window on weekend days such as Sunday early morning once a month on certain date. And for any pools I have I gave them intervals of 40 minutes on each pool to have maintenance to give enough time for the agent to download, update and restart itself.



        Please consult these documentation further for detailed explanation and use cases:



        For Azure DevOps Server:



        1. https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=azure-devops-2019

        2. https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/pools-queues?view=azure-devops-2019

        For Azure DevOps Service (on cloud TFS, formerly Visual Studio Team Services):



        1. https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=azure-devops

        2. https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/pools-queues?view=azure-devops






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Mar 25 at 8:54









        Eriawan KusumawardhonoEriawan Kusumawardhono

        2,89013238




        2,89013238





























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55333695%2frunning-maintenance-on-self-hosted-azure-devops-agents%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            SQL error code 1064 with creating Laravel foreign keysForeign key constraints: When to use ON UPDATE and ON DELETEDropping column with foreign key Laravel error: General error: 1025 Error on renameLaravel SQL Can't create tableLaravel Migration foreign key errorLaravel php artisan migrate:refresh giving a syntax errorSQLSTATE[42S01]: Base table or view already exists or Base table or view already exists: 1050 Tableerror in migrating laravel file to xampp serverSyntax error or access violation: 1064:syntax to use near 'unsigned not null, modelName varchar(191) not null, title varchar(191) not nLaravel cannot create new table field in mysqlLaravel 5.7:Last migration creates table but is not registered in the migration table

            용인 삼성생명 블루밍스 목차 통계 역대 감독 선수단 응원단 경기장 같이 보기 외부 링크 둘러보기 메뉴samsungblueminx.comeh선수 명단용인 삼성생명 블루밍스용인 삼성생명 블루밍스ehsamsungblueminx.comeheheheh

            155 수학 과학 기타 둘러보기 메뉴eh추가해eh문서를 완성해