Splitting the work up to make the cause linkable instead.

This is waiting on our new extension points to allow this.

Code changed in jenkins
User: Ivan Meredith
Path:
src/main/java/org/jenkinsci/plugins/displayurlapi/ClassicDisplayURLProvider.java
src/main/java/org/jenkinsci/plugins/displayurlapi/DisplayURLProvider.java
src/main/java/org/jenkinsci/plugins/displayurlapi/actions/AbstractDisplayAction.java
src/test/java/org/jenkinsci/plugins/displayurlapi/actions/ActionRedirectExtendedTest.java
http://jenkins-ci.org/commit/display-url-api-plugin/29162034cbc59d323e87962c8b114f0f083c2e05
Log:
{JENKINS-41502] Select provider using a paramater

kshultz https://github.com/jenkinsci/display-url-api-plugin/pull/17 is a companion pr, how is testing notes handled in this case?

imeredith, you've made it really simple actually, thanks for that. Since the PR has a test included as part of it, I typically do something like this.

Testing Notes:

• Test coverage has been added as part of the above-referenced PR.

But typically it's not been stories that have received the testing notes, it's been individual issues (bugs, RFEs, etc).

Code changed in jenkins
User: Ivan Meredith
Path:
src/main/java/org/jenkinsci/plugins/displayurlapi/ClassicDisplayURLProvider.java
src/main/java/org/jenkinsci/plugins/displayurlapi/DisplayURLProvider.java
src/main/java/org/jenkinsci/plugins/displayurlapi/actions/AbstractDisplayAction.java
src/test/java/org/jenkinsci/plugins/displayurlapi/actions/ActionRedirectExtendedTest.java
http://jenkins-ci.org/commit/display-url-api-plugin/4c68a345a7b691937fe11f40a495461cf23c98ed
Log:
Merge pull request #17 from jenkinsci/JENKINS-41502_select_provider_with_parameter

JENKINS-41502 Select provider using a paramater

Compare: https://github.com/jenkinsci/display-url-api-plugin/compare/d69340a23e68...4c68a345a7b6

kshultz Oh hmm. If we had decent tests in the initial pr's we might not have regressions for testing notes to be generated for!

imeredith, That's where we're hoping to get. But testing notes are getting included as part of new/unstarted as well as user-opened issues. In fact, I'd like to start participating in the issue planning process earlier, so that we can do just what you've described - ensure that there are tests included in the initial PRs. We're getting there, it's just not a quick process. There was a lot of catching up to do first.

I haven't been applying testing notes to the stories mostly because stories tend to be broader in scope, and include >1 issue (task/bug/rfe/etc) in them.

Code changed in jenkins
User: Ivan Meredith
Path:
pom.xml
http://jenkins-ci.org/commit/blueocean-display-url-plugin/a5eff368714dc20ab2cf094397c942a0e11b9b67
Log:
JENKINS-41502 Bump display-url-version

Code changed in jenkins
User: Ivan Meredith
Path:
pom.xml
src/main/java/org/jenkinsci/plugins/blueoceandisplayurl/BlueOceanDisplayURLImpl.java
http://jenkins-ci.org/commit/blueocean-display-url-plugin/42785e42fabb84a488a583b013bc41dd9a9ee1f4
Log:
JENKINS-41502 Bump display-url version (#12)

• JENKINS-41502 Bump display-url-version