New Pipeline for Regular Task Builds

[dassayantan24]

Context

Our courtesy push pipeline doesn’t build every task regularly, which may cause gaps in component governance for tasks that haven’t been built for a long time. The idea is to have a pipeline that runs daily and builds all tasks.

---

Task Name

N/A

---

Description

• onboadring new yaml for new pipeline to build all tasks
• tasks we only get from UI or build all tasks with
• component governance is auto injected as per the 1es template

---

Risk Assessment (Low / Medium / High)

No

---

Change Behind Feature Flag (Yes / No)

No

---

Tech Design / Approach

• Design has been written and reviewed. - Yes
• Any architectural decisions, trade-offs, and alternatives are captured. - yes

---

Documentation Changes Required (Yes/No)

Indicate whether related documentation needs to be updated. No

• User guides, API specs, system diagrams, or runbooks are updated. No

---

Unit Tests Added or Updated (Yes / No)

Indicate whether unit tests were added or modified to reflect these changes. No

---

Additional Testing Performed

List all other tests performed (manual or automated, including integration, regression, scenario tests, etc.).

---

Logging Added/Updated (Yes/No)

• Appropriate log statements are added with meaningful messages.
• Logging does not expose sensitive data.
• Log levels are used correctly (e.g., info, warn, error).

---

Telemetry Added/Updated (Yes/No)

• Custom telemetry (e.g., counters, timers, error tracking) is added as needed.
• Events are tagged with proper metadata for filtering and analysis.
• Telemetry is validated in staging or test environments.

---

Rollback Scenario and Process (Yes/No)

• Rollback plan is documented.

---

Dependency Impact Assessed and Regression Tested (Yes/No)

• All impacted internal modules, APIs, services, and third-party libraries are analyzed.
• Results are reviewed and confirmed to not break existing functionality.

---

Checklist

• Related issue linked (if applicable)
• Task version was bumped — see versioning guide
• Verified the task behaves as expected

[dassayantan24]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[tarunramsinghani]

We should not have option here to build specific tasks at all. the only option should be to build all tasks always.

we should instead add option to have list of deprecated tasks that can be skipped if needed, or it should pick the list of deprecated tasks from the repo itself may be, the list is available currently in https://github.com/microsoft/azure-pipelines-tasks/blob/master/DEPRECATION.md

[dassayantan24]

list of deprecated tasks that I can try to add, but can’t we keep the build-specific tasks at least for now? This is because testing the pipeline initially with all tasks will take around 9 hours

[tarunramsinghani]

Can we use any existing template file for build all taks like https://github.com/microsoft/azure-pipelines-tasks/blob/master/ci/build-all-tasks.yml ??