Handle accidents when building the code and what CI means

Clase 17 de 25 • Curso para Developers en Inglés (2020)

Resumen

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.`

Eduardo Kiriakos Piazza

student•

Security issues are common when building code.

Carlos Arriaga

teacher•

They are!

Efraín Hernández García

student•

That's true!

Sandra Milena Rojas Herrán

student•

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.

Wilson Delgado

student•

jajajajajaja that is funny

Juan Camilo Alvarez Jurado

student•

I have been through that, haha

Yes, it is very frustrating (not frustrated; remember that -ing adjectives are for things that cause a state, and -ed are for things in a state) :)

Gibrán Pelayo Miranda

student•

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.

Carlos Arriaga

teacher•

I totally agree. I think a good strategy to reduce this "Bug Hell" is to allocate the responsibility on ONE specific teammate and let him/her do the work. Of course, this is just an opinion.

Reinaldo Mendoza

student•

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.

Wilson Delgado

student•

if I have a small project, how is the better way to implement CI?

Carlos Arriaga

teacher•

Using GItHub

Carlos Nassif Trejo Garcia

student•

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

Felipe Bernardo González Barranco

student•

Thanks!

Cristian Blandón

student•

Syntax errors, compilation errors, runtime errors, errors everywhere :D

Carlos Arriaga

teacher•

Errors everywhere hahahaah

DANIEL ALBERTO PRADA HERRERA

student•

errors everywhere! jajaja

Miguel Angel Reyes Moreno

student•

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.

Santiago Herrera Velásquez

student•

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

Jesus Cuadro

student•

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

Daniel Alberto Vega Bejarano

student•

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

Daniel Alberto Vega Bejarano

student•

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.

Lizeth Soler

student•

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.

Emeli Yorleny Recinos Mojica

student•

Thanks

Johana Saraí Isleño Ayala

student•

excellent

Litzy Jasvell Martínez Calero

student•

Using automation to enable source control to build and test the latest versions fo the code submitted by the developers. Continuous Integration tools ru

Litzy Jasvell Martínez Calero

student•

Continuously submitting working, runnable software into source control that will be built and testes.

Litzy Jasvell Martínez Calero

student•

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

Litzy Jasvell Martínez Calero

student•

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

Litzy Jasvell Martínez Calero

student•