[JENKINS-49482] Better display of deployed artifacts. #125
Conversation
This file contains 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
bingshiao
added a commit
to bingshiao/pipeline-maven-plugin
that referenced
this pull request
Mar 27, 2018
* [JENKINS-27395] Record flow node and enclosing stage/branch for tests Downstream of jenkinsci/junit-plugin#76. This records the `FlowNode#id` for the step that's actually recording the test results and the enclosing stage(s)/branch(es) of that `FlowNode` with each suite, along with the names of the enclosing stage(s)/branch(es) on each `CaseResult` for display purposes. This is accomplished by getting the `FlowNode` via `context.get(FlowNode.class)`, and then passing the configured `JUnitResultArchiver`, the node's ID, the enclosing stage/branch IDs, and the run (which is used to get the `Run#getExternalizableId()` for internal purposes) to the new `JUnitResultArchiver#parseAndAttach` static method. That method does the rest of the work. Once this is all released, the classic test results pages will display the test name with the enclosing stage/branch names prepended (if there are test results from multiple stages/branches in the full test result - i.e., only if relevant). Blue Ocean has a PR to do the same that's pending. * Add issue annotation to the new test * Bump to junit 1.23 release. * Bump parent plugin version, fix tons of dependency issues * [JENKINS-49482] Hide empty 'Deployed Artifacts:' (jenkinsci#124) * [JENKINS-49482] Store artifact deployment details in the database and fix display of deployed artifacts. (jenkinsci#125) * [maven-release-plugin] prepare release pipeline-maven-3.3.1-beta-1 * [maven-release-plugin] prepare for next development iteration * [JENKINS-49482] Fix "java.lang.NoClassDefFoundError: edu/emory/mathcs/backport/java/util/Collections" * [maven-release-plugin] prepare release pipeline-maven-3.3.1-beta-2 * [maven-release-plugin] prepare for next development iteration * [JENKINS-49482] fix configuration screen * [maven-release-plugin] prepare release pipeline-maven-3.3.1 * [maven-release-plugin] prepare for next development iteration * [JENKINS-49549] Only display once the "Deployed Artifacts" report if withMaven is invoked 2+ times in a pipeline * [maven-release-plugin] prepare release pipeline-maven-3.3.2 * [maven-release-plugin] prepare for next development iteration * [JENKINS-27395] temporarily disable bump to the jenkins-junit-pipeline 1.23 due to additional dependencies. * Reverting d95e3dc as it is not necessary after ba36c1b. * [JENKINS-46785] Strategy to enable / disable publishers in pipelines. Default strategy, "IMPLICIT" is the current strategy to implicitly enable all publishers unless they are explicitly disabled. The second available strategy, "EXPLICIT", requires to explicitly enable the publishers in the "withMaven(options: [...])" attribute * [JENKINS-46785] Add unit test * [maven-release-plugin] prepare release pipeline-maven-3.4.0-beta-1 * [maven-release-plugin] prepare for next development iteration * [JENKINS-49632] Also record generated attached artifacts * [JENKINS-49632] uncomment the code * [maven-release-plugin] prepare release pipeline-maven-3.4.0 * [maven-release-plugin] prepare for next development iteration * [maven-release-plugin] prepare release pipeline-maven-3.4.1 * [maven-release-plugin] prepare for next development iteration * [JENKINS-49898] maven-invoker-plugin add support for relative path in "reportsDirectory", "projectsDirectory" and "cloneProjectsTo" (jenkinsci#131) * [maven-release-plugin] prepare release pipeline-maven-3.4.2 * [maven-release-plugin] prepare for next development iteration * [JENKINS-49896] Add support for invoker:integration-test in addition to invoker:run * [maven-release-plugin] prepare release pipeline-maven-3.4.3 * [maven-release-plugin] prepare for next development iteration * change order of developers in pom.xml so that Cyrille Le Clerc gets assigned the Jira issues * bump maven pom.xml plugins and parent pom * [JENKINS-50241] Introduce a dedicated build result screen for Maven details * JENKINS-49721 support `mvnw` maven installation (jenkinsci#136) * SQL views to help troubleshooting * [JENKINS-50241] Add "dependencies" section on the Maven details screen (jenkinsci#137)
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.
Store deployment details in the database
Build level details
Pipeline level details