[
https://issues.apache.org/jira/browse/CASSANDRA-16128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17198313#comment-17198313
]
Michael Semb Wever commented on CASSANDRA-16128:
------------------------------------------------
bq. Could you doublecheck in your local run in the dtests SHA is somewhere to
be seen? If it is some complicated thing bc of Docker maybe an echo of the SHA
even if it's outside them would be great.
Done.
Example, from a dtest build where SHAs from inside the dtest docker container…
{code}
dtest.sh (dtest 1/1024) cassandra: 68aca10 Adam Holmberg Tue Sep 15 15:56:39
2020 -0500 Remove flaky channelRead_Normal test that wasn't doing much
dtest.sh (dtest 1/1024) cassandra-dtest: 5db813c Yifan Cai Tue Sep 8 14:41:12
2020 -0700 When compaction gets interrupted, the exception should include the
compactionId
dtest.sh (dtest 1/1024) cassandra-builds: 13f0f39 Mick Semb Wever Fri Sep 18
12:33:12 2020 +0200 squash{code}
This output will appear in the dtest runs and in the pipeline run (for each
dtest split).
This required an addition to the patch, see the additional "squash" commit on
the existing {{mck/jenkins--print-git-shas-and-website-build}} branch.
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
