Re: [DISCUSS] Hide from the update center plugins without source code under the Jenkinsci github organization?

On 01/12/15 16:52, 'Jesse Glick' via Jenkins Developers wrote: > On Tue, Dec 1, 2015 at 5:32 AM, Baptiste Mathus wrote: >> plugins forked under the Jenkinsci org, BUT still maintained elsewhere > > There are a number of such cases where the @jenkinsci fork is out of > date.

Re: Bugs in AWS Elastic Beanstalk Deployment Plugin and AWS Elastic Beanstalk Publisher Plugin

Hi there, I see you already filed one of the issues on JIRA a week ago: https://issues.jenkins-ci.org/browse/JENKINS-31705 It seems that there are two AWS EB plugins which do the same thing and have similar names, so hopefully that's filed against the correct plugin.. :) Anyway, if you could

Re: Request for hosting: Git Relasenotes Plugin

No I dont want to merge them. I changed the name: https://github.com/tomasbjerre/git-publisher-plugin And the artifactid: git-changelog-publisher -Tomas Den tisdag 1 december 2015 kl. 21:39:00 UTC+1 skrev Christopher: > > Hi there, > > On 20/11/15 22:56, Tomas Bjerre wrote: > > Repo:

Re: Request for hosting

Hi Michael, Seems interesting. Just had a look at your plugin, I wonder why you want to call it "logstash-query-plugin", when your code and even your documentation [1] says ES. Why didn't you call it es or elasticsearch-query-plugin? IMO, even if you query indexes created by logstash, that's

Re: Request for hosting: Git Relasenotes Plugin

Hi there, On 20/11/15 22:56, Tomas Bjerre wrote: > Repo: https://github.com/tomasbjerre/git-releasenotes-plugin > Username: tomasbjerre > JenkinsCI username: tomasbjerre > > I made a pre-release here with some screenshots: > https://github.com/tomasbjerre/git-releasenotes-plugin/releases > >

Re: Bugs in AWS Elastic Beanstalk Deployment Plugin and AWS Elastic Beanstalk Publisher Plugin

Have you noticed the newly released versions of AWSEB Deployment Plugin now works with the AWS Credentials Plugins? (can't say for Publisher - It started from a copy from a user which tells me how to run issues instead of being patient) btw, we're in the wrong place. The right now is this:

Re: Plugin hosting request: terraform-plugin

Thanks! On Tuesday, December 1, 2015 at 3:50:22 PM UTC-5, Christopher wrote: > > Done! You should get an invite from GitHub by email. > > Welcome aboard :) > > Regards, > Chris > > > On 30/11/15 21:06, David Pires wrote: > > All, > > > > I'm in the final steps of finishing off my plugin

Re: Plugin hosting request: terraform-plugin

Done! You should get an invite from GitHub by email. Welcome aboard :) Regards, Chris On 30/11/15 21:06, David Pires wrote: > All, > > I'm in the final steps of finishing off my plugin for Terraform (more > testing, adding help files, writing documentation for wiki etc) and i'd > like to

Are you attending Fosdem 2016?

Hi All, Planning is underway for Fosdem 2016 (30 & 31 January 2016 ). We'd like to get an accurate head count of Jenkins contributors who will be able to help out at the Jenkins exhibit table. Pls email me off

Re: Request for Jenkins API Documentation

Most probably the file is locked by another process, Windows likes it. For example, even notepad can lock the file and block modifications from other places. You can use ProcessExplorer from Windows Essintials to discover a list of processes keeping the file lock. If there is a Jenkins process,

Re: Cannot get i18n message resolved on a config page

Messages.properties is only used for string referenced in (Java) source code. For foo.jelly / foo.groovy views, put your strings into foo.properties in the same folder. On 12.11.2015, at 16:48, Kirill wrote: > Hi folks, > > This is probably something very simple, but I

Re: Commit access for notification-plugin

Sorry for the response delay. Have you contacted the plugin's owner? Commonly we require a direct request and a 1-2 week delay before going forward with permissions вторник, 10 ноября 2015 г., 0:48:43 UTC+3 пользователь Kristen Oliphant написал: > > Hello, > > I would like to get commit access

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: Request for participation: Jenkins Security Officer candidates

Just read this e-mail. Congrats to Daniel! среда, 11 ноября 2015 г., 0:43:19 UTC+3 пользователь R Tyler Croy написал: > > > Based on the team lead proposal > (https://wiki.jenkins-ci.org/display/JENKINS/Proposal+-+Project+sub-teams) > > which was approved in the governance meeting last month,

Re: Throttle Concurrent Builds Plugin pull request

Hi Dmitry, My apologies, I was out of the community due to the personal reasons. Don't hesitate to contact plugin owners next time. I'll review the PR ASAP среда, 11 ноября 2015 г., 14:18:24 UTC+3 пользователь Dmitry Savenko написал: > > Hi, > > We have a project type, which does not extend

Re: Request for participation: Jenkins Security Officer candidates

I neglected to send an update this past week but the board has appointed Daniel Beck as the Jenkins Security Officer for the next 12 months. See On Tue, 10 Nov 2015, R. Tyler Croy wrote: > > Based on the team lead

Re: Cannot get i18n message resolved on a config page

Is the problem still actual? If yes, check that your messages are located in src/main/resources//MyBuildStep/config.properties . Only this file is being included by default четверг, 12 ноября 2015 г., 18:48:00 UTC+3 пользователь Kirill написал: > > Hi folks, > > This is probably something very

Re: Making New Plugin (Diff of console, source code, config files etc)

AFAIK there is no plugins directly addressing this things. Several related bits: - https://wiki.jenkins-ci.org/display/JENKINS/Artifact+Diff+Plugin - https://github.com/ablage/visual-diff-plugin (not published) - Job Config History allows to configure Jenkins item configs accross

Re: Adopt a plugin: job-import-plugin

Added Jesse Farinacci to Cc. He is active in the community sometimes, ho maybe his +1 is required. +1 from me вторник, 24 ноября 2015 г., 13:30:28 UTC+3 пользователь Emilio Escobar написал: > > Hi, > > I would like to adopt the Job Import Plugin ( >

Re: Travis Plugin Abandoned - Adopt?

Sounds like Java rewrite is the way to, sounds good to me, I'll update this thread when I have something to show. On Sun, Nov 29, 2015 at 5:31 PM, Daniel Beck wrote: > I don't think the Ruby Runtime is in a particularly great shape right now > anyway, so if you can keep

sitemonitor plugin new maintainer

Hi, As part of 'adopt a plugin' initiative, Francisco Hernandez will be the new maintainer of sitemonitor plugin. Could one of the admins update the lead for site-monitor component on JIRA? Francisco's jira id: onuba, github id: onuba Cheers, Cliff. -- You received this message because you

Plugin Hosting Request: couch-stats-plugin

All, I'm about ready to create the first release of my plugin to push build statistics to couchdb/cloudant, and I'd like to request hosting on jenkins-ci.org. - url: https://github.com/garethjevans/couch-stats-plugin - name: couch-stats - github username: garethjevans -

Bugs in AWS Elastic Beanstalk Deployment Plugin and AWS Elastic Beanstalk Publisher Plugin

Hi Team, I found out some bugs while working on the AWS Elastic Beanstalk Deployment and AWS Elastic Beanstalk Publisher Plugin. *1. AWS Elastic Beanstalk Plugin* In this, *a) The most vulnerable issue is that, AWS secret key is visible and its not hiding. So its a security issue.*

[DISCUSS] Hide from the update center plugins without source code under the Jenkinsci github organization?

Hi, As an aside of Andrew's last e-mail, I'd like to try and clarify what we should do when plugins do *NOT* have their source code under the Jenkins github org: Should they be visible in the public standard Jenkins update center? But why care? Because IMO publicly available plugins are a

Re: Proposal: Deprecate/hide from the update center plugins without wiki pages

Rightie-o, then the clock is starting as of now - four weeks from today (on my birthday!), we'll be turning this on. A. On Tue, Dec 1, 2015 at 8:49 AM, Baptiste Mathus wrote: > > 2015-12-01 13:47 GMT+01:00 Daniel Beck : > >> >> On 30.11.2015, at 17:16, Andrew

Re: jclouds-plugin Commit Access for Merging and Releasing v2.8.1

Sure thing - adding you now. A. On Tue, Dec 1, 2015 at 10:02 AM, Michael Fero wrote: > I am interested in receiving commit access to merge and release a version > of the jclouds-plugin (https://github.com/jenkinsci/jclouds-plugin) to > address [JENKINS-31655] ( >

Re: [DISCUSS] Hide from the update center plugins without source code under the Jenkinsci github organization?

On Tue, Dec 1, 2015 at 5:32 AM, Baptiste Mathus wrote: > plugins forked under the Jenkinsci org, BUT still maintained elsewhere There are a number of such cases where the @jenkinsci fork is out of date. There are even cases where both the original and fork repository are

Re: Who should review and fork plugin hosting requests?

No, you need to ask again in your previous post: - https://groups.google.com/forum/#!searchin/jenkinsci-dev/git-releasenotes-plugin/jenkinsci-dev/Jsck8GgWwJg/ijBwak9RCAAJ Cheers On Tuesday, 1 December 2015 08:03:10 UTC+1, Tomas Bjerre wrote: > > I have been waiting since 20 nov for my plugin to

Re: Proposal: Deprecate/hide from the update center plugins without wiki pages

Repeating my words again. -1 Wiki page may be lost because of different reasons (multi-module structure/refactoring is one of) and it absolutely not intuitive for developer why it doesn't appear in update center (enough headache with UC). AFAIK normal repositories like nexus rejecting "bad"

Re: Proposal: Deprecate/hide from the update center plugins without wiki pages

On 30.11.2015, at 17:16, Andrew Bayer wrote: > Thoughts? If I don't hear any strong opposition to this within a week, I'm > going to start the clock - four weeks after that, we'll switch the Update > Center generation to exclude any plugin without a corresponding wiki

jclouds-plugin Commit Access for Merging and Releasing v2.8.1

I am interested in receiving commit access to merge and release a version of the jclouds-plugin (https://github.com/jenkinsci/jclouds-plugin) to address [JENKINS-31655] (https://issues.jenkins-ci.org/browse/JENKINS-31655). My GitHub account name is 'mikefero'. Thank you for your assistance.

Re: Proposal: Deprecate/hide from the update center plugins without wiki pages

2015-12-01 13:47 GMT+01:00 Daniel Beck : > > On 30.11.2015, at 17:16, Andrew Bayer wrote: > > > Thoughts? If I don't hear any strong opposition to this within a week, > I'm going to start the clock - four weeks after that, we'll switch the > Update

deploy plugin pull requests

Hello, I am looking in to contributing to the jenkins project. For this I have found some tickets I would like to work on, but those changes have already been submitted.  jenkinsci/deploy-plugin |   | |   | |   |   |   |   |   | | jenkinsci/deploy-plugindeploy-plugin - Jenkins deploy plugin |

Re: Proposal: Deprecate/hide from the update center plugins without wiki pages

In parallel https://github.com/kohsuke/github-api/issues/195#issuecomment-161019362 how such rules handled in other projects in obvious and good ways. > On Dec 1, 2015, at 18:45, Andrew Bayer