jarjar/DVOP2025_Exercise
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Question 3

Browse Source
This commit is contained in:
jarjar 2025-03-03 21:53:02 +01:00
parent 8a1ee05c0d
commit 63ec323ef1
1 changed files with 14 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
commands.md
View File

@ -34,5 +34,18 @@ Documentation de la macro : (https://en.cppreference.com/w/cpp/preprocessor/repl
On peut voir qu'avec le cmake --version les version de cmake sont différentes entre les builds.
(Note perso) Si le CMakeLists n'a pas changé alors il faut voir au niveau de la version GCC (ou peut etre ailleurs) pour voir un potentiellement changement. (https://gcc.gnu.org/gcc-6/changes.html ou https://gcc.gnu.org/gcc-12/changes.html)
3. Now that you have assessed the situation, make the necessary modifications to make sure the Job environment and/or Job executable behaves in the same manner as it was before.
Une des soltutions est de modifier le fichier "CMakeLists.txt" en forcant la compilation en c++11.
Dans mon "CMakeLists", j'ai rajouté cette ligne : ```set(CMAKE_CXX_STANDARD 11)``` (Variable récupéré dans cette documenation : https://cmake.org/cmake/help/latest/prop_tgt/CXX_STANDARD.html#prop_tgt:CXX_STANDARD)
J'ai donc fais la modification que j'ai mis sur ce repertoire git : https://gitea.jarodcajna.fr/jarjar/test_app.git
J'ai ensuite modifié la pipeline pour qu'elle aille récupérer mon répertoire git et qu'elle récupère la branche "main".
En relancant le job, nous avons le meme resultat que l'ancien build. La modification a donc fonctionné.
_Explain in a few lines the steps you took and provide a package (git repository / patch files) containing your modifications and a note explaining your changes._
4. Describe another solution to make the Job environment and/or Job executable behave in the same manner as it was before.
_Explain in a few lines and compare it against your first solution._
5. Now that everything is running as expected, it is time to suggest a production rollout for this service. Please suggest changes to the service to ensure a secure, production-ready deployment to be accessed by a team of developers. The suggestions are not limited in scope, but should focus on security, performance and reliability.
_Explain in a few lines._