Re: Jenkins crashing java.exe when run on my windows 7 box.

[Dorcus Malorcus]

I had a similar issue with Tomcat running Jenkins.  I was able to get 
around it with these Java options: 

-Xms64m -Xmx256m 

But I also downgraded to Java 6.   YMMV. 

Dave

>
>

-- 
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/groups/opt_out.

Re: Jenkins vs. EBCDIC

[Dorcus Malorcus]

I agree. I just found the iconv utility.  I run this as the last steps in 
my shell script on any artifacts I want brought back to Jenkins.  This 
worked beautifully! 

Using Jenkins with z/OS opens up a lot of possibilities! 



>
>

-- 
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/groups/opt_out.

Re: Jenkins vs. EBCDIC

[Kevin Fleming (BLOOMBERG/ 731 LEXIN)]

It doesn't seem practical for build artifacts to have their encodings changed 
automatically; doing so would require that the Jenkins slave code somehow be 
told which files are safe to convert and which are not. The log is a different 
situation, of course; that would be safe to convert (and to do so on the fly).

- Original Message -
From: jenkinsci-users@googlegroups.com
To: jenkinsci-users@googlegroups.com
At: Nov 22 2013 16:50:04

Any updates on this?  I'm in the same boat.  The slave.jar connects just fine 
with no special encoding, but any artifacts created on z/OS USS side come back 
to the Jenkins server as EBCDIC and so does the log file found on the server 
(even though it won't display on the web page). 

Thanks! 
Dave (dorcus)


-- 
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/groups/opt_out.

-- 
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/groups/opt_out.

Re: Jenkins vs. EBCDIC

[Dorcus Malorcus]

Any updates on this?  I'm in the same boat.  The slave.jar connects just 
fine with no special encoding, but any artifacts created on z/OS USS side 
come back to the Jenkins server as EBCDIC and so does the log file found on 
the server (even though it won't display on the web page). 

Thanks! 
Dave (dorcus)

>
>

-- 
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/groups/opt_out.

Re: Attempting to run a Jenkins slave on OS/390 / ASCII vs. EBCDIC encoding issues / blank console log

[Dorcus Malorcus]

Hi jay, 

I'm wondering if you ever got a reply to this, or figured out a way to do 
this.  I'm in the exact same boat.  The slave-agent starts just fine and 
the Jenkins server can see all the good Node Statistics -- but I don't get 
a console log and I create a log.txt as an artifact with commands like:  

set >> log.txt 

When I look at the log.txt artifact, it's all in EBCDIC (I assume).  I 
would love to see the console log and the artifacts because I think there's 
a lot of good things to do with the USS side of z/OS in respect to Jenkins. 

Dave

-- 
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/groups/opt_out.

Re: Move existing jobs into folders

[Eric Wood]

Found how to do it under the advance tab on Manage Plugin, Initially it failed, 
but when I restarted jenkins it tells me I have 3.15 installed and 4.0 is 
available.





On , Eric Wood  wrote:
 
Daniel:

I have never performed such an operation.  I have installed the "Free" plugins, 
registered with cloudbee and downloaded the 3.15 version.  How do I:
"upload it to Jenkins via the update center"?




On Friday, November 22, 2013 1:36 PM, Daniel Beck  wrote:
 
On 22.11.2013, at 19:18, Eric Wood  wrote:

> How do you gain access to the "closed-source" version.  Is this part of the 
> CloudBees Free Enterprise Plugins?

Apparently, not anymore. It already includes Folders 4 when I tried it on a 
Jenkins 1.532.1-rc. But you can install that, wait until Jenkins is restarted, 
register, manually download Folders 3.15 from 
http://jenkins-updates.cloudbees.com/download/plugins/cloudbees-folder/ and 
upload it to Jenkins via the update center, and restart Jenkins again. It 
worked like a charm for me without any existing folders. If you have existing 
folders, I'd try it on a throwaway instance first to see what happens to these 
folders.

You'll also probably want to disable or remove the other (annoying) plugins 
that come with the bundle.


-- 
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/groups/opt_out.

-- 
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/groups/opt_out.

Re: Move existing jobs into folders

[Daniel Beck]

On 22.11.2013, at 20:07, Eric Wood  wrote:

> "upload it to Jenkins via the update center"?

Go to http://yourjenkins/pluginManager/advanced and scroll down to 'Upload 
Plugin'.

-- 
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/groups/opt_out.

Re: Move existing jobs into folders

[Eric Wood]

Daniel:

I have never performed such an operation.  I have installed the "Free" plugins, 
registered with cloudbee and downloaded the 3.15 version.  How do I:
"upload it to Jenkins via the update center"?




On Friday, November 22, 2013 1:36 PM, Daniel Beck  wrote:
 
On 22.11.2013, at 19:18, Eric Wood  wrote:

> How do you gain access to the "closed-source" version.  Is this part of the 
> CloudBees Free Enterprise Plugins?

Apparently, not anymore. It already includes Folders 4 when I tried it on a 
Jenkins 1.532.1-rc. But you can install that, wait until Jenkins is restarted, 
register, manually download Folders 3.15 from 
http://jenkins-updates.cloudbees.com/download/plugins/cloudbees-folder/ and 
upload it to Jenkins via the update center, and restart Jenkins again. It 
worked like a charm for me without any existing folders. If you have existing 
folders, I'd try it on a throwaway instance first to see what happens to these 
folders.

You'll also probably want to disable or remove the other (annoying) plugins 
that come with the bundle.


-- 
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/groups/opt_out.

-- 
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/groups/opt_out.

Re: Matrix-based security does not authenticate group users in Active Directory

[SamL]

Thank you for the reply Daniel.
This was a weird issue, that seems to have gone away.
All we did was to leave the Active Directory  and Matrix-based security 
enable overnight and the next day things began working ok.

Not sure what that is all about.


On Monday, November 18, 2013 9:49:10 AM UTC-8, SamL wrote:
>
> Hello Folks,
>
> We are facing an issue where Matrix-based security does not appear to be 
> authenticating against users in groups.
> We have tried both:
>
> Active Directory and LDAP Security Realms and the issue appears in both 
>  cases
>
> We we add an Active Directory name in the Matrix-based security  users in 
> that group only see the settings applied to anonymous.
> It works find for individual  users.
>
>
> There are no  errors in the log file either.
>
> Any help would be very much appreciated.
>
> Jenkins 1.509.4
> Ubuntu 12.04
> Jenkins Active Directory plugin 1.33
>
>

-- 
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/groups/opt_out.

how to verify ldap email plugin working?

[Henry Hsue]

I set up the plugin according 
to https://wiki.jenkins-ci.org/display/JENKINS/LDAP+Email+Plugin. 

How can I verify that emails from LDAP are being pulled in? 

-- 
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/groups/opt_out.

Re: Move existing jobs into folders

[Daniel Beck]

Just thought I'd add that 3.15 is a dead end.

It's no problem for me to use it on temporary test instances (and Folders 4 on 
the Enterprise-licensed instances), but if, for some reason, Folders 3.x 
becomes incompatible with future Jenkins in some way, you'll be in trouble -- 
upgrading to the then-current version will remove all of these shiny features, 
which can be painful especially for the folder-wide environment variables!

On 22.11.2013, at 19:36, Daniel Beck  wrote:

> On 22.11.2013, at 19:18, Eric Wood  wrote:
> 
>> How do you gain access to the "closed-source" version.  Is this part of the 
>> CloudBees Free Enterprise Plugins?
> 
> Apparently, not anymore. It already includes Folders 4 when I tried it on a 
> Jenkins 1.532.1-rc. But you can install that, wait until Jenkins is 
> restarted, register, manually download Folders 3.15 from 
> http://jenkins-updates.cloudbees.com/download/plugins/cloudbees-folder/ and 
> upload it to Jenkins via the update center, and restart Jenkins again. It 
> worked like a charm for me without any existing folders. If you have existing 
> folders, I'd try it on a throwaway instance first to see what happens to 
> these folders.
> 
> You'll also probably want to disable or remove the other (annoying) plugins 
> that come with the bundle.
> 
> -- 
> 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/groups/opt_out.
> 

-- 
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/groups/opt_out.

Re: Move existing jobs into folders

[Daniel Beck]

On 22.11.2013, at 19:18, Eric Wood  wrote:

> How do you gain access to the "closed-source" version.  Is this part of the 
> CloudBees Free Enterprise Plugins?

Apparently, not anymore. It already includes Folders 4 when I tried it on a 
Jenkins 1.532.1-rc. But you can install that, wait until Jenkins is restarted, 
register, manually download Folders 3.15 from 
http://jenkins-updates.cloudbees.com/download/plugins/cloudbees-folder/ and 
upload it to Jenkins via the update center, and restart Jenkins again. It 
worked like a charm for me without any existing folders. If you have existing 
folders, I'd try it on a throwaway instance first to see what happens to these 
folders.

You'll also probably want to disable or remove the other (annoying) plugins 
that come with the bundle.

-- 
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/groups/opt_out.

Re: Build Pipeline links do not work in the view for the pipeline jobs is in the folder iteself

[Eric Wood]

I'll look at the issue, but the folder plugin seems like a valuable plugin to 
me as I have many jobs and the capability to manage in a folder structure and 
then be able to filter, assign permission, etc.  is invaluable.  I have so many 
jobs that managing them as a "flat folder" is getting to be a nightmare.

Thanks, Eric



On Friday, November 22, 2013 1:14 PM, Daniel Beck  wrote:
 
On 22.11.2013, at 19:09, Eric Wood  wrote:

> The triggers for the job work, just linking to the results from the jobs in 
> the pipeline does not.  It seems like a bug and that it would be pretty easy 
> to fix and would add a lot of value to managing pipeline jobs.

Generally bad support for folders in other plugins appears to be the reason 
that the Folders plugin was recently open sourced.

A similar, possibly related issue is 
https://issues.jenkins-ci.org/browse/JENKINS-19310


-- 
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/groups/opt_out.

-- 
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/groups/opt_out.

Re: Move existing jobs into folders

[Eric Wood]

Daniel:

What do you mean by:

But you should still be able to use the full-featured, closed-source Folders 
3.x if you tell Cloudbees your email address. The following features exist in 
Folders version 3 that have been removed from Folders 4 (and moved into 
commercial Folders Plus 2):


How do you gain access to the "closed-source" version.  Is this part of the 
CloudBees Free Enterprise Plugins?


Thanks, Eric



On Friday, November 22, 2013 1:10 PM, Daniel Beck  wrote:
 
You can manually move jobs from the 'jobs' directory into 
'jobs/foldername/jobs'. It will break any existing job relationships, but 
plugins should be able to deal with disappearing jobs.

But you should still be able to use the full-featured, closed-source Folders 
3.x if you tell Cloudbees your email address. The following features exist in 
Folders version 3 that have been removed from Folders 4 (and moved into 
commercial Folders Plus 2):

* Move jobs into/out of folders (without reloading data, but will still break 
job relationships thanks to JENKINS-18028 -- it will appear to delete the 
existing job and to create a new job to plugins monitoring such things)
* Configurable health reports (for the weather icon)
* Custom icons
* Folder-wide environment variables inherited to all descendent items/job
* Restrict job types possible in the folder


On 22.11.2013, at 18:30, Eric Wood  wrote:

> I just starting using the folders plugin and it looks great.  Is there a way 
> for me to move existing jobs into folders for better organization?
> 
> Thanks, Eric
> 
> -- 
> 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/groups/opt_out.

-- 
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/groups/opt_out.

-- 
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/groups/opt_out.

Re: Build Pipeline links do not work in the view for the pipeline jobs is in the folder iteself

[Daniel Beck]

On 22.11.2013, at 19:09, Eric Wood  wrote:

> The triggers for the job work, just linking to the results from the jobs in 
> the pipeline does not.  It seems like a bug and that it would be pretty easy 
> to fix and would add a lot of value to managing pipeline jobs.

Generally bad support for folders in other plugins appears to be the reason 
that the Folders plugin was recently open sourced.

A similar, possibly related issue is 
https://issues.jenkins-ci.org/browse/JENKINS-19310

-- 
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/groups/opt_out.

Re: Move existing jobs into folders

[Daniel Beck]

You can manually move jobs from the 'jobs' directory into 
'jobs/foldername/jobs'. It will break any existing job relationships, but 
plugins should be able to deal with disappearing jobs.

But you should still be able to use the full-featured, closed-source Folders 
3.x if you tell Cloudbees your email address. The following features exist in 
Folders version 3 that have been removed from Folders 4 (and moved into 
commercial Folders Plus 2):

* Move jobs into/out of folders (without reloading data, but will still break 
job relationships thanks to JENKINS-18028 -- it will appear to delete the 
existing job and to create a new job to plugins monitoring such things)
* Configurable health reports (for the weather icon)
* Custom icons
* Folder-wide environment variables inherited to all descendent items/job
* Restrict job types possible in the folder

On 22.11.2013, at 18:30, Eric Wood  wrote:

> I just starting using the folders plugin and it looks great.  Is there a way 
> for me to move existing jobs into folders for better organization?
> 
> Thanks, Eric
> 
> -- 
> 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/groups/opt_out.

-- 
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/groups/opt_out.

Build Pipeline links do not work in the view for the pipeline jobs is in the folder iteself

[Eric Wood]

I have set up a bunch of jobs in a folder and linked them as a build pipeline 
(i.e. upstream/downstream jobs). The view for the pipeline is also in the 
folder.  I wanted to be able to better segment my jobs and the pipeline that 
controls them.  I have noticed that if I set up the pipeline in a view under 
the folder, none of the links in the pipeline work.  They all produce the 
following error:

Problem accessing /job/Common/view/test/Common/job/test-DEV/2
Not found

The job link is: /job/Common/job/test-DEV

The triggers for the job work, just linking to the results from the jobs in the 
pipeline does not.  It seems like a bug and that it would be pretty easy to fix 
and would add a lot of value to managing pipeline jobs.

-- 
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/groups/opt_out.

Re: How to use the REST API to submit and follow jobs

[Daniel Beck]

There's a (very) new plugin that seems to do exactly what you want:

https://github.com/Spedge/job-run-uuid
https://github.com/jenkinsci/job-run-uuid-plugin

Its developer wrote on the Jenkins devs list:

> The plugin allows you to request a build from the API but it returns a JSON 
> snippet with a UUID for the job. This allows you to track the status of a job 
> (using another part of the API) even before it has left the queue and has 
> been assigned a run id - being in the queue is a valid state.
> 
> I've found it very useful for executing batches (100+) of the same job but 
> with different parameters, then tracking the status of them as they get 
> completed.
> 
> [...]
> 
> I'm also happy to listen to any suggestions or recommendations for this :)

Regards
Daniel

On 22.11.2013, at 11:56, Julian Payne  wrote:

> I am trying to use the REST API to submit a job and follow it's progress. The 
> problem that I am facing is that I can not see a fool-proof way to know what 
> is the job number of the new job when I submit using 
> job/MyJob/buildWithParameters
> 
> What I get back as JSON is designed for the UI but does not seem to give me 
> an explicit handle to the new job.
> 
> Here are the different replies that I seem to get:
> 
> 1. inQueue = true
> queueItem = null
> nextBuildNumber = 
> 
> In this case I could suppose that my build will be  but as I need 
> concurrent builds is this guaranteed?
> 
> 2. inQueue = true
> queueItem = { number =  ... }
> 
> Again I can see that there is a build in the queue but how can I be sure 
> that is mine?
> 
> It seems that the REST API works fine for the Jenkins UI that does not track 
> specific jobs but not really designed to submit and track a specific job?
> 
> Hopefully I missed something and this is not the case?
> 
> 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.
> For more options, visit https://groups.google.com/groups/opt_out.

-- 
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/groups/opt_out.

Re: Move existing jobs into folders

[Vincent Latombe]

That should work by moving in filesystem.

(the move feature is part of the Folders Plus plugin that is part of
Jenkins Enterprise offer)

Vincent


2013/11/22 Eric Wood 

> The only way I could figure it out was to actually move the job to the
> folder in the underlying Jenkins file system and then reload configuration
> information.  Which seemed to work, but I have not played with it enough to
> know if there is some embedded information that needs to be adjusted.  Is
> this an acceptable method or is there a way in the UI?
>
> Thanks, Eric
>
>
>   On Friday, November 22, 2013 12:30 PM, Eric Wood <
> eric.w...@rocketmail.com> wrote:
>   I just starting using the folders plugin and it looks great.  Is there
> a way for me to move existing jobs into folders for better organization?
>
> Thanks, Eric
> --
> 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/groups/opt_out.
>
>
>--
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

Re: Move existing jobs into folders

[Eric Wood]

The only way I could figure it out was to actually move the job to the folder 
in the underlying Jenkins file system and then reload configuration 
information.  Which seemed to work, but I have not played with it enough to 
know if there is some embedded information that needs to be adjusted.  Is this 
an acceptable method or is there a way in the UI?

Thanks, Eric



On Friday, November 22, 2013 12:30 PM, Eric Wood  
wrote:
 
I just starting using the folders plugin and it looks great.  Is there a way 
for me to move existing jobs into folders for better organization?

Thanks, Eric
-- 
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/groups/opt_out.

-- 
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/groups/opt_out.

Move existing jobs into folders

[Eric Wood]

I just starting using the folders plugin and it looks great.  Is there a way 
for me to move existing jobs into folders for better organization?

Thanks, Eric

-- 
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/groups/opt_out.

Re: Git Plugin Triggering Build Inaccurately

[Erik Cokeley]

Thanks I'm going to try the Force polling using workspace option.

On Friday, November 22, 2013 11:51:33 AM UTC-5, Nicolas De loof wrote:
>
> yes, I'm looking into possible changes in jenkins-core that would allow 
> such a remote-polling to be used to detect potential changes, then use 
> workspace to "confirm" changes actually have to get handled by a build.
>
>
> 2013/11/22 Mark Waite >
>
>> Nicolas DeLoof just posted a hint that the issue may be related to the 
>> change in the default state of "fast remote polling".  Fast remote polling 
>> allows the master Jenkins instance to check for changes on a git 
>> repository, without cloning that git repository.  That technique makes 
>> commit detection much lighter and faster.  However, that technique cannot 
>> process inclusion and exclusion conditions.
>>
>> If you have not already downgraded your Git plugin, you might try adding 
>> the Advanced Behavior, "Force polling using workspace".
>>
>> Mark Waite
>>
>>
>> On Fri, Nov 22, 2013 at 8:06 AM, Erik Cokeley 
>> 
>> > wrote:
>>
>>> Thanks I'm going to downgrade my git plugin.  I think that is what I'm 
>>> running into.
>>>
>>> On Thursday, November 21, 2013 6:12:33 PM UTC-5, Mark Waite wrote:

 You may be suffering from:

 https://issues.jenkins-ci.org/browse/JENKINS-20569
  - 
 excluded regions not honored by Git plugin 2.0

 I believe there is also a bug report that include regions do not behave 
 as expected.  It is probably worth a search through Jira to see what it 
 will tell you about include and exclude regions.

 Mark Waite


 On Thu, Nov 21, 2013 at 4:03 PM, Erik Cokeley wrote:

> My git is calling Jenkins in it's post-receive hook exactly how it 
> says to here: https://wiki.jenkins-ci.org/display/JENKINS/Git+
> Plugin#GitPlugin-Pushnotificationfromrepository
>
> It is kicking off builds and doing the Poll SCM (which I checked).
>
> My git is huge (I mean HUGE) and I need to leverage the Included 
> Regions.
>
> It seems like I get mixed results for pushes.  I might push to 
> folderA/folderB/project1 and folderA/folderC/project2 will be triggered 
> along with project1's job.  And my Included Region will look like 
> folderA/folderB/.*
>
> Is this a known bug or can anyone point me to why builds are being 
> triggered wrong?
>
> I'm also making my branch */master is the * in that effecting anything 
> (I only have 1 git setup for anything as of now)
>  
> -- 
> 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/groups/opt_out.
>

  -- 
>>> 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/groups/opt_out.
>>>
>>
>>  -- 
>> 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/groups/opt_out.
>>
>
>

-- 
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/groups/opt_out.

Re: Git Plugin Triggering Build Inaccurately

[nicolas de loof]

yes, I'm looking into possible changes in jenkins-core that would allow
such a remote-polling to be used to detect potential changes, then use
workspace to "confirm" changes actually have to get handled by a build.


2013/11/22 Mark Waite 

> Nicolas DeLoof just posted a hint that the issue may be related to the
> change in the default state of "fast remote polling".  Fast remote polling
> allows the master Jenkins instance to check for changes on a git
> repository, without cloning that git repository.  That technique makes
> commit detection much lighter and faster.  However, that technique cannot
> process inclusion and exclusion conditions.
>
> If you have not already downgraded your Git plugin, you might try adding
> the Advanced Behavior, "Force polling using workspace".
>
> Mark Waite
>
>
> On Fri, Nov 22, 2013 at 8:06 AM, Erik Cokeley  wrote:
>
>> Thanks I'm going to downgrade my git plugin.  I think that is what I'm
>> running into.
>>
>> On Thursday, November 21, 2013 6:12:33 PM UTC-5, Mark Waite wrote:
>>>
>>> You may be suffering from:
>>>
>>> https://issues.jenkins-ci.org/browse/JENKINS-20569
>>>  -
>>> excluded regions not honored by Git plugin 2.0
>>>
>>> I believe there is also a bug report that include regions do not behave
>>> as expected.  It is probably worth a search through Jira to see what it
>>> will tell you about include and exclude regions.
>>>
>>> Mark Waite
>>>
>>>
>>> On Thu, Nov 21, 2013 at 4:03 PM, Erik Cokeley wrote:
>>>
 My git is calling Jenkins in it's post-receive hook exactly how it says
 to here: https://wiki.jenkins-ci.org/display/JENKINS/Git+
 Plugin#GitPlugin-Pushnotificationfromrepository

 It is kicking off builds and doing the Poll SCM (which I checked).

 My git is huge (I mean HUGE) and I need to leverage the Included
 Regions.

 It seems like I get mixed results for pushes.  I might push to
 folderA/folderB/project1 and folderA/folderC/project2 will be triggered
 along with project1's job.  And my Included Region will look like
 folderA/folderB/.*

 Is this a known bug or can anyone point me to why builds are being
 triggered wrong?

 I'm also making my branch */master is the * in that effecting anything
 (I only have 1 git setup for anything as of now)

 --
 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/groups/opt_out.

>>>
>>>  --
>> 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/groups/opt_out.
>>
>
>  --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

Re: Git Plugin Triggering Build Inaccurately

[Mark Waite]

Nicolas DeLoof just posted a hint that the issue may be related to the
change in the default state of "fast remote polling".  Fast remote polling
allows the master Jenkins instance to check for changes on a git
repository, without cloning that git repository.  That technique makes
commit detection much lighter and faster.  However, that technique cannot
process inclusion and exclusion conditions.

If you have not already downgraded your Git plugin, you might try adding
the Advanced Behavior, "Force polling using workspace".

Mark Waite


On Fri, Nov 22, 2013 at 8:06 AM, Erik Cokeley  wrote:

> Thanks I'm going to downgrade my git plugin.  I think that is what I'm
> running into.
>
> On Thursday, November 21, 2013 6:12:33 PM UTC-5, Mark Waite wrote:
>>
>> You may be suffering from:
>>
>> https://issues.jenkins-ci.org/browse/JENKINS-20569
>>  -
>> excluded regions not honored by Git plugin 2.0
>>
>> I believe there is also a bug report that include regions do not behave
>> as expected.  It is probably worth a search through Jira to see what it
>> will tell you about include and exclude regions.
>>
>> Mark Waite
>>
>>
>> On Thu, Nov 21, 2013 at 4:03 PM, Erik Cokeley  wrote:
>>
>>> My git is calling Jenkins in it's post-receive hook exactly how it says
>>> to here: https://wiki.jenkins-ci.org/display/JENKINS/Git+
>>> Plugin#GitPlugin-Pushnotificationfromrepository
>>>
>>> It is kicking off builds and doing the Poll SCM (which I checked).
>>>
>>> My git is huge (I mean HUGE) and I need to leverage the Included Regions.
>>>
>>> It seems like I get mixed results for pushes.  I might push to
>>> folderA/folderB/project1 and folderA/folderC/project2 will be triggered
>>> along with project1's job.  And my Included Region will look like
>>> folderA/folderB/.*
>>>
>>> Is this a known bug or can anyone point me to why builds are being
>>> triggered wrong?
>>>
>>> I'm also making my branch */master is the * in that effecting anything
>>> (I only have 1 git setup for anything as of now)
>>>
>>> --
>>> 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/groups/opt_out.
>>>
>>
>>  --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

Re: After failed upgrade, restarting Jenkins keeps upgrading GIT plugin

[Todd]

An update: it wasn't Jenkins, but a Chef script for 
Jenkinsthat
 was causing our issue. 
*git* was one of the plugins we had configured to automatically upgrade 
(the fix was to simply stop using this automatic upgrade feature). Hope 
this is of use to someone!

-- 
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/groups/opt_out.

Re: Git Plugin Triggering Build Inaccurately

[Erik Cokeley]

Thanks I'm going to downgrade my git plugin.  I think that is what I'm 
running into.

On Thursday, November 21, 2013 6:12:33 PM UTC-5, Mark Waite wrote:
>
> You may be suffering from:
>
> https://issues.jenkins-ci.org/browse/JENKINS-20569
>  - 
> excluded regions not honored by Git plugin 2.0
>
> I believe there is also a bug report that include regions do not behave as 
> expected.  It is probably worth a search through Jira to see what it will 
> tell you about include and exclude regions.
>
> Mark Waite
>
>
> On Thu, Nov 21, 2013 at 4:03 PM, Erik Cokeley 
> > wrote:
>
>> My git is calling Jenkins in it's post-receive hook exactly how it says 
>> to here: 
>> https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-Pushnotificationfromrepository
>>
>> It is kicking off builds and doing the Poll SCM (which I checked).
>>
>> My git is huge (I mean HUGE) and I need to leverage the Included Regions.
>>
>> It seems like I get mixed results for pushes.  I might push to 
>> folderA/folderB/project1 and folderA/folderC/project2 will be triggered 
>> along with project1's job.  And my Included Region will look like 
>> folderA/folderB/.*
>>
>> Is this a known bug or can anyone point me to why builds are being 
>> triggered wrong?
>>
>> I'm also making my branch */master is the * in that effecting anything (I 
>> only have 1 git setup for anything as of now)
>>  
>> -- 
>> 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/groups/opt_out.
>>
>
>

-- 
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/groups/opt_out.

Re: Jenkins is hanging

[Etienne Grandier-Vazeille]

Hi

Same issue on Windows 7 x64 with jenkins 1.540 and JDK 1.7.0_17.

One solution is downgrade to oldest version like 1.526.


Le jeudi 14 novembre 2013 22:42:53 UTC+1, Benoit Sautel a écrit :
>
> Hello.
>
> I upgraded my Jenkins to the latest version. It is now unable to start. I 
> get all symptoms described 
> here
> .
>
> I tried to remove all the configuration and jobs, but it still can't start.
>
> It runs on a Debian Squeeze server, with Java OpenJDK 1.6.0_27.
>
> In the log file I don't see any abnormal message:
>
> Running from: /usr/share/jenkins/jenkins.war
> Nov 14, 2013 10:10:07 PM org.eclipse.jetty.util.log.JavaUtilLog info
> INFO: jetty-8.y.z-SNAPSHOT
> Nov 14, 2013 10:10:08 PM org.eclipse.jetty.util.log.JavaUtilLog info
> INFO: Extract jar:file:/usr/share/jenkins/jenkins.war!/ to 
> /tmp/jetty-0.0.0.0-8080-jenkins.war--any-/webapp
> Nov 14, 2013 10:10:11 PM org.eclipse.jetty.util.log.JavaUtilLog info
> INFO: NO JSP Support for , did not find 
> org.apache.jasper.servlet.JspServlet
> Jenkins home directory: /var/lib/jenkins found at: 
> EnvVars.masterEnvVars.get("JENKINS_HOME")
> Nov 14, 2013 10:10:12 PM org.eclipse.jetty.util.log.JavaUtilLog info
> INFO: Started 
> SelectChannelConnector@0.0.0.0:8080
> Nov 14, 2013 10:10:12 PM winstone.Logger logInternal
> INFO: Winstone Servlet Engine v2.0 running: controlPort=disabled
> Nov 14, 2013 10:10:12 PM jenkins.InitReactorRunner$1 onAttained
> INFO: Started initialization
> Nov 14, 2013 10:10:12 PM jenkins.InitReactorRunner$1 onAttained
> INFO: Listed all plugins
> Nov 14, 2013 10:10:12 PM jenkins.InitReactorRunner$1 onAttained
> INFO: Prepared all plugins
> Nov 14, 2013 10:10:12 PM jenkins.InitReactorRunner$1 onAttained
> INFO: Started all plugins
> Nov 14, 2013 10:10:12 PM jenkins.InitReactorRunner$1 onAttained
> INFO: Augmented all extensions
> Nov 14, 2013 10:10:12 PM jenkins.InitReactorRunner$1 onAttained
> INFO: Loaded all jobs
>
> Here is the jmap report of the Jenkins process:
>
> JVM version is 20.0-b12
>
> using thread-local object allocation.
> Parallel GC with 18 thread(s)
>
> Heap Configuration:
>MinHeapFreeRatio = 40
>MaxHeapFreeRatio = 70
>MaxHeapSize  = 698351616 (666.0MB)
>NewSize  = 1310720 (1.25MB)
>MaxNewSize   = 17592186044415 MB
>OldSize  = 5439488 (5.1875MB)
>NewRatio = 2
>SurvivorRatio= 8
>PermSize = 21757952 (20.75MB)
>MaxPermSize  = 174063616 (166.0MB)
>
> Heap Usage:
> PS Young Generation
> Eden Space:
>capacity = 211484672 (201.6875MB)
>used = 61938720 (59.069366455078125MB)
>free = 149545952 (142.61813354492188MB)
>29.28756936105516% used
> From Space:
>capacity = 5177344 (4.9375MB)
>used = 5172992 (4.933349609375MB)
>free = 4352 (0.004150390625MB)
>99.9159414556962% used
> To Space:
>capacity = 7733248 (7.375MB)
>used = 0 (0.0MB)
>free = 7733248 (7.375MB)
>0.0% used
> PS Old Generation
>capacity = 22413312 (21.375MB)
>used = 12653512 (12.067329406738281MB)
>free = 9759800 (9.307670593261719MB)
>56.455342253746345% used
> PS Perm Generation
>capacity = 45940736 (43.8125MB)
>used = 45796672 (43.67510986328125MB)
>free = 144064 (0.13739013671875MB)
>99.68641338266762% used
>
> It sounds like the perm generation is nearly full. I tried to increase it 
> with -XX:MaxPermSize=256M but it dit not change anything.
>
> I joined the jstack report but it seems to indicate that there is no 
> deadlock.
>
> I also noted that when I stop the Jenkins service, the process keeps 
> running. I have to kill -9 it to get it stop.
>
> Would someone know where the problem comes from?
>
> Thanks in advance. And thank you for developing Jenkins which is an 
> awesome product.
>

