Tuition Classes in Bangalore

[Rahul Hariprasad]

*Coaching Centers in Bangalore* 
 it. In order 
to assist individuals come through specific goals in areas of their lives, 
several niche areas are established within the employment industry: life 
employment, government employment, Neuro -linguistic programming (NLP) 
employment, personal employment, performance employment, student 
employment, young  person employment, parent employment, expat employment 
and even Christian employment. Christian employment may be a comparatively 
new space within the employment trade

 and most frequently misunderstood. within the sense the name typically 
either describes the tactic that the coach uses or the target cluster for 
whom the particular form of employment would be best suited. within the 
case of Christian employment each a true, it's the kind of employment 
that's in all probability best fitted to Christians, however it conjointly 
includes a distinctive method of in operation that produces it clearly 
Christian.Since this type of life employment is intended specifically for 
Christians, it implies that believers will speak to a Christian coach and 
understand that the coach subscribes to identical beliefs and worth system 
as they are doing. Christians might so overtly discuss their religion and 
alternative personal or non secular problems with their coach.



 
http://www.busybizz.com/Coaching-And-Tuitions-Bangalore.php

-- 
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/65388b8f-62d7-4ef8-a1f9-c09c014e255a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: getScm() on AbstractProject vs. Run

[Jesse Glick]

On Mon, Nov 7, 2016 at 5:49 PM, Ullrich Hafner  wrote:
> Is there a way to get the diffs or affected line numbers from a 
> ChangeLogSet.Entry? Seems that only the plain path is available.

Yes, it does not currently define anything more granular than filenames.

-- 
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/CANfRfr2WnWk6ESKSorJ%2B4YR%2B_MZyvXHQaG9UAa2AaTtJruw%3DLw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Questions on updating flowdock plugin to support pipeline

[Jesse Glick]

On Mon, Nov 7, 2016 at 4:23 PM, Tim Downey  wrote:
> under pipeline,
> traditional Notifiers would not be used and instead flow control around
> build status should be inside of the pipeline as opposed to the plugin?

Right.

> also
> seems to require the most work for pipeline script writers

See Pipeline Model Definition 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/CANfRfr0ZKnJvuQwva_Q6tbBnPWEwh-2jmsPC4z-oTT5P_TmgZw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: Out-of-order weekly release? Just another attempt

[Oleg Nenashev]

Hi,

All the fixes are integrated. Changelogs for 2.30 are posted as well (here 

).
We are ready to roll out.

Thanks a lot for the hard work Oleg. The community owes you much.

Ah, thanks. People can always say thanks by contributing stuff to the 
Jenkins project ^_^

BR, Oleg

вторник, 8 ноября 2016 г., 0:15:46 UTC+1 пользователь Baptiste Mathus 
написал:
>
> +1. I've already seen many users asking for help about that on IRC and on 
> ml. Releasing earlier totally makes sense.
>
> Thanks a lot for the hard work Oleg. The community owes you much.
>
> Le 8 nov. 2016 12:04 AM, "Oleg Nenashev"  > a écrit :
>
>> Hi,
>>
>> So we have at least 4 +1s in all PRs + a kind of "the approach looks good 
>> to me " from orrc in IRC. I think it's enough to proceed taking the current 
>> community ratings into account (2 positive vs. 9 negative). 
>>
>> Kohsuke is available to spin the release, and I think it's better to do 
>> it sooner than later.
>>
>> BR, Oleg
>>
>> понедельник, 7 ноября 2016 г., 21:57:28 UTC+1 пользователь Oleg Nenashev 
>> написал:
>>>
>>> So we have all 3 patches ready for review (internal reviewbybees process 
>>> have been addressed):
>>>
>>>- https://github.com/jenkinsci/jenkins/pull/2624
>>>- https://github.com/jenkinsci/jenkins/pull/2622
>>>- https://github.com/jenkinsci/jenkins/pull/2621
>>>
>>> Would be great if somebody else reviews them. If we get enough +1s, we 
>>> may be probably able to release the fix even today.
>>>
>>> Thanks in advance,
>>> Oleg
>>>
>>>
>>> понедельник, 7 ноября 2016 г., 21:00:24 UTC+1 пользователь Samuel Van 
>>> Oort написал:

 +1 - needs an out of order release.  This causes 2 major breakages.   

 A small aspect of JENKINS-39404 is responsible for JENKINS-39555, which 
 badly breaks the whole pipeline plugin suite (and goodness knows what 
 else). 

 I have a fix for that which works, but am ensuring it doesn't have side 
 effects.

 On Monday, November 7, 2016 at 1:11:19 PM UTC-5, Oleg Nenashev wrote:
>
> Hi,
>
> According to my previous experience 
> , 
> I assume that nobody in this list cares about the Weekly releases. And 
> you're doing right, LTS is the only way to get enough stability. But I 
> want 
> to try again and to propose out-of-order release (2.30). 
>
> *Why?*
>
>- Many issues opened to JENKINS-39414 
>, blocker for 
>any instances having Ruby Runtime
>- LTS baseline selection is coming
>   - Starting from 2.26 weekly releases are screwed up by 
>   regressions
>   - If we do not resolve the fallout, we may have to select 2.25 
>   as the new LTS baseline
>   - In such case major improvements like JNLP4 won't get into the 
>   release. 
>   - According to Vivek, it's also going to impact the anticipated 
>   BlueOcean public release
>
> *What to fix?*
>
>- JENKINS-39414 
> - has not 
>been completely fixed in 2.29
>   - Stapler needs to be fixed again, PR #2622 
>   
>- JENKINS-39465 
> - Critical 
>bug, which blocks the JNLP4 adoption
>   - PR #2621  has 
>   two +1s
>- Not important: Several other minor bugfixes, which could be 
>integrated by tomorrow
>
> *When?*
>
>- I propose to do it tomorrow (Nov 8)
>
>
> What do you think about it?
>
>
> Best regards,
> Oleg
>
 -- 
