[JIRA] [git-client-plugin] (JENKINS-23091) Git. Problem with encoding in the list changes

2015-01-07 Thread gentoo.inte...@gmail.com (JIRA)














































Kanstantsin Shautsou
 commented on  JENKINS-23091


Git. Problem with encoding in the list changes















What encoding is set for java and what encoding is used in git commits?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [linenumbers-plugin] (JENKINS-26322) Line numbers always '1'

2015-01-07 Thread ol...@icp.uni-stuttgart.de (JIRA)












































  
Olaf Lenz
 edited a comment on  JENKINS-26322


Line numbers always '1'
















The problem seems to be pretty complex.

With your fix, I have seen it work in some circumstances.


	First of all, I'm using Google chrome. With that it now seems to work partly. With IE, that I used for test purposes, it doesn't show any line numbers, only the labels.
	When a log contains empty lines, the line numbers are shown on a single line.
	When the console log is long, a number of problems occurs:
	
		Computing the line numbers takes very long (and sometimes it even seems to kill the browser).
		When only a part of the log is shown (because it is too long to be displayed at once), no line numbers are shown at all.
	
	





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [linenumbers-plugin] (JENKINS-26322) Line numbers always '1'

2015-01-07 Thread ol...@icp.uni-stuttgart.de (JIRA)














































Olaf Lenz
 commented on  JENKINS-26322


Line numbers always '1'















The problem seems to be pretty complex.

With your fix, I have seen it work in some circumstances.


	First of all, I'm using Google chrome. With that it now seems to work partly. With IE, that I used for test purposes, it doesn't show any line numbers, only the labels.
	While the build is running, the line numbers seem to beare botched up
	It seems to work fine when a build has a short console log and the build is finished.




I'm using chrome



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [buildresult-trigger-plugin] (JENKINS-25998) Ad execution schedules generated by BuildResult-Trigger-plugin.

2015-01-07 Thread igna...@albors.ws (JIRA)















































Ignacio Albors
 assigned  JENKINS-25998 to Ignacio Albors



Ad execution schedules generated by BuildResult-Trigger-plugin.
















Change By:


Ignacio Albors
(08/Jan/15 7:18 AM)




Assignee:


Ignacio Albors



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [linenumbers-plugin] (JENKINS-26322) Line numbers always '1'

2015-01-07 Thread ol...@icp.uni-stuttgart.de (JIRA)














































Olaf Lenz
 commented on  JENKINS-26322


Line numbers always '1'















Cool! I will test it now.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


Blue Whale Solution-India Based 6$ an hour any technology

2015-01-07 Thread john9629....@gmail.com




 Hello ,



  I'm john from BlueWhale Solutions formally known as Open wire Solutions
Inc.

We are a Software technology Outsourcing consulting company formed in 2009
and its group founded in 1981, which provides software and manufacturing
services across the globe from textiles to top car manufacturing firms in
India and US.



We have been associated with top fortunes companies like Intel, Boeing,
Ford, Hyundai, Sumi Mother son, Foxconn, Honda Jets USA, Cavin kare, Wells
Forgo, CarMax US, Fannie mae, Penn national insurance ,Tommy Hilfiger,
Levis Clothing Limited US and India. We are headquartered in San Francisco,
California. We have a strong development team of 1100+ Employees in India,
US and Europe. 90% of our workforce is based in East Asia.



Our consulting cost are very less when compared to offshore global price.
Most of the infrastructure is owned by Blue whale solutions. As BWS group
is in the business for more than 31 years which provides service from
manufacturing to software.



Our prices are very competitive in the global market which starts from 6$
an hour which will be a unbelievable consulting cost when its compare to
global costing.



We provide software service at a cost of just 6-25$ an hour for all
technologies.



Some of the core service offerings are



* Web Development - open source development (.Net,PHP, e-commerce, CMS,

Joomla, Word press, Mambo,Magento etc.)



* Sugar CRM and Vtiger CRM



* Sage



* MAS 500



* Quick Books



* Microsoft Dynamics



*Health Care Services



* Mobile Applications (I phone, Android, Blackberry etc.)



* Web 2.0 Technology Design and Development



* Application, Product Development & Maintenance



* Enterprise Business Solutions (SAP, CRM, Oracle, People Soft etc.)



* Business Intelligence & Analytics (Data warehousing, Data mart,

Data Integration etc.)



* Open Source Consulting & Implementation



* SOA and Web Services



* Sales force



* Technical & Product support



* SEO, SMO Link exchange, Link building etc.



* Facebook Apps, Sales Force apps.



* Data entry, Form filling, CallCentre (inbound & outbound),

Remote desktop support etc.



* Gaming, Digital media services etc.



* QA & Testing Services.



We have been providing services from start-ups to fortune companies. We
have been successful enough in growing tones of start-ups to Million Dollar
Company in US. We have our own data center which is located in our own
facility. This facility is an added advantage for all customers who build
the software application in our facility where they can host and maintain
in our infrastructure. Our hosting and consulting cost are very competitive
when you compared to go daddy, blue host or any other hosting and
development company around the globe.



Our company infrastructures are located inside heart of the cites in India
and 90% of facilities are owned by the organization and all our facilities
works 24/7/365.



Our delivery model is unique in the market, we provide support to clients
on their scheduled timing which will be 24 hours a day. We work non-stop as
all of our staff resides at our company location.



We are happy to provide our existing customers as references. You can find
our existing customers from any state or any cities in the US. More than
90% of our customer's bases are from US and 90% of our infrastructures are
based in India rest of them are in US and Europe. We are happy that most of
the popular brands in US are in our clientele list.



We kindly request you to provide us an appointment, so we could demonstrate
our service offering and our past consulting experience. We would be also
happy to meet you in person if you are located in and around in US. If you
are ready with a project scope our Business Analyst team will be supporting
you for a free estimation.

You can always call us at  our CA office number @415.358.1697.

For More details about our company, kindly visit our Website



www.bluewhalesolutions.com

www.facebook.com/bluewhale.bws



Thanks & Regards,

john

www.bluewhalesolutions.com

New Business Associate - Bluewhale Solutions Inc.

 Technology- - - -Delivered- - - - Globally




Blue whale Solutions Inc ,

Blue whale Solutions Inc ,

Blue whale Solutions,

Blue whale Solutions Inc,

9th Floor,

301 W Maple Ave

9/3, Reddy Street

152 Colindeep Lane,

263 TownSend Street

Suite 220-C

Alandur, Chennai - 600 016

colindale,NW96DX,

San Francisco - 94107- CA

Vienna - 22180 - VA

India

London,Uk

Phone : 415.358.1697

Phone :  703-459-9942

Phone : +91-44-42124760

Phone :44-208-819-3955

Fax :  415.358.1697

Fax : 703-459-9942

Fax :+ :+91-44-42124760

Fax: 44-208-819-3955



 Skype ID : ray.bws

Phone USA : 415.358.1697

Mobile India : + 91 9962076139





-

Confidentiality Notice:

We respect your Online Privacy. This is not an unsolicited mail. Under
Bills.1618 Title III passed by the 105th U.S

Support regarding the JENIKNS+JIRA configuration

2015-01-07 Thread bharath chalavadi
Hi,

I have installed JIRA plugin in JENKINS.
I need support in how to configure JIRA in such a way that ... it will pass
components and Label when a jira is  raised form Jenkins


Many thanks for the support in advance

Regards
Bharath

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


[JIRA] [git-parameter-plugin] (JENKINS-16290) git parameter plugin doesn't support Jenkins slave setup with git repos checked out only on slaves

2015-01-07 Thread ma...@mancino-net.de (JIRA)














































Mario Mancino
 commented on  JENKINS-16290


git parameter plugin doesn't support Jenkins slave setup with git repos checked out only on slaves















Still doesn't work - but if you need a workaround:
Create a Matrix-Project tied to the master with a slave axis for your build slaves. 
This will run the build on the slave, but also checkout the repository on the master.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [core] (JENKINS-26329) Slave jobs with ubuntu 14.04 hang

2015-01-07 Thread mdkel...@gmail.com (JIRA)














































Mark Keller
 created  JENKINS-26329


Slave jobs with ubuntu 14.04 hang















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


08/Jan/15 3:12 AM



Description:


When I try to run a job on an Ubuntu 14.04 slave that requires downloading the oracle JDK or other components via gradlew or grailsw (like dependencies). The job will eventually hang and never finish.

Our CentOS 6.6 slaves this works with no problems. Running the job on an Ubuntu 14.04 master also works fine. This only happens on a slave. I have tested with the swarm plugin JNLP slave and the SSH slave. The hosts are also on AWS if that matters.

I would be glad to gather debugging, but I am getting very little in the logs.




