Thank you. That was exactly what I was looking for.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view
Look for "Rename a class" on
https://wiki.jenkins.io/display/JENKINS/Hint+on+retaining+backward+compatibility
it
will show how to use XStream aliases.
On Mon, Oct 1, 2018 at 7:24 AM pallen wrote:
> I renamed my MultiBranch classes from *ScmSource to *SCMSource forgetting
> the impact on the XML
I renamed my MultiBranch classes from *ScmSource to *SCMSource forgetting
the impact on the XML configuration data. I could undo the rename, or
better find a way to read the old XML configuration data?
--
You received this message because you are subscribed to the Google Groups
"Jenkins
Just release a new version?
On Mon, Oct 1, 2018 at 10:19 PM Jesse Glick wrote:
> On Mon, Oct 1, 2018 at 8:20 AM pallen wrote:
> > How do I remove a bad release from the Update Centre!
>
> If it is already in the hands of users, I think you need to “fix forward”.
>
&
On Mon, Oct 1, 2018 at 8:20 AM pallen wrote:
> How do I remove a bad release from the Update Centre!
If it is already in the hands of users, I think you need to “fix forward”.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developer
Thank you. Yes, I am the plugin owner.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this
You could add an item into here
https://github.com/jenkins-infra/update-center2/blob/master/src/main/resources/artifact-ignores.properties
if
you are the owner of the plugin.
On Mon, Oct 1, 2018 at 8:20 PM pallen wrote:
> Hi Guys,
>
> How do I remove a bad release from the Update Centr
Hi Guys,
How do I remove a bad release from the Update Centre!
p4-plugin 1.9.0
Looks like a case-sensitivity Class Name refactor has messed up the Jenkins
XML configuration. Any tips on that too? or just reinstate the old class
name?
Kind regards,
Paul
--
You received this message
