Plugin for adoption: build-pipeline-plugin

Hi Jenkins-dev, The build-pipeline-plugin <https://github.com/jenkinsci/build-pipeline-plugin/> is open for adoption. Mark Waite encouraged me to notify this list. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To

Re: Testers for PR in Build Pipeline Plugin

ng? >> >> 2015-12-09 13:26 GMT+01:00 Manuel Jesús Recena Soto : >> > Hello, >> > >> > Especially for users of Build Pipeline Plugin. >> > >> > I've sent a PR [1] (WiP) with a new proposal about how the information >> > is shown.

Re: Testers for PR in Build Pipeline Plugin

Perhaps this might be best posted onto the users list to try and get more people? Richard. On Fri, 11 Dec 2015 at 11:01 Manuel Jesús Recena Soto wrote: > ping? > > 2015-12-09 13:26 GMT+01:00 Manuel Jesús Recena Soto : > > Hello, > > > > Especially for use

Re: Testers for PR in Build Pipeline Plugin

ping? 2015-12-09 13:26 GMT+01:00 Manuel Jesús Recena Soto : > Hello, > > Especially for users of Build Pipeline Plugin. > > I've sent a PR [1] (WiP) with a new proposal about how the information > is shown. There are visible changes but also internal changes (big >

Testers for PR in Build Pipeline Plugin

Hello, Especially for users of Build Pipeline Plugin. I've sent a PR [1] (WiP) with a new proposal about how the information is shown. There are visible changes but also internal changes (big clean up). I'd be very thankful if someone can help to test these changes. Regards,

Re: Commit access to build-pipeline-plugin

to assign / close tickets, or merge a pull request. My username is dalvizu > > > > https://github.com/jenkinsci/build-pipeline-plugin > > https://github.com/dalvizu > > > > > > On Tuesday, November 10, 2015 at 4:50:49 AM UTC-7, Manuel Recena Soto > wrote:

Re: Commit access to build-pipeline-plugin

Daniel? I do not appear to have any additional > permissions, such as write access in the repository, the ability to assign / > close tickets, or merge a pull request. My username is dalvizu > > https://github.com/jenkinsci/build-pipeline-plugin > https://github.com/dalvizu > >

Re: Commit access to build-pipeline-plugin

a pull request. My username is dalvizu https://github.com/jenkinsci/build-pipeline-plugin https://github.com/dalvizu On Tuesday, November 10, 2015 at 4:50:49 AM UTC-7, Manuel Recena Soto wrote: > > Hello, > > 2015-11-10 12:06 GMT+01:00 Daniel Beck >: > > > > On 10.11.20

Re: Commit access to build-pipeline-plugin

Hello, 2015-11-10 12:06 GMT+01:00 Daniel Beck : > > On 10.11.2015, at 11:55, Manuel Jesús Recena Soto wrote: > >> +1. > > Granted committer permission. Thanks. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe fro

Re: Commit access to build-pipeline-plugin

On 10.11.2015, at 11:55, Manuel Jesús Recena Soto wrote: > +1. Granted committer permission. -- 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-

Re: Commit access to build-pipeline-plugin

Hello, 2015-11-10 11:38 GMT+01:00 Daniel Beck : > > On 10.11.2015, at 09:45, Manuel Jesús Recena Soto wrote: > >> I don't know if I can give you grant access, let me check. > > I can. Just state that you're not opposed to having a co-maintainer. +1. Dan, but we should be synced in the roadmap o

Re: Commit access to build-pipeline-plugin

On 10.11.2015, at 09:45, Manuel Jesús Recena Soto wrote: > I don't know if I can give you grant access, let me check. I can. Just state that you're not opposed to having a co-maintainer. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.

Re: Commit access to build-pipeline-plugin

ou are okay with it, I would like to help out, and I am asking here for > commit access, as this is where you referred me to. > > Can you please clarify: are you okay with me being a fellow maintainer of > the build pipeline plugin? And if you are okay, can someone grant me access

Re: Commit access to build-pipeline-plugin

, then I guess that is fine. But if you are okay with it, I would like to help out, and I am asking here for commit access, as this is where you referred me to. Can you please clarify: are you okay with me being a fellow maintainer of the build pipeline plugin? And if you are okay, can someone

Re: Commit access to build-pipeline-plugin

t; that > > you are busy and there is no urgency in those PRs. > > > > However, my original request has not been responded: I originally > privately > > asked Manuel for commit access, and he asked me to request it on this > list. > > > > So I am asking: ma

