Deploy image build

Resolves #7 (closed)

Add steps to generate a docker image for deployment when tags are pushed to the repositories.

added 1 commit

• 19b2724c - Do not attempt to remove bind-mounted directories from container

Compare with previous version

added 2 commits

• 3b724cdc - Remove left over empty directories from bind-mounted volumes
• c8686aa5 - Make deployment image entrypoint script executable

Compare with previous version

added 1 commit

• e43f9530 - Make deployment image entrypoint script executable after wget

Compare with previous version

added 1 commit

• 3fd85b63 - Remove logs folder from catkin_ws before commiting image

Compare with previous version

added 1 commit

• 8df0de24 - Deploy application image to internal registry

Compare with previous version

added 1 commit

• 242ea802 - Use fully qualified name to tag image, not just for pushing

Compare with previous version

List of related jobs:

• https://git.code.tecnalia.com/tecnalia_robotics/versatile/versatile_test_application/-/jobs/26140
• https://git.code.tecnalia.com/tecnalia_robotics/versatile/versatile_test_application/-/jobs/26156
• https://git.code.tecnalia.com/tecnalia_robotics/versatile/versatile_test_application/-/jobs/26180
• https://git.code.tecnalia.com/tecnalia_robotics/versatile/versatile_test_application/-/jobs/26196
• https://git.code.tecnalia.com/tecnalia_robotics/versatile/versatile_test_application/-/jobs/26205
• https://git.code.tecnalia.com/tecnalia_robotics/versatile/versatile_test_application/-/jobs/26245

Last one is almost there. Something went wrong while pushing to registry. One more attempt:

• https://git.code.tecnalia.com/tecnalia_robotics/versatile/versatile_test_application/-/jobs/26251

added 1 commit

• a9827b48 - Build and push deploy image in 'script' instead of 'after_script'

Compare with previous version

Last jobs get stuck pushing the image. Trying to use the JFrog CLI interface instead of a raw docker push using a simpler test repository for faster iteration:

https://git.code.tecnalia.com/tecnalia_robotics/sandbox/simple-deploy-test/-/jobs/26395

Summary of today's shenanigans:

• Miserably failed to make JFrog CLI succeed using the simple-deploy-test repo
• Using plain docker push is the only succeeded job in simple-deploy-test
• See jobs

After multiple last minute trial and error repetitions with Aitzol, we have found a combination of commands that allow pushing a docker image using JFrog CLI (at least from local host).

Started two more jobs in the versatile_test_application repository:

• Using plain docker push: https://git.code.tecnalia.com/tecnalia_robotics/versatile/versatile_test_application/-/jobs/26503
• Using JFrog CLI to push: https://git.code.tecnalia.com/tecnalia_robotics/versatile/versatile_test_application/-/jobs/26512

added 20 commits

• a9827b48...57c08712 - 6 commits from branch master
• cf3b0344 - Prepare default industrial_ci job for commit/tag variation by extension
• dae2df37 - Supress default industrial_ci job for tags
• 43173a04 - Add scripts/Dockerfile required for deployment script
• f1421673 - Add initial deployment steps
• 3bbfeefa - Commit industrial_ci image
• af52ce39 - Do not attempt to remove bind-mounted directories from container
• a17151ae - Remove left over empty directories from bind-mounted volumes
• f503514f - Make deployment image entrypoint script executable
• 2eb2bac2 - Make deployment image entrypoint script executable after wget
• 37a72dd8 - Remove logs folder from catkin_ws before commiting image
• 5ebf26b4 - Deploy application image to internal registry
• b45efde6 - Use fully qualified name to tag image, not just for pushing
• 87665b50 - Build and push deploy image in 'script' instead of 'after_script'
• 8228b2a3 - Use new naming scheme for deployment images

Compare with previous version

Rebased on top of master, to include changes in docker image naming convention, and changed the naming of the deployment images built.

Apparently the docker push timeouts were caused by using an access token to authenticate against the artifactory server. A new user has been created to perform this authentication as a proper user and now the push seems to succeed.

I launched one final job for testing using the default template: https://git.code.tecnalia.com/tecnalia_robotics/versatile/versatile_test_application/-/jobs/27034

I believe this is ready for review/comments, @jon.azpiazu.

assigned to @jon.azpiazu

unmarked as a Work In Progress

resolved all discussions

Which launchfile can I use to test it? This one https://git.code.tecnalia.com/tecnalia_robotics/versatile/versatile_test_application/blob/kinetic-devel/versatile_test_application/launch/flexbotics_framework.launch ?

I believe you should currently run https://git.code.tecnalia.com/tecnalia_robotics/versatile/versatile_test_application/blob/kinetic-devel/versatile_robots_lwr/versatile_robots_lwr_launch/launch/versatile_robots_lwr.launch first, to start the robot in simulation, and then the flexbotics_framework.launch you point to.

However, I also believe from some previous tests, that it will not work because some package has missing install rules. I will soon start to test this as well and try to fix the issues in the related packages.