search

jenkinsci / plasticscm-plugin

A plugin for Jenkins to be able to use Plastic SCM
MIT License
15 stars 31 forks source link

Support multibranch pipeline #32

Open ahatala opened 4 years ago

ahatala commented 4 years ago

The plastic plugin doesn't register as source for multibranch pipeline jobs.

thomrohit commented 2 years ago

Has this been implemented yet ?

mig42 commented 2 years ago

Hi @thomrohit! I'm afraid this is still a pending feature request.

Tommigun1980 commented 1 year ago

You can turn on Git support in the Plastic SCM server to achieve that: https://blog.plasticscm.com/2016/10/jenkins-multibranch-pipeline-projects.html

manzinge commented 5 months ago

Apparently there is an additional cost when using the GitServer feature to create a multibranch pipeline (Plastic On-Prem pricing for around 23$ p. User). Is there any known workaround to get the multibranch pipeline working with "just" a cloud repository?

mig42 commented 4 months ago

Hi @manzinge , multibranch support is still a pending feature to be implemented. It's in our roadmap but we can't commit to a date at this point - sorry for the inconvenience.

manzinge commented 4 months ago

Hey @mig42 thank you for the response! Is it possible to use the GitServer feature of the on-premise feature without paying the additional cost I mentioned above? I don't think the hefty additional cost for a feature that is still pending for the cloud feature is feasible. Please let me know if you have any Idea on how to get this working

mig42 commented 4 months ago

Unfortunately, I don't have that information 😔 Try contacting support and explaining your situation to them, maybe there's something they can do for your scenario.

alexgeek commented 2 months ago

Heya, we'd love to get this in too. Has these been looked at all at present? Potentially some of myself or one my team could look at implementing it.

mig42 commented 2 months ago

Hi @alexgeek,

Our plan is to adapt our plugin to leverage the SCM API plugin for SCM support in Jenkins. However, due to our present bandwith, the priority for this work has been pushed back in our team.