from:"Bruno P. Kinoshita"

Re: Errors on plugin development setup

2017-12-28 Thread 'Bruno P. Kinoshita' via Jenkins Developers

I was having the same problem yesterday. I believe some of my local maven repo 
artefacts were corrupted.
Deleting the .m2/repository folder and re-running mvn clean package fixed it.
Hope that helpsBruno

Sent from Yahoo Mail on Android 
 
  On Fri, 29 Dec 2017 at 6:31, Jean-Karlo Accetta 
wrote:   I'm trying to start development of a Jenkins plugin but I can't seem 
to get it started.  I've tried following several of the tutorials on the 
Jenkins pages but the HPI ones end up with the console saying its deprecated 
and that I should use the archetypes.  Those, in turn, end up giving me an 
error about the maven-enforcer-plugin.  Here is the output when running "mvn 
package" on a project created the empty-plugin archetype:

[INFO] Scanning for projects...
[INFO]
[INFO] 
[INFO] Building TODO Plugin 1.0-SNAPSHOT
[INFO] 
[INFO]
[INFO] --- maven-hpi-plugin:2.1:validate (default-validate) @ sample ---
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M1:display-info (display-info) @ sample 
---
[INFO] Maven Version: 3.5.2
[INFO] JDK Version: 9.0.1 normalized as: 9.0.1
[INFO] OS Info: Arch: x86_64 Family: mac Name: mac os x Version: 10.13.2
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (display-info) @ sample ---
[INFO] Restricted to JDK 1.7 yet 
org.kohsuke.stapler:stapler-jrebel:jar:1.253:provided contains 
org/kohsuke/stapler/JRebelFacet$ReloaderHook$1.class targeted to JDK 1.8
[INFO] Restricted to JDK 1.7 yet 
org.kohsuke.stapler:stapler-groovy:jar:1.253:provided contains 
org/kohsuke/stapler/jelly/groovy/Namespace.class targeted to JDK 1.8
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 3.200 s
[INFO] Finished at: 2017-12-28T12:21:11-05:00
[INFO] Final Memory: 54M/180M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce (display-info) 
on project sample: Execution display-info of goal 
org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce failed.: 
NullPointerException -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException 

I have looked online all day since yesterday and haven't found any helpful 
information on how to fix this issue or how to at least work around it.  I have 
tried setting the JAVA_HOME variable to both JDK 9.0.1 and JDK 1.8.0_152, while 
using Maven v3.5.2 and v3.5.0.

Any help would be greatly appreciated; thanks in advance.


-- 
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/21f2b298-44ff-456d-9ef5-64822739be14%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/1628811334.6136486.1514492052748%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Putting some plug-ins up for adoption

2017-08-23 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Oh, sorry for the typo.
Yes, these are **now** up for adoption.
ThanksBruno

On Wednesday, 23 August 2017, 2:33:15 PM NZST, Slide <slide.o@gmail.com>
wrote:

Do you mean the plugins are "now" up for adoption?
On Tue, Aug 22, 2017 at 4:41 PM 'Bruno P. Kinoshita' via Jenkins Developers
<jenkinsci-dev@googlegroups.com> wrote:

Hi,
Not using these plug-ins at the moment, and haven't had time to maintain them
lately. The following plug-ins are not up for adoption:
* https://wiki.jenkins.io/display/JENKINS/CCM+Plugin*
https://wiki.jenkins.io/display/JENKINS/TestLink+Plugin*
https://wiki.jenkins.io/display/JENKINS/Testopia+Plugin
Testopia is not being maintained anymore I think. Unless someone in Bugzilla
re-started work on it, then maybe the plug-in can be decommissioned.
CheersBruno

--
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/2038693730.153377.1503445286679%40mail.yahoo.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/CAPiUgVdsoTjVKskWu9_JEP8EvhhMTm4G0L5J5QR3zzavxdigJg%40mail.gmail.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/390109202.544103.1503475179391%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Putting some plug-ins up for adoption

2017-08-22 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hi, 
Not using these plug-ins at the moment, and haven't had time to maintain them 
lately. The following plug-ins are not up for adoption:
* https://wiki.jenkins.io/display/JENKINS/CCM+Plugin* 
https://wiki.jenkins.io/display/JENKINS/TestLink+Plugin* 
https://wiki.jenkins.io/display/JENKINS/Testopia+Plugin
Testopia is not being maintained anymore I think. Unless someone in Bugzilla 
re-started work on it, then maybe the plug-in can be decommissioned. 
CheersBruno

-- 
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/2038693730.153377.1503445286679%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request to join the Jenkins Security Team

2017-07-24 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hi Oleg,
I had seen the security advisory, and in the Wiki and GitHub I can see some
progress made to fix some of the 5 issues.
But I think the maintainer is the only one with access to read and comment in
the SECURITY-XXX tickets.
At least that's what I recall from when I worked on an SECURITY issue. My
intention was to check the progress of tickets, see if there was a patch
somewhere to be tested, or a discussion going on. And then try to help
scriptler and any other plugin I use/used or that is a dependency in one of the
plugins I use.
But I can wait till the maintainer has made further progress on the issues. I
will re-read the description of the security issues with more calm over the
next days, check latest code and try to liaise directly with the maintainer if
I have a patch.
CheersBruno

Sent from Yahoo Mail on Android

On Tue, 25 Jul 2017 at 0:06, Oleg Nenashev wrote:
Hi Bruno,

Generally I am +1 with this request. Having more people is definitely useful.

OTOH you probably do not need to be a member of the Security team if you just
want to fix Scriptler. It's vulnerabilities are publicly listed in this
advisory: https://jenkins.io/security/advisory/2017-04-10/ . Regarding plugins
maintained by active contributors, we usually assign security issues to them.
In all other cases like core fixes, yes it makes sense to join the security
team.

Best regards,
Oleg

суббота, 22 июля 2017 г., 12:38:12 UTC+3 пользователь kinow написал:
Hi,
I would like to request to be added to the Jenkins Security Team. My main
interest is in helping to fix issues in any dependency of the plug-ins I
maintain, as well as in the core. Right now Scriptler is a plug-in I would like
to try and see if I could help, as it is blocking active-choices-plugin.
GitHub with 2FA enabled: kinowCLA: https://github.com/jenkinsci/
infra-cla/pull/48FreeNode user: kinow
Thank youBruno

--
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/20d20e3c-a222-4d53-8309-3dd6daee74a0%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/614930702.4539161.1500901468492%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Request to join the Jenkins Security Team

2017-07-22 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hi,
I would like to request to be added to the Jenkins Security Team. My main 
interest is in helping to fix issues in any dependency of the plug-ins I 
maintain, as well as in the core. Right now Scriptler is a plug-in I would like 
to try and see if I could help, as it is blocking active-choices-plugin.
GitHub with 2FA enabled: kinowCLA: 
https://github.com/jenkinsci/infra-cla/pull/48FreeNode user: kinow
Thank youBruno

-- 
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/1708666797.3173034.1500716039118%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline Shared Groovy Libraries and system groovy script classpath

2017-05-07 Thread 'Bruno P. Kinoshita' via Jenkins Developers

+1 Andreas


Wanting the same right now. Started a small sandbox [1] some time ago to try 
understand everything I would need for active-choices, but got distracted by 
security and performance issues.

* Execute a Groovy script
* Allow user to add extra jars
* Graple dependency management support
* Option to enable script-security integration (on by default)

The Groovy execution layer in active-choices came from dynamicparameter-plugin, 
then was a bit tweaked. Later we added script-security. Now need to look into 
extra jars (right now integrating ImageJ).

Cheers
Bruno
[1] https://github.com/kinow/groovy-script-lib


From: Andreas Mandel 
To: Jenkins Developers  
Sent: Sunday, 7 May 2017 10:14 PM
Subject: Pipeline Shared Groovy Libraries and system groovy script classpath



Hi List,

since the last security updates, a common practice to work with system groovy 
scripting does not work any more. It might be easily resolvable with a small(?) 
change in the Pipeline Shared Groovy Libraries plugin.

We have a lot of system groovy scripts in Jenkins jobs that take care for 
cleanup, monitoring, etc. These jobs check out certain scripts from SCM and 
then call them as a system groovy script. With the recent changes, you cannot 
simply add and call something "dynamic" in the workspace as system groovy 
script anymore. I do not want to go a step back and put the whole code inside 
the Jenkins job definition. 

On the other hand with the Pipeline Shared Groovy Libraries plugin we now have 
a quite powerful library management plugin for groovy libraries. Unfortunately 
as of now this only works for pipeline jobs and not for the use in system 
groovy scripts. 

Would it be possible to add a functionality to mark a library in the Pipeline 
Shared Groovy Libraries plugin as "system groovy library" and so make it 
available on the class path of any system groovy script?

Could this work out? How are other resolving this topic?


Thanks,
Kind Regards,
Andreas.

-- 
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/c3537dfe-c206-428d-9e3a-7a298d98a785%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/800881429.5606274.1494162579878%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Yesterday's security advisory

2017-04-11 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Thanks for the detailed response Daniel.

>And even once the issue is fixed, there's overhead in coordinating release of 
>the fix, writing and publishing the advisory, blog, and warnings, sending 
>notifications, etc.

Perhaps we could create a type of Certified or Supported tag to plugins. 
Plug-ins under this tag/category would

* Use an ~recent LTS version
* Have security issues patches applied by the security team in 15 running days 
if there is no response from the maintainer
* Be released by the security team if a patch has been approved/reviewed but 
there was no response or availability of the plug-in maintainer

As a plugin developer, I would feel bad for others pushing changes and 
releasing the plug-in without notifying me; but if we had this category, then I 
think users/build engineers would favour to install plug-ins listed there, and 
as a plugin maintainer I would accept the items listed above as a way to show 
users updates would be released in a faster way.

Maybe this, combined with number of installations, could be a better indicator 
of how well maintained and production-ready the plug-in is (e.g. I would 
probably submit a plug-in to this category after I had confidence its API was 
ready and I had enough tests, fixed enough bugs, etc). Just food for thought.

>It's not enough to just assign an issue in SECURITY to plugin maintainers

Using what was suggested above, we would still assign the issue to them, but 
the security team could also work on a fix and propose the fix. Then the author 
of the plug-in could simply approve or provide further feedback.

> (...) (well, for me -- maybe I just suck at this)

I believe we worked on the active-choices plug-in issue, where we had to 
include the security script plug-in (SECURITY-255?). So having worked directly 
with you in the Jenkins security team, and having already dealt with CVE's in 
other libraries/projects in some companies, I must say that from the moment the 
issue was assigned to me, until we had the review, release schedule, and 
finally the review, everything was very professional and simple - from a plugin 
maintainer POV.

I felt quite bad for having a security issue in my code, but at no moment I 
felt like I was being blamed or pressured to release it as fast as possible 
(just to not disclose or leak anything about the issue at hand and carefully 
test the fix :). So kudos and thank you and all those involved in the security 
team! You definitely do not suck at this.

>We're always looking for more volunteers! Membership is open to most active 
>contributors. Prerequisites and process at https://jenkins.io/security/#team

Not the most active contributor, but will take a look to see if I can enlist, 
and maybe try to help in some way :)

Cheers
Bruno

From: Daniel Beck <m...@beckweb.net>
To: jenkinsci-dev@googlegroups.com 
Sent: Tuesday, 11 April 2017 10:55 PM
Subject: Re: Yesterday's security advisory

> On 11.04.2017, at 12:03, 'Bruno P. Kinoshita' via Jenkins Developers 
> <jenkinsci-dev@googlegroups.com> wrote:
> 
> Surprised to see scriptler there, wasn't expecting it given the number of 
> people using it. If there is anything I can do to help, just let me know. I 
> am a bit busy this week, but can definitely stop a couple of hours two or 
> three days this week and maybe during the upcoming holidays to help fixing 
> some issues.

Scriptler is also the one I hated most to delist. The advisory lists all the 
things currently wrong with Scriptler that we know of. Some of these I expect 
to be rather straightforward to fix. What needs some thinking is how to 
implement script execution in jobs in a way that's safe to use. Giving 
non-admins Run Scripts is not a good idea (in fact, this quirk of Scriptler is 
a major reason we threw in the changes to the auth strategies in this 
advisory), and build step configuration protection as implemented is rather 
easily circumvented, as demonstrated.

> It is not clear from your e-mail if that was a case of a problem in the 
> process used to communicate issues to plug-in maintainers, or if it was 
> caused due to the number of issues vs. number of people working on the issues.

Both.

It's not enough to just assign an issue in SECURITY to plugin maintainers -- 
many haven't had to deal with a privately reported security issue before, so 
the process required to prepare a fix is unusual, and we need to explain how to 
go about doing that. Then there's the problem that they may not even react, so 
I need to follow up via email, etc.

Once we have maintainers' attention, and they understand the process we'd like 
them to follow, there's the issue of implementation. Especially wrt scripting 
issues, some more advanced features may not map cleanly to sandboxing/approval. 
So these fixes took a lot more supporting effort than usual. And in cases where 
there's no maintainer,

Re: Yesterday's security advisory

2017-04-11 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hi Daniel,

Surprised to see scriptler there, wasn't expecting it given the number of 
people using it. If there is anything I can do to help, just let me know. I am 
a bit busy this week, but can definitely stop a couple of hours two or three 
days this week and maybe during the upcoming holidays to help fixing some 
issues.

I can try to help with scriptler (have been studying it to submit some pull 
requests / RFE's) and possibly with dynamicparameter. uno-choice was created 
based on dynamicparameter, so likely we can compare the code, look at some git 
commits, and try to pull the fix (likely security script plug-in integration?) 
into dynamicparameter.

Happy to test, reproduce bugs, or try to submit one or two pull requests if 
necessary.


>-- What should we do differently in the future, if a situation similar to this 
>one ever comes up again?

Excellent approach. Let's tackle the problem, not the blame :-)

It is not clear from your e-mail if that was a case of a problem in the process 
used to communicate issues to plug-in maintainers, or if it was caused due to 
the number of issues vs. number of people working on the issues. Do we need to 
increase the number of people in the security team, or define some timely 
process, like having a dashboard or notification system, that sends an e-mail 
every week with the number of issues pending notification?
Cheers
Bruno


From: Daniel Beck <m...@beckweb.net>
To: Jenkins Developers <jenkinsci-dev@googlegroups.com> 
Cc: Bruno P. Kinoshita <brunodepau...@yahoo.com.br>; neuralsandw...@gmail.com
Sent: Tuesday, 11 April 2017 9:51 PM
Subject: Yesterday's security advisory



Hi everyone,


We now had the situation where the number of vulnerabilities far exceeded what 
the security team could handle.

https://jenkins.io/security/advisory/2017-04-10/


As previously discussed on this list, I've suspended distribution of plugins 
that are currently vulnerable.

https://jenkins.io/blog/2017/04/10/security-advisory/#distributing-vulnerable-plugins


List of affected plugins:

https://github.com/jenkins-infra/backend-update-center2/blob/1be044d25a312ca90336044f501e0b9e38ca3b2e/src/main/resources/artifact-ignores.properties#L187...L209


Any thoughts about this, now that it has happened?


---


As I wrote in the blog post, I was unable to contact all maintainers. Most 
maintainers of affected plugins with fewer than 500 installations didn't learn 
about this in advance. This is really not how we usually work. I consider this 
to be an exceptional situation.


So, again, to affected plugin maintainers, I really am sorry. I just didn't see 
a feasible alternative to the chosen approach. Perhaps this thread can result 
in some ideas -- What should we do differently in the future, if a situation 
similar to this one ever comes up again?


---


And then there's plugins that needed to be delisted since they have mandatory 
dependencies on delisted plugins:

https://github.com/jenkins-infra/backend-update-center2/blob/1be044d25a312ca90336044f501e0b9e38ca3b2e/src/main/resources/artifact-ignores.properties#L212...L218


>From a security POV, there's nothing wrong (that I'm aware of) with any of 
>these, other than that they bring along with them an unsafe plugin. Some of 
>these are clearly tied to build-flow, so while that is gone, so are they. 
>Then, there are the others (maintainers in CC):


- uno-choice: This depends on Scriptler. I discussed that plugin with Domi 
(Scriptler's maintainer) when we couldn't get the fixes finished, and plan to 
work with him to fix the various issues over the next several weeks or so. Once 
that gets restored, uno-choice would also be published again.

- externalresource-dispatcher: This depends on Build Flow, whose maintainers 
added a deprecation notice to the plugin wiki last year. I would be surprised 
if that got revived again. So there's probably no good solution, other than 
cutting this dependency, if we keep unsafe plugins delisted.

-- 
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/1232115132.555969.1491904981368%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Testing a plugin before release

2017-03-13 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Normally I just run `mvn clean test`, or `mvn clean test firebug:firebug 
firebug:gui`. Then if everything works, I trust the mvn release:prepare & 
perform will work. If you are not confident it will work, you can try cutting 
an experimental release [1], which might be useful too if you'd like to deploy 
it to a test bed server. Just use -alpha in your version.


Hope that helps
B


[1] https://jenkins.io/blog/2013/09/23/experimental-plugins-update-center/




From: JordanGS 
To: Jenkins Developers  
Sent: Tuesday, 14 March 2017 8:42 AM
Subject: Testing a plugin before release



So as to avoid burning through version numbers with bad releases, i was 
wondering if there is a way to test to make sure everything will compile 
beforehand?

To publish the plugin we use: 

mvn release:prepare release:perform 
The documentation says that the jenkins credentials can be verified with:mvn 
deploy
Is there any way to verify that the build will succeed?

Maybe (for maven)

mvn release:prepare -DdryRun=true
and to make sure that the pull to GitHub won't have issues, just 
ssh -T g...@github.com

Or is there anything else that can be used?

-- 
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/b7ede8ea-cc0f-4ca2-80d9-427a737f38e6%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/391913242.6212062.1489437449756%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Put NUnit Plug-in up for adoption

2017-02-16 Thread 'Bruno P. Kinoshita' via Jenkins Developers

+1

Bruno





From: slide 
To: Jenkins Developers  
Cc: brunodepau...@yahoo.com.br
Sent: Friday, 17 February 2017 10:17 AM
Subject: Re: Put NUnit Plug-in up for adoption



I would like to take up ownership of this plugin, if no one objects I can 
change the default assignee and submit the PR for the repo permissions.

Thanks,

Alex

On Wednesday, January 18, 2017 at 12:25:47 PM UTC-7, kinow wrote:
Hi,
>
>
>There was a few requests lately for me to fix an issue in order to provide 
>nunit3 compatibility with the plug-in.
>
>
>Unfortunately I'm on a 45 days vacation, and won't work on much Open Source 
>until March.
>
>
>So I'd like to put the nunit plugin up for adoption. This way someone else can 
>help the users and prepare a new release.
>
>
>Could someone refresh my memory on the process for that? Do I need to update a 
>git repo or wiki page?
>
>
>Cheers
>Bruno
>
>
>Sent from Yahoo Mail on Android
-- 
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/3c41ac81-d4f5-4b46-878b-153adaa56eed%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/1816982514.1162990.1487279926440%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Put NUnit Plug-in up for adoption

2017-01-18 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hi,
There was a few requests lately for me to fix an issue in order to provide 
nunit3 compatibility with the plug-in.
Unfortunately I'm on a 45 days vacation, and won't work on much Open Source 
until March.
So I'd like to put the nunit plugin up for adoption. This way someone else can 
help the users and prepare a new release.
Could someone refresh my memory on the process for that? Do I need to update a 
git repo or wiki page?
CheersBruno
Sent from Yahoo Mail on Android

-- 
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/659795736.8805757.1484767356478%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problem during plugin release

2016-11-06 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hi Thomas,

I had a similar problem trying to release active-choices-plugin last Friday.

What worked for me was reading


https://issues.jenkins-ci.org/browse/INFRA-588

and updating the project pom.xml. Here's the summary for the fix, extracted 
from INFRA-588:

"""
UPDATE: the recommended and simplest solution is to just upgrade to the 2.x 
parent plugin pom. See https://github.com/jenkinsci/plugin-pom
This issue has been fixed in that pom starting with its 2.5 version.
So, just use that pom, and remove the references/overrides from your pom to 
make sure you inherit the right values.
"""

So here's what I did:

https://github.com/jenkinsci/active-choices-plugin/commit/ccb6ed06784cc5499ef268e7d6bb81dfec46c350

Furthermore, after fixing it, the mvn release:prepare failed, due to FindBugs 
warnings (I assume this new parent is checking plug-ins for FindBugs issues). 
So I'd suggest

1) try changing your pom.xml as per INFRA-588
2) run mvn clean test findbugs:findbugs findbugs:gui and confirm all tests are 
passing, and that FindBugs is happy too
3) release it :)

Hope that helps,
Bruno




- Original Message -
> From: Thomas Fürer 
> To: jenkinsci-dev@googlegroups.com
> Sent: Monday, 7 November 2016 6:51 AM
> Subject: Re: Problem during plugin release
> 
> I have tried to execute these script but get an NullPointerException.
> 
> I also have filed an Pull Request for my change.
> 
> Maybe anyone from the infrastructure crew can add this.
> 
> 
> Thanks
> 
> Thomas
> 
> 
> Am 06.11.2016 um 11:05 schrieb Fritz Elfert:
>>  Hi,
>> 
>>  You do not have permissions to release thinBackup (actually NOBODY has).
>>  You can fix this yourself. Read the README here:
>>  https://github.com/jenkins-infra/repository-permissions-updater/
>> 
>>  Cheers
>>   -Fritz
>> 
>>  On 06.11.2016 10:14, Thomas Fürer wrote:
>>>  Hi,
>>> 
>>>  I'm the maintainer of thinBackup-plugin and I want to release 
> several
>>>  commits.
>>>  I tried it several time now with
>>> 
>>>  mvn release:prepare release:perform -Dusername=tofuatjava 
> -Dpassword=...
>>> 
>>>  but I finally I get the error message
>>> 
>>>  [INFO] [ERROR] Failed to execute goal
>>>  org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy 
> (default-deploy)
>>>  on project thinBackup: Failed to deploy artifacts: Could not transfer
>>>  artifact org.jvnet.hudson.plugins:thinBackup:hpi:1.8 from/to
>>>  maven.jenkins-ci.org (https://repo.jenkins-ci.org/releases/): Failed to
>>>  transfer file:
>>> 
> https://repo.jenkins-ci.org/releases/org/jvnet/hudson/plugins/thinBackup/1.8/thinBackup-1.8.hpi.
>>>  Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1]
>>> 
>>>  I tried to update my credentials at accounts.jenkins-ci.io, but nothing
>>>  changes.
>>>  So, please could anyone check my credentials on the plugin hosting
>>>  repository or verify my settings in the pom?
>>> 
>>>  thomas
>>> 
>>>  PS: I found several posts in the wiki, most of them are in my opinion
>>>  outdate and it is not easy to find the relevant things.
>>> 
>>> 
>> 
> 
> 
> -- 
> 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/d37fb7fc-a767-592b-f83f-523625b9450e%40gmail.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/565216906.1628411.1478461178676%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: R Plugin dependency

2016-07-01 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hi Michael,
Was going to reply but Alex was faster.
Let me know if you need any help with the R Plug-in too. I want to investigate
making Scriptler support R scripts too. This way plug-ins that use Scriptler
scripts would automatically support R too (e.g. active-choices :) ). Another
idea is perhaps integrate Shiny with Jenkins.
Feel free to shoot an e-mail here or off-list in case you need anything.
CheersBruno

From: Alexandru Somai
To: Jenkins Developers
Sent: Saturday, 2 July 2016 12:56 AM
Subject: Re: R Plugin dependency

Hi,
To answer your question, I think that the correct groupId for the R plugin is
org.biuno.r, so the dependency would be:

org.biouno.r
r
0.2

But I don't know, isn't an easier way to achieve what you need? without writing
a new plugin? Just a thought.
Regards,Alex
On Friday, July 1, 2016 at 1:23:36 PM UTC+3, micha...@gmail.com wrote:
Hello,
I am creating my first own plugin to have a common build step across my
different jobs. Many of my jobs are running the same script (build, deploy
artifacts, test...) and I want to unify that.This script is written in R and
therefore I would like to run this R script in my own plugin. There is already
a R Plugin that is usefull to write our own script in the job, therefore I
would like to use this R plugin to run my R scripts inside my plugin. I saw
that the first step is to have it as a dependency. How can I add it as a
dependency in pom.xml?
I tried to write that in pom.xml:

repo.jenkins-ci.org
http://repo.jenkins-ci. org/public/

org.jenkins-ci. plugins
r
0.2

But it is not working, I have this error when I run mvn hpi:run in my plugin
directory:
[ERROR] Failed to execute goal on project michaelPlugin: Could not resolve
dependencies for project michaelPlugin:michaelPlugin: hpi:1.0-SNAPSHOT: Failed
to collect dependencies at org.jenkins-ci.plugins:r:jar: 0.2: Failed to read
artifact descriptor for org.jenkins-ci.plugins:r:jar: 0.2: Could not transfer
artifact org.jenkins-ci.plugins:r:pom: 0.2 from/to central
(https://repo.maven.apache. org/maven2): sun.security.validator.
ValidatorException: PKIX path building failed: sun.security.provider. certpath.
SunCertPathBuilderException: unable to find valid certification path to
requested target
Thank you.
--
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/b80a553a-9a97-45f7-9427-ca06e690b444%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/1169367420.626933.1467411512220.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: RFH: salt plugin

2016-03-19 Thread Bruno P. Kinoshita

Hi Christian,
We are evaluating Saltstack at work, and one of the tasks assigned to me is to 
look into how to integrate our PHP/Java builds with the server provisioning and 
configuration.
I have a working test environment with one master and two minions, so will try 
to install saltstack-plugin in a test Jenkins server and then toy with it a 
little bit, and also try to reproduce the issue with the credentials-plugin. 
Will report any comments in that issue (though I think it might be better to 
use Jenkins JIRA?).
ThanksBruno

 
  From: Christian McHugh 
 To: Jenkins Developers  
 Sent: Saturday, 19 March 2016 3:18 AM
 Subject: RFH: salt plugin
   
Howdy everybody,
A while back I created a plugin that allows you to define a build step that 
kicks off salt calls through saltapi's rest 
interface.https://github.com/jenkinsci/saltstack-pluginhttps://wiki.jenkins-ci.org/display/JENKINS/saltstack-plugin
The plugin works well for the intended purposes. However, I am not a (java) 
programmer and due to a job change will not have as much time to dedicate to 
becoming one :) As such, I was wondering if there was anyone in the community 
willing to help assist with maintenance of this plugin and perhaps help with 
modernizing and properly jenkins'ing the codebase. 

