subject:"git on jenkins"

Re: CI with Git in Jenkins

2020-04-01 Thread Mark Waite

I has assumed that was what you meant.  I assumed the question was, "Should
I specify a (possibly empty) polling interval in the Jenkinsfile on the
branches of my multibranch pipeline?"  My answer is, no, use web hooks as
the better solution.

On Wed, Apr 1, 2020 at 9:04 AM Roland Asmann 
wrote:

> I'm sorry, I guess I wasn't quite clear on what I meant with this last
> question.
>
> What I want to know is if the consensus is to put the *empty* definition
> of the polling in the Jenkinfile (so that configuring a single pipeline
> works) even when using multibranch pipelines?
>
>
> On 30.03.2020 18:55, Mark Waite wrote:
> >
> >
> > On Mon, Mar 30, 2020 at 10:03 AM Roland Asmann  > <mailto:roland.asm...@gmail.com>> wrote:
> >
> > Thanks for the explanation. I do agree, I just thought it a bit weird
> > that there was a difference in behavior...
> >
> > I still would like to know, what the consensus is to writing the
> > Jenkinsfile: add polling or not?
> >
> >
> > Consensus is to not add polling.  The "polling must die" blog post is
> > still applicable, even with Pipeline.  Much better to find a way to have
> > the git repository notify Jenkins that a commit has arrived, rather than
> > having Jenkins periodically ask if a commit has arrived.
> >
> > Major git providers (GitHub, Bitbucket, GitLab, Gitea) provide web hooks
> > that will notify Jenkins.  Many of those webhooks are even automatically
> > managed by Jenkins.  Jenkins servers behind firewalls can use web hook
> > routing tools to receive notifications inside the firewall from a git
> > hosting service outside the firewall.
> >
> > Mark Waite
> >
> > Thanks.
> >
> >
> > On 25.03.2020 14:53, Mark Waite wrote:
> >  > Multibranch pipelines assume that you want to build all branches
> > that
> >  > include a Jenkinsfile any time the notification is received
> through
> >  > notifyCommit or through a Web Hook.  If you do not want one or
> more
> >  > branches built on multibranch pipelines, you'll need to exclude
> > them.
> >  > The Basic Branch Build Strategies plugin (
> >  >
> >
> https://github.com/jenkinsci/basic-branch-build-strategies-plugin/blob/master/docs/user.adoc
> )
> >
> >  > provides many branch selection options.
> >  >
> >  > On Wed, Mar 25, 2020 at 7:39 AM Roland Asmann
> > mailto:roland.asm...@gmail.com>
> >  > <mailto:roland.asm...@gmail.com
> > <mailto:roland.asm...@gmail.com>>> wrote:
> >  >
> >  > Hi everybody,
> >  >
> >  > Way-back-when, Kohsuke wrote this post about how to setup CI
> with
> >  > Git in Jenkins:
> >  >
> >
> https://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/
> >  >
> >  > I have been using this in most my builds since and am still
> > trying
> >  > to get all colleagues to do the same (don't ask, my company
> > can be
> >  > difficult sometimes). Anyway, the other day I noticed that in
> > one of
> >  > my Jenkinsfiles, I forgot to activate the SCM polling.
> > However, this
> >  > project had been building on git pushes since the start!
> >  >
> >  > Doing some testing on my own, I came to the following
> conclusion:
> >  > - Non-pipeline jobs all need to have the polling activated to
> > react
> >  > to the Git hook
> >  > - Single pipeline jobs also need to have polling activated
> >  > - Multibranch pipelines **don't** need to have polling
> activated,
> >  > they just build whenever the git hook sends its request to
> > Jenkins
> >  >
> >  > Now, my question is, is this behavior correct? Does it mean
> > that for
> >  > multibranch pipelines, I **can't** NOT do CI? (Except for
> > removing
> >  > the hook, but that might influence other builds as well!) Is
> this
> >  > actual behavior documented somewhere and did I just miss this
> >  > information?
> >  >
> >  > And what is now the correct way to setup CI? Should I still
> > add the
> >  > polling in my Jenkinsfile or, if I am sure I will be using a
> >  > multibranch pipeline, just leave

Re: CI with Git in Jenkins

2020-04-01 Thread Roland Asmann

I'm sorry, I guess I wasn't quite clear on what I meant with this last 
question.


What I want to know is if the consensus is to put the *empty* definition 
of the polling in the Jenkinfile (so that configuring a single pipeline 
works) even when using multibranch pipelines?



On 30.03.2020 18:55, Mark Waite wrote:



On Mon, Mar 30, 2020 at 10:03 AM Roland Asmann <mailto:roland.asm...@gmail.com>> wrote:


Thanks for the explanation. I do agree, I just thought it a bit weird
that there was a difference in behavior...

I still would like to know, what the consensus is to writing the
Jenkinsfile: add polling or not?


Consensus is to not add polling.  The "polling must die" blog post is 
still applicable, even with Pipeline.  Much better to find a way to have 
the git repository notify Jenkins that a commit has arrived, rather than 
having Jenkins periodically ask if a commit has arrived.


Major git providers (GitHub, Bitbucket, GitLab, Gitea) provide web hooks 
that will notify Jenkins.  Many of those webhooks are even automatically 
managed by Jenkins.  Jenkins servers behind firewalls can use web hook 
routing tools to receive notifications inside the firewall from a git 
hosting service outside the firewall.


Mark Waite

Thanks.


On 25.03.2020 14:53, Mark Waite wrote:
 > Multibranch pipelines assume that you want to build all branches
that
 > include a Jenkinsfile any time the notification is received through
 > notifyCommit or through a Web Hook.  If you do not want one or more
 > branches built on multibranch pipelines, you'll need to exclude
them.
 > The Basic Branch Build Strategies plugin (
 >

https://github.com/jenkinsci/basic-branch-build-strategies-plugin/blob/master/docs/user.adoc)

 > provides many branch selection options.
 >
 > On Wed, Mar 25, 2020 at 7:39 AM Roland Asmann
mailto:roland.asm...@gmail.com>
 > <mailto:roland.asm...@gmail.com
<mailto:roland.asm...@gmail.com>>> wrote:
 >
 >     Hi everybody,
 >
 >     Way-back-when, Kohsuke wrote this post about how to setup CI with
 >     Git in Jenkins:
 >

https://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/
 >
 >     I have been using this in most my builds since and am still
trying
 >     to get all colleagues to do the same (don't ask, my company
can be
 >     difficult sometimes). Anyway, the other day I noticed that in
one of
 >     my Jenkinsfiles, I forgot to activate the SCM polling.
However, this
 >     project had been building on git pushes since the start!
 >
 >     Doing some testing on my own, I came to the following conclusion:
 >     - Non-pipeline jobs all need to have the polling activated to
react
 >     to the Git hook
 >     - Single pipeline jobs also need to have polling activated
 >     - Multibranch pipelines **don't** need to have polling activated,
 >     they just build whenever the git hook sends its request to
Jenkins
 >
 >     Now, my question is, is this behavior correct? Does it mean
that for
 >     multibranch pipelines, I **can't** NOT do CI? (Except for
removing
 >     the hook, but that might influence other builds as well!) Is this
 >     actual behavior documented somewhere and did I just miss this
 >     information?
 >
 >     And what is now the correct way to setup CI? Should I still
add the
 >     polling in my Jenkinsfile or, if I am sure I will be using a
 >     multibranch pipeline, just leave it out?
 >
 >     Thanks.
 >
 >     Roland
 >
 >     --
 >     You received this message because you are subscribed to the
Google
 >     Groups "Jenkins Users" group.
 >     To unsubscribe from this group and stop receiving emails from it,
 >     send an email to jenkinsci-users+unsubscr...@googlegroups.com
<mailto:jenkinsci-users%2bunsubscr...@googlegroups.com>
 >     <mailto:jenkinsci-users+unsubscr...@googlegroups.com
<mailto:jenkinsci-users%2bunsubscr...@googlegroups.com>>.
 >     To view this discussion on the web visit
 >

https://groups.google.com/d/msgid/jenkinsci-users/828bed5a-dda6-4782-82d9-6834b1f0e074%40googlegroups.com
 >   
  <https://groups.google.com/d/msgid/jenkinsci-users/828bed5a-dda6-4782-82d9-6834b1f0e074%40googlegroups.com?utm_medium=email_source=footer>.

 >
 > --
 > You received this message because you are subscribed to a topic
in the
 > Google Groups "Jenkins Users" group.
 > To unsubscribe from this topic, visit
 >
https://groups.google.com/d/

Re: CI with Git in Jenkins

2020-03-30 Thread Mark Waite

On Mon, Mar 30, 2020 at 10:03 AM Roland Asmann 
wrote:

> Thanks for the explanation. I do agree, I just thought it a bit weird
> that there was a difference in behavior...
>
> I still would like to know, what the consensus is to writing the
> Jenkinsfile: add polling or not?
>

Consensus is to not add polling.  The "polling must die" blog post is still
applicable, even with Pipeline.  Much better to find a way to have the git
repository notify Jenkins that a commit has arrived, rather than having
Jenkins periodically ask if a commit has arrived.

Major git providers (GitHub, Bitbucket, GitLab, Gitea) provide web hooks
that will notify Jenkins.  Many of those webhooks are even automatically
managed by Jenkins.  Jenkins servers behind firewalls can use web hook
routing tools to receive notifications inside the firewall from a git
hosting service outside the firewall.

Mark Waite


