Hi Radim,
Sorry, I don't think using current
ci.codenvycorp.com for anything production related is a good idea.
In general it has no any SLA and as solely (kind of support for it) person I simple have no knowledge of how important part of it works. So if something breaks on Codenvy CI it might take weeks for repair. Unfortunately person who did setup Codenvy CI left company and now Codenvy CI run as-is till something serious breaks, then it need to simple be shut down.
In particular for that job in question it had specific purpose like semi-manual run of series of job for comparing stability of it to central CI infrastructure. Because of this it was made in dirty and hackish way without any security, monitoring and backups in mind. It's nothing close to production grade.
Cloning of job is virtually impossible because job designed to be sole job on that slave. I doubt it can run with other job (even cloned) at the same slave.
I see that migration
codenvy.ci to central CI has no timeframe and and has enough manpower allocated to it.
From that I seeing it's very low priority effort.
Sorry, but adding new jobs to Codenvy CI isn't the option, even temporary (How temporary? Do you have due date and manpower for moving out of it? Which priority agreed for that move?).
If that job is critical for che7 and onward then it's even worse, please just don't use codenvy CI for anything critical.