Specifically, I just released a version of the plugin that trades out 
username/password fields in favor of using credentials ( :) ), but after making 
the release I've gotten a bug report that the credentials dropdown isn't being 
populated as expected ( :( 
)https://github.com/jenkinsci/saltstack-plugin/issues/16

This functionality works for me and some others that participated in some beta 
releases, but since I'm not able to replicate I'm not sure where to go from 
here. 
Is anyone able to provide guidance or direction on credentials usage or able to 
perform a quick code review with me? 

Thanks much!
-- 
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/a65543dc-0be4-42cb-9889-e35ea8186ca1%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/686800946.1669163.1458424097382.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Put Jenkins on the map

2015-09-17 Thread 'Bruno P. Kinoshita' via Jenkins Developers

I think it could be useful to have multiple layers on the map, with all enabled 
by default, but with an option to display only core committers, plug-in 
developers, CIA ambassadors, and so it goes.
 
  From: Baptiste Mathus 
 To: jenkinsci-dev@googlegroups.com 
 Sent: Thursday, 17 September 2015 8:49 PM
 Subject: Re: Put Jenkins on the map
   
Wondering, is this the jenkins developers at large that would appear on this 
map or only jenkins "core"? I.e. plugin developers too or not?
2015-09-17 10:46 GMT+02:00 Robert Sandell :



I made a quick fix to the map page, it's not beautiful, but now it should at 
least work again :)

http://jenkinsci.github.io/keyhole/


On Wed, Sep 16, 2015 at 7:38 PM, Alyssa Tong  wrote:

Hi Oleg,
it would be awesome to have both. This would be a good indicator of the growth 
of Jenkins. Since i'm not at all a developer, could someone help me to develop 
this map(s)?
thnxalyssa
On Sat, Sep 12, 2015 at 12:48 AM, Oleg Nenashev  wrote:

Hi Alyssa,

Are you looking for the "Jenkins events" map or for the "Jenkins contributors" 
map (probably both)? 
BTW here is the actual map setup guide: 
https://developers.google.com/maps/tutorials/kml/

Best regards,
Oleg

пятница, 11 сентября 2015 г., 11:29:55 UTC+3 пользователь Robert Sandell 
написал:
Well Google Maps no longer supports embedded KML without some changes

https://support.google.com/maps/answer/41136?p=kml=en=1

On Thu, Sep 10, 2015 at 8:08 PM, jieryn  wrote:

Sigh. You must be, you must be the change you want to see in the world. :-)

On Thu, Sep 10, 2015 at 2:07 PM, jieryn  wrote:
> You must the the change you want to see in the world. :-)
>
> On Thu, Sep 10, 2015 at 2:06 PM, Antonio Manuel Muñiz Martín
>  wrote:
>> 2015-09-10 19:27 GMT+02:00 jieryn :
>>> https://github.com/jenkinsci/keyhole
>>
>> Not working due to https://developers.google.com/maps/support/kmlmaps
>>
>> --
>> * Antonio Muñiz
>> * amunizmartin.com
>> * amuniz...@gmail.com
>>
>> --
>> 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/CACpar97Dpcq8vTcVnkJ_j1wc%3DOzXuvyrmK6-Ua9Y1o%3DjLucycQ%40mail.gmail.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-de...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAArU9iYZjcp1N2Nd3ewS5NorzJ%2BGQn8vEaX02ERYBtBCqVgCFA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.




-- 
Robert SandellSoftware EngineerCloudBees Inc.
-- 
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/2da6e9f5-a152-40b7-880f-6977d7d3212c%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/CAC9wNawXkcZ5A5XwtX%3DOJOBhF3cXyzYyWEsh%3DKk80_QEoh%2BkVQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.




-- 
Robert SandellSoftware EngineerCloudBees Inc.-- 
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/CALzHZS0tdtXEG%3DALSY%2B-XGa0AQYpNjz3asxGVDW0MsycXrJSiw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.




-- 
Baptiste  MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !-- 
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/CANWgJS7cG3dNQHV5%3D9gWCLHcqqNk1dVVjwrw%2B%3De5kzNCcUgxRA%40mail.gmail.com.
For

Re: CCM Plugin PR merge request

2015-09-14 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hi Antonio
I try to reply e-mails/pr's within days, but unfortunately haven't been able to
review yours, sorry. Cesar is busy with some personal projects and won't be
able to help at the moment.
Three weeks is a reasonable time but I prefer to give plug-in maintainers at
least 5 weeks of notice before asking commit rights or bumping the mailing
list, as some people may take 1 month vacation :o) but in case you have some
pending issues or need anything, drop me a mail off list. I try to keep my
inbox empty, so I reply e-mails faster than GitHub or mailing lists (which are
filtered to other folders).
Yesterday I started a new development cycle for the plug-ins that I maintain,
including ccm https://twitter.com/kinow/status/643200979945566208
However, I started with image-gallery, and will continue first with the ones
that are used in BioUno, as I have a hangout with another developer about these
plug-ins in the next days.
CheersBruno

From: Antonio Muñiz
To: jenkinsci-dev@googlegroups.com
Sent: Tuesday, 15 September 2015 3:33 AM
Subject: CCM Plugin PR merge request

Hello,

I've been pinging the maintainer of CCM Plugin for a while (@kinow) to
merge this PR: https://github.com/jenkinsci/ccm-plugin/pull/5

The second "official" maintainer (cesar1983, as listed in the pom)
does not seem to be active neither, so, could someone merge and
release this plugin? Or give me rights to do it?

Thanks,
Antonio.

--
Antonio Muñiz
Software Engineer
CloudBees, Inc.

--
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/CAJc7kzRpmkQ-%2BRbXBzLgrdbVrqr3E-4q8NMGbE4ff--aFd%3Deeg%40mail.gmail.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/1773335868.1743686.1442259157436.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: .hpi for statsd plugin

2015-08-01 Thread 'Bruno P. Kinoshita' via Jenkins Developers

If it is the statsd plugin from this repo [1], then it hasn't been released to 
Jenkins update center yet I think. There's a TODO in the read me, so worth 
checking with the author.
You can also browse the plugin mirrors [2] when looking for a hpi

[1] https://github.com/joemiller/jenkins-statsd-plugin[2] 
http://mirrors.jenkins-ci.org/plugins/

 
  From: Vanetta Floyd vanettafl...@gmail.com
 To: Jenkins Developers jenkinsci-dev@googlegroups.com 
 Sent: Saturday, August 1, 2015 6:58 AM
 Subject: .hpi for statsd plugin
   
Anyone know where I can get the .hpi for the statsd 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/607c468c-209c-4e3d-924a-305e720defc2%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/1515894067.38518.1438418548987.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Why is Jenkins using a HtmlUnit fork?

2015-07-27 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Just in case someone would like to check if we can get a new release of Apache 
Commons Jelly to replace our forked Jelly too; I'd started a discussion a 
couple of months ago in the apache dev-list and am (very) slowly working on it.

http://markmail.org/thread/r2vdpgtlbka62iki
Right now in my todo list:
- Mavenize the project, continuing Nial's work (just need to sort out the 
taglib site generation)- Understand what changed in Jenkins and why
- Review some old issues, including those submitted by KK 
https://issues.apache.org/jira/browse/JELLY-284?jql=PROJECT%3DJELLY%20AND%20CREATOR%3Dkohsuke-
 Start fixing issues- Find someone to be a release manager in commons

CheersBruno
 
  From: nicolas de loof nicolas.del...@gmail.com
 To: Mark Waite mark.earl.wa...@gmail.com 
Cc: jenkinsci-dev@googlegroups.com 
 Sent: Monday, July 27, 2015 7:14 PM
 Subject: Re: Why is Jenkins using a HtmlUnit fork?
   
I fully agree on the initial intent and benefit for project dynamic to fork and 
release custom binaries, the issue is those changes were not proposed upstream 
and in some cases (winstone for sample) the fork quickly diverged. As a result 
we hardly can get upstream improvements, I remember doing such an upgrade for 
svnkit and this was hard work to get confidence with the resulting codebase. 
Steven christou was able to switch back to mainstream svnkit which let us 
upgrade on a regular basisI'm confident Kohsuke and others don't fork unless 
they see it as the best way to solve the problem and deliver good value to 
Jenkins users.  I believe a fork is usually a response to a gap.
The SVNKit example is one that made Hudson (Jenkins) so compelling for me from 
the very beginning of Hudson(Jenkins).  Hudson support for Subversion worked 
well, whether or not the team maintaining SVNKit at that time had a full or 
complete solution to the problem.  I think the fork was done to benefit me as a 
user so that I could have a working, integrated, pure Java subversion 
implementation.  I wasn't required to install or configure Subversion on my 
Windows slave machines.  Yes, that focus on users made it harder for developers 
later, but I think that focus on users was part of what brought Jenkins to 
being installed on over 100 000 instances.
Since the attempt to port to the latest HTMLUnit was challenging, I suspect 
that means there were significant gaps between what was needed for Jenkins 
development and what HTMLUnit was providing at the time of the fork.
Mark Waite
On Sun, Jul 26, 2015 at 9:32 AM Tom Fennelly tom.fenne...@gmail.com wrote:

