Re: Change the root fork of an existing plugin

Ah, I thought the "forking process" was the default behaviour when adding a plugin to the JenkinsCI organisation. Thank you all for your answers, indeed breaking the fork link is the simpler solution. I'll ask github directly. Kind regards Aurélien On Fri, Aug 26, 2022 at 6:42 PM Basil Crow

Re: Change the root fork of an existing plugin

On Fri, Aug 26, 2022 at 9:36 AM 'Gavin Mogan' via Jenkins Developers wrote: > > Advantage of jenkins being the source is that github search will work org > wide for it. Also, CD is only supported when the GitHub repository is in the jenkinsci GitHub organization. In general I think we prefer

Re: Change the root fork of an existing plugin

You can ask github to break that link (so github doesn't say its forked), and then your development can be on a fork. You can probably ask them to change the source as well. Advantage of jenkins being the source is that github search will work org wide for it. On Fri, Aug 26, 2022 at 9:07 AM

Change the root fork of an existing plugin

Hello, We recently did some changes in our Github organisation (CerberusTesting ) and would like to spread changes to existing forks that now use deprecated root repositories, as our Jenkins plugin. The concerned plugin is the following:

Re: Apache Jelly grammar and parser

I think the best way to describe it is by showing those cases. That should illustrate my answer to Tim. You can find all the sample Jelly strings here: https://github.com/glasswalk3r/jenkins-translation-tool/tree/refactor/jelly_parser/t/samples . This is an ad hoc set of files: first I started

Re: Cannot deploy anymore to my plugin on repo.jenkins-ci.org

On Fri, Aug 26, 2022 at 12:41 AM 'Réda Housni Alaoui' via Jenkins Developers wrote: > Is this issue still unfixed? The issue is fixed. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving

Re: Apache Jelly grammar and parser

Thanks Tim! That is what I was expecting, but I got some cases that don't follow the format you just described. On Thu, Aug 25, 2022 at 4:28 PM Tim Van Holder wrote: > Hi Alceu, > > I would expect that in most cases, the jelly files used by Jenkins and its > plugins would already be using

Re: Apache Jelly grammar and parser

Hello Basil, Thanks for the references, I'll be checking them ASAP. The Jelly part of Apache Commons seems to be an abandoned project indeed (I tried their mailing list, no answers from that). It would be interesting if I wouldn't need to duplicate the logic in Perl, but I'm not sure how

Re: Apache Jelly grammar and parser

On Thu, Aug 25, 2022 at 9:28 PM Tim Van Holder wrote: > I would expect that in most cases, the jelly files used by Jenkins and its > plugins would already be using localized strings (like "${%Hello World}" > which will use the "Hello World" resource from the bundle matching the > jelly file's

Re: Apache Jelly grammar and parser

On Wed, Aug 24, 2022 at 6:29 PM Alceu Rodrigues de Freitas Junior < alceu.freitas...@gmail.com> wrote: > I've being working in a CLI to parse the properties and Jelly files from > the Jenkins project, in order to help the translation process from English > to other languages. > > The project is

Re: Cannot deploy anymore to my plugin on repo.jenkins-ci.org

Hi all, Is this issue still unfixed? I suppose this is why the gerrit plugin didn't receive any upgrade for almost a year (last commit on September 2021) ? If this is the case, please do something or this plugin is going to die. Regards Le jeudi 9 septembre 2021 à 00:18:15 UTC+2,