Environment:


Jenkins 1.595, ubuntu 14.04, slave using ssh slave 1.9 or swarm 1.21




Project:


Jenkins



Priority:


Minor



Reporter:


Mark Keller

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [svnmerge-plugin] (JENKINS-26280) Missing "Integrate Branch" from feature branch builds

2015-01-07 Thread hugues.cha...@gmail.com (JIRA)












































  
Hugues Chabot
 edited a comment on  JENKINS-26280


Missing "Integrate Branch" from feature branch builds
















This kind of project should be very well supported by the plugin.

Are you using matrix-based access control by any chances ? New permission for Rebase and Integrate were added in the last release.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [svnmerge-plugin] (JENKINS-26280) Missing "Integrate Branch" from feature branch builds

2015-01-07 Thread hugues.cha...@gmail.com (JIRA)














































Hugues Chabot
 commented on  JENKINS-26280


Missing "Integrate Branch" from feature branch builds















This kind of project should be very well supported by the plugin.

Are you using matrix-based access control by any changes ? New permission for Rebase and Integrate where added in the last release.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [svnmerge-plugin] (JENKINS-26280) Missing "Integrate Branch" from feature branch builds

2015-01-07 Thread cheung.jac...@gmail.com (JIRA)














































Jackey Cheung
 commented on  JENKINS-26280


Missing "Integrate Branch" from feature branch builds















Here's the scm config:

