15

So, I was poking at Kevin's profile and followed the link for Stack Overflow Valued Associate #00004 which brought me to a page:

enter image description here

Until such a time that these links work, please change Kevin's profile to be employee #404.

(to any who suggest I should have used the feedback site link, it links to this page.)

P.S.:

I'm sure there are others too.

  • +1 Add Marc Gravell too: meta.stackexchange.com/users/23354/marc-gravell – HackerKarma Sep 15 '15 at 3:08
  • Looks like everything posted before April 22, 2014 disappeared. – animuson Sep 15 '15 at 3:21
  • 5
    Ugh, that might be my fault. I did a blog build earlier today... and I vaguely recall "sometimes posts disappear!" being a thing, but I couldn't possibly tell you how or why. I will see what's what ASAP. – Adam Lear Sep 15 '15 at 3:43
  • 2
    @AnnaLear the default _config has limit_posts: 50, unlike the _blog.config. That tripped me up locally and could be related. – D.G. Sep 15 '15 at 5:09
  • I reproduced this issue as well trying to find this post blog.stackexchange.com/2011/06/optimizing-for-pearls-not-sand – Travis J Sep 15 '15 at 5:54
  • @D.G. Our builds should be running with _blog.config: Jekyll build --config '_blog.config.yml' --no-watch. Looking into why that is sometimes not respected. – Adam Lear Sep 15 '15 at 6:10
  • 1
    @AnnaLear Mr Hyde, obviously. – D.G. Sep 15 '15 at 6:20
15

For the curious, here's why once in a while the incorrect configuration file was loaded: Jekyll uses a little library called Mercenary that, among other things, is responsible for passing the parsed command line options to Jekyll. Mercenary had an obscure bug that caused these options to be incorrect; this bug was fixed in Mercenary 0.3.4.

The Jekyll installation on our build servers is based on PortableJekyll, and while some of the included gems (notably, Jekyll itself) have been updated over the versions that are shipped in PortableJekyll, Mercenary is still on 0.3.3, and thus still includes that bug. We'll be sure to update that today.

  • 1
    wonder what would happen when Mercenary version gets to 4.0.4 – gnat Sep 15 '15 at 12:07
  • 2
    @gnat Prior to that, 4.0.2 would be more concerning for many. – user213963 Sep 15 '15 at 13:18
6

Good news/meh news: I kicked off another build and that one seems to have used the right config file, so the posts are back. (Yay!) But, this also means we still don't know why this build sometimes fails.

We use TeamCity, and we're seeing the following in the build log for a bad build:

[Jekyll build] Jekyll build --config '_blog.config.yml' --no-watch
[Jekyll build] Configuration file: C:/BuildAgent/work/a24cc5c53d3309db/blog/_config.yml
[Jekyll build]             Source: C:/BuildAgent/work/a24cc5c53d3309db/blog
[Jekyll build]        Destination: C:/BuildAgent/work/a24cc5c53d3309db/blog/_site

vs a good build:

[Jekyll build] Jekyll build --config '_blog.config.yml' --no-watch
[Jekyll build] Configuration file: _blog.config.yml
[Jekyll build]             Source: C:/BuildAgent/work/a24cc5c53d3309db/blog
[Jekyll build]        Destination: C:/BuildAgent/work/a24cc5c53d3309db/blog/_site

So... that'll be a fun one to figure out.

You must log in to answer this question.