[Feature Request] SCM Extension point

[srinivas upadhya]

Im working towards introducing SCM extension point. In many ways similar to Package Repository Extension point, has a few differences which requires a different extension point (explained in the github issue).

Motivation being greater coverage for SCM materials. It will also provide an opportunity to move a few SCMs out as plugins which aids faster fixes & feature implementations, also making the core smaller.

Do let me know if someone has specific interest in this & have some feedback/questions.

[Vasco Figueira]

Hi,

Would this allow a pipeline to declare as a material a specific path in a repository?

Cheers,

Vasco

[srinivas upadhya]

Im working on providing an end-point (show as 'end-point' cloud in image). You will still need to write a implementation for end-point (shown as 'implementation' cloud in image) which will poll for changes & fetch code etc. sample plugin.

With this end-point you get the flexibility to write the implementation to your liking. i.e. you can write your own plugin which that will say allow, 'declare as a material a specific path in a repository'

[Ashwanth Kumar]

Can you provide a similar diagram (or an overlay) for the life cycle of messages in JSON API for the endpoint?

I'm specifically looking for when is "Latest SCM Revision" and "Latest SCM Revision Since" called? 

--
You received this message because you are subscribed to the Google Groups "go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email to go-cd+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Ashwanth Kumar / ashwanthkumar.in

[srinivas upadhya]

the first time a material is polled Go does a 'get latest revision'..from that point on it will do 'get latest revisions since' (since Go knows the last polled revision for that material)