Re: Having problem in importing the code from Github to Jenkins.

2017-01-11 Thread Mark Waite
Because you have probably not configured the git executable in Jenkins, or
possibly you chose to install Git without making git available from the
command line.  If you installed without making git available from the
command line, then you'll need to provide the absolute path to the git
executable.

Mark Waite

On Wed, Jan 11, 2017 at 10:24 PM Sathish M  wrote:

>
> 
>
> I am getting like this when I include SSH credential.why?
>
>
> On Thursday, January 12, 2017 at 10:34:33 AM UTC+5:30, Mark Waite wrote:
>
> You're using an scp / ssh connection, but seem to be hinting that you may
> be using a username / password credential.  If you're using an scp / ssh
> connection, then you need to use a private key credential.
>
> If a username / password credential is required, then you'll need to use
> https to connect to the repository.
>
> Mark Waite
>
> On Wed, Jan 11, 2017 at 9:51 PM Sathish M  wrote:
>
> Yeah okay,
> In Github,
>  I have created an account in GitHub.
> In Jenkins,
>  I added the needed Github plugins into my jenkins. And I added
> the credentials for my GitHub account and also the api credentials. And I
> tested the connection in manage jenkins->configuresystem. It succeeded. And
> I created a new job & In general tab I checked the Github project & gave
> the http link to my repo.
> In SCM I gave the repo SSH link and the added the api credential. And I am
> getting the error  (I have attached that )
>
>
> 
>
> Please help me with this.
>
>
> On Thursday, January 12, 2017 at 9:57:02 AM UTC+5:30, Ramanathan Muthaiah
> wrote:
>
> On Wednesday, January 11, 2017 at 2:45:26 PM UTC+5:30, Sathish M wrote:
>
> I am new to Jenkins. I've been learning it by myself, as of now I know to
> create a job & build it when my source code is in my local system. Now I am
> trying to work the same from Jenkins. I've been trying it but I can't get
> that. Can you help me to work here with Github.
>
>
> Ram : There are plenty of resources on the Internet regd Jenkins
> integration with GitHub.
>
> It will help if you can list what did you try and what did not work
> including tool or plugin versions.
>
> /Ram
>
> --
> 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/0654cd37-0cd6-4273-97dd-6cc3037d00a5%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/5bd855b2-e967-48d1-840c-6870da16d5b9%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/CAO49JtHcrRXEEBrJ_CgV%2BQsz-ovtRV3YkMZ6WjU2kqiaTT8H%2BA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Help me with this error

2017-01-11 Thread Mark Waite
If you installed git and added it to the PATH, then you should only need to
use the default "git".

If you did not add it to the PATH, then you'll need to provide the absolute
path to the executable.

Mark Waite

On Wed, Jan 11, 2017 at 10:28 PM Sathish M  wrote:

> I've Installed that git online. So the path is not required right
>
> --
> Sathish M
>
>
> On Thu, Jan 12, 2017 at 10:48 AM, Mark Waite 
> wrote:
>
> The git plugin allows a user to define the git executable which will be
> used to perform git commands.  That allows users to override the default
> git executable (for example, with /usr/local/bin/git instead of the default
> "git").
>
> That configuration is performed through "Manage Jenkins" -> "Global Tool
> Configuration".  In that page, there is a section "Git" which probably has
> a section named "Default".  In that section, there is a field named "Path
> to Git executable".  My guess is that field is empty in your
> installation, or the default git installation has been deleted and you need
> to add a git installation named "Default".
>
> Unfortunately, the global configuration page should show some warning that
> the field should not be empty.  It doesn't do that.
>
> Mark Waite
>
> On Wed, Jan 11, 2017 at 9:25 PM Sathish M  wrote:
>
> Sorry I didn't get you.
>
>
> On Thursday, January 12, 2017 at 12:45:15 AM UTC+5:30, Mark Waite wrote:
>
> The output
>
> >  init C:\Users\User\.jenkins\workspace\test-git # timeout=10
>
> usually means that you've made a system configuration error.  You've
> probably defined the name of the git executable as an empty field or empty
> string.  That line should have been:
>
> >  git init C:\Users\User\.jenkins\workspace\test-git # timeout=10
>
> and since the command name "git" is missing from the output, it likely
> means that you defined your git executable as the empty string.
>
> If the system configuration page which prompts for the git executable name
> doesn't show an empty field as an error, please submit an enhancement
> request to make that field warn if it is empty.
>
> Mark Waite
>
> On Wed, Jan 11, 2017 at 10:31 AM  wrote:
>
> Is Git properly installed on your Jenkins server?
>
>
> https://support.cloudbees.com/hc/en-us/articles/218156697-Git-Failed-to-connect-to-repository-Could-not-init-tmp
>
> On Wednesday, January 11, 2017 at 7:19:44 AM UTC-5, Sathish M wrote:
>
>
> Failed to connect to repository : Error performing command:  ls-remote -h 
> g...@github.com:
>
>
> and
>
>
>
> Started by user Administrator 
> Building on master in workspace C:\Users\User\.jenkins\workspace\test-git
> Cloning the remote Git repository
> Cloning repository g...@github.com:/ant_1
>  >  init C:\Users\User\.jenkins\workspace\test-git # timeout=10
> ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException 
> :
>  Could not init C:\Users\User\.jenkins\workspace\test-git
>   at 
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:666)
>  
> 
>   at 
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:467)
>  
> 
>   at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1054) 
> 
>   at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1094) 
> 
>   at hudson.scm.SCM.checkout(SCM.java:495) 
> 
>   at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) 
> 
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
>  
> 
>   at 
> jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) 
> 
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) 
> 
>   at hudson.model.Run.execute(Run.java:1720) 
> 
>   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 
> 

Re: Help me with this error

2017-01-11 Thread Sathish M
I've Installed that git online. So the path is not required right

--
Sathish M


On Thu, Jan 12, 2017 at 10:48 AM, Mark Waite 
wrote:

> The git plugin allows a user to define the git executable which will be
> used to perform git commands.  That allows users to override the default
> git executable (for example, with /usr/local/bin/git instead of the default
> "git").
>
> That configuration is performed through "Manage Jenkins" -> "Global Tool
> Configuration".  In that page, there is a section "Git" which probably has
> a section named "Default".  In that section, there is a field named "Path
> to Git executable".  My guess is that field is empty in your
> installation, or the default git installation has been deleted and you need
> to add a git installation named "Default".
>
> Unfortunately, the global configuration page should show some warning that
> the field should not be empty.  It doesn't do that.
>
> Mark Waite
>
> On Wed, Jan 11, 2017 at 9:25 PM Sathish M  wrote:
>
>> Sorry I didn't get you.
>>
>>
>> On Thursday, January 12, 2017 at 12:45:15 AM UTC+5:30, Mark Waite wrote:
>>
>> The output
>>
>> >  init C:\Users\User\.jenkins\workspace\test-git # timeout=10
>>
>> usually means that you've made a system configuration error.  You've
>> probably defined the name of the git executable as an empty field or empty
>> string.  That line should have been:
>>
>> >  git init C:\Users\User\.jenkins\workspace\test-git # timeout=10
>>
>> and since the command name "git" is missing from the output, it likely
>> means that you defined your git executable as the empty string.
>>
>> If the system configuration page which prompts for the git executable
>> name doesn't show an empty field as an error, please submit an enhancement
>> request to make that field warn if it is empty.
>>
>> Mark Waite
>>
>> On Wed, Jan 11, 2017 at 10:31 AM  wrote:
>>
>> Is Git properly installed on your Jenkins server?
>>
>> https://support.cloudbees.com/hc/en-us/articles/218156697-
>> Git-Failed-to-connect-to-repository-Could-not-init-tmp
>>
>> On Wednesday, January 11, 2017 at 7:19:44 AM UTC-5, Sathish M wrote:
>>
>>
>> Failed to connect to repository : Error performing command:  ls-remote -h 
>> g...@github.com:
>>
>>
>> and
>>
>>
>>
>> Started by user Administrator 
>> Building on master in workspace C:\Users\User\.jenkins\workspace\test-git
>> Cloning the remote Git repository
>> Cloning repository g...@github.com:/ant_1
>>  >  init C:\Users\User\.jenkins\workspace\test-git # timeout=10
>> ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException 
>> :
>>  Could not init C:\Users\User\.jenkins\workspace\test-git
>>  at 
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:666)
>>  
>> 
>>  at 
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:467)
>>  
>> 
>>  at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1054) 
>> 
>>  at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1094) 
>> 
>>  at hudson.scm.SCM.checkout(SCM.java:495) 
>> 
>>  at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) 
>> 
>>  at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
>>  
>> 
>>  at 
>> jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) 
>> 
>>  at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
>>  
>> 
>>  at hudson.model.Run.execute(Run.java:1720) 
>> 
>>  at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 
>> 
>>  at hudson.model.ResourceController.execute(ResourceController.java:98) 
>> 

