Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Prevent: "Migration of unmigrated content due to installation of a new plugin"

Emmet McPoland June 16, 2015

Hi,

We currently use https://wiki.jenkins-ci.org/display/JENKINS/Confluence+Publisher+Plugin.
To publish information to a confluence page from Jenkins.

Every now and again a change is automatically made to the page which strips the Wiki Markup used to define the regions we wish to update.

The exact comment given is :
    (Migration of unmigrated content due to installation of a new plugin)

As it removes the Wiki Markup, the information on the page is inaccurate. Ideally we would like to prevent this from happening. If we cant prevent it we would like to be able to be notified of this exact change (We don't want to be notified of all changes to the page, as we would be inundated).

At the moment, when we noticed that something is off, we rollback the page to a version prior to the migration change. At this stage several builds may have already occurred and therefore the information is still inaccurate.

Ive looked at the each plugin we have installed which provides release notes, none of them released a new version on the same day of the change. Ive also inspected the audit log but theres no mention of a plugin update having occurred on that day either

Referring to https://wiki.jenkins-ci.org/display/JENKINS/Confluence+Publisher+Plugin.
It states to use the Source Editor to add the markup for >=4.x
Unfortunately as OnDemand customers we don't have access to the ability to create User Macros or install the Source Editor. Also its bizarre that the old Wiki Markup method still works apart from something isn't migrating it correctly. What that something is, is a total mystery. Ideally Id like to find out what is causing the migration and prevent it from doing so.

1 answer

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 16, 2015

I suspect the migration is caused because Atlassian deploys releases into Cloud a lot and the upgrade process is spotting your markup and trying to migrate it to the new storage type.

I suspect the only valid approach for Cloud is to get the Jenkins plugin updated so that it posts in the right format instead of wiki. 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events