Old job config keeps triggering

Using Jenkins
1

Jenkins setup: Jenkins 2.462.3

Hi,

I have a job, triggering every 5 minutes.
I changed the script in the ‘Build steps/Command’.

The new script gets executed as expected.

However, Jenkins also keeps triggering the old script. As the old script does not exist anymore, and I find this in my logging “sh: ./xxx.ksh: No such file or directory“

I then renamed the job on Jenkins, but I see the old job name is generated again in the <JENKINS_HOME>/workspace and <JENKINS_HOME>/jobs folder.
A job ID folder is created for every run.

How can I stop/cleanup ghost jobs like that?

Thanks

2

I run my jobs through an SSH agent, and when I notice anomalies—for example, the jobs using an old version of a file—I simply delete both the job folder and the job@tmp folder from the workspace.
These folders are then recreated automatically, but with the current configuration.

If you’re okay with deleting these folders, I think this might solve your problem.

3

Thanks for your reply.

I already deleted the job folders in <Jenkins_HOME>/jobs and <Jenkins_HOME>/workspace directories.
Indeed, they are recreated the next time the ghost job triggers, but there is no config.xlm present.

I also tried renaming the Job. Now I have the renamed job being executed, but the old job also keeps executing. Since the old job executes config tries to execute a non-existing script, the old job doesn’t do anything anymore.