Excellent Conversation.
I set up the CI-CD rig in a lab with 9.9 and Jenkins and was about to post my experiences but it seems Ana has most succintly exposed the usage
complexities/limitations involved.
A few observations
Merge
The merge feature was especially exciting thing i was hoping to accomplish.The perfect world where different developers would be able to work on the same code in
different braches and we could merge the changes to the trunk.
I used the Subversion base merge feature of the Subversion plugin to merge the flow.xml of branhes together…however the Subversion merge added a few indentations and
comments that the designer did not like and left the flow service unrenderable in designer.I was able to remove the indentations and the merge worked…however I would
not recommend developers mucking around the flow.xmls
So in Summary -It can work…but it should be avoided
With 9.10 …There is feature to merge changes between services between different versions of the same code …but not with a branch…Hopefully this will be added.
Theres also a “diff” feature which annotates the differences between 2 versions of the server(again not with a different branch which I am looking for.)
Product Assets
This seems to be only for IS services .
It also seems that local Service ACL cannot be moved(It will be defaulted in the target server)
What i would like is for features that would allow in-place check in the version Control based on the generally used integration Products like TN Components,Process
Models,Optimize,Apama etc
Now I know this brings up the point regarding the need to install all the products locally and all that…but Why would I set up a CI-CD platform for only part of my
product base.
In order to sell the whole Continous Integration pitch to business…I need to be able ensure it for all products in my Portfolio…Not just for a few.
hopefully this is on SAGs to-do list.
License implication
With 9.12 SAG has come out with a DevOps edition,which allows you to install Local Iss as required by the Local Workstation Development without hitting the existing
Core license Caps.(Paid of Course)
I wonder how customers who setup the CI-CD with previouse versions worked around this issue.Im guessing that they might not even be aware of license violations,given
the layers between Procurement teams and development teams in todays enterprises.
Also the Devops edition came up October 2016 and the local worstation recommendation came out a couple of years at least before(9.6 I think)
This left Customers exposed to new tool features/Recommendation with negative license implications.
Testing
Im still lookign for testing tools to complete my CI-CD setup,
SAG has brought out testSuite with the devops edition in 9.12 but I havent got my hands on it yet(Doesnt even show up in installer)
Overview
It looks like SAG wanted to join the Continous-Integration Continous Development bandwagon and all the benefits that it would provide.
Its more like they wanted to be able to say “Yeah ,we support Continous Integration -Contious Delivery”
But I dont think they’re ‘there’ yet.It may take a few more iterations for them to perfect them for their entire stack and also a few implementation iterations and feedbacks like provided in this thread (Provided the CI-CD fad lasts long enough)