Re: New plugin

Thanks for all those suggestions. I will apply them and will return to you for further guidance. piątek, 22 marca 2024 o 11:53:49 UTC+1 db...@cloudbees.com napisał(a): > On Fri, Mar 22, 2024 at 11:12 AM DuMaM wrote: > >> My work environment requires from me to give users privileges to create

Re: New plugin

On Fri, Mar 22, 2024 at 11:12 AM DuMaM wrote: > My work environment requires from me to give users privileges to create > new jobs, but I need to lock creation of non pipeline jobs. > I could take a solution proposed a long time ago by Daniel Beck, but I > fought that maybe it's a good place for

RE: New plugin

Your problem with the restart is because you configure it in the constructor. But this is an Extension which is only created once at startup and not every time a check is performed. So you will need to fill the projectTypes list in the filter method (and don't make it a class field). You might

Re: New plugin - Support for Azure credentials via the Kubernetes Credentials Provider

Perfect. Thanks. Request submitted: https://github.com/jenkins-infra/repository-permissions-updater/issues/3746 lørdag den 13. januar 2024 kl. 12.52.31 UTC+1 skrev jone...@gmail.com: > Hi, > > You can follow > https://www.jenkins.io/doc/developer/publishing/requesting-hosting/ in > order to

Re: New plugin - Support for Azure credentials via the Kubernetes Credentials Provider

Hi, You can follow https://www.jenkins.io/doc/developer/publishing/requesting-hosting/ in order to host your plugin Best way is to start with mvn archetype:generate -B -DarchetypeGroupId=io.jenkins.archetypes -DarchetypeArtifactId=empty-plugin -DhostOnJenkinsGitHub=true

Re: New Plugin version not updated on Jenkins IO Plugin page

OK. Thanks! On Thursday, July 13, 2023 at 12:07:48 AM UTC-4 Mark Waite wrote: > On Wednesday, July 12, 2023 at 10:04:55 PM UTC-6 Ricardo DeLemos wrote: > > Yes. The 2 versions (1.2.0 and 1.2.1) showed up 15 minutes after I have > send you the previous email. It is all set now. > > Just for

Re: New Plugin version not updated on Jenkins IO Plugin page

On Wednesday, July 12, 2023 at 10:04:55 PM UTC-6 Ricardo DeLemos wrote: Yes. The 2 versions (1.2.0 and 1.2.1) showed up 15 minutes after I have send you the previous email. It is all set now. Just for reference on the next update: the 1.2.0 version took over 6hr to show up on

Re: New Plugin version not updated on Jenkins IO Plugin page

Yes. The 2 versions (1.2.0 and 1.2.1) showed up 15 minutes after I have send you the previous email. It is all set now. Just for reference on the next update: the 1.2.0 version took over 6hr to show up on https://plugins.jenkins.io/, while 1.2.1 showed up after 1 hr. It is just the time that

Re: New Plugin version not updated on Jenkins IO Plugin page

On Wednesday, July 12, 2023 at 8:57:48 PM UTC-6 Ricardo DeLemos wrote: Hi Mark, I have created a new release (1.20) following your recommendation, but I still do not see the new release in https://plugins.jenkins.io/crowdstrike-security/releases/

Re: New Plugin version not updated on Jenkins IO Plugin page

Hi Mark, I have created a new release (1.20) following your recommendation, but I still do not see the new release in https://plugins.jenkins.io/crowdstrike-security/releases/ . I have created a version 1.2.0, which I see on

Re: New Plugin version not updated on Jenkins IO Plugin page

The 1.1.0 release is not available on repo.jenkins-ci.org. https://repo.jenkins-ci.org/artifactory/releases/io/jenkins/plugins/crowdstrike-security/ shows a 1.0.0 release that was delivered in 2022. Since a tag has been created in the repository, I recommend that you declare the 1.1.0

Re: New plugin for showing dynamic header across Jenkins

Hey Gavin, Thanks for sharing your thoughts. *Easier than the existing system notice box? What does dynamic mean in this case* - I felt the existing system notice box content gets unnoticed and my way of showing the header at the top has more visibility. - By dynamic I mean we can have the

Re: New plugin for showing dynamic header across Jenkins

- Header content will be dynamic and easy to update for administrators. Easier than the existing system notice box? What does dynamic mean in this case [image: image.png] - Header content will have an expiry date and post expiry it would not be shown. I could potentially see that

Re: New Plugin With Multiple Components Hosting Question

On Thu, Jun 30, 2022 at 8:55 PM Mark Diesburg wrote: > We could submit just the source for the test-management plugin portion > with reference to the other two components on GitHub since they can be used > independently for other purposes. > > Would this be acceptable? > > Or would we have to

Re: New Plugin With Multiple Components Hosting Question

Hi All libraries used in a plugin must be published publicly, open source approved license, and to an artifact repository that anyone can pull from normally either maven central or Jenkins repository. Basically we can host it or you can push it to maven central if it makes sense outside of

Re: New plugin: global-pre-script-plugin

You need to make a HOSTING jira ticket - https://jenkins.io/doc/developer/publishing/requesting-hosting/ On Sat, Feb 1, 2020 at 1:53 PM Orekaria N wrote: > Hello > > > I have created a plugin that may interest > youhttps://github.com/Orekaria/global-pre-script-plugin > > Please, let me know if

Re: new plugin/option to deploy on staging

Thanks Oleg I will test those. best regards Reinaldo El jueves, 22 de agosto de 2019, 16:00:43 (UTC-5), Oleg Nenashev escribió: > > Hi, > > These page is being controlled by summary.jelly/groovy pages in Actions > which you can attach to the build. > > One of examples (maybe abit too heavy,

Re: new plugin/option to deploy on staging

Hi, These page is being controlled by summary.jelly/groovy pages in Actions which you can attach to the build. One of examples (maybe abit too heavy, but you can get an idea there): -

Re: New Plugin - Dependency-Track

Hi Steve, Please see https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins for information on how to get a plugin hosted. Regards, Alex On Wed, Sep 12, 2018 at 4:36 PM Steve Springett wrote: > Hello, > > I’m the author of a few Jenkins plugins and I’m working on another. > > The plugin is

Re: New plugin developer: A View Plugin

On Fri, Apr 20, 2018 at 2:27 PM, Sverre Moe wrote: > This made me suspect that I was using OpenJDK and Java 9. Oh, well Jenkins does not run on Java 9. At all. So there is that. -- You received this message because you are subscribed to the Google Groups "Jenkins

Re: New plugin developer: A View Plugin

target/surefire-reports/TEST-InjectedTest.xml WARNING: Failed to instantiate Key[type=org.jenkinsci.main.modules.instance_identity.PageDecoratorImpl, annotation=[none]]; skipping this component com.google.inject.ProvisionException: Unable to provision, see the following errors: 1) Error

Re: New plugin developer: A View Plugin

On Wed, Apr 18, 2018 at 5:18 PM, Sverre Moe wrote: > What kind of test is this? There is nothing in my newly created project. The Jenkins plugin build harness generates a synthetic test to verify basic sanity aspects of your plugin. I am not sure what specifically the

Re: New plugin Bitbucket Server Branch Source

In hindsight it might have better to split this into two separate plugins but at the time it was our understanding that Atlassian was moving to consolidate both the branding and API specification of Cloud and Server. The implementation would still be separate but the specification was supposed to

Re: New plugin Bitbucket Server Branch Source

Hi Am Sonntag, 12. März 2017 21:50:01 UTC+1 schrieb Stephen Connolly: > > > On Sun 12 Mar 2017 at 18:23, 'Robin Müller' via Jenkins Developers < > jenkin...@googlegroups.com > wrote: > ... > Not everyone in the OSS community has the luxury of somebody who can pay to > get licenses for these

Re: New plugin Bitbucket Server Branch Source

On Sun 12 Mar 2017 at 18:23, 'Robin Müller' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Hi, > > Am Sonntag, 12. März 2017 16:32:22 UTC+1 schrieb Stephen Connolly: > > I do not think this is the right way to go at all. > > Would you also implement the SCMSourceNavigator for

Re: New plugin Bitbucket Server Branch Source

Hi, Am Sonntag, 12. März 2017 16:32:22 UTC+1 schrieb Stephen Connolly: > > I do not think this is the right way to go at all. > Would you also implement the SCMSourceNavigator for GitLab within the GitHub Branch Source Plugin just as their names are similar? Bitbucket Cloud and Bitbucket Server

Re: New plugin Bitbucket Server Branch Source

I do not think this is the right way to go at all. There is a refactoring or two from my PoV to take place in the current plugin and that will result in much cleaner code without fracturing things. While there are multiple webhook plugins available for BB server, from my understanding there is

Re: New Plugin: SAML Plugin

Hi Ben, I am trying this plugin for ADFS integration SAML2.0, user able to login but says no overall read rights. Do you have any documentation around integration with ADFS? Regards Prabhat On Thursday, August 7, 2014 at 2:05:20 AM UTC+5:30, Ben McCann wrote: > > Hi, > > I created a SAML 2.0

Re: [New Plugin Request] - Amazon AWS Device Farm

Hi Hawker, Please grant me the access of Github/Jenkins account. Thanks, Hongda On Friday, July 17, 2015 at 2:43:40 PM UTC-7, Andrew Hawker wrote: > > Requesting a Github fork for a new plugin. > > Name: aws-device-farm-plugin > Github: https://github.com/awslabs/aws-device-farm-jenkins-plugin

Re: New plugin request for feedback: Execute a script every time a build gets deleted

AbstractBuild seems wrong if you also want to catch Pipelines deletions. Did you try just Job? Le 8 déc. 2016 6:58 PM, a écrit : > > I ended up extending RunListener to trigger my plugin when > a build is deleted. > > -- > You received this message because you are

Re: New plugin request for feedback: Execute a script every time a build gets deleted

I ended up extending RunListener to trigger my plugin when a build is deleted. -- 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

Re: New plugin request for feedback: Execute a script every time a build gets deleted

I am afraid you need write a plugin to extend ItemListener, see also http://javadoc.jenkins.io/hudson/model/listeners/ItemListener.html#onDeleted(hudson.model.Item) or you can check the JENKINS_HOME/jobs/job_name/builds folder on Jenkins server periodically and compare what builds you have On

Re: New plugin request for feedback: parameterized scheduler

It would be best to redirect this query to the Jenkins User List as this mailing list is used for development of plugins and not their use. Richard. On Thu, 1 Dec 2016 at 11:46 PC wrote: > Hi, > > I have installed this plugin and am trying to use it. This plugin is >

Re: New plugin request for feedback: parameterized scheduler

Hi, I have installed this plugin and am trying to use it. This plugin is exactly what I need, as I need to to schedule multiple builds with different parameters at each build. For some reason, the build is not triggering at the scheduled periods. I tried various schedules. Attached are the

Re: New plugin - gradle build

Thanks Jesse! On Saturday, November 12, 2016 at 9:28:10 AM UTC-6, Jesse Glick wrote: > > On Fri, Nov 11, 2016 at 7:10 PM, Taylor Patton > wrote: > > I do not yet see a job for my new plugin here > > Created > > >

Re: New plugin - gradle build

On Fri, Nov 11, 2016 at 7:10 PM, Taylor Patton wrote: > I do not yet see a job for my new plugin here Created https://jenkins.ci.cloudbees.com/job/plugins/job/Cisco-Spark-Notifier-plugin/ -- You received this message because you are subscribed to the Google Groups

Re: New Plugin hosting request: Splunk plugin for Jenkins

Hi Ted, Hosting requests are regularly reviewed by our team, but it can take a few days as it's done by volunteers. Daniel > On 27.09.2016, at 14:06, Ted Xiao wrote: > > I would like to request hosting the Splunk plugin >

Re: New plugin - environment-dashboard

Hey Vipin, Good initiate and thought you kept in design and writing this plugin. Yes it has to be updated. 1) Try to incorporate the server topology in environments. ex: For suppose Dev env contains 1 APP, 1 UI and 1 DB, these has to be grouped within Dev env so that user can have a Dev env