Master Job:
Repository URL:  https://192.168.3.15/svn//trunk
Credentials: 
Local module directory:  .(it's a single dot)
Repository depth:infinity
Ignore externals:checked
Check-out Strategy:  Use 'svn update' as much as possible, with 'svn revert' before update
Repository browser:  Auto

Feature Branch Job:
Repository URL:  https://192.168.3.15/svn//branches/dev1
Credentials: 
Local module directory:  .(it's a single dot)
Repository depth:infinity
Ignore externals:checked
Check-out Strategy:  Use 'svn update' as much as possible, with 'svn revert' before update
Repository browser:  Auto

That's all, nothing else is set, no module, no additional credential.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [core] (JENKINS-26277) Memory leak

2015-01-07 Thread ma...@ooyala.com (JIRA)












































  
Mario Rincon
 edited a comment on  JENKINS-26277


Memory leak
















Hello.

I left the system run a couple days to capture the behavior.

OK. Our current situation is this: the system starts taking memory until 99% of it is consumed, and then keeps on working with 99% of memory consumed. From the 16752 Mb, ~16594 Mb are consumed.

Speed of the server is OK.

The GC pauses for minor collections keep on creeping up.

The following happened once: once the GC pauses got to ~3.7 seconds, the GUI stopped responding, although in the log the system was still responding (jobs being run, etc).

I got an OOM message only once, when memory was 99% consumed: "java.lang.OutOfMemoryError: Requested array size exceeds VM limit". I haven't seen this anymore. The system continued working after this message.

I am not sure that this increase in memory usage is caused because of wrong GC values, but increases of memory used correspond with increases in minor collection times.

Sporadically I have ran the following commands to free memory:
echo 1 > /proc/sys/vm/drop_caches
free -m
echo 2 > /proc/sys/vm/drop_caches
free -m
echo 3 > /proc/sys/vm/drop_caches
free -m
sync

After these commands, I can see a clear diminution in memory usage, but still the GC pause times keep on growing.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [core] (JENKINS-26277) Memory leak

2015-01-07 Thread ma...@ooyala.com (JIRA)












































  
Mario Rincon
 edited a comment on  JENKINS-26277


Memory leak
















Hello.

I left the system run a couple days to capture the behavior.

OK. Our current situation is this: the system starts taking memory until 99% of it is consumed, and then keeps on working with 99% of memory consumed. From the 16752 Mb, ~16594 Mb are consumed.

Speed of the server is OK.

The GC pauses for minor collections keep on creeping up.

The following happened once: once the GC pauses got to ~3.7 seconds, the GUI stopped responding, although in the log the system was still responding (jobs being run, etc).

I got an OOM message only once, when memory was 99% consumed: "java.lang.OutOfMemoryError: Requested array size exceeds VM limit". I haven't seen this anymore. The system continued working after this message.

I am not sure that this increase in memory usage is caused because of wrong GC values, but increases of memory used correspond with increases in minor collection times.

Sporadically I have ran the following commands to free memory:
echo 1 > /proc/sys/vm/drop_caches
free -m
echo 2 > /proc/sys/vm/drop_caches
free -m
echo 3 > /proc/sys/vm/drop_caches
free -m
sync

After these commands, I can see a clear diminution in memory usage, but the GC pause times keep on growing.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [core] (JENKINS-26277) Memory leak

2015-01-07 Thread ma...@ooyala.com (JIRA)












































  
Mario Rincon
 edited a comment on  JENKINS-26277


Memory leak
















Hello.

I left the system run a couple days to capture the behavior.

OK. Our current situation is this: the system starts taking memory until 99% of it is consumed, and then keeps on working with 99% of memory consumed. From the 16752 Mb, ~16594 Mb are consumed.

Speed of the server is OK.

The GC pauses for minor collections keep on creeping up.

The following happened once: once the GC pauses got to ~3.7 seconds, the GUI stopped responding, although in the log the system was still responding (jobs being run, etc). I needed to restart the server (2 days ago).

I got an OOM message only once, when memory was 99% consumed: "java.lang.OutOfMemoryError: Requested array size exceeds VM limit". I haven't seen this anymore. The system continued working after this message.

I am not sure that this increase in memory usage is caused because of wrong GC values, but increases of memory used correspond with increases in minor collection times.

Sporadically I have ran the following commands to free memory:
echo 1 > /proc/sys/vm/drop_caches
free -m
echo 2 > /proc/sys/vm/drop_caches
free -m
echo 3 > /proc/sys/vm/drop_caches
free -m
sync

After these commands, I can see a clear diminution in memory usage, but the GC pause times keep on growing.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [core] (JENKINS-26277) Memory leak

2015-01-07 Thread ma...@ooyala.com (JIRA)














































Mario Rincon
 commented on  JENKINS-26277


Memory leak















Hello.

I left the system run a couple days to capture the behavior.

OK. Our current situation is this: the system starts taking memory until 99% of it is consumed, and then keeps on working with 99% of memory consumed. From the 16752 Mb, ~16594 Mb are consumed.

Speed of the server is OK.

The GC pauses for minor collections keep on creeping up.

The following happened once: once the GC pauses got to ~3.7 seconds, the GUI stopped responding, although in the log the system was still responding (jobs being run, etc). I needed to restart the server (2 days ago).

I got an OOM message only once, when memory was 99% consumed: "java.lang.OutOfMemoryError: Requested array size exceeds VM limit". I haven't seen this anymore. The system continued working after this message.

I am not sure that this increase in memory usage is caused because of wrong GC values, but increases of memory used correspond with increases in minor collection times.

Sporadically I have ran the following commands to free memory:
echo 1 > /proc/sys/vm/drop_caches
free -m
echo 2 > /proc/sys/vm/drop_caches
free -m
echo 3 > /proc/sys/vm/drop_caches
free -m
sync

After these commands, I can see a clear diminution in memory usage, but the GC pause times keep on growing. I am afraid I'll have to restart the server once the GC pause times gets closer to 4 seconds again.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [accelerated-build-now-plugin] (JENKINS-26328) set-build-parameter command hangs intermittently

2015-01-07 Thread apu...@yahoo.com (JIRA)














































Andy Pham
 updated  JENKINS-26328


set-build-parameter command hangs intermittently
















Change By:


Andy Pham
(07/Jan/15 11:58 PM)




Component/s:


accelerated-build-now-plugin





Component/s:


cli



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [accelerated-build-now-plugin] (JENKINS-26328) set-build-parameter command hangs intermittently

2015-01-07 Thread apu...@yahoo.com (JIRA)














































Andy Pham
 updated  JENKINS-26328


set-build-parameter command hangs intermittently
















Change By:


Andy Pham
(07/Jan/15 11:59 PM)




Environment:


Jenkins version 1.582
 on Linux



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [cli] (JENKINS-26328) set-build-parameter command hangs intermittently

2015-01-07 Thread apu...@yahoo.com (JIRA)














































Andy Pham
 updated  JENKINS-26328


set-build-parameter command hangs intermittently
















Change By:


Andy Pham
(07/Jan/15 11:52 PM)




Description:


I have multiple jobs that use the set-build-parameter command to set the build parameter like:
user error

java -jar jenkins-cli.jar -s http://my-jenkins-server set-build-parameter ParameterName ValueThe jenkins-cli.jar was downloaded from the server like:wget -o /dev/null http://my-jenkins-server/jnlpJars/jenkins-cli.jarIt seems recently the command hangs intermittently with different job.  If I ssh onto the slave node and kill the process running the command; the job resumes normally.  This seems to me a cli issue.  I got a core dump from the client side and attached to this defect.Let me know if other info is needed.





Priority:


Major
Trivial



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [cli] (JENKINS-26328) set-build-parameter command hangs intermittently

2015-01-07 Thread apu...@yahoo.com (JIRA)















































Andy Pham
 resolved  JENKINS-26328 as Not A Defect


set-build-parameter command hangs intermittently
















Change By:


Andy Pham
(07/Jan/15 11:30 PM)




Status:


Open
Resolved





Resolution:


Not A Defect



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [cli] (JENKINS-26328) set-build-parameter command hangs intermittently

2015-01-07 Thread apu...@yahoo.com (JIRA)














































Andy Pham
 updated  JENKINS-26328


set-build-parameter command hangs intermittently
















Change By:


Andy Pham
(07/Jan/15 11:26 PM)




Attachment:


javacore.20150107.165429.49449.0001.txt



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [cli] (JENKINS-26328) set-build-parameter command hangs intermittently

2015-01-07 Thread apu...@yahoo.com (JIRA)














































Andy Pham
 updated  JENKINS-26328


set-build-parameter command hangs intermittently
















Change By:


Andy Pham
(07/Jan/15 11:15 PM)




Attachment:


javacore.20141017.160752.58373.0001.txt



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [cli] (JENKINS-26328) set-build-parameter command hangs intermittently

2015-01-07 Thread apu...@yahoo.com (JIRA)














































Andy Pham
 updated  JENKINS-26328


set-build-parameter command hangs intermittently
















Change By:


Andy Pham
(07/Jan/15 11:12 PM)




Attachment:


javacore.20150107.165429.49449.0001.txt



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [core] (JENKINS-22932) Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted

2015-01-07 Thread patri...@vmware.com (JIRA)














































Patricia Wright
 commented on  JENKINS-22932


Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted















Even after running on LTS I still see this every week.




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [rebuild-plugin] (JENKINS-26024) Does not work with workflows

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-26024


Does not work with workflows















Code changed in jenkins
User: Jesse Glick
Path:
 COMPATIBILITY.md
http://jenkins-ci.org/commit/workflow-plugin/f198f75fd91223d7f440997bfb5d51c0ef04cc6a
Log:
  JENKINS-26024 Noting.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [pretested-integration-plugin] (JENKINS-25546) Support individual git scm configuration part in the Multi SCMs plugin (our case 12287)

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-25546


Support individual git scm configuration part in the Multi SCMs plugin (our case 12287)















Code changed in jenkins
User: Mads Nielsen
Path:
 src/main/java/org/jenkinsci/plugins/pretestedintegration/exceptions/UnsupportedConfigurationException.java
 src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/GitBridge.java
http://jenkins-ci.org/commit/pretested-integration-plugin/c9e2801895b1a48d8465d0581d95f9da34432ba0
Log:
  Review JENKINS-25546





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [pretested-integration-plugin] (JENKINS-25960) MultiScm configurations does not resolve corret git-client (our case 12426)

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-25960


MultiScm configurations does not resolve corret git-client (our case 12426)















Code changed in jenkins
User: Bue Petersen
Path:
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/MultipleScm_threeRepos_IT.java
http://jenkins-ci.org/commit/pretested-integration-plugin/6e27a1ed2eeb8e9321e6624534a2ca15eb1b79f6
Log:
  JENKINS-25960: Updated error msg in test to match.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [pretested-integration-plugin] (JENKINS-25618) Use standard commit message when the squash strategy is used case 12299

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-25618


Use standard commit message when the squash strategy is used case 12299















Code changed in jenkins
User: Mads Nielsen
Path:
 pom.xml
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/BuildResultValidator.java
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/GeneralBehaviourIT.java
http://jenkins-ci.org/commit/pretested-integration-plugin/f7ce71420e2f434ac3545663552b9be45c51af1c
Log:
  Added test for JENKINS-25618





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [pretested-integration-plugin] (JENKINS-25960) MultiScm configurations does not resolve corret git-client (our case 12426)

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-25960


MultiScm configurations does not resolve corret git-client (our case 12426)















Code changed in jenkins
User: Bue Petersen
Path:
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/BuildResultValidator.java
http://jenkins-ci.org/commit/pretested-integration-plugin/64208a4f0303ced609e075233eb804b6e7fc7575
Log:
  JENKINS-25960: Fixed tests due testutils change





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [pretested-integration-plugin] (JENKINS-25960) MultiScm configurations does not resolve corret git-client (our case 12426)

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-25960


MultiScm configurations does not resolve corret git-client (our case 12426)















Code changed in jenkins
User: Bue Petersen
Path:
 src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/AccumulatedCommitStrategy.java
 src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/GitBridge.java
 src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/GitMessages.java
 src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/SquashCommitStrategy.java
http://jenkins-ci.org/commit/pretested-integration-plugin/452398047cb4c1e6e843030f3934acdc75ffdf23
Log:
  JENKINS-25960: MultiScm fix - resolve git client:

When resolving the git client for MultiSCM we should chose the first
found git scm, but the one that matches the build data set.


	changed the findScm to select not the first, but the relevant git scm
  client
	changed error message in strategies to match better description of the
  problem, which is two-fold thus two things mentioned in error message
	Implemeted a shared message setup, also to be used in tests.































This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [pretested-integration-plugin] (JENKINS-25545) Multiple git repository names are not check and repositories risk be merged (our case 12286)

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-25545


Multiple git repository names are not check and repositories risk be merged (our case 12286)















Code changed in jenkins
User: Mads Nielsen
Path:
 src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/GitBridge.java
 src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/SquashCommitStrategy.java
http://jenkins-ci.org/commit/pretested-integration-plugin/89de8232695ff40b6145ca8a7fbb096f3ba4b11b
Log:
  Fixed JENKINS-25545





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [pretested-integration-plugin] (JENKINS-25618) Use standard commit message when the squash strategy is used case 12299

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-25618


Use standard commit message when the squash strategy is used case 12299















Code changed in jenkins
User: Mads Nielsen
Path:
 pom.xml
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/BuildResultValidator.java
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/GeneralBehaviourIT.java
http://jenkins-ci.org/commit/pretested-integration-plugin/2a5bdc6e5f11541c6c3d71e41d91fb7a0f6a323e
Log:
  Review JENKINS-25618





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [pretested-integration-plugin] (JENKINS-25544) Default repository name (origin) must work with git scm and multi SCMs git (our case 12285)

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-25544


Default repository name (origin) must work with git scm and multi SCMs git (our case 12285)















Code changed in jenkins
User: Mads Nielsen
Path:
 src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/GitBridge.java
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/GeneralBehaviourIT.java
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/JENKINS_24754_IT.java
http://jenkins-ci.org/commit/pretested-integration-plugin/475dfea4b78097a9f66f89f769122fcf195ce5bc
Log:
  Fixed JENKINS-25544





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [pretested-integration-plugin] (JENKINS-25960) MultiScm configurations does not resolve corret git-client (our case 12426)

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-25960


MultiScm configurations does not resolve corret git-client (our case 12426)















Code changed in jenkins
User: Bue Petersen
Path:
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/TestUtilsFactory.java
http://jenkins-ci.org/commit/pretested-integration-plugin/e7412ff87bc550a4603c6a5b0f3569af731f905e
Log:
  JENKINS-25960: Not directly releated to issue:


	Minor test utils improvement and docs































This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [pretested-integration-plugin] (JENKINS-25873) Extend version number with git SHA (our case 12396)

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-25873


Extend version number with git SHA (our case 12396)















Code changed in jenkins
User: Bue Petersen
Path:
 pom.xml
http://jenkins-ci.org/commit/pretested-integration-plugin/026ca1d8815e1054cac2d608a810848de1f56375
Log:
  JENKINS-25873: Added git short SHA to version number





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [pretested-integration-plugin] (JENKINS-25546) Support individual git scm configuration part in the Multi SCMs plugin (our case 12287)

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-25546


Support individual git scm configuration part in the Multi SCMs plugin (our case 12287)















Code changed in jenkins
User: Mads Nielsen
Path:
 resources/HelloWorldBuilder - jelly example/config.jelly
 resources/HelloWorldBuilder - jelly example/global.jelly
 resources/HelloWorldBuilder - jelly example/help-name.html
 resources/HelloWorldBuilder - jelly example/help-pretestCommits.html
 resources/HelloWorldBuilder - jelly example/help-selectBox.html
 resources/HelloWorldBuilder.java
 resources/hg_change_group_hook.py
 resources/hg_change_group_hook_with_parameters.py
 resources/hgrc
 src/main/java/org/jenkinsci/plugins/pretestedintegration/exceptions/UnsupportedConfigurationException.java
 src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/GitBridge.java
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/BuildResultValidator.java
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/JENKINS_25546_IT.java
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/TestUtilsFactory.java
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/UniqueBranchGenerator.java
http://jenkins-ci.org/commit/pretested-integration-plugin/e1100236a209cea4566c1d503c6451c7b794ca52
Log:
  Fixed JENKINS-25546





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [pretested-integration-plugin] (JENKINS-25959) Post-buid steps is executed though master is integration branch (our case 12427)

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-25959


Post-buid steps is executed though master is integration branch (our case 12427)















Code changed in jenkins
User: Bue Petersen
Path:
 src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/GitBridge.java
http://jenkins-ci.org/commit/pretested-integration-plugin/9cda5541c5fa785572dfb0efcb3ea0af05a91bc7
Log:
  JENKINS-25959: Ensuring post-build only done if result okay





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [pretested-integration-plugin] (JENKINS-24754) Add Support for named repositories, required for multiple scm selections (Praqma case 12019)

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-24754


Add Support for named repositories, required for multiple scm selections (Praqma case 12019)















Code changed in jenkins
User: Mads Nielsen
Path:
 docs/Illegal_JENKINS24754.png
 docs/More_than_1_gitBuild_data.png
 docs/legal_JENKINS24754.png
 src/main/java/org/jenkinsci/plugins/pretestedintegration/AbstractSCMBridge.java
 src/main/java/org/jenkinsci/plugins/pretestedintegration/PretestedIntegrationBuildWrapper.java
 src/main/java/org/jenkinsci/plugins/pretestedintegration/exceptions/NothingToDoException.java
 src/main/java/org/jenkinsci/plugins/pretestedintegration/exceptions/UnsupportedConfigurationException.java
 src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/AccumulatedCommitStrategy.java
 src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/GitBridge.java
 src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/SquashCommitStrategy.java
 src/main/resources/org/jenkinsci/plugins/pretestedintegration/scm/git/GitBridge/help-branch.html
 src/main/resources/org/jenkinsci/plugins/pretestedintegration/scm/git/GitBridge/help-repoName.html
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/GeneralBehaviourIT.java
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/JENKINS_24754_IT.java
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/SquashCommitStrategyIT.java
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/TestUtilsFactory.java
http://jenkins-ci.org/commit/pretested-integration-plugin/9a68e17c11d579aa9eacc7502acd077cf0fde8d9
Log:
  Implemented JENKINS-24754





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [pretested-integration-plugin] (JENKINS-25545) Multiple git repository names are not check and repositories risk be merged (our case 12286)

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-25545


Multiple git repository names are not check and repositories risk be merged (our case 12286)















Code changed in jenkins
User: Mads Nielsen
Path:
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/GeneralBehaviourIT.java
http://jenkins-ci.org/commit/pretested-integration-plugin/22965d98dc13df3992ce4d8bbe11b381568a7916
Log:
  Implemented test for JENKINS-25545





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [pretested-integration-plugin] (JENKINS-25873) Extend version number with git SHA (our case 12396)

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-25873


Extend version number with git SHA (our case 12396)















Code changed in jenkins
User: Bue Petersen
Path:
 pom.xml
http://jenkins-ci.org/commit/pretested-integration-plugin/ba9e785a801ec86c64dc0cc3e5020674c7e160f8
Log:
  JENKINS-25873: Disabled check of local workspace mods - build pipeline doesn't need it, and developers need the opposite





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [pretested-integration-plugin] (JENKINS-25886) Implement job configuration check - explicitly named remotes for MultiSCM (our case 12401)

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-25886


Implement job configuration check - explicitly named remotes for MultiSCM (our case 12401)















Code changed in jenkins
User: Bue Petersen
Path:
 src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/GitBridge.java
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/DoNotAllowMasterBranchAsReadyBranch.java
http://jenkins-ci.org/commit/pretested-integration-plugin/aa41c562c70e174e7177dd058b401243ddbc9d52
Log:
  JENKINS-25886: Minor java 1.6-1.7 compatibility fix to make javancss reporting work





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [pretested-integration-plugin] (JENKINS-25960) MultiScm configurations does not resolve corret git-client (our case 12426)

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-25960


MultiScm configurations does not resolve corret git-client (our case 12426)















Code changed in jenkins
User: Bue Petersen
Path:
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/MultipleScm_threeRepos_IT.java
http://jenkins-ci.org/commit/pretested-integration-plugin/3afb27572e7e39bb6ef640bb76895bf6ef71eb70
Log:
  JENKINS-25960: Test for issue.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [pretested-integration-plugin] (JENKINS-25886) Implement job configuration check - explicitly named remotes for MultiSCM (our case 12401)

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-25886


Implement job configuration check - explicitly named remotes for MultiSCM (our case 12401)















Code changed in jenkins
User: Bue Petersen
Path:
 src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/AccumulatedCommitStrategy.java
 src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/SquashCommitStrategy.java
http://jenkins-ci.org/commit/pretested-integration-plugin/70cc37d93546425d40c64a9bec4a500f5206f098
Log:
  JENKINS-25886: Change back unintented minor change.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [pretested-integration-plugin] (JENKINS-25618) Use standard commit message when the squash strategy is used case 12299

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-25618


Use standard commit message when the squash strategy is used case 12299















Code changed in jenkins
User: Mads Nielsen
Path:
 src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/SquashCommitStrategy.java
http://jenkins-ci.org/commit/pretested-integration-plugin/e91d7bb615be3ad75e3dc0d5d3196646f550716d
Log:
  Fixed JENKINS-25618





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [pretested-integration-plugin] (JENKINS-25512) If two branchheads points to same commit, wrong branch might get deleted (our case 12269)

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-25512


If two branchheads points to same commit, wrong branch might get deleted (our case 12269)















Code changed in jenkins
User: Bue Petersen
Path:
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/TwoBranchHeadsIT.java
http://jenkins-ci.org/commit/pretested-integration-plugin/45fcae0808f1b36bb1a5c99399e128f90cd1e962
Log:
  JENKINS-25512: Ignoring failing tests

There are tests written showing the problem, but the bug haven't been
solved. It not prioritized now, and we need a release so disabling tests
temporarily.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [pretested-integration-plugin] (JENKINS-25544) Default repository name (origin) must work with git scm and multi SCMs git (our case 12285)

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-25544


Default repository name (origin) must work with git scm and multi SCMs git (our case 12285)















Code changed in jenkins
User: Bue Petersen
Path:
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/JENKINS_24754_IT.java
http://jenkins-ci.org/commit/pretested-integration-plugin/1d0e65019bce2cd9cbd95e1fd8a1f072b789e742
Log:
  JENKINS-25544: Added test for using default names in git scm and the other repository in pretest





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [pretested-integration-plugin] (JENKINS-25888) Add more documentation on workflows and configuration (our case 12404)

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-25888


Add more documentation on workflows and configuration (our case 12404)















Code changed in jenkins
User: Bue Petersen
Path:
 README.md
http://jenkins-ci.org/commit/pretested-integration-plugin/547ed8fca5634c3380026f288a58162b7266cfba
Log:
  JENKINS-25888: More documentation - updated readme with few design decisions





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [pretested-integration-plugin] (JENKINS-25886) Implement job configuration check - explicitly named remotes for MultiSCM (our case 12401)

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-25886


Implement job configuration check - explicitly named remotes for MultiSCM (our case 12401)















Code changed in jenkins
User: Mads Nielsen
Path:
 src/main/java/org/jenkinsci/plugins/pretestedintegration/AbstractSCMBridge.java
 src/main/java/org/jenkinsci/plugins/pretestedintegration/IntegrationStrategy.java
 src/main/java/org/jenkinsci/plugins/pretestedintegration/PretestedIntegrationAction.java
 src/main/java/org/jenkinsci/plugins/pretestedintegration/PretestedIntegrationBuildWrapper.java
 src/main/java/org/jenkinsci/plugins/pretestedintegration/exceptions/NextCommitFailureException.java
 src/main/java/org/jenkinsci/plugins/pretestedintegration/exceptions/UnsupportedConfigurationException.java
 src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/AccumulatedCommitStrategy.java
 src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/GitBridge.java
 src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/SquashCommitStrategy.java
 src/main/resources/org/jenkinsci/plugins/pretestedintegration/scm/git/GitBridge/help-branch.html
 src/main/resources/org/jenkinsci/plugins/pretestedintegration/scm/git/GitBridge/help-repoName.html
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/AccumulatedCommitStrategyIT.java
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/DoNotAllowMasterBranchAsReadyBranch.java
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/GeneralBehaviourIT.java
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/JENKINS_24754_IT.java
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/JENKINS_25546_IT.java
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/MultipleScmIT.java
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/SquashCommitStrategyIT.java
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/TestUtilsFactory.java
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/TwoBranchHeadsIT.java
 src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/UniqueBranchGenerator.java
 src/test/java/org/jenkinsci/plugins/pretestedintegration/unit/AbstractSCMBridgeTest.java
 src/test/java/org/jenkinsci/plugins/pretestedintegration/unit/CommitTest.java
 src/test/java/org/jenkinsci/plugins/pretestedintegration/unit/DummyCommit.java
 src/test/java/org/jenkinsci/plugins/pretestedintegration/unit/DummyIntegrationStrategy.java
 src/test/java/org/jenkinsci/plugins/pretestedintegration/unit/PretestedIntegrationActionTest.java
http://jenkins-ci.org/commit/pretested-integration-plugin/703a6ca9f17a2e02b268306ac7a69a936841ae8e
Log:
  JENKINS-25886: Job config and build data selection:

Refactoring and implemented job configuration check to ensure explicit
named remotes if using MultiScm plugin.

Refactoring and improvements:


	Safer and simpler selection of build data, so dublicates are accepted
  if identical, ambiguity is avoided and reported as failure
	Refactoring methods changed interfaces, and is fixed.
	Unit tests is updated.
	Functional tests updated to match new error messages (no logic change)
	One functional tests updated to new use case, it tested now invalid
  configuration.
	Documentation notes are added to some functions.
	UI help text updated with "no trailing slash"-tip
	Functional tests now have headers explaining what is tested.































This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [pretested-integration-plugin] (JENKINS-25888) Add more documentation on workflows and configuration (our case 12404)

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-25888


Add more documentation on workflows and configuration (our case 12404)















Code changed in jenkins
User: Bue Petersen
Path:
 README.md
http://jenkins-ci.org/commit/pretested-integration-plugin/5fa964b5e6878aabdbe0f28dc0aaa39e2e3453ce
Log:
  JENKINS-25888: Documentation - updated readme in repository, mostly developer oriented info





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [rebuild-plugin] (JENKINS-26024) Does not work with workflows

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-26024


Does not work with workflows















Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
 src/main/java/com/sonyericsson/rebuild/RebuildAction.java
 src/main/java/com/sonyericsson/rebuild/RebuildActionFactory.java
 src/main/java/com/sonyericsson/rebuild/RebuildLastCompletedBuildAction.java
 src/main/java/com/sonyericsson/rebuild/RebuildProjectActionFactory.java
 src/main/java/com/sonyericsson/rebuild/RebuildValidator.java
 src/main/java/com/sonyericsson/rebuild/Rebuilder.java
 src/main/resources/com/sonyericsson/rebuild/RebuildAction/RunParameterValue.jelly
 src/main/resources/com/sonyericsson/rebuild/RebuildAction/parameterized.jelly
http://jenkins-ci.org/commit/rebuild-plugin/e17364675a5d21acf76e5c5bfc5b2f21cac2b918
Log:
  Merge pull request #31 from jenkinsci/JENKINS-26024-workflow

[FIXED JENKINS-26024] Allow this plugin to operate on workflows


Compare: https://github.com/jenkinsci/rebuild-plugin/compare/1ca3940c62a7...e17364675a5d




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [rebuild-plugin] (JENKINS-26024) Does not work with workflows

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-26024


Does not work with workflows















Code changed in jenkins
User: Jesse Glick
Path:
 src/main/java/com/sonyericsson/rebuild/RebuildAction.java
 src/main/java/com/sonyericsson/rebuild/RebuildActionFactory.java
 src/main/java/com/sonyericsson/rebuild/RebuildLastCompletedBuildAction.java
 src/main/java/com/sonyericsson/rebuild/RebuildProjectActionFactory.java
 src/main/java/com/sonyericsson/rebuild/RebuildValidator.java
 src/main/java/com/sonyericsson/rebuild/Rebuilder.java
 src/main/resources/com/sonyericsson/rebuild/RebuildAction/RunParameterValue.jelly
 src/main/resources/com/sonyericsson/rebuild/RebuildAction/parameterized.jelly
http://jenkins-ci.org/commit/rebuild-plugin/a4c94010177de19207a343b2064600e11e97b54b
Log:
  [FIXED JENKINS-26024] Allow this plugin to operate on workflows.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [rebuild-plugin] (JENKINS-26024) Does not work with workflows

2015-01-07 Thread scm_issue_l...@java.net (JIRA)















































SCM/JIRA link daemon
 resolved  JENKINS-26024 as Fixed


Does not work with workflows
















Change By:


SCM/JIRA link daemon
(07/Jan/15 10:51 PM)




Status:


In Progress
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [workflow-plugin] (JENKINS-26149) BuildTriggerStepExecution does not survive restart

2015-01-07 Thread scm_issue_l...@java.net (JIRA)















































SCM/JIRA link daemon
 resolved  JENKINS-26149 as Fixed


BuildTriggerStepExecution does not survive restart
















Change By:


SCM/JIRA link daemon
(07/Jan/15 10:22 PM)




Status:


In Progress
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [workflow-plugin] (JENKINS-26149) BuildTriggerStepExecution does not survive restart

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-26149


BuildTriggerStepExecution does not survive restart















Code changed in jenkins
User: Jesse Glick
Path:
 aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/PushdStepTest.java
 basic-steps/src/main/java/org/jenkinsci/plugins/workflow/steps/RetryStepExecution.java
 cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java
http://jenkins-ci.org/commit/workflow-plugin/cc76ee2256279676b4858cae95244585feceebaa
Log:
  Checking sources for other possible restartability bugs as in JENKINS-26149.
RetryStep looks suspicious but apparently works.
PushdStep cannot be tested due to a mysterious error noted in JENKINS-26137.


Compare: https://github.com/jenkinsci/workflow-plugin/compare/87553e9e6e35...cc76ee225627




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [workflow-plugin] (JENKINS-26137) Mysterious serialization errors

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-26137


Mysterious serialization errors















Code changed in jenkins
User: Jesse Glick
Path:
 aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/PushdStepTest.java
 basic-steps/src/main/java/org/jenkinsci/plugins/workflow/steps/RetryStepExecution.java
 cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java
http://jenkins-ci.org/commit/workflow-plugin/cc76ee2256279676b4858cae95244585feceebaa
Log:
  Checking sources for other possible restartability bugs as in JENKINS-26149.
RetryStep looks suspicious but apparently works.
PushdStep cannot be tested due to a mysterious error noted in JENKINS-26137.


Compare: https://github.com/jenkinsci/workflow-plugin/compare/87553e9e6e35...cc76ee225627




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [workflow-plugin] (JENKINS-26149) BuildTriggerStepExecution does not survive restart

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-26149


BuildTriggerStepExecution does not survive restart















Code changed in jenkins
User: Jesse Glick
Path:
 CHANGES.md
 aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/build/BuildTriggerStepRestartTest.java
 step-api/src/main/java/org/jenkinsci/plugins/workflow/steps/AbstractStepExecutionImpl.java
 support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStepExecution.java
http://jenkins-ci.org/commit/workflow-plugin/784a03a43442a93cd94ae6331b69a5fd3dba1632
Log:
  [FIXED JENKINS-26149] Make the build step survive restarts.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [cli] (JENKINS-26328) set-build-parameter command hangs intermittently

2015-01-07 Thread apu...@yahoo.com (JIRA)














































Andy Pham
 created  JENKINS-26328


set-build-parameter command hangs intermittently















Issue Type:


Bug



Assignee:


Unassigned


Attachments:


javacore.20150107.165429.49449.0001.txt



Components:


cli



Created:


07/Jan/15 10:18 PM



Description:


I have multiple jobs that use the set-build-parameter command to set the build parameter like:

java -jar jenkins-cli.jar -s http://my-jenkins-server set-build-parameter ParameterName Value

The jenkins-cli.jar was downloaded from the server like:

wget -o /dev/null http://my-jenkins-server/jnlpJars/jenkins-cli.jar

It seems recently the command hangs intermittently with different job.  If I ssh onto the slave node and kill the process running the command; the job resumes normally.  This seems to me a cli issue.  I got a core dump from the client side and attached to this defect.

Let me know if other info is needed.




Environment:


Jenkins version 1.582 on Linux




Project:


Jenkins



Priority:


Major



Reporter:


Andy Pham

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [docker-build-step-plugin] (JENKINS-26166) PullImageCommand.isImagePulled() misuses DockerClient.listImagesCmd().withFilters()

2015-01-07 Thread vjura...@java.net (JIRA)















































vjuranek
 resolved  JENKINS-26166 as Fixed


PullImageCommand.isImagePulled() misuses DockerClient.listImagesCmd().withFilters()
















Should be fixed by https://github.com/jenkinsci/docker-build-step-plugin/pull/22





Change By:


vjuranek
(07/Jan/15 10:07 PM)




Status:


In Progress
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [docker-build-publish-plugin] (JENKINS-26167) none default registry in PullImageCommand not working as expected

2015-01-07 Thread vjura...@java.net (JIRA)















































vjuranek
 resolved  JENKINS-26167 as Fixed


none default registry in PullImageCommand not working as expected
















Should be fixed by https://github.com/jenkinsci/docker-build-step-plugin/pull/22





Change By:


vjuranek
(07/Jan/15 10:08 PM)




Status:


In Progress
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [docker-build-step-plugin] (JENKINS-24388) Add registry authentication

2015-01-07 Thread vjura...@java.net (JIRA)















































vjuranek
 resolved  JENKINS-24388 as Fixed


Add registry authentication
















Should be fixed by https://github.com/jenkinsci/docker-build-step-plugin/pull/22





Change By:


vjuranek
(07/Jan/15 10:07 PM)




Status:


In Progress
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [core] (JENKINS-25026) Console output stops populating after several seconds

2015-01-07 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 commented on  JENKINS-25026


Console output stops populating after several seconds















Martin: Clearly, otherwise I'd be able to reproduce the problem 

Would be interesting to know whether all affected instances run behind Apache.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [core] (JENKINS-25026) Console output stops populating after several seconds

2015-01-07 Thread mscha...@gmail.com (JIRA)














































Martin Schayna
 commented on  JENKINS-25026


Console output stops populating after several seconds















A colleague of mine installed a new server with Jenkins in the same version (1.582) from scratch and the console is polling OK now. Sorry, I cannot reproduce it, apparently it happens under certain conditions only.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [core] (JENKINS-22932) Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted

2015-01-07 Thread patri...@vmware.com (JIRA)












































  
Patricia Wright
 edited a comment on  JENKINS-22932


Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted
















I've seen this happen even after recent fixes.

Jobs were running on the slaves at the time..
One thing I noticed - linux slaves didn't disconnect, only windows slaves.   

This was too big of a problem, I went back to LTS.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [workflow-plugin] (JENKINS-26149) BuildTriggerStepExecution does not survive restart

2015-01-07 Thread jgl...@cloudbees.com (JIRA)














































Jesse Glick
 started work on  JENKINS-26149


BuildTriggerStepExecution does not survive restart
















Change By:


Jesse Glick
(07/Jan/15 9:47 PM)




Status:


Open
In Progress



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [core] (JENKINS-22932) Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted

2015-01-07 Thread serge.do...@philips.com (JIRA)












































  
Serge Dorna
 edited a comment on  JENKINS-22932


Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted
















I'm seeing the same, master is 2008R2, slave is 7sp1
Jenkins ver. 1.580.2



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [core] (JENKINS-22932) Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted

2015-01-07 Thread serge.do...@philips.com (JIRA)














































Serge Dorna
 commented on  JENKINS-22932


Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted















I'm seeing the same, master is 2008R2, slave is 7sp1



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [workflow-plugin] (JENKINS-25736) Ability to pause a running flow

2015-01-07 Thread jgl...@cloudbees.com (JIRA)















































Jesse Glick
 assigned  JENKINS-25736 to Kohsuke Kawaguchi



Ability to pause a running flow
















Change By:


Jesse Glick
(07/Jan/15 9:29 PM)




Assignee:


Jesse Glick
Kohsuke Kawaguchi



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [pretested-integration-plugin] (JENKINS-25888) Add more documentation on workflows and configuration (our case 12404)

2015-01-07 Thread b...@praqma.net (JIRA)















































Bue Petersen
 resolved  JENKINS-25888 as Fixed


Add more documentation on workflows and configuration (our case 12404)
















Change By:


Bue Petersen
(07/Jan/15 9:11 PM)




Status:


In Progress
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [git-client-plugin] (JENKINS-26327) Git or Git Client Plugin Appending Additional Slash To Git SSH Url Scheme

2015-01-07 Thread timmy.le...@gmail.com (JIRA)














































Timmy Leahy
 created  JENKINS-26327


Git or Git Client Plugin Appending Additional Slash To Git SSH Url Scheme















Issue Type:


Bug



Assignee:


Nicolas De Loof



Components:


git-client-plugin, git-plugin



Created:


07/Jan/15 8:57 PM



Description:


I'm having an issue right now trying to set up a Jenkins job (on one Windows server) to monitor an internal Git repo located on a on a different Windows server running ssh through Cygwin with Gitosis.

The url looks like this: ssh://git@192.168.0.1:relative_path/repo.git (real values replaced for security). A relative path is the only path that will work. ~/ and an absolute path will not work because of how the server is configured.

When running git clone from the command line with the url, everything comes out fine.

When configuring a Git SCM in the Jenkins job it is able to run an ls-remote command (this confirms that the ssh keys are properly configured for the Jenkins instance). I've tried tweaking the url slightly and the background ls-remote command passes and fails accordingly.

However when the job executes, the url appears to be rewritten with an additional forward slash in the scheme which causes the clone command to fail.


Started by user Meh
[EnvInject] - Loading node environment variables.
Building in workspace D:\local_repo_test
 > git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git.exe config remote.origin.url ssh:///git@192.168.0.1:relative_path/repo.git # timeout=10
Fetching upstream changes from ssh:///git@192.168.0.1:relative_path/repo.git
 > git.exe --version # timeout=10
 > git.exe -c core.askpass=true fetch --tags --progress ssh:///git@192.168.0.1:relative_path/repo.git +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
ERROR: Error fetching remote repo 'origin'
Finished: FAILURE





Environment:


OS: Windows 7 Enterprise 64bit

JDK: 1.7.0_72-b32

Jenkins: 1.595

Plugins: Git, Git Client, Multiple SCM






Project:


Jenkins



Priority:


Minor



Reporter:


Timmy Leahy

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [core] (JENKINS-6610) RSS Feeds Ought to Accept Credentials

2015-01-07 Thread jgl...@cloudbees.com (JIRA)














































Jesse Glick
 commented on  JENKINS-6610


RSS Feeds Ought to Accept Credentials















Assuming that simply encoding the username and API token in the URL is undesirable for security reasons, I tend to like the idea of using a 401 when the client has not specified that it will Accept: text/html.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [durable-task-plugin] (JENKINS-26319) durable-task-plugin version 1.1 fail on windows with result "Cannot run program "nohup""

2015-01-07 Thread jgl...@cloudbees.com (JIRA)















































Jesse Glick
 resolved  JENKINS-26319 as Not A Defect


durable-task-plugin version 1.1 fail on windows with result "Cannot run program "nohup""
















No, JENKINS-25848 was about nohup failing on Macs in some cases. Your problem is that nohup does not exist at all—because you are running on Windows, so there is no reason for it to exist. Assuming you are encountering this from within a workflow running the sh step, the fix is simply to use the bat step instead.





Change By:


Jesse Glick
(07/Jan/15 8:23 PM)




Status:


Open
Resolved





Resolution:


Not A Defect



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [durable-task-plugin] (JENKINS-26319) durable-task-plugin version 1.1 fail on windows with result "Cannot run program "nohup""

2015-01-07 Thread jgl...@cloudbees.com (JIRA)














































Jesse Glick
 updated  JENKINS-26319


durable-task-plugin version 1.1 fail on windows with result "Cannot run program "nohup""
















Change By:


Jesse Glick
(07/Jan/15 8:23 PM)




Labels:


workflow



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [promoted-builds-plugin] (JENKINS-18385) accept groups for "users" that can run a manual promotion

2015-01-07 Thread jgl...@cloudbees.com (JIRA)














































Jesse Glick
 updated  JENKINS-18385


accept groups for "users" that can run a manual promotion
















(just reverting nonsensical change of summary)





Change By:


Jesse Glick
(07/Jan/15 8:21 PM)




Summary:


in
accept groups for "users" that can run
 a
 build script
 manual promotion



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [core] (JENKINS-16599) Master label settings are lost when configuring system settings

2015-01-07 Thread jgl...@cloudbees.com (JIRA)















































Jesse Glick
 resolved  JENKINS-16599 as Duplicate


Master label settings are lost when configuring system settings
















Change By:


Jesse Glick
(07/Jan/15 8:19 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [mercurial-plugin] (JENKINS-26316) Plaintext password shown in logged error string

2015-01-07 Thread jgl...@cloudbees.com (JIRA)















































Jesse Glick
 resolved  JENKINS-26316 as Incomplete


Plaintext password shown in logged error string
















Can you be more specific? How is the Mercurial installation configured—with caching, sharing, or neither? What form of credentials are you using to authenticate—HTTPS username/password? What is the complete text of the polling log in your case (with the actual password redacted of course)?





Change By:


Jesse Glick
(07/Jan/15 8:18 PM)




Status:


Open
Resolved





Resolution:


Incomplete



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [vagrant-plugin] (JENKINS-26326) Boot up Vagrant VM not using relative path

2015-01-07 Thread jess...@gmail.com (JIRA)














































Jesse Bowes
 updated  JENKINS-26326


Boot up Vagrant VM not using relative path
















Change By:


Jesse Bowes
(07/Jan/15 8:17 PM)




Description:


Under the Boot Up Vagrant VM task, specifying a relative path to the Vagrantfile doesnt work.Tried: ./Vagrantfile and VagrantfileIt appears as though 'vagrant up' tries to execute in /leaving the field empty gives a stack trace:
{noformat}
java.lang.NullPointerException	at java.util.regex.Matcher.getTextLength(Matcher.java:1234)	at java.util.regex.Matcher.reset(Matcher.java:308)	at java.util.regex.Matcher.(Matcher.java:228)	at java.util.regex.Pattern.matcher(Pattern.java:1088)	at hudson.FilePath.normalize(FilePath.java:285)	at hudson.FilePath.(FilePath.java:230)	at org.jenkinsci.plugins.vagrant.VagrantWrapper.parseVagrantEnvironment(VagrantWrapper.java:107)	at org.jenkinsci.plugins.vagrant.VagrantWrapper.validate(VagrantWrapper.java:184)	at org.jenkinsci.plugins.vagrant.VagrantWrapper.executeCommand(VagrantWrapper.java:133)	at org.jenkinsci.plugins.vagrant.VagrantUpCommand.perform(VagrantUpCommand.java:101)	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)	at hudson.model.Build$BuildExecution.build(Build.java:199)	at hudson.model.Build$BuildExecution.doRun(Build.java:160)	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533)	at hudson.model.Run.execute(Run.java:1745)	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)	at hudson.model.ResourceController.execute(ResourceController.java:89)	at hudson.model.Executor.run(Executor.java:240)
{noformat}


