Key: |
QB-2476
|
Type: |
Bug
|
Status: |
Resolved
|
Resolution: |
Fixed
|
Priority: |
Critical
|
Assignee: |
Robin Shen
|
Reporter: |
Fai Fung
|
Votes: |
0
|
Watchers: |
2
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 25/Jun/15 09:16 AM
Updated: 11/Jul/15 12:43 AM
|
|
Component/s: |
None
|
Affects Version/s: |
6.0.10
|
Fix Version/s: |
6.0.22
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
File Attachments:
|
None
|
Image Attachments:
|
|
|
I created two build configurations:
1). One uses the Artifactory Publish step and pushes an artifact to Artifactory, this works and I see the artifact and the build in artifactory.
2). Then I created a build configuration consuming this artifact, using the Artifactory Artifact Repository and use the LATEST build number.
When I trigger a couple of builds of buildconfig 1, a new build gets registered each time.
However 2). is triggered only once and if I run 2. manually it detects the first known build of 1. in Artifactory as LATEST.
Seems like the LATEST build determination is off.
|
Description
|
I created two build configurations:
1). One uses the Artifactory Publish step and pushes an artifact to Artifactory, this works and I see the artifact and the build in artifactory.
2). Then I created a build configuration consuming this artifact, using the Artifactory Artifact Repository and use the LATEST build number.
When I trigger a couple of builds of buildconfig 1, a new build gets registered each time.
However 2). is triggered only once and if I run 2. manually it detects the first known build of 1. in Artifactory as LATEST.
Seems like the LATEST build determination is off. |
Show » |
No work has yet been logged on this issue.
|
|