Re: What should we do with the CLI?

2016-12-15 Thread Jesse Glick
On Thu, Dec 15, 2016 at 2:58 AM, Oliver Gondža wrote: > I would say we have to keep the client (jenkins-cli.jar) and Java API more > or less untouched to keep things compatible for clients and plugins. If JENKINS-26463 is implementable, this just means it all becomes a plugin,

Re: [Blue Ocean]Stages in parallel not being displayed correctly

2016-12-15 Thread Jesse Glick
On Thu, Dec 15, 2016 at 2:00 AM, James Dumay wrote: > […in Declarative Pipeline] Any parallels have to be within a stage and there > is not nesting of stages. Making it unusable for the originally requested use case, since you could not differentiate the

Re: Stapler and f:radioBlock nodes

2016-12-15 Thread Jesse Glick
On Wed, Dec 14, 2016 at 6:25 PM, 'Claudiu Guiman' via Jenkins Developers wrote: > Any ideas on what I’m doing wrong? Not offhand, but generally: I would advise you to avoid all such low-level controls. Use high-level databinding controls instead. Define an

Re: Can't configure the 'Jira Issues' Macro in Confluence

2016-12-15 Thread Daniel Beck
> On 16.12.2016, at 00:10, 'Claudiu Guiman' via Jenkins Developers > wrote: > > Is there any workaround or any plan to fix it? I don't think so. You can track this issue here: https://issues.jenkins-ci.org/browse/INFRA-575 And the Confluence upgrade here:

Re: [Blue Ocean]Stages in parallel not being displayed correctly

2016-12-15 Thread Jesse Glick
On Thu, Dec 15, 2016 at 5:09 PM, Alan Wu wrote: > please pardon me if I make any > mistake in my script. There is nothing wrong with that script; its structure is just beyond the “display resolution” of both Stage View and Blue Ocean at the moment. -- You received this

Re: [Blue Ocean]Stages in parallel not being displayed correctly

2016-12-15 Thread James Dumay
There's some design kinks to work out for nesting. I've been asking people to illustrate their desired visualization for nested staging when they've requested we fix visualization and I get a lot of varied expectations regarding how it should look (I suspect we're going to have to pick the most

RE: Can't configure the 'Jira Issues' Macro in Confluence

2016-12-15 Thread 'Claudiu Guiman' via Jenkins Developers
Hi, Is there any workaround or any plan to fix it? -Original Message- From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Daniel Beck Sent: Thursday, December 15, 2016 15:10 To: jenkinsci-dev@googlegroups.com Subject: Re: Can't configure the 'Jira

Re: Can't configure the 'Jira Issues' Macro in Confluence

2016-12-15 Thread Daniel Beck
> On 15.12.2016, at 23:50, 'Claudiu Guiman' via Jenkins Developers > wrote: > > Is this some known issue or am I providing the wrong URL? AFAIR this is an incompatibility between Confluence and Jira versions and it's been broken since we upgraded Jira a while

Re: [Blue Ocean]Stages in parallel not being displayed correctly

2016-12-15 Thread Alan Wu
Thanks so much for all the quick responses. Personally I think having the ability to visualise nested stages within each parallel node are important. Says if I now have the parallel block within a stage called "Build and test" and add in a "deploy" stage after it, here is my two cents on how

Re: [Blue Ocean]Stages in parallel not being displayed correctly

2016-12-15 Thread James Dumay
Alan how would you write the Jenkinsfile for that example? On Fri, Dec 16, 2016 at 8:39 AM James Dumay wrote: > Thats great info Alan. BTW you should watch and vote for this ticket > https://issues.jenkins-ci.org/browse/JENKINS-38442 > > On Fri, Dec 16, 2016 at 8:35 AM

Can't configure the 'Jira Issues' Macro in Confluence

2016-12-15 Thread 'Claudiu Guiman' via Jenkins Developers
Hi, I'm trying to set up a known issues section in my plugin's wiki page, but I can't set up the Jira extension. The URL I'm using is

Consolidated report of all jobs in a View

2016-12-15 Thread Lakshmi narayana
Hi, Not sure this is right forum to address - to seek your valuable suggestion. I have 7 views with each having 150+ jobs. Need to have dash board report for each view with in *Jenkins.* With - · Number of total builds in the view - · Failed Builds - ·

consolidated build report from views

2016-12-15 Thread Lakshmi narayana
Hi, I have 7 views with each having 150+ jobs. I would like to have dash board report for each view with With - · Number of total builds - · Failed Builds - · Success Builds - · Pie chart with statistics *This report needs to be saved

Re: consolidated build report from views

2016-12-15 Thread Lakshmi narayana
its my mistake. Sorry. Wrong window pls delete the post On Thursday, December 15, 2016 at 5:22:16 PM UTC+5:30, Daniel Beck wrote: > > > > On 15.12.2016, at 12:31, Lakshmi narayana > wrote: > > > > Having No Luck yet ! > > Unless you're asking how to write a plugin to do

Re: Fwd: Re: Maintainer request for ghprb

2016-12-15 Thread Ben Patterson
Re-sending so we include the Jenkins dev thread Hi Nitin I'm the maintainer. Why don't you send me a message with your plans? Honza - sorry you don't care about the plugin these days but your legacy lives on! Ben On Dec 15, 2016 7:58 AM, "Ben Patterson" On Dec 15, 2016 7:49 AM, "Honza

Re: Maintainer request for ghprb

2016-12-15 Thread Honza Brázdil
Hi, I'm not maintaining the plugin for over two years now. I gave access to somebody back then and the plugin went on without me. I don't know what the state is or who the current maintainer is. Looking at github, the most active developer now is Ben Patterson [1], I wonder what his

Re: consolidated build report from views

2016-12-15 Thread Daniel Beck
> On 15.12.2016, at 12:31, Lakshmi narayana wrote: > > Having No Luck yet ! Unless you're asking how to write a plugin to do this yourself, you're asking on the wrong mailing list. -- You received this message because you are subscribed to the Google Groups "Jenkins

Re: What should we do with the CLI?

2016-12-15 Thread Robert Sandell
Disable CLI by default for new installations, like we enable security by default. Perhaps most importantly change all the documentation that mentions CLI and replace with ssh. We should also look into the commands that require a remoting channel to the client and see if we can rewrite them to