Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Let contributors know why tests are failing #9916

Open
pdurbin opened this issue Sep 14, 2023 · 1 comment
Open

Let contributors know why tests are failing #9916

pdurbin opened this issue Sep 14, 2023 · 1 comment
Labels
Component: Containers Anything related to cloudy Dataverse, shipped in containers. Feature: None No user-facing feature in particular Type: Suggestion an idea User Role: Hackathon Participant Core developers, frequent contributors, drive-by contributors, etc.

Comments

@pdurbin
Copy link
Member

pdurbin commented Sep 14, 2023 •
edited
Loading

Currently we show them a red x with no details of which tests failed.

This is because https://jenkins.dataverse.org is behind a firewall.

Probably we will try to build something public using GitHub Actions. Unfortunately, out of the box, GitHub Actions doesn't show details of failures to the public. (See https://github.com/gdcc/api-test-runner/actions/runs/6126277581 for example.) The hope is to publish a report somehow, as discussed at https://dataverse.zulipchat.com/#narrow/stream/379673-dev/topic/github.20test.20reports/near/385654854 . See progress by @poikilotherm at https://github.com/IQSS/dataverse/compare/9916-action-reports
@poikilotherm poikilotherm added the Component: Containers Anything related to cloudy Dataverse, shipped in containers. label Sep 14, 2023
@pdurbin pdurbin changed the title Let contributors know why test are failing Let contributors know why tests are failing Sep 18, 2023
poikilotherm added a commit that referenced this issue Sep 18, 2023
@poikilotherm
ci(test): upload test reports as artifacts #9916
ebe8914 
To be processed by another job within context of repo to allow write access (otherwise no summary can be added)
poikilotherm added a commit that referenced this issue Sep 18, 2023
@poikilotherm
ci(test): run report from separate workflow in repo context for write…
fd0f70c 
… access #9916
@pdurbin
Copy link
Member Author

pdurbin commented Oct 7, 2023

This is because https://jenkins.dataverse.org is behind a firewall.

The other day @donsizemore mentioned that when this server moves there's a chance we can open it up.

@pdurbin pdurbin added Type: Suggestion an idea User Role: Hackathon Participant Core developers, frequent contributors, drive-by contributors, etc. Feature: None No user-facing feature in particular labels Oct 8, 2023
@pdurbin pdurbin mentioned this issue Oct 19, 2023
Merged
@pdurbin pdurbin mentioned this issue Nov 28, 2023
Closed
@pdurbin pdurbin mentioned this issue Mar 27, 2024
Merged
@pdurbin pdurbin mentioned this issue Apr 26, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Component: Containers Anything related to cloudy Dataverse, shipped in containers. Feature: None No user-facing feature in particular Type: Suggestion an idea User Role: Hackathon Participant Core developers, frequent contributors, drive-by contributors, etc.
Projects
IQSS Dataverse Project
Status: No status
Recherche Data Gouv
Status: ⚠️ Needed/Important
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pdurbin @poikilotherm