-
Notifications
You must be signed in to change notification settings - Fork 240
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
404 error downloading sandbox-16.5.15922.0-gb #1252
Comments
I can see that that build has a problem - there are newer builds available, which are working - if you re-run you will likely get 15931 or 15935 |
For DE, I am still getting 15922. Do you know when the newer builds will be available? |
Yes, The last GB version is also still 15922. I was waiting 24 hours in the hope that it would build again, though it looks like my (sacrificial) Window Docker PC has died again so I'm probably going to have to wait til Monday. |
I have deleted the faulty version 15922 (the one without a platform) I have emailed our build team (who are responsible for publishing artifacts) that all country versions are not present. |
Confirmed, thank you Freddy. |
As I am propably experiencing the same problem, I will write it here. I was testing the Download-Artifacts and the -includePlatform will regularly give you a 404 Not found error. Download-File : Exception calling "DownloadFile" with "2" argument(s): "Fjernserveren returnerede en fejl: (404) Ikke fundet."
|
@freddydk if you do this change - are there any other routine in place that will catch these kind of issues with the builds? At least now you get notified by partners if something fails. We do not want to run our pipelines on old build for weeks without someone being notified that the builds are failing. You shouldn't need to email the build team about these kinds of problem, they should know already and be working on a fix. :) btw, still get 404 error for platform for Swedish nextminor. |
The error with 15946 and the missing platform should be fixed with the checkin I just made. |
@Rukkulakki - the issue you are facing here is probably what I talk about here: https://freddysblog.com/2020/08/18/one-of-these-days/ |
The issue sounds much like the one I am facing, but unfurtunately an update did not help PS C:\Windows\system32> Update-Module navcontainerhelper PS C:\Windows\system32> Download-Artifacts -artifactUrl (Get-BCArtifactUrl -country dk -type OnPrem -version 15.3.0.0 -select Closest) -includePlatform
PS C:\Windows\system32> get-installedmodule navcontainerhelper Version Name Repository Description 0.7.0.26 navcontainerhelper PSGallery PowerShell module |
Works in the bccontainerhelper. PS C:\Windows\system32> install-module bccontainerhelper -AllowClobber PS C:\Windows\system32> Download-Artifacts -artifactUrl (Get-BCArtifactUrl -country dk -type OnPrem -version 15.3.0.0 -select Closest) -includePlatform |
Thanks @freddydk, The fix seems to work as intended 👍 Now 16.5.15905.0 is used as Next Minor instead of 16.5.15946.0 that failed on platform. Lets hope that the build team has some routine for securing this going forward. ;-) |
@Rukkulakki did you remember to restart containerhelper after update - else it won't work. |
@freddydk I think I even tried restarting the entire powershell application, but something must have gone wrong at my end. |
I do recommend using bccontainerhelper though:-) |
PLEASE DO NOT INCLUDE ANY PASSWORDS OR TOKENS IN YOUR ISSUE!!!
Describe the issue
The container helper gets a 404 error downloading current "SecondToLastMajor" platform artifact.
Looks like someone has let you down.
Scripts used to create container and cause the issue
Full output of scripts
Additional context
The text was updated successfully, but these errors were encountered: