On Mon, Aug 27, 2018 at 10:02 AM Carles Capdevila Tejada
wrote:
> Right now it's working with:
> The good plugin name -> gitblit
> The old package name -> com.tsystems.sbs.gitblitbranchsource
>
> It seems to me that this is not perfect, but at least the plugin name is
> correct and this would
> w
>
> Which you can make those “6–12 projects” do. All they need to do is go
> the plugin manager, uninstall the old plugin from *Installed* (which
> will prompt to restart—but do not), then select the new plugin from
> *Available* and *Download now and install after restart* and agree to
> rest
On Sat, Aug 11, 2018 at 9:54 AM Oleg Nenashev wrote:
> There is a risk that two plugins get installed at once, and Jenkins admins
> will be responsible to manage it.
Which you can make those “6–12 projects” do. All they need to do is go
the plugin manager, uninstall the old plugin from *Installe
Hi,
Sorry, I have missed this thread.
Is there any way at all that I can migrate the jobs from the old plugin to
> the new (artifactId:*gitblit-branch-source *->* gitblit*)? I reckon not.
>
plugin name != classpath. As long as classpaths are the same, there should
be no compatibility. There is
