top

Code management in Cross-Platform Development

The IBM I platform has a mixed opinion which is dominant, dependable, securable, manageable, but it also a good solution provider.    ARCAD Software in its latest release has come with the ARCAD-Builder, which recompiles applications and checks if there is a huge impact on the dependent components. Initially, it was designed to for IBM I environments and integration with other ARCAD software. Later it got integrated with IBM source code management software called Rational Team Concert (RTC), till then there was no IBM i component. Version 3.0 of ARCAD Builder is now generally available on October 30—which has great support for several external code management(SCM) tools, which includes Subversion(SVN), Git and Microsoft Team Foundation Server(TFS).   Management tools and well-known repository tools like Git and Subversion for open source development and TFS is preferred by Windows development teams. ARCAD is making sure that these developer tools are popular in various companies where IBM plays the vital role and development tools can increase the usage of cross-platform work. Instead of forcing the developers to use tools which they prefer or forcing those to buy multiple tools that perform the same task in various development environments. This tool is built for development teams to have Common source repository which is becoming is a standard in the future.   IBM I component is implemented by ARCAD-Builder to the development teams who opt for non-IBM I repository enables the IBM i, which is also the part of build phase to be part of the overall build phase. Companies which have already started the implementation of multi-platform projects are suggesting ARCAD to provide them a single source code management tool. If you have already started using tools like TFS or Git for managing source code, these tools can be managed by IBM i. When Frontend and Backend application development is combined, that becomes a rule which force development teams to cooperate with each other, if there are changes made, there may be possibilities of having more impact on the frontend/backend. Cross-platform integration raises many expected and unexpected issues. This is occurred with higher frequency due to the increase in the open system developers. ARCAD and IBM i are aiming to expand a bit more. According to Magne, IBM i is no more a repository, the programmers of this generation are getting open source technologies with them and successfully using it. Git’s popularity has increased in the very short span of time in the current market, it is one of the highly regarded repositories. Now IBM is providing installable products on IBM i which provides high-level security for Git repositories users for handling Git repositories directly on IBM i. There is no central point of failure in Git because of its distributed nature. Last delivered files backup is taken as a backup even when the server goes down. In many scenarios where you find Git with Jenkins which is a well-known tool for handling build phase in open source environments. ARCAD-Builder was designed with Jenkins integration to increase the reciprocal capabilities of open source and IBM i. The IBM i and Microsoft Windows live, which come under common roof called IBM i shops which will be an added advantage for opting this tool which has better compatibility. Nowadays for Windows development, many IBM i shops are using TFS. According to Magne “TFS is being used for IBM i Source code management which has Eclipse as a plug-in. Microsoft had its own set of tools with its complete isolated development environment could not ignore the rest of the world." In a similar way, even IBM had to push RTC in the i community, leaving behind its isolation. The main motto was to have a single repository in RTC. Earlier IBM i community used to prefer its own set of tools and repository. Now both IBM and Microsoft recognized that Git can play that role and that shops using Git would prefer to extend using Git, which is now well supported by RTC and TFS. Magne told that “There is a shift from proprietary version control, there is a natural outcome of IBM i up gradation and  multi-tier application architecture”. There is a slight change in developer’s job because it is no longer single language dominance. It might be surprising that the number of python developers is more than Java developers. It depends on the individual organization  which language is best for them. IBM is planning to provide many options for development by expanding IBM i support for many languages. Handling entire code options, whether it is open source or not, is where ARCAD comes into the consideration.
Rated 4.0/5 based on 20 customer reviews
Normal Mode Dark Mode

Code management in Cross-Platform Development

Thomas Perez
Blog
25th Oct, 2016
Code management in Cross-Platform Development

The IBM I platform has a mixed opinion which is dominant, dependable, securable, manageable, but it also a good solution provider.   

ARCAD Software in its latest release has come with the ARCAD-Builder, which recompiles applications and checks if there is a huge impact on the dependent components. Initially, it was designed to for IBM I environments and integration with other ARCAD software. Later it got integrated with IBM source code management software called Rational Team Concert (RTC), till then there was no IBM i component. Version 3.0 of ARCAD Builder is now generally available on October 30—which has great support for several external code management(SCM) tools, which includes Subversion(SVN), Git and Microsoft Team Foundation Server(TFS).

 

Management tools and well-known repository tools like Git and Subversion for open source development and TFS is preferred by Windows development teams. ARCAD is making sure that these developer tools are popular in various companies where IBM plays the vital role and development tools can increase the usage of cross-platform work. Instead of forcing the developers to use tools which they prefer or forcing those to buy multiple tools that perform the same task in various development environments. This tool is built for development teams to have Common source repository which is becoming is a standard in the future.

 

IBM I component is implemented by ARCAD-Builder to the development teams who opt for non-IBM I repository enables the IBM i, which is also the part of build phase to be part of the overall build phase. Companies which have already started the implementation of multi-platform projects are suggesting ARCAD to provide them a single source code management tool. If you have already started using tools like TFS or Git for managing source code, these tools can be managed by IBM i.

When Frontend and Backend application development is combined, that becomes a rule which force development teams to cooperate with each other, if there are changes made, there may be possibilities of having more impact on the frontend/backend. Cross-platform integration raises many expected and unexpected issues. This is occurred with higher frequency due to the increase in the open system developers.

ARCAD and IBM i are aiming to expand a bit more. According to Magne, IBM i is no more a repository, the programmers of this generation are getting open source technologies with them and successfully using it. Git’s popularity has increased in the very short span of time in the current market, it is one of the highly regarded repositories. Now IBM is providing installable products on IBM i which provides high-level security for Git repositories users for handling Git repositories directly on IBM i.

There is no central point of failure in Git because of its distributed nature. Last delivered files backup is taken as a backup even when the server goes down. In many scenarios where you find Git with Jenkins which is a well-known tool for handling build phase in open source environments. ARCAD-Builder was designed with Jenkins integration to increase the reciprocal capabilities of open source and IBM i.

The IBM i and Microsoft Windows live, which come under common roof called IBM i shops which will be an added advantage for opting this tool which has better compatibility. Nowadays for Windows development, many IBM i shops are using TFS. According to Magne “TFS is being used for IBM i Source code management which has Eclipse as a plug-in. Microsoft had its own set of tools with its complete isolated development environment could not ignore the rest of the world."

In a similar way, even IBM had to push RTC in the i community, leaving behind its isolation. The main motto was to have a single repository in RTC. Earlier IBM i community used to prefer its own set of tools and repository. Now both IBM and Microsoft recognized that Git can play that role and that shops using Git would prefer to extend using Git, which is now well supported by RTC and TFS.

Magne told that “There is a shift from proprietary version control, there is a natural outcome of IBM i up gradation and  multi-tier application architecture”. There is a slight change in developer’s job because it is no longer single language dominance. It might be surprising that the number of python developers is more than Java developers. It depends on the individual organization  which language is best for them.

IBM is planning to provide many options for development by expanding IBM i support for many languages. Handling entire code options, whether it is open source or not, is where ARCAD comes into the consideration.

Thomas

Thomas Perez

Blog Author
Thomas is a Python evangelist and a programming ninja. Ask him about: open-source software, code-readability and functional programming.
Website : https://www.zeolearn.com

Leave a Reply

Your email address will not be published. Required fields are marked *

SUBSCRIBE OUR BLOG

Follow Us On

Share on

other Blogs

20% Discount