I can fix this by using the full path (/var/lib/jenkins/jobs/project/workspace/Vagrantfile), but it's not ideal



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [vagrant-plugin] (JENKINS-26326) Boot up Vagrant VM not using relative path

2015-01-07 Thread jess...@gmail.com (JIRA)














































Jesse Bowes
 updated  JENKINS-26326


Boot up Vagrant VM not using relative path
















Change By:


Jesse Bowes
(07/Jan/15 8:08 PM)




Description:


Under the Boot Up Vagrant VM task, specifying a relative path to the Vagrantfile doesnt work.Tried: ./Vagrantfile and VagrantfileIt appears as though 'vagrant up' tries to execute in /
leaving the field empty gives a stack trace:java.lang.NullPointerException	at java.util.regex.Matcher.getTextLength(Matcher.java:1234)	at java.util.regex.Matcher.reset(Matcher.java:308)	at java.util.regex.Matcher.(Matcher.java:228)	at java.util.regex.Pattern.matcher(Pattern.java:1088)	at hudson.FilePath.normalize(FilePath.java:285)	at hudson.FilePath.(FilePath.java:230)	at org.jenkinsci.plugins.vagrant.VagrantWrapper.parseVagrantEnvironment(VagrantWrapper.java:107)	at org.jenkinsci.plugins.vagrant.VagrantWrapper.validate(VagrantWrapper.java:184)	at org.jenkinsci.plugins.vagrant.VagrantWrapper.executeCommand(VagrantWrapper.java:133)	at org.jenkinsci.plugins.vagrant.VagrantUpCommand.perform(VagrantUpCommand.java:101)	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)	at hudson.model.Build$BuildExecution.build(Build.java:199)	at hudson.model.Build$BuildExecution.doRun(Build.java:160)	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533)	at hudson.model.Run.execute(Run.java:1745)	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)	at hudson.model.ResourceController.execute(ResourceController.java:89)	at hudson.model.Executor.run(Executor.java:240)
I can fix this by using the full path (/var/lib/jenkins/jobs/project/workspace/Vagrantfile), but it's not ideal



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [vagrant-plugin] (JENKINS-26326) Boot up Vagrant VM not using relative path

