Expand Jenkins migration guide comparing Jenkins project types
In #208668 (closed) we did a research about how Atlassian Bamboo may import Jenkins projects.
We identified how Jenkins saves configurations populated via the UI in a config.xml
file per project and how we could parse it.
We could expand our Migrating from Jenkins guide with the outcome of the research.
from #208668 (comment 328916533):
A lot of information from this research could be used to expand our Jenkins migration guide as this is essentially a translation of the Jenkins settings from the UI.
E.g. How jobs in Jenkins are sequential, vs parallel by stage in GitLab. Jenkins lets you specify in the same
Build triggers
section whether a pipeline runs onpush
vs on cron schedule while in GitLab it's very different.We could tie in the work done with
jfr-container-builder
as it's complementary to these configurations. For example: a customer has a Pipeline project that runs on a cron schedule and wants to migrate it to GitLab:
- the high level configurations (e.g. cron schedule) can be translated into creating a pipeline schedule
- the content of the pipeline (e.g. running the
Jenkinsfile
) can be initially ported using thejfr-container-builder
Another example: customer has
Build after other projects are built
configuration selected. We could map this setting with multi-project pipelines or pipeline subscriptions.