GitLab 8.8 released with Pipelines
about.gitlab.comJenkins 2.0 is also out with a new revamped pipeline feature.
Has anyone had experience migrating from jenkins to gitlab or the other way. What were the gains/issues encountered when trying to re-organized their existing setup?>
I'm also in the process of moving from jenkins to gitlab... and until now, the process is pretty smooth and easy ... gitlab-ci is easier to grasp and to work with... the only issues i got is about things like publishing build results (lints check or test results /counts ) althoug there is basic support for artifacts. it's not easily possible (at least for now) to fetch the artifacts for a given commit or branch without doing multiple api calls.
Thanks. We are working on bringing missing features to artifacts, so we will improve that workflow.
Jenkins 2 pipeline feature didn't look like more then the plugin they had before - but bundled into the core.
We just moved from a Jenkins Pipeline-setup to GitLab, didn't take that long time and our builds started going a lot faster after that.
Glad to hear that! I don't think there is anything you can't do with Jenkins with plugins. But in GitLab we try to make the best practice the default. Using build slaves is an option in Jenkins but our Runner is by default set up on another machine. Having your settings stored in the repository is an option in Jenkins but the default in GitLab with a nice syntax.
Wondering what's the big feature announcement tomorrow.
The hint was very obvious.
The blog post also mentioned: "This release contains another cool feature that we're saving for tomorrow."
maybe, this is it: https://webcache.googleusercontent.com/search?q=cache:9H9hnY...
It was in 8.8 milestone: https://gitlab.com/gitlab-org/gitlab-ce/issues/3299
Indeed. I almost can not contain my excitement.
:) thanks for not spoiling it here