When you copy a job it should be disabled by default so that any modifications
can be made to it before it tries to run.
New job starts running before I have a chance to configure the job
create a job from existing job start build to quickly
Provide more robust suppression of SCM polling for copied jobs
Provide action to save all unsaved jobs in a folder after copy
committed patch after getting ok from Kohsuke.
Code changed in hudson
User: : mindless
JENKINS-2494 note in change log
I've just copied a Maven job and found that it ran with the existing before I'd saved it.
Has the "Apply" button behaviour caused a regression here?
Code changed in jenkins
User: Stephen Connolly
[FIXES JENKINS-2494] Restore correct behaviour
Integrated in jenkins_main_trunk #2687
Result = UNSTABLE