Azure Pipelines vs. Rocket DevOps

It is good tool if you are doing continuous improvements in your code and you wish it goes live whenever you push code to GitHub. So integrating Azure Pipeline, it automatically does CI/CD in the background once you push code/merge code and it is live in few minutes. It also does some automated tests if you have wrote scripts

Incentivized

Rocket Aldon is perfect for simple changes to traditional IBM i development using RPGLE, CL, and DDS. It is great for finding related objects that are referenced in many locations and helping recompile all of these objects. However, Aldon has a particularly hard time with SQL views. For some reason, it is determined to lock every table related to a view even though this is not required by the operating system. Whenever one view references another view, you are always in danger of losing a view permanently if you didn't check it out and promote it. To clarify, imagine you created a view CUSTOMER_INFO. Then you make another view called CUSTOMER_SHIPMENTS that joins the CUSTOMER_INFO to a shipping table. If you ever change CUSTOMER_INFO and then promote it, there is a good chance that Aldon will delete the CUSTOMER_SHIPMENTS view and you will not get a single warning. It doesn't happen every time but when it does you are going to have a real mess on your hands.

Incentivized

• Integration with SonarQube
• Integration with Azure DevOps
• Integration with GitHub

Incentivized

• Allows flexibility for user groups
• Scripting for releasing of code
• Ease of comparing code versions within the tool

Incentivized

• The errors which we got sometimes are not clearly enough.
• There are some let's say hidden options, they could be more visible
• When the process is running we have to remember about manually refreshing to see the current status because it doesn't work automatically

Incentivized

• SQL object promotions
• User interface
• Incomplete error checking
• Fragmented promotion logs

Incentivized

Based on current integration with our release process, we will need to keep this for the future.

Incentivized

Support is hit and miss. Sometimes they give some great assistance and sometimes they are no help at all. It always seems like they can't replicate the problem but then they never try to get on our system to do deeper research. It's kind of frustrating dealing with them. Also, the website isn't that helpful.

Incentivized

We have used the GitHub CI/CD. Earlier we were using the Azure Pipelines but after GitHub had their actions, we integrated that for CI/CD. It runs the tests and makes a production build which can be live. GitHub CI/CD is more useful because we have to make script only once then just by few changes we can deploy it onto Azure, AWS, Google anywhere so we found it more convenient

Incentivized

Aldon provides needed functions for our current implementations and legacy systems. As we move toward modernization, we are going to look at alternatives from reviewing cost, integration capabilities and functionality

Incentivized

• we have had outages from Azure in the past

Incentivized

• Software promotion is much easier and doesn't require custom coding.
• Developers can work collaboratively with less overlap.
• Developers can find objects faster and research code more thoroughly.

Incentivized