Re: fatal: git index-pack failed

[Kevin Stevens]

Hi Mark - whilst looking for a place to stash my reference repo I 
discovered that Jenkins is keeping a cache of git checkouts in the 
/var/lib/jenkins/cache folder, and by deleting these files the multibranch 
pipeline scan now succeeds, so there was obviously something corrupt in 
that cache (possibly caused by a recent instability issue with the Jenkins 
server hardware), so I've not implemented a reference repo.
Thanks for your help ;-)

Kevin

On Tuesday, 2 July 2019 15:25:41 UTC+1, Kevin Stevens wrote:
>
> Thanks for the responses and the issue link Mark, I've increased the Git 
> timeout value as described, and confirmed in the log that the 30 minute 
> timeout is in effect, but I'm still seeing the same failure (i.e. fatal 
> error in Scan Multibranch Pipeline Now).
> I was pretty confident that there's not a timeout issue as the failure 
> occurs in a matter of seconds, so I'm going to try the reference repo 
> approach which seems like it should work, but it would appear to be an 
> issue within the git client parsing to me. I'll confirm my outcome.
>
> Regards, Kevin
>
> On Tuesday, 2 July 2019 13:37:41 UTC+1, Mark Waite wrote:
>>
>> Sorry, I didn't read your description thoroughly enough.  You said:
>>
>> I'm getting a fatal error reported when doing a repository scan (Scan 
>>> Multibranch Pipeline Now) which was previously working.  
>>>
>>
>> The command line git log output indicates that your repository is large 
>> enough that it may be reaching the default 10 minute clone timeout.  Refer 
>> to https://issues.jenkins-ci.org/browse/JENKINS-38973 for a discussion 
>> of possible workarounds.
>>
>> On Tue, Jul 2, 2019 at 6:31 AM Mark Waite  wrote:
>>
>>> The repository in the workspace on the agent running that build is 
>>> probably damaged.  Wipe the workspace on the agent and run the job again.
>>>
>>> If wiping the workspace and running the job again does not resolve it, 
>>> you may also be encountering a timeout while cloning the repository.  
>>> Increase the timeout for the repository clone from its default of 10 
>>> minutes to something large enough that it will allow you to clone the 
>>> repository.
>>>
>>> The amount of output you're showing hints that the repository is large 
>>> or the network connection between the agent and the upstream cloned 
>>> repository is slow.  In either of those cases, you probably want to reduce 
>>> the clone time and the disc space use by applying one or more of the 
>>> techniques described in "Git in the Large 
>>> <https://youtu.be/jBGFjFc6Jf8?t=6434>".  Those techniques include (1) 
>>> reference repositories on the agent, (2) narrow refspecs, (3) shallow 
>>> clones, and (4) sparse checkouts.
>>>
>>> If this is a Pipeline repository and the failure is during the initial 
>>> clone of the repository, then you may also need to use lightweight checkout 
>>> to only checkout the Jenkinsfile rather than the entire repository.  
>>> Alternately for Pipelines, if your git provider is GitHub, Bitbucket, or 
>>> Gitea, you can significantly improve performance by using those branch 
>>> source plugins to manage the Pipeline instead of relying on low-level 
>>> command line git calls.
>>>
>>> Reference repositories are usually the most effective technique to 
>>> reduce data transfer time and disc space use for large git repositories.  
>>> Allan Burdajewicz of CloudBees wrote a great article on reference 
>>> repositories at 
>>> https://support.cloudbees.com/hc/en-us/articles/115001728812-Using-a-Git-reference-repository
>>>  .
>>>
>>> On Tue, Jul 2, 2019 at 5:51 AM Kevin Stevens  wrote:
>>>
>>>> I'm getting a fatal error reported when doing a repository scan (Scan 
>>>> Multibranch Pipeline Now) which was previously working.
>>>> I've run the git commands manually from the command line (copied and 
>>>> pasted) and they appear to work correctly, so it seems like a problem with 
>>>> the Jenkins git client plugin.
>>>>
>>>> The scan log is below (repository name and account information modified 
>>>> for security reasons).
>>>> I'm not clear if this is a GIT or a Jenkins git client problem. I've 
>>>> cleared the Jenkins workspace and updated to the latest Jenkins plugins 
>>>> (running on Ubuntu 18.04).
>>>> Is anyone able to offer help in debugging this issue please?
>>>>

Re: fatal: git index-pack failed

[Kevin Stevens]

Thanks for the responses and the issue link Mark, I've increased the Git 
timeout value as described, and confirmed in the log that the 30 minute 
timeout is in effect, but I'm still seeing the same failure (i.e. fatal 
error in Scan Multibranch Pipeline Now).
I was pretty confident that there's not a timeout issue as the failure 
occurs in a matter of seconds, so I'm going to try the reference repo 
approach which seems like it should work, but it would appear to be an 
issue within the git client parsing to me. I'll confirm my outcome.

Regards, Kevin

On Tuesday, 2 July 2019 13:37:41 UTC+1, Mark Waite wrote:
>
> Sorry, I didn't read your description thoroughly enough.  You said:
>
> I'm getting a fatal error reported when doing a repository scan (Scan 
>> Multibranch Pipeline Now) which was previously working.  
>>
>
> The command line git log output indicates that your repository is large 
> enough that it may be reaching the default 10 minute clone timeout.  Refer 
> to https://issues.jenkins-ci.org/browse/JENKINS-38973 for a discussion of 
> possible workarounds.
>
> On Tue, Jul 2, 2019 at 6:31 AM Mark Waite  > wrote:
>
>> The repository in the workspace on the agent running that build is 
>> probably damaged.  Wipe the workspace on the agent and run the job again.
>>
>> If wiping the workspace and running the job again does not resolve it, 
>> you may also be encountering a timeout while cloning the repository.  
>> Increase the timeout for the repository clone from its default of 10 
>> minutes to something large enough that it will allow you to clone the 
>> repository.
>>
>> The amount of output you're showing hints that the repository is large or 
>> the network connection between the agent and the upstream cloned repository 
>> is slow.  In either of those cases, you probably want to reduce the clone 
>> time and the disc space use by applying one or more of the techniques 
>> described in "Git in the Large <https://youtu.be/jBGFjFc6Jf8?t=6434>".  
>> Those techniques include (1) reference repositories on the agent, (2) 
>> narrow refspecs, (3) shallow clones, and (4) sparse checkouts.
>>
>> If this is a Pipeline repository and the failure is during the initial 
>> clone of the repository, then you may also need to use lightweight checkout 
>> to only checkout the Jenkinsfile rather than the entire repository.  
>> Alternately for Pipelines, if your git provider is GitHub, Bitbucket, or 
>> Gitea, you can significantly improve performance by using those branch 
>> source plugins to manage the Pipeline instead of relying on low-level 
>> command line git calls.
>>
>> Reference repositories are usually the most effective technique to reduce 
>> data transfer time and disc space use for large git repositories.  Allan 
>> Burdajewicz of CloudBees wrote a great article on reference repositories at 
>> https://support.cloudbees.com/hc/en-us/articles/115001728812-Using-a-Git-reference-repository
>>  .
>>
>> On Tue, Jul 2, 2019 at 5:51 AM Kevin Stevens > > wrote:
>>
>>> I'm getting a fatal error reported when doing a repository scan (Scan 
>>> Multibranch Pipeline Now) which was previously working.
>>> I've run the git commands manually from the command line (copied and 
>>> pasted) and they appear to work correctly, so it seems like a problem with 
>>> the Jenkins git client plugin.
>>>
>>> The scan log is below (repository name and account information modified 
>>> for security reasons).
>>> I'm not clear if this is a GIT or a Jenkins git client problem. I've 
>>> cleared the Jenkins workspace and updated to the latest Jenkins plugins 
>>> (running on Ubuntu 18.04).
>>> Is anyone able to offer help in debugging this issue please?
>>>
>>>
>>> [Tue Jul 02 09:48:00 BST 2019] Starting branch indexing...
>>>  > git --version # timeout=10
>>> using GIT_ASKPASS to set credentials Jenkins Bitbucket User
>>>  > git ls-remote --symref 
>>> g...@bitbucket.org:my-company-name/my-repository-name.git # timeout=10
>>>  > git rev-parse --is-inside-work-tree # timeout=10
>>> Setting origin to 
>>> g...@bitbucket.org:my-company-name/my-repository-name.git
>>>  > git config remote.origin.url 
>>> g...@bitbucket.org:my-company-name/my-repository-name.git # timeout=10
>>> Fetching & pruning origin...
>>> Listing remote references...
>>>  > git config --get remote.origin.url # timeout=10
>>>  > git --version # timeout=10
>&

fatal: git index-pack failed

[Kevin Stevens]

I'm getting a fatal error reported when doing a repository scan (Scan 
Multibranch Pipeline Now) which was previously working.
I've run the git commands manually from the command line (copied and 
pasted) and they appear to work correctly, so it seems like a problem with 
the Jenkins git client plugin.

The scan log is below (repository name and account information modified for 
security reasons).
I'm not clear if this is a GIT or a Jenkins git client problem. I've 
cleared the Jenkins workspace and updated to the latest Jenkins plugins 
(running on Ubuntu 18.04).
Is anyone able to offer help in debugging this issue please?


[Tue Jul 02 09:48:00 BST 2019] Starting branch indexing...
 > git --version # timeout=10
using GIT_ASKPASS to set credentials Jenkins Bitbucket User
 > git ls-remote --symref 
g...@bitbucket.org:my-company-name/my-repository-name.git # timeout=10
 > git rev-parse --is-inside-work-tree # timeout=10
Setting origin to g...@bitbucket.org:my-company-name/my-repository-name.git
 > git config remote.origin.url 
g...@bitbucket.org:my-company-name/my-repository-name.git # timeout=10
Fetching & pruning origin...
Listing remote references...
 > git config --get remote.origin.url # timeout=10
 > git --version # timeout=10
using GIT_ASKPASS to set credentials Jenkins Bitbucket User
 > git ls-remote -h 
g...@bitbucket.org:my-company-name/my-repository-name.git # timeout=10
Fetching upstream changes from origin
 > git config --get remote.origin.url # timeout=10
using GIT_ASKPASS to set credentials Jenkins Bitbucket User
 > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* 
--prune
ERROR: [Tue Jul 02 09:48:10 BST 2019] Could not fetch branches from source 
498872a6-3888-419f-9d2f-a2baa4520968
hudson.plugins.git.GitException: Command "git fetch --tags --progress 
origin +refs/heads/*:refs/remotes/origin/* --prune" returned status code 
128:
stdout: 
stderr: remote: Counting objects: 114, done.
remote: Compressing objects:   0% (1/114)   
remote: Compressing objects:   1% (2/114)   
remote: Compressing objects:   2% (3/114)   
remote: Compressing objects:   3% (4/114)   
remote: Compressing objects:   4% (5/114)   
remote: Compressing objects:   5% (6/114)   
remote: Compressing objects:   6% (7/114)   
remote: Compressing objects:   7% (8/114)   
remote: Compressing objects:   8% (10/114)   
remote: Compressing objects:   9% (11/114)   
remote: Compressing objects:  10% (12/114)   
remote: Compressing objects:  11% (13/114)   
remote: Compressing objects:  12% (14/114)   
remote: Compressing objects:  13% (15/114)   
remote: Compressing objects:  14% (16/114)   
remote: Compressing objects:  15% (18/114)   
remote: Compressing objects:  16% (19/114)   
remote: Compressing objects:  17% (20/114)   
remote: Compressing objects:  18% (21/114)   
remote: Compressing objects:  19% (22/114)   
remote: Compressing objects:  20% (23/114)   
remote: Compressing objects:  21% (24/114)   
remote: Compressing objects:  22% (26/114)   
remote: Compressing objects:  23% (27/114)   
remote: Compressing objects:  24% (28/114)   
remote: Compressing objects:  25% (29/114)   
remote: Compressing objects:  26% (30/114)   
remote: Compressing objects:  27% (31/114)   
remote: Compressing objects:  28% (32/114)   
remote: Compressing objects:  29% (34/114)   
remote: Compressing objects:  30% (35/114)   
remote: Compressing objects:  31% (36/114)   
remote: Compressing objects:  32% (37/114)   
remote: Compressing objects:  33% (38/114)   
remote: Compressing objects:  34% (39/114)   
remote: Compressing objects:  35% (40/114)   
remote: Compressing objects:  36% (42/114)   
remote: Compressing objects:  37% (43/114)   
remote: Compressing objects:  38% (44/114)   
remote: Compressing objects:  39% (45/114)   
remote: Compressing objects:  40% (46/114)   
remote: Compressing objects:  41% (47/114)   
remote: Compressing objects:  42% (48/114)   
remote: Compressing objects:  43% (50/114)   
remote: Compressing objects:  44% (51/114)   
remote: Compressing objects:  45% (52/114)   
remote: Compressing objects:  46% (53/114)   
remote: Compressing objects:  47% (54/114)   
remote: Compressing objects:  48% (55/114)   
remote: Compressing objects:  49% (56/114)   
remote: Compressing objects:  50% (57/114)   
remote: Compressing objects:  51% (59/114)   
remote: Compressing objects:  52% (60/114)   
remote: Compressing objects:  53% (61/114)   
remote: Compressing objects:  54% (62/114)   
remote: Compressing objects:  55% (63/114)   
remote: Compressing ob

Passing gitlab environment variable from upstream to 2 downstream jobs.

[Kevin Brizida]

I'm a noob to Jenkins so apologies in advance if there's a basic simple 
solution to this. So we're in the middle of converting a project that ran 
solely on Windows to run on both linux and windows. So we only had a 
windows slave node building the project on an MR from gitlab, worked fine. 

I created a linux slave node that I tested soley with a test mr and it 
worked fine. 

So what I'm tasked with is based on one Merge request from gitlab, i need 
to fire off the build on both Nodes using an upstream job. That seems to be 
working also.

2 things I'm yet to accomplish:

First the more important of the 2, is when i run the downstream jobs 
independently with git ab web hook linked to each individual one. the 
project builds and and gitlab environment variable are in build steps (ex. 
clone test/${gitlabSourceBranch})

in my upstream job theyre not there when i try to echo them, and once i 
figure out how to echo them, how can i pass them to my windows and linux 
downstream job?

Second if one of those downstream jobs, how do I make the upstream job 
aware of the failure, right now the status is a success whether the 
downstream job fails or not. I'd like the upstream job to reflect the 
failure from the downstream jobs.

As an FYI, i cant use pipleines for the times being for reasons unknown to 
me at the moment, Thats future endeavor for the company with changes to new 
versions of Jenkins. Currently on Jenkins 2.127

Thanks in advance for the help

-- 
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/7d26c113-f0f7-4d37-98f6-c4b371180ec5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Is pipeline timeout suppose to work?

[Kevin Chow]

Hi Jer,

I'd like to followup if you figured out how to do timeout with Jenkins 
Scripted Pipeline. I'm looking into a solution to resolve it. 

I have something like but it doesn't work out for me.

timeout(5) {
node("docker") {
sh"""
//do something
"""
}
}



Thanks,

Kevin



On Wednesday, July 12, 2017 at 7:55:33 AM UTC-7, jer...@bodycad.com wrote:
>
> I think I got my answer about it into the console log after a hang, I had 
> to restart the jenkins service and got this as a result:
>
> *04:18:53* 
> *04:18:53* Build succeeded.
> *04:18:53* 0 Warning(s)
> *04:18:53* 0 Error(s)
> *04:18:53* 
> *04:18:53* Time Elapsed 00:14:25.77
> Waiting to resume part of Bodycad cpp projects » CAD_CPP_ContinuousBuild 
> #172: JGMachine <http://bcadlx03/Jenkins/computer/JGMachine/> is offline
> Waiting to resume part of Bodycad cpp projects » CAD_CPP_ContinuousBuild 
> #172: JGMachine <http://bcadlx03/Jenkins/computer/JGMachine/> is offline
> Ready to run at Wed Jul 12 10:50:34 EDT 2017
> *10:50:34* Timeout expired 5 hr 46 min ago
> *10:50:34* Cancelling nested steps due to timeout
> [Pipeline] }
> [Pipeline] // timeout
> [Pipeline] }
> [Pipeline] // stage
> [Pipeline] }
> [Pipeline] // timestamps
> [Pipeline] echo
> Error occurred during build:
> [Pipeline] echo
> java.lang.Exception: Resume after a restart not supported for non-blocking 
> synchronous steps
>
>
> the line: 
> *10:50:34* Timeout expired 5 hr 46 min ago
> tell me that it cannot be used that way.
>

-- 
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/e67e9e53-7e45-4426-83d1-fa062ef15d19%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Unable to run git repository on jenkins which is deplyed under tomcat8

[Kevin McCann]

There's a bunch of ways you could do this, depending on your set up.

You can set the Jenkins job to only build on changes to branches that match 
a certain string, then have all work done in the specific subfolders match 
that string. Like "/ui-*"

You could set up a second job that only checks for changes in those 
subfolders, then only kicks off the build job you already have if it finds 
changes.

If you are in a pipeline, you can access the changelog and grep for what 
you need.
https://support.cloudbees.com/hc/en-us/articles/217630098-How-to-access-Changelogs-in-a-Pipeline-Job-

If it were me in one of my typical projects, I'd check for changed files in 
the pipeline, and trigger the build based on the result of the search for 
the subfolder.

Stack Overflow posts that'll help:
https://stackoverflow.com/questions/5243593/how-to-trigger-a-build-only-if-changes-happen-on-particular-set-of-files
https://stackoverflow.com/questions/16054177/jenkins-plugin-for-triggering-build-whenever-any-file-changed-in-a-given-directo?noredirect=1&lq=1
https://stackoverflow.com/questions/6260383/how-to-get-list-of-changed-files-since-last-build-in-jenkins-hudson/39862273#39862273

Good luck!

On Friday, February 1, 2019 at 2:51:50 PM UTC-5, Panchangam Kalyan wrote:
>
> Quick help,
>
> Is there a way to trigger Jenkins job on changes only to a specific 
> subfolder in the Git repository.?
> Traditionally, we were using VSTS for CICD and it has inbuilt GIT hooks to 
> handle request but in Jenkins i couldn't find any concrete solution.
>
> Can some body please help.
>
>
> On Fri, Feb 1, 2019 at 7:29 AM Mark Waite  > wrote:
>
>>
>>
>> On Fri, Feb 1, 2019 at 5:10 AM Archana Srichandan > > wrote:
>>
>>> Hi,
>>>  Thanks for your reply. I gave the url as serverip:path to repository, 
>>> The username is given as the user of the remote server to which to do SSH. 
>>> I have created a private key for the user which I am logged in into the 
>>> jenkins server. I am copying the private key directly and also the 
>>> passphrase. Still I am not able to clone from the repository. Please let me 
>>> know if I am doing something wrong. 
>>> Note. Jenkins is running behind tomcat. (I deploy jenkins through 
>>> tomcat).
>>>
>>
>> Does the passphrase include characters which are special to the shell 
>> (like '#', '*', '(', or ')')?  If so, use a private key with a passphrase 
>> that does not include characters that are special to the shall.  The 
>> current git client plugin implementation has a problem with shell special 
>> characters in passphrases.
>>
>> Mark Waite
>>  
>>
>>> Regards,
>>> Archana Srichandan
>>>
>>>
>>> On Thu, Jan 31, 2019 at 8:58 PM Mark Waite >> > wrote:
>>>
 Did you assign a private key credential to that job?  A 
 username.password credential won't work with an SSH URL.  A private key 
 credential won't work with an http or https URL.

 If the private key has a passphrase, did you provide the passphrase 
 when defining the credential in Jenkins?

 Did you confirm that the private key will authenticate from the command 
 line?

 Mark Waite

 On Tue, Jan 29, 2019 at 3:17 PM > 
 wrote:

> Hi All,
>
> I am not able to run my git repo on Jenkins ,attach is the screen shot 
> for your reference.
>
> Regards,
> Archana Srichandan
>
> -- 
> 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/50dd7ccf-9ad6-45e3-a5fc-9cee050a7737%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


 -- 
 Thanks!
 Mark Waite

 -- 
 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/CAO49JtGvL%3DxHGju7a%2BbGvVd7Bhs7gvhr09Qd%3Dr3zkY1OOs2DhA%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-use...@googlegroups.com .
>>> To

jenkins jobs view problem

[Kevin]

*Dear All:*
*My Jenkins was previously version 2.138 using the official image on docker 
hub, using gitlab for authorization, upgrading to any version of the 
general user's project view cannot be displayed, error 404 and An error 
occurred when retrieving jobs for this view. Please consult the Jenkins 
logs For details. All views of the administrator are normal. This problem 
has been bothering me for a month, I hope I can get the guidance of the 
great gods, I am very grateful!*

*Sincerely Kevin*

-- 
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/be03dbb0-cf80-446b-955f-00cd7a74335b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Aggregating jobs and config from many servers into one

[Kevin White]

Thanks Rajendra.  I had avoided using the CLI because there are so many 
jobs to be moved, and it doesn't move plugins, credentials, etc.  I was 
hoping for a more-automated way of doing it, but it might not exist.  I 
have looked at butler, I'll take another look.

On Friday, August 10, 2018 at 11:33:21 AM UTC-6, rajendraprasad reddy wrote:
>
> Check whether the remote machines enabled REST Interface or jenkins cli, 
> you can easily export and import  jobs from any jenkins server to any other 
> jenkins server, other useful utility also I found called 'butler, script, 
> check online if you cannot find it I can send you link for the that to 
> download and use it, it is very simple, it also supports export and 
> importing plugins too.
>
> Thanks ,
> rajendra@gmail.com 
>
> On Fri 10 Aug, 2018, 10:00 PM Kevin White,  > wrote:
>
>> My team has several different Jenkins servers that we have decided to 
>> aggregate into just one.  I'm somewhat familiar with the process of 
>> migrating one old Jenkins instance to a new one, where the new one is 
>> essentially a clone of the old.  What I haven't seen is instructions for 
>> combining jobs/configs/plugins from multiple instances into one.
>>
>> I have installed the Job Import plugin, but for some reason, it doesn't 
>> list the jobs on most of the remote machines so they can't be imported.  No 
>> errors, just no jobs listing.  I suspect it may have something to do with 
>> the fact that the remote machines all use SSL.  I have provided working 
>> credentials in the plugin configuration for each of the remote instances, 
>> so that's not the issue.
>>
>> I have looked at thinBackup plugin, but it appears that it will restore 
>> only from one source, not many.
>>
>> If I copy the jobs folder over from the remotes, I won't get all the 
>> necessary plugins and other configuration files.
>>
>> I am currently trying to rsync from each of the remotes to the new one, 
>> but I have a feeling that will result in some incompatibilities.
>>
>> Any suggestions on how best to accomplish this?
>>
>> -- 
>> 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/d88f55f3-4712-4e47-9f50-930a1f7dc207%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/d88f55f3-4712-4e47-9f50-930a1f7dc207%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> 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/6f36556d-677f-4b89-b4bf-5a4e1451d870%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Aggregating jobs and config from many servers into one

[Kevin White]

My team has several different Jenkins servers that we have decided to 
aggregate into just one.  I'm somewhat familiar with the process of 
migrating one old Jenkins instance to a new one, where the new one is 
essentially a clone of the old.  What I haven't seen is instructions for 
combining jobs/configs/plugins from multiple instances into one.

I have installed the Job Import plugin, but for some reason, it doesn't 
list the jobs on most of the remote machines so they can't be imported.  No 
errors, just no jobs listing.  I suspect it may have something to do with 
the fact that the remote machines all use SSL.  I have provided working 
credentials in the plugin configuration for each of the remote instances, 
so that's not the issue.

I have looked at thinBackup plugin, but it appears that it will restore 
only from one source, not many.

If I copy the jobs folder over from the remotes, I won't get all the 
necessary plugins and other configuration files.

I am currently trying to rsync from each of the remotes to the new one, but 
I have a feeling that will result in some incompatibilities.

Any suggestions on how best to accomplish this?

-- 
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/d88f55f3-4712-4e47-9f50-930a1f7dc207%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: "Bitbucket Team/Project"

[Kevin Ford]

Having same issue, been trying to figure out for almost 2 weeks

On Monday, March 5, 2018 at 10:54:25 PM UTC-5, Christian Gagneraud wrote:
>
> I'm trying the "Bitbucket Team/Project" (which uses the "multibranch 
> Pipeline"). 
> Using "jenkinsci/blueocean:latest" docker image. 
>
> When i create a new ""Bitbucket Team/Project"" item, the BB project is 
> scanned, project is added and repo too. Repo that have a 
> "/Jenkinsfile" are picked up and built, everything seems to work as 
> expected. 
>
> Now when i go to one of the generated "multibranch pipeline" job, and 
> click the "View configuration" (no "Configure" accessible), I land on 
> a page that allows me to edit the job, but I get a Jenkins screenshot 
> showing "admin is missing Job/Configure permission" in between 
> "repository name" and "Behaviors" on the 
> https://jenkins-url/job/job-name/configure page. 
>
> When I manually create a custom multi-branch pipeline job with the 
> same bitbucket branch source, i do not see this message at all, and 
> there is nothing b/w "repository name" and "Behaviors". 
>
> Did I misconfigured something? The admin account is created suing a 
> pre-configure groovy hook: 
>
> - 
> def instance = Jenkins.getInstance() 
>
> def user = "admin" 
> def pass = "..." 
> def hudsonRealm = new HudsonPrivateSecurityRealm(false) 
> hudsonRealm.createAccount(user, pass) 
> instance.setSecurityRealm(hudsonRealm) 
>
> def strategy = new FullControlOnceLoggedInAuthorizationStrategy() 
> strategy.setAllowAnonymousRead(false) 
> instance.setAuthorizationStrategy(strategy) 
> instance.save() 
> - 
>
> Is it the cause of my problem? 
>
> Does anyone has example on how to use `RoleBasedAuthorizationStrategy` 
> from a groovy script? 
> I was stuck b/c I couldn't call the private `createAdminRole()` method 
> (and I'm an absolute noob with groovy and jenkins scripting) 
>
> Thanks, 
> Chris 
>

-- 
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/c3ceac01-ff6b-423f-be0b-bf26a6822765%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Recommending for cleaning up old builds when multibranch pipeline is in use?

[Kevin Brotcke]

I can confirm deleting old builds PER branch is working for declarative
syntax by using the option:
options {
  buildDiscarder(logRotator(numToKeepStr:'10'))
}

But this doesn't really solve my problem. I want to keep max N builds
across ALL branches in a multibranch pipeline to maintain a more
predictable disk usage rate. That's what my Groovy script accomplishes.


On Tue, Nov 28, 2017 at 4:53 PM, Mark Waite 
wrote:

>
>
> On Tuesday, November 28, 2017 at 4:50:48 PM UTC-7, Kevin Brotcke wrote:
>>
>> I also couldn't get the buildDiscarder working, nothing seems to be
>> happening. In our case we create a lot of long lasting branches which
>> filled up our Jenins server disk space pretty quickly. I wrote a quick
>> Groovy script to delete old builds across all branches but I'd prefer a
>> more integrated solution:
>>
>> https://gist.github.com/kevin-brotcke/8f65f07e7314ae811df242abc70b2ef2
>>
>>
> From scripted pipeline
> <https://github.com/MarkEWaite/jenkins-bugs/blob/eeac3d925dbb5723979bd87ecf6643d895e7c49b/Jenkinsfile#L8>,
> I use properties([[$class: 'BuildDiscarderProperty', strategy: [$class:
> 'LogRotator', numToKeepStr: '7']]]) and it works great.  I haven't tried it
> with declarative pipeline, but would be surprised if it did not work just
> as well there.
>
> Mark Waite
>
>
>
>>
>> On Friday, May 5, 2017 at 1:06:04 PM UTC-7, Mark Stosberg wrote:
>>>
>>> On Wednesday, March 1, 2017 at 4:08:53 AM UTC-5, Baptiste Mathus wrote:
>>>>>
>>>>> I don't think there's something per branch, but you probably want to
>>>>> either search JIRA and/or file a new feature request about it.
>>>>>
>>>>> You shouldn't need a special plugin, this is a standard feature.
>>>>> Here's the way to do it with Declarative Pipeline:
>>>>>
>>>>> pipeline {
>>>>> options {
>>>>> buildDiscarder(logRotator(numToKeepStr: '20'))
>>>>> }
>>>>> ...
>>>>> }
>>>>>
>>>>> Or with scripted Pipeline: https://github.com/j
>>>>> enkinsci/jenkins/blob/master/Jenkinsfile#L17-L19
>>>>>
>>>>
>>>
>>> I'm stil not seeing any signs that the buildDiscarder plugin is working
>>> for me. At the top of my Jenkinsfile, I have this:
>>>
>>> properties([[
>>>  $class: 'jenkins.model.BuildDiscarderProperty',
>>>   strategy: [$class: 'LogRotator', numToKeepStr: '50',
>>> artifactNumToKeepStr: '50']
>>> ]])
>>>
>>> That's just above my  "node {}" block.
>>>
>>> From reading related source code at:
>>> https://github.com/jenkinsci/jenkins/blob/08def67a18eee51de9
>>> f3f99bc2a792fee1c160e0/core/src/main/java/hudson/tasks/LogRotator.java
>>>
>>> I can see that this function should generate some logging, but I can't
>>> find the log entries indicating this is running in either the web-based
>>> Jenkins log page, or under /var/log/jenkins/*
>>>
>>> The effective-but-imperfect workaround I've found is to just manually
>>> delete only builds:
>>>
>>> find "/var/lib/jenkins/jobs/My Pipeline/branches/" -mindepth 3
>>> -maxdepth 3 -type d -ctime +15 | xargs -d '\n' rm -rf
>>>
>>> That doesn't have the safety nets of preserving any builds that are
>>> last-successful, promoted, etc.
>>>
>>> Some questions:
>>>
>>>   * Should the logging I see in the source code *always* be happening or
>>> there something I need to do activate that logging?
>>>   * Should properties() call work outside a node block?
>>>   * Are there any serious drawbacks to just manually deleting old build
>>> myself? This built-in log rotation has proven especially time-consuming for
>>> what seems like it should be a simple feature to setup.
>>>
>>> Thanks,
>>>
>>>   Mark
>>>
>>> 2017-02-28 20:24 GMT+01:00 Mark Stosberg :
>>>>>
>>>>>> For cleaning up old builds, the "Discard Old Builds" plugin is
>>>>>> recommended:
>>>>>>
>>>>>> https://wiki.jenkins-ci.org/display/JENKINS/Discard+Old+Build+plugin
>>>>>>
>>>>>> However, the instructions for reference a "post build&q

Re: Recommending for cleaning up old builds when multibranch pipeline is in use?

[Kevin Brotcke]

I also couldn't get the buildDiscarder working, nothing seems to be 
happening. In our case we create a lot of long lasting branches which 
filled up our Jenins server disk space pretty quickly. I wrote a quick 
Groovy script to delete old builds across all branches but I'd prefer a 
more integrated solution:

https://gist.github.com/kevin-brotcke/8f65f07e7314ae811df242abc70b2ef2


On Friday, May 5, 2017 at 1:06:04 PM UTC-7, Mark Stosberg wrote:
>
> On Wednesday, March 1, 2017 at 4:08:53 AM UTC-5, Baptiste Mathus wrote:
>>>
>>> I don't think there's something per branch, but you probably want to 
>>> either search JIRA and/or file a new feature request about it.
>>>
>>> You shouldn't need a special plugin, this is a standard feature. Here's 
>>> the way to do it with Declarative Pipeline: 
>>>
>>> pipeline {
>>> options {
>>> buildDiscarder(logRotator(numToKeepStr: '20'))
>>> }
>>> ...
>>> }
>>>
>>> Or with scripted Pipeline: 
>>> https://github.com/jenkinsci/jenkins/blob/master/Jenkinsfile#L17-L19
>>>
>>
>
> I'm stil not seeing any signs that the buildDiscarder plugin is working 
> for me. At the top of my Jenkinsfile, I have this:
>
> properties([[ 
>  $class: 'jenkins.model.BuildDiscarderProperty', 
>   strategy: [$class: 'LogRotator', numToKeepStr: '50', 
> artifactNumToKeepStr: '50'] 
> ]]) 
>
> That's just above my  "node {}" block. 
>
> From reading related source code at:
>
> https://github.com/jenkinsci/jenkins/blob/08def67a18eee51de9f3f99bc2a792fee1c160e0/core/src/main/java/hudson/tasks/LogRotator.java
>
> I can see that this function should generate some logging, but I can't 
> find the log entries indicating this is running in either the web-based 
> Jenkins log page, or under /var/log/jenkins/*
>
> The effective-but-imperfect workaround I've found is to just manually 
> delete only builds:
>
> find "/var/lib/jenkins/jobs/My Pipeline/branches/" -mindepth 3 
> -maxdepth 3 -type d -ctime +15 | xargs -d '\n' rm -rf
>
> That doesn't have the safety nets of preserving any builds that are 
> last-successful, promoted, etc. 
>
> Some questions:
>
>   * Should the logging I see in the source code *always* be happening or 
> there something I need to do activate that logging?
>   * Should properties() call work outside a node block?
>   * Are there any serious drawbacks to just manually deleting old build 
> myself? This built-in log rotation has proven especially time-consuming for 
> what seems like it should be a simple feature to setup. 
>
> Thanks,
>
>   Mark
>
> 2017-02-28 20:24 GMT+01:00 Mark Stosberg :
>>>
>>>> For cleaning up old builds, the "Discard Old Builds" plugin is 
>>>> recommended:
>>>>
>>>> https://wiki.jenkins-ci.org/display/JENKINS/Discard+Old+Build+plugin
>>>>
>>>> However, the instructions for reference a "post build" step which 
>>>> doesn't exist in the Configure interface for Multibranch Pipeline 
>>>> projects. 
>>>>
>>>> What's the recommended way to clean-up builds from multi-branch 
>>>> pipeline projects? Ideally I'd like different pruning policies for 
>>>> different branches. 
>>>>
>>>> Thanks,
>>>>
>>>>  Mark
>>>>
>>>> -- 
>>>> 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/1d9e0343-bbce-474f-a4fe-7623a4f39aaf%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/jenkinsci-users/1d9e0343-bbce-474f-a4fe-7623a4f39aaf%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> 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/b6dfc6d2-0d82-4bc3-a356-a710cfc01a6d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: withAWS step complains about not being able to support closures in the script console

[Kevin Milner]

>
>
> Ok, I think I've solved it. Well, I solved my core issue, which was that the 
> vars/publishToS3.groovy script was not being properly identified. I couldn't 
> figure out how to identify publishToS3. It could find neither publishToS3, 
> nor com.seven10.publishToS3. I think, because there was an implied class 
> being generated for publishToS3.call(), it was not able to find the class. I 
> corrected this by making publishToS3 an actual explicit class in the 
> src// folder.

I'm still not entirely sure if that's the solution that actually resulted 
in my pipeline working.
The docs for Pipeline in more advanced cases are not...good. 

-- 
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/95eb7cf3-6499-46c6-852a-1558d380057c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: withAWS step complains about not being able to support closures in the script console

[Kevin Milner]

Hi Richard, thanks for your response.
publishToS3 is called in another custom step that is then called by the 
pipeline. The reason for the "publish" bit is I kept getting errors along 
the lines of "duplicate class load attempted" (see my post here 
).
 
As a result of a suggestion on that question (which I now think might have 
been a "disguised" error for not being able to load the publishToS3 custom 
step) I added a member to a "container" class and initialize it earlier. I 
will post here the relevant bits of code:



This is the "container" class that I instantiate in my pipeline and it does 
some stuff, mostly holding variable names and whatnot:

// src/com/seven10/Builder.groovy
#!/usr/bin/env groovy
package com.seven10;

import java.text.SimpleDateFormat 
import java.util.Date
import com.seven10.publishToS3

class Builder implements Serializable{

 static final String TARGET_BUCKET = '...'
 static final String ADVANCED_INSTALLER_PATH = 
'c:\\advinst\\bin\\x86\\AdvancedInstaller.com'
 String cli_version
 String release_family
 String win_version
 def steps
 final def publisher
 def docker_images = [:]
 final String date

 Builder(steps) {
 println "Builder Constructor Enter"
 this.steps = steps
 def dateFormat = new SimpleDateFormat("MMdd")
 this.date = dateFormat.format(new Date())
 this.publisher = publishToS3.newInstance()
 }

 def init() {
 def pom = steps.readMavenPom file: 'pom.xml'
 if(pom.version == null) {
 this.cli_version = pom.parent.version
 } else {
 this.cli_version = pom.version
 }
 steps.echo "builder: pom version = " + this.cli_version
 this.win_version = getWinVersionFromVersion(cli_version)
 steps.echo "builder: win_version = " + this.win_version
 this.release_family = getRelFamily(cli_version)
 steps.echo "builder: release_family = " + this.release_family

 steps.echo "Builder Constructor Exit"
 }

 def getFriendlyName(String role_name) {
 "${role_name}_${this.cli_version}_${this.date}"
 }

 static def getRelFamily(String version){
 def rval
 switch (version) {
 case ~/^\d+\.\d+\.\d+$/: rval = (version=~ /^\d+\.\d+/)[0]; break
 case ~/.*-SNAPSHOT$/: rval = 'qa_latest'; break
 case ~/.*SG\d+/: rval = 'sg_latest'; break
 case ~/.*cee\d+/: rval = 'cee_latest'; break
 default: rval = "unknown"
 }
 rval
 }
 static def getWinVersionFromVersion(String version) {
 def rval = (version =~ /^\d+\.\d+\.\d+/)[0]
 println('windows version = ' + rval)
 rval
 }
}


The following snippet is my actual Jenkinsfile (but again, the actual issue I'm 
having right now seems to be just running the code in the script console to get 
it working first)


@Library('jenkins-lib') _

final BUILT_INSTALLER_PATH = 'smb_installer/installer/*.exe'
final BUILT_INSTALLER_PATH_WIN = 
'smb_installer\\installer\\Storfirst_SMB_Hydrator.exe'
final ADV_INST_PROJECT = 'smb_installer\\Hydrator.aip'

final HYDRATOR_JAR_SRC_PATH = 'lib/hydrator/docker/hydra-hydrator.jar'
final HYDRATOR_JAR_DEST_PATH = 'docker/hydrator/hydra-hydrator.jar'
final HYDRATOR_JAR_DEST_PATH_WIN = 'docker\\hydrator\\hydra-hydrator.jar'

final AUTOMATOR_JAR_SRC_PATH = 'lib/automator/docker/hydra-automator.jar'
final AUTOMATOR_JAR_DEST_PATH = 'docker/automator/hydra-automator.jar'

pipeline {
agent none
tools {
maven 'maven'
git 'git-install'
}

stages {
stage('Initialize') {
agent any
steps {
script {
builder = 
com.seven10.Builder.newInstance(this)
builder.init()
println("PATH = " + PATH)
println("M2_HOME = " + M2_HOME)
println("BRANCH_NAME = " + 
env.BRANCH_NAME)
}
}
}
stage('Build Executables') {
agent { label 'x64 && mvn && git' }
steps {
cleanWs notFailBuild: true
initSubmodules project_url: '...'
sh 'mvn clean install  --projects lib/parent'
// install nodejs and other voodoo stuff
sh 'mvn clean generate-resources  --projects 
lib/automator -PinstallNode'   
// install modules
sh 'mvn install -DskipTests'
// build executable jars
sh 'mvn package -DskipTests --projects 
lib/hydrator,lib/automator -PbuildExecutable'

// archive hydrator executable
sh "mv ${HYDRATOR_JAR_SRC_PATH} 
${HYDRATOR_JAR_DEST_PATH}"
fin

withAWS step complains about not being able to support closures in the script console

[Kevin Milner]

I'm having a TON of problems getting the pipeline system setup and working. 
One issue in particular is troubling me. I have a shared library that has a 
custom step in vars/publishToS3.groovy. It looks like this:
#!/usr/bin/env groovy
package com.seven10;


def call(hashmap){
 def src_file = hashmap['src_file']
 def target_path = hashmap['target_path']
 def bucket_name = hashmap.get('bucket_name', '...')
 def region = hashmap.get('region', '...')
 def credentials = hashmap.get('credentials', '...')
 
 withAWS(credentials: credentials, region: region) {
 s3Upload bucket: bucket_name, file: src_file, path: target_path
 }
}

But I kept getting weird errors in my build job (like 
'groovy.lang.MissingPropertyException: 
No such property: publish for class: groovy.lang.Binding') So in order to 
attempt to debug it, I created the following script in the script console.

def call(hashmap){
def src_file = hashmap['src_file']
def target_path = hashmap['target_path']
def bucket_name = hashmap.get('bucket_name', '...')
def region = hashmap.get('region', '...')
def credentials = hashmap.get('credentials', '...')
try {
  withAWS(credentials: credentials, region: region) {
try {
  s3Upload(bucket: bucket_name, file: src_file, path: target_path)
}
catch(error){
   println('inner-try: ' + error)
   throw error
}
  }
}
catch(error){
  println('outer-try: ' + error)
}
}


call src_file: 'blah', target_path: 'blahblah'

But when I execute this script I get the error:

outer-try: groovy.lang.MissingMethodException: No signature of method: 
Script1.withAWS() is applicable for argument types: (java.util.LinkedHashMap, 
Script1$_call_closure1) values: [[credentials:..., region:...], 
Script1$_call_closure1@47e8f461] Possible solutions: with(groovy.lang.Closure)

The docs for the withAWS step show it being called with a closure block in just 
this way (see here ).
The only other thing I can think of is that its not actually finding the 
withAWS step (as demonstrated by the fact that it is called "Script1.withAWS") 
if thats the case, how would I make sure its finding the actual plugin step 
instead of trying to find a local variable?


-- 
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/30eea0d8-10a5-4fce-b050-3064c2c475fb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Invoke another pipeline under another repository's branch

[Kevin Burnett]

:D

this is working for me:

build('/proj/hot-repo/master')

where proj is a bitbucket project key (bitbucket server in my case) and 
hot-repo is a repo within that project.

On Friday, September 15, 2017 at 11:30:02 AM UTC-4, Slava Dubrovskiy wrote:
>
>
> 15.09.2017 17:50, Dan Tran пишет: 
> > Ping! 
> 0% packet loss 
>
> -- 
> WBD, 
> Viacheslav Dubrovskyi 
>
>

-- 
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/24e22be1-57be-4734-a342-7c1485dc370f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins pipeline parallel execution for different nodes on both Declarative and Scripted

[Kevin Burnett]

you can use the "parallel" step in a declarative pipeline. you cannot wrap 
multiple stages inside a parallel step unless you use scripted (currently. 
this may be implemented in declarative in the future).

it is very hard to read code that is not indented. please indent your code. 
:) i think this is your pipeline, but with "steps" added inside the build 
stage and with a quote added to the end of the label 'server02' (it now 
validates clean):

pipeline {
  agent any
  stages {
stage('build') {
  steps {
agent { label 'testnode' }
echo 'build process'
  }
}
stage('Deployment') {
  steps {
parallel(
  "Deployment1": {
agent { label 'server01'}
echo 'deployment in server1'
  },
  "Deployment2": {
agent { label 'server02' }
echo 'deployment in server2'
  }
)
  }
}
  }
}


On Wednesday, August 23, 2017 at 9:40:32 PM UTC-4, jothibasu k wrote:
>
> I like to add stackoverflow questions also, in the below two questions in 
> one they are saying it doable in Declarative and another saying you need to 
> wrap it with script {} block.
>
> which one i we need to follow.
>
> https://stackoverflow.com/questions/44585619/parallel-jenkins-pipeline
>
>
> https://stackoverflow.com/questions/45294813/jenkins-declarative-pipeline-parallel-stages
>
> Thanks,
> JB
>
> On Thursday, August 24, 2017 at 6:53:07 AM UTC+5:30, jothibasu k wrote:
>>
>> I understand the basic difference between the Declarative and scripted 
>> pipeline in Jenkins 2.0.
>>
>> when I try to implement the parallel deployment on different nodes, it 
>> seems declarative is not working I guess.
>>
>> Question
>> 
>> 1. can you please confirm running the parallel task in the different node 
>> is supported or not in both pipeline model.
>> 2. if it works the syntax to do that in the declarative and scripted 
>> pipeline.
>>
>> My declarative pipeline 
>>
>> *pipeline {*
>> *agent any*
>> *stages {*
>> *stage('build') {*
>> *  agent { label 'testnode' }*
>> *  echo 'build process'*
>> *}*
>> *stage('Deployment') {*
>> *steps {*
>> *parallel (*
>> *"Deployment1": {*
>> *agent { label 'server01'}*
>> *echo 'deployment in server1'*
>> *},*
>>
>> *"Deployment2": {*
>> *agent { label 'server02 }*
>> *echo 'deployment in server2'*
>> *}*
>> *)*
>> *}*
>> *}*
>> *}*
>> *}*
>>
>>
>> the above example is not working, if i put the agent in stage level it is 
>> working but stream level it is not working, basically, i like to understand 
>> parallel execution in the different node is supported or not on both 
>> pipelines.
>>
>> Thanks in Advance,
>>
>>
>>

-- 
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/3ff93e0d-e44b-41f1-a72c-25d43c7f532d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

dockerFingerprintFrom

[Kevin Guo]

down votefavorite 


I have some troubles about dockerFingerprintFrom on jenkins pipeline.

The code is as follows:

node {
  stage("First stage") {
dockerFingerprintFrom([dockerfile: "."])
  }
}

It does not work I don't even know if this correct ... I would like ask if 
anyone has a practical example to show me ?

-- 
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/76b9d843-578e-49d1-930a-96c3ac7d0f3c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Bitbucket pull request plugin building on cron schedule instead of building on pull request updates

[Kevin Mullen]

 
Bitbucket Pullrequest Builder Plugin -- 1.4.26
Jenkins -- 2.60.1

I'm not using a pipeline. Just this setup. The box is checked on the job to 
check for updates "Build when a change is pushed to BitBucket".
Anyone ever have this problem?

-- 
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/7e601533-6e2e-4520-957e-0a6581ab031a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: notifyCommit won't fire specific jobs, need help debugging

[Kevin Burnett]

so the job that doesn't fire has parameters. what about the job in the same 
instance that you said works? does it have parameters? i'm believe i've 
seen jobs with parameters not get triggered, but i'm not sure if that's 
just how it works (job with parameters never get triggered) or if there are 
some configurations where they can get triggered by changes in source 
control and some configurations where they cannot.


On Monday, June 26, 2017 at 1:51:21 PM UTC-4, David Karr wrote:
>
> For months now, I and the local Jenkins admins I work with, have been 
> struggling with a problem where my main jenkins job is not firing on a 
> "notifyCommit" firing from a BitBucket instance.  We actually were able to 
> define another job in the same Jenkins instance, pointing to the same repo, 
> that IS fired when the notifyCommit url is hit, but we still can't get the 
> normal job to fire.  We also see the log entry that shows the notifyCommit 
> call, but it just doesn't start the job.
>
> The job works fine when we run it manually, it just doesn't fire 
> automatically.  It also works fine when it's spawned from the 
> "buildWithParameters" URL, which we use to build pull request branches 
> automatically (the same job is designed to build both master and pr 
> branches).
>
> We've tried numerous variations of the value in the "Branches to build" 
> field, but it doesn't appear to make any difference.
>
> We're using v2.46.2 of Jenkins and v3.3.0 of the git plugin for Jenkins.
>
> Assuming no one here has any bright ideas about why this is happening, I 
> figure my next step is to connect to the Jenkins instance with a remote 
> debugger and step through the code.  In order to do that, I have to obtain 
> the correct code to step through, and some hints on some breakpoints to set.
>
> I figure I at least need the source for the correct release.  When I look 
> on github, I see a release for "2.46.3", but not "2.46.2".  I do see that 
> github has a "3.3.0" release for the git plugin, so I assume I'm ok there.
>
> Assuming I can get the 2.46.2 vs. 2.46.3 issue resolved, are there any 
> other plugins that I need to get the source for in order to properly debug 
> this?
>

-- 
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/af6805e9-293f-4649-88fd-b33b0081a0cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GitHub and Bitbucket branch source UI refactoring

[Kevin Burnett]

This is so good. :)

The pre and post diffs looked right, and the new UI and functionality gives 
me everything that I was hoping for.

I'm going to remove the "discover pull requests from [everywhere]" 
behaviors and select "Only branches that are also filed as PRs" on 
production as soon as possible.

Michael Neale mentioned that one issue he had seen "does look better now 
with the new version." I used the plugin versions that Stephen originally 
posted on June 20, but I take Michael's comment to mean there might be 
newer versions. Please make this irrelevant by issuing release versions of 
these plugins this week. :)

Thanks a ton!
-KB

On Friday, June 23, 2017 at 12:45:44 PM UTC-4, Stephen Connolly wrote:
>
>
>
> On 23 June 2017 at 17:24, Mark Waite > 
> wrote:
>
>> I see duplicate entries in the "Add' configuration of the Bitbucket 
>> source for "Checkout over ssh".  Let me know if you need steps to see that.
>>
>
> Shouldn't... may just be a bug in the drop down populator when you have 
> GitHub and Bitbucket
>  
>
>>
>> I also wonder if the text "General", "Git" and "Bitbucket" should be 
>> italicized, or bold, or separated with dashes, or something, so that the 
>> user has a concept that things will be appearing under them.  They seem to 
>> be standard text currently, and it wasn't obvious to me that they were 
>> categories into which settings would be placed.
>>
>
> Cannot style the drop-down menu without significant JS changes that risk 
> affecting form binding.
>  
>
>>
>> Mark Waite
>>
>>
>> On Friday, June 23, 2017 at 9:58:52 AM UTC-6, Mark Waite wrote:
>>>
>>> The UI experience has been great for me in the two or three places where 
>>> I've used it.  I was a little surprised (and pleased) with the adaptation 
>>> that the local branch setting is now a toggle.  I think that's the right 
>>> approach, since (as far as I can tell) that is the 99% use case.
>>>
>>> Earlier I reported an NPE when configuring a multi-branch pipeline that 
>>> uses GitHub as source instead of Git as source.  The NPE was resolved by 
>>> removing the multiple-scms plugin.  Unfortunately, the 404 is still there, 
>>> along with a stack trace that starts with this:
>>>
>>> Jun 23, 2017 9:51:38 AM hudson.ExpressionFactory2$JexlExpression evaluate
>>> WARNING: Caught exception evaluating: 
>>> descriptor.calcFillSettings(field,attrs) in 
>>> /job/Git-Client-Folder/job/git-client-pipeline-github/configure. Reason: 
>>> java.lang.IllegalStateException: class 
>>> org.jenkinsci.plugins.github_branch_source.GitHubSCMSource$DescriptorImpl 
>>> doesn't have the doFillCredentialsIdItems method for filling a drop-down 
>>> list
>>> java.lang.IllegalStateException: class 
>>> org.jenkinsci.plugins.github_branch_source.GitHubSCMSource$DescriptorImpl 
>>> doesn't have the doFillCredentialsIdItems method for filling a drop-down 
>>> list
>>> at hudson.model.Descriptor.calcFillSettings(Descriptor.java:412)
>>> at sun.reflect.GeneratedMethodAccessor578.invoke(Unknown Source)
>>> at 
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:498)
>>> at 
>>> org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258)
>>> at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104)
>>> at 
>>> org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
>>> at 
>>> org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
>>> at 
>>> org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
>>> at 
>>> org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
>>> at 
>>> hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74)
>>> at 
>>> org.apache.commons.jelly.parser.EscapingExpression.evaluate(EscapingExpression.java:24)
>>> at 
>>> org.apache.commons.jelly.impl.ExpressionScript.run(ExpressionScript.java:66)
>>> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>>
>>> I'm not sure how to provide a repeatable condition for that bug yet, but 
>>> wanted to alert you about it.  I won't investigate further on it until 
>>> after the end of the working day today.
>>>
>>> Mark Waite
>>>
>>> On Friday, June 23, 2017 at 7:32:54 AM UTC-6, Stephen Connolly wrote:

 How do you find the new UI compared with the previous one?

 -- 
>> 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-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/c2e110d7-f929-461d-8595-273e8e543d89%40googlegroups.com
>>  
>> 
>> .
>>
>> For mo

Re: Fastest way to git tag in a Jenkinsfile?

[Kevin Burnett]

it is possible to skipDefaultCheckout and then "checkout scm". this isn't 
typically necessary or desirable if you want to operate on the same repo 
where your Jenkinsfile lives, but it sounds like you might want to override 
some checkout options, which seems cool. we also do this for some jobs that 
"trash the workspace" by writing some files as root, so the default 
checkout can't work on subsequent builds. in a Jenkinsfile stage we first 
"fix the workspace" by chown'ing it to the jenkins user, which allows `scm 
checkout` to work.

On Saturday, June 17, 2017 at 1:22:48 PM UTC-4, Mark Waite wrote:
>
> Defaults are taken when values are not provided.
>
> On Sat, Jun 17, 2017 at 11:19 AM Idan Adar > 
> wrote:
>
>> Another question, if I do customize "checkout", do I need to include 
>> everything like in your example, or only what I want specifically, like 
>> depth, and if nothing else is mentioned that the defaults are taken...?
>>
>> -- 
>> 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/ed87e710-1906-46b3-9486-6440b92da5ba%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/2cd44a76-c556-41a8-93f6-d40e81aca9e7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GitHub and Bitbucket branch source UI refactoring

[Kevin Burnett]

we'd be down to try that, yes. thanks for making these changes in a way 
that will benefit the product long-term!

fingers are crossed that there's already a built-in way to pretend like 
pull requests don't exist! you're already building the branches; why also 
build the pull requests, eh? :)

thanks!
kb


On Friday, June 16, 2017 at 2:35:54 PM UTC-4, Mark Waite wrote:
>
> I'd like to be part of the beta test.
>
> Mark Waite
>
> On Fri, Jun 16, 2017 at 12:19 PM Stephen Connolly  > wrote:
>
>> Just a quick status update.
>>
>> In final stages of this work now. Bobby is being a superstar and 
>> reviewing my 13k LoC change on the Bitbucket branch source - brings lots of 
>> feature parity with GitHub and adds the configuration ability of the pure 
>> Git branch source
>>
>> I am finalising the GitHub Branch Source changes... likely to be another 
>> big PR
>>
>> Then there's a 5k LoC change in the Git plugin
>>
>> Plan is to try and get all merged next week and cut a beta
>>
>> I'll be looking for people to help test at that stage.
>>
>> Please respond if you think you can help (lots of bugs fixed as a side 
>> effect of the refactoring - it makes things more easy to test => I found 
>> and fixed bugs)
>> -- 
>> Sent from my phone
>>
>> -- 
>> 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-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMxfYrZphgYDXFD3i%2Bo_7eDn7mn2qVrzJz6wFaoVkNmc%2Bw%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/fd613b68-3f87-4650-a3f9-6657d8f4179a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Can environment directive be used in post?

[Kevin Burnett]

i don't believe you can use the environment instruction in post, no.

but you can use 
withEnv: 
https://jenkins.io/doc/pipeline/steps/workflow-basic-steps/#code-withenv-code-set-environment-variables

On Wednesday, June 14, 2017 at 8:43:43 AM UTC-4, Idan Adar wrote:
>
> In a stage I can do the following: 
>
> stage ("Merge pull request") {
>  environment {
> JENKINSBOT = credentials('${JENKINSBOT_GHE_ACCESS_TOKEN}')
>  }
>  ...
>  ...
>  steps {
>   
>  }
> }
>
> Can this done also in post?
>
> post {
>  success {
>  environment { 
>  JENKINSBOT = credentials('${JENKINSBOT_GHE_ACCESS_TOKEN}')
>  }
>
>  script {
>  
>  }
>   }
> }
> 
>
> Or is there any other way to ahchieve this?
>

-- 
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/a3beb8eb-353f-41cb-ada9-dccbe889b189%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to set environment variable in multibranch pipeline?

[Kevin Burnett]

here's an example Jenkinsfile that sets an environment variable (REPO_URL) 
that applies to all stages. you can also use the withEnv step to set an 
environment variable for a certain block.

pipeline {
  agent { label 'docker' }
  environment {
REPO_URL = 'www.my.repo'
  }
  stages {
stage('build') {
  steps {
sh 'env | grep REPO_URL'
  }
}
  }
}

Jenkinsfiles apply to all branches in a repo, so that part is handled 
implicitly.

Hope this helps,
KB


On Tuesday, June 13, 2017 at 3:53:33 AM UTC-4, Mark Allison wrote:
>
> I have a Jenkins multibranch pipeline project and I want to set an 
> environment variable for all branches. Is this possible? I could only see a 
> way to do it with the environment injector plugin at the branch level. I 
> want to be able to do this at the project level because I want new feature 
> branches to automatically inherit some environment variables.
>

-- 
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/35f81b50-ac62-4f9c-8937-b8c600434a8e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Does Jenkis need the workspace in order to compare previous commits for Git repository

[Kevin Burnett]

I got super-confused here for a minute, so I thought it might be worth 
pointing out that people who are using multibranch pipelines can completely 
ignore the article presented in this thread (it says it's for 
"non-multibranch jobs") and get this bitbucket server add-on 
instead: 
https://marketplace.atlassian.com/plugins/nl.topicus.bitbucket.bitbucket-webhooks/server/overview.
 
stephen has recently submitted pull requests for this "topicus" add-on, so 
i'm pretty sure it's still a thing. :) it works in concert with the 
Bitbucket Branch Source jenkins plugin.

On Wednesday, June 7, 2017 at 11:29:09 PM UTC-4, Mark Waite wrote:
>
>
>
> On Wed, Jun 7, 2017 at 5:46 PM Stephen Connolly  > wrote:
>
>> On Wed 7 Jun 2017 at 22:48, Łukasz Zachulski > > wrote:
>>
>>> I've found Jenkins article Triggering a build using hooks in Bitbucket 
>>> server 
>>> 
>>>  
>>> and it states that
>>>
>>> You need to ensure that your workspace is not deleted after every build. 
 The Git plugin needs the workspace in order to compare previous commits to 
 check if there were changes in the repository or not.
>>>
>>>
>>>
> As far as I understand it, that statement is incorrect.  The git plugin 
> does not need the workspace to check if there were changes in the 
> repository or not.  The plugin remembers the SHA1 associated with a build.  
> If a SHA1 is detected which has not been previously built, then it is 
> assumed a new build is needed.
>
> Remote polling (the default) does not require a workspace, unless you're 
> using certain special cases, like ignoring commits based on the commit 
> author or commit message.
>
> Mark Waite
>  
>
>> What will happen if the workspace will be deleted or when build will be 
>>> simply executed on different node? Will Jenkins not be able to correctly 
>>> depict changes between previous and current builds?
>>>
>>>
> Changes from build to build are calculated using the git repository that 
> was used for the build.  That repository is assumed to have enough history 
> in it to compute the differences between the build and its predecessor.  
>
> Yes, it is possible to violate that assumption using a shallow clone value 
> that is less than the number of intervening commits between the build and 
> its predecessor.
>
> No, I haven't tested the behavior when that assumption is violated.
>
> Mark Waite
>  
>
>> How does this rule apply to *Pipeline*, especially *Multibranch* and 
>> *Bitbucket 
>>> Team* jobs and the fact that mult-ibranch jobs do it own branch 
>>> indexing? 
>>>
>>
>> Multibranch keeps its own track. You can ignore that rule for multibranch 
>>
>>>
>>>
>>> With Regards,
>>> Lukasz.
>>>
>>> -- 
>>> 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/2060c2f6-78a9-4421-a15d-aabafb3877d8%40googlegroups.com
>>>  
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> -- 
>> Sent from my phone
>>
>> -- 
>> 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/CA%2BnPnMwj%3DwH1-ue599HspTL8vkDzTYCfjJjM%3DBWbZF6CrK0t0A%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/07e9deec-a0ab-45ce-8ec6-a08db28cc93f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problems registering for jenkinsci-dev group

[Kevin Phillips]

Confirmed. I just connected to the jenkins IRC channel and they said the 
dev group has been flagged as "spam" by Google. :p

Looks like I just have to wait until they get that problem sorted out.

Thanks for the reply.

On Friday, May 12, 2017 at 3:13:42 PM UTC-3, Victor Martinez wrote:
>
> Although I'm subscribed I couldn't access since Google detected as a spam. 
> But even if you agree to proceed te group box is empty. I'm pretty sure 
> jenkins dev admins are already aware of.
>
> Cheers 
>

-- 
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/445498f0-23cc-4cee-aa24-462cf89f6954%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Problems registering for jenkinsci-dev group

[Kevin Phillips]

I have been looking to get involved with some of the Jenkins plugins' 
projects, and was reading the getting started guide on jenkins.io. There it 
tells me  I need to register with the 
jenkinsci-dev google group by sending an empty email to the 'subscribe' 
email address. When I did that I got an email response nearly right away 
saying the Google group jenkinsci-dev doesn't exist. Have I missed 
something, or is maybe the link out of date?

-- 
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/43329782-4105-44a1-9223-918d27ecf57e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Manual step stage on BlueOcean/Jenkins2 pipeline

[Kevin Burnett]

use the input step 
, like this:

timeout(time: 5, unit: 'DAYS') {
input message: 'Approve deployment?'
}


it's helpful to wrap it in a timeout, so eventually the pipeline will stop 
(fail) if no one approves it.

On Thursday, May 11, 2017 at 10:58:26 AM UTC-4, Thiago Carvalho Davila 
wrote:
>
> Hello,
>
> I am migrating my old pipelines to pipeline as code of Jenkins2. I've been 
> strugling to make manual step stages like stage('Deploy-Production'){}. It 
> is autoexecuted if I just put it in the pipeline{}.
>
> What is the best practice here? Is there native support to manual step?
>
> Thanks,
>
> Thiago
> -
>
>
> "Esta mensagem do SERVIÇO FEDERAL DE PROCESSAMENTO DE DADOS (SERPRO), 
> empresa pública federal regida pelo disposto na Lei Federal nº 5.615, é 
> enviada exclusivamente a seu destinatário e pode conter informações 
> confidenciais, protegidas por sigilo profissional. Sua utilização 
> desautorizada é ilegal e sujeita o infrator às penas da lei. Se você a 
> recebeu indevidamente, queira, por gentileza, reenviá-la ao emitente, 
> esclarecendo o equívoco."
>
> "This message from SERVIÇO FEDERAL DE PROCESSAMENTO DE DADOS (SERPRO) -- a 
> government company established under Brazilian law (5.615/70) -- is 
> directed exclusively to its addressee and may contain confidential data, 
> protected under professional secrecy rules. Its unauthorized use is illegal 
> and may subject the transgressor to the law's penalties. If you're not the 
> addressee, please send it back, elucidating the failure."
>

-- 
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/ee9fa059-1854-4ee8-9d00-d51b8501916a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How do I set env variable to currentBuild property in declarative pipeline environment.

[Kevin Burnett]

This is a way to accomplish what you're trying to do:

#!groovy

// assign to this variable in the first stage (see below), and then you can 
use it throughout your pipeline
// not quite as clean as using the environment block, but it works. the 
problem seems to be that
// the environment block is "compiled" at the same time as the parameters 
block, etc, so the things
// that you want to use to set up an environment variable (params, other 
env vars) are not yet available.
def buildRevision = "UNKNOWN"

pipeline {
agent {
label "linux"
}
parameters {
string(name: "releaseName", defaultValue: "RM_TEST", description: "Ivy 
release spec")
}
tools {
jdk 'jdk1.8.0_102'
maven 'maven-3.2.5'
}
stages {
stage("dummy") {
steps {
script {
buildRevision = 
"${params.releaseName}.${env.BRANCH_NAME}.${currentBuild.startTimeInMillis}.${env.BUILD_ID}"
}  
echo "buildRevision: ${buildRevision}"
}
}
}
}


On Wednesday, May 10, 2017 at 1:42:11 PM UTC-4, JG wrote:
>
> Unfortunately not.
>
> [branch_jenkins-dummy_master-ZKZSOZRU2C4BR7MTP6RRGC4D2OPUWJONM6DQP6YFBP3UB5R3DCYQ]
>  
> Running shell script
> + env
> + sort
> BRANCH_NAME=master
> BUILD_DISPLAY_NAME=#13
> BUILD_ID=13
> BUILD_NUMBER=13
> BUILD_REVISION=null
> BUILD_TAG=jenkins-testing-multibranch-jenkins-dummy-master-13
> ...
>
> It's specifically the inclusion of ${currentBuild.*property*} in the 
> variable declaration within the *environment{}* block that leaves the 
> variable null.
>
> On Wednesday, May 10, 2017 at 12:07:31 PM UTC-5, Cuong Tran wrote:
>>
>> Does it work with this?
>>
>> withEnv(["BUILD_REVISION=${env.BUILD_REVISION}"]) {
>> sh "env | sort"
>> }
>>
>> On Wednesday, May 10, 2017 at 8:20:45 AM UTC-7, JG wrote:
>>>
>>> I'm trying to set an env variable globally in my *pipeline {} *with a 
>>> concatenation of build details like this
>>>
>>> #!groovy
>>> pipeline {
>>> agent {
>>> label "linux"
>>> }
>>>   parameters {
>>> string(name: "releaseName", defaultValue: "RM_TEST", 
>>> description: "Ivy release spec")
>>> }
>>> tools {
>>> jdk 'jdk1.8.0_102'
>>> maven 'maven-3.2.5'
>>> }
>>> environment {
>>> BUILD_REVISION = 
>>> "${params.releaseName}.${env.BRANCH_NAME}.${currentBuild.startTimeInMillis}.${env.BUILD_ID}"
>>> RELEASE_NAME = "${params.releaseName}"
>>> }
>>> stages {
>>> stage("dummy") {
>>> steps {
>>> sh "echo 
>>> \"${params.releaseName}.${env.BRANCH_NAME}.${currentBuild.startTimeInMillis}.${env.BUILD_ID}\""
>>> sh "env | sort"
>>> }
>>> }
>>> }
>>> }
>>>
>>> and it seems to be silently failing. The *echo* command prints the 
>>> value as expected, but the *env *does not include a *BUILD_REVISION* 
>>> variable (the *RELEASE_NAME* env variable is shown in the output of 
>>> *env*. I also tried setting the *BUILD_REVISION* in an *environment{}* 
>>> block 
>>> within the stage, and also tried using a string property of 
>>> *currentBuild*. Nothing seems to work.
>>>
>>> It seems to work using *withEnv* 
>>>
>>> steps {
>>> sh "echo 
>>> \"${params.releaseName}.${env.BRANCH_NAME}.${currentBuild.startTimeInMillis}.${env.BUILD_ID}\""
>>> 
>>> withEnv(["BUILD_REVISION=${params.releaseName}.${env.BRANCH_NAME}.${currentBuild.startTimeInMillis}.${env.BUILD_ID}"])
>>>  
>>> {
>>> sh "env | sort"
>>> }
>>> }
>>>
>>> But I'll need to use the variable in multiple stages so I'd prefer it to 
>>> be in a global *environment{}* block.
>>>
>>

-- 
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/1c77d1a9-0272-40be-bfc0-dbb7e3184db7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: A job to update other jobs

[Kevin Burnett]

what is up morgan, man? :)

i just tested this to update a job description (it gets an http 302 when it 
works):

  curl -u user:pass -X POST 
https://ci.example.com/job/my-hot-job/submitDescription --data-urlencode 
"description=FROZEN by [fancy_business_here]"

maybe someone else knows all about updating jobs from xml files.

good luck,
kb

On Monday, May 8, 2017 at 2:06:33 PM UTC-4, Morgan Blackthorne wrote:
>
> We're using Chef automation around configuring our Jenkins jobs. Basically 
> chef clones a git repo with the job XML files, and then tells Jenkins to 
> use them.
>
> What we want to have is:
>
>1. One job to edit other jobs description to say "FROZEN by  
>at " or to remove the FROZEN line (basically a toggle)
>2. Chef will then be updated to look at the job XML currently on the 
>Jenkins server
>   1. If the description includes FROZEN, skip that job and leave it 
>   alone
>   2. If the description does not include FROZEN, update the job from 
>   the XML file
>
> I'm not really up to speed on Groovy, so what's the simplest way to 
> approach this? (I already know how to do the XML check for step 2, we can 
> just look at the XML over HTTP.)
>

-- 
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/fa729891-a5fe-44c8-9f6c-cafb050a5985%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline with CVS

[Kevin Burnett]

Use the pipeline syntax generator that you can find in the left nav of your 
jenkins UI in any pipeline job. It's sweet. I will not take any cheap shots 
at CVS while I'm here.





On Tuesday, May 2, 2017 at 4:54:42 AM UTC-4, xto...@gmail.com wrote:
>
> Hi,
>
>
> I try to write pipeline to check out code from CVS. While there are many 
> example with git, I cannot find any example with CVS. I would very 
> appreciate if anyone can post some groovy examples here.
>
>
> Regards,
>
> David
>

-- 
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/4c4d5f60-6a61-42bb-841a-064d9a29d7cf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multi branch source - PR versus branch build

[Kevin Burnett]

i'm actually totally with you on this.

i've been wanting to only build branches (and never build PRs) for a while 
now. in fact, we've gone so far as to "kill" PR builds manually in our 
shared library in order to not chew up resources needlessly:

if (env.BRANCH_NAME && env.BRANCH_NAME.contains('PR-')) {
  error("IntentionallyFailingPullRequestBuild")
}

our workaround is annoying since our pull requests obviously always show up 
as broken in bitbucket server. :|

i think https://issues.jenkins-ci.org/browse/JENKINS-43426 is related, and 
lots of new use-cases will be supported when this new UI is eventually 
rolled out (i hope our "ignore PRs completely" use case is supported, but 
i'm not 100% sure what's in scope).

On Monday, May 1, 2017 at 2:17:23 PM UTC-4, Dan Tran wrote:
>
>
> So I misunderstood the mechanism of PR build where the target branch is 
> not merged into the destination branch before build
>
> what is the benefit of auto build both merge and pr for every new commit? 
>  I can understand the benefit before issuing the PR, but from my experience 
> ppl usually issue PR very early to solicit feed back and there for we have 
> double builds
>
> Thanks
>
> -Dan
>
> On Monday, May 1, 2017 at 10:44:33 AM UTC-7, Kevin Burnett wrote:
>>
>> dan,
>>
>> i understand that you're using the bitbucket branch source plugin, you 
>> introduce a syntax error into the mainline branch (let's call it master), 
>> and you submit a pull request for a different branch (let's call it 
>> feature/new-hotness) that wasn't based off this bad master branch. your 
>> master build fails and your pull request build succeeds.
>>
>> that is what i'd expect, because it doesn't automatically merge the 
>> feature branch into master or master into the feature branch. where have i 
>> misunderstood?
>>
>>
>> On Sunday, April 30, 2017 at 5:26:44 PM UTC-4, Dan Tran wrote:
>>>
>>> Hi
>>>
>>> I am experimenting BitBucket multi branch source plugin I think PR build 
>>> is just same as branch build.
>>>
>>> Basically, i force a syntax failure  the main source, and create a pull 
>>> request from another branch.  
>>> I am expecting the PR build also fails as in main. But  it is  not.
>>>
>>> Am I missing something?
>>>
>>> Thanks
>>>
>>> 0Dan
>>>
>>

-- 
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/728454ea-fca1-40d9-90b7-1a04e7415fe8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multi branch source - PR versus branch build

[Kevin Burnett]

dan,

i understand that you're using the bitbucket branch source plugin, you 
introduce a syntax error into the mainline branch (let's call it master), 
and you submit a pull request for a different branch (let's call it 
feature/new-hotness) that wasn't based off this bad master branch. your 
master build fails and your pull request build succeeds.

that is what i'd expect, because it doesn't automatically merge the feature 
branch into master or master into the feature branch. where have i 
misunderstood?


On Sunday, April 30, 2017 at 5:26:44 PM UTC-4, Dan Tran wrote:
>
> Hi
>
> I am experimenting BitBucket multi branch source plugin I think PR build 
> is just same as branch build.
>
> Basically, i force a syntax failure  the main source, and create a pull 
> request from another branch.  
> I am expecting the PR build also fails as in main. But  it is  not.
>
> Am I missing something?
>
> Thanks
>
> 0Dan
>

-- 
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/6a1523be-25a0-4519-9887-28fd29363cde%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Job gets triggered by Bitbucket Push event but not by Pull request event.

[Kevin Burnett]

if you're using bitbucket server and the recommended bitbucket server 
add-on, maybe you're running into this documented regression: 
https://github.com/topicusfinan/bitbucket-webhooks-plugin/issues/31.

if so, as discussed in this github issue, a workaround is to downgrade this 
add-on to version 1.2.0.

On Thursday, April 6, 2017 at 1:07:28 AM UTC-4, joe.c...@gmail.com wrote:
>
> Hi guys,
>
> Iam not able to trigger a jenkins job , whenever I make a pull request in 
> bitbucket but I am able to trigger Jenkins job whenever there is commit in 
> bitbucket branch.
> I tried  "BitBucket pull request builder" plugin,  to achieve this but not 
> able to succeed.
>
> Any help will be appreciated...
>

-- 
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/3fe9ee64-b451-4fc9-89f7-c5d9bc435326%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Moving jobs from Bamboo to Jenkins

[Kevin Burnett]

type faster?

:)

...

:(

i don't think you're going to find much help in terms of an existing script 
to perform the whole 
migration. 
http://stackoverflow.com/questions/38910932/bamboo-to-jenkins-migration.

what i have found is that declarative pipelines facilitate migration quite 
well, since similar projects can use similar Jenkinsfiles (and you can put 
shared Jenkinsfile functionality in libraries as well). then, when you've 
added a bunch of Jenkinsfiles, you can mass import them into jenkins as 
long as you're using github or bitbucket for source control. 
https://jenkins.io/blog/2017/02/03/declarative-pipeline-ga/ post is maybe a 
reasonable starting point for getting into declarative pipelines.

On Friday, March 31, 2017 at 7:03:22 AM UTC-4, DevOps_PS wrote:
>
> *My company has decided to move from Bamboo to Jenkins. We have several 
> jobs already in Bamboo. Can someone help me with a solution on moving all 
> jobs from Bamboo to Jenkins swiftly ?*
>

-- 
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/77dcff40-23d9-4d92-ba85-ceb327a53a65%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to git push from a Jenkinsfile?

[Kevin Burnett]

you may want to omit the -b in "git checkout -b master" if the master 
branch already exists (seems likely).

we use this to make maven release work on any branch (maven release has a 
similar issue where it cannot work with detached head):

sh 'git checkout ' + env.BRANCH_NAME


On Friday, March 24, 2017 at 10:37:58 AM UTC-4, Idan Adar wrote:
>
> Joshua, perhaps you mean something like this?
> The git commands likely miss something...
>
> stage ("Publish to npm") {
>steps {
>   script {
>  STAGE_NAME = "Publish to npm"
>   }
>   
>   // Prepare the workspace
>   deleteDir()
>   sh '''
>  git checkout -b master
>  npm --no-git-tag-version version minor
>  git commit -am 'Bumped version number [ci skip]'
>  git push origin master
>   '''
>   }
>}
> }
>
>
> On Friday, March 24, 2017 at 4:31:59 PM UTC+3, Idan Adar wrote:
>>
>> Thanks for the question Joshua.
>> Here's the full Jenkinsfile: http://pastebin.com/nG4iTZhQ
>>
>> What happens is this:
>> 1. Developers make a pull request to the master branch from their feature 
>> branch.
>> 2. The pull_request webhook tells Jenkins to start working based on the 
>> stages in the Jenkinsfile. This includes: checkout, unit test, sonar 
>> analysis and merge to master.
>> 3. The effect of the merge is basically a push webhook, which means that 
>> Jenkins is now going to run the same Jenkinsfile, but on the master branch 
>> instead of the Pull Request. So, this time: checkout, unit tests and 
>> publish to npm.
>>
>> In the case where it is running from the master branch, I also bump the 
>> version number in package.json and want to push this change back to the 
>> master branch.
>> Developers will then update their feature branch with the updated 
>> package.json number...
>>
>> The part that is not working is the git push.
>> You have mentioned "localbranch". I haven't heard of this or know how to 
>> do this. Can you elaborate?
>>
>> On Friday, March 24, 2017 at 4:18:28 PM UTC+3, Joshua Noble wrote:
>>>
>>> Generally when you do a basic checkout, the Jenkins workspace is in a 
>>> detached HEAD state. You want to check out to a local branch likely using "
>>> localBranch". I have to ask though - if Jenkins does a merge of the PR 
>>> - why would you need to push?
>>>
>>> On Friday, March 24, 2017 at 7:37:57 AM UTC-4, Idan Adar wrote:

 How do you get "git push" to work in a Jenkinsfile? I am not sure what 
 am I missing.

 The Jenkinsfile checkouts a repo using an access token (this is 
 configured in the Jenkins UI for the job).
 The Jenkins file also does a merge of a PR in one of its stages: 

 withCredentials([usernamePassword(credentialsId: '', 
 usernameVariable: 'ACCESS_TOKEN_USERNAME', passwordVariable: 
 'ACCESS_TOKEN_PASSWORD',)]) {
 sh "curl -X PUT -d '{\"commit_title\": \"Merge pull request\"}' 
  https://***/pulls/$CHANGE_ID/merge?access_token=$ACCESS_TOKEN_PASSWORD";
 }

 But I can't get "git push" to work in another stage:

 git config --global user.name ''
 git config --global user.email 
 git commit -am 'Bumped version number'
 git remote set-url origin git@.git
 git push origin master

 I tried wrapping the above in withCredential and also . with agent, 
 but nothing works...  

 Tips?

