Do you Check-in your process template into source control? (legacy)
Updated by Brady Stroud [SSW] 1 year ago. See history
123
<asideEmbed
variant="info"
body={<>
**For Azure DevOps Server (and old TFS servers)**
**Note:** If using Azure DevOps (cloud) then you have no method of tracking changes to the Process Template.
</>}
figureEmbed={{
preset: "default",
figure: 'XXX',
shouldDisplay: false
}}
/>
The customized process template is a very important asset for your team, you should use Source Control to store the work-in-progress template so you can track the changes and avoid mistakes.
<imageEmbed alt="Image" size="large" showBorder={false} figureEmbed={{ preset: "default", figure: 'customized process template in source control', shouldDisplay: true }} src="/uploads/rules/do-you-check-in-your-process-template-into-source-control/CheckInTemplateIntoSourceControl.png" />You should also keep a version history log in ProcessTemplate.xml so you can track the deployed version easily.
Figure: ProcessTemplate.xml with version history log
Categories
Acknowledgements
Related rules
Need help?
SSW Consulting has over 30 years of experience developing awesome software solutions.