Re: New plugin - environment-dashboard

Hi do you still maintain this plugin? I'm having issues updating the dashboard after the build finishes. It instead shows just the unexpanded variable. Also I can't seem to quite get the links to work on the dashboard that link back to the actual job details page. Please any tips youc an give

Re: New plugin request: pipeline-milestone-step-plugin

Ups, right. https://issues.jenkins-ci.org/projects/HOSTING 2016-04-11 14:56 GMT+02:00 Baptiste Mathus : > For the record, yup, you've got to file a JIRA issue, but in HOSTING :-). > > See https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins for details. > > Cheers > >

Re: New plugin request: pipeline-milestone-step-plugin

For the record, yup, you've got to file a JIRA issue, but in HOSTING :-). See https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins for details. Cheers 2016-04-11 14:54 GMT+02:00 Manuel Jesús Recena Soto : > I meant "AFAIK" instead of "AFIAK" ;) > > 2016-04-11 14:53

Re: New plugin request: pipeline-milestone-step-plugin

I meant "AFAIK" instead of "AFIAK" ;) 2016-04-11 14:53 GMT+02:00 Manuel Jesús Recena Soto : > Hello Antonio, > > AFIAK, you have to file a Jira issue in INFRA project: > https://issues.jenkins-ci.org/secure/RapidBoard.jspa?projectKey=INFRA=true=51 > > Regards, > > 2016-04-11

Re: New plugin request: pipeline-milestone-step-plugin

Hello Antonio, AFIAK, you have to file a Jira issue in INFRA project: https://issues.jenkins-ci.org/secure/RapidBoard.jspa?projectKey=INFRA=true=51 Regards, 2016-04-11 13:43 GMT+02:00 Antonio Muñiz : > Hello, > > I'm working on a new Pipeline step, it was initially filed

Re: New plugin hosting request

Hi Sanketh, I've made a committer on this plugin and the lead of the JIRA component. Please review your inbox, you should have received an invitation. Leonardo is still committer. So, please start progressively, ideally by filing PR instead of directly pushing, and asking for review from your

Re: New plugin hosting request

It's a long wait by now. Could you please let me know the next steps? On Thursday, December 24, 2015 at 3:55:20 AM UTC+5:30, Daniel Beck wrote: > > Given that it's the end of the year I'd prefer to wait a bit longer to > give Leonardo time to respond even if on vacation. > > > On 23.12.2015, at

Re: New Plugin: Liquibase Runner

Hey Keith, Can you please provide instructions how to install this plugin from the zip file into Jenkins server. I did not see any instructions on the Liquibase site as well. Keith Collison wrote > Greetings esteemed Jenkinists: > > I have created a Jenkins Plugin and, per instructions on the