Re: Having problem in importing the code from Github to Jenkins.

2017-01-11 Thread Sathish M




I am getting like this when I include SSH credential.why?


On Thursday, January 12, 2017 at 10:34:33 AM UTC+5:30, Mark Waite wrote:
>
> You're using an scp / ssh connection, but seem to be hinting that you may 
> be using a username / password credential.  If you're using an scp / ssh 
> connection, then you need to use a private key credential.
>
> If a username / password credential is required, then you'll need to use 
> https to connect to the repository.
>
> Mark Waite
>
> On Wed, Jan 11, 2017 at 9:51 PM Sathish M  > wrote:
>
>> Yeah okay,
>> In Github,
>>  I have created an account in GitHub.
>> In Jenkins,
>>  I added the needed Github plugins into my jenkins. And I added 
>> the credentials for my GitHub account and also the api credentials. And I 
>> tested the connection in manage jenkins->configuresystem. It succeeded. And 
>> I created a new job & In general tab I checked the Github project & gave 
>> the http link to my repo. 
>> In SCM I gave the repo SSH link and the added the api credential. And I 
>> am getting the error  (I have attached that )
>>
>>
>> 
>>
>> Please help me with this.
>>
>>
>> On Thursday, January 12, 2017 at 9:57:02 AM UTC+5:30, Ramanathan Muthaiah 
>> wrote:
>>>
>>> On Wednesday, January 11, 2017 at 2:45:26 PM UTC+5:30, Sathish M wrote:

 I am new to Jenkins. I've been learning it by myself, as of now I know 
 to create a job & build it when my source code is in my local system. Now 
 I 
 am trying to work the same from Jenkins. I've been trying it but I can't 
 get that. Can you help me to work here with Github.

>>>
>>> Ram : There are plenty of resources on the Internet regd Jenkins 
>>> integration with GitHub.
>>>
>>> It will help if you can list what did you try and what did not work 
>>> including tool or plugin versions.
>>>
>>> /Ram
>>>
>> -- 
>> 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/0654cd37-0cd6-4273-97dd-6cc3037d00a5%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/5bd855b2-e967-48d1-840c-6870da16d5b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Help me with this error

2017-01-11 Thread Mark Waite
The git plugin allows a user to define the git executable which will be
used to perform git commands.  That allows users to override the default
git executable (for example, with /usr/local/bin/git instead of the default
"git").

That configuration is performed through "Manage Jenkins" -> "Global Tool
Configuration".  In that page, there is a section "Git" which probably has
a section named "Default".  In that section, there is a field named "Path
to Git executable".  My guess is that field is empty in your installation,
or the default git installation has been deleted and you need to add a git
installation named "Default".

Unfortunately, the global configuration page should show some warning that
the field should not be empty.  It doesn't do that.

Mark Waite

On Wed, Jan 11, 2017 at 9:25 PM Sathish M  wrote:

> Sorry I didn't get you.
>
>
> On Thursday, January 12, 2017 at 12:45:15 AM UTC+5:30, Mark Waite wrote:
>
> The output
>
> >  init C:\Users\User\.jenkins\workspace\test-git # timeout=10
>
> usually means that you've made a system configuration error.  You've
> probably defined the name of the git executable as an empty field or empty
> string.  That line should have been:
>
> >  git init C:\Users\User\.jenkins\workspace\test-git # timeout=10
>
> and since the command name "git" is missing from the output, it likely
> means that you defined your git executable as the empty string.
>
> If the system configuration page which prompts for the git executable name
> doesn't show an empty field as an error, please submit an enhancement
> request to make that field warn if it is empty.
>
> Mark Waite
>
> On Wed, Jan 11, 2017 at 10:31 AM  wrote:
>
> Is Git properly installed on your Jenkins server?
>
>
> https://support.cloudbees.com/hc/en-us/articles/218156697-Git-Failed-to-connect-to-repository-Could-not-init-tmp
>
> On Wednesday, January 11, 2017 at 7:19:44 AM UTC-5, Sathish M wrote:
>
>
> Failed to connect to repository : Error performing command:  ls-remote -h 
> g...@github.com:
>
>
> and
>
>
>
> Started by user Administrator 
> Building on master in workspace C:\Users\User\.jenkins\workspace\test-git
> Cloning the remote Git repository
> Cloning repository g...@github.com:/ant_1
>  >  init C:\Users\User\.jenkins\workspace\test-git # timeout=10
> ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException 
> :
>  Could not init C:\Users\User\.jenkins\workspace\test-git
>   at 
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:666)
>  
> 
>   at 
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:467)
>  
> 
>   at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1054) 
> 
>   at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1094) 
> 
>   at hudson.scm.SCM.checkout(SCM.java:495) 
> 
>   at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) 
> 
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
>  
> 
>   at 
> jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) 
> 
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) 
> 
>   at hudson.model.Run.execute(Run.java:1720) 
> 
>   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 
> 
>   at hudson.model.ResourceController.execute(ResourceController.java:98) 
> 
>   at hudson.model.Executor.run(Executor.java:404) 
> 
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
>
> 

Re: Having problem in importing the code from Github to Jenkins.

2017-01-11 Thread Mark Waite
You're using an scp / ssh connection, but seem to be hinting that you may
be using a username / password credential.  If you're using an scp / ssh
connection, then you need to use a private key credential.

If a username / password credential is required, then you'll need to use
https to connect to the repository.

Mark Waite

On Wed, Jan 11, 2017 at 9:51 PM Sathish M  wrote:

