Re: Trouble releasing a plugin to the directory

[Myles Grant]

Well, alright, thank you.

Here are my changes:
https://github.com/jenkinsci/slack-plugin/commit/28c09a905b936cf259a55d43223090ac3c23f9f8

Unfortunately, it failed:
https://slack-files.com/T024BE7LD-F024KPN92-bd3386/mvn_release_full.txt

What did I do wrong?


On Thu, Dec 12, 2013 at 5:59 PM, Jesse Glick  wrote:

> On Thu, Dec 12, 2013 at 7:08 PM, Myles Grant  wrote:
> > Is there something wrong in my pom.xml?
>
> Delete the distributionManagement, the maven-release-plugin
> configuration, and the groupId and try again.
>
> --
> 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/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-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Legal Question about Writing a Plugin for Proprietary Software

[Chris Wozny]

Hi all,

I would like to write a plugin which executes a build step to compile
a Green Hills Integrity RTOS project using their MULTI compiler. Are
there any legal issues with me writing this plugin since I am in no
way affiliated with Green Hills?

Thanks,
Woz

-- 
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/groups/opt_out.

Re: Trouble releasing a plugin to the directory

[Jesse Glick]

On Thu, Dec 12, 2013 at 7:08 PM, Myles Grant  wrote:
> Is there something wrong in my pom.xml?

Delete the distributionManagement, the maven-release-plugin
configuration, and the groupId and try again.

-- 
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/groups/opt_out.

Trouble releasing a plugin to the directory

[Myles Grant]

Hello,

I recently released a plugin and got jenkins-ci.org hosting. The plugin 
resides at: https://github.com/jenkinsci/slack-plugin

I am trying to get this plugin listed in the directory. The first time I 
did an mvn release, it seemed to work fine, but never showed up in the 
directory in my jenkins install. So after a couple weeks, I did some 
reading, and changed some things in my pom.xml. The output of the most 
recent 'mvn release:prepare release:perform' looks like this:

https://slack-files.com/T024BE7LD-F024KMDQZ-0e3837/mvn_release_full.txt

I don't see anything that would indicate that the plugin won't be released 
to the directory, but I also don't have any confidence that it will.

Last time I did this, I was able to see a build for my plugin go by 
on https://jenkins.ci.cloudbees.com/. This time, I did not see one.

So, questions:

1) Is there something wrong in my pom.xml?
2) Are there obvious errors in my "mvn release" output that indicate the 
plugin release did not work?
3) Is there somewhere I can go to track the release of my plugin to the 
directory to confirm that it worked, and find out why it didn't work if it 
didn't work?

Cheers,
Myles

-- 
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/groups/opt_out.

RE: Beta release of Gerrit Trigger plugin 2.11.0

[James Nord (jnord)]

So I've hand removed those lines from beta2 and the templates are happy.

What's not so happy is the "Use Rest API"  - all I get when I enter a username 
password and try to test is "Connection error : peer not authenticated"
I even tried a user in the Gerrit Administrators group but I still get the same 
response.
The https cert is signed by our internal certificate - but that won't be in the 
Jenkins java trustsore.  Is that a problem - or is it something else?
I've tried both the users ldap password and the Gerrit http password.


/James

From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On 
Behalf Of Mathieu Wang
Sent: 12 December 2013 15:19
To: jenkinsci-dev@googlegroups.com
Cc: 'Mathieu Wang'
Subject: Re: Beta release of Gerrit Trigger plugin 2.11.0

Yes, this variable is not used anywhere, so we can remove the tag safely.

On Thursday, December 12, 2013 4:41:15 AM UTC-5, Robert Sandell wrote:
Actually the GerritTrigger class is quite explicit in its declaration to 
Jenkins that it asserts AbstractProject to be the item it is added to. Whatever 
kind of trickery the template plugin does after that is somewhat beyond its 
control.

On the other hand I did a quick usage search for the trigger variable that is 
being declared on the line where it blows up and couldn't find any.

@Mathew do you think it's safe to remove the  
[mailto:jenkin...@googlegroups.com] On Behalf Of teilo
Sent: den 11 december 2013 17:45
To: jenkin...@googlegroups.com
Subject: Re: Beta release of Gerrit Trigger plugin 2.11.0

sorry trigger happy that should read "from an earlier post 2.10.1 release (aka 
2.10.2-snapshot)"

On Wednesday, 11 December 2013 16:43:32 UTC, teilo wrote:
Not sure this is still the case (as its from an early post but the plugins 
assumptions about project types appears incorrect and results in the following 
error


javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: 
file:/opt/jenkins/data/plugins/gerrit-trigger/WEB-INF/classes/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger/config.jelly:6:68:
  Can't convert 
com.cloudbees.hudson.plugins.modeling.controls.DescriptorListControl@3e0dfca4
 to class hudson.model.AbstractProject



I don't think this is a regression in the Cloudbees templates (although they 
may have been upgraded at similar times).



On Monday, 9 December 2013 18:45:07 UTC, Robert Sandell wrote:
Did some fixes in this area and released 2.11-beta-2


Robert Sandell
Software Tools Engineer - SW Environment and Product Configuration
Sony Mobile Communications

From: jenkin...@googlegroups.com 
[mailto:jenkin...@googlegroups.com] On Behalf Of Sandell, Robert
Sent: den 9 december 2013 16:48
To: jenkin...@googlegroups.com
Subject: RE: Beta release of Gerrit Trigger plugin 2.11.0

Ah,
It's because the server config is retrieved via the serverName field of the 
trigger and not from the provider of the event. I noticed some other places 
where I've missed that particular issue.

I'll start a 2.11-beta branch to work on these.


Robert Sandell
Software Tools Engineer - SW Environment and Product Configuration
Sony Mobile Communications

From: jenkin...@googlegroups.com 
[mailto:jen...@googlegroups.com] On Behalf Of Jyrki Puttonen
Sent: den 7 december 2013 18:00
To: jenkin...@googlegroups.com
Subject: Re: Beta release of Gerrit Trigger plugin 2.11.0

I found out one problem, using "Any Server" prevents Jenkins from reporting 
result to Gerrit. This happens from retriggering, pushing and from the search 
and trigger -page. Log has following line in every case:

Caused by: java.lang.NullPointerException
  at 
com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTrigger.schedule(GerritTrigger.java:531)

At that line, there's


PluginImpl.getInstance().getServer(serverName).getConfig().isGerritBuildCurrentPatchesOnly()

I would guess that getServer return null when "Any Server" is selected. I'm not 
sure what should be done when the returned server is null, so I couldn't fix 
this myself :)



On Sat, Dec 7, 2013 at 3:55 PM, Jyrki Puttonen 
mailto:jyrk...@gmail.com>> wrote:
Hi,