I spent a while trying to replace the forked HtmlUnit with HtmlUnit 2.17 (PR 
#1774). I've parked it for now. I was just running into one issue after another.
On 26 July 2015 at 11:25, nicolas de loof nicolas.del...@gmail.com wrote:

As long as such a hack is a way to quickly get a fix / feature while a pull 
request is waiting for approval I'm fine with that, but when this ends with 
svnkit-like maintenance hell I'm -1
Le dim. 26 juil. 2015 12:10, Kanstantsin Shautsou kanstantsin@gmail.com a 
écrit :

KK likes forking libraries to add some hacks, ask him.

On Wednesday, July 22, 2015 at 11:16:14 PM UTC+3, Tom Fennelly wrote:
Anyone have an idea? I'm hoping there was a really good reason, otherwise I 
think I might cry.
-- 
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/885ae71a-39e7-4c48-a78b-44acb5c970a7%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/CA%2BbPaoJYZZDayFo6Ynh84Gsed_Jr0q5FAjHJ%2BpGO7D8GuErLRw%40mail.gmail.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/CANMVJzmrY5jLiePK0hM%2BMQTqqKv6wNT%3DSTHDjM%3DYDd_Gc37%2B%3Dw%40mail.gmail.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

Re: Adding javascript to job status page

2015-07-23 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hi Annie
Comments below

Yes -- that would work! Do you know if there's a way that after each build, I 
can:

 1. run some javascript to generate the svg
You can have a build step, post build step, call another job, use the workflow 
plug-in, etc. The simplest would be to include a command that generates the SVG 
graph in your build, but there are many different ways to achieve the same 
result.

 2. store the svg in the same URL as the previous build 

If you archive your image as a build artifact. The URL won't change.

 3. the description is updated in reload (the svg url doesn't change)
http://162.243.246.75:8080/job/Examples/job/annie-jiao-001/
You can browse the configuration for that job for an example. Normally I use R 
to generate the graphs, but due to lack of time I decided to simply wget an 
image once and pretend I've generated it with some command :)
HTHBruno
 
  From: Annie Jiao anniej9...@gmail.com
 To: Jenkins Developers jenkinsci-dev@googlegroups.com 
Cc: brunodepau...@yahoo.com.br 
 Sent: Thursday, July 23, 2015 8:23 AM
 Subject: Re: Adding javascript to job status page
   
Hello!
Yes -- that would work! Do you know if there's a way that after each build, I 
can:
   
   - run some javascript to generate the svg
   - store the svg in the same URL as the previous build 
   - the description is updated in reload (the svg url doesn't change)
I currently don't know how to generate the svg and get it hosted after a build. 
Thanks!
Annie
On Tuesday, July 21, 2015 at 10:01:40 PM UTC-7, kinow wrote:
Hi Annie
Maybe in the job description? You can include HTML there, and try to add a link 
to an image archived in the latest successful build. Some times I use the Image 
Gallery Plug-in for doing something similar (displaying graphs generated with 
R), you may want to take a look if that's helpful too.
Hope that helps,Bruno

 
  From: Annie Jiao annie...@gmail.com
 To: Jenkins Developers jenkin...@googlegroups.com 
 Sent: Wednesday, July 22, 2015 9:00 AM
 Subject: Adding javascript to job status page
   
Hello!
I'm trying to use d3 to generate data visualization on the job status page 
(http://localhost:8080/jenkins/job/job-name/)
currently I'm using the active choices plugin and using a groovy script in the 
parameter I'm able to put the result on the build with parameters page 
(http://localhost:8080/jenkins/job/job-name/build?delay=0sec)
Is there a plugin I could use or somewhere in the config file where I can put 
the svg on the description page instead?
Thanks!-- 
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/f8b5c1d4-ff2a-4bd2-94ab-d349886c4a31%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/207025762.501033.1437639235840.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins UX

2015-07-22 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Thanks for all the hard work Gus. 

I can try building a Jenkins version with your pull requests, or if you have 
.war, I can try it with the active-choices-plugin, which relies on the DOM 
structure created in the build with parameters screen. CSS changes won't break 
the plug-in, but moving tables, divs, inputs, might break it.
CheersBruno

 
  From: Gus Reiber grei...@cloudbees.com
 To: Jenkins Developers jenkinsci-dev@googlegroups.com 
Cc: grei...@cloudbees.com 
 Sent: Thursday, July 23, 2015 10:31 AM
 Subject: Re: Jenkins UX
   
Awesome, awesome, awesome feedback all around.
So if I can summarize the feedback so far, it sounds to me like Kanstantsin is 
the most skeptical, but few if any of you are 100% sold, which is how it should 
be. Possible sources of discontent seem to break down like this:   
   - Don't forget about Tom's work and the existing SimpleTheme plugin 
   - Color, font, and border choices: Seems like maybe we like the simple black 
and white better, with less borders, less margins and smaller text (though that 
is not a consensus)
   - Collapse mechanism: The idea of clear segmentation seems to be generally 
embraced (Kanstantsin being the exception), but the sort of pegged ToC tracking 
that Bootstrap uses might be prefered. 
   - Console log should be better, too (I totally agree with that, but didn't 
choose that piece of the GUI as a starting point so am punting on thinking 
about that for the moment)
Most of my goal here is to show the sorts of tangible benefits that an overhaul 
of a GUI can bring that go beyond what can be done against the current Jenkins 
DOM with CSS alone. KK, Daniel, Tom and I agree that is the case enough to 
start organizing ourselves into both code and outreach to start making that 
case through forums and demos like this, and pull requests which we are 
starting to create.
As I see it, we will want to break down pull requests along this topic into 
manageable bites, the first of which being largely infrastructure and only 
minimal visual changes, if at all. It is my belief that the first step of doing 
any modernizing of the config page is to pull it out of tables and refactor 
hudson-behavior to function with a semantic and logically nested DOM structure, 
such that new styles of input elements can be folded into both core config 
items and plugin configuration without a lot of the crazy DOM wackery that 
happens today. Also, I think PrototypeJS and YUI are essentially dead 
technologies, so we will need to cast off those shackles.
...thus our first PR is likely to be all about enabling DOM changes to the 
jelly resources files in the form directory (even prior to the actual DOM 
changes).
Anyway, in the next few days, KK and Daniel will be looking to set up a hangout 
in which at least some of us might be able to get together and examine the ins 
and outs of this technical web.
...expect a seperate note from them with more specifics, shortly.





On Thursday, July 16, 2015 at 9:03:49 AM UTC-7, Gus Reiber wrote:
As threatened, but at long last, I have a demo video and associated blog 
post not really posted to a blog, but, still something that can be read and 
comment on
Please take a look, and send feedback:video:http://youtu.be/1Qn4jEwAeGc

post:https://docs.google.com/document/d/1sjd_Yl7wzyxVoaFurSGAVfgWNSwlnSLJztx7uexdgxE/edit?usp=sharing



On Monday, June 22, 2015 at 4:37:17 AM UTC-7, Gus Reiber wrote:
Hey all,
   Been a long time since my last post, as I had been cramming getting a 
prototype built for JUCs DC and London. I am happy to report Tom and my 
presentation was well received in DC. Now we are off to the UK.

Now that we have a simifunctional prototype, we will be working to figure out 
how to best post it so community members can provide feedback.

Thanks again for your interest. Please stay tuned.


-- 
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/a77c5054-7888-415c-9ae5-be73aa9e9af3%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/1535303428.364268.1437604671217.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Adding javascript to job status page

2015-07-21 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hi Annie
Maybe in the job description? You can include HTML there, and try to add a link
to an image archived in the latest successful build. Some times I use the Image
Gallery Plug-in for doing something similar (displaying graphs generated with
R), you may want to take a look if that's helpful too.
Hope that helps,Bruno

From: Annie Jiao anniej9...@gmail.com
To: Jenkins Developers jenkinsci-dev@googlegroups.com
Sent: Wednesday, July 22, 2015 9:00 AM
Subject: Adding javascript to job status page

Hello!
I'm trying to use d3 to generate data visualization on the job status page
(http://localhost:8080/jenkins/job/job-name/)
currently I'm using the active choices plugin and using a groovy script in the
parameter I'm able to put the result on the build with parameters page
(http://localhost:8080/jenkins/job/job-name/build?delay=0sec)
Is there a plugin I could use or somewhere in the config file where I can put
the svg on the description page instead?
Thanks!--
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/f8b5c1d4-ff2a-4bd2-94ab-d349886c4a31%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/1535308246.91361.1437541294430.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: embed svg created by d3 in plug-in

2015-07-11 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hi Annie
Maybe something like

```
def job = Jenkins.instance.getItem(job-name)
job.builds.each() {
  //println(it.timestamp)
  println(it.timeInMillis)
}
```

The timestamp returns a calendar, and the timeInMillis the long value.

I have Jenkins in my Eclipse workspace, and usually first take a look at 
github.com/jenkinsci/jenkins, but if
I cannot find what I'm after, I debug the call (e.g. from Api.java or 
Build.java) and look at the objects used, and how I could use them in Groovy.

Hope that helps,
Bruno

 
  From: Annie Jiao anniej9...@gmail.com
 To: jenkinsci-dev@googlegroups.com 
Cc: brunodepau...@yahoo.com.br 
 Sent: Saturday, July 11, 2015 9:39 AM
 Subject: Re: embed svg created by d3 in plug-in
   
Actually the output from 
http://localhost:8080/jenkins/job/job-name/api/json?tree=builds[timestamp] is 
exactly what I need. Is there a way to get this pragmatically in the groovy 
script?

On Thursday, July 9, 2015 at 6:24:06 PM UTC-7, Annie Jiao wrote:
Thanks a lot everyone! The scripts library is also very helpful. I'm now having 
trouble getting the timestamps of a build — for each project, I want to iterate 
through all the builds and get the timestamps. There's the method 
getTimeInMillis() that I would like to use, from the api 
(http://javadoc.jenkins-ci.org/hudson/model/Run.html), but I don't know how to 
access that when I'm iterating over Hudson.instance.items .

On Monday, July 6, 2015 at 5:36:52 PM UTC-7, kinow wrote:
I can try that later in a testing instance that we use to develop the plug-in, 
but if you haven't modified the script, the output is probably in the Jenkins 
logs (see [1] and [2]).
If you want to display that as parameters, the Active Choices plug-in expects 
your script to return an array of strings, being each string rendered as a 
parameter of the type selected (e.g. combo box, radio, input text, etc).
Hope that helpsBruno

[1] https://wiki.jenkins-ci.org/display/JENKINS/Logging
[2] https://wiki.jenkins-ci.org/display/JENKINS/Troubleshooting
 
  From: Annie Jiao annie...@gmail.com
 To: jenkin...@googlegroups.com 
Cc: brunod...@yahoo.com.br 
 Sent: Tuesday, July 7, 2015 12:12 PM
 Subject: Re: embed svg created by d3 in plug-in
   
https://scriptlerweb.appspot.com/script/show/426002
This looks great for what I'm trying to do. I added that as an active choice 
reactive reference parameter with the reference parameter field blank, and I 
do see the title when I click build with parameters, but nothing is printed 
to the HTML, the browser console, or the Logger Console. Where should i be 
looking for the output?
Thank you so much!

On Monday, July 6, 2015 at 3:37:23 PM UTC-7, kinow wrote:
If you are using Groovy, you can use Jenkins API to retrieve this kind of 
information. You can have a look at some of the Scriptler scripts 
https://scriptlerweb.appspot. com/catalog/list, and also check examples in the 
Groovy plug-in, StackOverflow and also check Jenkins' source code 
https://github.com/jenkinsci/ jenkins
HTHBruno

 
  From: Annie Jiao annie...@gmail.com
 To: jenkin...@googlegroups.com 
 Sent: Tuesday, July 7, 2015 9:41 AM
 Subject: Re: embed svg created by d3 in plug-in
   
This has been incredibly helpful! Thanks!
I see that it reads data from a csv file. Is there a way to populate it with 
data from the builds, instead of a preset file? (Suppose I want to plot % of 
builds that passed everyday for the past week).

On Wednesday, July 1, 2015 at 5:17:57 PM UTC-7, Ioannis Moutsatsos wrote:
No special plugin needed. You should be able to add some standard HTML 
(including an iframe) element to a project's description and it will be 
displayed when the job page is rendered. Take a look here where I've added an 
animated gif to demo how a build is executed.
Hope this helps to get you started.


On Wednesday, July 1, 2015 at 6:37:51 PM UTC-4, Annie Jiao wrote:
Yup, the svg will change to reflect data as new builds occur. (The navigation 
is secondary)
Do I need to install any plug-ins to use an iFrame?
Thanks a lot for your help!

On Wednesday, July 1, 2015 at 12:37:27 PM UTC-7, Ioannis Moutsatsos wrote:
So, will the SVG change as more builds are accumulated in the job history? It 
sounds like you want to use it for navigation purposes.You can include a 
graphic in your project description using HTML, even an iFrame.
It will then display on the http://localhost:8080/ jenkins/job/jobname/ page

On Wednesday, July 1, 2015 at 2:25:24 PM UTC-4, Annie Jiao wrote:
this'll be on the job level -- as in
http://localhost:8080/jenkins/ job/jobname/

On Wednesday, July 1, 2015 at 7:09:25 AM UTC-7, Ioannis Moutsatsos wrote:
I'm confused from the description of what you are trying to do.Where is this 
SVG graphic going to be displayed?   
   - Job level (ie is this going to be on the build UI) or
   - Build report level (ie part of the results after a build)
Depending on one of this options we can suggest some options.
On Tuesday, June 30, 2015 at 5:34:16 PM UTC-4, Annie

Re: embed svg created by d3 in plug-in

2015-07-06 Thread 'Bruno P. Kinoshita' via Jenkins Developers

If you are using Groovy, you can use Jenkins API to retrieve this kind of
information. You can have a look at some of the Scriptler scripts
https://scriptlerweb.appspot.com/catalog/list, and also check examples in the
Groovy plug-in, StackOverflow and also check Jenkins' source code
https://github.com/jenkinsci/jenkins
HTHBruno

From: Annie Jiao anniej9...@gmail.com
To: jenkinsci-dev@googlegroups.com
Sent: Tuesday, July 7, 2015 9:41 AM
Subject: Re: embed svg created by d3 in plug-in

This has been incredibly helpful! Thanks!
I see that it reads data from a csv file. Is there a way to populate it with
data from the builds, instead of a preset file? (Suppose I want to plot % of
builds that passed everyday for the past week).

On Wednesday, July 1, 2015 at 5:17:57 PM UTC-7, Ioannis Moutsatsos wrote:
No special plugin needed. You should be able to add some standard HTML
(including an iframe) element to a project's description and it will be
displayed when the job page is rendered. Take a look here where I've added an
animated gif to demo how a build is executed.
Hope this helps to get you started.

On Wednesday, July 1, 2015 at 6:37:51 PM UTC-4, Annie Jiao wrote:
Yup, the svg will change to reflect data as new builds occur. (The navigation
is secondary)
Do I need to install any plug-ins to use an iFrame?
Thanks a lot for your help!

On Wednesday, July 1, 2015 at 12:37:27 PM UTC-7, Ioannis Moutsatsos wrote:
So, will the SVG change as more builds are accumulated in the job history? It
sounds like you want to use it for navigation purposes.You can include a
graphic in your project description using HTML, even an iFrame.
It will then display on the http://localhost:8080/ jenkins/job/jobname/ page

On Wednesday, July 1, 2015 at 2:25:24 PM UTC-4, Annie Jiao wrote:
this'll be on the job level -- as in
http://localhost:8080/jenkins/ job/jobname/

On Wednesday, July 1, 2015 at 7:09:25 AM UTC-7, Ioannis Moutsatsos wrote:
I'm confused from the description of what you are trying to do.Where is this
SVG graphic going to be displayed?
- Job level (ie is this going to be on the build UI) or
- Build report level (ie part of the results after a build)
Depending on one of this options we can suggest some options.
On Tuesday, June 30, 2015 at 5:34:16 PM UTC-4, Annie Jiao wrote:
is it possible to create an svg graphic (non-interactive) using D3 and
embedding the result in a jenkins plug-in?
I do plan on making different parts of the svg clickable and link to other
pages further down the road.
Thanks!

--
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/19aa8409-edfd-4121-9674-579e4052bf2b%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/992039547.8012.143638539.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: embed svg created by d3 in plug-in

2015-07-06 Thread 'Bruno P. Kinoshita' via Jenkins Developers

I can try that later in a testing instance that we use to develop the plug-in, 
but if you haven't modified the script, the output is probably in the Jenkins 
logs (see [1] and [2]).
If you want to display that as parameters, the Active Choices plug-in expects 
your script to return an array of strings, being each string rendered as a 
parameter of the type selected (e.g. combo box, radio, input text, etc).
Hope that helpsBruno

[1] https://wiki.jenkins-ci.org/display/JENKINS/Logging
[2] https://wiki.jenkins-ci.org/display/JENKINS/Troubleshooting
 
  From: Annie Jiao anniej9...@gmail.com
 To: jenkinsci-dev@googlegroups.com 
Cc: brunodepau...@yahoo.com.br 
 Sent: Tuesday, July 7, 2015 12:12 PM
 Subject: Re: embed svg created by d3 in plug-in
   
https://scriptlerweb.appspot.com/script/show/426002
This looks great for what I'm trying to do. I added that as an active choice 
reactive reference parameter with the reference parameter field blank, and I 
do see the title when I click build with parameters, but nothing is printed 
to the HTML, the browser console, or the Logger Console. Where should i be 
looking for the output?
Thank you so much!

On Monday, July 6, 2015 at 3:37:23 PM UTC-7, kinow wrote:
If you are using Groovy, you can use Jenkins API to retrieve this kind of 
information. You can have a look at some of the Scriptler scripts 
https://scriptlerweb.appspot. com/catalog/list, and also check examples in the 
Groovy plug-in, StackOverflow and also check Jenkins' source code 
https://github.com/jenkinsci/ jenkins
HTHBruno

 
  From: Annie Jiao annie...@gmail.com
 To: jenkin...@googlegroups.com 
 Sent: Tuesday, July 7, 2015 9:41 AM
 Subject: Re: embed svg created by d3 in plug-in
   
This has been incredibly helpful! Thanks!
I see that it reads data from a csv file. Is there a way to populate it with 
data from the builds, instead of a preset file? (Suppose I want to plot % of 
builds that passed everyday for the past week).

On Wednesday, July 1, 2015 at 5:17:57 PM UTC-7, Ioannis Moutsatsos wrote:
No special plugin needed. You should be able to add some standard HTML 
(including an iframe) element to a project's description and it will be 
displayed when the job page is rendered. Take a look here where I've added an 
animated gif to demo how a build is executed.
Hope this helps to get you started.


On Wednesday, July 1, 2015 at 6:37:51 PM UTC-4, Annie Jiao wrote:
Yup, the svg will change to reflect data as new builds occur. (The navigation 
is secondary)
Do I need to install any plug-ins to use an iFrame?
Thanks a lot for your help!

On Wednesday, July 1, 2015 at 12:37:27 PM UTC-7, Ioannis Moutsatsos wrote:
So, will the SVG change as more builds are accumulated in the job history? It 
sounds like you want to use it for navigation purposes.You can include a 
graphic in your project description using HTML, even an iFrame.
It will then display on the http://localhost:8080/ jenkins/job/jobname/ page

On Wednesday, July 1, 2015 at 2:25:24 PM UTC-4, Annie Jiao wrote:
this'll be on the job level -- as in
http://localhost:8080/jenkins/ job/jobname/

On Wednesday, July 1, 2015 at 7:09:25 AM UTC-7, Ioannis Moutsatsos wrote:
I'm confused from the description of what you are trying to do.Where is this 
SVG graphic going to be displayed?   
   - Job level (ie is this going to be on the build UI) or
   - Build report level (ie part of the results after a build)
Depending on one of this options we can suggest some options.
On Tuesday, June 30, 2015 at 5:34:16 PM UTC-4, Annie Jiao wrote:
is it possible to create an svg graphic (non-interactive) using D3 and 
embedding the result in a jenkins plug-in?
I do plan on making different parts of the svg clickable and link to other 
pages further down the road.
Thanks!





-- 
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/19aa8409- edfd-4121-9674-579e4052bf2b% 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/25f68918-4702-418b-b03d-83a4ff387638%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

Re: Captcha on wiki

2015-07-02 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Oups, my bad. Thanks for fixing it Daniel!
Will use only the wiki markup editor instead of the wysiwyg from now on :)
CheersBruno

From: Daniel Beck m...@beckweb.net
To: jenkinsci-dev@googlegroups.com
Sent: Thursday, July 2, 2015 9:21 PM
Subject: Re: Captcha on wiki

This apparently was caused by the (WYSIWYG?) editor duplicating some page
content such that there was a single 600k character line in the wiki text. This
is how it started:

https://wiki.jenkins-ci.org/pages/diffpages.action?originalId=75891705pageId=78676521

Resolved by reverting to a version older than the border=1 duplication to get
rid of all the crap…

https://wiki.jenkins-ci.org/pages/diffpages.action?originalId=80642385pageId=80642387

…and inserting the previously manually saved current page contents without the
duplication.

https://wiki.jenkins-ci.org/pages/diffpages.action?pageId=74875908originalId=80642389

So everything should work again now.

Try not using the WYSIWYG editor, or at least ensure there are no accidental
changes in there by diffing with the previous version after you save.

On 02.07.2015, at 10:31, Daniel Beck m...@beckweb.net wrote:

On 02.07.2015, at 03:27, Ioannis Moutsatsos imoutsat...@gmail.com wrote:

Excellent points! The wiki has been SO FRUSTRATING!
I'm still unable to edit my Active Choices wiki page. Can't pass the captcha
and I'm sure I'm entering it correctly! WHO can help us resolve this?
Thank you for any feedback!

Unrelated to the captcha. I disabled it and still can't get past the form.
I'm trying to find out what's going on there.

--
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/778D4951-B2D8-4489-B64C-681D1DE15BCE%40beckweb.net.
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/6FEEC425-DAA6-4DB1-895A-6A8EFE2EFA25%40beckweb.net.

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/63128324.465269.1435829842618.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Captcha on wiki

2015-05-27 Thread 'Bruno P. Kinoshita' via Jenkins Developers

I have had similar problem in the past while editing the Testopia Plug-in Wiki
too. I was basically locked, and could not edit the page, it simply always
failed, even though I tried to slowly type the captcha.
So I tried rolling-back the Wiki to a previous version, and after that suddenly
I was able to edit and save it again with no problems.
Just my 0.02 cents
Bruno

From: Jesse Glick jgl...@cloudbees.com
To: Jenkins Dev jenkinsci-dev@googlegroups.com
Sent: Thursday, May 28, 2015 10:18 AM
Subject: Re: Captcha on wiki

On Fri, May 22, 2015 at 6:19 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
Am I the only one who has to keep trying to guess the really bad captcha 50
times just to save a page?

You are not the only one. Possibly relevant:
https://issues.jenkins-ci.org/browse/INFRA-300

--
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/CANfRfr1KY1DVYJyyE7TRBSxd9K7Koe%2BaUHOKhOOVR80JOPbgoQ%40mail.gmail.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/263143800.359863.1432765665000.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Out of disk space error on system partition: Can temp location for file parameter upload be changed?

2015-05-02 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hi Ioannis,

Is it possible to redirect the temporary file parameter uploads to this
partition instead of the C system partition?

The upload request is handled by Stapler, which uses Apache Commons FileUpload
for the part you have mentioned. For short files (under 10Kb default threshold)
you may not see the file being copied to the temporary directory at all. Files
larger than this threshold, and under the upload limit, are copied to the
temporary directory [1] during the upload.

Stapler creates a DiskFileItemFactory using the default constructor, without
specifying a repository (temp dir) [2]. In this case, Apache Commons FileUpload
defaults to using the system temporary directory (via java.io.tmpdir).

You can change the java.io.tmpdir to point to somewhere else - though I'm not
sure if that wouldn't break something else (I assume it wouldn't, but you
probably want to experiment with it first in testing box).
This PR [4] worked locally, but hopefully others will comment with other
suggestions here or in GitHub.

Hope that helps
Bruno

[1] https://commons.apache.org/proper/commons-fileupload/using.html
[2]
https://github.com/stapler/stapler/blob/b0b0b96e8561914a824517784dfda3f420b42549/core/src/main/java/org/kohsuke/stapler/RequestImpl.java#L865
[3]
https://github.com/apache/commons-fileupload/blob/a6ab65198a8f5c31044d6352dacbc3495c861943/src/main/java/org/apache/commons/fileupload/disk/DiskFileItem.java#L544
[4] https://github.com/stapler/stapler/pull/49

From: Ioannis Moutsatsos imoutsat...@gmail.com
To: jenkinsci-dev@googlegroups.com
Sent: Friday, May 1, 2015 6:44 AM
Subject: Out of disk space error on system partition: Can temp location for
file parameter upload be changed?

I discovered that on a Windows Jenkins server (Windows 2008 R2 Server) when a
'file parameter uploads a file to the server it uses the
C:\Users\userName\AppData\Local\Temp folder to keep a temporary copy of the
file.
In addition, these temporary files are not cleaned with any frequency.
As a result, I have run out of disk space trying to upload large files to the
server.
However, the same server has a very large D partition. Is it possible to
redirect the temporary file parameter uploads to this partition instead of
the C system partition?
Thanks for any feedback!Ioannis--
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/45f995a1-a5e4-458c-ac90-a95c8de47ad1%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/1612514023.107324.1430580712752.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Chat Room Plugin

2015-04-27 Thread 'Bruno P. Kinoshita' via Jenkins Developers

What if the IRC bot, after forking the repo under the jenkinsci organization,
also scheduled the creation of a default Wiki page? We could create a default
template, with just that Confluence macro that brings the plug-in details
(Jira, GitHub repo, name, maintainer/assigner, etc).

IIRC, the plug-in name and JIRA component have been standarised some time ago,
so it shouldn't be too complicate to get the Wiki page name for the new plug-in.

WDYT?

Bruno

From: Baptiste Mathus bmat...@batmat.net
To: jenkinsci-dev@googlegroups.com
Sent: Monday, April 27, 2015 7:56 PM
Subject: Re: Jenkins Chat Room Plugin

+1. Some plugins don't even have a README in the repo itself... Might be just
me, but lately, when I click onto the links from the jenkins_releases tweets,
the wiki page is rarely found :-(.

IMO, this policy should be reconsidered since the pain is for Jenkins users
(finding what the plugin is doing, and so on).
2015-04-27 9:47 GMT+02:00 Daniel Beck m...@beckweb.net:

I've been saying for a while that we should just remove all plugins from the UC
that don't have a wiki link and source repo in jenkinsci
(Github)/svn.jenkins-ci.org.

Unfortunately we decided to try the gentle 'dear plugin author, please do this'
approach first and I've yet to write the wiki page for it.

On 27.04.2015, at 08:11, domi d...@fortysix.ch wrote:

does anyone know what the “Jenkins Chat Room Plugin” is?
There was a release announced (see tweet below), but the link to the wiki is
wrong (again one of these plugins!) and i can’t find a repository for it
either…
/Domi

Begin forwarded message:

From: domi d...@fortysix.ch
Subject: Tweet von Jenkins releases auf Twitter
Date: 26 Apr 2015 08:38:49 GMT+2
To: Dominik Bartholdi d...@fortysix.ch

Jenkins releases (@jenkins_release)
26.04.15 07:01
Jenkins Chat Room Plugin 1.0 (new) dlvr.it/9YBNXz #jenkinsci

Die Twitter App downloaden

--
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/13107427-759D-436A-8A21-33A593380632%40fortysix.ch.
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/4BE09115-041B-4AD2-BEC2-3962F2A3C8C5%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

--
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !--
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/CANWgJS5H3xu9MENFHuupN6zN3T0hDW8ij_KyZAEPzTP43Yvv4Q%40mail.gmail.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/458850033.2428029.1430123620064.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Release Active Choices Plug-in (was: Re: New plug-in: Uno Choice Plug-in for dynamic parameters)

2015-04-22 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Thanks Kanstantsin!
If there are no objections maybe someone with karma could clone it, and then I 
would fix the plug-in name in the code before the 1.0 release :)
Bruno

  From: Kanstantsin Shautsou kanstantsin@gmail.com
 To: jenkinsci-dev@googlegroups.com 
 Sent: Wednesday, April 22, 2015 3:10 AM
 Subject: Re: Release Active Choices Plug-in (was: Re: New plug-in: Uno Choice 
Plug-in for dynamic parameters)

imho sounds ok. But not very like “Re-active” for other plugin names.

On Apr 21, 2015, at 16:03, 'Bruno P. Kinoshita' via Jenkins Developers 
jenkinsci-dev@googlegroups.com wrote:
Bump again :)
What about renaming the plug-in at the repository
https://github.com/biouno/uno-choice-plugin
To Active Choices Plug-in as Ioannis suggested?
The plug-in provides parameter types that can be updated based on other 
parameter values in the UI. We have already some users downloading the plug-in 
either manually or from our update center, but we really would like to make it 
available to all users.
Thank you!Bruno

  From: 'Bruno P. Kinoshita' via Jenkins Developers 
jenkinsci-dev@googlegroups.com
 To: jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com 
Cc: m...@beckweb.net m...@beckweb.net 
 Sent: Wednesday, April 1, 2015 11:20 AM
 Subject: Re: New plug-in: Uno Choice Plug-in for dynamic parameters

Maybe i already suggested not to use Jenkins word, just XXX plugin
Agreed, we can drop the Jenkins prefix.
Re-active prefix is not obvious for me...
Would you have other suggestions? Unfortunately I'm horrible choosing names :)
ThanksBruno

  From: Kanstantsin Shautsou kanstantsin@gmail.com
 To: jenkinsci-dev@googlegroups.com 
Cc: m...@beckweb.net; brunodepau...@yahoo.com.br 
 Sent: Tuesday, March 31, 2015 6:01 PM
 Subject: Re: New plug-in: Uno Choice Plug-in for dynamic parameters

Maybe i already suggested not to use Jenkins word, just XXX plugin

Re-active prefix is not obvious for me...
On Monday, March 30, 2015 at 11:09:26 PM UTC+3, kinow wrote:
Bump anyone?

+1 / -1 for Jenkins Active Choices Plug-in? Any other suggestion?

CheersBruno

  From: Ioannis Moutsatsos imout...@gmail.com
 To: jenkin...@googlegroups.com 
Cc: m...@beckweb.net 
 Sent: Friday, February 27, 2015 11:47 AM
 Subject: Re: New plug-in: Uno Choice Plug-in for dynamic parameters

What do you all think about  naming the plugin 'Active Choices Plugin' . The 
plugin would then add 3 new parameter types:   
   - Active Choices [aka Uno-Choice Dynamic Choice]   

   - Re-Active Choices [aka Uno-Choice Cascade Dynamic]   

   - Re-Active References [aka Uno-Choice Dynamic Reference]
The 'Re-active' prefix perhaps would fit well with the main function of these 
parameter which is to actively react to changes in other submission form UI 
parameters.
On Thursday, February 19, 2015 at 1:59:19 AM UTC-5, Daniel Beck wrote:

On 18.02.2015, at 22:01, Jesse Glick jgl...@cloudbees.com wrote:

 I would pick a plugin named “Dynamic Parameter”
 and skip right over “Uno Choice”.

There is already 'Dynamic Extended Choice' and 'Dynamic Parameter'. At least 
with the 'Uno' it has a less generic name and you're not going to confuse it 
with another plugin all the time.

-- 
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/4936cd59- 9505-420d-b37c-1e59e1206357% 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/b2218c24-4487-447d-b7d9-54623732109f%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/1906857759.1148400.1427840444347.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to a topic in the Google 
Groups Jenkins Developers group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/jenkinsci-dev/qUBLhE-4ybY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid

Release Active Choices Plug-in (was: Re: New plug-in: Uno Choice Plug-in for dynamic parameters)

2015-04-21 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Bump again :)
What about renaming the plug-in at the repository
https://github.com/biouno/uno-choice-plugin
To Active Choices Plug-in as Ioannis suggested?
The plug-in provides parameter types that can be updated based on other 
parameter values in the UI. We have already some users downloading the plug-in 
either manually or from our update center, but we really would like to make it 
available to all users.
Thank you!Bruno

 
  From: 'Bruno P. Kinoshita' via Jenkins Developers 
jenkinsci-dev@googlegroups.com
 To: jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com 
Cc: m...@beckweb.net m...@beckweb.net 
 Sent: Wednesday, April 1, 2015 11:20 AM
 Subject: Re: New plug-in: Uno Choice Plug-in for dynamic parameters
   
Maybe i already suggested not to use Jenkins word, just XXX plugin
Agreed, we can drop the Jenkins prefix.
Re-active prefix is not obvious for me...
Would you have other suggestions? Unfortunately I'm horrible choosing names :)
ThanksBruno


 
  From: Kanstantsin Shautsou kanstantsin@gmail.com
 To: jenkinsci-dev@googlegroups.com 
Cc: m...@beckweb.net; brunodepau...@yahoo.com.br 
 Sent: Tuesday, March 31, 2015 6:01 PM
 Subject: Re: New plug-in: Uno Choice Plug-in for dynamic parameters
   
Maybe i already suggested not to use Jenkins word, just XXX plugin

Re-active prefix is not obvious for me...
On Monday, March 30, 2015 at 11:09:26 PM UTC+3, kinow wrote:
Bump anyone?

+1 / -1 for Jenkins Active Choices Plug-in? Any other suggestion?

CheersBruno
 

  From: Ioannis Moutsatsos imout...@gmail.com
 To: jenkin...@googlegroups.com 
Cc: m...@beckweb.net 
 Sent: Friday, February 27, 2015 11:47 AM
 Subject: Re: New plug-in: Uno Choice Plug-in for dynamic parameters
   
What do you all think about  naming the plugin 'Active Choices Plugin' . The 
plugin would then add 3 new parameter types:   
   - Active Choices [aka Uno-Choice Dynamic Choice]   

   - Re-Active Choices [aka Uno-Choice Cascade Dynamic]   

   - Re-Active References [aka Uno-Choice Dynamic Reference]
The 'Re-active' prefix perhaps would fit well with the main function of these 
parameter which is to actively react to changes in other submission form UI 
parameters.
On Thursday, February 19, 2015 at 1:59:19 AM UTC-5, Daniel Beck wrote:

On 18.02.2015, at 22:01, Jesse Glick jgl...@cloudbees.com wrote:

 I would pick a plugin named “Dynamic Parameter”
 and skip right over “Uno Choice”.

There is already 'Dynamic Extended Choice' and 'Dynamic Parameter'. At least 
with the 'Uno' it has a less generic name and you're not going to confuse it 
with another plugin all the time.



-- 
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/4936cd59- 9505-420d-b37c-1e59e1206357% 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/b2218c24-4487-447d-b7d9-54623732109f%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/1906857759.1148400.1427840444347.JavaMail.yahoo%40mail.yahoo.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/1188114509.559863.1429621432095.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Reorganizing the mailing lists web page

2015-04-03 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Much better!

Thanks Daniel
Bruno

-
Em sex, 3 de abr de 2015 10:39 BRT Daniel Beck escreveu:

I hope that most new users who post here instead of the users list are just
confused about the purpose of the respective lists (I'm a developer, so I'll
ask my question on the dev list) ...

So I changed the list of mailing lists on jenkins-ci.org:

http://jenkins-ci.org/content/mailing-lists

Major changes:
* Users list is now mentioned first
* Some lists (especially the dev list) now have longer and/or hopefully
clearer explanations
* It now links to to smart-questions because there can never be enough
references to it
* Separated sections for English and non-English lists to make the entire web
page easier to parse

Old appearance for reference:
https://web.archive.org/web/20150314230033/http://jenkins-ci.org/content/mailing-lists

Please respond if you want me to change anything/revert everything.

--
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/AC0112A7-345B-4A43-862A-E2678FF0A0E0%40beckweb.net.
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/1428076344.86559.BPMail_high_carrier%40web163503.mail.gq1.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin hosting request: plugin for LSF

2015-03-31 Thread 'Bruno P. Kinoshita' via Jenkins Developers

I'm doing something similar in the PBS Plug-in too [1]. There is an item in our
backlog to create a common batch plug-in, that would support PBS, LSF, SunGrid,
etc.
Maybe using DRMAA v2, or creating/extending an API for that could be useful not
only for the plug-in, but also for other tools (e.g. Galaxy).

From: Jay doktor.noetigenfa...@gmail.com
To: jenkinsci-dev@googlegroups.com
Sent: Tuesday, March 31, 2015 9:27 AM
Subject: Re: Plugin hosting request: plugin for LSF

Hi,
exciting!I'm also using Jenkins and let build jobs run on LSF nodes.But i'm
using a different approach: i've managed to create slave nodes which are turned
on when needed and for this i submit a jenkins slave.jar to LSF.But the direct
way isn't working, so i have written a script which submits a dummy job and
then does a passwordless ssh login to the node the job was scheduled on. On
this node i start a jenkins slave.jar.But it would be much cleaner if i had a
plugin doing this and there would be no need for ssh login, but directly submit
slave.jar
Jay

Am Montag, 30. März 2015 11:25:00 UTC+2 schrieb Laisvydas Skurevičius:
Hello,
I have created a plugin which lets you submit batch jobs to LSF batch system
and I would like to host it in the official jenkins repository.I am giving you
the required info:
GitHub plugin name: lsf-cloudGitHub ID: LaisvydasLTGitHub repository:
https://github.com/ LaisvydasLT/lsf-cloud
Sincerely,Laisvydas Skurevicius
--
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/ddd03b08-eaa7-4376-b0da-4d797170b306%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/1669237154.918616.1427809161980.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin hosting request: plugin for LSF

2015-03-31 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Missing [1] link https://github.com/biouno/pbs-plugin
CheersBruno

From: Bruno P. Kinoshita brunodepau...@yahoo.com.br
To: jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com
Sent: Tuesday, March 31, 2015 10:39 AM
Subject: Re: Plugin hosting request: plugin for LSF

From: Jay doktor.noetigenfa...@gmail.com
To: jenkinsci-dev@googlegroups.com
Sent: Tuesday, March 31, 2015 9:27 AM
Subject: Re: Plugin hosting request: plugin for LSF

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/1009101254.936701.1427809224480.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Grouping jobs by project, status, or attributes other than folder location

2015-03-31 Thread 'Bruno P. Kinoshita' via Jenkins Developers

 As I see it, there are three types of settings/metadata I would want to 
 track

Agreed on the three of them. I didn't have a clear picture of this three types, 
but I will try to shamelessly use what you suggested to group metadata 
collectors :)

The Taverna Workflow [1] (which code was recently donated to ASF for the 
incubation), does a great job supporting metadata. It has a plug-in for data 
provenance [2], which allows researchers to track workflows and artifacts being 
generated by these workflows. The plug-in utilizes the PROV ontology [3]. I 
think it covers some of the types of settings/metadata that you mentioned.

By extending the Metadata Plug-in to use the same ontology and support 
metadata, a Jenkins workflow (maybe created with the new Workflow Plug-in) 
could be uploaded to the myexperiment [4] too :-) 

This way we would be able to share workflows, re-run existing workflows, and 
(hopefully) make it easier to reproduce workflows. At least that's what I'm 
planning to investigate once I've relocated. Or **maybe**, we could even re-run 
a simple workflow created in Jenkins in Taverna, as long as there was some kind 
of compatibility between plug-ins.

 Have you used our new CloudBees Analytics plugins at all?
Wasn't aware of it. Could you send a link to some docs or presentation about 
it, please? Tried searching for it but I couldn't find a link.

CheersBruno

[1] http://www.taverna.org.uk/[2] 
http://www.taverna.org.uk/documentation/taverna-2-x/provenance/
[3] http://www.w3.org/TR/prov-overview/[4] http://www.myexperiment.org/home
 
  From: Gus Reiber grei...@cloudbees.com
 To: jenkinsci-dev@googlegroups.com 
 Sent: Tuesday, March 31, 2015 2:41 PM
 Subject: Re: Grouping jobs by project, status, or attributes other than folder 
location
   
Hey Bruno,   Yeah, the SQL style syntax is exactly the sort of thing I am 
wishing I could apply to Job properties and other entities within Jenkins as 
well.Since we need Folders for RBAC anyway, Folders end up being our single and 
dominant form of metadata and we use them to define product based job groups. 
That works okay, but in particular, its a poor mechanism for fetching the list 
of all products that went to production this past Thursday, which on the 
surface of it, would be a perfectly normal question to ask a build manager.
As I see it, there are three types of settings/metadata I would want to 
track   
   - Config settings established prior to a job run: what repositories, what 
security context, what Docker image, which type of build-step constructors are 
being used, what slave pool should be used, what test environments should be 
used, who gets notified, etc   

   - Settings that are purely metadata: what project name do I want to apply to 
these groups of Jenkins items, what are the sorts of stage/environment names I 
want to use across projects to track comparative progress between projects...
   - Results determined by the job execution: What artifacts were made, what 
compute units actually did the build, how long did it take, did it succeed, 
where did the artifacts go...
For the Config settings, it seems helpful to me that these setting be robustly 
accessible prior to the job running, as one of the key things one might want to 
examine is how the planned process ends up comparing to the factual results. 
These being computers, of course they will do what you tell them, but you might 
have open pieces in your job-chain that someone else can edit, or your rules 
may be so abstract and complicated comparing the expected to the actual is 
often a very useful visualization.
For the purely metadata, I would hope that they would be minimal, as it is 
often difficult to know in advance the ways you will want to sort and group 
your information later.
And for the results set, it really feels to me that the Jenkins Job centered 
approach might not be right here. It might be better to look first at the 
artifacts, which are obviously related to the job, but are the product of it, 
and thus slightly different.
Have you used our new CloudBees Analytics plugins at all?They are meant to do 
some of this results and post-process settings sorting.
Thanks Bruno,Always a pleasure.
Gus 


On Mon, Mar 30, 2015 at 12:48 PM, 'Bruno P. Kinoshita' via Jenkins Developers 
jenkinsci-dev@googlegroups.com wrote:



Hey Gus
 -- Does anyone else attempt to make queries against Jenkins of this sort?

For scientists and researchers it's extremely important to be able to store, 
retrieve and search metadata. We have an idea of how to extend the metadata 
plug-in [1] (probably via several Pull Requests), so that it provides the 
following features:   
   - Automatically collect metadata of Jenkins items (jobs, builds, artifacts, 
etc)
   - Let users collect extra metadata with builders/publishers/etc. For 
instance, Cell Profiler [2] has a metadata module that can collect metadata 
from file names. So a file named TRIAGE-CP001-20151120035003

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

2015-03-31 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Maybe i already suggested not to use Jenkins word, just XXX plugin
Agreed, we can drop the Jenkins prefix.
Re-active prefix is not obvious for me...
Would you have other suggestions? Unfortunately I'm horrible choosing names :)
ThanksBruno


 
  From: Kanstantsin Shautsou kanstantsin@gmail.com
 To: jenkinsci-dev@googlegroups.com 
Cc: m...@beckweb.net; brunodepau...@yahoo.com.br 
 Sent: Tuesday, March 31, 2015 6:01 PM
 Subject: Re: New plug-in: Uno Choice Plug-in for dynamic parameters
   
Maybe i already suggested not to use Jenkins word, just XXX plugin

Re-active prefix is not obvious for me...
On Monday, March 30, 2015 at 11:09:26 PM UTC+3, kinow wrote:
Bump anyone?

+1 / -1 for Jenkins Active Choices Plug-in? Any other suggestion?

CheersBruno
 

  From: Ioannis Moutsatsos imout...@gmail.com
 To: jenkin...@googlegroups.com 
Cc: m...@beckweb.net 
 Sent: Friday, February 27, 2015 11:47 AM
 Subject: Re: New plug-in: Uno Choice Plug-in for dynamic parameters
   
What do you all think about  naming the plugin 'Active Choices Plugin' . The 
plugin would then add 3 new parameter types:   
   - Active Choices [aka Uno-Choice Dynamic Choice]   

   - Re-Active Choices [aka Uno-Choice Cascade Dynamic]   

   - Re-Active References [aka Uno-Choice Dynamic Reference]
The 'Re-active' prefix perhaps would fit well with the main function of these 
parameter which is to actively react to changes in other submission form UI 
parameters.
On Thursday, February 19, 2015 at 1:59:19 AM UTC-5, Daniel Beck wrote:

On 18.02.2015, at 22:01, Jesse Glick jgl...@cloudbees.com wrote:

 I would pick a plugin named “Dynamic Parameter”
 and skip right over “Uno Choice”.

There is already 'Dynamic Extended Choice' and 'Dynamic Parameter'. At least 
with the 'Uno' it has a less generic name and you're not going to confuse it 
with another plugin all the time.



-- 
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/4936cd59- 9505-420d-b37c-1e59e1206357% 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/b2218c24-4487-447d-b7d9-54623732109f%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/1906857759.1148400.1427840444347.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

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

2015-03-30 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Bump anyone?

+1 / -1 for Jenkins Active Choices Plug-in? Any other suggestion?

CheersBruno
 

  From: Ioannis Moutsatsos imoutsat...@gmail.com
 To: jenkinsci-dev@googlegroups.com 
Cc: m...@beckweb.net 
 Sent: Friday, February 27, 2015 11:47 AM
 Subject: Re: New plug-in: Uno Choice Plug-in for dynamic parameters
   
What do you all think about  naming the plugin 'Active Choices Plugin' . The 
plugin would then add 3 new parameter types:   
   - Active Choices [aka Uno-Choice Dynamic Choice]   

   - Re-Active Choices [aka Uno-Choice Cascade Dynamic]   

   - Re-Active References [aka Uno-Choice Dynamic Reference]
The 'Re-active' prefix perhaps would fit well with the main function of these 
parameter which is to actively react to changes in other submission form UI 
parameters.
On Thursday, February 19, 2015 at 1:59:19 AM UTC-5, Daniel Beck wrote:

On 18.02.2015, at 22:01, Jesse Glick jgl...@cloudbees.com wrote:

 I would pick a plugin named “Dynamic Parameter”
 and skip right over “Uno Choice”.

There is already 'Dynamic Extended Choice' and 'Dynamic Parameter'. At least 
with the 'Uno' it has a less generic name and you're not going to confuse it 
with another plugin all the time.



-- 
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/4936cd59-9505-420d-b37c-1e59e1206357%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/8473919.693922.1427745974297.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Grouping jobs by project, status, or attributes other than folder location

2015-03-30 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hey Gus
 -- Does anyone else attempt to make queries against Jenkins of this sort?

For scientists and researchers it's extremely important to be able to store, 
retrieve and search metadata. We have an idea of how to extend the metadata 
plug-in [1] (probably via several Pull Requests), so that it provides the 
following features:   
   - Automatically collect metadata of Jenkins items (jobs, builds, artifacts, 
etc)
   - Let users collect extra metadata with builders/publishers/etc. For 
instance, Cell Profiler [2] has a metadata module that can collect metadata 
from file names. So a file named TRIAGE-CP001-20151120035003.txt could generate 
metadata such as {code: CP001, date:2015-11-20 03:50:03UTC} if the user 
selected a File Name Metadata Collector   

   - Store the metadata in an embedded triple store (Jena) using an ontology 
created for Jenkins, which will import other ontologies such as DC, W3C Prov, 
etc.   

   - A search module and interface, that supports both Lucene (via jena-text 
module) and SPARQL.

The idea behind it is to have a pre defined ontology, which will ease learning 
about the data model used for the metadata, and transform Jenkins into a SPARQL 
endpoint. That way you'll be able to even query remote Jenkins for metadata too.
We have had some discussions about it already, but I will try to have a working 
version in the following months. As an example, this question Show me all the 
jobs that use this set of slaves could be answered by a SPARQL query similar 
to this one (syntax not tested, just a quick example):
PREFIX jenkins: http://
SELECT ?jobs 
WHERE {?jobs a jenkins:Job .?jobs jenkins:hasSlave ?slave .?slave 
jenkins:slaveName ?slaveName .?slaveName IN ('...')
}
 -- Has anyone used the Metadata plugin, or some other plugin or home-grown 
 solution to solve this issue?
I used it and had a look at the code, and I feel like I can extend it to 
support the ontology and SPARQL. @Ioannis used it too, maybe he can give his 
feedback on it too.
This is something that is necessary for experiments and scientific pipelines. 
It would be interesting if we could in some way join forces to work on it :-)