Re: Commit access to build-pipeline-plugin

st. > > So I am asking: may I please I have commit access to the build pipeline > plugin? I do not believe it is being actively maintained, and I would like > to help out. > > > On Friday, October 30, 2015 at 9:42:32 AM UTC-6, Manuel Recena Soto wrote: >> >> Yes, but I

Re: Commit access to build-pipeline-plugin

Manuel for commit access, and he asked me to request it on this list. So I am asking: may I please I have commit access to the build pipeline plugin? I do not believe it is being actively maintained, and I would like to help out. On Friday, October 30, 2015 at 9:42:32 AM UTC-6, Manuel Recena Soto

Re: Commit access to build-pipeline-plugin

AM UTC-6, Manuel Recena Soto wrote: >> >> Hello Dan, >> >> I replied you few days ago: >> >> https://github.com/jenkinsci/build-pipeline-plugin/pull/79#issuecomment-146625699 >> >> Regards, >> >> 2015-10-20 17:12 GMT+02:00 Dan Alvizu

Re: Commit access to build-pipeline-plugin

Hi, Sorry for the bump. Asking again. Is this the right place to be making this sort of request? On Tuesday, October 20, 2015 at 9:16:01 AM UTC-6, Manuel Recena Soto wrote: > > Hello Dan, > > I replied you few days ago: > > https://github.com/jenkinsci/build-pipel

Re: Commit access to build-pipeline-plugin

Hello Dan, I replied you few days ago: https://github.com/jenkinsci/build-pipeline-plugin/pull/79#issuecomment-146625699 Regards, 2015-10-20 17:12 GMT+02:00 Dan Alvizu : > Hello, > > I'd like to have commit access to the build-pipeline-plugin > (https://github.com/jenkins

Commit access to build-pipeline-plugin

Hello, I'd like to have commit access to the build-pipeline-plugin (https://github.com/jenkinsci/build-pipeline-plugin). I believe the original authors (centrum systems) no longer maintain it, and only recena is involved. I e-mailed him directly and he 302'd me here. I'd like to

Re: Build Pipeline Plugin

I'm interested in being a maintainer, if you need help. I have a few pending PRs myself: https://github.com/jenkinsci/build-pipeline-plugin/pull/89 https://github.com/jenkinsci/build-pipeline-plugin/pull/79 On Wednesday, October 7, 2015 at 2:24:34 PM UTC-6, Manuel Recena Soto

Re: Build Pipeline Plugin

@martinda I'll try to help. If you are interested to "adopt" this plugin, we can work together. 2015-10-07 19:56 GMT+02:00 Kanstantsin Shautsou : > Author blessed @Recena to work on it, i have no objections. Only suggestion > to keep web integration tests working (tested on firefox). > Do you want

Re: Build Pipeline Plugin

Author blessed @Recena to work on it, i have no objections. Only suggestion to keep web integration tests working (tested on firefox). Do you want to be a maintainer? On Wednesday, October 7, 2015 at 8:43:07 PM UTC+3, martinda wrote: > > Any update on the discussion around the ownership of this p

Re: Build Pipeline Plugin

Any update on the discussion around the ownership of this plugin? Lots of pending pull-requests, and I have an itch too (JENKINS-30813 ). -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.

Re: please publish the build pipeline plugin 1.4.8 release notes

My mistake. I thought I'd done it. Regards, 2015-09-17 15:38 GMT+02:00 martinda : > Please publish the build pipeline plugin 1.4.8 release notes to the wiki. > > Thank you. > > -- > You received this message because you are subscribed to the Google Groups > "

Re: please publish the build pipeline plugin 1.4.8 release notes

CC'ed On Thursday, September 17, 2015 at 4:38:36 PM UTC+3, martinda wrote: > > Please publish the build pipeline plugin 1.4.8 release notes to the wiki. > > Thank you. > -- You received this message because you are subscribed to the Google Groups "Jenkins Develope

please publish the build pipeline plugin 1.4.8 release notes

Please publish the build pipeline plugin 1.4.8 release notes to the wiki. Thank you. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jen

Re: Build Pipeline Plugin