> Thanks.
>
>
> On 25.03.2020 14:53, Mark Waite wrote:
> > Multibranch pipelines assume that you want to build all branches that
> > include a Jenkinsfile any time the notification is received through
> > notifyCommit or through a Web Hook.  If you do not want one or more
> > branches built on multibranch pipelines, you'll need to exclude them.
> > The Basic Branch Build Strategies plugin (
> >
> https://github.com/jenkinsci/basic-branch-build-strategies-plugin/blob/master/docs/user.adoc)
>
> > provides many branch selection options.
> >
> > On Wed, Mar 25, 2020 at 7:39 AM Roland Asmann  > <mailto:roland.asm...@gmail.com>> wrote:
> >
> > Hi everybody,
> >
> > Way-back-when, Kohsuke wrote this post about how to setup CI with
> > Git in Jenkins:
> >
> https://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/
> >
> > I have been using this in most my builds since and am still trying
> > to get all colleagues to do the same (don't ask, my company can be
> > difficult sometimes). Anyway, the other day I noticed that in one of
> > my Jenkinsfiles, I forgot to activate the SCM polling. However, this
> > project had been building on git pushes since the start!
> >
> > Doing some testing on my own, I came to the following conclusion:
> > - Non-pipeline jobs all need to have the polling activated to react
> > to the Git hook
> > - Single pipeline jobs also need to have polling activated
> > - Multibranch pipelines **don't** need to have polling activated,
> > they just build whenever the git hook sends its request to Jenkins
> >
> > Now, my question is, is this behavior correct? Does it mean that for
> > multibranch pipelines, I **can't** NOT do CI? (Except for removing
> > the hook, but that might influence other builds as well!) Is this
> > actual behavior documented somewhere and did I just miss this
> > information?
> >
> > And what is now the correct way to setup CI? Should I still add the
> > polling in my Jenkinsfile or, if I am sure I will be using a
> > multibranch pipeline, just leave it out?
> >
> > Thanks.
> >
> > Roland
> >
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Jenkins Users" group.
> > To unsubscribe from this group and stop receiving emails from it,
> > send an email to jenkinsci-users+unsubscr...@googlegroups.com
> > <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/jenkinsci-users/828bed5a-dda6-4782-82d9-6834b1f0e074%40googlegroups.com
> > <
> https://groups.google.com/d/msgid/jenkinsci-users/828bed5a-dda6-4782-82d9-6834b1f0e074%40googlegroups.com?utm_medium=email_source=footer
> >.
> >
> > --
> > You received this message because you are subscribed to a topic in the
> > Google Groups "Jenkins Users" group.
> > To unsubscribe from this topic, visit
> >
> https://groups.google.com/d/topic/jenkinsci-users/IDXKJukzJbo/unsubscribe.
> > To unsubscribe from this group and all its topics, send an email to
> > jenkinsci-users+unsubscr...@googlegroups.com
> > <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtF-Hx%3Ds5MvNssLoE5jDnzhhVu4HkuSvosNd_Y9zdoxmrA%40mail.gmail.com
> > <
> https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtF-Hx%3Ds5MvNssLoE5jDnzhhVu4HkuSvosNd_Y9zdoxmrA%40mail.gmail.com?utm_medium=email_source=

Re: CI with Git in Jenkins

2020-03-30 Thread Roland Asmann

Thanks for the explanation. I do agree, I just thought it a bit weird
that there was a difference in behavior...

I still would like to know, what the consensus is to writing the
Jenkinsfile: add polling or not?

Thanks.

On 25.03.2020 14:53, Mark Waite wrote:
Multibranch pipelines assume that you want to build all branches that
include a Jenkinsfile any time the notification is received through
notifyCommit or through a Web Hook. If you do not want one or more
branches built on multibranch pipelines, you'll need to exclude them.
The Basic Branch Build Strategies plugin (
https://github.com/jenkinsci/basic-branch-build-strategies-plugin/blob/master/docs/user.adoc)
provides many branch selection options.

On Wed, Mar 25, 2020 at 7:39 AM Roland Asmann <mailto:roland.asm...@gmail.com>> wrote:

Hi everybody,

Way-back-when, Kohsuke wrote this post about how to setup CI with
Git in Jenkins:

https://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/

I have been using this in most my builds since and am still trying
to get all colleagues to do the same (don't ask, my company can be
difficult sometimes). Anyway, the other day I noticed that in one of
my Jenkinsfiles, I forgot to activate the SCM polling. However, this
project had been building on git pushes since the start!

Doing some testing on my own, I came to the following conclusion:
- Non-pipeline jobs all need to have the polling activated to react
to the Git hook
- Single pipeline jobs also need to have polling activated
- Multibranch pipelines **don't** need to have polling activated,
they just build whenever the git hook sends its request to Jenkins

Now, my question is, is this behavior correct? Does it mean that for
multibranch pipelines, I **can't** NOT do CI? (Except for removing
the hook, but that might influence other builds as well!) Is this
actual behavior documented somewhere and did I just miss this
information?

And what is now the correct way to setup CI? Should I still add the
polling in my Jenkinsfile or, if I am sure I will be using a
multibranch pipeline, just leave it out?

Thanks.

Roland

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

Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to jenkinsci-users+unsubscr...@googlegroups.com
<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit

https://groups.google.com/d/msgid/jenkinsci-users/828bed5a-dda6-4782-82d9-6834b1f0e074%40googlegroups.com

<https://groups.google.com/d/msgid/jenkinsci-users/828bed5a-dda6-4782-82d9-6834b1f0e074%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to a topic in the
Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/jenkinsci-users/IDXKJukzJbo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
jenkinsci-users+unsubscr...@googlegroups.com
<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtF-Hx%3Ds5MvNssLoE5jDnzhhVu4HkuSvosNd_Y9zdoxmrA%40mail.gmail.com
<https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtF-Hx%3Ds5MvNssLoE5jDnzhhVu4HkuSvosNd_Y9zdoxmrA%40mail.gmail.com?utm_medium=email_source=footer>.

--
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/10726501-9ed7-5d86-1147-1a83083c0a29%40gmail.com.

Re: CI with Git in Jenkins

2020-03-25 Thread Mark Waite

Multibranch pipelines assume that you want to build all branches that
include a Jenkinsfile any time the notification is received through
notifyCommit or through a Web Hook.  If you do not want one or more
branches built on multibranch pipelines, you'll need to exclude them.  The
Basic Branch Build Strategies plugin (
https://github.com/jenkinsci/basic-branch-build-strategies-plugin/blob/master/docs/user.adoc)
provides many branch selection options.

On Wed, Mar 25, 2020 at 7:39 AM Roland Asmann 
wrote:

> Hi everybody,
>
> Way-back-when, Kohsuke wrote this post about how to setup CI with Git in
> Jenkins:
> https://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/
>
> I have been using this in most my builds since and am still trying to get
> all colleagues to do the same (don't ask, my company can be difficult
> sometimes). Anyway, the other day I noticed that in one of my Jenkinsfiles,
> I forgot to activate the SCM polling. However, this project had been
> building on git pushes since the start!
>
> Doing some testing on my own, I came to the following conclusion:
> - Non-pipeline jobs all need to have the polling activated to react to the
> Git hook
> - Single pipeline jobs also need to have polling activated
> - Multibranch pipelines **don't** need to have polling activated, they
> just build whenever the git hook sends its request to Jenkins
>
> Now, my question is, is this behavior correct? Does it mean that for
> multibranch pipelines, I **can't** NOT do CI? (Except for removing the
> hook, but that might influence other builds as well!) Is this actual
> behavior documented somewhere and did I just miss this information?
>
> And what is now the correct way to setup CI? Should I still add the
> polling in my Jenkinsfile or, if I am sure I will be using a multibranch
> pipeline, just leave it out?
>
> Thanks.
>
> Roland
>
> --
> 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/828bed5a-dda6-4782-82d9-6834b1f0e074%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/828bed5a-dda6-4782-82d9-6834b1f0e074%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAO49JtF-Hx%3Ds5MvNssLoE5jDnzhhVu4HkuSvosNd_Y9zdoxmrA%40mail.gmail.com.

CI with Git in Jenkins

2020-03-25 Thread Roland Asmann

Hi everybody,

Way-back-when, Kohsuke wrote this post about how to setup CI with Git in
Jenkins:
https://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/

I have been using this in most my builds since and am still trying to get
all colleagues to do the same (don't ask, my company can be difficult
sometimes). Anyway, the other day I noticed that in one of my Jenkinsfiles,
I forgot to activate the SCM polling. However, this project had been
building on git pushes since the start!

Doing some testing on my own, I came to the following conclusion:
- Non-pipeline jobs all need to have the polling activated to react to the
Git hook
- Single pipeline jobs also need to have polling activated
- Multibranch pipelines **don't** need to have polling activated, they just
build whenever the git hook sends its request to Jenkins

Now, my question is, is this behavior correct? Does it mean that for
multibranch pipelines, I **can't** NOT do CI? (Except for removing the
hook, but that might influence other builds as well!) Is this actual
behavior documented somewhere and did I just miss this information?

And what is now the correct way to setup CI? Should I still add the polling
in my Jenkinsfile or, if I am sure I will be using a multibranch pipeline,
just leave it out?

Thanks.

Roland

--
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/828bed5a-dda6-4782-82d9-6834b1f0e074%40googlegroups.com.

Re: Push sources checked out from Gerrit to Git on jenkins Job using pipeline

2020-01-13 Thread Dominic Espiritu

Hi Björn Pedersen,

Thanks for the reply, I will try the first approach you mentioned, I might
also take a look at the gerrit replication feature in the future since I
have one repository that is modified completely in gerrit
and should not be synced with my Git, Im just wondering of its possible
with a wrapper withCredentials to just provide the credentialsId
without the username and password since in my jenkins global credentials
its already stored my username with password?

Thanks,
Dominic


On Tue, 14 Jan 2020 at 15:15, 'Björn Pedersen' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:

> Hi,
>
> Checkout from the source with scm and just add a shell step that does the
> push. Per default the scm implementation also will use the installed
> commandline git client.
> If you need credentials for the push, you can wrap the shell step in a
> withCredentials.
>
> But maybe just using the gerrit replication instead could be  a better
> option.
>
> Björn
>
> Am Dienstag, 14. Januar 2020 06:19:48 UTC+1 schrieb Dominic Espiritu:
>>
>> Hi,
>>
>> I would just like to ask if possible to push updates from my Gerrit
>> repository to Git repository using SCM in jenkins? I only tried doing this
>> on a manual steps from my terminal window, Any suggestions would be a good
>> help.
>>
>> Thanks,
>> Dominic
>>
> --
> 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/2e89c015-febc-4381-a923-fcb08013433d%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAAL0yhmLqY_q2yX-jKaj%3D_n1_OD2xsWCNeW_%2B_05k9%3DBxAmGmQ%40mail.gmail.com.

Re: Push sources checked out from Gerrit to Git on jenkins Job using pipeline

2020-01-13 Thread 'Björn Pedersen' via Jenkins Users

Hi,

Checkout from the source with scm and just add a shell step that does the 
push. Per default the scm implementation also will use the installed 
commandline git client.
If you need credentials for the push, you can wrap the shell step in a 
withCredentials.

But maybe just using the gerrit replication instead could be  a better 
option.

Björn

Am Dienstag, 14. Januar 2020 06:19:48 UTC+1 schrieb Dominic Espiritu:
>
> Hi,
>
> I would just like to ask if possible to push updates from my Gerrit 
> repository to Git repository using SCM in jenkins? I only tried doing this 
> on a manual steps from my terminal window, Any suggestions would be a good 
> help.
>
> Thanks,
> Dominic
>

-- 
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/2e89c015-febc-4381-a923-fcb08013433d%40googlegroups.com.

Push sources checked out from Gerrit to Git on jenkins Job using pipeline

2020-01-13 Thread Dominic Espiritu

Hi,