>>>

-- 
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/b96ad9e4-a965-4455-9ef0-f3d27cf9c06a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline script for Build Trigger

[Kevin Burnett]

Sebastian, here's a snippet of a declarative Jenkinsfile pipeline showing a 
time-based (cron) trigger:

pipeline {
  triggers {
// every 30 minutes during 9 hours each night
cron('H/30 20,21,22,23,0,1,2,3,4 * * *')
  }
  agent { label 'docker' }
  environment {
GIT_COMMITTER_NAME = 'jenkins'
GIT_COMMITTER_EMAIL = 'jenk...@jenkins.io'
  }
  stages {
stage('setup') {
.

On Friday, January 27, 2017 at 4:58:21 AM UTC-5, Sebastian Gurlt wrote:
>
> Hey,
>
> I want to do the same with automatic time based builds, any hint how I 
> could implement this ? :)
>
> Greetings
> Sebastian
>
> Am Freitag, 12. August 2016 20:55:03 UTC+2 schrieb John Engelman:
>>
>> I was able to get the branch to enable the trigger by adding the 
>> following to my Jenkinsfile:
>>
>> properties([
>> pipelineTriggers([
>>   [$class: "GitHubPushTrigger"]
>> ])
>>   ])
>>
>> I then manually executed a Branch Index on the parent job and the 
>> resulting PR builds had the trigger on push setting enabled.
>>
>> On Thursday, August 11, 2016 at 9:01:19 AM UTC-5, Michal Medvecky wrote:
>>>
>>> I see that the related issue was resolved, but I still don't know how to 
>>> add "Build when a change is pushed to GitHub" support to my Jenkinsfile.
>>>
>>> Can anyone help me please?
>>>
>>> Michal
>>>
>>

-- 
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/4c299cfe-887a-4729-9a34-235d6c5c971f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins TestComplete plugin looks only in the Jenkins workspace for the Project file

[Kevin Kapell]

I am using Jenkins v2.32.1 with the TestComplete plugin and TestComplete 12.

My TestComplete scripts are in a location on the PC that is not the Jenkins 
workspace folder.

I tried entering the following as the path to the scripts:

"C:\Program Files (x86)\SmartBear\TestExecute 12\Bin\TestExecute" 
"C:\Repository\Automation\Help Desk\HelpDesk - Ticket Functionality.pjs" /run 
/exit

However, the Jenkins plugin tries to file the file under its workspace folder 
and it of course does not find the file.

How do I set the path in Jenkins so that it finds the TestComplete project file?


Kevin Kapell
Software Quality Assurance Manager
Main: (800) 975-TRAX
Cell: (585) 766-3406
catertrax.com<http://catertrax.com/>

[cid:image001.jpg@01D23E98.C858CE60]<http://catertrax.com/become-a-traxer/>  
[cid:image002.png@01D23E98.C858CE60] 
<http://www.prweb.com/releases/2016/catertraxrochestertop100/prweb13814038.htm>
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for 
the sole use of the intended recipients(s) and may contain confidential and 
privileged information. Any unauthorized review, use, disclosure or 
distribution is prohibited. If you are not the intended recipient, please 
contact the sender by reply e-mail and destroy all copies of the original 
message.

-- 
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/BY1PR0401MB14828EF70A85991DB4E132DC85630%40BY1PR0401MB1482.namprd04.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.

Re: Remote trigger configuration

[Kevin Yu]

Alternative is to use curl to trigger the job remotely.

On Thursday, December 22, 2016 at 11:20:46 PM UTC-8, JenkinsJunkyard wrote:
>
> Hello,
>
> I am not able to configure the jenkins for remote trigger. Few years back 
> I had done this, with older version using "Manage Credentials" option. But 
> the latest versions don't have Manage Credentials option to configure 
> hostname, hostname and port, etc options. And the docs in internet/google 
> point to older documents which tell to configure with "Manage Credentials" 
> only. Please help me on this.
>
>
> Thanks,
> HelpMeJenkins
>

-- 
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/acc767bc-f744-4f95-b338-011173e75bde%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Need pipeline script help

[Kevin Yu]

You should be able to change it in Manage Jenkins from Jenkins GUI

On Wednesday, December 28, 2016 at 12:14:08 PM UTC-8, Venkat S wrote:
>
> Hi All,
>
> Simple question: How to change the jenkins home directory location? By 
> default it points to /var/lib/jenkins whereas I want it to point to 
> /mnt/home/jenkins. I have changed my $JENKINS_HOME to /mnt/home/jenkins but 
> it doesn't help me.
>
> I am getting jenkins Ui problem. see below error.  If i leave same 
> /var/lib/jenkins/ it's working fine.
> HTTP ERROR: 503
>
> Problem accessing /. Reason:
>
> Service Unavailable
>
> --
> *Powered by Jetty://*
>
> On 8 December 2016 at 11:04, Venkat S > 
> wrote:
>
>> Thanks all
>>
>> Is this jenkins job DSL and jenkins pipeline is same or different. 
>> Actually i need to create pipeline for creating Docker RPM creation.Let me 
>> know your suggestions.
>>
>> Thanks
>> Venkat
>>   
>>
>> On 7 December 2016 at 21:33, xwyxw > 
>> wrote:
>>
>>> [image: Boxbe]  This message is 
>>> eligible for Automatic Cleanup! (daniel.c...@gmail.com ) Add 
>>> cleanup rule 
>>> 
>>>  
>>> | More info 
>>> 
>>>  
>>>
>>> This may enlight your way 
>>> https://github.com/jenkinsci/pipeline-examples/tree/master/pipeline-examples
>>>
>>> On Tuesday, December 6, 2016 at 5:47:41 PM UTC+11, Venkat S wrote:

 I am very new for Jenkins. i am try to create Jenkins pipeline script. 
 Please help me out develop pipeline script. if you have any syntax share 
 with me.

 Thanks
 Venkat

>>> -- 
>>> 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/B_2ecad_VkM/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to 
>>> jenkinsci-use...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-users/e5954dd4-8704-4b59-a3b2-50a624260cf0%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/203d7e86-e9e5-4dfa-bebc-1f0425ea9aa5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins email ext - How to add other people to watch job list

[Kevin Yu]

Hi all.

I understand user can go to a job and click watch job to subscribe yourself
for the changes of this job. What I'm trying to do is in system groovy, use
the class in Jenkins email-ext plugin to add other people to the watch job
list.

At the moment, after I run my script, user "build" is not added to the
watch list.
Here's my system groovy script:

import jenkins.model.*;
import hudson.model.*;
import hudson.plugins.emailext.watching.*;

def build = Thread.currentThread().getCurrentExecutable()
def buildEnvVars = new HashMap()
buildEnvVars.putAll(build.getEnvVars())
def JOB_NAME = buildEnvVars["JOB_NAME"]

println JOB_NAME
instance = Jenkins.instance.getItemByFullName(JOB_NAME)

EmailExtWatchAction watch = new EmailExtWatchAction(instance)

User user = User.get("build")

prop = watch.getJobProperty()
prop.addWatcher(user)
instance.save()

println """
IS_WATCHING=${watch.isWatching()}
EMAIL_TRIGGERS=${watch.getTriggers()}
WATCHERS = ${prop.getWatchers()}
"""


Many thanks,
Kevin

-- 
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/CAMV-oz%3DDEdL8g17UPnj%2BA7XCDSg%2BjnGRFwgEiTCh0MqyWaTn7g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Latest version of Chrome 52.0.2743.116 fails to launch under Jenkins 2.7.2

[Kevin MacDonald]

My problem is fixed. I was lucky enough to come across this web 
page: 
https://sites.google.com/a/chromium.org/chromedriver/help/chrome-doesn-t-start
which instructed me to add the --no-sandbox switch when launching Chrome. 
Jenkins 2.7.2 with the service running under the System account, using the 
latest versions of Chrome and chromedriver. exe is now working. I enabled 
the Jenkins chromedriver plugin so that I have the latest version in use.

On Wednesday, August 10, 2016 at 11:10:32 AM UTC-7, Kevin MacDonald wrote:
>
> I am running Jenkins v2.7.2 on Windows Server 2008 R2. 
>
> Upon Chrome updating to this latest version, Watir now fails to launch 
> Chrome properly. Chrome comes up under the System account and sits with a 
> black screen. I also tried directing Selenium to use Chrome Canary. No 
> luck. 
>
> I am doing this in ruby. If I remove the Chrome path then the current 
> version of Chrome is used:
> Selenium::WebDriver::Chrome.path = 
> "C:\\Users\\admin\\AppData\\Local\\Google\\Chrome 
> SxS\\Application\\chrome.exe" 
>$ie = Watir::Browser.new :chrome, :switches => 
> %w[--ignore-certificate-errors --disable-extensions 
> --disable-popup-blocking --disable-translate --allow-file-access 
> --disable-gpu --incognito]
>
>
> I've also tried various combinations of using the Jenkins Chromedriver 
> plugin or not with Chrome or Chrome Canary, and I get a widely varying 
> array of errors, any of which can be googled for and will turn up on very 
> old threads. I am very stuck.
>

-- 
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/5a70ea9c-ce65-4942-adbb-188592b4cbd4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Run pipeline flyweight executors off of master

[Kevin Phillips]

In my opinion, even more problematic than possibly running unsafe code in a 
flyweight executor on the master is the fact that these flyweight pipeline 
threads perform a full checkout of the target repository - at least when 
using Git as the SCM. So if one has a relatively large code repository 
containing product code - say several gigabytes - and they want to store 
their Jenkinsfile with the code so they can leverage the MultiBranch 
options in Jenkins Pipeline, they end up with many copies of their entire 
codebase being checked out on the master, possibly causing the master to 
run out of disk space. Add to this the fact that these "temporary" 
workspaces created on the master by the flyweight tasks are not 
automatically deleted when not in use and there is no way to purge them 
from the Jenkins dashboard and you are just asking for problems. This isn't 
a case of whether this will become a problem as much as it is an issue of 
when it will become a problem.

In my opinion, Jenkinsfile's stored in SCM should be checked out on an 
agent as a typical freestyle job would do, and a default "node" allocated 
by the executor that launches the script contained therein for the node on 
which it is already running on. Then the rest of the Jenkinsfile could be 
processed in place without requiring any sort of flyweight executor at all, 
and avoiding the issues with having multiple checkouts of the same code 
spread across a build farm. Also, I think this would be inline with how 
some other more modern continuous integration servers work like travis-ci, 
so it's not without precidence.

On Monday, June 13, 2016 at 6:03:20 PM UTC-3, Eli White wrote:
>
> We follow the Jenkins configuration best practices and have no executors 
> on our master node and force everything to run on our agents. 
>
> We are starting to work with pipeline jobs and are worried that bad 
> Jenkinsfiles could cause problems on our master. 
> How can we force the flyweight jobs to run on a designated machine *other* 
> than master? 
>
> How do other people handle this?
>

-- 
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/2e7225fd-1017-4e66-ab9e-8802ed24c1a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Latest version of Chrome 52.0.2743.116 fails to launch under Jenkins 2.7.2

[Kevin MacDonald]

I am running Jenkins v2.7.2 on Windows Server 2008 R2. 

Upon Chrome updating to this latest version, Watir now fails to launch 
Chrome properly. Chrome comes up under the System account and sits with a 
black screen. I also tried directing Selenium to use Chrome Canary. No 
luck. 

I am doing this in ruby. If I remove the Chrome path then the current 
version of Chrome is used:
Selenium::WebDriver::Chrome.path = 
"C:\\Users\\admin\\AppData\\Local\\Google\\Chrome 
SxS\\Application\\chrome.exe" 
   $ie = Watir::Browser.new :chrome, :switches => 
%w[--ignore-certificate-errors --disable-extensions 
--disable-popup-blocking --disable-translate --allow-file-access 
--disable-gpu --incognito]


I've also tried various combinations of using the Jenkins Chromedriver 
plugin or not with Chrome or Chrome Canary, and I get a widely varying 
array of errors, any of which can be googled for and will turn up on very 
old threads. I am very stuck.

-- 
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/4e75caf6-c682-4977-a08c-a4c04a420bb8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Authentication problems creating GitHub organization folder

[Kevin Godby]

Hello.

I'm trying to create a folder for my GitHub organization. Unfortunately, 
when I select my GitHub credentials, it says 'invalid credentials' and 
fails to scan the repositories (throwing a FileNotFoundException). Scanning 
with no credentials works initially but quickly runs up against the rate 
limit.

The personal access token associated with the GitHub user I selected has 
the following OAuth scopes enabled for Jenkins:

 * repo
* repo:status
* repo_deployment
* public_repo
 * admin:repo_hook
* read:repo_hook
* write:repo_hook
 * admin:org_hook

Does anyone have any suggestions as to what the problem might be?

Thanks!

—Kevin Godby

-- 
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/31f716a9-58fa-4051-8462-526d8eb9439e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

using slack notifications to multiple teams/channels

[Kevin]

per this post - https://github.com/jenkinsci/slack-plugin/issues/111 I 
should be able to configure my slack settings to be able to send build 
notifications to multiple teams.
but there is nothing in the help section or on the slack plugin page 
- https://wiki.jenkins-ci.org/display/JENKINS/Slack+Plugin that explains 
the syntax of how you specify multiple teams. I have tried spaces between 
team names, commas, commas and spaces etc but I immediately get an error. 
Same thing for tokens.

should it be -

team1,team2
token for team1, token for team2 etc.?

-- 
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/d079fddd-a2b6-4f3f-a8de-71561c4231c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Launching a slave as a docker-cloud (formerly tutum) stack

[Kevin Milner]

Hello,
I am trying to put together a jenkins system that is hosted on AWS through 
docker-cloud. I have created a few stacks that have the modules that I 
might want to test against (mongo, rabbit, etc). The Jenkins master is also 
running on its own stack. I wrote two scripts, one on the master (called 
start_slave.sh) and the other on the slave (called phone_home.sh).
start_slave using the docker-cloud cli (installed on the master) to spin up 
a selected stack. The last thing the start_slave script does is issue a 
docker-cloud exec 
(https://docs.docker.com/apidocs/docker-cloud/#execute-command-inside-a-container)
 
command that launches phone_home.sh on the slave. The phone_home script 
basically just downloads and launches the slave.jar.
When I run start_slave from a terminal on the master, the slave.jar file 
appears to launch as expected (I get the information about how I'm not 
using it right, then it goes into spittting out mime code to the stdout. 
I'm guessing this is what it is supposed to look like?), but when I try to 
run the container as part of a dummy node startup script, the logs show the 
connection just hanging after the launch of phone_home.
My question is this: Is there something I'm missing about launching the 
slave.jar from inside a container? Am I doing this correctly? 
I've also tried to launch the stack by mounting the docker socket in both 
the slave and master, using curl to issue api commands and the docker 
plugin. None of these seem to work but except for the plugin are more 
docker issues if I can't get this to work.
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/162787d8-cd33-431f-82b9-c617ada5ac43%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ability to show new repo commits after last build?

[Kevin]

Hi Baptiste,
at the moment, the devs are manually triggering builds when they are ready 
(probably once every couple of hours). I agree that it should be happening 
much more often than that and am going to start getting them used to the 
idea that as soon as they make a commit, that code will be checked out and 
tested by Jenkins. You guys are right - once we start doing this, there 
should be no need for that other feature I initially posted about.

-- 
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/dac5573c-3956-4f3b-a66a-54e791dc725f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ability to show new repo commits after last build?

[Kevin]

bummer. I have been slowing migrating our projects over from TeamCity and 
found out today that this was a feature that my devs really liked in 
TeamCity. 
thanks for the quick response.


On Tuesday, March 22, 2016 at 2:33:02 PM UTC-5, Kevin wrote:
>
> may be overlooking something simple but is there a way to display in a 
> Jenkins project any new commits made to a Github repo (that the Jenkins 
> project is configured to use) since the last build was run? 
>
> My users are hoping to be able to go into Jenkins, select a project and 
> see somewhere a list of the newest commits to the repo since the last 
> successfully completed build.
>

-- 
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/b8259f6c-5f27-4d1e-af93-2139aa88376d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Ability to show new repo commits after last build?

[Kevin]

 

may be overlooking something simple but is there a way to display in a 
Jenkins project any new commits made to a Github repo (that the Jenkins 
project is configured to use) since the last build was run? 

My users are hoping to be able to go into Jenkins, select a project and see 
somewhere a list of the newest commits to the repo since the last 
successfully completed build.

-- 
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/08b94e33-6e25-4099-b650-8c362a733537%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Parameterized Trigger / Future.get() is blocking/failing

[Kevin Prettre]

Hi again,

after further research, it seems that I'm experiencing this 
issue https://issues.jenkins-ci.org/browse/JENKINS-19776 that was 
previously marked as resolved.

Seems not after all.

@Oleg Nenashev might help

Le mercredi 27 janvier 2016 14:23:07 UTC+1, Kevin Prettre a écrit :
>
> Hi all
>
> I'm facing a problem with this plugin (version listed a the end of the 
> post).
>
> I've a main job (JobA) that generates 50 different parameter files for 
> another job to perform (JobB).
>
> All the 50 JobB are correctly put in the queue, and JobA starts to loop 
> here TriggerBuilder.java#L138 
> <https://github.com/jenkinsci/parameterized-trigger-plugin/blob/e54b5c308514be9b560d66d9a650a5239915b889/src/main/java/hudson/plugins/parameterizedtrigger/TriggerBuilder.java#L138>
> .
>
> But suddenly, for no appearing reason, JobA stops looping. However, in the 
> meantime, all of the 50 JobB have successfully finished their work.
>
> If anyone could drop an idea so I can further investigate, because I'm out 
> of idea and I've been pulling my hair with this for the past 2 weeks.
>
> *More info :*
>
> Jenkins v 1.625
> Parameterized Trigger Plugin v 2.29
>
>
> Thanks a lot
>

-- 
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/6b10c228-eda7-4ed5-aceb-a5a6130cda54%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Parameterized Trigger / Future.get() is blocking/failing

[Kevin Prettre]

Hi all

I'm facing a problem with this plugin (version listed a the end of the 
post).

I've a main job (JobA) that generates 50 different parameter files for 
another job to perform (JobB).

All the 50 JobB are correctly put in the queue, and JobA starts to loop 
here TriggerBuilder.java#L138 

.

But suddenly, for no appearing reason, JobA stops looping. However, in the 
meantime, all of the 50 JobB have successfully finished their work.

If anyone could drop an idea so I can further investigate, because I'm out 
of idea and I've been pulling my hair with this for the past 2 weeks.

*More info :*

Jenkins v 1.625
Parameterized Trigger Plugin v 2.29


Thanks a lot

-- 
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/cf401573-f773-4fb7-b77b-248462c595be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: PeriodicWork not running periodically

[Kevin]

I should have mentioned that all 10 of the jenkins.util.Timer's are in the 
RUNNABLE state and the Jenkins cron thread is in TIMED_WAITING which seems 
to make sense (I think).

The queued and completed tasks from jenkins.util.Timer.get() hasn't changed 
appreciably
On Friday, January 15, 2016 at 9:00:23 AM UTC-5, Kevin wrote:
>
> Wow, can't believe I didn't know about /threadDump before, thanks!
>
> Anyways I mostly see lots (on the order of 100s) of:
>
> "Computer.threadPoolForRemoting [#85811]" Id=380625 Group=main 
> TIMED_WAITING on 
> java.util.concurrent.SynchronousQueue$TransferStack@687826ae
> at sun.misc.Unsafe.park(Native Method)
> -  waiting on java.util.concurrent.SynchronousQueue$TransferStack@687826ae
> at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> at 
> java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(SynchronousQueue.java:460)
> at 
> java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:362)
> at java.util.concurrent.SynchronousQueue.poll(SynchronousQueue.java:941)
> at 
> java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1066)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
>
>
> I did see some (~20) CPS executors that looked suspicious (they're also 
> hanging forever when i go to the job):
>
> "Running CpsFlowExecution[Owner[workflow_test/619:workflow_test#619]]" 
> Id=7310 Group=main RUNNABLE
> at 
> org.kohsuke.stapler.framework.io.LargeText$BufferSession.skip(LargeText.java:532)
> at 
> org.kohsuke.stapler.framework.io.LargeText.writeLogTo(LargeText.java:211)
> at 
> hudson.console.AnnotatedLargeText.writeRawLogTo(AnnotatedLargeText.java:162)
> at 
> org.jenkinsci.plugins.workflow.job.WorkflowRun.copyLogs(WorkflowRun.java:359)
> at 
> org.jenkinsci.plugins.workflow.job.WorkflowRun.access$600(WorkflowRun.java:107)
> at 
> org.jenkinsci.plugins.workflow.job.WorkflowRun$GraphL.onNewHead(WorkflowRun.java:752)
> -  locked java.util.concurrent.atomic.AtomicBoolean@7eb2df49
> at 
> org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.notifyListeners(CpsFlowExecution.java:799)
> at 
> org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$4.run(CpsThreadGroup.java:320)
> at 
> org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:32)
> at 
> hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)
> at 
> jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
>
> Number of locked synchronizers = 1
> - java.util.concurrent.ThreadPoolExecutor$Worker@d3b1e0f
>
>
> I noticed them before but I assumed they weren't related to this, issue, I 
> think they're waiting for slaves nodes that have been removed from our 
> jenkins (not just disconnected but deleted), I'll clean these up with the 
> /kill url on workflows and see if that improves things since the threaddump 
> makes me wonder if these are related.
>
>
> Thanks again
>
> On Thursday, January 14, 2016 at 4:14:16 PM UTC-5, Christopher Orr wrote:
>>
>> On 14/01/16 21:30, Kevin wrote: 
>> > Hi all, I've got some custom cloud providers that don't seem to get 
>> > triggered, I've traced it back to NodeProvisionerInvoker not being 
>> > called (even after 30 minutes of waiting), I can call the 
>> > nodeProvisioners by hand (using the update function) in the same way 
>> > that the NodeProvisionerInvoker does in the groovy script console and 
>> > things seem to work.  Actually it seems like a number of bits related 
>> to 
>> > PeriodicWork classes aren't working since I assume git polling and the 
>> > periodic build setting are a PeriodicWork things, but they're also not 
>> > triggering. 
>> > 
>> > I did also look at PeriodicWork.all().collect {it.class.name} 
>> > and println jenkins.util.Timer.get() and got: 
>> > 
>> > hudson.diagnosis.HudsonHomeDiskUsageChecker, 
>> > hudson.diagnosis.MemoryUsageMonitor, 
>> > hudson.model.FingerprintClea

