Git plugin - GIT_BRANCH set to detached

[Hamish Campbell]

Hey all,

We recently upgraded Jenkins from git-code 1.7 / git plugin 1.5 to latest 
versions (1.9.1 / 2.2.0 respectively).

We're also using the GitHub pull request builder to create PR builds on 
push to git.

Previously, the jenkins var GIT_BRANCH was set to the remote ref, e.g. 
"origin/pr/191/merge". After upgrading the plugin GIT_BRANCH is "detached". 
Mainline builds are still correctly marked as "master".

Additionally, the jenkins API response for the build does not seem to be 
aware of the ref. In other words, before the upgrade, we had 
"origin/pr/191/merge" listed in buildsByBranchName, however we no longer 
see new PR branches appear in the build list any more.

Is there a way to configure the previous behaviour for the updated plugin 
version?

-- 
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.

Default instance with hetero-list

[Richard Lavoie]

Hi guys,

I have an hetero-list where I'd like to have default values pre-populated in 
the form when we select a descriptor in the select box.

Ideally, I'd like to have the descriptor instanciate the describable with the 
no-arg constructor when a user request the associated config.jelly file.

My actual solution in my jelly file is to have an if check to see if instance 
is defined and use the descriptor object if not which leads me to have the same 
methods in my descriptor for the default values I want to be prefilled.

Is there a more clever way to achieve such thing ?

Thanks,
Richard Lavoie

-- 
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: Classloading issues between git and git-client plugins?!

[Robert Sandell]

But if that was the issue then we wouldn't see the issue when running on
the master I guess, but we do.
Den 7 apr 2014 17:58 skrev "Stephen Connolly" <
stephen.alan.conno...@gmail.com>:

> because the channel is not hooked up to the überclassloader somehow... so
> when the class is called for on the remote end, it doesn't show up. I
> suspect some of the perf improvements in classloading are hitting long
> running slaves. If my theory is correct disconnecting and reconnecting the
> slave in question should clear the issue.
>
>
> On 7 April 2014 16:51, Sandell, Robert wrote:
>
>> The only support contract I have is myself and my groovy script console J
>>
>>
>>
>> What baffles me is that the uberClassLoader can load the class, but the
>> build fails to.
>>
>>
>>
>>
>>
>>
>>
>> *Robert Sandell*
>>
>> *Sony Mobile Communications*
>>
>> Tel: +46 10 80 12721
>>
>> sonymobile.com
>>
>>
>>
>> *From:* jenkinsci-dev@googlegroups.com [mailto:
>> jenkinsci-dev@googlegroups.com] *On Behalf Of *Stephen Connolly
>> *Sent:* den 7 april 2014 17:05
>>
>> *To:* jenkinsci-dev@googlegroups.com
>> *Subject:* Re: Classloading issues between git and git-client plugins?!
>>
>>
>>
>> I have nothing jumping to mind... this looks like something to do with
>> remoting though... in other words the class is failing to load on the
>> remote classloader not Jenkins core's classloader itself which probably
>> points to Kohsuke as the best placed to comment. Robert, you could always
>> open a support ticket if you have a support contract with somebody... ;-)
>>
>>
>>
>> On 7 April 2014 15:57, Mark Waite  wrote:
>>
>> Unfortunately, I don't have any reasonable suggestions for further
>> techniques to debug the classloading issue.  I am hopeful that Kohsuke or
>> Jesse or Stephen have suggestions, since I think classloading is handled
>> deep in core, well below the layers of my comfort.
>>
>>
>>
>> As far as I know, most of the jar file dependencies are "up to date" in
>> the git-client-plugin pom.xml and the git-plugin pom.xml.
>>
>>
>>
>> There are two dependencies intentionally pointed at older versions.  The
>> "guava" dependency is kept at 11.0.01 because Jenkins core keeps its
>> version at 11.0.1.  The multiple-scms dependency is kept at 0.2 because
>> there is a known problem with the multiple-scms plugin 0.3.  Do you have
>> the multiple SCMs plugin installed?  Is it enabled?  Are you using it?
>>
>>
>>
>> Mark Waite
>>
>>
>>
>> Mark Waite
>>
>>
>>
>> On Mon, Apr 7, 2014 at 8:44 AM, Sandell, Robert <
>> robert.sand...@sonymobile.com> wrote:
>>
>> Yes those look like similar issues.
>>
>> Any thoughts on how I can continue to debug the issue?
>>
>> Few jobs on the currently affected masters use the git plugin, so I can
>> keep them alive for a little bit more before I need to take drastic
>> measures.
>>
>>
>>
>>
>>
>>
>>
>> *Robert Sandell*
>>
>> *Sony Mobile Communications*
>>
>> Tel: +46 10 80 12721
>>
>> sonymobile.com
>>
>>
>>
>> *From:* jenkinsci-dev@googlegroups.com [mailto:
>> jenkinsci-dev@googlegroups.com] *On Behalf Of *Mark Waite
>> *Sent:* den 4 april 2014 04:38
>> *To:* jenkinsci-dev@googlegroups.com
>> *Subject:* Re: Classloading issues between git and git-client plugins?!
>>
>>
>>
>> In case it helps, https://issues.jenkins-ci.org/browse/JENKINS-21520reports 
>> something similar, though the investigation there has not shown any
>> way to repeat the bug.
>>
>>
>>
>> Likewise https://issues.jenkins-ci.org/browse/JENKINS-20254 seems to be
>> in a similar area.
>>
>>
>>
>> On Thu, Apr 3, 2014 at 9:19 AM, Mark Waite 
>> wrote:
>>
>> It's the credentials plugin installed, and current, and enabled?
>>
>> There have been other reports of a class loader failure, but we have not
>> been able to duplicate them.
>>
>> On Apr 3, 2014 9:00 AM, "Sandell, Robert" 
>> wrote:
>>
>> Onto my next post LTS upgrade problem.
>>
>>
>>
>> Suddenly we see this stacktrace in build logs when the git plugin is
>> fetching from the repository.
>>
>>
>>
>> Caused by: java.lang.NoClassDefFoundError:
>> org.jenkinsci.plugins.gitclient.GitClient
>>
>>  at java.lang.Class.getDeclaredFields0(Native Method)
>>
>>  at java.lang.Class.privateGetDeclaredFields(Class.java:2397)
>>
>>  at java.lang.Class.getDeclaredField(Class.java:1946)
>>
>>  at
>> java.io.ObjectStreamClass.getDeclaredSUID(ObjectStreamClass.java:1659)
>>
>>  at
>> java.io.ObjectStreamClass.access$700(ObjectStreamClass.java:72)
>>
>>  at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:480)
>>
>>  at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:468)
>>
>>  at java.security.AccessController.doPrivileged(Native Method)
>>
>>  at java.io.ObjectStreamClass.(ObjectStreamClass.java:468)
>>
>>  at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:365)
>>
>>  at
>> java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:602)
>>
>>  at
>> java.io.ObjectInputStream.readNonP

