No tienes acceso a esta clase

¬°Contin√ļa aprendiendo! √önete y comienza a potenciar tu carrera

Handle accidents when building the code and what CI means

17/25
Recursos

Al desarrollar software muchas integraciones pueden fallar y es importante detectar estos bugs a tiempo para no complicar m√°s la entrega del proyecto o la manera de trabajar de tu equipo en la empresa.

Manejar accidentes al construir el código.

Imagina que has terminado tu trabajo y funciona perfectamente en tu ordenador. Env√≠as los cambios al repositorio, pero tus compa√Īeros de equipo comienzan a tener problemas con esa nueva funcionalidad.

  • There are many things that can go wrong with software development.
  • Think of examples of problems that might arise when developing new software.
  • Do you have the same problems when you are working with small or big teams?
  • How‚Äôs your Continuous Integration?

Qué es la integración contínua (CI)

La Integración Continua es una técnica para dar garantías y reducir el impacto de conflictos en el código de tu proyecto.

  • Principles of CI:
    • Continuously submitting working, runnable software into the source that will be built and tested.
    • Using automation to enable source control to build and test the latest version of your code submitted by the developers.
    • Continuous Integration tools run your tests as soon as you submit your code.
    • Source control emails the developers last involved in conflicts that appear when submitting.
    • Continuous Integration wraps version control compilation and testing into a single repeatable process.
  • Source Control guarantees the impact reduction of conflicts.
    • Avoid Merge Hell.
    • Fix bugs quickly, testable build.
    • Ensure Ownership.

Trabajar con Integración Continua optimiza los tiempos de aparición y resolución de bugs, además de mejorar la comunicación con tu equipo de trabajo que desarrolla software.


Contribución creada por: Kevin Fiorentino.`

Aportes 42

Preguntas 1

Ordenar por:

¬ŅQuieres ver m√°s aportes, preguntas y respuestas de la comunidad?

Security issues are common when building code.

Sometimes teacher, and It has passed, the developers have problems with code, and they don’t know why. Then, they invested much time and the error was a simple semicolon. That is frustrated, and we think that we have that we do the university again, hahaha.

The modules do not perform as expected, an "untraceable" bug that made everybody crazy, the tasks are taking longer than planned. The greater the team, the number of problems arise if there is bad communication.

Oh I remember that day, when after a couple weeks I finally complete my first webpage with database connection, late night the day before I finally made it, everything was up and running, PHP, HTML and CSS plus a little bit of JS, my first real project in university also the main grade for that subject. I was so proud of my work when the next day it comes to show my posh work, it is not working, and I just tested the day before and everything was good and I had not touched anything since the last test(at that time 2010 I had no idea of git or any kind of tools related), huge surprise, my teacher told me take a look, you have until the end of the class to make it through, I saw everything fine in my code and suddenly I realize the hosting had changed the PHP version that day and my code was broken because of that(It was my fault, it was something that I had to check), unbelievable, yesterday it speaks German and now its French was my first thought, I told my teacher about the issue and just laugh and gave me another day to deliver, I get immerse in the new documentation and found out that I needed to change some functions and that was it. It ends up working as it supposed to be with a little bit of love and anguish.

Handle accidents when building the code
Problems occur when you deliver faulty code
Solve with:

Continuous Integration
A technique that guarantees the reduction in the impact of conflicts by doing the following

  • Continuously submitting working, runnable software into source control that will be built and tested
  • Using automation to enable source control to build and test the latest versions of the code submitted by the developers

Version control, compiles, and tests

Syntax errors, compilation errors, runtime errors, errors everywhere ūüėĄ

Core principles of CI

  • Continuously submitting working, runnable software into source control that will be built and testes.
  • Using automation to enable source control to build and test the latest versions fo the code submitted by the developers.
  • Continuous Integration tools run your tests as soon as you submit your code.
  • Source control emails the developers last involved in conflicts that appear when submitting.
  • Continuous Integration wraps version control, compilation and testing a single repeatable process.

The problems with small teams are smaller, the communication is easier so is posible take the problems more fast

One problem could be that you don’t know if the software to be developed will be viable

I consider that it is more difficult to work with bigger teams because there are more situations to handle and mostly of the leader time is short. So, it is better to have a smaller teams to have more control about the issues and take decisions to handle them

We had a issue on a merge request, where it was not consider job of a partner. it could happen if we don’t understand how to use Git and Github appropriately.

One problem is not have your branch with the last version or when you need comment some portion of code and you don’t remember uncomment it.

Thanks

excellent

Using automation to enable source control to build and test the latest versions fo the code submitted by the developers. Continuous Integration tools ru
Continuously submitting working, runnable software into source control that will be built and testes.
Continuously submitting working, runnable software into source control that will be built and tested Using automation to enable source control to build and test the latest versions of the code submitted by the developers
Handle accidents when building the code Problems occur when you deliver faulty code Solve with: Continuous Integration A technique that guarantees the reduction in the impact of conflicts by doing the following
The modules do not perform as expected, an "untraceable" bug that made everybody crazy, the tasks are taking longer than planned. The greater the team, the number of problems arise if there is bad communication.
Sometimes teacher, and It has passed, the developers have problems with code, and they don’t know why. Then, they invested much time and the error was a simple semicolon. That is frustrated, and we think that we
Hello

Thanks

Also

Firts

More

Awesome

Hello

great

Handle accidents when building the code and what CI means Handle accidents when building the code
Problems occur when you deliver faulty code
Solve with:

Continuous Integration
A technique that guarantees the reduction in the impact of conflicts by doing the following

Continuously submitting working, runnable software into source control that will be built and tested
Using automation to enable source control to build and test the latest versions of the code submitted by the developers
Version control, compiles, and tests Core principles of CI

Continuously submitting working, runnable software into source control that will be built and testes.
Using automation to enable source control to build and test the latest versions fo the code submitted by the developers.
Continuous Integration tools run your tests as soon as you submit your code.
Source control emails the developers last involved in conflicts that appear when submitting.
Continuous Integration wraps version control, compilation and testing a single repeatable process.

I really like your course.

Dependencies out of support.

  • I think that the size of the team is important, because you can reduce the number of troubles, and you can have better traceability of how things are going on.

Commit malformed code due to cache¬īs troublers.

Something as simple as having a different indent level in your code can cause problems. We should all agree in a team, to use, for example, an extension like Prettier to make all the code follow certain rules! ūüėÉ

Avoid Merge Hell is one of the most important problems.

Sometimes, problems arise because of using different versions of some packages.

Continuous Integration (CI) wraps version control, compilation and testing into a single repeatable process.

404 error, the page doesn’t exist, because it is not devoloped yet

when your team made some changes, but the forget save and they send us the code with the same problems like they would not be fixed it.

good
yes

Most of the time the problems working with teams arise when there’s a lack of communication