Overview of the Suggestion
Jenkins is old. Jenkins can croak any day. Jenkins can also be turned off without a lot of prior notice. And Jenkins doesn't show everyone why tests are failing or how. Jenkins also doesn't test containers. So we want to be ahead of this happening, and have failsafes in place through GitHub Action Workflows. So @donsizemore on behalf of the Research Data Management Core from the University of North Carolina at Chapel Hill proposes this solution of running the api tests in the integration-tests.txt file in GitHub Actions just like how unit tests and real integration tests are already tested in maven_unit_test.yml
What kind of user is the suggestion intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Every engineer who works with Dataverse source code
What inspired this idea?
@donsizemore, @pdurbin, and @poikilotherm encouraged me to work on this workflow!
What existing behavior do you want changed?
N/A
Any brand new behavior do you want to add to Dataverse?
N/A
Any open or closed issues related to this suggestion?
Yes, this will also address #9916 and any other issues that y'all think can be addressed
Are you thinking about creating a pull request for this issue?
Help is always welcome, is this idea something you or your organization plan to implement?
Yes, RDMC from UNC-CH is in the process of refining this workflow.
Additional context given at: https://dataverse.zulipchat.com/#narrow/channel/375812-containers/topic/goodbye-jenkins-you-did-an-amazing-job/with/591527683
Overview of the Suggestion
Jenkins is old. Jenkins can croak any day. Jenkins can also be turned off without a lot of prior notice. And Jenkins doesn't show everyone why tests are failing or how. Jenkins also doesn't test containers. So we want to be ahead of this happening, and have failsafes in place through GitHub Action Workflows. So @donsizemore on behalf of the Research Data Management Core from the University of North Carolina at Chapel Hill proposes this solution of running the api tests in the integration-tests.txt file in GitHub Actions just like how unit tests and real integration tests are already tested in maven_unit_test.yml
What kind of user is the suggestion intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Every engineer who works with Dataverse source code
What inspired this idea?
@donsizemore, @pdurbin, and @poikilotherm encouraged me to work on this workflow!
What existing behavior do you want changed?
N/A
Any brand new behavior do you want to add to Dataverse?
N/A
Any open or closed issues related to this suggestion?
Yes, this will also address #9916 and any other issues that y'all think can be addressed
Are you thinking about creating a pull request for this issue?
Help is always welcome, is this idea something you or your organization plan to implement?
Yes, RDMC from UNC-CH is in the process of refining this workflow.
Additional context given at: https://dataverse.zulipchat.com/#narrow/channel/375812-containers/topic/goodbye-jenkins-you-did-an-amazing-job/with/591527683