Cheers

[1] https://groups.google.com/forum/#!topic/biouno-developers/2u1dQ0uX5RM[2] 
http://www.cellprofiler.org/CPmanual/Metadata.html
 

  From: Gus Reiber grei...@cloudbees.com
 To: jenkinsci-dev@googlegroups.com 
 Sent: Monday, March 30, 2015 1:29 PM
 Subject: Grouping jobs by project, status, or attributes other than folder 
location
   
Hey all,   I currently using the folder plugin to group my projects together, 
but am finding that it is difficult to get cross-cutting job 
status/stage/attribute views of the jobs contained within those folders. Here 
are a set of examples of the sorts of queries I would like to be able to 
generate views based upon:   
   - Show me all the jobs related to a particular project (for me, this is 
typically the folder)
   - Show me all the jobs that deploy to production (many folders might have 
a job that does this)   

   - Show me all the jobs that use this set of slaves
   - Show me all the jobs triggered by a submission from 'John Dowe' (I can 
never trust that J.D., he is all over the place)
   - Show me all the jobs tied to this repository  
The metadata plugin seems like it is geared towards this 
issue:https://wiki.jenkins-ci.org/display/JENKINS/Metadata+plugin

so I guess I have two questions:-- Does anyone else attempt to make queries 
against Jenkins of this sort?-- Has anyone used the Metadata plugin, or some 
other plugin or home-grown solution to solve this issue?
-- 
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/3f9c0f9e-abb0-4092-804e-489f505be2ff%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/2095356288.690480.1427744927153.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Commit access request to merge change to tap-plugin

2015-03-05 Thread 'Bruno P. Kinoshita' via Jenkins Developers


Hi Mathieu,

I hadn't seen that PR, sorry. Will merge it in a couple of hours.

Thanks
Bruno

--
Em qui, 5 de mar de 2015 00:04 BRT Mathieu Gervais escreveu:

Hi,

Per the documentation @
https://wiki.jenkins-ci.org/display/JENKINS/Pull+Request+to+Repositories
I am writing to this mailgroup to request commit access to
jenkinsci/tap-plugin in order to merge this pull request
https://github.com/jenkinsci/tap-plugin/pull/8 (I know it is silly, but
it's sadly a blocker for us).

My github username is egoine.
Repository I need commit access to is jenkinsci/tap-plugin

Thanks!

-mathieu

-- 
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/CADoV0utNJZczdq0muWPffpB-MEKQ_EcqXg3bQ%3Dh3HBXgGg-sog%40mail.gmail.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/1425552450.50382.BPMail_high_carrier%40web163501.mail.gq1.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

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

2015-02-19 Thread 'Bruno P. Kinoshita' via Jenkins Developers

 Finally, we have to consider the effort required to rename the plugin (Bruno, 
 WDYT? )
There will be some effort, and we can miss updating some Javadocs or Strings 
here or there. Some users already familiar with the Uno Choice name would have 
to be notified on the new name. 

But if we agree on a new name, I'd gladly fire Eclipse, rename the artifact ID 
and update the Javadocs and any other reference to the old name that I can find 
:^)
Bruno
 

  From: Ioannis Moutsatsos imoutsat...@gmail.com
 To: jenkinsci-dev@googlegroups.com 
 Sent: Thursday, February 19, 2015 12:36 AM
 Subject: Re: New plug-in: Uno Choice Plug-in for dynamic parameters
   
All,
I do have to take responsibility for naming this plugin. So here goes the 
thinking behind it.
This is a plugin for making one or more choices among options for a parameter. 
Some of the functionality was previously distributed among different plugins 
(dynamic parameter plugin, extensible choice parameter plugin, extended choice 
plugin), but none of these was able to deliver cleanly and consistently the 
four main things I wanted:   
   - Dynamic generation of the parameter options, 
   - multi-select using a variety of formats (check-boxes, radio buttons, 
lists), 
   - filtering, and 
   - dynamically refreshed options based on other parameter choices that users 
make.   


Thus I thought that naming the plugin Uno-Choice was appropriate for two 
reasons:   
   - One (Uno) control that could do it all and
   - Uno for the project behind it (BioUno.org)
In retrospect, perhaps I could have chosen a better name but having Bruno like 
it, sealed the deal! The rest is history as they say...Bruno developed it, and 
here we are finally contributing it to empower all Jenkins users.
So, if the name could confuse new users how could we improve it?
Let me try to offer a few alternatives.    
   - BioUno Dynamic Choices
   - BioUno Scripted Choices
   - Dynamic Options Parameter
   - Scripted Options Parameter
Finally, we have to consider the effort required to rename the plugin (Bruno, 
WDYT? )
Thanks all for the feedbackBest regardsIoannis

On Wednesday, February 18, 2015 at 7:31:29 PM UTC-5, Richard Bywater wrote:
Personally I'd avoid the word Uno in the plugin name completely as, according 
to the README, you can have one *or more* parameters and Uno Choice Dynamic 
Parmeter says to me that the plugin only supports one choice.

Richard.

On Thu, Feb 19, 2015 at 1:22 PM, 'Bruno P. Kinoshita' via Jenkins Developers 
jenkin...@googlegroups. com wrote:

 A suggestion: give the plugin a more descriptive name. Random Jenkinsusers 
are not going to have any idea what “Uno” is. Crediting theinstitution that 
did the work is fine, but if I were looking to makemy parameters dynamic, I 
would pick a plugin named “Dynamic Parameter”and skip right over “Uno Choice”.
Good point. I didn't choose the name, but I like it. Maybe Uno Choice Dynamic 
Parameter? Other suggestions?   BTW if this is to be usable in a secured 
installation you need tointegrate with the script-security plugin.
True! My bad for forgetting about this. I will try to integrate it in my next 
development cycle for the plug-in. I will try to check if the Dynamic Parameter 
plug-in is already integrated with the script-security plug-in. If not, I'll 
try to submit a pull request (otherwise I'll use it as reference :)
CheersBruno 
 
  From: Jesse Glick jgl...@cloudbees.com
 To: Jenkins Dev jenkin...@googlegroups. com 
 Sent: Wednesday, February 18, 2015 7:01 PM
 Subject: Re: New plug-in: Uno Choice Plug-in for dynamic parameters
   
On Tue, Feb 17, 2015 at 8:30 AM, 'Bruno P. Kinoshita' via Jenkins


Developers jenkin...@googlegroups. com wrote:
 We developed a plug-in in the BioUno project

A suggestion: give the plugin a more descriptive name. Random Jenkins
users are not going to have any idea what “Uno” is. Crediting the
institution that did the work is fine, but if I were looking to make
my parameters dynamic, I would pick a plugin named “Dynamic Parameter”
and skip right over “Uno Choice”.

BTW if this is to be usable in a secured installation you need to
integrate with the script-security 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+unsub...@ googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/ 
msgid/jenkinsci-dev/ CANfRfr0gip- ui8oZggT277keKGzYDJoH_ 
WKsEHPFSWjcbw3%2BAQ%40mail. gmail.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-de...@ googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/ 
msgid/jenkinsci-dev/ 1979203684.442515

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

2015-02-19 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hi Daniel!
The plug-in hasn't been released to the Jenkins update center yet, just to the
update center hosted at BioUno - we do this because of some niche plug-ins
(phylogenetics, PBS/Torque, etc).

If the plug-in proposal gets accepted here and we agree on a new name, we can
then release it to all users under the new artifact id.
Cheers,Bruno

From: Daniel Beck m...@beckweb.net
To: jenkinsci-dev@googlegroups.com
Sent: Thursday, February 19, 2015 3:47 PM
Subject: Re: New plug-in: Uno Choice Plug-in for dynamic parameters

On 19.02.2015, at 16:17, 'Bruno P. Kinoshita' via Jenkins Developers
jenkinsci-dev@googlegroups.com wrote:

rename the artifact ID

The old one will still be available in update center, and just be a dead end.
Not sure whether we've ever removed anything (there are a few plugins where
this happened and it's not pretty).

--
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/3A1751C9-76F0-40C0-9D48-4A764ECF19AB%40beckweb.net.

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/271565627.716651.1424369013143.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins UX

2015-02-18 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hello Gus, 

I heard good feedback on the new Jenkins UI. Kudos everyone involved!
I don't really have much to contribute I think. But yesterday I posted to the 
dev-list about a new plug-in, Uno Choice, that is being used by researchers 
(both in academia and in industry). 
The plug-in relies utilizes HTML DOM elements to access job parameters. Should 
any of these elements gets changed due to UX enhancements, the plug-in would  
stop working. 

What I would like to have in order to avoid having this kind of issues, is 
something like  global JS objects exposed by Jenkins - I'm not a JavaScript 
programmer, so I'm not completely sure that it is a good idea/practice. 

This way, plug-ins like Uno Choice could access parameters' elements, the Queue 
HTML elements, enable/disable buttons, without depending directly on any screen 
selector. More or less something like: 

# JS code used in the job parameter screen
```var parameters = Jenkins.parameters.all();var fields = 
parameters[0].getFields();var name = parameters[0].name;// internally Jenkins 
controls the selectors to access the parameters. Should any of these changes, 
plug-ins wouldn't be affected.
```
Not sure if that's the best option...

My +1 :^) please continue the hard work on improving Jenkins UX.

All the best,
Bruno


  From: Gus Reiber grei...@cloudbees.com
 To: jenkinsci-dev@googlegroups.com 
 Sent: Wednesday, February 18, 2015 2:27 PM
 Subject: Jenkins UX
   
At the end of last summer, my friend and co-worker, Tom Fennelly, along with 
the help of Kevin Burke, 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   

   - Any comments on the UI changes in 1.572: 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 conversation along, I also have a handful of 
questions to which I would love responses:   
   - For plugin builders, can you tell me a bit about creating the UI portion 
of your plugin (did you use the data binding form controls, what was hard, what 
did you have to invent)?   

   - For regular Jenkins users, what are the UX areas of Jenkins you would most 
like to see improved (I think it is the item create/config and the 
dashboard/job list grid, but would love to hear others and general feedback)?   

   - For UXers and other Jenkins contributors, how do my 3 forward paths seem 
(are there others, do you have experience with any yourself, do any seem 
scary)?   

   - Has anyone tried to make their own themes with the new capabilities Tom 
has added or would you appreciate and handful of canned options to choose 
between?

Re: Jenkins UX

2015-02-18 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hi Gus. I have replied off-list with access to a Jenkins server where we tested 
the Uno Choice plug-in. 

There you'll find several jobs configured to create dynamic parameters and even 
some graphs I think? (Ioannis feel free correct me if I'm wrong).
Will reply your questions when I arrive at home.
ThanksBruno

 
  From: Gus Reiber grei...@cloudbees.com
 To: jenkinsci-dev@googlegroups.com 
 Sent: Wednesday, February 18, 2015 6:05 PM
 Subject: Re: Jenkins UX
   
Thanks for your feedback, Bruno.Your concern is exactly the concern that keeps 
me up at night.
Thanks also for raising Uno Choice as an example.I am very much looking for 
specific examples of plugins with reasonable adoption that use the DOM to scrap 
bits and pieces of data out of Jenkins so I can get a test case list together.
...and your reward for you awesome feedback is 3 more questions from me... ;^)
   
   - About Uno Choice, specifically, when you talk about crawling the page for 
job parameters, does this happen in the create/config page, the dashboard/item 
table, somewhere else, or all of the above?   
   

   - When you talk about a global JS object, I am guessing you mean the data 