Re: Backporting for 1.544.1 started

[oliver gondža]

Correction it is 1.554.1.

https://groups.google.com/d/topic/jenkinsci-dev/tpoD0qsucMk/discussion
--
oliver

--
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.

Backporting for 1.554.1 started

[oliver gondža]

Hi,

Backporting window for next LTS now opened. The RC will be published on  
2014-04-16.


--
oliver

--
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.

Backporting for 1.544.1 started

[oliver gondža]

Hi,

Backporting window for next LTS now opened. The RC will be published on  
2014-04-16.


--
oliver

--
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: Classloading issues between git and git-client plugins?!

[Stephen Connolly]

because the channel is not hooked up to the überclassloader somehow... so
when the class is called for on the remote end, it doesn't show up. I
suspect some of the perf improvements in classloading are hitting long
running slaves. If my theory is correct disconnecting and reconnecting the
slave in question should clear the issue.


On 7 April 2014 16:51, Sandell, Robert wrote:

> The only support contract I have is myself and my groovy script console J
>
>
>
> What baffles me is that the uberClassLoader can load the class, but the
> build fails to.
>
>
>
>
>
>
>
> *Robert Sandell*
>
> *Sony Mobile Communications*
>
> Tel: +46 10 80 12721
>
> sonymobile.com
>
>
>
> *From:* jenkinsci-dev@googlegroups.com [mailto:
> jenkinsci-dev@googlegroups.com] *On Behalf Of *Stephen Connolly
> *Sent:* den 7 april 2014 17:05
>
> *To:* jenkinsci-dev@googlegroups.com
> *Subject:* Re: Classloading issues between git and git-client plugins?!
>
>
>
> I have nothing jumping to mind... this looks like something to do with
> remoting though... in other words the class is failing to load on the
> remote classloader not Jenkins core's classloader itself which probably
> points to Kohsuke as the best placed to comment. Robert, you could always
> open a support ticket if you have a support contract with somebody... ;-)
>
>
>
> On 7 April 2014 15:57, Mark Waite  wrote:
>
> Unfortunately, I don't have any reasonable suggestions for further
> techniques to debug the classloading issue.  I am hopeful that Kohsuke or
> Jesse or Stephen have suggestions, since I think classloading is handled
> deep in core, well below the layers of my comfort.
>
>
>
> As far as I know, most of the jar file dependencies are "up to date" in
> the git-client-plugin pom.xml and the git-plugin pom.xml.
>
>
>
> There are two dependencies intentionally pointed at older versions.  The
> "guava" dependency is kept at 11.0.01 because Jenkins core keeps its
> version at 11.0.1.  The multiple-scms dependency is kept at 0.2 because
> there is a known problem with the multiple-scms plugin 0.3.  Do you have
> the multiple SCMs plugin installed?  Is it enabled?  Are you using it?
>
>
>
> Mark Waite
>
>
>
> Mark Waite
>
>
>
> On Mon, Apr 7, 2014 at 8:44 AM, Sandell, Robert <
> robert.sand...@sonymobile.com> wrote:
>
> Yes those look like similar issues.
>
> Any thoughts on how I can continue to debug the issue?
>
> Few jobs on the currently affected masters use the git plugin, so I can
> keep them alive for a little bit more before I need to take drastic
> measures.
>
>
>
>
>
>
>
> *Robert Sandell*
>
> *Sony Mobile Communications*
>
> Tel: +46 10 80 12721
>
> sonymobile.com
>
>
>
> *From:* jenkinsci-dev@googlegroups.com [mailto:
> jenkinsci-dev@googlegroups.com] *On Behalf Of *Mark Waite
> *Sent:* den 4 april 2014 04:38
> *To:* jenkinsci-dev@googlegroups.com
> *Subject:* Re: Classloading issues between git and git-client plugins?!
>
>
>
> In case it helps, https://issues.jenkins-ci.org/browse/JENKINS-21520reports 
> something similar, though the investigation there has not shown any
> way to repeat the bug.
>
>
>
> Likewise https://issues.jenkins-ci.org/browse/JENKINS-20254 seems to be
> in a similar area.
>
>
>
> On Thu, Apr 3, 2014 at 9:19 AM, Mark Waite 
> wrote:
>
> It's the credentials plugin installed, and current, and enabled?
>
> There have been other reports of a class loader failure, but we have not
> been able to duplicate them.
>
> On Apr 3, 2014 9:00 AM, "Sandell, Robert" 
> wrote:
>
> Onto my next post LTS upgrade problem.
>
>
>
> Suddenly we see this stacktrace in build logs when the git plugin is
> fetching from the repository.
>
>
>
> Caused by: java.lang.NoClassDefFoundError:
> org.jenkinsci.plugins.gitclient.GitClient
>
>  at java.lang.Class.getDeclaredFields0(Native Method)
>
>  at java.lang.Class.privateGetDeclaredFields(Class.java:2397)
>
>  at java.lang.Class.getDeclaredField(Class.java:1946)
>
>  at
> java.io.ObjectStreamClass.getDeclaredSUID(ObjectStreamClass.java:1659)
>
>  at java.io.ObjectStreamClass.access$700(ObjectStreamClass.java:72)
>
>  at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:480)
>
>  at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:468)
>
>  at java.security.AccessController.doPrivileged(Native Method)
>
>  at java.io.ObjectStreamClass.(ObjectStreamClass.java:468)
>
>  at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:365)
>
>  at
> java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:602)
>
>  at
> java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1622)
>
>  at
> java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1517)
>
>  at
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1771)
>
>  at
> java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
>
>  at
> java.io.ObjectInputStream.readObject(ObjectInputSt

RE: Classloading issues between git and git-client plugins?!

[Sandell, Robert]

The only support contract I have is myself and my groovy script console :)

What baffles me is that the uberClassLoader can load the class, but the build 
fails to.



Robert Sandell
Sony Mobile Communications
Tel: +46 10 80 12721
sonymobile.com

