run 7.0.x pipeline

[almerico]

No description provided.

[ryandawsonuk]

Currently blocked on this as needs jenkins-x/updatebot#73

Instead for now having to build the 7.0.x branch using https://github.com/Activiti/activiti-scripts/tree/testerfor70xtrain

[salaboy]

@almerico @ryandawsonuk was this solved already?

[ryandawsonuk]

No jenkins-x/updatebot#73 is still open. We release 7.0.0.SR1 by relying on activiti-scripts as we weren't able to run the JX pipelines for it

[ryandawsonuk]

The updatebot PR has now been merged. But to get the update we'll need to upgrade to a new JX version. (After a cluster upgrade we'd then need to re-enable the 7.0.x branches for scanning in the Jenkins console.) Seems to me it would be good if #2553 could be tackled at the same time but that one is waiting on a different (still open) JX issue.

[almerico]

@ryandawsonuk I think maven11 image upgrade is enough

[ryandawsonuk]

Oh that would be cool. Unfortunately seems new version of it has not yet been published as last one for builder-maven is from yesterday and for builder-maven-java11 last was five days ago, whereas updatebot PR was merged today

[salaboy]

@almerico @ryandawsonuk what is the status of this?

[ryandawsonuk]

There are no new builder-maven-java11 and all the new builder-maven images are snapshots that seem to relate to particular PRs. I can't see any version that we can point to so still waiting for the JX guys,.

[ryandawsonuk]

@almerico has pointed out that JX have moved their docker images to GCR :)

[salaboy]

@almerico can you close this if this is done?

[almerico]

Done