Re: Jira login down?

[R. Tyler Croy]

(replies inline)

On Tue, 09 Feb 2016, matthew.web...@diamond.ac.uk wrote:

> Also down for me ??? attempting to log in generates the message ???Sorry, a 
> communication error occurred while trying to contact the remote 
> authentication server.???


FWIW this has been corrected and I've filed this ticket
(https://issues.jenkins-ci.org/browse/INFRA-560) to help address the gap we had
in process monitoring for LDAp





- R. Tyler Croy

--
 Code: 
  Chatter: 

  % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
--

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/20160209185138.GD17392%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Digital signature

Jenkins and VSphere

[Ginga, Dick]

Hello all, I have been playing with the VSphere plugin for Jenkins and have had 
only limited success. I'm getting a lot of Oops.

I am not interested in creating a VM to be used as a slave. I want to use 
Jenkins to create the VM, install various tools, configure network access, etc. 
has anyone done this?

Dick Ginga, Informatics R
PerkinElmer Inc. | For the Better
HUMAN HEALTH | ENVIRONMENTAL HEALTH
940 Winter Street, Waltham MA 02451

dick.gi...@perkinelmer.com
Mobile - 508-847-1434
Office - 781-663-6947


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E2D86C0F57%40AMERMBX02.PERKINELMER.NET.
For more options, visit https://groups.google.com/d/optout.

Re: Generate pipeline jobs like with job-dsl

[geoffroy . jabouley]

Have a look at the Multijob plugin. This is another way or representing 
Build pipeline, with some nice features to organize your CI.
You can of course generate Multijob projects using JobDSL


Le mardi 9 février 2016 17:52:12 UTC+1, Andrew Bayer a écrit :
>
> You can actually generate Pipeline jobs *with* Job DSL - look for the 
> "workflow" stuff in the Job DSL API Viewer - 
> https://jenkinsci.github.io/job-dsl-plugin/#path/workflowJob
>
> A.
>
> On Tue, Feb 9, 2016 at 3:27 AM, Carlos Lucas  > wrote:
>
>> Hi,
>>
>> Nowadays, we are using a Jenkins with more than 300 different jobs. Most 
>> of them are generated using jobdsl plugin automatically from a config file.
>> Now, I would like to migrate some of them from classic projects to 
>> pipeline projects. 
>>
>> What is the best way to generate pipeline jobs like jobdls? Any kind of 
>> templates?
>>
>> Thank you!
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/764b9495-c2f6-40ad-9e81-190da1c7ba70%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/30691b4b-e745-406a-a0c6-c68992ce605e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Claim plugin has fallen silent

[douglas3457]

Solved!
 
Since commit c2ea74e2a58cddff9219a03ffe261c1f95ea4be5 

 
the claim plugin has included all the Build Failure Analyzer failure causes 
in the generated JavaScript, like this:
 
var json = '{"First cause title":"First failure cause description",
 "Second title":"Second description",
 ...
 }';
 
It is failing to escape any single quotes in the failure cause text, which 
tripped up the browsers' JavaScript parsing. See James Telfer's comment on 
issue JENKINS-28722 

There is a simple work-around: Remove any single quotes from all failure 
cause titles and descriptions.