From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On 
Behalf Of Stephen Connolly
Sent: den 7 april 2014 17:05
To: jenkinsci-dev@googlegroups.com
Subject: Re: Classloading issues between git and git-client plugins?!

I have nothing jumping to mind... this looks like something to do with remoting 
though... in other words the class is failing to load on the remote classloader 
not Jenkins core's classloader itself which probably points to Kohsuke as 
the best placed to comment. Robert, you could always open a support ticket if 
you have a support contract with somebody... ;-)

On 7 April 2014 15:57, Mark Waite 
mailto:mark.earl.wa...@gmail.com>> wrote:
Unfortunately, I don't have any reasonable suggestions for further techniques 
to debug the classloading issue.  I am hopeful that Kohsuke or Jesse or Stephen 
have suggestions, since I think classloading is handled deep in core, well 
below the layers of my comfort.

As far as I know, most of the jar file dependencies are "up to date" in the 
git-client-plugin pom.xml and the git-plugin pom.xml.

There are two dependencies intentionally pointed at older versions.  The 
"guava" dependency is kept at 11.0.01 because Jenkins core keeps its version at 
11.0.1.  The multiple-scms dependency is kept at 0.2 because there is a known 
problem with the multiple-scms plugin 0.3.  Do you have the multiple SCMs 
plugin installed?  Is it enabled?  Are you using it?

Mark Waite

Mark Waite

On Mon, Apr 7, 2014 at 8:44 AM, Sandell, Robert 
mailto:robert.sand...@sonymobile.com>> wrote:
Yes those look like similar issues.
Any thoughts on how I can continue to debug the issue?
Few jobs on the currently affected masters use the git plugin, so I can keep 
them alive for a little bit more before I need to take drastic measures.



Robert Sandell
Sony Mobile Communications
Tel: +46 10 80 12721
sonymobile.com

From: jenkinsci-dev@googlegroups.com 
[mailto:jenkinsci-dev@googlegroups.com] 
On Behalf Of Mark Waite
Sent: den 4 april 2014 04:38
To: jenkinsci-dev@googlegroups.com
Subject: Re: Classloading issues between git and git-client plugins?!

In case it helps, https://issues.jenkins-ci.org/browse/JENKINS-21520 reports 
something similar, though the investigation there has not shown any way to 
repeat the bug.

Likewise https://issues.jenkins-ci.org/browse/JENKINS-20254 seems to be in a 
similar area.

On Thu, Apr 3, 2014 at 9:19 AM, Mark Waite 
mailto:mark.earl.wa...@gmail.com>> wrote:

It's the credentials plugin installed, and current, and enabled?

There have been other reports of a class loader failure, but we have not been 
able to duplicate them.
On Apr 3, 2014 9:00 AM, "Sandell, Robert" 
mailto:robert.sand...@sonymobile.com>> wrote:
Onto my next post LTS upgrade problem.

Suddenly we see this stacktrace in build logs when the git plugin is fetching 
from the repository.

Caused by: java.lang.NoClassDefFoundError: 
org.jenkinsci.plugins.gitclient.GitClient
 at java.lang.Class.getDeclaredFields0(Native Method)
 at java.lang.Class.privateGetDeclaredFields(Class.java:2397)
 at java.lang.Class.getDeclaredField(Class.java:1946)
 at 
java.io.ObjectStreamClass.getDeclaredSUID(ObjectStreamClass.java:1659)
 at java.io.ObjectStreamClass.access$700(ObjectStreamClass.java:72)
 at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:480)
 at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:468)
 at java.security.AccessController.doPrivileged(Native Method)
 at java.io.ObjectStreamClass.(ObjectStreamClass.java:468)
 at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:365)
 at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:602)
 at 
java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1622)
 at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1517)
 at 
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1771)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
 at hudson.remoting.UserRequest.deserialize(UserRequest.java:182)
 at hudson.remoting.UserResponse.retrieve(UserRequest.java:211)
 at hudson.remoting.Channel.call(Channel.java:723)

A similar stacktrace if we try to run the build on the master instead.

We got this problem at one time when we first upgraded (everything), my first 
guess was that it was because of some library changes in git-c

Re: Unable to publish Jenkins plugin - cloudtest-plugin

[Mukul Sharma]

Thank you very much Mark, worked like a charm!!

Mukul

On Saturday, April 5, 2014 6:37:40 PM UTC-7, Mark Adamcin wrote:
>
> Yes. You are currently inheriting the entire build section from the 
> jenkins parent pom. It should be okay to add the following to your pom, 
> after the pluginRepositories section:
>
> 
> 
> 
> org.apache.maven.plugins
> maven-release-plugin
> 2.5
> 
> 
> 
> 
>
> Mark Adamcin
> http://adamcin.net/
>
>
> On Sat, Apr 5, 2014 at 1:19 PM, Mukul Sharma 
> 
> > wrote:
>
>> Thanks a lot Tom and Mark,
>>
>> Tom, your commands seem to have worked (It checked in the pom.xml changes 
>> correctly). The published plugin hasn't showed up in the update-center.json 
>> yet but I'll recheck in a few hours.
>>
>> Mark, I couldn't find a section for maven-plugin version in my pom.xml.
>>
>> This is what it looks like - 
>>
>> http://maven.apache.org/POM/4.0.0"; xmlns:xsi="
>> http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="
>> http://maven.apache.org/POM/4.0.0 
>> http://maven.apache.org/maven-v4_0_0.xsd";>
>>   4.0.0
>>   
>> org.jenkins-ci.plugins
>> plugin
>> 1.447
>>   
>>
>>   com.soasta.jenkins
>>   cloudtest
>>   2.13-SNAPSHOT
>>   hpi
>>   SOASTA CloudTest Plugin
>>   
>> https://wiki.jenkins-ci.org/display/JENKINS/SOASTA+CloudTest+Plugin
>>
>>   
>> scm:git:ssh://github.com/jenkinsci/cloudtest-plugin.git
>> 
>> scm:git:ssh://
>> g...@github.com/jenkinsci/cloudtest-plugin.git
>> https://github.com/jenkinsci/cloudtest-plugin
>> HEAD
>>   
>>
>>   
>> 
>>   msolnit
>>   Matt Solnit
>> 
>> 
>>   kohsuke
>>   Kohsuke Kawaguchi
>> 
>>   
>>
>>   
>>   
>> 
>>   repo.jenkins-ci.org
>>   http://repo.jenkins-ci.org/public/
>> 
>>   
>>
>>   
>> 
>>   repo.jenkins-ci.org
>>   http://repo.jenkins-ci.org/public/
>> 
>>   
>> 
>>
>> Can you point me to the right location?
>>
>> Thanks,
>> Mukul
>>
>> On Friday, April 4, 2014 4:15:14 PM UTC-7, Mukul Sharma wrote:
>>>
>>>  Hello,
>>>
>>> I've been trying to publish the latest version of cloudtest-plugin (
>>> https://wiki.jenkins-ci.org/display/JENKINS/SOASTA+CloudTest+Plugin) 
>>> for the past few days but its not working.
>>>
>>> Maven is not checking in any changes to pom.xml file.
>>>
>>> Also, even though the process seems to be successful, the plugin never 
>>> makes it to the server.
>>>
>>> I've attached the log files. Can someone please take a look and let me 
>>> know whats wrong?
>>>
>>> Thanks,
>>>
>>> Mukul
>>>
>>  -- 
>> 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 .
>> 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: Classloading issues between git and git-client plugins?!

