Hi all,
A while ago Iv'e implemented a plugin that allows you to run git-bisect
inside jenkins. I started it as a project for my company and figured that
other people could use it too; but it appears that my use-case was not
everyones use-case, and... that writing plugins is not my area of
Hi Robert, the link you gave describes how to add an action to a build. but
I can't store this field in a build's action, because I might lose track of
this field. For example, if a build fails before it gets to my plugin, or
at some time the user decides to delete all previous build.
So it's
remoteFs should be automatically created by agents on-demand. Robert has
pointed to the right part of the code.
However, there are some tricky bits with that...
1. Jenkins agent is able to connect and ACCEPT RUNS even if RemoteFs is
not writable
2. The runs will obviously fail, but it
It should not be a problem with Stephen's speed-reading skills :)
I'm +1 for going forward.
I spent pretty much time on cleaning up Everyone from some my repos, and
just deleting it seems to be the most feasible approach.
Even if something goes wrong with automatic migration, we have enough
