Can not revert the "Keep this build forever" Option
470 views
Skip to first unread message
Thomas Marek
Jun 24, 2011, 9:42:12 AM6/24/11
to Jenkins Users
Hello,
for quite some time we have the problem that new builds get marked as
"Keep this build forever" automatically and we can not revert that?!
It seams that every build depends on the previous build, but we don't
know why?!
e.g. if i call http://.../job/.../90/confirmDelete?json={}&Submit=Delete+this+build
i get the error message "Warning: Cannot delete this build, because it
is #91 depends on this"
We use matrix based jobs and the Build-Publisher plugin.
Any ideas?
Thanks in advance!
Thomas
for quite some time we have the problem that new builds get marked as
"Keep this build forever" automatically and we can not revert that?!
It seams that every build depends on the previous build, but we don't
know why?!
e.g. if i call http://.../job/.../90/confirmDelete?json={}&Submit=Delete+this+build
i get the error message "Warning: Cannot delete this build, because it
is #91 depends on this"
We use matrix based jobs and the Build-Publisher plugin.
Any ideas?
Thanks in advance!
Thomas
Gary
Jun 24, 2011, 8:25:57 PM6/24/11
to Jenkins Users
We have the same problem too, I'm quickly running out of disk space
because of it.
I did notice that some of the initial unstable or failed builds would
get marked as failed and automatically marked as "keep forever"....not
sure why though.
We as well are using matrix based jobs.
On Jun 24, 9:42 am, Thomas Marek <tma...@googlemail.com> wrote:
> Hello,
>
> for quite some time we have the problem that new builds get marked as
> "Keep this build forever" automatically and we can not revert that?!
> It seams that every build depends on the previous build, but we don't
> know why?!
> e.g. if i callhttp://.../job/.../90/confirmDelete?json={}&Submit=Delete+this+build
because of it.
I did notice that some of the initial unstable or failed builds would
get marked as failed and automatically marked as "keep forever"....not
sure why though.
We as well are using matrix based jobs.
On Jun 24, 9:42 am, Thomas Marek <tma...@googlemail.com> wrote:
> Hello,
>
> for quite some time we have the problem that new builds get marked as
> "Keep this build forever" automatically and we can not revert that?!
> It seams that every build depends on the previous build, but we don't
> know why?!
Gary
Jun 24, 2011, 8:29:06 PM6/24/11
to Jenkins Users
Also, I did notice that the project that is being marked like this has
"track svn of another project" being used. The one that it's tracking
happens to be the one with all the "keep forever" builds.
"track svn of another project" being used. The one that it's tracking
happens to be the one with all the "keep forever" builds.
soowei
Jul 11, 2011, 6:26:17 PM7/11/11
to Jenkins Users
There now is a bug on JIRA for this exact issue.
https://issues.jenkins-ci.org/browse/JENKINS-10197
- Soo Wei
On Jun 24, 5:29 pm, Gary <gary.y...@gmail.com> wrote:
> Also, I did notice that the project that is being marked like this has
> "track svn of another project" being used. The one that it's tracking
> happens to be the one with all the "keepforever" builds.
> > > It seams that everybuilddepends on the previousbuild, but we don't
https://issues.jenkins-ci.org/browse/JENKINS-10197
- Soo Wei
On Jun 24, 5:29 pm, Gary <gary.y...@gmail.com> wrote:
> Also, I did notice that the project that is being marked like this has
> "track svn of another project" being used. The one that it's tracking
>
> On Jun 24, 8:25 pm, Gary <gary.y...@gmail.com> wrote:
>
>
>
>
>
>
>
> > We have the same problem too, I'm quickly running out of disk space
> > because of it.
>
> > I did notice that some of the initial unstable or failed builds would
> > get marked as failed and automatically marked as "keepforever"....not
> On Jun 24, 8:25 pm, Gary <gary.y...@gmail.com> wrote:
>
>
>
>
>
>
>
> > We have the same problem too, I'm quickly running out of disk space
> > because of it.
>
> > I did notice that some of the initial unstable or failed builds would
> > sure why though.
>
> > We as well are using matrix based jobs.
>
> > On Jun 24, 9:42 am, Thomas Marek <tma...@googlemail.com> wrote:
>
> > > Hello,
>
> > > for quite some time we have the problem that new builds get marked as
> > > "Keepthisbuildforever" automatically and we can not revert that?!
>
> > We as well are using matrix based jobs.
>
> > On Jun 24, 9:42 am, Thomas Marek <tma...@googlemail.com> wrote:
>
> > > Hello,
>
> > > for quite some time we have the problem that new builds get marked as
> > > It seams that everybuilddepends on the previousbuild, but we don't
> > > know why?!
> > > e.g. if i callhttp://.../job/.../90/confirmDelete?json={}&Submit=Delete+this+build
> > > i get the error message "Warning: Cannot delete thisbuild, because it
> > > e.g. if i callhttp://.../job/.../90/confirmDelete?json={}&Submit=Delete+this+build
> > > is #91 depends on this"
>
> > > We use matrix based jobs and theBuild-Publisher plugin.
>
Thomas Marek
Jul 12, 2011, 3:10:23 AM7/12/11
to jenkins...@googlegroups.com
Cool! Thanks for the info!
Thomas
Thomas
Reply all
Reply to author
Forward
0 new messages