[Stephen Connolly]

I have nothing jumping to mind... this looks like something to do with
remoting though... in other words the class is failing to load on the
remote classloader not Jenkins core's classloader itself which probably
points to Kohsuke as the best placed to comment. Robert, you could always
open a support ticket if you have a support contract with somebody... ;-)


On 7 April 2014 15:57, Mark Waite  wrote:

> Unfortunately, I don't have any reasonable suggestions for further
> techniques to debug the classloading issue.  I am hopeful that Kohsuke or
> Jesse or Stephen have suggestions, since I think classloading is handled
> deep in core, well below the layers of my comfort.
>
> As far as I know, most of the jar file dependencies are "up to date" in
> the git-client-plugin pom.xml and the git-plugin pom.xml.
>
> There are two dependencies intentionally pointed at older versions.  The
> "guava" dependency is kept at 11.0.01 because Jenkins core keeps its
> version at 11.0.1.  The multiple-scms dependency is kept at 0.2 because
> there is a known problem with the multiple-scms plugin 0.3.  Do you have
> the multiple SCMs plugin installed?  Is it enabled?  Are you using it?
>
> Mark Waite
>
> Mark Waite
>
>
> On Mon, Apr 7, 2014 at 8:44 AM, Sandell, Robert <
> robert.sand...@sonymobile.com> wrote:
>
>> Yes those look like similar issues.
>>
>> Any thoughts on how I can continue to debug the issue?
>>
>> Few jobs on the currently affected masters use the git plugin, so I can
>> keep them alive for a little bit more before I need to take drastic
>> measures.
>>
>>
>>
>>
>>
>>
>>
>> *Robert Sandell*
>>
>> *Sony Mobile Communications*
>>
>> Tel: +46 10 80 12721
>>
>> sonymobile.com
>>
>>
>>
>> *From:* jenkinsci-dev@googlegroups.com [mailto:
>> jenkinsci-dev@googlegroups.com] *On Behalf Of *Mark Waite
>> *Sent:* den 4 april 2014 04:38
>> *To:* jenkinsci-dev@googlegroups.com
>> *Subject:* Re: Classloading issues between git and git-client plugins?!
>>
>>
>>
>> In case it helps, https://issues.jenkins-ci.org/browse/JENKINS-21520reports 
>> something similar, though the investigation there has not shown any
>> way to repeat the bug.
>>
>>
>>
>> Likewise https://issues.jenkins-ci.org/browse/JENKINS-20254 seems to be
>> in a similar area.
>>
>>
>>
>> On Thu, Apr 3, 2014 at 9:19 AM, Mark Waite 
>> wrote:
>>
>> It's the credentials plugin installed, and current, and enabled?
>>
>> There have been other reports of a class loader failure, but we have not
>> been able to duplicate them.
>>
>> On Apr 3, 2014 9:00 AM, "Sandell, Robert" 
>> wrote:
>>
>> Onto my next post LTS upgrade problem.
>>
>>
>>
>> Suddenly we see this stacktrace in build logs when the git plugin is
>> fetching from the repository.
>>
>>
>>
>> Caused by: java.lang.NoClassDefFoundError:
>> org.jenkinsci.plugins.gitclient.GitClient
>>
>>  at java.lang.Class.getDeclaredFields0(Native Method)
>>
>>  at java.lang.Class.privateGetDeclaredFields(Class.java:2397)
>>
>>  at java.lang.Class.getDeclaredField(Class.java:1946)
>>
>>  at
>> java.io.ObjectStreamClass.getDeclaredSUID(ObjectStreamClass.java:1659)
>>
>>  at
>> java.io.ObjectStreamClass.access$700(ObjectStreamClass.java:72)
>>
>>  at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:480)
>>
>>  at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:468)
>>
>>  at java.security.AccessController.doPrivileged(Native Method)
>>
>>  at java.io.ObjectStreamClass.(ObjectStreamClass.java:468)
>>
>>  at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:365)
>>
>>  at
>> java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:602)
>>
>>  at
>> java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1622)
>>
>>  at
>> java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1517)
>>
>>  at
>> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1771)
>>
>>  at
>> java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
>>
>>  at
>> java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
>>
>>  at hudson.remoting.UserRequest.deserialize(UserRequest.java:182)
>>
>>  at hudson.remoting.UserResponse.retrieve(UserRequest.java:211)
>>
>>  at hudson.remoting.Channel.call(Channel.java:723)
>>
>>
>>
>> A similar stacktrace if we try to run the build on the master instead.
>>
>>
>>
>> We got this problem at one time when we first upgraded (everything), my
>> first guess was that it was because of some library changes in git-client
>> so we cleaned up some old hpi and jpi files and installed the previous
>> micro version of git and git client, started Jenkins and it worked again.
>>
>> The other servers didn't have the problem when we upgraded them. But
>> suddenly yesterday it happened in runtime. On Monday the git plugin worked
>> and on Tuesday it didn't.
>>
>>
>>
>> I've tried some Groovy debugging with the 

Re: Classloading issues between git and git-client plugins?!

[Mark Waite]

Unfortunately, I don't have any reasonable suggestions for further
techniques to debug the classloading issue.  I am hopeful that Kohsuke or
Jesse or Stephen have suggestions, since I think classloading is handled
deep in core, well below the layers of my comfort.

As far as I know, most of the jar file dependencies are "up to date" in the
git-client-plugin pom.xml and the git-plugin pom.xml.