> Yeah okay,
> In Github,
>  I have created an account in GitHub.
> In Jenkins,
>  I added the needed Github plugins into my jenkins. And I added
> the credentials for my GitHub account and also the api credentials. And I
> tested the connection in manage jenkins->configuresystem. It succeeded. And
> I created a new job & In general tab I checked the Github project & gave
> the http link to my repo.
> In SCM I gave the repo SSH link and the added the api credential. And I am
> getting the error  (I have attached that )
>
>
> 
>
> Please help me with this.
>
>
> On Thursday, January 12, 2017 at 9:57:02 AM UTC+5:30, Ramanathan Muthaiah
> wrote:
>
> On Wednesday, January 11, 2017 at 2:45:26 PM UTC+5:30, Sathish M wrote:
>
> I am new to Jenkins. I've been learning it by myself, as of now I know to
> create a job & build it when my source code is in my local system. Now I am
> trying to work the same from Jenkins. I've been trying it but I can't get
> that. Can you help me to work here with Github.
>
>
> Ram : There are plenty of resources on the Internet regd Jenkins
> integration with GitHub.
>
> It will help if you can list what did you try and what did not work
> including tool or plugin versions.
>
> /Ram
>
> --
> 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/0654cd37-0cd6-4273-97dd-6cc3037d00a5%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/CAO49JtH-V%2Bu_G0rkLuG67Lp4-%2B8L0oyL4VkL8WDVHq%2Bq0yABhA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Having problem in importing the code from Github to Jenkins.

2017-01-11 Thread Sathish M
Yeah okay,
In Github,
 I have created an account in GitHub.
In Jenkins,
 I added the needed Github plugins into my jenkins. And I added the 
credentials for my GitHub account and also the api credentials. And I 
tested the connection in manage jenkins->configuresystem. It succeeded. And 
I created a new job & In general tab I checked the Github project & gave 
the http link to my repo. 
In SCM I gave the repo SSH link and the added the api credential. And I am 
getting the error  (I have attached that )



Please help me with this.


On Thursday, January 12, 2017 at 9:57:02 AM UTC+5:30, Ramanathan Muthaiah 
wrote:
>
> On Wednesday, January 11, 2017 at 2:45:26 PM UTC+5:30, Sathish M wrote:
>>
>> I am new to Jenkins. I've been learning it by myself, as of now I know to 
>> create a job & build it when my source code is in my local system. Now I am 
>> trying to work the same from Jenkins. I've been trying it but I can't get 
>> that. Can you help me to work here with Github.
>>
>
> Ram : There are plenty of resources on the Internet regd Jenkins 
> integration with GitHub.
>
> It will help if you can list what did you try and what did not work 
> including tool or plugin versions.
>
> /Ram
>

-- 
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/0654cd37-0cd6-4273-97dd-6cc3037d00a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Having problem in importing the code from Github to Jenkins.

2017-01-11 Thread Ramanathan Muthaiah
On Wednesday, January 11, 2017 at 2:45:26 PM UTC+5:30, Sathish M wrote:
>
> I am new to Jenkins. I've been learning it by myself, as of now I know to 
> create a job & build it when my source code is in my local system. Now I am 
> trying to work the same from Jenkins. I've been trying it but I can't get 
> that. Can you help me to work here with Github.
>

Ram : There are plenty of resources on the Internet regd Jenkins 
integration with GitHub.

It will help if you can list what did you try and what did not work 
including tool or plugin versions.

/Ram

-- 
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/5ec04edd-c253-4cc2-b6e9-fc3985a52d00%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Help me with this error

2017-01-11 Thread Sathish M
Sorry I didn't get you.

On Thursday, January 12, 2017 at 12:45:15 AM UTC+5:30, Mark Waite wrote:
>
> The output
>
> >  init C:\Users\User\.jenkins\workspace\test-git # timeout=10
>
> usually means that you've made a system configuration error.  You've 
> probably defined the name of the git executable as an empty field or empty 
> string.  That line should have been:
>
> >  git init C:\Users\User\.jenkins\workspace\test-git # timeout=10
>
> and since the command name "git" is missing from the output, it likely 
> means that you defined your git executable as the empty string.
>
> If the system configuration page which prompts for the git executable name 
> doesn't show an empty field as an error, please submit an enhancement 
> request to make that field warn if it is empty.
>
> Mark Waite
>
> On Wed, Jan 11, 2017 at 10:31 AM  
> wrote:
>
>> Is Git properly installed on your Jenkins server?
>>
>>
>> https://support.cloudbees.com/hc/en-us/articles/218156697-Git-Failed-to-connect-to-repository-Could-not-init-tmp
>>
>> On Wednesday, January 11, 2017 at 7:19:44 AM UTC-5, Sathish M wrote:
>>>
>>>
>>> Failed to connect to repository : Error performing command:  ls-remote -h 
>>> g...@github.com:
>>>
>>>
>>> and 
>>>
>>>
>>>
>>> Started by user Administrator 
>>> Building on master in workspace C:\Users\User\.jenkins\workspace\test-git
>>> Cloning the remote Git repository
>>> Cloning repository g...@github.com:/ant_1
>>>  >  init C:\Users\User\.jenkins\workspace\test-git # timeout=10
>>> ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException 
>>> :
>>>  Could not init C:\Users\User\.jenkins\workspace\test-git
>>> at 
>>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:666)
>>>  
>>> 
>>> at 
>>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:467)
>>>  
>>> 
>>> at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1054) 
>>> 
>>> at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1094) 
>>> 
>>> at hudson.scm.SCM.checkout(SCM.java:495) 
>>> 
>>> at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) 
>>> 
>>> at 
>>> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
>>>  
>>> 
>>> at 
>>> jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) 
>>> 
>>> at 
>>> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
>>>  
>>> 
>>> at hudson.model.Run.execute(Run.java:1720) 
>>> 
>>> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 
>>> 
>>> at hudson.model.ResourceController.execute(ResourceController.java:98) 
>>> 
>>> at hudson.model.Executor.run(Executor.java:404) 
>>> 
>>>
>>> -- 
>> 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/be631749-8b2c-49c3-9c40-7500f3fa403d%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 

Re: Help me with this error

2017-01-11 Thread Sathish M
yes

On Wednesday, January 11, 2017 at 11:01:38 PM UTC+5:30, 
harold...@lexmark.com wrote:
>
> Is Git properly installed on your Jenkins server?
>
>
> https://support.cloudbees.com/hc/en-us/articles/218156697-Git-Failed-to-connect-to-repository-Could-not-init-tmp
>
> On Wednesday, January 11, 2017 at 7:19:44 AM UTC-5, Sathish M wrote:
>>
>>
>> Failed to connect to repository : Error performing command:  ls-remote -h 
>> g...@github.com:
>>
>>
>> and 
>>
>>
>>
>> Started by user Administrator 
>> Building on master in workspace C:\Users\User\.jenkins\workspace\test-git
>> Cloning the remote Git repository
>> Cloning repository g...@github.com:/ant_1
>>  >  init C:\Users\User\.jenkins\workspace\test-git # timeout=10
>> ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException 
>> :
>>  Could not init C:\Users\User\.jenkins\workspace\test-git
>>  at 
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:666)
>>  
>> 
>>  at 
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:467)
>>  
>> 
>>  at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1054) 
>> 
>>  at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1094) 
>> 
>>  at hudson.scm.SCM.checkout(SCM.java:495) 
>> 
>>  at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) 
>> 
>>  at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
>>  
>> 
>>  at 
>> jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) 
>> 
>>  at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
>>  
>> 
>>  at hudson.model.Run.execute(Run.java:1720) 
>> 
>>  at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 
>> 
>>  at hudson.model.ResourceController.execute(ResourceController.java:98) 
>> 
>>  at hudson.model.Executor.run(Executor.java:404) 
>> 
>>
>>

-- 
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/74c553e2-584b-431c-9a74-cbec89038aef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Declarative Pipeline] Non-executed stages report success

