Generic package limitations
Proposal
We are hoping to starting using the new generic package feature to store CI artifacts as part of our release management. However we've come across a few issues/limitations which make it difficult to start using it fully.
The key issues we're seeing at the moment are:
- Inflexible version numbering (e.g. can't use 4th digit or semantic names - see also #273034 (closed)).
- The same file can be duplicated (as opposed to replaced) which can lead to confusion or the wrong file being downloaded.
- Packages allow files to be added liberally, with no real control, but can't be locked, replaced or overwritten.
- The package history does not record changes made after initial creation of the package, e.g. if a file is added or replaced.
- Other than uploading a single compressed file, it's not easy to see how files could be easily downloaded later for use in a release; it seems that each file would need to be downloaded separately (see also #273743).
It's really great to see an artifacts feature in GitLab as this will save connecting different systems into the development toolchain. However, it seems that the current solution needs a bit more development before it will become truly useful.
Apologies if this hasn't been raised in the right place/format, this is the first time I've raised an issue on GitLab.
Edited by Matt Page