Can't comment in github if you don't create a PR.  Create a PR.

There are definitely some things here that will break the site when it's
published.  It needs more work.


On Tue, Jul 9, 2013 at 11:16 PM, Everett Toews
<[email protected]>wrote:

> Forgot to mention, I won't be able to focus on this much tomorrow so any
> review comments will have to wait until Thursday.
>
> Regards,
> Everett
>
> On Jul 9, 2013, at 11:05 PM, Everett Toews wrote:
>
> > Here's the solution [1] abayer and I found this afternoon. The jclouds
> site can now be edited and proofed entirely online. Here's an example [2].
> >
> > I haven't done a PR to jclouds/jclouds-site yet as it would involve
> changing the CloudBees job. Specifically, it would need to be changed as in
> the Build section of this Configure [3].
> >
> > If you're still want/need to run jekyll locally, you would use this
> command to start it.
> >
> > jekyll serve --watch --baseurl '/'
> >
> > Please review [1] and [2]. I imagine I must have missed some refs
> somewhere.
> >
> > Thanks,
> > Everett
> >
> > [1]
> https://github.com/rackerlabs/jclouds-site/compare/relative-everything?expand=1
> > [2]
> https://jclouds.ci.cloudbees.com/job/ept-site-tmp/13/artifact/_site/index.html
> > [3] https://jclouds.ci.cloudbees.com/job/ept-site-tmp/configure
> >
> > On Jul 8, 2013, at 6:41 AM, Everett Toews wrote:
> >
> > Cool! Thanks AndrewP.
> >
> > Let's come out of the meetup tonight with actionable task that will
> finish this off this week.
> >
> > Cheers,
> > Everett
> >
> > On Jul 8, 2013, at 8:03 AM, Andrew Phillips wrote:
> >
> > There will be more chances to chat at the meetup, I just returned from
> the
> > Black Rock Desert.  I have had to set this up before, and there are some
> > much simpler options.
> >
> > Glad to hear - looking forward to seeing what we come up with. Just as
> an additional data point, I've put up an experimental DEV@cloud job [1]
> to see if that approach could even work.
> >
> > It's not set up to trigger on pull requests right now, but the main
> point is that it saves the generated site files *per build* [2, 3], so
> multiple pull requests would not overwrite each other.
> >
> > The main challenge currently is that the links do not work [4] because
> they're, um, not relative ;-)
> >
> > ap
> >
> > [1]
> https://jclouds.ci.cloudbees.com/job/EXPERIMENTAL-jclouds.github.com/
> > [2]
> https://jclouds.ci.cloudbees.com/job/EXPERIMENTAL-jclouds.github.com/4/artifact/
> > [3]
> https://jclouds.ci.cloudbees.com/job/EXPERIMENTAL-jclouds.github.com/5/artifact/
> > [4]
> https://jclouds.ci.cloudbees.com/job/EXPERIMENTAL-jclouds.github.com/4/artifact/_site/index.html
> >
> >
>
>

Reply via email to