On Tuesday, February 9, 2016 at 2:25:32 PM UTC+13, dougl...@gmail.com wrote:
>
> Turns out we are suffering a JS error: "ReferenceError: ShowPopup is not 
> defined" when we are clicking on the Claim It link. I'm not sufficiently 
> familiar with JS to be able to find the error in the code (if any) myself - 
> as far as I can see, the function is there.
>
> Presumably, the defect emerged after our restart because that was when we 
> started using the Claim plugin 2.8. Code was added to 
> AbstractClaimBuildAction/summary.jelly in commit 
> c2ea74e2a58cddff9219a03ffe261c1f95ea4be5, to add integration with the Build 
> Failure Analyzer plugin (which we are using). See:
>
>
> https://github.com/jenkinsci/claim-plugin/blob/master/src/main/resources/hudson/plugins/claim/AbstractClaimBuildAction/summary.jelly
>  
>
> https://github.com/jenkinsci/claim-plugin/commit/c2ea74e2a58cddff9219a03ffe261c1f95ea4be5
>
> We have applied the following work-around via Greasemonkey script, just to 
> make the claim "popup" visible at all times. This is simply the content of 
> the (unreachable) ShowPopup() function:
>
> hp = document.getElementById("claimHoverPopup");
> hp.style.display = "block";
>
> Applies equally to Firefox 44.0 (on Linux) and Chromium (on Windows or 
> Linux).
>
>
> On Friday, February 5, 2016 at 5:45:04 PM UTC+13, dougl...@gmail.com 
> wrote:
>>
>> Our Jenkins server suffered a power outage, and since restart, the Claim 
>> plugin has refused to work: Clicking on the "Claim it" link for a failed 
>> job has no visible effect.
>>
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/57636c2d-213b-44a6-834a-7b3edaafc902%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Generate pipeline jobs like with job-dsl

[Carlos Lucas]

Hi,

Nowadays, we are using a Jenkins with more than 300 different jobs. Most of 
them are generated using jobdsl plugin automatically from a config file.
Now, I would like to migrate some of them from classic projects to pipeline 
projects. 

What is the best way to generate pipeline jobs like jobdls? Any kind of 
templates?

Thank you!

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/764b9495-c2f6-40ad-9e81-190da1c7ba70%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: Jira login down?

[Matthew.Webber]

Also down for me – attempting to log in generates the message “Sorry, a 
communication error occurred while trying to contact the remote authentication 
server.”
Matthew Webber

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Jon Schewe
Sent: 09 February 2016 02:16
To: jenkinsci-users
Subject: Jira login down?

I tried logging into Jira today to update a ticket and got
Sorry, a communication error occurred while trying to contact the remote 
authentication server. 
Is anyone else having this problem or is it just me?

Jon



-- 
This e-mail and any attachments may contain confidential, copyright and or 
privileged material, and are for the use of the intended addressee only. If you 
are not the intended addressee or an authorised recipient of the addressee 
please notify us of receipt by returning the e-mail and do not use, copy, 
retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not 
necessarily of Diamond Light Source Ltd. 
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments 
are free from viruses and we cannot accept liability for any damage which you 
may sustain as a result of software viruses which may be transmitted in or with 
the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and 
Wales with its registered office at Diamond House, Harwell Science and 
Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6836E1DC2DDC174C9D64B7860E5AF5FCA90EDCE0%40EXCHMBX01.fed.cclrc.ac.uk.
For more options, visit https://groups.google.com/d/optout.

issues.jenkins-ci.org: No login possible

[David Aldrich]

login to issues.jenkins-ci.org seems to be 
broken:

"Sorry, a communication error occurred while trying to contact the remote 
authentication server."

Best regards

David

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/41302A7145AC054FA7A96CFD03835A0A0BA8D410%40EX10MBX02.EU.NEC.COM.
For more options, visit https://groups.google.com/d/optout.

Jenkins ignores Maven profile properties

[Martijn Hiemstra]

I have a maven project and locally everything perfectly. When I do maven 
tomcat7:redeploy everything works perfectly. When I run that same project 
on Jenkins then the wrong profile properties are loaded. 

This is the situation. In my pom.xml in the build plugins section I have 
this:


org.apache.tomcat.maven
tomcat7-maven-plugin
2.2

${tomcat-server}
${tomcat-url}
${tomcat-context}



In my settings.xml I have this:

  

  tomcat-localhost
  
local.server
http://localhost:8080/manager/text
/MyProject
  


  tomcat-test
  
test.server
http://10.101.55.43:8080/manager/text
/
  

  

in the servers section I have defined the username and passwords for the 
servers. Now I configure my Maven project in Jenkins and in the maven 
section I set this in the goals and options field:

tomcat7:redeploy -P tomcat-test