I would just like to ask if possible to push updates from my Gerrit 
repository to Git repository using SCM in jenkins? I only tried doing this 
on a manual steps from my terminal window, Any suggestions would be a good 
help.

Thanks,
Dominic

-- 
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/b5858828-76a3-4adb-ba6c-02e2272d62bb%40googlegroups.com.

Re: Odd environment problem with git under Jenkins on AIX

2019-04-30 Thread Mark Waite

On Tue, Apr 30, 2019 at 7:02 AM Rich Stephens wrote:


> I would be happy to join the platform group, though I am not sure of what
> assistance I might be.  While I have used Jenkins on Linux, AIX, HPUX, and
> Windows, my experience is limited to simple master setups building a legacy
> C/C++ project.
>
>
Anyone with the skills to maintain an aging AIX environment will certainly
be able to contribute when we're evaluating platform topics.  There are
often interesting subtleties in using Jenkins on a different platform that
can help the community as a whole.

Mark Waite


> Again, thank you for your assistance.
>
> --
> 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/c458b5e6-71aa-48a7-8fc9-cbdf4bcea6c6%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFu74PN8XW8ey_u4Wq4vP3BswFMRNv4XvrzhqU%2B52KhdQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Odd environment problem with git under Jenkins on AIX

2019-04-30 Thread Rich Stephens

Mark,

I am sincerely sorry if my sense of humor offended. I'm not sure why you
thought I was determined to proceed on any particular path. I was willing
to try the master/slave route as you suggested, and I asked a further
question as to whether I would end up having the same problem on the slave
- then I utterly failed to comprehend your answer. My joke was at my own
expense and my own failure to get what you were saying.

I sincerely appreciate your efforts to assist me.

I no longer require any help on this particular topic, however, since I
have since been able to bypass the problem by using the "JGit" mode of the
git plugin, which does not have the problem and has worked well so far.
Although I _am_ having one odd Java error getting thrown at the end of my
builds (I have created a different post on this topic). I have no idea if
the problem would have happened using the native git open of the git
plugin, or whether it's related to the JGit option, since I never got that
far before.

As for my experiences using Jenkins master(s) on AIX, it is limited to this
one machine, for the last 7 years. It has been working fine using Java
1.6 and Jenkins 1.5(something?) for all of that. It was using Mercurial as
its source repository, and our Mercural server is being retired, so I was
mandated to move my source code to git. I then had to go through the
process of upgrading Jenkins and Java so I could use the git plugin. Thus
begins my sad tale.

As for OpenJDK, that was actually my first choice for upgrading. I
searched all over the OpenJDK website for a link to a download for their
JDK8 for AIX, and could not find it. The page I _did_ find, however,
mentioned that OpenJDK8 supports AIX 7.1 and later. The machine I am
working with is on AIX 6.1, and thus could not use the OpenJDK8 port for
AIX even if I could have found it. I cannot upgrade this machine to AIX
7.1. I have to remain compatible to support AIX 6.1 because the software
it is compiling is a legacy product for which my company still gets a
decent amount of license revenue.

I would be happy to join the platform group, though I am not sure of what
assistance I might be. While I have used Jenkins on Linux, AIX, HPUX, and
Windows, my experience is limited to simple master setups building a legacy
C/C++ project.

Again, thank you for your assistance.

--
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/c458b5e6-71aa-48a7-8fc9-cbdf4bcea6c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Odd environment problem with git under Jenkins on AIX

2019-04-26 Thread Mark Waite

On Fri, Apr 26, 2019 at 2:28 PM Rich Stephens  wrote:

> It was a bit of a joke.  I’m sorry if it offended you.
> It didn’t seem to offend anyone actually involved in the conversation, but
> thanks for the tip.
>
>
That was the point where I decided to stop responding to the thread.  You
seemed determined to proceed on the path that you had chosen.  That's your
right, since it is your time that you're investing in your exploration.

I am very interested to hear more about your experiences with Jenkins
masters on AIX.  While the JDK on AIX is JDK 1.8, I believe it is using the
IBM J9 virtual machine rather than the virtual machine provided by
OpenJDK.  I expect many interesting discoveries await you in that
exploration.  I'm aware of Jenkins agents on AIX and Jenkins agents on s390
mainframes (likely all running the IBM J9 virtual machine), but am not
aware of any other users running a Jenkins master on AIX.

If you're interested in the history of the J9 virtual machine, refer to
https://en.wikipedia.org/wiki/OpenJ9.  If you'd like to run a J9 virtual
machine on commodity hardware, refer to https://adoptopenjdk.net/ where you
can download an OpenJ9 based JDK.

If you'd like to join the Jenkins platform Special Interest Group, refer to
https://jenkins.io/sigs/platform/ .  We'd love to have your help as we work
with various platforms and explore various platforms.

Thanks!
Mark Waite

> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/900a6243-75d1-4cb4-bb75-63ee035e2335%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Thanks!
Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtG28aqSfe%3DwpEEgzJt5hhxFrrO4DmFq_m%3DOvg06p0E9cQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Odd environment problem with git under Jenkins on AIX

2019-04-26 Thread Rich Stephens

It was a bit of a joke.  I’m sorry if it offended you.
It didn’t seem to offend anyone actually involved in the conversation, but 
thanks for the tip.

-- 
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/900a6243-75d1-4cb4-bb75-63ee035e2335%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Odd environment problem with git under Jenkins on AIX

2019-04-26 Thread Baptiste Mathus

Le ven. 26 avr. 2019 à 15:20, Rich Stephens  a écrit :

> I fully have no clue what you just said.
>
> "You might, but you won't have git commands executed to scan multibranch
> pipelines, since those are executed on the master."
>
> Can you translate this to English?
>

Please, beware your phrasing. That is certainly not respectful in general,
and even less to people trying to help you for free in their free time.

I suppose and hope that was just an expression misstep.

Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS5rCPrryGXDdy8j_LYph-B-NdqNd%3DjTBzBTZqe8UFPqXA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Odd environment problem with git under Jenkins on AIX

2019-04-26 Thread Rich Stephens

If anyone's still following this, my problem has been solved by simply 
switching the the "JGit" option for the Git plugin.  It's working perfectly.

Thanks for all who provided any information they could.

-- 
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/94f5d79f-1ac7-43b5-a962-f2d798d363d2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Odd environment problem with git under Jenkins on AIX

2019-04-26 Thread Rich Stephens

OK, Googled "Jenkins multibranch pipeline" and "Jenkinsfile".   Still 
doesn't seem to have any bearing on my issue, but thanks for the input.

-- 
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/1fd6ae7d-bfc6-43d8-95d7-90a65ee12af5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Odd environment problem with git under Jenkins on AIX

2019-04-26 Thread Rich Stephens

Again, no clue what you're talking about.

Don't know what a "multibranch pipeline" is, and don't know what a 
Jenkinsfile is and why I would have it checked into my source code, nor how 
it applies to this situation at all?

-- 
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/01edfef6-7a40-4c7a-98f4-1100d2a6e78b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Odd environment problem with git under Jenkins on AIX

2019-04-26 Thread Dirk Heinrichs

Am Freitag, den 26.04.2019, 06:20 -0700 schrieb Rich Stephens:

"You might, but you won't have git commands executed to scan multibranch
pipelines, since those are executed on the master."

If you have Multibranch pipelines, they will scan your git repository for
branches containing a Jenkinsfile and dynamically create jobs for each branch
that meets this criteria. This happens on the master. The created jobs will
then run on whatever agent is configured in the Jenkinsfile.

HTH...

Dirk

Dirk Heinrichs
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
Phone: +49 2226 15966 18
Email: dhein...@opentext.com
Website: www.recommind.de
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan,
Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
This e-mail may contain confidential and/or privileged information. If you are
not the intended recipient (or have received this e-mail in error) please
notify the sender immediately and destroy this e-mail. Any unauthorized
copying, disclosure or distribution of the material in this e-mail is strictly
forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht
gestattet.

--
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/6ece7346f61aa543fe278de162717ab0d58be619.camel%40opentext.com.
For more options, visit https://groups.google.com/d/optout.

Re: Odd environment problem with git under Jenkins on AIX

2019-04-26 Thread Rich Stephens

I fully have no clue what you just said.

"You might, but you won't have git commands executed to scan multibranch 
pipelines, since those are executed on the master."

Can you translate this to English?   Are you saying git won't run on the 
slave AT ALL?  If not, how will it get the source code to compile?

"I assume that adjusting the environment of the agent is simpler and faster 
to test than adjusting the environment of the agent."  

I assume you mean something else, because you just pretty much said that 
you assume apples are different from apples?

"Running the master on Linux (or Windows) allows you to use the same JDK 
that is used by many Jenkins users.  That will reduce the amount of code 
that might detect problems in the IBM JDK on AIX.  It was a preventive 
suggestion for future problems, with some distant hope that it might also 
assist with this specific issue."

I am running the same JDK (at least major/minor version) on all my Jenkins 
environments.  JDK 1.8. Including this AIX one. So...

-- 
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/1bd36946-5d3d-4faa-9e5b-b10847288c35%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Odd environment problem with git under Jenkins on AIX

2019-04-26 Thread Mark Waite

On Fri, Apr 26, 2019 at 6:06 AM Rich Stephens  wrote:

> I was thinking exactly the same thing.  I'd still have the same
> environment problem, either way.
>
>>
>>
You might, but you won't have git commands executed to scan multibranch
pipelines, since those are executed on the master.

I assume that adjusting the environment of the agent is simpler and faster
to test than adjusting the environment of the agent.

Running the master on Linux (or Windows) allows you to use the same JDK
that is used by many Jenkins users.  That will reduce the amount of code
that might detect problems in the IBM JDK on AIX.  It was a preventive
suggestion for future problems, with some distant hope that it might also
assist with this specific issue.


>
>> --
> 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/86743ecd-4ee4-4bcb-8b4e-b80c1586b76c%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEoXY%2B0HfKuH2MAMWW%3DU6W6G0X8h%2B1jyb376QWvaSMHpQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Odd environment problem with git under Jenkins on AIX

2019-04-26 Thread Rich Stephens

I was thinking exactly the same thing.  I'd still have the same environment 
problem, either way.

>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/86743ecd-4ee4-4bcb-8b4e-b80c1586b76c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Odd environment problem with git under Jenkins on AIX

2019-04-26 Thread Dirk Heinrichs

Am Donnerstag, den 25.04.2019, 14:56 -0600 schrieb Mark Waite:

and run an agent on AIX

But wouldn't that still leave him with the env problem on that agent?

Unfortunately I don't have access to an AIX host anymore, so I'm afraid I also
can't help.

Bye...

Dirk

--
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/0cb0a23d30e33733bad4853d7f3de3199a72cc90.camel%40opentext.com.
For more options, visit https://groups.google.com/d/optout.