Re: PeriodicWork not running periodically

[Kevin]

Wow, can't believe I didn't know about /threadDump before, thanks!

Anyways I mostly see lots (on the order of 100s) of:

"Computer.threadPoolForRemoting [#85811]" Id=380625 Group=main 
TIMED_WAITING on 
java.util.concurrent.SynchronousQueue$TransferStack@687826ae
at sun.misc.Unsafe.park(Native Method)
-  waiting on java.util.concurrent.SynchronousQueue$TransferStack@687826ae
at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
at 
java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(SynchronousQueue.java:460)
at 
java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:362)
at java.util.concurrent.SynchronousQueue.poll(SynchronousQueue.java:941)
at 
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1066)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)


I did see some (~20) CPS executors that looked suspicious (they're also 
hanging forever when i go to the job):

"Running CpsFlowExecution[Owner[workflow_test/619:workflow_test#619]]" 
Id=7310 Group=main RUNNABLE
at 
org.kohsuke.stapler.framework.io.LargeText$BufferSession.skip(LargeText.java:532)
at org.kohsuke.stapler.framework.io.LargeText.writeLogTo(LargeText.java:211)
at 
hudson.console.AnnotatedLargeText.writeRawLogTo(AnnotatedLargeText.java:162)
at 
org.jenkinsci.plugins.workflow.job.WorkflowRun.copyLogs(WorkflowRun.java:359)
at 
org.jenkinsci.plugins.workflow.job.WorkflowRun.access$600(WorkflowRun.java:107)
at 
org.jenkinsci.plugins.workflow.job.WorkflowRun$GraphL.onNewHead(WorkflowRun.java:752)
-  locked java.util.concurrent.atomic.AtomicBoolean@7eb2df49
at 
org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.notifyListeners(CpsFlowExecution.java:799)
at 
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$4.run(CpsThreadGroup.java:320)
at 
org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:32)
at 
hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)
at 
jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Number of locked synchronizers = 1
- java.util.concurrent.ThreadPoolExecutor$Worker@d3b1e0f


I noticed them before but I assumed they weren't related to this, issue, I 
think they're waiting for slaves nodes that have been removed from our 
jenkins (not just disconnected but deleted), I'll clean these up with the 
/kill url on workflows and see if that improves things since the threaddump 
makes me wonder if these are related.


Thanks again

On Thursday, January 14, 2016 at 4:14:16 PM UTC-5, Christopher Orr wrote:
>
> On 14/01/16 21:30, Kevin wrote: 
> > Hi all, I've got some custom cloud providers that don't seem to get 
> > triggered, I've traced it back to NodeProvisionerInvoker not being 
> > called (even after 30 minutes of waiting), I can call the 
> > nodeProvisioners by hand (using the update function) in the same way 
> > that the NodeProvisionerInvoker does in the groovy script console and 
> > things seem to work.  Actually it seems like a number of bits related to 
> > PeriodicWork classes aren't working since I assume git polling and the 
> > periodic build setting are a PeriodicWork things, but they're also not 
> > triggering. 
> > 
> > I did also look at PeriodicWork.all().collect {it.class.name} 
> > and println jenkins.util.Timer.get() and got: 
> > 
> > hudson.diagnosis.HudsonHomeDiskUsageChecker, 
> > hudson.diagnosis.MemoryUsageMonitor, 
> > hudson.model.FingerprintCleanupThread, 
> > hudson.model.LoadStatistics$LoadStatisticsUpdater, 
> > hudson.model.WorkspaceCleanupThread, 
> > hudson.slaves.ComputerRetentionWork, 
> > hudson.slaves.ConnectionActivityMonitor, 
> > hudson.slaves.NodeProvisioner$NodeProvisionerInvoker, 
> > hudson.triggers.Trigger$Cron, 
> > jenkins.model.DownloadSettings$DailyCheck, 
> > org.jenkinsci.plugins.periodicreincarnation.PeriodicReincarnation] 
> > 
> > 
> > and 
> > 
> > 
> jenkins.util.ErrorLoggingScheduledThreadPoolExecutor@6d72bb0e[Running, 
> > pool size = 10, active threads = 10, queued tasks = 2521, completed 
> > tasks = 1134830] 
>
> If the number of active threads remains equ

PeriodicWork not running periodically

[Kevin]

Hi all, I've got some custom cloud providers that don't seem to get 
triggered, I've traced it back to NodeProvisionerInvoker not being called 
(even after 30 minutes of waiting), I can call the nodeProvisioners by hand 
(using the update function) in the same way that the NodeProvisionerInvoker 
does in the groovy script console and things seem to work.  Actually it 
seems like a number of bits related to PeriodicWork classes aren't working 
since I assume git polling and the periodic build setting are a 
PeriodicWork things, but they're also not triggering.

I did also look at PeriodicWork.all().collect {it.class.name} and println 
jenkins.util.Timer.get() and got:

hudson.diagnosis.HudsonHomeDiskUsageChecker, 
hudson.diagnosis.MemoryUsageMonitor, hudson.model.FingerprintCleanupThread, 
hudson.model.LoadStatistics$LoadStatisticsUpdater, 
hudson.model.WorkspaceCleanupThread, hudson.slaves.ComputerRetentionWork, 
hudson.slaves.ConnectionActivityMonitor, 
hudson.slaves.NodeProvisioner$NodeProvisionerInvoker, 
hudson.triggers.Trigger$Cron, jenkins.model.DownloadSettings$DailyCheck, 
org.jenkinsci.plugins.periodicreincarnation.PeriodicReincarnation]


and 

jenkins.util.ErrorLoggingScheduledThreadPoolExecutor@6d72bb0e[Running, pool 
size = 10, active threads = 10, queued tasks = 2521, completed tasks = 
1134830]


respectively.  Anyways does anyone have any idea what might make periodic 
work items decide to no longer run?  Is there any way to restart this thing 
without rebooting Jenkins?

I'm using the latest Jenkins now, but was using a Jenkins from ~November 
and also had this issue crop up recently (after having run on that version 
without encountering this issue for a couple months)

Thanks in advance.
-Kevin

-- 
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/c9270830-8c0a-4623-95d7-eac10b9d426c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Running Scala (SBT) Script as Post-Build "Execute Shell" Task?

[Kevin Meredith]

I added an "Execute Shell" post-build task to my Jenkins Job. 

However, the script fails since I don't have sbt <http://www.scala-sbt.org/> (a 
build tool for Scala, the JVM language) installed.

The build job's Console Output shows:

>line 47: sbt: command not found

Based on this StackOverflow answer 
<http://stackoverflow.com/a/15020218/409976>, I'm expecting that I need to:

1. install `sbt` on the Jenkins box
2. git clone my project to the Linux equivalent of `/Jenkins/workspace/`
3. edit my script to `cd` in order to get to the root directory of my 
project
4. run the script via `sbt ...`

Thanks
Kevin

-- 
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/6a0d6e1a-8057-4648-9649-c384836617e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: Jenkins freaked out

[Kevin Brown]

I’m guessing it was the second option as we don’t do automated builds of code, 
but use Jenkins like a CRON service for our environment (scripts that clean up 
logs, perform maintenance on the database, back office work, etc…). The 
permissions we took away was basically yanking the Authorized_keys file from 
the remote systems so that Jenkins couldn’t login to the system (send commands 
via ssh). I’m guessing the clean shutdown cleared out all the bad cruft from 
the metadata and that’s why Jenkins came up properly the second time. After 
that second boot up Jenkins behaved normally (other than not being able to 
successfully send the commands over ssh to the remote systems).

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Jennifer Hofmeister
Sent: Friday, November 06, 2015 5:55 AM
To: jenkinsci-users@googlegroups.com
Subject: RE: Jenkins freaked out

Hi,

I can imagine two scenarios, that are Jenkins-unspecific:


-  You had a number of CMS commits after the outage (if this is 
possible on your systems), and once Jenkins was back up again, it polled all of 
them at once and thus ended up with a bulk of new builds, including several 
different changes in the same job

-  Your power outage caused some metadata loss (maybe Jenkins was 
writing at the time the outage occurred), and Jenkins “forgot” its build 
history, thus trying to fire up every one of those jobs to what it thought was 
an initial first build.

I had a scenario similar to the last one when I wanted to update Jenkins to 
1.6xx. The newer version failed to import the old build history into the new 
format, and I experienced the effect you described. So it could be some hiccup 
caused by corrupted data.

Did you experience anything else after you restarted Jenkins? Do you think it 
has to do with the permissions (which permissions?) you took away?

Jennifer

From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Kevin Brown
Sent: Donnerstag, 5. November 2015 17:34
To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>
Subject: Jenkins freaked out

I’m not exactly sure what happened with our Jenkins, but we had a power outage 
that took the machines down without any chance of graceful shutdown. When we 
got the systems back up, we started Jenkins up and instead of starting up and 
just bringing up the few jobs that were scheduled for around the time the 
machine started up, we had all the Build Executors full (30) and over 120 jobs 
in the Build Queue, quite a few of which were the same job, so it was firing 
off jobs as fast as the Build Executors could come free from another job. We 
were able to then shutdown Jenkins via its interface and after taking away the 
permissions on the remote systems it runs jobs on, we brought it back up and 
the Build Queue was empty and the Build Executors were quiet.

Any thoughts on why this might have happened?

Jenkins v 1.596
--
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/FCBFCDE72C66B34C8F7AD8D62D262D4E36432244%40ilsaw05.corp.incentivelogic.com<https://groups.google.com/d/msgid/jenkinsci-users/FCBFCDE72C66B34C8F7AD8D62D262D4E36432244%40ilsaw05.corp.incentivelogic.com?utm_medium=email&utm_source=footer>.
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAA587D532C45541B62417404F1D22030E83D378%40you-exch1.younicos.local<https://groups.google.com/d/msgid/jenkinsci-users/CAA587D532C45541B62417404F1D22030E83D378%40you-exch1.younicos.local?utm_medium=email&utm_source=footer>.
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/FCBFCDE72C66B34C8F7AD8D62D262D4E3643345E%40ilsaw05.corp.incentivelogic.com.
For more options, visit https://groups.google.com/d/optout.

Re: jenkins UI hanging on job page, threads blocked

[brother kevin]

So our curl job helped to mask the issue, but eventually it too started 
backing up, unable to keep up with the slowdown.  It appears that this 
issue evidences itself every time garbage collection occurs.

We are using the junit plugin v1.9 
(https://wiki.jenkins-ci.org/display/JENKINS/JUnit+Plugin) to provide graph 
and convenient links to test failures. This plugin appears to be at the 
heart of the slowdown, but it isn't clear to us WHY these chains of reads 
are happening in the first place.  Also note we save 500 builds for each 
job and would save more if it was feasible.

So, lets manually trigger a garbage collection and then go visit two 
interstitial build pages (e.g. https://jenkins/jobs/job1/1234/ and 
https://jenkins/jobs/job2/3456)

Now lets run the following strace against the pid of the jenkins java 
processon our CentOS install -

strace -p  -f -e trace='!futex' -s1000 -e trace='open' 2>&1 | 
grep 'jobs'

OUTPUT:
[pid 1000] 16:45:21 
open("/var/lib/jenkins/jobs/job1/builds/1234/junitResult.xml", O_RDONLY) = 
487
[pid 2000] 16:45:24 
open("/var/lib/jenkins/jobs/job2/builds/3456/junitResult.xml", O_RDONLY) = 
483
[pid 1000] 16:45:26 
open("/var/lib/jenkins/jobs/job1/builds/1233/junitResult.xml", O_RDONLY) = 
487
[pid 2000] 16:45:28 
open("/var/lib/jenkins/jobs/job2/builds/3455/junitResult.xml", O_RDONLY) = 
483

It will continue to do this for all 500 builds for each job, spinning up 
another java thread for each job, starting a cycle lasting ~41 minutes (500 
builds, 5 seconds each).  Remember, this was triggered by visiting a single 
interstitial job page for each job.  What is it doing?

It appears to be opening each 16MB junit.xml file and parsing it... but for 
what purpose?

strace of pid that is opening each 16MB junit.xml -
[pid 21366] 16:50:46 fstat(177, {st_mode=S_IFREG|0644, st_size=18788419, 
...}) = 0
[pid 21366] 16:50:46 lseek(177, 0, SEEK_CUR) = 10403840
[pid 21366] 16:50:46 lseek(177, 0, SEEK_END) = 18788419
[pid 21366] 16:50:46 lseek(177, 10403840, SEEK_SET) = 10403840
[pid 21366] 16:50:46 read(177, "8K of XML DATA

[pid 21366] 16:50:46 fstat(177, {st_mode=S_IFREG|0644, st_size=18788419, 
...}) = 0
[pid 21366] 16:50:46 lseek(177, 0, SEEK_CUR) = 10412032
[pid 21366] 16:50:46 lseek(177, 0, SEEK_END) = 18788419
[pid 21366] 16:50:46 lseek(177, 10412032, SEEK_SET) = 10412032
[pid 21366] 16:50:46 read(177, "NEXT 8K OF XML FILE

We have temporarily reduced the pain caused by this issue by reducing the 
number of saved builds from 500 to 50, but we would love to find a fix or 
better understand what is happening.

Thanks!

Kevin*2



On Wednesday, October 14, 2015 at 8:40:16 AM UTC-7, brother kevin wrote:
>
> To follow-up on this thread for anyone who is experiencing similar issues 
> with junit processing and memory usage -
>
> Firstly, we noticed that a specific set of pages were taking the longest 
> to load - the interstitial build number pages that show changes, scm 
> revisions, and a Test Result link (e.g. https://jenkins/job/myjob/43980/).
>
> Secondly, we noticed that the longer the job ran without someone actively 
> loading one of the interstitial build pages, the worse the problem became. 
>  For example, attempting to load one of these pages after a weekend with no 
> activity could take upwards of a minute.
>
> Finally, if the most recent interstitial job page was loaded by a single 
> user, all of the other pages then became responsive for all users.
>
> Our workaround for the time being is a cron job that pre-loads these 
> interstitial pages using curl.  We were pleasantly surprised this worked at 
> all and we are anxious to better understand what is causing this new 
> blocking behavior.
>
> 0 * * * * jenkins lastBuild=`ls -ltr /var/lib/jenkins/jobs/myjob/builds | 
> tail -1 | awk '{print $9}'`; curl -k https://jenkins/job/myjob/$lastBuild/ 
> > /tmp/$lastBuild.output
>
>
>
> On Tuesday, September 29, 2015 at 11:09:46 AM UTC-7, brother kevin wrote:
>>
>> The problem returned after changing the max builds back to 500 for the 
>> job in question.  We kept upping the -Xmx value and jenkins continued to 
>> run out of memory and the web ui would become unusable, with most requests 
>> timing out.
>>
>> We eventually settled on -Xmx16384M and the jenkins monitoring plugin 
>> showed the junit xml processing cresting the 16GB watermark.
>>
>> We upgraded from v1.8 of the junit plugin, to the latest version v1.9, 
>> and experienced the same excessive memory usage.
>>
>> The junit.xml file has includes 51,000 tests and is about 17MB in size. 
>>  Is that indicative of a job that has too many tests within it?
>>
>> Please advise, we have turned off junit processing on the job in question 

Jenkins freaked out

[Kevin Brown]

I'm not exactly sure what happened with our Jenkins, but we had a power outage 
that took the machines down without any chance of graceful shutdown. When we 
got the systems back up, we started Jenkins up and instead of starting up and 
just bringing up the few jobs that were scheduled for around the time the 
machine started up, we had all the Build Executors full (30) and over 120 jobs 
in the Build Queue, quite a few of which were the same job, so it was firing 
off jobs as fast as the Build Executors could come free from another job. We 
were able to then shutdown Jenkins via its interface and after taking away the 
permissions on the remote systems it runs jobs on, we brought it back up and 
the Build Queue was empty and the Build Executors were quiet.

Any thoughts on why this might have happened?

Jenkins v 1.596

-- 
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/FCBFCDE72C66B34C8F7AD8D62D262D4E36432244%40ilsaw05.corp.incentivelogic.com.
For more options, visit https://groups.google.com/d/optout.

Re: jenkins UI hanging on job page, threads blocked

[brother kevin]

To follow-up on this thread for anyone who is experiencing similar issues 
with junit processing and memory usage -

Firstly, we noticed that a specific set of pages were taking the longest to 
load - the interstitial build number pages that show changes, scm 
revisions, and a Test Result link (e.g. https://jenkins/job/myjob/43980/).

Secondly, we noticed that the longer the job ran without someone actively 
loading one of the interstitial build pages, the worse the problem became. 
 For example, attempting to load one of these pages after a weekend with no 
activity could take upwards of a minute.

Finally, if the most recent interstitial job page was loaded by a single 
user, all of the other pages then became responsive for all users.

Our workaround for the time being is a cron job that pre-loads these 
interstitial pages using curl.  We were pleasantly surprised this worked at 
all and we are anxious to better understand what is causing this new 
blocking behavior.

0 * * * * jenkins lastBuild=`ls -ltr /var/lib/jenkins/jobs/myjob/builds | 
tail -1 | awk '{print $9}'`; curl -k https://jenkins/job/myjob/$lastBuild/ 
> /tmp/$lastBuild.output



On Tuesday, September 29, 2015 at 11:09:46 AM UTC-7, brother kevin wrote:
>
> The problem returned after changing the max builds back to 500 for the job 
> in question.  We kept upping the -Xmx value and jenkins continued to run 
> out of memory and the web ui would become unusable, with most requests 
> timing out.
>
> We eventually settled on -Xmx16384M and the jenkins monitoring plugin 
> showed the junit xml processing cresting the 16GB watermark.
>
> We upgraded from v1.8 of the junit plugin, to the latest version v1.9, and 
> experienced the same excessive memory usage.
>
> The junit.xml file has includes 51,000 tests and is about 17MB in size. 
>  Is that indicative of a job that has too many tests within it?
>
> Please advise, we have turned off junit processing on the job in question 
> and our memory usage has dropped to below 4GB.
>
> Thank you!
>
>>

-- 
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/922ed56a-d029-48cb-a5b1-6fd6b6e20676%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: is 51,000 tests too much in a job?

[Kevin Goess]

> Check how much heap you have allowed jenkins to use.  

We're currently running with

 -XX:PermSize=128M -XX:MaxPermSize=512M -Xmx16384M

and the jenkins memory graph under /monitoring shows us maxing out under 
12GB, and that seems excessive to me, since we only have about a dozen 
builds going on. Is 12-16GB there excessive and maybe indicative of a 
problem, or is that all standard?

-- 
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/44a41436-1833-4663-8be1-0092f5041fdf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

is 51,000 tests too much in a job?

[Kevin Goess]

Is 51,000 tests too much in a single job?

We're seeing painful slowdowns in the Jenkins UI and this question came up. 
 Our junit.xml file is about 17MB in size.  Are other people running that 
number of tests successfully?




-- 
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/9be581c9-263b-457a-ab06-6fabcdbd0b6d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Deleting Jenkins Bindings

[Kevin Meredith]

Solution:

*Jenkins -> Credentials -> Select Binding -> Delete*

-- 
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/5f17b36c-e4a6-4f12-b77b-5486c88037e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Using Remote Access API to Add Binding?

[Kevin Meredith]

Given a Jenkins build using the Remote Access API 
, is it 
possible to create Secret Text values?

Also, is it possible to specify that a Build should use a particular 
Binding, as well as its corresponding environment variable?

Example (of what I'm looking for):

PUT JENKINS_URL/build/1234/plugins  w/ body { "key": FOO, 
"binding_name_to_use": FOO_BINDING }

I'd expect for that POST to set a Binding of "FOO" with a value of 
"FOO_BINDING" (I'm assuming that FOO_BINDING was already created) to the 
build "1234."

Does such an API call exist?

-- 
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/0a50ea79-8af8-43d4-a8ea-303a4be3051c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Active Directory Plugin is not working

[Kevin Meredith]

LDAP Error Code 49: 

indicates that during a bind operation one of the following occurred: The 
client passed either an incorrect DN or password, or the password is 
incorrect because it has expired, intruder detection has locked the 
account, or another similar reason. See the data code for more information.

-http://wiki.servicenow.com/index.php?title=LDAP_Error_Codes#gsc.tab=0

On Thursday, October 1, 2015 at 5:31:19 PM UTC-4, Viviana Chévez wrote:
>
>Hello, I´ve been having issues with the Active Directory Plugin, I´ve 
> been using Jenkins for 3 months, and this is the first time that this 
> happen.
> Im using Jenkins version 1.631. Today, suddenly, I cannot login in 
> Jenkins, this is the log.
>
>  Oct 01, 2015 3:24:55 PM 
> hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl 
> bind
> WARNING: Failed to authenticate while binding to companydomain
> javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: 
> LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 52e, 
> v1db1 ]
> at com.sun.jndi.ldap.LdapCtx.mapErrorCode(Unknown Source)
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(Unknown Source)
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(Unknown Source)
> at com.sun.jndi.ldap.LdapCtx.connect(Unknown Source)
> at com.sun.jndi.ldap.LdapCtx.ensureOpen(Unknown Source)
> at com.sun.jndi.ldap.LdapCtx.ensureOpen(Unknown Source)
> at com.sun.jndi.ldap.LdapCtx.reconnect(Unknown Source)
> at 
> hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:518)
> at 
> hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:434)
> at 
> hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:263)
> at 
> hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:219)
> at 
> hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:163)
> at 
> org.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:122)
> at 
> org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:200)
> at 
> org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:47)
> at 
> org.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:74)
> at 
> org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252)
> at 
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
> at 
> jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93)
> at 
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
> at 
> org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
> at 
> hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
> at 
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
> at 
> hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
> at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
> at 
> org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
> at 
> hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
> at 
> org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474)
> at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499)
> at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
> at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533)
> at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
> at 
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428)
> at 
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)
> at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
> at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWr

Re: Deleting Jenkins Bindings

[Kevin Meredith]

Note - I posted this question in Stackoverflow too 
- http://stackoverflow.com/questions/32890683/deleting-jenkins-bindings.

-- 
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/55b977c1-57da-4afb-a8e2-6a8e651ec379%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: jenkins UI hanging on job page, threads blocked

[brother kevin]

The problem returned after changing the max builds back to 500 for the job 
in question.  We kept upping the -Xmx value and jenkins continued to run 
out of memory and the web ui would become unusable, with most requests 
timing out.

We eventually settled on -Xmx16384M and the jenkins monitoring plugin 
showed the junit xml processing cresting the 16GB watermark.

We upgraded from v1.8 of the junit plugin, to the latest version v1.9, and 
experienced the same excessive memory usage.

The junit.xml file has includes 51,000 tests and is about 17MB in size.  Is 
that indicative of a job that has too many tests within it?

Please advise, we have turned off junit processing on the job in question 
and our memory usage has dropped to below 4GB.

Thank you!

>

-- 
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/decd1354-c50a-4848-bcd5-68f3e4cdd414%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Deleting Jenkins Bindings

[Kevin Meredith]

I'm using Jenkins in order to pass environment variables to a build script:




However, I'd like to delete some un-used bindings. 

How can I do that?

-- 
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/6954ae25-15fa-401b-bfe1-9a277714e6df%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

jenkins UI hanging on job page, threads blocked

[Kevin Goess]

For one one our builds, if we try to load a job page like /job/www/12345/, 
the browser would hang forever and the jenkins /monitoring page would show 
the thread blocked on TestResultAction









Handling GET /job/www/43365/ from x.x.x.x 
: RequestHandlerThread[#17] AbstractBuild/index.jelly 
AbstractTestResultAction/summary.jelly   
yes 5 BLOCKED 
hudson.tasks.junit.TestResultAction.getResult(TestResultAction.java:135)

The stacktrace looked like this:

Handling GET /job/www/43365/ from x.x.x.x : RequestHandlerThread[#17] 
AbstractBuild/index.jelly AbstractTestResultAction/summary.jelly
hudson.tasks.junit.TestResultAction.getResult(TestResultAction.java:135)
hudson.tasks.junit.TestResultAction.getFailedTests(TestResultAction.java:186)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:606)
org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)
org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)
org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)
org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)
org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74)
org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134)
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41)
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38)
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98)
org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98)
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)
org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147)
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98)
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallySta

web UI hangs as app reads all old junitResult..xml files

[Kevin Goess]

The first time we click on a link to see a build, the web UI hangs for 
about ten minutes.  stracing the thread that's got 100% of the cpu shows 
that it's reading each one of the 500 junitResult.xml files:

...
open("/var/lib/jenkins/jobs/www/builds/42596/junitResult.xml", O_RDONLY) = 
382
open("/var/lib/jenkins/jobs/www/builds/42595/build.xml", O_RDONLY) = 382
...

Each junitResult.xml file is about 17MB and takes about a second to load, 
so the 500 files take almost ten minutes to load the page.

Any subsequent page loads for that particular build are immediate, and 
jenkins doesn't go troll all the old junitResult.xml files. In fact loading 
that build again even while the first one is still doing its thing is 
immediate.

We're running v1.613.  It seems like the change is recent-ish (last month 
or two?) but we can't tie it to any particular change.

Has anyone else seen this? Any idea what might be going on?

-- 
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/f05f84c1-1c30-4145-b6e7-050b114850bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins won't start

[Kevin Bond]

Hello, I just upgraded to 1.624 and now Jenkins won't start - it is stuck 
at "Please wait while Jenkins is getting ready to work" indefinitely. Here 
is a thread dump: https://gist.github.com/kbond/b673d053666c39233d6d

Can anyone help?

Thanks,
Kevin

-- 
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/8dfc5a23-d353-4648-9177-f8b2ba3134b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Disabling Jenkins Security

[Kevin Meredith]

When disabling security (via *Configure Global Security*), is it possible 
to enable a prompt, double-checking that the user wants to disable it?

If not, would it be reasonable to prompt the user, "Are you sure that you'd 
like to disable security?"


-- 
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/16ffc152-666e-456d-bbe0-c72d5b022377%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Triggers - Always, Send to Developers, An attempt to send e-mail to empty list of recipients ignored

[Kevin Navero]

Ok, this is weird..it's working now, but I don't really know what I did to 
fix it. The MailAddressResolver isn't case sensitive is it? I may have been 
modifying my git config user.email around as well as the email address in 
the Jenkins "people" list.

