| Summary: | ASTERISK-27492: Testsuite: Create a branching structure | ||
| Reporter: | Kevin Harwell (kharwell) | Labels: | |
| Date Opened: | 2017-12-19 09:41:26.000-0600 | Date Closed: | 2018-04-12 18:33:39 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Tests/testsuite |
| Versions: | GIT | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | See discussion [here|http://lists.digium.com/pipermail/asterisk-dev/2017-December/076679.html]. Create a branching system for the testsuite. This should include (some of these can, or might need to, be broken out into their own issue):
1) The creation of a "legacy" branch in order to stay backward compatible with older Asterisk branches. 2) The creation of branches associated with Asterisk branches (for instance 13 testsuite branch is associated with 13 Asterisk branch, etc...) 3) Update mkrelease script to also create a tag in the testsuite for each associated released Asterisk branch. 4) Update jenkins to use the new structure. 5) (This last one might need to be broken out into its own issue?) Remove the versioning information embedded in testsuite from the various branches where it makes sense. | ||
| Comments: | By: Kevin Harwell (kharwell) 2018-04-12 18:33:31.074-0500 All tasks pretty much completed for this issue. The testsuite now has branching. Note, for step 5: for each branch I removed tests that would not run on a given branch due to not being supported on that version. Initially though we were going to leave the version information in the tests themselves and the python code at least for now. However [~coreyfarrell] took up the mantel and has removed all the versioning from the testsuite. Thanks Corey! | ||