Re: Odd environment problem with git under Jenkins on AIX

2019-04-25 Thread Mark Waite

Sorry, but no suggestions to offer on how to resolve that issue.

I would suggest that you host the Jenkins master on Linux or Windows and
run an agent on AIX.  Running the master on AIX probably places you in the
"less than 0.1% of all users" category.

On Thu, Apr 25, 2019 at 1:30 PM Rich Stephens  wrote:

> I have finally gotten Jenkins and the git plugin running (I have managed
> to upgrade to Java8).
>
> git works perfectly from the command line.
>
> If I include /opt/freeware/lib into the LIBPATH when starting jenkins,
> when I try to connect to a remove repository, I get basically this error:
>
> OpenSSL version mismatch. Built against 1000105f, you have 10bf
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
>
> Coincidentally, this is the same error that I get if I include
> /opt/freeware/lib in my own LIBPATH.
>
> If I _don't_ include /opt/freeware/lib in the LIBPATH for jenkins, I get:
>
> Failed to connect to repository : Command "git ls-remote -h ssh://
> g...@stash.saas-p.com:7999/optio/core.git HEAD" returned status code 255:
> stdout:
> stderr: exec(): 0509-036 Cannot load program git because of the following
> errors:
> 0509-150   Dependent module /usr/lib/libiconv.a(libiconv.so.2) could not
> be loaded.
> 0509-152   Member libiconv.so.2 is not found in archive
>
> If I don't include it in my own LIBPATH, git works normally.
>
> I tried reproducing my own PATH and LIBPATH in the startup script for git,
> but still no joy.  I get the second error.
>
>
> Obviously there is some sort of environment issue with jenkins, but I
> can't figure out what it is.
> Any thoughts?
>
>
>
>
>
>
>
> --
> 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/87b14e73-7fc1-49aa-b944-e227b473146c%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/87b14e73-7fc1-49aa-b944-e227b473146c%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtH0kyvWKvTYGqJ9-GrZea1H7UkyBVrcH7t1Bccw3heJ0w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Odd environment problem with git under Jenkins on AIX

2019-04-25 Thread Rich Stephens

I have finally gotten Jenkins and the git plugin running (I have managed to
upgrade to Java8).

git works perfectly from the command line.

If I include /opt/freeware/lib into the LIBPATH when starting jenkins, when
I try to connect to a remove repository, I get basically this error:

OpenSSL version mismatch. Built against 1000105f, you have 10bf
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Coincidentally, this is the same error that I get if I include
/opt/freeware/lib in my own LIBPATH.

If I _don't_ include /opt/freeware/lib in the LIBPATH for jenkins, I get:

Failed to connect to repository : Command "git ls-remote -h
ssh://g...@stash.saas-p.com:7999/optio/core.git HEAD" returned status code
255:
stdout:
stderr: exec(): 0509-036 Cannot load program git because of the following
errors:
0509-150 Dependent module /usr/lib/libiconv.a(libiconv.so.2) could not be
loaded.
0509-152 Member libiconv.so.2 is not found in archive

If I don't include it in my own LIBPATH, git works normally.

I tried reproducing my own PATH and LIBPATH in the startup script for git,
but still no joy. I get the second error.

Obviously there is some sort of environment issue with jenkins, but I can't
figure out what it is.
Any thoughts?

--
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/87b14e73-7fc1-49aa-b944-e227b473146c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trigger from GIT to Jenkins buildWithParameters ignores parameter value in pipeline

2019-03-20 Thread Jaroslav Koblizek

Thanks Aaron.

The issue was in missing escaping of & in URL. More details I posted to 
https://stackoverflow.com/questions/55257984/trigger-from-git-to-jenkins-buildwithparameters-ignores-parameter-value-in-pipel/55265035

-- 
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/b5dbd4ce-c337-4d80-bc5e-2e26c15d9e5b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trigger from GIT to Jenkins buildWithParameters ignores parameter value in pipeline

2019-03-20 Thread Aaron Digulla

 Use 

params.ABC

"params" contains build parameters, "env" the environment.

-- 
Aaron Digulla

-- 
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/e24195ee-68a7-44f9-a714-81170d98cb8f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Trigger from GIT to Jenkins buildWithParameters ignores parameter value in pipeline

2019-03-20 Thread Jaroslav Koblizek

 

I have a *post-receive* hook in GIT (works ok) which calls


http://ip:port/job/project_name/buildWithParameters?token=abc=qwe
>
 

*ABC* is my parameter which is defined in Jenkins' project as *String 
parameter* with default value *xyz*. URL has value *qwe*.


[image: enter image description here] 


My Jenkins *pipeline script* is


pipeline {
> agent any
> stages {
> stage('Checkout') {
> steps {
> print env.ABC
> }
> }
> }
> }
>
>
When the build is triggered from GIT, env.ABC prints xyz and not qwe.


[image: enter image description here] 


*How to get the value qwe from the URL ?* My goal is to pass versioned tag 
name from GIT to pipeline.


Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/809d5fb5-4553-40de-8eb7-01ef775dda10%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: i need to connect git on jenkins but im getiing error 128

2019-03-01 Thread Mark Waite

It is generally a bad practice to embed a space character in the name of
the git repository.  If the example you provided accurately describes what
you're trying to do, then you'll probably need to rename the repository
from 'project Name' to something that does not include space characters.