I just installed the beta version, and had few problems.

1. Gerrit configuration was lost, and I had to add a new server.

2. Manual triggering from search didn't work. After following steps and testing 
after everyone it started to work
- I had $GERRIT_REFSPEC as Branch Specifier, changed to $GERRIT_BRANCH
- Changed server from Any Server to specific one
- Touched every field in Project configuration (pattern, branch)
Then it started to work. After it started to work, I changed server back to Any 
Server and Branch Specifier back to $GERRIT_REFSPEC and it seems to be working.

Pushing to gerrit seems to be working, at least after I did those previous 
steps.

I'll keep the

Re: Backports for 1.532.2

[Jesse Glick]

On Wed, Dec 11, 2013 at 5:02 PM, Daniel Beck  wrote:
> JENKINS-16936: This allows use of advanced API features disabled by default

FYI, I have written a plugin exercising this extension point:

https://wiki.jenkins-ci.org/display/JENKINS/Secure+Requester+Whitelist+Plugin

-- 
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/groups/opt_out.

Read the SVN tag in custom plug-in

[nkokkella]

Hi,
i have a requirement to save the build data to database. 
Requirement is to get the tag name being built in java class (custom 
plug-in to develop), 

Is there any simple way to get the tag name into java class.

My class extends Builder class, tried all the ways to get the SVN tag name 
but did not find any way.

Appreciate quick help.

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

Re: New Plugin: Mashup Portlets

[Ullrich Hafner]

You can make the dependency to the dashboard view optional. You can have a
look at the findbugs plugin: here I'm providing some portlet's related to
findbugs. If the user does not install the dashboard view, then the
portlets just not show up, without causing a failure...

Am Donnerstag, 12. Dezember 2013 schrieb Georg Henzler :

> I think we cannot add the sonar portlets to the sonar plugin, because that
> would introduce the dependency to the dashboard plugin (this would mean
> forcing all users of the sonar plugin to install the dashboard plugin).
>
> It would be an option to add the portlets to the dashboard view plugin -
> on the other hand it probably gets at some point a bit monolistic if all
> new portlets form the community end up in the dasboard view itself.
>
> @Peter & Marco: What do you think?
>
> Georg
>
> On Wednesday, December 11, 2013 11:16:57 PM UTC+11, Ullrich Hafner wrote:
>>
>> Wouldn’t it make more sense to add your core portlets to the dashboard
>> view plug-in and add your sonar portlets to the sonar plugin?
>>
>> Ull
>>
>> Am 11.12.2013 um 03:24 schrieb Georg Henzler :
>>
>> Hi all,
>>
>> I've created additional dashboard portlets to extend the
>> https://wiki.jenkins-ci.org/display/JENKINS/Dashboard+View. They are
>> very flexible (especially the Generic JS Portlet), but I have been using
>> them mainly to create a Developer Dashboard that included the following
>> information on one Jenkins page:
>>
>> * CI Build Status (obviously possible by default ;-))
>> * Latest SCM changes (using Recent Changes Portlet)
>> * New Sonar Violations from last night's run (using the Sonar Portlets)
>> * Server Status of DEV/TEST/INT (Deployment Job Status and current actual
>> status using a Nagios-like URL for each server and the Generic JS Portlet
>> to display the info)
>>
>> I believe nothing like this exists already (having checked
>> https://wiki.jenkins-ci.org/display/JENKINS/Plugins) and I'd be happy to
>> push it over to https://github.com/jenkinsci to make it available for
>> everyone.
>>
>> For current source code and more information see
>> https://github.com/ghenzler/jenkins-mashup-portlets
>>
>> Regards
>> Georg
>>
>>
>> --
>> 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-dev+unsubscr...@googlegroups.com  'cvml', 'jenkinsci-dev%2bunsubscr...@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-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Beta release of Gerrit Trigger plugin 2.11.0

[Jesse Glick]

On Thu, Dec 12, 2013 at 4:54 AM, James Nord (jnord)  wrote:
> although the actual job that
> the trigger will be added to will eventually be some form of
> hudson.model.Job

Indeed a FreestyleProject, in the example given.

> when the configuration jelly is called it’s not actually
> the job that’s being configured but the template instance – which isn’t even
> a Hudson.model.Job.

Correct, using JobProperty.getJobOverrides the ./configure binding is replaced.

I think the problematic assumption is that ${it} is a job. You can use
StaplerRequest.findAncestorObject(AbstractProject.class) (checking the
result for null) to find the project being configured. That is, of
course, if you actually need this, though it seems ${trigger} is not
used anyway.

-- 
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/groups/opt_out.

Re: Beta release of Gerrit Trigger plugin 2.11.0

[Mathieu Wang]

Yes, this variable is not used anywhere, so we can remove the tag safely.

On Thursday, December 12, 2013 4:41:15 AM UTC-5, Robert Sandell wrote:
>
> Actually the GerritTrigger class is quite explicit in its declaration to 
> Jenkins that it asserts AbstractProject to be the item it is added to. 
> Whatever kind of trickery the template plugin does after that is somewhat 
> beyond its control.
>
>  
>
> On the other hand I did a quick usage search for the trigger variable that 
> is being declared on the line where it blows up and couldn’t find any.
>
>  
>
> @Mathew do you think it’s safe to remove the  var=”trigger”… tag on line 5 in config.jelly?
>
>  
>
>  
>
> *Robert Sandell*
>
> Software Tools Engineer - SW Environment and Product Configuration
>
> Sony Mobile Communications
>
>  
>
> *From:* jenkin...@googlegroups.com  [mailto:
> jenkin...@googlegroups.com ] *On Behalf Of *teilo
> *Sent:* den 11 december 2013 17:45
> *To:* jenkin...@googlegroups.com 
> *Subject:* Re: Beta release of Gerrit Trigger plugin 2.11.0
>
>  
>
> sorry trigger happy that should read "from an earlier post 2.10.1 release 
> (aka 2.10.2-snapshot)"
>
> On Wednesday, 11 December 2013 16:43:32 UTC, teilo wrote:
>
> Not sure this is still the case (as its from an early post but the plugins 
> assumptions about project types appears incorrect and results in the 
> following error
>
>  
>
> javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: 
> file:/opt/jenkins/data/plugins/gerrit-trigger/WEB-INF/classes/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger/config.jelly:6:68:
>   Can't convert 
> com.cloudbees.hudson.plugins.modeling.controls.DescriptorListControl@3e0dfca4 
>  to class hudson.model.AbstractProject
>
>  
>
> I don't think this is a regression in the Cloudbees templates (although they 
> may have been upgraded at similar times).
>
>  
>
>
> On Monday, 9 December 2013 18:45:07 UTC, Robert Sandell wrote:
>
> Did some fixes in this area and released 2.11-beta-2
>
>  
>
>  
>
> *Robert Sandell*
>
> Software Tools Engineer - SW Environment and Product Configuration
>
> Sony Mobile Communications
>
>  
>
> *From:* jenkin...@googlegroups.com [mailto:jenkin...@googlegroups.com] *On 
> Behalf Of *Sandell, Robert
> *Sent:* den 9 december 2013 16:48
> *To:* jenkin...@googlegroups.com
> *Subject:* RE: Beta release of Gerrit Trigger plugin 2.11.0
>
>  
>
> Ah,
>
> It’s because the server config is retrieved via the serverName field of 
> the trigger and not from the provider of the event. I noticed some other 
> places where I’ve missed that particular issue.
>
>  
>
> I’ll start a 2.11-beta branch to work on these.
>
>  
>
>  
>
> *Robert Sandell*
>
> Software Tools Engineer - SW Environment and Product Configuration
>
> Sony Mobile Communications
>
>  
>
> *From:* jenkin...@googlegroups.com [mailto:jen...@googlegroups.com] *On 
> Behalf Of *Jyrki Puttonen
> *Sent:* den 7 december 2013 18:00
> *To:* jenkin...@googlegroups.com
> *Subject:* Re: Beta release of Gerrit Trigger plugin 2.11.0
>
>  
>
> I found out one problem, using "Any Server" prevents Jenkins from 
> reporting result to Gerrit. This happens from retriggering, pushing and 
> from the search and trigger -page. Log has following line in every case:
>
>  
>
> Caused by: java.lang.NullPointerException
>
>   at 
> com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTrigger.schedule(GerritTrigger.java:531)
>
>  
>
> At that line, there's 
>
>  
>
>   
>   
> PluginImpl.getInstance().getServer(serverName).getConfig().isGerritBuildCurrentPatchesOnly()
>
>  
>
> I would guess that getServer return null when "Any Server" is selected. 
> I'm not sure what should be done when the returned server is null, so I 
> couldn't fix this myself :)
>
>  
>
>  
>
>  
>
> On Sat, Dec 7, 2013 at 3:55 PM, Jyrki Puttonen  wrote:
>
> Hi,
>
>  
>
> I just installed the beta version, and had few problems.
>
>  
>
> 1. Gerrit configuration was lost, and I had to add a new server.
>
>  
>
> 2. Manual triggering from search didn't work. After following steps and 
> testing after everyone it started to work
>
> - I had $GERRIT_REFSPEC as Branch Specifier, changed to $GERRIT_BRANCH
>
> - Changed server from Any Server to specific one
>
> - Touched every field in Project configuration (pattern, branch)
>
> Then it started to work. After it started to work, I changed server back 
> to Any Server and Branch Specifier back to $GERRIT_REFSPEC and it seems to 
> be working.
>
>  
>
> Pushing to gerrit seems to be working, at least after I did those previous 
> steps.
>
>  
>
> I'll keep the beta version running and report if there's other problems.
>
>  
>
> On Thu, Nov 28, 2013 at 5:40 PM, Sandell, Robert <
> robert@sonymobile.com> wrote:
>
> The notify parameter is not something you can set (yet), there is probably 
> still much that can be done to enhance the usage of the REST API.
>
> The only thing that is used fr

Re: New Plugin: Mashup Portlets

[Marco Ambu]

I would definitely suggest adding new portlets as new plugins. Then it's up
to you to categorize them... In your case I see two different plugins, one
for sonar, one for all the others.
My idea would be to have all the portlets out of the main plugin (which
then would contain only the infrastructure).

Marco


On 12 December 2013 13:32, Georg Henzler wrote:

> I think we cannot add the sonar portlets to the sonar plugin, because that
> would introduce the dependency to the dashboard plugin (this would mean
> forcing all users of the sonar plugin to install the dashboard plugin).
>
> It would be an option to add the portlets to the dashboard view plugin -
> on the other hand it probably gets at some point a bit monolistic if all
> new portlets form the community end up in the dasboard view itself.
>
> @Peter & Marco: What do you think?
>
> Georg
>
> On Wednesday, December 11, 2013 11:16:57 PM UTC+11, Ullrich Hafner wrote:
>
>> Wouldn’t it make more sense to add your core portlets to the dashboard
>> view plug-in and add your sonar portlets to the sonar plugin?
>>
>> Ull
>>
>> Am 11.12.2013 um 03:24 schrieb Georg Henzler :
>>
>> Hi all,
>>
>> I've created additional dashboard portlets to extend the
>> https://wiki.jenkins-ci.org/display/JENKINS/Dashboard+View. They are
>> very flexible (especially the Generic JS Portlet), but I have been using
>> them mainly to create a Developer Dashboard that included the following
>> information on one Jenkins page:
>>
>> * CI Build Status (obviously possible by default ;-))
>> * Latest SCM changes (using Recent Changes Portlet)
>> * New Sonar Violations from last night's run (using the Sonar Portlets)
>> * Server Status of DEV/TEST/INT (Deployment Job Status and current actual
>> status using a Nagios-like URL for each server and the Generic JS Portlet
>> to display the info)
>>
>> I believe nothing like this exists already (having checked
>> https://wiki.jenkins-ci.org/display/JENKINS/Plugins) and I'd be happy to
>> push it over to https://github.com/jenkinsci to make it available for
>> everyone.
>>
>> For current source code and more information see
>> https://github.com/ghenzler/jenkins-mashup-portlets
>>
>> Regards
>> Georg
>>
>>
>> --
>> 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-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>



-- 
Marco Ambu
E-mail: marco.a...@gmail.com
LinkedIn profile: 

-- 
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/groups/opt_out.

Re: New Plugin: Mashup Portlets

[Georg Henzler]

I think we cannot add the sonar portlets to the sonar plugin, because that 
would introduce the dependency to the dashboard plugin (this would mean 
forcing all users of the sonar plugin to install the dashboard plugin). 

It would be an option to add the portlets to the dashboard view plugin - on 
the other hand it probably gets at some point a bit monolistic if all new 
portlets form the community end up in the dasboard view itself.

@Peter & Marco: What do you think?

Georg

On Wednesday, December 11, 2013 11:16:57 PM UTC+11, Ullrich Hafner wrote:
>
> Wouldn’t it make more sense to add your core portlets to the dashboard 
> view plug-in and add your sonar portlets to the sonar plugin?
>
> Ull 
>
> Am 11.12.2013 um 03:24 schrieb Georg Henzler 
> 
> >:
>
> Hi all,
>
> I've created additional dashboard portlets to extend the 
> https://wiki.jenkins-ci.org/display/JENKINS/Dashboard+View. They are very 
> flexible (especially the Generic JS Portlet), but I have been using them 
> mainly to create a Developer Dashboard that included the following 
> information on one Jenkins page:
>
> * CI Build Status (obviously possible by default ;-))
> * Latest SCM changes (using Recent Changes Portlet)
> * New Sonar Violations from last night's run (using the Sonar Portlets)
> * Server Status of DEV/TEST/INT (Deployment Job Status and current actual 
> status using a Nagios-like URL for each server and the Generic JS Portlet 
> to display the info)
>
> I believe nothing like this exists already (having checked 
> https://wiki.jenkins-ci.org/display/JENKINS/Plugins) and I'd be happy to 
> push it over to https://github.com/jenkinsci to make it available for 
> everyone.
>
> For current source code and more information see 
> https://github.com/ghenzler/jenkins-mashup-portlets
>
> Regards
> Georg
>
>
> -- 
> 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-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

New plugin:Parameterized Build Queue Decision Handler

[Nicolas Morey-Chaisemartin]

Hi everyone,

I've published a new plugin developed by Kalray on github:
https://github.com/nmorey/parameterized-build-QDH

The goal of this plugin is to be able to merge builds in the build queue if 
they have the same value for a list of specified parameters.
We use a lot of project whose parameter is the git branch to integrate, this 
allows us to merge multiple builds trying to integrate the same branch.

It adds a field in project configuration to list the parameters that should 
match to merge builds. When builds are merged,
the plugin can also concatenate some of the other parameters (ie notification 
email).

I am no Java developer so a lot of things in there are probably done the wrong 
way.
I'd be interested in some feedback if you have any.


Nicolas

--
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/groups/opt_out.

RE: Beta release of Gerrit Trigger plugin 2.11.0

[Sandell, Robert]

I assumed wrongly that the declaration "class GerritTrigger extends 
Trigger" was signal enough to core that it only applied to 
AbstractProject, but upon further inspection I noticed that the descriptor is 
returning true for everything in the isApplicable(Item) method. It should be 
checking for instance of AbstractProject, but then I would definitely break the 
templates.

Any suggestions?
As much of the rest of the code is assuming AbstractProject the check should be 
there, I don't for example want to trigger an entire folder, but at the same 
time the templates are probably nice to have.


Robert Sandell
Software Tools Engineer - SW Environment and Product Configuration
Sony Mobile Communications

From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On 
Behalf Of Stephen Connolly
Sent: den 12 december 2013 10:51
To: jenkinsci-dev@googlegroups.com
Cc: Mathieu Wang
Subject: Re: Beta release of Gerrit Trigger plugin 2.11.0

I can probably construct a literate build job or any multi-branch based project 
job that would blow up if you are assuming that you are always being added to 
an AbstractProject...

On 12 December 2013 09:41, Sandell, Robert 
mailto:robert.sand...@sonymobile.com>> wrote:
Actually the GerritTrigger class is quite explicit in its declaration to 
Jenkins that it asserts AbstractProject to be the item it is added to. Whatever 
kind of trickery the template plugin does after that is somewhat beyond its 
control.

On the other hand I did a quick usage search for the trigger variable that is 
being declared on the line where it blows up and couldn't find any.

@Mathew do you think it's safe to remove the mailto:jenkinsci-dev@googlegroups.com> 
[mailto:jenkinsci-dev@googlegroups.com] 
On Behalf Of teilo
Sent: den 11 december 2013 17:45
To: jenkinsci-dev@googlegroups.com

Subject: Re: Beta release of Gerrit Trigger plugin 2.11.0

sorry trigger happy that should read "from an earlier post 2.10.1 release (aka 
2.10.2-snapshot)"