Re: New plugin hosting request

Dear Team, There is no update from the plugin developer/maintainer, please let me know how to proceed here. Thanks, Sanketh On Tuesday, December 15, 2015 at 9:38:27 PM UTC+5:30, Sanketh P B wrote: > > Sure, I agree with you. We could enhance the existing plugin. > @Leonardo Kobus: Please

Re: New plugin hosting request

Given that it's the end of the year I'd prefer to wait a bit longer to give Leonardo time to respond even if on vacation. > On 23.12.2015, at 19:09, Sanketh P B wrote: > > Dear Team, > > There is no update from the plugin developer/maintainer, please let me know > how to

Re: New Plugin hosting request: Docker Ephemeral Cloud

I'm not sure where this thread is now -- are you still asking for hosting of this plugin? If so, could anyone speak up wrt whether there are legitimate reasons not to do this? So far the number of existing similar implementations has been mentioned -- how similar are they? Would an

Re: New plugin hosting request

Sure, I agree with you. We could enhance the existing plugin. @Leonardo Kobus: Please provide your inputs on how to proceed. Thanks, Sanketh On Monday, December 14, 2015 at 1:32:22 PM UTC+5:30, Oleg Nenashev wrote: > > In general we try to avoid creation of new plugins wherever it is >

Re: New plugin hosting request

In general we try to avoid creation of new plugins wherever it is possible. IMHO it makes sense to consider integrating the functionality into a single plugin^ because they are very close. I agree that the existing plugin does not cover all your case, but it could be solved by the plugin

Re: New plugin hosting request

Dear Oleg Nenashev, This plugin offers support for frequently performed operations (change in product version, file version and copyright info) on .Net, managed .Net and C++ assembly information in a easy way. The other concentrates on .Net only and for updating versions. Kindly suggest your

Re: New plugin hosting request

Hi Sanketh, How the plugin differs from https://github.com/jenkinsci/change-assembly-version-plugin ? >From what I see it would be better to update that plugin instead of creating the new one Best regards, Oleg Nenashev пятница, 11 декабря 2015 г., 18:29:12 UTC+3 пользователь Sanketh P B

Re: New plugin hosting request

You posted on a weekend, so please be patient. On Mon, Dec 7, 2015 at 1:04 AM Sanketh P B wrote: > Dear All, > > Any updates here? > > Thanks, > Sanketh > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To

Re: New plugin development: vscale.io slave

No code in the repo so far... Are there any plans/milestones? вторник, 17 ноября 2015 г., 15:43:19 UTC+3 пользователь ak...@selectel.ru написал: > > Hi guys, > We are planning to develop jenkins-plugin to run slave jobs on > https://vscale.io > So it'll be very similar to DigitalOcean plugin. >

Re: New Plugin Hosting (IFTTT Build Notifier)

Looks good. I forked the plugin to https://github.com/jenkinsci/ifttt-build-notifier-plugin and made you a committer. The wiki page should explain what to do next, and how to release: https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins I also created a component for it on

Re: New Plugin Hosting (IFTTT Build Notifier)

Thanks a lot Daniel! -- 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: New Plugin hosting request: Docker Ephemeral Cloud

The Docker landscape in Jenkins is kind of a mess, but I do feel this is a good thing for an extensible open source project. The situation is exaggerated here because there is so much interest and momentum in Docker. We've discussed two Docker client libraries in this thread. There is a third,

Re: New Plugin Request: slack-webhook-plugin

Okay, i'll merge with the slack-plugin. Thanks On Monday, November 23, 2015 at 2:57:01 AM UTC-5, Baptiste Mathus wrote: > > +1. IMO we should try and enrich existing plugins particularly when this > is not gonna be a feature bloat, and/or when the codebase isn't too big. > It makes it easier to

Re: New Plugin hosting request: Docker Ephemeral Cloud

On Mon, Nov 23, 2015 at 11:56 AM, kmbulebu wrote: > 'Here's some of the issues I've encountered while working > with the plugins that rely on the docker cli: All valid points (with some workarounds), but the flip side is that when calling a CLI you can reproduce the exact

Re: New Plugin Hosting (IFTTT Build Notifier)

Hi Daniel, As you suggested, I fixed both the problems. Could you please help me with review and setup the plug-in? Thanks, Unmesh -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails

Re: New Plugin Request: slack-webhook-plugin

+1 for merging and adding a feature flag in the global configuration to enable one or/and the other functionality /Domi > On 22 Nov 2015, at 21:27, Daniel Beck wrote: > > Would it make sense to integrate this into the Slack Plugin? I mean, it's in > the other direction,

Re: New Plugin Request: slack-webhook-plugin

+1. IMO we should try and enrich existing plugins particularly when this is not gonna be a feature bloat, and/or when the codebase isn't too big. It makes it easier to find for users, and maybe less likely to become unmaintained. Cheers Le 23 nov. 2015 8:15 AM, "domi" a écrit :

Re: New Plugin Request: slack-webhook-plugin

Would it make sense to integrate this into the Slack Plugin? I mean, it's in the other direction, but still… On 22.11.2015, at 07:32, David Pires wrote: > Hi all, > > I'd like to host my plugin on jenkins-ci.org. > • url:

Re: New Plugin Request: slack-webhook-plugin

That was my initial thought, but then reading the wiki (about making unique features) I thought it didn't really have anything to do with the Slack plugin, which is really a notifier, this is more of a simplified ChatBot, that is currently only working with Slack (but could work with HipChat

Re: New Plugin Request: slack-webhook-plugin

Actually making it a generic webhook plugin wouldn't make sense either, as reading the wiki it seems better to make smaller unique plugins which don't require too much configuration. This plugin is the opposite of the Slack plugin as it's a outgoing-webhook, rather than an incoming webhook,

Re: New plugin request for feedback: parameterized scheduler

Plugin released, any feedback welcome: https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Scheduler+Plugin 2015-11-18 6:22 GMT+01:00 Baptiste Mathus : > OK, as we've tested it successfully, I'm going to fork it. > > Thanks > > 2015-11-17 11:14 GMT+01:00 Baptiste Mathus

Re: New Plugin Hosting (IFTTT Build Notifier)

Hi Umesh, Out of interest, is this plugin compatible with the Workflow job type? Regards Nigel On Saturday, October 24, 2015 at 1:26:17 PM UTC+1, Unmesh Gundecha wrote: > > Hi, > > I have created a new plugin > for pushing build >

Re: New Plugin Hosting (IFTTT Build Notifier)

Hi, Any thoughts/views on this? is it good/not so good to be added in the Plug-Ins list? Thanks, Unmesh On Saturday, 24 October 2015 17:56:17 UTC+5:30, Unmesh Gundecha wrote: > > Hi, > > I have created a new plugin > for pushing build >

Re: New Plugin Hosting (IFTTT Build Notifier)

I think this is a good idea. Two remarks: * "}{" is a valid project name (unless you're on Windows). So make sure to escape it when using string concatenation to build your JSON. * The help file links use a different plugin ID, so cannot be found. Neither would prevent hosting, unless someone

Re: New Plugin hosting request: Docker Ephemeral Cloud

This is the problem about jenkins - 1000 half backed plugins. Would be better with 100 well curated :) That's where I'd be willing to pay for support. 2015-11-18 16:48 GMT+01:00 Kirill Merkushev : > Think plugins can be merged without any problem with saving of current >

Re: New Plugin Hosting (IFTTT Build Notifier)

On 18.11.2015, at 18:09, Daniel Beck wrote: > * "}{" is a valid project name (unless you're on Windows). So make sure to > escape it when using string concatenation to build your JSON. To clarify, the quotes are part of the project name. -- You received this message

Re: New Plugin hosting request: Docker Ephemeral Cloud

> > On Nov 18, 2015, at 17:32, domi wrote: > > To be honest, the whole list of jenkins docker plugins feels like a zoo and > there is no way a normal user can keep up and make the right choice. Technically it’s a question to plugin manager and providing ratings & statistics.

Re: New Plugin hosting request: Docker Ephemeral Cloud

> > > To be honest, the whole list of jenkins docker plugins feels like a zoo > and there is no way a normal user can keep up and make the right choice. > I think this work should be coordinated better and an uptodate comparison > should be kept at a central place. > ..my 2cents > /Domi > > I

Re: New Plugin hosting request: Docker Ephemeral Cloud

> On Nov 18, 2015, at 18:25, Nigel Magnay wrote: > > > To be honest, the whole list of jenkins docker plugins feels like a zoo and > there is no way a normal user can keep up and make the right choice. > I think this work should be coordinated better and an uptodate

Re: New Plugin hosting request: Docker Ephemeral Cloud

Think plugins can be merged without any problem with saving of current functionality for both. (With shading of both libs). One will use one type of cloud, another - own type of cloud. They can be located in separate packages and don't mix in different cases. (But please use

Re: New Plugin Hosting (IFTTT Build Notifier)

Hi Daniel, I think have I fixed both the problems just now. Could you please review? Thanks, Unmesh -- 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

Re: New Plugin hosting request: Docker Ephemeral Cloud

On Tuesday, November 17, 2015 at 7:28:00 PM UTC+3, Jesse Glick wrote: > > On Mon, Nov 16, 2015 at 10:02 PM, kmbulebu > wrote: > > I believe the real horse race is between the > > underlying docker libraries. In the end, we'll likely have a clear > winner, > > and can

Re: New Plugin hosting request: Docker Ephemeral Cloud

To be honest, the whole list of jenkins docker plugins feels like a zoo and there is no way a normal user can keep up and make the right choice. I think this work should be coordinated better and an uptodate comparison should be kept at a central place. ..my 2cents /Domi > On 18 Nov 2015, at

Re: New Plugin hosting request: Docker Ephemeral Cloud

On Mon, Nov 16, 2015 at 10:02 PM, kmbulebu wrote: > I believe the real horse race is between the > underlying docker libraries. In the end, we'll likely have a clear winner, > and can standardize a group of plugins around that. Perhaps docker-commons > becomes that focal

Re: New Plugin hosting request: Docker Ephemeral Cloud

FWIW, I have pushed changes for both TLS and JNLP in docker-plugin, so the comparison can now be reduced to Docker Plugin - Provides additional capabilities beyond slaves, such as Docker build steps. On Tue, Nov 17,

Re: New plugin request for feedback: parameterized scheduler

OK, as we've tested it successfully, I'm going to fork it. Thanks 2015-11-17 11:14 GMT+01:00 Baptiste Mathus : > Hi, > > Note: this is *not* a fork request. > > Just an email here to get potential feedback about that plugin [1]. I've > already gotten some feedback from Daniel

Re: New Plugin hosting request: Docker Ephemeral Cloud

(replies inline) On Fri, 13 Nov 2015, kmbulebu wrote: > I'd like to introduce a new plugin for hosting on jenkins-ci.org, the > docker ephemeral cloud plugin. > > Github Home: https://github.com/kmbulebu/docker-ephemeral-cloud > Github and Jenkins username: kmbulebu > Name:

Re: New Plugin hosting request: Docker Ephemeral Cloud

Thanks for your kind words :). I understand. At a high level, they both aim to deliver slaves using Docker. This is an old problem; do you break away and create new, or revise in place? I think we should move forward with the new one, and let it work itself out. I'm not opposed to merging,

Re: New plugin Build-name-updater

Hi Lev, Just noticed that https://wiki.jenkins-ci.org/display/JENKINS/Build+Name+Setter+Plugin still has the 'adopt-a-plugin' tag. I guess you should remove it. I see that you seem to have released a new version yesterday. Btw, I guess you could (should?) simply remove kohsuke from the pom.xml,

Re: New plugin Build-name-updater

Hello, since my mail to the developer list seems not to be delivered I send you this mail directly again: I had the same problem not long ago that releasing with maven did not work. The solution was to omit username and password (only call "mvn release:prepare release:perform") and instead

Re: New plugin for Mattermost integration

> After some evaluation, I agree with the maintainer of the slack plugin that sharing the code base will probably complicate matters in the not too distant future... How to continue? Op zaterdag 24 oktober 2015 23:43:48 UTC+2 schreef Daniel Beck: > > Wouldn't it make sense to integrate this as

Re: New plugin for Mattermost integration

Makes sense. Still can't hurt for you to keep an eye on each other's work and integrate fixes that make sense in both! https://github.com/jenkinsci/mattermost-plugin Made you committer and created a JIRA component as well with you as lead. Remember to point the pom.xml to this new repo, and to