2017-01-11 Thread Andrew Bayer
That's a good question - I'll look into that.

A.

On Wed, Jan 11, 2017 at 3:00 PM Chris Carson  wrote:

> https://issues.jenkins-ci.org/browse/JENKINS-41009
>
> Is there a way to access these failure tags from rest api?
>
>
> On Wednesday, January 4, 2017 at 11:50:10 AM UTC-6, Andrew Bayer wrote:
>
> That's actually addressed with Blue Ocean - we mark failed stages with a
> special tag that Blue Ocean knows to treat as a failure. I think we could
> probably do the same in stage view - could you possibly open a JIRA for
> that? Thanks!
>
> A.
>
> On Jan 3, 2017 15:52, "Chris Carson"  wrote:
>
> I am trying out the Declarative Pipeline
>  and
> noticed some odd behavior in reporting. In the current Scripted Pipeline
> behavior when a stage fails the pipeline stops and reports as failed,
> however, in Declarative Pipelines the stages that don't run any steps,
> either by the 'when' block expression being false or previous stage
> failing/aborting, report the following: start stage -> end stage -> reports
> the stage as success -> ... -> reports the overall build as a failure.
>
> Example:
>
>
>
> Is this a design decision and if so can the stages be instead reported as
> "not executed" instead of "success"?
>
>
>
>
>
>
>
>
>
>
> --
>
>
> 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/bd5fa631-5e70-440d-a2e3-6d9dd2e184da%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/07a4a307-73f5-4c72-8d84-535437d5fcea%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/CAPbPdOZ5SN2uB0xTtDSN2atuGy5p9-BCUgF%3DMw%3DeDQDCsLQuog%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Git Plugin - Merge before build, push on success and delete branch after

2017-01-11 Thread Mark Waite
If the repository is only accessible with a private key (RSA
authentication), then you'll need to make that private key available to the
job while it is running.  You may need to launch an ssh-agent from within
the job, or you might experiment with the ssh-agent plugin to see if it
could assist you.

You might also consider deleting the branch in a downstream job which runs
on a node dedicated to the "delete branch" task.

Mark Waite

On Wed, Jan 11, 2017 at 3:58 PM Robert Berta  wrote:

> Hi folks,
>
> I using Git Plugin 3.0.1.
> I selected merge before build option and specified the feature branch name
> I want to merge into master.
> After build is done the changes are pushed back to master .
> Now I want to delete the feature branch. I lost more than a day trying out
> a shell step to delete the branch. I failed because I need RSA
> authentification and can't change the user I run the job with.
> Help !!!
>
> Cheers,
> Robert
>
> --
> 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/765cc70a-7b07-4b5d-96bf-97f950d3660b%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/CAO49JtFmkMRnWU%2B26KDGfDp4VszFKwvNOK-sWn6335cGWq6gcQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: How to trigger Jenkins build with parameters from Gitlab webhook?

2017-01-11 Thread Indra Gunawan (ingunawa)
It should be “echo MYPARAM: ${env.MYPARAM}” in pipeline


From:  on behalf of Mark Allison 

Reply-To: "jenkinsci-users@googlegroups.com" 
Date: Wednesday, January 11, 2017 at 2:58 PM
To: Jenkins Users 
Subject: Re: How to trigger Jenkins build with parameters from Gitlab webhook?

I have defined it outside of the pipeline script in the This project is 
parameterised section. Is that what you mean? I haven't defined anything in the 
pipeline itself. Do I need to do it there? If so, what is the syntax?

Thanks

On Monday, 9 January 2017 18:41:36 UTC, David Karr wrote:
I'm not sure if this matters, but did you define that parameter in the
pipeline job?

On Mon, Jan 9, 2017 at 3:02 AM, Mark Allison  
wrote:
> I have GitLab Community Edition 8.15.2 successfully trigger pipeline
> projects in Jenkins 2.32.1 using a webhook (but without any parameters). I
> want the gitlab push to trigger a build with parameters but the parameter
> value is null when it comes through to Jenkins so the build fails.
>
> The gitlab webhook looks like:
>
> http://jenkins.server:8080/project/project-a/buildWithParameters?MYPARAM=foo
>
>
> In my pipeline project I echo the parameter value out with
>
> echo "MYPARAM: ${MYPARAM}"
>
>
> and it's not set to anything. Any ideas on where I've gone wrong?
>
> --
> 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/058c423d-150e-4f17-99ca-aa0dfc2c5d50%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/bf8683f8-6f93-454f-9c2c-dbf867d70adb%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/115AB43B-F963-408E-815C-A1115C0E1E93%40cisco.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Declarative Pipeline] Non-executed stages report success

2017-01-11 Thread Chris Carson
https://issues.jenkins-ci.org/browse/JENKINS-41009

Is there a way to access these failure tags from rest api?

On Wednesday, January 4, 2017 at 11:50:10 AM UTC-6, Andrew Bayer wrote:
>
> That's actually addressed with Blue Ocean - we mark failed stages with a 
> special tag that Blue Ocean knows to treat as a failure. I think we could 
> probably do the same in stage view - could you possibly open a JIRA for 
> that? Thanks! 
>
> A. 
>
> On Jan 3, 2017 15:52, "Chris Carson"  
> wrote:
>
>> I am trying out the Declarative Pipeline 
>>  and 
>> noticed some odd behavior in reporting. In the current Scripted Pipeline 
>> behavior when a stage fails the pipeline stops and reports as failed, 
>> however, in Declarative Pipelines the stages that don't run any steps, 
>> either by the 'when' block expression being false or previous stage 
>> failing/aborting, report the following: start stage -> end stage -> reports 
>> the stage as success -> ... -> reports the overall build as a failure.
>>
>> Example:
>>
>>
>>
>> Is this a design decision and if so can the stages be instead reported as 
>> "not executed" instead of "success"?
>>
>>
>> -- 
>> 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/bd5fa631-5e70-440d-a2e3-6d9dd2e184da%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/07a4a307-73f5-4c72-8d84-535437d5fcea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Git Plugin - Merge before build, push on success and delete branch after

2017-01-11 Thread Robert Berta
Hi folks,

I using Git Plugin 3.0.1.
I selected merge before build option and specified the feature branch name 
I want to merge into master.
After build is done the changes are pushed back to master . 
Now I want to delete the feature branch. I lost more than a day trying out 
a shell step to delete the branch. I failed because I need RSA 
authentification and can't change the user I run the job with.
Help !!!

Cheers,
Robert

-- 
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/765cc70a-7b07-4b5d-96bf-97f950d3660b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: How to trigger Jenkins build with parameters from Gitlab webhook?

2017-01-11 Thread Mark Allison
I have defined it outside of the pipeline script in the *This project is 
parameterised section*. Is that what you mean? I haven't defined anything 
in the pipeline itself. Do I need to do it there? If so, what is the syntax?

Thanks

