You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "jprinet (via GitHub)" <gi...@apache.org> on 2026/10/12 15:03:03 UTC
[D] Publish CI Build Scans to develocity.apache.org [superset]
GitHub user jprinet created a discussion: Publish CI Build Scans to develocity.apache.org
Superset's CI builds with Python, npm and Docker. ASF runs a Develocity instance at https://develocity.apache.org, already used by other Apache projects, that can record each CI run as a Build Scan: test results with history (flaky and slow tests), console logs, failure grouping and Docker layer timings.
Proposal: add the `gradle/develocity-actions` setup actions to the CI workflows that run pytest, npm and Docker image builds. The integration is CI-only, adds no dependency to the project, and every step is skipped when the `DEVELOCITY_ACCESS_KEY` secret isn't set, so fork PRs and local development are unaffected.
Prerequisites: the actions on the ASF allow list (apache/infrastructure-actions#1383), and an access key from ASF Infra.
cc @rusackas
GitHub link: https://github.com/apache/superset/discussions/45216
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Publish CI Build Scans to develocity.apache.org [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
GitHub user rusackas added a comment to the discussion: Publish CI Build Scans to develocity.apache.org
Thanks for putting this together. Skipping every step when the secret isn't set is the part I care most about, so fork PRs and local dev stay untouched. The access key from Infra is the piece outside our hands, so that and the allow list PR seem like the gating items. I'll be taking a closer look at the PR and following up as time allows. Really appreciate your help/interest/availability here :)
GitHub link: https://github.com/apache/superset/discussions/45216#discussioncomment-19110534
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Publish CI Build Scans to develocity.apache.org [superset]
Posted by "jprinet (via GitHub)" <gi...@apache.org>.
GitHub user jprinet added a comment to the discussion: Publish CI Build Scans to develocity.apache.org
Implementation: #45217
GitHub link: https://github.com/apache/superset/discussions/45216#discussioncomment-18883032
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Publish CI Build Scans to develocity.apache.org [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
GitHub user rusackas edited a comment on the discussion: Publish CI Build Scans to develocity.apache.org
Thanks for putting this together. Skipping every step when the secret isn't set is the part I care most about, so fork PRs and local dev stay untouched. The access key from Infra is the piece outside our hands, so that and the allow list PR seem like the gating items. I'll be taking a closer look at the PR(s) and following up as time allows to close the loop here if other PMCs are into the idea too. Really appreciate your help/interest/availability here :)
GitHub link: https://github.com/apache/superset/discussions/45216#discussioncomment-19110534
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org