New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Atomic switching between published snapshots #8

Closed
msiebuhr opened this Issue Mar 14, 2014 · 4 comments

Comments

Projects
None yet
3 participants
@msiebuhr
Copy link

msiebuhr commented Mar 14, 2014

There seem to be a small hole when switching from publishing one snapshot to another on the same url. Ex:

aptly publish snapshot -distribution=dev-testing dev-testing-20130314-140332
... add new package to dev-testing and make a new snapshot ...
aptly publish drop dev-testing
aptly publish snapshot -distribution=dev-testing dev-testing-20130314-145115

Between the last two commands there is a small period of time where the dev-testing repository doesn't exist. If a server happen to be checking the repository at that time, it will fail.

While I have only browsed the source cursory, it does seem it would be possible to implement a publish swtich-snapshot command, that I believe should roughly consist of:

  1. Add any packages added by the new snapshot
  2. Update repository meta-data
  3. Remove existing packages not referenced in the new snapshot.

@smira smira added the enhancement label Mar 14, 2014

@smira smira added this to the v0.5 milestone Mar 14, 2014

@smira

This comment has been minimized.

Copy link
Member

smira commented Mar 14, 2014

Hm, I like this idea a lot... Thanks, @msiebuhr, I think it's worth including in next version.

I was also thinking about situation when you publish "automatically" some local repo as it changes (skipping the snapshot phase), for example with testing local repo snapshot could even be extra step which is not required.

@msiebuhr

This comment has been minimized.

Copy link

msiebuhr commented Mar 14, 2014

I was also thinking about situation when you publish "automatically" some local repo as it changes (skipping the snapshot phase), for example with testing local repo snapshot could even be extra step which is not required.

That's one of the pain-points we've been looking at (and wondering a bit about).

Split into #10.

@smira smira modified the milestone: v0.5 Mar 14, 2014

smira added a commit that referenced this issue Apr 8, 2014

smira added a commit that referenced this issue Apr 15, 2014

smira added a commit that referenced this issue Apr 21, 2014

smira added a commit that referenced this issue Apr 22, 2014

smira added a commit that referenced this issue Apr 22, 2014

Re-publishing for local repositories. #8
Cleanup part is missing.

smira added a commit that referenced this issue Apr 22, 2014

smira added a commit that referenced this issue Apr 22, 2014

smira added a commit that referenced this issue Apr 22, 2014

smira added a commit that referenced this issue Apr 22, 2014

smira added a commit that referenced this issue Apr 22, 2014

smira added a commit that referenced this issue Apr 22, 2014

smira added a commit to aptly-dev/aptly-bash-completion that referenced this issue Apr 22, 2014

smira added a commit to aptly-dev/aptly-dev.github.io that referenced this issue Apr 22, 2014

smira added a commit to aptly-dev/aptly-bash-completion that referenced this issue Apr 22, 2014

smira added a commit that referenced this issue Apr 22, 2014

smira added a commit to aptly-dev/aptly-dev.github.io that referenced this issue Apr 22, 2014

@smira

This comment has been minimized.

Copy link
Member

smira commented Apr 22, 2014

This should be done. Expect 0.5 really soon!

@smira smira closed this Apr 22, 2014

@JensRantil

This comment has been minimized.

Copy link

JensRantil commented Apr 23, 2014

👍

sliverc pushed a commit to sliverc/aptly that referenced this issue Nov 21, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment