Skip to content
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

I cannot find artifacts for 4.4.1 in appveyor #558

Closed
marlonchosky opened this issue Jan 12, 2021 · 5 comments
Closed

I cannot find artifacts for 4.4.1 in appveyor #558

marlonchosky opened this issue Jan 12, 2021 · 5 comments

Comments

@marlonchosky
Copy link

Hello. I want to load the symbols from version 4.4.1 but I can't find its artifacts. I have searched here https://ci.appveyor.com/project/castleproject/core/build/4.4.1/artifacts but I haven't found it.

@stakx
Copy link
Member

stakx commented Jan 12, 2021

You have looked in the right place. I suppose the reason that the symbols are no longer there is AppVeyor's current artifacts retention policy (introduced about 2 years ago, IIRC), which states that build artifacts will be deleted after 6 months.

That's unfortunate, and something we should keep in mind when migrating our CI from AppVeyor to GitHub Actions (#497).

@marlonchosky
Copy link
Author

  1. But the artifacts from version 4.4.0, which I understand are older than 4.4.1, can be viewed on AppVeyor :/
  2. So are you planning to migrate to GitHub Actions? If that is the case, when you do this migration, do not forget to put it in the documentation please.

@stakx
Copy link
Member

stakx commented Jan 12, 2021

But the artifacts from version 4.4.0, which I understand are older than 4.4.1, can be viewed on AppVeyor :/

I suspect those are still around because the build ran before the new artifact retention policy was introduced.

So are you planning to migrate to GitHub Actions?

Yes, that's the plan.

If that is the case, when you do this migration, do not forget to put it in the documentation please.

Sure.

@marlonchosky
Copy link
Author

marlonchosky commented Jan 13, 2021

I suspect those are still around because the build ran before the new artifact retention policy was introduced.

Ok, so that's what surely happened.

Great, thank you for the answers 👍

@jonorossi
Copy link
Member

We should stop relying on symbols being available for releases on our CI server and instead publish symbols with NuGet now that there is a better story for symbols.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants