Solution for FLEXDEPLOY-11430

If you are upgrading to 7.0.0.0+ (even 8.0.0.0+) from any version before 7.0.0.0, and you used custom groovy code, you may be affected by FLEXDEPLOY-11430.

To find out easily if you are affected, check the row count of the following query.

select 'pipeline_stage_step' objectType, pipeline_stage_step_id id, data from fd.pipeline_stage_step pss
join fd.pipeline_stage ps
on ps.pipeline_stage_id = pss.pipeline_stage_id
join fd.pipeline_version pv
on ps.pipeline_version_id = pv.pipeline_version_id
join fd.pipeline_definition p
on pv.pipeline_definition_id = p.pipeline_definition_id
and p.active_pipeline_version_id = pv.pipeline_version_id
where active_copy = 'Y'
and data like '%import flexagon.fd.model.appmodules%'
union
select 'pipeline_stage_gate', pipeline_stage_gate_id, data from fd.pipeline_stage_gate psg
join fd.pipeline_stage ps
on ps.pipeline_stage_id = psg.pipeline_stage_id
join fd.pipeline_version pv
on ps.pipeline_version_id = pv.pipeline_version_id
join fd.pipeline_definition p
on pv.pipeline_definition_id = p.pipeline_definition_id
and p.active_pipeline_version_id = pv.pipeline_version_id
where active_copy = 'Y'
and data like '%import flexagon.fd.model.appmodules%'
union
select 'webhook', function_data_id, script_text
from fd.webhook_provider_function_data
where script_text like '%import flexagon.fd.model.appmodules%'
order by objecttype, id;

If there are matches, you will need to update the lines that have

import flexagon.fd.model.appmodules

in them.

Before 7.0.0.0	After 7.0.0.0
`flexagon.fd.model.appmodules.helpers.release.pojo.ReleaseProjectVersion`	`flexagon.fd.model2.pipeline.execution.variables`.`ReleaseProjectVersion`

See the FlexDeploy JavaDoc (7.0), (8.0) to locate additional classes. Some custom Groovy scripts may need to be rewritten due to changes in the objects that were modified.