You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by Christian Grobmeier <gr...@apache.org> on 2023/10/13 11:46:04 UTC
Staging website (was: [VOTE] Release Apache Log4j 2.21.0)
>> [1] Christian's recent Jekyll experiment on the `asf-staging` branch
>> of `logging-site` repository confused the INFRA and it is acting
>> strangely. This will *NOT* be an issue when we push the website
>> changes to production, i.e., `asf-site` branch. Though we will try
>> fixing `asf-staging` anyway in the meantime.
On Fri, Oct 13, 2023, at 13:28, Piotr P. Karwasz wrote:
> I think that the problem is that the `asf-staging` branch in
> `logging-site` has switched from a `content` folder to an `output`
> folder, while some of our 6 other site repos have a `content` folder.
> It is fixable, but INFRA offers us an infinite number of
> `logging-<foo>.staged.apache.org` domains and I think we should use
> it.
According to this doc:
https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INFRA&title=git+-+.asf.yaml+features#Git.asf.yamlfeatures-WebsitedeploymentserviceforGitrepositories
We just have to give it a profile:
staging:
profile: mystuff
Would result in:
logging-mystuff.staged.apache.org
I can easily migrate to this.
The folder "output" is the default with ASF infra, but it is possible to replace it with content:
jekyll:
whoami: jekyll
target: asf-staging
outputdir: content
Why is content not causing this issue?
For me both is possible, just trying to understand the best way.
Kind regards,
Christian
Re: Staging website (was: [VOTE] Release Apache Log4j 2.21.0)
Posted by Ralph Goers <ra...@dslextreme.com>.
Nevermind. I was using the wrong url.
Ralph
> On Oct 13, 2023, at 8:21 AM, Ralph Goers <ra...@dslextreme.com> wrote:
>
> I get a 404 trying to access the log4j2 staging web site. Although technically not required for a release I am not comfortable voting for the release without being able to see the web site.
>
> Ralph
>
>> On Oct 13, 2023, at 6:46 AM, Piotr P. Karwasz <pi...@gmail.com> wrote:
>>
>> Hi Christian,
>>
>> On Fri, 13 Oct 2023 at 13:46, Christian Grobmeier <gr...@apache.org> wrote:
>>> Why is content not causing this issue?
>>> For me both is possible, just trying to understand the best way.
>>
>> From what I understand, if a branch (in any repo) has a configuration:
>>
>> staging:
>> whoami: name_of_the_branch
>> profile: <profile>
>> subdir: <subdir>
>>
>> INFRA copies the content of the branch into <subdir> of a directory
>> served by Apache HTTPD. Our current merged site should look like:
>>
>> content/log4jphp/...Log4j PHP stuff...
>> output/...Jekyll stuff...
>>
>> When this is done a script determines which folder is the document
>> root for the server. Since we have both `content` and `output` the
>> script probably fails (I don't see neither Log4PHP nor your Jekyll
>> stuff).
>>
>> Piotr
>
Re: Staging website (was: [VOTE] Release Apache Log4j 2.21.0)
Posted by Ralph Goers <ra...@dslextreme.com>.
I get a 404 trying to access the log4j2 staging web site. Although technically not required for a release I am not comfortable voting for the release without being able to see the web site.
Ralph
> On Oct 13, 2023, at 6:46 AM, Piotr P. Karwasz <pi...@gmail.com> wrote:
>
> Hi Christian,
>
> On Fri, 13 Oct 2023 at 13:46, Christian Grobmeier <gr...@apache.org> wrote:
>> Why is content not causing this issue?
>> For me both is possible, just trying to understand the best way.
>
> From what I understand, if a branch (in any repo) has a configuration:
>
> staging:
> whoami: name_of_the_branch
> profile: <profile>
> subdir: <subdir>
>
> INFRA copies the content of the branch into <subdir> of a directory
> served by Apache HTTPD. Our current merged site should look like:
>
> content/log4jphp/...Log4j PHP stuff...
> output/...Jekyll stuff...
>
> When this is done a script determines which folder is the document
> root for the server. Since we have both `content` and `output` the
> script probably fails (I don't see neither Log4PHP nor your Jekyll
> stuff).
>
> Piotr
Re: Staging website (was: [VOTE] Release Apache Log4j 2.21.0)
Posted by "Piotr P. Karwasz" <pi...@gmail.com>.
Hi Stephen,
On Wed, 18 Oct 2023 at 07:36, Stephen Webb <sw...@gmail.com> wrote:
>
> Hi Piotr,
>
> The Log4cxx staging website URL
> https://logging.staged.apache.org/log4cxx/latest_stable/usage-overview.html
> now reports a 404.
>
> The .asf.yaml contains:
>
> staging:
> profile: ~
> whoami: asf-staging
> subdir: content/log4cxx
>
>
> Do you have a suggestion as to where I can find it now?
When branch `asf-staging` in `logging-site` changed from a `content`
directory to an `output` directory, all the staging websites went
down. Even if the change was reverted it still does not work,
Christian is working on this (since last week).
If you need to generate a staging website soon, change the `.asf.yaml` to:
staging:
profile: log4cxx
whoami: asf-staging
subdir: content/log4cxx
and the website should be available under
`https://logging-log4cxx.staged.apache.org`.
Piotr
Re: Staging website (was: [VOTE] Release Apache Log4j 2.21.0)
Posted by Stephen Webb <sw...@gmail.com>.
Hi Piotr,
The Log4cxx staging website URL
https://logging.staged.apache.org/log4cxx/latest_stable/usage-overview.html
now reports a 404.
The .asf.yaml contains:
staging:
profile: ~
whoami: asf-staging
subdir: content/log4cxx
Do you have a suggestion as to where I can find it now?
Thanks
Stephen Webb
On Sat, Oct 14, 2023 at 1:35 AM Piotr P. Karwasz <pi...@gmail.com>
wrote:
> Hi Christian,
>
> On Fri, 13 Oct 2023 at 13:46, Christian Grobmeier <gr...@apache.org>
> wrote:
> > Why is content not causing this issue?
> > For me both is possible, just trying to understand the best way.
>
> From what I understand, if a branch (in any repo) has a configuration:
>
> staging:
> whoami: name_of_the_branch
> profile: <profile>
> subdir: <subdir>
>
> INFRA copies the content of the branch into <subdir> of a directory
> served by Apache HTTPD. Our current merged site should look like:
>
> content/log4jphp/...Log4j PHP stuff...
> output/...Jekyll stuff...
>
> When this is done a script determines which folder is the document
> root for the server. Since we have both `content` and `output` the
> script probably fails (I don't see neither Log4PHP nor your Jekyll
> stuff).
>
> Piotr
>
Re: Staging website (was: [VOTE] Release Apache Log4j 2.21.0)
Posted by "Piotr P. Karwasz" <pi...@gmail.com>.
Hi Christian,
On Fri, 13 Oct 2023 at 13:46, Christian Grobmeier <gr...@apache.org> wrote:
> Why is content not causing this issue?
> For me both is possible, just trying to understand the best way.
From what I understand, if a branch (in any repo) has a configuration:
staging:
whoami: name_of_the_branch
profile: <profile>
subdir: <subdir>
INFRA copies the content of the branch into <subdir> of a directory
served by Apache HTTPD. Our current merged site should look like:
content/log4jphp/...Log4j PHP stuff...
output/...Jekyll stuff...
When this is done a script determines which folder is the document
root for the server. Since we have both `content` and `output` the
script probably fails (I don't see neither Log4PHP nor your Jekyll
stuff).
Piotr
Re: Staging website (was: [VOTE] Release Apache Log4j 2.21.0)
Posted by Christian Grobmeier <gr...@apache.org>.
Hi
On Mon, Oct 23, 2023, at 11:01, Volkan Yazıcı wrote:
> Staging website has been broken since October 10, that is, the last two
> weeks – please, correct me if I'm wrong. I support Christian's Jekyll
> migration and I know he is blocked by INFRA.
I have created the issue only 5 days ago, after Infra and I discussed a lot about bug fixing some infra code.
It was a weekend between, so I think we should be a bit more patient
> 1. Do we have a deadline to consider alternative courses of action?
I have no deadline, I would like to make this happen
> 2. Can we implement your Jekyll goal in a way (e.g., build+publish via
> CI) that we can roll back to the old working state yet make Jekyll work for
> you?
The bug fix works and we have /content folder as it was before.
There is a mess up on the server to which we don't have access to. Even when we rollback, there will not be a change, as we already have tzhe old setup
>
>
> On Fri, Oct 13, 2023 at 1:47 PM Christian Grobmeier <gr...@apache.org>
> wrote:
>
>>
>> >> [1] Christian's recent Jekyll experiment on the `asf-staging` branch
>> >> of `logging-site` repository confused the INFRA and it is acting
>> >> strangely. This will *NOT* be an issue when we push the website
>> >> changes to production, i.e., `asf-site` branch. Though we will try
>> >> fixing `asf-staging` anyway in the meantime.
>>
>> On Fri, Oct 13, 2023, at 13:28, Piotr P. Karwasz wrote:
>> > I think that the problem is that the `asf-staging` branch in
>> > `logging-site` has switched from a `content` folder to an `output`
>> > folder, while some of our 6 other site repos have a `content` folder.
>> > It is fixable, but INFRA offers us an infinite number of
>> > `logging-<foo>.staged.apache.org` domains and I think we should use
>> > it.
>>
>> According to this doc:
>>
>> https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INFRA&title=git+-+.asf.yaml+features#Git.asf.yamlfeatures-WebsitedeploymentserviceforGitrepositories
>>
>> We just have to give it a profile:
>>
>> staging:
>> profile: mystuff
>>
>> Would result in:
>>
>> logging-mystuff.staged.apache.org
>>
>> I can easily migrate to this.
>>
>> The folder "output" is the default with ASF infra, but it is possible to
>> replace it with content:
>>
>> jekyll:
>> whoami: jekyll
>> target: asf-staging
>> outputdir: content
>>
>> Why is content not causing this issue?
>> For me both is possible, just trying to understand the best way.
>>
>> Kind regards,
>> Christian
>>
Re: Staging website (was: [VOTE] Release Apache Log4j 2.21.0)
Posted by Volkan Yazıcı <vo...@yazi.ci>.
Staging website has been broken since October 10, that is, the last two
weeks – please, correct me if I'm wrong. I support Christian's Jekyll
migration and I know he is blocked by INFRA.
1. Do we have a deadline to consider alternative courses of action?
2. Can we implement your Jekyll goal in a way (e.g., build+publish via
CI) that we can roll back to the old working state yet make Jekyll work for
you?
On Fri, Oct 13, 2023 at 1:47 PM Christian Grobmeier <gr...@apache.org>
wrote:
>
> >> [1] Christian's recent Jekyll experiment on the `asf-staging` branch
> >> of `logging-site` repository confused the INFRA and it is acting
> >> strangely. This will *NOT* be an issue when we push the website
> >> changes to production, i.e., `asf-site` branch. Though we will try
> >> fixing `asf-staging` anyway in the meantime.
>
> On Fri, Oct 13, 2023, at 13:28, Piotr P. Karwasz wrote:
> > I think that the problem is that the `asf-staging` branch in
> > `logging-site` has switched from a `content` folder to an `output`
> > folder, while some of our 6 other site repos have a `content` folder.
> > It is fixable, but INFRA offers us an infinite number of
> > `logging-<foo>.staged.apache.org` domains and I think we should use
> > it.
>
> According to this doc:
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INFRA&title=git+-+.asf.yaml+features#Git.asf.yamlfeatures-WebsitedeploymentserviceforGitrepositories
>
> We just have to give it a profile:
>
> staging:
> profile: mystuff
>
> Would result in:
>
> logging-mystuff.staged.apache.org
>
> I can easily migrate to this.
>
> The folder "output" is the default with ASF infra, but it is possible to
> replace it with content:
>
> jekyll:
> whoami: jekyll
> target: asf-staging
> outputdir: content
>
> Why is content not causing this issue?
> For me both is possible, just trying to understand the best way.
>
> Kind regards,
> Christian
>