Re: performance labs

2015-10-01 Thread Andrew Bayer
...and I can most likely provide builds.apache.org's jobs/builds/load/etc
as a use case.

A.

On Thu, Oct 1, 2015 at 9:54 AM, Andrew Bayer  wrote:

> +1 - that'd be fantastic. I'd love to help with that.
>
> A.
>
> On Thu, Oct 1, 2015 at 4:50 AM, Michael Neale 
> wrote:
>
>> Hey all - I have thought it would be a great idea to have some quasi
>> formal "performance lab" setups for Jenkins.
>>
>> Recently around Jenkins 2.0 planning threads there have been lots of
>> comments around performance challenges. Often things like launch time
>> (talking many minutes to an hour for large workspaces - launch times are
>> probably a good proxy for a whole lot of issues, but there are other issues
>> too).
>>
>> At JUC west there was an excellent talk by Akshay Dayal from Google, on
>> scaling jenkins. I highly recommend flicking through the slides
>> 
>> or watching the talk
>> 
>> if you have time.
>>
>> Basically, they had some performance goals and started by setting up
>> measurements and test scenarios to validate their progress - both around
>> scalability of slaves (an interesting issue) but also on bootup time (time
>> to recovery) which is very interesting. It reminded me that to improve
>> something like this you kind of need easily repeatable measurements in
>> controlled environments, which currently I don't think the Jenkins project
>> has set up? (correct me if wrong).
>>
>> I know Stephen Connolly did some work a few years back on slave
>> scalability which was interesting (building out a test suite
>> infrastructure), but I am not aware of subsequent efforts.
>>
>> Is this something people would be interested in?
>>
>> Having either large sample JENKINS_HOME specimens or test code that can
>> generate pathological data would be required, as well as automation around
>> running it on a variety of machines (not necessarily cloud, ideally want to
>> be testing code not cloud infrastructure).
>>
>>
>> --
>> 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/76a12929-8f10-4b50-bf01-04cc77768149%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/CAPbPdOYAiBEDObK2HkzNhWdc-Ehm9UY-%2B1%2B4LYOYHcDHLifPhw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: performance labs

2015-10-01 Thread Andrew Bayer
+1 - that'd be fantastic. I'd love to help with that.

A.

On Thu, Oct 1, 2015 at 4:50 AM, Michael Neale 
wrote:

> Hey all - I have thought it would be a great idea to have some quasi
> formal "performance lab" setups for Jenkins.
>
> Recently around Jenkins 2.0 planning threads there have been lots of
> comments around performance challenges. Often things like launch time
> (talking many minutes to an hour for large workspaces - launch times are
> probably a good proxy for a whole lot of issues, but there are other issues
> too).
>
> At JUC west there was an excellent talk by Akshay Dayal from Google, on
> scaling jenkins. I highly recommend flicking through the slides
> 
> or watching the talk
> 
> if you have time.
>
> Basically, they had some performance goals and started by setting up
> measurements and test scenarios to validate their progress - both around
> scalability of slaves (an interesting issue) but also on bootup time (time
> to recovery) which is very interesting. It reminded me that to improve
> something like this you kind of need easily repeatable measurements in
> controlled environments, which currently I don't think the Jenkins project
> has set up? (correct me if wrong).
>
> I know Stephen Connolly did some work a few years back on slave
> scalability which was interesting (building out a test suite
> infrastructure), but I am not aware of subsequent efforts.
>
> Is this something people would be interested in?
>
> Having either large sample JENKINS_HOME specimens or test code that can
> generate pathological data would be required, as well as automation around
> running it on a variety of machines (not necessarily cloud, ideally want to
> be testing code not cloud infrastructure).
>
>
> --
> 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/76a12929-8f10-4b50-bf01-04cc77768149%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/CAPbPdOaLf62SY2gR7c-fzudi6yT44wvtnj2rhFCGJ1UEtGng3Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins Plugin Install Wizard - check out the progress (video) ...

2015-10-01 Thread Daniel Beck

On 30.09.2015, at 08:30, Victor Martinez  wrote:

> On the other hand, if the security is one of the important pieces then any 
> Builder might be affected easily since AFAIK they don't run in any sandbox 
> therefore you might run "rm -rf /" and change the restriction label as 
> "master". Does it mean "Shell plugin" (I know it's part of the core) is 
> unsecured? If so, does it mean any other plugins which are using it are also 
> unsecured? And that's an example of bypassing the "security layout". Don't 
> get me wrong, I do like the idea of adding value to Jenkins with this wizard 
> feature, but what I don't like is the way of filtering plugins which are 
> useful IMO.

(Accidentally sent this to Victor directly)

It's possible to secure an instance well enough from this by e.g. setting the 
number of executors on master to 0. Another option would be plugins that limit 
what can be built where using the QueueTaskDispatcher extension point. Sure, 
users can still wreak havoc on slaves, but that's probably less of an issue 
than having unrestricted access to JENKINS_HOME.

Regarding the plugin criteria, it looked like a good idea to not surprise users 
by including plugins that make any security configuration they may configure 
irrelevant. Maybe I'm wrong about this and nobody cares (but then I wonder why 
Role Strategy is so popular, complex security setups that are too painful doing 
with matrix-auth is the one thing it does). So if there are others who think 
that plugins undermining an admin-defined security setup should be allowed into 
the wizard, please say so.

-- 
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/E7360758-4A6F-430D-B913-DE6FE633040D%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.


Re: Post-build Actions on Jobs executed on slaves

2015-10-01 Thread Paul Wellner Bou
Hi,

thanks, seems to work now, with MasterToSlaveCallable, on master and slave
as well. I just have to take care that all objects I need are serializable.

Regards
Paul.

On Thu, Oct 1, 2015 at 12:01 PM Paul Wellner Bou  wrote:

> Thank you for the reply.
>
> I am using a Publisher extending Publisher.
>
> This looks promising. I discovered a stackoverflow thread with a bit of
> code doing  a smiliar thing (
> http://stackoverflow.com/questions/9279898/can-hudson-slaves-run-plugins).
>
> Whats the difference between launcher.getChannel().call(task); and
> build.getWorkspace().act(task)? The JavaDoc of the latter looks promising.
>
> What I am wondering now, is which Caller to use. There is a
> FilePath.FileCallable, where the JavaDoc says "Subtypes would likely want
> to extend from either {@link MasterToSlaveCallable}* or {@link
> SlaveToMasterFileCallable}."
>
> I would use MasterToSlaveCallable now, does this work on the master then
> as well? Or do I have to detect somehow if I am running on a master or a
> slave?
>
> Thank you very much,
> Paul.
>
>
>
> On Thu, Oct 1, 2015 at 10:38 AM Ullrich Hafner 
> wrote:
>
>> Are you referring to an action that implements the Action interface? Or
>> to a post build publisher that derives from Recorder or Publisher?
>>
>> The latter one can execute Runnables on a slave, e.g. to read information
>> from the workspace. See FilePath#act for details...
>>
>> Am 01.10.2015 um 08:25 schrieb Paul Wellner Bou :
>>
>> Good morning,
>>
>> I have a build job checking out a git repository running on a jenkins
>> slave, which works fine. But I am trying to access the workspace in an
>> Post-build Action plugin, which does not seem to be possible: The
>> Post-build Action is run on the master (at least thats what the
>> System.getenv("HOSTNAME") is telling me.
>>
>> Is there any way to run the Post-build Actions on the slave?
>>
>> Thank you and regards
>> Paul.
>>
>>
>> --
>>
>> 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/fe2bda4d-a374-4b04-b720-5702c4586e2b%40googlegroups.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/NwNN-HnnI8Q/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/jenkinsci-dev/9A91F3C4-F8DA-4D10-9693-77AF5ADF7B35%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/CAMDwiY_Oz1SgyfwUOW_%2BsdX05Um8sdpKnUKYMOeQa_DUN%2BjhrA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Plugin Hosting Request: Parallels Desktop Cloud

2015-10-01 Thread Roman Kulikov
Hi, Jenkins!

Let me present our new small "Parallels Desktop Cloud" plugin.

* GitHub: https://github.com/Parallels/jenkins-parallels
* Jenkins repo name: parallels-desktop-plugin
* My GiHub username: romankulikov
* My jenkins-ci.org username: romankulikov
* Description: with the plugin, Parallels Desktop virtual machines are 
launched dynamically whenever they are needed to build jobs, and then 
suspended during idle time, for high-density usage of resources.

|| Roman Kulikov

-- 
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/272c512d-5aeb-49ef-b98a-882b22a94a4b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins Plugin Install Wizard - check out the progress (video) ...

2015-10-01 Thread Daniel Beck

On 01.10.2015, at 08:42, Victor Martinez  wrote:

> Therefore, IMO those categories and recommended plugin as long as they are 
> not part of any Commercial version shouldn't be blocked by those 3 "filters", 
> don't you think? I mean, if I was Company who provides a Jenkins enterprise 
> version I shouldn't allow any unsecured plugins for bare things even though 
> it's also based on OSS, but as long as this is an open source version it 
> shouldn't restrict those plugins at all. 
> 
> Again, I strongly believe this wizard is a great idea but this approach 
> prunes too much plugins.

Please provide an alternative list of criteria, or plugins -- right now it's 
not clear how you'd like to proceed here. Or are you rejecting the concept of a 
curated list entirely, preferring to show all 1000+ plugins?

-- 
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/3BE8D129-C343-4E9F-9666-C734CF9861FD%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins Plugin Install Wizard - check out the progress (video) ...

2015-10-01 Thread Victor Martinez
Sure, Since there was already an agreement of having a single wizard as Tom 
already noticed, sorry about that suggestion, I joint the thread a bit 
late, I believe in the below criteria (see my red and blue comments)

- Is the plugin useful, and does it actually work? (Mostly approximated by 
install count) 
   Agree
- Does the plugin integrate well with Jenkins? Does it work well in secured and 
distributed Jenkins? 
   As I already mention "secured" shouldn't pruned any plugins as long as 
those are heavily used by the community and it is an open source version
- Are the features it provides useful to someone fairly new to Jenkins? 
   What do you mean about someone fairly new to Jenkins? Configuration as 
Code (Workflow, JobDSL or jenkins builder) will be fairly complex to 
understand by someone new to Jenkins, even using  you use Workflow, don't 
you think?Then some of those recommended plugins don't follow this criteria.
- Even if it's not popular, is it a reasonably common SCM? (SCM's are so 
fundamental to successful Jenkins use that these shouldn't be as heavily 
restricted as some of the other categories.) 
   Agree

As an example of one of my production jenkins instances, there are a bunch 
of plugins and probably some of them will not part of the recommended list, 
since the above list criteria.

PluginVersionNumber of jobshipchat 
0.1.6449throttle-
concurrents 

1.8.3292rebuild 
1.22291timestamper 
1.5.13261build-failure-analyzer 
1.13.0254
envinject 1.90
236mercurial 
1.50163build-blocker-plugin 
1.6157
heavy-job 1.1
157mailer 1.15150jira 
1.39114git 
2.3.589multiple-scms 
0.375ws-
cleanup 
0.2156
ownership 0.7
47parameterized-trigger 
2.
2545github 1.11.3
26matrix-project 
1.624
gradle 1.2422build
-timeout 1.
14.120ant 1.220groovy 
1.1920conditional-
buildstep 
1.
3.316junit 1.915
chucknorris 
0.510groovy-postbuild 
1.108
copyartifact 
1.318build-
user-vars-plugin 
1.47email
-ext 2.38.26job
-dsl 1.385
postbuildscript 
0.165
jenkins-multijob-plugin 
1.135ircbot 
2.255custom-tools-
plugin 0.
4.44htmlpublisher 
1.44sonar 
2.13
subversion 2.5
.13ghprb 

1.28.62scriptler 
2.72javadoc 
1.12locks-and-
latches 0
.62xvnc 1.172
findbugs 4.562cobertura 
1.9.52feature-
branch-notifier 

Re: sign up

2015-10-01 Thread Larry Shatzer, Jr.
When I try to create it, I get

ID eladiomartin98 is already taken. Perhaps you already have an account
imported from legacy java.net? You may try resetting the password.

Did you have an older account you need to reset the password? Or did
another admin create your account, and not let you know?

-- Larry

On Wed, Sep 30, 2015 at 3:59 PM, Martin, Eladio 
wrote:

> Please advise how to get my access up on Jenkins site…
>
>
>
> User id: eladiomartin98
>
>
>
>
>
>
>
>
>
> *Eladio Martin • Bank of America Merrill Lynch • Global Markets Technology* *•
> CODE/ *
> *Desk 7-1398, 250 Vesey Street, NY, NY 10080*
> *Tel:* *(212) 449-1088 <%28212%29%20449-1088> • Mobile:* *(917) 288-5549
> <%28917%29%20288-5549> •* *Email:* *eladio.mar...@baml.com*
> 
>
>
>
>
> --
> This message, and any attachments, is for the intended recipient(s) only,
> may contain information that is privileged, confidential and/or proprietary
> and subject to important terms and conditions available at
> http://www.bankofamerica.com/emaildisclaimer. If you are not the intended
> recipient, please delete this message.
>
> --
> 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/9FD6365237FEB94093CF2EB3B88100EA8D1ACA4A%40smtp_mail.bankofamerica.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/CAPr6TnS0ikJJ8Js8L2NbZg_kGv0Q6CF0Z3RbcAeyafVEHGA8Vg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Duplicate Code Scanner Plug-in

2015-10-01 Thread Christopher Orr
This happened because plugin names are now taken from the pom.xml rather
than the wiki page name.

So the better fix would be to update the  tag in the POM for the
next release.

Regards,
Chris


On 29/09/15 15:01, Arnaud Héritier wrote:
> Hi Ullrich,
> 
>   I just noticed that the plugin named in the update center `Duplicate
> Code Scanner Plug-in ` is in fact
> the DRY plugin : https://wiki.jenkins-ci.org/display/JENKINS/DRY+Plugin
> 
>   Maybe you could rename the wiki page to avoid look for a dry plugin in
> the update center (if you use the search feature of the update center
> you find it because it is returned from its identifier but in the UI
> it's not easy to find it)
> 
> 
> ​
>   cheers,
> 
> -
> Arnaud Héritier
> http://aheritier.net
> Mail/GTalk: aheritier AT gmail DOT com
> Twitter/Skype : aheritier
> 
> -- 
> 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/CAFNCU--RyuY-NKB3rV%2B%3D8K67OEThwFxx%2BgPZ67ttNcE1i6-gvw%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/560D5002.1060300%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.


Re: Plugin Manager - Uninstalling/Disabling plugins that have active dependant plugins ???

2015-10-01 Thread Tom Fennelly
I Created PR #1847  for 
this.

Here's the changes in action: https://youtu.be/YMLKumX-kkI

-- 
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/8fbcea95-fef8-4313-b715-ebaf854922a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: NoClassDefFoundError: com/cloudbees/plugins/credentials/CredentialsProvider

2015-10-01 Thread Victor Martinez
Awesome!If you need them only form testing then change their scope as test
Cheers

-- 
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/a1cd0fac-ef27-420e-a542-d646a4b747e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: NoClassDefFoundError: com/cloudbees/plugins/credentials/CredentialsProvider

2015-10-01 Thread Jacqueline Taing
How do you specify scope of dependency in pom.xml?

Thanks,
-jacqui

On Thursday, October 1, 2015 at 11:03:51 AM UTC-7, Victor Martinez wrote:
>
> Awesome!If you need them only form testing then change their scope as test
> Cheers

-- 
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/16843f9d-b99f-4dad-bc68-ce6eb0fe52e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: NoClassDefFoundError: com/cloudbees/plugins/credentials/CredentialsProvider

2015-10-01 Thread Jacqueline Taing
Thanks all! I did have to add the dependencies to pom.xml.  I added the two 
items below and now everything is good.


org.jenkins-ci.plugins
credentials
1.8.3
true


org.jenkins-ci.plugins
matrix-auth
1.0.2
true



On Wednesday, September 30, 2015 at 3:42:30 PM UTC-7, Jesse Glick wrote:
>
> On Wed, Sep 30, 2015 at 6:18 PM, Victor Martinez 
>  wrote: 
> > Some missing dependencies: 
> > - https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Plugin 
>
> Specifically `cloudbees-folder` has 
>
>
> https://github.com/jenkinsci/cloudbees-folder-plugin/blob/cloudbees-folder-4.10/pom.xml#L55-L60
>  
>
> Since this is an `optional` dependency, it does not automatically get 
> included transitively in your plugin’s test classpath. If you want it, 
> you need to add it. 
>
> That said, it looks like a bug in `cloudbees-folder` that it has this 
> optional dependency yet does not behave gracefully when the dependency 
> is missing. Possibly it suffices for `@Extension` to be marked 
> `(optional=true)`. Perhaps file a bug/PR. 
>

-- 
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/d661bba1-1ae0-45ac-b5df-8075e7107323%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


View that polls latest builds from a project

2015-10-01 Thread Jacqueline Taing
I need some guidance...

I am trying to implement a dashboard by extending the Dashboard View 
 plugin (which extends 
ListView 
).
 
 My dashboard needs to display status of latest builds for specific 
projects.  Currently, the builds that get shown on the dashboard seem to be 
set at dashboard create time since the portlets that are defining the 
content are created on submit of Edit View.  It never seems to change after 
that.  Is there a way to poll the projects for newer builds and update my 
dashboard/dashboard portlets with data from those builds?

Thanks!
-jacqui

-- 
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/2e4177b9-28a2-4069-91e1-a1e7b170243a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins Plugin Install Wizard - check out the progress (video) ...

2015-10-01 Thread Baptiste Mathus
IIUC, though it seems a good idea to try and base the list to the actual
usage of plugins, this wouldn't work for many plugins that do not have to
be configured.

For example, it wouldn't work for mine which is enabled globally (
buildtriggerbadge
,
obviously required in the list if you ask me).

2015-10-01 15:36 GMT+02:00 Victor Martinez :

> Sure, Since there was already an agreement of having a single wizard as
> Tom already noticed, sorry about that suggestion, I joint the thread a bit
> late, I believe in the below criteria (see my red and blue comments)
>
> - Is the plugin useful, and does it actually work? (Mostly approximated by
> install count)
>Agree
> - Does the plugin integrate well with Jenkins? Does it work well in
> secured and distributed Jenkins?
>As I already mention "secured" shouldn't pruned any plugins as long as
> those are heavily used by the community and it is an open source version
> - Are the features it provides useful to someone fairly new to Jenkins?
>What do you mean about someone fairly new to Jenkins? Configuration as
> Code (Workflow, JobDSL or jenkins builder) will be fairly complex to
> understand by someone new to Jenkins, even using  you use Workflow, don't
> you think?Then some of those recommended plugins don't follow this criteria.
> - Even if it's not popular, is it a reasonably common SCM? (SCM's are so
> fundamental to successful Jenkins use that these shouldn't be as heavily
> restricted as some of the other categories.)
>Agree
>
> As an example of one of my production jenkins instances, there are a bunch
> of plugins and probably some of them will not part of the recommended list,
> since the above list criteria.
>
> PluginVersionNumber of jobshipchat
> 0.1.6449
> throttle-concurrents
> 
> 1.8.3292rebuild
> 1.22291
> timestamper 1.5.13
> 261build-failure-analyzer
> 1.13.0
> 254envinject
> 1.90236
> mercurial 
> 1.50163build-blocker-plugin
> 1.6157
> heavy-job 1.
> 1157mailer 1.15150jira
> 1.39114git
> 2.3.589multiple-
> scms 0.3
> 75ws-cleanup
> 0.21
> 56ownership 
> 0.747parameterized-trigger
> 2
> .2545github 1.11
> .326matrix-project
> 1.624
> gradle 1.2422
> build-timeout
> 1.14.120
> ant 1.220groovy
> 1.1920
> conditional-buildstep
> 
> 1.3.316junit 1.9
> 15chucknorris
> 0.510groovy
> -postbuild
> 1.108
> copyartifact
> 1.318
> build-user-vars-plugin
> 1.47
> email-ext 2.
> 38.26job-dsl 1
> .385postbuildscript
> 0.165
> jenkins-multijob-plugin
> 1.135ircbot
> 2.255custom-tools-
> plugin 0.
> 4.44htmlpublisher
> 1.44
> sonar 
> 2.13subversion
> 2.5.13ghprb
> 