On Wednesday, 11 December 2013 16:43:32 UTC, teilo wrote:
Not sure this is still the case (as its from an early post but the plugins 
assumptions about project types appears incorrect and results in the following 
error


javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: 
file:/opt/jenkins/data/plugins/gerrit-trigger/WEB-INF/classes/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger/config.jelly:6:68:
  Can't convert 
com.cloudbees.hudson.plugins.modeling.controls.DescriptorListControl@3e0dfca4
 to class hudson.model.AbstractProject



I don't think this is a regression in the Cloudbees templates (although they 
may have been upgraded at similar times).



On Monday, 9 December 2013 18:45:07 UTC, Robert Sandell wrote:
Did some fixes in this area and released 2.11-beta-2


Robert Sandell
Software Tools Engineer - SW Environment and Product Configuration
Sony Mobile Communications

From: jenkin...@googlegroups.com 
[mailto:jenkin...@googlegroups.com] On Behalf Of Sandell, Robert
Sent: den 9 december 2013 16:48
To: jenkin...@googlegroups.com
Subject: RE: Beta release of Gerrit Trigger plugin 2.11.0

Ah,
It's because the server config is retrieved via the serverName field of the 
trigger and not from the provider of the event. I noticed some other places 
where I've missed that particular issue.

I'll start a 2.11-beta branch to work on these.


Robert Sandell
Software Tools Engineer - SW Environment and Product Configuration
Sony Mobile Communications

From: jenkin...@googlegroups.com 
[mailto:jen...@googlegroups.com] On Behalf Of Jyrki Puttonen
Sent: den 7 december 2013 18:00
To: jenkin...@googlegroups.com
Subject: Re: Beta release of Gerrit Trigger plugin 2.11.0

I found out one problem, using "Any Server" prevents Jenkins from reporting 
result to Gerrit. This happens from retriggering, pushing and from the search 
and trigger -page. Log has following line in every case:

Caused by: java.lang.NullPointerException
  at 
com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTrigger.schedule(GerritTrigger.java:531)

At that line, there's


PluginImpl.getInstance().getServer(serverName).getConfig().isGerritBuildCurrentPatchesOnly()

I would guess that getServer return null when "Any Server" is selected. I'm not 
sure what should be done when the returned server is null, so I couldn't fix 
this myself :)



On Sat, Dec 7, 2013 at 3:55 PM, Jyrki Puttonen 
mailto:jyrk...@gmail.com>> wrote:
Hi,

I just installed the beta version, and had few problems.

1. Gerrit configuration was lost, and I had to add a new server.

2. Manual triggering from search didn't work. After following

How to 'commit' the modifications did at Jenkins machine to SVN server

[ranjith kumar]

Hi,

I am using SVN for version controlling and Jenkins for continuous
integration.
I am using a script, on the Jenkins machine only,  to build the PDF files
after building the .sln file.
Now I want to upload these PDF files to SVN server so that everyone would
be able to see the PDF files.

1) In Jenkins, is there any way to do so that the effect of "running  'svn
commit' " would be achieved?
I tried to run "svn commit -m 'committing' " as a MSBuild command
inside Jenkins.
But it gave me the following error. Can someone tell me how to resolve
this issue?
 "
 C:\Program Files (x86)\Jenkins\jobs\myproj\workspace>svn upgrade
svn: E155019: Can't upgrade 'C:\Program Files
(x86)\Jenkins\jobs\myproj\workspace' as it is not a pre-1.7 working copy
directory
svn: E15: Missing default entry

C:\Program Files (x86)\Jenkins\jobs\myproj\workspace>exit 1
Build step 'Execute Windows batch command' marked build as failure
   Sending e-mails to: Ranjith ranj...@google.com
Finished: FAILURE"

2) I dont know how Jenkins is getting working copy from the SVN?
 But it is not equal to running "svn co" !
 That is why I think I got the above error.
Please help me in committing the files at Jenkins server to the svn
server.


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

Re: Beta release of Gerrit Trigger plugin 2.11.0

[Stephen Connolly]

That is correct as I read the template code... but Jesse has spent more
time in the templates plugin and KK wrote it while I was working on the
RBAC plugin... so I usually defer to KK on this plugin


On 12 December 2013 09:54, James Nord (jnord)  wrote:

>  In this case as this is a Cloudbees Template although the actual job
> that the trigger will be added to will eventually be some form of
> hudson.model.Job when the configuration jelly is called it’s not actually
> the job that’s being configured but the template instance – which isn’t
> even a Hudson.model.Job.
>
>
>
> I’m assuming that Stephen will correct me very shortly on this – or weigh
> in with some more information J
>
>
>
> /James
>
>
>
> *From:* jenkinsci-dev@googlegroups.com [mailto:
> jenkinsci-dev@googlegroups.com] *On Behalf Of *Stephen Connolly
> *Sent:* 12 December 2013 09:51
> *To:* jenkinsci-dev@googlegroups.com
> *Cc:* Mathieu Wang
>
> *Subject:* Re: Beta release of Gerrit Trigger plugin 2.11.0
>
>
>
> I can probably construct a literate build job or any multi-branch based
> project job that would blow up if you are assuming that you are always
> being added to an AbstractProject...
>
>
>
> On 12 December 2013 09:41, Sandell, Robert 
> wrote:
>
> Actually the GerritTrigger class is quite explicit in its declaration to
> Jenkins that it asserts AbstractProject to be the item it is added to.
> Whatever kind of trickery the template plugin does after that is somewhat
> beyond its control.
>
>
>
> On the other hand I did a quick usage search for the trigger variable that
> is being declared on the line where it blows up and couldn’t find any.
>
>
>
> @Mathew do you think it’s safe to remove the  var=”trigger”… tag on line 5 in config.jelly?
>
>
>
>
>
> *Robert Sandell*
>
> Software Tools Engineer - SW Environment and Product Configuration
>
> Sony Mobile Communications
>
>
>
> *From:* jenkinsci-dev@googlegroups.com [mailto:
> jenkinsci-dev@googlegroups.com] *On Behalf Of *teilo
> *Sent:* den 11 december 2013 17:45
> *To:* jenkinsci-dev@googlegroups.com
>
>
> *Subject:* Re: Beta release of Gerrit Trigger plugin 2.11.0
>
>
>
> sorry trigger happy that should read "from an earlier post 2.10.1 release
> (aka 2.10.2-snapshot)"
>
> On Wednesday, 11 December 2013 16:43:32 UTC, teilo wrote:
>
> Not sure this is still the case (as its from an early post but the plugins
> assumptions about project types appears incorrect and results in the
> following error
>
>
>
> javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: 
> file:/opt/jenkins/data/plugins/gerrit-trigger/WEB-INF/classes/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger/config.jelly:6:68:
>   Can't convert 
> com.cloudbees.hudson.plugins.modeling.controls.DescriptorListControl@3e0dfca4 
> to class hudson.model.AbstractProject
>
>
>
> I don't think this is a regression in the Cloudbees templates (although they 
> may have been upgraded at similar times).
>
>
>
>
> On Monday, 9 December 2013 18:45:07 UTC, Robert Sandell wrote:
>
> Did some fixes in this area and released 2.11-beta-2
>
>
>
>
>
> *Robert Sandell*
>
> Software Tools Engineer - SW Environment and Product Configuration
>
> Sony Mobile Communications
>
>
>
> *From:* jenkin...@googlegroups.com 
> [mailto:jenkin...@googlegroups.com]
> *On Behalf Of *Sandell, Robert
> *Sent:* den 9 december 2013 16:48
> *To:* jenkin...@googlegroups.com
> *Subject:* RE: Beta release of Gerrit Trigger plugin 2.11.0
>
>
>
> Ah,
>
> It’s because the server config is retrieved via the serverName field of
> the trigger and not from the provider of the event. I noticed some other
> places where I’ve missed that particular issue.
>
>
>
> I’ll start a 2.11-beta branch to work on these.
>
>
>
>
>
> *Robert Sandell*
>
> Software Tools Engineer - SW Environment and Product Configuration
>
> Sony Mobile Communications
>
>
>
> *From:* jenkin...@googlegroups.com 
> [mailto:jen...@googlegroups.com]
> *On Behalf Of *Jyrki Puttonen
> *Sent:* den 7 december 2013 18:00
> *To:* jenkin...@googlegroups.com
> *Subject:* Re: Beta release of Gerrit Trigger plugin 2.11.0
>
>
>
> I found out one problem, using "Any Server" prevents Jenkins from
> reporting result to Gerrit. This happens from retriggering, pushing and
> from the search and trigger -page. Log has following line in every case:
>
>
>
> Caused by: java.lang.NullPointerException
>
>   at
> com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTrigger.schedule(GerritTrigger.java:531)
>
>
>
> At that line, there's
>
>
>
>
>   
> PluginImpl.getInstance().getServer(serverName).getConfig().isGerritBuildCurrentPatchesOnly()
>
>
>
> I would guess that getServer return null when "Any Server" is selected.
> I'm not sure what should be done when the returned server is null, so I
> couldn't fix this myself :)
>
>
>
>
>
>
>
> On Sat, Dec 7, 2013 at 3:55 PM, Jyrki Puttonen  wrote:
>
> Hi,
>
>
>
> I just installed the beta version, and had few problems.
>

Re: Pushing my plugin to GitHub (Newbie)

[Jane King]

Hi Ulli,

Thanks for your help, but still no luck for me.

This is what I get:

