When the seed job runs next time, any job that isn't explicitly part of the seed job is disabled.
The existing job history will stick around and eventually someone should delete them manually from Jenkins. On Mon, Sep 21, 2020 at 10:46 AM Valentyn Tymofieiev <[email protected]> wrote: > We are removing several jobs associated with Py2 and Py35. Is removing a > groovy file sufficient or Jenkins will still remember the job from the > earlier 'Seed' invocation and continue running it until manually disabled? > If so, what's the process for manually disabling the job? > > Looked at Jenkins tips on the dev wiki[1] but didn't see these > instructions. > > Thanks! > > [1] https://cwiki.apache.org/confluence/display/BEAM/Jenkins+Tips >
