| *** rdale has quit IRC | 03:31 | |
| *** gtristan has joined #baserock | 04:39 | |
| gtristan | :-/ | 06:07 |
|---|---|---|
| * gtristan notices that ybd MR 300 was merged differently than what he originally saw | 06:08 | |
| gtristan | instead of a 'sha:' field, there is now a 'tree:' field | 06:08 |
| gtristan | I dont know what to do with a 'tree:' field, I need a 'sha:' | 06:08 |
| gtristan | fwiw: http://paste.baserock.org/omugedihib | 06:20 |
| gtristan | There's nothing you can really do with a tree sha, except "know it", it's just not useful beyond that. | 06:21 |
| gtristan | odd, ok the code looks like it's doing (both ?) but maybe I encountered a bug | 06:24 |
| gtristan | cause shas are just not coming up in the saved definitions.yml | 06:24 |
| * gtristan palmface | 06:25 | |
| gtristan | ${target}.yml, case closed | 06:25 |
| gtristan | This line is a bit confusing: https://gitlab.com/baserock/ybd/blob/master/ybd/cache.py#L188 | 06:38 |
| gtristan | It updates the output ${target}.yml with ref: ${unpetrify-ref}... so it says, yet the ${target}.yml has the loaded ref in ref as expected | 06:38 |
| * paulsherwood waves | 06:48 | |
| paulsherwood | gtristan: that may be a bug | 06:49 |
| paulsherwood | update_manifest is only reporting - i didn't touch it when making the #300 change, so it may be reporting the wrong thing now | 06:50 |
| * paulsherwood thinks there are a couple of things wrong with the manifest stuff | 06:51 | |
| paulsherwood | while i'm on i can explain the use-case - i wonder if you've thought of it for bst | 06:51 |
| paulsherwood | - user generates a new release of a stack | 06:52 |
| paulsherwood | - last 'release' may be last definitions commit, or last tag, or some other ref | 06:53 |
| paulsherwood | - needs to provide (as part of the release) a list of all component changes since last release | 06:53 |
| paulsherwood | - for all components which have *not* changed, may need to generate a statement to that effect, or just not report on them | 06:54 |
| paulsherwood | - for components which have changed, the format of the change list ideally would be configurable | 06:55 |
| paulsherwood | so ybd has a release-cmd: setting which allows us to configure what is generated for the delta | 06:56 |
| *** gtristan has quit IRC | 06:56 | |
| paulsherwood | in other news, how would you feel about supporting tree instead of commit in the cache-key *as an option* | 06:57 |
| paulsherwood | there's no need for all users to share the same cache-key alg version/options | 07:02 |
| *** gtristan has joined #baserock | 08:43 | |
| gtristan | paulsherwood, I lost power and went off to eat lunch... I was wondering in the mean time, maybe we can ditch the manifest entirely ? It seems to me that if we fill in some blanks in the generated file with MR 300, whatever it is people do with manifests, they could also do with that file no ? | 08:46 |
| * gtristan got lost a bit with manifests | 08:46 | |
| gtristan | back to cache-key again, I'm not entirely averse to adding the option, but I *really* think its going to be a nearly worthless optimization | 08:49 |
| gtristan | paulsherwood, I would rather live with commit sha for a while without adding extra noise - and if it *does* turn out to be an optimization worth doing, then so be it | 08:50 |
| gtristan | *however*, if we do that optimization, the tree sha should additionally be recorded in project metadata (this can be automated with the `bst track <target>` feature) | 08:51 |
| gtristan | i.e.: rule of thumb, you never need gits, or network connectivity, to calculate cache keys | 08:52 |
| gtristan | regarding release management and deltas; I'm not convinced it should be implemented by the tool itself (I'm not sure the tool should have any knowledge of what your last "release" was) | 08:56 |
| gtristan | And certainly, storing your project does not require a particular type of VCS, it's project data; can be stored in a tarball, or in CVS for all the tool should care | 08:57 |
| gtristan | that said, the intent of the --format option to `bst show` is to allow powerful scripting around it | 08:58 |
| *** toscalix has joined #baserock | 08:58 | |
| gtristan | the hope is that whatever additional stuff (like release management) should be easily scriptable | 08:58 |
| gtristan | morning toscalix | 08:59 |
| gtristan | toscalix, I looked at your slides, is there any recording ? | 09:00 |
| toscalix | I believe so but not sure | 09:00 |
| toscalix | I would have to ask gary | 09:00 |
| toscalix | hopefully in a few days the vm will be ready | 09:01 |
| toscalix | the idea is t present it at ELC | 09:01 |
| gtristan | ah, maybe I should wait for the big show :) | 09:02 |
| gtristan | when is that ? | 09:02 |
| toscalix | in two weeks | 09:05 |
| toscalix | i would suggest you to wait because we are fixing a couple of issues that prevent lava from testing | 09:06 |
| gtristan | ah, ok let me know :) | 09:06 |
| toscalix | I will | 09:06 |
| gtristan | I was interested last time you gave the similar talk in Manchester :) | 09:06 |
| toscalix | it has taken us very long to finish this. It was complicated though. A lot of different technologies involved. | 09:07 |
| *** toscalix has quit IRC | 09:13 | |
| paulsherwood | for those who haven't seen the slides, what is 'this'? | 09:32 |
| gtristan | kernel CI, and testing in general | 09:41 |
| paulsherwood | ack | 09:42 |
| paulsherwood | gtristan: how close are you to a bst that i could run to build (say) current baserock definitions? | 09:43 |
| gtristan | paulsherwood, I put the conversion script on the side (although it's a good start so far, MR 300 helps a lot), would need to spend a day or two on that and test the result to say for sure | 09:44 |
| gtristan | (right now I'm trying to push the rpm-metadata updating automation through, get it out of the way) | 09:45 |
| gtristan | guestimation: around one week of work away (including a deployment) | 09:48 |
| *** edcragg_ has quit IRC | 10:24 | |
| *** jude_ has quit IRC | 10:25 | |
| *** leeming has quit IRC | 10:25 | |
| paulsherwood | ack | 10:44 |
| *** rdale has joined #baserock | 13:01 | |
| *** rdale has quit IRC | 13:09 | |
| *** gtristan has quit IRC | 13:53 | |
| *** locallycompact has joined #baserock | 17:05 | |
| *** locallycompact has quit IRC | 17:12 | |
| *** locallycompact has joined #baserock | 18:02 | |
| *** edcragg has joined #baserock | 18:31 | |
| *** jude_ has joined #baserock | 18:32 | |
| *** leeming has joined #baserock | 18:32 | |
| *** edcragg has quit IRC | 18:35 | |
| *** edcragg has joined #baserock | 18:37 | |
| *** locallycompact has joined #baserock | 19:35 | |
| *** locallycompact has joined #baserock | 23:10 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!