Atom is a free and open source text editor offering a range of packages and themes.
N/A
Jenkins
Score 8.4 out of 10
N/A
Jenkins is an open source automation server. Jenkins provides hundreds of plugins to support building, deploying and automating any project. As an extensible automation server, Jenkins can be used as a simple CI server or turned into a continuous delivery hub for any project.
Jenkins is the only tool I would consider using for CTCI deployment. Its plugins make it easy to customize to any environment you can conjure up and will always be custom fit to your needs as a DevOps engineer. Other tools have better support but lack the customizability and …
Atom is great for simple HTML coding. It's fast, has intuitive shortcuts and several options. I particularly love the "convert spaces to tabs" function that I haven't seen in other editors.
I'm not sure how it would fair in more serious web development today, if there are plugins for live updates of the page you are working on...
But the problem is that it has been discontinued so you know there are no new features or fixes coming through.
Jenkins is a highly customizable CI/CD tool with excellent community support. One can use Jenkins to build and deploy monolith services to microservices with ease. It can handle multiple "builds" per agent simultaneously, but the process can be resource hungry, and you need some impressive specs server for that. With Jenkins, you can automate almost any task. Also, as it is an open source, we can save a load of money by not spending on enterprise CI/CD tools.
Atom is highly customizable and allows for various themes and extensions that can make your code easier to read.
Atom has many code hinting features that allow users to write faster and integrate with services likeLINT that can clean up your code once your done to meet your internal teams style choices.
It's very fast and manages projects well - Accessing other files within a related folder(s) is very easy and intuitive.
Automated Builds: Jenkins is configured to monitor the version control system for new pull requests. Once a pull request is created, Jenkins automatically triggers a build process. It checks out the code, compiles it, and performs any necessary build steps specified in the configuration.
Unit Testing: Jenkins runs the suite of unit tests defined for the project. These tests verify the functionality of individual components and catch any regressions or errors. If any unit tests fail, Jenkins marks the build as unsuccessful, and the developer is notified to fix the issues.
Code Analysis: Jenkins integrates with code analysis tools like SonarQube or Checkstyle. It analyzes the code for quality, adherence to coding standards, and potential bugs or vulnerabilities. The results are reported back to the developer and the product review team for further inspection.
Well Atom is open source so the re-new is a no brainer. The only way I would stop using Atom is if the developers somehow made it not function well. Or, if the project got forked to a commercial version or something. Or, there could be the case that development stops or that it was not updated on this or that platform
We have a certain buy-in as we have made a lot of integrations and useful tools around jenkins, so it would cost us quite some time to change to another tool. Besides that, it is very versatile, and once you have things set up, it feels unnecessary to change tool. It is also a plus that it is open source.
I give Atom a 9 because it is one of the most modern text editors built with JavaScript intentionally to allow the editor to be changed and modified with custom functionality that a team may need. I think I would otherwise give atom an 8 due to support, but it gets a 9/10 because of the extensibility/plugin capability.
Jenkins streamlines development and provides end to end automated integration and deployment. It even supports Docker and Kubernetes using which container instances can be managed effectively. It is easy to add documentation and apply role based access to files and services using Jenkins giving full control to the users. Any deviation can be easily tracked using the audit logs.
No, when we integrated this with GitHub, it becomes more easy and smart to manage and control our workforce. Our distributed workforce is now streamlined to a single bucket. All of our codes and production outputs are now automatically synced with all the workers. There are many cases when our in-house team makes changes in the release, our remote workers make another release with other environment variables. So it is better to get all of the work in control.
Atom has an active forum and a Slack group where you can ask technical questions. Occasionally, the authors will pop in to answer a few questions here and there, but most of the time, its other helpful users who will assist you. Though they aren't the most knowledgeable, they are at least timely.
As for plugin support, that differs with each plugin, but as I mentioned before, many plugins are no longer maintained.
As with all open source solutions, the support can be minimal and the information that you can find online can at times be misleading. Support may be one of the only real downsides to the overall software package. The user community can be helpful and is needed as the product is not the most user-friendly thing we have used.
It is worth well the time to setup Jenkins in a docker container. It is also well worth to take the time to move any "Jenkins configuration" into Jenkinsfiles and not take shortcuts.
Our company likes to keep things open, and we don't want to prevent developers from customizing their environment the way they want. Atom seemed to be a lot more open than our existing tools and has good community support on pretty much any programming language. This can create some confusion since adding too many extensions or customizing can make the tool slower than it is supposed to be.
Overall, Jenkins is the easiest platform for someone who has no experience to come in and use effectively. We can get a junior engineer into Jenkins, give them access, and point them in the right direction with minimal hand-holding. The competing products I have used (TravisCI/GitLab/Azure) provide other options but can obfuscate the process due to the lack of straightforward simplicity. In other areas (capability, power, customization), Jenkins keeps up with the competition and, in some areas, like customization, exceeds others.
The tool we use when we need quick fixes. Allows fast, reliable scripting to fix urgent problems in our applications.
When applications grow from 5-10 files to 100's, they need to be migrated to a heavier-duty IDE. This can be cumbersome and quite annoying, but is necessary to maintain code integrity on such a large scale (since it cannot be done with the limited default toolset of Atom).