C:\...\GitHub\webload-plugin [master]> git push
Warning: Permanently added 'github.com,192.30.252.129' (RSA) to the list of 
known hosts.
ERROR: Permission to jenkinsci/webload-plugin.git denied to jane-king.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository 
exists.

 (I'm using GitHub for Windows, PowerShell shell)
I tried "git push  g...@github.com:jenkinsci/webload-plugin.git master" but 
got same results
Tried "git push  ssh://g...@github.com:jenkinsci/webload-plugin.git master" 
from 
so
.
I tried adding another SSH key also added one without keyphrase, still no 
luck.
I tired the steps in Hosting 
Plugins
 tutorial, 
but got message that repository already exists.
Checked everything else I could find in google  
http://stackoverflow.com/questions/15361398/git-jenkins-scm-plugin-permission-denied
, 
http://jenkins-ci.361315.n4.nabble.com/cannot-access-to-my-own-plugin-repo-td4670471.html

I still don't understand what I'm doing wrong.

  Regards,
 Jane.



On Tuesday, December 10, 2013 11:23:37 AM UTC+2, Ullrich Hafner wrote:
>
> You should push with the user git. Did you already upload a key in GitHub?
> See https://help.github.com/articles/pushing-to-a-remote
>
> Then push with ssh and URL g...@github.com:jenkinsci/webload-plugin.git
>
> Ulli
>
> Am 10.12.2013 um 09:22 schrieb Jane King 
> >:
>
> Hi all,
>
>  
>
> I am not able to push my plugin code to the repository.
>
> I'm new to Git and GitHub, so sorry in advance for the newbie question.
>
>  
>
> I got my repository created at https://github.com/jenkinsci/webload-pluginby 
> Ullrich Hafner (thanks!), and seems like I have been given permissions 
> to use it.
>
>  
>
> This is what I did:
>
> -  Installed 'GitHub for Windows', logged in
>
> -  Cloned the "jenkinsci/webload-plugin" repository
>
> -  Used "Open in explorer"
>
> -  Added some files
>
> -  Committed by changes, so now I have 'unsynced commits'
>
> -  I clicked 'publish' but got an error:
> *"Error – failed to publish this branch"*
>
>  
>
> If I use "Open a shell here" and try "git push", I get:
>
> remote: Permission to jenkinsci/webload-plugin.git denied to jane-king.
>
> fatal: unable to access '
> https://github.com/jenkinsci/webload-plugin.git/': The
>
> requested URL returned error: 403
>
>  
>
> What am I doing wrong?
>
>  
>
>Thanks in advance,
>
>   Jane
>
> -- 
> 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-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

RE: Beta release of Gerrit Trigger plugin 2.11.0

[James Nord (jnord)]

In this case as this is a Cloudbees Template although the actual job that the 
trigger will be added to will eventually be some form of hudson.model.Job when 
the configuration jelly is called it's not actually the job that's being 
configured but the template instance - which isn't even a Hudson.model.Job.

I'm assuming that Stephen will correct me very shortly on this - or weigh in 
with some more information :)

/James

From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On 
Behalf Of Stephen Connolly
Sent: 12 December 2013 09:51
To: jenkinsci-dev@googlegroups.com
Cc: Mathieu Wang
Subject: Re: Beta release of Gerrit Trigger plugin 2.11.0

I can probably construct a literate build job or any multi-branch based project 
job that would blow up if you are assuming that you are always being added to 
an AbstractProject...

On 12 December 2013 09:41, Sandell, Robert 
mailto:robert.sand...@sonymobile.com>> wrote:
Actually the GerritTrigger class is quite explicit in its declaration to 
Jenkins that it asserts AbstractProject to be the item it is added to. Whatever 
kind of trickery the template plugin does after that is somewhat beyond its 
control.

On the other hand I did a quick usage search for the trigger variable that is 
being declared on the line where it blows up and couldn't find any.

@Mathew do you think it's safe to remove the mailto:jenkinsci-dev@googlegroups.com> 
[mailto:jenkinsci-dev@googlegroups.com] 
On Behalf Of teilo
Sent: den 11 december 2013 17:45
To: jenkinsci-dev@googlegroups.com

Subject: Re: Beta release of Gerrit Trigger plugin 2.11.0

sorry trigger happy that should read "from an earlier post 2.10.1 release (aka 
2.10.2-snapshot)"

On Wednesday, 11 December 2013 16:43:32 UTC, teilo wrote:
Not sure this is still the case (as its from an early post but the plugins 
assumptions about project types appears incorrect and results in the following 
error


javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: 
file:/opt/jenkins/data/plugins/gerrit-trigger/WEB-INF/classes/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger/config.jelly:6:68:
  Can't convert 
com.cloudbees.hudson.plugins.modeling.controls.DescriptorListControl@3e0dfca4
 to class hudson.model.AbstractProject



I don't think this is a regression in the Cloudbees templates (although they 
may have been upgraded at similar times).



On Monday, 9 December 2013 18:45:07 UTC, Robert Sandell wrote:
Did some fixes in this area and released 2.11-beta-2


Robert Sandell
Software Tools Engineer - SW Environment and Product Configuration
Sony Mobile Communications

From: jenkin...@googlegroups.com 
[mailto:jenkin...@googlegroups.com] On Behalf Of Sandell, Robert
Sent: den 9 december 2013 16:48
To: jenkin...@googlegroups.com
Subject: RE: Beta release of Gerrit Trigger plugin 2.11.0

Ah,
It's because the server config is retrieved via the serverName field of the 
trigger and not from the provider of the event. I noticed some other places 
where I've missed that particular issue.

I'll start a 2.11-beta branch to work on these.


Robert Sandell
Software Tools Engineer - SW Environment and Product Configuration
Sony Mobile Communications

From: jenkin...@googlegroups.com 
[mailto:jen...@googlegroups.com] On Behalf Of Jyrki Puttonen
Sent: den 7 december 2013 18:00
To: jenkin...@googlegroups.com
Subject: Re: Beta release of Gerrit Trigger plugin 2.11.0

I found out one problem, using "Any Server" prevents Jenkins from reporting 
result to Gerrit. This happens from retriggering, pushing and from the search 
and trigger -page. Log has following line in every case:

Caused by: java.lang.NullPointerException
  at 
com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTrigger.schedule(GerritTrigger.java:531)

At that line, there's


PluginImpl.getInstance().getServer(serverName).getConfig().isGerritBuildCurrentPatchesOnly()

I would guess that getServer return null when "Any Server" is selected. I'm not 
sure what should be done when the returned server is null, so I couldn't fix 
this myself :)



On Sat, Dec 7, 2013 at 3:55 PM, Jyrki Puttonen 
mailto:jyrk...@gmail.com>> wrote:
Hi,

I just installed the beta version, and had few problems.

1. Gerrit configuration was lost, and I had to add a new server.

2. Manual triggering from search didn't work. After following steps and testing 
after everyone it started to work
- I had $GERRIT_REFSPEC as Branch Specifier, changed to $GERRIT_BRANCH
- Changed server from Any Server to specific one
- Touched every field in Project configuration (pattern, branch)
Then it started to work. After it start

Re: Beta release of Gerrit Trigger plugin 2.11.0

[Stephen Connolly]

I can probably construct a literate build job or any multi-branch based
project job that would blow up if you are assuming that you are always
being added to an AbstractProject...


On 12 December 2013 09:41, Sandell, Robert wrote:

> Actually the GerritTrigger class is quite explicit in its declaration to
> Jenkins that it asserts AbstractProject to be the item it is added to.
> Whatever kind of trickery the template plugin does after that is somewhat
> beyond its control.
>
>
>
> On the other hand I did a quick usage search for the trigger variable that
> is being declared on the line where it blows up and couldn’t find any.
>
>
>
> @Mathew do you think it’s safe to remove the  var=”trigger”… tag on line 5 in config.jelly?
>
>
>
>
>
> *Robert Sandell*
>
> Software Tools Engineer - SW Environment and Product Configuration
>
> Sony Mobile Communications
>
>
>
> *From:* jenkinsci-dev@googlegroups.com [mailto:
> jenkinsci-dev@googlegroups.com] *On Behalf Of *teilo
> *Sent:* den 11 december 2013 17:45
> *To:* jenkinsci-dev@googlegroups.com
>
> *Subject:* Re: Beta release of Gerrit Trigger plugin 2.11.0
>
>
>
> sorry trigger happy that should read "from an earlier post 2.10.1 release
> (aka 2.10.2-snapshot)"
>
> On Wednesday, 11 December 2013 16:43:32 UTC, teilo wrote:
>
> Not sure this is still the case (as its from an early post but the plugins
> assumptions about project types appears incorrect and results in the
> following error
>
>
>
> javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: 
> file:/opt/jenkins/data/plugins/gerrit-trigger/WEB-INF/classes/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger/config.jelly:6:68:
>   Can't convert 
> com.cloudbees.hudson.plugins.modeling.controls.DescriptorListControl@3e0dfca4 
> to class hudson.model.AbstractProject
>
>
>
> I don't think this is a regression in the Cloudbees templates (although they 
> may have been upgraded at similar times).
>
>
>
>
> On Monday, 9 December 2013 18:45:07 UTC, Robert Sandell wrote:
>
> Did some fixes in this area and released 2.11-beta-2
>
>
>
>
>
> *Robert Sandell*
>
> Software Tools Engineer - SW Environment and Product Configuration
>
> Sony Mobile Communications
>
>
>
> *From:* jenkin...@googlegroups.com 
> [mailto:jenkin...@googlegroups.com]
> *On Behalf Of *Sandell, Robert
> *Sent:* den 9 december 2013 16:48
> *To:* jenkin...@googlegroups.com
> *Subject:* RE: Beta release of Gerrit Trigger plugin 2.11.0
>
>
>
> Ah,
>
> It’s because the server config is retrieved via the serverName field of
> the trigger and not from the provider of the event. I noticed some other
> places where I’ve missed that particular issue.
>
>
>
> I’ll start a 2.11-beta branch to work on these.
>
>
>
>
>
> *Robert Sandell*
>
> Software Tools Engineer - SW Environment and Product Configuration
>
> Sony Mobile Communications
>
>
>
> *From:* jenkin...@googlegroups.com 
> [mailto:jen...@googlegroups.com]
> *On Behalf Of *Jyrki Puttonen
> *Sent:* den 7 december 2013 18:00
> *To:* jenkin...@googlegroups.com
> *Subject:* Re: Beta release of Gerrit Trigger plugin 2.11.0
>
>
>
> I found out one problem, using "Any Server" prevents Jenkins from
> reporting result to Gerrit. This happens from retriggering, pushing and
> from the search and trigger -page. Log has following line in every case:
>
>
>
> Caused by: java.lang.NullPointerException
>
>   at
> com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTrigger.schedule(GerritTrigger.java:531)
>
>
>
> At that line, there's
>
>
>
>
>   
> PluginImpl.getInstance().getServer(serverName).getConfig().isGerritBuildCurrentPatchesOnly()
>
>
>
> I would guess that getServer return null when "Any Server" is selected.
> I'm not sure what should be done when the returned server is null, so I
> couldn't fix this myself :)
>
>
>
>
>
>
>
> On Sat, Dec 7, 2013 at 3:55 PM, Jyrki Puttonen  wrote:
>
> Hi,
>
>
>
> I just installed the beta version, and had few problems.
>
>
>
> 1. Gerrit configuration was lost, and I had to add a new server.
>
>
>
> 2. Manual triggering from search didn't work. After following steps and
> testing after everyone it started to work
>
> - I had $GERRIT_REFSPEC as Branch Specifier, changed to $GERRIT_BRANCH
>
> - Changed server from Any Server to specific one
>
> - Touched every field in Project configuration (pattern, branch)
>
> Then it started to work. After it started to work, I changed server back
> to Any Server and Branch Specifier back to $GERRIT_REFSPEC and it seems to
> be working.
>
>
>
> Pushing to gerrit seems to be working, at least after I did those previous
> steps.
>
>
>
> I'll keep the beta version running and report if there's other problems.
>
>
>
> On Thu, Nov 28, 2013 at 5:40 PM, Sandell, Robert <
> robert@sonymobile.com> wrote:
>
> The notify parameter is not something you can set (yet), there is probably
> still much that can be done to enhance the usage of the REST API.
>
> The only thing t

RE: Beta release of Gerrit Trigger plugin 2.11.0

[Sandell, Robert]

Actually the GerritTrigger class is quite explicit in its declaration to 
Jenkins that it asserts AbstractProject to be the item it is added to. Whatever 
kind of trickery the template plugin does after that is somewhat beyond its 
control.

On the other hand I did a quick usage search for the trigger variable that is 
being declared on the line where it blows up and couldn't find any.

@Mathew do you think it's safe to remove the mailto:jenkinsci-dev@googlegroups.com] On 
Behalf Of teilo
Sent: den 11 december 2013 17:45
To: jenkinsci-dev@googlegroups.com
Subject: Re: Beta release of Gerrit Trigger plugin 2.11.0

sorry trigger happy that should read "from an earlier post 2.10.1 release (aka 
2.10.2-snapshot)"

