Jenkins environmental variables issue for kubernetes slaves running on EKS

2019-01-24 Thread Surya yaramada`
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 Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/945e62c1-e63e-46d2-aeae-fa635c03a6ab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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

2019-01-24 Thread Mykola Nikishov
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 configuring plugin 
> authorize-project. Can some share with me the information about it?

Check your http://jenkins/configuration-as-code/ for Actions and
Reference.

For instance, install and configure jenkins and plugins, then use Export
Configuration to get YAML configuration with your changes.

Jenkins Configuration as Code Reference
http://jenkins/configuration-as-code/reference shows all available
options.

-- 
Mykola

https://manandbytes.gitlab.io/
https://manandbytes.github.io/

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/87munpahyt.fsf%40think.
For more options, visit https://groups.google.com/d/optout.


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

2019-01-24 Thread Faad Sayaou
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 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 which goes as follows 
>>
>>
>> String IncBuildNum() {
>>
>> def v= getVersion("path/to/file.xml")
>>
>> def splitted= v..split('\\.')
>> splitted[3]= (((splitted[3] +1 as BigDecimal) + 1 ) as String)
>>
>> return splitted.join('.')
>> }
>>
>> However, I will like to increase this number 1 for every Jenkins build. 
>> Right now 
>> Is this possible?
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/8db59767-f91c-400e-a012-6a46db036261%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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

2019-01-24 Thread Justin Harringa
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.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:39 UTC+1, Justin Harringa wrote:
>>
>> 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 which goes as follows
>>>
>>>
>>> String IncBuildNum() {
>>>
>>> def v= getVersion("path/to/file.xml")
>>>
>>> def splitted= v..split('\\.')
>>> splitted[3]= (((splitted[3] +1 as BigDecimal) + 1 ) as String)
>>>
>>> return splitted.join('.')
>>> }
>>>
>>> However, I will like to increase this number 1 for every Jenkins build.
>>> Right now
>>> Is this possible?
>>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/LfbCVSYZIx8/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/8db59767-f91c-400e-a012-6a46db036261%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAOa798WfxzLy%3DPR99XAXQC%2BwyhiDA_wK2OTpeTHu%3D-ONwtxD%3DQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


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 which goes as follows 
>
>
> String IncBuildNum() {
>
> def v= getVersion("path/to/file.xml")
>
> def splitted= v..split('\\.')
> splitted[3]= (((splitted[3] +1 as BigDecimal) + 1 ) as String)
>
> return splitted.join('.')
> }
>
> However, I will like to increase this number 1 for every Jenkins build. 
> Right now 
> Is this possible?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/b97bdd9d-5238-4db3-abc4-2ef4bd984e36%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: "Processing environment for ${pluginClassName}"

2019-01-24 Thread Justin Harringa
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 to accomplish?
>
>
>
>
> *Robert Rajendra*
>
> Associate Network/Server Support Engineer
>
> IT Hands
>
> P: +91 863.087.3094
>
> W: www.ITHands.com 
>
>
> On Thu, 24 Jan 2019 at 01:33, Justin Harringa  > wrote:
>
>> 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 environment for 
>> org.jenkinsci.plugins.workflow.job.properties.PipelineTriggersJobProperty
>> Processing environment for jenkins.model.BuildDiscarderProperty
>> Processing environment for 
>> org.jenkinsci.plugins.workflow.multibranch.BranchJobProperty
>>
>>
>> Thanks all!
>>
>> Justin
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/CAOa798Vs-SVD4LqAgK92stFd-kycjgzVMkYx_rb-uojfX1R_-A%40mail.gmail.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/d21b6599-9e22-418c-a6fa-7badddaa218b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


How to auto increment a variable for every Jenkins Build

2019-01-24 Thread Faad Sayaou
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 BigDecimal) + 1 ) as String)

return splitted.join('.')
}

However, I will like to increase this number 1 for every Jenkins build. 
Right now 
Is this possible?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0c7cec4a-5506-4e62-9c51-165059505386%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Jenkins folder config hanging

2019-01-24 Thread Minkyu Kim
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 and tried to access the folder, but it threw me the error.. I 
guess it's because the folder is not fully configured yet.

so, why is this happening to me? this is freshly installed Jenkins.

did I miss some installation steps?

I attached my error message.

somebody please help me, thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/90d1d1d8-8248-4410-8481-150ce329565b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
A problem occurred while processing the request. Please check our bug tracker 
to see if a similar problem has already been reported. If it is already 
reported, please vote and put a comment on it to let us gauge the impact of the 
problem. If you think this is a new issue, please file a new issue. When you 
file an issue, make sure to add the entire stack trace, along with the version 
of Jenkins and relevant plugins. The users list might be also useful in 
understanding what has happened.
Stack trace

org.apache.commons.jelly.JellyTagException: 
jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.150.2.jar!/lib/hudson/actions.jelly:39:70:
  
com/cloudbees/hudson/plugins/folder/properties/FolderCredentialsProvider
at 
org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:745)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:289)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at 
org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at 
org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at 
org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)
at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
at 
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at 
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at 
org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
at 
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at 
org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at 
org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)
at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
at 
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at 

Strange Git Polling Behaviour

2019-01-24 Thread Simon Young
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 
triggered.

And we have another job which polls the "remotes/origin/kubernetes" branch, 
which also doesn't run when that branch is changed. However, in the course 
of the build, that pipeline job checks out a second repo like this:

git url: 'g...@bitbucket.org:organisation/repo2.git', branch: 'master', 
credentialsId: 'jenkins_bitbucket'

Now, any changes to that 2nd repo trigger the job in Jenkins - even though 
it's not mentioned in the job config at all.

AND... sometimes, when builds fail (e.g. due to a syntax error in the 
Jenkinsfile), the build tries to run every minute until someone fixes the 
problem.

So in summary, jobs are *not* running when we want them to, and *are* 
running when we don't want them to.

Can anyone offer some pointers as to how to troubleshoot this? The Git 
Polling Log for the job doesn't help much, but it does confirm that changes 
to repo2 are triggering the build:

Started on Jan 24, 2019 10:11:00 AM
Using strategy: Default
[poll] Last Built Revision: Revision 
f77b3b19c4430faa5dc5fae597321d78f6f21209 (refs/remotes/origin/kubernetes)
 > git --version # timeout=10
using GIT_SSH to set credentials Allows Jenkins to fetch code from BitBucket 
repositories
 > git ls-remote -h g...@bitbucket.org:organisation/repo1.git # timeout=10
Found 10 remote heads on g...@bitbucket.org:organisation/repo1.git
Using strategy: Default
[poll] Last Built Revision: Revision 
f77b3b19c4430faa5dc5fae597321d78f6f21209 (refs/remotes/origin/kubernetes)
 > git --version # timeout=10
using GIT_SSH to set credentials Allows Jenkins to fetch code from BitBucket 
repositories
 > git ls-remote -h g...@bitbucket.org:organisation/repo1.git # timeout=10
Found 10 remote heads on g...@bitbucket.org:organisation/repo1.git
Using strategy: Default
[poll] Last Built Revision: Revision 
b5e3423b8575c7ecd90dae310437389b87a4a17f (refs/remotes/origin/master)
 > git --version # timeout=10
using GIT_SSH to set credentials Allows Jenkins to fetch code from BitBucket 
repositories
 > git ls-remote -h g...@bitbucket.org:organisation/repo2.git # timeout=10
Found 5 remote heads on g...@bitbucket.org:organisation/repo2.git
[poll] Latest remote head revision on refs/heads/master is: 
6b413eaa1e715a4f1e3b5826b9b621d60f923792
Done. Took 9.8 sec
Changes found

Any suggestions appreciated!

Simon.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/d92d75ee-113f-41da-b908-f64599f68272%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: "Processing environment for ${pluginClassName}"

2019-01-24 Thread Robert Rajendra
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 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 environment for 
> org.jenkinsci.plugins.workflow.job.properties.PipelineTriggersJobProperty
> Processing environment for jenkins.model.BuildDiscarderProperty
> Processing environment for 
> org.jenkinsci.plugins.workflow.multibranch.BranchJobProperty
>
>
> Thanks all!
>
> Justin
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CAOa798Vs-SVD4LqAgK92stFd-kycjgzVMkYx_rb-uojfX1R_-A%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CABbC_KFUW_OvVSsGr50NCDzEJ3PhkUakt3RUZ2zpvxj28a5%3DGA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


"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 environment for
org.jenkinsci.plugins.workflow.job.properties.PipelineTriggersJobProperty
Processing environment for jenkins.model.BuildDiscarderProperty
Processing environment for
org.jenkinsci.plugins.workflow.multibranch.BranchJobProperty


Thanks all!

Justin

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAOa798Vs-SVD4LqAgK92stFd-kycjgzVMkYx_rb-uojfX1R_-A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.