model of the config form, primarily.   
If not, and you are scrapping data out of the dashboard table, I am still 
assuming the data you are looking for is not here [ 
https://ci.jenkins-ci.org/job/lib-jira-api/api/json ] or burried deep down that 
tree, or it is, fetching it via ajax is either too onerus or too non-performant 
to be worth the hassle?   
   

   - As I see it, for much of Jenkins plugin interoperation, and even some of 
its core functionality, there isn't really a programmatic API, but a set of 
facts about how Jenkins draws things on the screen that can be exploited to 
make features and components that share data in meaningful and interesting 
ways. The rub is that now to improve the UX in almost any meaningful way 
requires either changing that DOM (since that is what controls the rendering 
and GUI driven interactivity) and breaking those makeshift APIs, or 
establishing a new means for UI building that is completely independant of the 
past DOM. In that case plugins aren't broken, but a choice is required within 
Jenkins, work on an old canvas where old plugins work just fine, or work on the 
new canvas which starts without plugins, but is more capable.   
so my question here is if you had to choose (and I am hoping you don't and 
won't) between accepting some breakage or having a sort of split-canvas choice 
within Jenkins, which would you choose?
Would you need more information before you could you even make such a choice?   
   
Neither of these options seems very satisfying to me.

Thanks Again,Gus

On Wed, Feb 18, 2015 at 9:12 AM, 'Bruno P. Kinoshita' via Jenkins Developers 
jenkinsci-dev@googlegroups.com wrote:



Hello Gus, 

I heard good feedback on the new Jenkins UI. Kudos everyone involved!
I don't really have much to contribute I think. But yesterday I posted to the 
dev-list about a new plug-in, Uno Choice, that is being used by researchers 
(both in academia and in industry). 
The plug-in relies utilizes HTML DOM elements to access job parameters. Should 
any of these elements gets changed due to UX enhancements, the plug-in would  
stop working. 

What I would like to have in order to avoid having this kind of issues, is 
something like  global JS objects exposed by Jenkins - I'm not a JavaScript 
programmer, so I'm not completely sure that it is a good idea/practice. 

This way, plug-ins like Uno Choice could access parameters' elements, the Queue 
HTML elements, enable/disable buttons, without depending directly on any screen 
selector. More or less something like: 

# JS code used in the job parameter screen
```var parameters = Jenkins.parameters.all();var fields = 
parameters[0].getFields();var name = parameters[0].name;// internally Jenkins 
controls the selectors to access the parameters. Should any of these changes, 
plug-ins wouldn't be affected.
```
Not sure if that's the best option...

My +1 :^) please continue the hard work on improving Jenkins UX.

All the best,
Bruno


  From: Gus Reiber grei...@cloudbees.com
 To: jenkinsci-dev@googlegroups.com 
 Sent: Wednesday, February 18, 2015 2:27 PM
 Subject: Jenkins UX
   
At the end of last summer, my friend and co-worker, Tom Fennelly, along with 
the help of Kevin Burke, 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   

   - Any comments on the UI changes

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

2015-02-18 Thread 'Bruno P. Kinoshita' via Jenkins Developers

A suggestion: give the plugin a more descriptive name. Random Jenkinsusers
are not going to have any idea what “Uno” is. Crediting theinstitution that
did the work is fine, but if I were looking to makemy parameters dynamic, I
would pick a plugin named “Dynamic Parameter”and skip right over “Uno Choice”.
Good point. I didn't choose the name, but I like it. Maybe Uno Choice Dynamic
Parameter? Other suggestions? BTW if this is to be usable in a secured
installation you need tointegrate with the script-security plugin.
True! My bad for forgetting about this. I will try to integrate it in my next
development cycle for the plug-in. I will try to check if the Dynamic Parameter
plug-in is already integrated with the script-security plug-in. If not, I'll
try to submit a pull request (otherwise I'll use it as reference :)
CheersBruno

From: Jesse Glick jgl...@cloudbees.com
To: Jenkins Dev jenkinsci-dev@googlegroups.com
Sent: Wednesday, February 18, 2015 7:01 PM
Subject: Re: New plug-in: Uno Choice Plug-in for dynamic parameters

On Tue, Feb 17, 2015 at 8:30 AM, 'Bruno P. Kinoshita' via Jenkins

Developers jenkinsci-dev@googlegroups.com wrote:
We developed a plug-in in the BioUno project

BTW if this is to be usable in a secured installation you need to
integrate with the script-security 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/CANfRfr0gip-ui8oZggT277keKGzYDJoH_WKsEHPFSWjcbw3%2BAQ%40mail.gmail.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/1979203684.442515.1424305331365.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

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

2015-02-17 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hello all,
We developed a plug-in in the BioUno project [1], initially based on the
Dynamic Parameter Plug-in [2], but that followed a different approach for
dynamic parameters. It provides parameters that are also rendered from Groovy
scripts (per job script or via Scriptler integration) **but that can be related
to other parameters**.
It utilizes JavaScript (FWIW dynamicparameter-plugin code is 2.8% JavaScript
according to GitHub interface and uno-choice's is 43.9%) to monitor the HTML
elements of one parameter, and trigger changes in other parameters. This way,
you can easily create many parameters, like Maven Group ID, Artifact ID and
Versions, that are dynamically updated.
Quick example: The Maven group ID could be a Uno Choice Dynamic Choice
Parameter that returns a list of maven group IDs in some Maven repo using
Groovy. Once the user selects a group ID, the artifact ID (a Uno Choice
Cascade Dynamic Choice Parameter) would automatically get updated, and its
Groovy script rendered. The selected group ID would be available to the
artifact id Groovy script as a variable. This way your script can load only the
artifacts related to the selected group ID.
Attached is a GIF file with another example with a State parameter that
dynamically updates the City parameter accordingly.
The following Wiki page has been created and contains further information and
examples: https://wiki.jenkins-ci.org/display/JENKINS/Uno+Choice+Plugin There
are other features that were added to the plug-in such as hidden parameters,
parameter filtering, self-referenced parameters and more, that I believe
Ioannis could explain much better if necessary.
GitHub repository: https://github.com/biouno/uno-choice-plugin/GitHub user IDS:
@kinow and @imoutsatsos
If the plug-in gets accepted, I'll adjust the pom.xml, and will cut a 1.0
release.
Thank you!Bruno
[1] http://biouno.org/[2]
https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Dynamic+Parameter+Plug-in

--
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/50262896.2043921.1424179818746.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Testopia jenkins integration

2014-12-15 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Sorry Ankush, haven't had time to take a look yet. I still have a working
Bugzilla/Testopia + Jenkins environment in my computer, so it mustn't be very
hard to debug it later. My guess is that your key custom field is
missing/wrong, or the unit result file generated is different than expected by
the plug-in.
Could you please file an issue with the information you provided here in the
mailing list, please? Feel free to ping me there if I take too long to take a
look on it. Probably will do after holidays.
Thanks!Bruno

From: Ankush Aggarwal er.ankush.aggar...@gmail.com
To: jenkinsci-dev@googlegroups.com
Sent: Monday, December 15, 2014 2:53 AM
Subject: Re: Testopia jenkins integration

Hi Bruno,
Did you get a chance to check it.
Thanks,Ankush

On Thursday, 27 November 2014 16:23:12 UTC+5:30, Ankush Aggarwal wrote:
Hi All,
I am integrating Testopia with Jenkins,
Download very simple java app from internet having test cases.Jenkins
authentication with testopia is working fine.Created test Plan, test run, test
case in TestopiaAttached both jenkins and testopia conf details.
jenkins is not able found test results and not able to update testopia. Anyone
please help me on this.
Testing.sh :-cd target/test-classes/usr/java/jdk1.7.0_71/bin/java -cp
.:/var/lib/jenkins/jobs/App/ target/classes/*:/var/lib/
jenkins/jobs/App/junit-4.11. jar:/var/lib/jenkins/jobs/App/
hamcrest-core-1.3.jar org.junit.runner.JUnitCore com.mkyong.core.TestApp1

[INFO] -- --

[INFO] BUILD SUCCESS
[INFO] -- --

[INFO] Total time: 3.574 s
[INFO] Finished at: 2014-11-21T02:17:54-05:00
[INFO] Final Memory: 9M/57M
[INFO] -- --

Build step 'Invoke Maven 3' changed build result to SUCCESS
Connecting to Testopia to retrieve automated test cases
Preparing Testopia connection properties
Executing single build steps
[App] $ /bin/sh -xe /tmp/ hudson2693326793877533844.sh
+ ./testing.sh
JUnit version 4.11
.
Time: 0.007

OK (1 test)

Executing iterative build steps
Seeking test results
Found 0 test results
Finished: SUCCESS
--
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/705c1916-5b69-4f6c-9ee2-90b8389da38c%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/1924379476.137250.1418692440244.JavaMail.yahoo%40jws10798.mail.gq1.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Patch for JENKINS-20998

2014-12-12 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hi Bram!
Would you be willing to create a GitHub account and submit a pull request? I
think that'd be easier for others to review and/or comment your code.

I've linked your message in the JIRA issue, so maybe watchers of that issue
will take a look at your patch and provide some feedback on it.
All the best,Bruno

From: bram.stapp...@gmail.com bram.stapp...@gmail.com
To: jenkinsci-dev@googlegroups.com
Sent: Friday, December 12, 2014 10:14 AM
Subject: Patch for JENKINS-20998

I have created a patch for issue
https://issues.jenkins-ci.org/browse/JENKINS-20998. See attached screenshot for
the resulting Workspace View.
Disclaimers: This is my first attempt at a Jenkins contribution. I have read
the relevant pages on contributing to Jenkins turned up by Google search. I do
not have an account on the Jira issue tracker, nor do I have a Github account.
Hence, this submission via the mailing list.--
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/1e9baa27-5169-48ad-8de2-b01b1ffe7ee5%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/60077051.145168.1418389086716.JavaMail.yahoo%40jws10783.mail.gq1.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Testopia jenkins integration

2014-12-04 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hi Ankush
You can follow the Wiki -
https://wiki.jenkins-ci.org/display/JENKINS/Testopia+Plugin
Check your Jenkins, Testopia and plug-in versions for compatibility. You can
post your config (screenshots, xml, etc) if that doesn't help.
All the bestBruno

From: Ankush Aggarwal er.ankush.aggar...@gmail.com
To: jenkinsci-dev@googlegroups.com
Sent: Thursday, December 4, 2014 4:22 AM
Subject: Re: Testopia jenkins integration

Hi Kinow,
Thanks for reply.

Yes i am missing this seeking result part. I have tried to integrated with
selenium java suite, htmlsuite, or even basic shell script having echo command
but failed to achieve exact results.
I followed https://www.youtube.com/watch?v=tH_E0O1QchU video.
Could you please share some link where testopia + jenkins implementation things
are documented or steps to follow or video that can help me.
Thanks,Ankush

[INFO] -- --

[INFO] BUILD SUCCESS
[INFO] -- --

[INFO] Total time: 3.574 s
[INFO] Finished at: 2014-11-21T02:17:54-05:00
[INFO] Final Memory: 9M/57M
[INFO] -- --

OK (1 test)

Executing iterative build steps
Seeking test results
Found 0 test results
Finished: SUCCESS
--
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/2cafb8e3-d6c4-4f64-ac42-1e5413a2218a%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/1882542569.1245946.1417739240024.JavaMail.yahoo%40jws10731.mail.gq1.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: commit access for selenium-plugin

2014-12-01 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hi Oleksandr!
Have you contacted Richard directly? As far as I know, he's quite busy, but had
plans to implement some new features in the selenium-plugin. Might be worth
checking with him before merging the pull requests yourself.
CheersBruno

From: Oleksandr Kulychok alex.kool...@gmail.com
To: jenkinsci-dev@googlegroups.com
Sent: Monday, December 1, 2014 11:46 AM
Subject: commit access for selenium-plugin

Please give me commit access to https://github.com/jenkinsci/selenium-plugin
My gitHub user name is: kool79
Repository maintainer does not respond for pull requests for more than 2 weeks

Thanks, Oleksandr Kulychok--
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/7215fbcf-50d0-4210-b1ae-a5593202a6b5%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/1686123952.742526.1417443549141.JavaMail.yahoo%40jws10772.mail.gq1.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Testopia jenkins integration

2014-11-27 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hi Ankush,

I think you are missing the result seeking strategy? The plug-in uses these
strategies to look for your test results, and that could be causing the 0 tests
found message.
HTH,Bruno

From: Ankush Aggarwal er.ankush.aggar...@gmail.com
To: jenkinsci-dev@googlegroups.com
Sent: Thursday, November 27, 2014 8:53 AM
Subject: Testopia jenkins integration

Hi All,
I am integrating Testopia with Jenkins,
Download very simple java app from internet having test cases.Jenkins
authentication with testopia is working fine.Created test Plan, test run, test
case in TestopiaAttached both jenkins and testopia conf details.
jenkins is not able found test results and not able to update testopia. Anyone
please help me on this.
Testing.sh :-cd target/test-classes/usr/java/jdk1.7.0_71/bin/java -cp
.:/var/lib/jenkins/jobs/App/ target/classes/*:/var/lib/
jenkins/jobs/App/junit-4.11. jar:/var/lib/jenkins/jobs/App/
hamcrest-core-1.3.jar org.junit.runner.JUnitCore com.mkyong.core.TestApp1

[INFO] -- --

[INFO] BUILD SUCCESS
[INFO] -- --

[INFO] Total time: 3.574 s
[INFO] Finished at: 2014-11-21T02:17:54-05:00
[INFO] Final Memory: 9M/57M
[INFO] -- --

OK (1 test)

Executing iterative build steps
Seeking test results
Found 0 test results
Finished: SUCCESS--
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/0824adb5-ceb8-495c-aeed-8ec5b51855b0%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/1929685679.422714.1417089221615.JavaMail.yahoo%40jws10759.mail.gq1.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

[testlink-plugin] Looking for other maintainers/committers

2014-10-05 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hi all, 
Some time ago I started writing the TestLink plug-in, and even wrote articles 
and went to conferences to talk about it. Later I worked with Peter Florijn to 
release a similar plug-in but for Testopia.
However, now I have no cycles to work on TestLink and been busy with other OSS 
projects, and am also relocating to another continent, so probably my next 
cycle to work on TestLink, testlink-java-api or TestLink Plug-in will happen 
only in 2015.
If anyone is interested we can work together on some issues, then I'll show you 
what/how/why things work in the plug-in and in the Java API. I can cut new 
releases as you need, but if you are willing to wear the release-manager hat, 
I'll provide you the rights to jenkinsci/testlink-plugin repo and the Sonatype 
repo as well. 
Just ping me here, off-list, IRC (kinow), Twitter or wherever works best for 
you.
Thank you!Bruno
ps: if you know of any open positions in NZ/Auckland for 2015, please give me a 
shout and I'll owe you a beer/coffee :)

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: New composer-columns plugin

2014-09-12 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Sounds like a good idea too Fred, +1 for adding it to an existing plug-in then 
:)

Bruno

 From: FredG fred.g...@googlemail.com
To: jenkinsci-dev@googlegroups.com 
Cc: brunodepau...@yahoo.com.br 
Sent: Friday, September 12, 2014 8:50 AM
Subject: Re: New composer-columns plugin

Hi,

In my unwinnable quest to stop uncontrolled growth of tiny plug-ins 
(especially listview-column plug-ins), I'd highly recommend to merge these two 
plug-ins together.
I think it's a perfect fit to include columns that depend on third-party 
software/plug-ins with plug-ins that depend on the same software.
Common columns without any dependencies should be bundled in the Extra Columns 
Plugin.

Regards,

Fred

On Thursday, September 11, 2014 5:02:01 PM UTC+2, kinow wrote:
Hi Javi, 

Sounds like a useful plug-in. I haven't had time to look at this repo [1], 
but in case you are interested in releasing a composer-plugin for Jenkins, 
that could serve as basis too. It hasn't been released yet.

[1] https://github.com/renanbr/ composer-plugin

 From: Javi Hernández javi...@gmail.com
To: jenkin...@googlegroups.com 
Sent: Thursday, September 11, 2014 11:53 AM
Subject: New composer-columns plugin

Hello,

I've created a new Jenkins plugin witch allows to show composer.json version 
in view columns. Soon, I want to add more column features: dependency 
version, etc.

I would like to host this plugin in jenkinsci github repo. Now it's hosted 
at https://github.com/ javihgil/composer-columns- plugin. 

Best.
-- 
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.
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.
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.
For more options, visit https://groups.google.com/d/optout.

Re: new plugin hosting request

2014-09-09 Thread 'Bruno P. Kinoshita' via Jenkins Developers



Hey Matthew, 

I'm working with a team using Ansible YAML playbooks, so probably using similar 
syntax for creating Jenkins projects would be a good idea. 

Are you going to host the plug-in under jenkinsci org at GitHub? 

Thanks!
Bruno



 From: 'Matthew Moore' via Jenkins Developers jenkinsci-dev@googlegroups.com
To: jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com 
Sent: Tuesday, September 9, 2014 12:41 PM
Subject: new plugin hosting request
 


I have posted a new plugin here:

  https://github.com/mattmoor/yaml-project-plugin



and added its associated wiki page here:
  https://wiki.jenkins-ci.org/display/JENKINS/YAML+Project+Plugin


FWIW, this is the basis of the talk I plan to give at JUC 2014 this Fall.





thanks,
-M



-- 

Matthew Moore
DI/Docker (aka Convoy)
Developer Infrastructure @ Google

-- 
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.
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.
For more options, visit https://groups.google.com/d/optout.

Re: new plugin hosting request

2014-09-09 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Oh got it, then you simply convert the YAML file back to JSON. 

If there's no objection, I'll fork this repository under jenkinsci using the 
IRC bot in the next hour. The Wiki looks good, no similar plug-ins, or any 
other that could have this plug-in as a feature, code looks good as well, 
license compatible.

I think the only thing wrong is the artifactId. Can you rename it to 
artifactIdyaml-project/artifactId, please? The plug-in part only gets added 
to the github repository name. We can create a component in JIRA and assign you 
as maintainer, do you have a JIRA user already?

Thanks!
Bruno





 From: 'Matthew Moore' via Jenkins Developers jenkinsci-dev@googlegroups.com
To: jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com 
Sent: Tuesday, September 9, 2014 1:41 PM
Subject: Re: new plugin hosting request
 


To be clear: I am not defining any YAML syntax.


The syntax for the YAML this parses is entirely defined by Jenkins' Structured 
Form Submissions.


This is entirely by design, since it means that basically any plugin that 
Jenkins can create through the UI, this plugin should be able to create from 
YAML.



Better still, the YAML asks users to specify precisely what the UI does :)






Are you going to host the plug-in under jenkinsci org at GitHub?


Yes, that is essentially what this thread is about.




Happy to chat more, especially if any of the above isn't clear.
-M





On Tue, Sep 9, 2014 at 8:55 AM, 'Bruno P. Kinoshita' via Jenkins Developers 
jenkinsci-dev@googlegroups.com wrote:



Hey Matthew, 


I'm working with a team using Ansible YAML playbooks, so probably using 
similar syntax for creating Jenkins projects would be a good idea. 


Are you going to host the plug-in under jenkinsci org at GitHub? 


Thanks!
Bruno




 From: 'Matthew Moore' via Jenkins Developers 
 jenkinsci-dev@googlegroups.com
To: jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com 
Sent: Tuesday, September 9, 2014 12:41 PM
Subject: new plugin hosting request
 


I have posted a new plugin here:

  https://github.com/mattmoor/yaml-project-plugin



and added its associated wiki page here:
  https://wiki.jenkins-ci.org/display/JENKINS/YAML+Project+Plugin


FWIW, this is the basis of the talk I plan to give at JUC 2014 this Fall.





thanks,
-M



-- 

Matthew Moore
DI/Docker (aka Convoy)
Developer Infrastructure @ Google
-- 
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.
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.
For more options, visit https://groups.google.com/d/optout.




-- 

Matthew Moore
DI/Docker (aka Convoy)
Developer Infrastructure @ Google

-- 
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.
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.
For more options, visit https://groups.google.com/d/optout.

Re: new plugin hosting request

2014-09-09 Thread 'Bruno P. Kinoshita' via Jenkins Developers

testng-plugin and build-flow-plugin also use the -plugin suffix in the artifact 
id .

All set Matthew, plugin created at [1], component yaml-project created in JIRA. 
You should already have commit access, but let me know if that doesn't work. 

Also, I have already tried the YAML plug-in and I liked it. Are there other 
ways to get the YAML file, like from some web site, ftp, etc? 

Thanks!
Bruno

[1] https://github.com/jenkinsci/yaml-project-plugin



 From: 'Matthew Moore' via Jenkins Developers jenkinsci-dev@googlegroups.com
To: jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com 
Sent: Tuesday, September 9, 2014 3:00 PM
Subject: Re: new plugin hosting request
 


Found one:
dependency
  groupIdorg.jenkins-ci.plugins/groupId
  artifactIdbuild-pipeline-plugin/artifactId
  version1.4.3/version
  optionaltrue/optional
/dependency


However, I'm just happy it means I'm not crazy, I have already pushed a change 
removing '-plugin' from artifactId.




thanks again,
-M







On Tue, Sep 9, 2014 at 10:57 AM, Matthew Moore mattm...@google.com wrote:

Huh, my mistake on Artifact ID.  I've been using -plugin for the various 
Google-specific plugins, but I sampled a few plugins I would have referenced 
and you are 100% correct :)


I'll change the artifact id shortly.  My username is generally 'mattmoor', 
pretty sure I am registered, since I've released a few plugins now.


thanks for the quick turnaround.
-M



On Tue, Sep 9, 2014 at 10:49 AM, 'Bruno P. Kinoshita' via Jenkins Developers 
jenkinsci-dev@googlegroups.com wrote:

Oh got it, then you simply convert the YAML file back to JSON. 


If there's no objection, I'll fork this repository under jenkinsci using the 
IRC bot in the next hour. The Wiki looks good, no similar plug-ins, or any 
other that could have this plug-in as a feature, code looks good as well, 
license compatible.


I think the only thing wrong is the artifactId. Can you rename it to 
artifactIdyaml-project/artifactId, please? The plug-in part only gets 
added to the github repository name. We can create a component in JIRA and 
assign you as maintainer, do you have a JIRA user already?


Thanks!
Bruno







 From: 'Matthew Moore' via Jenkins Developers 
 jenkinsci-dev@googlegroups.com
To: jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com 
Sent: Tuesday, September 9, 2014 1:41 PM
Subject: Re: new plugin hosting request
 


To be clear: I am not defining any YAML syntax.


The syntax for the YAML this parses is entirely defined by Jenkins' 
Structured Form Submissions.


This is entirely by design, since it means that basically any plugin that 
Jenkins can create through the UI, this plugin should be able to create 
from YAML.



Better still, the YAML asks users to specify precisely what the UI does :)






Are you going to host the plug-in under jenkinsci org at GitHub?


Yes, that is essentially what this thread is about.




Happy to chat more, especially if any of the above isn't clear.
-M





On Tue, Sep 9, 2014 at 8:55 AM, 'Bruno P. Kinoshita' via Jenkins Developers 
jenkinsci-dev@googlegroups.com wrote:



Hey Matthew, 


I'm working with a team using Ansible YAML playbooks, so probably using 
similar syntax for creating Jenkins projects would be a good idea. 


Are you going to host the plug-in under jenkinsci org at GitHub? 


Thanks!
Bruno




 From: 'Matthew Moore' via Jenkins Developers 
 jenkinsci-dev@googlegroups.com
To: jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com 
Sent: Tuesday, September 9, 2014 12:41 PM
Subject: new plugin hosting request
 


I have posted a new plugin here:

  https://github.com/mattmoor/yaml-project-plugin



and added its associated wiki page here:
  https://wiki.jenkins-ci.org/display/JENKINS/YAML+Project+Plugin


FWIW, this is the basis of the talk I plan to give at JUC 2014 this Fall.





thanks,
-M



-- 

Matthew Moore
DI/Docker (aka Convoy)
Developer Infrastructure @ Google
-- 
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.
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.
For more options, visit https://groups.google.com/d/optout.






-- 

Matthew Moore
DI/Docker (aka Convoy)
Developer Infrastructure @ Google

-- 
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.
For more options, visit

Re: [HEADS UP] getTestResultAction removed in 1.577

2014-08-26 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Thanks for the heads up Jesse. IIRC the tap-plugin also utilizes these methods. 
I'll take a look this weekend and will update it.

Bruno

 From: Jesse Glick jgl...@cloudbees.com
To: Jenkins Dev jenkinsci-dev@googlegroups.com 
Sent: Tuesday, August 26, 2014 4:24 PM
Subject: [HEADS UP] getTestResultAction removed in 1.577

For proper stratification I needed to deprecate
AbstractBuild.getTestResultAction (and .getAggregatedTestResultAction)
in Jenkins core 1.577, allowing the JUnit test result publisher and
associated APIs to be split into junit-plugin. Plugins calling these
methods will generally not work in 1.577+. The replacement is trivial
and does not require a newer core dependency: just call
.getAction(DesiredActionClass.class).

For the economy of scale I committed this fix to the master branch of
all plugins in https://github.com/jenkinsci/ a month ago, but did not
release it except for a handful of bundled plugins. The following
plugins still have this change unreleased as of this writing:

ci-game-plugin
email-ext-plugin
extra-columns-plugin
graphite-plugin
integrity-plugin
ivy-plugin
JiraTestResultReporter-plugin
lotus-connections-plugin
meliora-testlab-plugin
parallel-test-executor-plugin
regression-report-plugin
tikal-multijob-plugin
violation-columns-plugin

If you maintain one of these plugins, please consider cutting a
release from trunk to support users of weekly builds. If there are
other unreleased and unreleasable trunk changes, the fixing commits
ought to be easy to backport to a special branch release, but reply
here or to me privately if you need any help with that.

-- 
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.
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.
For more options, visit https://groups.google.com/d/optout.

Re: New Plugin: SAML Plugin

2014-08-09 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hi Ben, 

I think your plugin was uploaded to the snapshot repository. 

Take a look at any of this previous threads 

https://groups.google.com/d/msg/jenkinsci-dev/qkmbl3HrYgk/dWnVU7-nTjoJ

https://groups.google.com/forum/#!searchin/jenkinsci-dev/snapshot/jenkinsci-dev/fyxXO0HXrGc/r1KYltnfzesJ

Hope that helps
Bruno



 From: Ben McCann b...@benmccann.com
To: jenkinsci-dev@googlegroups.com 
Sent: Saturday, August 9, 2014 3:56 PM
Subject: Re: New Plugin: SAML Plugin
 


I don't see my plugin yet in the two sites mentioned on the wiki. It's been 
almost 24 hours and it said they should show up within 6, so I think 
somethings wrong.
http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/

http://repo.jenkins-ci.org/releases/org/jvnet/hudson/plugins/



When I ran mvn release:prepare release:perform it uploaded the files and I 
can download them all:
[INFO] Uploaded: 
http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/saml/0.1-SNAPSHOT/saml-0.1-20140808.222605-1.hpi
 (11269 KB at 581.9 KB/sec)
[INFO] Uploaded: 
http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/saml/0.1-SNAPSHOT/saml-0.1-20140808.222605-1.pom
 (3 KB at 4.5 KB/sec)
[INFO] Uploaded: 
http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/saml/0.1-SNAPSHOT/maven-metadata.xml
 (770 B at 1.7 KB/sec)
[INFO] Uploaded: 
http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/saml/maven-metadata.xml
 (318 B at 0.5 KB/sec)
[INFO] Uploaded: 
http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/saml/0.1-SNAPSHOT/saml-0.1-20140808.222605-1.jar
 (16 KB at 18.1 KB/sec)
[INFO] Uploaded: 
http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/saml/0.1-SNAPSHOT/maven-metadata.xml
 (941 B at 1.8 KB/sec)
[INFO] Uploaded: 
http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/saml/0.1-SNAPSHOT/saml-0.1-20140808.222605-1-sources.jar
 (9 KB at 10.9 KB/sec)
[INFO] Uploaded: 
http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/saml/0.1-SNAPSHOT/maven-metadata.xml
 (2 KB at 2.1 KB/sec)
[INFO] Uploaded: 
http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/saml/0.1-SNAPSHOT/saml-0.1-20140808.222605-1-javadoc.jar
 (60 KB at 61.9 KB/sec)
[INFO] Uploaded: 
http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/saml/0.1-SNAPSHOT/maven-metadata.xml
 (2 KB at 2.5 KB/sec)


Any suggestions?


Thanks,
Ben







On Sat, Aug 9, 2014 at 11:46 AM, Ben McCann b...@benmccann.com wrote:

I just filed two bugs for the https issue. I have to say I am quite concerned 
this is an issue and that there are over 50 open items listed as critical 
security issues in the bug tracker.
https://issues.jenkins-ci.org/browse/JENKINS-24190

https://issues.jenkins-ci.org/browse/JENKINS-24191










On Fri, Aug 8, 2014 at 4:00 PM, Ben McCann b...@benmccann.com wrote:

Great! Thank you so much.


I've made the changes you've requested and released 0.1. I think... It's not 
showing up yet as available for download and the wiki still says No 
Information For This Plugin. Perhaps it just takes awhile to appear due to 
some caching or something


Is there anything I should do to have the plugin listed here: 
https://wiki.jenkins-ci.org/display/JENKINS/Plugins ?  It looks like it has 
to be tagged as a user plugin, but I'm not sure where those tags are managed.


Btw, it seems like not a great idea that the update site is 
http://updates.jenkins-ci.org/update-center.json. That seems like something 
that should really, really have HTTPS enabled on it.


Thanks!
Ben









On Fri, Aug 8, 2014 at 1:07 PM, Christopher Orr ch...@orr.me.uk wrote:

Hi there,

Your plugin has been cloned here, and the GitHub ID you mentioned also has 
commit access:
https://github.com/jenkinsci/saml-plugin

If you could follow convention and remove the -plugin suffix from the 
artifactId in pom.xml, that would be great.  The URL to the licence would 
also need to be changed (not that it's usually necessary, AFAIK).

Also the All rights reserved comments to your company in the source files 
seems like it maybe conflicts with the fact that the code is meant to be 
Apache licensed?  (Not that I'm a lawyer)

In any case, you just need to follow the steps here to make a release:
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins

Welcome aboard :)

Regards,
Chris



On 08/08/2014 07:20 PM, Ben McCann wrote:

Hi,

Any thoughts on this?

Thanks,
Ben

On Aug 7, 2014 11:54 AM, Ben McCann b...@benmccann.com

mailto:b...@benmccann.com wrote:

    Hi,

    Just wanted to follow up on this and see if there was anything I
    needed to do to have this downloadable from the Jenkins plugin
    registry. There's no plugin currently supporting SAML 2.0, so I
    think

Re: DTKit sources location?

2014-07-25 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hi Vincent,

Some time ago I was investigating an xUnit issue, and also tracked down the 
problem to dtkit. Since I couldn't send a pull request, I gave up and someone 
eventually fixed it later.

+1 for that

Bruno



 From: Vincent Latombe vincent.lato...@gmail.com
To: Jenkins Dev jenkinsci-dev@googlegroups.com 
Sent: Friday, July 25, 2014 5:14 AM
Subject: DTKit sources location?
 


Hi,

I'm trying to solve an issue related to xUnit, apparently it is located in one 
of the libs used by this plugin, dtkit.

Apparently this lib is still on svn 
https://svn.jenkins-ci.org/tags/dtkit-default-junit-parent-0.39/ but hasn't 
been mirrored to github as part of the global github migration.

Would it be possible to mirror it to the jenkinsci org?



Vincent
-- 
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.
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.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins plugin for HPC job systems

2014-06-12 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hi Jesse,

I will probably read the FlyweightTask javadocsrc and will experiment with it.

But that special project type could work too. Any chance to see an Open Source 
version of it this year? :-) 

Thanks!

Bruno



 From: Jesse Glick jgl...@cloudbees.com
To: jenkinsci-dev@googlegroups.com 
Sent: Thursday, June 12, 2014 10:59 AM
Subject: Re: Jenkins plugin for HPC job systems
 

On Wed, Jun 11, 2014 at 8:29 PM, 'Bruno P. Kinoshita' via Jenkins
Developers jenkinsci-dev@googlegroups.com wrote:
 I thought about re-using the monitor-external-job plug-in

It makes for pretty weak integration since it does not let Jenkins
*initiate* the build. Cf.

http://developer-blog.cloudbees.com/2014/03/support-for-long-running-builds-in.html

 Any advice on how to add items created in the cluster to the build queue in 
 Jenkins?

I guess you could create a dummy FlyweightTask (tied to the master
label) whose Executable does nothing but sleep, and schedule it when
the cluster item is created, but have it claim to be “blocked” (with a
new cause you define) until the cluster actually starts running it.

I am not sure if that is really intuitive, or if you would better
define a new Widget showing cluster status in a specialized manner.

James Hetherington wrote:
 I don't think I understand the durable-task solution, as to me that sounds 
 like one would not be able to move existing freestyle jobs
 back and forth between conventional nodes and batch system nodes

Correct; freestyle projects are incapable of surviving Jenkins
restarts, and I do not think that can be changed. Thus in Jenkins
Enterprise we added a new project type superficially similar to
freestyle but using durable-task-plugin for the main build step and
which does survive restarts. Analogously, workflow builds (using a
very different UI) can survive restarts and can also use
durable-task-plugin to manage running your external build process
during this time.


-- 
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.
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.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins plugin for HPC job systems

2014-06-12 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hello James

Regarding the problem of Jenkins going offline, my feeling would be to 
mitigate this risk by: (1) Warning and doing a qdel on all Jenkins-submitted 
jobs when Jenkins shuts down cleanly. (2) Warning and doing a qdel on all 
lingering Jenkins jobs when Jenkins comes back up after an unclean shutdown.


That's the beauty of durable tasks and similar approaches: we won't have to 
qdel PBS jobs. Jenkins will reconnect automagically with the cluster and will 
continue monitoring the job till it is over.

I don't think I understand the durable-task solution, as to me that sounds 
like one would not be able to move existing freestyle jobs back and forth 
between conventional nodes and batch system nodes... It seems to me that the 
right solution would be a new kind of slave node, rather than a new kind of 
job, though I'm happy to be corrected...


I'm still learning about the durable-task solution (and keeping track of what I 
understand about it [1]). But IIUC we could still use the slave node to 
represent the PBS cluster. The problem lies in the way we trigger PBS jobs and 
keep track of what's running. 

At the moment you can use a Freestyle project in Jenkins to qsub a job to the 
cluster. But if anything happens to Jenkins while the script is running in the 
cluster, you may lose that build and maybe have to connect to the cluster or 
look for it in the PBS queues in Jenkins.

Using the durable-task solution, or similar approaches, after Jenkins is 
restarted it would revive the job for us. Yesterday a researcher submitted a 
pull request [2] to make the Freestyle project to run as long as the PBS job is 
running in the cluster. 

I will try to write a prototype using some Jenkins+PBS durable solution and 
what he proposed too, and cut a new release by next weekend (though with the 
world cup that could take a few more days :-)

Bruno

[1] http://tupilabs.com/2014/06/13/durable-tasks-in-jenkins.html

[2] https://github.com/biouno/pbs-plugin/pull/2



 From: James Hetherington james...@gmail.com
To: jenkinsci-dev@googlegroups.com 
Sent: Thursday, June 12, 2014 9:38 AM
Subject: Re: Jenkins plugin for HPC job systems
 


I had a look at Bruno's plugin -- it looks like a great starting point for 
what we need.

I think generalising Bruno's PBS Java API to support other similar systems 
with qsub/qstat type commands should work well: it seems that a 
PBSSlaveComputer could be generalised into a BatchSystemSlave.


Regarding the problem of Jenkins going offline, my feeling would be to 
mitigate this risk by: (1) Warning and doing a qdel on all Jenkins-submitted 
jobs when Jenkins shuts down cleanly. (2) Warning and doing a qdel on all 
lingering Jenkins jobs when Jenkins comes back up after an unclean shutdown.


I don't think I understand the durable-task solution, as to me that sounds 
like one would not be able to move existing freestyle jobs back and forth 
between conventional nodes and batch system nodes... It seems to me that the 
right solution would be a new kind of slave node, rather than a new kind of 
job, though I'm happy to be corrected...





On Thu, Jun 12, 2014 at 1:29 AM, 'Bruno P. Kinoshita' via Jenkins Developers 
jenkinsci-dev@googlegroups.com wrote:

Hi Jesse,


I'm waiting for the workflow plugin but hadn't heard about the durable tasks 
plugin. 


The current implementation of the pbs plugin [1] was a POC to submit jobs via 
the qsub command to a PBS Torque server. In our tests a PBS job was triggered 
from a Freestyle project to the server via a SSH jump box in a university 
cluster. It is working and creating new jobs.


However, indeed if Jenkins goes offline the build stops running, even though 
the PBS job might still be running. I thought about re-using the 
monitor-external-job plug-in, but in some places qsub might be the only 
option to submit jobs.
 
I will experiment with the durable task plugin. Any advice on how to add 
items created in the cluster to the build queue in Jenkins? 


The current implementation creates a PBSSlaveComputer that represents a PBS 
Server. A Widget is created to retrieve the list of queues and its jobs from 
the server.


Thanks!
Bruno


[1] https://github.com/biouno/pbs-plugin




 From: Jesse Glick jgl...@cloudbees.com
To: jenkinsci-dev@googlegroups.com 
Sent: Wednesday, June 11, 2014 1:11 PM
Subject: Re: Jenkins plugin for HPC job systems
 

On Wed, Jun 11, 2014 at 10:05 AM, James Hetherington james...@gmail.com 
wrote:
 Is anyone aware of a plugin which already does this?

No but I have heard of someone interested in SGE support. My idea was
to implement the durable-task-plugin API, at which point any client of
that plugin can use the system (and Jenkins does not need to be
continuously running while the scheduling system runs your batch job).
Jenkins Enterprise by CloudBees has one such client, which looks and
feels like a freestyle project; the upcoming Workflow

Re: Jenkins plugin for HPC job systems

2014-06-11 Thread 'Bruno P. Kinoshita' via Jenkins Developers


Hi James

We have developed a pbs plugin, but it needs more work to be ready to 
production use.

Maybe we can collaborate? We have a pbs java api too. 

http://biouno.org

Bruno
--
Em qua, 11 de jun de 2014 11:05 BRT James Hetherington escreveu:

I am considering starting to write a Jenkins plugin to support the use of 
HPC job scheduler systems like SGE, LL and PBS.

Jobs currently queued in the batch system would show as pending jobs in the 
Jenkins UI.
Jobs would be qsubbed when they are requested to be built, and the job 
would transition to currently running when it runs on the scheduler

Configuration for the scheduler-based slave would specify the commands to 
be used for job submission, termination and status monitoring, with 
standard options for common queue systems, 
as well as SSH connection details to the login node of an HPC system.

I have two questions:

1. Is anyone aware of a plugin which already does this?
2. Would anyone be interested in collaborating on such a project?

-- 

  Dr James Hetherington,

Team Leader,   Honorary Lecturer
Research Software DevelopmentDepartment of Computer Science
Research IT Services
Information Services Division   Faculty of Engineering

University College London

Tel: 02035495164 (Int. 65164)
Mobile: 07946868834
Skype: ucgajhe
Twitter: @uclrcsoftdev
Blog: blogs.ucl.ac.uk/research-software-development/
Site: development.rc.ucl.ac.uk

-- 
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.
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.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins plugin for HPC job systems

2014-06-11 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hi Jesse,

I'm waiting for the workflow plugin but hadn't heard about the durable tasks 
plugin. 

The current implementation of the pbs plugin [1] was a POC to submit jobs via 
the qsub command to a PBS Torque server. In our tests a PBS job was triggered 
from a Freestyle project to the server via a SSH jump box in a university 
cluster. It is working and creating new jobs.

However, indeed if Jenkins goes offline the build stops running, even though 
the PBS job might still be running. I thought about re-using the 
monitor-external-job plug-in, but in some places qsub might be the only option 
to submit jobs.
 
I will experiment with the durable task plugin. Any advice on how to add items 
created in the cluster to the build queue in Jenkins? 

The current implementation creates a PBSSlaveComputer that represents a PBS 
Server. A Widget is created to retrieve the list of queues and its jobs from 
the server.

Thanks!
Bruno

[1] https://github.com/biouno/pbs-plugin



 From: Jesse Glick jgl...@cloudbees.com
To: jenkinsci-dev@googlegroups.com 
Sent: Wednesday, June 11, 2014 1:11 PM
Subject: Re: Jenkins plugin for HPC job systems
 

On Wed, Jun 11, 2014 at 10:05 AM, James Hetherington james...@gmail.com 
wrote:
 Is anyone aware of a plugin which already does this?

No but I have heard of someone interested in SGE support. My idea was
to implement the durable-task-plugin API, at which point any client of
that plugin can use the system (and Jenkins does not need to be
continuously running while the scheduling system runs your batch job).
Jenkins Enterprise by CloudBees has one such client, which looks and
feels like a freestyle project; the upcoming Workflow plugin suite has
another caller, which is used routinely for running forked commands
like shell scripts.


-- 
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.
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.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin release to wrong maven repo?

2014-05-28 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hi all, 

I had similar problem when releasing biouno plug-ins. Even though it uses a 
custom update center and maven repository, the problem was similar; my releases 
were going to the snapshot repository [1]. 

I think the solution so far has been changing the release-plugin version. In my 
case I changed a configuration in my git repository as in [2]. Apparently git 
changed the status message, what caused the release plugin to interpret my 
release as a snapshot - in my case. 

What I did in my git repositories for Java projects was:

`git config --add status.displayCommentPrefix true`

Not sure if it is the same issue that is happening for some plugins, but worth 
a shot in case you don't want to change your maven settings.

HTH,
Bruno

[1] http://jira.codehaus.org/browse/SCM-740

[2] http://ilikeorangutans.github.io/2014/04/29/maven-release-plugin-and-git-19



 From: Ulli Hafner ullrich.haf...@gmail.com
To: jenkinsci-dev@googlegroups.com 
Sent: Wednesday, May 28, 2014 12:44 PM
Subject: Re: Plugin release to wrong maven repo?
 


Add this to the build section of your log: 


          plugin
              groupIdorg.apache.maven.plugins/groupId
              artifactIdmaven-release-plugin/artifactId
              version2.5/version
              dependencies
                  dependency
                      groupIdorg.apache.maven.scm/groupId
                      artifactIdmaven-scm-provider-gitexe/artifactId
                      version1.9/version
                  /dependency
              /dependencies
          /plugin


PS: Please update the wiki if that works:-)
 
Am 28.05.2014 um 11:49 schrieb Cees Bos cbos...@gmail.com:

Hi Ulli,

Thanks for you quick response!
Based on the referred mail thread it is not clear to me what to change to 
publish it is in the right way. I am not that familiar with maven. 

Is there something I need to change in my pom.xml of settings.xml?
I am using maven 3.0.5.

Regards,
Cees




On Wed, May 28, 2014 at 11:30 AM, Ulli Hafner ullrich.haf...@gmail.com 
wrote:

You also hit the maven snapshot bug, seems that the wiki note  
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins needs to be more 
prominent…


See https://groups.google.com/forum/#!topic/jenkinsci-dev/qkmbl3HrYgk


Am 28.05.2014 um 10:51 schrieb Cees Bos cbos...@gmail.com:

Hi all,

I followed the steps on 
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins to release the 
send-stacktrace-to-eclipse-plugin.

As mentioned on the wiki page I did check 
http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/ to see if the 
plugin is there, but it is not.

This is what was published by the release process:



[INFO] Uploaded: 
http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/send-stacktrace-to-eclipse-plugin/1.5-SNAPSHOT/send-stacktrace-to-eclipse-plugin-1.5-20140528.083705-1-javadoc.jar
 (37 KB at 22.1 KB/sec)
[INFO] Uploading: 
http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/send-stacktrace-to-eclipse-plugin/1.5-SNAPSHOT/maven-metadata.xml
[INFO] 2/2 KB 
[INFO]  
[INFO] Uploaded: 
http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/send-stacktrace-to-eclipse-plugin/1.5-SNAPSHOT/maven-metadata.xml
 (2 KB at 1.4 KB/sec)


Maven build was successful.


It looks like it did publish the content to a different maven repository. 



The POM of my plugin can be found here.


Regards,

Cees


-- 
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.
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.
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.
For more options, visit https://groups.google.com/d/optout.

Re: Refreshing the Jenkins UI

2014-05-28 Thread 'Bruno P. Kinoshita' via Jenkins Developers

It would be great if there were some standard Javascript objects or a common 
API to access UI elements too. Something like below:

script type='text/javascript'
JUI().use('parameters', function (Y) {
    var parameters = J.jobParameters(); // this could return all the parameters 
present in the UI if any
    ...

    var select = parameters[0];
    var remoteObject = st:bind value=${it.getParametersProvider()}/
    select.setValue(remoteObject.getNewValues());
});
/script

Sometime ago we wrote a plugin that supports updating based on other job 
parameters. For adding parameter types from other plugins we have to a) check 
whether they use the taglibs or custom HTML elements, b) provide ways to 
retrieve values and c) update the values in the UI. 

I think having some kind of Jenkins javascript variables or standard objects 
would help this kind of plug-in that relies heavily on the UI.

Thanks
Bruno





 From: Jesse Glick jgl...@cloudbees.com
To: jenkinsci-dev@googlegroups.com 
Sent: Wednesday, May 28, 2014 5:49 PM
Subject: Re: Refreshing the Jenkins UI
 

On Wed, May 28, 2014 at 4:37 PM, Kohsuke Kawaguchi
kkawagu...@cloudbees.com wrote:
 This is also an area where plugin config files are shielded from the raw
 HTML tags through taglibs

Well, only insofar as they choose to use those taglibs. In most cases
they do, but there are some places
 where plugins add raw trs where
they expect to be inside a table.

 more dynamic content update in real time without page reloading.

It would be nice (especially if we can finally kill Auto Refresh!),
but you have to be very careful about the performance impact.
ajaxBuildQueue and ajaxExecutors already impose a significant burden
on the server when a lot of people are holding pages open. Anyone
proposing to add *more* AJAX stuff had better promise to fix the
performance of what is already there first. Being able to collapse
these widgets is fine but they are
 expanded by default and there is
currently no way to leave them expanded yet impose minimal overhead.

And the problem is that adding more dynamic updates in a modular way
(i.e., friendly to plugins) translates to a lot of separate HTTP
requests, and thus lots of overhead—unless you take care to define a
new API framework for “stuff that may be contributed by various
components and should be bundled in a periodic refresh when out of
date”, which is starting to sound like a crappy reimplementation of
Meteor.


-- 
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.
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.
For more options, visit https://groups.google.com/d/optout.

Re: Dynamic Parameter question

2014-05-19 Thread 'Bruno P. Kinoshita' via Jenkins Developers



Hi there! Chiming in.

I've updated the uno-choice Wiki, please take a look 
https://github.com/biouno/uno-choice-plugin/wiki

Ioannis, I believe you have the rights to edit the Wiki too, so feel free to 
add better examples or add/edit pages :) I added a few examples I had in my 
computer. 

Hope that helps
Bruno



 From: alok kumar alok.kuma...@gmail.com
To: jenkinsci-dev@googlegroups.com 
Sent: Monday, May 19, 2014 10:19 AM
Subject: Re: Dynamic Parameter question
 


Thanks. That would be of great help. I will wait for your mail 
On May 19, 2014 4:37 PM, Ioannis Moutsatsos imoutsat...@gmail.com wrote:

In the reference parameter option write a comma separated list of the form 
parameters you would like your script to use. Then use them as parameters in 
your script. I can provide some additional details when I get to work later 
today. 
On May 19, 2014 6:13 AM, alok kumar alok.kuma...@gmail.com wrote:

Hi Loannis,
Thanks for guiding me.
Can you please provide me an example groovy script meant to do this kind of 
work?
I am a little lost as I can even see any help icon for the way the script 
should be written using the other job parameters.


Thanks,
Alok

On Friday, 9 May 2014 23:08:31 UTC+5:30, Ioannis Moutsatsos  wrote:
I think that all the capability that you need is available to theuno-choice 
plugin developed by the BioUno project.


This plugin generates dynamic choice selections from a groovy script. You 
can use one or more parameters from the current Jenkins job form to 
parameterize the groovy script and it will update the list when on eof them 
changes (before submitting the build).
Finally, you can display the choices as a single or multi-select drop down 
list or as a checkbox or radio button options.


The plug-ins developed for BioUno are too niche-specific and thus aren’t 
released to Jenkins update center. In order to install the plug-ins you 
have to add the BioUno update center.

See here for instructions


Hope it helps.
Best regards
Ioannis

On Monday, May 5, 2014 11:05:32 AM UTC-4, alok kumar wrote:
Hi All,
We have a requirement in one of our Jenkins parameterized build project 
where we need to populate a selection of options in one parameter  based 
on the selection that was made before in another parameter i.e. 
dynamically populating the second parameter based on the first one.


What is the best way to do this? I need to have check boxes as options in 
the second parameter based on the selection of a single choice parameter 
in the first one.


E.g. say that we select car in the first parameter, I should get to choose 
from Ford, Toyota, Honda, Subaru, etc in the next parameter and that 
should be check boxes.


Is there a way to achieve this requirement? Also, how do we access the 
value of a parameter in a groovy script in another parameter?


Any help would be deeply appreciated.


Thanks in advance,
Alok
-- 
You received this message because you are subscribed to a topic in the 
Google Groups Jenkins Developers group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/jenkinsci-dev/3kfNtNr-4u4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
jenkinsci-dev+unsubscr...@googlegroups.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.
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.
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.
For more options, visit https://groups.google.com/d/optout.

Re: Dynamic Parameter question

2014-05-19 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hi Ioannis!

It was in my todo list too, as well as writing Javascript unit tests for the 
plug-in (still haven't learned how to properly do that :)

One feature that I think we can remove is the pattern for archived artifacts. I 
had a different idea of how to use that, but I think it is now not necessary. 
Feel free to add/update issues and we can work on them and cut a new release 
later this week.

Feel free to send suggestions too Alok, or let us know if there is anything 
missing/broken.

Cheers
Bruno



 From: Ioannis Moutsatsos imoutsat...@gmail.com
To: jenkinsci-dev@googlegroups.com 
Sent: Monday, May 19, 2014 1:07 PM
Subject: Re: Dynamic Parameter question
 


Hi Bruno;


The wiki looks pretty good now! I was planning helping with some examples but 
you beat me to it!
Anyway, I will try to write something that could be complementary to your 
documentation. 


I'm testing v 0.11 today. So far so good!


I also could get the image gallery to work with images from another project. 
So that's quite important!
Will send additional feedback by the end of the day.


Thanks and best regards
Ioannis



On Mon, May 19, 2014 at 10:24 AM, 'Bruno P. Kinoshita' via Jenkins Developers 
jenkinsci-dev@googlegroups.com wrote:



Hi there! Chiming in.


I've updated the uno-choice Wiki, please take a look 
https://github.com/biouno/uno-choice-plugin/wiki


Ioannis, I believe you have the rights to edit the Wiki too, so feel free to 
add better examples or add/edit pages :) I added a few examples I had in my 
computer. 


Hope that helps
Bruno




 From: alok kumar alok.kuma...@gmail.com
To: jenkinsci-dev@googlegroups.com 
Sent: Monday, May 19, 2014 10:19 AM
Subject: Re: Dynamic Parameter question
 


Thanks. That would be of great help. I will wait for your mail 
On May 19, 2014 4:37 PM, Ioannis Moutsatsos imoutsat...@gmail.com wrote:

In the reference parameter option write a comma separated list of the form 
parameters you would like your script to use. Then use them as parameters in 
your script. I can provide some additional details when I get to work later 
today. 
On May 19, 2014 6:13 AM, alok kumar alok.kuma...@gmail.com wrote:

Hi Loannis,
Thanks for guiding me.
Can you please provide me an example groovy script meant to do this kind 
of work?
I am a little lost as I can even see any help icon for the way the script 
should be written using the other job parameters.


Thanks,
Alok

On Friday, 9 May 2014 23:08:31 UTC+5:30, Ioannis Moutsatsos  wrote:
I think that all the capability that you need is available to 
theuno-choice plugin developed by the BioUno project.


This plugin generates dynamic choice selections from a groovy script. You 
can use one or more parameters from the current Jenkins job form to 
parameterize the groovy script and it will update the list when on eof 
them changes (before submitting the build).
Finally, you can display the choices as a single or multi-select drop 
down list or as a checkbox or radio button options.


The plug-ins developed for BioUno are too niche-specific and thus aren’t 
released to Jenkins update center. In order to install the plug-ins you 
have to add the BioUno update center.

See here for instructions


Hope it helps.
Best regards
Ioannis

On Monday, May 5, 2014 11:05:32 AM UTC-4, alok kumar wrote:
Hi All,
We have a requirement in one of our Jenkins parameterized build project 
where we need to populate a selection of options in one parameter  based 
on the selection that was made before in another parameter i.e. 
dynamically populating the second parameter based on the first one.


What is the best way to do this? I need to have check boxes as options 
in the second parameter based on the selection of a single choice 
parameter in the first one.


E.g. say that we select car in the first parameter, I should get to 
choose from Ford, Toyota, Honda, Subaru, etc in the next parameter and 
that should be check boxes.


Is there a way to achieve this requirement? Also, how do we access the 
value of a parameter in a groovy script in another parameter?


Any help would be deeply appreciated.


Thanks in advance,
Alok
-- 
You received this message because you are subscribed to a topic in the 
Google Groups Jenkins Developers group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/jenkinsci-dev/3kfNtNr-4u4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
jenkinsci-dev+unsubscr...@googlegroups.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.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Developers

Re: Dynamic Parameter question

2014-05-19 Thread 'Bruno P. Kinoshita' via Jenkins Developers

Hi

 1. Does this work only with the choice parameter? OR it can be used with the 
 extended choice, extensible choice, node label, etc parameters?


I have tested it with the choice parameter and the parameters from dynamic 
parameter plug-in. It shouldn't be had to include other parameters, but it 
isn't very elegant. The way it works, basically, is by navigating through 
Jenkins DOM (that is likely to be stable, specially with the new selenium tests 
that are being written) and extracting ${name}=${value}.

Give it a shot. If it doesn't work, file an issue at 
https://github.com/biouno/uno-choice-plugin/issues, provide as much info as 
possible (examples, use cases, code snippets, screen shots, etc) and we'll try 
our best to fix it for you. Or you can send a pull request as well ;)

 2, The way you have accessed the referenced variable i.e. 
 binding.variables.get(parameter) ? Is it always the same for all the 
 parameters mentioned above by me?


Yes, though if for example binding.variables.get(versionNumber) is not null, 
then you can treat it as a normal variable in your scripts (i.e.: 
artifactFinalName = myjar + versionNumber). 

Sorry for bothering too much, but, this is a real life saver plugin designed 
by you two :-) 

Never bothers at all, the more users/questions like these, the better the 
plug-in will be :-) 

Thank you!
Bruno



 From: alok kumar alok.kuma...@gmail.com
To: jenkinsci-dev@googlegroups.com 
Sent: Monday, May 19, 2014 2:03 PM
Subject: Re: Dynamic Parameter question
 


Hi Loannis and Bruno,
Thanks a lot for all the help and It did work the way you have shown in the 
example.
I have a couple of doubts here:


1. Does this work only with the choice parameter? OR it can be used with the 
extended choice, extensible choice, node label, etc parameters?
2, The way you have accessed the referenced variable i.e. 
binding.variables.get(parameter) ? Is it always the same for all the 
parameters mentioned above by me?


Sorry for bothering too much, but, this is a real life saver plugin designed 
by you two :-)


Thanks,
Alok



On Mon, May 19, 2014 at 9:51 PM, 'Bruno P. Kinoshita' via Jenkins Developers 
jenkinsci-dev@googlegroups.com wrote:

Hi Ioannis!


It was in my todo list too, as well as writing Javascript unit tests for the 
plug-in (still haven't learned how to properly do that :)


One feature that I think we can remove is the pattern for archived artifacts. 
I had a different idea of how to use that, but I think it is now not 
necessary. Feel free to add/update issues and we can work on them and cut a 
new release later this week.


Feel free to send suggestions too Alok, or let us know if there is anything 
missing/broken.


Cheers
Bruno




 From: Ioannis Moutsatsos imoutsat...@gmail.com
To: jenkinsci-dev@googlegroups.com 
Sent: Monday, May 19, 2014 1:07 PM

Subject: Re: Dynamic Parameter question



Hi Bruno;


The wiki looks pretty good now! I was planning helping with some examples 
but you beat me to it!
Anyway, I will try to write something that could be complementary to your 
documentation. 


I'm testing v 0.11 today. So far so good!


I also could get the image gallery to work with images from another project. 
So that's quite important!
Will send additional feedback by the end of the day.


Thanks and best regards
Ioannis



On Mon, May 19, 2014 at 10:24 AM, 'Bruno P. Kinoshita' via Jenkins 
Developers jenkinsci-dev@googlegroups.com wrote:



Hi there! Chiming in.


I've updated the uno-choice Wiki, please take a look 
https://github.com/biouno/uno-choice-plugin/wiki


Ioannis, I believe you have the rights to edit the Wiki too, so feel free 
to add better examples or add/edit pages :) I added a few examples I had in 
my computer. 


Hope that helps
Bruno




 From: alok kumar alok.kuma...@gmail.com
To: jenkinsci-dev@googlegroups.com 
Sent: Monday, May 19, 2014 10:19 AM
Subject: Re: Dynamic Parameter question
 


Thanks. That would be of great help. I will wait for your mail 
On May 19, 2014 4:37 PM, Ioannis Moutsatsos imoutsat...@gmail.com 
wrote:

In the reference parameter option write a comma separated list of the form 
parameters you would like your script to use. Then use them as parameters 
in your script. I can provide some additional details when I get to work 
later today. 
On May 19, 2014 6:13 AM, alok kumar alok.kuma...@gmail.com wrote:

Hi Loannis,
Thanks for guiding me.
Can you please provide me an example groovy script meant to do this kind 
of work?
I am a little lost as I can even see any help icon for the way the 
script should be written using the other job parameters.


Thanks,
Alok

On Friday, 9 May 2014 23:08:31 UTC+5:30, Ioannis Moutsatsos  wrote:
I think that all the capability that you need is available to 
theuno-choice plugin developed by the BioUno project.


This plugin generates dynamic choice selections from a groovy script. 
You can use

Re: Dynamically populate choice parameters (Cross posted to the jenkins-users)

2014-04-08 Thread Bruno P. Kinoshita

Hi Delbert

Another approach could be to call a groovy script and use:
https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Dynamic+Parameter+Plug-in

I think that's doable with a Groovy script and the dynamic-parameter plugin, 
unless one parameter depends on the value of other parameters e.g. you have a 
field groupId, and once it gets selected you'll want the artifactId field to 
get updated too with the new values, and subsequently with the version field 
after one artifact gets selected.

HTH
Bruno



 From: delbert dev delber...@gmail.com
To: jenkinsci-dev@googlegroups.com 
Sent: Tuesday, April 8, 2014 4:02 PM
Subject: Dynamically populate choice parameters (Cross posted to the 
jenkins-users)
 


I am looking either for an existing plugin or suggestion for writing my own 
plugin that will give me the following functionality:


On the job configuration page the user has access to one or more choice 
parameter drop-down menus. Now when the user clicks one of these drop-down 
boxes the values are dynamically populated by a list of strings.


I need the list of strings to be e.g versions from all artifacts in the 
snapshot repository in artifactory/nexus having the coordinates: 
groupId:artifactId:*.


Are there any plugins that allows generating dynamically values e.g from 
listing elements on a webserver?


I have looked at:
https://wiki.jenkins-ci.org/display/JENKINS/Extended+Choice+Parameter+plugin



Using this approach I would need to implement some logic that build a remote 
properties file. Another approach could be to call a groovy script and use:
https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Dynamic+Parameter+Plug-in





 Any other suggestions?
-- 
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.
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.
For more options, visit https://groups.google.com/d/optout.

Re: Script Security plugin

2014-03-31 Thread Bruno P. Kinoshita

Hi Jesse!

Thanks for the comments. I didn't think about using an AtomicReference, 
much better this way :)

I had copied the doCheckScript method from your sample pull request, 
but I didn't find a way to pass the sandbox parameter without adding some 
Javascript code to get its value. 

wrt the sandbox and configuring() method, do you think maybe changing the 
signature to include the sandbox as parameter and simply returning the 
script if sanbbox==true would help? This way plugin devs wouldn't have 
to remember to check the sandbox value.

Thanks again!
Bruno


 From: Jesse Glick jgl...@cloudbees.com
To: jenkinsci-dev@googlegroups.com 
Sent: Monday, March 31, 2014 11:44 AM
Subject: Re: Script Security plugin
 

On Fri, Mar 28, 2014 at 7:03 PM, Bruno P. Kinoshita
brunodepau...@yahoo.com.br wrote:
 https://github.com/Seitenbau/sb-jenkins-dynamicparameter/pull/28

I noted several mistakes in the usage of the various ScriptApproval
methods. I wonder if I need to make an easier-to-use wrapper object
for GroovyLanguage, basically a Describable containing a script and a
sandbox flag, which would have a stock config.jelly (including
help-sandbox.html and a doCheckScript method), and a constructor and
some other methods that calls the right things at the right times. The
downside is that this would not be serialization-compatible with
current describable classes which have a direct script field; they
would need to have a readResolve method that converts the inline
script into this wrapper. I will think about it though.

 feel free to massage the text as needed

I did.

 I added a custom Runnable to store the result of the
 script execution, since the plug-in uses it to create the dynamic parameters
 (or was there an easier way?)

An overload taking Callable could be added as a convenience. (You can
use an inline Runnable class and an AtomicReference for more concise
code using the current API, BTW.)


-- 
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.
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.
For more options, visit https://groups.google.com/d/optout.

Re: Script Security plugin

2014-03-28 Thread Bruno P. Kinoshita

Here's my try at integrating the security plug-in with the dynamic parameter 
plug-in. 

https://github.com/Seitenbau/sb-jenkins-dynamicparameter/pull/28


- After I integrated the Script Security Plugin many of the existing tests 
started to fail with NPE. I modified 
the tests to work with the script approval and updated the Wiki [1] (ps: feel 
free to massage the text as needed)

- Do you think it would be possible and make sense to use an object with some 
return value in the GroovySandbox too [2]? 
Like Callable, and we use Void when not returning anything. I added a custom 
Runnable to store the result of the 
script execution, since the plug-in uses it to create the dynamic parameters 
(or was there an easier way?)

I had to peek at the code to understand the preapprove and configuring methods 
and 
had a quick look at the rest of the code. It all looks nice and works as 
expected. Kudos 
and many thanks! 

Cheers, 

[1] 
https://wiki.jenkins-ci.org/pages/diffpages.action?pageId=71436691originalId=72417559
[2] 
https://github.com/Seitenbau/sb-jenkins-dynamicparameter/pull/28/files#diff-70f42f03a5626274410da1b61f8726a6R142

 
Bruno P. Kinoshita 
http://kinoshita.eti.br 
http://tupilabs.com



 From: Jesse Glick jgl...@cloudbees.com
To: jenkinsci-dev@googlegroups.com 
Sent: Thursday, March 13, 2014 5:41 PM
Subject: Re: Script Security plugin
 

On Thu, Mar 13, 2014 at 4:02 PM, Bruno P. Kinoshita
brunodepau...@yahoo.com.br wrote:
 I'll have to write a plug-in (or extend the extended choice parameter
 plugin) that will use Groovy.

There is already one in this area that would benefit from a
script-security integration:

https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Dynamic+Parameter+Plug-in


-- 
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.
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.
For more options, visit https://groups.google.com/d/optout.

Re: Opensourcing a plugin under a different github org

2014-03-24 Thread Bruno P. Kinoshita

I believe it is, the Dynamic Parameter seems to be hosted elsewhere 
https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Dynamic+Parameter+Plug-in
 
HTH

Bruno


 From: Surya Gaddipati suryapraka...@gmail.com
To: jenkinsci-dev@googlegroups.com 
Sent: Monday, March 24, 2014 3:04 PM
Subject: Opensourcing a plugin under a different github org
 


My employer is interested in opensourcing a plugin that we developed in house. 
But we would like our plugin to be under github org not jenkins-ci ( for 
obvious reasons) . 


Is it possible to make plugin  show up in the default jenkins update center?
-- 
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.
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.
For more options, visit https://groups.google.com/d/optout.

Re: Script Security plugin

2014-03-13 Thread Bruno P. Kinoshita

I'll have to write a plug-in (or extend the extended choice parameter plugin) 
that will use Groovy. I'll take a look at the devs reference and maybe will try 
to use it.

But my +1 for the proposal, really liked the sandbox and approval queue ideas.

Cheers
Bruno



 From: Jesse Glick jgl...@cloudbees.com
To: jenkinsci-dev@googlegroups.com 
Sent: Wednesday, March 12, 2014 7:45 PM
Subject: Script Security plugin
 

I am working on a new plugin

https://github.com/jenkinsci/script-security-plugin

which allows other plugins with scripts (usually Groovy) to run those
in a secured fashion. The wiki

https://wiki.jenkins-ci.org/display/JENKINS/Script+Security+Plugin

has details. People who are working on Groovy-based plugins (e.g.
job-dsl) should consider trying to integrate with it. Comments on the
API are welcomed.

(I realized too late that I should have started with version 0.1, not
1.0-beta-1, since API changes may still be needed.)

-- 
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.
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.
For more options, visit https://groups.google.com/d/optout.

Re: batch-task-plugin question

2014-03-03 Thread Bruno P. Kinoshita


Hi Jesper, I have a similar case in one project. But we use the promote plugin.

We have different types of promotions, like promote to QA.

These promotions can happen automatically or manually.

Hope that helps
Bruno

--
Em seg, 3 de mar de 2014 12:17 BRT Jesper Eskilson escreveu:

Hi,

I have a particular use-case which I'm not sure how to approach. We have a 
production build environment which runs every night. I would like to be 
able to define certain actions (e.g. release) on each build which the 
user should be able to execute (manually). Ideally, I'd like to have a 
Release button on the status page for each build, possibly with some 
additional configuration parameters for the external script.

As I understand it there are at least three options available:

1. Use the batch-task-plugin. The problem here is that the 
batch-task-plugin only seem to be able to execute the task on the project 
itself. There does not seem to be a way to specify which build to execute 
the task for.
2. Extend the batch-task plugin. 
3. Write my own plugin. 

Any ideas about how I should proceed? Are there any other plugins which 
might already do this?


-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Jenkins Translation Plugin

2013-12-20 Thread Bruno P. Kinoshita

Hi Bruno!

As far as I know, that plug-ins sends user contributions to a server, and then 
these contribs are later added to the project.

In the Sao Paulo meetup (7th December) Kohsuke joined us for our Hackathon. 
There, Fernando Boaglio became a committer and coordinated the translation 
team. He committed his changes shortly after the event [1]

In the past Boaglio also posted to the pt_BR mailing list some ideas for the 
pt_BR translation process [2]. He standardized upper/lower case and added a 
list of words that should not be translated to avoid confusion (such as 
Build/Construção) [3]. 

Feel free to send your contributions, but it may be a good idea to catch up 
with him on IRC or in one of the mailing lists and check if you can perhaps 
work together :^) 

Hope that helps, 

[1] 
https://github.com/jenkinsci/jenkins/commit/587992c3725d43899c80160bd1178b764af9b371
[2] https://groups.google.com/forum/#!topic/jenkinsci-br/nW-sP-RTauE

[3] https://wiki.jenkins-ci.org/display/JENKINS/Brazilian+Portuguese+Translation
 
Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com



 From: Bruno Kühnen Meneguello br...@meneguello.com
To: Jenkins CI - Developers jenkinsci-dev@googlegroups.com 
Sent: Friday, December 20, 2013 6:42 PM
Subject: Jenkins Translation Plugin
 

Hello,

I want to know how Jenkins Translation Plugin works (on server side) and 
offer my name to review and integrate Portuguese (brasilian) 
translations for core and plugins.

Thanks

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.




-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Is Jenkins the leading Opens Source CI? Usage Statistics vs Other Continuous Integration Systems

2013-12-09 Thread Bruno P. Kinoshita

Hi Ioannis, 

I think someone posted some link or doc with Jenkins usage here in the mailing 
list. I tried finding it but without success. Someone may have added this info 
to the Wiki, so you may want to take another look in the mailing list (if you 
haven't already) and in the Wiki. 

There are some surveys like [1] and [2], but maybe you'll have to investigate 
how they conducted these surveys.

I work in the BioUno project along with a bioinformatics researcher. We 
presented some BioUno plug-ins last Saturday during the Sao Paulo Jenkins 
Meetup [3]. Let me know if you need anything :^) 

Do you know if you'll be allowed to share your final paper online, or if there 
are any limitations set by the publisher/journal? 

Thanks!

[1] 
http://zeroturnaround.com/rebellabs/devprod-report-revisited-continuous-integration-servers-in-2013/
[2] http://www.cloudbees.com/jenkins/jenkins-ci/2012-survey.cb
[3] http://www.meetup.com/jenkinsmeetup/events/133598002/

Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com



 From: Ioannis Moutsatsos imoutsat...@gmail.com
To: jenkinsci-dev@googlegroups.com 
Sent: Monday, December 9, 2013 5:09 PM
Subject: Is Jenkins the leading Opens Source CI? Usage Statistics vs Other 
Continuous Integration Systems
 


Is anyone aware of any statistics comparing usage or used installations of 
Jenkins CI compared to other similar systems?


I'm writing a paper for a scientific publication and I would like to 
support/reference my claim that Jenkins is the leading open source continuous 
integration server.
If you are interested you can take a look at the motivation behind this 
publication here


Thanks and best regards
--Ioannis--


-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.




-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Connecting unix slaves through a tunnel

2013-10-24 Thread Bruno P. Kinoshita

Hi Alok!

Not sure if there's some way of connecting slaves like you want :o( but I need 
something similar for submitting jobs to a PBS cluster from Jenkins - I have 
SSH access to one machine from which I can SSH connect to all other nodes. 
Probably I will use something like the https://github.com/xebialabs/overthere 
XebiaLabs library. 

If you find no other way to add a slave via a jump station in Jenkins, maybe 
you could file a RFE issue in JIRA. For now, I think you can execute something 
like ssh -L local_port:remote_host:remote_port 
your_user@gateway_machine (off the top of my head)

This way you could connect to the slave via the local_port you designated. 

HTH, 

Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com



 From: alok kumar alok.kuma...@gmail.com
To: jenkinsci-us...@googlegroups.com; jenkinsci-dev@googlegroups.com 
Sent: Thursday, October 24, 2013 1:33 PM
Subject: Connecting unix slaves through a tunnel
 


Hi All,
I have a set of unix build machines which need to be used as jenkins slaves. 
They include linux, solaris, HPUX, AIX, etc.

Now, the only way to connect to those machines is using SSH through a 
designated machine.

So, how is it possible to make these machines jenkins slaves as I cannot 
connect to them via SSH directly from the master?

Is there a way to achieve this using gateway or some kind of tunnelling?

Is there any plugin that can be used to achieve this requirement?

Any help would be greatly appreciated.

Thanks,
Alok







-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.




-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Tapping into Test Results

2013-10-04 Thread Bruno P. Kinoshita

I've had to adapt the tap-plugin [1] to display TAP test results in Jenkins, 
mimicking the JUnit test results. Perhaps taking a look at the code will help 
you in some way.

[1] https://github.com/jenkinsci/tap-plugin

Hope that helps, 

Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com


From: teilo teilo+goo...@teilo.net
To: jenkinsci-dev@googlegroups.com 
Cc: cletusdso...@hotmail.com 
Sent: Friday, October 4, 2013 1:26 PM
Subject: Re: Tapping into Test Results



I don't think there is anything documented as this is done via plugin 
extensions.
if you grabbed all source from githun (including plugins) you could grep for 
extends AbstractTestResultAction and that may give you an idea (but I'm not 
sure that the ones that exist are open source.


The prefixes (I believe) need to be unique for the different types. The one I 
am working on at the moment is cucumber and I hope to be able to open source 
it shortly.

/James

On Friday, 4 October 2013 16:50:58 UTC+1, Cletus D'Souza  wrote:
Good to know that there will be more than just junit test results.  Where can I 
find a list of these test types documented?  Will the test id contain a 
different prefix (ex: junit/ for junit tests)?
 
Thanks!
Cletus

 

 Date: Thu, 3 Oct 2013 14:47:13 -0700
 From: teilo+...@teilo.net
 To: jenkin...@googlegroups.com
 Subject: RE: Tapping into Test Results
 
 eep in mind that not all test results are of the junit type.  You may be 
 able to get all this information with the test.* classes
 
 GetFailedTests is broken so you would likely want to getResult and take Avon 
 depending on the type if object returned
 
 -- 
 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.
 For more options, visit https://groups.google.com/ groups/opt_out.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Problems with ISA SERVER

2013-09-12 Thread Bruno P. Kinoshita

Hi Jose, 

I have a Jenkins instance behind a ISA server too. In my case, the server is 
running in a Linux/Red Hat, and we've installed cntlm [1]. The authentication 
to the proxy is done via cntlm, and then in Jenkins I simply configure the 
proxy as localhost:3128.

Hope that helps, 

[1] http://cntlm.sourceforge.net/

Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com



From: Jose Diaz jamdiazd...@gmail.com
To: jenkinsci-dev@googlegroups.com 
Sent: Thursday, September 12, 2013 12:33 PM
Subject: Problems with ISA SERVER



Hello Guys.

I am some days trapped in it issue.

In my company we have an ISA SERVER.

I am configuring the information of my proxy in the tab ( manage plugins - 
advanced configuration ).

The problem is that i got error 502 when try to install a plugin.

The ISA Server register a request of anonymous user. Why?  if I am sending the 
information of username/password too.

Some idea?

Jose
-- 
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.
For more options, visit https://groups.google.com/groups/opt_out. 

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: New release of NUnit Plug-in and merge PR

2013-08-05 Thread Bruno P. Kinoshita

Bump? :) 

Already released TAP plug-in, now in the works to release CCM and TestLink, but 
I could release NUnit plug-in too, if there're no objections.

Bruno

 From: Bruno P. Kinoshita brunodepau...@yahoo.com.br
To: jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com 
Sent: Monday, July 1, 2013 3:06 PM
Subject: New release of NUnit Plug-in and merge PR

Hi

I have a pending pull request [1] for NUnit Plug-in [2], that fixes 
JENKINS-9965 [3], and would like to see if it can be merged and released. 

I've tried to contact the plug-in maintainer via his @java.net (on June 20th) 
and @gmail account (on June 26, last weekend), but got no response so far. 
Does anybody know if the plug-in is still being maintained? 

I'm planning to cut new releases of TAP, CCM, Testopia and TestLink plug-ins 
in the next days, and would like to volunteer to cut a new release of NUnit 
plug-in, if there is no objection.

Thank you in advance!

Bruno

[1] https://github.com/jenkinsci/nunit-plugin/pull/5
[2] https://wiki.jenkins-ci.org/display/JENKINS/NUnit+Plugin
[3] https://issues.jenkins-ci.org/browse/JENKINS-9965

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Three months, and I am still waiting for my pull request

2013-07-10 Thread Bruno P. Kinoshita

Hi Louis, 

My bad, I'm ccm maintainer. I've been busy with other projects and couldn't 
find time to review issues/PR's in Jenkins plug-ins.

I'll review your pull request and merge/comment it today and will cut a new 
release today or tomorrow. How does that sound to you? :)

All the best, 
 
Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com



 From: Louis Henry Nayegon louis.henry.naye...@gmail.com
To: jenkinsci-dev@googlegroups.com 
Sent: Wednesday, July 10, 2013 7:28 AM
Subject: Three months, and I am still waiting for my pull request
 


Hi,
 
Having just read this 
https://wiki.jenkins-ci.org/display/JENKINS/Pull+Request+to+Repositories I 
though it was about time I got in contact with someone.
 
I have been waiting months for this pull request
 
https://github.com/jenkinsci/ccm-plugin/pull/1
 
The change is quite simple and I would of though it would be released by now.
 
What can I do ?
 
Regards
Louis
-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 




-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: subversion plugin development

2013-07-02 Thread Bruno P. Kinoshita

Bonjour Nicolas, 

Doing a git clone + mvn hpi:run I get the same results in 
http://host:port/pluginManager/installed. I think the 1.26 version is 
bundled with Jenkins 1.466 (parent in the subversion-plugin pom.xml).

Here's a quick hack. Not sure if the best way of doing this (@anyboby feel free 
to chime in if you know a better way):

 mvn clean hpi:run
 stop Jenkins
 mvn clean package
 rm work/plugins/subversion* -rf
 cp target/subversion.hpi work/plugins/subversion.hpi
 touch work/plugins/subversion.hpi.pinned
 mvn clean hpi:run 

At least here after doing these steps, in 
http://host:port/pluginManager/installed the version displayed changed to 
1.51-SNAPSHOT (private-07/02/2013 13:19-kinow)

Hope that helps, 

Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com



 From: nicolas de loof nicolas.del...@gmail.com
To: jenkinsci-dev@googlegroups.com 
Sent: Tuesday, July 2, 2013 11:35 AM
Subject: subversion plugin development
 


I'm running mvn hpi:run on subversion plugin expecting I can do some quick 
test on a bug fix, but I always get the war-packaged 1.26 subversion plugin 
installed, even there's a pinned file generated. What's wrong ?
-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 


 

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Request for sonargraph-plugin componet creation in JIRA

2013-05-03 Thread Bruno P. Kinoshita

Hi Esteban, 
What is the JIRA user ID of the default assignee? 
Cheers

Bruno P. Kinoshita

http://kinoshita.eti.br

http://tupilabs.com

--- Em sex, 3/5/13, Esteban Angee esteban.an...@hello2morrow.com escreveu:

De: Esteban Angee esteban.an...@hello2morrow.com
Assunto: Request for sonargraph-plugin componet creation in JIRA
Para: jenkinsci-dev@googlegroups.com
Data: Sexta-feira, 3 de Maio de 2013, 11:03


  


  
  
Hello,



We are releasing sonargraph-plugin (

https://github.com/jenkinsci/sonargraph-plugin)
soon. We kindly request the creation of a JIRA component for our
plugin Issue Tracking. 



Cheers,

-- 
Esteban Angee Agudelo
Software Engineer
hello2morrow S.A.S
(574)5804555
esteban.an...@hello2morrow.com
http://www.hello2morrow.com
  




-- 

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.

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

 

 

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Request for sonargraph-plugin componet creation in JIRA

2013-05-03 Thread Bruno P. Kinoshita

Hi Esteban, 
Component sonargraph created - 
https://issues.jenkins-ci.org/browse/JENKINS/component/17620
Cheers

Bruno P. Kinoshita

http://kinoshita.eti.br

http://tupilabs.com

--- Em sex, 3/5/13, Esteban Angee esteban.an...@hello2morrow.com escreveu:

De: Esteban Angee esteban.an...@hello2morrow.com
Assunto: Re: Request for sonargraph-plugin componet creation in JIRA
Para: jenkinsci-dev@googlegroups.com
Data: Sexta-feira, 3 de Maio de 2013, 12:23


  


  
  
Hi Bruno,



The ID for the default assignee is esteban_h2m



Kind regards,





On 05/03/2013 09:36 AM, Bruno P.
  Kinoshita wrote:



  

  
Hi Esteban, 
  

  
  What is the JIRA user ID
  of the default assignee? 
  


  Cheers



Bruno P. Kinoshita


  http://kinoshita.eti.br


  http://tupilabs.com



--- Em sex,
  3/5/13, Esteban Angee esteban.an...@hello2morrow.com 
escreveu:



  De: Esteban Angee
  esteban.an...@hello2morrow.com

  Assunto: Request for sonargraph-plugin componet
  creation in JIRA

  Para: jenkinsci-dev@googlegroups.com

  Data: Sexta-feira, 3 de Maio de 2013, 11:03

  

  
 Hello,

  

  We are releasing sonargraph-plugin ( 
https://github.com/jenkinsci/sonargraph-plugin)
  soon. We kindly request the creation of a JIRA
  component for our plugin Issue Tracking. 

  

  Cheers,

  -- 
Esteban Angee Agudelo
Software Engineer
hello2morrow S.A.S
(574)5804555
esteban.an...@hello2morrow.com
http://www.hello2morrow.com

-- 

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.

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

 

 

  

  

  

  
  -- 

  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.

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

   

   




-- 
Esteban Angee Agudelo
Software Engineer
hello2morrow S.A.S
(574)5804555
esteban.an...@hello2morrow.com
http://www.hello2morrow.com
  




-- 

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.

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

 

 

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: What about a Composer plugin?

2013-04-26 Thread Bruno P. Kinoshita

Hi Renan, 
I've already added Composer to my CodeIgniter project and am now getting my 
feet wet with packagist, composer, eclipse+composer, etc.
I'll keep an eye on the repository and will create a branch to send some code 
too.
 Just a note, I will be back to the office in July. That's all I can do for 
now. I will give more effective feedbacks when I come back, anyway... it's 
done, we have a mission.
Enjoy your vacation. As we say in Brazil: missão dada é missão cumprida :) 
(mission given is mission accomplished).

Thanks!

Bruno P. Kinoshita

http://kinoshita.eti.br

http://tupilabs.com

--- Em sex, 26/4/13, Renan de Lima renandel...@gmail.com escreveu:

De: Renan de Lima renandel...@gmail.com
Assunto: Re: What about a Composer plugin?
Para: jenkinsci-dev@googlegroups.com
Data: Sexta-feira, 26 de Abril de 2013, 21:08

Bruno,
I've created https://github.com/renanbr/composer-plugin repository. You are 
collaborator =)Next week some people will start coding, they also have access 
to manage pull request.


I'll ping composer-dev group about what we are doing.
Just a note, I will be back to the office in July. That's all I can do for now. 
I will give more effective feedbacks when I come back, anyway... it's done, we 
have a mission.


thanks
--
Renan de Lima Barbosa


On 25 April 2013 16:01, Bruno P. Kinoshita brunodepau...@yahoo.com.br wrote:


Hello, 


Before talk about Composer, some words about build.xml. Actually we are moving 
from Phing to Ant for some reasons:    - Ant makes projects more pluggable 
for IDEs, CI Servers... (less shell)

    - Ant is recommended in http://jenkins-php.org    - Ant is faster than 
 Phing
    - Ant parallel task is stable, Phing task is not
What do you think about this?
ATM I'm using Ant as it's easier for me - I use Java and Maven or Ivy+Ant for 
most of my projects.


I only thought about Phing because I found its Eclipse plugin in the same 
update site of Composer plug-in [1].


 If possible, I would like to know more about your migration project and how 
 you are planning this.
My current project is a website that uses Continuous Integration + Continuous 
Delivery with 

Ant + Rsync. We're adding applications (mobile apps, facebook, etc) and we'll 
need to add a few dependencies to this project. 


So far, the way we did this was by unzipping the PHP libraries to the CI 
application/libraries folder. What is not the more elegant solution, but works. 
Now we are working to create a 

REST API and add these libraries with Composer. 
One alternative is migrating from CI to FuelPHP, so we could drop TankAuth 
authentication 

library in favor of FuelPHP's bundled auth library, and use REST controllers 
provided by FuelPHP (no library needed for this too). 


One thing that I would like to see
 in this plug-in, is looking at my job and being able to spot all the 
dependencies (name/version) used in Composer.


 It's my first contact with Jenkins CI Community. I don't know how plugins  
 life cycle works neither how mature the idea must be to start coding. We 

 have a laboratory sector to try some contexts as well. I have some Java  
 skilled guys in my DevOps team, we can help when possible.

 Ready to go! Just waiting your signal to start.
I believe
 there is no plug-in for this, and a lot of PHP users would like to use it. If 
you create a GitHub repository to work on this plug-in, you can send me the 
link and I'll take a look to see if I can help you guys.


Once the code is stable enough, we can ask here to fork the repository, create 
theWiki page + JIRA component for this new plug-in and prepare for the initial 
release. 


How does that sound to you?
Cheers, 


[1]
 http://p2.dubture.com/
Bruno P. Kinoshita

http://kinoshita.eti.br

http://tupilabs.com

--- Em qui, 25/4/13, Renan de Lima renandel...@gmail.com escreveu:



De: Renan de Lima renandel...@gmail.com


Assunto: Re: What about a Composer plugin?
Para: jenkinsci-dev@googlegroups.com
Data: Quinta-feira, 25 de Abril de 2013, 9:03



Hi there,

I'm migrating a few projects from CodeIgniter (+bunch of libraries and sparks) 
to FuelPHP and to CodeIgniter+Composer, and am having to learn Composer. 

 Is there any activity
 to integrate Composer and Jenkins?Not that I'm aware of. Is there a better 
way to use Composer through Jenkins?In my todo-list, right next to Composer is 
Phing. I haven't had time to read all the docs about Composer, but I want to 
understand if you have to run composer or if you can call it in phing scripts. 
What do you think?


Before talk about Composer, some words about build.xml. Actually we are moving 
from Phing to Ant for some reasons:    - Ant makes projects more pluggable for 
IDEs, CI Servers... (less shell)


    - Ant is recommended in http://jenkins-php.org    - Ant is faster than 
Phing    - Ant parallel task is stable, Phing task is not


What do you think about this?
Getting back to Composer plugin... We are planning two kinds of job for every 
project:
    - build

Re: What about a Composer plugin?

2013-04-25 Thread Bruno P. Kinoshita

Hello, 
Before talk about Composer, some words about build.xml. Actually we are moving 
from Phing to Ant for some reasons:    - Ant makes projects more pluggable 
for IDEs, CI Servers... (less shell)    - Ant is recommended in 
http://jenkins-php.org    - Ant is faster than Phing    - Ant parallel task 
is stable, Phing task is notWhat do you think about this?
ATM I'm using Ant as it's easier for me - I use Java and Maven or Ivy+Ant for 
most of my projects.
I only thought about Phing because I found its Eclipse plugin in the same 
update site of Composer plug-in [1].
 If possible, I would like to know more about your migration project and how 
 you are planning this.
My current project is a website that uses Continuous Integration + Continuous 
Delivery with Ant + Rsync. We're adding applications (mobile apps, facebook, 
etc) and we'll need to add a few dependencies to this project. 
So far, the way we did this was by unzipping the PHP libraries to the CI 
application/libraries folder. What is not the more elegant solution, but works. 
Now we are working to create a REST API and add these libraries with Composer. 
One alternative is migrating from CI to FuelPHP, so we could drop TankAuth 
authentication library in favor of FuelPHP's bundled auth library, and use REST 
controllers provided by FuelPHP (no library needed for this too). 
One thing that I would like to see in this plug-in, is looking at my job and 
being able to spot all the dependencies (name/version) used in Composer.
 It's my first contact with Jenkins CI Community. I don't know how plugins  
 life cycle works neither how mature the idea must be to start coding. We  
 have a laboratory sector to try some contexts as well. I have some Java  
 skilled guys in my DevOps team, we can help when possible. Ready to go! 
 Just waiting your signal to start.
I believe there is no plug-in for this, and a lot of PHP users would like to 
use it. If you create a GitHub repository to work on this plug-in, you can send 
me the link and I'll take a look to see if I can help you guys.
Once the code is stable enough, we can ask here to fork the repository, create 
theWiki page + JIRA component for this new plug-in and prepare for the initial 
release. 
How does that sound to you?
Cheers, 
[1] http://p2.dubture.com/
Bruno P. Kinoshita

http://kinoshita.eti.br

http://tupilabs.com

--- Em qui, 25/4/13, Renan de Lima renandel...@gmail.com escreveu:

De: Renan de Lima renandel...@gmail.com
Assunto: Re: What about a Composer plugin?
Para: jenkinsci-dev@googlegroups.com
Data: Quinta-feira, 25 de Abril de 2013, 9:03

Hi there,

I'm migrating a few projects from CodeIgniter (+bunch of libraries and sparks) 
to FuelPHP and to CodeIgniter+Composer, and am having to learn Composer.  Is 
there any activity to integrate Composer and Jenkins?Not that I'm aware of. Is 
there a better way to use Composer through Jenkins?In my todo-list, right next 
to Composer is Phing. I haven't had time to read all the docs about Composer, 
but I want to understand if you have to run composer or if you can call it in 
phing scripts. What do you think?
Before talk about Composer, some words about build.xml. Actually we are moving 
from Phing to Ant for some reasons:    - Ant makes projects more pluggable for 
IDEs, CI Servers... (less shell)
    - Ant is recommended in http://jenkins-php.org    - Ant is faster than 
Phing    - Ant parallel task is stable, Phing task is not
What do you think about this?
Getting back to Composer plugin... We are planning two kinds of job for every 
project:
    - build-job: for every project development line (trunk, branches...). This 
job executes quality checks as described in http://jenkins-php.org It also 
generates tags;
    - deploy-job: one per project, it sends files of a package version to the 
web servers.
For build-job, Composer is necessary to get dependencies before to run 
Ant/Phing build.xml (http://getcomposer.org/doc/ 03-cli.md#install and 
http://getcomposer.org/doc/03- cli.md#update). Here is the reason of Invoke 
Composer.

Note: every project is plugged in a private repository 
(https://github.com/composer/ satis and https://github.com/composer/ 
packagist). So it's possible get projects from there by require/require-dev 
entry in a composer.json file or create-project command 
(http://getcomposer.org/doc/ 03-cli.md#create-project).

For deploy-job, users must pick up a version to deploy. We need use List 
Composer Package Versions (http://getcomposer.org/doc/ 03-cli.md#show) to send 
version value as argument to create-project command using Invoke Composer 
before send it to the servers.

In short I am willing to run Composer *before* 
Ant/Phing scripts in build-job, and *before* send files to the servers 
in deploy-job.

If possible, I would like to know more about your migration project and how you 
are planning this.

Do you think that suggestions is useful for community?Definitely. I can help 
writing the plug-in, and can test

Re: What about a Composer plugin?

2013-04-24 Thread Bruno P. Kinoshita

Hi Renan, 

I'm migrating a few projects from CodeIgniter (+bunch of libraries and sparks) 
to FuelPHP and to CodeIgniter+Composer, and am having to learn Composer. 

 Is there any activity to integrate Composer and Jenkins?

Not that I'm aware of.

 Is there a better way to use Composer through Jenkins?

In my todo-list, right next to Composer is Phing. I haven't had time to read 
all the docs about Composer, but I want to understand if you have to run 
composer or if you can call it in phing scripts. What do you think?

Do you think that suggestions is useful for community?

Definitely. I can help writing the plug-in, and can test it while I migrate my 
projects.

Thanks!

Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com

--- Em qua, 24/4/13, Renan de Lima renandel...@gmail.com escreveu:

De: Renan de Lima renandel...@gmail.com
Assunto: What about a Composer plugin?
Para: jenkinsci-dev@googlegroups.com
Cc: edgar...@gmail.com
Data: Quarta-feira, 24 de Abril de 2013, 9:14

Hello all,

I use Jenkins at work for PHP projects. We are 
starting adopt Composer in our systems cycle life. Unfortunately I've 
not seen any integration between Composer and Jenkins CI.

For my organization we need basically two features:



1. Invoke Composer [build step]

Arguments:
- php path (optional, defaults to /usr/bin/env php)
- composer path (optional, defaults to /usr/bin/env composer or a built-in 
composer executable)


- command (required... install/update/create-project/ validate... see 
https://getcomposer.org/doc/ 03-cli.md )
- options (free text to send to command line)


2. List Composer Package Versions [parameter]


Arguments:
- php path (optional, defaults to /usr/bin/env php)
- composer path (optional, defaults to /usr/bin/env composer or a built-in 
composer executable)
- package name (required)


- stability (some checkboxes that users can pick: dev, alpha, beta, RC and/or 
stable, see https://getcomposer.org/doc/ 04-schema.md#minimum-stability )



So then...

Is there any activity to integrate Composer and Jenkins?
Is there a better way to use Composer through Jenkins?
Do you think that suggestions is useful for community?

thanks,

Renan de Lima

just a note, I don't know if it's necessary... Composer is a dependency manager 
for PHP http://getcomposer.org/







-- 

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.

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

 

 


-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: When should I mark a JIRA issue as Resolved?

2013-03-03 Thread Bruno P. Kinoshita

Usually I let the bot mark the issue as Resolved (with the [FIXED JENKINS-] 
commit log). 

Then when the plug-in is released and I see it either in the update center or 
in the twitter bot, I change the issue status to Closed with the message Fixed 
in 9.99 version.

HTH, 

Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com



 From: Mark Waite markwa...@yahoo.com
To: jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com 
Sent: Saturday, March 2, 2013 9:55 AM
Subject: When should I mark a JIRA issue as Resolved?
 

Is there a general policy or guideline related to when I should resolve an 
issue which has been reported in JIRA?


It seems there is a robot that resolves issues when certain text is detected 
in git commit messages.  I think that indicates the general policy is to 
resolve issues when the fix is submitted, not when the fix has been released 
in an official build.


I just reopened an issue because the fix seems to require updates to two 
different plugins.  One of the plugins has been released with the fix, while 
the other has not yet released a version which includes the fix.  I compiled a 
local copy of the unreleased plugin, installed it, and confirmed that the 
issue is resolved with the unreleased version of the plugin.


Based on the robot behavior of resolving the issue when the change is 
submitted, I think that means I should mark the issue as resolved since the 
necessary changes are in the source code to fix the issue and users will 
receive the fix with the next release of the plugin.  Is that the expectation?


Thanks,
Mark Waite
-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 


 

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Did support for writing Groovy plugins ever happen?

2013-02-22 Thread Bruno P. Kinoshita

Hi there, 


I think Job DSL Plug-in [1] has some groovy scripts and Java classes too. 

[1] https://github.com/jenkinsci/job-dsl-plugin

HTH,
 
Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com


- Original Message -
 From: R. Tyler Croy ty...@monkeypox.org
 To: jenkinsci-dev@googlegroups.com
 Cc: 
 Sent: Friday, February 22, 2013 12:09 PM
 Subject: Re: Did support for writing Groovy plugins ever happen?
 
 
 On Wed, 20 Feb 2013, Jesse Glick wrote:
 
  On 02/20/2013 06:33 AM, R. Tyler Croy wrote:
  I'm wondering if support for actually writing plugins fully in 
 Groovy was ever built?
 
  AFAIK you can just create src/main/groovy/**/*.groovy and start coding.
 
  The one problem I know of is that Groovy does not implement JSR 269
  [1] so indexed annotations (especially @Extension) will be ignored.
  The workaround would be to use src/main/java/**/*.java to write
  ?entry points? but implement all the real logic in Groovy files.
 
  Stapler views may be written in Groovy (src/main/resources/**/*.groovy 
 rather than src/main/resources/**/*.jelly).
 
 
 You don't happen to know of any plugins to emulate or mimic, which are 
 already
 full-on Groovy?
 
 
 - R. Tyler Croy
 --
     Code: https://github.com/rtyler
 Chatter: https://twitter.com/agentdero
 

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Advice on developing HA solution

2013-01-23 Thread Bruno P. Kinoshita

Morning Mikael!

We have been working on a bioinformatics solution with Jenkins [1]. We are 
working to connect Jenkins with a PBS server. Similar to what is done with the 
EC2 plug-in, however, we are working to connect Jenkins build queue to PBS job 
queue. 

Our goal is provide a PBS Project, and let users submit jobs (or simply build 
steps) to PBS servers without having to write PBS scripts (this would be done 
via a plug-in). 

The PBS server and the job scheduler (either the native one or Maui) would then 
schedule the jobs/buildsteps to one of the PBS nodes. 

The jobs are handled in the PBS server by a job queue, similar to the build 
queue in Jenkins. We are now working to include the pbs jobs in the Jenkins 
build queue.

This way, if you had a very long build step, like finding contigs in 
shotgun DNA sequences using some NGS program, you could schedule a job in 
Jenkins but run this long task in the PBS cluster and be notified once the 
program has finished.

Just 0.02 cents to your research :o) All the best,

[1] biouno.org

Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com



 From: Mikael Stockman mekkarmikk...@gmail.com
To: jenkinsci-dev@googlegroups.com 
Sent: Wednesday, January 23, 2013 6:55 AM
Subject: Advice on developing HA solution
 

Hi!
We are two thesis workers who have been assigned the task of investigating
possible high availability solutions for Jenkins.


We are aware of Cloudbees and their HA plugin, but the company that we are 
working
for is looking for a solution where two jenkins masters can run 
simultaneously, and 
possibly share the load between each other.
The desired solution would not need the user to be aware of that there are 
several
Jenkins instances, but it should look like one Jenkins from the users 
perspective.
It is not necessary that the Jenkins instances share JENKINS_HOME.


We have been thinking about different possible ways to achieve this. But 
writing a plugin
seems promising. However there may be other solutions such as a plugin working 
with an external
program, or possibly an entirely external solution.


If anyone has has been working with this, we would be very happy to hear your
thoughts.


Also, we could really benefit from some advice on what to look out for, and 
what can cause problems.


Actually any input on this topic will be valuable to us.


Thanks in advance!


Best regards
Mikael and Daniel

Re: Advice on developing HA solution

2013-01-23 Thread Bruno P. Kinoshita

Hi Andrew! 

That PBS plugin looks *amazing*. I have access to a sizable (~4000 core) PBS 
cluster and was debating asking for an upgrade to my jenkins box, but it looks 
like I can just farm out my long-running build tasks to the cluster :)


That's the idea :o) I have _partial_ access to a small PBS cluster with 32 
nodes/8 core each, where I've tried submitting jobs with MPI and OpenMP. 

The PBS plug-in [1] is still under development and needs some adjustments. The 
researcher member of BioUno is relocating from Sao Paulo to New Orleans, so I'm 
waiting for him to continue the work on BioUno.

But let me know if you are would like to try the plug-in. I could do some final 
adjustments and send you a packaged hpi file, probably before or during 
Carnival in February.

Cheers

[1] https://github.com/tupilabs/pbs-plugin

Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com



 From: Andrew Melo andrew.m...@gmail.com
To: jenkinsci-dev@googlegroups.com 
Sent: Wednesday, January 23, 2013 2:33 PM
Subject: Re: Advice on developing HA solution
 

Hi bruno


On Wed, Jan 23, 2013 at 3:53 AM, Bruno P. Kinoshita 
brunodepau...@yahoo.com.br wrote:

Morning Mikael!

We have been working on a bioinformatics solution with Jenkins [1]. We are 
working to connect Jenkins with a PBS server. Similar to what is done with 
the EC2 plug-in, however, we are working to connect Jenkins build queue to 
PBS job queue. 

Our goal is provide a PBS Project, and let users submit jobs (or simply build 
steps) to PBS servers without having to write PBS scripts (this would be done 
via a plug-in). 

The PBS server and the job scheduler (either the native one or Maui) would 
then schedule the jobs/buildsteps to one of the PBS nodes. 

The jobs are handled in the PBS server by a job queue, similar to the build 
queue in Jenkins. We are now working to include the pbs jobs in the Jenkins 
build queue.

This way, if you had a very long build step, like finding contigs in 
shotgun DNA sequences using some NGS program, you could schedule a job in 
Jenkins but run this long task in the PBS cluster and be notified once the 
program has finished.

Just 0.02 cents to your research :o) All the best,



