-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improvement - Acciones de Github - Adaptar Github Actions (2) #18
Conversation
Actions executed at: 2024-01-17 08:54:04. |
@@ -31,7 +36,11 @@ jobs: | |||
- name: echo environment variables | |||
run: echo ${{ env }} | |||
- name: Update develop instance | |||
run: ssh $DEVELOP_SSH_USERNAME@$DEVELOP_HOST "test -e /web/${{ env.BRANCH_CLEAN }}" && (echo "Directory branch exists" && ssh $DEVELOP_SSH_USERNAME@$DEVELOP_HOST "cd /web/${{ env.BRANCH_CLEAN }} && git stash && git pull && wget --delete-after --no-check-certificate https://develop.sinergiacrm.org/${{ env.BRANCH_CLEAN }}/SticRepair.php && rm -rf /web/${{ env.BRANCH_CLEAN }}/cache" && wget --delete-after --no-check-certificate https://develop.sinergiacrm.org/${{ env.BRANCH_CLEAN }}) || echo "Branch doesn't exist in develop" | |||
run: ssh $DEVELOP_SSH_USERNAME@$DEVELOP_HOST "test -e /web/${{ env.BRANCH_CLEAN }}" && (echo "Directory branch exists" && ssh $DEVELOP_SSH_USERNAME@$DEVELOP_HOST "cd /web/${{ env.BRANCH_CLEAN }} && git stash && git pull && rm -rf /web/${{ env.BRANCH_CLEAN }}/cache") || echo "Branch doesn't exist in develop" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A considerar dependiendo de la intención: cambiar el git stash por git stash -u. La opción -u también añade al stash los ficheros untracked; si el objetivo es "limpiar" el directorio, quizás sería más adecuado.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(A)provado
Después de la integración del PR #7 se detecta que la actualización de la instancia de pruebas no funciona correctamente. Esto es debido al cambio de localización del fichero que realiza la reparación.
Se adapta la acción que realiza la actualización de la instancia, cuando se suben cambios a una rama, para que recoja el fichero SticRepair.php desde nuestro repositorio de scripts.