2015-01-07 Thread jess...@gmail.com (JIRA)














































Jesse Bowes
 created  JENKINS-26326


Boot up Vagrant VM not using relative path















Issue Type:


Bug



Assignee:


Unassigned


Components:


vagrant-plugin



Created:


07/Jan/15 8:00 PM



Description:


Under the Boot Up Vagrant VM task, specifying a relative path to the Vagrantfile doesnt work.

Tried: 
./Vagrantfile and Vagrantfile

It appears as though 'vagrant up' tries to execute in /

I can fix this by using the full path (/var/lib/jenkins/jobs/project/workspace/Vagrantfile), but it's not ideal




Project:


Jenkins



Priority:


Minor



Reporter:


Jesse Bowes

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [gradle-jpi-plugin] (JENKINS-25643) Not able to use example build.gradle file with Java 8

2015-01-07 Thread m...@daniel-spilker.com (JIRA)















































Daniel Spilker
 resolved  JENKINS-25643 as Fixed


Not able to use example build.gradle file with Java 8
















Fixed in 0.8.0.





Change By:


Daniel Spilker
(07/Jan/15 7:23 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [gradle-jpi-plugin] (JENKINS-25643) Not able to use example build.gradle file with Java 8

2015-01-07 Thread m...@daniel-spilker.com (JIRA)















































Daniel Spilker
 closed  JENKINS-25643 as Fixed


Not able to use example build.gradle file with Java 8
















Change By:


Daniel Spilker
(07/Jan/15 7:23 PM)




Status:


Resolved
Closed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [libvirt-slave-plugin] (JENKINS-12523) Could not initialize class org.libvirt.Connect

2015-01-07 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 commented on  JENKINS-12523


Could not initialize class org.libvirt.Connect















G. Kr. Do you have the sources for your change somewhere?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [dashboard-view-plugin] (JENKINS-26325) Invalid test results link

2015-01-07 Thread dtho...@willowgarage.com (JIRA)














































Dirk Thomas
 updated  JENKINS-26325


Invalid test results link
















Change By:


Dirk Thomas
(07/Jan/15 7:18 PM)




Description:


A dashboard-view with the column "Test Result" (with
 format
 "Test
 result
 format
 2") shows invalid links to the test results.In the case of the example view referenced as the URL the link points to:http://54.183.26.131:8080/view/wrong_test_result_link/view/wrong_test_result_link/job/IdevS32__catkin__ubuntu_saucy_i386/lastCompletedBuild/testReport/The URL contains the "view/VIEWNAME" part twice and is therefore invalid.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [dashboard-view-plugin] (JENKINS-26325) Invalid test results link

2015-01-07 Thread dtho...@willowgarage.com (JIRA)














































Dirk Thomas
 created  JENKINS-26325


Invalid test results link















Issue Type:


Bug



Assignee:


Peter Hayes



Components:


dashboard-view-plugin



Created:


07/Jan/15 7:16 PM



Description:


A dashboard-view with the column "Test Result" (with format "Test result 2") shows invalid links to the test results.

In the case of the example view referenced as the URL the link points to:

http://54.183.26.131:8080/view/wrong_test_result_link/view/wrong_test_result_link/job/IdevS32__catkin__ubuntu_saucy_i386/lastCompletedBuild/testReport/

The URL contains the "view/VIEWNAME" part twice and is therefore invalid.




Environment:


Jenkins 1.594, dashboard-view plugin 2.9.4




Project:


Jenkins



Priority:


Major



Reporter:


Dirk Thomas

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [envinject-plugin] (JENKINS-26302) REGRESSION: Node environment doesn't work

2015-01-07 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 updated  JENKINS-26302


REGRESSION: Node environment doesn't work
















Assigning to envinject.

If you could provide the last plugin version that is known to work, and the one that broke, that would be helpful.





Change By:


Daniel Beck
(07/Jan/15 7:05 PM)




Component/s:


envinject-plugin





Component/s:


core



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [core] (JENKINS-26312) Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden

2015-01-07 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 commented on  JENKINS-26312


Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden
















#footer-container {
	display: none;
}

This Simple Theme plugin CSS works for me as workaround, without SCM Sync Plugin.

If you don't want to remove the footer entirely (e.g. to keep SCM Sync info), something like the following removes all the crap and reduces vertical space used:

#footer .page_generated {
	display: none;
}
#footer .rest_api {
	display: none;
}
#footer .jenkins_ver {
	display: none;
}
#footer .page_generated {
	display: none;
}
#footer #l10n-footer { // Localization Plugin
	display: none !important;
}
#footer-container {
	padding: 0px;
}




