Re: How to auto increment a variable for every Jenkins Build

2019-01-24 Thread Justin Harringa
antic major.minor release where build number is the patch version. On Thu, Jan 24, 2019 at 12:09 PM Faad Sayaou wrote: > The build number gets really large which is something we do not want. > Would have been good if there was a way to reset it. > > On Thursday, 24 January 2019 21:01

Re: How to auto increment a variable for every Jenkins Build

2019-01-24 Thread Justin Harringa
Any reason you couldn't use the BUILD_NUMBER environment variable for this? On Thursday, January 24, 2019 at 10:12:30 AM UTC-8, Faad Sayaou wrote: > > Hello everyone, > > I would like to auto increment a number for every Jenkins build. I have a > function which reads value (1.0.0.0) from a file

Re: "Processing environment for ${pluginClassName}"

2019-01-24 Thread Justin Harringa
> what do you want to accomplish? > > > > > *Robert Rajendra* > > Associate Network/Server Support Engineer > > IT Hands > > P: +91 863.087.3094 > > W: www.ITHands.com <http://www.ithands.com/> > > > On Thu, 24 Jan 2019 at 01:33, Justin Harrin

"Processing environment for ${pluginClassName}"

2019-01-24 Thread Justin Harringa
I've been trying to figure out what is spitting out these lines in my console log for a bit. Anyone know off hand what is doing this? My google-foo on GitHub and on the web in general doesn't seem to be coming up with any good results. Is this a plugin or Jenkins in general? Example: Processing e