On Monday, 9 January 2017 18:41:36 UTC, David Karr wrote:
>
> I'm not sure if this matters, but did you define that parameter in the 
> pipeline job? 
>
> On Mon, Jan 9, 2017 at 3:02 AM, Mark Allison  > wrote: 
> > I have GitLab Community Edition 8.15.2 successfully trigger pipeline 
> > projects in Jenkins 2.32.1 using a webhook (but without any parameters). 
> I 
> > want the gitlab push to trigger a build with parameters but the 
> parameter 
> > value is null when it comes through to Jenkins so the build fails. 
> > 
> > The gitlab webhook looks like: 
> > 
> > 
> http://jenkins.server:8080/project/project-a/buildWithParameters?MYPARAM=foo 
> > 
> > 
> > In my pipeline project I echo the parameter value out with 
> > 
> > echo "MYPARAM: ${MYPARAM}" 
> > 
> > 
> > and it's not set to anything. Any ideas on where I've gone wrong? 
> > 
> > -- 
> > 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/058c423d-150e-4f17-99ca-aa0dfc2c5d50%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/bf8683f8-6f93-454f-9c2c-dbf867d70adb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: How to use Jenkinsfile in pipeline builds?

2017-01-11 Thread Mark Allison
Actually this works fine, ignore. I had misconfigured something.

On Wednesday, 11 January 2017 20:10:36 UTC, Mark Allison wrote:
>
> I have a pipeline build and I want to move it to source control. I've 
> copied out the script from the the project into a Jenkinsfile and added it 
> to git. In my pipeline I have code like this:
>
> #!groovy​
> node {
>
> stage('checkout') {
>
> deleteDir()
> git 'http://git.server/markallison/my-project.git'
> }
> 
> stage('build') {
> // build code
>
>
> }
>
>
> ... etc
>
> I like to have a clean workspace every time the build runs, so how do I do 
> this without having to have a separate project for my Jenkinsfile? 
>
>

-- 
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/7c6c8d1a-7ff1-41bb-b329-8c6e580d99ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[Jenkins World 2017]: Call for Paper is OPEN

2017-01-11 Thread Alyssa Tong
Hello,

The events team has already began the planning for the annual Jenkins World
 conference.
This year it will take place in San Francisco, California on 28 - 31
August.  The Call for Papers is currently open
 with the last day for
submission on Sunday 5 March.

If you have an inspiring Jenkins story, pls submit
.

BR,
alyssa

-- 
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/CAC9wNay%2B-LSAjkicnSLVut8rAVMbyQPvHfRrnSxy4mz8ZJuWTg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Issues with role-strategy plugin on 2.32.1

2017-01-11 Thread Francisca Munhoz
I have upgraded from 2.7.1 to 2.32.1 yesterday, and I got this message 
about RoleBasedAuthorizationStrategy:

Does anyone had this issue before? 

I was using role-strategy:2.3.2 on 2.7.1 and it did not changed for 2.32.1


hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: 
java.io.IOException: Unable to read /home/jenkins/config.xml
at hudson.WebAppMain$3.run(WebAppMain.java:248)
Caused by: org.jvnet.hudson.reactor.ReactorException: java.io.IOException: 
Unable to read /home/jenkins/config.xml
at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269)
at jenkins.InitReactorRunner.run(InitReactorRunner.java:47)
at jenkins.model.Jenkins.executeReactor(Jenkins.java:1110)
at jenkins.model.Jenkins.(Jenkins.java:926)
at hudson.model.Hudson.(Hudson.java:85)
at hudson.model.Hudson.(Hudson.java:81)
at hudson.WebAppMain$3.run(WebAppMain.java:231)
Caused by: java.io.IOException: Unable to read /home/jenkins/config.xml
at hudson.XmlFile.unmarshal(XmlFile.java:161)
at jenkins.model.Jenkins.loadConfig(Jenkins.java:3015)
at jenkins.model.Jenkins.access$1100(Jenkins.java:326)
at jenkins.model.Jenkins$16.run(Jenkins.java:3033)
at 
org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
at jenkins.model.Jenkins$7.runTask(Jenkins.java:1086)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
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)
Caused by: jenkins.util.xstream.CriticalXStreamException: 
com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy : 
com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy
 Debugging information 
message : 
com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy
cause-exception : 
com.thoughtworks.xstream.mapper.CannotResolveClassException
cause-message   : 
com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy
class   : hudson.model.Hudson
required-type   : hudson.model.Hudson
converter-type  : hudson.util.RobustReflectionConverter
path: /hudson/authorizationStrategy
line number : 8
version : not available
---
at 
hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:356)
at 
hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:270)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)
at 
com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134)
at 
com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32)
at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1189)
at hudson.util.XStream2.unmarshal(XStream2.java:114)
at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1173)
at hudson.XmlFile.unmarshal(XmlFile.java:159)
... 11 more
Caused by: com.thoughtworks.xstream.mapper.CannotResolveClassException: 
com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy
at 
com.thoughtworks.xstream.mapper.DefaultMapper.realClass(DefaultMapper.java:79)
at 
com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
at 
com.thoughtworks.xstream.mapper.DynamicProxyMapper.realClass(DynamicProxyMapper.java:55)
at 
com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
at 
com.thoughtworks.xstream.mapper.PackageAliasingMapper.realClass(PackageAliasingMapper.java:88)
at 
com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
at 
com.thoughtworks.xstream.mapper.ClassAliasingMapper.realClass(ClassAliasingMapper.java:79)
at 
com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
at 
com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
at 
com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
at 
com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30)
at 

Re: Github Organization and credentials

2017-01-11 Thread Justin Knowles
Well after messing with this for days I magically got it working once I 
posted this. The fix for me was a combination of my github org config and 
my Jenkinsfile. In the github org I went to my org -> configure -> 
repository sources (github organization) -> advanced and changed "checkout 
credentials" from "-same as scan credentials-" to explicitly be the same 
credentials I used for the scan credentials.

My Jenkinsfile was changed to:

*node {*
*  checkout scm*

*stage('Test (verify)') {*
*  withMaven(*
*  maven: 'maven3',*
*  mavenLocalRepo: '.repository') {*
*sh "mvn clean install"*
*  }*
*}*
*}*


