This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author xtreak
Recipients paul.moore, steve.dower, tim.golden, vstinner, xtreak, zach.ware
Date 2018-09-05.09:48:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1536140889.84.0.56676864532.issue34575@psf.upfronthosting.co.za>
In-reply-to
Content
Another way will be to invalidate the cache by manually updating cleanup-cache.txt in the end. But this requires a commit that has to be reverted later to enable caching and I don't think it's worthy to pollute git history for this.

https://help.appveyor.com/discussions/questions/1310-delete-cache#comment_36916917


> You can have any file as dependency that will be triggering cache invalidation, even "cleanup-cache.txt" say in the root of your repo:
> cache:
>     - my_cached_folder -> cleanup-cache.txt
> Whenever CRC32 of cleanup-cache.txt is changed the cache is invalidated, i.e. not restored in the beginning of the build.

@paul.moore It's here : https://github.com/python/cpython/blob/master/.github/appveyor.yml


Thanks
History
Date User Action Args
2018-09-05 09:48:09xtreaksetrecipients: + xtreak, paul.moore, vstinner, tim.golden, zach.ware, steve.dower
2018-09-05 09:48:09xtreaksetmessageid: <1536140889.84.0.56676864532.issue34575@psf.upfronthosting.co.za>
2018-09-05 09:48:09xtreaklinkissue34575 messages
2018-09-05 09:48:09xtreakcreate