There are two dependencies intentionally pointed at older versions.  The
"guava" dependency is kept at 11.0.01 because Jenkins core keeps its
version at 11.0.1.  The multiple-scms dependency is kept at 0.2 because
there is a known problem with the multiple-scms plugin 0.3.  Do you have
the multiple SCMs plugin installed?  Is it enabled?  Are you using it?

Mark Waite

Mark Waite


On Mon, Apr 7, 2014 at 8:44 AM, Sandell, Robert <
robert.sand...@sonymobile.com> wrote:

> Yes those look like similar issues.
>
> Any thoughts on how I can continue to debug the issue?
>
> Few jobs on the currently affected masters use the git plugin, so I can
> keep them alive for a little bit more before I need to take drastic
> measures.
>
>
>
>
>
>
>
> *Robert Sandell*
>
> *Sony Mobile Communications*
>
> Tel: +46 10 80 12721
>
> sonymobile.com
>
>
>
> *From:* jenkinsci-dev@googlegroups.com [mailto:
> jenkinsci-dev@googlegroups.com] *On Behalf Of *Mark Waite
> *Sent:* den 4 april 2014 04:38
> *To:* jenkinsci-dev@googlegroups.com
> *Subject:* Re: Classloading issues between git and git-client plugins?!
>
>
>
> In case it helps, https://issues.jenkins-ci.org/browse/JENKINS-21520reports 
> something similar, though the investigation there has not shown any
> way to repeat the bug.
>
>
>
> Likewise https://issues.jenkins-ci.org/browse/JENKINS-20254 seems to be
> in a similar area.
>
>
>
> On Thu, Apr 3, 2014 at 9:19 AM, Mark Waite 
> wrote:
>
> It's the credentials plugin installed, and current, and enabled?
>
> There have been other reports of a class loader failure, but we have not
> been able to duplicate them.
>
> On Apr 3, 2014 9:00 AM, "Sandell, Robert" 
> wrote:
>
> Onto my next post LTS upgrade problem.
>
>
>
> Suddenly we see this stacktrace in build logs when the git plugin is
> fetching from the repository.
>
>
>
> Caused by: java.lang.NoClassDefFoundError:
> org.jenkinsci.plugins.gitclient.GitClient
>
>  at java.lang.Class.getDeclaredFields0(Native Method)
>
>  at java.lang.Class.privateGetDeclaredFields(Class.java:2397)
>
>  at java.lang.Class.getDeclaredField(Class.java:1946)
>
>  at
> java.io.ObjectStreamClass.getDeclaredSUID(ObjectStreamClass.java:1659)
>
>  at java.io.ObjectStreamClass.access$700(ObjectStreamClass.java:72)
>
>  at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:480)
>
>  at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:468)
>
>  at java.security.AccessController.doPrivileged(Native Method)
>
>  at java.io.ObjectStreamClass.(ObjectStreamClass.java:468)
>
>  at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:365)
>
>  at
> java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:602)
>
>  at
> java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1622)
>
>  at
> java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1517)
>
>  at
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1771)
>
>  at
> java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
>
>  at
> java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
>
>  at hudson.remoting.UserRequest.deserialize(UserRequest.java:182)
>
>  at hudson.remoting.UserResponse.retrieve(UserRequest.java:211)
>
>  at hudson.remoting.Channel.call(Channel.java:723)
>
>
>
> A similar stacktrace if we try to run the build on the master instead.
>
>
>
> We got this problem at one time when we first upgraded (everything), my
> first guess was that it was because of some library changes in git-client
> so we cleaned up some old hpi and jpi files and installed the previous
> micro version of git and git client, started Jenkins and it worked again.
>
> The other servers didn't have the problem when we upgraded them. But
> suddenly yesterday it happened in runtime. On Monday the git plugin worked
> and on Tuesday it didn't.
>
>
>
> I've tried some Groovy debugging with the following script:
>
>
>
> def gitClient = Jenkins.instance.pluginManager.getPlugin("git-client")
>
>
> println(gitClient.classLoader.findLoadedClass("org.jenkinsci.plugins.gitclient.GitClient"))
>
> //output: interface org.jenkinsci.plugins.gitclient.GitClient
>
>
> println(Jenkins.instance.pluginManager.uberClassLoader.findClass("org.jenkinsci.plugins.gitclient.GitClient"))
>
> //output: interface org.jenkinsci.plugins.gitclient.GitClient
>
>
>
> def gitPlugin = Jenkins.instance.pluginManager.getPlugin("git")
>
> println(gitPlugin.classLoader.findLoadedClass("hudson.plugi

Re: New plugin (poll-mailbox-trigger) Hosting and Repository Request

[Slide]

Hi Nick,

I would assume the nickg username is the one you want to use. Did you setup
settings.xml to have your username and password? There is info on the wiki
for releasing plugins.

Thanks,

Slide
On Apr 7, 2014 7:14 AM, "Nick Grealy"  wrote:

> Hi Slide,
>
> First of all, thank for setting that up!
>
> What credentials should I be using to connect to repo.jenkins-ci.org?
> (I've tried resetting the password for "nickg", "nickgrealy", and my email
> "nickgrealy at gmail dot com", no luck, "credentials not found")
>
> Kind regards,
>
> Nick Grealy
>
> On Monday, 7 April 2014 15:24:45 UTC+10, slide wrote:
>>
>> I forked the repo into the jenkinsci org and added you as a committer
>> [1]. I also created a JIRA component [2] with you as the default assignee.
>> Welcome aboard!
>>
>> slide
>>
>> 1 - https://github.com/jenkinsci/poll-mailbox-trigger-plugin
>> 2 - https://issues.jenkins-ci.org/secure/IssueNavigator.
>> jspa?mode=hide&reset=true&jqlQuery=project+%3D+JENKINS+
>> AND+status+in+%28Open%2C+%22In+Progress%22%2C+Reopened%
>> 29+AND+component+%3D+poll-mailbox-trigger
>>
>>
>> On Fri, Apr 4, 2014 at 4:45 PM, Nick Grealy  wrote:
>>
>>> Hi,
>>>
>>> I'm creating a Jenkins plugin, poll a mailbox and trigger jobs based on
>>> new matching emails.
>>>
>>> Could you please create hosting and fork my github jenkins plugin?
>>>
>>> *Jenkins Plugin Name:* poll-mailbox-trigger
>>> *Current Location:* https://github.com/nickgrealy/poll-mailbox-trigger
>>> *My GitHub User:* nickgrealy
>>> *My JenkinsCI User:* nickg
>>>
>>> Thank you!
>>>
>>> Nick
>>>
>>> --
>>> 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.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Website: http://earl-of-code.com
>>
>  --
> 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: Classloading issues between git and git-client plugins?!

[Sandell, Robert]

Yes those look like similar issues.
Any thoughts on how I can continue to debug the issue?
Few jobs on the currently affected masters use the git plugin, so I can keep 
them alive for a little bit more before I need to take drastic measures.



Robert Sandell
Sony Mobile Communications
Tel: +46 10 80 12721
sonymobile.com

From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On 
Behalf Of Mark Waite
Sent: den 4 april 2014 04:38
To: jenkinsci-dev@googlegroups.com
Subject: Re: Classloading issues between git and git-client plugins?!

In case it helps, https://issues.jenkins-ci.org/browse/JENKINS-21520 reports 
something similar, though the investigation there has not shown any way to 
repeat the bug.

Likewise https://issues.jenkins-ci.org/browse/JENKINS-20254 seems to be in a 
similar area.

On Thu, Apr 3, 2014 at 9:19 AM, Mark Waite 
mailto:mark.earl.wa...@gmail.com>> wrote:

It's the credentials plugin installed, and current, and enabled?

There have been other reports of a class loader failure, but we have not been 
able to duplicate them.
On Apr 3, 2014 9:00 AM, "Sandell, Robert" 
mailto:robert.sand...@sonymobile.com>> wrote:
Onto my next post LTS upgrade problem.

Suddenly we see this stacktrace in build logs when the git plugin is fetching 
from the repository.

Caused by: java.lang.NoClassDefFoundError: 
org.jenkinsci.plugins.gitclient.GitClient
 at java.lang.Class.getDeclaredFields0(Native Method)
 at java.lang.Class.privateGetDeclaredFields(Class.java:2397)
 at java.lang.Class.getDeclaredField(Class.java:1946)
 at 
java.io.ObjectStreamClass.getDeclaredSUID(ObjectStreamClass.java:1659)
 at java.io.ObjectStreamClass.access$700(ObjectStreamClass.java:72)
 at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:480)
 at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:468)
 at java.security.AccessController.doPrivileged(Native Method)
 at java.io.ObjectStreamClass.(ObjectStreamClass.java:468)
 at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:365)
 at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:602)
 at 
