spontoreau / rust-azure-devops

[No longer maintain] 🦀 Rust extension for Azure DevOps

Hi 🖖

My name is Sylvain, I'm a french software developer for almost 14 years. For the past six years I have focused on TypeScript, a language I love and which has allowed me to write the french book 📖 "TypeScript - Notions fondamentales". On the community side, I'm co-organizing the Paris TypeScript meetup with some friends and I'm also Microsoft MVP in the Developer Technologies category!

I have been passionate about web development since the beginning of my career, especially on the backend side. I enjoy crafting web services using my favorite patterns: CQRS and Event Sourcing. I also like Agile methodology, eXtreme Programming approach and Behavior Driven Development. On the cloud side I'm an AWS afficionado especially Serverless services like Lambda, DynamoDB, Event Bridge, ... Also I'm really a huge fan of CloudFormation ! I like using CDK for my Infra as Code and with GitHub Actions it's my favourite combination 😎

rust-azure-devops's Issues

Collaborate with crate-ci's efforts on azure pipeline support?

I've started work on some templates within crate-ci which is meant to be an unofficial official collaboration point for CI documentation and tools. Going the route of tasks seems like it'd be better and looks like you've already started on it!

Feel free to join the discussion at https://github.com/crate-ci/resources/issues/2

Cargo build command: Advanced option to build a release version

Currently you can do that by adding "--release" inside the options field. It can be a checkbox instead!

Related to #9

Cargo all commands - ability to specify working directory

My rust project isn't at the root directory of my repo. As such, the ability to specify the working directory to run cargo is important.

Right now, I use the a powershell script to do each of the cargo commands I need in this fashion:

steps:
- powershell: . 'path/to/build-script.ps1' '-build' 'path/to/project' 
  displayName: Build

Cargo/Rustc/Rustup: Advanced option to enable verbose output

Avaiable by adding "--verbose" inside the options field. It can be a checkbox instead!

Change VSTS to Azure DevOps

VSTS is now Azure DevOps. Documentation have to be updated

Cargo test command: Publish test results

Test command need to be able to publish test results in Azure Dev Ops.

Related to #9

YAML build definition for continuous integration

Definition needs to be inside the repository!

Cargo task: Commands

Cargo commands have to be available as a dropdown list in order to be more user friendly.

Commands value:

• Build
• Test
• Custom

Task/Input names for YAML

Task & Input names need to be changed to be more relevant for YAML file.