subject:"Gradle JPI Plugin"

Re: Unable to fully release Job DSL Plugin due to issue with `gradle-jpi-plugin`

2021-10-27 Thread Jamie Tanna

I've managed to resolve this by upgrading the plugin 
<https://github.com/jenkinsci/job-dsl-plugin/commit/6b7a8d813c3c3b9f5daf0fcee823c9fd128d8f42>
 

On Wednesday, October 27, 2021 at 9:38:55 AM UTC+1 Jamie Tanna wrote:

> I've also raised this on the plugin 
> <https://github.com/jenkinsci/gradle-jpi-plugin/issues/192>
>
> On Wednesday, October 27, 2021 at 9:35:30 AM UTC+1 Jamie Tanna wrote:
>
>> Hey folks,
>>
>> I've just started my first release of the Job DSL Plugin (commit 
>> <https://github.com/jenkinsci/job-dsl-plugin/commit/027c7ebdbe24481b2d2d5f712c987446ea296972>)
>>  
>> and it's failing to publish the Jenkins Plugin, with the following error:
>>
>> ```
>> Initialized native services in: /home/jamie/.gradle/native
>> The client will now receive all logging from the daemon (pid: 67009). The 
>> daemon log file: /home/jamie/.gradle/daemon/5.0/daemon-67009.out.log
>> Starting 9th build in daemon [uptime: 2 mins 57.098 secs, performance: 
>> 100%]
>> Using 16 worker leases.
>> Starting Build
>> Settings evaluated using settings file 
>> '/home/jamie/workspaces/job-dsl-plugin/settings.gradle'.
>> Projects loaded. Root project using build file 
>> '/home/jamie/workspaces/job-dsl-plugin/build.gradle'.
>> Included projects: [root project 'job-dsl-plugin-root', project 
>> ':job-dsl-api-viewer', project ':job-dsl-core', project ':job-dsl-plugin']
>>
>> > Configure project :
>> Evaluating root project 'job-dsl-plugin-root' using build file 
>> '/home/jamie/workspaces/job-dsl-plugin/build.gradle'.
>>
>> > Configure project :job-dsl-core
>> Evaluating project ':job-dsl-core' using build file 
>> '/home/jamie/workspaces/job-dsl-plugin/job-dsl-core/build.gradle'.
>>
>> > Configure project :job-dsl-api-viewer
>> Evaluating project ':job-dsl-api-viewer' using build file 
>> '/home/jamie/workspaces/job-dsl-plugin/job-dsl-api-viewer/build.gradle'.
>>
>> > Configure project :job-dsl-plugin
>> Evaluating project ':job-dsl-plugin' using build file 
>> '/home/jamie/workspaces/job-dsl-plugin/job-dsl-plugin/build.gradle'.
>> All projects evaluated.
>> Selected primary task 'publish' from project :
>> Tasks to be executed: [task ':job-dsl-core:publish', task 
>> ':job-dsl-plugin:generatePomFileForMavenJpiPublication', task 
>> ':job-dsl-core:compileAstJava', task ':job-dsl-core:compileAstGroovy', task 
>> ':job-dsl-core:processAstResources', task ':job-dsl-core:astClasses', task 
>> ':job-dsl-core:compileJava', task ':job-dsl-core:compileGroovy', task 
>> ':job-dsl-core:processResources', task ':job-dsl-core:classes', task 
>> ':job-dsl-core:generateApiDoc', task ':job-dsl-core:jar', task 
>> ':job-dsl-plugin:localizer', task ':job-dsl-plugin:compileJava', task 
>> ':job-dsl-plugin:compileGroovy', task ':job-dsl-plugin:processResources', 
>> task ':job-dsl-plugin:classes', task ':job-dsl-plugin:configureManifest', 
>> task ':job-dsl-plugin:jar', task ':job-dsl-plugin:javadoc', task 
>> ':job-dsl-plugin:javadocJar', task ':job-dsl-plugin:sourcesJar', task 
>> ':job-dsl-api-viewer:assetCompile', task 
>> ':job-dsl-api-viewer:extractWebJars', task 
>> ':job-dsl-api-viewer:combineCss', task ':job-dsl-api-viewer:combineJs', 
>> task ':job-dsl-api-viewer:concat', task ':job-dsl-api-viewer:copyData', 
>> task ':job-dsl-api-viewer:copyFonts', task 
>> ':job-dsl-api-viewer:downloadUpdateCenter', task 
>> ':job-dsl-api-viewer:processUpdateCenter', task 
>> ':job-dsl-api-viewer:build', task ':job-dsl-plugin:generateLicenseInfo', 
>> task ':job-dsl-plugin:war', task 
>> ':job-dsl-plugin:publishMavenJpiPublicationToJenkinsRepository', task 
>> ':job-dsl-plugin:publish']
>> :job-dsl-core:publish (Thread[Execution worker for ':',5,main]) started.
>>
>> > Task :job-dsl-core:publish UP-TO-DATE
>> Skipping task ':job-dsl-core:publish' as it has no actions.
>> :job-dsl-core:publish (Thread[Execution worker for ':',5,main]) 
>> completed. Took 0.002 secs.
>> :job-dsl-plugin:generatePomFileForMavenJpiPublication (Thread[Execution 
>> worker for ':',5,main]) started.
>>
>> > Task :job-dsl-plugin:generatePomFileForMavenJpiPublication FAILED
>> Task ':job-dsl-plugin:generatePomFileForMavenJpiPublication' is not 
>> up-to-date because:
>>   Task.upToDateWhen is false.
>> :job-dsl-plugin:generatePomFileForMavenJpiPublication (Thread[Execution 
>> worker for ':',5,main]) completed. Took 0.044 secs.
>> 1 actionable task: 1 executed
>>
>> * Try:
>> Run with --debug option to get more log output. Run with --scan to get

Re: Unable to fully release Job DSL Plugin due to issue with `gradle-jpi-plugin`

2021-10-27 Thread Jamie Tanna

I've also raised this on the plugin 
<https://github.com/jenkinsci/gradle-jpi-plugin/issues/192>

On Wednesday, October 27, 2021 at 9:35:30 AM UTC+1 Jamie Tanna wrote:

> Hey folks,
>
> I've just started my first release of the Job DSL Plugin (commit 
> <https://github.com/jenkinsci/job-dsl-plugin/commit/027c7ebdbe24481b2d2d5f712c987446ea296972>)
>  
> and it's failing to publish the Jenkins Plugin, with the following error:
>
> ```
> Initialized native services in: /home/jamie/.gradle/native
> The client will now receive all logging from the daemon (pid: 67009). The 
> daemon log file: /home/jamie/.gradle/daemon/5.0/daemon-67009.out.log
> Starting 9th build in daemon [uptime: 2 mins 57.098 secs, performance: 
> 100%]
> Using 16 worker leases.
> Starting Build
> Settings evaluated using settings file 
> '/home/jamie/workspaces/job-dsl-plugin/settings.gradle'.
> Projects loaded. Root project using build file 
> '/home/jamie/workspaces/job-dsl-plugin/build.gradle'.
> Included projects: [root project 'job-dsl-plugin-root', project 
> ':job-dsl-api-viewer', project ':job-dsl-core', project ':job-dsl-plugin']
>
> > Configure project :
> Evaluating root project 'job-dsl-plugin-root' using build file 
> '/home/jamie/workspaces/job-dsl-plugin/build.gradle'.
>
> > Configure project :job-dsl-core
> Evaluating project ':job-dsl-core' using build file 
> '/home/jamie/workspaces/job-dsl-plugin/job-dsl-core/build.gradle'.
>
> > Configure project :job-dsl-api-viewer
> Evaluating project ':job-dsl-api-viewer' using build file 
> '/home/jamie/workspaces/job-dsl-plugin/job-dsl-api-viewer/build.gradle'.
>
> > Configure project :job-dsl-plugin
> Evaluating project ':job-dsl-plugin' using build file 
> '/home/jamie/workspaces/job-dsl-plugin/job-dsl-plugin/build.gradle'.
> All projects evaluated.
> Selected primary task 'publish' from project :
> Tasks to be executed: [task ':job-dsl-core:publish', task 
> ':job-dsl-plugin:generatePomFileForMavenJpiPublication', task 
> ':job-dsl-core:compileAstJava', task ':job-dsl-core:compileAstGroovy', task 
> ':job-dsl-core:processAstResources', task ':job-dsl-core:astClasses', task 
> ':job-dsl-core:compileJava', task ':job-dsl-core:compileGroovy', task 
> ':job-dsl-core:processResources', task ':job-dsl-core:classes', task 
> ':job-dsl-core:generateApiDoc', task ':job-dsl-core:jar', task 
> ':job-dsl-plugin:localizer', task ':job-dsl-plugin:compileJava', task 
> ':job-dsl-plugin:compileGroovy', task ':job-dsl-plugin:processResources', 
> task ':job-dsl-plugin:classes', task ':job-dsl-plugin:configureManifest', 
> task ':job-dsl-plugin:jar', task ':job-dsl-plugin:javadoc', task 
> ':job-dsl-plugin:javadocJar', task ':job-dsl-plugin:sourcesJar', task 
> ':job-dsl-api-viewer:assetCompile', task 
> ':job-dsl-api-viewer:extractWebJars', task 
> ':job-dsl-api-viewer:combineCss', task ':job-dsl-api-viewer:combineJs', 
> task ':job-dsl-api-viewer:concat', task ':job-dsl-api-viewer:copyData', 
> task ':job-dsl-api-viewer:copyFonts', task 
> ':job-dsl-api-viewer:downloadUpdateCenter', task 
> ':job-dsl-api-viewer:processUpdateCenter', task 
> ':job-dsl-api-viewer:build', task ':job-dsl-plugin:generateLicenseInfo', 
> task ':job-dsl-plugin:war', task 
> ':job-dsl-plugin:publishMavenJpiPublicationToJenkinsRepository', task 
> ':job-dsl-plugin:publish']
> :job-dsl-core:publish (Thread[Execution worker for ':',5,main]) started.
>
> > Task :job-dsl-core:publish UP-TO-DATE
> Skipping task ':job-dsl-core:publish' as it has no actions.
> :job-dsl-core:publish (Thread[Execution worker for ':',5,main]) completed. 
> Took 0.002 secs.
> :job-dsl-plugin:generatePomFileForMavenJpiPublication (Thread[Execution 
> worker for ':',5,main]) started.
>
> > Task :job-dsl-plugin:generatePomFileForMavenJpiPublication FAILED
> Task ':job-dsl-plugin:generatePomFileForMavenJpiPublication' is not 
> up-to-date because:
>   Task.upToDateWhen is false.
> :job-dsl-plugin:generatePomFileForMavenJpiPublication (Thread[Execution 
> worker for ':',5,main]) completed. Took 0.044 secs.
> 1 actionable task: 1 executed
>
> * Try:
> Run with --debug option to get more log output. Run with --scan to get 
> full insights.
>
> * Exception is:
> org.gradle.api.tasks.TaskExecutionException: Execution failed for task 
> ':job-dsl-plugin:generatePomFileForMavenJpiPublication'.
> at 
> org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:96)
> at 
> org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:65)
> at 
> org.gradle.api.internal.tasks.execution.ActionEventFiringTaskExec

