For my project I realised that requirements are more tightly bound to code changes while issues may likely be around documentation, lack of training etc so I used github features to tackle customer side of things while actual product development was kept on TFS.īoth github and TFS can achieve this on its own so no point in mixing them if you dont need to. The problem in using both is that you are splitting up the code flow and issue/requirement flow. Slight automation and assignment for keeping things under SLAs.Note: that the name of the Compute Instance needs to be unique across the region for all customers.
Create a Compute Instance through the Azure Machine Learning studio. Customer has multiple branches and can raise a request from anywhere in the world using email that creates a github issue and label it accordingly. Create a Compute Instance and prepare it to use R with Visual Studio Code for an interactive session.A placeholder repo to keep bug and issues on existing releases.Backlog is built with in this and tracking of work items is performed here.Was already integrated into client other developments and staff was comfortable managing it so kept requirements and work items there.As you have not written much about what your aim is to achieve from both i have used them to get these benefits.
0 kommentar(er)