Other things to consider:

   - Have you defined a Jenkins credential with the username and password
   that is used to access that repository?
   - Are you using that Jenkins credential in the job definition?
   - Are you able to clone from that repository using command line git with
   the username and password from the Jenkins credential?
   - Can you clone public repositories (for example,
   https://github.com/jenkinsci/git-client-plugin)?
   - Can you clone other private repositories?
   - Have you tried adding JGit from the "Manage Jenkins" -> "Global Tool
   Configuration" -> "Git installations" section, then adjust your job to use
   JGit instead of command line git?
   - Is this a Freestyle job, a Pipeline job, a Multibranch Pipeline job,
   or something else?
   - What version of command line git is running on the agent where the
   command fails?
   - What operating system are you using?


On Fri, Mar 1, 2019 at 6:19 AM mohammad sayekooie 
wrote:

> *Failed to connect to repository : Command "git ls-remote -h
> http://a.a.a.a:8081/master/project 
> Name.git HEAD" returned status code 128:*
> stdout:
> stderr: error: The requested URL returned error: 401 Unauthorized while
> accessing http://*a.a.a.a:8081/master/project Name.git*/info/refs
>
> fatal: HTTP request failed
>
> --
> 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/afaaf96d-0c35-4e92-b49c-19f564ffacea%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtH9Bu6R1L8J7MY6xzD7wwDg72XwooNq5t85sKw7cAbzYg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: i need to connect git on jenkins but im getiing error 128

2019-03-01 Thread Dirk Heinrichs

Am Freitag, den 01.03.2019, 04:56 -0800 schrieb mohammad sayekooie:

401 Unauthorized

And that doesn't ring a bell? Seems you need to provide credentials.

HTH...

Dirk

Dirk Heinrichs
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
Phone: +49 2226 15966 18
Email: dhein...@opentext.com
Website: www.recommind.de
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer John Marshall Doolittle, Gordon Davies,
Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
This e-mail may contain confidential and/or privileged information. If you are
not the intended recipient (or have received this e-mail in error) please
notify the sender immediately and destroy this e-mail. Any unauthorized
copying, disclosure or distribution of the material in this e-mail is strictly
forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht
gestattet.

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

i need to connect git on jenkins but im getiing error 128

2019-03-01 Thread mohammad sayekooie

*Failed to connect to repository : Command "git ls-remote -h 
http://a.a.a.a:8081/master/project Name.git HEAD" returned status code 128:*
stdout: 
stderr: error: The requested URL returned error: 401 Unauthorized while 
accessing http://*a.a.a.a:8081/master/project Name.git*/info/refs

fatal: HTTP request failed

-- 
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/afaaf96d-0c35-4e92-b49c-19f564ffacea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Git with Jenkins

2016-11-26 Thread Mark Waite

Yes.

On Sat, Nov 26, 2016 at 11:43 AM Anup  wrote:

> If I commit code to remote repository with gitignore created to exclude
> directory containing test data (username and password), will software build
> run successfully in Jenkins?
>
> --
> 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/48ee29dd-a0d2-4287-8828-149466abcdab%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/CAO49JtHhpWSKH9gO2NTPtb0upK71EFLor%2BKi%3DQt%2BkqBrwy%3DN7g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Git with Jenkins

2016-11-26 Thread Anup

If I commit code to remote repository with gitignore created to exclude 
directory containing test data (username and password), will software build 
run successfully in Jenkins?

-- 
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/48ee29dd-a0d2-4287-8828-149466abcdab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2 Pipeline script triggering itself. How to not poll for changes by git user Jenkins?

2016-09-14 Thread Mark Waite

No work around that I've found.

On Wed, Sep 14, 2016 at 8:20 AM Phil Swenson  wrote:

> Hi, we have a Jenkins Pipeline job that changes a pom.xml file and checks
> in the change.  This of course causes the job to kick itself off again.
>
> Is there a way to configure the job to ignore the jenkins user?
>
> I tried this:
>
>git url: 'g...@bitbucket.org:myrepo.git', excludedUsers: 'jenkins',
> branch: branch, credentialsId: 'mycredstuff', variable: 'CREDENTIALS'
>
> This didn't seem to work.
>
> I see there is an issue opened against jenkins here:
>
> https://issues.jenkins-ci.org/browse/JENKINS-36195
>
>
> Is there a way to work around this issue?
>
> Thanks
> phil
>
>
> --
> 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/db03411a-6510-47a1-a8d6-6e86b07f2c8c%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/CAO49JtEf%2B7wBOOVEsOZuRBUOvsu4XTzyjsMaZkbvCoL4_q4Hkg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins 2 Pipeline script triggering itself. How to not poll for changes by git user Jenkins?

2016-09-14 Thread Phil Swenson

Hi, we have a Jenkins Pipeline job that changes a pom.xml file and checks 
in the change.  This of course causes the job to kick itself off again.

Is there a way to configure the job to ignore the jenkins user?

I tried this:

   git url: 'g...@bitbucket.org:myrepo.git', excludedUsers: 'jenkins', 
branch: branch, credentialsId: 'mycredstuff', variable: 'CREDENTIALS'

This didn't seem to work.

I see there is an issue opened against jenkins here:

https://issues.jenkins-ci.org/browse/JENKINS-36195


Is there a way to work around this issue?

Thanks
phil
 

-- 
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/db03411a-6510-47a1-a8d6-6e86b07f2c8c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GIT and Jenkins for dummies

2016-05-14 Thread Mark Waite

Did you use the credentials link on the administer Jenkins page to tell
Jenkins your ssh private key?

After that, dogs you choose that credential for your fit repository from
the job definition page?

Mark Waite

On Sat, May 14, 2016, 2:09 AM David Montgomery 
wrote:

> Hi,
>
> PS I can even clone as jenkins user using ssh on github.  So is this a bug
> with jenkins 2.3 UI?  Should I revert back to a more stable version of
> jenkins?
>
> On Saturday, May 14, 2016 at 3:56:25 PM UTC+8, David Montgomery wrote:
>>
>> Hello Jenkins Dev team,
>>
>> Wow what pain.
>>
>> In this folder I have my keys and yes I an authenticate
>> /var/lib/jenkins/.ssh
>>
>>  ssh -T g...@github.com
>> The authenticity of host 'github.com (xxx.xxx' can't be established.
>> RSA key fingerprint is 1dsdsdsdsd.
>> Are you sure you want to continue connecting (yes/no)? yes
>> Warning: Permanently added 'github.com,1xxx.xxx' (RSA) to the list of
>> known hosts.
>> Hi aws-deploy! You've successfully authenticated, but GitHub does not
>> provide shell access.
>> jenkins@jenkins-zen-aws-development-sg-jzkm:~/.ssh$ git config --global
>> user.email "cloud+jenk...@example.com"
>> jenkins@jenkins-zen-aws-development-sg-jzkm:~/.ssh$ git config --global
>> user.name "jenkins"
>>
>>
>> And wowin the UI I get the below
>>
>> Failed to connect to repository : Command "git -c core.askpass=true
>> ls-remote -h g...@github.com:test/test.git HEAD" returned status code 128:
>> stdout:
>> stderr: Permission denied (publickey).
>> fatal: Could not read from remote repository.
>>
>> Please make sure you have the correct access rights
>> and the repository exists.
>>
>>
>> OMG but is works on the command line..
>>
>> git -c core.askpass=true ls-remote -h g...@github.com:tats/test.git
>> 7ccd2997c8b6d7261b1d9c534753ce2d3a356657refs/heads/development
>> 7ee63a5fa284d9de7e55dc6d3733db9237d78ba0refs/heads/master
>>
>> So.why?
>>
>>
>>
>>
>>
>>
>> On Friday, May 13, 2016 at 8:18:51 PM UTC+8, David Montgomery wrote:
>>>
>>> Hi,
>>>
>>> I am new do Jenkins 2 and finding configuring git my no stretch of the
>>> imagination straightforward.  Where is the "I am stupid to live
>>> documentation?"
>>>
>>> I am on a standard ubuntu 14.04 server, using github and my ssh keys
>>> work.  Docs on how to setup server with git so far are terrible with
>>> different methods of doing things.
>>>
>>> Thanks
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/c5385f1e-d529-4177-98f7-c02cbf9afcd9%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/CAO49JtHKNZx6oMTJX_rOJr4Lbz-hVMDf4tBCF3V19%3D00dkvX7w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: GIT and Jenkins for dummies

2016-05-14 Thread David Montgomery

Hi,

PS I can even clone as jenkins user using ssh on github.  So is this a bug 
with jenkins 2.3 UI?  Should I revert back to a more stable version of 
jenkins?  

On Saturday, May 14, 2016 at 3:56:25 PM UTC+8, David Montgomery wrote:
>
> Hello Jenkins Dev team,
>
> Wow what pain.
>
> In this folder I have my keys and yes I an authenticate
> /var/lib/jenkins/.ssh
>
>  ssh -T g...@github.com
> The authenticity of host 'github.com (xxx.xxx' can't be established.
> RSA key fingerprint is 1dsdsdsdsd.
> Are you sure you want to continue connecting (yes/no)? yes
> Warning: Permanently added 'github.com,1xxx.xxx' (RSA) to the list of 
> known hosts.
> Hi aws-deploy! You've successfully authenticated, but GitHub does not 
> provide shell access.
> jenkins@jenkins-zen-aws-development-sg-jzkm:~/.ssh$ git config --global 
> user.email "cloud+jenk...@example.com"
> jenkins@jenkins-zen-aws-development-sg-jzkm:~/.ssh$ git config --global 
> user.name "jenkins"
>
>
> And wowin the UI I get the below
>
> Failed to connect to repository : Command "git -c core.askpass=true 
> ls-remote -h g...@github.com:test/test.git HEAD" returned status code 128:
> stdout: 
> stderr: Permission denied (publickey). 
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
>
>
> OMG but is works on the command line..
>
> git -c core.askpass=true ls-remote -h g...@github.com:tats/test.git
> 7ccd2997c8b6d7261b1d9c534753ce2d3a356657refs/heads/development
> 7ee63a5fa284d9de7e55dc6d3733db9237d78ba0refs/heads/master
>
> So.why?  
>
>
>
>
>
>
> On Friday, May 13, 2016 at 8:18:51 PM UTC+8, David Montgomery wrote:
>>
>> Hi,
>>
>> I am new do Jenkins 2 and finding configuring git my no stretch of the 
>> imagination straightforward.  Where is the "I am stupid to live 
>> documentation?"
>>
>> I am on a standard ubuntu 14.04 server, using github and my ssh keys 
>> work.  Docs on how to setup server with git so far are terrible with 
>> different methods of doing things.
>>
>> Thanks
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/c5385f1e-d529-4177-98f7-c02cbf9afcd9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GIT and Jenkins for dummies

2016-05-14 Thread David Montgomery

Hello Jenkins Dev team,

Wow what pain.

In this folder I have my keys and yes I an authenticate
/var/lib/jenkins/.ssh

 ssh -T g...@github.com
The authenticity of host 'github.com (xxx.xxx' can't be established.
RSA key fingerprint is 1dsdsdsdsd.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'github.com,1xxx.xxx' (RSA) to the list of known 
hosts.
Hi aws-deploy! You've successfully authenticated, but GitHub does not 
provide shell access.
jenkins@jenkins-zen-aws-development-sg-jzkm:~/.ssh$ git config --global 
user.email "cloud+jenk...@example.com"
jenkins@jenkins-zen-aws-development-sg-jzkm:~/.ssh$ git config --global 
user.name "jenkins"

And wowin the UI I get the below

Failed to connect to repository : Command "git -c core.askpass=true 
ls-remote -h g...@github.com:test/test.git HEAD" returned status code 128:
stdout: 
stderr: Permission denied (publickey). 
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

OMG but is works on the command line..

git -c core.askpass=true ls-remote -h g...@github.com:tats/test.git
7ccd2997c8b6d7261b1d9c534753ce2d3a356657refs/heads/development
7ee63a5fa284d9de7e55dc6d3733db9237d78ba0refs/heads/master

So.why?  

On Friday, May 13, 2016 at 8:18:51 PM UTC+8, David Montgomery wrote:
>
> Hi,
>
> I am new do Jenkins 2 and finding configuring git my no stretch of the 
> imagination straightforward.  Where is the "I am stupid to live 
> documentation?"
>
> I am on a standard ubuntu 14.04 server, using github and my ssh keys 
> work.  Docs on how to setup server with git so far are terrible with 
> different methods of doing things.
>
> Thanks
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6af9e81d-18bc-4c4c-beb3-6bf6df57e60b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

GIT and Jenkins for dummies

2016-05-13 Thread David Montgomery

Hi,

I am new do Jenkins 2 and finding configuring git my no stretch of the 
imagination straightforward.  Where is the "I am stupid to live 
documentation?"

I am on a standard ubuntu 14.04 server, using github and my ssh keys work.  
Docs on how to setup server with git so far are terrible with different 
methods of doing things.

Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/7b0c886f-370c-497b-bac0-151df6e214d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Project structure with git and Jenkins

2014-10-01 Thread Stephen Connolly

It does sound like a use case for my employer's (CloudBees) proprietary
validated merge plugin... I'm sure you can figure out how to find out more
about it without me venturing any further into pimp our own wares
territory

On 1 October 2014 03:31, Mark Waite mark.earl.wa...@gmail.com wrote:

 Given that condition (developer computers are too slow for reasonable
 compilation), I don't have any suggestion that I would consider very
 helpful.

 You could try having them commit to git on their local computer using
 feature branches, then push the feature branch to a central repository for
 compilation by Jenkins.  It seems like a real problem that you're making
 developers round trip through a central server before they can decide if
 their code computer.

 Thanks,
 Mark Waite

 On Tue, Sep 30, 2014 at 8:25 PM, Ritesh Patel rpa...@shipco.com wrote:

 Thank you Mark.

 Actually, we are facing compilation time issue on local servers as we are
 using GWT.
 To solve it, we set a central server with very good configuration.
 So, developers can use that server for compilation.
 Now, the idea is that developers have code on some shared drive, they
 implement the code, and to compile they use jenkins, which is on central
 server.

 Thanks,
 Ritesh Patel.

 On Monday, September 29, 2014 10:18:47 PM UTC+7, Mark Waite wrote:

 Can you explain further what you hope to gain by using a shared drive
 for development?

 Git works best with local drives.  It is a fast version control system
 in large measure because the vast majority of its operations work on the
 local file system.  If you make git operate on a shared file system, you've
 now inserted a slowdown (network access) into all the operations performed
 by developers, all day long.  That seems like a serious penalty for the
 most active portion of a developer's working day.

 Git users have the notion of a feature branch which allows a developer
 to submit something to be evaluated by Jenkins, without making that change
 available on the authoritative branch.  You could investigate a feature
 branch based workflow, and use Jenkins to automate the merge from feature
 branches to the authoritative branch.

 Alternately, you could consider using Gerrit, which provides a code read
 facility and related workflow as a layer over a git repository.

 Mark Waite

 On Sun, Sep 28, 2014 at 10:34 PM, Ritesh Patel rpa...@shipco.com
 wrote:

 Hi All,

 Right now, in our project, developers develop code on shared drive,
 compile on common server, but deploy on local PC.
 But, we want continuous integration in future with git and Jenkins.
 Our main requirement is that developers should not have anything on
 their PC, they develop on shared drive, once they save, they can ask
 Jenkins to compile and deploy automatically.
 But, this should happen without commit to main branch.
 How we can achieve this?

 Thanks in advance.

 Ritesh Patel.

 --
 You received this message because you are subscribed to the Google
 Groups Jenkins Users group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to jenkinsci-use...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.




 --
 Thanks!
 Mark Waite

  --
 You received this message because you are subscribed to the Google Groups
 Jenkins Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to jenkinsci-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.




 --
 Thanks!
 Mark Waite

 --
 You received this message because you are subscribed to the Google Groups
 Jenkins Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to jenkinsci-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Project structure with git and Jenkins

2014-09-30 Thread Ritesh Patel

Thank you Mark.

Actually, we are facing compilation time issue on local servers as we are 
using GWT. 
To solve it, we set a central server with very good configuration.
So, developers can use that server for compilation.
Now, the idea is that developers have code on some shared drive, they 
implement the code, and to compile they use jenkins, which is on central 
server.

Thanks,
Ritesh Patel.

On Monday, September 29, 2014 10:18:47 PM UTC+7, Mark Waite wrote:

 Can you explain further what you hope to gain by using a shared drive for 
 development?

 Git works best with local drives.  It is a fast version control system in 
 large measure because the vast majority of its operations work on the local 
 file system.  If you make git operate on a shared file system, you've now 
 inserted a slowdown (network access) into all the operations performed by 
 developers, all day long.  That seems like a serious penalty for the most 
 active portion of a developer's working day.

 Git users have the notion of a feature branch which allows a developer 
 to submit something to be evaluated by Jenkins, without making that change 
 available on the authoritative branch.  You could investigate a feature 
 branch based workflow, and use Jenkins to automate the merge from feature 
 branches to the authoritative branch.

 Alternately, you could consider using Gerrit, which provides a code read 
 facility and related workflow as a layer over a git repository.

 Mark Waite

 On Sun, Sep 28, 2014 at 10:34 PM, Ritesh Patel rpa...@shipco.com 
 javascript: wrote:

 Hi All,

 Right now, in our project, developers develop code on shared drive, 
 compile on common server, but deploy on local PC.
 But, we want continuous integration in future with git and Jenkins. 
 Our main requirement is that developers should not have anything on their 
 PC, they develop on shared drive, once they save, they can ask Jenkins to 
 compile and deploy automatically.
 But, this should happen without commit to main branch.
 How we can achieve this?

 Thanks in advance.

 Ritesh Patel.

 -- 
 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/d/optout.




 -- 
 Thanks!
 Mark Waite
  

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Project structure with git and Jenkins

2014-09-30 Thread Mark Waite

Given that condition (developer computers are too slow for reasonable
compilation), I don't have any suggestion that I would consider very
helpful.

You could try having them commit to git on their local computer using
feature branches, then push the feature branch to a central repository for
compilation by Jenkins.  It seems like a real problem that you're making
developers round trip through a central server before they can decide if
their code computer.

Thanks,
Mark Waite

On Tue, Sep 30, 2014 at 8:25 PM, Ritesh Patel rpa...@shipco.com wrote:

 Thank you Mark.

 Actually, we are facing compilation time issue on local servers as we are
 using GWT.
 To solve it, we set a central server with very good configuration.
 So, developers can use that server for compilation.
 Now, the idea is that developers have code on some shared drive, they
 implement the code, and to compile they use jenkins, which is on central
 server.

 Thanks,
 Ritesh Patel.

 On Monday, September 29, 2014 10:18:47 PM UTC+7, Mark Waite wrote:

 Can you explain further what you hope to gain by using a shared drive for
 development?

 Git works best with local drives.  It is a fast version control system in
 large measure because the vast majority of its operations work on the local
 file system.  If you make git operate on a shared file system, you've now
 inserted a slowdown (network access) into all the operations performed by
 developers, all day long.  That seems like a serious penalty for the most
 active portion of a developer's working day.

 Git users have the notion of a feature branch which allows a developer
 to submit something to be evaluated by Jenkins, without making that change
 available on the authoritative branch.  You could investigate a feature
 branch based workflow, and use Jenkins to automate the merge from feature
 branches to the authoritative branch.

 Alternately, you could consider using Gerrit, which provides a code read
 facility and related workflow as a layer over a git repository.

 Mark Waite

 On Sun, Sep 28, 2014 at 10:34 PM, Ritesh Patel rpa...@shipco.com wrote:

 Hi All,

 Right now, in our project, developers develop code on shared drive,
 compile on common server, but deploy on local PC.
 But, we want continuous integration in future with git and Jenkins.
 Our main requirement is that developers should not have anything on
 their PC, they develop on shared drive, once they save, they can ask
 Jenkins to compile and deploy automatically.
 But, this should happen without commit to main branch.
 How we can achieve this?

 Thanks in advance.

 Ritesh Patel.

 --
 You received this message because you are subscribed to the Google
 Groups Jenkins Users group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to jenkinsci-use...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.




 --
 Thanks!
 Mark Waite

  --
 You received this message because you are subscribed to the Google Groups
 Jenkins Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to jenkinsci-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.




-- 
Thanks!
Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Project structure with git and Jenkins

2014-09-29 Thread Mark Waite

Can you explain further what you hope to gain by using a shared drive for
development?

Git works best with local drives.  It is a fast version control system in
large measure because the vast majority of its operations work on the local
file system.  If you make git operate on a shared file system, you've now
inserted a slowdown (network access) into all the operations performed by
developers, all day long.  That seems like a serious penalty for the most
active portion of a developer's working day.

Git users have the notion of a feature branch which allows a developer to
submit something to be evaluated by Jenkins, without making that change
available on the authoritative branch.  You could investigate a feature
branch based workflow, and use Jenkins to automate the merge from feature
branches to the authoritative branch.

Alternately, you could consider using Gerrit, which provides a code read
facility and related workflow as a layer over a git repository.

Mark Waite

On Sun, Sep 28, 2014 at 10:34 PM, Ritesh Patel rpa...@shipco.com wrote:

 Hi All,

 Right now, in our project, developers develop code on shared drive,
 compile on common server, but deploy on local PC.
 But, we want continuous integration in future with git and Jenkins.
 Our main requirement is that developers should not have anything on their
 PC, they develop on shared drive, once they save, they can ask Jenkins to
 compile and deploy automatically.
 But, this should happen without commit to main branch.
 How we can achieve this?

 Thanks in advance.

 Ritesh Patel.

 --
 You received this message because you are subscribed to the Google Groups
 Jenkins Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to jenkinsci-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.




-- 
Thanks!
Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Taggin in Git using jenkins

2013-11-25 Thread Prashant Sawant

Hi
I have a build pipeline with around 10 modules to build , at the end of 
10th module I want to tag the GIT with build pipeline build number
Currently I added the following in post build script 
 
git tag ${BUILD_TAG}
git push --tag
 
but it tag with 10th module name and build number , which is not helpful
If I want use build pipeline variables , how can I do that
 
please advise
 
Thanks
Prashant

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: GIT and Jenkins

2013-03-07 Thread nicolas de loof

right, ls-remote is used to validate repository URL (form master) and to
poll scm (single branch)


2013/3/7 Eduardo Dias eduardodia...@gmail.com

 I had the same problem and  done what Nicolas suggested and the
 message stopped. Even Jenkins does not use master to build the jenkis
 master try to access repository.


 2013/3/7 nicolas de loof nicolas.del...@gmail.com

 does the clone run on master or some slave ?

 this ls-remote command is executed on master, maybe you just miss the
 adequate ssh key there. Long term plan is to integrate
 ssh-credentials-plugin in git-plugin to manage this.


 2013/3/7 Jeff predato...@gmail.com

 I thought I asked this and fixed it before, but it has come up again and
 I am not seeing this in the archives

 When we setup a job that pulls source from GIT, I see this error shown
 below the Repository URL box:


 Failed to connect to repository : Error performing command:  ls-remote
 -h g...@github.com:myRepo/myApp.git HEAD

 or for projects using our internal GitoLIte repo:


  Failed to connect to repository : Error performing command:  ls-remote
 -h gitol...@git1.mycompany.int:myInternalApp.git HEAD

 The project clones and builds just fine, but I don't think the SCM
 Polling works properly and I think it is related to the above issue.

 Any idea what it might be?  Google searches indicate that the absolute
 path to the git binary must be specified, which I've set (/usr/bin/git).

 I've set the git user.name/user.email environment values on the job
 settings.

 I don't know what else to look at.  Thoughts?

 --
 Jeff Vincent
 See my LinkedIn profile at:
 http://www.linkedin.com/in/rjeffreyvincent
 I ♥ DropBox http://db.tt/9O6LfBX !!

 --
 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.






 --

 Atenciosamente,

 Eduardo

 --
 You received this message because you are subscribed to the Google Groups
 Jenkins Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to jenkinsci-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: GIT and Jenkins

2013-03-06 Thread Mark Waite

The command that is listed there is a surprise.  I think it should say git 
ls-remote ... rather than ls-remote   

I wonder if your Jenkins is unable to locate the Git executable?  Check the 
system configuration screen to see if it is pointing to a non-existent git 
executable, or possibly to a git executable on the master which does not exist 
on a slace.

You might also check the Advanced section of the Jenkins to see if the fast 
remote polling is enabled.  I believe the git plugin using the ls-remote 
command to perform fast remote polling.  I think that is less likely to be the 
problem, since the polling command should be git ls-remote rather than 
ls-remote.

Mark Waite




 From: Jeff predato...@gmail.com
To: jenkinsci-users@googlegroups.com 
Sent: Wednesday, March 6, 2013 5:35 PM
Subject: GIT and Jenkins
 

I thought I asked this and fixed it before, but it has come up again and I am 
not seeing this in the archives


When we setup a job that pulls source from GIT, I see this error shown below 
the Repository URL box:




Failed to connect to repository : Error performing command:  ls-remote -h 
g...@github.com:myRepo/myApp.git HEAD 


or for projects using our internal GitoLIte repo:




Failed to connect to repository : Error performing command:  ls-remote -h 
gitol...@git1.mycompany.int:myInternalApp.git HEAD 


The project clones and builds just fine, but I don't think the SCM Polling 
works properly and I think it is related to the above issue.


Any idea what it might be?  Google searches indicate that the absolute path to 
the git binary must be specified, which I've set (/usr/bin/git).


I've set the git user.name/user.email environment values on the job settings.


I don't know what else to look at.  Thoughts?

-- 

Jeff Vincent
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent
I ♥ DropBox !!  
-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 




-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: GIT and Jenkins

2013-03-06 Thread nicolas de loof

does the clone run on master or some slave ?

this ls-remote command is executed on master, maybe you just miss the
adequate ssh key there. Long term plan is to integrate
ssh-credentials-plugin in git-plugin to manage this.

2013/3/7 Jeff predato...@gmail.com

 I thought I asked this and fixed it before, but it has come up again and I
 am not seeing this in the archives

 When we setup a job that pulls source from GIT, I see this error shown
 below the Repository URL box:


 Failed to connect to repository : Error performing command:  ls-remote -h
 g...@github.com:myRepo/myApp.git HEAD

 or for projects using our internal GitoLIte repo:


  Failed to connect to repository : Error performing command:  ls-remote
 -h gitol...@git1.mycompany.int:myInternalApp.git HEAD

 The project clones and builds just fine, but I don't think the SCM
 Polling works properly and I think it is related to the above issue.

 Any idea what it might be?  Google searches indicate that the absolute
 path to the git binary must be specified, which I've set (/usr/bin/git).

 I've set the git user.name/user.email environment values on the job
 settings.

 I don't know what else to look at.  Thoughts?

 --
 Jeff Vincent
 See my LinkedIn profile at:
 http://www.linkedin.com/in/rjeffreyvincent
 I ♥ DropBox http://db.tt/9O6LfBX !!

 --
 You received this message because you are subscribed to the Google Groups
 Jenkins Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to jenkinsci-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: git on jenkins

2013-02-19 Thread Johannes Wienke

On 02/18/2013 05:08 PM, Kamal Ahmed wrote:
 Hi,
 I setup 2 linux hosts with passwordless login, and git clone IP 
 Address:/extra/yte/www/repo/Dout.git
 works on command line, but when i use : IP 
 Address:/extra/yte/www/repo/Dout.git as repo URL, i get an error:
 
 Failed to connect to repository : Command /usr/bin/git ls-remote -h IP 
 Address:/extra/yte/www/repo/Dout.git HEAD returned 
 status code 128:
 stdout: 
 stderr: Permission denied, please try again. 
 Permission denied, please try again. 
 Permission denied (publickey,password). 
 fatal: The remote end hung up unexpectedly

I think you missed the ssh:// in the URL?

Cheers,
Johannes




signature.asc
Description: OpenPGP digital signature

Re: git on jenkins

2013-02-19 Thread Mark Waite

I think that indicates that the user account context where you have configured 
passwordless login is probably different than the user account context where 
you are executing Jenkins.

You might be able to check that by creating a small job which performs some ssh 
command to the same remote host which is hosting your git repository.  For 
example, if you create a job which runs the command ssh IP address hostname 
(on IP address, execute the command hostname), then you'll probably see a 
similar permission denied message and you can begin studying the differences 
between the context where it works and the context where it fails.

Mark Waite




 From: Kamal Ahmed kamalah...@yahoo.com
To: Johannes Wienke jwie...@techfak.uni-bielefeld.de; 
jenkinsci-users@googlegroups.com jenkinsci-users@googlegroups.com 
Sent: Tuesday, February 19, 2013 5:27 AM
Subject: Re: git on jenkins
 

Johannes,

I still get error if i use ssh ( See attached screen shot ) 

Thanks,
-Kamal.









 From: Johannes Wienke jwie...@techfak.uni-bielefeld.de
To: jenkinsci-users@googlegroups.com 
Cc: Kamal Ahmed kamalah...@yahoo.com 
Sent: Tuesday, February 19, 2013 5:47 AM
Subject: Re: git on jenkins
 
On 02/18/2013 05:08 PM, Kamal Ahmed wrote:
 Hi,
 I setup 2 linux hosts with passwordless login, and git clone IP 
 Address:/extra/yte/www/repo/Dout.git
 works on command line, but when i use : IP 
 Address:/extra/yte/www/repo/Dout.git as repo URL, i get an error:
 
 Failed to connect to repository : Command /usr/bin/git ls-remote -h IP 
 Address:/extra/yte/www/repo/Dout.git HEAD returned 
 status code 128:
 stdout: 
 stderr: Permission denied, please try again. 
 Permission denied, please try again. 
 Permission denied (publickey,password). 
 fatal: The remote end hung up unexpectedly

I think you missed the ssh:// in the URL?

Cheers,
Johannes





-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 




-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: git on jenkins

2013-02-19 Thread Kamal Ahmed



kahmed@datascout:~/TEMP$ id
uid=1000(kahmed) gid=1000(kahmed) 
groups=1000(kahmed),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),109(lpadmin),124(sambashare)
kahmed@datascout:~/TEMP$ git clone 
10.100.100.96:/extra/cte/www/repo/Dout.git
Cloning into 'Dout'...
remote: Counting objects: 835, done.
remote: Compressing objects: 100% (604/604), done.
remote: Total 835 (delta 248), reused 597 (delta 141)
Receiving objects: 100% (835/835), 44.51 MiB | 20.25 MiB/s, done.
Resolving deltas: 100% (248/248), done.
kahmed@datascout:~/TEMP$ 