Re: NoClassDefFoundError: com/cloudbees/plugins/credentials/CredentialsProvider

2015-10-01 Thread Victor Martinez
There are a list of different dependency scopes, in your case you need to 
add the test scope tag. 

Further details: 
- 
https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope

If you don't need that dependency in your runtime then use that test scope.

Cheers

On Thursday, 1 October 2015 20:14:58 UTC+2, Jacqueline Taing wrote:
>
> How do you specify scope of dependency in pom.xml?
>
> Thanks,
> -jacqui
>
> On Thursday, October 1, 2015 at 11:03:51 AM UTC-7, Victor Martinez wrote:
>>
>> Awesome!If you need them only form testing then change their scope as test
>> Cheers
>
>

-- 
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/f39571f9-037a-4e8e-aff4-c8f7c20b4475%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: NoClassDefFoundError: com/cloudbees/plugins/credentials/CredentialsProvider

2015-10-01 Thread Jacqueline Taing
Thank you!

On Thursday, October 1, 2015 at 1:42:34 PM UTC-7, Victor Martinez wrote:
>
> There are a list of different dependency scopes, in your case you need to 
> add the test scope tag. 
>
> Further details: 
> - 
> https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope
>
> If you don't need that dependency in your runtime then use that test scope.
>
> Cheers
>
> On Thursday, 1 October 2015 20:14:58 UTC+2, Jacqueline Taing wrote:
>>
>> How do you specify scope of dependency in pom.xml?
>>
>> Thanks,
>> -jacqui
>>
>> On Thursday, October 1, 2015 at 11:03:51 AM UTC-7, Victor Martinez wrote:
>>>
>>> Awesome!If you need them only form testing then change their scope as 
>>> test
>>> Cheers
>>
>>

