Looks like a few more stories before the 0.57 release marker. Is there any hope we'll get the new garden release before the weekend? (Preferably with a day to test it out. :p)
xoebus
We're hoping so
The garden team have been super fast at fixing our issues
So we may get that out on Thursday
I need to check on the progress of the other track
It'll be tight with the shorter week
mhoran
Cool.
We're using the bosh deployment resource to test out our stacks against cf-release. We'd like the resource to upload --rebase. Would this not be desired, or perhaps it could be an option? We don't really want to have to track the cf-release version numbers and bump them when we make our stack modifications.
I guess our version doesn't have to match cf-release. Maybe?
zachgersh_ joined the channel
flavorjones_ joined the channel
squeedee_ joined the channel
cppforlife__ joined the channel
cppforlife_ has quit
mmb has quit
zachgersh has quit
willpragnell has quit
alexsuraci has quit
squeedee has quit
zachgersh_ is now known as zachgersh
flavorjones_ is now known as flavorjones
cppforlife__ is now known as cppforlife_
mmb joined the channel
willpragnell joined the channel
alexsuraci joined the channel
alexsuraci
mhoran: we won't be adding --rebase; it's a pretty janky bosh feature that last i heard they're planning to remove once there are better options. which i think there are now.
the version can be whatever you want (that's what --rebase does; it creates its own version based on the current latest)
one trick is to just version it as a unix timestamp
mhoran
Okay. Cool.
alexsuraci
i.e. create release --version 0.0.$(date +"%s") or whatever it is
mhoran: are you testing against non-final cf releases?
mhoran
Yeah; acceptance-passed.
Timestamp sounds reasonable.
We use timestamps elsewhere. I was definitely over thinking this one
alexsuraci
in an ideal world there would be final releases coming out of runtime's pipeline much more frequently
having everyone create their own cf-release is a nightmarish hellscape
mhoran
Our use case is a bit weird. We're taking over rootfs and need to test that against the release. So we have to create a release anyway.