Re: Fill textbox default with java

Great! Moving it into the 'DescriptorImp' sure did the trick! On Thursday, August 18, 2016 at 3:49:19 PM UTC+2, Jesse Glick wrote: > > On Thu, Aug 18, 2016 at 9:14 AM, Robert Sandell > wrote: > > add your helper method to the descriptor instead. > > Thus

new contributors to windows-azure-storage-plugin and azure-slave-plugin

Hello Could we please have the following two GitHub IDs added to the contributors list for the windows-azure-storage-plugin and azure-slave-plugin? They will be working on enhancements

RE: new contributors to windows-azure-storage-plugin and azure-slave-plugin

Thank you. From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Slide Sent: Thursday, August 18, 2016 4:18 PM To: jenkinsci-dev@googlegroups.com Cc: Arun Chandrasekhar ; Huanhuan Sun ; Arjun Roy

Re: new contributors to windows-azure-storage-plugin and azure-slave-plugin

Done, they may need to accept the invitation on Github to be able to push, etc. On Thu, Aug 18, 2016 at 4:05 PM 'Martin Sawicki' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Hello > > Could we please have the following two GitHub IDs added to the > contributors list for the

Re: unable to use javascript ScriptEngine in pipeline step implementation

On Thu, Aug 18, 2016 at 12:55 PM, Chris Price wrote: > ScriptEngineManager manager = new ScriptEngineManager(); Probably your `Thread.currentThread().getContextClassLoader()` is not able to “see” the JRE’s engines for some reason a debugger might illuminate. Try using the

Re: unable to use javascript ScriptEngine in pipeline step implementation

On Thursday, August 18, 2016 at 10:54:41 AM UTC-7, Jesse Glick wrote: > > On Thu, Aug 18, 2016 at 12:55 PM, Chris Price > wrote: > > ScriptEngineManager manager = new ScriptEngineManager(); > > Probably your `Thread.currentThread().getContextClassLoader()` is not > able

Re: Documentation to understand Jenkins' jelly-isms

Thanks, It does look a lot cleaner. However, groovy or jelly still leaves me in the same place. I've found that I can review lib/form, lib/layout etc inside of the jenkins-core jar and read what would be the documentation. I guess that'll have to do. Cheers On Wednesday, 17 August 2016

[Plugin] Exception while saving configuration for custom plugin

Hello Jenkins developers, I’m currently developing a Jenkins plugin for deploying artifacts to a proprietary software by Hewlett Packard Enterprise. Therefore, I’m using the software’s Java API. The initial configuration of the job and the post-build step are working fine. The deployment

Re: Can't upload the hpi at end of build because repository is down

Effective POMs, after inheritance, interpolation, and profiles are applied: http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/mav 4.0.0

Re: Wiki's Plugin Information section not showing new release of plugin

Thanks. That works and I see the new version in the plugin wiki page. On Thursday, August 18, 2016 at 1:57:03 PM UTC+5:30, Daniel Beck wrote: > > We aggressively cache wiki pages, otherwise Confluence would be too slow. > If you add a query parameter, you circumvent the cache, and there it shows

Re: getTarget() in Pipeline