On Wednesday, January 11, 2017 at 3:12:23 PM UTC-5, Justin Knowles wrote:
>
> Hello. I'm having an issue creating a Github Organization (GO from now on) 
> and also not quite understanding how credentials (the plugin) fit into all 
> this. I think I understand that credentials via the plugin can be siloed 
> into different groups or folders for access control purposes. I have a few 
> credentials in jenkins/global (ie at the URL /credentials), and another 
> scoped to "Jenkins", of which some of the global ones should have 
> sufficient permissions for the GO plugin, but after creating my new GO 
> they're not listed (the list only shows "-none-") and I'm shown a 
> "Credentials 
> are recommended" message. 
>
> Saving my newly created GO kicks off the folder computation process which 
> does nothing because its trying to use anonymous access, and revisiting its 
> settings page still doesn't show any credentials global or otherwise. Ok, 
> understandable. 
>
> From my GO/settings page I have the option of adding credentials with two 
> options: folder credentials provider (by the name of my new GO) and Jenkins 
> credentials provider (by the name of Jenkins). From here I chose to add 
> credentials using the GO provider by generating a new personal access token 
> in github with these permissions: 
>
> * repo  Full control of private repositories*
> *  repo:status  Access commit status*
> *  repo_deployment  Access deployment status*
> *  public_repo*
>
> * admin:repo_hook  Full control of repository hooks*
> *  write:repo_hook  Write repository hooks*
> *  read:repo_hook  Read repository hooks*
>
> * admin:org_hook  Full control of organization hooks*
>
> Those may be too wide, but whatever, I think they're enough? I select 
> those creds, apply the changes, and start folder computation, and now it 
> sees everything. Awesome. As a test I have just one branch in one repo with 
> a Jenkinsfile and this is it:
>
> *node {*
> *  // git url: 'https://github.com/COMPANY/COMPANY-java-core.git 
> '*
>
> *  stage('Test (verify)') {*
> *withMaven(*
> *  maven: 'maven3',*
> *  mavenLocalRepo: '.repository') {*
> *sh "mvn clean install"*
> *}*
> *  }*
> *}*
>
> With and without that git url has returned different errors, I can go back 
> and find out what they were if it matters. Regardless, with it how it is 
> now if I go to a detected branch and look at the log for what it tried to 
> do using the Jenkins file, I see this: 
> https://gist.githubusercontent.com/jayceekay/20a9797de5fa76a8b444cefc2cf65674/raw/21b507979df4acff83a5609204505d3e6e4bece2/log
>
> Namely, to clone the repo it does:
>
> Connecting to https://api.github.com using ME/** (COMPANY github 
> organization token)
> Cloning the remote Git repository
> Cloning repository https://github.com/COMPANY/COMPANY-java-core.git
>
>
> But then later I see:
>
> Fetching upstream changes from 
> https://github.com/COMPANY/COMPANY-java-core.git
> using GIT_ASKPASS to set credentials COMPANY github organization token
>  > git fetch --tags --progress 
> https://github.com/COMPANY/COMPANY-java-core.git 
> +refs/heads/*:refs/remotes/origin/*
>  > git config remote.origin1.url 
> https://github.com/COMPANY/COMPANY-java-core.git # timeout=10
> Fetching upstream changes from 
> https://github.com/COMPANY/COMPANY-java-core.git
> using GIT_ASKPASS to set credentials COMPANY github organization token
>  > git fetch --tags --progress 
> https://github.com/COMPANY/COMPANY-java-core.git 
> +refs/pull/*/head:refs/remotes/origin/pr/*
> Checking out Revision some_commit_hash (ME/jenkinsfile-test)
>  > git config core.sparsecheckout # timeout=10
>  > git checkout -f some_commit_hash
>
>
> 1. it seems like its doing the same thing more than once
> 2. rather than default to the credentials I gave it it's defaulting to 
> asking for a password
>
> I've read online that from here I can go into individual repositories that 
> were found and tweak the Github plugin settings (under advanced) and change 
> the checkout credentials to be different from the scan credentials, which I 
> can see and change, but cannot actually *save*? 
>
> All suggestions welcome!
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins 

Github Organization and credentials

2017-01-11 Thread Justin Knowles
Hello. I'm having an issue creating a Github Organization (GO from now on) 
and also not quite understanding how credentials (the plugin) fit into all 
this. I think I understand that credentials via the plugin can be siloed 
into different groups or folders for access control purposes. I have a few 
credentials in jenkins/global (ie at the URL /credentials), and another 
scoped to "Jenkins", of which some of the global ones should have 
sufficient permissions for the GO plugin, but after creating my new GO 
they're not listed (the list only shows "-none-") and I'm shown a "Credentials 
are recommended" message. 

Saving my newly created GO kicks off the folder computation process which 
does nothing because its trying to use anonymous access, and revisiting its 
settings page still doesn't show any credentials global or otherwise. Ok, 
understandable. 

>From my GO/settings page I have the option of adding credentials with two 
options: folder credentials provider (by the name of my new GO) and Jenkins 
credentials provider (by the name of Jenkins). From here I chose to add 
credentials using the GO provider by generating a new personal access token 
in github with these permissions: 

* repo  Full control of private repositories*
*  repo:status  Access commit status*
*  repo_deployment  Access deployment status*
*  public_repo*

* admin:repo_hook  Full control of repository hooks*
*  write:repo_hook  Write repository hooks*
*  read:repo_hook  Read repository hooks*

* admin:org_hook  Full control of organization hooks*

Those may be too wide, but whatever, I think they're enough? I select those 
creds, apply the changes, and start folder computation, and now it sees 
everything. Awesome. As a test I have just one branch in one repo with a 
Jenkinsfile and this is it:

*node {*
*  // git url: 'https://github.com/COMPANY/COMPANY-java-core.git'*

*  stage('Test (verify)') {*
*withMaven(*
*  maven: 'maven3',*
*  mavenLocalRepo: '.repository') {*
*sh "mvn clean install"*
*}*
*  }*
*}*

With and without that git url has returned different errors, I can go back 
and find out what they were if it matters. Regardless, with it how it is 
now if I go to a detected branch and look at the log for what it tried to 
do using the Jenkins file, I see 
this: 
https://gist.githubusercontent.com/jayceekay/20a9797de5fa76a8b444cefc2cf65674/raw/21b507979df4acff83a5609204505d3e6e4bece2/log

Namely, to clone the repo it does:

Connecting to https://api.github.com using ME/** (COMPANY github 
organization token)
Cloning the remote Git repository
Cloning repository https://github.com/COMPANY/COMPANY-java-core.git


But then later I see:

Fetching upstream changes from https://github.com/COMPANY/COMPANY-java-core.git
using GIT_ASKPASS to set credentials COMPANY github organization token
 > git fetch --tags --progress https://github.com/COMPANY/COMPANY-java-core.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin1.url 
 > https://github.com/COMPANY/COMPANY-java-core.git # timeout=10
Fetching upstream changes from https://github.com/COMPANY/COMPANY-java-core.git
using GIT_ASKPASS to set credentials COMPANY github organization token
 > git fetch --tags --progress https://github.com/COMPANY/COMPANY-java-core.git 
 > +refs/pull/*/head:refs/remotes/origin/pr/*
Checking out Revision some_commit_hash (ME/jenkinsfile-test)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f some_commit_hash


1. it seems like its doing the same thing more than once
2. rather than default to the credentials I gave it it's defaulting to 
asking for a password

I've read online that from here I can go into individual repositories that 
were found and tweak the Github plugin settings (under advanced) and change 
the checkout credentials to be different from the scan credentials, which I 
can see and change, but cannot actually *save*? 

All suggestions welcome!

-- 
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/668c27ca-517e-4823-9d83-05a37906cb35%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


How to use Jenkinsfile in pipeline builds?

2017-01-11 Thread Mark Allison
I have a pipeline build and I want to move it to source control. I've 
copied out the script from the the project into a Jenkinsfile and added it 
to git. In my pipeline I have code like this:

#!groovy​
node {

stage('checkout') {

deleteDir()
git 'http://git.server/markallison/my-project.git'
}

stage('build') {
// build code


}

   
... etc

I like to have a clean workspace every time the build runs, so how do I do 
this without having to have a separate project for my Jenkinsfile? 
   

-- 
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/0cf05e7f-0f14-4f5f-94d6-0995b33ac500%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Help me with this error

2017-01-11 Thread Mark Waite
The output

>  init C:\Users\User\.jenkins\workspace\test-git # timeout=10

usually means that you've made a system configuration error.  You've
probably defined the name of the git executable as an empty field or empty
string.  That line should have been:

>  git init C:\Users\User\.jenkins\workspace\test-git # timeout=10

and since the command name "git" is missing from the output, it likely
means that you defined your git executable as the empty string.

If the system configuration page which prompts for the git executable name
doesn't show an empty field as an error, please submit an enhancement
request to make that field warn if it is empty.

Mark Waite

On Wed, Jan 11, 2017 at 10:31 AM  wrote:

> Is Git properly installed on your Jenkins server?
>
>
> https://support.cloudbees.com/hc/en-us/articles/218156697-Git-Failed-to-connect-to-repository-Could-not-init-tmp
>
> On Wednesday, January 11, 2017 at 7:19:44 AM UTC-5, Sathish M wrote:
>
>
> Failed to connect to repository : Error performing command:  ls-remote -h 
> g...@github.com:
>
>
> and
>
>
>
> Started by user Administrator 
> Building on master in workspace C:\Users\User\.jenkins\workspace\test-git
> Cloning the remote Git repository
> Cloning repository g...@github.com:/ant_1
>  >  init C:\Users\User\.jenkins\workspace\test-git # timeout=10
> ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException 
> :
>  Could not init C:\Users\User\.jenkins\workspace\test-git
>   at 
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:666)
>  
> 
>   at 
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:467)
>  
> 
>   at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1054) 
> 
>   at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1094) 
> 
>   at hudson.scm.SCM.checkout(SCM.java:495) 
> 
>   at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) 
> 
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
>  
> 
>   at 
> jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) 
> 
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) 
> 
>   at hudson.model.Run.execute(Run.java:1720) 
> 
>   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 
> 
>   at hudson.model.ResourceController.execute(ResourceController.java:98) 
> 
>   at hudson.model.Executor.run(Executor.java:404) 
> 
>
> --
> 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/be631749-8b2c-49c3-9c40-7500f3fa403d%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/CAO49JtEyYvpv-kYa2O0O5%3Doa027idnK5CsTz%3DvbJ8UHCwi_6HQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Running Job from pipleline - old code is excuted

2017-01-11 Thread Peter McNab
I saw a case like then after I changed the name of my Jenkinsfile, but 
forgot to update the filename in the "script to execute" part of the job 
configuration.


Somewhat surprised to see that my workspace wasn't being cleaned between 
jobs, but it had me scratching my head for a bit.


Pete



On 1/11/2017 8:00 AM, Boaz Nahum wrote:

Hi.

I'm using Jenkins 2.32.1 running on WIndows Server

The jenkinsfile that describe the pipeline is something like this:
|
node('boaz'){
|

println "Hello from node ${env.NODE_NAME}"

stage('preparation') {

node('boaz') {

def parameters = [

[$class: 'StringParameterValue', name: 
'param_sandbox_path', value: '${sandboxPath}']



];

build job: "periodic-build-1-preparation", parameters: 
parameters

}
}
}

I'm not using SCM to create workspace.

The job "periodic-build-1-preparation" The job is freestyle job with 
one build step which is shell script
The job started and run as expected. Then I change it, but no matter 
what I tried to do -*the old job code is running*. I know it because 
it is shell script that echo the commands before running.


Thanks
Boaz





--
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/7bed6558-fce2-4c26-a7c9-1fb91a3ab02d%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/3d1f8f92-241d-69cd-ce1d-d6a2da198eee%40perforce.com.
For more options, visit https://groups.google.com/d/optout.


Re: Help me with this error

2017-01-11 Thread harold . putman
Is Git properly installed on your Jenkins server?

https://support.cloudbees.com/hc/en-us/articles/218156697-Git-Failed-to-connect-to-repository-Could-not-init-tmp

On Wednesday, January 11, 2017 at 7:19:44 AM UTC-5, Sathish M wrote:
>
>
> Failed to connect to repository : Error performing command:  ls-remote -h 
> g...@github.com :
>
>
> and 
>
>
>
> Started by user Administrator 
> Building on master in workspace C:\Users\User\.jenkins\workspace\test-git
> Cloning the remote Git repository
> Cloning repository g...@github.com:/ant_1
>  >  init C:\Users\User\.jenkins\workspace\test-git # timeout=10
> ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException 
> :
>  Could not init C:\Users\User\.jenkins\workspace\test-git
>   at 
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:666)
>  
> 
>   at 
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:467)
>  
> 
>   at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1054) 
> 
>   at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1094) 
> 
>   at hudson.scm.SCM.checkout(SCM.java:495) 
> 
>   at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) 
> 
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
>  
> 
>   at 
> jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) 
> 
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) 
> 
>   at hudson.model.Run.execute(Run.java:1720) 
> 
>   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 
> 
>   at hudson.model.ResourceController.execute(ResourceController.java:98) 
> 
>   at hudson.model.Executor.run(Executor.java:404) 
> 
>
>

-- 
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/be631749-8b2c-49c3-9c40-7500f3fa403d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Running Job from pipleline - old code is excuted

2017-01-11 Thread Slide
Just curious, why do you have a node() inside of a node()?

On Wed, Jan 11, 2017, 09:01 Boaz Nahum  wrote:

> Hi.
>
> I'm using Jenkins 2.32.1 running on WIndows Server
>
> The jenkinsfile that describe the pipeline is something like this:
> node('boaz') {
>
> println "Hello from node ${env.NODE_NAME}"
>
> stage('preparation') {
>
> node('boaz') {
>
> def parameters = [
>
> [$class: 'StringParameterValue', name:
> 'param_sandbox_path', value: '${sandboxPath}']
>
>
> ];
>
> build job: "periodic-build-1-preparation", parameters:
> parameters
> }
> }
> }
>
> I'm not using SCM to create workspace.
>
> The job "periodic-build-1-preparation" The job is freestyle job with one
> build step which is shell script
> The job started and run as expected. Then I change it, but no matter what
> I tried to do -* the old job code is running*. I know it because it is
> shell script that echo the commands before running.
>
> Thanks
> Boaz
>
>
>
>
>
> --
> 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/7bed6558-fce2-4c26-a7c9-1fb91a3ab02d%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/CAPiUgVdV61hVQ2_%3DZfjGcmfjOqLtwGgF0KxZ5wPPci-P9%2BtWgw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Blue Ocean Parameters

2017-01-11 Thread harold . putman
I have a pipeline build that uses the ExtendedChoice plugin to let a user 
choose which profiles to build from a multimodule maven project.

[ ] Everything
[ ] UI
[ ] Backend
[ ] Admin tools

Blue Ocean does not prompt for parameters when the build is Run, so I 
assume I need to prompt for input. I'm having difficult figuring out the 
magic to allow checkboxes for input. I'm looking at the documentation here 
https://jenkins.io/doc/pipeline/steps/pipeline-input-step/#input-wait-for-interactive-input,
 
but it doesn't provide much help. Are there any examples of different types 
of input?

Here are two inputs that I was able to get working...

def userInput = input(
 id: 'userInput', message: 'Let\'s promote?', parameters: [
 [$class: 'TextParameterDefinition', defaultValue: 'uat', description: 
'Environment', name: 'env'],
 [$class: 'BooleanParameterDefinition', defaultValue: true, description: 
'Target', name: 'target']
]) 

Can anyone point me to others that might support checkboxes?

-- 
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/bd7025d4-b833-4712-a165-ddd784e6c9cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Running Job from pipleline - old code is excuted

2017-01-11 Thread Boaz Nahum
Hi.

I'm using Jenkins 2.32.1 running on WIndows Server

The jenkinsfile that describe the pipeline is something like this:
node('boaz') {

println "Hello from node ${env.NODE_NAME}"

stage('preparation') {

node('boaz') {

def parameters = [

[$class: 'StringParameterValue', name: 
'param_sandbox_path', value: '${sandboxPath}']


];

build job: "periodic-build-1-preparation", parameters: 
parameters
}
}
}

I'm not using SCM to create workspace. 

The job "periodic-build-1-preparation" The job is freestyle job with one 
build step which is shell script
The job started and run as expected. Then I change it, but no matter what I 
tried to do -* the old job code is running*. I know it because it is shell 
script that echo the commands before running.

Thanks
Boaz





-- 
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/7bed6558-fce2-4c26-a7c9-1fb91a3ab02d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Master/Slave requirements

2017-01-11 Thread jerome
Hi,
I would like to know how people are doing to manage the slave requirements 
and installation when having different platform between master and slave.

I'm currently having a very simple setup where my Windows master have 
everything installed on it and no slave.  We are looking at making a Linux 
Master and Windows slaves.

   - Linux Master
   - many Windows slaves
   - different Visual Studio version on slaves
   - I already use Jenkinsfile pipeline, may need to adjust some node stuff

Is it possible to have groovy/python scripts on the master accessible by 
the salve:

   1. do I need to stash them and unstash them at every build?
   2. can I access them directly on the salve by requesting the master?

Is Jenkins plugins on the master accessible on the salves? timestamps, zip 
util, email ...

How one give installed software on the salve or manage them? especially the 
one not handled by Jenkins like Microsoft Visual Studio.
Can I force to have them and keep the installer or archive to deploy them 
on the slave machine (like Python 2.7, Doxygen)?

I also have some lint executable for Windows only, can I store them on the 
Master and deploy them on slvae automaticaly or I need to setup each slave 
manually?

If someone can shed some light on this, I will begin the migration testing 
later this week, but would like to have a better idea before I take a 
plunge into this and not try stuff that are impossible.

Thanks,
Jerome

-- 
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/b7064734-9683-4fb2-92c5-00b38f2328e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Some questions on ArtifactArchiver for a pipeline script

2017-01-11 Thread jerome

Use:
println(pwd());
that should help you determine current working directory.

If the /home/user/project is the current working directory where the 
project is checkout and you are looking at /home/user/artifacts for the zip 
files:

archiveArtifacts artifacts: "../artifacts/**/*.zip", excludes: "
../artifacts/notIncluded/**/*.zip", fingerprint: true, allowEmptyArchive: 
false, onlyIfSuccessful: true;

