Azure DevOps Agent general and enforced administrative task(s)
up vote
0
down vote
favorite
In order to ensure compliance certain task(s) have to be executed either before the build/deployment happens or after they have finished by the agent (private agent pool). These tasks are common for all projects in our account (100s of projects with 1000s of builds) and mandatory. It should NOT be possible for the user (project build administrator) to remove/change it.
Instead of individually adding these "administrative" tasks to each build and release configuration I am looking for a way by which I can force their execution centrally, maybe on the agent with some configuration. Is there such an option available? If not available, can it be developed as an additional plugin?
azure-devops azure-pipelines azure-pipelines-release-pipeline azure-pipelines-build-task azure-pipelines-release-task
add a comment |
up vote
0
down vote
favorite
In order to ensure compliance certain task(s) have to be executed either before the build/deployment happens or after they have finished by the agent (private agent pool). These tasks are common for all projects in our account (100s of projects with 1000s of builds) and mandatory. It should NOT be possible for the user (project build administrator) to remove/change it.
Instead of individually adding these "administrative" tasks to each build and release configuration I am looking for a way by which I can force their execution centrally, maybe on the agent with some configuration. Is there such an option available? If not available, can it be developed as an additional plugin?
azure-devops azure-pipelines azure-pipelines-release-pipeline azure-pipelines-build-task azure-pipelines-release-task
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
In order to ensure compliance certain task(s) have to be executed either before the build/deployment happens or after they have finished by the agent (private agent pool). These tasks are common for all projects in our account (100s of projects with 1000s of builds) and mandatory. It should NOT be possible for the user (project build administrator) to remove/change it.
Instead of individually adding these "administrative" tasks to each build and release configuration I am looking for a way by which I can force their execution centrally, maybe on the agent with some configuration. Is there such an option available? If not available, can it be developed as an additional plugin?
azure-devops azure-pipelines azure-pipelines-release-pipeline azure-pipelines-build-task azure-pipelines-release-task
In order to ensure compliance certain task(s) have to be executed either before the build/deployment happens or after they have finished by the agent (private agent pool). These tasks are common for all projects in our account (100s of projects with 1000s of builds) and mandatory. It should NOT be possible for the user (project build administrator) to remove/change it.
Instead of individually adding these "administrative" tasks to each build and release configuration I am looking for a way by which I can force their execution centrally, maybe on the agent with some configuration. Is there such an option available? If not available, can it be developed as an additional plugin?
azure-devops azure-pipelines azure-pipelines-release-pipeline azure-pipelines-build-task azure-pipelines-release-task
azure-devops azure-pipelines azure-pipelines-release-pipeline azure-pipelines-build-task azure-pipelines-release-task
edited Nov 22 at 14:38
asked Nov 22 at 14:20
zlogo
14
14
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53432963%2fazure-devops-agent-general-and-enforced-administrative-tasks%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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