Feature #4199
ci: Read-only config file
| Status: | Closed | Start date: | 07/31/2013 | |
|---|---|---|---|---|
| Priority: | Medium | Due date: | ||
| Assignee: | Ilias Tsitsimpis | % Done: | 100% |
|
| Category: | synnefo-ci | Spent time: | - | |
| Target version: | 0.15 |
Description
Do not update the configuration file, because:
1) is tracked by the repository
2) The order of sections/options changes.
Use a different method for finding the temporary configuration file. (e.g. a build serial ?)
Associated revisions
ci: Temporary_config supports multiple machines
Use one temporary_config that will contain information
about every machine we have build until now, so we
can go back and use/inspect one of them.
Refs #4199
ci: Temporary_config supports multiple machines
Use one temporary_config that will contain information
about every machine we have build until now, so we
can go back and use/inspect one of them.
Refs #4199
ci: Temporary_config supports multiple machines
Use one temporary_config that will contain information
about every machine we have build until now, so we
can go back and use/inspect one of them.
Refs #4199
History
#1 Updated by Christos Stavrakakis about 10 years ago
To elaborate more on the build serial:
You can have a prefix for the created instances, and the final name can be the prefix + the serial. e.g.: snf-ci-42.
Then you can have a directory holding the necessary configuration for each build, e.g. /tmp/snf-ci-builds/42.
If you have this, then you can run steps for previous builds, e.g. snf-ci burnin --serial=40.
#2 Updated by Ilias Tsitsimpis about 10 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
ci: Temporary_config supports multiple machines
Use one temporary_config that will contain information
about every machine we have build until now, so we
can go back and use/inspect one of them.
#3 Updated by Ilias Tsitsimpis almost 10 years ago
- Status changed from Resolved to Closed