You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airflow.apache.org by siddharth anand <r3...@gmail.com> on 2018/05/15 13:50:18 UTC
Fwd: Cannot access https://cms.apache.org/incubator/publish
Kaxil,
Can you try these steps and update the airflow wiki (committer guide) based on your findings?
-s
Sent from Sid's iPhone
Begin forwarded message:
> From: Martin Gainty <mg...@hotmail.com>
> Date: May 15, 2018 at 4:21:13 AM PDT
> To: "sanand@apache.org" <sa...@apache.org>
> Subject: Re: Cannot access https://cms.apache.org/incubator/publish
>
> Hi Anand
>
> apparently the new URL is incubator.apache.org as I could not find any references to cms ..here is jbake readme
> # Apache Incubator Website
> 2
> 3
> ## Prerequisites
> 4
> 5
> The website is built using JBake and a Groovy template. The builds for the website do require internet access.
> 6
> 7
> - Install JBake from http://jbake.org/download.html
> 8
> - Create an environment variable `JBAKE_HOME` pointing to your JBake installation
> 9
> - Ensure that you have a JVM locally, e.g. [OpenJDK](http://openjdk.java.net/install/)
> 10
> 11
> ## Building & Running the site
> 12
> 13
> There is a custom `bake.sh` file that is used to build the website. You can call it with any of the [arguments you would pass to jbake](http://jbake.org/docs/2.5.1/#bake_command).
> 14
> The easiest way to use it is to run `./bake.sh -b -s` this will start up JBake in a watching mode as you make changes it will refresh after a short period of time.
> 15
> While working with it locally, you'll notice that the site URLs redirect to `incubator.apache.org`, to change this edit `jbake.properties` and uncomment the line referencing `localhost`
> 16
> 17
> ## Jenkins Setup
> 18
> 19
> Commits to the `jbake-site` branch are automatically checked out and built using `build_site.sh`. Once this goes live those commits will go against `master`. The jenkins job can be found at [https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20Site/](https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20Site/)
> 20
> The result of the commits are pushed to the `asf-site` branch which are then published using `gitwcsub`
> 21
> 22
> ## Asciidoctor
> 23
> 24
> Most of the pages in the site are written using Asciidoctor. While it is a form of asciidoc it does have some [syntax differences that are worth reviewing](http://asciidoctor.org/docs/asciidoc-syntax-quick-reference/)
> 25
> 26
> ## Groovy Templates
> 27
> 28
> The site templates are written in groovy scripts. Even though the files end with `.gsp` they are not GSP files and do not have access to tag libraries. You can run custom code in them, similar to what is done in [homepage.gsp](templates/homepage.gsp)
>
> if you have hard requirement to accessing cms.apache.org
> write a request for username/password to cms.apache.org to site admin: dns@apache.org
>
> Good Luck!
> Martin
> ______________________________________________
>
>
>
> From: John D. Ament <jo...@apache.org>
> Sent: Monday, May 14, 2018 10:01 PM
> To: general@incubator.apache.org
> Cc: sanand@apache.org
> Subject: Re: Cannot access https://cms.apache.org/incubator/publish
>
> The Incubator website is no longer managed via CMS. Please review
> https://incubator.apache.org/guides/website.html
> Updating the top-level Incubator website
> incubator.apache.org
> The Incubator website is generated by the incubator git repository. The primary document format is asciidoc, templates are based on gsp, and we use jbake to build it. You can edit files directly on github and raise a pull request or just checkout the repository at https://git-wip-us.apache.org/repos ...
>
>
>
> John
>
> On Mon, May 14, 2018 at 9:17 PM Martin Gainty <mg...@hotmail.com> wrote:
>
> > Hi Sid
> >
> >
> > as long as you have JavaScript enabled in the browser
> > and you gave the same issue with curl then AFAIK its a permissions error
> >
> >
> > can you contract admin or webmaster and have them email you valid
> > username/password
> >
> > ?
> >
> > Martin
> > ______________________________________________
> >
> >
> >
> > ________________________________
> > From: Sid Anand <sa...@apache.org>
> > Sent: Monday, May 14, 2018 9:12 PM
> > To: Martin Gainty
> > Cc: general@incubator.apache.org
> > Subject: Re: Cannot access https://cms.apache.org/incubator/publish
> >
> > So, perhaps I (sanand) don't have the necessary permissions?
> > -s
> >
> > On Mon, May 14, 2018 at 6:11 PM, Sid Anand <sa...@apache.org> wrote:
> >
> > > I get the same error (I've hidden my password).
> > >
> > > sianand@LM-SJN-21002367:~ $ curl --user sanand:****
> > > https://cms.apache.org/incubator/publish
> > >
> > > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
> > >
> > > <html><head>
> > >
> > > <title>404 Not Found</title>
> > >
> > > </head><body>
> > >
> > > <h1>Page Not Found</h1>
> > >
> > > <p>The requested URL was not found on this server. If you are trying to
> > > edit a CMS-driven page, your local working copy may have been pruned.</p>
> > >
> > > <p>Please go to <a href='https://cms.apache.org'>cms.apache.org</a>,
> > find
> > > your project, and click on 'force new working copy' to create a new
> > >
> > > working copy to edit.</p>
> > >
> > > </body></html>
> > >
> > >
> > > On Mon, May 14, 2018 at 4:22 PM, Martin Gainty <mg...@hotmail.com>
> > > wrote:
> > >
> > >> hi sid
> > >>
> > >>
> > >> can you access https with your credentials using curl e.g
> > >>
> > >> curl --user <user:password> https://cms.apache.org/incubator/publish
> > >>
> > >>
> > >> ?
> > >> Martin
> > >> ______________________________________________
> > >>
> > >>
> > >>
> > >> ------------------------------
> > >> *From:* Sid Anand <sa...@apache.org>
> > >> *Sent:* Monday, May 14, 2018 5:30 PM
> > >> *To:* general@incubator.apache.org
> > >> *Subject:* Cannot access https://cms.apache.org/incubator/publish
> > >>
> > >> Hi Folks!
> > >> Several committers/PMC members from Apache Airflow cannot publish
> > updates
> > >> to the Airflow incubator project page.
> > >>
> > >> The steps below used to work for us:
> > >>
> > >> Page at https://cwiki.apache.org/confluence/display/AIRFLOW/
> > >> Committers%27+Guide instructs doing the following:
> > >>
> > >>
> > >> 1. Check out the svn repo at https://svn.apache.org/
> > >> repos/asf/incubator/public/trunk/content/projects
> > >> <https://svn.apache.org/repos/asf/incubator/public/trunk/con
> > >> tent/projects>
> > >> 2. Update {local_working_dir}/content/projects/airflow.xml
> > >> 3. svn commit -m "Adding xxx as committer/pmc member to apache
> > airflow"
> > >> 4. Publish to the incubator website using https://cms.apache.org/
> > >> incubator/publish
> > >> 5. Verify your change on http://incubator.apache.
> > >> org/projects/airflow.html
> > >>
> > >>
> > >> I completed first 3 steps but I can't access the link (
> > >> https://cms.apache.org/incubator/publish) on 4th step and it gives me
> > >> following error:
> > >>
> > >> Page Not Found
> > >> > The requested URL was not found on this server. If you are trying to
> > >> edit
> > >> > a CMS-driven page, your local working copy may have been pruned.
> > >> > Please go to cms.apache.org, find your project, and click on 'force
> > new
> > >> > working copy' to create a new working copy to edit.
> > >>
> > >
> > >
> >
Re: Cannot access https://cms.apache.org/incubator/publish
Posted by Naik Kaxil <k....@reply.com>.
Sure I will do this and update the wiki
On 15/05/2018, 14:51, "siddharth anand" <r3...@gmail.com> wrote:
Kaxil,
Can you try these steps and update the airflow wiki (committer guide) based on your findings?
-s
Sent from Sid's iPhone
Kaxil Naik
Data Reply
2nd Floor, Nova South
160 Victoria Street, Westminster
London SW1E 5LB - UK
phone: +44 (0)20 7730 6000
k.naik@reply.com
www.reply.com
Begin forwarded message:
> From: Martin Gainty <mg...@hotmail.com>
> Date: May 15, 2018 at 4:21:13 AM PDT
> To: "sanand@apache.org" <sa...@apache.org>
> Subject: Re: Cannot access https://cms.apache.org/incubator/publish
>
> Hi Anand
>
> apparently the new URL is incubator.apache.org as I could not find any references to cms ..here is jbake readme
> # Apache Incubator Website
> 2
> 3
> ## Prerequisites
> 4
> 5
> The website is built using JBake and a Groovy template. The builds for the website do require internet access.
> 6
> 7
> - Install JBake from http://jbake.org/download.html
> 8
> - Create an environment variable `JBAKE_HOME` pointing to your JBake installation
> 9
> - Ensure that you have a JVM locally, e.g. [OpenJDK](http://openjdk.java.net/install/)
> 10
> 11
> ## Building & Running the site
> 12
> 13
> There is a custom `bake.sh` file that is used to build the website. You can call it with any of the [arguments you would pass to jbake](http://jbake.org/docs/2.5.1/#bake_command).
> 14
> The easiest way to use it is to run `./bake.sh -b -s` this will start up JBake in a watching mode as you make changes it will refresh after a short period of time.
> 15
> While working with it locally, you'll notice that the site URLs redirect to `incubator.apache.org`, to change this edit `jbake.properties` and uncomment the line referencing `localhost`
> 16
> 17
> ## Jenkins Setup
> 18
> 19
> Commits to the `jbake-site` branch are automatically checked out and built using `build_site.sh`. Once this goes live those commits will go against `master`. The jenkins job can be found at [https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20Site/](https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20Site/)
> 20
> The result of the commits are pushed to the `asf-site` branch which are then published using `gitwcsub`
> 21
> 22
> ## Asciidoctor
> 23
> 24
> Most of the pages in the site are written using Asciidoctor. While it is a form of asciidoc it does have some [syntax differences that are worth reviewing](http://asciidoctor.org/docs/asciidoc-syntax-quick-reference/)
> 25
> 26
> ## Groovy Templates
> 27
> 28
> The site templates are written in groovy scripts. Even though the files end with `.gsp` they are not GSP files and do not have access to tag libraries. You can run custom code in them, similar to what is done in [homepage.gsp](templates/homepage.gsp)
>
> if you have hard requirement to accessing cms.apache.org
> write a request for username/password to cms.apache.org to site admin: dns@apache.org
>
> Good Luck!
> Martin
> ______________________________________________
>
>
>
> From: John D. Ament <jo...@apache.org>
> Sent: Monday, May 14, 2018 10:01 PM
> To: general@incubator.apache.org
> Cc: sanand@apache.org
> Subject: Re: Cannot access https://cms.apache.org/incubator/publish
>
> The Incubator website is no longer managed via CMS. Please review
> https://incubator.apache.org/guides/website.html
> Updating the top-level Incubator website
> incubator.apache.org
> The Incubator website is generated by the incubator git repository. The primary document format is asciidoc, templates are based on gsp, and we use jbake to build it. You can edit files directly on github and raise a pull request or just checkout the repository at https://git-wip-us.apache.org/repos ...
>
>
>
> John
>
> On Mon, May 14, 2018 at 9:17 PM Martin Gainty <mg...@hotmail.com> wrote:
>
> > Hi Sid
> >
> >
> > as long as you have JavaScript enabled in the browser
> > and you gave the same issue with curl then AFAIK its a permissions error
> >
> >
> > can you contract admin or webmaster and have them email you valid
> > username/password
> >
> > ?
> >
> > Martin
> > ______________________________________________
> >
> >
> >
> > ________________________________
> > From: Sid Anand <sa...@apache.org>
> > Sent: Monday, May 14, 2018 9:12 PM
> > To: Martin Gainty
> > Cc: general@incubator.apache.org
> > Subject: Re: Cannot access https://cms.apache.org/incubator/publish
> >
> > So, perhaps I (sanand) don't have the necessary permissions?
> > -s
> >
> > On Mon, May 14, 2018 at 6:11 PM, Sid Anand <sa...@apache.org> wrote:
> >
> > > I get the same error (I've hidden my password).
> > >
> > > sianand@LM-SJN-21002367:~ $ curl --user sanand:****
> > > https://cms.apache.org/incubator/publish
> > >
> > > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
> > >
> > > <html><head>
> > >
> > > <title>404 Not Found</title>
> > >
> > > </head><body>
> > >
> > > <h1>Page Not Found</h1>
> > >
> > > <p>The requested URL was not found on this server. If you are trying to
> > > edit a CMS-driven page, your local working copy may have been pruned.</p>
> > >
> > > <p>Please go to <a href='https://cms.apache.org'>cms.apache.org</a>,
> > find
> > > your project, and click on 'force new working copy' to create a new
> > >
> > > working copy to edit.</p>
> > >
> > > </body></html>
> > >
> > >
> > > On Mon, May 14, 2018 at 4:22 PM, Martin Gainty <mg...@hotmail.com>
> > > wrote:
> > >
> > >> hi sid
> > >>
> > >>
> > >> can you access https with your credentials using curl e.g
> > >>
> > >> curl --user <user:password> https://cms.apache.org/incubator/publish
> > >>
> > >>
> > >> ?
> > >> Martin
> > >> ______________________________________________
> > >>
> > >>
> > >>
> > >> ------------------------------
> > >> *From:* Sid Anand <sa...@apache.org>
> > >> *Sent:* Monday, May 14, 2018 5:30 PM
> > >> *To:* general@incubator.apache.org
> > >> *Subject:* Cannot access https://cms.apache.org/incubator/publish
> > >>
> > >> Hi Folks!
> > >> Several committers/PMC members from Apache Airflow cannot publish
> > updates
> > >> to the Airflow incubator project page.
> > >>
> > >> The steps below used to work for us:
> > >>
> > >> Page at https://cwiki.apache.org/confluence/display/AIRFLOW/
> > >> Committers%27+Guide instructs doing the following:
> > >>
> > >>
> > >> 1. Check out the svn repo at https://svn.apache.org/
> > >> repos/asf/incubator/public/trunk/content/projects
> > >> <https://svn.apache.org/repos/asf/incubator/public/trunk/con
> > >> tent/projects>
> > >> 2. Update {local_working_dir}/content/projects/airflow.xml
> > >> 3. svn commit -m "Adding xxx as committer/pmc member to apache
> > airflow"
> > >> 4. Publish to the incubator website using https://cms.apache.org/
> > >> incubator/publish
> > >> 5. Verify your change on http://incubator.apache.
> > >> org/projects/airflow.html
> > >>
> > >>
> > >> I completed first 3 steps but I can't access the link (
> > >> https://cms.apache.org/incubator/publish) on 4th step and it gives me
> > >> following error:
> > >>
> > >> Page Not Found
> > >> > The requested URL was not found on this server. If you are trying to
> > >> edit
> > >> > a CMS-driven page, your local working copy may have been pruned.
> > >> > Please go to cms.apache.org, find your project, and click on 'force
> > new
> > >> > working copy' to create a new working copy to edit.
> > >>
> > >
> > >
> >
Re: Cannot access https://cms.apache.org/incubator/publish
Posted by Naik Kaxil <k....@reply.com>.
Hi Sid,
I think Jenkins trigger a build on incubator svn repo daily as seen here https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20Site/426/console
When I checked http://incubator.apache.org/projects/airflow.html the page has already been updated.
However, I still tried to follow the steps in the last email but I got lost of jbake errors.
Regards,
Kaxil
On 15/05/2018, 14:51, "siddharth anand" <r3...@gmail.com> wrote:
Kaxil,
Can you try these steps and update the airflow wiki (committer guide) based on your findings?
-s
Sent from Sid's iPhone
Kaxil Naik
Data Reply
2nd Floor, Nova South
160 Victoria Street, Westminster
London SW1E 5LB - UK
phone: +44 (0)20 7730 6000
k.naik@reply.com
www.reply.com
Begin forwarded message:
> From: Martin Gainty <mg...@hotmail.com>
> Date: May 15, 2018 at 4:21:13 AM PDT
> To: "sanand@apache.org" <sa...@apache.org>
> Subject: Re: Cannot access https://cms.apache.org/incubator/publish
>
> Hi Anand
>
> apparently the new URL is incubator.apache.org as I could not find any references to cms ..here is jbake readme
> # Apache Incubator Website
> 2
> 3
> ## Prerequisites
> 4
> 5
> The website is built using JBake and a Groovy template. The builds for the website do require internet access.
> 6
> 7
> - Install JBake from http://jbake.org/download.html
> 8
> - Create an environment variable `JBAKE_HOME` pointing to your JBake installation
> 9
> - Ensure that you have a JVM locally, e.g. [OpenJDK](http://openjdk.java.net/install/)
> 10
> 11
> ## Building & Running the site
> 12
> 13
> There is a custom `bake.sh` file that is used to build the website. You can call it with any of the [arguments you would pass to jbake](http://jbake.org/docs/2.5.1/#bake_command).
> 14
> The easiest way to use it is to run `./bake.sh -b -s` this will start up JBake in a watching mode as you make changes it will refresh after a short period of time.
> 15
> While working with it locally, you'll notice that the site URLs redirect to `incubator.apache.org`, to change this edit `jbake.properties` and uncomment the line referencing `localhost`
> 16
> 17
> ## Jenkins Setup
> 18
> 19
> Commits to the `jbake-site` branch are automatically checked out and built using `build_site.sh`. Once this goes live those commits will go against `master`. The jenkins job can be found at [https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20Site/](https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20Site/)
> 20
> The result of the commits are pushed to the `asf-site` branch which are then published using `gitwcsub`
> 21
> 22
> ## Asciidoctor
> 23
> 24
> Most of the pages in the site are written using Asciidoctor. While it is a form of asciidoc it does have some [syntax differences that are worth reviewing](http://asciidoctor.org/docs/asciidoc-syntax-quick-reference/)
> 25
> 26
> ## Groovy Templates
> 27
> 28
> The site templates are written in groovy scripts. Even though the files end with `.gsp` they are not GSP files and do not have access to tag libraries. You can run custom code in them, similar to what is done in [homepage.gsp](templates/homepage.gsp)
>
> if you have hard requirement to accessing cms.apache.org
> write a request for username/password to cms.apache.org to site admin: dns@apache.org
>
> Good Luck!
> Martin
> ______________________________________________
>
>
>
> From: John D. Ament <jo...@apache.org>
> Sent: Monday, May 14, 2018 10:01 PM
> To: general@incubator.apache.org
> Cc: sanand@apache.org
> Subject: Re: Cannot access https://cms.apache.org/incubator/publish
>
> The Incubator website is no longer managed via CMS. Please review
> https://incubator.apache.org/guides/website.html
> Updating the top-level Incubator website
> incubator.apache.org
> The Incubator website is generated by the incubator git repository. The primary document format is asciidoc, templates are based on gsp, and we use jbake to build it. You can edit files directly on github and raise a pull request or just checkout the repository at https://git-wip-us.apache.org/repos ...
>
>
>
> John
>
> On Mon, May 14, 2018 at 9:17 PM Martin Gainty <mg...@hotmail.com> wrote:
>
> > Hi Sid
> >
> >
> > as long as you have JavaScript enabled in the browser
> > and you gave the same issue with curl then AFAIK its a permissions error
> >
> >
> > can you contract admin or webmaster and have them email you valid
> > username/password
> >
> > ?
> >
> > Martin
> > ______________________________________________
> >
> >
> >
> > ________________________________
> > From: Sid Anand <sa...@apache.org>
> > Sent: Monday, May 14, 2018 9:12 PM
> > To: Martin Gainty
> > Cc: general@incubator.apache.org
> > Subject: Re: Cannot access https://cms.apache.org/incubator/publish
> >
> > So, perhaps I (sanand) don't have the necessary permissions?
> > -s
> >
> > On Mon, May 14, 2018 at 6:11 PM, Sid Anand <sa...@apache.org> wrote:
> >
> > > I get the same error (I've hidden my password).
> > >
> > > sianand@LM-SJN-21002367:~ $ curl --user sanand:****
> > > https://cms.apache.org/incubator/publish
> > >
> > > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
> > >
> > > <html><head>
> > >
> > > <title>404 Not Found</title>
> > >
> > > </head><body>
> > >
> > > <h1>Page Not Found</h1>
> > >
> > > <p>The requested URL was not found on this server. If you are trying to
> > > edit a CMS-driven page, your local working copy may have been pruned.</p>
> > >
> > > <p>Please go to <a href='https://cms.apache.org'>cms.apache.org</a>,
> > find
> > > your project, and click on 'force new working copy' to create a new
> > >
> > > working copy to edit.</p>
> > >
> > > </body></html>
> > >
> > >
> > > On Mon, May 14, 2018 at 4:22 PM, Martin Gainty <mg...@hotmail.com>
> > > wrote:
> > >
> > >> hi sid
> > >>
> > >>
> > >> can you access https with your credentials using curl e.g
> > >>
> > >> curl --user <user:password> https://cms.apache.org/incubator/publish
> > >>
> > >>
> > >> ?
> > >> Martin
> > >> ______________________________________________
> > >>
> > >>
> > >>
> > >> ------------------------------
> > >> *From:* Sid Anand <sa...@apache.org>
> > >> *Sent:* Monday, May 14, 2018 5:30 PM
> > >> *To:* general@incubator.apache.org
> > >> *Subject:* Cannot access https://cms.apache.org/incubator/publish
> > >>
> > >> Hi Folks!
> > >> Several committers/PMC members from Apache Airflow cannot publish
> > updates
> > >> to the Airflow incubator project page.
> > >>
> > >> The steps below used to work for us:
> > >>
> > >> Page at https://cwiki.apache.org/confluence/display/AIRFLOW/
> > >> Committers%27+Guide instructs doing the following:
> > >>
> > >>
> > >> 1. Check out the svn repo at https://svn.apache.org/
> > >> repos/asf/incubator/public/trunk/content/projects
> > >> <https://svn.apache.org/repos/asf/incubator/public/trunk/con
> > >> tent/projects>
> > >> 2. Update {local_working_dir}/content/projects/airflow.xml
> > >> 3. svn commit -m "Adding xxx as committer/pmc member to apache
> > airflow"
> > >> 4. Publish to the incubator website using https://cms.apache.org/
> > >> incubator/publish
> > >> 5. Verify your change on http://incubator.apache.
> > >> org/projects/airflow.html
> > >>
> > >>
> > >> I completed first 3 steps but I can't access the link (
> > >> https://cms.apache.org/incubator/publish) on 4th step and it gives me
> > >> following error:
> > >>
> > >> Page Not Found
> > >> > The requested URL was not found on this server. If you are trying to
> > >> edit
> > >> > a CMS-driven page, your local working copy may have been pruned.
> > >> > Please go to cms.apache.org, find your project, and click on 'force
> > new
> > >> > working copy' to create a new working copy to edit.
> > >>
> > >
> > >
> >