Re: Hosting New Jenkins plugin on Jenkins

Thank you all for help. We can see our plugin is published to market place. Appreciated all the guidance and support. On Thu, Nov 30, 2023 at 2:30 PM 'Gavin Mogan' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > we usually say up to 3 hours since multiple parts have to line up,

Re: Hosting New Jenkins plugin on Jenkins

https://updates.jenkins.io/latest/amazon-inspector-image-scanner.hpi?mirrorlist shows that the plugin is already available on 4 of the mirrors. https://plugins.jenkins.io/amazon-inspector-image-scanner/ shows it is available on the plugins site (at least to me). Mark Waite On Thursday,

Re: Hosting New Jenkins plugin on Jenkins

I don't recall exactly but someone in the community might know exactly Le jeu. 30 nov. 2023, 18:59, naveen sharma a écrit : > Hi Adrien, Please suggest What's the frequency to update The plugin site ( > plugins.jenkins.io). We are announcing it shortly and expecting to be > available on

Re: Hosting New Jenkins plugin on Jenkins

Great. Thank you for help understanding process. On Fri, Nov 17, 2023 at 2:18 PM Adrien Lecharpentier < adrien.lecharpent...@gmail.com> wrote: > Hello, > > The hosting process timing is not really long if there is no major issues > found. The sooner you start it the better. > For the

Re: Hosting New Jenkins plugin on Jenkins

After you do a release, It should show up in update center first (inside of jenkins) within a few minutes, and plugins.jenkins.io up to 3 hours later (depending on when last run was) On Fri, Nov 17, 2023 at 11:18 AM Adrien Lecharpentier < adrien.lecharpent...@gmail.com> wrote: > Hello, > > The

Re: Hosting New Jenkins plugin on Jenkins

Hello, The hosting process timing is not really long if there is no major issues found. The sooner you start it the better. For the availability of the plugin in the update center (what you called the market place I believe), you totally control that: once your hosting request is completed, you

Re: Hosting

Always room for more :) On Thu, 27 Oct 2022 at 15:11, Adrien Lecharpentier < adrien.lecharpent...@gmail.com> wrote: > I would also be happy to help on the hosting process. > Is there any room for me to help? > > Le dim. 9 oct. 2022 à 20:11, 'Herve Le Meur' via Jenkins Developers < >

Re: Hosting

I would also be happy to help on the hosting process. Is there any room for me to help? Le dim. 9 oct. 2022 à 20:11, 'Herve Le Meur' via Jenkins Developers < jenkinsci-dev@googlegroups.com> a écrit : > Wiling to help too :) > I'll take care of your request tomorrow morning NotMyFault. > > Le

Re: Hosting

Wiling to help too :) I'll take care of your request tomorrow morning NotMyFault. Le dim. 9 oct. 2022, 20:01, Alexander Brandes a écrit : > Submitted https://github.com/jenkins-infra/helpdesk/issues/3163 > > On Sunday, 9 October 2022 at 19:49:03 UTC+2 ga...@gavinmogan.com wrote: > >> I think

Re: Hosting

Submitted https://github.com/jenkins-infra/helpdesk/issues/3163 On Sunday, 9 October 2022 at 19:49:03 UTC+2 ga...@gavinmogan.com wrote: > I think you'll have to request via helpdesk permissions for > https://github.com/orgs/jenkins-infra/teams/hosting/members > > On Sun, Oct 9, 2022 at 9:07 AM

Re: Hosting

I think you'll have to request via helpdesk permissions for https://github.com/orgs/jenkins-infra/teams/hosting/members On Sun, Oct 9, 2022 at 9:07 AM Alexander Brandes wrote: > Hey, > > I'd be up to assist with handling the RPU too. > > Best regards, > Alex > > On Sunday, 9 October 2022 at

Re: Hosting

Hey, I'd be up to assist with handling the RPU too. Best regards, Alex On Sunday, 9 October 2022 at 17:53:13 UTC+2 slide wrote: > I can help with that. I know the process is different from when I was > doing it before, but I can come up to speed. > > On Sat, Oct 8, 2022, 21:11 'Gavin Mogan'

Re: Hosting

I can help with that. I know the process is different from when I was doing it before, but I can come up to speed. On Sat, Oct 8, 2022, 21:11 'Gavin Mogan' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > I'm looking for someone interested in replacing me. Right now it seems to

Re: Hosting

I'm looking for someone interested in replacing me. Right now it seems to just be tim and myself. Tim's been amazing and processing all the new plugin requests. Wrote tooling to help verify things, etc. He's already doing a ton of other things, so I've been trying to help out with the maintainer

Re: Hosting

So last ticket is now closed. On Sun, Apr 10, 2022 at 1:16 PM Gavin Mogan wrote: > > Looks like its mostly waiting for security > https://issues.jenkins.io/browse/HOSTING-1160 > > On Sun, Apr 10, 2022 at 12:40 PM Alex Earl wrote: > > > > Anything I can do to help get that one over the finish

Re: Hosting

Looks like its mostly waiting for security https://issues.jenkins.io/browse/HOSTING-1160 On Sun, Apr 10, 2022 at 12:40 PM Alex Earl wrote: > > Anything I can do to help get that one over the finish line? > > On Fri, Apr 8, 2022 at 9:10 AM 'Gavin Mogan' via Jenkins Developers > wrote: >> >> We

Re: Hosting

Anything I can do to help get that one over the finish line? On Fri, Apr 8, 2022 at 9:10 AM 'Gavin Mogan' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > We have one left mostly waiting on security > > On Fri., Apr. 8, 2022, 9:08 a.m. Tim Jacomb, wrote: > >> It was kept while

Re: Hosting

We have one left mostly waiting on security On Fri., Apr. 8, 2022, 9:08 a.m. Tim Jacomb, wrote: > It was kept while we processed the remaining stragglers in Jira, I think > those have finished now so we can remove the code. > > The checker and hosted was copied into the RPU repo > > On Fri, 8

Re: Hosting

It was kept while we processed the remaining stragglers in Jira, I think those have finished now so we can remove the code. The checker and hosted was copied into the RPU repo On Fri, 8 Apr 2022 at 15:30, slide wrote: > Since I have been out of the loop for a while, I was reviewing the >

Re: Hosting && Gavin Schedule

Gavin, This is a conversation I am very interested in. I think having a clear "tiering" system would be fantastic and was one of the first things on my plate to look into. Do you think I can maybe set up a call with you, Mark Waite, Daniel and myself? Thank you for bringing this up! Jake

Re: Hosting && Gavin Schedule

We've been doing it for a long time already. Allowing insecure plugins into the infra creates a LOT of work for the security folks. I think it's a benefit to run the security checks to reduce that already heavy workload. It usually just takes a couple of back and forth discussions on Jira for

Re: Hosting && Gavin Schedule

I understand the case that we wan't to make sure users/administrators can somehow trust what is offered in the public/official update center. But I don't like the idea of restricting or putting up barriers for new contributors to join the project, or hindering the potential innovation coming in

Re: Hosting && Gavin Schedule

I can run them before approving / reviewing them In addition, i would like to help manage end users expectation about what kind of support a plugin might have (Core, Community, Professional, etc). Just one more thing to do on the todo list. Gavin On Fri, Sep 17, 2021 at 8:16 PM Gavin Mogan

Re: Hosting && Gavin Schedule

I Lost track of where you did the ping to me. Sounds out I need to be clearer. if I get more scripts to run, I can run them before On Thu, Sep 16, 2021 at 10:10 PM Gavin Mogan wrote: > I'm sorry I thought you were offering them up. I didn't realize you were > asking if I wanted them. I can

Re: Hosting && Gavin Schedule

I'm sorry I thought you were offering them up. I didn't realize you were asking if I wanted them. I can certainly try them out As for the banner. It might be worth some sort of verified publisher or something else that indicates when the company maintains the plugin and you should contact thier

Re: Hosting && Gavin Schedule

> On 17. Sep 2021, at 04:32, 'Gavin Mogan' via Jenkins Developers > wrote: > > So sure, someone other than you can do more in-depth reviews of the code. > I've been doing absolute basic checks with the expertise I have. I was very > clear when I took over the hosting lead position that I