so i CAN clone the repo, using git, from command line, and WHY i cannot do the 
same via Jenkins ? That is the question.

and as per your suggestion: again from command line:

ssh kahmed@10.100.100.96 hostname
cybage02


so i AM able to execute commands without password.




 From: Mark Waite markwa...@yahoo.com
To: jenkinsci-users@googlegroups.com jenkinsci-users@googlegroups.com 
Sent: Tuesday, February 19, 2013 7:44 AM
Subject: Re: git on jenkins
 

I think that indicates that the user account context where you have configured 
passwordless login is probably different than the user account context where 
you are executing Jenkins.


You might be able to check that by creating a small job which performs some 
ssh command to the same remote host which is hosting your git repository.  For 
example, if you create a job which runs the command ssh IP address 
hostname (on IP address, execute the command hostname), then you'll 
probably see a similar permission denied message and you can begin studying 
the differences between the context where it works and the context where it 
fails.


Mark Waite




 From: Kamal Ahmed kamalah...@yahoo.com
To: Johannes Wienke jwie...@techfak.uni-bielefeld.de; 
jenkinsci-users@googlegroups.com jenkinsci-users@googlegroups.com 
Sent: Tuesday, February 19, 2013 5:27 AM
Subject: Re: git on jenkins
 

Johannes,