that's not a minor issue to me at all!

This is NOT a minor issue, I'm unable to save/apply any changes only if I change the magnification size of the page.

Feel free to bring this up in the next Governance Meeting of the Jenkins project. I'm just applying the priority as defined in Jira. And it's really not difficult to find the workaround, or apply it. Writing the above rules took maybe five minutes.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [build-pipeline-plugin] (JENKINS-23828) Build Pipeline View doesn't show build user id on Downstream Projects

2015-01-07 Thread pat...@diabol.se (JIRA)














































Patrik Boström
 commented on  JENKINS-23828


Build Pipeline View doesn't show build user id on Downstream Projects















It looks to be related to JENKINS-19755



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [core] (JENKINS-25026) Console output stops populating after several seconds

2015-01-07 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 commented on  JENKINS-25026


Console output stops populating after several seconds















The last response, after which the page stops polling, looks like this:

What's the HTTP response code for this response?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [junit-plugin] (JENKINS-24946) JUnit Tests Results fail to archive in V1.582

2015-01-07 Thread dan...@beckweb.net (JIRA)















































Daniel Beck
 resolved  JENKINS-24946 as Cannot Reproduce


JUnit Tests Results fail to archive in V1.582
















Alright, resolving this as Cannot Reproduce as upgrading from 1.1 to 1.2 seems like a viable solution. 1.3 has the incompatibility problem but that's inherent in the current dependency declaration / LTS versioning, so please look the other way 