Note, you don't need the step(([$class:]) wrapper anymore, make it easier 
to read into recent Jenkins. you can also change the path before calling 
archive (I haven't test it but it should work, make it more compact and 
easier to maintain and understand):
dir("../artifacts")
{
  archiveArtifacts artifacts: "**/*.zip" ...
}



-- 
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/ee8e98cd-6527-4e67-9da4-7d47f657b76e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Help me with this error

2017-01-11 Thread Sathish M



Failed to connect to repository : Error performing command:  ls-remote -h 
g...@github.com:


and 



Started by user Administrator 
Building on master in workspace C:\Users\User\.jenkins\workspace\test-git
Cloning the remote Git repository
Cloning repository g...@github.com:/ant_1
 >  init C:\Users\User\.jenkins\workspace\test-git # timeout=10
ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException 
:
 Could not init C:\Users\User\.jenkins\workspace\test-git
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:666) 

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:467) 

at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1054) 

at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1094) 

at hudson.scm.SCM.checkout(SCM.java:495) 

at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) 

at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
 

at 
jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) 

at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) 

at hudson.model.Run.execute(Run.java:1720) 

at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 

at hudson.model.ResourceController.execute(ResourceController.java:98) 

at hudson.model.Executor.run(Executor.java:404) 


-- 
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/54ea81fb-5e3b-4c10-8fdb-426574ba5a06%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Some questions on ArtifactArchiver for a pipeline script

