Archived Artifacts

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Archived Artifacts

Nicky Ramone
Hello.

I noticed that despite my configuration is defined so that no artifacts are archived, the artifacts are stored in the disk anyway for all builds.
Example:
$JENKINS_HOME/jobs/dummy/modules/com.dummy/builds/2012-07-12_10-24-06/archive/com.dummy/dummy/dummy,tar.gz

Is this due to fingerprinting? is there any way to avoid this?

Thanks
Regards
Reply | Threaded
Open this post in threaded view
|

Re: Archived Artifacts

Nicky Ramone
Did anyone notice the same behavior?

On Mon, Dec 10, 2012 at 2:41 PM, Nicky Ramone <[hidden email]> wrote:
Hello.

I noticed that despite my configuration is defined so that no artifacts are archived, the artifacts are stored in the disk anyway for all builds.
Example:
$JENKINS_HOME/jobs/dummy/modules/com.dummy/builds/2012-07-12_10-24-06/archive/com.dummy/dummy/dummy,tar.gz

Is this due to fingerprinting? is there any way to avoid this?

Thanks
Regards

Reply | Threaded
Open this post in threaded view
|

Re: Archived Artifacts

Kanstantsin Shautsou
In reply to this post by Nicky Ramone
You use maven style project, it saves build artifacts. If you have problems with space, decrease history.

On 10.12.2012, at 20:41, Nicky Ramone <[hidden email]> wrote:

> Hello.
>
> I noticed that despite my configuration is defined so that no artifacts are archived, the artifacts are stored in the disk anyway for all builds.
> Example:
> $JENKINS_HOME/jobs/dummy/modules/com.dummy/builds/2012-07-12_10-24-06/archive/com.dummy/dummy/dummy,tar.gz
>
> Is this due to fingerprinting? is there any way to avoid this?
>
> Thanks
> Regards

Reply | Threaded
Open this post in threaded view
|

Re: Archived Artifacts

domi@fortysix.ch
In the advanced section of your maven build, you can "Disable automatic artifact archiving"
With the "Create Job Advanced Plugin" you can disable this setting per default for new jobs: https://wiki.jenkins-ci.org/display/JENKINS/Create+Job+Advanced+Plugin
/Domi

On 18.12.2012, at 16:26, Kanstantsin Shautsou <[hidden email]> wrote:

> You use maven style project, it saves build artifacts. If you have problems with space, decrease history.
>
> On 10.12.2012, at 20:41, Nicky Ramone <[hidden email]> wrote:
>
>> Hello.
>>
>> I noticed that despite my configuration is defined so that no artifacts are archived, the artifacts are stored in the disk anyway for all builds.
>> Example:
>> $JENKINS_HOME/jobs/dummy/modules/com.dummy/builds/2012-07-12_10-24-06/archive/com.dummy/dummy/dummy,tar.gz
>>
>> Is this due to fingerprinting? is there any way to avoid this?
>>
>> Thanks
>> Regards
>

Reply | Threaded
Open this post in threaded view
|

Re: Archived Artifacts

Jan Seidel-2
In reply to this post by Nicky Ramone
Hi Nicky,

is the comma set on purpose?
dummy,tar.gz <- look between dummy and tar

Regards
Jan

Am Montag, 10. Dezember 2012 18:41:36 UTC+1 schrieb Nicky Ramone:
Hello.

I noticed that despite my configuration is defined so that no artifacts are archived, the artifacts are stored in the disk anyway for all builds.
Example:
$JENKINS_HOME/jobs/dummy/modules/com.dummy/builds/2012-07-12_10-24-06/archive/com.dummy/dummy/dummy,tar.gz

Is this due to fingerprinting? is there any way to avoid this?

Thanks
Regards
Reply | Threaded
Open this post in threaded view
|

Re: Archived Artifacts

Nicky Ramone
In reply to this post by domi@fortysix.ch
Domi, I think this is the solution to my problem. I will try this.
Thanks!

On Tue, Dec 18, 2012 at 1:04 PM, domi <[hidden email]> wrote:
In the advanced section of your maven build, you can "Disable automatic artifact archiving"
With the "Create Job Advanced Plugin" you can disable this setting per default for new jobs: https://wiki.jenkins-ci.org/display/JENKINS/Create+Job+Advanced+Plugin
/Domi

On 18.12.2012, at 16:26, Kanstantsin Shautsou <[hidden email]> wrote:

> You use maven style project, it saves build artifacts. If you have problems with space, decrease history.
>
> On 10.12.2012, at 20:41, Nicky Ramone <[hidden email]> wrote:
>
>> Hello.
>>
>> I noticed that despite my configuration is defined so that no artifacts are archived, the artifacts are stored in the disk anyway for all builds.
>> Example:
>> $JENKINS_HOME/jobs/dummy/modules/com.dummy/builds/2012-07-12_10-24-06/archive/com.dummy/dummy/dummy,tar.gz
>>
>> Is this due to fingerprinting? is there any way to avoid this?
>>
>> Thanks
>> Regards
>