On Wednesday, 11 December 2013 16:43:32 UTC, teilo wrote:
Not sure this is still the case (as its from an early post but the plugins 
assumptions about project types appears incorrect and results in the following 
error


javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: 
file:/opt/jenkins/data/plugins/gerrit-trigger/WEB-INF/classes/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger/config.jelly:6:68:
  Can't convert 
com.cloudbees.hudson.plugins.modeling.controls.DescriptorListControl@3e0dfca4
 to class hudson.model.AbstractProject



I don't think this is a regression in the Cloudbees templates (although they 
may have been upgraded at similar times).



On Monday, 9 December 2013 18:45:07 UTC, Robert Sandell wrote:
Did some fixes in this area and released 2.11-beta-2


Robert Sandell
Software Tools Engineer - SW Environment and Product Configuration
Sony Mobile Communications

From: jenkin...@googlegroups.com 
[mailto:jenkin...@googlegroups.com] On Behalf Of Sandell, Robert
Sent: den 9 december 2013 16:48
To: jenkin...@googlegroups.com
Subject: RE: Beta release of Gerrit Trigger plugin 2.11.0

Ah,
It's because the server config is retrieved via the serverName field of the 
trigger and not from the provider of the event. I noticed some other places 
where I've missed that particular issue.

I'll start a 2.11-beta branch to work on these.


Robert Sandell
Software Tools Engineer - SW Environment and Product Configuration
Sony Mobile Communications

From: jenkin...@googlegroups.com 
[mailto:jen...@googlegroups.com] On Behalf Of Jyrki Puttonen
Sent: den 7 december 2013 18:00
To: jenkin...@googlegroups.com
Subject: Re: Beta release of Gerrit Trigger plugin 2.11.0

I found out one problem, using "Any Server" prevents Jenkins from reporting 
result to Gerrit. This happens from retriggering, pushing and from the search 
and trigger -page. Log has following line in every case:

Caused by: java.lang.NullPointerException
  at 
com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTrigger.schedule(GerritTrigger.java:531)

At that line, there's


PluginImpl.getInstance().getServer(serverName).getConfig().isGerritBuildCurrentPatchesOnly()

I would guess that getServer return null when "Any Server" is selected. I'm not 
sure what should be done when the returned server is null, so I couldn't fix 
this myself :)



On Sat, Dec 7, 2013 at 3:55 PM, Jyrki Puttonen 
mailto:jyrk...@gmail.com>> wrote:
Hi,

I just installed the beta version, and had few problems.

1. Gerrit configuration was lost, and I had to add a new server.

2. Manual triggering from search didn't work. After following steps and testing 
after everyone it started to work
- I had $GERRIT_REFSPEC as Branch Specifier, changed to $GERRIT_BRANCH
- Changed server from Any Server to specific one
- Touched every field in Project configuration (pattern, branch)
Then it started to work. After it started to work, I changed server back to Any 
Server and Branch Specifier back to $GERRIT_REFSPEC and it seems to be working.

Pushing to gerrit seems to be working, at least after I did those previous 
steps.

I'll keep the beta version running and report if there's other problems.

On Thu, Nov 28, 2013 at 5:40 PM, Sandell, Robert 
mailto:robert@sonymobile.com>> wrote:
The notify parameter is not something you can set (yet), there is probably 
still much that can be done to enhance the usage of the REST API.
The only thing that is used from the command settings is the contents of the 
message.


Robert Sandell
Software Tools Engineer - SW Environment and Product Configuration
Sony Mobile Communications

From: jenkin...@googlegroups.com 
[mailto:jenkin...@googlegroups.com] On Behalf Of Øyvind Harboe
Sent: den 28 november 2013 10:24
To: jenkin...@googlegroups.com
Cc: jenkins...@googlegroups.com
Subject: Re: Beta release of Gerrit Trigger plugin 2.11

Re: Plug-in to annotate test results

[Vincent Latombe]

I do think the Claim Plugin allows to claim test failures. It's available
as a new option as part of existing test results report actions (Look for
Additional test report features)

Vincent


2013/12/12 Otto P 

> Hi Vincent,
>
> Thanks for the hint - this plugin is a step in the right direction. I'll
> see how far it gets us. Originally I was thinking about something smart
> that reports back in the context of a particular failing test, but simply
> doing it per failed build is already helpful.
>
> Cheers
>
> Otto
>
>
>
> On Wednesday, December 11, 2013 1:34:36 PM UTC+1, Otto P wrote:
>>
>> Pardon if this has been answered before.
>>
>> I am looking for a way to manually annotate test results.
>>
>> The use case: suppose a test fails. You analyze the root cause. The
>> problem is not trivially fixed. So you want to capture your findings
>> somewhere - other than a sticky note or a vague discussion in the hallway.
>> Next day you come in again, you don't quite remember the details of the
>> analysis from the previous day (perhaps there are 100s of tests and a
>> million other things that require your attention). I would like help from
>> Jenkins and pop up the note from yesterday automatically. This until the
>> problem gets resolved.
>>
>> So - in the Jenkins test page, I would like
>> - an "annotation" box that allows me to add free-form text
>> - If the test still fails since, Jenkins to pre-populate this box, or add
>> a little help icon or something, that shows the previous test annotations
>>
>> My question: is there an existing plug-in that does something like this
>> already? If not, and I were to develop my own, any pointers where I should
>> start to do this?
>>
>> 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.
> 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-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Plug-in to annotate test results

[Otto P]

Hi Vincent,

Thanks for the hint - this plugin is a step in the right direction. I'll 
see how far it gets us. Originally I was thinking about something smart 
that reports back in the context of a particular failing test, but simply 
doing it per failed build is already helpful.

Cheers

Otto



On Wednesday, December 11, 2013 1:34:36 PM UTC+1, Otto P wrote:
>
> Pardon if this has been answered before. 
>
> I am looking for a way to manually annotate test results. 
>
> The use case: suppose a test fails. You analyze the root cause. The 
> problem is not trivially fixed. So you want to capture your findings 
> somewhere - other than a sticky note or a vague discussion in the hallway. 
> Next day you come in again, you don't quite remember the details of the 
> analysis from the previous day (perhaps there are 100s of tests and a 
> million other things that require your attention). I would like help from 
> Jenkins and pop up the note from yesterday automatically. This until the 
> problem gets resolved. 
>
> So - in the Jenkins test page, I would like
> - an "annotation" box that allows me to add free-form text
> - If the test still fails since, Jenkins to pre-populate this box, or add 
> a little help icon or something, that shows the previous test annotations
>
> My question: is there an existing plug-in that does something like this 
> already? If not, and I were to develop my own, any pointers where I should 
> start to do this?
>
> 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.
For more options, visit https://groups.google.com/groups/opt_out.