Leave it to Oleg to save my a** ;-) On Thursday, January 30, 2020 at 5:16:45 PM UTC+1, Oleg Nenashev wrote: > > I would join as mentor as well > > On Thu, Jan 30, 2020, 17:05 Jon Brohauge <jonbr...@gmail.com <javascript:>> > wrote: > >> This is something I'd love to see get accepted into GSoC 2020. I'd even >> volunteer being a mentor for this. Although a more technical mentor would >> probably be needed alongside. >> >> Rgds, >> Jon >> >> On Wednesday, January 29, 2020 at 11:23:31 AM UTC+1, Ullrich Hafner wrote: >>> >>> I started a document for the project idea: >>> >>> https://docs.google.com/document/d/1fl3sF0mArtv2THOjPSZvNufGme4P24BtT0BirHMeMRY/edit?usp=sharing >>> >>> Feel free to extend or comment. >>> >>> Am 28.01.2020 um 13:12 schrieb Oleg Nenashev <o.v.n...@gmail.com>: >>> >>> + Ullrich Hafner who was interested to write up a project idea for this >>> topic. >>> I would be happy to be a mentor there, and I believe we could find more >>> mentors to make it happen >>> >>> >>> On Mon, Jan 27, 2020 at 5:55 PM Sladyn Nunes <sladyn...@gmail.com> >>> wrote: >>> >>>> +1 >>>> "ChatOps" triggers would be highly beneficial thereby letting the >>>> github-branch-source to run the required checks on specific parts. Also >>>> detailed reports from GitHub Checks could be published and maybe parsed as >>>> required. >>>> >>>> >>>> On Mon, Jan 27, 2020, 6:27 PM Oleg Nenashev <o.v.n...@gmail.com> wrote: >>>> >>>>> Just to bump this thread, we consider adding Checks API integration as >>>>> a GSoC 2020 project idea. >>>>> We had a preliminary discussion with Ulli Hafner (Warnings NG) and >>>>> other parties. >>>>> >>>>> If someone is interested to join the project, please let me know >>>>> >>>>> On Thursday, May 10, 2018 at 5:56:28 PM UTC+2, Jesse Glick wrote: >>>>>> >>>>>> On Thu, May 10, 2018 at 5:37 AM, Steven F <steven...@gmail.com> >>>>>> wrote: >>>>>> > The examples in the article show elements such as linting, >>>>>> > build, static analysis as separate and individually runnable >>>>>> things. In >>>>>> > Jenkins 2.x Pipeline it feels like bundling these things together >>>>>> is more >>>>>> > encouraged. >>>>>> >>>>>> Well, it is generally more straightforward to have those things be run >>>>>> >>>>>> as part of a single Jenkins build, triggered by SCM changes. What is >>>>>> missing is an API which would allow Jenkins report plugins (`Publisher >>>>>> >>>>>> & SimpleBuildStep`, for example) to indicate to the system that there >>>>>> >>>>>> is some information to be displayed in an abstract “change request”, >>>>>> perhaps associated with source code lines, which would then be >>>>>> implemented by `github-branch-source` with the Checks API. >>>>>> >>>>>> jxpe...@godaddy.com wrote: >>>>>> > just rerunning the job from github would save a step >>>>>> >>>>>> See JENKINS-45455 for rerunning generally; again we would need a new >>>>>> API to allow this is to be integrated with in-PR “chatops” triggers, >>>>>> so that `github-branch-source` could receive GH events and refire them >>>>>> >>>>>> as requests to rerun parts of a build, which >>>>>> `pipeline-model-definition` would then interpret as a Declarative >>>>>> build trigger. >>>>>> >>>>>> All this would allow you to do more from GitHub and less from Blue >>>>>> Ocean or the Jenkins “classic” UI. @abayer has done the most work in >>>>>> this area and should probably be commenting. >>>>>> >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Jenkins Developers" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to jenkin...@googlegroups.com. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/jenkinsci-dev/8215b84f-fd28-4066-a8d6-473683a43282%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/8215b84f-fd28-4066-a8d6-473683a43282%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> >>>> -- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "Jenkins Developers" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/jenkinsci-dev/UGhDM5lcz8Y/unsubscribe >>>> . >>>> To unsubscribe from this group and all its topics, send an email to >>>> jenkin...@googlegroups.com. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAC-Leqttb4%3DVhSnd%3DKLeq69GioC4mzmpyadcJUG0gdX9TN%3DbOw%40mail.gmail.com >>>> >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAC-Leqttb4%3DVhSnd%3DKLeq69GioC4mzmpyadcJUG0gdX9TN%3DbOw%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>> >>> >>> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Jenkins Developers" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/jenkinsci-dev/UGhDM5lcz8Y/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> jenkin...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/465bce4a-321b-444a-b0ae-594ff1e42e8c%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/465bce4a-321b-444a-b0ae-594ff1e42e8c%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >
-- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/c740c5b0-dc34-41bd-bf54-a8b51069afb6%40googlegroups.com.