I still get error if i use ssh ( See attached screen shot ) 

Thanks,
-Kamal.









 From: Johannes Wienke jwie...@techfak.uni-bielefeld.de
To: jenkinsci-users@googlegroups.com 
Cc: Kamal Ahmed kamalah...@yahoo.com 
Sent: Tuesday, February 19, 2013 5:47 AM
Subject: Re: git on jenkins
 
On 02/18/2013 05:08 PM, Kamal Ahmed wrote:
 Hi,
 I setup 2 linux hosts with passwordless login, and git clone IP 
 Address:/extra/yte/www/repo/Dout.git
 works on command line, but when i use : IP 
 Address:/extra/yte/www/repo/Dout.git as repo URL, i get an error:
 
 Failed to connect to repository : Command /usr/bin/git ls-remote -h IP 
 Address:/extra/yte/www/repo/Dout.git HEAD returned 
 status code 128:
 stdout: 
 stderr: Permission denied, please try again. 
 Permission denied, please try again. 
 Permission denied (publickey,password). 
 fatal: The remote end hung up unexpectedly

I think you missed the ssh:// in the URL?

Cheers,
Johannes





-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 



-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 




-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: git on jenkins

2013-02-19 Thread Kamal Ahmed

Something is wrong with the email To: section, as this replaced my name with 
Johannes -- FYI to List Admins
-Kamal.





 From: Johannes Wienke jwie...@techfak.uni-bielefeld.de
To: jenkinsci-users@googlegroups.com 
Cc: Kamal Ahmed kamalah...@yahoo.com 
Sent: Tuesday, February 19, 2013 10:51 AM
Subject: Re: git on jenkins
 
On 02/19/2013 04:49 PM, Kamal Ahmed wrote:
 
 
 kahmed@datascout:~/TEMP$ id
 uid=1000(kahmed) gid=1000(kahmed) 
 groups=1000(kahmed),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),109(lpadmin),124(sambashare)
 kahmed@datascout:~/TEMP$ git clone 
 10.100.100.96:/extra/cte/www/repo/Dout.git
 Cloning into 'Dout'...
 remote: Counting objects: 835, done.
 remote: Compressing objects: 100% (604/604), done.
 remote: Total 835 (delta 248), reused 597 (delta 141)
 Receiving objects: 100% (835/835), 44.51 MiB | 20.25 MiB/s, done.
 Resolving deltas: 100% (248/248), done.
 kahmed@datascout:~/TEMP$ 
 
 so i CAN clone the repo, using git, from command line, and WHY i cannot do 
 the same via Jenkins ? That is the question.
 
 and as per your suggestion: again from command line:
 
 ssh kahmed@10.100.100.96 hostname
 cybage02

The slave is really running under user kahmed?

Cheers,
Johannes






-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: git on jenkins

2013-02-19 Thread Kamal Ahmed

Username = kahmed
which is the same user which can do a git successfully on a command line.







 From: Johannes Wienke jwie...@techfak.uni-bielefeld.de
To: Kamal Ahmed kamalah...@yahoo.com; jenkinsci-users@googlegroups.com 
Sent: Tuesday, February 19, 2013 12:12 PM
Subject: Re: git on jenkins
 
On 19.02.2013 17:28 schrieb Kamal Ahmed:
 
 Johannes,
 
 sorry for the private message, just fat fingered when replying.
 yes, i am using 
 Launch slave on Unix machines using SSH as start method
 
 not sure what is the file to be configured
 
 My network is 
 
 [Jenkins Master ] --- [ Slave ] --- [10.100.100.96/cybage02] , cybage02, 
 is where the git repo is setup.
 

That wasn't what I meant. If you look at the configuration of the slave
in the jenkins web interface, what is the value of the username field,
if you open open up the extended settings for the SSH connection?

Cheers,
Johannes






-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: git on jenkins

2013-02-19 Thread Johannes Wienke

On 19.02.2013 18:25 schrieb Kamal Ahmed:
 Username = kahmed
 which is the same user which can do a git successfully on a command line.

Hm ok, then I don't know. Maybe ssh agent is required and not available
in the jenkins session or something like that?

Cheers,
Johannes




signature.asc
Description: OpenPGP digital signature

Re: git on jenkins

2013-02-19 Thread Sami Tikka

I suggest you change your job configuration like this:

1) Remove the all the SCM configuration.

2) As first build step, add a shell script step which executes:

env
ssh -v 10.100.100.96 hostname

Then trigger the job to run. Then click open the build and the console. Check 
the output.

Then run the same commands from the command line where you are able to log in. 
Compare results with the output from Jenkins.

-- Sami

Kamal Ahmed kamalah...@yahoo.com kirjoitti 19.2.2013 kello 19.25:

 Username = kahmed
 which is the same user which can do a git successfully on a command line.
 
 
 From: Johannes Wienke jwie...@techfak.uni-bielefeld.de
 To: Kamal Ahmed kamalah...@yahoo.com; jenkinsci-users@googlegroups.com 
 Sent: Tuesday, February 19, 2013 12:12 PM
 Subject: Re: git on jenkins
 
 On 19.02.2013 17:28 schrieb Kamal Ahmed:
  
  Johannes,
  
  sorry for the private message, just fat fingered when replying.
  yes, i am using 
  Launch slave on Unix machines using SSH as start method
  
  not sure what is the file to be configured
  
  My network is 
  
  [Jenkins Master ] --- [ Slave ] --- [10.100.100.96/cybage02] , cybage02, 
  is where the git repo is setup.
  
 
 That wasn't what I meant. If you look at the configuration of the slave
 in the jenkins web interface, what is the value of the username field,
 if you open open up the extended settings for the SSH connection?
 
 Cheers,
 Johannes
 
 
 
 
 
 -- 
 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.