-- 
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/7146b31e-f8ab-404e-b947-a97569fb4f63%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Jenkins 1.625.1 LTS RC testing started

2015-10-01 Thread oliver gondža

Hello everyone,

Latest RC was made public and it is ready to be tested. Release is  
scheduled for 2015-10-14.


Report your findings in this thread or on the test plan wiki page.

Download bits from  
http://mirrors.jenkins-ci.org/war-stable-rc/latest/jenkins.war
Check community maintained LTS test plan  
https://wiki.jenkins-ci.org/display/JENKINS/LTS+1.625.x+RC+Testing


Thanks
--
oliver

--
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/op.x5tfcokusbfict%40dhcp-10-40-3-130.brq.redhat.com.
For more options, visit https://groups.google.com/d/optout.


1.625.1 RC2 posted

2015-10-01 Thread Kohsuke Kawaguchi
See *-stable-rc under http://mirrors.jenkins-ci.org/

-- 
Kohsuke Kawaguchi

-- 
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/CAN4CQ4yND-a4-3RctdBAJSORgDpzCs1599xXU-uuo93Pdn5iWQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: performance labs

2015-10-01 Thread Michael Neale
Oh wow - they may be a perfect test workload. Do you know if boot up times 
are in the many many minutes for those instances? Some data on the 
jenkins_home dir sizes?
It would be ideal to use opensource workloads (even if it is a point in 
time) vs something contrived, or a scrubbed version of a private users data 
that has donated it, however it would want to be pretty hefty (not 
necessarily 2TB jenkins_homes that I have heard of, or 40 minute boot up, 
but something up there would be nice). 

