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.
What's in this PR?
Refresh functionality for refresh button
Why
So when a user's servers are in a CONNECTED state but they we only have their config data but no pipeline events or when we have pipeline events but no plugin config data, they can try refreshing the panel so see if their Jenkins admin has got their act together and is now sending data through.
User hits refresh but we still don't have data - just rerenders same content
Screen.Recording.2023-12-11.at.10.30.21.am.mov
User hits refresh and now we have the data so they see the updated content (is this example, their plugin configuration from Jenkins)
Screen.Recording.2023-12-11.at.10.29.29.am.mov
Added feature flags
same same
Affected issues
Arc-2738
How has this been tested?
Locally and unit testing.
What's Next?
Algolia