You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafodion.apache.org by Gunnar Tapper <ta...@gmail.com> on 2015/12/02 22:24:40 UTC
Publishing Website
Hi,
https://issues.apache.org/jira/browse/INFRA-9831 contains a comment that
states:
Alice has pushed content to the asf-site branch.
https://git-wip-us.apache.org/repos/asf?p=incubator-trafodion-site.git;a=tree;h=refs/heads/asf-site;hb=refs/heads/asf-site
But the site is not showing up:
http://trafodion.incubator.apache.org/
What did we miss?
This seems to indicate that the actual website content needs to be in an
asf-site branch, which seems to be complementary to the main Trafodion
branch?
So, if I check in the code, then how does the docs/target folder get built,
copied to asf-site, and then published? Obviously, this works needs to be
done by a committer but I'd like to understand the steps involved.
--
Thanks,
Gunnar
*If you think you can you can, if you think you can't you're right.*
Re: Publishing Website
Posted by Gunnar Tapper <ta...@gmail.com>.
Thanks. This is exactly where this project is at including copying of
documents.
Gunnar
On Wed, Dec 2, 2015 at 3:42 PM, Stack <st...@duboce.net> wrote:
> Manual for now till you figure all involved then try to automate (Only now
> is the project I work on getting to a state where the push of the website
> is automated). Usually you'll have stuff you'll want to copy out of main
> repo and over to the site repo -- stuff like javadoc and other doc product
> -- that you'll want to include in any generated site.
>
> St.Ack
>
> On Wed, Dec 2, 2015 at 2:21 PM, Gunnar Tapper <ta...@gmail.com>
> wrote:
>
> > Hi,
> >
> > Is this manual process the preferred way or should we be working out of
> > https://git-wip-us.apache.org/repos/asf/incubator-trafodion-site.git
> > directly
> > for future modifications? What do other podlings do? Alas, the
> > documentation regarding this is labelled as VERY out-of-date on
> > http://incubator.apache.org/guides/sites.html, which makes it hard to
> know
> > what to do.
> >
> > Thanks,
> >
> > Gunnar
> >
> > On Wed, Dec 2, 2015 at 3:07 PM, Stack <st...@duboce.net> wrote:
> >
> > > On Wed, Dec 2, 2015 at 2:05 PM, Gunnar Tapper <tapper.gunnar@gmail.com
> >
> > > wrote:
> > >
> > > > ...
> > > > 6. Magic happens. :)
> > > >
> > >
> > > Exactly! (gitpubsub runs on a period and copies over any changes...)
> > >
> > > St.Ack
> > >
> >
> >
> >
> > --
> > Thanks,
> >
> > Gunnar
> > *If you think you can you can, if you think you can't you're right.*
> >
>
--
Thanks,
Gunnar
*If you think you can you can, if you think you can't you're right.*
Re: Publishing Website
Posted by Stack <st...@duboce.net>.
Manual for now till you figure all involved then try to automate (Only now
is the project I work on getting to a state where the push of the website
is automated). Usually you'll have stuff you'll want to copy out of main
repo and over to the site repo -- stuff like javadoc and other doc product
-- that you'll want to include in any generated site.
St.Ack
On Wed, Dec 2, 2015 at 2:21 PM, Gunnar Tapper <ta...@gmail.com>
wrote:
> Hi,
>
> Is this manual process the preferred way or should we be working out of
> https://git-wip-us.apache.org/repos/asf/incubator-trafodion-site.git
> directly
> for future modifications? What do other podlings do? Alas, the
> documentation regarding this is labelled as VERY out-of-date on
> http://incubator.apache.org/guides/sites.html, which makes it hard to know
> what to do.
>
> Thanks,
>
> Gunnar
>
> On Wed, Dec 2, 2015 at 3:07 PM, Stack <st...@duboce.net> wrote:
>
> > On Wed, Dec 2, 2015 at 2:05 PM, Gunnar Tapper <ta...@gmail.com>
> > wrote:
> >
> > > ...
> > > 6. Magic happens. :)
> > >
> >
> > Exactly! (gitpubsub runs on a period and copies over any changes...)
> >
> > St.Ack
> >
>
>
>
> --
> Thanks,
>
> Gunnar
> *If you think you can you can, if you think you can't you're right.*
>
Re: Publishing Website
Posted by Gunnar Tapper <ta...@gmail.com>.
Hi,
Is this manual process the preferred way or should we be working out of
https://git-wip-us.apache.org/repos/asf/incubator-trafodion-site.git directly
for future modifications? What do other podlings do? Alas, the
documentation regarding this is labelled as VERY out-of-date on
http://incubator.apache.org/guides/sites.html, which makes it hard to know
what to do.
Thanks,
Gunnar
On Wed, Dec 2, 2015 at 3:07 PM, Stack <st...@duboce.net> wrote:
> On Wed, Dec 2, 2015 at 2:05 PM, Gunnar Tapper <ta...@gmail.com>
> wrote:
>
> > ...
> > 6. Magic happens. :)
> >
>
> Exactly! (gitpubsub runs on a period and copies over any changes...)
>
> St.Ack
>
--
Thanks,
Gunnar
*If you think you can you can, if you think you can't you're right.*
Re: Publishing Website
Posted by Stack <st...@duboce.net>.
On Wed, Dec 2, 2015 at 2:05 PM, Gunnar Tapper <ta...@gmail.com>
wrote:
> ...
> 6. Magic happens. :)
>
Exactly! (gitpubsub runs on a period and copies over any changes...)
St.Ack
Re: Publishing Website
Posted by Gunnar Tapper <ta...@gmail.com>.
Indeed. It seems that there's repository for the website:
https://issues.apache.org/jira/browse/TRAFODION-31
Maybe the right steps are:
1. Update incubator-trafodion docs etc.
2. Checkin
3. Committer builds
4. Commiter checks out and copies new docs/target content to
https://git-wip-us.apache.org/repos/asf/incubator-trafodion-site.git
5. Committer checks in changes.
6. Magic happens. :)
Thanks,
Gunnar
On Wed, Dec 2, 2015 at 2:59 PM, Steve Varnau <st...@esgyn.com> wrote:
> I think Roberta's process refers to updating the incubator site:
> http://incubator.apache.org/projects/trafodion.html
>
> Whereas Gunnar is trying to figure out how we publish our project site:
> http://trafodion.incubator.apache.org/
>
> --Steve
>
>
> > -----Original Message-----
> > From: Roberta Marton [mailto:roberta.marton@esgyn.com]
> > Sent: Wednesday, December 2, 2015 1:32 PM
> > To: dev@trafodion.incubator.apache.org
> > Subject: RE: Publishing Website
> >
> > Here are the steps I take to publish changes to the PROJECTS website.
> > I have also change the distribution web site but the steps are simpler,
> > you
> > don't have to regenerate the docs.
> >
> > Steps to change the project website:
> >
> > 1. Make sure svn exists – can be downloaded from yum
> > a. which svn
> > b. svn --version (version 1.6.11 worked for me)
> > 2. Create a directory to store the svn repositoy
> > 3. Checkout source code, this creates a directory called incubator:
> > svn co https://svn.apache.org/repos/asf/incubator/public/trunk
> > 4. Go to projects directory, from incubator – cd content/projects
> > 5. Edit the file trafodion.xml and make desired changes
> > 6. Ask for a review of the changes – I sent this to the dev list,
> perhaps
> > the codereview list would have been better.
> > 7. Regenerate the documentation by running 'ant' or 'build'
> > (build.sh/build.bat) from the top level. This transforms the .xml file
> > into
> > .html files and places the resultant files in ../target/site.
> > a. cd <svn-directory>.incubator
> > b. ./build.sh
> > c. cd target/site/projects
> > d. Edit trafodion.html and verify changes exist, don't change this
> > directory
> > nor add it to svn
> > 8. Commit your changes
> > a. svn status
> > b. svn commit –m "message…"
> > c. go to
> > http://svn.apache.org/viewvc/incubator/public/trunk/content/projects/ to
> > see
> > if your changes were committed
> > 9. Did not do this: Review your changes via the "commits" mail list.
> > 10. Wait a minute for the CMS to build your changes.
> > 11. Publish your changes going to:
> > https://cms.apache.org/incubator/publish
> >
> > Roberta
> >
> > -----Original Message-----
> > From: Gunnar Tapper [mailto:tapper.gunnar@gmail.com]
> > Sent: Wednesday, December 2, 2015 1:25 PM
> > To: dev@trafodion.incubator.apache.org
> > Subject: Publishing Website
> >
> > Hi,
> >
> > https://issues.apache.org/jira/browse/INFRA-9831 contains a comment that
> > states:
> >
> > Alice has pushed content to the asf-site branch.
> > https://git-wip-us.apache.org/repos/asf?p=incubator-trafodion-
> > site.git;a=tree;h=refs/heads/asf-site;hb=refs/heads/asf-site
> >
> >
> > But the site is not showing up:
> > http://trafodion.incubator.apache.org/
> >
> > What did we miss?
> >
> > This seems to indicate that the actual website content needs to be in an
> > asf-site branch, which seems to be complementary to the main Trafodion
> > branch?
> >
> > So, if I check in the code, then how does the docs/target folder get
> > built,
> > copied to asf-site, and then published? Obviously, this works needs to be
> > done by a committer but I'd like to understand the steps involved.
> >
> > --
> > Thanks,
> >
> > Gunnar
> > *If you think you can you can, if you think you can't you're right.*
>
--
Thanks,
Gunnar
*If you think you can you can, if you think you can't you're right.*
RE: Publishing Website
Posted by Steve Varnau <st...@esgyn.com>.
I think Roberta's process refers to updating the incubator site:
http://incubator.apache.org/projects/trafodion.html
Whereas Gunnar is trying to figure out how we publish our project site:
http://trafodion.incubator.apache.org/
--Steve
> -----Original Message-----
> From: Roberta Marton [mailto:roberta.marton@esgyn.com]
> Sent: Wednesday, December 2, 2015 1:32 PM
> To: dev@trafodion.incubator.apache.org
> Subject: RE: Publishing Website
>
> Here are the steps I take to publish changes to the PROJECTS website.
> I have also change the distribution web site but the steps are simpler,
> you
> don't have to regenerate the docs.
>
> Steps to change the project website:
>
> 1. Make sure svn exists – can be downloaded from yum
> a. which svn
> b. svn --version (version 1.6.11 worked for me)
> 2. Create a directory to store the svn repositoy
> 3. Checkout source code, this creates a directory called incubator:
> svn co https://svn.apache.org/repos/asf/incubator/public/trunk
> 4. Go to projects directory, from incubator – cd content/projects
> 5. Edit the file trafodion.xml and make desired changes
> 6. Ask for a review of the changes – I sent this to the dev list, perhaps
> the codereview list would have been better.
> 7. Regenerate the documentation by running 'ant' or 'build'
> (build.sh/build.bat) from the top level. This transforms the .xml file
> into
> .html files and places the resultant files in ../target/site.
> a. cd <svn-directory>.incubator
> b. ./build.sh
> c. cd target/site/projects
> d. Edit trafodion.html and verify changes exist, don't change this
> directory
> nor add it to svn
> 8. Commit your changes
> a. svn status
> b. svn commit –m "message…"
> c. go to
> http://svn.apache.org/viewvc/incubator/public/trunk/content/projects/ to
> see
> if your changes were committed
> 9. Did not do this: Review your changes via the "commits" mail list.
> 10. Wait a minute for the CMS to build your changes.
> 11. Publish your changes going to:
> https://cms.apache.org/incubator/publish
>
> Roberta
>
> -----Original Message-----
> From: Gunnar Tapper [mailto:tapper.gunnar@gmail.com]
> Sent: Wednesday, December 2, 2015 1:25 PM
> To: dev@trafodion.incubator.apache.org
> Subject: Publishing Website
>
> Hi,
>
> https://issues.apache.org/jira/browse/INFRA-9831 contains a comment that
> states:
>
> Alice has pushed content to the asf-site branch.
> https://git-wip-us.apache.org/repos/asf?p=incubator-trafodion-
> site.git;a=tree;h=refs/heads/asf-site;hb=refs/heads/asf-site
>
>
> But the site is not showing up:
> http://trafodion.incubator.apache.org/
>
> What did we miss?
>
> This seems to indicate that the actual website content needs to be in an
> asf-site branch, which seems to be complementary to the main Trafodion
> branch?
>
> So, if I check in the code, then how does the docs/target folder get
> built,
> copied to asf-site, and then published? Obviously, this works needs to be
> done by a committer but I'd like to understand the steps involved.
>
> --
> Thanks,
>
> Gunnar
> *If you think you can you can, if you think you can't you're right.*
RE: Publishing Website
Posted by Roberta Marton <ro...@esgyn.com>.
Here are the steps I take to publish changes to the PROJECTS website.
I have also change the distribution web site but the steps are simpler, you
don't have to regenerate the docs.
Steps to change the project website:
1. Make sure svn exists – can be downloaded from yum
a. which svn
b. svn --version (version 1.6.11 worked for me)
2. Create a directory to store the svn repositoy
3. Checkout source code, this creates a directory called incubator:
svn co https://svn.apache.org/repos/asf/incubator/public/trunk
4. Go to projects directory, from incubator – cd content/projects
5. Edit the file trafodion.xml and make desired changes
6. Ask for a review of the changes – I sent this to the dev list, perhaps
the codereview list would have been better.
7. Regenerate the documentation by running 'ant' or 'build'
(build.sh/build.bat) from the top level. This transforms the .xml file into
.html files and places the resultant files in ../target/site.
a. cd <svn-directory>.incubator
b. ./build.sh
c. cd target/site/projects
d. Edit trafodion.html and verify changes exist, don't change this directory
nor add it to svn
8. Commit your changes
a. svn status
b. svn commit –m "message…"
c. go to
http://svn.apache.org/viewvc/incubator/public/trunk/content/projects/ to see
if your changes were committed
9. Did not do this: Review your changes via the "commits" mail list.
10. Wait a minute for the CMS to build your changes.
11. Publish your changes going to: https://cms.apache.org/incubator/publish
Roberta
-----Original Message-----
From: Gunnar Tapper [mailto:tapper.gunnar@gmail.com]
Sent: Wednesday, December 2, 2015 1:25 PM
To: dev@trafodion.incubator.apache.org
Subject: Publishing Website
Hi,
https://issues.apache.org/jira/browse/INFRA-9831 contains a comment that
states:
Alice has pushed content to the asf-site branch.
https://git-wip-us.apache.org/repos/asf?p=incubator-trafodion-site.git;a=tree;h=refs/heads/asf-site;hb=refs/heads/asf-site
But the site is not showing up:
http://trafodion.incubator.apache.org/
What did we miss?
This seems to indicate that the actual website content needs to be in an
asf-site branch, which seems to be complementary to the main Trafodion
branch?
So, if I check in the code, then how does the docs/target folder get built,
copied to asf-site, and then published? Obviously, this works needs to be
done by a committer but I'd like to understand the steps involved.
--
Thanks,
Gunnar
*If you think you can you can, if you think you can't you're right.*