java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1622)
 at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1517)
 at 
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1771)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
 at hudson.remoting.UserRequest.deserialize(UserRequest.java:182)
 at hudson.remoting.UserResponse.retrieve(UserRequest.java:211)
 at hudson.remoting.Channel.call(Channel.java:723)

A similar stacktrace if we try to run the build on the master instead.

We got this problem at one time when we first upgraded (everything), my first 
guess was that it was because of some library changes in git-client so we 
cleaned up some old hpi and jpi files and installed the previous micro version 
of git and git client, started Jenkins and it worked again.
The other servers didn't have the problem when we upgraded them. But suddenly 
yesterday it happened in runtime. On Monday the git plugin worked and on 
Tuesday it didn't.

I've tried some Groovy debugging with the following script:

def gitClient = Jenkins.instance.pluginManager.getPlugin("git-client")
println(gitClient.classLoader.findLoadedClass("org.jenkinsci.plugins.gitclient.GitClient"))
//output: interface org.jenkinsci.plugins.gitclient.GitClient
println(Jenkins.instance.pluginManager.uberClassLoader.findClass("org.jenkinsci.plugins.gitclient.GitClient"))
//output: interface org.jenkinsci.plugins.gitclient.GitClient

def gitPlugin = Jenkins.instance.pluginManager.getPlugin("git")
println(gitPlugin.classLoader.findLoadedClass("hudson.plugins.git.GitSCM"))
//output: class hudson.plugins.git.GitSCM
println(Jenkins.instance.pluginManager.uberClassLoader.findClass("hudson.plugins.git.GitSCM"))
//output: class hudson.plugins.git.GitSCM
println(gitPlugin.classLoader.findLoadedClass("org.jenkinsci.plugins.gitclient.GitClient"))
//output: interface org.jenkinsci.plugins.gitclient.GitClient

def job = Jenkins.instance.getItem("Tools_GerritTester")
println(job.getClass().getClassLoader().findLoadedClass("org.jenkinsci.plugins.gitclient.GitClient"))
//output: null
println(job.getClass().getClassLoader().findLoadedClass("hudson.plugins.git.GitSCM"))
//output: null
println(job.getScm().getClass().getClassLoader().findLoadedClass("org.jenkinsci.plugins.gitclient.GitClient"))
//output: interface org.jenkinsci.plugins.gitclient.GitClient


The output is the same whether I run it on a master with the problem or one 
that doesn't have it.

Are there any other classloading scenarios that I've missed, or something else 
I can try to find the issue? I'd prefer to not just reboot and forget ab

Re: New plugin (poll-mailbox-trigger) Hosting and Repository Request

[Nick Grealy]

Hi Slide,

Nevermind, I worked it out. Thank you!

Kind regards,

Nick

On Tuesday, 8 April 2014 00:14:43 UTC+10, Nick Grealy wrote:
>
> Hi Slide,
>
> First of all, thank for setting that up!
>
> What credentials should I be using to connect to repo.jenkins-ci.org? 
> (I've tried resetting the password for "nickg", "nickgrealy", and my email 
> "nickgrealy at gmail dot com", no luck, "credentials not found")
>
> Kind regards,
>
> Nick Grealy
>
> On Monday, 7 April 2014 15:24:45 UTC+10, slide wrote:
>>
>> I forked the repo into the jenkinsci org and added you as a committer 
>> [1]. I also created a JIRA component [2] with you as the default assignee. 
>> Welcome aboard!
>>
>> slide
>>
>> 1 - https://github.com/jenkinsci/poll-mailbox-trigger-plugin
>> 2 - 
>> https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?mode=hide&reset=true&jqlQuery=project+%3D+JENKINS+AND+status+in+%28Open%2C+%22In+Progress%22%2C+Reopened%29+AND+component+%3D+poll-mailbox-trigger
>>
>>
>> On Fri, Apr 4, 2014 at 4:45 PM, Nick Grealy  wrote:
>>
>>> Hi,
>>>
>>> I'm creating a Jenkins plugin, poll a mailbox and trigger jobs based on 
>>> new matching emails.
>>>
>>> Could you please create hosting and fork my github jenkins plugin?
>>>
>>> *Jenkins Plugin Name:* poll-mailbox-trigger
>>> *Current Location:* https://github.com/nickgrealy/poll-mailbox-trigger
>>> *My GitHub User:* nickgrealy
>>> *My JenkinsCI User:* nickg
>>>
>>> Thank you!
>>>
>>> Nick
>>>
>>> -- 
>>> 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.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> -- 
>> Website: http://earl-of-code.com 
>>
>