I guess the next step is an initial scope of what we want to measure. To 
keep things focussed I am thinking or boot up to job load time, and listing 
a few things. 




On Thursday, October 1, 2015 at 5:55:08 PM UTC+10, Andrew Bayer wrote:
>
> ...and I can most likely provide builds.apache.org's jobs/builds/load/etc 
> as a use case.
>
> A.
>
> On Thu, Oct 1, 2015 at 9:54 AM, Andrew Bayer  > wrote:
>
>> +1 - that'd be fantastic. I'd love to help with that.
>>
>> A.
>>
>> On Thu, Oct 1, 2015 at 4:50 AM, Michael Neale > > wrote:
>>
>>> Hey all - I have thought it would be a great idea to have some quasi 
>>> formal "performance lab" setups for Jenkins. 
>>>
>>> Recently around Jenkins 2.0 planning threads there have been lots of 
>>> comments around performance challenges. Often things like launch time 
>>> (talking many minutes to an hour for large workspaces - launch times are 
>>> probably a good proxy for a whole lot of issues, but there are other issues 
>>> too). 
>>>
>>> At JUC west there was an excellent talk by Akshay Dayal from Google, on 
>>> scaling jenkins. I highly recommend flicking through the slides 
>>>  
>>> or watching the talk 
>>> 
>>>  
>>> if you have time. 
>>>
>>> Basically, they had some performance goals and started by setting up 
>>> measurements and test scenarios to validate their progress - both around 
>>> scalability of slaves (an interesting issue) but also on bootup time (time 
>>> to recovery) which is very interesting. It reminded me that to improve 
>>> something like this you kind of need easily repeatable measurements in 
>>> controlled environments, which currently I don't think the Jenkins project 
>>> has set up? (correct me if wrong). 
>>>
>>> I know Stephen Connolly did some work a few years back on slave 
>>> scalability which was interesting (building out a test suite 
>>> infrastructure), but I am not aware of subsequent efforts. 
>>>
>>> Is this something people would be interested in? 
>>>
>>> Having either large sample JENKINS_HOME specimens or test code that can 
>>> generate pathological data would be required, as well as automation around 
>>> running it on a variety of machines (not necessarily cloud, ideally want to 
>>> be testing code not cloud infrastructure). 
>>>
>>>
>>> -- 
>>> 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/76a12929-8f10-4b50-bf01-04cc77768149%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/297b9981-edc5-49e2-b46f-f0b49183f32c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins Plugin Install Wizard - check out the progress (video) ...

2015-10-01 Thread Daniel Beck

On 01.10.2015, at 15:36, Victor Martinez  wrote:

> - Does the plugin integrate well with Jenkins? Does it work well in secured 
> and distributed Jenkins? 
>As I already mention "secured" shouldn't pruned any plugins as long as 
> those are heavily used by the community and it is an open source version

I think we'll have to agree to disagree here. If a plugin, without warning you, 
undermines whatever security the admin sets up, it should not be available in 
this dialog.

> - Are the features it provides useful to someone fairly new to Jenkins? 
>What do you mean about someone fairly new to Jenkins? Configuration as 
> Code (Workflow, JobDSL or jenkins builder) will be fairly complex to 
> understand by someone new to Jenkins, even using  you use Workflow, don't you 
> think?Then some of those recommended plugins don't follow this criteria.

You'll notice I left out plugins that, secured or not, are mostly useful when 
scripting around in Jenkins internals. The kind of plugin that makes people 
file issues like JENKINS-26416 or JENKINS-24790. For example, Groovy Postbuild 
and Scriptler fall into this category.

Looking at the list of plugins you're showing me I can say with confidence that 
this setup dialog is not meant for you, but that's okay -- it's not meant for 
me either! It is for getting less (or in-)experienced users started with a 
useful set of features, rather than dumping them into an empty instance that 
doesn't even have their SCM.

-- 
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/0A5652F4-B6D2-49CF-A9A9-EF5E7ECD14BD%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins 2.0 proposal

2015-10-01 Thread Kaj Kandler
Go for it! Those 4 digit minor numbers are getting a bit long :-)

I'd just go for the UX/UI theme as 2.0. Not that all other things are 
desirable too, but just the visual part could be a big boon and some 
disruption for the plugin community as well. That said, is UI going to be 
important going forward with DSL and Workflow?

I also think documentation improvements could be really helpful. 
* For example I could not find a definition of the general Queue mechanism 
and discipline, only references in plugins that change it. But nothing 
authoritative.
* Similar, the documentation of extension points and API's is gravely 
lacking (what is getBuildVariables() supposed to do? Can it call 
getEnvironment()? Not if it wants to interoperate with a later build of the 
SVN plugin, which calls getBuildVariables() in the getEnvironment - poof 
stack overflow - who's fault is it? Oh, why does getBuildVariables() not 
have any access to a logger?)