>> 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/90974857-f373-46d2-9e33-6a4d851217e1%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/2ed4d476-9605-403b-9a8d-ad0227b6abf8%40googlegroups.com.
For more 

Re: Proposal: Out-of-order weekly release? Just another attempt

[Oleg Nenashev]

Hi,

So we have at least 4 +1s in all PRs + a kind of "the approach looks good 
to me " from orrc in IRC. I think it's enough to proceed taking the current 
community ratings into account (2 positive vs. 9 negative). 

Kohsuke is available to spin the release, and I think it's better to do it 
sooner than later.

BR, Oleg

понедельник, 7 ноября 2016 г., 21:57:28 UTC+1 пользователь Oleg Nenashev 
написал:
>
> So we have all 3 patches ready for review (internal reviewbybees process 
> have been addressed):
>
>- https://github.com/jenkinsci/jenkins/pull/2624
>- https://github.com/jenkinsci/jenkins/pull/2622
>- https://github.com/jenkinsci/jenkins/pull/2621
>
> Would be great if somebody else reviews them. If we get enough +1s, we may 
> be probably able to release the fix even today.
>
> Thanks in advance,
> Oleg
>
>
> понедельник, 7 ноября 2016 г., 21:00:24 UTC+1 пользователь Samuel Van Oort 
> написал:
>>
>> +1 - needs an out of order release.  This causes 2 major breakages.   
>>
>> A small aspect of JENKINS-39404 is responsible for JENKINS-39555, which 
>> badly breaks the whole pipeline plugin suite (and goodness knows what 
>> else). 
>>
>> I have a fix for that which works, but am ensuring it doesn't have side 
>> effects.
>>
>> On Monday, November 7, 2016 at 1:11:19 PM UTC-5, Oleg Nenashev wrote:
>>>
>>> Hi,
>>>
>>> According to my previous experience 
>>> , I 
>>> assume that nobody in this list cares about the Weekly releases. And you're 
>>> doing right, LTS is the only way to get enough stability. But I want to try 
>>> again and to propose out-of-order release (2.30). 
>>>
>>> *Why?*
>>>
>>>- Many issues opened to JENKINS-39414 
>>>, blocker for 
>>>any instances having Ruby Runtime
>>>- LTS baseline selection is coming
>>>   - Starting from 2.26 weekly releases are screwed up by regressions
>>>   - If we do not resolve the fallout, we may have to select 2.25 as 
>>>   the new LTS baseline
>>>   - In such case major improvements like JNLP4 won't get into the 
>>>   release. 
>>>   - According to Vivek, it's also going to impact the anticipated 
>>>   BlueOcean public release
>>>
>>> *What to fix?*
>>>
>>>- JENKINS-39414  
>>>- has not been completely fixed in 2.29
>>>   - Stapler needs to be fixed again, PR #2622 
>>>   
>>>- JENKINS-39465  
>>>- Critical bug, which blocks the JNLP4 adoption
>>>   - PR #2621  has 
>>>   two +1s
>>>- Not important: Several other minor bugfixes, which could be 
>>>integrated by tomorrow
>>>
>>> *When?*
>>>
>>>- I propose to do it tomorrow (Nov 8)
>>>
>>>
>>> What do you think about it?
>>>
>>>
>>> Best regards,
>>> Oleg
>>>
>>

-- 
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/90974857-f373-46d2-9e33-6a4d851217e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: Out-of-order weekly release? Just another attempt

[Baptiste Mathus]

+1. I've already seen many users asking for help about that on IRC and on
ml. Releasing earlier totally makes sense.

Thanks a lot for the hard work Oleg. The community owes you much.

Le 8 nov. 2016 12:04 AM, "Oleg Nenashev"  a écrit :

> Hi,
>
> So we have at least 4 +1s in all PRs + a kind of "the approach looks good
> to me " from orrc in IRC. I think it's enough to proceed taking the current
> community ratings into account (2 positive vs. 9 negative).
>
> Kohsuke is available to spin the release, and I think it's better to do it
> sooner than later.
>
> BR, Oleg
>
> понедельник, 7 ноября 2016 г., 21:57:28 UTC+1 пользователь Oleg Nenashev
> написал:
>>
>> So we have all 3 patches ready for review (internal reviewbybees process
>> have been addressed):
>>
>>- https://github.com/jenkinsci/jenkins/pull/2624
>>- https://github.com/jenkinsci/jenkins/pull/2622
>>- https://github.com/jenkinsci/jenkins/pull/2621
>>
>> Would be great if somebody else reviews them. If we get enough +1s, we
>> may be probably able to release the fix even today.
>>
>> Thanks in advance,
>> Oleg
>>
>>
>> понедельник, 7 ноября 2016 г., 21:00:24 UTC+1 пользователь Samuel Van
>> Oort написал:
>>>
>>> +1 - needs an out of order release.  This causes 2 major breakages.
>>>
>>> A small aspect of JENKINS-39404 is responsible for JENKINS-39555, which
>>> badly breaks the whole pipeline plugin suite (and goodness knows what
>>> else).
>>>
>>> I have a fix for that which works, but am ensuring it doesn't have side
>>> effects.
>>>
>>> On Monday, November 7, 2016 at 1:11:19 PM UTC-5, Oleg Nenashev wrote:

 Hi,

 According to my previous experience
 , I
 assume that nobody in this list cares about the Weekly releases. And you're
 doing right, LTS is the only way to get enough stability. But I want to try
 again and to propose out-of-order release (2.30).

 *Why?*