-- 
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: New plugin (poll-mailbox-trigger) Hosting and Repository Request

[Nick Grealy]

Hi Slide,

First of all, thank for setting that up!

What credentials should I be using to connect to repo.jenkins-ci.org? (I've 
tried resetting the password for "nickg", "nickgrealy", and my email 
"nickgrealy at gmail dot com", no luck, "credentials not found")

Kind regards,

Nick Grealy

On Monday, 7 April 2014 15:24:45 UTC+10, slide wrote:
>
> I forked the repo into the jenkinsci org and added you as a committer [1]. 
> I also created a JIRA component [2] with you as the default assignee. 
> Welcome aboard!
>
> slide
>
> 1 - https://github.com/jenkinsci/poll-mailbox-trigger-plugin
> 2 - 
> https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?mode=hide&reset=true&jqlQuery=project+%3D+JENKINS+AND+status+in+%28Open%2C+%22In+Progress%22%2C+Reopened%29+AND+component+%3D+poll-mailbox-trigger
>
>
> On Fri, Apr 4, 2014 at 4:45 PM, Nick Grealy 
> > wrote:
>
>> Hi,
>>
>> I'm creating a Jenkins plugin, poll a mailbox and trigger jobs based on 
>> new matching emails.
>>
>> Could you please create hosting and fork my github jenkins plugin?
>>
>> *Jenkins Plugin Name:* poll-mailbox-trigger
>> *Current Location:* https://github.com/nickgrealy/poll-mailbox-trigger
>> *My GitHub User:* nickgrealy
>> *My JenkinsCI User:* nickg
>>
>> Thank you!
>>
>> Nick
>>
>> -- 
>> 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 .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Website: http://earl-of-code.com 
>

-- 
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.

New Plugin

[Fabio Douek]

Hi,

I developed a new Jenkins plugin, and I was wondering if I can get commit 
access and a new repo created in jenkinsci. Once the repo is created, if I 
run a maven release, would that be immediately be available in the site 
update, or there is a periodic job to build/publish the plugins from the 
GIT repo?

Plugin name: myst-plugin
Git Hub ID: 7000332
Git Hub User ID: fdouek-rxr
https://github.com/rubiconred/myst-jenkins-plugin

https://wiki.jenkins-ci.org/display/JENKINS/MyST+Plugin

Thanks,

Fabio.



-- 
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: new user / plugin

[Ulli Hafner]

Renamed to https://github.com/jenkinsci/newgen-servers-plugin

Don’t forget to update your refs.

Am 07.04.2014 um 11:45 schrieb Andrius Stasauskas :

> If its only possible to delete this repository and create new one, could you 
> please do that instead ?
> 
> 2014 m. balandis 7 d., pirmadienis 12:44:18 UTC+3, Andrius Stasauskas rašė:
> Ullrich, is it possible to rename this plugin from exigen-servers-plugin to 
> newgen-servers-plugin, by renaming repository also - I would like to avoid 
> conflict to my current workplace and be able to still open source this ?
> 
> 2014 m. balandis 1 d., antradienis 10:02:48 UTC+3, Andrius Stasauskas rašė:
> That totally worked! Thank you :)
> 
> 2014 m. balandis 1 d., antradienis 09:55:57 UTC+3, Ullrich Hafner rašė:
> Please retry.
> 
> Am 01.04.2014 um 08:49 schrieb Andrius Stasauskas :
> 
>> Hm, I have tried to push some changes and got:
>> 
>> git.exe push -v --progress  "origin" master
>> 
>> Pushing to https://github.com/jenkinsci/exigen-servers-plugin
>> remote: Permission to jenkinsci/exigen-servers-plugin.git denied to allstone.
>> fatal: unable to access 
>> 'https://github.com/jenkinsci/exigen-servers-plugin/': The requested URL 
>> returned error: 403
>> 
>> git did not exit cleanly (exit code 128) (8159 ms @ 1/04/2014 9:51:45 a.m.)
>> 
>> Any ideas?
>> 
>> 2013 m. liepa 5 d., penktadienis 13:29:20 UTC+3, Ullrich Hafner rašė:
>> Hi Andrius,
>> 
>> here is your repository:
>> https://github.com/jenkinsci/exigen-servers-plugin
>> 
>> Welcome aboard!
>> 
>> Ulli
>> 
>> Am 04.07.2013 um 15:55 schrieb Andrius Stasauskas :
>> 
>>> hello everyone. I am new to jenkins-dev mailing list, although not new to 
>>> jenkins itself :)
>>> 
>>> now I am following the tutorial in 
>>> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins to post my 
>>> plugin. My github user allstone, github id 4940854 . My plugins name is 
>>> exigen-servers and has exigen-servers.hpi file.
>>> 
>>> I am not sure, but who can give me commit access and create repository 
>>> under jenkinsci in order for me to be able to commit that plugin there?
>>> 
>>> -- 
>>> 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.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>  
>>>  
>> 
>> 
>> -- 
>> 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.
>> 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.



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: new user / plugin

[Andrius Stasauskas]

If its only possible to delete this repository and create new one, could 
you please do that instead ?

