Get Involved. Join the Conversation.


    Christopher Maggiulli
    Integration Cloud (VBCS, PCS, ICS), DBaaS, APEX
    Topic posted October 30, 2018 by Christopher MaggiulliSilver Crown: 22,500+ Points, last edited December 30, 2018 by Arijit ChakrabortyBronze Trophy: 5,000+ Points, tagged Administration, Deployment, Git, Issues, Maven, Pipeline, Release, Tip 
    348 Views, 1 Comment
    Integration Cloud (VBCS, PCS, ICS), DBaaS, APEX
    Tying together devops using devcs

    So we onboarded Oracle Integration Cloud about 8 months ago for a pilot app.  We since built a myriad of applications (3 applications that use VBCS as a front end, PCS runtime, ICS for connectivity), then 3 other mobile / hybrid applications strictly using visual builder, an APEX application and a variety of PL/SQL utilities.


    The hardest part is the ops side.  Promoting from test to prod.  Keeping track of what version goes with what.  Collaborating, etc.  I was told devcs is "foundational" so I just spun up an instance since its free.  It created a git repo, confluence wiki, jira,and jenkins.

    I am very knowledgable on these tools in their more traditional sense - but is devcs meant for OIC?  I want to version our vbcs source code.  I want to version our integrations and runtimes.  I want to group the integrations / runtimes / vbcs components that go together to make "one application" together, and separate them from the other integrations / vbcs apps / bpmn runtimes that belong to different "applications".  I want a way to deploy from test to production automatically.  Can I do this in devcs?  has anyone done this successfully?

    I feel like after a year I have a shallow but broad knowledge of all these components (plus idcs, oracle jet, weblogic, em, dbaas, apex, pl/sql, etc) but I'm having a hard time tying everything together and placing each application in its own neat little box.  I don't want things to get unruly, but after tinkering with devcs for a few hours I'm coming up with more questions than answers. 



    • Shay Shmeltzer

      Yes DevCS is exactly meant for these goals.

      Here is a quick demo that shows the full CI/CD cycle in DevCS:

      Oracle Developer Cloud Service Overview Demo

      As you can see there you can use the build steps to do the CI/CD steps.

      Leveraging the Git repository you can version the code of the different artifacts in your app - you might want to leverage separate git repositories in the same project for different types of artifacts.

      For VB apps here is a quick intro on the integration: Managing Visual Builder Code with Developer Cloud Service

      APEX and OIC Integrations/processes don't directly expose the code right now - but the do offer APIs that let you "export" the app - which you can then import into the Git repo.

      As for CI/CD - this is what the jobs and pipelines in DevCS do.

      Again different services have different ways of achieving CI/CD automation. Right now for APEX/OIC you can use their import APIs as well as some other lifecycle APIs you can use, see their doc - for example for PCS  - Designtime Projects

      You can invoke those using shell scripts in a build step.

      VB is working on publishing CI/CD APIs in the upcoming release.