Advanced parameters or env vars for maven build step properties?

2023-05-16 Thread 'David Balazic' via Jenkins Users
Hi! Is there a way to specify advanced syntax properties to a maven build in a freestyle project? By advanced I mean some text manipulation or even output of system (command line) commands. Using Jenkins 2.387.2 we created a freestyle project and added an "Invoke top-level Maven targets" step

git plugin, use --single-branch option to save disk space?

2023-05-26 Thread 'David Balazic' via Jenkins Users
Hi! With the git plugin, is there a way to clone a repo with the --single-branch option? We have a freestyle job wit a Git source code, where we specify the branch as: refs/heads/main And when the build is done, the cloned repo (the .git folder) is very big, about 2.6 GB. We use a command line

RE: git plugin, use --single-branch option to save disk space?

2023-05-26 Thread 'David Balazic' via Jenkins Users
Thanks but I already tested those: Refspec: refs/heads/main Honor refspec on initial clone: enabled Shallow clone: enabled Shallow clone depth: 1 They download a little less : 1.8 GB The credit goes to the shallow clone option. The Honor refspec option does not seem to make any difference. Eve

RE: git plugin, use --single-branch option to save disk space?

2023-05-26 Thread 'David Balazic' via Jenkins Users
risks with "main") Regards, David Balažic From: 'David Balazic' via Jenkins Users Sent: Friday, 26 May 2023 15:23 Thanks but I already tested those: Refspec: refs/heads/main Honor refspec on initial clone: enabled Shallow clone: enabled Shallow clone depth: 1 They downlo

RE: git plugin, use --single-branch option to save disk space?

2023-05-26 Thread 'David Balazic' via Jenkins Users
Thanks! That did the trick. David Balažic Lead engineer Endava From: jenkinsci-users@googlegroups.com On Behalf Of Mark Waite Sent: Friday, 26 May 2023 15:47 To: Jenkins Users Subject: Re: git plugin, use --single-bra

git job weirdness (in Changes)

2023-06-20 Thread 'David Balazic' via Jenkins Users
Hi! I have set up a job in Jenkins v2.387.2 with sources from git and a maven build step. Last time I committed and pushed two changes into the repo. (one push after both commits) The Jenkins job detected the change and started a build. Issues: - the changes page in Jenkins ( /view/foo/job/my

RE: git job weirdness (in Changes)

2023-07-04 Thread 'David Balazic' via Jenkins Users
the first (changes list) was not tested as only one commit was done between latest en previous build. Regards, David From: 'David Balazic' via Jenkins Users Sent: Tuesday, 20 June 2023 10:17 To: 'David Balazic' via Jenkins Users Subject: git job weirdness (in Changes) Hi!

RE: git job weirdness (in Changes)

2023-09-05 Thread 'David Balazic' via Jenkins Users
n that local copy. The third issue (file list look) is still present in the new job, while the first (changes list) was not tested as only one commit was done between latest en previous build. Regards, David From: 'David Balazic' via Jenkins Users Sent: Tuesday, 20 June 2023 10:17 T

GIT sparse checkout and triggering a build

2023-10-26 Thread 'David Balazic' via Jenkins Users
Hi! I have two questions. As our git repo content was split into two projects (the files stayed the same, we just build the two in two separate Jenkins jobs), the situation is like this: The git root contains folders related to one project, for example foo1, foo2 and foo3 and folders related t

RE: GIT sparse checkout and triggering a build

2023-11-13 Thread 'David Balazic' via Jenkins Users
file.ext (no leading slash, unlike the sparse chekout paths) A clearer documentation would be nice. Regards, David Balažic (sorry fort he long email footer inserted by my organization) -Original Message- From: 'David Balazic' via Jenkins Users Sent: Thursday, 26 October

RE: GIT sparse checkout and triggering a build

2023-11-13 Thread 'David Balazic' via Jenkins Users
A small typo: the actual lines under "Included Regions" were: ^foo1/.* ^foo2/.* ^foo3/.* Sorry, David Balažic -Original Message----- From: 'David Balazic' via Jenkins Users Sent: Monday, 13 November 2023 13:54 To: jenkinsci-users@googlegroups.com Subject: RE: GIT