That PBS plugin looks *amazing*. I have access to a sizable (~4000 core) PBS 
cluster and was debating asking for an upgrade to my jenkins box, but it looks 
like I can just farm out my long-running build tasks to the cluster :)


-Andrew
 

[1] biouno.org

Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com



 From: Mikael Stockman mekkarmikk...@gmail.com
To: jenkinsci-dev@googlegroups.com
Sent: Wednesday, January 23, 2013 6:55 AM
Subject: Advice on developing HA solution



Hi!
We are two thesis workers who have been assigned the task of investigating
possible high availability solutions for Jenkins.


We are aware of Cloudbees and their HA plugin, but the company that we are 
working
for is looking for a solution where two jenkins masters can run 
simultaneously, and 
possibly share the load between each other.
The desired solution would not need the user to be aware of that there are 
several
Jenkins instances, but it should look like one Jenkins from the users 
perspective.
It is not necessary that the Jenkins instances share JENKINS_HOME.


We have been thinking about different possible ways to achieve this. But 
writing a plugin
seems promising. However there may be other solutions such as a plugin 
working with an external
program, or possibly an entirely external solution.


If anyone has has been working with this, we would be very happy to hear your
thoughts.


Also, we could really benefit from some advice on what to look out for, and 
what can cause problems.


Actually any input on this topic will be valuable to us.


Thanks in advance!


Best regards
Mikael and Daniel

 




-- 
--
Andrew Melo

Re: Jenkins selenium page object framework

2012-11-26 Thread Bruno P. Kinoshita

+1, I'd like to add more tests to some of the plug-ins I maintain :o) 

Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com

- Original Message -
 From: Kohsuke Kawaguchi k...@kohsuke.org
 To: Richard Lavoie lavoie.rich...@gmail.com; Jenkins Dev 
 jenkinsci-dev@googlegroups.com
 Cc: 
 Sent: Monday, November 26, 2012 10:38 PM
 Subject: Re: Jenkins selenium page object framework

 Hi,

 Moving this conversations to jenkinsci-dev@googlegroups.com.

 Yes, what you are talking about is [1], which is an attempt to define 
 blackbox 
 acceptance tests in a way that lets us test our final deliverables (rpm, deb, 
 etc.) It contains the page objects, among other things.

 I think having a java library that defines page objects for Jenkins is 
 useful. 
 Go for it!

 You might be also interested in [2], which creates handles in the form input 
 fields that simplifies the XPath-based selection of the right target node.

 There's also a conversation of adding another functionality (either in this 
 plugin or another one) that exposes Groovy scripting console in a way that 
 lets 
 you verify side-effects that happen on the server more easily.

 And then maybe it's possible to run selenium-tests in JRuby so that we can 
 run some Java-based selenium tests in the same environment, which allows you 
 to 
 leverage pluggable layers in the selenium-tests and VirtualBox integrations.

 [1] https://github.com/jenkinsci/selenium-tests
 [2] https://wiki.jenkins-ci.org/display/JENKINS/Form+Element+Path+Plugin

 On 11/20/2012 06:23 PM, Richard Lavoie wrote:
  Hey Kohsuke,

  I'll be starting the work of a framework based on selenium page object
  design pattern.

  I know you are doing something similar (in ruby or python afaik) with
  rtyler to test jenkins itself but I thought it would be nice to have the
  same thing in java for those who'd want to be able to test form fill 
 and
  actions in their plugins.

  Let me know what you think about it.

  --
  Richard Lavoie
  IT consultant / consultant en informatique

 -- Kohsuke Kawaguchi                          http://kohsuke.org/

