Re: [Jenkins] Passing parameters to build-artifacts.sh

2016-07-18 Thread Eyal Edri
nks, > Vojtech > > > - Original Message - > > From: "Vojtech Szocs" > > To: "David Caro" > > Cc: "infra" > > Sent: Wednesday, June 22, 2016 7:04:19 PM > > Subject: Re: [Jenkins] Passing parameters to build-artifacts.s

Re: [Jenkins] Passing parameters to build-artifacts.sh

2016-07-18 Thread Vojtech Szocs
t repo? Thanks, Vojtech - Original Message - > From: "Vojtech Szocs" > To: "David Caro" > Cc: "infra" > Sent: Wednesday, June 22, 2016 7:04:19 PM > Subject: Re: [Jenkins] Passing parameters to build-artifacts.sh > > > > - Ori

Re: [Jenkins] Passing parameters to build-artifacts.sh

2016-06-22 Thread Vojtech Szocs
- Original Message - > From: "David Caro" > To: "Nir Soffer" > Cc: "infra" > Sent: Wednesday, June 22, 2016 6:31:44 PM > Subject: Re: [Jenkins] Passing parameters to build-artifacts.sh > > On 06/22 19:21, Nir Soffer wrote: >

Re: [Jenkins] Passing parameters to build-artifacts.sh

2016-06-22 Thread Vojtech Szocs
ssage - > From: "Barak Korren" > To: "Vojtech Szocs" > Cc: "infra" > Sent: Wednesday, June 22, 2016 5:47:46 PM > Subject: Re: [Jenkins] Passing parameters to build-artifacts.sh > > This could be done, but not trival to do, and also requires you to know

Re: [Jenkins] Passing parameters to build-artifacts.sh

2016-06-22 Thread David Caro
On 06/22 19:21, Nir Soffer wrote: > On Wed, Jun 22, 2016 at 6:47 PM, Barak Korren wrote: > > This could be done, but not trival to do, and also requires you to know, > > before merging, that this is the patch you are gonna release. > > > > A differnt but somewhat common practice is to use git tagg

Re: [Jenkins] Passing parameters to build-artifacts.sh

2016-06-22 Thread Nir Soffer
On Wed, Jun 22, 2016 at 6:47 PM, Barak Korren wrote: > This could be done, but not trival to do, and also requires you to know, > before merging, that this is the patch you are gonna release. > > A differnt but somewhat common practice is to use git tagging and 'git > describe' to set the package

Re: [Jenkins] Passing parameters to build-artifacts.sh

2016-06-22 Thread Barak Korren
This could be done, but not trival to do, and also requires you to know, before merging, that this is the patch you are gonna release. A differnt but somewhat common practice is to use git tagging and 'git describe' to set the package version. We can make build_artifacts trigger when a tag is push

Re: [Jenkins] Passing parameters to build-artifacts.sh

2016-06-22 Thread Sandro Bonazzola
On Wed, Jun 22, 2016 at 5:39 PM, Vojtech Szocs wrote: > Hi, > > I'm just curious whether it's possible to do the following: > > Let's say we have a project (ovirt-engine-dashboard) built by Jenkins, > which means there's a Jenkins job that runs build-artifacts.sh script > whenever a patch gets me

[Jenkins] Passing parameters to build-artifacts.sh

2016-06-22 Thread Vojtech Szocs
Hi, I'm just curious whether it's possible to do the following: Let's say we have a project (ovirt-engine-dashboard) built by Jenkins, which means there's a Jenkins job that runs build-artifacts.sh script whenever a patch gets merged via gerrit. Can we somehow pass custom parameters to build-art