Skip to content

[JENKINS-47803 && JENKINS-7009] Remove working copy if external is broken - #247

Open
PhilippHomann wants to merge 2 commits into
jenkinsci:masterfrom
PhilippHomann:removeOnExternalFailure
Open

[JENKINS-47803 && JENKINS-7009] Remove working copy if external is broken#247
PhilippHomann wants to merge 2 commits into
jenkinsci:masterfrom
PhilippHomann:removeOnExternalFailure

Conversation

@PhilippHomann

@PhilippHomann PhilippHomann commented Nov 4, 2020

Copy link
Copy Markdown

Currently checkout will silently ignores an external failure due to locked working copy.
So build continues without one recognizing that the result is build using an old revision.

With this fix the update will behave like the non-external checkout: delete working copy and start with a fresh one.

@PhilippHomann

Copy link
Copy Markdown
Author

Anyone?
@daniel-beck @jglick

@daniel-beck

Copy link
Copy Markdown
Member

I'm not a maintainer. The only reason I show up in the history is because I staged security fixes.

@jglick

jglick commented Nov 27, 2020

Copy link
Copy Markdown
Member

I also do not pretend to maintain this plugin. Not sure if anyone does.

@PhilippHomann
PhilippHomann force-pushed the removeOnExternalFailure branch from 814a5e8 to b04c6c2 Compare September 9, 2026 08:07
@MarkEWaite
MarkEWaite removed their request for review September 9, 2026 11:58

@Eccenux Eccenux left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm confused about this change:
b04c6c2

Is that related to detecting broken externals?


@Issue("JENKINS-47803")
@Test
public void lockedExternal() throws Exception {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should have a comment on the setup phase of the test – what is being setup and why

@Test
public void ensureCancelOnExternalsFail() throws Exception {
Proc p = runSvnServe(getClass().getResource("JENKINS-777.zip"));

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above. should have a comment on the setup phase of the test – what is being setup and why

}
}

void lockWorkspace(String dbFile, String pathToLock) throws Exception {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is an interesting way to emulate a lock. Is this documented somewhere?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants