Translation of the abstract of the report — is everything okay?

Thanks to the help Dormidont-but somehow hardly moved the abstract of his report on Russian. Habr, look please, whether all is clear, and is not ashamed to put this on off.the JavaOne website. Thank you!

Frequent deployment in varied production environment increases the burden on DevOps. To ensure that the scan passed without errors and the application is deployed correctly becomes more difficult.

This report will address some common errors in the traditional continuous-integration that increase risk, add handmade, lead to the manifestation of the human factor, and generally make DevOps nervous before clicking "Deploy".

Then we will demonstrate automated methods, which will overcome these problems with the help you already use popular tools such as your build system (Maven, Gradle or Ant+Ivy), your continuous integration server (Jenkins, Bamboo or TeamCity), and using binary repository.

Regardless of whether you are building software for cloud platforms or private infrastructure, we show how to obtain a fully automated production Assembly, which collects fully traceable, managed and ready to scan products.
October 8th 19 at 00:52
5 answers
October 8th 19 at 00:54
Solution
My nadmozg. Not found the original. Removed substitutes articles of the type "this" and "your", signs of oral speech "which", well and on trifles. I would get rid of tautologies and returned word production, but can ill in the subject area.
Actually, I want to say that calques of terms is not such a great evil as calques grammar, from which any translation of the smell of the Store on the couch.

Often unfolding in a diverse production environment increases the burden on DevOps. It becomes increasingly difficult to ensure that the application is deployed correctly.

The report will discuss some common errors in the traditional continuous-integration that increase risk and the amount of manual work. These errors lead to the manifestation of the human factor, making DevOps nervous before clicking "Deploy".

Next, we will demonstrate automated methods that can overcome these problems by using a already used the popular tools: build system (Maven, Gradle or Ant+Ivy), continuous integration server (Jenkins, Bamboo or TeamCity) and binary repository.

Regardless of whether you are building software for cloud platforms or private infrastructure, we show how to obtain a fully automated production and assembling, collecting fully traceable, managed and ready to implement products.
Wow, that's great. Thank you! - Webster59 commented on October 8th 19 at 00:57
Original:
Frequently deploying to production puts bigger pressure than before on DevOps to make sure the good, qualified application is provisioned with no mistakes. This session will explore some common pitfalls with traditional Continuous-Integration that increase risk, introduce manual input and human error, and generally make DevOps cringe before hitting the “deploy” button.

We will then demonstrate automation techniques that overcome these issues using popular tools, like Maven, Gradle, your CI server, custom scripts and a Binary Repository. Whether you are building software for the cloud or in-house, this presentation will show you how to have completely automated production builds that release applications which are fully traceable, managed and ready to be provisioned with no fear!
- Webster59 commented on October 8th 19 at 01:00
October 8th 19 at 00:56
Frequent deployment in varied production environment increases the burden on DevOps. To ensure that the scan passed without errors and the application is deployed correctly becomes more difficult.
That's tough, times with 3 read. Concentration scan in the text :)
Ha, in the original there is deployment and provisioning. How to write? - Webster59 commented on October 8th 19 at 00:59
All killed one scan, has become clearer, I hope :) - Webster59 commented on October 8th 19 at 01:02
October 8th 19 at 00:58
And it is possible to the Russian language of subjectivity is not something that even the remarks and the irregularities?

— "This report" -> "this report"?
— "add the handmade" ??? (M. b. "increase the amount of manual work")
— 3rd paragraph: three times "your"
— 3rd paragraph: if a transfer started "using", then why again "using" before the last member of the uniform?
— 4th paragraph: "the Assembly, which collects"
Thanks, all fixed. - Webster59 commented on October 8th 19 at 01:01
— 3rd paragraph: if a transfer started "using", then why again "using" before the last member of the uniform?

Because it's a different list :) the First sheet is your tools, a second sheet (one member, though) is that you need to add for profit. - Webster59 commented on October 8th 19 at 01:04
October 8th 19 at 01:00
Regular deploy to production increases the burden on DevOps

So it will be clearer, IMHO. No need to mock the language just for the sake of bullying.
October 8th 19 at 01:02
In the first paragraph or "scan passed without errors" or "application is deployed correctly" can be thrown out.

"traceable" in the last paragraph, maybe "which can be monitored" or something? Well, "Assembly" -> "build system", probably.
Thank you, done. - Webster59 commented on October 8th 19 at 01:05

Find more questions by tags Web DevelopmentJava