It is vital in a Release Management to move your changes into different stages of the development lifecycle (Dev-->QA-->Staging-->Production) and move the stable code into the Production environment to create an effecient and a quality software. In Jiffy, there could arise a situation where the Dev and QA environments could be in one Jiffy machine and the staging and Production environments could be altogether in a different machine. This should, though, not hamper the movement of the stable code going from one environment to another. Jiffy provides an import and export feature where you could export, say, the example Task (CSS_Dev_Scenario_1) from QA environment to a Staging environment in another setup. We will now see how this is carried out in Jiffy.
Jiffy provides an Export facility at two levels. You can export either from the Task level or at the Release level. We will export our example Task from the QA_Release to Staging_Release, by performing one of the below:
Once you click on the
Export button, Jiffy will download a
.zip file which consists of the Task that we are exporting.
The next logical step is to import this Task into the Staging Release. To achieve this, in our example, select the Staging_Release and click on
+Add Task and click on
Import from File, as highlighted below:
The import wizard opens up where, by default not only do you have an option to import a Task from the .zip file that we created and saved on our system, but can additionally import the various central repository files (xml, csv, JSON,..), templates, UI Controls, any reusable components and the configurations of the imported Task. The wizard driven import Tasks makes it easy for the users to work with the import feature. The wizard driven approach is as shown below:
Click
Next
Click
Next
Click
Next
Click
Next
Click
Next
Click
Next
Click
Next
Click on
Save. This will create a new Task in the Staging_Release, as shown below:
To see the version management of this Task, you can go to
Repository-->
SCM Repository from the main page, which will display the versions of the Task in the Staging Release, as shown below:
