[
https://issues.apache.org/jira/browse/CASSANDRA-16128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17197683#comment-17197683
]
Michael Semb Wever commented on CASSANDRA-16128:
------------------------------------------------
bq. I'd swear there was a way to comment on diffs but I can't find it.
You can comment on the commit page:
https://github.com/apache/cassandra-builds/commit/6d53544bfc9c48179dc9c4a9157c610773f45a3c
bq. Also can I see some dev-branch test run with this patch?
At this point it has to be tested on a separate (local) jenkins installation.
(Which I've done.)
This is also *the testing* before any in-tree patch.
bq. Is 'git clean -xdff' a thing …
It was there in the script before :shrug:
I can change it to `git clean -xdf` if we're sure that's the correct command??
bq. Why in some places the dtests repro clone was removed?
The dtest clone happens inside the docker container. Cloning outside was
meaningless.
bq. So it's nice it will be now more handy but dtests SHA should be reachable
as well somewhere.
Yeah, let me chase this up and see how/where a "cassandra-dtest.head" can be
added…
Thanks for the feedback.
Yes.
> Jenkins: dsl for website build, logging repo SHAs, and using nightlies.a.o
> instead of archiving
> -----------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-16128
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16128
> Project: Cassandra
> Issue Type: Task
> Components: CI
> Reporter: Michael Semb Wever
> Assignee: Michael Semb Wever
> Priority: Normal
> Fix For: 4.0-beta
>
>
> Jenkins improvements
> 1. Add the cassandra-website job into cassandra_job_dsl.seed.groovy (so we
> don't lose it next time the Jenkins master is corrupted)
> 2. Print the SHAs of the different git repos used during the build process.
> Also store them in the .head files (so the pipeline can print them out too).
> 3. Instead of archiving artefacts, ssh them to
> https://nightlies.apache.org/cassandra/
> (Disk usage on agents is largely under control, but disk usage on master was
> the new problem. The suspicion here is the Cassandra-*-artifact's artefacts
> was the disk usage culprit, though we have to evidence to support it.)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
