"Processing environment for ${pluginClassName}"

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

Re: "Processing environment for ${pluginClassName}"

what do you want to accomplish? *Robert Rajendra* Associate Network/Server Support Engineer IT Hands P: +91 863.087.3094 <+91%2086308%2073094> W: www.ITHands.com On Thu, 24 Jan 2019 at 01:33, Justin Harringa wrote: > I've been trying to figure out what is spitt

Strange Git Polling Behaviour

Hi, We are seeing some very odd behaviour when configuring Pipeline jobs to poll for changes in a BitBucket git repository. For example, we have a couple of jobs which poll the branch specifier "remotes/origin/master" every minute. These jobs simply don't run at all and have to be manually tri

Jenkins folder config hanging

Hi, My new job wants me to use Jenkins, so I'm very new to this. It is freshly installed on my Windows10 machine. after installing Jenkins and plugins, I tried to create folder named "Test Folder" and it hung on config. I tried with out any space in name "TEST" and behaved the same. I exited

How to auto increment a variable for every Jenkins Build

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 which goes as follows String IncBuildNum() { def v= getVersion("path/to/file.xml") def splitted= v..split('\\.') splitted[3]= (((splitted[3] +1 as BigDe

Re: "Processing environment for ${pluginClassName}"

I'd like to eliminate these from console output as it's unnecessary noise. I really don't see the utility in these lines other than plugin debugging (which should probably be in Jenkins logs instead). On Thursday, January 24, 2019 at 2:17:02 AM UTC-8, Robert Rajendra wrote: > > what do you want

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

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: How to auto increment a variable for every Jenkins Build

You can change nextBuildNumber but there are some implications there. Sounds like you're not only looking for an incrementer but a semantic version handler. You do get new build numbers with multi-branch. I could see something like that working by using a branching strategy for each semantic major.

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

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:39 UTC+1, Justin Harringa wrote: > > Any reason you couldn't use the BUILD_NUMBER environment variable for this? > > On Thursday, January

Re: How to configure the plugin authorize-project with configuration-as-code?

Guo Zhenyang writes: > I'm trying to use configuration-as-code to initial the configuration of the > Jenkins. Thought it says JCasC "Support most plugins without extra > development effort" in https://jenkins.io/projects/jcasc/, I can't find a > list of supported plugins or a demo of configuri

Jenkins environmental variables issue for kubernetes slaves running on EKS

I am running simple command sh 'env' inside the jenkins executor which is running in EKS , where am able to view environmental variables defined in jenkins except those with defined by dot(.) for examplemaven.user=deployer -- You received this message because you are subscribed to the Google Gr