Job versions
Mostly software development is an iterative process. Within a project, developers will iterate through a develop and test cycle until the software is ready to be put into production use. We can also think of an iterative process across projects; release 1 is deployed and is used for a period of time, but some enhancements or amendments are needed, so another project is undertaken and, at the end of this, release 2 is deployed into the wild. This process may go on for many years!
In order to support these iterative processes, the software is versioned to keep track of the code and components that constitute a given release. While the Studio does not contain a full-featured version control system, it does have some features which allow developers to manage software versions.
As we have been developing jobs in the previous chapters, you may have noticed that the Studio adds a version number to the end of the job name that we define. You can see this in the Repository view of jobs...