-- 
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/groups/opt_out.

Re: Multijob jenkins plugin help

[Eric Pyle]

Hi Rodrigo,

This seems like a situation that you could solve by creating a single 
parent POM for all the components and just building that in a Jenkins job.


Regards,
Eric

On 11/21/2013 2:52 PM, Rodrigo Berto wrote:
Hello people, my name is Rodrigo and I am completely new into Jenkins 
world.


In the project I'm working on right now, we are setting up Jenkins for 
a CI process. We started by creating one job per each different 
component of our system but we are looking forward to have just one 
job for all the components. The issues is that each of this parts we 
want to integrate in a single job uses a different maven pom.


So, then I started to investigate and found the Multijob plugin which 
would let me execute a build of each of the components we want to 
have, however, it seems to be executing the single jobs anyway.


Is there a way to stop building the single jobs of each component I 
have configured before and use the Multijob task only? Is there 
another option or workaround I could follow in order to have all my 
components with each respective pom building in a single job?



Thanks!!

Rodrigo
--
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/groups/opt_out.


--
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/groups/opt_out.

Re: Findbugs plugin - tell Jenkins where to find the XML file

[John D. Ament]

My results are currently inconsistent with two projects.

In both projects, my maven command line is the same, e.g. clean install 
deploy findbugs:findbugs 

In one project, Jenkins is picking up the findbugsXml.xml and running 
findbugs against it.  In the other, no I do not see the FINDBUGS output in 
the console.  Both are using findbugs 2.5.2.

On Thursday, November 21, 2013 6:16:55 PM UTC-5, Ullrich Hafner wrote:
>
> In a maven job every child module XML should be picked up automatically. 
> How do you start findbugs? Which version of the maven findbugs plugin are 
> you using? Newer version should produce a findbugsXml.xml file and not the 
> outdated find bugs.xml file...
>
> Are there logging messages in the console log of your build that start 
> with [FINDBUGS]?
>
> Am Donnerstag, 21. November 2013 schrieb John D. Ament :
>
>> So if I have a multi module project, where the root pom.xml doesn't have 
>> findbugs, but instead one of the child modules has it, there's not 
>> possibility to have a maven job pick up that findbugs.xml file in 
>> my-submodule/target/findbugs.xml ?
>>
>> On Thursday, November 21, 2013 4:15:53 PM UTC-5, Ullrich Hafner wrote:
>>>
>>> For Maven jobs, the file name is automatically derived from the pom.
>>> For Freestyle jobs, you can enter the filename in the advanced section.
>>>
>>> Ulli 
>>>
>>> Am 21.11.2013 um 19:52 schrieb John D. Ament :
>>>
>>> All,
>>>
>>> Is it possible to tell Jenkins where to find the findbugs xml file after 
>>> running a build?
>>> I have a multi module project, and want Jenkins to be able to run 
>>> findbugs analysis on all of the XML files and report against it that way.
>>>
>>> John
>>>
>>> -- 
>>> 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/groups/opt_out.
>>>
>>>
>>>  -- 
>> 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/groups/opt_out.
>>
>

