You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Gregor Zurowski <gr...@list.zurowski.org> on 2021/12/16 19:16:37 UTC
Camel Release | Website Build Issues
Hi Everyone:
I wanted to finish up the steps necessary to release Camel 3.14.0, but
I am running into issues with the website build:
```
YN0000: ERROR: "build:antora" exited with 1.
YN0000: The command failed for workspaces that are depended upon by
other workspaces; can't satisfy the dependency graph
```
See: https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/630/console
Any ideas why that's happening?
Thanks in advance
Gregor
Re: Camel Release | Website Build Issues
Posted by Zoran Regvart <zo...@regvart.com>.
Hi Andrea & Cameleers,
On Thu, Dec 16, 2021 at 8:36 PM Andrea Cosentino <an...@gmail.com> wrote:
> I would like to stress once again how much it's becoming non-deterministic
> to build the website.
I'm surprised that the build of the website is deemed
non-deterministic, and not the changes to the documentation. I've
found that the vast majority of website build failures were due to
changes to the documentation and not caused by the build process.
Last issue[1] that caused the website (not the build) to break was
when a change I made[2] broke loading CSS resources in the Antora part
of the website. I take full responsibility for that and I do wish that
I had caught that issue sooner, and I'm trying to find some time to
add more tests (e.g. visual regression tests[3]) to catch that.
Nonetheless, this was the first issue of this kind that I can remember
-- and I'll accept more feedback on this.
A lot of thought and effort has been and is done to increase the
robustness, ease maintainability and the overall quality of the
website, most of this work has been done by David and to a lesser
degree by me.
I think we have to remember, when the website build fails an issue has
been detected that could/will break the live website. We don't have a
staging process, all changes go directly live. I think we should make
every effort not to break the live website while allowing for frequent
website updates at the same time. Failing builds are a part of that.
The work David is proposing on partial builds will help with that by
allowing us to run quick local checks and in the future quick checks
on PRs. This will provide another, much earlier, barrier preventing
the website build failure. If folk want to help with that I'm sure
David is eager to see any help or comments on that.
> This is becoming everyday more complicated than it should be.
Can you elaborate on this? The website in itself is very complex, it
has two distinct ways of generating and rendering the resulting HTML
that we managed to marry together, we have ten git repositories and I
can't count how many branches that need to be in a correct state for
the documentation to build: i.e. contain proper versions, don't
contain syntax issues or broken links. I'd be happy to help and work
on any issue that anyone thinks is unnecessarily complicated.
> I think we need to focus on this. Because we shouldn't postpone a release
> for reason like this.
I agree, and I think a good way to help is to do reviews and suggest
improvements. The issue[1] I mentioned above was caused by a pull
request that I, being a large change, left in review for a significant
amount of time. I failed to check the preview properly, i.e. I checked
the Hugo bits that were causing problems, but failed to check a clean
Antora build that was done on the PR; so having a local build that was
not a clean build masked the issue for me.
> Building the website should be something like black magic and voodoo
> invocation. It should work much more easily.
To build the website one needs to follow the instructions[4], I
understand that for mainly Java developers this can seem like black
magic, I can only assure folk that it isn't. I'd be happy to work on
improving this, but I don't have a concrete issue to work on, please
provide examples of what is not clear and I can work on adding more
documentation or simplifications.
> I'll start another dev discussion about this argument.
+1
zoran
[1] https://github.com/apache/camel-website/issues/718
[2] https://github.com/apache/camel-website/pull/712
[3] https://github.com/apache/camel-website/issues/726
[4] https://github.com/apache/camel-website/#build-the-website-and-antora-theme
--
Zoran Regvart
Re: Camel Release | Website Build Issues
Posted by Gregor Zurowski <gr...@list.zurowski.org>.
Thanks for looking into this and fixing it.
Gregor
On Fri, Dec 17, 2021 at 5:19 AM David Jencks <da...@gmail.com> wrote:
>
> FWIW I’m working on a local build setup for (main) camel and discovered some gaps in @djencks/antora-source-watch exposed by the `components` component being distributed across `camel` and `camel-spring-boot`. Perhaps it will be ready tomorrow.
>
> I’d find it much easier to take complaints about the website build seriously if there was active consideration and discussion around my attempts to improve the situation. It’s been a couple days since my recent email on the subject with no responses that I can see. In particular future(1) would probably mean a local build of a subproject to check for errors could be done with no preparation other than having camel-website cloned appropriately, node installed, and take about a minute. It would be great to have a CI check as well, but this or even the local builds I’m working on now would be far better than the current situation where I think no one knows about the instructions https://camel.apache.org/manual/improving-the-documentation.html#_local_build_instructions <https://camel.apache.org/manual/improving-the-documentation.html#_local_build_instructions> and they are far too hard to follow.
>
> David Jencks
>
> > On Dec 16, 2021, at 2:46 PM, David Jencks <da...@gmail.com> wrote:
> >
> > I followed the link Gregor provided and see this:
> >
> > ➤ YN0000: [18:59:31.230] WARN (asciidoctor): skipping reference to missing attribute: headername
> > ➤ YN0000: file: docs/components/modules/ROOT/pages/salesforce-component.adoc
> > ➤ YN0000: source: https://github.com/apache/camel.git <https://github.com/apache/camel.git> (refname: main, start path: docs/components)
> > ➤ YN0000: [18:59:31.235] WARN (asciidoctor): skipping reference to missing attribute: id
> > ➤ YN0000: file: docs/components/modules/ROOT/pages/salesforce-component.adoc
> > ➤ YN0000: source: https://github.com/apache/camel.git <https://github.com/apache/camel.git> (refname: main, start path: docs/components)
> >
> >
> > I’m not sure how much more clear the build could possibly be about what is wrong???
> >
> > Back before Antora 3 these errors would still be present but not result in a failed build. You could look at the console output, but no one ever did.
> >
> > To fix:
> >
> > - the indicated file is a symlink, so follow it to it’s source components/camel-salesforce/camel-salesforce-component/src/main/docs/salesforce-component.adoc
> >
> > - look at git log to see who to blame….
> >
> > - find the newly added non-attributes {header name} and {id} and escape them
> >
> > ...
> >
> > https://github.com/apache/camel/pull/6550 <https://github.com/apache/camel/pull/6550>
> >
> > It’s not nearly easy enough to do a build to see if you’ve broken the site, but my POC makes it at least plausible.
> >
> > Browser plugins and the Intellij asciidoc plugin are not an adequate replacement for building the site.
> >
> > I suggest that no one change an adoc file without at least checking the antora build locally. Without local checks and PR builds we can expect the website to be always broken. Unfortunately I still don’t know of an easy-enough way to have PR builds.
> >
> > David Jencks
> >
> >> On Dec 16, 2021, at 11:38 AM, Andrea Cosentino <ancosen@gmail.com <ma...@gmail.com>> wrote:
> >>
> >> To be clear, I really appreciate the work done on docs and website, but
> >> it's really frustrating to get a different error each time you try to have
> >> a green ci build.
> >>
> >> Il gio 16 dic 2021, 20:36 Andrea Cosentino <ancosen@gmail.com <ma...@gmail.com>> ha scritto:
> >>
> >>> Thanks Gregor for spending your time on this.
> >>>
> >>> I would like to stress once again how much it's becoming non-deterministic
> >>> to build the website.
> >>>
> >>> This is becoming everyday more complicated than it should be.
> >>>
> >>> I think we need to focus on this. Because we shouldn't postpone a release
> >>> for reason like this.
> >>>
> >>> Building the website should be something like black magic and voodoo
> >>> invocation. It should work much more easily.
> >>>
> >>> I'll start another dev discussion about this argument.
> >>>
> >>> Il gio 16 dic 2021, 20:17 Gregor Zurowski <gregor@list.zurowski.org <ma...@list.zurowski.org>> ha
> >>> scritto:
> >>>
> >>>> Hi Everyone:
> >>>>
> >>>> I wanted to finish up the steps necessary to release Camel 3.14.0, but
> >>>> I am running into issues with the website build:
> >>>>
> >>>> ```
> >>>> YN0000: ERROR: "build:antora" exited with 1.
> >>>> YN0000: The command failed for workspaces that are depended upon by
> >>>> other workspaces; can't satisfy the dependency graph
> >>>> ```
> >>>> See:
> >>>> https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/630/console <https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/630/console>
> >>>>
> >>>> Any ideas why that's happening?
> >>>>
> >>>> Thanks in advance
> >>>> Gregor
> >>>>
> >>>
> >
>
Re: Camel Release | Website Build Issues
Posted by Andrea Cosentino <an...@gmail.com>.
Thanks for fixing it.
Il ven 17 dic 2021, 05:19 David Jencks <da...@gmail.com> ha
scritto:
> FWIW I’m working on a local build setup for (main) camel and discovered
> some gaps in @djencks/antora-source-watch exposed by the `components`
> component being distributed across `camel` and `camel-spring-boot`. Perhaps
> it will be ready tomorrow.
>
> I’d find it much easier to take complaints about the website build
> seriously if there was active consideration and discussion around my
> attempts to improve the situation. It’s been a couple days since my recent
> email on the subject with no responses that I can see. In particular
> future(1) would probably mean a local build of a subproject to check for
> errors could be done with no preparation other than having camel-website
> cloned appropriately, node installed, and take about a minute. It would be
> great to have a CI check as well, but this or even the local builds I’m
> working on now would be far better than the current situation where I think
> no one knows about the instructions
> https://camel.apache.org/manual/improving-the-documentation.html#_local_build_instructions
> <
> https://camel.apache.org/manual/improving-the-documentation.html#_local_build_instructions>
> and they are far too hard to follow.
>
> David Jencks
>
> > On Dec 16, 2021, at 2:46 PM, David Jencks <da...@gmail.com>
> wrote:
> >
> > I followed the link Gregor provided and see this:
> >
> > ➤ YN0000: [18:59:31.230] WARN (asciidoctor): skipping reference to
> missing attribute: headername
> > ➤ YN0000: file:
> docs/components/modules/ROOT/pages/salesforce-component.adoc
> > ➤ YN0000: source: https://github.com/apache/camel.git <
> https://github.com/apache/camel.git> (refname: main, start path:
> docs/components)
> > ➤ YN0000: [18:59:31.235] WARN (asciidoctor): skipping reference to
> missing attribute: id
> > ➤ YN0000: file:
> docs/components/modules/ROOT/pages/salesforce-component.adoc
> > ➤ YN0000: source: https://github.com/apache/camel.git <
> https://github.com/apache/camel.git> (refname: main, start path:
> docs/components)
> >
> >
> > I’m not sure how much more clear the build could possibly be about what
> is wrong???
> >
> > Back before Antora 3 these errors would still be present but not result
> in a failed build. You could look at the console output, but no one ever
> did.
> >
> > To fix:
> >
> > - the indicated file is a symlink, so follow it to it’s source
> components/camel-salesforce/camel-salesforce-component/src/main/docs/salesforce-component.adoc
> >
> > - look at git log to see who to blame….
> >
> > - find the newly added non-attributes {header name} and {id} and escape
> them
> >
> > ...
> >
> > https://github.com/apache/camel/pull/6550 <
> https://github.com/apache/camel/pull/6550>
> >
> > It’s not nearly easy enough to do a build to see if you’ve broken the
> site, but my POC makes it at least plausible.
> >
> > Browser plugins and the Intellij asciidoc plugin are not an adequate
> replacement for building the site.
> >
> > I suggest that no one change an adoc file without at least checking the
> antora build locally. Without local checks and PR builds we can expect the
> website to be always broken. Unfortunately I still don’t know of an
> easy-enough way to have PR builds.
> >
> > David Jencks
> >
> >> On Dec 16, 2021, at 11:38 AM, Andrea Cosentino <ancosen@gmail.com
> <ma...@gmail.com>> wrote:
> >>
> >> To be clear, I really appreciate the work done on docs and website, but
> >> it's really frustrating to get a different error each time you try to
> have
> >> a green ci build.
> >>
> >> Il gio 16 dic 2021, 20:36 Andrea Cosentino <ancosen@gmail.com <mailto:
> ancosen@gmail.com>> ha scritto:
> >>
> >>> Thanks Gregor for spending your time on this.
> >>>
> >>> I would like to stress once again how much it's becoming
> non-deterministic
> >>> to build the website.
> >>>
> >>> This is becoming everyday more complicated than it should be.
> >>>
> >>> I think we need to focus on this. Because we shouldn't postpone a
> release
> >>> for reason like this.
> >>>
> >>> Building the website should be something like black magic and voodoo
> >>> invocation. It should work much more easily.
> >>>
> >>> I'll start another dev discussion about this argument.
> >>>
> >>> Il gio 16 dic 2021, 20:17 Gregor Zurowski <gregor@list.zurowski.org
> <ma...@list.zurowski.org>> ha
> >>> scritto:
> >>>
> >>>> Hi Everyone:
> >>>>
> >>>> I wanted to finish up the steps necessary to release Camel 3.14.0, but
> >>>> I am running into issues with the website build:
> >>>>
> >>>> ```
> >>>> YN0000: ERROR: "build:antora" exited with 1.
> >>>> YN0000: The command failed for workspaces that are depended upon by
> >>>> other workspaces; can't satisfy the dependency graph
> >>>> ```
> >>>> See:
> >>>>
> https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/630/console
> <
> https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/630/console
> >
> >>>>
> >>>> Any ideas why that's happening?
> >>>>
> >>>> Thanks in advance
> >>>> Gregor
> >>>>
> >>>
> >
>
>
Re: Camel Release | Website Build Issues
Posted by David Jencks <da...@gmail.com>.
FWIW I’m working on a local build setup for (main) camel and discovered some gaps in @djencks/antora-source-watch exposed by the `components` component being distributed across `camel` and `camel-spring-boot`. Perhaps it will be ready tomorrow.
I’d find it much easier to take complaints about the website build seriously if there was active consideration and discussion around my attempts to improve the situation. It’s been a couple days since my recent email on the subject with no responses that I can see. In particular future(1) would probably mean a local build of a subproject to check for errors could be done with no preparation other than having camel-website cloned appropriately, node installed, and take about a minute. It would be great to have a CI check as well, but this or even the local builds I’m working on now would be far better than the current situation where I think no one knows about the instructions https://camel.apache.org/manual/improving-the-documentation.html#_local_build_instructions <https://camel.apache.org/manual/improving-the-documentation.html#_local_build_instructions> and they are far too hard to follow.
David Jencks
> On Dec 16, 2021, at 2:46 PM, David Jencks <da...@gmail.com> wrote:
>
> I followed the link Gregor provided and see this:
>
> ➤ YN0000: [18:59:31.230] WARN (asciidoctor): skipping reference to missing attribute: headername
> ➤ YN0000: file: docs/components/modules/ROOT/pages/salesforce-component.adoc
> ➤ YN0000: source: https://github.com/apache/camel.git <https://github.com/apache/camel.git> (refname: main, start path: docs/components)
> ➤ YN0000: [18:59:31.235] WARN (asciidoctor): skipping reference to missing attribute: id
> ➤ YN0000: file: docs/components/modules/ROOT/pages/salesforce-component.adoc
> ➤ YN0000: source: https://github.com/apache/camel.git <https://github.com/apache/camel.git> (refname: main, start path: docs/components)
>
>
> I’m not sure how much more clear the build could possibly be about what is wrong???
>
> Back before Antora 3 these errors would still be present but not result in a failed build. You could look at the console output, but no one ever did.
>
> To fix:
>
> - the indicated file is a symlink, so follow it to it’s source components/camel-salesforce/camel-salesforce-component/src/main/docs/salesforce-component.adoc
>
> - look at git log to see who to blame….
>
> - find the newly added non-attributes {header name} and {id} and escape them
>
> ...
>
> https://github.com/apache/camel/pull/6550 <https://github.com/apache/camel/pull/6550>
>
> It’s not nearly easy enough to do a build to see if you’ve broken the site, but my POC makes it at least plausible.
>
> Browser plugins and the Intellij asciidoc plugin are not an adequate replacement for building the site.
>
> I suggest that no one change an adoc file without at least checking the antora build locally. Without local checks and PR builds we can expect the website to be always broken. Unfortunately I still don’t know of an easy-enough way to have PR builds.
>
> David Jencks
>
>> On Dec 16, 2021, at 11:38 AM, Andrea Cosentino <ancosen@gmail.com <ma...@gmail.com>> wrote:
>>
>> To be clear, I really appreciate the work done on docs and website, but
>> it's really frustrating to get a different error each time you try to have
>> a green ci build.
>>
>> Il gio 16 dic 2021, 20:36 Andrea Cosentino <ancosen@gmail.com <ma...@gmail.com>> ha scritto:
>>
>>> Thanks Gregor for spending your time on this.
>>>
>>> I would like to stress once again how much it's becoming non-deterministic
>>> to build the website.
>>>
>>> This is becoming everyday more complicated than it should be.
>>>
>>> I think we need to focus on this. Because we shouldn't postpone a release
>>> for reason like this.
>>>
>>> Building the website should be something like black magic and voodoo
>>> invocation. It should work much more easily.
>>>
>>> I'll start another dev discussion about this argument.
>>>
>>> Il gio 16 dic 2021, 20:17 Gregor Zurowski <gregor@list.zurowski.org <ma...@list.zurowski.org>> ha
>>> scritto:
>>>
>>>> Hi Everyone:
>>>>
>>>> I wanted to finish up the steps necessary to release Camel 3.14.0, but
>>>> I am running into issues with the website build:
>>>>
>>>> ```
>>>> YN0000: ERROR: "build:antora" exited with 1.
>>>> YN0000: The command failed for workspaces that are depended upon by
>>>> other workspaces; can't satisfy the dependency graph
>>>> ```
>>>> See:
>>>> https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/630/console <https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/630/console>
>>>>
>>>> Any ideas why that's happening?
>>>>
>>>> Thanks in advance
>>>> Gregor
>>>>
>>>
>
Re: Camel Release | Website Build Issues
Posted by David Jencks <da...@gmail.com>.
I followed the link Gregor provided and see this:
➤ YN0000: [18:59:31.230] WARN (asciidoctor): skipping reference to missing attribute: headername
➤ YN0000: file: docs/components/modules/ROOT/pages/salesforce-component.adoc
➤ YN0000: source: https://github.com/apache/camel.git <https://github.com/apache/camel.git> (refname: main, start path: docs/components)
➤ YN0000: [18:59:31.235] WARN (asciidoctor): skipping reference to missing attribute: id
➤ YN0000: file: docs/components/modules/ROOT/pages/salesforce-component.adoc
➤ YN0000: source: https://github.com/apache/camel.git <https://github.com/apache/camel.git> (refname: main, start path: docs/components)
I’m not sure how much more clear the build could possibly be about what is wrong???
Back before Antora 3 these errors would still be present but not result in a failed build. You could look at the console output, but no one ever did.
To fix:
- the indicated file is a symlink, so follow it to it’s source components/camel-salesforce/camel-salesforce-component/src/main/docs/salesforce-component.adoc
- look at git log to see who to blame….
- find the newly added non-attributes {header name} and {id} and escape them
...
https://github.com/apache/camel/pull/6550 <https://github.com/apache/camel/pull/6550>
It’s not nearly easy enough to do a build to see if you’ve broken the site, but my POC makes it at least plausible.
Browser plugins and the Intellij asciidoc plugin are not an adequate replacement for building the site.
I suggest that no one change an adoc file without at least checking the antora build locally. Without local checks and PR builds we can expect the website to be always broken. Unfortunately I still don’t know of an easy-enough way to have PR builds.
David Jencks
> On Dec 16, 2021, at 11:38 AM, Andrea Cosentino <an...@gmail.com> wrote:
>
> To be clear, I really appreciate the work done on docs and website, but
> it's really frustrating to get a different error each time you try to have
> a green ci build.
>
> Il gio 16 dic 2021, 20:36 Andrea Cosentino <an...@gmail.com> ha scritto:
>
>> Thanks Gregor for spending your time on this.
>>
>> I would like to stress once again how much it's becoming non-deterministic
>> to build the website.
>>
>> This is becoming everyday more complicated than it should be.
>>
>> I think we need to focus on this. Because we shouldn't postpone a release
>> for reason like this.
>>
>> Building the website should be something like black magic and voodoo
>> invocation. It should work much more easily.
>>
>> I'll start another dev discussion about this argument.
>>
>> Il gio 16 dic 2021, 20:17 Gregor Zurowski <gr...@list.zurowski.org> ha
>> scritto:
>>
>>> Hi Everyone:
>>>
>>> I wanted to finish up the steps necessary to release Camel 3.14.0, but
>>> I am running into issues with the website build:
>>>
>>> ```
>>> YN0000: ERROR: "build:antora" exited with 1.
>>> YN0000: The command failed for workspaces that are depended upon by
>>> other workspaces; can't satisfy the dependency graph
>>> ```
>>> See:
>>> https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/630/console
>>>
>>> Any ideas why that's happening?
>>>
>>> Thanks in advance
>>> Gregor
>>>
>>
Re: Camel Release | Website Build Issues
Posted by Andrea Cosentino <an...@gmail.com>.
To be clear, I really appreciate the work done on docs and website, but
it's really frustrating to get a different error each time you try to have
a green ci build.
Il gio 16 dic 2021, 20:36 Andrea Cosentino <an...@gmail.com> ha scritto:
> Thanks Gregor for spending your time on this.
>
> I would like to stress once again how much it's becoming non-deterministic
> to build the website.
>
> This is becoming everyday more complicated than it should be.
>
> I think we need to focus on this. Because we shouldn't postpone a release
> for reason like this.
>
> Building the website should be something like black magic and voodoo
> invocation. It should work much more easily.
>
> I'll start another dev discussion about this argument.
>
> Il gio 16 dic 2021, 20:17 Gregor Zurowski <gr...@list.zurowski.org> ha
> scritto:
>
>> Hi Everyone:
>>
>> I wanted to finish up the steps necessary to release Camel 3.14.0, but
>> I am running into issues with the website build:
>>
>> ```
>> YN0000: ERROR: "build:antora" exited with 1.
>> YN0000: The command failed for workspaces that are depended upon by
>> other workspaces; can't satisfy the dependency graph
>> ```
>> See:
>> https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/630/console
>>
>> Any ideas why that's happening?
>>
>> Thanks in advance
>> Gregor
>>
>
Re: Camel Release | Website Build Issues
Posted by Andrea Cosentino <an...@gmail.com>.
Thanks Gregor for spending your time on this.
I would like to stress once again how much it's becoming non-deterministic
to build the website.
This is becoming everyday more complicated than it should be.
I think we need to focus on this. Because we shouldn't postpone a release
for reason like this.
Building the website should be something like black magic and voodoo
invocation. It should work much more easily.
I'll start another dev discussion about this argument.
Il gio 16 dic 2021, 20:17 Gregor Zurowski <gr...@list.zurowski.org> ha
scritto:
> Hi Everyone:
>
> I wanted to finish up the steps necessary to release Camel 3.14.0, but
> I am running into issues with the website build:
>
> ```
> YN0000: ERROR: "build:antora" exited with 1.
> YN0000: The command failed for workspaces that are depended upon by
> other workspaces; can't satisfy the dependency graph
> ```
> See:
> https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/630/console
>
> Any ideas why that's happening?
>
> Thanks in advance
> Gregor
>
Re: Camel Release | Website Build Issues
Posted by Zoran Regvart <zo...@regvart.com>.
Hi Cameleers,
Everything looks good now. The issue was that I've forgotten to remove
`prerelease: true`[1] for Camel Karaf 3.14.x.
This is already documented[2], so my bad for adjusting the versions too hastily.
zoran
[1] https://github.com/apache/camel-karaf/commit/734dcba22798e35918762fee7212efbba59c7326
[2] https://camel.apache.org/manual/release-guide-website.html#_changes_to_the_new_branches_e_g_camel_3_13_x_in_affected_content_repositories
On Fri, Dec 17, 2021 at 12:54 PM Zoran Regvart <zo...@regvart.com> wrote:
>
> Hi Cameleers,
> the website built successfully, and 3.14.0
> announcement/downloads/documentation can be now seen online. I'm
> looking into the Camel Karaf redirect issue.
>
> zoran
>
> On Fri, Dec 17, 2021 at 12:27 PM Zoran Regvart <zo...@regvart.com> wrote:
> >
> > Hi Cameleers,
> > the second rebuild also failed with the same redirect issue[1]. I
> > decided to retry and skip checks to get the website published while I
> > investigate. I expect the next build to succeed[2].
> >
> > zoran
> >
> > [1] https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/637/
> > [2] https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/638/
> >
> > On Fri, Dec 17, 2021 at 10:59 AM Zoran Regvart <zo...@regvart.com> wrote:
> > >
> > > Hi Cameleers,
> > > the build[1] failed as the redirects are still pointing to the older
> > > 3.13.x version for Karaf, I think this is because I triggered the
> > > build before I pushed the last changes to the camel-karaf 3.14.x
> > > branch, I'll retry and investigate if it fails again,
> > >
> > > zoran
> > >
> > > [1] https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/636/console
> > >
> > > On Fri, Dec 17, 2021 at 10:21 AM Zoran Regvart <zo...@regvart.com> wrote:
> > > >
> > > > Hi Cameleers,
> > > > I've noticed that we didn't update the versions in the Antora
> > > > descriptors. Quick reminder that David created a website/documentation
> > > > release guide here:
> > > >
> > > > https://camel.apache.org/manual/release-guide-website.html
> > > >
> > > > I've went through it and made those changes with one caveat, when
> > > > Camel Quarkus based on Camel 3.14.0 is released we need to also update
> > > > the `cq-version` attribute here:
> > > >
> > > > https://github.com/apache/camel/blob/camel-3.14.x/docs/components/antora.yml#L38
> > > >
> > > > zoran
> > > >
> > > > On Thu, Dec 16, 2021 at 8:17 PM Gregor Zurowski
> > > > <gr...@list.zurowski.org> wrote:
> > > > >
> > > > > Hi Everyone:
> > > > >
> > > > > I wanted to finish up the steps necessary to release Camel 3.14.0, but
> > > > > I am running into issues with the website build:
> > > > >
> > > > > ```
> > > > > YN0000: ERROR: "build:antora" exited with 1.
> > > > > YN0000: The command failed for workspaces that are depended upon by
> > > > > other workspaces; can't satisfy the dependency graph
> > > > > ```
> > > > > See: https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/630/console
> > > > >
> > > > > Any ideas why that's happening?
> > > > >
> > > > > Thanks in advance
> > > > > Gregor
> > > >
> > > >
> > > >
> > > > --
> > > > Zoran Regvart
> > >
> > >
> > >
> > > --
> > > Zoran Regvart
> >
> >
> >
> > --
> > Zoran Regvart
>
>
>
> --
> Zoran Regvart
--
Zoran Regvart
Re: Camel Release | Website Build Issues
Posted by Zoran Regvart <zo...@regvart.com>.
Hi Cameleers,
the website built successfully, and 3.14.0
announcement/downloads/documentation can be now seen online. I'm
looking into the Camel Karaf redirect issue.
zoran
On Fri, Dec 17, 2021 at 12:27 PM Zoran Regvart <zo...@regvart.com> wrote:
>
> Hi Cameleers,
> the second rebuild also failed with the same redirect issue[1]. I
> decided to retry and skip checks to get the website published while I
> investigate. I expect the next build to succeed[2].
>
> zoran
>
> [1] https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/637/
> [2] https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/638/
>
> On Fri, Dec 17, 2021 at 10:59 AM Zoran Regvart <zo...@regvart.com> wrote:
> >
> > Hi Cameleers,
> > the build[1] failed as the redirects are still pointing to the older
> > 3.13.x version for Karaf, I think this is because I triggered the
> > build before I pushed the last changes to the camel-karaf 3.14.x
> > branch, I'll retry and investigate if it fails again,
> >
> > zoran
> >
> > [1] https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/636/console
> >
> > On Fri, Dec 17, 2021 at 10:21 AM Zoran Regvart <zo...@regvart.com> wrote:
> > >
> > > Hi Cameleers,
> > > I've noticed that we didn't update the versions in the Antora
> > > descriptors. Quick reminder that David created a website/documentation
> > > release guide here:
> > >
> > > https://camel.apache.org/manual/release-guide-website.html
> > >
> > > I've went through it and made those changes with one caveat, when
> > > Camel Quarkus based on Camel 3.14.0 is released we need to also update
> > > the `cq-version` attribute here:
> > >
> > > https://github.com/apache/camel/blob/camel-3.14.x/docs/components/antora.yml#L38
> > >
> > > zoran
> > >
> > > On Thu, Dec 16, 2021 at 8:17 PM Gregor Zurowski
> > > <gr...@list.zurowski.org> wrote:
> > > >
> > > > Hi Everyone:
> > > >
> > > > I wanted to finish up the steps necessary to release Camel 3.14.0, but
> > > > I am running into issues with the website build:
> > > >
> > > > ```
> > > > YN0000: ERROR: "build:antora" exited with 1.
> > > > YN0000: The command failed for workspaces that are depended upon by
> > > > other workspaces; can't satisfy the dependency graph
> > > > ```
> > > > See: https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/630/console
> > > >
> > > > Any ideas why that's happening?
> > > >
> > > > Thanks in advance
> > > > Gregor
> > >
> > >
> > >
> > > --
> > > Zoran Regvart
> >
> >
> >
> > --
> > Zoran Regvart
>
>
>
> --
> Zoran Regvart
--
Zoran Regvart
Re: Camel Release | Website Build Issues
Posted by Zoran Regvart <zo...@regvart.com>.
Hi Cameleers,
the second rebuild also failed with the same redirect issue[1]. I
decided to retry and skip checks to get the website published while I
investigate. I expect the next build to succeed[2].
zoran
[1] https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/637/
[2] https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/638/
On Fri, Dec 17, 2021 at 10:59 AM Zoran Regvart <zo...@regvart.com> wrote:
>
> Hi Cameleers,
> the build[1] failed as the redirects are still pointing to the older
> 3.13.x version for Karaf, I think this is because I triggered the
> build before I pushed the last changes to the camel-karaf 3.14.x
> branch, I'll retry and investigate if it fails again,
>
> zoran
>
> [1] https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/636/console
>
> On Fri, Dec 17, 2021 at 10:21 AM Zoran Regvart <zo...@regvart.com> wrote:
> >
> > Hi Cameleers,
> > I've noticed that we didn't update the versions in the Antora
> > descriptors. Quick reminder that David created a website/documentation
> > release guide here:
> >
> > https://camel.apache.org/manual/release-guide-website.html
> >
> > I've went through it and made those changes with one caveat, when
> > Camel Quarkus based on Camel 3.14.0 is released we need to also update
> > the `cq-version` attribute here:
> >
> > https://github.com/apache/camel/blob/camel-3.14.x/docs/components/antora.yml#L38
> >
> > zoran
> >
> > On Thu, Dec 16, 2021 at 8:17 PM Gregor Zurowski
> > <gr...@list.zurowski.org> wrote:
> > >
> > > Hi Everyone:
> > >
> > > I wanted to finish up the steps necessary to release Camel 3.14.0, but
> > > I am running into issues with the website build:
> > >
> > > ```
> > > YN0000: ERROR: "build:antora" exited with 1.
> > > YN0000: The command failed for workspaces that are depended upon by
> > > other workspaces; can't satisfy the dependency graph
> > > ```
> > > See: https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/630/console
> > >
> > > Any ideas why that's happening?
> > >
> > > Thanks in advance
> > > Gregor
> >
> >
> >
> > --
> > Zoran Regvart
>
>
>
> --
> Zoran Regvart
--
Zoran Regvart
Re: Camel Release | Website Build Issues
Posted by Zoran Regvart <zo...@regvart.com>.
Hi Cameleers,
the build[1] failed as the redirects are still pointing to the older
3.13.x version for Karaf, I think this is because I triggered the
build before I pushed the last changes to the camel-karaf 3.14.x
branch, I'll retry and investigate if it fails again,
zoran
[1] https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/636/console
On Fri, Dec 17, 2021 at 10:21 AM Zoran Regvart <zo...@regvart.com> wrote:
>
> Hi Cameleers,
> I've noticed that we didn't update the versions in the Antora
> descriptors. Quick reminder that David created a website/documentation
> release guide here:
>
> https://camel.apache.org/manual/release-guide-website.html
>
> I've went through it and made those changes with one caveat, when
> Camel Quarkus based on Camel 3.14.0 is released we need to also update
> the `cq-version` attribute here:
>
> https://github.com/apache/camel/blob/camel-3.14.x/docs/components/antora.yml#L38
>
> zoran
>
> On Thu, Dec 16, 2021 at 8:17 PM Gregor Zurowski
> <gr...@list.zurowski.org> wrote:
> >
> > Hi Everyone:
> >
> > I wanted to finish up the steps necessary to release Camel 3.14.0, but
> > I am running into issues with the website build:
> >
> > ```
> > YN0000: ERROR: "build:antora" exited with 1.
> > YN0000: The command failed for workspaces that are depended upon by
> > other workspaces; can't satisfy the dependency graph
> > ```
> > See: https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/630/console
> >
> > Any ideas why that's happening?
> >
> > Thanks in advance
> > Gregor
>
>
>
> --
> Zoran Regvart
--
Zoran Regvart
Re: Camel Release | Website Build Issues
Posted by Zoran Regvart <zo...@regvart.com>.
Hi Cameleers,
I've noticed that we didn't update the versions in the Antora
descriptors. Quick reminder that David created a website/documentation
release guide here:
https://camel.apache.org/manual/release-guide-website.html
I've went through it and made those changes with one caveat, when
Camel Quarkus based on Camel 3.14.0 is released we need to also update
the `cq-version` attribute here:
https://github.com/apache/camel/blob/camel-3.14.x/docs/components/antora.yml#L38
zoran
On Thu, Dec 16, 2021 at 8:17 PM Gregor Zurowski
<gr...@list.zurowski.org> wrote:
>
> Hi Everyone:
>
> I wanted to finish up the steps necessary to release Camel 3.14.0, but
> I am running into issues with the website build:
>
> ```
> YN0000: ERROR: "build:antora" exited with 1.
> YN0000: The command failed for workspaces that are depended upon by
> other workspaces; can't satisfy the dependency graph
> ```
> See: https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/630/console
>
> Any ideas why that's happening?
>
> Thanks in advance
> Gregor
--
Zoran Regvart