Repository navigation
Fixed : Pages with tags not run when new FitNesse is started. - #42
Merged
Merged
Conversation
Contributor
|
Thanks @suratdas! , actually this is a fix for https://issues.jenkins.io/browse/JENKINS-67171 |
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
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.
Steps to reproduce the issue
With this plugin, select to start FitNesse and try to run a page with tags. e.g.
TestSuite&runTestsMatchingAnyTag=smoke,criticalThe build will fail (see screenshot below).Why it fails and what the fix is
The code checks to see if the FitNesse is up and running before it appends the
suiteresponder. Because the URL includes&, it results in404from the FitNesse server causing the build to terminate.With this pull request, the base page now strips the
&part to check FitNesse status resulting in a successful build.Checks