![]() It could still be cheaper because right now, my company has a small team, and sometimes it's difficult to use a paid product for a small team. "In terms of the pricing for GitLab, on a scale of one to five, with one being expensive and five being cheap, I'm rating pricing for the solution a four."GitLab's pricing is good compared to others on the market."."I'm not aware of the licensing costs because those were covered by the customer."."The price of GitLab could be better, it is expensive."."We are using its free version, and we are evaluating its Premium version."I don't mind the price because I use the free version.".We have a yearly subscription in which we can increase the number of licenses, but we have to pay at the end of the year." We can't bear it now, and we have to find another solution. If you connect Jenkins with bookings and lockouts, it can be challenging." "Jenkins can improve by continuing to add additional plugins for all the new solutions that are coming out within the cloud sphere." "The enterprise version is less stable than the open-source version." "It can be improved by including automated mobile reporting integrations." The initial setup could be more straightforward. If the error message is clear, then I wouldn't have to escalate the issue to different teams." "UI is quite outdated." "The onboarding of Jenkins should be smoother, and it should have more pipelines available as it's deployed on many different servers." "Jenkins can be improved, but it's difficult for me to explain. ![]() I have to escalate it to the Jenkins DevOps team just to see what caused the failure. If a job does not go through, at times the error message does not clearly indicate what caused the failure. "The UI of Jenkins could improve." "Tasks such as deployment, cloning, database switchover, and all other database missions and tasks are being done through Jenkins. They have a really complicated procedure for their support." "The price of GitLab could improve, it is high." However, some basic features on things like that could be really helpful." "As a partner, sometimes it's difficult to get support. It's understandably not going to be their main focus and their core, and whenever you are with a company that needs a bit more advanced features on that specific topic, you're probably still going to integrate with another tool like Jira Service Management, for example. I see some, for example, covering ITSM on a DevOps team level, and that's one of the things that I and my current client would find really helpful. That doesn't mean that GitLab should build something similar to Jira because that will always have its place, but they could grow a bit in those kinds of supporting features. We tend to always use, for example, Jira next to it. We have to acquire third-party components to work with Kubernetes." "This solution could be improved by adding modifications such as slack notifications." "It's more related to the supporting layer of features, such as issue management and issue tracking. We have to develop many things to make it work. They should raise awareness." "Based on what I know so far, its integration with Kubernetes is not so good. If there is someone new to the system they would not know if there is a conflict." "It should be used by a larger number of people. They should be more detailed but less technical." "Merge conflicts and repository maintenance could improve. Their tutorials are too technical for a user to understand. We have a deployment application where we can run our tests and add various variables to be passed as assertions to those tests. I am satisfied with the product." "GitHub linking is pretty good. I like that you work on anything, and you make anything. Jenkins makes life easy for the database and DevOps teams." "Jenkins is a very mature product." "Jenkins' most valuable feature is Pipeline." "I am not aware of the available options in the market right now compared to Jenkins, but I am pretty much happy with the service that Jenkins is providing our company." "I love Jenkins. ![]() We can see results without having to depend on different teams. With Jenkins, we can bring all the technologies together by the click of a button. Additionally, with the solution, I can use other reporting tools, such as Flow." "When we have manual tasks, we have to depend on multiple technical teams. "It's very easy to learn." "The most valuable features of Jenkins are the ease of use and the information about how to use the features is readily available on the internet.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |