Timeline for What is an artifact repository?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Nov 15, 2019 at 9:09 | history | suggested | Cameron Kerr | CC BY-SA 4.0 |
Remove potential confusion of conflating 'container' and 'image'
|
| Nov 15, 2019 at 3:42 | review | Suggested edits | |||
| S Nov 15, 2019 at 9:09 | |||||
| Nov 1, 2017 at 12:23 | comment | added | tutuca | Does it makes sense to also keep track of configuration files or fixtures in these kind of repositories? | |
| Mar 10, 2017 at 19:55 | vote | accept | Dave Swersky | ||
| Mar 10, 2017 at 15:39 | comment | added | Pierre.Vriens♦ | merci, but just in case, here is your chance to further address my additional comment ... | |
| Mar 10, 2017 at 15:19 | comment | added | SztupY | @Pierre.Vriens added some small comments, but maybe it can be addressed in a separate Question as well | |
| Mar 10, 2017 at 15:19 | history | edited | SztupY | CC BY-SA 3.0 |
Adressing comments
|
| Mar 10, 2017 at 8:59 | comment | added | Tensibai | May worth adding the 'channel' capability over the Versionning support, having the ability to have some machine targeting the latest release in channel "develop" and prod machine targeting a specific version in channel "stable". | |
| Mar 9, 2017 at 16:18 | history | edited | SztupY | CC BY-SA 3.0 |
added 418 characters in body
|
| Mar 9, 2017 at 16:13 | history | answered | SztupY | CC BY-SA 3.0 |