[
https://issues.apache.org/jira/browse/CASSANDRA-16765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17393780#comment-17393780
]
Michael Semb Wever edited comment on CASSANDRA-16765 at 8/5/21, 10:17 AM:
--------------------------------------------------------------------------
Patch at
https://github.com/apache/cassandra-builds/compare/trunk...thelastpickle:mck/16765
[~Anthony Grasso], the patch raises a number of questions…
- the branches we can build in-tree docs becomes hardcoded in the jenkins
config, both in what to
[build|https://github.com/apache/cassandra-builds/compare/trunk...thelastpickle:mck/16765#diff-1f760d89dfb81ea05a11d862007a4e4e586b38aac7ae87f62c5b2e86571809c0R1268]]
and in what changes to
[listen|https://github.com/apache/cassandra-builds/compare/trunk...thelastpickle:mck/16765#diff-1f760d89dfb81ea05a11d862007a4e4e586b38aac7ae87f62c5b2e86571809c0R1256]
for to trigger off a build,
- no released versions are listed, i.e. git tags. how will they be introduced
into [this
line|https://github.com/apache/cassandra-builds/compare/trunk...thelastpickle:mck/16765#diff-1f760d89dfb81ea05a11d862007a4e4e586b38aac7ae87f62c5b2e86571809c0R1268]
- the notions of {{stable}} and {{latest}} docs are hardcoded by jenkins
[here|https://github.com/apache/cassandra-builds/compare/trunk...thelastpickle:mck/16765#diff-1f760d89dfb81ea05a11d862007a4e4e586b38aac7ae87f62c5b2e86571809c0R1271-R1272],
is this something that can be put into antora?
was (Author: michaelsembwever):
Patch at
https://github.com/apache/cassandra-builds/compare/trunk...thelastpickle:mck/16765
[~Anthony Grasso], the patch raises a number of questions…
- the branches we can build in-tree docs becomes hardcoded in the jenkins
config, both in what to
[build||https://github.com/apache/cassandra-builds/compare/trunk...thelastpickle:mck/16765#diff-1f760d89dfb81ea05a11d862007a4e4e586b38aac7ae87f62c5b2e86571809c0R1268]]
and in what changes to
[listen|https://github.com/apache/cassandra-builds/compare/trunk...thelastpickle:mck/16765#diff-1f760d89dfb81ea05a11d862007a4e4e586b38aac7ae87f62c5b2e86571809c0R1256]
for to trigger off a build,
- no released versions are listed, i.e. git tags. how will they be introduced
into [this
line|https://github.com/apache/cassandra-builds/compare/trunk...thelastpickle:mck/16765#diff-1f760d89dfb81ea05a11d862007a4e4e586b38aac7ae87f62c5b2e86571809c0R1268]
- the notions of {{stable}} and {{latest}} docs are hardcoded by jenkins
[here|https://github.com/apache/cassandra-builds/compare/trunk...thelastpickle:mck/16765#diff-1f760d89dfb81ea05a11d862007a4e4e586b38aac7ae87f62c5b2e86571809c0R1271-R1272],
is this something that can be put into antora?
> Update Cassandra build CI script for new website
> ------------------------------------------------
>
> Key: CASSANDRA-16765
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16765
> Project: Cassandra
> Issue Type: Task
> Components: Build, CI, Documentation/Website
> Reporter: Anthony Grasso
> Assignee: Michael Semb Wever
> Priority: Normal
>
> Update the apache/cassandra-build repository has [.groovy job
> script|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy]
> to use the new tooling to build the website.
> The apache/cassandra-build repository has [.groovy job
> script|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy].
> It [builds and deploys the
> website|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L1255-L1268]
> to cassandra-website staging when the cassandra-website is updated.
> We need to change the commands in the .groovy script to at least rebuild the
> site when a change happens in the cassandra-website repository.
> It would be also good to build the docs when a change happens to doc/source
> directory in the cassandra repository.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
