SPI Update Rate

[mredig]

This isn't a complaint so much as trying to understand what's happening and if I'm missing something that I should be doing.

I just pushed an update to a package of mine to GitHub about a half hour ago, but SwiftPackageIndex.com hasn't updated it yet. Now, I don't expect that it would happen immediately or anything, but I'm trying to test that I'm setting up docc correctly (separate issue). Quick iterations are the name of the game when troubleshooting, of course!

Anyways, I've been trying to keep an eye on the progress to see when it'll update. I looked at the build monitor and saw that, when I pushed my commits, the most recent build was ~10 minutes ago. I've been keeping an eye on this since then and have seen tons of other builds come through in this time, but not mine.

• Is there a web hook I should set up to notify SPI of changes?
• Do some projects get priority? Those with higher stars/more often used/searched for/etc? Does sponsorship of the project result in a higher priority?

My project isn't super popular or anything.

So yeah, not complaining (even if it sounds like it), I'm just trying to understand or see if there's something I can do to improve my conformance to expectations. Thanks!

Edit: Checked it again (this is 5 hours after I first posted this) and it's updated! I don't know when it happened, nor any of the questions listed earlier, but I thought I'd share that it went through :)

[finestructure]

I'm guessing you are referring to changes to the default branch? In order to not be overwhelmed by all the changes happening on every project's default branch, we collate builds over a 24h period.

What that means is: if you've not had a default branch build in the last 24h, your change will be scheduled immediately. Otherwise, we hold it back until 24h have passed.

Releases (tags) are built immediately.

Hope that helps!

[mredig]

Nope - It was a release tag... Though, when you say release, you might mean the official GitHub Release... Where I just mean I tagged the commit as 0.1.5 and pushed it to GitHub.

[mredig]

(tho I totally understand the need to rate limit builds - I'm impressed with how many you do already!)

[finestructure]

Ah ok. When I say "built immediately", I mean immediately after discovery. However, we don't get notified of new tags immediately. We continuously scan all repositories for new tags. That process can take up to 5-6h, depending your luck!

[mredig]

That explains it! Would be cool if you implemented opt in support for webhooks (though I understand that could cause uneven load distribution... but I can wish :) )