Re: Svn Credentials

2014-02-19 Thread Baptiste Mathus
I would definitively go with the groovy script console to do that
configuration on every job.

Cheers
Le 19 févr. 2014 01:43, Jmata jmat...@gmail.com a écrit :

 So this is our current setup.
 1 master (server2012)
 14 slaves(server2003, 2008, OSX)
 500 jobs across the slaves.
 1 AD svcSVN account in our domain. Im in the process of upgrading to the
 jenkins master to 1.551 but ran into the problem where all the jobs fail
 because there is not password stored inside the configuration setting in
 the job. I really don't want to configure every single job with the domain
 svcSVN account.. that would take hours. Just trying to put this setting
 globally so it will automatically know what credentials it needs to use.
 The Master Jenkins is running on Windows Server 2012 Environment hope this
 helps a bit more ...Please advise .

 Thanks

 On Tuesday, February 18, 2014 5:32:12 PM UTC-7, Indra Gunawan (ingunawa)
 wrote:

  HI Jmata,

  In our setup, we have a generic AD user that runs Jenkins.
 For any given SVN repository, we simply check out with “-N” once as this
 user and let SVN keep the credential password cached.  The cache credential
 is stored as file in the generic user home directory/.subversion/auth/
 svn.simple/.
 Unless you are building on a slave connecting to master as a different
 user, all jobs should be able to check out since the same AD user also runs
 the Jenkins instance/ Jenkins Master.

 -Indra

   From: Jmata jma...@gmail.com
 Reply-To: jenkins...@googlegroups.com jenkins...@googlegroups.com
 Date: Tuesday, February 18, 2014 at 3:18 PM
 To: jenkins...@googlegroups.com jenkins...@googlegroups.com
 Subject: Svn Credentials

   Hey Guys,
 Having an SVN issue..
 So here is my problem, I have about 500 jobs in my Jenkins Master. All my
 jobs are failing because I need to enter our svn username and password, I
 really don't want to do this process for all 500 jobs under the configure
 option.
 Is there a way I can just use one global password for SVN? I did put the
 creds under Configure System Global SVN Publisher but that didn't seem to
 work.
 Any Ideas would be appreciated.

  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-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: Svn Credentials

2014-02-18 Thread Indra Gunawan (ingunawa)
HI Jmata,

In our setup, we have a generic AD user that runs Jenkins.
For any given SVN repository, we simply check out with -N once as this user 
and let SVN keep the credential password cached.  The cache credential is 
stored as file in the generic user home directory/.subversion/auth/svn.simple/.
Unless you are building on a slave connecting to master as a different user, 
all jobs should be able to check out since the same AD user also runs the 
Jenkins instance/ Jenkins Master.

-Indra

From: Jmata jmat...@gmail.commailto:jmat...@gmail.com
Reply-To: 
jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com 
jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com
Date: Tuesday, February 18, 2014 at 3:18 PM
To: jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com 
jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com
Subject: Svn Credentials

Hey Guys,
Having an SVN issue..
So here is my problem, I have about 500 jobs in my Jenkins Master. All my jobs 
are failing because I need to enter our svn username and password, I really 
don't want to do this process for all 500 jobs under the configure option.
Is there a way I can just use one global password for SVN? I did put the creds 
under Configure System Global SVN Publisher but that didn't seem to work.
Any Ideas would be appreciated.

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.commailto: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: Svn Credentials

2014-02-18 Thread Jmata
So this is our current setup. 
1 master (server2012)
14 slaves(server2003, 2008, OSX)
500 jobs across the slaves.
1 AD svcSVN account in our domain. Im in the process of upgrading to the 
jenkins master to 1.551 but ran into the problem where all the jobs fail 
because there is not password stored inside the configuration setting in 
the job. I really don't want to configure every single job with the domain 
svcSVN account.. that would take hours. Just trying to put this setting 
globally so it will automatically know what credentials it needs to use.
The Master Jenkins is running on Windows Server 2012 Environment hope this 
helps a bit more ...Please advise .

Thanks

On Tuesday, February 18, 2014 5:32:12 PM UTC-7, Indra Gunawan (ingunawa) 
wrote:

  HI Jmata,

  In our setup, we have a generic AD user that runs Jenkins.  
 For any given SVN repository, we simply check out with “-N” once as this 
 user and let SVN keep the credential password cached.  The cache credential 
 is stored as file in the generic user home 
 directory/.subversion/auth/svn.simple/.
 Unless you are building on a slave connecting to master as a different 
 user, all jobs should be able to check out since the same AD user also runs 
 the Jenkins instance/ Jenkins Master.
  
 -Indra

   From: Jmata jma...@gmail.com javascript:
 Reply-To: jenkins...@googlegroups.com javascript: 
 jenkins...@googlegroups.com javascript:
 Date: Tuesday, February 18, 2014 at 3:18 PM
 To: jenkins...@googlegroups.com javascript: 
 jenkins...@googlegroups.com javascript:
 Subject: Svn Credentials
  
   Hey Guys, 
 Having an SVN issue.. 
 So here is my problem, I have about 500 jobs in my Jenkins Master. All my 
 jobs are failing because I need to enter our svn username and password, I 
 really don't want to do this process for all 500 jobs under the configure 
 option. 
 Is there a way I can just use one global password for SVN? I did put the 
 creds under Configure System Global SVN Publisher but that didn't seem to 
 work.
 Any Ideas would be appreciated.

  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-use...@googlegroups.com javascript:.
 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: SVN credentials re-use in shell script, later in the build job

2012-08-24 Thread marathiboy
Hello,

I use it and it just works..I added svn command (like svn info) within build
step - execute shell and it works without any issues. I actually wrote a
script and call that script within execute shell

M



--
View this message in context: 
http://jenkins.361315.n4.nabble.com/SVN-credentials-re-use-in-shell-script-later-in-the-build-job-tp4638528p4638536.html
Sent from the Jenkins users mailing list archive at Nabble.com.