Re: Backporting for LTS 2.60.3 started

On 2017-07-27 07:19, Andreas Mandel wrote: Thanks for the feedback. Does this mean, according to plan, you release LTS versions even with blocker issues? Or do you judge the severity of the issue different? We are trying to narrow this further down to the versions you have mentioned in the

Re: Backporting for LTS 2.60.3 started

> On 27. Jul 2017, at 07:19, Andreas Mandel wrote: > > Thanks for the feedback. Does this mean, according to plan, you release LTS > versions even with blocker issues? Or do you judge the severity of the issue > different? Yes. The train model means we leave the

Re: Trigger promotions from another job

Hi, Have you got the solution? I am looking for similar feasibility. On Wednesday, April 15, 2015 at 7:24:46 PM UTC+5:30, Varal wrote: > > Hey everyone, > > For the past 2 days I've been struggling with the following issue: > I have a few jobs whose builds are promoted to "Latest" when

Customizing Build Items

Hi, I am new to Jenkins plugin writing . I have written a plugin to add new Item and new build step . However i would like to know if there is a way to exclude few build Items highlighted in blue below . I basically want only *Build* to be displayed once somebody selects my project type . I

Re: Backporting for LTS 2.60.3 started

All valid points, for sure. This aspect of the Train Model was not clear to me... I need to find a way for me how to reduce the risk to run into such issues as much as possible for our productive system. We do tests in advance and feedback - but actually this is not very formal (on our side)

Information Request - Pipeline Execution Node Run Schema

We are building solutions using the RESTful wfapi, and I am trying to discern the node schema that is used on the resultant JSON payloads. Given the output below, I am seeing nodes 6 and 11 that have useful data. My question is, how would I know which nodes from which to gather logs, if were

Jenkins mark usage request from CloudBees

On behalf of CloudBees, I’d like to request the permission to use the following name that uses ‘Jenkins’ in it: - CloudBees Jenkins Advisor To help people understand how this name is going to be used, let me describe a bit about the effort for which we’d like to use this name. CloudBees is

Re: Information Request - Pipeline Execution Node Run Schema

On Thu, Jul 27, 2017 at 1:28 PM, Jimmy Ray wrote: > We are building solutions using the RESTful wfapi This is written by / only used by the Stage View visualization, which is dormant, all the active work going into Blue Ocean. So I would not really recommend relying on it,

HockeyApp Plugin Maintainers

I'd like to contact the maintainers of the HockeyApp plugin, https://wiki.jenkins.io/display/JENKINS/Hockeyapp+Plugin who are listed as: * Oliver Hoeltke (ohoeltke) * Brenton Bartel (Brantone) I've had a couple of pull requests pending for a few months and haven't received any replies when

Re: Information Request - Pipeline Execution Node Run Schema

So, to be clear, you all are not doing anymore work on the Stage View Visualization? Will Blue Ocean expose an API that non-Jenkins apps can consume for these data? On Thursday, 27 July 2017 15:41:40 UTC-4, Jesse Glick wrote: > > On Thu, Jul 27, 2017 at 1:28 PM, Jimmy Ray