2017-01-11 Thread Kristian
Hey,

I have some questions on the ArtifactArchiver. I have several
projects, where the artifacts are copied into a special directory,
which is not a subfolder of the directory where the source code lies /
where the compilation is done.

For example, my source code lies at /home/user/project and after the
compilation and linking is done, the artifacts (in sometimes they are
already zipped) are copied into /home/user/artifacts.

Now, I want Jenkins pipeline to search there for the artifacts / zip
files. I already tried several ways of finding that directory.

stage('archive') {
step([$class: 'ArtifactArchiver', artifacts:
"**/../artifacts/*", fingerprint: true])

step([$class: 'ArtifactArchiver', artifacts:
"../artifacts/*", fingerprint: true])

step([$class: 'ArtifactArchiver', artifacts:
"**/artifacts/*", fingerprint: true])

step([$class: 'ArtifactArchiver', artifacts:
"artifacts/*", fingerprint: true])

step([$class: 'ArtifactArchiver', artifacts:
"/home/user/artifacts/*", fingerprint: true])
}

None of them worked i.e. the build always failed. What I am doing wrong here?

Another question is: Is there a way to give me some verbose output
when using ArtifactArchiver for debugging purposes?

-- 
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/CAO5HUhMQBEeQm0ghh7oq0vKs-XyMnXhXm8DF4Da3i3r_NeqybQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Problems using jenkins-cli quiet-down -block

2017-01-11 Thread Joe

Hi all,

I want to run some scripts externally that require that all jobs are 
stopped.

I expected the following command to stop new jobs being started, and only 
return once all the jobs in the queue have finished (or reached the end of 
a stage for pipeline and paused):
java -jar jenkins-cli.jar -s IP quiet-down -block
The command does stop new jobs from been started and shows a red banner on 
the web interface, but the command returns straight away, even when a job 
is still running. 
Have I misunderstood the "block" option? 

At the end of the script I was then planning to use: 
java -jar jenkins-cli.jar -s IP cancel-quiet-down 
This always removes the red banner from the web UI but sometime the job 
queue does not restart. 

Using Jenkins version 2.19.4 on Windows 7 running as a service. 

Is there another way to achieve 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/19dea84c-7930-43b8-8ddf-b89bb5a52f41%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Having problem in importing the code from Github to Jenkins.

2017-01-11 Thread Sathish M
I am new to Jenkins. I've been learning it by myself, as of now I know to 
create a job & build it when my source code is in my local system. Now I am 
trying to work the same from Jenkins. I've been trying it but I can't get 
that. Can you help me to work here with Github.

-- 
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/3f0289ed-fc18-4401-a355-c26391292c86%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Memory leak (groovy)

2017-01-11 Thread Сергей Баранов
Thanks for your reply. 
I'v checked this, and found that all our workflow jobs uses SCM, as I know, 
in this mode 'groovy sandbox' enabled with no options.

вторник, 10 января 2017 г., 22:01:50 UTC+3 пользователь Sam K написал:
>
> Is the 'groovy sandbox' checked for all jobs?  If you've allowed groovy 
> code to be executed outside of the sandbox, its possible one of the 
> pipelines is using a non-white-listed groovy command that is bringing down 
> Jenkins server.  Just talking from my personal experience.  
>
> On Friday, January 6, 2017 at 2:17:58 AM UTC-8, Сергей Баранов wrote:
>>
>> Hi all,
>>
>> I have a problem with memory leaks on our Jenkins ver. 2.39 (Pipeline 
>> groovy plugin ver. 2.23). 
>> We have a lot of pipeline jobs, jenkins server crushes 1-2 times a week 
>> and we can't find the reason.
>>
>> I'v created the heap dump and I see a lot of arrays without values 
>> https://i.gyazo.com/fed8f8e9fbd752ad460bda1174f68911.png
>> https://i.gyazo.com/a980b213e6ebfe586c9f0d3ff9a91b84.png
>>
>> How can I detect the cause of this problem?
>>
>> 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/abb36e42-9867-42fa-ad8d-8ede086b17b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.