Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publishing BuildRuns to VersionOne does not work correctly with matrix projects in Jenkins #12

Open
mrpaff opened this issue Oct 7, 2015 · 0 comments

Comments

@mrpaff
Copy link

mrpaff commented Oct 7, 2015

I have a multi-configuration job in Jenkins which uses the matrix project plug-in.
The project is executed on two different platforms.
Let's call the project "projectA", which is executed on two platforms - platformX and platformY
I add the V1 Notifier to the matrix project as post-build action.
I also created BuildProject in VersionOne with Reference=projectA

However when the build is executed on platformX, V1Notifier is not able to find BuildProject.
That's because it searches for BuildProject with name platform=platformX and not for projectA.

Expected result:
When V1Notifier is added to matrix project with multiple configurations it should:

  • Look for BuildProject named after the matrix project in Jenkins and not after specific configuration
  • Create BuildRun for every executed configuration
  • Create only one ChangeSet (assuming only one commit trigerred the build), but assign it to all BuildRuns representing this multi-configuration build
  • Assign all BuildRuns to the Defect/Backlog Item
  • BuildRun should contain the full name of the Jenkins build (e.g projectA >> platformX #123)

If necessary I can attach the definition of one of our matrix jobs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant