we want to use the SonarLint to improve code quality in our projects. We’re using mostly COBOL for our in-house development and are trialing proof of concept on both VS Code and Topaz workbench, is there an ETA on COBOL support in VS Code such as is available in the Eclipse IDE plugin?
Welcome to our community. This is not in our roadmap currently, but we will be tracking this thread and we can always adjust our roadmap according to people interest in this feature.
Can you share the type of Cobol project you are working on? Are you editing Cobol in local source files, or are you using a VSCode plugin that connects to the mainframe remotely?
We do standard COBOL programming with SQL and also HOGAN COBOL programming. We are editing Java in local source files but would like to use SonarLint to do the same with COBOL, we also are using the Zowe Explorer and the IBM Z Open Editor extension to connect to our mainframe source libraries so if these could all be integrated together that would be better.
Hi. We have the same needs in my company. We already have Sonar Data Center with Cobol support. We are currently in a project to migrate the Cobol IDE in VSCode. We’ll use Zowe Explorer to communicate with z/OS but Cobol sources are on local computer in git repository. We want to analyse this sources with Sonar Lint on the fly without having launching a jenkins job.
We use IBM Cobol with IBM Z Ope nEditor…
Hello @Yves_Michon and welcome to the SonarSource community.
Thanks to @Yves_Michon and @GregHep for sharing your needs; do you have an idea how many developers in your companies are migrating to VSCode for COBOL development?
We potentially have somewhere between 60-70 developers that will be moving to VS Code for COBOL development. This is not a company-wide estimate as I can only speak for my development team.
Hi,
Same for our company (same group as @Yves_Michon but not yet same company), for about 350 COBOL developers migrating from IBM VisualAge Pacbase to native COBOL with VS Code.
We have connected the SonarLint extension for VS Code with SonarQube. This escalates faults detected in a previous Sonar analysis, but it does not do real-time checking while coding.
We would like the developer to be informed of faults as soon as possible, while coding in VS Code, (we use IBM Z Open Editor extension for VS Code).
Hi @FALLAI-Denis , welcome to the SonarSource community and thanks for detailing the needs for your company. Although supporting COBOL in VSCode in not in our short-term roadmap, we’ve made a note of your request and we’ll take it into account for future roadmap decisions.
One more vote for Please add the COBOL rules to VSCode SonarLint.
I currently have 6 internal programmers and about 25 external working for a partner company all with this requirement. Cobol code is all PC based, and managed under TFS for the moment, but moving to git soon to come. We have been mandated by the powers above to make pre-compile linting a constant in all of the development environments before the end of the year, as a step of RIRD. COBOL has had a late starter however.
Our current environment is:
Older version of MFCOBOL for Windows. While I have no issues adapting the rules, or adding new ones, I would never the less like to avoid breaking out my perl skills to create an alternate solution. Code management in Visual Studio, Development IDE = VSCODE Source files and copy members are in a LAN directories.
They are checked into our individual LAN workspaces as needed.
We are somewhat dependent on VSCode simply because there are few extensions that are actually available for general COBOL on Visual Studio…
We are currently using Sonarqube on large amounts of SQL, Python, C#, and Java I believe, and lint will start being tied to all of those environments also.
We have the same need in our company. We have 500 mainframe developers using an Eclipse IDE and we are looking into providing them a VSCode IDE also. SonarLint is mandatory in the IDE.
Hello @Bachri_Abdel and welcome to the Sonar community!
We added this as a feature request we are considering for SonarLint roadmap (you can see it in the roadmap page here) - but it is not something we’ll be working on during 2022. We’ll share any update here and in the roadmap page.
HI @Bachri_Abdel, you surely can add your voice by upvoting the feature via the roadmap link above - we use those inputs to assess the interest around any new feature idea and to adjust our priorities. You’re also welcome to contact our support to discuss more in details your request.
Hi @Bachri_Abdel and a very happy new year to you too!
The support for COBOL in VSCode is now a 2023 candidate, meaning that we’ll explore possible technical solutions to deliver it. Depending on the outcome, we may be able to ship something during the year; I don’t foresee any updates in Q1 though.
Hello,
we’ve recently released a new version of SonarLint for VS Code that introduces support for Cobol analysis! You can see more details and the requirements here.
The functionality is currently in Beta - if you have a chance to try it, we’d be thankful if you can share your feedback with ==> this short survey <==