I personally love Wikis (at least those that accept Wiki syntax, which 
Atlassian messes up with its newer versions and standard Wysiwyg editors 
that break 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/a8fe3ad1-14c9-4c6c-b4db-fac1a5ea78b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins 2.0 proposal

2015-10-01 Thread Michael Neale
yes picking a JS framework seems like picking a Loser these days - no
matter what you do, you will pick wrong ;) Longevity isn't great. Doing as
much with plain old js (possibly with jquery given it isn't going anywhere)
is probably a good baseline, but it would be great to see plugins take
advantage of the modularity and explore what can be done with react.



On Wed, Sep 30, 2015 at 7:42 PM Tom Fennelly  wrote:

> On 30 September 2015 at 09:29, Michael Neale 
> wrote:
>
>>
>>
>> On Wed, Sep 30, 2015 at 9:59 AM Surya Gaddipati 
>> wrote:
>>
>>> Great post Kohsuke. Thank you for creating Jenkins.
>>>
>>> >Time to bump up the system requirement to Java 8 and Servlet 3.0.
>>> Let's think about what this would enable to users.
>>>
>>> I've been using Java 8 for serverside rendering of react fontend for
>>> dotci using Nashorn. It has been working beautifully.
>>>
>>
>> Oh that is quite interesting. By react you mean react from facebook?
>>
>>
> We purposely stayed away from using the likes of React/Polymer etc in the
> install wizard. We feel it would be too "controversial" to use in Jenkins
> Core. However, I think they could be very interesting options in a plugin,
> so making it easy to use these would be a great thing I think.
>
> --
> 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/vbXK7JJekFw/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/jenkinsci-dev/CA%2BbPaoLXGC85XTg8yXdfQWxQ9C_2LznskYJB_om0vBKot6FNsg%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/CAKVMTi7ywWYBYkC1z2VARcUAU9VvS7mvtEbowN7TQqoaG58Y8g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Post-build Actions on Jobs executed on slaves

2015-10-01 Thread Paul Wellner Bou
Thank you for the reply.

I am using a Publisher extending Publisher.

This looks promising. I discovered a stackoverflow thread with a bit of
code doing  a smiliar thing (
http://stackoverflow.com/questions/9279898/can-hudson-slaves-run-plugins).

Whats the difference between launcher.getChannel().call(task); and
build.getWorkspace().act(task)? The JavaDoc of the latter looks promising.

What I am wondering now, is which Caller to use. There is a
FilePath.FileCallable, where the JavaDoc says "Subtypes would likely want
to extend from either {@link MasterToSlaveCallable}* or {@link
SlaveToMasterFileCallable}."

I would use MasterToSlaveCallable now, does this work on the master then as
well? Or do I have to detect somehow if I am running on a master or a slave?

Thank you very much,
Paul.


On Thu, Oct 1, 2015 at 10:38 AM Ullrich Hafner 
wrote:

> Are you referring to an action that implements the Action interface? Or to
> a post build publisher that derives from Recorder or Publisher?
>
> The latter one can execute Runnables on a slave, e.g. to read information
> from the workspace. See FilePath#act for details...
>
> Am 01.10.2015 um 08:25 schrieb Paul Wellner Bou :
>
> Good morning,
>
> I have a build job checking out a git repository running on a jenkins
> slave, which works fine. But I am trying to access the workspace in an
> Post-build Action plugin, which does not seem to be possible: The
> Post-build Action is run on the master (at least thats what the
> System.getenv("HOSTNAME") is telling me.
>
> Is there any way to run the Post-build Actions on the slave?
>
> Thank you and regards
> Paul.
>
>
> --
>
> 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/fe2bda4d-a374-4b04-b720-5702c4586e2b%40googlegroups.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/NwNN-HnnI8Q/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/jenkinsci-dev/9A91F3C4-F8DA-4D10-9693-77AF5ADF7B35%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/CAMDwiY_v-yXrY8dE9bVAymZAn1-W%2B%3D1UMktdADcEJKLAstMdQg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins 2.0 proposal

2015-10-01 Thread Michael Neale
I sometimes feel the same way about unfamiliar TLDs, but perhaps it is us
internet old timers that balk at non .org or .com things?

On Thu, Oct 1, 2015 at 7:24 PM Andrew Bayer  wrote:

> Some thoughts...
>
> jenkins.cd is a bad idea. It has a weird feel to it - I've never seen
> another .cd domain. It's more narrow and marketing-specific than
> jenkins-ci.org, as has been said. Honestly, it feels more like a startup
> domain than an OSS project domain. If we can get jenkins.org or another
> of the more common TLDs, sure, that's an improvement, but jenkins.cd just
> doesn't feel right.
>
> I'm not comfortable with the timeframe - this is our best opportunity to
> make major architectural changes to core for a long time, and we should
> really take advantage of that. Let's have real discussions about breaking
> compatibility in some places, re-doing the backend storage (I strongly feel
> we should move core's storage (and quasi-core plugins like junit-plugin,
> Maven/matrix job types, etc) to an abstraction layer - so that it becomes
> possible to move builds/tests/etc to be stored in something other than
> XML), etc.
>
> Given that I think 2.0 should be more radical a change than proposed, I
> also think we should keep the 1.x LTS line going for like a year - just bug
> fixes, of course, but we'd really need to have a path for people to take
> time to move off of removed functionality or plugins that won't work any
> more in 2.0, etc, and keeping up the LTS track is a necessary part of that.
>
>
> A.
>
> On Thu, Oct 1, 2015 at 12:31 AM, James Nord  wrote:
>
>> OT: if you can buy some ssd disks and raid them so you can get space and
>> redundancy you will probalg see an order of magnitude difference.  I had
>> start up times of 3 hours which fell to 3 minutes...   As for tests have
>> you tuned the jvm memory settings? If not then the results get garbage
>> collected whilst loading other results that are needed which keads to the
>> results being loaded again which leads to And eventually enough loads
>> and gcs pass that it works again.
>> Apart from artifact/log archival/retreival most of the io in jenkins will
>> be loading small files and random Iops is king not sequential bandwidth.
>> YMMV standard disclaimers apply
>>
>
>> --
>
>
>> 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/7f434dd9-a7c6-4477-ac46-43bf34dbb8b4%40googlegroups.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/vbXK7JJekFw/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/jenkinsci-dev/CAPbPdOYtrnhrkZORCTzGxgRrMhydS%3DzEKRAS8FffPaK_24Ln2A%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/CAKVMTi6WJGb0jAcv0swk3wMcnp9hp53%2BgOez4Ha8GUExy2%2BuTA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins 2.0 proposal

2015-10-01 Thread Andrew Bayer
Some thoughts...

jenkins.cd is a bad idea. It has a weird feel to it - I've never seen
another .cd domain. It's more narrow and marketing-specific than
jenkins-ci.org, as has been said. Honestly, it feels more like a startup
domain than an OSS project domain. If we can get jenkins.org or another of
the more common TLDs, sure, that's an improvement, but jenkins.cd just
doesn't feel right.

I'm not comfortable with the timeframe - this is our best opportunity to
make major architectural changes to core for a long time, and we should
really take advantage of that. Let's have real discussions about breaking
compatibility in some places, re-doing the backend storage (I strongly feel
we should move core's storage (and quasi-core plugins like junit-plugin,
Maven/matrix job types, etc) to an abstraction layer - so that it becomes
possible to move builds/tests/etc to be stored in something other than
XML), etc.

Given that I think 2.0 should be more radical a change than proposed, I
also think we should keep the 1.x LTS line going for like a year - just bug
fixes, of course, but we'd really need to have a path for people to take
time to move off of removed functionality or plugins that won't work any
more in 2.0, etc, and keeping up the LTS track is a necessary part of that.


A.

On Thu, Oct 1, 2015 at 12:31 AM, James Nord  wrote:

> OT: if you can buy some ssd disks and raid them so you can get space and
> redundancy you will probalg see an order of magnitude difference.  I had
> start up times of 3 hours which fell to 3 minutes...   As for tests have
> you tuned the jvm memory settings? If not then the results get garbage
> collected whilst loading other results that are needed which keads to the
> results being loaded again which leads to And eventually enough loads
> and gcs pass that it works again.
> Apart from artifact/log archival/retreival most of the io in jenkins will
> be loading small files and random Iops is king not sequential bandwidth.
> YMMV standard disclaimers apply
>
> --
> 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/7f434dd9-a7c6-4477-ac46-43bf34dbb8b4%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/CAPbPdOYtrnhrkZORCTzGxgRrMhydS%3DzEKRAS8FffPaK_24Ln2A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Post-build Actions on Jobs executed on slaves

2015-10-01 Thread Ullrich Hafner
Are you referring to an action that implements the Action interface? Or to a 
post build publisher that derives from Recorder or Publisher?

The latter one can execute Runnables on a slave, e.g. to read information from 
the workspace. See FilePath#act for details...

> Am 01.10.2015 um 08:25 schrieb Paul Wellner Bou :
> 
> Good morning,
> 
> I have a build job checking out a git repository running on a jenkins slave, 
> which works fine. But I am trying to access the workspace in an Post-build 
> Action plugin, which does not seem to be possible: The Post-build Action is 
> run on the master (at least thats what the System.getenv("HOSTNAME") is 
> telling me.
> 
> Is there any way to run the Post-build Actions on the slave?
> 
> Thank you and regards
> Paul.
> 
> 
> --
> 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/fe2bda4d-a374-4b04-b720-5702c4586e2b%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/9A91F3C4-F8DA-4D10-9693-77AF5ADF7B35%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail