| *** tjamison has left #automotive | 00:27 | |
| *** kooltux__ has quit IRC | 00:33 | |
| *** mdurnev has joined #automotive | 01:01 | |
| *** AlisonChaiken has joined #automotive | 05:17 | |
| *** CTtpollard has joined #automotive | 06:59 | |
| *** warter has joined #automotive | 07:28 | |
| *** warter is now known as jbocklage123 | 07:29 | |
| *** rstreif has joined #automotive | 07:33 | |
| *** rajm has joined #automotive | 07:39 | |
| *** leon has joined #automotive | 07:57 | |
| *** leon is now known as leon-anavi | 07:57 | |
| leon-anavi | morning | 07:58 |
|---|---|---|
| *** jonathanmaw has joined #automotive | 08:00 | |
| *** kbroulik has joined #automotive | 08:04 | |
| *** rdale has joined #automotive | 08:08 | |
| *** rstreif_ has joined #automotive | 08:10 | |
| *** rstreif has quit IRC | 08:11 | |
| *** gunnarx has joined #automotive | 08:16 | |
| CTtpollard | gunnarx: I'm debating a branch of g-d-p that tracks the current yocto/ivi version branch instead of refs and dropping it into a pipeline | 08:33 |
| * gunnarx is reading, trying to understand | 08:34 | |
| gunnarx | can we break it down. what is current yocto/ivi version branch? meta-ivi? | 08:35 |
| CTtpollard | not sure I can simplify that one further | 08:35 |
| CTtpollard | we're defined by an ivi release, then in turn a yocto release | 08:35 |
| CTtpollard | we use .gitmodules to point to refs, you can point to branches | 08:35 |
| gunnarx | yes, a "meta-ivi" release if you want to be more clear | 08:35 |
| gunnarx | How do you point to branches? Not using submodules I think | 08:36 |
| gunnarx | Modifying the init script to checkout the tip of the branch? | 08:37 |
| CTtpollard | it can be given a branch field | 08:37 |
| gunnarx | it being a submodule? | 08:37 |
| CTtpollard | yes, since git 1.8.2 apparently | 08:39 |
| CTtpollard | for meta-oic as an example | 08:39 |
| gunnarx | sorry I'm slow today... despite Goa Psy-Trance in the headphones. :) | 08:39 |
| CTtpollard | I'd blame friday | 08:39 |
| gunnarx | Sounds good to me. There are many ways, you could of course modify init script also. | 08:40 |
| gunnarx | Keeping this on a branch makes sense though - easy to set up such a pipeline. | 08:40 |
| gunnarx | Do we like that idea better than the pipeline idea with an environment variable that controls which layers to replace (the one that would generalize our current latest-meta-genivi-dev recipe) | 08:41 |
| CTtpollard | yes! | 08:42 |
| pedroalvarez | gunnarx's pipeline idea will allow us to forget about this special branch that would track the tip of meta-ivi branch | 08:43 |
| gunnarx | :( they hate my idea ... | 08:43 |
| CTtpollard | just one thing, does it still have the limitation of only being able to track PR's for 'master'? | 08:43 |
| gunnarx | hmm... | 08:43 |
| pedroalvarez | CTtpollard: no, the limitation is that the repo has to have a master branch | 08:43 |
| pedroalvarez | iirc | 08:43 |
| CTtpollard | ah ok | 08:44 |
| gunnarx | For each individual repo, only PRs aimed to the master branch of that repo will get picked up | 08:44 |
| gunnarx | so master branch of m-g-d can be tracked, or any other repo. | 08:44 |
| CTtpollard | hmm, so for instance now with meta-ivi10 we could not use it to test PR's into gdp | 08:44 |
| CTtpollard | but we could just for standard commits to that version branch | 08:45 |
| gunnarx | I don't see any separate meta-ivi-10 branch on g-d-p git? what are you referring to? | 08:45 |
| * pedroalvarez continues at being on holidays | 08:46 | |
| pedroalvarez | o/ | 08:46 |
| CTtpollard | gunnarx: meta-ivi's own 10.0 branch | 08:46 |
| gunnarx | what the hell, some cheesy lovesong is invading my psychedelic trance. hang on. | 08:46 |
| CTtpollard | wrong playlist? :P | 08:47 |
| gunnarx | ok, changed channel now. you were saying? | 08:47 |
| gunnarx | Yes, the bug (but they probably consider it a feature request, ugh) is open. PRs to meta-ivi branch 10 can't be automatically tested. | 08:48 |
| gunnarx | But you could script that instead then. | 08:48 |
| CTtpollard | so, we could use the layer replacement to track a version branch of meta-ivi (say 10.0 for now) which would test each new commit against master GDP. But dues to the master limitation with PR's we could not test PR's to that branch against master gdp | 08:49 |
| CTtpollard | right | 08:49 |
| gunnarx | yes | 08:50 |
| gunnarx | I suppose it's possible to script GitHub PR monitoring separately | 08:50 |
| gunnarx | One of you could go give a +1 on the bug/feature request :) | 08:51 |
| gunnarx | s/One/All/ ! | 08:51 |
| CTtpollard | definitely, got the url? | 08:51 |
| gunnarx | yes, just have to go to Confluence, it's on our Go pages | 08:52 |
| gunnarx | https://github.com/ashwanthkumar/gocd-build-github-pull-requests/issues/66 | 08:52 |
| CTtpollard | cheers | 08:54 |
| khem | CTtpollard: it smells like you guys are working towards a CI pipeline of some sort ? | 08:56 |
| CTtpollard | khem: indeed :) .genivi.org/go/pipelines | 08:59 |
| CTtpollard | * http://go.genivi.org/go/pipelines | 08:59 |
| khem | ok. git submodules or gerrit ? | 08:59 |
| khem | ah logins | 08:59 |
| CTtpollard | GDP currently uses git submodules to init the needed yocto layers, go.cd is the CI system | 09:00 |
| CTtpollard | khem: you can login is guest if you wish to take a look | 09:00 |
| CTtpollard | gunnarx: speaking of which, how does one recover/reset a password on go.genivi? | 09:03 |
| gunnarx | sorry, was afk a while. recover/reset a password must currently follow the same process as creating a new account I'm afraid. | 09:08 |
| gunnarx | In other words, notify me and I'll delete the old user and confirm the SSH key is in place and then you continue from there. | 09:08 |
| *** jbocklage123 has quit IRC | 09:14 | |
| gunnarx | CTtpollard: I imagine it should be somewhat trivial to script a GitHub PR trigger... You know you can pull down pull requests right? And their numbers are consecutive. So just iterate from a cached value up until the pull fails. That's the most recent PR. Then build it :) | 09:22 |
| gunnarx | You'd need a trigger of course, but we might use a timer maybe... | 09:23 |
| CTtpollard | yeh without digging into the API a timer for the poll rate is probably the place to start | 09:25 |
| gunnarx | I must have found the right playlist now - Progressive-Psy. | 09:26 |
| gunnarx | brain kicking into gear... | 09:27 |
| CTtpollard | I think the replacement of the core layers for now, tracking the current version/release in use is the best place to start. From there we can look into we use the feedback from there to keep gdp master up-to date | 09:30 |
| gunnarx | Makes sense. If you end up still contemplating PR builds you may want to check out TOOL-86 also for info. I can't add watchers on tickets - maybe something toscalix can fix? | 09:31 |
| CTtpollard | i.e new commit in say poky jethro branch is tested, green light. What mechanism will we follow to take that result and update GDP master to that submodule commit | 09:31 |
| gunnarx | Idk GDP maintainers do what they're supposed to ;) | 09:32 |
| gunnarx | Eh, let me back up | 09:32 |
| CTtpollard | automation,automation. | 09:32 |
| gunnarx | Sure, automating a new PR possibly. Not sure if it's the best use of our time, but why not set up a "wish list" ticket on it. | 09:32 |
| CTtpollard | There needs to be some sort of feedback loop from that sort of testing, else it's pretty noisy | 09:33 |
| gunnarx | what do you have in mind? | 09:34 |
| CTtpollard | not quite sure yet, but generating a matching PR sounds like an ultimate goal. But even some sort of notification with a parse-able such a this sha of gdp was used with this sha of $metalayerbranch succeeded | 09:37 |
| CTtpollard | *output such as | 09:37 |
| gunnarx | Yes. I was going to end it with my findings but I put the JIRA ticket back to in progress to capture this stuff also. | 09:38 |
| CTtpollard | for now, unless you know of something else, we'd have to just trawl through the job logs from the pipelines to see what commits were tested | 09:38 |
| CTtpollard | I'll dump my feelings into the ticket, thanks for pointing it out | 09:39 |
| gunnarx | I know what you're after and it is useful. But many times you are OK with knowing that the topmost commit works. E.g. if some branch was failing but now works, you'd update the layer to what now works and ignore the previous. | 09:39 |
| gunnarx | So in practice it usually works out, but definitely if automation can tell you every combination... | 09:39 |
| gunnarx | automating git bisect and such is a holy grail. | 09:40 |
| CTtpollard | yes I suppose if the last job is green in such a pipeline, then that infers the tip of the branch is ok to be integrated | 09:43 |
| CTtpollard | which could be assessed at a given rate, daily / weekly perhaps | 09:45 |
| gunnarx | Yes. The Go/GitHub PR builds work that way - they only test the latest commit in the PR. If you add a new commit, the test is rerun. (I think you know this but for everyone's benefit...) | 09:46 |
| CTtpollard | then the manual PR to switch GDP to any of the new tested sha's from the modules will allow the changes to be tested in a single integration | 09:48 |
| CTtpollard | as that could potentially lead to an error | 09:50 |
| gunnarx | isn't that the case today? If you sent a PR to g-d-p.git you can include multiple layers and submodule updates if they have dependencies? | 09:52 |
| CTtpollard | yes, but what I mean is that we could have these pipelines tracking the tips of version branches, with will be integrated against master of GDP | 09:53 |
| CTtpollard | say if we did a weekly check, and 'x' layers were tested and shown to have new working commits, they still need to be tested in a single integration | 09:54 |
| CTtpollard | together | 09:54 |
| CTtpollard | sorry if I'm not getting the point across very well | 09:57 |
| gunnarx | No it's fine, I see what you mean. But it feels like we're beating a dead horse by now - why not implement something and try it for a while. | 09:57 |
| CTtpollard | +1 | 09:57 |
| gunnarx | +1 | 09:58 |
| CTtpollard | it doesn't help that im also trying to handle my actual car's problems at the same time as this discussion | 09:58 |
| *** gunnarx has quit IRC | 10:21 | |
| *** gunnarx has joined #automotive | 10:26 | |
| *** gunnarx has joined #automotive | 10:26 | |
| *** nuohan has quit IRC | 11:55 | |
| *** nuohan has joined #automotive | 11:59 | |
| *** nuohan has quit IRC | 12:09 | |
| *** rstreif has joined #automotive | 12:09 | |
| *** rstreif_ has quit IRC | 12:10 | |
| *** nuohan has joined #automotive | 12:11 | |
| *** jonathanmaw has quit IRC | 12:16 | |
| *** jonathanmaw has joined #automotive | 12:31 | |
| *** rstreif has quit IRC | 12:39 | |
| *** rstreif has joined #automotive | 12:39 | |
| *** rstreif_ has joined #automotive | 12:52 | |
| *** rstreif has quit IRC | 12:52 | |
| *** rstreif_ has quit IRC | 12:58 | |
| *** rstreif_ has joined #automotive | 12:58 | |
| CTtpollard | sigh | 13:00 |
| *** ashwasimha_ has joined #automotive | 13:06 | |
| gunnarx | mobile networks. it's the same for me a lot of time... :-/ | 13:13 |
| *** rstreif_ has quit IRC | 13:42 | |
| *** mdurnev has quit IRC | 13:45 | |
| *** jlrmagnus has joined #automotive | 13:49 | |
| *** nuohan has quit IRC | 13:52 | |
| *** halfline has quit IRC | 14:03 | |
| *** halfline has joined #automotive | 14:04 | |
| *** nuohan has joined #automotive | 14:10 | |
| *** nisha has quit IRC | 14:14 | |
| *** jlrmagnus has quit IRC | 14:26 | |
| *** nuohan has quit IRC | 14:41 | |
| *** nuohan has joined #automotive | 14:41 | |
| *** nuohan has quit IRC | 14:47 | |
| *** nuohan has joined #automotive | 14:47 | |
| *** nish has joined #automotive | 14:51 | |
| *** nish is now known as nisha | 14:51 | |
| *** kbroulik has quit IRC | 15:06 | |
| *** gunnarx has quit IRC | 15:08 | |
| *** jlrmagnus has joined #automotive | 15:37 | |
| *** jonathanmaw has quit IRC | 15:45 | |
| *** mvick has quit IRC | 15:52 | |
| *** gunnarx has joined #automotive | 15:57 | |
| *** gunnarx has joined #automotive | 15:57 | |
| *** mvick has joined #automotive | 15:59 | |
| *** ashwasimha_ has quit IRC | 16:11 | |
| *** leon-anavi has quit IRC | 16:15 | |
| *** rajm has quit IRC | 16:28 | |
| *** gunnarx has quit IRC | 16:30 | |
| *** rdale has quit IRC | 16:44 | |
| *** AlisonChaiken has quit IRC | 16:47 | |
| *** jlrmagnus has quit IRC | 17:11 | |
| *** AlisonChaiken has joined #automotive | 17:17 | |
| *** robin__ has quit IRC | 17:44 | |
| *** jlrmagnus has joined #automotive | 17:52 | |
| *** jlrmagnus has quit IRC | 17:57 | |
| *** robin__ has joined #automotive | 18:22 | |
| *** CTtpollard has quit IRC | 18:30 | |
| *** praneeth has quit IRC | 19:31 | |
| *** praneeth has joined #automotive | 19:31 | |
| *** Martiini has joined #automotive | 19:41 | |
| *** praneeth has quit IRC | 19:54 | |
| *** jlrmagnus has joined #automotive | 20:12 | |
| *** praneeth has joined #automotive | 20:17 | |
| *** jlrmagnus has quit IRC | 20:29 | |
| *** khem has quit IRC | 20:33 | |
| *** jlrmagnus has joined #automotive | 20:44 | |
| *** khem has joined #automotive | 20:45 | |
| *** nisha has quit IRC | 21:02 | |
| *** murphy has quit IRC | 21:17 | |
| *** jlrmagnus has quit IRC | 21:47 | |
| *** jlrmagnus has joined #automotive | 21:47 | |
| *** Martiini has quit IRC | 22:51 | |
| *** mvick has quit IRC | 22:59 | |
| *** jlrmagnus has quit IRC | 23:58 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!