On Monday, June 8, 2015 at 8:16:48 PM UTC-7, slide wrote:
>
> email-ext does use the MailAddressResolver just like Mailer plugin, which 
> means it should be getting the information from the person's account in 
> Jenkins. I would need more information about your setup because it works 
> just fine for me.
>
> On Mon, Jun 8, 2015 at 7:43 PM Kevin Navero  > wrote:
>
>> I'm currently running into an issue where in my job configuration, the 
>> trigger is set to "Always" and will send an email to the developer of the 
>> last commit after the build is complete. In the logs I get:
>>
>> Email was triggered for: Always
>> Sending email for trigger: Always
>> An attempt to send an e-mail to empty list of recipients, ignored.
>>
>> After reading the wiki, I noticed it says,
>>
>> *Send to Developers * - Check this checkbox to send the email to anyone 
>> who checked in code for the last build.  The plugin will generate an email 
>> address based on the committer's id and an appended "default email suffix" 
>> from Jenkins's global configuration page.  For instance, if a change was 
>> committed by someone with an id "first.last", and the default email suffix 
>> is "@somewhere.com", then an email will be sent to "
>> first...@somewhere.com "
>>
>> So I tried to change my Jenkins username id to . and set the 
>> default email suffix to a valid email suffix. This still didn't work as I 
>> expected.
>>
>> When I use the built-in Jenkins email notifier, I successfully get 
>> emails, but only for cases where the build is unstable, and I want the 
>> developer who's changes are being tested to receive an email *all the 
>> time* after the build is finished. In the Jenkins "People" listing, each 
>> committer id is mapped to an email address; does Email Ext not get the 
>> email from that, the same way that the built-in Jenkins email notifier 
>> does? 
>>
>> Worst case scenario, I'll probably end up hacking with Perl and send in 
>> the committer email address into the build job as a parameter.
>>
>> -- 
>> 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/b7e37720-acdb-45d0-86bc-3604599a1acf%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/b7e37720-acdb-45d0-86bc-3604599a1acf%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> 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/743e4e70-822e-46fb-9fc2-5579767bcbd4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Triggers - Always, Send to Developers, An attempt to send e-mail to empty list of recipients ignored

[Kevin Navero]

Hm, if the email-ext gets the email information from a person's information 
in the "people" listings (Jenkins users and people mentioned in commit 
messages), then what's with the email generation algorithm mentioned in the 
wiki? Is that like a second fallback option to resolve the email address? 
>From my understanding, the email generation algorithm mentioned in the wiki 
is completely separate from the MailAddressResolver which checks the 
information in the person's account in Jenkins as you said. I could also be 
completely misinterpreting the doc maybe. 

On Monday, June 8, 2015 at 8:16:48 PM UTC-7, slide wrote:
>
> email-ext does use the MailAddressResolver just like Mailer plugin, which 
> means it should be getting the information from the person's account in 
> Jenkins. I would need more information about your setup because it works 
> just fine for me.
>
> On Mon, Jun 8, 2015 at 7:43 PM Kevin Navero  > wrote:
>
>> I'm currently running into an issue where in my job configuration, the 
>> trigger is set to "Always" and will send an email to the developer of the 
>> last commit after the build is complete. In the logs I get:
>>
>> Email was triggered for: Always
>> Sending email for trigger: Always
>> An attempt to send an e-mail to empty list of recipients, ignored.
>>
>> After reading the wiki, I noticed it says,
>>
>> *Send to Developers * - Check this checkbox to send the email to anyone 
>> who checked in code for the last build.  The plugin will generate an email 
>> address based on the committer's id and an appended "default email suffix" 
>> from Jenkins's global configuration page.  For instance, if a change was 
>> committed by someone with an id "first.last", and the default email suffix 
>> is "@somewhere.com", then an email will be sent to "
>> first...@somewhere.com "
>>
>> So I tried to change my Jenkins username id to . and set the 
>> default email suffix to a valid email suffix. This still didn't work as I 
>> expected.
>>
>> When I use the built-in Jenkins email notifier, I successfully get 
>> emails, but only for cases where the build is unstable, and I want the 
>> developer who's changes are being tested to receive an email *all the 
>> time* after the build is finished. In the Jenkins "People" listing, each 
>> committer id is mapped to an email address; does Email Ext not get the 
>> email from that, the same way that the built-in Jenkins email notifier 
>> does? 
>>
>> Worst case scenario, I'll probably end up hacking with Perl and send in 
>> the committer email address into the build job as a parameter.
>>
>> -- 
>> 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/b7e37720-acdb-45d0-86bc-3604599a1acf%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/b7e37720-acdb-45d0-86bc-3604599a1acf%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> 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/0f1f4a63-33ea-436b-9c7b-4ac4b6407a66%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Triggers - Always, Send to Developers, An attempt to send e-mail to empty list of recipients ignored

[Kevin Navero]

I'm on Windows 7 x64 Professional and `java -version` gives me:

java version "1.7.0_51"
Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)

I'm running Jenkins version 1.616, Email Ext is at version 2.40.4. Attached 
show the relevant job settings underneath "Editable Email Notifications" 
for Post-build Actions (job*.PNG), and the relevant system configuration 
settings underneath "Extended E-mail Notification" (sysconf*.PNG). Does 
anything seem weirdly off?

On Monday, June 8, 2015 at 8:16:48 PM UTC-7, slide wrote:
>
> email-ext does use the MailAddressResolver just like Mailer plugin, which 
> means it should be getting the information from the person's account in 
> Jenkins. I would need more information about your setup because it works 
> just fine for me.
>
> On Mon, Jun 8, 2015 at 7:43 PM Kevin Navero  > wrote:
>
>> I'm currently running into an issue where in my job configuration, the 
>> trigger is set to "Always" and will send an email to the developer of the 
>> last commit after the build is complete. In the logs I get:
>>
>> Email was triggered for: Always
>> Sending email for trigger: Always
>> An attempt to send an e-mail to empty list of recipients, ignored.
>>
>> After reading the wiki, I noticed it says,
>>
>> *Send to Developers * - Check this checkbox to send the email to anyone 
>> who checked in code for the last build.  The plugin will generate an email 
>> address based on the committer's id and an appended "default email suffix" 
>> from Jenkins's global configuration page.  For instance, if a change was 
>> committed by someone with an id "first.last", and the default email suffix 
>> is "@somewhere.com", then an email will be sent to "
>> first...@somewhere.com "
>>
>> So I tried to change my Jenkins username id to . and set the 
>> default email suffix to a valid email suffix. This still didn't work as I 
>> expected.
>>
>> When I use the built-in Jenkins email notifier, I successfully get 
>> emails, but only for cases where the build is unstable, and I want the 
>> developer who's changes are being tested to receive an email *all the 
>> time* after the build is finished. In the Jenkins "People" listing, each 
>> committer id is mapped to an email address; does Email Ext not get the 
>> email from that, the same way that the built-in Jenkins email notifier 
>> does? 
>>
>> Worst case scenario, I'll probably end up hacking with Perl and send in 
>> the committer email address into the build job as a parameter.
>>
>> -- 
>> 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/b7e37720-acdb-45d0-86bc-3604599a1acf%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/b7e37720-acdb-45d0-86bc-3604599a1acf%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> 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/b21fb7cf-660e-4c1e-8786-cd8b52048ef6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Triggers - Always, Send to Developers, An attempt to send e-mail to empty list of recipients ignored

[Kevin Navero]

I'm currently running into an issue where in my job configuration, the 
trigger is set to "Always" and will send an email to the developer of the 
last commit after the build is complete. In the logs I get:

Email was triggered for: Always
Sending email for trigger: Always
An attempt to send an e-mail to empty list of recipients, ignored.

After reading the wiki, I noticed it says,

*Send to Developers * - Check this checkbox to send the email to anyone who 
checked in code for the last build.  The plugin will generate an email 
address based on the committer's id and an appended "default email suffix" 
from Jenkins's global configuration page.  For instance, if a change was 
committed by someone with an id "first.last", and the default email suffix 
is "@somewhere.com", then an email will be sent to 
"first.l...@somewhere.com"

So I tried to change my Jenkins username id to . and set the 
default email suffix to a valid email suffix. This still didn't work as I 
expected.

When I use the built-in Jenkins email notifier, I successfully get emails, 
but only for cases where the build is unstable, and I want the developer 
who's changes are being tested to receive an email *all the time* after the 
build is finished. In the Jenkins "People" listing, each committer id is 
mapped to an email address; does Email Ext not get the email from that, the 
same way that the built-in Jenkins email notifier does? 

Worst case scenario, I'll probably end up hacking with Perl and send in the 
committer email address into the build job as a parameter.

-- 
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/b7e37720-acdb-45d0-86bc-3604599a1acf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Git + Email-ext + send email to developers + developers list empty

[Kevin Navero]

Hi, has this been resolved yet? I'm running into the same problem. 
According to the wiki, it seems like the "send to developers" option 
doesn't get the email addresses from the "people" listing, but rather it 
generates the email addresses dynamically by concatenating the user id with 
the default email suffix set in the system config? Why can't it just get 
the email addresses from the "people" listing similar to how the built-in 
email notification works?


On Thursday, September 25, 2014 at 9:28:53 AM UTC-7, Ramya Dhanapal wrote:
>
> Hi All, 
>
> I have the git plugin and email-ext plugin set up. I have a post-build 
> action trigger set up to send out email on 'Success' to the group '
> Developers'. 
>
> Jenkins: Jenkins 1.575 
> git plugin: 2.2.6 
> email-ext plugin:2.38.2 
>
> But, the list of Developers seems to be empty. 
>
> I get the below error: 
>
> 15:39:07 Email was triggered for: Success 
> 15:39:07 Sending email for trigger: Success 
> 15:39:07 An attempt to send an e-mail to empty list of recipients, 
> ignored. 
>
> Elsewhere I read if $changes is empty, the Developers would not be 
> populated. But I verified that $changes provides me all the changes since 
> the last build.
>
> Kindly help. 
>
> Regards, 
> Ramya 
>

-- 
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/e1024b8a-bbd0-4795-9a2a-9bb200e1577a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Publishing a single javadoc from a multiconfiguration/matrix job

[Kevin Moody]

Hi All,

So, this is a little bit weird, but we have a multi-language, 
multi-platform build.  It is run in Jenkins via one multi-configuration 
job, with 10 different configurations.  Unfortunately, some 
platform-independent pieces, such as jars and javadocs, are being built on 
every single configuration.  However, I would like to find a way to publish 
a single javadoc to the "main" build page.  I just verified that the 
"Publish Javadoc" post-build action does publish individual javadoc builds 
to their respective configuration's page.  But, I was hoping to get that 
extra visibility of having it on the main page.  Is there anything that I 
can do to make the javadoc and/or docLinks plugins understand a 
matrix/multi-configuration job and only create links on the main page?

Thanks in advance,
Kevin

-- 
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/daa5e1e3-c164-4434-8a53-ab0e1b1e2db0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [workflow plugin] is there a way to get workflow node steps to show in node history?

[Kevin]

OK great, I'll try out OnceRetentionStrategy too thanks.

The cloud we use isn't anything that's open sourced at present, just a 
little plugin I whipped up for our in house virtualization infrastructure. 
 Can't really say to much more than that at present, but I hope to have a 
whitepaper on our infrastructure sometime this half-year so I should be 
able to share much more then.

Anyways, neat stuff, keep up the good work!

On Thursday, January 8, 2015 at 12:46:11 PM UTC-5, Jesse Glick wrote:
>
> On Tuesday, December 16, 2014 10:39:22 PM UTC-5, Kevin wrote:
>>
>> Seems like swapping my RunListener out for an ExecutorListener would 
>> work fine for this use case.
>>
>
> That would help, though it does not handle flows crossing Jenkins 
> restarts. You are advised to use OnceRetentionStrategy from 
> durable-task-plugin for this purpose, or otherwise check for 
> ContinuableExecutable from an existing retention strategy.
>
> Out of curiosity, which cloud is this? It would be nice to update 
> workflow-plugin/COMPATIBILITY.md with a link to any related issue marked 
> with the ‘workflow’ label.
>

-- 
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/bddb9451-79dd-4e52-960e-ede78de29272%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [workflow plugin] is there a way to get workflow node steps to show in node history?

[Kevin Browder]

Basically I'm trying to replace a bunch of jobs that are in one-shot vms
(that get removed after a while with a RetentionStrategy and get taken
offline after a single run with a RunListener) and combine them into a
single workflow, ideally the same behavior would apply.

Seems like swapping my RunListener out for an ExecutorListener would work
fine for this use case.

On Tuesday, December 16, 2014, Kohsuke Kawaguchi  wrote:

> I'm not sure if I understand the question.
>
> I guess you want to know what has run on a given hudson.model.Node? When
> the only things that run on Node was hudson.model.Run, RunListener was
> sufficient to keep track of this, but with workflow, we are running
> PlaceholderTask on Executor, and there's currently no Listener to get
> notified for that?
>
> Would ExecutorListener of some use? Or am I missing the question?
>
>
> 2014-12-16 7:00 GMT-08:00 Kevin  >:
>>
>> Actually now that I look a things more closely it looks like the actual
>> node-steps don't call RunListeners either, is it possible to have the "one
>> shot" slave behavior in a workflow?  If so how?
>>
>> On Monday, December 15, 2014 4:39:53 PM UTC-5, Kevin wrote:
>>>
>>> Title says it all, is there a way to get workflow node steps to show in
>>> node history?  At least for me the node steps in the CPS DSL don't appear
>>> to do this.
>>>
>>> I've got a one-shot cloud provider that inspects history as a last
>>> resort (with a RetentionStrategy) in case a RunListener isn't called,
>>> additionally it would be nice if history showed these steps anyways imho.
>>>
>>  --
>> 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/83d5b6aa-78d5-49a2-9f66-9d3cf46ccc94%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/83d5b6aa-78d5-49a2-9f66-9d3cf46ccc94%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> Kohsuke Kawaguchi
>
> --
> 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/yJ4fxgHNRf4/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/CAN4CQ4x_XSL1S3WFF_iNEH9b9tuxZ3hEAsrSQXRQZvPn%2BZu_7A%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAN4CQ4x_XSL1S3WFF_iNEH9b9tuxZ3hEAsrSQXRQZvPn%2BZu_7A%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> 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/CAMqyT3Yex5PaqF0Wk_1cv1A6uJTpqWbQwwiPKW_07Z%2BNXZj0qg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [workflow plugin] is there a way to get workflow node steps to show in node history?

[Kevin]

Actually now that I look a things more closely it looks like the actual 
node-steps don't call RunListeners either, is it possible to have the "one 
shot" slave behavior in a workflow?  If so how?

On Monday, December 15, 2014 4:39:53 PM UTC-5, Kevin wrote:
>
> Title says it all, is there a way to get workflow node steps to show in 
> node history?  At least for me the node steps in the CPS DSL don't appear 
> to do this.
>
> I've got a one-shot cloud provider that inspects history as a last resort 
> (with a RetentionStrategy) in case a RunListener isn't called, additionally 
> it would be nice if history showed these steps anyways imho.
>

-- 
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/83d5b6aa-78d5-49a2-9f66-9d3cf46ccc94%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[workflow plugin] is there a way to get workflow node steps to show in node history?

[Kevin]

Title says it all, is there a way to get workflow node steps to show in 
node history?  At least for me the node steps in the CPS DSL don't appear 
to do this.

I've got a one-shot cloud provider that inspects history as a last resort 
(with a RetentionStrategy) in case a RunListener isn't called, additionally 
it would be nice if history showed these steps anyways imho.

-- 
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/03d1e212-0730-4949-baaa-d86697ab76cf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Can single Jenkins slave serve multiple Jenkins masters?

[Kevin]

Also, when start 2nd slave, do we suppose to see two "Jenkins Slave" items 
on windows service list?

Kevin 

On Wednesday, 16 July 2014 11:55:36 UTC-4, SA Evans wrote:
>
> What you'd need to do is set up multiple agents on the slave node, one 
> agent for each Jenkins master.  You would also need to set up independent 
> workspaces for each agent as well.  This is assuming that your test 
> hardware can handle more than one job at a time.  We do this a lot and it 
> works fine, assuming that multiple slave jobs can run simultaneously 
> without conflict.  
>
> Scott
>
>
> On Wed, Jul 16, 2014 at 10:51 AM, Kevin > 
> wrote:
>
>> Hi, all:
>>
>> I have two Jenkins masters trying to run a test, and that test resides in 
>> single computer which is hooked up with test hardware set.
>>
>> My question is: 
>> Can I turn that computer (which is connected to test hardware) into a 
>> Jenkins slave so that both Jenkins master can run test when needed?
>>
>> Thanks!
>>
>> Kevin
>>
>>
>>  -- 
>> 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 .
>> 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.
For more options, visit https://groups.google.com/d/optout.

Re: Can single Jenkins slave serve multiple Jenkins masters?

[Kevin]

Hi, Scott:

Thanks for the answer!

With the first slave running, I setup a different workspace for 2nd slave, 
and try to launch 2nd slave. It seems work, but when I click "File"--> 
"Install as a service" on this following window:



It fails and never returns. All I see is a circle rolling in this window 
and never stops. If I close this window, the master Jenkins will report 
this slave goes offline.

Anything I should check to fix this issue?

Thanks!

Kevin

On Wednesday, 16 July 2014 11:55:36 UTC-4, SA Evans wrote:
>
> What you'd need to do is set up multiple agents on the slave node, one 
> agent for each Jenkins master.  You would also need to set up independent 
> workspaces for each agent as well.  This is assuming that your test 
> hardware can handle more than one job at a time.  We do this a lot and it 
> works fine, assuming that multiple slave jobs can run simultaneously 
> without conflict.  
>
> Scott
>
>
> On Wed, Jul 16, 2014 at 10:51 AM, Kevin > 
> wrote:
>
>> Hi, all:
>>
>> I have two Jenkins masters trying to run a test, and that test resides in 
>> single computer which is hooked up with test hardware set.
>>
>> My question is: 
>> Can I turn that computer (which is connected to test hardware) into a 
>> Jenkins slave so that both Jenkins master can run test when needed?
>>
>> Thanks!
>>
>> Kevin
>>
>>
>>  -- 
>> 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 .
>> 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.
For more options, visit https://groups.google.com/d/optout.

Can single Jenkins slave serve multiple Jenkins masters?

[Kevin]

Hi, all:

I have two Jenkins masters trying to run a test, and that test resides in 
single computer which is hooked up with test hardware set.

My question is: 
Can I turn that computer (which is connected to test hardware) into a 
Jenkins slave so that both Jenkins master can run test when needed?

Thanks!

Kevin


-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: using Jenkins credential store with CVS plugin?

[Kevin Buchs]

Here is the "correct" answer - the plugin has its own global credential 
store.
http://stackoverflow.com/questions/23940354/how-to-use-jenkins-credential-store-when-accessing-cvs/24340501#24340501


-- 
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.
For more options, visit https://groups.google.com/d/optout.

Is there a text/json/parsable form of http://mirrors.jenkins-ci.org/status.html

[Kevin]

I'm behind a proxied firewall and want to allow all the mirrors via 
scripting without trolling through HTML.  Is the mirror list somewhere on 
github perhaps?
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.
For more options, visit https://groups.google.com/d/optout.

using Jenkins credential store with CVS plugin?

[Kevin Buchs]

Is there a way to use the credential store with the CVS plugin to access a 
CVS repository? Looking for a way to store credential once and have one 
place to change it, despite many jobs making use of it.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re:Jenkins can't connect to a Git server via SSH using username/password

[Kevin Fleming (BLOOMBERG/ 731 LEXIN)]

If you are using one of the recent Git plugins, you'll have to put your 
credentials in the Credentials area in Jenkins, not in the URL itself.

- Original Message -
From: jenkinsci-users@googlegroups.com
To: jenkinsci-users@googlegroups.com
At: May  7 2014 12:25:38


We are trying to connect to a Git repository via SSH (not Github) using 
username/password (we're not using keys)  and the Git plugin but we're getting 
the following error:
Failed to connect to repository : Command "git ls-remote -h 
ssh://account@repository/path/toApplication HEAD" returned status code 128:
stdout: 
stderr: Permission denied, please try again. 
Permission denied, please try again. 
Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). 
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
--
If we use the anonymous access or change the access type from SSH to HTTPS, it 
works fine, but we should be able to use the SSH with user/password without 
having to add the public/private keys.
Aleyda
-- 
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.
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.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins slave appear offline - SSHLauncher threads BLOCKED

[Kevin Fleming (BLOOMBERG/ 731 LEXIN)]

Unfortunately it's not possible to reconnect to an SSH session; if the session 
is disconnected, the SSH daemon on the receiving end will close its end, and 
kill any processes that had been launched by that connection. In other words, 
any job that was running will be lost.

- Original Message -
From: jenkinsci-users@googlegroups.com
To: jenkinsci-users@googlegroups.com
At: May  5 2014 17:19:46

Hello Stephen,

Thank you for the informative reply. I look forward to your blog post!

To answer your question, we have approximately 2 dozen standard ssh Linux 
slaves, and about 10 JNLP Windows slaves to support various 
platform/configurations.

Based on the build history, sometimes we have up to 10 jobs running 
concurrently. Not 24x7, approximately once every 2 hours, and queue is pretty 
much empty most of the time. I would qualify the system as light traffic.

>From your reply, I am even more concerned with disproportionally high number 
>of the blocked threads (120) compare to offline slaves (2 at the time), as it 
>sounds like it should be closer to 1:1? Also, do you know if the standard ssh 
>connector performs a timeout and reconnect or does it block indefinitely? Not 
>sure if each attempt to reconnect is spawning off new blocked threads?!

Let me know if there is any other information which could prove to be useful.

Charles

On Monday, May 5, 2014 12:42:23 PM UTC-7, Stephen Connolly wrote:

How many slaves do you have?

It is rather easy to saturate a server with a small number of ssh-slaves based 
slaves.

For example, on an AWS m3.large class machine, 10 ssh-slaves concurrently 
building jobs as chatty as the mock-load-builder job type is the most you can 
push.

If you use JNLP slaves, you can get close to 60 concurrent builds before the 
system starts falling over.

The CloudBees NIO ssh-slaves plugin (part if the enterprise offering) has a 
different performance characteristic... My most recent tests I was able to get 
up to 120 concurrent builds, without affecting the Jenkins UI (I only had set 
up for that number of slaves... It likely can go further, though m3.large is 
not beefy enough) what was affected though we're build times. The builds were 
2-3 times slower due to back-pressure effects causing the builds to block on 
STDOUT.

If anyone else is interested, we will be releasing our scalability test harness 
(actually I will be ripping the bottom out of the acceptance test framework and 
putting the scalability harness in its place... But the harness is also useful 
for scalability testing). We will also be publishing our findings.

The other thing to watch is how your entropy pool is holding up. The default 
random source in Linux typically gets exhausted quite quickly. That can cause 
your ssh slaves to fail ping tests and timeout/block

I think the package you want to install is haveged

That or switch java to /dev/urandom

Note: I am currently not recommending any specific slave connector, there are 
trade-offs with each type of connector. I will be writing up a blog post in the 
near future discussing the various trade-offs.

Standard ssh-slaves degrades poorly... This is great if you want to know when 
you have reached your limit

NIO ssh-slaves degrades gracefully, I need to determine where it starts 
degrading relative to standard ssh-slaves, but if UI responsiveness is more 
important than build times then this has advantages (though you need to be a 
paying cloudbees customer)

JNLP scales the highest without affecting build times, but degrades fastest, is 
a poor fit for on-demand connection/retention strategies and does not offer the 
same transport encryption security as the ssh- versions

Those are just the brief high-level measures

On Monday, 5 May 2014, Charles Chan  wrote:

Hello,

One of the issue we have recently been experiencing with Jenkins is that the 
slaves (node) would go offline for no apparent reason and would not reconnect 
automatically.
When slaves appear as offline, we tried to launch/reconnect the slave manually 
but it does not work either. However, we are able to SSH into the machine using 
PuTTy.
The only workaround is to restart the Jenkins server, until the problem 
surfaces again. (Typically in a week.)

Instance Information

Jenkins Server:1.562
SSH Credentials Plugin:1.6.1
SSH Slaves Plugin  1.6

Thread dump of slave node:
{dump}
"Channel reader thread: qa-linbuild-02" prio=5 WAITING 
java.lang.Object.wait(Native Method) 
java.lang.Object.wait(Object.java:485) 
com.trilead.ssh2.channel.ChannelManager.waitUntilChannelOpen(ChannelManager.java:109)
 
com.trilead.ssh2.channel.ChannelManager.openSessionChannel(ChannelManager.java:583)
 com.trilead.ssh2.Session.(Session.java:41) 
com.trilead.ssh2.Connection.openSession(Connection.java:1129) 
com.trilead.ssh2.SFTPv3Client.(SFTPv3Client.java:99) 
com.trilead.ssh2.SFTPv3Client.(SFTPv3Client.

Re: maven plugin - how to obtain the jenkins user name

[Kevin Fleming (BLOOMBERG/ 731 LEXIN)]

Then you do mean the user who initiated the job; note that this does not 
necessarily mean a user who was logged in, as jobs can be started by 
'anonymous' (from an SCM trigger for example), or via the API.

The Build object itself should have a record of the user who initiated it, 
there's no need to talk to the Jenkins/Hudson objects to see who is logged in, 
and in fact that would not work in a build step anyway because they don't run 
in the same environment.

- Original Message -
From: jenkinsci-users@googlegroups.com
To: jenkinsci-users@googlegroups.com
Cc: Kevin Fleming (BLOOMBERG/ 731 LEXIN)
At: May  5 2014 15:27:54

I mean the user that is logged on jenkins and started a jenkins job that in the 
build step refers a pom.xml that declares this plugin. 


Em segunda-feira, 5 de maio de 2014 14h21min39s UTC-3, Kevin Fleming  escreveu:
What do you mean by 'running'? Does this plugin provide a build step, a 
publisher, or something else? If it provides something that is used during a 
build, then you want the user who initiated the build.

- Original Message -
From: jenkins...@googlegroups.com
To: jenkins...@googlegroups.com
Cc: bma...@batmat.net
At: May  5 2014 12:49:10

I'd like to log who is running this maven plugin.  
I thought I could access the jenkins user from a simple maven plugin running on 
jenkins.. I'm afraid I'll have to build (or extend) a jenkins plugin to achieve 
that. 

Regards. Mauro. 

Em sábado, 3 de maio de 2014 12h04min32s UTC-3, Baptiste Mathus  escreveu:

Well, no indeed. Maven is an independent project and generally runs out of 
Jenkins.
Maybe you should explain a bit more what you are trying to achieve.
Cheers
Le 1 mai 2014 00:50, "Mauro Flores"  a écrit :

Maybe I haven't expressed myself correctly. 


I get a ClassNotFound exception for hudson.model.User. 

Does a maven plugin (not a jenkins plugin) has access to jenkins classpath ? 

Regards. Mauro Flores. 

Em terça-feira, 29 de abril de 2014 18h29min31s UTC-3, Mauro Flores  escreveu:
Thanks. Michael. 

A complementary question. 

Do I have to add the jar of this class "hudson.model.User" to my maven plugin 
jar? Or the classpath of jenkins is visible to the execution of my maven plugin?
If I have to add, can you help how to define the dependency. 
If I do like below I lot of jars are brought. 


org.jenkins-ci.main
jenkins-core
1.543



Em sábado, 26 de abril de 2014 11h59min44s UTC-3, Michael Clarke  escreveu:
Use User.current()


On 25 April 2014 23:17, Mauro Flores  wrote:
 
Hello, 

I'm building a maven plugin. 
I'd like to access the name of the user logged on jenkins inside the maven 
plugin. 

Regards. Mauro. 


 -- 
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.
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-use...@googlegroups.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-use...@googlegroups.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.
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.
For more options, visit https://groups.google.com/d/optout.

Re: maven plugin - how to obtain the jenkins user name

[Kevin Fleming (BLOOMBERG/ 731 LEXIN)]

What do you mean by 'running'? Does this plugin provide a build step, a 
publisher, or something else? If it provides something that is used during a 
build, then you want the user who initiated the build.

- Original Message -
From: jenkinsci-users@googlegroups.com
To: jenkinsci-users@googlegroups.com
Cc: bmat...@batmat.net
At: May  5 2014 12:49:10

I'd like to log who is running this maven plugin.  
I thought I could access the jenkins user from a simple maven plugin running on 
jenkins.. I'm afraid I'll have to build (or extend) a jenkins plugin to achieve 
that. 

Regards. Mauro. 

Em sábado, 3 de maio de 2014 12h04min32s UTC-3, Baptiste Mathus  escreveu:

Well, no indeed. Maven is an independent project and generally runs out of 
Jenkins.
Maybe you should explain a bit more what you are trying to achieve.
Cheers
Le 1 mai 2014 00:50, "Mauro Flores"  a écrit :

Maybe I haven't expressed myself correctly. 


I get a ClassNotFound exception for hudson.model.User. 

Does a maven plugin (not a jenkins plugin) has access to jenkins classpath ? 

Regards. Mauro Flores. 

Em terça-feira, 29 de abril de 2014 18h29min31s UTC-3, Mauro Flores  escreveu:
Thanks. Michael. 

A complementary question. 

Do I have to add the jar of this class "hudson.model.User" to my maven plugin 
jar? Or the classpath of jenkins is visible to the execution of my maven plugin?
If I have to add, can you help how to define the dependency. 
If I do like below I lot of jars are brought. 


org.jenkins-ci.main
jenkins-core
1.543



Em sábado, 26 de abril de 2014 11h59min44s UTC-3, Michael Clarke  escreveu:
Use User.current()


On 25 April 2014 23:17, Mauro Flores  wrote:
 
Hello, 

I'm building a maven plugin. 
I'd like to access the name of the user logged on jenkins inside the maven 
plugin. 

Regards. Mauro. 


 -- 
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.
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-use...@googlegroups.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.
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.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins doesn't care that needed JDK is not configured on slave

[Kevin Fleming (BLOOMBERG/ 731 LEXIN)]

Well, this requires that the slave be accessible, which would not be true for 
cloud slaves that are spawned on demand :-)

It's an interesting idea, but there would need to be some sort of 'mapping' 
mechanism to take the raw strings from the slave's environment and turn them 
into suitable labels. Note also that most of this information is not really in 
'environment variables' on the slave, but is extractable through various tools.

- Original Message -
From: jenkinsci-users@googlegroups.com
To: jenkinsci-users@googlegroups.com
At: Apr 29 2014 11:43:30

Maybe this exists but I missed it, but I also wonder if there is a way to 
inject system environment variables on any node (master/slaves) so that things 
like OS name/family, architecture, OS distribution (e.g., 'Ubuntu 14.04 LTS'), 
etc. could be already available.
 
Seems redundant to have to manually specify labels that are inherent to the 
slave environment.


On Tue, Apr 29, 2014 at 7:40 AM, Kevin Fleming (BLOOMBERG/ 731 LEXIN) 
 wrote:
 
You are correct, the decision logic for choosing slaves only takes labels into 
account, it does not match up JDK requirements. You'll have to put the 
appropriate labels on your slaves as well.

Rather than modifying the decision logic, though, a way to solve this problem 
would be for the configuration code that manages the list of installed JDKs on 
a slave to have an option to inject labels automatically into the slave's list 
of labels based on the installed JDKs. That would allow the normal label-based 
decision logic to work, but would eliminate the duplicate data entry (and the 
opportunity for mistakes).


- Original Message -
From: jenkinsci-users@googlegroups.com

To: jenkinsci-users@googlegroups.com
At: Apr 29 2014 07:51:24

As we need a lot of manually installed tools, we decided to have strictly 
separated slaves and provide rather lots of labels to get each project built on 
the right slave.
This works really good so far. Now we thought we could spare at least the label 
for the JDK, as Jenkins in a sense has all needed information to pick the right 
slave for a needed JDK:
* All used JDKs are provided in the Jenkins core configuration, and all of them 
are marked as "do not install automatically".
* Each project has the "Used JDK" set to a particular JDK.
* Each node has a list of all manually installed JDKs.
Hence, if Jenkins needs to pick a Slave from the list of possible nodes, it can 
"see" which of those have the needed JDK for a particular project installed.
Unfortunately it does not. In fact, it picks just ANY, even one that has not 
the needed JDK installed.

Certainly this can be easily worked around by using another label for the JDK, 
but we think this is redenundant information. If Jenkins can auto-install a 
missing JDK, why can't it in turn not simply use a different slave if the JDK 
is missing for those not wanting to use auto-install? 
 -- 
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.
 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.
For more options, visit https://groups.google.com/d/optout.


-- 
Jeff Vincent
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent-- 
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.
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.
For more options, visit https://groups.google.com/d/optout.

Re:Jenkins doesn't care that needed JDK is not configured on slave

[Kevin Fleming (BLOOMBERG/ 731 LEXIN)]

You are correct, the decision logic for choosing slaves only takes labels into 
account, it does not match up JDK requirements. You'll have to put the 
appropriate labels on your slaves as well.

Rather than modifying the decision logic, though, a way to solve this problem 
would be for the configuration code that manages the list of installed JDKs on 
a slave to have an option to inject labels automatically into the slave's list 
of labels based on the installed JDKs. That would allow the normal label-based 
decision logic to work, but would eliminate the duplicate data entry (and the 
opportunity for mistakes).

- Original Message -
From: jenkinsci-users@googlegroups.com
To: jenkinsci-users@googlegroups.com
At: Apr 29 2014 07:51:24

As we need a lot of manually installed tools, we decided to have strictly 
separated slaves and provide rather lots of labels to get each project built on 
the right slave.
This works really good so far. Now we thought we could spare at least the label 
for the JDK, as Jenkins in a sense has all needed information to pick the right 
slave for a needed JDK:
* All used JDKs are provided in the Jenkins core configuration, and all of them 
are marked as "do not install automatically".
* Each project has the "Used JDK" set to a particular JDK.
* Each node has a list of all manually installed JDKs.
Hence, if Jenkins needs to pick a Slave from the list of possible nodes, it can 
"see" which of those have the needed JDK for a particular project installed.
Unfortunately it does not. In fact, it picks just ANY, even one that has not 
the needed JDK installed.

Certainly this can be easily worked around by using another label for the JDK, 
but we think this is redenundant information. If Jenkins can auto-install a 
missing JDK, why can't it in turn not simply use a different slave if the JDK 
is missing for those not wanting to use auto-install? 
-- 
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.
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.
For more options, visit https://groups.google.com/d/optout.

Re:[SOLVED] Apache SSL Proxy Jenkins

[Kevin Fleming (BLOOMBERG/ 731 LEXIN)]

Interesting! Thanks for the report, I'll have to experiment with this when I 
bring my Jenkins back up.

Is the AllowEncodedSlashes issue also present in Apache HTTPD 2.2.x, or just 
2.4.x?

- Original Message -
From: jenkinsci-users@googlegroups.com
To: jenkinsci-users@googlegroups.com
At: Apr 28 2014 00:54:41

After some effort, I finally got Apache with an SSL connection to correctly 
proxy to Jenkins at localhost:8080/jenkins. There were two issues:

(1) The AllowEncodedSlashes setting is not inherited by virtual hosts, and 
virtual hosts are used in many default Apache configurations, such as the one 
in Ubuntu. The workaround is to add the AllowEncodedSlashes setting inside a 
VirtualHost container (/etc/apache2/sites-available/default in Ubuntu). ( this 
text was copied from here: 
http://stackoverflow.com/questions/4390436/need-to-allow-encoded-slashes-on-apache
 ). An Apache bug (#46830) was opened and fixed. However, it is still an issue 
in Apache 2.4.7 on Ubuntu.

When only declared globally, Jenkins reports that the reverse proxy setup is 
broken. It might be worth mentioning this as a possible cause here: 
https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+says+my+reverse+proxy+setup+is+broken

(2) Some pages returned absolute links (e.g., 
"http://localhost:8080/jenkins/..."; ) rather than relative links. Specifically, 
go to Jenkins' "People" page and select a user. The user's icon is broken. To 
fix this, I added an output filter that made any absolute links relative.

I haven't actually add jobs yet. But, hopefully, someone will find this 
information useful :)

-- Scott

Here's my final Apache configuration file:

# The following directive is not inherited by virtual hosts and *must* 
additionally be copied to each virtual host declaration
AllowEncodedSlashes NoDecode

# Jenkins must be configured with prefix "/jenkins" and port 8080
http://localhost:8080/jenkins*>
Order deny,allow
Allow from all


ProxyPass http://localhost:8080/jenkins nocanon
ProxyPassReverse http://localhost:8080/jenkins
Header edit Location ^http://([^/]+)/jenkins https://$1/jenkins

# This fixes absolute links to http://localhost:8080/jenkins
AddOutputFilterByType INFLATE;SUBSTITUTE;DEFLATE text/html
Substitute "s|http://localhost:8080/|/|n"

Order deny,allow
Allow from all
Require all granted


-- 
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.
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.
For more options, visit https://groups.google.com/d/optout.

Re:Amazon EC2 plugin does not resume stopped instances

[Kevin Fleming (BLOOMBERG/ 731 LEXIN)]

You already posted this question and people have been responding to you. Why 
did you start a new thread with the same question?

- Original Message -
From: jenkinsci-users@googlegroups.com
To: jenkinsci-users@googlegroups.com
At: Apr 28 2014 11:07:01

As per description, the Amazon EC2 allows to set slaves to be stopped rather
than terminated so their state is preserved and can be reused.

Unfortunately that does not seem to work at all.

Once my On Demand node is stopped (either manually or due to idle timeout),
subsequent build start creates completely new instance based on selected
AMI.
However, if I launch the node manually via Manage Nodes, instance on EC2
will be resumed and subsequent build start will reuse this instance instead
of creating new one.

Is it somehow possible to configure Jenkins to resume instances on EC2
automatically?


--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/Amazon-EC2-plugin-does-not-resume-stopped-instances-tp4700115.html
Sent from the Jenkins users mailing list archive at Nabble.com.

-- 
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.
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.
For more options, visit https://groups.google.com/d/optout.

Re:CppCheck plugin configuration for multiple targets

[Kevin Fleming (BLOOMBERG/ 731 LEXIN)]

Most of the Jenkins publishers (test results, warnings, etc.) assume that the 
project builds a single target, so you will have trouble if you build multiple 
targets in a single project. Even though you have a large number of targets, it 
may be better to have separate projects for each one (you can use templating 
plugins to manage the proliferation of projects with nearly identical settings).

- Original Message -
From: jenkinsci-users@googlegroups.com
To: jenkinsci-users@googlegroups.com
At: Apr 25 2014 05:32:03

  
Hi All,

I've got a jenkins job that builds around 30 targets. As part of the build, 
cppcheck gets executed over the source of each target and I end up with one xml 
file per target. A jenkins post build action publishes the cppcheck reports.

There are two issue I have:
1. Since all the reported issues are combined into a single table by the 
CppCheck plugin, it isn't clear which target has the issue. A source file can 
be shared by multiple targets but the targets have different build 
configurations.
2. Some existing issues are simultaneous reported as fixed and unchanged in the 
CppCheck Result details table. This is not due to differences in build 
configurations. I suspect this is due to the way the xml reports are combined 
and compared with previous results? If an existing issue is reported as 
unchanged n times, it also get reported as solved n-1 times.

So I feel I'm probably not using the CppCheck as intended. Does anyone have a 
better suggestion for how I should manage running cppcheck over multiple 
targets and reporting the results?

Regards
Mavik


-- 
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.
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.
For more options, visit https://groups.google.com/d/optout.

Re:qemu nodes are very slow in jenkins

[Kevin Fleming (BLOOMBERG/ 731 LEXIN)]

Are you saying that you can run two qemu 'nodes' without Jenkins and your 
system performs well?

It's not surprising that starting up two virtual machines on your computer 
makes it run slower; you have given it more work to do!

- Original Message -
From: jenkinsci-users@googlegroups.com
To: jenkinsci-users@googlegroups.com
At: Apr 21 2014 02:42:49

Hi all,
I'm on fedora 20. In my jenkins when I pressed build two qemu node should boot 
with vyatta image. But they are too slowly. The cpu usage is also very high 
when qemu is start.

Cpu(s): 75.7%
qemu-system:40%
dynamips:42%
I enable qemu-kvm as below:
In etc/default/grub : at the end of line 'GRUB_CMDLINE_LINUX' I add 
kvm-intel.nested=1


# grub2-mkconfig -o /boot/grub2/grub.cfg
reboot

But the problem is still remain.

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.
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.
For more options, visit https://groups.google.com/d/optout.

Re: SCM Sync Configuration plugin exception

[Kevin Fleming (BLOOMBERG/ 731 LEXIN)]

The SCMSync plugin may not have been upgraded to support usage of the 
Credentials plugin yet.

- Original Message -
From: jenkinsci-users@googlegroups.com
To: jenkinsci-users@googlegroups.com
At: Apr 14 2014 14:29:26

I just noticed that  
https://wiki.jenkins-ci.org/display/JENKINS/ScmSyncConfig+Troubleshootings
says that my hudson.scm.SubversionSCM.xml file should contain the SVN 
credentials.

The contents of this file is included below and doesn't contain any credentials.
SVN credentials are set under Jenkins / Credentials.
All of our jobs are using SVN and everything works except the SCM Sync plugin.

Please help.

Thank you,
Igor.




  125
  false
  100
  false
  false



On Monday, April 14, 2014 1:07:04 PM UTC-4, Igor Berger wrote:
Hello,

SCM Sync Configuration plugin used to work great until a couple of months ago.

Since then, it doesn't sync. I see an "ERROR" in Manage Jenkins / Configure 
System screen.
When I click on it, I see a callstack. Below is the same call stack from 
jenkins.err.log.

I tried reinstalling SCM Sync, but the problem persists. :(

Creating a test job according to 
https://wiki.jenkins-ci.org/display/JENKINS/ScmSyncConfig+Troubleshootings
worked without any problems. Any ideas?

I'm running:
Jenkins 1532.3 LTS
SCM Sync Configuration Plugin 0.0.7.4.
Credentials Plugin  1.10.
Windows Server 2008 R2 64-bit

Thanks,
Igor.


Apr 14, 2014 11:41:18 AM winstone.Logger logInternal
SEVERE: Error while serving 
http://myjenkins:8080/plugin/scm-sync-configuration/descriptorForSCM/hudson.plugins.scm_sync_configuration.scms.ScmSyncSubversionSCM/checkRemote
java.lang.reflect.InvocationTargetException
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
 at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
  at 
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
   at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120)
 at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
  at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
 at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)
 at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
  at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
 at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)
 at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
  at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
 at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631)
at org.kohsuke.stapler.Stapler.service(Stapler.java:225)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
   at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
 at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
   at 
hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46)
  at 
hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103)
  at 
hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
   at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
  at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
 at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
 at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
 at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
 at 
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
 at 
jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
 at 
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)