Re: [GSOC 2020 PROJECT IDEA] Jenkins distribution customize service
I would prefer two types of solutions: * pre-defined packaging. For example, AWS suite * the provider needs to guarantee the quality of it and maintain it. * users defined * we don’t guarantee anything about the suite. For example compatible something. We only provide the packing result How about this? Do you think it makes sense? On 02/21/2020 23:46，Jesse Glick wrote： On Fri, Feb 21, 2020 at 9:50 AM Chris Kilding wrote: Versions of each downstream plugin that is relevant to the use case would be pinned and controlled in the POM. Each meta-plugin release marks a combination of those plugins that are certified to work together. This takes the version testing and pinning work out of the Jenkins admin’s hands. This would not accomplish your goal, since plugin dependencies are on _minimum_ versions. A new release of one of the component plugins (say, `aws-java-sdk`) would be delivered to update sites immediately, regardless of what the current metaplugin POM says. This is why CloudBees offers https://docs.cloudbees.com/docs/admin-resources/latest/assurance-program/ as a value-add feature: the general update site publishes the latest Maven release of every plugin without any cross-testing. As for `workflow-aggregator`, I discourage its use since it just pulls in various stuff without any clear criteria for what is relevant and important. You might fare better with a pack which “supports AWS”, but you would still need to think about which parts of AWS are important for most users and which are not. BTW for an abandoned attempt in this area which I think was not mentioned previously: https://github.com/jenkins-infra/evergreen/tree/140e2a12da772917529fb93a9e48c2c34daec1c0/distribution/flavors/aws-ec2-cloud -- 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/CANfRfr3YQsE50L%2BqTnKqYFMyDrDSYbRNr_FWjFEsKZ6mK1C6Uw%40mail.gmail.com. -- 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/58e7c4ca.7c7e.1706fefa9c4.Coremail.zxjlwt%40126.com.
Re: Proposal: Jenkins Core PR reviewers team
I will add Marky to the reviewers team on Monday if there is no negative feedback provided in this thread. I have an action item to document the processes, but I am behind the schedule on that (and pretty much everything else, sorry). One of the major TODO items for me is to clarify what "substantial contributions" mean in the Core PR previewer prerequisites, but I believe that we should focus on contributors, not on bureaucracy. On Thursday, February 20, 2020 at 6:15:24 PM UTC+1, Matt Sicker wrote: > > +1 from me as well! > > On Tue, Feb 18, 2020 at 3:33 AM Baptiste Mathus > wrote: > > > > +1 to add Marky too. > > > > On Tue, Feb 18, 2020 at 9:59 AM Tim Jacomb > wrote: > >> > >> +1 from my side > >> > >> On Tue, 18 Feb 2020 at 08:10, Francisco Javier Fernandez < > fjfer...@cloudbees.com > wrote: > >>> > >>> Oleg, Marky, +1 from my side. Any help is always more than welcome! > >>> > >>> El domingo, 16 de febrero de 2020, 19:59:06 (UTC+1), Marky Jackson > escribió: > > Thank you kindly Oleg, please do get well. Sending healing thoughts. > > On Feb 16, 2020, at 10:30 AM, Oleg Nenashev > wrote: > > Hi Marky. As we discussed in PM, I have an action item to follow-up > on that. Sorry that I cannot provide the response time you expect, but I > was mostly off over past days (sick leave). I will do my best to propose > formal criteria for newcomer core PR reviewers next week. The informal > criteria before was several months of activities in the core and a number > of substantial contributions. > > If others vote in favor of adding Marky to the Core PR Reviewers, I > am +1 w.r.t that. > > BR, Oleg > > > > On Sun, Feb 16, 2020, 19:10 Marky Jackson > wrote: > > > > I wanted to circle back around on this > > > > On Thursday, February 13, 2020 at 4:48:44 PM UTC-8, Marky Jackson > wrote: > >> > >> I am happy to be included and thank you Gavin > >> > >> On Feb 13, 2020, at 4:46 PM, 'Gavin Mogan' via Jenkins Developers < > jenkin...@googlegroups.com> wrote: > >> > >> Sorry ya'll, with the new approved core developers, I'm going to > step down as a core-pr-reviewer. Its a little overwhelming to me, and I'm > not comfortable with core/java, but i'm still up for helping out randomly > where i can, especially for plugins, and web/javascript stuff. I'll lurk > randomly elsewhere. > >> > >> (this leaves room for Marky though) > >> > >> On Sun, Feb 2, 2020 at 1:04 AM Marky Jackson > wrote: > >>> > >>> I love a good challenge. > >>> Let’s hold off on this request and I will get some general reviews > under my belt for some time and reapply at a later date. > >>> Thanks kindly for the consideration. > >>> > >>> On Feb 1, 2020, at 11:53 PM, Daniel Beck > wrote: > >>> > >>> > >>> Extrapolating from the introduction of this team would mean people > should first be regular core PR reviewers. There's no process barrier to > just start doing that. > >>> > >>> Right now, > https://github.com/jenkinsci/jenkins/pulls?utf8=%E2%9C%93=is%3Apr+involves%3Amarkyjackson-taulia > > looks a little empty. > >>> > >>> -- > >>> 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/CAMo7PtLNMKCiby_hamQ%2BpUBZyVZBzyTphw8LiTE1Y1xsbz9EOw%40mail.gmail.com. > > > >>> > >>> > >>> -- > >>> 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/6001CF17-C6EB-4F86-ABF0-3754580C0BE3%40gmail.com. > > > >> > >> > >> -- > >> 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/CAG%3D_DusuUMUQuMqXYwbQ6vf%2BqaXgNzT9cg_5M9QYJzh7c%3DVbWg%40mail.gmail.com. > > > >> > >> > > -- > > 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/0sdrcSOQW64/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > jenkin...@googlegroups.com.
Re: About - Simple Pull Request Plugin
Hi Vu Tuan, Thank you for the detailed information about the plugin. So in this situation, my suggestions are below. - As the SPPR plugin is not developed any more and name of the plugin do match with its purpose, starting a new plugin for PAY ( Pipeline As Yaml) will be more accurate. - Of course, I do not want to throw all the effort in the SPPR, I may use some of the codes from there, if it is okay ? - @Oleg, I saw that this plugin is also selected for GSC 2020, I want to be sure that, writing this plugin will not affect GSC 2020 or any other Jenkins/Community Projects. Thanks. On Saturday, February 22, 2020 at 2:13:34 PM UTC+1, Vu Tuan Pham wrote: > > Hi Aytunc, > > Thank you for reaching out to me. To give you some context, I took over > this project from a GSoC project (Google Summer of Code) from a student. He > was unable to finish the project on time, so I decided to take it over > after GSoC to see if I can continue working on it to bring it to official > release (1.0). Unfortunately, due to time permit and some of my personal > reasons, I haven't had time to maintain it over the past 2 years. > > However, I can still help you my question at my best: > - At first, the intend was to integrate with multiple version control > systems as it mentioned in the description of the repo > https://github.com/jenkinsci/simple-pull-request-job-plugin. But > overtime, I think the target shifted toward Pipeline as YAML, which the > name of the plugin is not reflecting what it is doing. > - As I mentioned, iiuc, this project is no longer under development by > anybody, so if you have any idea about a new project, you can always > proceed ahead. If you think SPPR project is useful in some ways, you can > also consider merging 2 projects, there is no restriction for you to do > that. > > To understand more about this project, you can watch these presentation > videos during GSoC 2018 (can skip to SPPR plugin presentation): > https://www.youtube.com/watch?v=qWHM8S0fzUw=youtu.be > https://www.youtube.com/watch?v=tuTODhJOTBU=youtu.be > https://www.youtube.com/watch?v=GGEtN4nbtng=youtu.be > > cc ...@Martin d'Anjou , who is the mentor of this project > during GSoC 2018. I think Martin can give you some insights on the project. > Let us know if you have any further questions. > > Thanks, > Vu Tuan > > On Wednesday, February 19, 2020 at 4:54:07 AM UTC+8, Aytunc Beken wrote: >> >> Hi Oleg, >> >> Nice to meet you Vu Tuan. >> >> I have some doubts, may be you can help me understand things. >> >> - Why the name of the plugin is different ? Also It says it is about pull >> requests from various version controls. If this plugin will continue >> focusing on both, It will be good to separate them. >> - I was planing to use ModelASTPipelineDef >> (org.jenkinsci.plugins.pipeline.modeldefinition.ast) for converting Yaml to >> Jenkins and vice versa. As this is internal model of Declarative pipeline, >> It will be easy to maintain. >> >> I will be glad if I can get your ideas/comment about these. >> >> Thanks. Regards >> > -- 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/81073e48-032c-4f83-bbee-799fe1a7926f%40googlegroups.com.
Re: About - Simple Pull Request Plugin
Hi Aytunc, Thank you for reaching out to me. To give you some context, I took over this project from a GSoC project (Google Summer of Code) from a student. He was unable to finish the project on time, so I decided to take it over after GSoC to see if I can continue working on it to bring it to official release (1.0). Unfortunately, due to time permit and some of my personal reasons, I haven't had time to maintain it over the past 2 years. However, I can still help you my question at my best: - At first, the intend was to integrate with multiple version control systems as it mentioned in the description of the repo https://github.com/jenkinsci/simple-pull-request-job-plugin. But overtime, I think the target shifted toward Pipeline as YAML, which the name of the plugin is not reflecting what it is doing. - As I mentioned, iiuc, this project is no longer under development by anybody, so if you have any idea about a new project, you can always proceed ahead. If you think SPPR project is useful in some ways, you can also consider merging 2 projects, there is no restriction for you to do that. To understand more about this project, you can watch these presentation videos during GSoC 2018 (can skip to SPPR plugin presentation): https://www.youtube.com/watch?v=qWHM8S0fzUw=youtu.be https://www.youtube.com/watch?v=tuTODhJOTBU=youtu.be https://www.youtube.com/watch?v=GGEtN4nbtng=youtu.be cc @Martin d'Anjou , who is the mentor of this project during GSoC 2018. I think Martin can give you some insights on the project. Let us know if you have any further questions. Thanks, Vu Tuan On Wednesday, February 19, 2020 at 4:54:07 AM UTC+8, Aytunc Beken wrote: > > Hi Oleg, > > Nice to meet you Vu Tuan. > > I have some doubts, may be you can help me understand things. > > - Why the name of the plugin is different ? Also It says it is about pull > requests from various version controls. If this plugin will continue > focusing on both, It will be good to separate them. > - I was planing to use ModelASTPipelineDef > (org.jenkinsci.plugins.pipeline.modeldefinition.ast) for converting Yaml to > Jenkins and vice versa. As this is internal model of Declarative pipeline, > It will be easy to maintain. > > I will be glad if I can get your ideas/comment about these. > > Thanks. Regards > -- 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/029d3b34-8dde-4034-86bf-85b78acf6752%40googlegroups.com.