Sorry for the lousy context. But you where right, implementing 'StaplerProxy' did the trick! On Wednesday, August 17, 2016 at 4:45:48 PM UTC+2, Jesse Glick wrote: > > On Wed, Aug 17, 2016 at 1:58 AM, Markus Axelsson > wrote: > > public Object getTarget() { > > Is

Wiki's Plugin Information section not showing new release of plugin

I released a new version of Team Concert Plugin (v 1.2.0.1) on 16/08. The update has started showing up in Jenkins' update center. But the wiki's Plugin Information section still shows 1.2.0.0. Is there anything additional that needs to done to get the version updated? Usually it gets updated

Re: Wiki's Plugin Information section not showing new release of plugin

We aggressively cache wiki pages, otherwise Confluence would be too slow. If you add a query parameter, you circumvent the cache, and there it shows the correct version: https://wiki.jenkins-ci.org/display/JENKINS/Team+Concert+Plugin?nocache > On 18.08.2016, at 09:48, Lakshmi Narasimhan

Re: Interested in building your plugin on ci.jenkins.io?

Well, the default setting in the new plugin parent pom is a test-parallelisation of 1C and IIRC the default max heap the the JVM runs on is 512MB. My tests are a bit more hungry for heap than that so I've set the max heap to 1GB per fork (I used to have it on 2GB but our current build slaves

Re: Documentation to understand Jenkins' jelly-isms

The generated documentation is linked to in the "Additional references" section on the wiki https://wiki.jenkins-ci.org/display/JENKINS/Extend+Jenkins but the "taglibs defined in Jenkins core" link is broken, maybe something got lost when we migrated to jenkins.io ? /B On Thu, Aug 18, 2016 at

Re: Documentation to understand Jenkins' jelly-isms

Actually I favour jelly over groovy because it is much closer to the html... However I am an old hand and had experience with eg cocoon as a html rendering framework before I started with jelly back in 2006 I am not sure what the recommendations are going to be as we tradition to the blue ocean

Re: Backporting for 2.7.2 started

Must drink more coffee - this was meant to go to the 2.7.3 thread :-( On Thursday, August 18, 2016 at 11:23:48 AM UTC+1, James Nord wrote: > > Any chance of getting JENKINS-34668 included? > It was missing the candidate flag, and makes Jenkins (and derivatives) > looks really bad with browser

Re: Backporting for LTS 2.7.3 started

> On 18.08.2016, at 12:28, James Nord wrote: > > Any chance of getting JENKINS-34668 included? Correct link (HTML email is evil): https://issues.jenkins-ci.org/browse/JENKINS-34668 -- You received this message because you are subscribed to the Google Groups "Jenkins

Re: Documentation to understand Jenkins' jelly-isms

https://issues.jenkins-ci.org/browse/INFRA-897 /B On Thu, Aug 18, 2016 at 12:50 PM, Robert Sandell wrote: > The generated documentation is linked to in the "Additional references" > section on the wiki https://wiki.jenkins-ci.org/ > display/JENKINS/Extend+Jenkins but

Release Plugin-Errors

Hi, I have developed one plugin and submitted in the github repository,the plugin was already forked , while trying to release the plugin i am getting the following error,any one help me to resolve this issue. Thanks for helping. [ERROR] Failed to execute goal

Re: Backporting for LTS 2.7.3 started

Any chance of getting JENKINS-34668 included? It was missing the candidate flag, and makes Jenkins (and derivatives) looks really bad with browser width < 940 px which is not uncommon on windows 10 when using side-by-side viewing. /James On

Fill textbox default with java

This will probably my last question about this plugin. I have what seems as a simple issue. I want to give a default value to a textbox in my PlotBuilder\config.jelly: ... ... See complete file here

Re: Documentation to understand Jenkins' jelly-isms

I always open the tag source file, since the documentation is not necessarily sufficient to understand how to use it. I also frequently search GitHub to find usages of the tag in code that I trust to have been written by someone knowledgeable. Generally the tag usage is underdocumented. In

Re: Backporting for 2.7.2 started

Any chance of getting JENKINS-34668 included? It was missing the candidate flag, and makes Jenkins (and derivatives) looks really bad with browser width < 940 px which is not uncommon on windows when using side-by-side viewing. /James On Tuesday, July 19, 2016 at 12:53:45 PM UTC+1, ogondza

Re: Fill textbox default with java

On Thu, Aug 18, 2016 at 9:14 AM, Robert Sandell wrote: > add your helper method to the descriptor instead. Thus `default="${descriptor.defaultCsvFileName}"` where `DescriptorImpl` contains `public String getDefaultCsvFileName()`. -- You received this message because you

Re: Fill textbox default with java

The it reference is probably not referring to what you think it is, or probably null in case you are adding a new step (there is no instance of the step yet). So you probably need to add your helper method to the descriptor instead. /B On Thu, Aug 18, 2016 at 2:11 PM, Markus Axelsson <

Re: Parameterized plugin with pipeline plugin - BuildInfoExporterAction

On Wed, Aug 17, 2016 at 4:43 PM, Quang Truong wrote: > in those methods, > they return the list of AbstractBuild which can't be cast to WorkflowRun, so > the return list is not empty but those items which are WorkflowRun items are > Null objects. Then fix that plugin

unable to use javascript ScriptEngine in pipeline step implementation

Hi, I have a custom pipeline step I'm writing (in Java, implementing workflow Step/StepExecution). Inside of my step's implementation I need to load some JavaScript code. I started off with this approach: ScriptEngineManager manager = new ScriptEngineManager(); ScriptEngine engine =

Re: unable to use javascript ScriptEngine in pipeline step implementation

On Thu, Aug 18, 2016 at 2:30 PM, Chris Price wrote: > Is there any specific classloader you'd recommend for use in a plugin > context? Not really. That of some class in your plugin? Of some class in Jenkins core? The parent of that of some class in Jenkins core? You really need