[yast-devel] GitHub services and webhooks, yast-commit@opensuse.org ?
Hi all, the GitHub Services are deprecated and are replaced by GitHub web hooks. Basically the Services provided an additional logic to process the hooks. For example the email service sends email notifications to the specified address, while the web hooks are just plain HTTP POST requests without any logic (that needs to be implemented on the server side). You can find more details in [1]. This week they disabled the old Services (till January 14, 19:00 UTC) so the users can prepare for the final shut down. Travis and Jenkins ------------------ We use the Services for triggering the Travis and Jenkins builds. The Travis Service has been replaced automatically by a web hook by the Travis server remotely, no action needed, I just removed the old Service configuration from the repositories. For the public Jenkins I have configured an organization web hook. The advantage is that it should cover all YaST Git repositories (even the ones added in the future), no need to configure this for each repository separately. The disadvantage is that it sends the notification also for repositories which do not have any Jenkins job configured. But as the vast majority of the packages use Jenkins and the missing Jenkins jobs are usually for dropped or unmaintained packages which we do not touch anyway then the real overhead should be very minimal. I also removed the old Jenkins Service configuration from GitHub. There is still a fallback to check the repository status once a day at the public Jenkins, so if any web hook is for any reason not delivered (network issue, Jenkins down,...) then still at least once a day the Git repositories are scanned for changes. This means the public Jenkins should work just as expected. Of course, if you see any issues there then just ping me. yast-commit@opensuse.org -------------------------- The only problematic GitHub Service is the email Service which for YaST sends notifications to yast-commit@opensuse.org. There is no simple replacement, we would need a publicly reachable server which can send emails to yast-commit@opensuse.org. But the question is: do we really need that? Does somebody really read the emails from yast-commit@opensuse.org? You can see the activity log also at the main https://github.com/ page, or there is a news feed link at the bottom. That can be also an alternative to the commit mails. Would that be enough for you? (Personally I do not read the commit ML, I'm asking here for feedback to see if there is any use for that.) [1] https://developer.github.com/v3/guides/replacing-github-services/ [2] https://developer.github.com/changes/2018-11-05-github-services-brownout/ -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8 -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
V Wed, 9 Jan 2019 15:55:46 +0100
Ladislav Slezak
Hi all,
the GitHub Services are deprecated and are replaced by GitHub web hooks. Basically the Services provided an additional logic to process the hooks.
For example the email service sends email notifications to the specified address, while the web hooks are just plain HTTP POST requests without any logic (that needs to be implemented on the server side). You can find more details in [1].
This week they disabled the old Services (till January 14, 19:00 UTC) so the users can prepare for the final shut down.
Travis and Jenkins ------------------
We use the Services for triggering the Travis and Jenkins builds. The Travis Service has been replaced automatically by a web hook by the Travis server remotely, no action needed, I just removed the old Service configuration from the repositories.
For the public Jenkins I have configured an organization web hook. The advantage is that it should cover all YaST Git repositories (even the ones added in the future), no need to configure this for each repository separately.
The disadvantage is that it sends the notification also for repositories which do not have any Jenkins job configured. But as the vast majority of the packages use Jenkins and the missing Jenkins jobs are usually for dropped or unmaintained packages which we do not touch anyway then the real overhead should be very minimal.
I also removed the old Jenkins Service configuration from GitHub. There is still a fallback to check the repository status once a day at the public Jenkins, so if any web hook is for any reason not delivered (network issue, Jenkins down,...) then still at least once a day the Git repositories are scanned for changes.
This means the public Jenkins should work just as expected. Of course, if you see any issues there then just ping me.
Thanks for taking care.
yast-commit@opensuse.org --------------------------
The only problematic GitHub Service is the email Service which for YaST sends notifications to yast-commit@opensuse.org. There is no simple replacement, we would need a publicly reachable server which can send emails to yast-commit@opensuse.org.
But the question is: do we really need that? Does somebody really read the emails from yast-commit@opensuse.org?
You can see the activity log also at the main https://github.com/ page, or there is a news feed link at the bottom. That can be also an alternative to the commit mails. Would that be enough for you?
(Personally I do not read the commit ML, I'm asking here for feedback to see if there is any use for that.)
Me neither. I used to read it before we start doing code reviews, as I sometime do post commit review. But nowadays do not check it for months. Josef
[1] https://developer.github.com/v3/guides/replacing-github-services/ [2] https://developer.github.com/changes/2018-11-05-github-services-brownout/
-- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 1/9/19 6:55 AM, Ladislav Slezak wrote:
Hi all,
the GitHub Services are deprecated and are replaced by GitHub web hooks. Basically the Services provided an additional logic to process the hooks.
<snip>
yast-commit@opensuse.org --------------------------
The only problematic GitHub Service is the email Service which for YaST sends notifications to yast-commit@opensuse.org. There is no simple replacement, we would need a publicly reachable server which can send emails to yast-commit@opensuse.org.
But the question is: do we really need that? Does somebody really read the emails from yast-commit@opensuse.org?
Yes, I do. Religiously. Every day. I depend on that to watch and see what I, as a non-YaST Team Member, can contribute. That is where I spot the typos and grammar errors that I have been fixing. When I understand coding, I will also watch for anything I can do to fix there or improve. Also, when I see what is going on, it sometimes gives me ideas that I can suggest for possible improvements in the Users' experience.
You can see the activity log also at the main https://github.com/ page, or there is a news feed link at the bottom. That can be also an alternative to the commit mails. Would that be enough for you?
I was not aware of this. Do not know if there is anything obvious telling non-YaST Team Members who wish to Contribute should look there. Perhaps there is a way to get that more obvious to interested would-be contributors.
(Personally I do not read the commit ML, I'm asking here for feedback to see if there is any use for that.)
I think I already answered that. But, maybe I am the only one? I am busy with openSUSE Elections at the moment, but I will check the above links ASAP and see if they are a suitable replacement in cases such as mine. I will report back as soon as I do. Thanks, -- -Gerry Makaro openSUSE Board Elections Committee (election-officials **at** openSUSE.org) openSUSE Member openSUSE Global Moderator openSUSE Contributor YaST Contributor aka Fraser_Bell on the Forums, OBS, IRC, and mail at openSUSE.org Fraser-Bell on Github -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 1/9/19 3:55 PM, Ladislav Slezak wrote:
Hi all,
[...]
Travis and Jenkins ------------------
[...]
This means the public Jenkins should work just as expected. Of course, if you see any issues there then just ping me.
Thanks a lot!
yast-commit@opensuse.org --------------------------
[...]
(Personally I do not read the commit ML, I'm asking here for feedback to see if there is any use for that.)
I do not read the commit ML. I believe that Github notifications (anyone can subscribe to any repo he/she is interested in) are way more useful. At least for a developer, since they includes the whole discussion on the pull request. Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 1/9/19 2:55 PM, Ladislav Slezak wrote:
Hi all,
the GitHub Services are deprecated and are replaced by GitHub web hooks. Basically the Services provided an additional logic to process the hooks.
For example the email service sends email notifications to the specified address, while the web hooks are just plain HTTP POST requests without any logic (that needs to be implemented on the server side). You can find more details in [1].
This week they disabled the old Services (till January 14, 19:00 UTC) so the users can prepare for the final shut down.
Travis and Jenkins ------------------
We use the Services for triggering the Travis and Jenkins builds. The Travis Service has been replaced automatically by a web hook by the Travis server remotely, no action needed, I just removed the old Service configuration from the repositories.
For the public Jenkins I have configured an organization web hook. The advantage is that it should cover all YaST Git repositories (even the ones added in the future), no need to configure this for each repository separately.
The disadvantage is that it sends the notification also for repositories which do not have any Jenkins job configured. But as the vast majority of the packages use Jenkins and the missing Jenkins jobs are usually for dropped or unmaintained packages which we do not touch anyway then the real overhead should be very minimal.
I also removed the old Jenkins Service configuration from GitHub. There is still a fallback to check the repository status once a day at the public Jenkins, so if any web hook is for any reason not delivered (network issue, Jenkins down,...) then still at least once a day the Git repositories are scanned for changes.
This means the public Jenkins should work just as expected. Of course, if you see any issues there then just ping me.
Thanks Ladislav! Once again, you save us ;)
yast-commit@opensuse.org --------------------------
The only problematic GitHub Service is the email Service which for YaST sends notifications to yast-commit@opensuse.org. There is no simple replacement, we would need a publicly reachable server which can send emails to yast-commit@opensuse.org.
But the question is: do we really need that? Does somebody really read the emails from yast-commit@opensuse.org?
You can see the activity log also at the main https://github.com/ page, or there is a news feed link at the bottom. That can be also an alternative to the commit mails. Would that be enough for you?
(Personally I do not read the commit ML, I'm asking here for feedback to see if there is any use for that.)
I don't use that mailing list at all. Instead, I receive GitHub notification in my personal gmail account. For me this is more useful because you can even have such notification in your mobile and read them when you are bored :)
[1] https://developer.github.com/v3/guides/replacing-github-services/ [2] https://developer.github.com/changes/2018-11-05-github-services-brownout/
-- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 10. 01. 19 v 1:26 Fraser_Bell napsal(a): [...]
I think I already answered that. But, maybe I am the only one?
I am busy with openSUSE Elections at the moment, but I will check the above links ASAP and see if they are a suitable replacement in cases such as mine.
I will report back as soon as I do.
Any news? It seems that you are the only one reading that ML. In that case I think it does not make sense to implement and maintain a replacement. So the GitHub commit emails will not be sent after Jan 31 2018. Thank you for our understanding. -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak@suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 1/18/19 6:06 AM, Ladislav Slezak wrote:
Dne 10. 01. 19 v 1:26 Fraser_Bell napsal(a): [...]
I think I already answered that. But, maybe I am the only one?
I am busy with openSUSE Elections at the moment, but I will check the above links ASAP and see if they are a suitable replacement in cases such as mine.
I will report back as soon as I do.
Any news? It seems that you are the only one reading that ML. In that case I think it does not make sense to implement and maintain a replacement.
Agreed. Although I have not checked the links, in afterthought it should not be a problem. If there is any, I am sure you or one of the other YaST Team members can help me figure out what I can do.
So the GitHub commit emails will not be sent after Jan 31 2018.
Thank you for our understanding.
It only makes good sense, IMO. Thanks, -- -Gerry Makaro openSUSE Board Elections Committee (election-officials **at** openSUSE.org) openSUSE Member openSUSE Global Moderator openSUSE Contributor YaST Contributor aka Fraser_Bell on the Forums, OBS, IRC, and mail at openSUSE.org Fraser-Bell on Github -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 09. 01. 19 v 15:55 Ladislav Slezak napsal(a):
yast-commit@opensuse.org --------------------------
The only problematic GitHub Service is the email Service which for YaST sends notifications to yast-commit@opensuse.org. There is no simple replacement, we would need a publicly reachable server which can send emails to yast-commit@opensuse.org.
Actually GitHub in the end added a new notification option for each Git repository (see [1]). They also imported the email address from the old Email service. That means the notification emails should work as before. 👍 Sorry for the confusion. 😝 [1] https://help.github.com/articles/about-email-notifications-for-pushes-to-you... -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8 -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (5)
-
Ancor Gonzalez Sosa -
Fraser_Bell -
Josef Reidinger -
José Iván López González -
Ladislav Slezak