Dennis,
Thanks for replying. We are using SVN. The exact ECO process for this project is under construction as it is a relatively new project and deployments will be at our customer's site. We use JIRA for tracking specific change requests.
Here's an example of our basic process:
- Software changes made (according to JIRA tasks) and source code checked in
- Builds released per schedule with version numbers (from JIRA projects) hard-coded into the application
- Builds deployed at different locations & times
Here's what I'd like to see to improve things:
- Builds released with version numbers generated from one of the following:
1. Loaded from JIRA release numbers - maybe auto-generated for reference by LabVIEW when building the application
2. Part of a custom build launcher
>> This would be a custom interface that runs functions like those in Application Builder palette while also sending version info
>> Perhaps it could prompt the user for version info or read from something auto-generated.
- Builds should automatically make version numbers visible within the application (for example, LabVIEW has the Help>>About window)
- Build numbers should be programmatically/dynamically accessible without having to install an additional .NET framework that isn't listed in 'Additional Installers'
Curious if there are any tools that support these kinds of things. I am aware of Deploy by Wirebird Labs and Proligent by Averna, although I am lacking in knowledge about specific features.
Regards,
Dan