♻️ Azure Pipeline - Simplify the build process

[Aibono1225]

Cc: @JackDevAU @bradystroud @BrookJeynes @adamcogan

Hi Team,

What code could be improved?

As per my conversation with @JackDevAU, the task "Get History Commits of Each Contributor" is not relevant to the project build. We should move it from the Production & Staging pipeline to UpdateRulesHistory. This will help us reduce the build time by 3 to 4 mins.

Tasks

• Remove the task from the build pipeline
• Add it to the UpdateRulesHistory pipeline

Screenshots

Thanks!

[Aibono1225]

Update 04/02/2024:

The task Get History Commits of Each Contributor involves creating a static file commits.json during the Build Pipeline, therefore it cannot be easily moved from one pipeline to another. 🙁
Note: the file commits.json is used for Rules.Widget v1 and users' rule page.

Option A:

Like we did with history.json, in the UpdateRulesHistory pipeline, we store all data for commits.json in the CosmosDB. Then in the Build Pipeline we use an API to get the data and create the json file.

Option B:

Keep the pipeline as it is.

[JackDevAU]

Hi @Aibono1225

As per our conversation, let's talk to @wicksipedia, @william-liebenberg or @GordonBeeming to see if they have some ideas how we can simplify this build process.

[JackDevAU]

Hey @Aibono1225

Whats the progress on this?

[Aibono1225]

Update 11/03/2024:

As per my conversation with @wicksipedia , there is another approach to deal with this issue:

Option C:

Separate the task Get History Commits of Each Contributor from the build pipeline. Ideally move it to GitHub Actions for safer token use. Combine the result of both processes into 1 artifact before release.