History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-3503
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Robin Shen
Reporter: Benoit Maury-Bouet
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
QuickBuild

Expose grape/ ivy settings

Created: 26/Feb/20 09:27 AM   Updated: 02/Mar/20 11:56 PM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
File Attachments: 1. XML File grapeConfig.xml (1.0 kb)



 Description  « Hide
Dear all,

We would love to use IVY and grape to build groovy libs and apis we could easily reuse in scripts.
so we could use @Grab to point to our gitlab instance.



 All   Comments   Work Log   Change History      Sort Order:
Robin Shen [28/Feb/20 12:43 AM]
I am not familiar with Ivy/grape things. How do you anticipate to use that in QB? Via a special step to call Ivy/grape command?

Benoit Maury-Bouet [02/Mar/20 08:03 AM]
Hi Robin,

Was I did a few months back as a proof of concept :
1. Added ivy-2.5.0-rc1.jar to plugins\com.pmease.quickbuild.libs
2. Create a .groovy folder in quickbuild's user home folder with a grapeConfig.xml
2. Build a groovy library
3. Publish the jar file to artifactory
4. Create a script step using groovy:
----------------------
groovy:
@GrabResolver(name='artifactory', root='https://artifactory/artifactory/maven-playground-local/', m2Compatible='true')
@Grab("org.ubisoft.bge2:bge2-qb-groovylib:0.4")
import org.ubisoft.bge2.JiraTools

def jt = new JiraTools();
----------------------

The issue being this is only doable for scripts run on server right now because agents lacks the grapeconfig.xml file
We can of course create our own specific agent setup to make sure this work.

QB has it's own defaultGrapeConfig.xml in
com.pmease.quickbuild_XXX.jar => groovy-all-1.8.9.jar
and if i remeber correctly some paths doesn't exist anymore, so we have to wait for the timeout to fire before we can use our own config file

I'm attaching our grapeConfig.xml as a sample



Robin Shen [02/Mar/20 11:56 PM]
Looks to me that you want to use new groovy libraries. If so, how about putting the library (jira tool lib here I guess) directly into QB's "plugins/com.pmease.quickbuild.libs" directory?