Work around Julia artifacts permission errors #1603
Assignees
Labels
CI/CD
Continuous Integration/Continuous deployment
Comments
|
I've made a build (and have scheduled it to run on a failing agent) https://dpcbuild.deltares.nl/buildConfiguration/Ribasim_Ribasim_Windows_FixJuliaArtifactPermissions?branch=continuous_control&buildTypeTab=overview&mode=builds Let's see how often we need to run this, and either detect the failure and run it, or always run it. |
evetion
added a commit
that referenced
this issue
Aug 12, 2024
Fixes #1603 Given the recent changes in Teamcity, the original project is lost-ish https://dpcbuild.deltares.nl/buildConfiguration/Ribasim_Ribasim_Windows_FixJuliaArtifactPermissions?branch=continuous_control&buildTypeTab=overview&mode=builds? As in automatic (?), greyed-out, no build steps or builds visible. Furthermore, the new Template(s) used is/are platform-agnostic, so harder to integrate a Windows specific fix. So the easier way is just to integrate it into pixi, and always running it at CI time, also useful when it irrevocably happens on Windows laptops. However, there seems to be no way to have platform specific tasks (@Hofer-Julian is that correct and maybe worth an issue? I know you proposed the deno shell 😉), so I now just append an `exit`, ignoring any exit code of the previous command. --------- Co-authored-by: Martijn Visser <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sometimes we get a randomly failing build, of the form:
The upstream issue and workaround is JuliaLang/julia#52272 (comment).
Of course it is a lot of work to fix permissions manually on TeamCity agents, so we need something better.
@evetion suggested earlier to make a TeamCity job which can fix this error. Or perhaps we can just try fixing the permissions on each run, to never leave behind a broken agent.
The text was updated successfully, but these errors were encountered: