We are going to deploy our snaps to Snapcraft automatically, but firstly we need a staging server for QA purposes. The main problem is that the QA team builds and publishes and tests the build several times before this particular version will be officially released. It means that we must be able to upload packages that may somehow conflict with the previously uploaded versions during this process.
Usually we host and use our own server, and completely remove all uploaded packages before each iteration.
- Are there any alternative SNAP store (api/v2) implementations that conform snapcraft.io, and that we can use internally?
- Can we use snapcraft.io for these purposes?
- Is there some kind of API to remove or ignore conflicts with previously uploaded packages (we will register a special private snap name for it).
- If not, I think we can create such “a special private snap name” uniqually for each iteration. But it means there can be up to tens or even hundreds of private snaps for each official release. Is it possible?
Of course, we will be ready to unregister & remove them after some time, but AFAIK it cannot be done automatically (without filing a public request).
Thanks in advance!