<< Back to previous view

[QB-3378] Able to use dependency build information to script QuicBuild repository dest path
Created: 19/Apr/19  Updated: 04/May/19

Status: Resolved
Project: QuickBuild
Component/s: None
Affects Version/s: 9.0.8
Fix Version/s: 9.0.9

Type: Improvement Priority: Major
Reporter: Robin Shen Assigned To: Unassigned
Resolution: Fixed Votes: 0
Remaining Estimate: Unknown Time Spent: Unknown
Original Estimate: Unknown


 Description   
I'm attempting to use the Quickbuild repository to retrieve dependent build artifacts to create an overall release package with all artifacts. Essentially I have an application that is made up of 13 different components. They want to be able to build the components separately so they can patch easily if needed; but from most runs, all components would be built if changes are found. The issue I'm running into is the following. I have ComponentA & ComponentB; Component A artifacts generated are under a folder "bin" the same is true for ComponentB. So when I run my configuration that gets ComponentA & Component B's artifacts, it pulls both to a folder "bin" I need these to be separate though, like ComponentA/bin & ComponentB/bin. That way on deploy I can tell whose artifacts need to deploy to where. Is there a way to use DestinationPath for this? Something like this.getConfigurationID() or this.getConfigurationName()? I know those don't exist, but I'm hoping there is some other way. I'm assuming you loop through the files to retrieve when there are multiple configurations listed, but I'm not seeing a way to specify in the destination the configuration ID or name of the configuration that artifacts are currently being retrieve from

 Comments   
Comment by Scott Chapman [ 01/May/19 01:23 PM ]
I've upgraded to 9.09 to get this enhancement; however, I'm not seeing in the script help section or information section what object.value I'm to use. Please advise.
Comment by Scott Chapman [ 01/May/19 01:26 PM ]
Never mind. I found it. current.getDependency()
Generated at Sat Apr 20 04:54:32 UTC 2024 using JIRA 189.