2014 m. balandis 7 d., pirmadienis 12:44:18 UTC+3, Andrius Stasauskas rašė:
>
> Ullrich, is it possible to rename this plugin from exigen-servers-plugin 
> to newgen-servers-plugin, by renaming repository also - I would like to 
> avoid conflict to my current workplace and be able to still open source 
> this ?
>
> 2014 m. balandis 1 d., antradienis 10:02:48 UTC+3, Andrius Stasauskas rašė:
>>
>> That totally worked! Thank you :)
>>
>> 2014 m. balandis 1 d., antradienis 09:55:57 UTC+3, Ullrich Hafner rašė:
>>>
>>> Please retry.
>>>
>>> Am 01.04.2014 um 08:49 schrieb Andrius Stasauskas >> >:
>>>
>>> Hm, I have tried to push some changes and got:
>>>
>>> git.exe push -v --progress  "origin" master
>>>
>>> Pushing to https://github.com/jenkinsci/exigen-servers-plugin
>>> remote: Permission to jenkinsci/exigen-servers-plugin.git denied to 
>>> allstone.
>>> fatal: unable to access '
>>> https://github.com/jenkinsci/exigen-servers-plugin/': The requested URL 
>>> returned error: 403
>>>
>>> git did not exit cleanly (exit code 128) (8159 ms @ 1/04/2014 9:51:45 
>>> a.m.)
>>>
>>> Any ideas?
>>>
>>> 2013 m. liepa 5 d., penktadienis 13:29:20 UTC+3, Ullrich Hafner rašė:

 Hi Andrius,

 here is your repository:
 https://github.com/jenkinsci/exigen-servers-plugin

 Welcome aboard!

 Ulli

 Am 04.07.2013 um 15:55 schrieb Andrius Stasauskas >>> >:

 hello everyone. I am new to jenkins-dev mailing list, although not new 
 to jenkins itself :)

 now I am following the tutorial in 
 https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins to post my 
 plugin. My github user allstone, github id 4940854 . My plugins name 
 is exigen-servers and has exigen-servers.hpi file.

 I am not sure, but who can give me commit access and create repository 
 under jenkinsci in order for me to be able to commit that plugin there?

 -- 
 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.
 For more options, visit https://groups.google.com/groups/opt_out.
  
  



>>> -- 
>>> 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.
>>> 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: new user / plugin

[Andrius Stasauskas]

Ullrich, is it possible to rename this plugin from exigen-servers-plugin to 
newgen-servers-plugin, by renaming repository also - I would like to avoid 
conflict to my current workplace and be able to still open source this ?

2014 m. balandis 1 d., antradienis 10:02:48 UTC+3, Andrius Stasauskas rašė:
>
> That totally worked! Thank you :)
>
> 2014 m. balandis 1 d., antradienis 09:55:57 UTC+3, Ullrich Hafner rašė:
>>
>> Please retry.
>>
>> Am 01.04.2014 um 08:49 schrieb Andrius Stasauskas :
>>
>> Hm, I have tried to push some changes and got:
>>
>> git.exe push -v --progress  "origin" master
>>
>> Pushing to https://github.com/jenkinsci/exigen-servers-plugin
>> remote: Permission to jenkinsci/exigen-servers-plugin.git denied to 
>> allstone.
>> fatal: unable to access '
>> https://github.com/jenkinsci/exigen-servers-plugin/': The requested URL 
>> returned error: 403
>>
>> git did not exit cleanly (exit code 128) (8159 ms @ 1/04/2014 9:51:45 
>> a.m.)
>>
>> Any ideas?
>>
>> 2013 m. liepa 5 d., penktadienis 13:29:20 UTC+3, Ullrich Hafner rašė:
>>>
>>> Hi Andrius,
>>>
>>> here is your repository:
>>> https://github.com/jenkinsci/exigen-servers-plugin
>>>
>>> Welcome aboard!
>>>
>>> Ulli
>>>
>>> Am 04.07.2013 um 15:55 schrieb Andrius Stasauskas >> >:
>>>
>>> hello everyone. I am new to jenkins-dev mailing list, although not new 
>>> to jenkins itself :)
>>>
>>> now I am following the tutorial in 
>>> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins to post my 
>>> plugin. My github user allstone, github id 4940854 . My plugins name is 
>>> exigen-servers 
>>> and has exigen-servers.hpi file.
>>>
>>> I am not sure, but who can give me commit access and create repository 
>>> under jenkinsci in order for me to be able to commit that plugin there?
>>>
>>> -- 
>>> 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.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>  
>>>  
>>>
>>>
>>>
>> -- 
>> 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.
>> 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: buildflow release?

[nicolas de loof]

2014-04-07 9:44 GMT+02:00 James Nord (jnord) :

>  Is it time for another release of buildflow plugin?
>
>
>
> There have been numerous fixes/improvements/changes since the last release
> over a year ago[1]
>
>
>
> The only issue I see is that it has broken backwards compatability due to
> the removal of the workspace - but if this is the accepted route it would
> be better to get that out now before too many more people start relying on
> it...
>
>
>
> @Nicolas - I'm happy to cut the release if you don't have time.
>

Please do


>
> /James
>
>
>
> [1]
> https://github.com/jenkinsci/build-flow-plugin/compare/build-flow-plugin-0.10...master
>
> --
> 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.

buildflow release?

[James Nord (jnord)]

Is it time for another release of buildflow plugin?

There have been numerous fixes/improvements/changes since the last release over 
a year ago[1]

The only issue I see is that it has broken backwards compatability due to the 
removal of the workspace - but if this is the accepted route it would be better 
to get that out now before too many more people start relying on it...

@Nicolas - I'm happy to cut the release if you don't have time.

/James

[1] 
https://github.com/jenkinsci/build-flow-plugin/compare/build-flow-plugin-0.10...master

-- 
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: New plugin for Play!Framework

[Ulli Hafner]

I think it makes sense to contact the other author before releasing a different 
plugin. We can still decide what to do after that... 

Am 04.04.2014 um 15:13 schrieb Rafael Ribeiro Rezende :

> Hello all,
> 
> I'm about to finish a plugin to build Play!Framework projects from Jenkins.
> 
> There is already an available implementation from Takafumi Ikeda that hasn't 
> been maintained since some 3 years ago. Play!Framework changed a lot since 
> then and Jenkins have grown up a lot as well. In summary, the plugin doesn't 
> seem to work anymore (at least I didn't manage to make it work without 
> repairing some source code). It uses some deprecated methods as well.
> 
> https://github.com/jenkinsci/play-plugin
> 
> Then, I decided to create a plugin from scratch. It's simpler in terms of 
> implementation, but with a better interface (imo) and structure.
> I plan to contact the Play!Framework community soon to get some better use 
> cases and see how I could improve it a bit more...
> 
> Anyway, my question here is: should I release it to jenkins as a new plugin 
> or should I contact the play-plugin developer and see if I could overwrite it?
> 
> From one hand, it's a complete new code, new project, which could 
> characterise it as a new plugin.
> On the other hand, it provides more o less the functionality of the existing 
> plugin, which is no longer supported and, afaik, broken. (I can be wrong 
> here, ok?)
> So, the next step depends pretty much on the policy of the Jenkins community 
> regarding plugin release.
> 
> Cheers,
> 
> Rafael
> 
> -- 
> 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.



signature.asc
Description: Message signed with OpenPGP using GPGMail