This means that Jenkins should load the properties of the profile with id 
tomcat-test however when the war file gets uploaded I see this in the job 
console:

Uploading: 
http://localhost:8080/manager/text/deploy?path=%2FMyProject=true

Even though I have clearly indicated that maven should load the tomcat-test 
properties, it loads the tomcat-localhost instead. Outside of Jenkins, 
locally on my machine, it works properly.



-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/3182dd36-d761-42de-ab65-544e742fa131%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Git Plugin Error

[Paulo Moreira]

Thank You Marc ;)

Finally got it running!

So I installed git with OpenSSH and created credentials.

I owe you a beer, and a BIG one!

Cheers,
Paulo M.

segunda-feira, 8 de Fevereiro de 2016 às 17:49:39 UTC, Mark Waite escreveu:
>
> You use the Jenkins credentials system to register a credential with the 
> user name and private key file, then reference that credential from the job 
> definition.
>
> Credentials are defined through "Jenkins" -> "Credentials".  You can then 
> choose to create credentials which are accessible to all jobs, or 
> credentials which are only accessible to jobs whose SCM is using a specific 
> SCM URL (like git://github.com  or g...@bitbucket.org 
>  or https://gitlab.com/ or https://assembla.com/ 
> ), or a specific SCM protocol (like https or ssh or git).
>
> Refer to https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Plugin for 
> more information on credentials.
>
> Mark Waite
>
> On Mon, Feb 8, 2016 at 10:42 AM Paulo Moreira  > wrote:
>
>> Hi Mark,
>>
>> Thank you for the anwser.
>>
>> Ok so I installed git with default openssh but now I get:
>>
>> status code 128:
>> stdout: 
>> stderr: Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).
>> fatal: Could not read from remote repository.
>> How can I add my keys for auto git clone without plink.exe?
>>
>> Thanks
>>
>>
>>
>>
>> sábado, 6 de Fevereiro de 2016 às 23:12:55 UTC, Mark Waite escreveu:
>>
>>> The error message hints that you have chosen to install git for Windows 
>>> to use plink rather than the default openssh authentication system.  The 
>>> simplest solution is probably to reconfigure your git for Windows to use 
>>> openssh rather than plink.
>>>
>>> If you must use plink, you may find helpful instructions on the wiki 
>>> page of the git plugin. 
>>>
>>> Mark Waite
>>>
>>> On Sat, Feb 6, 2016, 4:08 PM Paulo Moreira  wrote:
>>>
>>
 Paulo Moreira
 to mark.earl.waite, nicolas.deloof
 1 day agoDetails
 Dear Jenkins Masters,

 Sorry to bother you but I am strugguling to get the git plugin working 
 under my environment.

 Can you please help?
 I am working on this issue for some days now :(

 Here is my setting:

 Master:
 Jenkins Master under Linux CentOS
- git clone by shell --> Ok
- git plugin --> Ok

 Node:
 Under Windows 7
- git clone by shell --> Ok
- git plugin --> NOK  (and here is my problem)


 Cloning repository ssh://g...@gitlab.xxx.git
  > git init D:\workspace\test_git_newgitlab_win # timeout=10
 Fetching upstream changes from ssh://g...@gitlab.xxx.git
  > git --version # timeout=10
 using GIT_SSH to set credentials
  > git -c core.askpass=true fetch --tags --progress 
 ssh://g...@gitlab.xxx.git +refs/heads/*:refs/remotes/origin/*
 ERROR: Error cloning remote repo 'origin'
 hudson.plugins.git.GitException: Command "git -c core.askpass=true 
 fetch --tags --progress ssh://g...@gitlab.xxx.git 
 +refs/heads/*:refs/remotes/origin/*" returned status code 128:
 stdout:
 stderr: plink: unknown option "-o"
 plink: unknown option "-p"
 fatal: Could not read from remote repository.

 GIT_HOME=D:\Programs\Git\cmd
 HOME=C:\Users\paulomoreira

 PATH=D:\Programs\TortoiseSVN\bin;D:\Programs\PuTTY;D:\Programs\PuTTY;D:\Programs\TortoiseGit\bin;D:\Programs\Git\cmd;D:\Programs\Git\bin

 Jenkins:V 1.639
 Git Client plugin: 1.19.2
 Git plugin: 2.4.2


 I have run out off solutions :(

 --
 You received this message because you are subscribed to the Google 
 Groups "Jenkins Users" group.

>>> To unsubscribe from this group and stop receiving emails from it, send 
 an email to jenkinsci-use...@googlegroups.com.
>>>
>>>
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-users/2d903c70-08ff-4cd3-81a4-4bcdf446cd27%40googlegroups.com
 .
 For more options, visit https://groups.google.com/d/optout.

>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/4aeb0cdc-e9f4-4d2b-800b-cb12651288ba%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.

Re: Generate pipeline jobs like with job-dsl

[Andrew Bayer]

You can actually generate Pipeline jobs *with* Job DSL - look for the
"workflow" stuff in the Job DSL API Viewer -
https://jenkinsci.github.io/job-dsl-plugin/#path/workflowJob

A.

On Tue, Feb 9, 2016 at 3:27 AM, Carlos Lucas 
wrote:

> Hi,
>
> Nowadays, we are using a Jenkins with more than 300 different jobs. Most
> of them are generated using jobdsl plugin automatically from a config file.
> Now, I would like to migrate some of them from classic projects to
> pipeline projects.
>
> What is the best way to generate pipeline jobs like jobdls? Any kind of
> templates?
>
> Thank you!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/764b9495-c2f6-40ad-9e81-190da1c7ba70%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

Question about gerrit trigger - Gerrit Verified Commands

[Zhaobang Liu]

Hi there,

We are trying to add some more automation from jenkins to gerrit. Currently 
our jenkins is sending verified and code review value to gerrit using 
gerrit trigger plugin. It's like
gerrit review , --message 'Build is successful 
' --verified  --code-review 

We want Jenkins be able to merge the code as well. We were expecting that 
we can just do
gerrit review , --message 'Build is successful 
' --verified  --code-review  --submit

However, all of other arguments are working but not --submit. If we do it 
from command line to ssh to gerrit and run gerrit review, the command works.

We took a quick look at the code of gerrit-trigger but it looks like it is 
parsing the message, verified value and code review value but not submit. 
Am I correct?

If you are using gerrit, how do you get code merged? Thanks for sharing the 
information.

Best,
Zhaobang

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/86b34f0d-0753-4c38-a856-e4d022e76b52%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: play-autotest-plugin no longer available

[Rafael Rezende]

Ok.
Could it be caused by the mismatching between the artifactId and the wiki
page Id (if there is such a thing)?

The first maintainer assigned artifactId "play-autotest-plugin", but a wiki
page simply as "play-plugin".

In the Open Issues link I also get an error message: "The value
'play-autotest-plugin' does not exist for the field 'component'."
On Feb 10, 2016 01:47, "Daniel Beck"  wrote:

> We require that every plugin has a wiki page and links to it from the POM.
>
> For some reason, this plugin's wiki page exists and was still rejected. I
> suggest we wait a bit to see whether this resolves itself, otherwise I'll
> need to investigate.
>
> On 08.02.2016, at 10:46, Rafael Rezende  wrote:
>
> > The current release (1.0.0) and the archive pages are unavailable (404
> not found) from the plugin's wiki:
> > https://wiki.jenkins-ci.org/display/JENKINS/play-plugin
> >
> > Archive link:
> > http://updates.jenkins-ci.org/download/plugins/play-autotest-plugin/
> >
> > Current version:
> > http://updates.jenkins-ci.org/latest/play-autotest-plugin.hpi
> >
> > Was this plugin removed/banned? Or is there some misconfiguration?
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Jenkins Users" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to jenkinsci-users+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/f7b5686d-2d48-4e4a-86e7-423cbfe3f7a9%40googlegroups.com
> .
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/N3D0ceIor5M/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/3CAEDE72-4685-404B-9DFB-BD8C21874EA2%40beckweb.net
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: issues.jenkins-ci.org: No login possible

[Daniel Beck]

Should be resolved.

On 09.02.2016, at 07:43, David Aldrich  wrote:

> 
> login to issues.jenkins-ci.org seems to be broken:
>  
> “Sorry, a communication error occurred while trying to contact the remote 
> authentication server.“
>  
> Best regards
>  
> David
>  
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/41302A7145AC054FA7A96CFD03835A0A0BA8D410%40EX10MBX02.EU.NEC.COM.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/B70B6CD9-4120-402C-AA40-0AD76E4B207F%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: play-autotest-plugin no longer available

[Daniel Beck]

We require that every plugin has a wiki page and links to it from the POM.

For some reason, this plugin's wiki page exists and was still rejected. I 
suggest we wait a bit to see whether this resolves itself, otherwise I'll need 
to investigate.

On 08.02.2016, at 10:46, Rafael Rezende  wrote:

> The current release (1.0.0) and the archive pages are unavailable (404 not 
> found) from the plugin's wiki:
> https://wiki.jenkins-ci.org/display/JENKINS/play-plugin
> 
> Archive link:
> http://updates.jenkins-ci.org/download/plugins/play-autotest-plugin/
> 
> Current version:
> http://updates.jenkins-ci.org/latest/play-autotest-plugin.hpi
> 
> Was this plugin removed/banned? Or is there some misconfiguration?
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/f7b5686d-2d48-4e4a-86e7-423cbfe3f7a9%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/3CAEDE72-4685-404B-9DFB-BD8C21874EA2%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: play-autotest-plugin no longer available

[Christopher Orr]

I fixed the "Open issues" link — the component name in JIRA was wrong.

Everything else (aside from the wiki URL in POM) seems fine.

Regards,
Chris

P.S. This mail would have been better suited to the jenkinsci-dev
mailing list :)


On 10/02/16 02:01, Rafael Rezende wrote:
> Ok.
> Could it be caused by the mismatching between the artifactId and the
> wiki page Id (if there is such a thing)?
> 
> The first maintainer assigned artifactId "play-autotest-plugin", but a
> wiki page simply as "play-plugin".
> 
> In the Open Issues link I also get an error message: "The value
> 'play-autotest-plugin' does not exist for the field 'component'."
> 
> On Feb 10, 2016 01:47, "Daniel Beck"  > wrote:
> 
> We require that every plugin has a wiki page and links to it from
> the POM.
> 
> For some reason, this plugin's wiki page exists and was still
> rejected. I suggest we wait a bit to see whether this resolves
> itself, otherwise I'll need to investigate.
> 
> On 08.02.2016 , at 10:46, Rafael Rezende
> > wrote:
> 
> > The current release (1.0.0) and the archive pages are unavailable
> (404 not found) from the plugin's wiki:
> > https://wiki.jenkins-ci.org/display/JENKINS/play-plugin
> >
> > Archive link:
> > http://updates.jenkins-ci.org/download/plugins/play-autotest-plugin/
> >
> > Current version:
> > http://updates.jenkins-ci.org/latest/play-autotest-plugin.hpi
> >
> > Was this plugin removed/banned? Or is there some misconfiguration?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/56BA9D4F.2090408%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: play-autotest-plugin no longer available

[Christopher Orr]

Hi there,

The plugin wiki page was renamed, seemingly in late November, from:
https://wiki.jenkins-ci.org/display/JENKINS/play-plugin?nocache

To:
https://wiki.jenkins-ci.org/display/JENKINS/Play%21+Framework+Plugin

But the POM still points to the old URL that no longer exists:
https://github.com/jenkinsci/play-plugin/blob/play-autotest-plugin-1.0.1/pom.xml#L14

As Daniel mentioned, this means that the plugin won't be included in the
Update Centre because it doesn't have a valid wiki URL:
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-CreatingaWikipage

However, the old wiki page URL *appears* to still exist (without the
"?nocache"), but this is unfortunately due to a known wiki bug:
https://issues.jenkins-ci.org/browse/INFRA-301

Therefore I've submitted a pull request to override the wiki URL for
your plugin temporarily:
https://github.com/jenkinsci/backend-update-center2/pull/39

i.e. if that PR gets merged, your plugin should reappear in the Update
Centre within a few hours.

But please update the  field in your pom.xml (and maybe add a space
to the  field ;), and next time you make a release maybe let us
know, so that we can remove this temporary override.

Regards,
Chris


On 10/02/16 01:47, Daniel Beck wrote:
> We require that every plugin has a wiki page and links to it from the POM.
> 
> For some reason, this plugin's wiki page exists and was still rejected. I 
> suggest we wait a bit to see whether this resolves itself, otherwise I'll 
> need to investigate.
> 
> On 08.02.2016, at 10:46, Rafael Rezende  wrote:
> 
>> The current release (1.0.0) and the archive pages are unavailable (404 not 
>> found) from the plugin's wiki:
>> https://wiki.jenkins-ci.org/display/JENKINS/play-plugin
>>
>> Archive link:
>> http://updates.jenkins-ci.org/download/plugins/play-autotest-plugin/
>>
>> Current version:
>> http://updates.jenkins-ci.org/latest/play-autotest-plugin.hpi
>>
>> Was this plugin removed/banned? Or is there some misconfiguration?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/56BA9C4D.8090708%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Question about gerrit trigger - Gerrit Verified Commands

[Indra Gunawan (ingunawa)]

In one of the team I enabled for Git/Gerrit, we have 1st job that is triggered 
by Gerrit's patchset/changeset upload event.
It reports build status back to Gerrit but we intentionally set the job not to 
give any vote.

Next we have a 2nd job that is triggered by Gerrit's "Comment  is added" event 
where +2 Code-Review is given by reviewer.
This job reports the build status back to Gerrit and give a +1 or -1 Verified 
vote based on build result.

Lastly on Gerrit, we implement comment-added hook where it fires when a comment 
is added;  it checks if +2 CR and +1 Verified are given; if it is then it 
executes Gerrit review command to submit.

From: 
> on 
behalf of Zhaobang Liu 
>
Reply-To: 
"jenkinsci-users@googlegroups.com" 
>
Date: Tuesday, February 9, 2016 at 2:30 PM
To: "jenkinsci-users@googlegroups.com" 
>
Subject: Question about gerrit trigger - Gerrit Verified Commands

Hi there,

We are trying to add some more automation from jenkins to gerrit. Currently our 
jenkins is sending verified and code review value to gerrit using gerrit 
trigger plugin. It's like
gerrit review ,--message 'Build is successful 
'--verified --code-review 

We want Jenkins be able to merge the code as well. We were expecting that we 
can just do
gerrit review ,--message 'Build is successful 
'--verified --code-review --submit

However, all of other arguments are working but not --submit. If we do it from 
command line to ssh to gerrit and run gerrit review, the command works.

We took a quick look at the code of gerrit-trigger but it looks like it is 
parsing the message, verified value and code review value but not submit. Am I 
correct?

If you are using gerrit, how do you get code merged? Thanks for sharing the 
information.

Best,
Zhaobang

--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/86b34f0d-0753-4c38-a856-e4d022e76b52%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/D2E01C6D.45F3C%25ingunawa%40cisco.com.
For more options, visit https://groups.google.com/d/optout.

Are jelly templates supported in email-ext with pipeline

[Rinaldo DiGiorgio]

I am able to use email-ext with pipeline to send emails.  I am trying to 
use jelly templates. I do not see an option for the template processor in 
the following. I tried adding *SCRIPT* to the body.


emailext attachLog: true, body: ' ${SCRIPT, 
template="html/test.groovy"}', subject: 'Test of email', to: 
'someaddr...@somedomain.com'






-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f7ed76fc-7c0d-4b5d-b582-5e39d468809d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.