all now... Good luck. > > Cheers, Geoff > > On Monday, September 7, 2015 at 7:26:50 PM UTC+10, Manuel Recena Soto > wrote: >> >> Hello, >> >> I have been working on this bug JENKINS-28180 and I sent a PR >> (https://github.com/jenkinsci/build-pipeline-p

Re: Build Pipeline Plugin

> (https://github.com/jenkinsci/build-pipeline-plugin/pull/81). > > There are 13 PR waiting for review and merge. Is there any plan to cut > a release soon? I saw that the last release was done by Kanstantsin. > > I can help on maintenance of this plugin if you (commun

Re: Build Pipeline Plugin

eally useful plugin and disappeared, maybe he knows them and can > ask for comments. > At least they can change Contribution rules that strictly says that > everybody should get reply from them and not from some maillist from guys > that didn’t create this plugin > > https:/

Re: Build Pipeline Plugin

>> ask for comments. >>> At least they can change Contribution rules that strictly says that >>> everybody should get reply from them and not from some maillist from guys >>> that didn’t create this plugin >>> https://wiki.jenkins-ci.org/display/JENKINS/Build+Pip

Re: Build Pipeline Plugin

t reply from them and not from some maillist from guys >> that didn’t create this plugin >> https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin+-+How+to+Contribute >> >> On Sep 9, 2015, at 23:46, Manuel Jesús Recena Soto >> wrote: >> >> Hello Ka

Re: Build Pipeline Plugin

nows them and can > ask for comments. > At least they can change Contribution rules that strictly says that > everybody should get reply from them and not from some maillist from guys > that didn’t create this plugin > https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin+-+How+

Re: Build Pipeline Plugin

maillist from guys that didn’t create this plugin https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin+-+How+to+Contribute <https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin+-+How+to+Contribute> > On Sep 9, 2015, at 23:46, Manuel Jesús Recena Soto wrote: &

Re: Build Pipeline Plugin

>>>> >>>> 2015-09-07 11:26 GMT+02:00 Manuel Jesús Recena Soto : >>>> > Hello, >>>> > >>>> > I have been working on this bug JENKINS-28180 and I sent a PR >>>> > (https://github.com/jenkinsci/build-pipeline-plugin

Re: Build Pipeline Plugin

Manuel Jesús Recena Soto >> >: >>> > Hello, >>> > >>> > I have been working on this bug JENKINS-28180 and I sent a PR >>> > (https://github.com/jenkinsci/build-pipeline-plugin/pull/81). >>> > >>> > There are 13 PR wait

Re: Build Pipeline Plugin

t; 2015-09-07 11:26 GMT+02:00 Manuel Jesús Recena Soto : >>> > Hello, >>> > >>> > I have been working on this bug JENKINS-28180 and I sent a PR >>> > (https://github.com/jenkinsci/build-pipeline-plugin/pull/81). >>> > >>> > There a

Re: Build Pipeline Plugin

On Mon, Sep 7, 2015 at 9:19 PM, Manuel Jesús Recena Soto > wrote: > >> ping? >> >> 2015-09-07 11:26 GMT+02:00 Manuel Jesús Recena Soto : >> > Hello, >> > >> > I have been working on this bug JENKINS-28180 and I sent a PR >> > (https:

Re: Build Pipeline Plugin

28180 and I sent a PR > > (https://github.com/jenkinsci/build-pipeline-plugin/pull/81). > > > > There are 13 PR waiting for review and merge. Is there any plan to cut > > a release soon? I saw that the last release was done by Kanstantsin. > > > > I can help on

Re: Build Pipeline Plugin

ping? 2015-09-07 11:26 GMT+02:00 Manuel Jesús Recena Soto : > Hello, > > I have been working on this bug JENKINS-28180 and I sent a PR > (https://github.com/jenkinsci/build-pipeline-plugin/pull/81). > > There are 13 PR waiting for review and merge. Is there any plan to cut >

Build Pipeline Plugin

Hello, I have been working on this bug JENKINS-28180 and I sent a PR (https://github.com/jenkinsci/build-pipeline-plugin/pull/81). There are 13 PR waiting for review and merge. Is there any plan to cut a release soon? I saw that the last release was done by Kanstantsin. I can help on

Re: build-pipeline-plugin pull request review

ry decide what to do. > > On Wednesday, January 21, 2015 at 11:30:34 AM UTC+3, pat...@patbos.com > wrote: >> >> Hi, >> >> I have created a PR for the build-pipeline-plugin with fixes for >> JENKINS-22665 and JENKINS-19755. >> https://github.com/jenkins

Re: build-pipeline-plugin pull request review

asing again. Please contact me in IRC tomorrow and let's try decide what to do. On Wednesday, January 21, 2015 at 11:30:34 AM UTC+3, pat...@patbos.com wrote: > > Hi, > > I have created a PR for the build-pipeline-plugin with fixes for > JENKINS-22665 and JENKINS-19755. >

build-pipeline-plugin pull request review

Hi, I have created a PR for the build-pipeline-plugin with fixes for JENKINS-22665 and JENKINS-19755. https://github.com/jenkinsci/build-pipeline-plugin/pull/64 The PR will solve problem with the serialization of the User object within MyUserIdCause (JENKINS-22665) and after a restart all

Re: Build pipeline plugin pull request review

ersion with hotfixes, i will try to look/test >>> your PR >>> > when i will have time (if nobody do it earlier). >>> > >>> > On Thursday, November 13, 2014 6:00:32 PM UTC+3, Jeff Storey wrote: >>> >> >>> >> Hi, >>>

Re: Build pipeline plugin pull request review

:00:32 PM UTC+3, Jeff Storey wrote: >> >> >> >> Hi, >> >> >> >> I had opened a pull request about a week ago to fix a few significant >> >> issues with the build pipeline plugin not working for parameterized >> >> bu

Re: Build pipeline plugin pull request review

13, 2014 6:00:32 PM UTC+3, Jeff Storey wrote: > >> > >> Hi, > >> > >> I had opened a pull request about a week ago to fix a few significant > >> issues with the build pipeline plugin not working for parameterized > >> builds (the issues fixe

Re: Build pipeline plugin pull request review

look/test your PR > when i will have time (if nobody do it earlier). > > On Thursday, November 13, 2014 6:00:32 PM UTC+3, Jeff Storey wrote: >> >> Hi, >> >> I had opened a pull request about a week ago to fix a few significant >> issues with the build pipelin

Re: Build pipeline plugin pull request review

y, November 13, 2014 6:00:32 PM UTC+3, Jeff Storey wrote: >> >> Hi, >> >> I had opened a pull request about a week ago to fix a few significant >> issues with the build pipeline plugin not working for parameterized >> builds (the issues fixes here were mentioned i

Re: Build pipeline plugin pull request review

gt; Hi, > > I had opened a pull request about a week ago to fix a few significant > issues with the build pipeline plugin not working for parameterized > builds (the issues fixes here were mentioned in 7 different JIRA > issues that I found). This is my first commit to Jenkins, so I was &

Build pipeline plugin pull request review

Hi, I had opened a pull request about a week ago to fix a few significant issues with the build pipeline plugin not working for parameterized builds (the issues fixes here were mentioned in 7 different JIRA issues that I found). This is my first commit to Jenkins, so I was hoping someone could

Re: bump new build-pipeline-plugin version

No replies for a long time. Released. I was unable to find where previous changelogs are and added new entry on wiki page with link to GH diff. On Friday, October 24, 2014 1:19:37 PM UTC+3, Kanstantsin Shautsou wrote: > > Kindly reminder. > > On Wednesday, October 22, 2014 12:25:01 AM UTC+3, Kan

Re: bump new build-pipeline-plugin version

Kindly reminder. On Wednesday, October 22, 2014 12:25:01 AM UTC+3, Kanstantsin Shautsou wrote: > > Build from master resolved broken jenkins because of > https://issues.jenkins-ci.org/browse/JENKINS-22146 . Please release new > version or bless me to run maven-release-plugin. > -- You receiv

bump new build-pipeline-plugin version

Build from master resolved broken jenkins because of https://issues.jenkins-ci.org/browse/JENKINS-22146 . Please release new version or bless me to run maven-release-plugin. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe

Pending pull request: build-pipeline-plugin

Hi, About 10 days ago, I submitted a patch (with additional tests) for the Build Pipeline Plugin in order to fix JENKINS-22146 (view faces an infinite recursion under certain circumstances). Successful pull request is here: https://github.com/jenkinsci/build-pipeline-plugin/pull/41 May I get

Re: Commit access to Build-pipeline-plugin

Done. Welcome aboard! Am 08.04.2014 um 18:53 schrieb Thomas Carsuzan : > Hi, > > I submitted 3 pull requests 25 days ago and still no review > (https://github.com/jenkinsci/build-pipeline-plugin/pulls) > May I get commit access to this repository ? > > Github Accou

Commit access to Build-pipeline-plugin

Hi, I submitted 3 pull requests 25 days ago and still no review ( https://github.com/jenkinsci/build-pipeline-plugin/pulls) May I get commit access to this repository ? Github Account : Tetradeus (https://github.com/Tetradeus) Regards, Thomas -- You received this message because you are

Re: Commit access to the Build Pipeline Plugin?

Will do, thanks. On 14 Oct 2013 13:16, "Ulli Hafner" wrote: > I added you as a committer. Welcome aboard! > > Maybe it would make sense to start your work in a branch until you get in > touch with Geoff. So no work will be lost... > > Ulli > > Am 14.10.2013 um 11:16 schrieb Tom Akehurst : > > My

Re: Commit access to the Build Pipeline Plugin?

I added you as a committer. Welcome aboard! Maybe it would make sense to start your work in a branch until you get in touch with Geoff. So no work will be lost... Ulli Am 14.10.2013 um 11:16 schrieb Tom Akehurst : > My github name is tomakehurst. I'm not sure how to contact Geoff directly. >

Re: Commit access to the Build Pipeline Plugin?

My github name is tomakehurst. I'm not sure how to contact Geoff directly. On 14 Oct 2013 09:21, "Ulli Hafner" wrote: > What is your github user name? > > I think it make sense to get in contact with Geoff on how to proceed. > > Ulli > > Am 12.10.2013 um 17:37 schrieb Tom Akehurst : > > I've noti

Re: Commit access to the Build Pipeline Plugin?

What is your github user name? I think it make sense to get in contact with Geoff on how to proceed. Ulli Am 12.10.2013 um 17:37 schrieb Tom Akehurst : > I've noticed Geoff Bullen has started committing to this again. Anyone know > whether this means he's picking up the reins again? > > If n

Re: Commit access to the Build Pipeline Plugin?

I've noticed Geoff Bullen has started committing to this again. Anyone know whether this means he's picking up the reins again? If not, could someone give me commit access? Thanks, Tom On 4 October 2013 10:21, Tom Akehurst wrote: > OK. I can't guarantee I'll be able to spend tons of time on i

Re: Commit access to the Build Pipeline Plugin?

OK. I can't guarantee I'll be able to spend tons of time on it, but with that proviso please count me in. On 2 October 2013 23:05, Jesse Glick wrote: > On Mon, Sep 23, 2013 at 9:04 AM, Tom Akehurst > wrote: > > a) Its last release was the 5th of September, which suggests someone is > > still d

Re: Commit access to the Build Pipeline Plugin?

On Mon, Sep 23, 2013 at 9:04 AM, Tom Akehurst wrote: > a) Its last release was the 5th of September, which suggests someone is > still doing some maintenance on it i.e. it's not completely dormant Kohsuke and I did a couple fixes during the Jenkins CI Code Camp, since there seemed to be no one ma

Commit access to the Build Pipeline Plugin?

Hi, I raised a pull request against this a couple of weeks ago, and since it's gone un-merged I got an email suggesting I request commit access. I'm happy to take on some bug fixing and refactoring of this plugin as I'm using it heavily at the moment. However a) Its last release was the 5th of

build-pipeline-plugin null pointer

I recently upgraded to jenkins 1.529 and build-pipeline-plugin 1.3.5. I have a downstream job that is invoked manually. An authenticated user can trigger the build from the pipeline view, the build will seem to start; but, within a few seconds go back blue. No record of a failed build or

Re: build-pipeline-plugin Problem building

The build-pipeline-plugin tags each release. The current release is 1.3.5, you can see there is a tag, 'build-pipeline-plugin-1.3.5'. I would checkout out that tag, create a branch and do what you need. But even if you make no changes, that point in the repo should build cleanly. I c

build-pipeline-plugin Problem building

Hello. I have an issue with the build-pipeline-plugin. Whenewer my pipeline gets more than two steps, rendering of the pipeline fails with a NPE in ProjectForm. I can see in the source that a commit lately has (hopefully) fixed this by checking for null on the actions of the project. Now I

Re: Modify Build Pipeline plugin to display test results for each build

Any help is much appreciated. Thanks in advance! > > xmlns:d="jelly:define" xmlns:l="/lib/layout" xmlns:t="/lib/hudson" > xmlns:f="/lib/form" xmlns:i="jelly:fmt"> > type="text/css" rel="stylesheet" />

Modify Build Pipeline plugin to display test results for each build

Hi guys, I'm new to both Jenkins and jelly, and I'm struggling with a task that should be relatively simple -- displaying test results, as in "10 fail/20 pass". I want to do this at the bottom of each node in the Build Pipeline, in the highlighted area below in bpp.jelly. I tried using jelly's