Re: (another) docker slaves plugin - review request

I haven't fully grokked how the alternative launch scheme works (I assume it's operating as a launcher higher up the food chain). I don't know if this is giving you options of controlling the build environment before it is launched based on the build it is about to execute. I would imagine you

Re: create-text-file plugin - New hosting reuest

On 15.12.2015, at 17:06, Sanketh P B wrote: > could you please provide commit access for the same? I did. You just need to accept the invitation into the jenkinsci organization by GitHub. -- You received this message because you are subscribed to the Google Groups

Re: (another) docker slaves plugin - review request

> > > > nigelm, > > It uses queue listener to look for a label and add a slave . > > Docker has many, many load balancing tools , docker swarm for example. You > can simply point jenkins to your swarm instance for docker. > > I see no reasons why Jenkins would be doing load balancing with docker >

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: create-text-file plugin - New hosting reuest

Thanks for forking it. I am unable to commit to https://github.com/jenkinsci/text-file-operations-plugin.git, could you please provide commit access for the same? Error: remote: Permission to jenkinsci/text-file-operations-plugin.git denied to sankethpb. fatal: unable to access

Re: CRX Content Package Deployer Plugin

Hi Dean, If you are building an hpi/jpi file and uploading it manually, you probably have to restart the jenkins instance for the plugin to be activated. I test it using mvn hpi:run, which runs a local jenkins instance with the plugin already installed. Mark Adamcin http://adamcin.net/ On Tue,

Re: (another) docker slaves plugin - review request

So, do you agree that cloud api is not good enough for docker containers ? On Sunday, December 13, 2015 at 12:53:44 PM UTC-6, Surya Gaddipati wrote: > > This is not a hosting request. I am hoping to get some feedback on the > plugin and see if its worth hosting/merging into other plugins. > >

Re: (another) docker slaves plugin - review request

> Do you think that the cloud API *ought* to be good enough for docker containers ? Not quite sure what you mean. But yea cloud api should support single use throwaway slaves that are tied to a single build. On Sunday, December 13, 2015 at 12:53:44 PM UTC-6, Surya Gaddipati wrote: > > This

Re: (another) docker slaves plugin - review request

> On Dec 15, 2015, at 19:17, Surya Gaddipati wrote: > > >So what is your problem around Cloud API based provisioning? > > 1. Delay in provisioning -> There is no technical reason user has to deal > with this. This is totally a problem we can solve . > 2. Container

Jenkins Core PR - review

Hi All, Is there anything I can do get this PR reviewed. https://github.com/jenkinsci/jenkins/pull/1934 This is blocking us from running Load Balanced Jenkins ( without shared disk). Surya -- You received this message because you are subscribed to the Google Groups "Jenkins Developers"

Re: (another) docker slaves plugin - review request

Hi, that’s wrong info about docker-plugin. docker-plugin support: - provisioning jenkins slaves - building/publish images (duplicated/duplicates docker-build-publish-plugin) - Docker container controls All functionality is written via docker-java library layer. > On Dec 15, 2015, at 18:59, Surya

Re: (another) docker slaves plugin - review request

Hi Surya, Thanks for your reply, I've a few questions below. On Tue, Dec 15, 2015 at 4:43 PM, Surya Gaddipati wrote: > Hi Yoann, > Thank you for your response. > > > I was wondering what was missing to rewrite a simplified version of it. > > So here are couple of

Re: automatic behavior after job fails on a node

There is a todo in the Build Failure Analyser plugin to add steps to take in case a specific failure cause is found. But we never got around to implementing it. If you are interested you're welcome to taking a crack at it. https://wiki.jenkins-ci.org/display/JENKINS/Build+Failure+Analyzer /B On

Signup for jenkins-ci.org vs the spam problem

I just tried to sign up for Jenkin's Jira, so I was forwarded to the sign up page https://jenkins-ci.org/account/signup I filled out the form and send it to the server, there I got the response that you have an ongoing spam problem, I should post here. > Oops! > > Due to the spam problem, we

Re: Request for hosting: CPWR-PDS-download

Good question. CC'd Chad, who emailed me asking about the status here. If it doesn't make sense to combine them, I think the plugins seem ready to fork. -Chris On 14/12/15 16:24, Andrew Bayer wrote: > Out of curiosity, would it make more sense to combine these into one > compuware-download

Re: (another) docker slaves plugin - review request

> On Dec 15, 2015, at 18:43, Surya Gaddipati wrote: > > Hi Yoann, > Thank you for your response. > > > I was wondering what was missing to rewrite a simplified version of it. > > So here are couple of things that I found needed to be changed > > 1. changed to use

Re: (another) docker slaves plugin - review request

Hi nigelm, The important difference between this and all other docker slaves plugin is that this doesn't use jenkins' cloud api for the reasons listed here On Sunday, December 13, 2015 at

Re: (another) docker slaves plugin - review request

Hi Yoann, Thank you for your response. > I was wondering what was missing to rewrite a simplified version of it. So here are couple of things that I found needed to be changed 1. changed to use spotify-docker api client instead of command line, I needed it to talk to docker-swarm to

Re: (another) docker slaves plugin - review request

Surya, could you describe your use case because it seems that you want two orthogonal features in one? > On Dec 15, 2015, at 18:47, Surya Gaddipati wrote: > > Hi nigelm, > > The important difference between this and all other docker slaves plugin is > that this

Re: (another) docker slaves plugin - review request

Hi Kanstantsin , Use case is exactly this https://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin "The aim of the docker plugin is to be able to use a docker host to dynamically provision a slave, run a single build, then tear-down that slave." But without going through Jenkins Cloud

Re: (another) docker slaves plugin - review request

Yes, i'm working on such thing in my new plugin, will notify when will have something working. On Monday, December 14, 2015 at 6:41:26 PM UTC+3, Surya Gaddipati wrote: > > Hi Oleg, > Thank you for your feedback. > > Looks like DockerPlugin uses Jenkins clound api ( link >

Re: Best practices for integration of credentials in a plugin

Hi Adrien, Well, there is no real issue with the Plain Credential Plugin but I find that the label "secret text" used by this plugin when creating a new credential entry is a little bit vague. Using a simple password field would also work but I prefer using a credential item in order to avoid

Re: (another) docker slaves plugin - review request

Hi Surya, As one of the author of https://github.com/ndeloof/docker-slaves-plugin , I was wondering what was missing to rewrite a simplified version of it. Maybe we could work together to improve this plugin instead? Yoann. On Tue, Dec 15, 2015 at 2:29 PM, Kanstantsin Shautsou <

Re: Best practices for integration of credentials in a plugin

IMHO you should be looking by *interface* i.e. you want any credential that implements both PasswordCredentials and StandardCredentials. You should not be looking for a specific implementation type. If you look for a concrete implementation class then you prevent somebody implementing an

Re: (another) docker slaves plugin - review request

> I agree that independent Docker slave makes sense. > IIRC such functionality is provided by one of existing Docker plugins, but > I'm not sure. There're too many of them :( > > If no, I would vote for integrating the proposal into Docker-plugin if > there is no showstoppers. > > ​docker-plugin

Re: Best practices for integration of credentials in a plugin

Jean-Christophe, so I would say use the Plain Credential plugin. A plain text password is *never* the answer. I agree that the field name can be vague, but we can discuss about it with Jesse or create a quick PR. -- Adrien Le mar. 15 déc. 2015 à 14:58, jcsirot a écrit : >

Re: Signup for jenkins-ci.org vs the spam problem

Created, you should have gotten an email. -- Larry On Tue, Dec 15, 2015 at 4:55 AM, chefffe wrote: > I just tried to sign up for Jenkin's Jira, so I was forwarded to the sign > up page > https://jenkins-ci.org/account/signup > > I filled out the form and send it to the

CRX Content Package Deployer Plugin

Has anyone downloaded the source code, built the code and SUCCESSFULLY deployed the code into Jenkins? I can download the code and get it to build. Then, I can successfully install the plugin into Jenkins. However, for some reason it doesn't show up as an available plugin when I select "This

Re: Signup for jenkins-ci.org vs the spam problem

(replies inline) On Tue, 15 Dec 2015, chefffe wrote: > I just tried to sign up for Jenkin's Jira, so I was forwarded to the sign > up page > https://jenkins-ci.org/account/signup > > I filled out the form and send it to the server, there I got the response > that you have an ongoing spam

Re: Publish EZ-Templates plugin

#1 ez-templates-1.1 was deployed to the repo on Dec 14th ... http://repo.jenkins-ci.org/public/org/jenkins-ci/plugins/ez-templates/ ... but it's plugin info on the wiki page is blank ... https://wiki.jenkins-ci.org/display/JENKINS/EZ+Templates+Plugin ... and it doesn't appear in the update

Is there any way to post message from slave to Jenkins job console

Hi, I'm in need of posting info about ongoing test plan and test case from slave to jenkins job console in order to see the clear progress of the build. Is there any way to access jenkins job console from slave, if so please share your thoughts. Thanks, Ari -- You received this message