Hi Parashant,
Thanks for your response. The below integration is what we are looking for
"When developers check into a source controlled repository (es: Bitbucket), the check ins should trigger CI service (jenkins) to build, validate and submit SDK plugins to stage"
yes it will be similar to Travis CI (as per the documentation).
If we get steps to integrate SDK plugin/Travis CI, that also will be helpful for us. The same way we can try with Jenkins also.
Thank you in advance for your time and assistance!
Thanks,
Deniz
dbaby - Currently we're also taking a look into setting up a Jenkins-based CI workflow. By now we are thinking about the steps and possible issues coming up.
We are thinking about setting up a docker container which contains the Lithium SDK, so we can trigger the submit command after a developer checks in new source code. While the Lithium SDK comes up with some configurations (e.g. upload token) it may be useful to put these into some environment variables, so you can change them (which will be necessary for the token in this case on a monthly basis).
Regards,
Christian
Hi Cike,
Thanks for your response and seems to be good.
But can't we achieve same without a docker container. Because as per documentation in
http://sdk-docs.lithium.com/learn/workflow#continuousIntegration
check-ins triggered (someway not sure) submission of SDK to stage
Thank you in advance for your time and assistance!
Thanks,
Deniz
dbaby - Docker is not mandatory in this case, it's only one approach we're currently looking in. You find different plugins (e.g. for Git, NodeJS) to extend your Jenkins server, so it can be notified by your SCM when developers push their code.
After a push Jenkins will run your defined steps (maybe some testing and finally the push2stage by the Lithium SDK).
Regards,
Christian
Hi Cike,
Thank you for your time and assistance! Will try the same...
Thanks,
Deniz