(Also, weekly releases are only considered supported for a week, which means if you're still running 1.594 or 1.595, you're on your own  )





Change By:


Daniel Beck
(07/Jan/15 6:43 PM)




Status:


Open
Resolved





Resolution:


Cannot Reproduce



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [promoted-builds-plugin] (JENKINS-18385) in a build script

2015-01-07 Thread don.me...@sial.com (JIRA)














































Don Meuth
 updated  JENKINS-18385


in a build script
















Change By:


Don Meuth
(07/Jan/15 6:16 PM)




Summary:


accept groups for "users" that can run
in
 a
 manual promotion
 build script



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [linenumbers-plugin] (JENKINS-26322) Line numbers always '1'

2015-01-07 Thread vinc...@latombe.net (JIRA)














































Vincent Latombe
 commented on  JENKINS-26322


Line numbers always '1'















Indeed, the recent layout changed broke the css, I pushed a fix and released 1.1.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [linenumbers-plugin] (JENKINS-26322) Line numbers always '1'

2015-01-07 Thread scm_issue_l...@java.net (JIRA)















































SCM/JIRA link daemon
 resolved  JENKINS-26322 as Fixed


Line numbers always '1'
















Change By:


SCM/JIRA link daemon
(07/Jan/15 5:51 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [linenumbers-plugin] (JENKINS-26322) Line numbers always '1'

2015-01-07 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-26322


Line numbers always '1'















Code changed in jenkins
User: Vincent LATOMBE
Path:
 src/main/resources/org/jenkinsci/plugins/linenumbers/LineNumbersAnnotatorFactory/style.css
http://jenkins-ci.org/commit/linenumbers-plugin/a0aa00e3cd91cb35a3c9379e05f6d468e18eefa2
Log:
  [FIXED JENKINS-26322] Widen css selector for compatibility with new layout





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [gerrit-plugin] (JENKINS-26323) The "Build Current Patches Only" only works, if NO parameters in the build are altered

2015-01-07 Thread martin.h.schroe...@intel.com (JIRA)














































Martin Schröder
 updated  JENKINS-26323


The "Build Current Patches Only" only works, if NO parameters in the build are altered
















Change By:


Martin Schröder
(07/Jan/15 5:26 PM)




Description:


The "Build Current Patches Only" feature currently identifies previous builds based on their parameters as they were present when the build was first scheduled.If you use a plugin that alters the parameters after the job has started, the cancelling of previous builds does not work, since the GerritTrigger#cancelJob() method does not find the job anymore.This is easily and trivially fixed, by not scanning for the parameters, but instead for the GerritEvent that is stored in the GerritCause used to start a build.A pull request has been uploaded here: https://github.com/jenkinsci/gerrit-trigger-plugin/pull/
194
195



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [linenumbers-plugin] (JENKINS-26322) Line numbers always '1'

2015-01-07 Thread vinc...@latombe.net (JIRA)












































  
Vincent Latombe
 edited a comment on  JENKINS-26322


Line numbers always '1'
















What browser do you use? The numbering relies on css features that may not be implemented the same way in all browsers... Another possibility is that some recent change in the core changed the generated markup, breaking the plugin altogether.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [linenumbers-plugin] (JENKINS-26322) Line numbers always '1'

2015-01-07 Thread vinc...@latombe.net (JIRA)














































Vincent Latombe
 commented on  JENKINS-26322


Line numbers always '1'















What browser do you use? The numbering relies on css features that may not be implemented the same way in all browsers...



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [core] (JENKINS-25971) Job list and console output are not properly aligned in the new UI

2015-01-07 Thread seventhso...@gmail.com (JIRA)














































Steven Murphy
 updated  JENKINS-25971


Job list and console output are not properly aligned in the new UI
















Screen shot of the Console Output page in 1.596.  Note the bullet points to the left of the ant target names.

(of course the black box has been added by me to obscure file names etc...)





Change By:


Steven Murphy
(07/Jan/15 5:07 PM)




Attachment:


ConsoleOutput_1.596.jpg



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [core] (JENKINS-25971) Job list and console output are not properly aligned in the new UI

2015-01-07 Thread seventhso...@gmail.com (JIRA)














































Steven Murphy
 updated  JENKINS-25971


Job list and console output are not properly aligned in the new UI
















Screen shot of 1.594 Console Output screen 

(of course the black box has been added by me to blank out file names etc...)





Change By:


Steven Murphy
(07/Jan/15 5:06 PM)




Attachment:


ConsoleOutput_1.594.jpg



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [mesos-plugin] (JENKINS-26324) Add configurable bridged network mode for Docker containers

2015-01-07 Thread eder_ste...@gmx.at (JIRA)














































Stefan Eder
 created  JENKINS-26324


Add configurable bridged network mode for Docker containers















Issue Type:


New Feature



Assignee:


Vinod Kone



Components:


mesos-plugin



Created:


07/Jan/15 4:48 PM



Description:


With Mesos 0.20.1 bridged network mode support for docker containers was introduced (https://issues.apache.org/jira/browse/MESOS-1621).

To enable this feature for Jenkins mesos-plugin users the plugin needs the following adaptions:

	Let users configure "HOST" or "BRIDGE" networking
	(Optional) Let users add port mappings for "BRIDGE" networking



The options should be configurable in the in the Docker container configuration part of the Mesos cloud configuration.

A pull request for this feature is on the way...




Project:


Jenkins



Priority:


Minor



Reporter:


Stefan Eder

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [core] (JENKINS-26312) Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden

2015-01-07 Thread etienne.ba...@gmail.com (JIRA)














































Etienne BAALI
 commented on  JENKINS-26312


Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden















Hello,
Same thing here.
If you don't want to downgrade version, you can show up the button if you go to bottom and set full screen (F11).



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [gerrit-plugin] (JENKINS-26323) The "Build Current Patches Only" only works, if NO parameters in the build are altered

2015-01-07 Thread martin.h.schroe...@intel.com (JIRA)














































Martin Schröder
 updated  JENKINS-26323


The "Build Current Patches Only" only works, if NO parameters in the build are altered
















Change By:


Martin Schröder
(07/Jan/15 4:36 PM)




Description:


The "Build Current Patches Only" feature currently identifies previous builds based on their parameters as they were present when the build was first scheduled.If you use a plugin that alters the parameters after the job has started, the cancelling of previous builds does not work, since the GerritTrigger#cancelJob() method does not find the job anymore.This is easily and trivially fixed, by not scanning for the parameters, but instead for the GerritEvent that is stored in the GerritCause used to start a build.A pull request
 will be
 has been
 uploaded
 ASAP
 here: https://github
.
com/jenkinsci/gerrit-trigger-plugin/pull/194





Labels:


abort gerrit gerrit-trigger





URL:


https://github.com/jenkinsci/gerrit-trigger-plugin/pull/194



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


  1   2   >