Unable to fully release Job DSL Plugin due to issue with `gradle-jpi-plugin`

2021-10-27 Thread Jamie Tanna

Hey folks,

I've just started my first release of the Job DSL Plugin (commit 
)
 
and it's failing to publish the Jenkins Plugin, with the following error:

```
Initialized native services in: /home/jamie/.gradle/native
The client will now receive all logging from the daemon (pid: 67009). The 
daemon log file: /home/jamie/.gradle/daemon/5.0/daemon-67009.out.log
Starting 9th build in daemon [uptime: 2 mins 57.098 secs, performance: 100%]
Using 16 worker leases.
Starting Build
Settings evaluated using settings file 
'/home/jamie/workspaces/job-dsl-plugin/settings.gradle'.
Projects loaded. Root project using build file 
'/home/jamie/workspaces/job-dsl-plugin/build.gradle'.
Included projects: [root project 'job-dsl-plugin-root', project 
':job-dsl-api-viewer', project ':job-dsl-core', project ':job-dsl-plugin']

> Configure project :
Evaluating root project 'job-dsl-plugin-root' using build file 
'/home/jamie/workspaces/job-dsl-plugin/build.gradle'.

> Configure project :job-dsl-core
Evaluating project ':job-dsl-core' using build file 
'/home/jamie/workspaces/job-dsl-plugin/job-dsl-core/build.gradle'.

> Configure project :job-dsl-api-viewer
Evaluating project ':job-dsl-api-viewer' using build file 
'/home/jamie/workspaces/job-dsl-plugin/job-dsl-api-viewer/build.gradle'.

> Configure project :job-dsl-plugin
Evaluating project ':job-dsl-plugin' using build file 
'/home/jamie/workspaces/job-dsl-plugin/job-dsl-plugin/build.gradle'.
All projects evaluated.
Selected primary task 'publish' from project :
Tasks to be executed: [task ':job-dsl-core:publish', task 
':job-dsl-plugin:generatePomFileForMavenJpiPublication', task 
':job-dsl-core:compileAstJava', task ':job-dsl-core:compileAstGroovy', task 
':job-dsl-core:processAstResources', task ':job-dsl-core:astClasses', task 
':job-dsl-core:compileJava', task ':job-dsl-core:compileGroovy', task 
':job-dsl-core:processResources', task ':job-dsl-core:classes', task 
':job-dsl-core:generateApiDoc', task ':job-dsl-core:jar', task 
':job-dsl-plugin:localizer', task ':job-dsl-plugin:compileJava', task 
':job-dsl-plugin:compileGroovy', task ':job-dsl-plugin:processResources', 
task ':job-dsl-plugin:classes', task ':job-dsl-plugin:configureManifest', 
task ':job-dsl-plugin:jar', task ':job-dsl-plugin:javadoc', task 
':job-dsl-plugin:javadocJar', task ':job-dsl-plugin:sourcesJar', task 
':job-dsl-api-viewer:assetCompile', task 
':job-dsl-api-viewer:extractWebJars', task 
':job-dsl-api-viewer:combineCss', task ':job-dsl-api-viewer:combineJs', 
task ':job-dsl-api-viewer:concat', task ':job-dsl-api-viewer:copyData', 
task ':job-dsl-api-viewer:copyFonts', task 
':job-dsl-api-viewer:downloadUpdateCenter', task 
':job-dsl-api-viewer:processUpdateCenter', task 
':job-dsl-api-viewer:build', task ':job-dsl-plugin:generateLicenseInfo', 
task ':job-dsl-plugin:war', task 
':job-dsl-plugin:publishMavenJpiPublicationToJenkinsRepository', task 
':job-dsl-plugin:publish']
:job-dsl-core:publish (Thread[Execution worker for ':',5,main]) started.

> Task :job-dsl-core:publish UP-TO-DATE
Skipping task ':job-dsl-core:publish' as it has no actions.
:job-dsl-core:publish (Thread[Execution worker for ':',5,main]) completed. 
Took 0.002 secs.
:job-dsl-plugin:generatePomFileForMavenJpiPublication (Thread[Execution 
worker for ':',5,main]) started.

> Task :job-dsl-plugin:generatePomFileForMavenJpiPublication FAILED
Task ':job-dsl-plugin:generatePomFileForMavenJpiPublication' is not 
up-to-date because:
  Task.upToDateWhen is false.
:job-dsl-plugin:generatePomFileForMavenJpiPublication (Thread[Execution 
worker for ':',5,main]) completed. Took 0.044 secs.
1 actionable task: 1 executed

* Try:
Run with --debug option to get more log output. Run with --scan to get full 
insights.

* Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task 
':job-dsl-plugin:generatePomFileForMavenJpiPublication'.
at 
org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:96)
at 
org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:65)
at 
org.gradle.api.internal.tasks.execution.ActionEventFiringTaskExecuter.execute(ActionEventFiringTaskExecuter.java:44)
at 
org.gradle.api.internal.tasks.execution.TimeoutTaskExecuter.execute(TimeoutTaskExecuter.java:53)
at 
org.gradle.api.internal.tasks.execution.SnapshotAfterExecutionTaskExecuter.execute(SnapshotAfterExecutionTaskExecuter.java:38)
at 
org.gradle.api.internal.tasks.execution.OutputDirectoryCreatingTaskExecuter.execute(OutputDirectoryCreatingTaskExecuter.java:51)
at 
org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:59)
at

Compatiblity problem between gradle-jpi-plugin:0.26.0 (latest) and gradle:<4.4

2018-05-14 Thread 吴思稣

It report an exception `Unable to load class 
'org.gradle.api.file.DirectoryProperty'` when I update the gradle plugin 
[gradle-jpi-plugin](https://github.com/jenkinsci/gradle-jpi-plugin) to 
version 0.26.0, which is the [latest 
release](https://github.com/jenkinsci/gradle-jpi-plugin/releases/tag/0.26.0) 
on 5 Apr 2018.
And it runs normally with `gradle-jpi-plugin:0.25.0`.

I figure out that it seems like this 
[commit](https://github.com/jenkinsci/gradle-jpi-plugin/commit/64ef3fd963080230c94c85beb1af0f07ab6b2aa7)
 
break the compatibility.
In the commit, it import the class `org.gradle.api.file.DirectoryProperty`, 
which first occurs in gradle of version 4.4.

I think either adding a requirement for gradle version on README, or fixing 
this break should be done.
Thanks.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/de59264d-5b8d-4934-8aea-844295beb2f5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: gradle-jpi-plugin dependency resolution patch

2017-07-24 Thread Ryan Campbell

It would be awesome to merge this so that we can get better pipeline
support for the gradle-plugin!

On Mon, Jul 17, 2017 at 1:28 PM <ajohn...@cloudbees.com> wrote:

> Hello Jenkins devs,
>
> About 3 weeks ago I spoke with Daniel Spilker about the gradle-jpi-plugin
> <https://github.com/jenkinsci/gradle-jpi-plugin> not picking up
> transitive dependencies. He submitted this PR
> <https://github.com/jenkinsci/gradle-jpi-plugin/pull/87> which seems to
> fix the issue.
>
> Partial pipeline support
> <https://github.com/jenkinsci/gradle-plugin/pull/52> for the
> gradle-plugin is currently blocked for review/merge while waiting for this
> patch to be released. Writing this to ping Daniel and ask for help getting
> a merge of his gradle-jpi-plugin patch.
>
> Thanks all,
> - Alex Johnson (github: alexbrjo)
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/ee349e5d-7a37-4c76-932c-08a60fca4882%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/ee349e5d-7a37-4c76-932c-08a60fca4882%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANHK%3DJ2xMJcnm4pp%2BizYOWH%3D2hVy%3DcwSn99mao81tK0uETj%2BuA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

gradle-jpi-plugin dependency resolution patch

2017-07-17 Thread ajohnson

Hello Jenkins devs,

About 3 weeks ago I spoke with Daniel Spilker about the gradle-jpi-plugin 
<https://github.com/jenkinsci/gradle-jpi-plugin> not picking up transitive 
dependencies. He submitted this PR 
<https://github.com/jenkinsci/gradle-jpi-plugin/pull/87> which seems to fix 
the issue. 

Partial pipeline support 
<https://github.com/jenkinsci/gradle-plugin/pull/52> for the gradle-plugin 
is currently blocked for review/merge while waiting for this patch to be 
released. Writing this to ping Daniel and ask for help getting a merge of 
his gradle-jpi-plugin patch.

Thanks all,
- Alex Johnson (github: alexbrjo)

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/ee349e5d-7a37-4c76-932c-08a60fca4882%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Lost Commit Access to gradle-jpi-plugin

2015-07-08 Thread Daniel Beck

Hi Daniel,

that was me. I'm sorry about that. You now should again have access.

Background:
Basically every repo in jenkinsci has a team named 'Reponame Developers' that
grants write or admin access to that repo. For some reason (I suspect manual
forks through the UI rather than going through the IRC bot), some of these
groups have been messed up and granted access to more than 10 entirely
unrelated repos. As this is clearly wrong, I cleaned some of that up yesterday.
I suspect your access to gradle-jpi-plugin was granted through such a
misconfiguration.

On 08.07.2015, at 17:55, Daniel Spilker m...@daniel-spilker.com wrote:

Hi,

I (daspilker) somehow lost commit access to gradle-jpi-plugin. Can someone
fix this please?

https://github.com/jenkinsci/gradle-jpi-plugin

Thanks,
Daniel

--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an
email to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CAKqW32BrvMu_%2B0Ma%3DtXvNjHcDxAE4scAHmrvwgkyN__whtGaQQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/9B2ECD53-7373-4894-924B-7008C9EB523E%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Lost Commit Access to gradle-jpi-plugin

2015-07-08 Thread Daniel Spilker

Hi,

I (daspilker) somehow lost commit access to gradle-jpi-plugin. Can someone
fix this please?

https://github.com/jenkinsci/gradle-jpi-plugin

Thanks,
Daniel

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAKqW32BrvMu_%2B0Ma%3DtXvNjHcDxAE4scAHmrvwgkyN__whtGaQQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Gradle JPI Plugin 0.11.x

2015-05-08 Thread Daniel Spilker

Hi,

version 0.11.0 of the Gradle JPI plugin contains a critical regression [1].
The plugin will publish a HPI file which contains the POM XML. This has
been fixed in 0.11.1.

Sorry for any inconvenience.

Daniel


[1]: https://issues.jenkins-ci.org/browse/JENKINS-28305

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAKqW32CF-Geqhnbnw%2BGFGMOjkw3btakiSgCqk6Xhgjki8QwtBQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Gradle JPI Plugin

2015-02-17 Thread Daniel Spilker

Hi,

I'm the maintainer of the Gradle JPI plugin [1] (the Gradle equivalent of 
the maven-hpi-plugin) and I would like to get the plugin listed on the 
Gradle Plugin Portal [2].

To get the plugin included, some steps [3] need to be accomplished. The 
Gradle JPI plugin already fulfills all but step #4: add a 'gradle-plugin' 
attribute to each version in your plugin package. That needs to be done on 
the Jenkins Bintray account [4] for each version of the gradle-jpi-plugin 
package [5]. The attribute name is 'gradle-plugin' with a value of 
'org.jenkins-ci.jpi:org.jenkins-ci.tools:gradle-jpi-plugin'.

Can someone with access to the Bintray account do that? Or shall I post 
this on the infra list or create an INFRA ticket?

There is also RTFACT-6860 [6] in the Artifactory JIRA to sync attributes 
from Artifactory to Bintray. But that's not implemented yet, so for now it 
needs to be set directly in Bintray.

Daniel

[1] https://github.com/jenkinsci/gradle-jpi-plugin
[2] https://plugins.gradle.org/
[3] https://plugins.gradle.org/submit
[4] https://bintray.com/jenkins
[5] https://bintray.com/jenkins/maven/tools%3Agradle-jpi-plugin/view
[6] https://www.jfrog.com/jira/browse/RTFACT-6860

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5cd7645d-937b-4bd6-a42b-60896286ce8b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Failure Using the Gradle JPI Plugin

2015-01-08 Thread Daniel Spilker

The gradle-jpi-plugin 0.7.2 can be used with Gradle 1.12 and JDK 7. Make
sure to update the wrapper when changing Gradle versions.

That said, I released gradle-jpi-plugin 0.8.0 which must be used with
Gradle 2.2.1 and JDK7 or JDK8. Have a look at the changelog:
https://github.com/jenkinsci/gradle-jpi-plugin/blob/0.8.0/CHANGELOG.md

Daniel

On Tue, Jan 6, 2015 at 12:07 PM, Thomas Goeppel thomas.goep...@gmail.com
wrote:

Daniel,

thanks for the fast reply!

Your hint was good, even if I already had been using Java 7 in my
programming environment. After downgrading to Java 6, groovyw jpi works!

But what should I say, installing an outdated version of Java is a small
price to pay if the goal is using a modern programming language :-)

Cheers,
Thomas

On Monday, January 5, 2015 9:18:31 PM UTC+1, Daniel Spilker wrote:

Hi!

Sorry, the documentation does not give any recommendations. The
recommended Gradle version for the Gradle JPI Plugin is 1.12. Newer
versions will cause problems, the next version will support Gradle 2.2.1.

You have to use Java 7 since Java 8 also causes problems (
https://issues.jenkins-ci.org/browse/JENKINS-25643). If you want to
share your plugin with other users, you should probably stick to JDK6 since
that's the minimum version supported by Jenkins, see
https://wiki.jenkins-ci.org/display/JENKINS/Java+5+Compatibility.

Jenkins will provide a Groovy runtime for plugins (which is currently
1.8.9), you should use that version to avoid problems. It's added to the
dependencies automatically by the Gradle JPI plugin.

Daniel

On Mon, Jan 5, 2015 at 8:57 PM, Thomas Goeppel thomas@gmail.com
wrote:

Hello developers community!

I'd like to experiment with Jenkins plugins written in Groovy, and to
get started I'm trying to build a Groovy Jenkins plugin demo from Shiran
Rubin's talk at the 2014 Jenkins conference in Israel (video
https://www.youtube.com/watch?v=h_epgCWJ8lE, slides
https://www.cloudbees.com/sites/default/files/juc_presentation.pdf,
my fork of the github-repository
https://github.com/TG9541/frogballs-plugin).

The build fails with the following error message:

:compileGroovy
:processResources UP-TO-DATE
:classes
:jpi FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':jpi'.
java/util/HashMap$Entry

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or
--debug option to get more log output.

BUILD FAILED

I'm using Ubuntu 14.04, and since I couldn't find tool version
requirements, I installed most things from packages.

gradle -version prints the following versions:

Gradle 1.4

Gradle build time: Monday, September 9, 2013 8:44:25 PM UTC
Groovy: 1.8.6
Ant: Apache Ant(TM) version 1.9.3 compiled on April 8 2014
JVM: 1.7.0_65 (Oracle Corporation 24.65-b04)
OS: Linux 3.13.0-44-generic amd64

I tried the following, without seeing the error message change:

- build with the --debug option, and Gradle prior to 2.0 had issues
with Java1.8

http://forums.gradle.org/gradle/topics/gradle_fails_on_jdk8_with_java_lang_classnotfoundexception_java_util_hashmap_entry
- I downgraded to Java/JDK1.7 * changed the gradle-jpi-plugin dependency
from version 0.5.0 to 0.7.2
- used the dependencies I found in the job-dsl-plugin
https://github.com/jenkinsci/job-dsl-plugin/blob/master/build.gradle
(e.g. gradleVersion = '1.12')

A generally recommendation in the Gradle forums is upgrading Gradle, and
Groovy, to version 2.x. I do that, since it's not clear to me how the
Groovy version used in Jenkins relates to the version used by the build
tools (e.g. version of groovyc in the environment).

It would be nice if someone with more experience could have a look at
it, and could shed some light on the Groovy version tool/build dependencies!

Thanks in advance!

--
You received this message because you are subscribed to the Google
Groups Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send
an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/jenkinsci-dev/2092c5b5-1d1d-475e-a251-c0d690720601%
40googlegroups.com
https://groups.google.com/d/msgid/jenkinsci-dev/2092c5b5-1d1d-475e-a251-c0d690720601%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

Failure Using the Gradle JPI Plugin

2015-01-05 Thread Thomas Goeppel

Hello developers community!

I'd like to experiment with Jenkins plugins written in Groovy, and to get
started I'm trying to build a Groovy Jenkins plugin demo from Shiran
Rubin's talk at the 2014 Jenkins conference in Israel (video
https://www.youtube.com/watch?v=h_epgCWJ8lE, slides
https://www.cloudbees.com/sites/default/files/juc_presentation.pdf, my fork
of the github-repository https://github.com/TG9541/frogballs-plugin).

The build fails with the following error message:

:compileGroovy
:processResources UP-TO-DATE
:classes
:jpi FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':jpi'.
java/util/HashMap$Entry

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug
option to get more log output.

BUILD FAILED

I'm using Ubuntu 14.04, and since I couldn't find tool version
requirements, I installed most things from packages.

gradle -version prints the following versions:

Gradle 1.4

I tried the following, without seeing the error message change:

- build with the --debug option, and Gradle prior to 2.0 had issues
with Java1.8

http://forums.gradle.org/gradle/topics/gradle_fails_on_jdk8_with_java_lang_classnotfoundexception_java_util_hashmap_entry

- I downgraded to Java/JDK1.7 * changed the gradle-jpi-plugin dependency
from version 0.5.0 to 0.7.2
- used the dependencies I found in the job-dsl-plugin
https://github.com/jenkinsci/job-dsl-plugin/blob/master/build.gradle
(e.g. gradleVersion = '1.12')

It would be nice if someone with more experience could have a look at it,
and could shed some light on the Groovy version tool/build dependencies!

Thanks in advance!

--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/2092c5b5-1d1d-475e-a251-c0d690720601%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Failure Using the Gradle JPI Plugin

2015-01-05 Thread Daniel Spilker

Hi!

Sorry, the documentation does not give any recommendations. The recommended
Gradle version for the Gradle JPI Plugin is 1.12. Newer versions will cause
problems, the next version will support Gradle 2.2.1.

You have to use Java 7 since Java 8 also causes problems (
https://issues.jenkins-ci.org/browse/JENKINS-25643). If you want to share
your plugin with other users, you should probably stick to JDK6 since
that's the minimum version supported by Jenkins, see
https://wiki.jenkins-ci.org/display/JENKINS/Java+5+Compatibility.

Jenkins will provide a Groovy runtime for plugins (which is currently
1.8.9), you should use that version to avoid problems. It's added to the
dependencies automatically by the Gradle JPI plugin.

Daniel

On Mon, Jan 5, 2015 at 8:57 PM, Thomas Goeppel thomas.goep...@gmail.com
wrote:

Hello developers community!

I'd like to experiment with Jenkins plugins written in Groovy, and to get
started I'm trying to build a Groovy Jenkins plugin demo from Shiran
Rubin's talk at the 2014 Jenkins conference in Israel (video
https://www.youtube.com/watch?v=h_epgCWJ8lE, slides
https://www.cloudbees.com/sites/default/files/juc_presentation.pdf, my fork
of the github-repository https://github.com/TG9541/frogballs-plugin).

The build fails with the following error message:

:compileGroovy
:processResources UP-TO-DATE
:classes
:jpi FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':jpi'.
java/util/HashMap$Entry

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or
--debug
option to get more log output.

BUILD FAILED

I'm using Ubuntu 14.04, and since I couldn't find tool version
requirements, I installed most things from packages.

gradle -version prints the following versions:

Gradle 1.4

I tried the following, without seeing the error message change:

- build with the --debug option, and Gradle prior to 2.0 had issues
with Java1.8

It would be nice if someone with more experience could have a look at it,
and could shed some light on the Groovy version tool/build dependencies!

Thanks in advance!

--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an
email to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/2092c5b5-1d1d-475e-a251-c0d690720601%40googlegroups.com
https://groups.google.com/d/msgid/jenkinsci-dev/2092c5b5-1d1d-475e-a251-c0d690720601%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CAKqW32Dbq736HQEKtbg5tCvDq4%3DUKL3JsTevcbO8sA%2Bt%3DzPTHA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Gradle JPI Plugin 0.7.0 Released

2014-11-04 Thread Daniel Spilker

0.7.0 has a regression bug, dependencies are not included in the JPI file
[1]. 0.7.1 has been released with a fix. See the changelog [2] for details.

[1] https://issues.jenkins-ci.org/browse/JENKINS-25401
[2] https://github.com/jenkinsci/gradle-jpi-plugin/blob/0.7.1/CHANGELOG.md


On Fri, Oct 24, 2014 at 9:33 AM, Daniel Spilker m...@daniel-spilker.com
wrote:

 Hi,

 there is a new version of the Gradle JPI plugin [1].

 Some highlights from the changelog [2]:
 * updated Gradle to version 1.12, which is now the recommended version for
 projects using the plugin
 * added support for the Plugin-Developers and Support-Dynamic-Loading
 manifest attributes
 * set stapler.jelly.noCache to true when running the server task
 * copy plugin dependencies into working directory when running server
 task, JENKINS-25219 [3]
 * ignore non-existing directories (e.g. src/main/resources) when running
 localizer or server tasks
 * added findbugs:annotations:1.0.0 dependency to avoid compiler warnings,
 JENKINS-14400 [4]
 * added org.jenkins-ci.jpi as alternative qualified plugin id for Gradle
 plugin portal

 This will be the last version supporting Gradle 1.x. The next version will
 support Gradle 2.x only since we need a new feature in Gradle to be able to
 publish the JPI _and_ the JAR [5].

 Please report any problems or feature requests [6].

 [1] https://github.com/jenkinsci/gradle-jpi-plugin
 [2] https://github.com/jenkinsci/gradle-jpi-plugin/blob/0.7.0/CHANGELOG.md
 [3] https://issues.jenkins-ci.org/browse/JENKINS-25219
 [4] https://issues.jenkins-ci.org/browse/JENKINS-14400
 [5]
 https://issues.jenkins-ci.org/browse/JENKINS-25007?focusedCommentId=213889
 [6] https://issues.jenkins-ci.org/browse/JENKINS/component/16321

 Daniel

  --
 You received this message because you are subscribed to a topic in the
 Google Groups Jenkins Developers group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/jenkinsci-dev/2-TWdJWQrRM/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 jenkinsci-dev+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Gradle JPI Plugin 0.7.0 Released

2014-10-24 Thread Daniel Spilker

Hi,

there is a new version of the Gradle JPI plugin [1].

Some highlights from the changelog [2]:
* updated Gradle to version 1.12, which is now the recommended version for 
projects using the plugin
* added support for the Plugin-Developers and Support-Dynamic-Loading 
manifest attributes
* set stapler.jelly.noCache to true when running the server task
* copy plugin dependencies into working directory when running server task, 
JENKINS-25219 [3]
* ignore non-existing directories (e.g. src/main/resources) when running 
localizer or server tasks
* added findbugs:annotations:1.0.0 dependency to avoid compiler warnings, 
JENKINS-14400 [4]
* added org.jenkins-ci.jpi as alternative qualified plugin id for Gradle 
plugin portal

This will be the last version supporting Gradle 1.x. The next version will 
support Gradle 2.x only since we need a new feature in Gradle to be able to 
publish the JPI _and_ the JAR [5].

Please report any problems or feature requests [6].

[1] https://github.com/jenkinsci/gradle-jpi-plugin
[2] https://github.com/jenkinsci/gradle-jpi-plugin/blob/0.7.0/CHANGELOG.md
[3] https://issues.jenkins-ci.org/browse/JENKINS-25219
[4] https://issues.jenkins-ci.org/browse/JENKINS-14400
[5] 
https://issues.jenkins-ci.org/browse/JENKINS-25007?focusedCommentId=213889
[6] https://issues.jenkins-ci.org/browse/JENKINS/component/16321

Daniel

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Gradle JPI Plugin Released

2014-10-03 Thread Kohsuke Kawaguchi



Yay! This is great!

Would you be interested in doing a guest post on 
http://jenkins-ci.org/node to talk about this, plans for the future, 
and/or perhaps how to gradle-fy your Jenkins plugin project?


I think a lot of people will be interested in this.


On 10/01/2014 01:05 PM, Daniel Spilker wrote:

I released a new version of the Gradle JPI plugin:
https://github.com/jenkinsci/gradle-jpi-plugin/blob/0.6.0/CHANGELOG.md

Please give it a try and report any problems:
https://issues.jenkins-ci.org/browse/JENKINS/component/16321


Daniel

--
You received this message because you are subscribed to the Google
Groups Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send
an email to jenkinsci-dev+unsubscr...@googlegroups.com
mailto:jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Kohsuke Kawaguchi  http://kohsuke.org/

--
You received this message because you are subscribed to the Google Groups Jenkins 
Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Gradle JPI Plugin Released

2014-10-02 Thread Jeremy Marshall

Hi Daniel

it all works fine with my two plugins 
 selenium-axis-plugin https://github.com/jenkinsci/selenium-axis-plugin

 and an unreleased rebuild at run time demo axis plugin (in the Chuck 
Norris style) https://github.com/JeremyMarshall/chuck-norris-axis-plugin

What changes are there? 

Regards
Jeremy


-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Gradle JPI Plugin Released

2014-10-01 Thread Daniel Spilker

I released a new version of the Gradle JPI plugin:
https://github.com/jenkinsci/gradle-jpi-plugin/blob/0.6.0/CHANGELOG.md

Please give it a try and report any problems:
https://issues.jenkins-ci.org/browse/JENKINS/component/16321


Daniel

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Push access for gradle-jpi-plugin

2014-09-30 Thread Jeremy Marshall




 Hi 

I borrowed the setup for the selenium axis plugin (groovy and all) and I 
think it would be better in a more up to date gradle, so if there's 
anything I can do to help please let me know


Jeremy

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Push access for gradle-jpi-plugin

2014-09-24 Thread Daniel Spilker

Sorry, it's not working for me. I see no merge buttons on pull request and
can't push from the command line. Can you double check?

On Tue, Sep 23, 2014 at 12:11 PM, Ulli Hafner ullrich.haf...@gmail.com
wrote:

 Done.

 Welcome aboard! Ulli

 Am 22.09.2014 um 22:46 schrieb Daniel Spilker m...@daniel-spilker.com:

 Hi,

 I (daspilker) would like to get push access to
 https://github.com/jenkinsci/gradle-jpi-plugin.

 The plugin is unmaintained for several months now, no one is answering on
 issues or pull requests. I talked to Andrew Bayer at JUC Berlin and he said
 that he lost interest in maintaining it.

 I raised the question about the future of the plugin some weeks ago, but
 no one outside the Job DSL plugin answered:

 https://groups.google.com/forum/?fromgroups#!searchin/jenkinsci-dev/jpi/jenkinsci-dev/mHi2_MqWY2U/743C60b-028J

 Thanks in advance,
 Daniel

 --
 You received this message because you are subscribed to the Google Groups
 Jenkins Developers group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to jenkinsci-dev+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.




-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Push access for gradle-jpi-plugin

2014-09-24 Thread Ulli Hafner

Can please retry?

Am 24.09.2014 um 09:58 schrieb Daniel Spilker m...@daniel-spilker.com:

Sorry, it's not working for me. I see no merge buttons on pull request and
can't push from the command line. Can you double check?

On Tue, Sep 23, 2014 at 12:11 PM, Ulli Hafner ullrich.haf...@gmail.com
wrote:
Done.

Welcome aboard! Ulli

Am 22.09.2014 um 22:46 schrieb Daniel Spilker m...@daniel-spilker.com:

Hi,

I (daspilker) would like to get push access to
https://github.com/jenkinsci/gradle-jpi-plugin.

The plugin is unmaintained for several months now, no one is answering on
issues or pull requests. I talked to Andrew Bayer at JUC Berlin and he said
that he lost interest in maintaining it.

I raised the question about the future of the plugin some weeks ago, but no
one outside the Job DSL plugin answered:
https://groups.google.com/forum/?fromgroups#!searchin/jenkinsci-dev/jpi/jenkinsci-dev/mHi2_MqWY2U/743C60b-028J

Thanks in advance,
Daniel

signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Push access for gradle-jpi-plugin

2014-09-24 Thread Daniel Spilker

Now it works, thanks!

On Wed, Sep 24, 2014 at 12:22 PM, Ulli Hafner ullrich.haf...@gmail.com
wrote:

Can please retry?

Am 24.09.2014 um 09:58 schrieb Daniel Spilker m...@daniel-spilker.com:

Sorry, it's not working for me. I see no merge buttons on pull request and
can't push from the command line. Can you double check?

On Tue, Sep 23, 2014 at 12:11 PM, Ulli Hafner ullrich.haf...@gmail.com
wrote:

Done.

Welcome aboard! Ulli

Am 22.09.2014 um 22:46 schrieb Daniel Spilker m...@daniel-spilker.com:

Hi,

I (daspilker) would like to get push access to
https://github.com/jenkinsci/gradle-jpi-plugin.

The plugin is unmaintained for several months now, no one is answering on
issues or pull requests. I talked to Andrew Bayer at JUC Berlin and he said
that he lost interest in maintaining it.

I raised the question about the future of the plugin some weeks ago, but
no one outside the Job DSL plugin answered:

https://groups.google.com/forum/?fromgroups#!searchin/jenkinsci-dev/jpi/jenkinsci-dev/mHi2_MqWY2U/743C60b-028J

Thanks in advance,
Daniel

Re: gradle-jpi-plugin job config

2014-09-24 Thread Jesse Glick

On Tue, Sep 23, 2014 at 4:27 PM, Daniel Spilker m...@daniel-spilker.com wrote:
 it runs gradle test jpi which fails because
 it's building a Gradle plugin, not a Jenkins plugin. gradle check should
 do better. Can you change that?

Done:

https://jenkins.ci.cloudbees.com/job/plugins/job/gradle-jpi-plugin/20/console

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: gradle-jpi-plugin job config

2014-09-23 Thread Jesse Glick

On Tue, Sep 23, 2014 at 7:42 AM, Daniel Spilker m...@daniel-spilker.com wrote:
 the job for the gradle-jpi-plugin is a Maven job, but should be a Gradle job.

 Can someone please change that?

Done, though I think Jenkins will have to be restarted before the
change takes effect.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: gradle-jpi-plugin job config

2014-09-23 Thread Daniel Spilker

The change is effective. But it runs gradle test jpi which fails because
it's building a Gradle plugin, not a Jenkins plugin. gradle check should
do better. Can you change that? Sorry, it should have mentioned that before.

Daniel

On Tue, Sep 23, 2014 at 8:34 PM, Jesse Glick jgl...@cloudbees.com wrote:

 On Tue, Sep 23, 2014 at 7:42 AM, Daniel Spilker m...@daniel-spilker.com
 wrote:
  the job for the gradle-jpi-plugin is a Maven job, but should be a Gradle
 job.
 
  Can someone please change that?

 Done, though I think Jenkins will have to be restarted before the
 change takes effect.

 --
 You received this message because you are subscribed to a topic in the
 Google Groups Jenkins Developers group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/jenkinsci-dev/J3WT3ej51Yo/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 jenkinsci-dev+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Push access for gradle-jpi-plugin

2014-09-22 Thread Daniel Spilker

Hi,

I (daspilker) would like to get push access to 
https://github.com/jenkinsci/gradle-jpi-plugin.

The plugin is unmaintained for several months now, no one is answering on 
issues or pull requests. I talked to Andrew Bayer at JUC Berlin and he said 
that he lost interest in maintaining it.

I raised the question about the future of the plugin some weeks ago, but no 
one outside the Job DSL plugin answered:
https://groups.google.com/forum/?fromgroups#!searchin/jenkinsci-dev/jpi/jenkinsci-dev/mHi2_MqWY2U/743C60b-028J

Thanks in advance,
Daniel

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Gradle JPI Plugin

2014-08-18 Thread Daniel Spilker

Hi,

I have been using the Gradle JPI plugin to build the Job DSL plugin for 
some time now. It has been doing great so far, but it also has it's issues. 
The biggest issue is that it seems to be unmaintained.

Every time I hit an issue with the Gradle JPI plugin, I'm close to porting 
the Job DSL plugin to Maven. But the Job DSL plugin is written in Groovy 
and I like the idea of having a full Groovy development stack and IMHO the 
Groovy integration in Gradle is much better than the available Maven 
plugins.

I'm not a Gradle expert (yet), but I could volunteer to do some work. I 
already reported a few issues and opened several pull requests. Apart from 
that, I would like to get the plugin migrated to Gradle 2.0 and get rid of 
all the warnings it produces in the build output.

Is anyone else using the Gradle JPI Plugin? Should we just scrap it or 
should we try to find a new maintainer?

Daniel

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Unable to fully release Job DSL Plugin due to issue with `gradle-jpi-plugin`

Re: Unable to fully release Job DSL Plugin due to issue with `gradle-jpi-plugin`

Unable to fully release Job DSL Plugin due to issue with `gradle-jpi-plugin`

Compatiblity problem between gradle-jpi-plugin:0.26.0 (latest) and gradle:<4.4

Re: gradle-jpi-plugin dependency resolution patch

gradle-jpi-plugin dependency resolution patch

Re: Lost Commit Access to gradle-jpi-plugin

Lost Commit Access to gradle-jpi-plugin

Gradle JPI Plugin 0.11.x

Gradle JPI Plugin

Re: Failure Using the Gradle JPI Plugin

Failure Using the Gradle JPI Plugin

Re: Failure Using the Gradle JPI Plugin

Re: Gradle JPI Plugin 0.7.0 Released

Gradle JPI Plugin 0.7.0 Released

Re: Gradle JPI Plugin Released

Re: Gradle JPI Plugin Released

Gradle JPI Plugin Released

Re: Push access for gradle-jpi-plugin

Re: Push access for gradle-jpi-plugin

Re: Push access for gradle-jpi-plugin

Re: Push access for gradle-jpi-plugin

Re: gradle-jpi-plugin job config

Re: gradle-jpi-plugin job config

Re: gradle-jpi-plugin job config

Push access for gradle-jpi-plugin

Gradle JPI Plugin

27 matches

Site Navigation

Mail list logo

Footer information