Integrate resqui pipeline#15
Closed
thodkatz wants to merge 3 commits into
Closed
Conversation
I use a dashverse_token secret to publish results but pr can't read these secrets
Author
|
Can't test this PR because secrets can't be read from forks, it needs to be a base branch, so I can't test the publishing to DashVERSE |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is an attempt to run resqui via github actions and to publish the summary report to a self hosted DashVERSE instanced deployed at INAB-CERTH.
I have already tested the integration with this project. With this PR I am attempting to test the integration at the organization level.
For security reasons, since the action is running locally, it needs to be approved for external (not within the org) users.
We should be able to view the dashboard at http://160.40.71.177:8083/ within the LAN.
Note:
A secret for the dashverse token is saved at the org level. PRs from forks can't read these secrets, so publishing results won't work. The secret can be read only if the branch is on the base, so it will work at merge point. Otherwise PRs from base branches will work as well.