- Many issues opened to JENKINS-39414
, blocker for
any instances having Ruby Runtime
- LTS baseline selection is coming
   - Starting from 2.26 weekly releases are screwed up by
   regressions
   - If we do not resolve the fallout, we may have to select 2.25
   as the new LTS baseline
   - In such case major improvements like JNLP4 won't get into the
   release.
   - According to Vivek, it's also going to impact the anticipated
   BlueOcean public release

 *What to fix?*

- JENKINS-39414 
- has not been completely fixed in 2.29
   - Stapler needs to be fixed again, PR #2622
   
- JENKINS-39465 
- Critical bug, which blocks the JNLP4 adoption
   - PR #2621  has
   two +1s
- Not important: Several other minor bugfixes, which could be
integrated by tomorrow

 *When?*

- I propose to do it tomorrow (Nov 8)


 What do you think about it?


 Best regards,
 Oleg

>>> --
> 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/90974857-f373-46d2-9e33-6a4d851217e1%
> 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/CANWgJS59eC4ZAOj8nB9n%2BKrg5hhNXBO3VubD%2BCHYhq1BCTdzFg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: getScm() on AbstractProject vs. Run

[Ullrich Hafner]

> Am 27.10.2016 um 01:18 schrieb Jesse Glick :
> 
> Anyway for the stated use case
> 
>> Compute the warnings in a build and map these warnings to corresponding SCM 
>> changes
> 
> `getScm()` was not what you wanted to begin with. You want
> 
> Run run = …;
> @SuppressWarnings("unchecked") List> changeSets =
>  run.getClass().getMethod("getChangeSets").invoke(run);
> 

Is there a way to get the diffs or affected line numbers from a 
ChangeLogSet.Entry? Seems that only the plain path is available. 

-- 
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/0B921028-9E83-4902-A627-022130A4F091%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request for adopting envInject plugin

[Daniel Beck]

> On 07.11.2016, at 23:07, Ce Qi  wrote:
> 
> it's a good opportunity for me to improve my programming skills

Not to discourage you, but are you sure you're up to the task? Or maybe we can 
help you in some way here?

I'm asking about this because Envinject has had a number of severe regressions 
in the past (indicating it's complex and not that easy to maintain), and tens 
of thousands of people rely on the plugin working correctly for their builds…

-- 
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/6719B151-7AB6-45D2-B05D-D1EE4018EC0B%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Request for adopting envInject plugin

[Ce Qi]

Hello,

I'd like to adopt the envInject plugin as it's up for adoption now.

I'm keen to contribute back to Jenkins community as I'm using Jenkins
everyday and it's a good opportunity for me to improve my programming
skills.


my github id: ceqi
my jenkins infra id: ce7


I look forward to hearing from you soon!



Many thanks,

Ce Qi

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

Re: Questions on updating flowdock plugin to support pipeline

[Tim Downey]

Ok, so you're saying the convention would be that under pipeline,
traditional Notifiers would not be used and instead flow control around
build status should be inside of the pipeline as opposed to the plugin?  In
other words, instead of having the flowdockNotifier() figure out what to do
based on build status (from within the plugin), I should instead just
require the pipeline script writer to pass the correct args based on the
pipeline script logic directly (using try, catch logic in the pipeline)?

I can see that doing so would provide the most flexibility, but it also
seems to require the most work for pipeline script writers.  A specific
example would be crafting the logic to notify of a "fixed" build from a
pipeline.  As of now, the plugin does the work to determine if a build has
transitioned from failed to success and is now "fixed".  If that work is
now the job of the pipeline script, it will certainly complicate things and
result in lots of duplication and variance from one persons pipeline to
anothers.

That said, I appreciate the feedback and am still trying to digest what
folks are looking for in terms of idiomatic pipeline code.

Thanks for your time,
Tim


On Mon, Nov 7, 2016 at 3:52 PM, Jesse Glick  wrote:

> On Mon, Nov 7, 2016 at 2:26 PM, Tim Downey 
> wrote:
> > The issue is that run.getResult() is returning null even when used in a
> > pipeline *after* which the build should have failed (e.g. after failing
> to
> > pass unit tests or compilation).  I'm wondering if there is something I
> need
> > to do to ensure that I get the proper build result from the job and have
> > this step run only after that.
>
> For a `SimpleBuildStep` this would apply:
>
> https://github.com/jenkinsci/workflow-basic-steps-plugin/
> blob/master/CORE-STEPS.md#interacting-with-build-status
>
> but you are apparently writing a `Step`, so:
>
> > Is there something
> > different I should be doing to ensure that the flowdockNotifier is only
> run
> > after we've received some sort of build result?  The Flowdock plugin
> > traditionally has been a Notifier and run as a post build action.
>
> It is generally the responsibility of the script to decide whether or
> not to run a given publisher and with what settings. Avoid calling
> `Run.getResult`.
>
> --
> 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/kI0BtRoE7kM/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/CANfRfr2igFVJW-gMuaUvrFW%2Btf-874Cx3CaRY1yD1FzJRYemLg%
> 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/CAJp9yiPJ4ikd288qvNQMzsmknmv8sNYAN3V1rDRsiSOZRp_2VA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: Out-of-order weekly release? Just another attempt

[Oleg Nenashev]

So we have all 3 patches ready for review (internal reviewbybees process 
have been addressed):

   - https://github.com/jenkinsci/jenkins/pull/2624
   - https://github.com/jenkinsci/jenkins/pull/2622
   - https://github.com/jenkinsci/jenkins/pull/2621
   
Would be great if somebody else reviews them. If we get enough +1s, we may 
be probably able to release the fix even today.

Thanks in advance,
Oleg


понедельник, 7 ноября 2016 г., 21:00:24 UTC+1 пользователь Samuel Van Oort 
написал:
>
> +1 - needs an out of order release.  This causes 2 major breakages.   
>
> A small aspect of JENKINS-39404 is responsible for JENKINS-39555, which 
> badly breaks the whole pipeline plugin suite (and goodness knows what 
> else). 
>
> I have a fix for that which works, but am ensuring it doesn't have side 
> effects.
>
> On Monday, November 7, 2016 at 1:11:19 PM UTC-5, Oleg Nenashev wrote:
>>
>> Hi,
>>
>> According to my previous experience 
>> , I 
>> assume that nobody in this list cares about the Weekly releases. And you're 
>> doing right, LTS is the only way to get enough stability. But I want to try 
>> again and to propose out-of-order release (2.30). 
>>
>> *Why?*
>>
>>- Many issues opened to JENKINS-39414 
>>, blocker for any 
>>instances having Ruby Runtime
>>- LTS baseline selection is coming
>>   - Starting from 2.26 weekly releases are screwed up by regressions
>>   - If we do not resolve the fallout, we may have to select 2.25 as 
>>   the new LTS baseline
>>   - In such case major improvements like JNLP4 won't get into the 
>>   release. 
>>   - According to Vivek, it's also going to impact the anticipated 
>>   BlueOcean public release
>>
>> *What to fix?*
>>
>>- JENKINS-39414  
>>- has not been completely fixed in 2.29
>>   - Stapler needs to be fixed again, PR #2622 
>>   
>>- JENKINS-39465  
>>- Critical bug, which blocks the JNLP4 adoption
>>   - PR #2621  has 
>>   two +1s
>>- Not important: Several other minor bugfixes, which could be 
>>integrated by tomorrow
>>
>> *When?*
>>
>>- I propose to do it tomorrow (Nov 8)
>>
>>
>> What do you think about it?
>>
>>
>> Best regards,
>> Oleg
>>
>

-- 
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/024643e6-f9c2-4d43-8578-45ea3df81ebf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Fwd: [Plugin] Please review PR and release jsch-plugin

[Daniel Beck]

Hi Zoran,

There were repeated attempts to contact you via GitHub, and it appears you've 
stopped maintaining the jsch-plugin.

(See https://github.com/jenkinsci/jsch-plugin/pull/2 and the linked PR in 
ssh-credentials-plugin)

Are you okay with us making Łukasz the new maintainer of the plugin?

Daniel

> Begin forwarded message:
> 
> From: Łukasz Jąder 
> Subject: Re: [Plugin] Please review PR and release jsch-plugin
> Date: 5. November 2016 um 23:16:00 MEZ
> To: Jenkins Developers 
> Reply-To: jenkinsci-dev@googlegroups.com
> 
> Hello Jenkins Admins,
> 
> Please grant me push / commit access to 
> https://github.com/jenkinsci/jsch-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/c105513b-16f1-4dc7-bbad-6e6ccc39bf9e%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/7E49B798-E820-4C4C-A4D0-833306F90F32%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Questions on updating flowdock plugin to support pipeline

[Jesse Glick]

On Mon, Nov 7, 2016 at 2:26 PM, Tim Downey  wrote:
> The issue is that run.getResult() is returning null even when used in a
> pipeline *after* which the build should have failed (e.g. after failing to
> pass unit tests or compilation).  I'm wondering if there is something I need
> to do to ensure that I get the proper build result from the job and have
> this step run only after that.

For a `SimpleBuildStep` this would apply:

https://github.com/jenkinsci/workflow-basic-steps-plugin/blob/master/CORE-STEPS.md#interacting-with-build-status

but you are apparently writing a `Step`, so:

> Is there something
> different I should be doing to ensure that the flowdockNotifier is only run
> after we've received some sort of build result?  The Flowdock plugin
> traditionally has been a Notifier and run as a post build action.

It is generally the responsibility of the script to decide whether or
not to run a given publisher and with what settings. Avoid calling
`Run.getResult`.

-- 
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/CANfRfr2igFVJW-gMuaUvrFW%2Btf-874Cx3CaRY1yD1FzJRYemLg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How can a plugin save output when running in pipeline

[Jesse Glick]

On Thu, Nov 3, 2016 at 7:31 PM, Christian McHugh
 wrote:
> Does anyone have a recommendation or example for how to save output of a
> plugin into a variable when running as a pipeline job?

`PwdStep` shows the simplest example I can think of.

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

Re: Plugin dev for Jenkins 2

[Jesse Glick]

On Thu, Nov 3, 2016 at 12:53 PM, Vincent Latombe
 wrote:
> I think jenkins-dev:run already sets -Dhudson.Main.development=true to
> bypass this. Probably the hpi plugin could use the same?

Maybe. Or you can just close the dialog and proceed, after logging in
as `admin`.

-- 
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/CANfRfr0LbUVMj%2B3ELpqu29G2bkvtwsNPvUGLwPTZ9rk-GZDm6g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline Step vs Wrap Environment Variable Writing

[Jesse Glick]

On Wed, Nov 2, 2016 at 4:48 PM, Jimmy Ray  wrote:
> final EnvVars environment = build.getEnvironment(listener); ...
> environment.addLine(String.format("%s=%s", key, value));

Makes no sense. The result of `getEnvironment` is immutable—a new map
each time you call it.

If you have a block-scoped Pipeline `Step`, the equivalent of
`SimpleBuildWrapper.Context.env` would be to use
`EnvironmentExpander`. See `EnvStep` for a simple example.

There is intentionally no way to set build-wide variables, only within
a block scope.

-- 
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/CANfRfr2MnOWC9NApPH7n6s9fW7r%2BgLb%2B1SS60shCmnOMGPDV_A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Failed builds hide Project action

[Jesse Glick]

On Wed, Nov 2, 2016 at 2:43 AM, Fima  wrote:
> 1. Why look at the last successful and not the last builds?

Because in general if the build failed, the publisher may not have
run. If all build steps have run, but there is something wrong with
the source code, then the status should be `UNSTABLE`. Using
`getLastSuccessfulBuild` guarantees that only complete builds are
considered.

> I can make It can check for last completed check if results were or
> actions were recorded and use replace actions to add them instead of
> relaying on latest successful?

Did not understand that sentence.

Possibly the logic could be amended to check both
`getLastSuccessfulBuild` and `getLastCompletedBuild` in case both
exist but the latter is newer; collecting all the `LastBuildAction`s
from each; for each `LastBuildAction` class, picking the newest of the
two choices, if both exist; and then calling `getProjectActions` on
those. Would be easy enough to write the main code; needs test
coverage.

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

Re: PR and release pending. Reverse Proxy Auth. Plugin

[Jesse Glick]

On Wed, Nov 2, 2016 at 7:32 AM, Emilio Escobar  wrote:
> There is a PR https://github.com/jenkinsci/reverse-proxy-auth-plugin/pull/28
> waiting for merge two weeks ago

And my #29 may fix a gigantic performance problem.

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

Re: Proposal: Out-of-order weekly release? Just another attempt

[Jesse Glick]

On Mon, Nov 7, 2016 at 1:28 PM, Oleg Nenashev  wrote:
> we must include ATH in our weekly release Pipeline. It should
> have caught all issues we see.

Confirmed that ATH would have caught JENKINS-39555, since the symptoms
are so severe. In general though ATH only covers a tiny fraction of
plugin functionality; functional tests would catch far more
regressions (including this one), which is why I consider
`plugin-compatibility-tester` important.

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

Re: Proposal: Out-of-order weekly release? Just another attempt

[Samuel Van Oort]

+1 - needs an out of order release.  This causes 2 major breakages.   

A small aspect of JENKINS-39404 is responsible for JENKINS-39555, which 
badly breaks the whole pipeline plugin suite (and goodness knows what 
else). 

I have a fix for that which works, but am ensuring it doesn't have side 
effects.

On Monday, November 7, 2016 at 1:11:19 PM UTC-5, Oleg Nenashev wrote:
>
> Hi,
>
> According to my previous experience 
> , I 
> assume that nobody in this list cares about the Weekly releases. And you're 
> doing right, LTS is the only way to get enough stability. But I want to try 
> again and to propose out-of-order release (2.30). 
>
> *Why?*
>
>- Many issues opened to JENKINS-39414 
>, blocker for any 
>instances having Ruby Runtime
>- LTS baseline selection is coming
>   - Starting from 2.26 weekly releases are screwed up by regressions
>   - If we do not resolve the fallout, we may have to select 2.25 as 
>   the new LTS baseline
>   - In such case major improvements like JNLP4 won't get into the 
>   release. 
>   - According to Vivek, it's also going to impact the anticipated 
>   BlueOcean public release
>
> *What to fix?*
>
>- JENKINS-39414  - 
>has not been completely fixed in 2.29
>   - Stapler needs to be fixed again, PR #2622 
>   
>- JENKINS-39465  - 
>Critical bug, which blocks the JNLP4 adoption
>   - PR #2621  has two 
>   +1s
>- Not important: Several other minor bugfixes, which could be 
>integrated by tomorrow
>
> *When?*
>
>- I propose to do it tomorrow (Nov 8)
>
>
> What do you think about it?
>
>
> Best regards,
> Oleg
>

-- 
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/b55f703d-68f3-4fdb-b99f-5fed5f87ce80%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Questions on updating flowdock plugin to support pipeline

[Tim Downey]

Hi Jesse,

I'm hoping you can point me in the right direction for one more thing.  I'm 
trying to understand at what point in the pipeline process does the build 
result (via run.getResult()) become available?  As you can see below, I'm 
calling the original FlowdockNotifier code in a step execution in order to 
be able to use the "legacy" plugin in a pipeline.  I'm including two blocks 
below.  First is how it's being used in a pipeline, and the second is the 
step execution code.

The issue is that run.getResult() is returning null even when used in a 
pipeline *after* which the build should have failed (e.g. after failing to 
pass unit tests or compilation).  I'm wondering if there is something I 
need to do to ensure that I get the proper build result from the job and 
have this step run only after that.

Here's the pipeline.  In this example, I was assuming that by running the 
flowdockNotifier in the pipeline, I'd already have the correct build result 
in place as a result of the mvn build in the previous section.  Instead, 
I'm getting null for run.getResult() no matter what.  Is there something 
different I should be doing to ensure that the flowdockNotifier is only run 
after we've received some sort of build result?  The Flowdock plugin 
traditionally has been a Notifier and run as a post build action.

try {
sshagent([config.gitCredentials]) {

withMaven(maven: 'Maven', mavenLocalRepo: '.repository', 
mavenSettingsConfig: 
'org.jenkinsci.plugins.configfiles.maven.MavenSettingsConfig1450194231885') 
{
sh "mvn versions:set -DnewVersion=${version}"
sh "mvn clean install"
}
  }

 } catch (err) {
mail body: "Please go to ${BUILD_URL} and verify the build." ,
from: config.email,
replyTo: config.email,
subject: "Build failed in Jenkins: ${JOB_NAME} ${version}",
to: config.recipients

throw err
} finally {
// Post build items here -- build will have already passed or 
failed by now?
flowdockNotifier(flowToken: 'myflowdocktoken', 
notificationTags: "jenkins, ${JOB_NAME}",
chatNotification:true, notifyFailure: true)

}

Here's the step execution.

*public* *static* *class* Execution *extends* 
AbstractSynchronousStepExecution {

   

   @StepContextParameter *private* *transient* Launcher launcher;

   @StepContextParameter *private* *transient* FilePath workspace;

   @StepContextParameter *private* *transient* TaskListener listener;

   @StepContextParameter *private* *transient* Run run;

   @StepContextParameter *private* *transient* EnvVars env;

   @Inject(optional=*true*) *private* *transient* FlowdockNotifierStep 
step;


@Override

   *protected* Void run() *throws* Exception {

   listener.getLogger().println("Running flowdock notifier.");

   

   FlowdockNotifier notifier = *new* FlowdockNotifier(step.flowToken
,

step.notificationTags, 

convertToString(step.chatNotification),

convertToString(step.notifySuccess),

convertToString(step.notifyFailure),

convertToString(step.notifyFixed),

convertToString(step.notifyUnstable), 

convertToString(step.notifyAborted),

convertToString(step.notifyNotBuilt));

   

   notifier.perform(run, workspace, launcher, listener);


*return* *null*;

   }


*private* *static* *final* *long* *serialVersionUID* = 1L;


*private* *static* String convertToString(Boolean bool) {

  *return* bool != *null* ? bool.toString() : *null*;

   }

   }

Thanks for any help,
Tim

On Tuesday, November 1, 2016 at 5:55:55 PM UTC-4, Jesse Glick wrote:
>
> On Tue, Nov 1, 2016 at 2:04 PM, Tim Downey  > wrote: 
> >if(build.getProject().getRootProject() != build.getProject()) { 
> >projectName = 
> > build.getProject().getRootProject().getDisplayName(); 
> >configuration = " on " + build.getProject().getDisplayName(); 
> >} else { 
> >projectName = build.getProject().getDisplayName(); 
> >} 
> > 
> > 
> > From the call, I've switched the fromBuild method to take Run 
> instead 
> > of AbstractProject 
>
> Instead of `AbstractBuild` I suppose you mean. 
>
> > but the issue is that I'm not clear on what needs to be 
> > done in the conditional.  The existing code seems to be trying to figure 
> out 
> > if it is the root project in order to construct the message (which will 
> be 
> > sent to flowdock) but I'm not sure what the equivalent would be when 
> working 
> > from Run instead of 

Re: Proposal: Out-of-order weekly release? Just another attempt

[Samuel Van Oort]

I'm looking into JENKINS-39555 now -- for some reason the usual JIRA 
notification wasn't delivered.  

On Monday, November 7, 2016 at 1:11:19 PM UTC-5, Oleg Nenashev wrote:
>
> Hi,
>
> According to my previous experience 
> , I 
> assume that nobody in this list cares about the Weekly releases. And you're 
> doing right, LTS is the only way to get enough stability. But I want to try 
> again and to propose out-of-order release (2.30). 
>
> *Why?*
>
>- Many issues opened to JENKINS-39414 
>, blocker for any 
>instances having Ruby Runtime
>- LTS baseline selection is coming
>   - Starting from 2.26 weekly releases are screwed up by regressions
>   - If we do not resolve the fallout, we may have to select 2.25 as 
>   the new LTS baseline
>   - In such case major improvements like JNLP4 won't get into the 
>   release. 
>   - According to Vivek, it's also going to impact the anticipated 
>   BlueOcean public release
>
> *What to fix?*
>
>- JENKINS-39414  - 
>has not been completely fixed in 2.29
>   - Stapler needs to be fixed again, PR #2622 
>   
>- JENKINS-39465  - 
>Critical bug, which blocks the JNLP4 adoption
>   - PR #2621  has two 
>   +1s
>- Not important: Several other minor bugfixes, which could be 
>integrated by tomorrow
>
> *When?*
>
>- I propose to do it tomorrow (Nov 8)
>
>
> What do you think about it?
>
>
> Best regards,
> Oleg
>

-- 
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/b035390c-3a4e-48f9-9b33-08e2e3e8864d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: Out-of-order weekly release? Just another attempt

[Oleg Nenashev]

Yes, JENKINS-39555  is 
a must-have. Hopefully your ongoing triangulation will find a hotfix for it.

In general, we must include ATH in our weekly release Pipeline. It should 
have caught all issues we see.


понедельник, 7 ноября 2016 г., 19:17:10 UTC+1 пользователь Arnaud Héritier 
написал:
>
> +1 for an additional release
> (+2 to use LTS in production :-P)
>
> On Mon, Nov 7, 2016 at 7:11 PM, Oleg Nenashev  > wrote:
>
>> Hi,
>>
>> According to my previous experience 
>> , I 
>> assume that nobody in this list cares about the Weekly releases. And you're 
>> doing right, LTS is the only way to get enough stability. But I want to try 
>> again and to propose out-of-order release (2.30). 
>>
>> *Why?*
>>
>>- Many issues opened to JENKINS-39414 
>>, blocker for any 
>>instances having Ruby Runtime
>>- LTS baseline selection is coming
>>   - Starting from 2.26 weekly releases are screwed up by regressions
>>   - If we do not resolve the fallout, we may have to select 2.25 as 
>>   the new LTS baseline
>>   - In such case major improvements like JNLP4 won't get into the 
>>   release. 
>>   - According to Vivek, it's also going to impact the anticipated 
>>   BlueOcean public release
>>
>> *What to fix?*
>>
>>- JENKINS-39414  
>>- has not been completely fixed in 2.29
>>   - Stapler needs to be fixed again, PR #2622 
>>   
>>- JENKINS-39465  
>>- Critical bug, which blocks the JNLP4 adoption
>>   - PR #2621  has 
>>   two +1s
>>- Not important: Several other minor bugfixes, which could be 
>>integrated by tomorrow
>>
>> *When?*
>>
>>- I propose to do it tomorrow (Nov 8)
>>
>>
>> What do you think about it?
>>
>>
>> Best regards,
>> Oleg
>>
>> -- 
>> 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/1da7822a-5270-4cf6-8b5e-f322dfb37cb0%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> -
> 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/a537ec4d-2ebc-4da4-8a35-cd2ee7ffb63e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Proposal: Out-of-order weekly release? Just another attempt

[Oleg Nenashev]

Hi,

According to my previous experience 
, I 
assume that nobody in this list cares about the Weekly releases. And you're 
doing right, LTS is the only way to get enough stability. But I want to try 
again and to propose out-of-order release (2.30). 

*Why?*

   - Many issues opened to JENKINS-39414 
   , blocker for any 
   instances having Ruby Runtime
   - LTS baseline selection is coming
  - Starting from 2.26 weekly releases are screwed up by regressions
  - If we do not resolve the fallout, we may have to select 2.25 as the 
  new LTS baseline
  - In such case major improvements like JNLP4 won't get into the 
  release. 
  - According to Vivek, it's also going to impact the anticipated 
  BlueOcean public release
   
*What to fix?*

   - JENKINS-39414  - 
   has not been completely fixed in 2.29
  - Stapler needs to be fixed again, PR #2622 
  
   - JENKINS-39465  - 
   Critical bug, which blocks the JNLP4 adoption
  - PR #2621  has two 
  +1s
   - Not important: Several other minor bugfixes, which could be integrated 
   by tomorrow
   
*When?*

   - I propose to do it tomorrow (Nov 8)


What do you think about it?


Best regards,
Oleg

-- 
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/1da7822a-5270-4cf6-8b5e-f322dfb37cb0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: Out-of-order weekly release? Just another attempt

[Arnaud Héritier]

+1 for an additional release
(+2 to use LTS in production :-P)

On Mon, Nov 7, 2016 at 7:11 PM, Oleg Nenashev 
wrote:

> Hi,
>
> According to my previous experience
> , I
> assume that nobody in this list cares about the Weekly releases. And you're
> doing right, LTS is the only way to get enough stability. But I want to try
> again and to propose out-of-order release (2.30).
>
> *Why?*
>
>- Many issues opened to JENKINS-39414
>, blocker for any
>instances having Ruby Runtime
>- LTS baseline selection is coming
>   - Starting from 2.26 weekly releases are screwed up by regressions
>   - If we do not resolve the fallout, we may have to select 2.25 as
>   the new LTS baseline
>   - In such case major improvements like JNLP4 won't get into the
>   release.
>   - According to Vivek, it's also going to impact the anticipated
>   BlueOcean public release
>
> *What to fix?*
>
>- JENKINS-39414  -
>has not been completely fixed in 2.29
>   - Stapler needs to be fixed again, PR #2622
>   
>- JENKINS-39465  -
>Critical bug, which blocks the JNLP4 adoption
>   - PR #2621  has two
>   +1s
>- Not important: Several other minor bugfixes, which could be
>integrated by tomorrow
>
> *When?*
>
>- I propose to do it tomorrow (Nov 8)
>
>
> What do you think about it?
>
>
> Best regards,
> Oleg
>
> --
> 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/1da7822a-5270-4cf6-8b5e-f322dfb37cb0%
> 40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



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

Re: Proposal: Out-of-order weekly release? Just another attempt

[Daniel Beck]

> On 07.11.2016, at 19:11, Oleg Nenashev  wrote:
> 
> What do you think about it?

There's also JENKINS-39555. 2.30 without a fix for that seems pointless.

Screwing up a weekly due to a big change once in a while happens, but we should 
work towards making 2.30 not suck, LTS baseline or not.

Given the scope and that the past weekly didn't fix it, an out of order release 
would be useful, assuming we can get all of this fixed before Thursday or 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/DD3A0A12-2D17-4C99-8645-C12888FD5C55%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Memory Leak in pipeline?

[Daniel Weber]

Thanks. I double-checked. It was set correctly and really does not help 
here.

Am Montag, 7. November 2016 14:38:42 UTC+1 schrieb Daniel Beck:
>
>
> > On 07.11.2016, at 14:33, Daniel Beck  
> wrote: 
> > 
> > Is this https://issues.jenkins-ci.org/browse/JENKINS-33358? Have you 
> tried -Dgroovy.use.classvalue=true? 
>
> Never mind, I just saw… 
>
> > • ✓ Set -Dgroovy.use.classvalue=true, as reported in JENKINS-33358. Did 
> not help 
>
> FWIW I'd double check this is actually set at the correct location on the 
> command line, and System.getProperty(…) reports the correct value. I've 
> seen too many `java -jar jenkins.war -Dwhatever=something` in the past…

-- 
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/82aac3b9-ece6-4c8e-8d80-2d047c59421e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Memory Leak in pipeline?

[Jesse Glick]

On Monday, November 7, 2016 at 7:58:35 AM UTC-5, Daniel Weber wrote:
>
> we keep running into memory issues with pipelines
>

Already have a fix for a set of leaks in 
https://github.com/jenkinsci/workflow-cps-plugin/pull/83, which should be 
in the next release. Whether or not that is *your* leak is impossible to 
say without trying the update. Your GC root analysis shows only weak 
references, so it is not actually pointing to the problem at all.

-- 
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/890e2080-1b53-47fe-bfff-d4fad961da67%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Memory Leak in pipeline?

[Daniel Beck]

> On 07.11.2016, at 14:33, Daniel Beck  wrote:
> 
> Is this https://issues.jenkins-ci.org/browse/JENKINS-33358? Have you tried 
> -Dgroovy.use.classvalue=true?

Never mind, I just saw…

> • ✓ Set -Dgroovy.use.classvalue=true, as reported in JENKINS-33358. Did not 
> help

FWIW I'd double check this is actually set at the correct location on the 
command line, and System.getProperty(…) reports the correct value. I've seen 
too many `java -jar jenkins.war -Dwhatever=something` in the past…

-- 
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/062082C4-33AA-435B-BCF5-1C55AA7CBAC7%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Memory Leak in pipeline?

[Daniel Beck]

Is this https://issues.jenkins-ci.org/browse/JENKINS-33358? Have you tried 
-Dgroovy.use.classvalue=true?

> On 07.11.2016, at 13:58, Daniel Weber  wrote:
> 
> Hi all,
> 
> we keep running into memory issues with pipelines. I put together all 
> information here:
> 
>
> https://github.com/DanielWeber/jenkins-issues/tree/master/pipeline-memory-leak
> 
> including a small example I used to reproduce the problem. We're kind of 
> desperate to 
> find a solution, since we went "all-in" on pipelines and now we are in 
> trouble.
> 
> Any pointers are welcome. We have a test machine running to reproduce this, I 
> saved 
> some heap dumps and can extract any information that could be of help.
> 
> Please help us, Jenkins Developers. You are our only hope... 
> 
> Thanks in advance!
> 
> Best Regards,
> Daniel
> 
> -- 
> 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/2eb3e936-2d80-4a45-8077-bf1dfe39611f%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/E8D11B88-5EA7-4DB1-A5FA-A8BF85474390%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Memory Leak in pipeline?

[Daniel Weber]

Hi all,

we keep running into memory issues with pipelines. I put together all 
information here:

  
 https://github.com/DanielWeber/jenkins-issues/tree/master/pipeline-memory-leak

including a small example I used to reproduce the problem. We're kind of 
desperate to 
find a solution, since we went "all-in" on pipelines and now we are in 
trouble.

Any pointers are welcome. We have a test machine running to reproduce this, 
I saved 
some heap dumps and can extract any information that could be of help.

Please help us, Jenkins Developers. You are our only hope... 

Thanks in advance!

Best Regards,
Daniel

-- 
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/2eb3e936-2d80-4a45-8077-bf1dfe39611f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to make the Jenkins build output as downloadable from Jenkins server machine itself?

[Ben Patterson]

I realize this is not as pretty as was what you were looking for, but you 
can always tee your build scripts to a log file, and archive that.

(I thought I'd answer in case there's not an easier way; but if there is, 
hopefully someone can suggest something more Jenkins-y.  --cheers)

On Monday, November 7, 2016 at 1:34:13 AM UTC-5, Vadivel Natarajan wrote:
>
> Hi All,
>
> I found the artifacts download information from the below link for 
> Appveyor.
>
> https://www.appveyor.com/docs/packaging-artifacts/
>
> Is there anything similar this for jenkins?
>
> Please share your suggestions about this..
>
> Thanks in advance.
>
> On Mon, Nov 7, 2016 at 1:25 AM, Vadivel Natarajan  > wrote:
>
>> I am new to Jenkins. i have configured the Jenkins "Free Style" project 
>> and executing a power shell a script to get an executable application(Exe) 
>> as output. i have searched for some of the plugins to make the Jenkins 
>> output (exe) as downloadable from the Jenkins server machine itself as an 
>> artifact link(download link). But i found the Jenkins plugins to copy the 
>> archive files, upload to ftp and some other plugins.
>>
>> So, Could anyone please suggest me is there any option or plugin 
>> available to make the each Jenkins build output file as downloadable from 
>> the Jenkins server machine by keeping it in a server machine some other 
>> place?
>>
>
>

-- 
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/06317e9f-9827-400e-9527-0aeb8d362ee0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

get sonar credentials in jenkins

[tom vin]

Hi,

I am developing a Jenkins plugin, and I would like to get sonar credentials 
from Jenkins.

Assuming the user define such credentials, of course..

The scenario is – when build finished (upon onCompleted event), I would 
like to submit a request to sonar server, in order to retrieve some results 
from sonar web API.

Is it possible ? if so, how do I get sonar credentials in Jenkins ?

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/1e019af2-2e68-4177-9e84-36d47c0768a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.