Builds are failing in Appveyor
Hi Team,
On Friday, we encountered an issue where our builds were failing with an internal error. To troubleshoot, we attempted changing the .NET version and updating the OS version. These changes resolved the issue for some projects, but others began failing with different errors.
Later, we received your communication regarding a cache storage issue on the AppVeyor end. Today, we tried running the builds again without any changes to the .NET version or OS, and they worked fine for about 7–8 hours.
However, for the past 2 hours, we are once again experiencing internal build errors, which is now causing a blockage and has become a high-priority issue for us.
Kindly look into this on an urgent basis.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Owen McDonnell on 28 Jul, 2025 04:40 PM
Have you tried the
Re-build commitbutton on a previously successful build? Does it now fail?If so, can you link to the previously successful but now failing build?
2 Posted by Dinesh Prajapat... on 28 Jul, 2025 05:43 PM
I have also rebuild the commit which was running before and now it is not working from last few hours which we suspect is because of cache issue as the error is same
./install-foreman.ps1
Package source with Name: SequensisToolsFeed added successfully.
>/usr/share/dotnet/sdk/3.0.103/NuGet.targets(123,5): error : Unable to load the service index for source https://sequensis.myget.org/F/tool-packages/auth/9793a328-23d0-4400-afc3-516fb0354bd5/api/v3/index.json. [/tmp/1chham4g.hgy/restore.csproj]
/usr/share/dotnet/sdk/3.0.103/NuGet.targets(123,5): error : The SSL connection could not be established, see inner exception. [/tmp/1chham4g.hgy/restore.csproj]
/usr/share/dotnet/sdk/3.0.103/NuGet.targets(123,5): error : The remote certificate is invalid according to the validation procedure. [/tmp/1chham4g.hgy/restore.csproj]
The tool package could not be restored.
Tool 'foreman' failed to install. This failure may have been caused by:
* You are attempting to install a preview release and did not use the --version option to specify the version.
* A package by this name was found, but it was not a .NET Core tool.
* The required NuGet feed cannot be accessed, perhaps because of an Internet connection problem.
* You mistyped the name of the tool.
For more reasons, including package naming enforcement, visit https://aka.ms/failure-installing-tool
/home/appveyor/projects/oakbrookjourneywebsite/dotnettools/foreman: The term '/home/appveyor/projects/oakbrookjourneywebsite/dotnettools/foreman' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
Link: https://ci.appveyor.com/project/Sequensis/oakbrookjourneywebsite/builds/52475560
Support Staff 3 Posted by Owen McDonnell on 28 Jul, 2025 09:52 PM
Can you share the contents of the
install_foreman.ps1script. Feel free to make the conversation private if you don't want to share it publicly.4 Posted by Dinesh Prajapat... on 29 Jul, 2025 04:44 AM
Hi Owen,
Details have been shared with appveyor team on mail.
Could you please check on that.