Create azure-pipelines_maven_cached_ua.yml

[ghost]

Create a cached UA Maven example for Azure DevOps.

[samq-ws]

@lukebroganws Can you explain where in the script the UA is being pulled from a cache? I do not see it anywhere

[ghost]

Hey @samq-ws - this script is designed the same way as the following example in GitLab:
https://github.com/whitesource-ft/ws-examples/blob/main/CI-CD/GitLab/gitlab-maven-cached-ua.yml

The script simply queries the UA repository of releases, taking the date of the last released UA and then compares it to the existing JAR in the pipeline, if a newer date exists, a new UA is downloaded. If there is no UA, it will simply download the latest one.

[samq-ws]

Hey @samq-ws - this script is designed the same way as the following example in GitLab: https://github.com/whitesource-ft/ws-examples/blob/main/CI-CD/GitLab/gitlab-maven-cached-ua.yml

The script simply queries the UA repository of releases, taking the date of the last released UA and then compares it to the existing JAR in the pipeline, if a newer date exists, a new UA is downloaded. If there is no UA, it will simply download the latest one.

Let's take this offline as this is not caching the UA. It is just updating a previously existing UA. The PS team has already created a utility for this, so I'd like to take this offline and understand why we are duplicating efforts.

[tidharm]

@lukebroganws, @samq-ws, I'd like to close this PR, and if needed, migrate it into a new PR in mend-toolkit/mend-examples.

Where are we in this discussion? Do we agree on the need for this example and on its validity?
Should I copy these changes to a new PR in the new org, or close this PR without further action?