Hosting Request

2015-02-20 Thread Igor Filin


Hello,

 

My name is Igor Filin, I'm working for SmartBear Software (smartbear.com).

We created a plug-in for integrating our automated testing products - 
TestComplete and TestExecute - with Jenkins. The plug-in allows running 
TestCompete tests from Jenkins and viewing test results.

Could you add this plug-in to your plug-in list?

 

Plug-in name: tc

My GitHub username: Igor-Filin

 

Best regards,

Igor Filin

Software Engineer

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/ebab5817-4779-45d9-9663-65b0e3dad297%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Rename of JGiven-Plugin artifactId

2015-02-20 Thread Stefan Wolf
Hi,

I created a new plugin 
(see https://wiki.jenkins-ci.org/display/JENKINS/JGiven+Plugin 
and https://github.com/jenkinsci/jgiven-plugin).

It seems to me that I got the artifactId wrong - it should probably be 
jgiven and not jgiven-plugin.
Now I would like to rename that since not many users will have installed 
the plugin yet...
I opened a pull request to backend-update-center2 
(https://github.com/jenkinsci/backend-update-center2/pull/10) to ignore the 
jgiven-plugin and would then release a new version of the plugin with the 
correct artifactId.
Could someone please merge the pull request? Who has commit access to this 
repository - I am in the core group and don't have...

Regards,
Stefan

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/ff29a7e4-f40a-40b8-9f4f-99a4d203f133%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Validation or default values for repeatableHeteroProperty

2015-02-20 Thread Stefan Wolf
Hi,


Am Mittwoch, 18. Februar 2015 21:54:12 UTC+1 schrieb Jesse Glick:

 On Tue, Feb 17, 2015 at 6:02 AM, Stefan Wolf glow...@gmail.com 
 javascript: wrote: 
  I am using a repeatableHeteroProperty to configure a list of reports to 
  generate. Now I want to validate in the UI that this list is not empty. 
  Is this possible? 

 Not sure. You would expect to be able to add to the descriptor 

 public FormValidation doCheckReports(@QueryParameter ListReport value) { 
 return value.isEmpty () ? FormValidation.error(empty!) : 
 FormValidation.ok(); 
 } 


Thats what I tried and it didn't work.
 

 If that works, I would suggest filing a PR for the ui-samples-plugin 
 to demonstrate it. If not, something needs to be implemented in 
 repeatableHeteroProperty.jelly. 


So seems like I need to implement something.
Any ideas how to add default values for a field like that?

Regards,
Stefan 

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/2e1dab5e-c06f-481d-9837-07678d41938a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: request commit access to jenkinsci/gitlab-hook-plugin

2015-02-20 Thread Javier Palacios
I was trying to push to the gitlab-hook-plugin repository, and it seems
that I don't have permission. Do I miss something?

Javier Palacios

On Tue, Jan 20, 2015 at 10:59 PM, Ulli Hafner ullrich.haf...@gmail.com
wrote:

 Done. Welcome aboard! Ulli

 Am 20.01.2015 um 12:54 schrieb javier.palac...@fon.com:



 Hello,

 I'm going to take on the development of gitlab-hook plugin[1], so I would
 like to get access to https://github.com/jenkinsci/gitlab-hook-plugin. It
 would also be good if jira could get configured to automatically assign to
 me tickets opened for the gitlab-hook-plugin component.

 Both my github and jenkins ids are javiplx.

 Javier Palacios

 [1]
 https://github.com/elvanja/jenkins-gitlab-hook-plugin/pull/48#issuecomment-70327014


 --
 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 jenkinsci-dev+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/86a229e3-c60a-4647-a234-e2a268b43122%40googlegroups.com
 https://groups.google.com/d/msgid/jenkinsci-dev/86a229e3-c60a-4647-a234-e2a268b43122%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.


  --
 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 jenkinsci-dev+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/4B024401-4317-4577-8029-A331DF10BE1F%40gmail.com
 https://groups.google.com/d/msgid/jenkinsci-dev/4B024401-4317-4577-8029-A331DF10BE1F%40gmail.com?utm_medium=emailutm_source=footer
 .

 For more options, visit https://groups.google.com/d/optout.


-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAOAgqVzLURRs4Z_XtWJhFTdZP_NW_O8eW%2BvEbiixKu-gVdfevw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Rename of JGiven-Plugin artifactId

2015-02-20 Thread Daniel Beck
The repo is owned by the infra team, so I could merge it.

Do you know why some entries are 'foo=1' while others are just 'foo'? Does this 
not matter?

On 20.02.2015, at 09:57, Stefan Wolf glowwo...@gmail.com wrote:

 Hi,
 
 I created a new plugin (see 
 https://wiki.jenkins-ci.org/display/JENKINS/JGiven+Plugin and 
 https://github.com/jenkinsci/jgiven-plugin).
 
 It seems to me that I got the artifactId wrong - it should probably be jgiven 
 and not jgiven-plugin.
 Now I would like to rename that since not many users will have installed the 
 plugin yet...
 I opened a pull request to backend-update-center2 
 (https://github.com/jenkinsci/backend-update-center2/pull/10) to ignore the 
 jgiven-plugin and would then release a new version of the plugin with the 
 correct artifactId.
 Could someone please merge the pull request? Who has commit access to this 
 repository - I am in the core group and don't have...
 
 Regards,
 Stefan
 
 -- 
 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 jenkinsci-dev+unsubscr...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-dev/ff29a7e4-f40a-40b8-9f4f-99a4d203f133%40googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/372ECC6F-4C6F-4B23-821D-6689F8BA8365%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.


Running a command line instruction in HelloWorld plugin

2015-02-20 Thread Bruno
Hi everyone,

I'm trying to develop a Jenkins plugin for some internal tools, and I'm a 
complete newbie. Basically, I just want to run some command line 
instructions, (then to collect data from reports generated by the previous 
instructions and to draw graphs). 

In the HelloWorld plugin, the only class is HelloWorldBuilder extending 
Builder. I assume that I have to write some lines in the perform method 
to run, say, a instruction like mkdir new_folder.

How can I do this ? I've tried to use the BatchFile class to run a .bat 
(instead of a single instruction), but the javadoc page is quite empty..

Thx in advance.

Bruno

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/a4e1d5d1-795d-4a14-9239-1d62767bbf85%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Running a command line instruction in HelloWorld plugin

2015-02-20 Thread Mads Nielsen
i think you can use the launcher parameter in your perform.

So like
launcher.launch().pwd(build.getWorkspace()).cmdAsSingleString(mkdir
new_folder).join()


On Fri, Feb 20, 2015 at 3:48 PM, Bruno bruno.mart...@liebherr.com wrote:

 Hi everyone,

 I'm trying to develop a Jenkins plugin for some internal tools, and I'm a
 complete newbie. Basically, I just want to run some command line
 instructions, (then to collect data from reports generated by the previous
 instructions and to draw graphs).

 In the HelloWorld plugin, the only class is HelloWorldBuilder extending
 Builder. I assume that I have to write some lines in the perform method
 to run, say, a instruction like mkdir new_folder.

 How can I do this ? I've tried to use the BatchFile class to run a .bat
 (instead of a single instruction), but the javadoc page is quite empty..

 Thx in advance.

 Bruno

  --
 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 jenkinsci-dev+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/a4e1d5d1-795d-4a14-9239-1d62767bbf85%40googlegroups.com
 https://groups.google.com/d/msgid/jenkinsci-dev/a4e1d5d1-795d-4a14-9239-1d62767bbf85%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.




-- 
[image: ]
Mads Nielsen
Consultant
m...@praqma.net
+45 50 98 18 09
Skype: inkspot
Praqma
www.praqma.com
Allerød Stationsvej 4
DK-3450 Allerød
+45 36 77 27 62

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAFariut6JoirzuyUvtz_Hd4-LTjfnvomAVrgeujcy81C%3D4wyog%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins UX

2015-02-20 Thread Tom Fennelly
Great stuff here guys.

Hopefully we can translate some of these ideas into here into JIRA feature 
tasks (if not already in JIRA) for tracking (label user-experience).

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/dcfbc084-2004-4a3d-bfc4-4161714f4db6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Running a command line instruction in HelloWorld plugin

2015-02-20 Thread Bruno
Works fine, thank you !

Le vendredi 20 février 2015 15:54:27 UTC+1, Mads Nielsen a écrit :

 i think you can use the launcher parameter in your perform. 

 So like 
 launcher.launch().pwd(build.getWorkspace()).cmdAsSingleString(mkdir 
 new_folder).join()
  

 On Fri, Feb 20, 2015 at 3:48 PM, Bruno bruno@liebherr.com 
 javascript: wrote:

 Hi everyone,

 I'm trying to develop a Jenkins plugin for some internal tools, and I'm a 
 complete newbie. Basically, I just want to run some command line 
 instructions, (then to collect data from reports generated by the previous 
 instructions and to draw graphs). 

 In the HelloWorld plugin, the only class is HelloWorldBuilder extending 
 Builder. I assume that I have to write some lines in the perform method 
 to run, say, a instruction like mkdir new_folder.

 How can I do this ? I've tried to use the BatchFile class to run a .bat 
 (instead of a single instruction), but the javadoc page is quite empty..

 Thx in advance.

 Bruno

  -- 
 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 jenkinsci-de...@googlegroups.com javascript:.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-dev/a4e1d5d1-795d-4a14-9239-1d62767bbf85%40googlegroups.com
  
 https://groups.google.com/d/msgid/jenkinsci-dev/a4e1d5d1-795d-4a14-9239-1d62767bbf85%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.




 -- 
 [image: ]
 Mads Nielsen
 Consultant
 m...@praqma.net javascript:
 +45 50 98 18 09
 Skype: inkspot
 Praqma
 www.praqma.com
 Allerød Stationsvej 4
 DK-3450 Allerød
 +45 36 77 27 62

 

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/7eedb38c-a626-4a22-84cc-f98431d013dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Requesting access for jenkinsci/aws-codedeploy-plugin

2015-02-20 Thread 'McFarlane, Joshua' via Jenkins Developers
Hi,

I'm one of the engineers on the CodeDeploy team and would like commit access to 
merge in changes for the aws-codedeploy-plugin from our source repository.

Plugin Name: aws-codedeploy-plugin
GitHub ID: https://github.com/jmcfar
Source Repository: https://github.com/awslabs/aws-codedeploy-plugin
JenkinsCI Fork: https://github.com/jenkinsci/aws-codedeploy-plugin

Thanks!
Josh McFarlane

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/395B3471B1C92641BA25D4313C14D0564C3B7DF7%40ex10-mbx-31007.ant.amazon.com.
For more options, visit https://groups.google.com/d/optout.


Re: How does Jenkins test harness run the tests?

2015-02-20 Thread Jesse Glick
On Thu, Feb 19, 2015 at 11:36 AM, Kirill yam...@gmail.com wrote:
 how does Jenkins JUnit rule organize tests if I run tests via Surefire
 Maven plugin without any custom settings (so it's 1 JVM and threads are
 reused)?

Depending on the parent POM version, there may be tests run in
parallel, but never 1 per JVM.

 is Jenkins instance shared by all the tests?

No. Each test case gets its own Jenkins.instance, $JENKINS_HOME, HTTP port, etc.

(Unless you make JenkinsRule a @ClassRule rather than a @Rule. This is
rarely done, but it is an option if you are concerned about overhead
and none of the test cases within this suite actually change any
settings or create any items, but merely rely on Jenkins services
being loaded.)

 I have a few tests that delete all the projects

No need to delete projects unless they were created earlier in the
same test case (@Test method).

 then create the project with the same name -
 MY_PROJECT on set up (annotated by @Before). However, sometimes tests fail
 complaining that MY_PROJECT already exists - but quite rarely, probably 1 in
 10 times.

I have never seen such a thing happen. Perhaps your test is doing
something unusual, or your plugin has an odd flaw.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0r8xdgOkEeS9o8-VL4_D_ERh7f-NDvY7tvdTyW3eX8fQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Ignore SCM Polling schedule option from job Config.

2015-02-20 Thread adib
Hi,

 Internally we use Git as the SCM with git plugin which triggers poll 
on push request. For internal use I am looking for a way to Ignore the SCM 
polling schedule option from the job configuration page, so that jobs are 
only triggered on push notifications and not based on cron values in this 
field.

   One of the possible ways i thought of was to replace the already present 
SCMTrigger object in the Job Trigger with a new SCMTrigger with empty spec 
value when a user saves the Job Configuration, but i couldn't find a good 
extension point to do so. Took a look at the SavebleListener but saving the 
project in onchange() doesn't look like a very good approach.

   Although ideally i would like to disable that option, but i couldn't 
find a way to disable UI elements of the config page with a plugin. If 
anyone has done something similar before would like to know their  thoughts.

   Any suggestions on the extension point or on the approach. I am looking 
of making this as a plugin or add it to git plugin and contribute back to 
the community so help from the community will help me to take the right 
approach from start.

thanks,
Aditya.


-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/d33a7fec-0dec-4b88-90dd-77738a11eca6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: New plug-in: Uno Choice Plug-in for dynamic parameters

2015-02-20 Thread Jesse Glick
On Thu, Feb 19, 2015 at 10:17 AM, 'Bruno P. Kinoshita' via Jenkins
Developers jenkinsci-dev@googlegroups.com wrote:
 rename the artifact ID and update the Javadocs and any other reference to the 
 old name

To be clear, I was not suggesting a change of artifactId, package
names, etc. Just the display name (pom.xml#name, and wiki title).

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2mJx6RUM%2BT24PBQJpXb108JJr8E8D9gKSrt7_MqmNCDA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Rename of JGiven-Plugin artifactId

2015-02-20 Thread Daniel Beck
Merged.

On 20.02.2015, at 22:58, Stefan Wolf glowwo...@gmail.com wrote:

 Hi Daniel,
 
 Am Freitag, 20. Februar 2015 15:25:44 UTC+1 schrieb Daniel Beck:
 The repo is owned by the infra team, so I could merge it. 
 
 Yes, please!
  
 Do you know why some entries are 'foo=1' while others are just 'foo'? Does 
 this not matter? 
 
 I can second Baptiste's comment that it doesn't matter, so you could remove 
 all the =1s.
 
 Thanks,
 Stefan 
 
 On 20.02.2015, at 09:57, Stefan Wolf glow...@gmail.com wrote: 
 
  Hi, 
  
  I created a new plugin (see 
  https://wiki.jenkins-ci.org/display/JENKINS/JGiven+Plugin and 
  https://github.com/jenkinsci/jgiven-plugin). 
  
  It seems to me that I got the artifactId wrong - it should probably be 
  jgiven and not jgiven-plugin. 
  Now I would like to rename that since not many users will have installed 
  the plugin yet... 
  I opened a pull request to backend-update-center2 
  (https://github.com/jenkinsci/backend-update-center2/pull/10) to ignore the 
  jgiven-plugin and would then release a new version of the plugin with the 
  correct artifactId. 
  Could someone please merge the pull request? Who has commit access to this 
  repository - I am in the core group and don't have... 
  
  Regards, 
  Stefan 
  
  -- 
  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 jenkinsci-de...@googlegroups.com. 
  To view this discussion on the web visit 
  https://groups.google.com/d/msgid/jenkinsci-dev/ff29a7e4-f40a-40b8-9f4f-99a4d203f133%40googlegroups.com.
   
  For more options, visit https://groups.google.com/d/optout. 
 
 
 -- 
 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 jenkinsci-dev+unsubscr...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-dev/962aa736-bcdb-412f-b781-c15221730b84%40googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/8669EC91-4AAC-4F6C-B362-50DDE12B99D6%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.


Re: Validation or default values for repeatableHeteroProperty

2015-02-20 Thread Jesse Glick
On Fri, Feb 20, 2015 at 3:51 AM, Stefan Wolf glowwo...@gmail.com wrote:
 So seems like I need to implement something.

Seems so.

 Any ideas how to add default values for a field like that?

I would suggest focusing your time on adding validation, which is more
broadly useful than default values. (Default values also tend to
interact poorly with other features.)

You would have to dig around to see where and how this is implemented
for existing controls. Search for checkUrl attribute in taglibs, CSS
class ‘validated’, and hudson-behavior.js sections for
registerValidator and FormChecker and controlValue.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0K0egOVPo%2BrwPpNYggGXCo%3D4ZA9Vmvo2ocAWrrcHT_rg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: New plug-in: Uno Choice Plug-in for dynamic parameters

2015-02-20 Thread Daniel Beck

On 20.02.2015, at 21:33, Jesse Glick jgl...@cloudbees.com wrote:

 Just the display name (pom.xml#name, and wiki title).

We have a minor issue with issue tracker components when display name and 
artifact ID are different, especially at the start of the name.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/EFDE0ACD-457C-4319-B2C3-F43FF06B8E0E%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins plugin's classloader isolation

2015-02-20 Thread Jesse Glick
On Fri, Feb 20, 2015 at 10:09 AM,  ejor...@gmail.com wrote:
 This is similar to the XmlFile problem we located but here we can not set the 
 XStream class loader

Do not really follow your example but it sounds like the XStream form
of your plugin’s settings includes this third-party library which
another plugin also bundles. So, stop using those types in your
settings. Use only classes defined in your plugin.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0MiZGbq09P8j3o1kj2Ww%3D%2Bkf6v72rXQyZyDG%3DPNAoSKg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins UX

2015-02-20 Thread Ulli Hafner
As I plug-in developer I would like to have more powerful UI building blocks 
that I can *easily* use. E.g., in my static analysis plug-in I’m currently 
using plain and old YUI tabs to categorize warnings by module, package, etc. 
Now that Tom improved the main view tabs in Jenkins core I also would love to 
improve these plug-in tabs in the same way. Is this feasible? How much effort 
does it take? What are the steps to do? etc.

As you already mentioned, the job configuration is not very user friendly, 
especially if there are multiple Advanced, Add, Delete, etc. buttons. If the 
input field layout is complex then it is really hard to understand which button 
belongs to which group. Having some layout templates would help...

And finally what I also would like to see is the possibility to have a more 
appealing project view where trend graphs etc. could be rearranged (e.g., like 
the Jira dashboard). One of my students is planning to provide some views in a 
way similar to Sonar in his master thesis. Is this easy to achieve in Jenkins? 
Where should we start the work? Can we reuse some existing components/libraries?

So my +1 for your path 2 and 3.

What I think is not so important is theming (but this might be a matter of 
taste). This works quite well for Jenkins core but as soon as other plugins are 
involved (and we have more than 1000) this is normally getting a mess. I would 
rather prefer to have *one* good looking theme for core *and* plugins. (This is 
quite similar to e.g. IOS themes where you get really beautiful new icons for 
the most important apps, but you still have a lot of other icons around that 
look totally misplaced in the new icon scheme). Here it would help if we would 
have some interested volunteers who would help plug-in developers to provide 
consistent icons.

 Am 18.02.2015 um 17:27 schrieb Gus Reiber grei...@cloudbees.com:
 
 At the end of last summer, my friend and co-worker, Tom Fennelly 
 https://github.com/tfennelly, along with the help of Kevin Burke 
 https://github.com/kevinburke, Daniel Beck 
 https://github.com/daniel-beck, and others began the first steps of 
 improving and modernizing the Jenkins user experience. In addition to some of 
 the superficial enhancements, these changes are meant to add a bit of 
 responsiveness and cross-device usability to the Jenkins GUI, as well as 
 adding a means of creating and swapping new CSS based display themes. This 
 effort is best summarized by this article from Jenkins-ci.org, and this 
 thread from the Jenkinsci-users group:
 User Interface Refresh http://jenkins-ci.org/node/501#disqus_thread: 
 http://jenkins-ci.org/node/501#disqus_thread 
 http://jenkins-ci.org/node/501#disqus_thread
 Any comments on the UI changes in 1.572 
 https://groups.google.com/forum/#!searchin/jenkinsci-users/ui$20tom/jenkinsci-users/ULEV87g9iac/LaTt5J2tHV8J:
  
 https://groups.google.com/forum/#!searchin/jenkinsci-users/ui$20tom/jenkinsci-users/ULEV87g9iac/LaTt5J2tHV8J
  
 https://groups.google.com/forum/#!searchin/jenkinsci-users/ui$20tom/jenkinsci-users/ULEV87g9iac/LaTt5J2tHV8J
 As part of our second wave effort here at CloudBees, I am looking at ways of 
 improving the usability of the Jelly based form controls used in the item 
 creation and configuration pages and the responsiveness and interactivity of 
 the main dashboard grid control.
 
 In my investigations so far, I believe there are essentially 3 non-exclusive 
 paths forward for enhancing these elements:
 CSS only -- Building on the last round of enhancements, we can offer a set of 
 theme extensions that will allow the Jenkins users and community to customize 
 basic layout, iconography, and typeface to tailor Jenkins to their own tastes.
 UI component expansion and refactoring -- By modifying and adding to the 
 existing set of Jelly files and their corresponding data binding rules we can 
 significantly modernize the way Jenkins views and configs draw themselves and 
 potentially streamline plugin creation.
 Client side MVC veneers -- In a manner similar to what CloudBees has recently 
 done with the new Workflow visualization, we can rethink our approach to new 
 feature UIs by using a REST API based architecture coupled with client-side 
 rendering widgets. This would allow us to use newer framework libraries like 
 Angular.js and newer component libraries like Bootstrap and JQuery UI to add 
 greater richness to the Jenkins user experience.
 These are likely not the only paths forward, but merely the first I can think 
 of.  With that reality in mind, I am hoping to reach out to you the Jenkins 
 community to help ground and sculpt our thinking about what is both possible 
 and desirable.
 
 If you are at all interested in the Jenkins user experience, I would love to 
 get your feedback of any sort on this thread, which could be as simple as a 
 +1 or as involved as a PHD thesis or as much as you have time to type into 
 a response box.
 
 To the extent that it helps 

Re: Jenkins UX

2015-02-20 Thread Slide
I completely agree with the configuration page stuff. Email-ext has so many
options these days that whenever someone wants a new feature, I cry a
little thinking about how its going to make the UI more of a mess. I'm
definitely open to any ideas people have on improving it, but it would be
nice to have some additional widgets to grab from the taglibs.

On Fri Feb 20 2015 at 4:57:29 PM Ulli Hafner ullrich.haf...@gmail.com
wrote:

 As I plug-in developer I would like to have more powerful UI building
 blocks that I can *easily* use. E.g., in my static analysis plug-in I’m
 currently using plain and old YUI tabs to categorize warnings by module,
 package, etc. Now that Tom improved the main view tabs in Jenkins core I
 also would love to improve these plug-in tabs in the same way. Is this
 feasible? How much effort does it take? What are the steps to do? etc.

 As you already mentioned, the job configuration is not very user friendly,
 especially if there are multiple Advanced, Add, Delete, etc. buttons. If
 the input field layout is complex then it is really hard to understand
 which button belongs to which group. Having some layout templates would
 help...

 And finally what I also would like to see is the possibility to have a
 more appealing project view where trend graphs etc. could be rearranged
 (e.g., like the Jira dashboard). One of my students is planning to provide
 some views in a way similar to Sonar in his master thesis. Is this easy to
 achieve in Jenkins? Where should we start the work? Can we reuse some
 existing components/libraries?

 So my +1 for your path 2 and 3.

 What I think is not so important is theming (but this might be a matter of
 taste). This works quite well for Jenkins core but as soon as other plugins
 are involved (and we have more than 1000) this is normally getting a mess.
 I would rather prefer to have *one* good looking theme for core *and*
 plugins. (This is quite similar to e.g. IOS themes where you get really
 beautiful new icons for the most important apps, but you still have a lot
 of other icons around that look totally misplaced in the new icon scheme).
 Here it would help if we would have some interested volunteers who would
 help plug-in developers to provide consistent icons.

 Am 18.02.2015 um 17:27 schrieb Gus Reiber grei...@cloudbees.com:


 At the end of last summer, my friend and co-worker, Tom Fennelly
 https://github.com/tfennelly, along with the help of Kevin Burke
 https://github.com/kevinburke, Daniel Beck
 https://github.com/daniel-beck, and others began the first steps of
 improving and modernizing the Jenkins user experience. In addition to some
 of the superficial enhancements, these changes are meant to add a bit of
 responsiveness and cross-device usability to the Jenkins GUI, as well as
 adding a means of creating and swapping new CSS based display themes. This
 effort is best summarized by this article from Jenkins-ci.org, and this
 thread from the Jenkinsci-users group:

- *User Interface Refresh
http://jenkins-ci.org/node/501#disqus_thread:*
http://jenkins-ci.org/node/501#disqus_thread
http://jenkins-ci.org/node/501#disqus_thread
- *Any comments on the UI changes in 1.572

 https://groups.google.com/forum/#!searchin/jenkinsci-users/ui$20tom/jenkinsci-users/ULEV87g9iac/LaTt5J2tHV8J:*
 https://groups.google.com/forum/#!searchin/jenkinsci-
users/ui$20tom/jenkinsci-users/ULEV87g9iac/LaTt5J2tHV8J

 https://groups.google.com/forum/#!searchin/jenkinsci-users/ui$20tom/jenkinsci-users/ULEV87g9iac/LaTt5J2tHV8J

 As part of our second wave effort here at CloudBees, I am looking at ways
 of improving the usability of the Jelly based form controls used in the
 item creation and configuration pages and the responsiveness and
 interactivity of the main dashboard grid control.

 In my investigations so far, I believe there are essentially 3
 non-exclusive paths forward for enhancing these elements:

1. *CSS only --* Building on the last round of enhancements, we can
offer a set of theme extensions that will allow the Jenkins users and
community to customize basic layout, iconography, and typeface to tailor
Jenkins to their own tastes.
2. *UI component expansion and refactoring --* By modifying and adding
to the existing set of Jelly files and their corresponding data binding
rules we can significantly modernize the way Jenkins views and configs draw
themselves and potentially streamline plugin creation.
3. *Client side MVC veneers --* In a manner similar to what CloudBees
has recently done with the new Workflow visualization, we can rethink our
approach to new feature UIs by using a REST API based architecture coupled
with client-side rendering widgets. This would allow us to use newer
framework libraries like Angular.js and newer component libraries like
Bootstrap and JQuery UI to add greater richness to the Jenkins user
experience.

 These are likely not the 

Re: How can I customize build details page?

2015-02-20 Thread Kirill
OK, so answer to question #1 is Yes - if Action has a summary.jelly, it's 
added to the build summary. Just tried that. Hurray!

But I still don't know whether it's possible to alter other summary 
sections, added by other build steps and plugins, or not. Is it possible to 
update their output or redefine the sequence of those sections?
It's probably not straightforward and not even a good idea.

четверг, 19 февраля 2015 г., 12:55:17 UTC пользователь Kirill написал:

 Hi,

 I'm new to Jenkins plugin development. Looks like plugins like Git or 
 Maven plugin are able to add stuff to build's details (see example 
 attached).
 As a result, there are different sections - Changes, Triggered by, 
 Test result, etc. How are they added? My understanding is that they 
 appear on build's details page if there's summary.jelly defined for 
 extension (Action). Is this correct? That question #1.
 Question #2 is - can I alter other summary sections (like Changes), 
 created by other plugins used in the build?

 Regards,
 Kirill.


-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/f4aa446b-3802-4e18-9c43-7c2dbcf084c3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins plugin's classloader isolation

2015-02-20 Thread ejorris
Hi, I do belong to same organisation as Kirill and responsible for one of 
the two mentioned plugins. We did locate one fault where we used the 
Jenkins XmlFile class to save on file. When adding a XStream with a proper 
ClassLoader defined we solved this part: 



*final XStream xs = new 
XStream();xs.setClassLoader(this.getClass().getClassloader());final XmlFile 
xFile = new XmlFile(xs, file);*

But we also have problems with the Jenkins saved job configurations files 
(config.xml). For instance we have a trigger implemented in plugin A which 
have a variable that is defined in the library that we share with the 
plugin B (different versions of the lib). From config.xml file:














*triggers  com.xxx.yyy.triggering.MessageTrigger 
plugin=ec@21.0.8-SNAPSHOTconsumers  
com.xxx.yyy.triggering.consumer.JobFinishedEventConsumer
jobInstanceNameTrigger/jobInstanceNameresults
com.xxx.yyy.datawrappers.ResultCode 
plugin=ec@21.0.8-SNAPSHOT  nameSUCCESS/name
/com.xxx.yyy.datawrappers.ResultCode  /results  
/com.xxx.yyy.triggering.consumer.JobFinishedEventConsumer
/consumers  /com.xxx.yyy.triggering.MessageTrigger/triggers*

When we do startup and act upon the* onLoaded()* we do something like this 
(simplified): 

f


*or (AbstractProject?, ? project : 
jenkins.getAllItems(AbstractProject.class)) {   for (Trigger? t : 
project.getTriggers().values()) { .JobFinishedEventConsumer 
consumer = ((MessageTrigger)t).getConsumers().get(0);*

If we then try to retreive the consumer value for ResultCode we get a class 
cast exception if we have both plugins installed.

I have not been able to figure out how/where I should set the correct class 
loader for this. This is similar to the XmlFile problem we located but here 
we can not set the XStream class loader... or can we?




  
  



-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/e5d2fbd5-4119-4623-aa2a-2883b098c061%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Rename of JGiven-Plugin artifactId

2015-02-20 Thread Stefan Wolf
Hi Daniel,

Am Freitag, 20. Februar 2015 15:25:44 UTC+1 schrieb Daniel Beck:

 The repo is owned by the infra team, so I could merge it. 


Yes, please!
 

 Do you know why some entries are 'foo=1' while others are just 'foo'? Does 
 this not matter? 


I can second Baptiste's comment that it doesn't matter, so you could remove 
all the =1s.

Thanks,
Stefan 


 On 20.02.2015, at 09:57, Stefan Wolf glow...@gmail.com javascript: 
 wrote: 

  Hi, 
  
  I created a new plugin (see 
 https://wiki.jenkins-ci.org/display/JENKINS/JGiven+Plugin and 
 https://github.com/jenkinsci/jgiven-plugin). 
  
  It seems to me that I got the artifactId wrong - it should probably be 
 jgiven and not jgiven-plugin. 
  Now I would like to rename that since not many users will have installed 
 the plugin yet... 
  I opened a pull request to backend-update-center2 (
 https://github.com/jenkinsci/backend-update-center2/pull/10) to ignore 
 the jgiven-plugin and would then release a new version of the plugin with 
 the correct artifactId. 
  Could someone please merge the pull request? Who has commit access to 
 this repository - I am in the core group and don't have... 
  
  Regards, 
  Stefan 
  
  -- 
  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 jenkinsci-de...@googlegroups.com javascript:. 
  To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-dev/ff29a7e4-f40a-40b8-9f4f-99a4d203f133%40googlegroups.com.
  

  For more options, visit https://groups.google.com/d/optout. 



-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/962aa736-bcdb-412f-b781-c15221730b84%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.