Adopting the Next Build Number plugin

Hi, I'm volunteering to adopt this plugin, since it shows that it's up for adoption. It's not that I really want to adopt it, but I do need the latest changes to get released (https://github.com/jenkinsci/next-build-number-plugin/pull/4/commits), and nobody is doing it. Thanks! -- You

Re: Adopting the Next Build Number plugin

Yes On Fri, Jan 29, 2016 at 10:06 AM, Oliver Gondža wrote: > On 01/29/2016 03:48 PM, Akom wrote: > >> Hi, >> >> I'm volunteering to adopt this plugin, since it shows that it's up for >> adoption. >> > > For this account: https://github.com/akomakom? > > -- > oliver > > -- >

Re: Adopting the Next Build Number plugin

On 01/29/2016 04:07 PM, Akom wrote: Yes You are a committer now as well as a component lead. (Please make sure to state your GutHub and JIRA id next time). -- oliver -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe

Re: account creation for dweomer

On 29.01.2016, at 13:34, Kanstantsin Shautsou wrote: > Could somebody describe why `account creation` requests are targeted into > dev list? They can't exactly open a ticket for it… Note that there's already a thread on the infra list, where Craig asks why we

Re: account creation for pkyeck

Created. You should receive an email with the password. On Fri, Jan 29, 2016 at 2:47 AM, Philipp Kyeck wrote: > Jenkins ver. 1.625.3 > > thanks > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe

Re: Adopting the Next Build Number plugin

On 01/29/2016 03:48 PM, Akom wrote: Hi, I'm volunteering to adopt this plugin, since it shows that it's up for adoption. For this account: https://github.com/akomakom? -- oliver -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To

Re: account creation for dweomer

Could somebody describe why `account creation` requests are targeted into dev list? On Thursday, January 28, 2016 at 9:35:29 PM UTC+3, Larry Shatzer, Jr. wrote: > > Created. You should have gotten an email with the password. > > On Thu, Jan 28, 2016 at 11:31 AM, Jacob Blain Christen

account creation for pkyeck

Jenkins ver. 1.625.3 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

Re: [pipeline] Jenkins core version dependency for pipeline?

Depends on which version of Pipeline you want to build against; see its changelog. 1.609.x for current. -- 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

Re: REST api to trigger a job in the build pipeline

Hi Michael, I can trigger job A and job B independently with success using REST. For example , job A is a build job and job B is to deploy to a dev environment. Job B execution is not reflected in the Jenkins UI build pipeline. (should show in green when successful, but still show in blue )

Create a new account

I signed up with the username EliWhite and the email jenk...@eli-white.com 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

Re: [pipeline] Jenkins core version dependency for pipeline?

On Fri, Jan 29, 2016 at 10:08 AM, Antonio Muñiz wrote: > > On Fri, Jan 29, 2016 at 1:24 AM, Craig Rodrigues > wrote: > > > > What version should we use? > > > If you are asking from a user point of view, Pipeline 1.13 requires > 1.609.3. > From a

git-plugin better support for Maven release

Issue: When performing a maven release, it is necessary that the local branch name is the same as the remote branch sans "origin/" to allow successful pushes of the updated pom files. The maven release plugin does a push as "git push origin {local_branch}:{local_branch}". As a result of this,

[pipeline] Hard to find "Click here to forcibly terminate running steps"

Hi, I recently had a pipeline running, and had to terminate it from the web interface by clicking on the red "X" icon. The build did not terminate. At this point, I had to go to: https://jenkins.freebsd.org/job/FreeBSD_HEAD/75/console then I had to scroll all the way to the bottom, and click

Additional information for sign-up request

Please create a new account for me. userid: rami Jenkins for Windows v1.646 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

Re: plugin for code coverage diffs per pr

This sounds like Sputnik, which can easily be adapted to a Jenkins plugin. https://github.com/TouK/sputnik Does this do what you're talking about? Or am I off-base? -- Larry Bordowitz On Friday, January 29, 2016 1:08 PM, Eugene Platonov wrote: Thanks Oliver.Do you

Re: New account request

When trying the account signup link, I get - Oops! Due to the spam problem, we will need additional verification for your sign-up request. More details are found on our wiki on how to get your account created. On Friday,

plugin for code coverage diffs per pr

Hi All, i have setup process using GitHub pull request builder and Groovy Postbuild plugins which reports difference in code coverage per PR.

New account request

I'm posting here based on the wiki instructions to try and get a new account for myself activated. https://wiki.jenkins-ci.org/display/JENKINS/User+Account+on+Jenkins email = donaldrwo...@gmail.com uid = drwoods Thanks, Donald -- You received this message because you are subscribed to the

ideas for

Hi All, i have setup process using GitHub pull request builder and Groovy Postbuild plugins which reports difference in code coverage per PR.

Re: plugin for code coverage diffs per pr

On 01/29/2016 08:21 PM, Eugene Platonov wrote: 2. Is there a better/easier way to achieve same goal? The main point seem to be making PR-building plugin and coverage-collecting one aware of each other. Then you can compare PR build results with latest build based on master. Imho, this is a

Re: New account request

Created. You should get an email with the password. -- Larry On Fri, Jan 29, 2016 at 12:28 PM, drwoods wrote: > When trying the account signup link, I get - > Oops! > > Due to the spam problem, we will need additional verification for your > sign-up request. More

Re: Create a new account

Created. You should get an email with the password. -- Larry On Fri, Jan 29, 2016 at 12:55 PM, Robert Pilachowski wrote: > > I am trying to create a new account with username rpilachowski. > > thanks... > ...robert > > -- > You received this message because you are

Re: plugin for code coverage diffs per pr

Thanks Oliver. Do you mean run coverage collection twice in same build? one for master and one for branch to be merged? I was thinking on this approach, but it will take twice longer to finish. I went with two different builds to run coverage only once during PR and use pre-computed coverage