Re: Plugin Development - Ajax Example
Hi,
Finally solved the problem with JavaScriptMethod.
For the problem was in Script side.
I had the change the ${instance} to ${it}
var pipelineAsYamlSnippetizer =
Thank you all for the help.
On Tuesday, May 19, 2020 at 9:33:35 PM UTC+2, Gavin Mogan wrote:
>
> Uh, prototype is a frontend library, it doesn't actually expose things. I
> think any of the doName (like doAjax) expose as web GETters
>
> var request = new XMLHttpRequest();
> request.open('GET', "${it.baseUrl}/buildHistory/all", true);
>
> request.onload = function() {
> if (this.status >= 200 && this.status < 400) {
> // Success!
> var hist = $$("buildHistory");
>
> var newhist = document.createElement('div');
> newhist.innerHTML = this.response.text;
> newhist.headers = hist.headers
>
> relace(hist, newhist);
> fireBuildHistoryChanged();
> } else {
> // We reached our target server, but it returned an error
> }
> };
>
> request.onerror = function() {
> // There was a connection error of some sort
> };
>
> request.send();
>
> ```
>
>
> ```
> new Ajax.Request("${it.baseUrl}/buildHistory/all",{
> method: "get",
> onComplete: function(rsp,_) {
>
> var hist = $$("buildHistory");
>
> var newhist = document.createElement('div');
> newhist.innerHTML = rsp.responseText;
> newhist.headers = hist.headers
>
> replace(hist, newhist);
> fireBuildHistoryChanged();
> }
> });
> }
> ```
> becomes
> ```
>
>
> On Tue, May 19, 2020 at 12:27 PM Ullrich Hafner > wrote:
>
>> The problem with the alternatives is that they have no server
>> counterpart. Or how do you route the requests to the Java model when using
>> jQuery directly?
>>
>> Am 19.05.2020 um 20:52 schrieb 'Gavin Mogan' via Jenkins Developers <
>> jenkin...@googlegroups.com >:
>>
>> Ajax.Request is actually prototype, and I strongly recommend not using
>> it, as its incredibly old and has messed with a lot of standard apis.
>>
>> I recommend using jquery, or the native alternatives
>> (XMLHttpRequest/fetch)
>>
>> http://youmightnotneedjquery.com/ (search for ajax) has some good
>> examples
>>
>> On Tue, May 19, 2020 at 11:49 AM Ullrich Hafner > > wrote:
>>
>>> You can also have a look at some plugins that use the new JS UI
>>> components (bootstrap, charts, datatables). All of these plugins use Ajax
>>> to populate charts and tables: they also use the techniques described in
>>> the wiki and I can confirm that it works! What exactly is not working in
>>> your plugin?
>>>
>>> The plugins that use these JA Ajax elements are
>>> - warnings plugin
>>> - forensics plugin
>>> - autograding plugin
>>>
>>>
>>> Am 19.05.2020 um 15:58 schrieb Aytunc Beken >> >:
>>>
>>> I will check. Thanks!
>>>
>>> On Tuesday, May 19, 2020 at 3:57:27 PM UTC+2, Oleg Nenashev wrote:
>>>>
>>>> Jenkins Build History widget is probably the best example of AJAX usage
>>>> in Jenkins:
>>>>
>>>>- JAVA:
>>>>
>>>> https://github.com/jenkinsci/jenkins/blob/449c5aced523a6e66fe3d6a804e5dbfd5c5c67c6/core/src/main/java/hudson/widgets/HistoryWidget.java#L210-L256
>>>>- Jelly with embedded JavaScriptL
>>>>
>>>> https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/widgets/HistoryWidget/index.jelly#L79-L115
>>>>
>>>> BR, Oleg
>>>>
>>>> On Tuesday, May 19, 2020 at 3:35:15 PM UTC+2, Aytunc Beken wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I am trying to implement Ajax call in UI page. I could only find this
>>>>> page (
>>>>> https://wiki.jenkins.io/display/JENKINS/AJAX+with+JavaScript+proxy)
>>>>> however it did not worked.
>>>>>
>>>>> I will be glad if anyone can point some help.
>>>>>
>>>>> - Documentation
>>>>> - Plugin implemented Ajax
>>>>> - Plugin implemented Jquery
>>>>>
>>>>>
>>>>> Thanks a lot.
>>>>>
>>>>>
>>> --
>>> You received this message because you are subscribed to the
Re: Plugin Development - Ajax Example
I will check. Thanks! On Tuesday, May 19, 2020 at 3:57:27 PM UTC+2, Oleg Nenashev wrote: > > Jenkins Build History widget is probably the best example of AJAX usage in > Jenkins: > >- JAVA: > > https://github.com/jenkinsci/jenkins/blob/449c5aced523a6e66fe3d6a804e5dbfd5c5c67c6/core/src/main/java/hudson/widgets/HistoryWidget.java#L210-L256 >- Jelly with embedded JavaScriptL > > https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/widgets/HistoryWidget/index.jelly#L79-L115 > > BR, Oleg > > On Tuesday, May 19, 2020 at 3:35:15 PM UTC+2, Aytunc Beken wrote: >> >> Hi, >> >> I am trying to implement Ajax call in UI page. I could only find this >> page (https://wiki.jenkins.io/display/JENKINS/AJAX+with+JavaScript+proxy) >> however it did not worked. >> >> I will be glad if anyone can point some help. >> >> - Documentation >> - Plugin implemented Ajax >> - Plugin implemented Jquery >> >> >> Thanks a lot. >> >> -- 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/15189aee-5005-46a0-9569-36e24a70e02c%40googlegroups.com.
Plugin Development - Ajax Example
Hi, I am trying to implement Ajax call in UI page. I could only find this page (https://wiki.jenkins.io/display/JENKINS/AJAX+with+JavaScript+proxy) however it did not worked. I will be glad if anyone can point some help. - Documentation - Plugin implemented Ajax - Plugin implemented Jquery Thanks a lot. -- 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/282cb068-a394-40aa-a15c-4eb1bd5d6c8b%40googlegroups.com.
Re: How to Change Plugin Name - Remote File Plugin
Thanks for the all responses. Again I would like to get opinions about the name of the plugin. I received some feedback from users where they addresses that name of the plugin do no reflect what it does. I know we can not use some special words in name, just wondering, can "Remote Pipeline File" or "External Pipeline File" be used ? On Sunday, April 5, 2020 at 4:34:17 AM UTC+2, Gavin Mogan wrote: > > All the plugins that had wiki as the when I did the first migration, > should already have a redirect in place. > > For whatever reason remote-file wasn't included in the batch. Was url set > wrong? or was it blacklisted or something? > > Either way I included it in my new batch - > https://github.com/jenkins-infra/jenkins-infra/pull/1456 > > On Fri, Apr 3, 2020 at 12:25 AM Oleg Nenashev > wrote: > >> Once the plugin documentation is migrated to GitHub, we can add a redirect >> >> <https://github.com/jenkins-infra/jenkins-infra/blob/staging/dist/profile/templates/confluence/vhost.conf>on >> >> the Jenkins Infra side. After that the Wiki page will be gone forever from >> the user perspective. >> >> Another thing we could do it to whitelist more GitHub topics so that >> Plugin site and plugin manager show the plugin in proper categories. Right >> now https://plugins.jenkins.io/remote-file/ shows only "pipeline". We >> could even add a special label for WorkflowBranchProjectFactory >> implementations. >> >> BR, Oleg >> >> >> On Thursday, April 2, 2020 at 7:00:12 PM UTC+2, Gavin Mogan wrote: >>> >>> Wiki is slowly going away. Most things will be populated from pom file >>> though. >>> >>> I would take the opportunity to make sure your documentation (url in >>> pom) is pointed at github so you can make changes as needed. >>> >>> Blog: https://jenkins.io/blog/2019/10/21/plugin-docs-on-github/ >>> Docs: >>> https://jenkins.io/doc/developer/publishing/documentation/#using-github-as-a-source-of-documentation >>> >>> On Thu, Apr 2, 2020 at 7:52 AM Aytunc Beken wrote: >>> >>>> Thanks, >>>> >>>> I am also interested in changing the name Wiki page name, is that >>>> possible? >>>> >>>> On Sat, Mar 28, 2020 at 6:00 PM James Nord wrote: >>>> >>>>> change the 'name' element in pom.xml. >>>>> >>>>> you will also need to change any references you have in the plugin >>>>> (index.jelly for example). >>>>> >>>>> just don't change the artifactId as this will make it a new plugin. >>>>> >>>>> -- >>>>> 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/575lIZaiqq0/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/6c30a2a9-bb0b-4a58-a0e1-a19c3e414c03%40googlegroups.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/CAKDu2g%2B1dbD2w_hsQ4z77g125-CzJ%3D9_TZjdqpaserbtfN%3DV8w%40mail.gmail.com >>>> >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAKDu2g%2B1dbD2w_hsQ4z77g125-CzJ%3D9_TZjdqpaserbtfN%3DV8w%40mail.gmail.com?utm_medium=email_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 jenkin...@googlegroups.com . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/1f9f6b0d-61c2-4bcd-84f4-74f33c0d7e71%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/1f9f6b0d-61c2-4bcd-84f4-74f33c0d7e71%40googlegroups.com?utm_medium=email_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/af1e3cd3-e8a0-4035-94ad-5c0778e10603%40googlegroups.com.
Re: How to Change Plugin Name - Remote File Plugin
Thanks, I am also interested in changing the name Wiki page name, is that possible? On Sat, Mar 28, 2020 at 6:00 PM James Nord wrote: > change the 'name' element in pom.xml. > > you will also need to change any references you have in the plugin > (index.jelly for example). > > just don't change the artifactId as this will make it a new plugin. > > -- > 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/575lIZaiqq0/unsubscribe. > To unsubscribe from this group and all its topics, 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/6c30a2a9-bb0b-4a58-a0e1-a19c3e414c03%40googlegroups.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/CAKDu2g%2B1dbD2w_hsQ4z77g125-CzJ%3D9_TZjdqpaserbtfN%3DV8w%40mail.gmail.com.
How to Change Plugin Name - Remote File Plugin
Hi, I would like to change "Remote File Plugin" to more understandable name like "Multibranch Remote Jenkinsfile Plugin". - It this name okay to use ? - How can I do that ? Thanks. https://issues.jenkins-ci.org/browse/JENKINS-45273?focusedCommentId=387340=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-387340 -- 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/f83ac688-1328-4345-93ba-98e06695a389%40googlegroups.com.
Re: About - Simple Pull Request Plugin
Hi Oleg, Thanks a lot. I read all the document, all seems fine. Just, I want to be sure, I understood that traveling or attending meetings physically is not required. If these are true, then please count me in :) On Wednesday, February 26, 2020 at 7:45:38 PM UTC+1, Oleg Nenashev wrote: > > Hi, > > Thanks for your interest! It would be great to work with you on this > project > > We have all the requirements documented here: > https://jenkins.io/projects/gsoc/mentors/ > It is a long read, https://jenkins.io/blog/2019/12/20/call-for-mentors/ is > probably a quicker intro. > TL;DR: There is no need to make any commitment until April, but in summer > GSoC mentorship may require around 5 hours per week, give or take. > > Best regards, > Oleg > > On Wednesday, February 26, 2020 at 5:18:11 PM UTC+1, Aytunc Beken wrote: >> >> Hi Oleg, >> >> Came to my mind after I saw the Gsoc Approval. If you want/need, I will >> be happy to support/help you for mentoring this plugin. >> I do not know what are the requirements for this, just wanted to say this. >> >> Thanks. >> >> On Tuesday, February 25, 2020 at 9:28:44 AM UTC+1, Aytunc Beken wrote: >>> >>> Hi Oleg, >>> >>> First I want to focus on this new Pipeline As Yaml Plugin. After that, I >>> can work in this plugin (SPPR) also. >>> >>> So thanks a lot for the support, I will start working on this plugin >>> immediately. >>> >>> >>> On Monday, February 24, 2020 at 2:03:32 PM UTC+1, Oleg Nenashev wrote: >>>> >>>> Hi Aytunc, >>>> >>>> - 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 ? >>>>> >>>> As long as you follow the MIT License requirements, sure. >>>> You may also want to consider taking over this plugin or contributing >>>> to its codebase, but it is up to you. >>>> Obviously, it would be great to have this new plugin as oprn-source. >>>> >>>> - @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 >>>>> >>>> >>>> GSoC 2020 lists potential project ideas, it is not a problem if some >>>> ideas overlap with pending work. Students would need to consider the >>>> ongoing developments in their project proposals, and ideally to sync-up >>>> with stakeholders in the dev list. >>>> It would be great to put a notice with a link to this thread so that >>>> potential applicants know there is ongoing parallel effort. >>>> >>>> BR, Oleg >>>> >>>> >>>> >>>> On Sat, Feb 22, 2020 at 2:25 PM Aytunc Beken >>>> wrote: >>>> >>>>> 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 &
Re: About - Simple Pull Request Plugin
Hi Oleg, Came to my mind after I saw the Gsoc Approval. If you want/need, I will be happy to support/help you for mentoring this plugin. I do not know what are the requirements for this, just wanted to say this. Thanks. On Tuesday, February 25, 2020 at 9:28:44 AM UTC+1, Aytunc Beken wrote: > > Hi Oleg, > > First I want to focus on this new Pipeline As Yaml Plugin. After that, I > can work in this plugin (SPPR) also. > > So thanks a lot for the support, I will start working on this plugin > immediately. > > > On Monday, February 24, 2020 at 2:03:32 PM UTC+1, Oleg Nenashev wrote: >> >> Hi Aytunc, >> >> - 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 ? >>> >> As long as you follow the MIT License requirements, sure. >> You may also want to consider taking over this plugin or contributing to >> its codebase, but it is up to you. >> Obviously, it would be great to have this new plugin as oprn-source. >> >> - @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 >>> >> >> GSoC 2020 lists potential project ideas, it is not a problem if some >> ideas overlap with pending work. Students would need to consider the >> ongoing developments in their project proposals, and ideally to sync-up >> with stakeholders in the dev list. >> It would be great to put a notice with a link to this thread so that >> potential applicants know there is ongoing parallel effort. >> >> BR, Oleg >> >> >> >> On Sat, Feb 22, 2020 at 2:25 PM Aytunc Beken wrote: >> >>> 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 Tua
Re: [GSOC 2020 PROJECT IDEA] Autobuild without Jenkinsfile
Hey, You can also check this plugin, https://plugins.jenkins.io/remote-file/. Idea is to have centralized Jenkins file for all multibranch projects. May be it can be helpful. -- 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/fab58d3b-0442-465f-99e9-a4e0a85c1b17%40googlegroups.com.
Re: About - Simple Pull Request Plugin
Hi Oleg, First I want to focus on this new Pipeline As Yaml Plugin. After that, I can work in this plugin (SPPR) also. So thanks a lot for the support, I will start working on this plugin immediately. On Monday, February 24, 2020 at 2:03:32 PM UTC+1, Oleg Nenashev wrote: > > Hi Aytunc, > > - 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 ? >> > As long as you follow the MIT License requirements, sure. > You may also want to consider taking over this plugin or contributing to > its codebase, but it is up to you. > Obviously, it would be great to have this new plugin as oprn-source. > > - @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 >> > > GSoC 2020 lists potential project ideas, it is not a problem if some ideas > overlap with pending work. Students would need to consider the ongoing > developments in their project proposals, and ideally to sync-up with > stakeholders in the dev list. > It would be great to put a notice with a link to this thread so that > potential applicants know there is ongoing parallel effort. > > BR, Oleg > > > > On Sat, Feb 22, 2020 at 2:25 PM Aytunc Beken > wrote: > >> 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.modeldefi
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 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/0bbcc3ac-9f88-45be-afb1-21c82f52b38c%40googlegroups.com.
Re: About - Simple Pull Request Plugin
Hi Oleg, Sorry for my late response. I think the requirements you defined will make plugin more usable. So I will try to also implement those requirements. So I am planing to start working on this plugin. How should I proceed ? Thanks. On Thursday, February 13, 2020 at 8:35:51 PM UTC+1, Oleg Nenashev wrote: > > Hi Aytunc, > > Your approach is quite similar to what is documented in my project idea. > I went a bit beyond w.r.t implementation options, but the approach you > suggest is one of the most straightforward ways to implement Pipeline as > YAML. > > - Develop a Converter which will convert yml files to legacy declarative >> or scripted pipelines . >> > There is no legacy declarative or scripted pipelines :) . They keep > evolving, and I do not think that YAML support is going to replace them > anytime soon. > https://github.com/jenkinsci/simple-pull-request-job-plugin is an example > of such converter. > The converter approach makes total sense as a standalone solution, > > Develop a converter screen where uses can convert their declarative >> pipelines to yaml or vice versa. >> > Would be great > > > > On Wednesday, February 12, 2020 at 1:50:25 PM UTC+1, Aytunc Beken wrote: >> >> Hi Oleg, >> >> Thanks for the details. The projects which are proposed/developed are >> similar what I want to achieve. However, approach may differ. >> >> What I planned was this: >> - Develop a Converter which will convert yml files to legacy declarative >> or scripted pipelines . >>Reason: Just wanted not to interfere with the core pipeline mechanism. >> A smart, well developed converter will be enough to make it work. >> - Develop a converter screen where uses can convert their declarative >> pipelines to yaml or vice versa. >>Reason: Users should not spend time to convert their legacy pipelines. >> UI converter will same lots of time. >> >> How these sounds for you ? Not sure how much it is parallel within your >> mind. >> >> Thanks. >> >> >> On Wednesday, February 12, 2020 at 1:26:47 PM UTC+1, Oleg Nenashev wrote: >>> >>> UPD. I have officially submitted this project idea: >>> https://groups.google.com/forum/#!topic/jenkins-pipeline-authoring-sig/Ko8KTEcK_vY >>> >>> and jenkins-infra/jenkins.io#2849 >>> <https://github.com/jenkins-infra/jenkins.io/pull/2849> >>> >>> Hi Aytunc, what would be your plan there? the GSoC project idea does not >>> block anyone from working on this area, but it might make sense to sync-up >>> with other interested contributors. >>> >>> Best regards, >>> Oleg >>> >>> On Monday, February 10, 2020 at 5:14:51 PM UTC+1, Oleg Nenashev wrote: >>>> >>>> Hi, >>>> >>>> No ongoing work right now, but indeed there is a lot of interest in the >>>> community. >>>> If you are interested to work on it, this is great! >>>> >>>> Actually I am planning to submit a follow-up project idea for Google >>>> Summer of Code 2020. I have already referenced it in >>>> https://gitter.im/jenkinsci/pipeline-authoring-sig , but I have not >>>> announced it yet through official channels. >>>> The draft idea is here: >>>> https://github.com/jenkins-infra/jenkins.io/blob/ff5527bb98f1b28159f88894c9abbe346eeaf3d2/content/projects/gsoc/2020/project-ideas/pipeline-as-yaml-experiment.adoc >>>> If you plan to work on this area in short-term, I will adjust my >>>> project idea accordingly. >>>> >>>> Best regards, >>>> Oleg >>>> >>>> >>>> On Monday, February 10, 2020 at 11:05:01 AM UTC+1, Aytunc Beken wrote: >>>>> >>>>> Hi, >>>>> >>>>> I was planning to work on a new plugin for enabling Yaml files for >>>>> Pipelines. However I found this plugin and it looks similar. >>>>> >>>>> https://jenkins.io/blog/2018/07/17/simple-pull-request-plugin/ >>>>> >>>>> Does any one knows about it? Does is still continues ? >>>>> >>>>> 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/93176789-754f-4526-8226-b0e3c081bf12%40googlegroups.com.
Re: About - Simple Pull Request Plugin
Hi Oleg, Thanks for the details. The projects which are proposed/developed are similar what I want to achieve. However, approach may differ. What I planned was this: - Develop a Converter which will convert yml files to legacy declarative or scripted pipelines . Reason: Just wanted not to interfere with the core pipeline mechanism. A smart, well developed converter will be enough to make it work. - Develop a converter screen where uses can convert their declarative pipelines to yaml or vice versa. Reason: Users should not spend time to convert their legacy pipelines. UI converter will same lots of time. How these sounds for you ? Not sure how much it is parallel within your mind. Thanks. On Wednesday, February 12, 2020 at 1:26:47 PM UTC+1, Oleg Nenashev wrote: > > UPD. I have officially submitted this project idea: > https://groups.google.com/forum/#!topic/jenkins-pipeline-authoring-sig/Ko8KTEcK_vY > > and jenkins-infra/jenkins.io#2849 > <https://github.com/jenkins-infra/jenkins.io/pull/2849> > > Hi Aytunc, what would be your plan there? the GSoC project idea does not > block anyone from working on this area, but it might make sense to sync-up > with other interested contributors. > > Best regards, > Oleg > > On Monday, February 10, 2020 at 5:14:51 PM UTC+1, Oleg Nenashev wrote: >> >> Hi, >> >> No ongoing work right now, but indeed there is a lot of interest in the >> community. >> If you are interested to work on it, this is great! >> >> Actually I am planning to submit a follow-up project idea for Google >> Summer of Code 2020. I have already referenced it in >> https://gitter.im/jenkinsci/pipeline-authoring-sig , but I have not >> announced it yet through official channels. >> The draft idea is here: >> https://github.com/jenkins-infra/jenkins.io/blob/ff5527bb98f1b28159f88894c9abbe346eeaf3d2/content/projects/gsoc/2020/project-ideas/pipeline-as-yaml-experiment.adoc >> If you plan to work on this area in short-term, I will adjust my project >> idea accordingly. >> >> Best regards, >> Oleg >> >> >> On Monday, February 10, 2020 at 11:05:01 AM UTC+1, Aytunc Beken wrote: >>> >>> Hi, >>> >>> I was planning to work on a new plugin for enabling Yaml files for >>> Pipelines. However I found this plugin and it looks similar. >>> >>> https://jenkins.io/blog/2018/07/17/simple-pull-request-plugin/ >>> >>> Does any one knows about it? Does is still continues ? >>> >>> 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/f61408ea-63a9-4ea6-8a1c-b47e5b6d3385%40googlegroups.com.
About - Simple Pull Request Plugin
Hi, I was planning to work on a new plugin for enabling Yaml files for Pipelines. However I found this plugin and it looks similar. https://jenkins.io/blog/2018/07/17/simple-pull-request-plugin/ Does any one knows about it? Does is still continues ? 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/CAKDu2gLzK11Crc34BR5O%2BnDVCeAMyAX1PYaaWnbOj0gOWtHeew%40mail.gmail.com.
Light Runner With Page
Dear All, I would like to get suggestions about plugin development. Currently I am developing a plugin which do lots of in the background and I log things to Jenkins Server logs. I wan to create a page or light run like the one in MultiBranch Pipeline Scan log where user can follow what is going on. If anyone have any suggestions or ideas about this, I will be glad if they contact me. Thanks a lot. #jenkinsrocks -- 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/CAKDu2gJ4PDcyFi517WJfTsiQ4-9EVhBb%3DjrD38RxS4VpmzSRuA%40mail.gmail.com.
Re: Plugin Adoption - Purge Job History Plugin
Hi, My PR is merged. Can someone add me as maintainer in the repository ? Thanks https://github.com/jenkinsci/purge-job-history-plugin On Tue, Jul 30, 2019 at 11:39 PM Daniel Beck wrote: > https://github.com/jenkins-infra/repository-permissions-updater/ is the > repository we use as reference who is a maintainer. > > File a PR to the file corresponding to the plugin, and make sure to > reference the maintainer's public approval there. > > > On 30. Jul 2019, at 16:52, Aytunc Beken > wrote: > > > > Hi, > > > > I would like to adopt Purge Job History Plugin ( > https://github.com/jenkinsci/purge-job-history-plugin) if possible. > Current maintainer accepted adoption, you can see his consent in this pull > request ( https://github.com/jenkinsci/purge-job-history-plugin/pull/3 ) > > > > My GitHub account is https://github.com/aytuncbeken > > My Jenkins account Id is aytuncbeken. > > > > Thanks in advance. > > > > 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/CAKDu2gKiqApnN6dGKmNchdnxW1GOdJnXhV3M%3DenOzuPtKijTSw%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/0C313B5E-FE03-4E03-A462-AD59A456128A%40beckweb.net > . > -- 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/CAKDu2gK5HaZWJBpDSYbZb-0igdft9k683i58Yq%3Da78qKzPXOnQ%40mail.gmail.com.
Re: Plugin Adoption - Purge Job History Plugin
Hi Daniel, I will be glad if someone can approve my pull request for permission update. https://github.com/jenkins-infra/repository-permissions-updater/pull/1245 Thanks On Tue, Jul 30, 2019 at 11:39 PM Daniel Beck wrote: > https://github.com/jenkins-infra/repository-permissions-updater/ is the > repository we use as reference who is a maintainer. > > File a PR to the file corresponding to the plugin, and make sure to > reference the maintainer's public approval there. > > > On 30. Jul 2019, at 16:52, Aytunc Beken > wrote: > > > > Hi, > > > > I would like to adopt Purge Job History Plugin ( > https://github.com/jenkinsci/purge-job-history-plugin) if possible. > Current maintainer accepted adoption, you can see his consent in this pull > request ( https://github.com/jenkinsci/purge-job-history-plugin/pull/3 ) > > > > My GitHub account is https://github.com/aytuncbeken > > My Jenkins account Id is aytuncbeken. > > > > Thanks in advance. > > > > 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/CAKDu2gKiqApnN6dGKmNchdnxW1GOdJnXhV3M%3DenOzuPtKijTSw%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/0C313B5E-FE03-4E03-A462-AD59A456128A%40beckweb.net > . > -- 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/CAKDu2gJ38OPz_KwHEZqQ%3D_TUAPOAK%3Dn1JMdxRv2e1qJsPydL_g%40mail.gmail.com.
Plugin Adoption - Purge Job History Plugin
Hi, I would like to adopt Purge Job History Plugin ( https://github.com/jenkinsci/purge-job-history-plugin) if possible. Current maintainer accepted adoption, you can see his consent in this pull request ( https://github.com/jenkinsci/purge-job-history-plugin/pull/3 ) My GitHub account is https://github.com/aytuncbeken My Jenkins account Id is aytuncbeken. Thanks in advance. 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/CAKDu2gKiqApnN6dGKmNchdnxW1GOdJnXhV3M%3DenOzuPtKijTSw%40mail.gmail.com.
