[JIRA] (JENKINS-10622) Cron Tab still running even when the job is disabled

dbeck@cloudbees.com (JIRA)

unread,

Mar 2, 2017, 2:00:07 PM3/2/17

to jenkinsc...@googlegroups.com

Daniel Beck updated an issue

Jenkins /

JENKINS-10622

Cron Tab still running even when the job is disabled

Change By:	Daniel Beck
Labels:	newbie-friendly

Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

gentoo.integer@gmail.com (JIRA)

unread,

Mar 2, 2017, 2:03:10 PM3/2/17

to jenkinsc...@googlegroups.com

Kanstantsin Shautsou commented on

JENKINS-10622

Re: Cron Tab still running even when the job is disabled

I already made such fix in core and it end with a lot of errors in triggers. I fixed a lot but then restored original behaviour. Jenkins core has no any design in field of ancient triggers + triggers are used for non trigger related stuff like dependencies. Better not touch it.

Add Comment

samhrncir@gmail.com (JIRA)

unread,

Dec 8, 2019, 7:34:02 PM12/8/19

to jenkinsc...@googlegroups.com

Sam Hrncir commented on

JENKINS-10622

Re: Cron Tab still running even when the job is disabled

From reviewing Gregory Boissinot's account, he seems to be no longer activly contributing for the past 3 years and should be taken off as assignee this bug.

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

samhrncir@gmail.com (JIRA)

unread,

Feb 21, 2020, 2:29:02 PM2/21/20

to jenkinsc...@googlegroups.com

Sam Hrncir assigned an issue to Sam Hrncir

Jenkins /

JENKINS-10622

Cron Tab still running even when the job is disabled

Change By:	Sam Hrncir
Assignee:	Gregory Boissinot Sam Hrncir

Add Comment

samhrncir@gmail.com (JIRA)

unread,

Feb 21, 2020, 2:30:03 PM2/21/20

to jenkinsc...@googlegroups.com

Sam Hrncir edited a comment on

JENKINS-10622

Re: Cron Tab still running even when the job is disabled

From reviewing {color:#172b4d}Gregory Boissinot I ' s account, he seems to be no longer activly contributing for the past 3 years and should be taken off as assignee ll have a look at this bug.

{color} issue and report