-- 
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/groups/opt_out.

Re: Use different backend (plug in) for authentication and authorization?

[Stephen Connolly]

More I don't want you to think I am promising something that I am not. Or
to phrase it another way... it solves a problem that may or may not be your
actual problem... but for sure it is not the problem you originally
asked... but then the problem you originally asked may or may not be your
actual problem ;-)


On 22 November 2013 07:17, Steffen Breitbach wrote:

> Don't worry, I wasn't going to run around begging for money ;-)
>
> I just have heard "...or you could use the enterprise version" one too
> many times, so I think I'll give it a closer look (for real this time).
>
> -Ursprüngliche Nachricht-
> Von: jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] Im Auftrag von Stephen Connolly
> Gesendet: Donnerstag, 21. November 2013 16:31
> An: jenkinsci-users@googlegroups.com
> Betreff: Re: Use different backend (plug in) for authentication and
> authorization?
>
> Try a 30 day evaluation license first... I am worried that you might be
> confused about how the RBAC's local groups work... you are still going to
> be limited by what the Security Realm you choose can provide... but one of
> the reasons for RBAC was to allow Jenkins to manage its own internal group
> details...
>
> e.g. before I started at cloudbees, the problem I had when running Jenkins
> is we needed to authenticate against corporate AD but we didn't want to
> deal with the heavyweight corp IT process to create and maintain groups in
> AD, so being able to have local groups was a critical requirement in any
> RBAC authorization strategy, hence I baked it in as an *Additional* layer
>
>
> On 21 November 2013 14:34, Steffen Breitbach 
> wrote:
>
>
> I think I might have to convince middle management to buy a
> license ;-)
>
> -Ursprüngliche Nachricht-
> Von: jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] Im Auftrag von Stephen Connolly
> Gesendet: Donnerstag, 21. November 2013 11:56
> An: jenkinsci-users@googlegroups.com
> Betreff: Re: Use different backend (plug in) for authentication
> and authorization?
>
>
> you could certainly write such a Security Realm implementation...
> but be warned that Security Realm implementations are probably among the
> more complex to write (i.e. it can be easy to fuck them up)
>
> The user and group information is all provided by the single
> Security Ream component, so they both have to come from a single plugin.
>
> An alternative is the commercial CloudBees Enterprise RBAC plugin
> which lets you define and manage groups *within* jenkins... that gives you
> an additional layer for group information (i.e. your CAS Security realm
> would not be providing RBAC with "external" group information and it will
> not - in and of itself - go and ask your LDAP server about groups... if you
> configured the LDAP security realm, however, then the RBAC plugin would get
> the LDAP group info... but you wouldn't have the CAS authentication then
> ;-) )
>
>
> On 21 November 2013 10:18, Steffen Breitbach <
> steffen.breitb...@1und1.de> wrote:
>
>
> Hi everyone!
>
> In our company one can use CAS as an authentication
> service for single sign on purposes. Unfortunately, however, that is all it
> does. The response contains information about the user (like email address)
> but not about the roles he is in. This has to be done e.g. trough LDAP.
>
> Is there a way to use two different plug ins for
> authentication and authorization in Jenkins?
>
> Regards
>   Steffen
>
> --
> 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 jenkinsci-users%2bunsubscr...@googlegroups.com>   jenkinsci-users%2bunsubscr...@googlegroups.com  jenkinsci-users%252bunsubscr...@googlegroups.com> > .
>
> For more options, visit
> https://groups.google.com/groups/opt_out.
>
>
>
> --
> 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  jenkinsci-users%2bunsubscr...@googlegroups.com> .
> For more options, visit https://groups.google.com/groups/opt_out.
>
> --
> 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  jenkinsci-users%2bunsubscr...@googlegroups.com> .
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
> --
> You received this message 

Re: Is it any good to use Jenkins as a web based UI for running operational scripts?

[Baptiste Mathus]

+1. We're even considering using Jenkins as the default light scheduler for
some of our customers.
Basically, use Jenkins to do anything repetitive. People's brains should be
used to do things machines can't.
Le 21 nov. 2013 20:59, "Mark Waite"  a écrit :

> It is well within the Jenkins use model to use it to automate all sorts of
> other tasks.  We've even gone so far as to have some of our tasks learn how
> to write more detailed information in JUnit format so that we can monitor
> results from portions of the task while still allowing the task to complete.
>
>
> On Thu, Nov 21, 2013 at 12:55 PM, Yasir  wrote:
>
>> I am contemplating whether to use Jenkins for non-build related things.
>>  It seems like a lot people are doing that, however, what I want to ask is
>> that does it go against the principle of Jenkins?  I would love to automate
>> certain daily tasks that a team member has to perform using jenkins.  But I
>> don't want to use it if by doing so will bastardize jenkins and it will be
>> used incorrectly.  any thoughts?
>>
>> Yasir
>>
>> On Wednesday, August 29, 2012 12:24:58 AM UTC-5, Manglu wrote:
>>>
>>> I encountered an operations team which had built a number of jobs in
>>> Jenkins and all it does was kickstart scripts in the OS.
>>>
>>> This sounded a bit strange to me as they are effectively using Jenkins
>>> as a glorified UI for these tasks.
>>>
>>> Are there others who do similar stuff?
>>>
>>> Thanks
>>>
>>> Manglu
>>>
>>>
>>>
>>>
>>>  --
>> 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/groups/opt_out.
>>
>
>  --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

How to use the REST API to submit and follow jobs

[Julian Payne]

I am trying to use the REST API to submit a job and follow it's progress. 
The problem that I am facing is that I can not see a fool-proof way to know 
what is the job number of the new job when I submit using 
job/MyJob/buildWithParameters

What I get back as JSON is designed for the UI but does not seem to give me 
an explicit handle to the new job.

Here are the different replies that I seem to get:

1. inQueue = true
queueItem = null
nextBuildNumber = 

In this case I could suppose that my build will be  but as I need 
concurrent builds is this guaranteed?

2. inQueue = true
queueItem = { number =  ... }

Again I can see that there is a build in the queue but how can I be 
sure that is mine?

It seems that the REST API works fine for the Jenkins UI that does not 
track specific jobs but not really designed to submit and track a specific 
job?

Hopefully I missed something and this is not the case?

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

Re: best way to update jenkins on ubuntu 13.10?

[Daniel Beck]

On 22.11.2013, at 09:27, Marius Gedminas  wrote:

> There's a bug in upstream packaging that breaks upgrades:
> https://issues.jenkins-ci.org/browse/JENKINS-18798
> 
> There's a related bug that makes Jenkins not start up on boot:
> https://issues.jenkins-ci.org/browse/JENKINS-19329

Are these really _bugs_ in the Jenkins Debian package? It looks like the Ubuntu 
maintainers created another Jenkins package that behaves differently, and the 
'official' Jenkins releases ('upstream') simply don't know or care about its 
existence. If you create something new 'downstream', shouldn't you need to 
handle any compatibility issues between your package and the 'official' one?

-- 
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/groups/opt_out.

Re: best way to update jenkins on ubuntu 13.10?

[Marius Gedminas]

On Thursday, November 21, 2013 10:30:03 PM UTC+2, and...@wazoku.com wrote:

> Ah yes sorry I missed that..
> Now I followed the doc from that page but it still didn't work and left me 
> in a half-configured state; I had to force a dpkg -i of the old package to 
> fix it..
>
> Basically it was failing
> Setting up jenkins (1.540) ...
> start: Job failed to start
> invoke-rc.d: initscript jenkins, action "start" failed.
> dpkg: error processing jenkins (--configure):
>  subprocess installed post-installation script returned error exit status 1
> Errors were encountered while processing:
>  jenkins
>
> So maybe is the package not correct for Ubuntu 13.10 or what else can it 
> be?
>

There's a bug in upstream packaging that breaks upgrades:
https://issues.jenkins-ci.org/browse/JENKINS-18798

There's a related bug that makes Jenkins not start up on boot:
https://issues.jenkins-ci.org/browse/JENKINS-19329

Workarounds for both issues:

sudo apt-get remove jenkins jenkins-common
sudo apt-get install jenkins
sudo rm /etc/init/jenkins.conf
sudo update-rc.d jenkins defaults
sudo service jenkins start

-- 
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/groups/opt_out.