=== sportsquid__ is now known as sportsquid [01:47] I'm here to say hello to elopio, kyrofa, sergiusens, popey and flexiondotorg [01:47] for the google code-in [01:47] Hey there sportsquid, welcome! [01:48] hi [01:51] Sorry if I do anything wrong, this is my first time using IRC [02:10] Hello sportsquid! [02:22] Hello! [04:38] elopio: you around? [05:05] here's a demonstration of what I found https://asciinema.org/a/SNVVdRErHV9sjglO9Ga5R2PFW [05:58] popey, if you get some free time could you please take a look at my task https://codein.withgoogle.com/dashboard/task-instances/5288882268536832/ [05:58] I will [05:58] (just woke up) [06:06] popey, ok no promblem [07:46] popey, could you take a look at my submission if you have some spare time? Thanks! [07:47] Sure thing! [09:36] hello [09:39] hi [12:09] @popey Hi, I have done the snap creation tutorial task [12:09] What do I need to submit? [12:10] A few Screenshots are usually sufficient, [12:14] Ok, I have sent it in on the GCI task page [12:16] Awesome, thanks. I'll take a look shortly [12:49] Thanks === vonnewman is now known as owenl131 [16:04] elopio: for my task, what we ideally want is for the link to show next to do build in travis right? [16:07] daniellimws: any way of reporting is good. [16:08] as long as we don't have to dig on the log, it's a huge win. [16:09] ok, currently with what I found we can definitely make a script to load the links [16:09] now still waiting for travis support to respond regarding the annotations [16:09] weirdly there is not a single piece of documentation regarding that [16:10] hopefully can be able to achieve this https://goo.gl/yNV2HQ [16:37] that would be perfect daniellimws ! [16:40] hmm it seems that they just removed the feature one week ago? [16:40] https://github.com/travis-ci/travis-api/pull/602 [16:40] Pull 602 in travis-ci/travis-api "delete annotations from api" [Merged] [16:40] this is so weird [16:42] no wonder I could not find any documentation regarding it [16:42] elopio: what do you say? in this case there probably is not much hope to display the link next to the build already [16:43] daniellimws: you lost me a little. How did you get to show that link on the job? Without annotations? [16:44] elopio: which part are you referring to? [16:44] "currently with what I found we can definitely make a script to load the links" [16:44] oh, you meant loading, not displaying? [16:45] yea not on the travis website [16:45] yeah, that's good. Please include in the research that the annotations have just been removed. [16:45] ok [16:45] have you seen this? https://asciinema.org/a/SNVVdRErHV9sjglO9Ga5R2PFW [16:46] I had not :) [16:48] is that ok? [16:49] daniellimws: it is very nice, yes. If publishing the link in the travis job is not possible, I'm wondering what alternatives we could try. [16:49] we have a bot on irc called snappy-m-o. Maybe, we add a command that runs that travis log | grep you found, and returns the url [16:49] I also found a way to notify via IRC [16:50] https://docs.travis-ci.com/user/notifications/#Configuring-IRC-notifications [16:50] daniellimws: does it notify on IRC even on pull requestS? [16:50] yea I think it notifies after every successful build [16:50] it says at the bottom "Pull Request builds do not trigger IRC notifications." [16:51] oh [16:51] what makes pull requests hard is that you can't have secrets in them [16:52] what does that mean? [16:52] API keys? [16:52] travis has a way to encrypt secrets, and not show them on the log. But, on pull requests you could just echo the unencrypted secret, and expose it to the world [16:53] oh that's not good [16:53] so, the encrypted secrets are only available on branches that come from the organization. So we trust our team members to never echo a secret, but we can't trust the world [16:54] oh so the IRC notification being not supported is largely due to this reason right? [16:54] maybe. That would be a good question for travis support. [16:54] the docs don't explain why. And I see that slack notifications support pull requests. [16:55] Sorry but I don't understand. Can't they still echo the secrets [16:55] Can't people still echo the secrets whenever they want? [16:56] daniellimws: it depends on how that notifier is implemented. If they have a server that takes messages from travis, and prints them to IRC, there are no secrets involved. [16:56] so the answer to your two last questions is, I don't know :) [16:57] I mean can't people just hide a line or so to display the secret in their pull requests, and give people the link to that build in travis? [16:57] but, what you have done so far is pretty useful already. [16:57] daniellimws: what do you think of this? We send a message to the snappy-m-o bot on irc telling him: give me the snap url for pull request #123. The bot uses the apis to find the travis job id from the pull request id, calls travis log | grep transfer, and returns the url [16:58] flexiondotorg: can you take a look at this please? https://codein.withgoogle.com/dashboard/task-instances/4790241665744896/ [16:58] elopio: sure thing [16:58] daniellimws: sorry, I'm confused by that last question. In pull requests that are not from `snapcore`, there are no secrets. [16:59] sorry I'm even more confused now @.@ if there are no secrets, what did you mean by saying people out of the team can expose secrets? [17:00] daniellimws: there are two types of pull requests, the ones that come from snapcore, and the ones that come from other repos. [17:00] once you are a member of the snapcore team, you can push a branch to the snapcore repo [17:01] travis exposes secrets to pull requests that come from snapcore branches. So if I want to echo the unencrypted snapcraft.io credentials, I can do it. Of course, I was approved into the snapcore team because they trust I will not do such thing. [17:02] ahh I get it now [17:02] travis doesn't expose secrets to pull requests that don't come from snapcore branches. So people that are not part of the snapcore team can't echo the secrets, they are just not available encrypted or unencrypted. [17:02] so, am I going to work on the IRC bot? [17:03] daniellimws: well, that sounds like bonus points right? It would be happy if you finish the task with a little research about how to translate a pull request id to the corresponding travis job id. [17:04] elopio: sure no problem [17:04] if you want to finish the job adding a script to the bot, well, more good karma for you :D [17:04] where is the bot repo? [17:04] https://github.com/elopio/snappy-m-o [17:05] ok thanks [17:07] popey: I'll review that task in an hour or so. [17:07] elopio: what should the command be? "give me the snap url for pull request #xyz" does sound a bit too long, doesn't it? [17:07] Thanks [17:07] daniellimws: ivanfon: jakewalker: konrad11901: m4sk1n_: and anybody else who is participating on google code in: Tomorrow we will have an Ubuntu Hour, on google hangouts [17:07] https://community.ubuntu.com/t/ubuntu-hour-friday-november-15th/2722 [17:07] ok [17:07] it would be great if you could join us, and tell us a little bout your experience so far. [17:08] hmm, it's going to be at 3am over here [17:10] elopio, I'll do my best to take part in Ubuntu Hour, but as for now I can't promise anything :/ [17:10] but I hope I'll be able to join it [17:11] daniellimws: you are excused :) [17:11] haha maybe I'll have a look but highly unlikely [17:11] konrad11901: I will post the link here ~30 minutes before we start, in case you can make it. [17:11] elopio: I’m gonna be in class but I can probably take part for a bit [17:12] daniellimws: the command could be something like "travis get-snap 123" [17:12] elopio: ok [17:14] https://codein.withgoogle.com/dashboard/tasks/6251477829943296/ [17:14] this is the task corresponding to the ubuntu hour ^ [17:16] elopio: is the chatbot mup on #snappy? [17:16] daniellimws: no, snappy-m-o [17:17] ok [17:17] oh, it's dead. Let me wake it up [17:19] elopio: ok :) [17:23] m4sk1n_: great, please leave a comment on community.ubuntu.com [17:46] elopio, one technical question: can I participate in this call without any camera? [17:46] I mean, only with a microphone [17:46] konrad11901: yes. The camera is optional. [17:47] ok, thanks :) [17:59] I have translated my own tutorial to Polish, do I need review from another Polish-speaking person? [18:24] elopio, a small side note: you should change the date in the "Participate on the Ubuntu Hour, November 15th" task ;) [18:25] m4sk1n_: yes, a peer review is required always. [18:25] konrad11901: oh, right [19:07] I joined for the GCI task, should I be saying hi to elopio, kyrofa, and wxl now or wait until tomorrow? [19:08] inhumanthree1, haha, any time! Welcome :) [19:08] wanting to help out inhumanthree1 ? [19:10] the ubuntu hour task said to come here first and say hello to you three [19:10] oh [19:10] hello :) [19:11] ...oh, nevermind [19:11] I can't actually participate because it's at 11:00 [19:11] guess I'll go abandon the task, goodbye [19:13] kyrofa: did you understand the context of all that? [19:13] wxl, haha, believe it or not, yes :D [19:14] kyrofa: well given my name was implied, i'd like to know XD [19:14] There's a task for attending the Ubuntu Hour [19:14] (which you're attending, elopio must have put you on there) [19:14] ahhhhh [19:14] yeah well it's also tomorrow X''''D [19:14] But apparently it's happening at sleepy time? [22:32] are you going to add tasks based on tutorial suggestions?