Details
-
Improvement
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
The changelog and the deliver is done in the same remote method. If the deliver fails, the changelog is lost.
Split it up, so that failed delivers still have changelogs.
This is actually not something the SCM implementation can do anything about.
The change log is parsed and written in the same breath as the ClearCase deliver. This means that the core dictates, that if anything fails in checkout() no change log is written.
This is also applicable for the git plugin when the "Merge before build" option is set.
If the deliver or the merge fails, the change log is not written, even though there is an actual change set. No one is blamed as a result.
Attachments
Issue Links
- depends on
-
JENKINS-19740 Add an additional step after SCM checkout, letting SCM implementations do more work after change log is written
-
- Resolved
-
Activity
Christian Wolfgang
created issue -
Christian Wolfgang
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Summary | When a deliver fails, the changelog is written, case 9869 | When a deliver fails, the changelog is NOT written, case 9869 |
Christian Wolfgang
made changes -
| Component/s | core [ 15593 ] | |
| Component/s | git [ 15543 ] | |
| Description |
The changelog and the deliver is done in the same remote method. If the deliver fails, the changelog is lost. Split it up, so that failed delivers still have changelogs. |
The changelog and the deliver is done in the same remote method. If the deliver fails, the changelog is lost. Split it up, so that failed delivers still have changelogs. This is actually not something the SCM implementation can anything about. The change log is parsed and written in the same breath as the ClearCase deliver. This means that the core dictates, that if anything fails in checkout() no change log is written. This is also applicable for the git plugin when the "Merge before build" option is set. |
Christian Wolfgang
made changes -
| Description |
The changelog and the deliver is done in the same remote method. If the deliver fails, the changelog is lost. Split it up, so that failed delivers still have changelogs. This is actually not something the SCM implementation can anything about. The change log is parsed and written in the same breath as the ClearCase deliver. This means that the core dictates, that if anything fails in checkout() no change log is written. This is also applicable for the git plugin when the "Merge before build" option is set. |
The changelog and the deliver is done in the same remote method. If the deliver fails, the changelog is lost. Split it up, so that failed delivers still have changelogs. This is actually not something the SCM implementation can anything about. The change log is parsed and written in the same breath as the ClearCase deliver. This means that the core dictates, that if anything fails in checkout() no change log is written. This is also applicable for the git plugin when the "Merge before build" option is set. If the deliver or the merge fails, the change log is not written, even though there is an actual change set. No one is blamed as a result. |
Christian Wolfgang
made changes -
| Description |
The changelog and the deliver is done in the same remote method. If the deliver fails, the changelog is lost. Split it up, so that failed delivers still have changelogs. This is actually not something the SCM implementation can anything about. The change log is parsed and written in the same breath as the ClearCase deliver. This means that the core dictates, that if anything fails in checkout() no change log is written. This is also applicable for the git plugin when the "Merge before build" option is set. If the deliver or the merge fails, the change log is not written, even though there is an actual change set. No one is blamed as a result. |
The changelog and the deliver is done in the same remote method. If the deliver fails, the changelog is lost. Split it up, so that failed delivers still have changelogs. This is actually not something the SCM implementation can do anything about. The change log is parsed and written in the same breath as the ClearCase deliver. This means that the core dictates, that if anything fails in checkout() no change log is written. This is also applicable for the git plugin when the "Merge before build" option is set. If the deliver or the merge fails, the change log is not written, even though there is an actual change set. No one is blamed as a result. |
| Link |
This issue depends on |
Mads Nielsen
made changes -
| Fix Version/s | current [ 10162 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Workflow | JNJira [ 151012 ] | JNJira + In-Review [ 193776 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |