Tuition Classes in Bangalore

*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,

Re: getScm() on AbstractProject vs. Run

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

Re: Questions on updating flowdock plugin to support pipeline

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

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

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

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

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

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

+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

Re: getScm() on AbstractProject vs. Run

> 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 = …; >

Re: Request for adopting envInject plugin

> 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

Request for adopting envInject plugin

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

Re: Questions on updating flowdock plugin to support pipeline

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

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

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

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

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?

Re: Questions on updating flowdock plugin to support pipeline

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

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

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

Re: Plugin dev for Jenkins 2

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`.

Re: Pipeline Step vs Wrap Environment Variable Writing

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

Re: Failed builds hide Project action

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

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

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

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

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

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

+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

Re: Questions on updating flowdock plugin to support pipeline

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

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

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 >

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

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 г.,

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

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

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

+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

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

> 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,

Re: Memory Leak in pipeline?

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

Re: Memory Leak in pipeline?

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

Re: Memory Leak in pipeline?

> 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

Re: Memory Leak in pipeline?

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: > >

Memory Leak in pipeline?

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

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

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,

get sonar credentials in jenkins

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