[ 
https://issues.apache.org/jira/browse/CASSANDRA-16128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199475#comment-17199475
 ] 

Michael Semb Wever commented on CASSANDRA-16128:
------------------------------------------------

Example build:
- https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/26/
- 
https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/26/console


Related nightlies.a.o files:
- https://nightlies.apache.org/cassandra/Cassandra-devbranch/26/
- 
https://nightlies.apache.org/cassandra/Cassandra-devbranch-artifacts/jdk=JDK%201.8%20(latest),label=cassandra/24/build/
- 
https://nightlies.apache.org/cassandra/Cassandra-devbranch-artifacts/jdk=JDK%2011%20(latest),label=cassandra/24/build/
- 
https://nightlies.apache.org/cassandra/Cassandra-devbranch-test/19/build/test/logs/
- https://nightlies.apache.org/cassandra/Cassandra-devbranch-dtest/

Things to fix:
 - website dsl doesn't work
 - remove javadoc upload to nightlies for devbranch
- fix `cat *.head` 

> 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

Reply via email to