I almost missed that Developer Cloud Service has been updated to 12.2.1. Great news as we now can use JDeveloper 12.2.1 to access the agile capabilities like
- Interact with Tasks/Issues in JDeveloper
- Leverage the Team view in JDeveloper (tasks, builds, and code repositories)
- Connect to DevCS and its projects from inside JDeveloper
- Create Agile boards and manage sprints in Developer Cloud Service
- Associate code commits with specific tasks
- Monitor team activity in the Team Dashboard
- Handle Git transactions
For more information about how JDeveloper and the DCS are integrated watch this video ‘Agile development with Oracle JDeveloper and Oracle Developer Cloud Service’.
This was possible since last year. So, what’s new?
New is that the JCS is also available in 12.2.1 and that we can use the whole continuous integration scenario. For this we have to configure a 12.2.1 JCS instance which then can be used for deployment. When we select to create a new instance of a JCS we see the new wizard which allows us to select a WebLogic Server 12c in version 12.2.1
On the ‘Edition’ page we don’t find anything new so we skip it and go to the Details page where we specify the needed information for the service, database configuration, backup and the WebLogic user
After getting the confirmation page we create the new service and finally after a short time we see the new service
A look at the Enterprise Manager of the new service shows the new login page
and after logging in the new 12.2.1 Enterprise Manager
It look modern and fresh. However, this is not what this blog is about. I installed my ADF Version Web Service BlogAdfVersionWS to check which ADF version is running in this instance. Selection the modules we find the test point on the right side of the Web Service
After selecting the test point we select to run the ‘GetVersion’ service
That’s right what we expect when running ADF 12.2.1!
Next time we see how to change the build and deployment part of the DCS to work with the JCS 12.2.1.