<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ticket search results</title><link>https://forge-allura.apache.org/p/allura/tickets/</link><description>You searched for labels:"code-snapshots"</description><language>en</language><lastBuildDate>Mon, 24 Sep 2018 19:36:21 -0000</lastBuildDate><item><title>Better progress indicator for snapshot generation</title><link>https://forge-allura.apache.org/p/allura/tickets/6144/</link><description>Had a user that thought snapshot generation of [the ascom svn repository](/p/ascom/code/) was hanging because it was taking a very long time. Turns out, (based on the size of the download I was finally offered later) the repo is just very large (~17GB iirc). A repo that size is understandably going to take a while to generate, but it would be nice if we could have a better indicator for that.

This may not be *as* necessary once [#6070] is done though, since a partial repo won't be quite so large.

Alternatively, we may want to consider if we even want to serve snapshots that size.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Sun, 22 Feb 2015 20:59:30 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6144/</guid></item><item><title>Make code snapshots based on directory</title><link>https://forge-allura.apache.org/p/allura/tickets/6070/</link><description>It'd be nice to make code snapshots for the given path instead of the whole directory.  This is *especially* true of SVN where you'd want a snapshot of trunk but not all the branches &amp; tags directories.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 24 Sep 2018 19:36:21 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6070/</guid></item><item><title>Change code snapshots to zip files</title><link>https://forge-allura.apache.org/p/allura/tickets/6069/</link><description>Our .tar.gz files aren't opening properly on windows, and zip files are easier to open on windows anyway.  So let's change to generate .zip files.  And test that they open fine on Windows.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6069/</guid></item><item><title>Make symbolic refs work for snapshots for Hg and SVN</title><link>https://forge-allura.apache.org/p/allura/tickets/6046/</link><description>Symbolic refs work in code snapshot links for git repositories, e.g. http://sourceforge.net/p/allura/git/ci/master/tarball, but not for Hg or SVN.  They appear to partially work, in that a snapshot file is generated, but either the URL or the file name end up using the non-symbolic commit ID.

All three should probably be normalized to use the non-symbolic commit ID so that caching works properly (the code for "master" will change, so the cached allura-git-master.tar.gz file will be out of date), probably by making http://sourceforge.net/p/allura/git/ci/master/tarball redirect to the non-symbolic URL in case there is a push while waiting for the file to be complete.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Cory Johns</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:52 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6046/</guid></item></channel></rss>