Re: Hosting

I am ready to help again on hosting. Similar to how Gavin phrased it, I'll help move tickets through the pipe. Cheers Le jeu. 26 août 2021 à 08:23, Tim Jacomb a écrit : > You can just click leave team > > On Wed, 25 Aug 2021 at 22:33, Slide wrote: > >> I should probably be removed from that

Re: Hosting

You can just click leave team On Wed, 25 Aug 2021 at 22:33, Slide wrote: > I should probably be removed from that team as well. > > On Wed, Aug 25, 2021 at 1:18 PM Tim Jacomb wrote: > >> Oleg has permissions on the team or Olivier: >> https://github.com/orgs/jenkins-infra/teams/hosting/members

Re: Hosting

I should probably be removed from that team as well. On Wed, Aug 25, 2021 at 1:18 PM Tim Jacomb wrote: > Oleg has permissions on the team or Olivier: > https://github.com/orgs/jenkins-infra/teams/hosting/members > > > On Wed, 25 Aug 2021 at 21:03, Slide wrote: > >> Those are the basics, just

Re: Hosting

Oleg has permissions on the team or Olivier: https://github.com/orgs/jenkins-infra/teams/hosting/members On Wed, 25 Aug 2021 at 21:03, Slide wrote: > Those are the basics, just the bot checker (jenkins-admin: check > HOSTING-) in the jenkins-hosting channel. > > On Wed, Aug 25, 2021 at 12:20

Re: Hosting

Those are the basics, just the bot checker (jenkins-admin: check HOSTING-) in the jenkins-hosting channel. On Wed, Aug 25, 2021 at 12:20 PM 'Gavin Mogan' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Okay, making it official. If nobody else speaks up as wanting to take over >

Re: Hosting

Okay, making it official. If nobody else speaks up as wanting to take over as lead before end of week (Friday night pacific time) I'll take over and make sure hosting requests get moving. I think i've fixed my irc client so I should stay in the channels now. Can I get invited to the hosting

Re: Hosting

Thank you very much Alex for the effort you invested on this area. This is a really important piece of the process for the security perspective. The fact that you did the preliminary security checks and if something was weird, to ask the security team to make a more complete audit, was of a

Re: Hosting

If nobody else is able to step up, I can take it, but I won't be code reviewing and as quickly as possible switch it from jira+irc to https://github.com/jenkins-infra/repository-permissions-updater + issue bot All i'll be doing is "Is there another plugin that sounds similar? Does it pass the

Re: Hosting Team

Hi all, We did not have a meeting today, because there were no participants except Alex Earl and Daniel Beck. It was a nice chat though. For the original topic, we plan to restart the Doodle poll and reconvene after we find more interested contributors. If you are interested to start

Re: Hosting Team

