You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are you a customer of Octopus Deploy? Don't raise the issue here. Please contact our support team so we can triage your issue, making sure it's handled appropriately.
Prerequisites
I have verified the problem exists in the latest version
I have searched open and closed issues to make sure it isn't already reported
I have written a descriptive issue title
I have linked the original source of this report
I have tagged the issue appropriately (area/*, kind/bug, tag/regression?)
The bug
The Octopus Deploy plugin for Jenkins will not parse Commit comments or VcsType correctly if its the first commit to a new Github branch.
Any subsequent commits will parse the details correctly.
From the code, it looks as though the commit comments and VcsType are determined by the "Previous Build", on that particular branch. This means that there is no "Previous Build" for a new branch commit.
What I expected to happen
Initial commits on a branch should determine if they have branched off from a different tree and include those commits comments as well.
The VcsType should be determined from something other than the "Previous Build"
Steps to reproduce
Create a Jenkins pipeline to push Build Information to an Octopus Instance.
Make at least a couple of commits to the default branch.
Use the pipeline to make the next commit to a new Branch.
Are you a customer of Octopus Deploy? Don't raise the issue here. Please contact our support team so we can triage your issue, making sure it's handled appropriately.
Prerequisites
The bug
The Octopus Deploy plugin for Jenkins will not parse Commit comments or VcsType correctly if its the first commit to a new Github branch.
Any subsequent commits will parse the details correctly.
From the code, it looks as though the commit comments and VcsType are determined by the "Previous Build", on that particular branch. This means that there is no "Previous Build" for a new branch commit.
What I expected to happen
Initial commits on a branch should determine if they have branched off from a different tree and include those commits comments as well.
The VcsType should be determined from something other than the "Previous Build"
Steps to reproduce
Screen capture
First commit to a new branch
![image](https://user-images.githubusercontent.com/5361797/114116866-cce17000-9928-11eb-822b-c9900b3d27cb.png)
Subsequent commits
![image](https://user-images.githubusercontent.com/5361797/114116910-e5518a80-9928-11eb-8a98-755fceac4a97.png)
Affected versions
Jenkins plugin 3.1.3 tested.
Workarounds
None available.
Links
Original Ticket
https://help.octopus.com/t/build-information/26464
Link to relevant section in Code Repo - Public
octopus-jenkins-plugin/src/main/java/hudson/plugins/octopusdeploy/OctopusDeployPushBuildInformationRecorder.java
Lines 204 to 280 in 006ef70
The text was updated successfully, but these errors were encountered: