[JIRA] (JENKINS-15406) Root build script field is never used

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-15406) Root build script field is never used

JIRA noreply@jenkins-ci.org
Issue Type: Bug Bug
Assignee: Gregory Boissinot
Components: gradle
Created: 04/Oct/12 4:20 PM
Description:

It seems "root build script" field is always omitted.

For instance, I have a git repository having a foo/build.gradle script.
I then set "root build script" to "${WORKSPACE}/foo/"
I'm using gradlew.

I would like to either execute



${WORKSPACE}/foo/gradlew

_or_ execute

${WORKSPACE}/gradlew -p ${WORKSPACE}/foo

But for now, it is :

${WORKSPACE}/gradlew



which is executed, not using foo/build.gradle script.

Not that it isn't related to gradlew since when using a gradle installation, it remains the same.

I tried to put ${WORKSPACE}/foo/build.gradle in "Build file" field as a workaround, but it didn't worked either (build script is taken, but with -b, not -p which seems reasonable)

Environment: gradle plugin 1.20
Project: Jenkins
Priority: Critical Critical
Reporter: Frédéric Camblor
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
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-15406) When using gradlew, root build script field is not used to locate gradlew

JIRA noreply@jenkins-ci.org
Change By: Frédéric Camblor (04/Oct/12 4:25 PM)
Summary: Root When using gradlew, root  build script field is  never  not  used  to locate gradlew
Priority: Critical Minor
Description: It seems "root build script"  field  is  always omitted  not really well taken when using gradlew .

For instance, I have a git repository having a foo/build.gradle script.
I then set "root build script" to "${WORKSPACE}/foo/"
I'm using gradlew.

I would like to  either  execute 
{code}
${WORKSPACE}/foo/gradlew 
{code} 

_or_ execute But for now, it is some sort of :  
{code}
${WORKSPACE}/gradlew -p ${WORKSPACE}/foo
{code}

But for now, it is :
{code}
${WORKSPACE}/
I think we should define gradlew
{code}
which is executed, not using foo/build.gradle script.

Not that it isn't related
 location (relative  to  gradlew since when using a gradle installation  checked out root repository) because for the moment ,  it remains  the  same.

I tried
 only way  to  put ${WORKSPACE}/foo/build.gradle in "Build file" field as a  workaround , but it didn't worked either (build script  the problem  is  taken, but with -b, not -p which seems reasonable)  to put gradlew in the root scm hierarchy
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
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-15406) When using gradlew, root build script field is not used to locate gradlew

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Change By: Frédéric Camblor (04/Oct/12 4:25 PM)
Description: It seems "root build script" is not really well taken when using gradlew.

For instance, I have a git repository having a foo/build.gradle script.
I then set "root build script" to "${WORKSPACE}/foo/"

I would like to execute
 :  

{code}
${WORKSPACE}/foo/gradlew 
{code} 

But for now, it is some sort of :

{code}
${WORKSPACE}/gradlew -p ${WORKSPACE}/foo
{code}

I think we should define gradlew location (relative to checked out root repository) because for the moment, the only way to workaround the problem is to put gradlew in the root scm hierarchy
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
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-15406) When using gradlew, root build script field is not used to locate gradlew

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Change By: Frédéric Camblor (04/Oct/12 4:26 PM)
Description: It seems "root build script" is not really well taken when using gradlew.

For instance, I have a git repository having a foo/build.gradle script.
I then set "root build script" to "${WORKSPACE}/foo/"

I would like to execute :

{code}
$
\ {WORKSPACE \ }/foo/gradlew 
{code} 

But for now, it is some sort of :

{code}
$
\ {WORKSPACE \ }/gradlew -p $ \ {WORKSPACE \ }/foo
{code}

I think we should define gradlew location (relative to checked out root repository) because for the moment, the only way to workaround the problem is to put gradlew in the root scm hierarchy
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
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-15406) When using gradlew, root build script field is not used to locate gradlew

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Gregory Boissinot resolved Bug JENKINS-15406 as Fixed
Change By: Gregory Boissinot (26/Nov/12 9:12 PM)
Status: Open Resolved
Resolution: Fixed
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
Reply | Threaded
Open this post in threaded view
|

[JIRA] [gradle] (JENKINS-15406) When using gradlew, root build script field is not used to locate gradlew

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

Hello,

Encountered that bug today. Checked jenkins gradle plugin sources and provided a fix - please check this pull request

Regards, Denis

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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

[JIRA] [gradle] (JENKINS-15406) When using gradlew, root build script field is not used to locate gradlew

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

Code changed in jenkins
User: denis.zhdanov
Path:
src/main/java/hudson/plugins/gradle/Gradle.java
http://jenkins-ci.org/commit/gradle-plugin/19a81cfa7f1ee6073a0b589811cba61e9763c569
Log:
[FIXED JENKINS-15406]

Use gradle wrapper from a project which is located not at the workspace root

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 [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

[JIRA] [gradle] (JENKINS-15406) When using gradlew, root build script field is not used to locate gradlew

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

Code changed in jenkins
User: Gregory Boissinot
Path:
src/main/java/hudson/plugins/gradle/Gradle.java
http://jenkins-ci.org/commit/gradle-plugin/8e6f838a6d051ca087b2e936be61b0e7675c75c8
Log:
Merge pull request #21 from denis-zhdanov/master

[FIXED JENKINS-15406]

Compare: https://github.com/jenkinsci/gradle-plugin/compare/1dac78bcda1a...8e6f838a6d05

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 [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

[JIRA] [gradle] (JENKINS-15406) When using gradlew, root build script field is not used to locate gradlew

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Change By: SCM/JIRA link daemon (06/Apr/14 9:23 PM)
Status: Reopened Resolved
Resolution: Fixed
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 [hidden email].
For more options, visit https://groups.google.com/d/optout.