Re: Warning: Incoming Docker Hub rate limits are going to negatively impact CouchDB CI workflows

2020-10-29 Thread Joan Touzet
Following up, I've implemented a new Jenkins job that re-pulls all current couchdbdev images on each docker node every night. The job takes 12 minutes to run. Once a week, it also runs the "pull them all" set of images I mentioned a few months ago, to keep our images on Docker Hub from disapp

Re: A problematic side effect of archiving branches

2020-10-29 Thread Joan Touzet
On 2020-10-29 11:08 a.m., Ilya Khlopotov wrote: Why not just lay down a new tag on main to work around this? Good idea. This could work. We would need to do it for each dependency if we archived branches on it. I have only archived branches on apache/couchdb . I was planning on doing faux

Re: A problematic side effect of archiving branches

2020-10-29 Thread Ilya Khlopotov
> Why not just lay down a new tag on main to work around this? Good idea. This could work. We would need to do it for each dependency if we archived branches on it. On 2020/10/29 14:32:17, Joan Touzet wrote: > Hi Ilya, > > Sorry about this trouble. Based on this feedback I will not pursue >

Re: A problematic side effect of archiving branches

2020-10-29 Thread Joan Touzet
Hi Ilya, Sorry about this trouble. Based on this feedback I will not pursue removal of our release branches. On 2020-10-29 5:56 a.m., Ilya Khlopotov wrote: ❯ git describe --always --tags archive/prototype/fdb-layer-get-doc-spans-580-gdfb27b48a but: $ git checkout 3.x Branch '3.x' set up t

Re: A problematic side effect of archiving branches

2020-10-29 Thread Jan Lehnardt
yikes, okay, never mind :D this just sounded simpler than “patching rebar” Best Jan — > On 29. Oct 2020, at 11:18, Ilya Khlopotov wrote: > > The negative refspec is a recent addition to git. They are available only > since 2.29. Which was released less then 2 weeks ago. > > On 2020/10/29 10

Re: A problematic side effect of archiving branches

2020-10-29 Thread Ilya Khlopotov
The negative refspec is a recent addition to git. They are available only since 2.29. Which was released less then 2 weeks ago. On 2020/10/29 10:09:13, Jan Lehnardt wrote: > This won’t help you if you already `fetch`’d, but how about suggesting a git > config that folks can apply locally that

Re: A problematic side effect of archiving branches

2020-10-29 Thread Jan Lehnardt
This won’t help you if you already `fetch`’d, but how about suggesting a git config that folks can apply locally that adds a fetch ref spec that excludes `archive/`? > On 29. Oct 2020, at 10:56, Ilya Khlopotov wrote: > > Hello, > > As you've probably know, recently old branches were archived.

A problematic side effect of archiving branches

2020-10-29 Thread Ilya Khlopotov
Hello, As you've probably know, recently old branches were archived. I tried to build a new release locally and was very surprised that it couldn't start. After scratching my head for few hours I figured out the following. I used `git fetch` command without specifying specific branch. This cause