chore(build): Provide multiple build jobs. Closes #150

[SamVanhoutte]

Add multiple stages & jobs:

• Prerequisites
• UnitTests
• PackageAndRelease

[netlify]

✔️ Deploy Preview for arcus-azureml ready!

🔨 Explore the source changes: 4261488

🔍 Inspect the deploy log: https://app.netlify.com/sites/arcus-azureml/deploys/61bc7037d0ce940007a65039

😎 Browse the preview: https://deploy-preview-153--arcus-azureml.netlify.app

[SamVanhoutte]

Build seems to fail, because of dependencies installed in first stage, not being found in the second stage.
Is this because they could be seperate machines?

[stijnmoreels]

Build seems to fail, because of dependencies installed in first stage, not being found in the second stage. Is this because they could be seperate machines?

Yeah, but if you can install them locally into a build artifact you can pass along them to the next stage. Our other Arcus repo's all have this approach. We'll see.

[stijnmoreels]

Great to have some more separation and consistency with the Arcus repo's. I'm wondering if the other Python ML package uses the same (almost the same) setup for building; and if so, we could move it to our general Azure DevOps YAML templates repo instead of manually having all the script commands here.

Also, we should update the release pipeline too, right?

[SamVanhoutte]

@stijnmoreels release build is updated.
Issues arcus-azure/azure-devops-templates#50 and arcus-azure/azure-devops-templates#51 created for the template generation

[stijnmoreels]

@stijnmoreels release build is updated. Issues arcus-azure/azure-devops-templates#50 and arcus-azure/azure-devops-templates#51 created for the template generation

Great! 👍

[stijnmoreels]

We can always look further into why the build and tests jobs needs to be in the same stage, but for a first run, I think this is good. @ALaks96 , what do you think?

[stijnmoreels]

Great first improvement on this 💯