Re: mxnet.io website publishing

[Marco de Abreu]

Thanks a lot Aaron for revamping the entire process pipeline! I'm sure
we'll now have a more consistent and stable user experience for our
website.

So far, everything seems to be working flawlessly, great job!

As explained by Aaron, you can now access
http://mxnet.incubator.apache.org/date.txt in order to see the date of the
last update. This allows you to check whether your API updates or tutorials
have already been published or if there might be a problem.

-Marco

On Wed, Apr 25, 2018 at 8:00 PM, Aaron Markham 
wrote:

> The MXNet website has been updated. Please let me know if there are any
> issues.
> It always seems to get hung up on big commits, so you have to publish a
> tiny update. I've added this to the publish CI job via the date.txt file
> which happens as a follow up commit to nudge the site replication process.
> (Thanks for the idea, Marco).
>
> Cheers,
> Aaron
>
> On Wed, Apr 25, 2018 at 2:16 PM, Aaron Markham 
> wrote:
>
> > I've updated Jenkins CI and the docs build scripts with #10485
> > . The CI run to
> > build the website with the latest docs has completed successfully
> >  20build%20-%20test%20pipeline/62/>,
> > and it deployed the docs to my fork
> > . A preview of
> the
> > site is hosted here: http://34.235.144.251/
> >
> > To get the site by refreshed by deploying to the production repo, I need
> > credentials for the site repo at https://github.com/apache/
> > incubator-mxnet-site. Then I'll rerun the publish job after pointing it
> > at production.
> >
> > Who can grant me access to the incubator-mxnet-site repo? There are
> > several accounts in CI's security tokens list that might work, but I
> don't
> > want to use any of those without permission (and I'm not sure if they
> have
> > access anyway). If you're setup and want to let me use yours, that's
> > fine... just let me know.
> >
> > Cheers,
> > Aaron
> >
> >
> >
> >
> >
>

Re: mxnet.io website publishing

[Aaron Markham]

The MXNet website has been updated. Please let me know if there are any
issues.
It always seems to get hung up on big commits, so you have to publish a
tiny update. I've added this to the publish CI job via the date.txt file
which happens as a follow up commit to nudge the site replication process.
(Thanks for the idea, Marco).

Cheers,
Aaron

On Wed, Apr 25, 2018 at 2:16 PM, Aaron Markham 
wrote:

> I've updated Jenkins CI and the docs build scripts with #10485
> . The CI run to
> build the website with the latest docs has completed successfully
> ,
> and it deployed the docs to my fork
> . A preview of the
> site is hosted here: http://34.235.144.251/
>
> To get the site by refreshed by deploying to the production repo, I need
> credentials for the site repo at https://github.com/apache/
> incubator-mxnet-site. Then I'll rerun the publish job after pointing it
> at production.
>
> Who can grant me access to the incubator-mxnet-site repo? There are
> several accounts in CI's security tokens list that might work, but I don't
> want to use any of those without permission (and I'm not sure if they have
> access anyway). If you're setup and want to let me use yours, that's
> fine... just let me know.
>
> Cheers,
> Aaron
>
>
>
>
>

mxnet.io website publishing

[Aaron Markham]

I've updated Jenkins CI and the docs build scripts with #10485
. The CI run to build
the website with the latest docs has completed successfully
,
and it deployed the docs to my fork
. A preview of the
site is hosted here: http://34.235.144.251/

To get the site by refreshed by deploying to the production repo, I need
credentials for the site repo at
https://github.com/apache/incubator-mxnet-site. Then I'll rerun the publish
job after pointing it at production.

Who can grant me access to the incubator-mxnet-site repo? There are several
accounts in CI's security tokens list that might work, but I don't want to
use any of those without permission (and I'm not sure if they have access
anyway). If you're setup and want to let me use yours, that's fine... just
let me know.

Cheers,
Aaron