Re: Seperate configure access to different views

2012-12-24 Thread kapila narang
thanks but i have tried this but seems to be missing something.. would be great help if u can suggest where am i going wrong- using Jenkins ver. 1.492, plugin- view-job-filters 1.22 I need to create 10 different users for my TL of different Line of business, e.g. i take LOB name ABC & created user

Re: View Level Access-Need Help !!

2012-12-24 Thread kapila narang
Hey Japinder, I am in similar issue can u help me here how u got it sorted? http://groups.google.com/group/jenkinsci-users/browse_thread/thread/dc4e05a80278d8ab/3603f6bed037cf5b?hl=en&lnk=gst&q=kapila#3603f6bed037cf5b On Nov 26, 4:15 pm, japinder gill wrote: > yes i tried using Project-based M

Re: Seperate configure access to different views

2012-12-24 Thread japinder gill
so sorry kapila, right now m on leave, i have not yet fully implemented this but still working on it.i will be working more on this in jan. meanwhile do share if you happen to do it. On Monday, December 17, 2012 11:14:28 AM UTC+5:30, kapila narang wrote: > > Hi, > I have jenkins running for 80

Re: Seperate configure access to different views

2012-12-24 Thread kapila narang
oh! okay sure On Mon, Dec 24, 2012 at 4:19 PM, japinder gill wrote: > so sorry kapila, right now m on leave, i have not yet > fully implemented this but still working on it.i will be working more on > this in jan. > meanwhile do share if you happen to do it. > > On Monday, December 17, 2012 11:1

Build directory and clean procedure [best practices]

2012-12-24 Thread Paulo J. Matos
Hello, I am using jenkins for the first time. Great software, I am very happy with its ease of use. I do however have some questions: * I got jenkins to hourly poll a git rep, the I execute a shell script. Is this shell script supposed to build, install and test? Or should these things be sepa

Re: Build directory and clean procedure [best practices]

2012-12-24 Thread Eric Pyle
Hi Paulo, I think common practice is to have your shell script build when it detects a check-in via polling, on successful completion of build it would call another Jenkins job to install and test. This separates pure compiling errors from logical or other errors which cause tests to fail. Second,