-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Removing AbstractFolder.delete
override
#356
Conversation
r.assertBuildStatus(Result.ABORTED, r.waitForCompletion(build1)); | ||
r.assertBuildStatus(Result.ABORTED, r.waitForCompletion(build2)); | ||
assertTrue(build3.isCancelled()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually this passes even with src/main/
from this PR and pom.xml
from master
, i.e. using the original inherited AbstractItem.delete
implementation which already cancelled builds and queue items for folder children. It would not call FreeStyleProject.delete
prior to Folder.delete
but there was not much practical impact (perhaps only missing calls to ItemListener.fireOnDeleted
) since all of $JENKINS_HOME/jobs/d/
was deleted.
FreeStyleBuild build1 = p.scheduleBuild2(0).getStartCondition().get(); | ||
FreeStyleBuild build2 = p.scheduleBuild2(0).getStartCondition().get(); | ||
QueueTaskFuture<FreeStyleBuild> build3 = p.scheduleBuild2(0); | ||
Thread.sleep(1000); // TODO Queue.cancel(Item) can return false immediately after scheduling |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
…r-plugin into AbstractFolder.delete
@@ -22,7 +22,7 @@ | |||
<changelist>999999-SNAPSHOT</changelist> | |||
<gitHubRepo>jenkinsci/${project.artifactId}-plugin</gitHubRepo> | |||
<!-- remember to change the io.jenkins.tools.bom artifact when changing this --> | |||
<jenkins.version>2.387.3</jenkins.version> | |||
<jenkins.version>2.433</jenkins.version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not yet in an LTS version of course. I have no strong opinion as to whether we should wait for that or not.
Downstream of jenkinsci/jenkins#8645. Subsumes #355.