Some of that is not quite correct.
A 'build' is a specific run of a job, yes, and Jenkins stores the logs,
parameters and other metadata associated with the build, along with any data
produced by publishers used in the build (unit test reports, warnings analysis,
stuff like that). It does *not*
Hi Paulo,
It's tricky when you start, I remember finding this all a bit confusing too!
On 25/01/2013 11:16, Paulo Matos wrote:
* Builds are the files created during a job.
My understanding is that a build is a specific, numbered run of a job.
So if a job triggers the
creation of 2 files and
Hi,
I am slightly confused by the difference between artifacts and builds.
Correct me if I am wrong and please add whatever I might have missed.
* Builds are the files created during a job. So if a job triggers the
creation of 2 files and 3 directories, that's the build and it exists in