Conversation
|
You can access the deployment of this PR at https://ci-renku-3981.dev.azure.renku.ch |
lorenzo-cavazzi
left a comment
There was a problem hiding this comment.
Generic comment: Why make a separate workflow? A bunch of jobs overlap with the existing pull-request-test workflow. We can adapt it to have an additional deploy-pr-azure job
olevski
left a comment
There was a problem hiding this comment.
One small suggestion. And I think Lorenzo did the review at the same time as me.
0eb7e66 to
10e85a9
Compare
0bc1ec0 to
809da18
Compare
5b26a74 to
69e912b
Compare
69e912b to
659426d
Compare
lorenzo-cavazzi
left a comment
There was a problem hiding this comment.
Looks good already 👏
I added a couple of nitpick comments, feel free to ignore them.
I added the deploy string and something seems off with #legacy, the tests didn't run
There is an issue on the cluster with csi-rclone, hence some sessions are not able to start |
06e99d2 to
3fc96bd
Compare
Shouldn't the check still show up? I'm surprised to see that the job was skipped even with the #legacy option in the deploy string. Also, this hasn't been addressed #3981 (comment) |
b2101b9 to
2266829
Compare
e4a9f33 to
3a8ec5d
Compare
Approved by Tasko, issues addressed
|
Tearing down the temporary RenkuLab deployment for this PR. |

Deploy to the Azure Dev cluster by using the
(slash)AzureDeploystring/AzureDeploy #legacy