Re: [2.0] Website rebump

I'm saying YES to showcase the plugins, but NO to hiding the extensibility way down the plugin list. IMHO the extensibility documentation is equally important as the plugins themselves and the user and installation guides, i.e. it should not be more than one click (and no scrolling) from the main

Re: QUESTION: ssh-agent dependencies

Hi, This dates from this commit back from 2015-08-24 by Manuel Recena: https://github.com/jenkinsci/ssh-agent-plugin/commit/010e968ab2ff8efa23a51d56d9046329140c96b5 from this PR https://github.com/jenkinsci/ssh-agent-plugin/pull/4 IIUC, this PR was supposed to add ssh-agent steps to DSL. Hence,

Re: [2.0] Website rebump

Back to the tech, If we go for a static site generation with a PR model I believe we need to have the individual plugin pages distributed somehow, because if everything is centralized to one repo with a PR model then we could risk loosing the wonderful silo model we currently have with plugins. I

Re: performance labs

So I actually tried creating test data a year or so ago (maven job type with a large number of sub modules) and creating several of them in folders - but I never saw the issues (3 hour cold startup time) I was seeing on the production instance :( Maven project is available at

Re: [2.0] Website rebump

Assuming the plugins moved into the static model and didn't remain in the Wiki side. Personally I think that perhaps we are trying to bite off too much in one chunk. Would a good starting point be taking a small part of the site (e.g. the Drupal + some basic getting started type stuff) and doing

Re: Jenkins 2.0 proposal

Cough cough ahem my scalability framework might do the job... If I can remember where I put that code (let's you script setting up a Jenkins with slaves, plugins, jobs, folders, etc... Can even fire the whole thing up on AWS too... Then I got distracted again... I wish I could keep focus!) On

Re: 2.0 - breaking out into multiple tracks

On Fri, Oct 9, 2015 at 4:41 PM, Arnaud Héritier wrote: > Will it increase the stability and performances of Jenkins. Not under current plans, no. IIUC the benefits would mostly be for new users who would start with small installations anyway. -- You received this message

2.0 website: content track

I'm dividing up the website conversation into several tracks. See this Wiki page for the overall structure. And in particular, in this thread let's focus on identifying pillars. In the original proposal that I made, which is captured very

Re: jenkins.ci library releases.

On Thursday, October 8, 2015 at 1:57:43 PM UTC+2, Jesse Glick wrote: > > On Thu, Oct 8, 2015 at 6:44 AM, James Nord wrote: > > "[maven-release-plugin] (jnord) some-funky-library-1.2.3-4" - but this > > would be the user on the CI system not the user on github. > > > > Would that work for

QUESTION: ssh-agent dependencies

Hi there, I'd like to know whether the ssh-agent plugin dependencies are wrong or not Latest Release Latest Release Date Required Core Dependencies1.8 ( archives) Aug 07, 2015

Re: Re: performance labs

On Tuesday 06 October 2015 22:29:31 Michael Neale wrote: > When you say "job upload" what were you measuring? it was actually a measurement how Jenkins responsiveness to POST requests changes when you switch underlying web server and was done by one of my students as part of his master thesis,

2.0 website: tech track

I'm dividing up the website conversation into several tracks. See this Wiki page for the overall structure. My summary of the tech track discussion so far is that: - There's a proposal on the table best summarized in this post

Re: QUESTION: ssh-agent dependencies

> On 09 Oct 2015, at 15:54, Daniel Beck wrote: > > > On 09.10.2015, at 10:19, Victor Martinez > wrote: > >> In order to support the workflow plugin those dependent modules should be >> part of every plugin? If that's the case, is there any

2.0 website: sticker making track

I'm dividing up the website conversation into several tracks. See this Wiki page for the overall structure. The sticker making track of the conversation is about the presentation, which we didn't talk about that much. One of the things

Re: 2.0 - breaking out into multiple tracks

> > > And Jenkins 2.0 is a big change for users --- you suddenly get a whole lot of > new things you haven't used before, and it encourages & promotes different > ways of using it. I think it's well qualified to call it 2.0, and I don't > think it's trying to untrain the general expectation.

Re: [2.0] Website rebump

TOP POSTING because holy mega-thread batman! :) What I see happening here is solutions being mixed up with problem statements The top-level goals, in my opinion are (in no particular order): * Make a good usable site, that looks good and connects visitors with the information that is

Re: [2.0] Website rebump

2015-10-09 14:34 GMT-07:00 R. Tyler Croy : > What I see happening here is solutions being mixed up with problem > statements > ... > Anyways, if you're passionate about the subject, fleshing out ideas and > proposals in confluence is IMHO the best path forward. > Let me

Re: [2.0] Website rebump

Tried out the demo you had setup - overall I think it is good for content that doesn't change too often but I worry about content that changes on a regular basis or trying to get somebody who isn't that upskilled in things like GitHub to understand and follow the process. (e.g. The fact that after

Re: QUESTION: ssh-agent dependencies

On Fri, Oct 9, 2015 at 4:25 PM, Arnaud Héritier wrote: > you are proposing to rewrite the dependencies resolution mechanism of maven > and friends in bash ? Of course not! First of all I said nothing about Bash. Second, Jenkins dependency semantics are pretty simple:

Re: QUESTION: ssh-agent dependencies

Thank for those answers and suggestions to solve those dependencies. I can somehow wrap that functionality but as long as I use the puppet jenkins module I'm a bit exposed since it doesn't support those transitive dependencies (https://github.com/jenkinsci/puppet-jenkins/tree/master) at the

New plugin Build-name-updater

- Github link: https://github.com/Le0Michine/Jenkins-Build-name-updater-plugin/tree/master - Repo name: "Build-name-updater-plugin" - User name the same as in the URL - jenkins-ci.org username: Le0; - Description: my plugin updates a build name during the build process, it

Re: [2.0] Website rebump

I think the talk of scrolling and hover menus is a giant red-herring. The form factor of the pages needs to be malleable and determined at least in part by the device requesting the information. We should not be trying to build a website from the toolbar menu down. We shouldn't be writing a new

Re: [2.0] Website rebump

> WDYT? That could work, but I'm personally not fond of drop down menus as it tends to be a suboptimal experience on touch devices. /B On Fri, Oct 9, 2015 at 12:36 PM, Daniel Beck wrote: > > On 09.10.2015, at 12:18, Robert Sandell wrote: > > > If we

Re: l10n - unable to commit

Em quinta-feira, 8 de outubro de 2015 21:14:29 UTC-3, Kohsuke Kawaguchi escreveu: > > Hmm, I could be wrong, but I don't see your CLA on file here > .What's > your jenkins-ci.org username? > > Hi Kohsuke, I thought I should

new plugin, attention-plugin

Hi We've are working on releasing a plugin we've used internally and making it public. We've committed it to my github account but would like to move it to the jenkinci github instead. Could someone help us setup an repository. It's a plugin we use internally to help tracking red builds. The

Re: performance labs

A theory of mine is that startup times can depend on how "old" your build records are, if there needs to be a lot of conversion of old data structures in new plugin versions that could have a measurable impact, maybe even OldDataMonitor gets involved and slows things down. So there could be a

Re: [2.0] Website rebump

On 09.10.2015, at 12:18, Robert Sandell wrote: > If we go for a static site generation with a PR model I believe we need to > have the individual plugin pages distributed somehow, because if everything > is centralized to one repo with a PR model then we could risk

Re: new plugin, attention-plugin

Hi, Trying to understand what your plugin does (a README could be added to give basic info + link to wiki ?) IIUC, it is designed to let people tell they volunteer to fix a build? If so, how does it compare to the Claim Plugin? Or Warnings maybe? Cheers 2015-10-09 13:25 GMT+02:00 Marcus

Re: QUESTION: ssh-agent dependencies

On Fri, Oct 9, 2015 at 9:54 AM, Daniel Beck wrote: > read the plugin dependencies from the HPI files and recursively (transitive > dependencies) add them to your installation Yes, you can do that. I tend to recommend instead that the tool building the image flag these as

Re: [2.0] Website rebump

On 09.10.2015, at 12:43, Robert Sandell wrote: > That could work, but I'm personally not fond of drop down menus as it tends > to be a suboptimal experience on touch devices. Check out how centos.org looks on your phone (or your browser at 770 or fewer pixels wide).

Re: [2.0] Website rebump

On 09.10.2015, at 12:24, Richard Bywater wrote: > In all of this I'd still like to have a discussion on how we might get > Confluence up to a modern version which would, I think, allow for a lot of > the "features" that we are looking for for some of the content at least.

Re: Request to become maintainer of SeleniumHtmlReportPublisher

Hi Stefan, I've transferred the ownership to you. You should get an invitation to jenkinsciorg soon. Welcome aboard! -- 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,

Re: New plugin Build-name-updater

Yes I have. But I considered this way again and decided to create pull request. On Friday, October 9, 2015 at 7:50:15 PM UTC+3, Victor Martinez wrote: > > Hi Lev, > Have you considered adding that feature to the build-name-setter plugin? > Cheers, > Víctor > > On Friday, 9 October 2015

Re: Request to become maintainer of SeleniumHtmlReportPublisher

Thx a lot. I'll go on with merging my branch and make a relase soon... Am Freitag, 9. Oktober 2015 19:02:33 UTC+2 schrieb Oleg Nenashev: > > Hi Stefan, > > I've transferred the ownership to you. You should get an invitation to > jenkinsciorg soon. > > Welcome aboard! > -- You received this

Re: QUESTION: ssh-agent dependencies

On Fri, Oct 9, 2015 at 12:09 PM, Victor Martinez wrote: > since the workflow plugin is an active plugin and being in > development actively, I wonder whether that particular dependency won't > affect it. How so? As of 1.0 there should be no incompatible API

Re: Jenkins 2.0 proposal

OK, this is probably something someone should start as a plugin. IIUC, you are taking the idea of the Job DSL plugin and then extending it to the system configuration, which I think is sensible. 2015-10-07 13:05 GMT-07:00 Baptiste Mathus : > Another idea I'll dump here. it's

Re: New plugin Build-name-updater

Hi Lev, Have you considered adding that feature to the build-name-setter plugin? Cheers, Víctor On Friday, 9 October 2015 18:24:55 UTC+2, Lev Mishin wrote: > > >- Github link: >https://github.com/Le0Michine/Jenkins-Build-name-updater-plugin/tree/master > >- Repo name:

Request to become maintainer of plugin-usage-plugin

Hi there, I've been waiting for a new release of this plugin, actually my PR was merged two weeks ago but it was requested in early July, so I wonder whether this project is abandoned somehow and if I can become a new maintainer of this project. @Christian what do you think? -

Re: QUESTION: ssh-agent dependencies

The same https://github.com/jenkinsci/credentials-binding-plugin/blob/master/pom.xml#L61-L65 -- 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: [2.0] Website rebump

On Friday, October 9, 2015 at 12:50:00 PM UTC+2, Daniel Beck wrote: > > > On 09.10.2015, at 12:43, Robert Sandell > wrote: > > > That could work, but I'm personally not fond of drop down menus as it > tends to be a suboptimal experience on touch devices. > > Check

Re: QUESTION: ssh-agent dependencies

Hello, As I said here [1], I'll review this dependency. But IIRC, It is necessary and is well configured. Regards, [1] https://github.com/jenkinsci/ssh-agent-plugin/pull/4#discussion_r41622070 2015-10-09 10:49 GMT+02:00 Baptiste Mathus : > Hi, > > This dates from this commit

Re: QUESTION: ssh-agent dependencies

СС jglick > On Oct 9, 2015, at 16:33, Manuel Jesús Recena Soto wrote: > > Hello, > > As I said here [1], I'll review this dependency. But IIRC, It is necessary > and is well configured. > > Regards, > > [1]

Re: QUESTION: ssh-agent dependencies

On 09.10.2015, at 10:19, Victor Martinez wrote: > In order to support the workflow plugin those dependent modules should be > part of every plugin? If that's the case, is there any planning to add those > features as part of the jenkins core? I like the idea of

Re: QUESTION: ssh-agent dependencies

On Fri, Oct 9, 2015 at 4:19 AM, Victor Martinez wrote: > In order to support the workflow plugin those dependent modules should be > part of every plugin? Yes. The `workflow-step-api` plugin was expressly designed to be small and devoid of UI so that it would be

Re: QUESTION: ssh-agent dependencies

Maybe the rationale is that this dependency is not seen as a big problem since workflow-plugin is actually composed of many different plugins, and that that one is more a library plugin. Hence that's not gonna install the workflowJob type in a unintentional manner? 2015-10-09 15:35 GMT+02:00

Re: QUESTION: ssh-agent dependencies

I'll find out another way of adding transitive dependencies in a less insane way of reading the wiki and see those dependent plugins as you already suggested some good approaches. Even though I don't like the idea of forcing that dependent plugin, actually I like the way of JobDSL being less

Re: 2.0 - breaking out into multiple tracks

2015-10-08 5:01 GMT-07:00 Nigel Magnay : > >> Ok, I'll bite. >> >> There are a number of conflicting things we need to balance. >> >> * There are some bigger UI/UX refreshes that we want to get out to >> users. A long standing complaint is that the Jenkins UI/UX is dated.

Re: 2.0 - breaking out into multiple tracks

On Friday, October 9, 2015 at 9:14:47 PM UTC+3, Kohsuke Kawaguchi wrote: > > > 2015-10-08 5:01 GMT-07:00 Nigel Magnay > : > >> >>> Ok, I'll bite. >>> >>> There are a number of conflicting things we need to balance. >>> >>> * There are some bigger UI/UX refreshes that we

Re: Plugin Hosting Request for Custom Command SCM and Node Cleanup Plugin

The return code handling can for sure be improved also I don't understand the issue at the moment. Code review is for sure a good Idea, I am not a routinized plugin developer. Nevertheless the SCM plugin is running in my companies build system with 4 slaves and has already survived thousands of