git on jenkins

2013-02-18 Thread Kamal Ahmed

Hi,
I setup 2 linux hosts with passwordless login, and git clone IP 
Address:/extra/yte/www/repo/Dout.git
works on command line, but when i use : IP 
Address:/extra/yte/www/repo/Dout.git as repo URL, i get an error:

Failed to connect to repository : Command /usr/bin/git ls-remote -h IP 
Address:/extra/yte/www/repo/Dout.git HEAD returned 
status code 128:
stdout: 
stderr: Permission denied, please try again. 
Permission denied, please try again. 
Permission denied (publickey,password). 
fatal: The remote end hung up unexpectedly

Anyone solved this issue before ?
Thanks,
-Kamal.

-- 
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.

using git with Jenkins , stderr: ssh: Could not resolve hostname : Name or service not known

2013-02-12 Thread Kamal Ahmed

I am trying to use git with Jenkins.

The URL that i have been given is:
git clone 10.100.243.212:/var/www/invo_app , which works as an LDAP user on 
command line:


But when i use Jenkins , i get:


Cloning repository ssh:///$GIT_USER@1.2.3.4:/var/www/invo_app
git --version
git version 1.7.9.5
ERROR: Error cloning remote repo 'origin' : Could not clone 
ssh:///$GIT_USER@1.2.3.4:/var/www/invo_app hudson.plugins.git.GitException: 
Could not clone ssh:///$GIT_USER@1.2.3.4:/var/www/invo_app at 
hudson.plugins.git.GitAPI.clone(GitAPI.java:273) at 
hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1044) at 
hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:986) at 
hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) at 
hudson.remoting.UserRequest.perform(UserRequest.java:118) at 
hudson.remoting.UserRequest.perform(UserRequest.java:48) at 
hudson.remoting.Request$2.run(Request.java:326) at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at 
java.util.concurrent.FutureTask.run(FutureTask.java:166) at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) 
at
 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) 
at java.lang.Thread.run(Thread.java:679) Caused by: 
hudson.plugins.git.GitException: Command /usr/bin/git clone --progress -o 
origin ssh:///$GIT_USER@1.2.3.4:/var/www/invo_app 
/home/kahmed/workspace/invo_app returned status code 128:
stdout: Cloning into '/home/kahmed/workspace/invo_app'... stderr: ssh: Could 
not resolve hostname : Name or service not known
fatal: The remote end hung up unexpectedly at 
hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:897) at 
hudson.plugins.git.GitAPI.access$000(GitAPI.java:42) at 
hudson.plugins.git.GitAPI$1.invoke(GitAPI.java:269) at 
hudson.plugins.git.GitAPI$1.invoke(GitAPI.java:248) at 
hudson.FilePath.act(FilePath.java:865) at 
hudson.FilePath.act(FilePath.java:838) at 
hudson.plugins.git.GitAPI.clone(GitAPI.java:248) ... 12 more
Trying next repository
ERROR: Could not clone repository FATAL: Could not clone 
hudson.plugins.git.GitException: Could not clone at 
hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1056) at 
hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:986) at 
hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) at 
hudson.remoting.UserRequest.perform(UserRequest.java:118) at 
hudson.remoting.UserRequest.perform(UserRequest.java:48) at 
hudson.remoting.Request$2.run(Request.java:326) at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at 
java.util.concurrent.FutureTask.run(FutureTask.java:166) at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) 
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) 
at java.lang.Thread.run(Thread.java:679)

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Git and Jenkins-- behind master by 55 commits

2012-03-15 Thread Sami Tikka

2012/3/15 KB1JWQ sort...@gmail.com:
 I find I have to git checkout master or it stays on no branch.

Why is the no branch a problem?

 What's the proper way to get the build operation to happen on the
 most current version of master?

Do not checkout master in your build step. Trust the git plugin. The
git plugin manages the workspace repository a bit differently to what
you are used to (because it has some nifty features) but it delivers
the result you are looking for if you do not go in there and run your
own git commands. If you do, all bets are off.

If you really want to manage the checkout procedure yourself, you
should choose No SCM in the job configuration. Then you can do
whatever you want.

-- Sami

Git and Jenkins-- behind master by 55 commits

2012-03-14 Thread KB1JWQ

I'm attempting to have a github project build every time master gets
updated.

Building in workspace /var/lib/jenkins/jobs/Example-scrapers-php/
workspace
Checkout:workspace / /var/lib/jenkins/jobs/Example-scrapers-php/
workspace - hudson.remoting.LocalChannel@32edeea8
Using strategy: Default
Last Built Revision: Revision e724d19f971fa0fe488e789a29ef38d66c0eba25
(origin/master)
Checkout:workspace / /var/lib/jenkins/jobs/Example-scrapers-php/
workspace - hudson.remoting.LocalChannel@32edeea8
Fetching changes from 1 remote Git repository
Fetching upstream changes from g...@github.com:Example/Server-Scraper
Commencing build of Revision e724d19f971fa0fe488e789a29ef38d66c0eba25
(origin/master)
Checking out Revision e724d19f971fa0fe488e789a29ef38d66c0eba25 (origin/
master)
[workspace] $ /bin/sh -xe /tmp/hudson4532906084275378804.sh
+ git checkout master
Previous HEAD position was e724d19... Deploying
e815460cb155b08141f29676ca0a5e975f7046ba of /example/staging/scraper/
var/importapi.example.com
Switched to branch 'master'
Your branch is behind 'origin/master' by 55 commits, and can be fast-
forwarded.

... at which point it goes into the build operation with an old
version of code.

I find I have to git checkout master or it stays on no branch.
What's the proper way to get the build operation to happen on the
most current version of master?

Re: dpkg versioning from Git via Jenkins

2012-03-01 Thread Michael Prokop

* KB1JWQ wrote:
 I'm in the process of setting up continuous integration.  I have a git
 project that I can successfully build into a .deb via Jenkins, from
 the master branch.

 How do I sanely change the version number of each build so that it
 bumps the Debian changelog (else the deb build fails), the version
 number of the package, and probably the naming of the resulting .deb
 as well?  Ultimately I want these debs to be put into a staging
 repository, so apt-get update; apt-get install foo automatically
 installs the latest Jenkins build of foo.

 It seems to me that the git commit hash would be semi-sane, but I'm
 new at Git, Jenkins, and Debian packaging...

I'm doing something like that in my
https://github.com/mika/jenkins-debian-glue project.

So what tools might be interesting for you (depending on your
workflow and needs) WRT changelog handling:

* git-dch
* debchange --release ...
* dch -b -v ...

git-dch supports the git commit hash out-of-the-box in the version
string, you can also include custom information like build-number,
timestamps,... in the version string.

-mika-
-- 
http://michael-prokop.at/  || http://adminzen.org/
http://grml-solutions.com/ || http://grml.org/

RE: Git+Gitolite+Jenkins

2012-02-27 Thread Matthew.Webber

Try git clone ssh://git@myGitServer/repo.git (WITHOUT repositories/ in the 
URL). That's a gitolite thing.

 -Original Message-
 From: jenkinsci-users@googlegroups.com 
 [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Charles
 Sent: 27 February 2012 15:38
 To: Jenkins Users
 Subject: Re: Git+Gitolite+Jenkins
 
 If I do this from my workstation:
 
 git clone git@myGitServer:repo.git
 
 The repo clones correctly.
 
 However, if I do this:
 
 git clone ssh://git@myGitServer/repositories/repo.git
 
 I get:
 
 charles.brown /c/Development
 $ git clone ssh://git@myGitServer/repositories/hub-application.git
 Cloning into 'hub-application'...
 Using keyboard-interactive authentication.
 R access for repositories/hub-application DENIED to charles.brown
 (Or there may be no repository at the given path. Did you spell it
 correctly?)
 fatal: The remote end hung up unexpectedly
 
 Same if I su to the 'jenkins' user...
 

--
This e-mail and any attachments may contain confidential, copyright and or 
privileged material, and are for the use of the intended addressee only. If you 
are not the intended addressee or an authorised recipient of the addressee 
please notify us of receipt by returning the e-mail and do not use, copy, 
retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not 
necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments 
are free from viruses and we cannot accept liability for any damage which you 
may sustain as a result of software viruses which may be transmitted in or with 
the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and 
Wales with its registered office at Diamond House, Harwell Science and 
Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom

Re: Git+Gitolite+Jenkins

2012-02-27 Thread Charles

yep...  that was it...  removed the /repositories directory and all
worked as it should...

Thanks!!

On Feb 27, 9:43 am, matthew.web...@diamond.ac.uk wrote:
 Try git clone ssh://git@myGitServer/repo.git (WITHOUT repositories/ in the 
 URL). That's a gitolite thing.









  -Original Message-
  From: jenkinsci-users@googlegroups.com 
  [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Charles
  Sent: 27 February 2012 15:38
  To: Jenkins Users
  Subject: Re: Git+Gitolite+Jenkins

  If I do this from my workstation:

  git clone git@myGitServer:repo.git

  The repo clones correctly.

  However, if I do this:

  git clone ssh://git@myGitServer/repositories/repo.git

  I get:

  charles.brown /c/Development
  $ git clone ssh://git@myGitServer/repositories/hub-application.git
  Cloning into 'hub-application'...
  Using keyboard-interactive authentication.
  R access for repositories/hub-application DENIED to charles.brown
  (Or there may be no repository at the given path. Did you spell it
  correctly?)
  fatal: The remote end hung up unexpectedly

  Same if I su to the 'jenkins' user...

 --
 This e-mail and any attachments may contain confidential, copyright and or 
 privileged material, and are for the use of the intended addressee only. If 
 you are not the intended addressee or an authorised recipient of the 
 addressee please notify us of receipt by returning the e-mail and do not use, 
 copy, retain, distribute or disclose the information in or attached to the 
 e-mail.
 Any opinions expressed within this e-mail are those of the individual and not 
 necessarily of Diamond Light Source Ltd.
 Diamond Light Source Ltd. cannot guarantee that this e-mail or any 
 attachments are free from viruses and we cannot accept liability for any 
 damage which you may sustain as a result of software viruses which may be 
 transmitted in or with the message.
 Diamond Light Source Limited (company no. 4375679). Registered in England and 
 Wales with its registered office at Diamond House, Harwell Science and 
 Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom

60 matches

Mail list logo