Re: New plugin for Mattermost integration

OK, I managed to upload my version (took a while to get github creds and jenkins creds working...) Now I probably have to wait a while to see if everything actually succeeded...? Op donderdag 5 november 2015 12:42:10 UTC+1 schreef Daniel Beck: > > Makes sense. Still can't hurt for you to keep

Re: New plugin for Mattermost integration

The artifacts are in the Maven repo, so that looks good. The update center gets regenerated every few hours, so if you're really bored, keep looking at the logs of https://ci.jenkins-ci.org/job/infra_update_center_v3/ to see your plugin get mentioned. Note that once that's done, you're still

Re: New plugin Build-name-updater

Hmm, quite strange, I've just run 'deploy' target from 'lifecycle' in Idea and plugin was successfully released. Will it appear here ? On Tuesday, November 3, 2015 at 11:18:43 PM UTC+3, Lev Mishin wrote: > > Hi again > I have read

Re: New plugin Build-name-updater

Hi again I have read all the article but I unable to deploy a new version. I try to run mvn release:prepare release:perform -Dusername=... -Dpassword=... with login/pass, but the error occurs: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy

Re: New plugin Build-name-updater

Please check that you also uploaded sources and javadocs (action that maven-release-plugin do). On Tuesday, November 3, 2015 at 11:22:24 PM UTC+3, Lev Mishin wrote: > > Hmm, quite strange, I've just run 'deploy' target from 'lifecycle' in Idea > and plugin was successfully released. Will it

Re: New plugin for Mattermost integration

After some evaluation, I agree with the maintainer of the slack plugin that sharing the code base will probably complicate matters in the not too distant future... Met vriendelijke groet, Jo Vandeginste jo.vandegin...@gmail.com -- You received this message because you are subscribed to the

Re: New plugin Build-name-updater

Hi Lev, Read https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Releasingtojenkinsci.org main gotcha: beware forcing recent maven-release-plugin versions if you depend on an old Jenkins version for the plugin. Cheers 2015-10-27 8:21 GMT+01:00 Lev Mishin

Re: New plugin Build-name-updater

Hi Lev, I've granted you developer permissions & changed the default assignee in JIRA. Now you should be able to merge PRs and release the plugin on your own. Best regards, Oleg понедельник, 26 октября 2015 г., 13:36:01 UTC+3 пользователь Lev Mishin написал: > > Just to remind > > On

Re: New plugin Build-name-updater

Just to remind On Wednesday, October 21, 2015 at 12:07:15 PM UTC+3, Lev Mishin wrote: > > Thanks! > > On Wed, Oct 21, 2015, 11:14 AM Oleg Nenashev > wrote: > >> Hi Lev, >> >> I'll ping Kohsuke regarding the ownership handover. >> >> Best regards, >> Oleg >> >> среда, 21

Re: New Plugin Hosting (IFTTT Build Notifier)

My jenkins-ci.org username is *upgundecha* On Saturday, 24 October 2015 17:56:17 UTC+5:30, Unmesh Gundecha wrote: > > Hi, > > I have created a new plugin > for pushing build > notifications to IFTTT (htttp://ifttt.com) channels and I wish

Re: New plugin for Mattermost integration

I also created a job builder plugin: https://github.com/jovandeginste/jenkins-jobs-mattermost Op zaterdag 24 oktober 2015 21:40:14 UTC+2 schreef Jo Vandeginste: > > Github url: https://github.com/jovandeginste/jenkins-mattermost-plugin > The name the repository should have: "mattermost-plugin" >

Re: New plugin for Mattermost integration

Wouldn't it make sense to integrate this as a feature in the Slack plugin (and maybe change it's display name)? This way both sets of users can benefit from new features and bug fixes, at least as long as development of these services doesn't significantly diverge... On 24.10.2015, at 21:40,

  1   2   3   4   5   6   >