Re: New Jira component for lotus connections plugin

2012-11-18 Thread Bruno P. Kinoshita

Hi Phil, 

I was going to create it for you, but looks like it has already been created :-)

https://issues.jenkins-ci.org/browse/JENKINS/component/17221

Component: lotus-connections
Lead: Phil Rumble

Cheers, 

Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com



 From: Phil Rumble philrum...@hotmail.com
To: jenkinsci-dev@googlegroups.com 
Sent: Monday, November 19, 2012 12:54 AM
Subject: Re: New Jira component for lotus connections plugin
 

Anyone?? 

How can I create a new JIRA component for the the lotus connections plugin?



On Thu, Nov 8, 2012 at 12:41 PM, Phil Rumble philrum...@hotmail.com wrote:

Hi,

a jira component for my lotus connections plugin would be very useful (for 
bug reports and feature requests), can anyone please add it?


my jira username: philrumble
plugin id: lotus-connections-plugin


Have  Fun,

Phil

Re: Installations statistics?

2012-11-05 Thread Bruno P. Kinoshita

I've also noticed this. The latest file from jenkins-ci.org/census is 
201208.json.gz, with the stats from September/2012. 

Cheers,
 
Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com


- Original Message -
 From: Christian Wolfgang c...@praqma.net
 To: jenkinsci-dev@googlegroups.com
 Cc: 
 Sent: Monday, 5 November 2012 10:54 AM
 Subject: Installations statistics?
 
 Hi.
 
 What happened to the installations statistics for the plugins? They
 kinda stuck in August!
 
 Br.
 Christian

Re: readonly textarea

2012-10-31 Thread Bruno P. Kinoshita

Hi @slide, 

I think this has been fixed in 1.477 [1]. Try bumping your parent version to 
1.477 or superior and check if that works :o)

[1] https://github.com/jenkinsci/jenkins/commit/d0dbd3b8525287cf1fce51c7639b50a4f55520b0#L5R84

Cheers, 

Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com



 From: Slide slide.o@gmail.com
To: jenkinsci-dev@googlegroups.com 
Sent: Wednesday, 31 October 2012 2:04 PM
Subject: readonly textarea
 

I have something like the following in one of my config.jelly files for my 
plugin, but it doesn't seem to actually create the 'readonly' attribute for 
the textarea. I looked at the taglib and it sets readonly to 
$(attrs.readonly}, so I am not sure why it is not working.


f:textarea name=... readonly=${!hasPermission ? 'readonly' : ''}/


Am I just doing it completely wrong?


Thanks!


slide


-- 
Website: http://earl-of-code.com

Re: readonly textarea

2012-10-31 Thread Bruno P. Kinoshita

I see, I think the next LTS is based on 1.480, and should be out soon. 

Cheers


Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com



 From: Slide slide.o@gmail.com
To: jenkinsci-dev@googlegroups.com 
Sent: Wednesday, 31 October 2012 5:50 PM
Subject: Re: readonly textarea
 




On Wed, Oct 31, 2012 at 12:34 PM, Bruno P. Kinoshita 
brunodepau...@yahoo.com.br wrote:

Hi @slide, 

I think this has been fixed in 1.477 [1]. Try bumping your parent version to 
1.477 or superior and check if that works :o)

[1] https://github.com/jenkinsci/jenkins/commit/d0dbd3b8525287cf1fce51c7639b50a4f55520b0#L5R84

Cheers, 

Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com





Bummer, I keep my plugin on the latest LTS as much as possible which is 1.466. 
I've have to do something else.


Thanks,


slide


 

 From: Slide slide.o@gmail.com
To: jenkinsci-dev@googlegroups.com
Sent: Wednesday, 31 October 2012 2:04 PM
Subject: readonly textarea



I have something like the following in one of my config.jelly files for my 
plugin, but it doesn't seem to actually create the 'readonly' attribute for 
the textarea. I looked at the taglib and it sets readonly to 
$(attrs.readonly}, so I am not sure why it is not working.


f:textarea name=... readonly=${!hasPermission ? 'readonly' : ''}/


Am I just doing it completely wrong?


Thanks!


slide


--
Website: http://earl-of-code.com


 




-- 
Website: http://earl-of-code.com

[jclouds plugin] Wrong SCM link in Wiki

2012-10-28 Thread Bruno P. Kinoshita

Hi all, 

I'm writing a new plug-in based on jclouds, and noticed that the SCM (GitHub) 
link in the plug-in Wiki is broken.

Instead of https://github.com/jenkinsci/jclouds-plugin, it is 
displaying https://github.com/jenkinsci/jclouds-jenkins-plugin

The SCM entry is right in the plug-in pom.xml, so I believe the Wiki macro 
concatenates the GitHub prefix + plugin-id + plugin. But the id of the 
plug-in (jclouds-jenkins) is different than the repository name in GitHub 
(jclouds-plugin).

BTW, thanks for jclouds :o) the plug-in I'm writing has nothing to do with 
cloud computing, but I can take most of what I need from this plug-in.

Cheers, 
 
Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com

Re: Unable to test Jenkins plugin

2012-10-23 Thread Bruno P. Kinoshita

Hi Dimitri, 

But I have some questions. In my company, we mostly use maven 2.2.1 for 
building our project. If I create my plugin with the latest version,
will there be compatibility problems? 

If you are building the plug-in in your company, using 2.2.1, so you may have 
problems (though it's been a while since I last used maven 2.2.1 to develop 
plug-ins, or build projects in Jenkins). 

If you are building the plug-in with maven 3.0.4, and only installing in your 
Jenkins, then you can use it with jobs using any maven version.

Hope that helps, 

Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com



 From: Dimitri CHARLES charles2000dimi...@gmail.com
To: jenkinsci-dev@googlegroups.com 
Cc: Bruno P. Kinoshita brunodepau...@yahoo.com.br 
Sent: Tuesday, 23 October 2012 12:38 PM
Subject: Re: Unable to test Jenkins plugin
 

Hi, thanks for your answer. 


I went to test it with maven 3.0.4 and he works. Thanks for your guidance. 


But I have some questions. In my company, we mostly use maven 2.2.1 for 
building our project. If I create my plugin with the latest version,
will there be compatibility problems? 


Dimitri

Le mardi 23 octobre 2012 02:19:46 UTC+2, kinow a écrit :
Hi Dimitri, 
I created a plug-in last week I think, and run mvn hpi:run and it worked fine 
(it was using 1.466 too).
But my Maven is 3.0.4. There are some special settings for Maven 2.x in the 
plug-in tutorial, but could you consider updating your Maven to 3.0.4, maybe 
installing both, and giving it a try? 
If you are not able to run the plug-in with Maven 3.0.4, then we can further 
investigate this issue. What do you think? 
Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com

_ ___
 From: Dimitri CHARLES charles20...@gmail.com
To: jenkin...@googlegroups.com 
Sent: Monday, 22 October 2012 9:45 PM
Subject: Re: Unable to test Jenkins plugin
 

I forgot to say that I am using 
Maven 2.2.1
Jenkins 1.466

Le mardi 23 octobre 2012 01:32:58 UTC+2, Dimitri CHARLES a écrit :
I am actually trying to develop a Jenkins plugin using maven but I am unable 
to test it.
I created my project with the command mvn -cpu hpi:create. I called 
the project jenkins-plugin-tutorial. I packaged it with mvn package or mvn 
install and run the Jenkins server with mvn hpi:run.
By default, there is a HelloWorlBuilder for testing purpose that should 
appear at the Jenkins configuration page (Jenkins Menu - Manage Jenkins - 
Configure System) or under the Build section, but it does not display.
I followed these two tutorials (here and here) step by step many times by 
making sure that I do not make a mistake but it still dont work.
Maybe I have made something wrong. Can somebody gives me some hint how to 
correct my errors.

Re: Unable to test Jenkins plugin

2012-10-22 Thread Bruno P. Kinoshita

Hi Dimitri, 

I created a plug-in last week I think, and run mvn hpi:run and it worked fine 
(it was using 1.466 too).

But my Maven is 3.0.4. There are some special settings for Maven 2.x in the 
plug-in tutorial, but could you consider updating your Maven to 3.0.4, maybe 
installing both, and giving it a try? 

If you are not able to run the plug-in with Maven 3.0.4, then we can further 
investigate this issue. What do you think? 

Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com



 From: Dimitri CHARLES charles2000dimi...@gmail.com
To: jenkinsci-dev@googlegroups.com 
Sent: Monday, 22 October 2012 9:45 PM
Subject: Re: Unable to test Jenkins plugin
 

I forgot to say that I am using 
Maven 2.2.1
Jenkins 1.466

Le mardi 23 octobre 2012 01:32:58 UTC+2, Dimitri CHARLES a écrit :
I am actually trying to develop a Jenkins plugin using maven but I am unable 
to test it.
I created my project with the command mvn -cpu hpi:create. I called 
the project jenkins-plugin-tutorial. I packaged it with mvn package or mvn 
install and run the Jenkins server with mvn hpi:run.
By default, there is a HelloWorlBuilder for testing purpose that should 
appear at the Jenkins configuration page (Jenkins Menu - Manage Jenkins - 
Configure System) or under the Build section, but it does not display.
I followed these two tutorials (here and here) step by step many times by 
making sure that I do not make a mistake but it still dont work.
Maybe I have made something wrong. Can somebody gives me some hint how to 
correct my errors.

Re: Track history of an individual testcase

2012-10-17 Thread Bruno P. Kinoshita

Here's a quick (and dirty) groovy script for that

https://gist.github.com/3906161

I wrote it in some spare time after lunch, but I think it may help you on 
writing an 
Groovy script for that. If you write a better version, I would like to see it 
in the Scriptler 
plug-in scripts repository.

The HistoryResult class is not really necessary. I started writing with this 
class and forgot to remove it. And the output (a sample at the bottom 
of the script) is ugly. Probably you'll want to use some formatter or output to 
a HTML file.

Hope that helps, just my 0.02 cents :-)

ps: You'll notice that I wrote it for a junit-and-tap project. This project 
contains both TAP and 
JUnit results. This script works only for the junit test results. But it's very 
easy to add support 
to TAP too.

Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com



 From: Christopher Orr ch...@orr.me.uk
To: jenkinsci-dev@googlegroups.com 
Sent: Wednesday, 17 October 2012 9:45 AM
Subject: Re: Track history of an individual testcase
 
Yeah, that certainly sounds useful.

A quick possibility could be to write a Groovy script (and contribute it 
to the jenkins-scripts repo) which takes a job name and a test name, 
and then loops through all builds, printing out a basic list containing 
build number, and test status for each.

Chris


On 16/10/12 15:25, Bruno P. Kinoshita wrote:
 Hi Björn,

 I don't know if a plug-in for this already exists or not, but I think it
 doesn't and it sounds like a good idea :)

 You could use a Recorder [1], and iterate through the past builds
 (perhaps a depth option here would be a good idea). You can then use the
 following (not tested) to retrieve the tests in a Build*:

      ListAbstractTestResultAction actionsWithTests =
 build.getActions(AbstractTestResultAction.class);
      for(AbstractTestResultAction? leAction : actionsWithTests) {
          TestResult testResult = (TestResult)leAction.getResult(); // if
 instanceof...
          // look for certain test status, and report it
      }

 Hope that helps,

 [1] http://javadoc.jenkins-ci.org/?hudson/tasks/Recorder.html
 * Depending on the plug-in, you may have to use other classes, junit and
 tap plugin adds a AbstractTestResultAction. I believe TestNG has a
 custom build action with test results.
 Bruno P. Kinoshita
 http://kinoshita.eti.br
 http://tupilabs.com

     
     *From:* Björn Julander julander.bj...@gmail.com
     *To:* jenkinsci-dev@googlegroups.com
     *Sent:* Tuesday, 16 October 2012 6:38 AM
     *Subject:* Track history of an individual testcase

     I'm looking for the feature of getting a history of an individual
     test case, does such already exist?

     Motivation: I have a Unit testcase that failed in the last run.
     I have a suspicion that it might be an intermittent failure and
     would like
     to investigate that. Today I can only click manually through each build
     which is time consuming and don't give me an overview.

     What I would like to do is to click on the testcase and see it's
     history for each run,
     preferable with a summary of the other test cases.

     I assume this doesn't exist (or please point me in the right direction).
     I have not developet a jenkins plugin before, can you give me some
     pointers
     on where one should hook in such a feature.
     I guess there should be some good existing extension point for this,
     but which one?

     Any tips in any direction is hightly appreciated!

     Thanks // Björn

Re: http://www.reddit.com/r/jenkinsci/

2012-09-21 Thread Bruno P. Kinoshita

Hi Lisa! Great idea.

+1 to using reddit, and +1 to adding a section on the jenkins-ci.org with 
r/jenkinsci posts


Cheers

Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com



 From: Lisa lwe...@cloudbees.com
To: jenkinsci-dev@googlegroups.com 
Sent: Friday, 21 September 2012 5:07 PM
Subject: http://www.reddit.com/r/jenkinsci/
 

Hi,

I've been posting Jenkins related links to Reddit Jenkins community that Tyler 
created some time ago. I think this is more live than the
current news section in Wiki 
(https://wiki.jenkins-ci.org/display/JENKINS/Home), and
lately I noticed a few more people started posting links, so I wanted to
encourage the community to both post and subscribe to it as a  convenient
way to get updated on what's going on with Jenkins.

And I also wonder what people think about adding adding a
section on the http://jenkins-ci.org/ blog
page that shows the recent /r/jenkinsci postings, to improve visibility?
Cheers,
Lisa Wells, CloudBees

Re: http://www.reddit.com/r/jenkinsci/

2012-09-21 Thread Bruno P. Kinoshita



Hi, 

I recently worked on a web site with a requirement of displaying the right 
image on FaceBook. When you share a page in facebook, it tries to get the 
website image from the following html meta tag: 

meta property=og:image content=http://url/images/icon-facebook.gif; / 

There are other meta tags used too (check Open Graph [1] for more), like: 


meta property=og:title content=bla bla / 
meta property=og:site_name content=bla bla bla / 

I think there are other meta tags that were (or still are) used too, but these 
seem to work.

If these tags are not available, FB tries to get some images available in the 
page, but sometimes it misses one or two images. I shared 
www.reddit.com/r/jenkinsci, and although I could select different images, the 
Jenkins logo wasn't available. 


I took a look at a subreddit where I'm moderator to see if there was something 
in the settings, but couldn't find anything to include these meta tags. 


So here's a (dirty) trick for changing the image that is displayed on Facebook: 


- Go to FaceBook and paste http://www.jenkins-ci.org (or a web site with 
image/tags that you want to display)

- Wait for FaceBook to load the images from the website and select  the butler 
headshot (or one of your preference)

- Delete the web site address and now paste the right content
- Post it


You can also create a web page somewhere with the right OpenGraph tags for 
displaying the description/content/url etc, pointing to the post in 
r/jenkinsci. It's dirty and ugly, but it works :-/


Hope that helps, 

[1] http://ogp.me/

Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com



 From: Lisa Wells lwe...@cloudbees.com
To: jenkinsci-dev@googlegroups.com 
Cc: Bruno P. Kinoshita brunodepau...@yahoo.com.br 
Sent: Friday, 21 September 2012 7:16 PM
Subject: Re: http://www.reddit.com/r/jenkinsci/
 

The JFrog image appears to come up whenever jenkins-ci.org is cited.  I posted 
this link and it still has the JFrog image:
http://jenkins-ci.org/content/come-join-jenkins-user-conference-san-francisco-september-30th

Maybe Reddit is pulling from the sponsor logos on the blog page?
L


On Fri, Sep 21, 2012 at 5:08 PM, Kohsuke Kawaguchi kkawagu...@cloudbees.com 
wrote:

On 09/21/2012 01:11 PM, Bruno P. Kinoshita wrote:

Hi Lisa! Great idea.

+1 to using reddit, and +1 to adding a section on the jenkins-ci.org with 
r/jenkinsci posts


I have a suspicion that rtyler had set up some kind of automatic reddit posting 
from @jenkinsci. I'm how he did it.

The other thing I noticed is that posts like [1] gets JFrog logo as the 
image. I'm a fan of what they do and all, but is there any way we can 
convince Reddit to pick up a Jenkins logo as the default image?


[1] 
http://www.reddit.com/r/jenkinsci/comments/yy0vv/volunteers_needed_for_juc_sf/
-- 
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Nectar, our professional version of Jenkins



-- 

Lisa Wells
Marketing Bee 
www.CloudBees.com  |  Blog.CloudBees.com  | +1 512.751.8423  |  
@productprincipl

1 2 >

1 - 100 of 129 matches

Mail list logo