would like to join, but I cannot attend the meeting :( On Wednesday, May 5, 2021 at 2:26:57 PM UTC+2 slide wrote: > The meeting is at 4PM UTC, my mistake. > > On Tuesday, May 4, 2021 at 1:14:53 PM UTC-7 slide wrote: > >> Hi Everyone, >> >> If you have been looking for a way to help out Jenkins,

Re: Hosting Team

The meeting is at 4PM UTC, my mistake. On Tuesday, May 4, 2021 at 1:14:53 PM UTC-7 slide wrote: > Hi Everyone, > > If you have been looking for a way to help out Jenkins, there is an > opportunity that we are having a kickoff meeting tomorrow. The Hosting team > needs more people to be

Re: Hosting requests for similar projects

Since Jenkins already has a built-in extensible CLI, we could simply reject both `HOSTING` requests. For non-plugin repositories I see no compelling advantage to in-org hosting. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To

Re: Hosting requests for similar projects

I thought I replied to this a while ago. Apologies. I'm also not in favor of having two split projects. It's just confusing for end users and more likely to be abandoned with only a single maintainer. My vote is either arbitrarily pick one, or get them to decide which they want to use as the

Re: Hosting requests for similar projects

Any other feedback for this? On Tue, Dec 22, 2020 at 12:01 PM Tim Jacomb wrote: > agree would be great if they could be merged > > and also the jenkins core (and winstone) CLI enhanced with a more modern > CLI library > > On Tue, 22 Dec 2020 at 18:13, Slide wrote: > >> Hi Everyone, >> >>

Re: Hosting requests for similar projects

agree would be great if they could be merged and also the jenkins core (and winstone) CLI enhanced with a more modern CLI library On Tue, 22 Dec 2020 at 18:13, Slide wrote: > Hi Everyone, > > Currently we have two hosting requests open ( >

Re: Hosting a Java library for JEP-309: Bill of Materials (HOSTING-1050)

> Can you elaborate? If there is some optimization in Jenkins core that would be beneficial, why not just do it now? What I am doing could be applied to the core when immutable configurations are used, e.g. for plugins and Jenkins core defined in Docker images. If we preprocess plugin

Re: Hosting a Java library for JEP-309: Bill of Materials (HOSTING-1050)

On Mon, Nov 23, 2020 at 9:00 AM Oleg Nenashev wrote: > Jenkins still needs an exploded HPI file to read the plugin manifests. Can you elaborate? If there is some optimization in Jenkins core that would be beneficial, why not just do it now? -- You received this message because you are

Re: Hosting the Jenkins UI/UX Hackfest repository in jenkinsci

Thanks all! After the discussion at the governance meeting we moved it to the Jenkins organization https://github.com/jenkinsci/ui-ux-hackfest-2020 On Wednesday, May 20, 2020 at 7:22:20 PM UTC+2, Vlad Silverman wrote: > > +1 > > On May 20, 2020, at 8:52 AM, Ullrich Hafner > wrote: > > +1 > > Am

Re: Hosting the Jenkins UI/UX Hackfest repository in jenkinsci

+1 > On May 20, 2020, at 8:52 AM, Ullrich Hafner wrote: > > +1 > >> Am 20.05.2020 um 17:12 schrieb Marky Jackson > >: >> >> +1 >> >>> On May 20, 2020, at 6:38 AM, Oleg Nenashev >> > wrote: >>> >>> Hi all, >>> >>> I am working

Re: Hosting the Jenkins UI/UX Hackfest repository in jenkinsci

+1 > Am 20.05.2020 um 17:12 schrieb Marky Jackson : > > +1 > >> On May 20, 2020, at 6:38 AM, Oleg Nenashev > > wrote: >> >> Hi all, >> >> I am working on a repository for the UI/UX online hackfest >>

Re: Hosting the Jenkins UI/UX Hackfest repository in jenkinsci

+1 > On May 20, 2020, at 6:38 AM, Oleg Nenashev wrote: > > Hi all, > > I am working on a repository for the UI/UX online hackfest > next week. This > repository would be used for tracking and visualizing contributions during > the

Re: Hosting the Jenkins UI/UX Hackfest repository in jenkinsci

+1 On Wed, May 20, 2020, at 5:10 PM, Tim Jacomb wrote: > +1000 > > On Wed, 20 May 2020 at 14:51, Mark Waite wrote: >> +1 from me. >> >> On Wed, May 20, 2020 at 7:38 AM Oleg Nenashev wrote: >>> Hi all, >>> >>> I am working on a repository for the UI/UX online hackfest >>>

Re: Hosting the Jenkins UI/UX Hackfest repository in jenkinsci

+1000 On Wed, 20 May 2020 at 14:51, Mark Waite wrote: > +1 from me. > > On Wed, May 20, 2020 at 7:38 AM Oleg Nenashev > wrote: > >> Hi all, >> >> I am working on a repository for the UI/UX online hackfest >> next week. >> This

Re: Hosting the Jenkins UI/UX Hackfest repository in jenkinsci

+1 from me. On Wed, May 20, 2020 at 7:38 AM Oleg Nenashev wrote: > Hi all, > > I am working on a repository for the UI/UX online hackfest > next week. > This repository would be used for tracking and visualizing contributions > during

Re: Hosting process

I am +1000 on the transfer goal, instead of forking. I am quite bothered TBH by the immense amount of fork links that are still present on many (most?) plugins in our GH org. I believe that it sends quite a misleading message especially to new contributors. We indeed need to be very careful and

Re: Hosting process

As long as the transfer process is automated, +100 for that. It should also help to avoid issues when contributor companies request hosting but then continue development in their own repos (no finger-pointing in this thread). On Wednesday, August 28, 2019 at 8:58:13 PM UTC+2, Gavin Mogan wrote:

Re: Hosting process

> Which would be a downside I think. Oh I thought that was the intention Yea for sure a downside On Wed, Aug 28, 2019 at 11:56 AM Jesse Glick wrote: > On Wed, Aug 28, 2019 at 12:31 PM 'Gavin Mogan' via Jenkins Developers > wrote: > > That would break the fork linkage > > Which would be a

Re: Hosting process

On Wed, Aug 28, 2019 at 12:31 PM 'Gavin Mogan' via Jenkins Developers wrote: > That would break the fork linkage Which would be a downside I think. Also the current method forces you to remember to delete your own account’s clone so the @jenkinsci one does not appear as a fork of it. Also you

Re: Hosting process

On Wed, Aug 28, 2019 at 9:31 AM 'Gavin Mogan' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Why transfer it at all? Why not clone, create the new repo, then push. > > That would break the fork linkage, and be less complicated. > > Probably a little slower but doesn't need to

Re: Hosting process

Why transfer it at all? Why not clone, create the new repo, then push. That would break the fork linkage, and be less complicated. Probably a little slower but doesn't need to be realtime speeds On Wed., Aug. 28, 2019, 9:03 a.m. Slide, wrote: > > On Wed, Aug 28, 2019 at 8:59 AM Oleg Nenashev

Re: Hosting process

On Wed, Aug 28, 2019 at 8:59 AM Oleg Nenashev wrote: > the requester would initiate a repository transfer request on Github >> > > Note that it used to require some additional automation logic, because a > contributor cannot just move a project to jenkinsci. > It has to happen through an

Re: Hosting process

> > the requester would initiate a repository transfer request on Github > Note that it used to require some additional automation logic, because a contributor cannot just move a project to jenkinsci. It has to happen through an intermediate organization like

Re: Hosting process

Sounds like a good idea. On Tue, Aug 27, 2019 at 12:03 PM 'Gavin Mogan' via Jenkins Developers wrote: > > +1 > I like the idea of not having to contact support to break the link > > > On Tue, Aug 27, 2019 at 10:01 AM Slide wrote: >> >> Based on some feedback from various people during plugin

Re: Hosting process

+1 I like the idea of not having to contact support to break the link On Tue, Aug 27, 2019 at 10:01 AM Slide wrote: > Based on some feedback from various people during plugin hosting requests, > our current method of forking and renaming repositories is not as desirable > as one might hope. I

Re: Hosting ci.jenkins.io-runner in jenkinsci or jenkins-infra

Thanks for the feedback! I have moved the repository to https://github.com/jenkinsci/ci.jenkins.io-runner On Monday, February 18, 2019 at 2:37:10 PM UTC+1, Mark Waite wrote: > > +1 > > On Mon, Feb 18, 2019, 5:12 AM Slide > wrote: > >> +1 >> >> On Mon, Feb 18, 2019 at 12:18 AM Oleg Nenashev >

Re: Hosting ci.jenkins.io-runner in jenkinsci or jenkins-infra

+1 On Mon, Feb 18, 2019, 5:12 AM Slide +1 > > On Mon, Feb 18, 2019 at 12:18 AM Oleg Nenashev > wrote: > >> If nobody is against, I would like to proceed with hosting of the repo. >> It has already proven its usability for some bits of the Jenkinsfile >> Runner and Pipeline Library development.

Re: Hosting ci.jenkins.io-runner in jenkinsci or jenkins-infra

+1 On Mon, Feb 18, 2019 at 12:18 AM Oleg Nenashev wrote: > If nobody is against, I would like to proceed with hosting of the repo. > It has already proven its usability for some bits of the Jenkinsfile > Runner and Pipeline Library development. > > I will make sure that the repository

Re: Hosting ci.jenkins.io-runner in jenkinsci or jenkins-infra

If nobody is against, I would like to proceed with hosting of the repo. It has already proven its usability for some bits of the Jenkinsfile Runner and Pipeline Library development. I will make sure that the repository explicitly documents its limitations and that it is NOT a full clone of

Re: Hosting ci.jenkins.io-runner in jenkinsci or jenkins-infra

For infra.isTrusted() it will return false, but it may be possible to override it in JCasC if needed. Generally ci.jenkins.io-runner has a number of limitations: https://github.com/oleg-nenashev/ci.jenkins.io-runner#limitations (e.g. DinD or Windows support), so I would not expect it to work for

Re: Hosting ci.jenkins.io-runner in jenkinsci or jenkins-infra

Does this support testing trusted stuff at all (e.g., isTrusted in the infra pipeline library)? Or is this mainly for non-trusted components? On Fri, Dec 14, 2018 at 10:15 AM Oleg Nenashev wrote: > Hi all, > > Few weeks ago I have created a ci.jenkins.io-runner >

Re: hosting request - simple-build-for-pipeline

I note in the past plugin proposals were discussed here first, but the doc (https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins) mentions going straight to HOSTING (does that mean discussion around the name/purpose of it

Re: hosting request - simple-build-for-pipeline

On 19.02.2016, at 05:39, Michael Neale wrote: > HOSTING ticket opened: https://issues.jenkins-ci.org/browse/HOSTING-32 Let's not start notifying this list every time we open a ticket. If we wanted that I could have just set up HOSTING to do it automatically. Besides,

Re: Hosting a new Plugin - Maintenance jobs scheduler plugin

Hi Victor, we're moving hosting requests to JIRA, and only keep previous requests around on this list until we've handled them. Please follow the instructions here: https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Requesthosting Daniel > On 22.12.2015, at 17:32,

Re: Hosting a new Plugin - Maintenance jobs scheduler plugin

Thanks :) -- 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

Re: Hosting request for Silk Performer plugin

Done. The plugin has been forked: https://github.com/jenkinsci/silk-performer-plugin You should get an invitation to the jenkinsci organization soon. Welcome aboard! понедельник, 14 декабря 2015 г., 13:02:34 UTC+3 пользователь Thomas Krupa написал: > > Dear Team, > > > > I would like to host

RE: Hosting request for Silk Performer plugin

Oleg, I changed it to silk-performer-plugin Here is the updated plugin’s info - GitHub url: https://github.com/SilkPerformer/jenkins-silkperformer-executor/ - Name of plugin: silk-performer-plugin - GitHub username: SilkPerformer - Jenkins-ci.org username: silk - Plugin description: This plugin

RE: Hosting request for Silk Performer plugin

hi oleg, I’d prefer silk-performer-plugin. thanks thomas From: Oleg Nenashev [mailto:o.v.nenas...@gmail.com] Sent: Montag, 14. Dezember 2015 18:26 To: Jenkins Developers Cc: Thomas Krupa Subject: Re: Hosting request for Silk Performer plugin What about silkperformer-builder-plugin or just silk

Re: Hosting request for Silk Performer plugin

What about silkperformer-builder-plugin or just silk-performer-plugin. The latter one may be useful if you consider adding extra functionality like report publihers понедельник, 14 декабря 2015 г., 13:02:34 UTC+3 пользователь Thomas Krupa написал: > > Dear Team, > > > > I would like to host

Re: Hosting request for AppBuilder plugin

Hi Oleg, Thank you for your quick reaction, I have received the invitation and now I will create the wiki page for the plugin. Thank you! Best regards, Georgi -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this

Re: Hosting request for AppBuilder plugin

Hi Georgi, The plugin has been forked to https://github.com/jenkinsci/telerik-appbuilder-plugin . You should get an invitation to jenkinsci organisation on GitHub soon. Welcome aboard! Best regards, Oleg понедельник, 14 декабря 2015 г., 10:34:13 UTC+3 пользователь georgi.a...@telerik.com

Re: Hosting request for AppBuilder plugin

Sure, I changed it to telerik-appbuilder-plugin. I think that this ID is a bit more correct :) Here is the updated plugin's info: - GitHub url: https://github.com/Icenium/appbuilder-jenkins-plugin - Name of plugin: telerik-appbuilder-plugin - GitHub username: galexandrov - Jenkins-ci.org

Re: Hosting request for AppBuilder plugin

"AppBuilder" plugin is a bit vague to me. Would it be possible to add something to the plugin ID in order to point to the exact tool? Maybe telerik-appbuilder-plugin? вторник, 8 декабря 2015 г., 12:18:09 UTC+3 пользователь georgi.a...@telerik.com написал: > > Dear Team, > > I would like to host

Re: Hosting turbo plugin / Renaming

Thanks Chris. Ah cool. Mateusz and I will follow your advice and do it like this. On Thursday, October 15, 2015 at 12:45:24 AM UTC+9, Roman Stoffel wrote: > > Hello everybody > > I would like to rename the 'SpoonScript Plugin'. From previous posts I > think the procedure is to put up the

Re: Hosting turbo plugin / Renaming

Hi there, On 14/10/15 17:45, Roman Stoffel wrote: > I would like to rename the 'SpoonScript Plugin'. From previous posts I > think the procedure is to put up the plugin under the new name and then > mark the old one as 'deprecated'. That's more the procedure we have to go through when people

Re: Hosting request for new plugin - WildFly Deployer Plugin

@Oleg - thanks @Kanstantsin - the JBoss Management Plugin (and the Deploy Plugin) were written for JBoss v4.x (2006?)these are not suitable for the new WildFly/JBoss architecture with server groups, etc. Red Hat appears to be using the JBoss name for their commerical offerings - WildFly

Re: Hosting request for new plugin - WildFly Deployer Plugin

Hi Dan, The repository has been forked yesterday: https://github.com/jenkinsci/wildfly-deployer-plugin You should have an invitation in your inbox. Today I've also created a component in Jenkins JIRA. Welcome aboard! Best regards, Oleg Nenashev понедельник, 5 октября 2015 г., 23:31:19 UTC+3

Re: Hosting request for new plugin - WildFly Deployer Plugin

I may mistake, but i saw 2 plugins for jboss (now called wildfly?) On Wednesday, October 7, 2015 at 2:22:34 PM UTC+3, Oleg Nenashev wrote: > > Hi Dan, > > The repository has been forked yesterday: > https://github.com/jenkinsci/wildfly-deployer-plugin > You should have an invitation in your

Re: Hosting request for new plugin creating a Jira URL out of the Git history/changelog

Hi, thank you very much. It worked, wiki page created, release built. Regards Paul. On Sun, Oct 4, 2015 at 11:10 AM Oleg Nenashev wrote: > Hi Paul, > > The plugin has been forked: > https://github.com/jenkinsci/git-changelog-plugin . You should get an > invitation to

Re: Hosting request for new plugin creating a Jira URL out of the Git history/changelog

Hi Paul, The plugin has been forked: https://github.com/jenkinsci/git-changelog-plugin . You should get an invitation to jenkinsci organization soon. Welcome aboard! Best regards, Oleg Nenashev пятница, 2 октября 2015 г., 23:46:44 UTC+3 пользователь Paul Wellner Bou написал: > > Good

Re: [Hosting Request] TraceTronic ECU-TEST Plugin

Hi Christian, The plugin has been forked: https://github.com/jenkinsci/ecutest-plugin You should get a jenkinsci org invitation soon. Welcome aboard! Best regards, Oleg Nenashev вторник, 29 сентября 2015 г., 12:30:30 UTC+3 пользователь Pönisch, Christian написал: > > Hello, > > > > we

Re: Hosting request for new plugin creating a Jira URL out of the Git history/changelog

Good evening, After a lot of refactoring it works now, even with git workspaces on Jenkins slaves. The README may include more examples, but that will be work for the wiki page, once this plugin might get included in jenkins' plugin collection. Is there a chance to get it hosted on jenkins?

Re: Hosting request for new plugin creating a Jira URL out of the Git history/changelog

IMHO such generic plugin makes sense. The code is really hardcoded to be git=>jira only, but it's possible to generalize it to "git-changelog-generator". If not, we could also publish it as a "git-jira-changelog-generator". The most of the functionality is located in another library BTW, so

Re: Hosting request for Behave Test results Jenkins plugin

Hi, The repository has been forked: https://github.com/jenkinsci/behave-testresults-publisher-plugin You should receive an githib org invitation to your inbox soon. Welcome aboard! > On 29 Sep 2015, at 11:52, Chaitanya

Re: Hosting request for new plugin creating a Jira URL out of the Git history/changelog

Thank you for the inspiration: I decoupled the logic from the jira functionality and refactored both, the library and the jenkins plugin, even renamed the repositories and artifacts: https://github.com/paulwellnerbou/git-changelog-jenkins-plugin The documentation now needs a bit more of rework,

Re: Hosting request for new plugin creating a Jira URL out of the Git history/changelog

Seems the core JIRA plugin provides a related functionality (https://issues.jenkins-ci.org/browse/JENKINS-6381). Would it be possible to somehow merge your proposal into this plugin? пятница, 25 сентября 2015 г., 15:23:44 UTC+3 пользователь Paul Wellner Bou написал: > > Github:

Re: Hosting request for Behave Test results Jenkins plugin

Do you consider adding a new functionality (e.g. Behave builder)? "behave-plugin" maybe quite vague, but I don't see other alternatives excepting "behave-bdd-plugin" or "behave-publisher-plugin". WDYT? Please also provide your Jenkins JIRA ID? пятница, 18 сентября 2015 г., 14:12:42 UTC+3

Re: Hosting request for new plugin creating a Jira URL out of the Git history/changelog

That may be new, I searched several days for something similar and did not find anything. I know that the JIRA plugin is able to create a changelog, but only if the releases are managed by Jira as well. It is new for me that the Jira plugin was able to scan the actual git history of the

Re: Hosting request for new plugin sumologic-publisher-plugin

Hi Deven, The plugin has been forked: https://github.com/jenkinsci/sumologic-publisher-plugin . You should get an invitation to the jenkinsci organization soon. Welcome aboard! Best regards, Oleg вторник, 22 сентября 2015 г., 1:11:17 UTC+3 пользователь Deven Norton написал: > > Friendly

Re: Hosting request for new plugin creating a Jira URL out of the Git history/changelog

Good morning, I had a deeper look at the jenkins-jira-plugin, and no, it is not doing what I am trying to do with my git-jira-log plugin. First of all: Maybe I should rename it and give it a more generic aim: The logic in my plugin is not about jira, it is mainly about extracting changelogs out

Re: hosting request for new plugin

Right, I specifically meant the name of the forked repo in the jenkinsci org: https://github.com/jenkinsci/pagerduty-plugin There's also a component 'pagerduty-plugin' owned by you in issues.jenkins-ci.org. Welcome aboard! On 24.09.2015, at 23:13, Alexander Leibzon

Re: hosting request for new plugin

Thanks! On Friday, September 25, 2015 at 2:09:54 PM UTC+3, Daniel Beck wrote: > > Right, I specifically meant the name of the forked repo in the jenkinsci > org: > > https://github.com/jenkinsci/pagerduty-plugin > > There's also a component 'pagerduty-plugin' owned by you in >

Re: hosting request for new plugin

Well, as your plugin, when forked, is gonna be under the Jenkins org, it will both clear that it's Jenkins related and inconsistently named compared to others. -- Baptiste Le 24 sept. 2015 11:13 PM, "Alexander Leibzon" a écrit : > Thanks for pointing me on that! > >

Re: Hosting a new Plugin - Percentage DiskSpace usage column

Hi, any news? Thanks On Saturday, 19 September 2015 13:44:52 UTC+2, Victor Martinez wrote: > > Alright, I've already renamed, further details: > >- Github repo: *https://github.com/v1v/percentage-du-node-column-plugin >* >-

Re: Hosting a new Plugin - Percentage DiskSpace usage column

Done: https://github.com/jenkinsci/percentage-du-node-column-plugin I also created a JIRA component for you. Daniel On 24.09.2015, at 12:43, Victor Martinez wrote: > Hi, >any news? > Thanks > On Saturday, 19 September 2015 13:44:52 UTC+2, Victor Martinez

  1   2   3   4   >