![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Alexander Uldall
|
|
Attachments:
|
jenkins_jira_post.PNG, jenkins_job_trigger.PNG, jira_post_stash.PNG |
|
Components:
|
pretested-integration |
|
Created:
|
21/Jul/14 1:06 PM
|
|
Description:
|
The SCM Changes list is invalidated after the pretest plugin has merged a ready-branch to master. This makes the list for the job and the jira notification contain invalid commit hash links.
I guess this is bacause of the squash commit that is used, making the commit on master different than the on that triggered jenkins, in tandem with the deletion of the branch causing stash to not find the commit in the repository. This makes the information presented misleading for users.
I would probably propose to either "change" the changes links provided by the git scm plugin to the new, squashed commit, keeping the old list in a separate pane if possible.
See attached images for how it looks in our jenkins/jira/stash setup.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Morten Engelhardt Olsen
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/d/optout.
