date:20150828

2015-08-28 Thread ebrahim.mosh...@newvoicemedia.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick commented on  JENKINS-30166 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Implement an SCMSource for BitBucket  
 
 
 
 
 
 
 
 
 
 
Number one is unfortunate. Have you contacted Atlassian asking whether they intend to add functionality comparable to this? 

BB is managing PRs as independent repositories (not as refs in the same repository like GitHub does)
 
Well, GitHub of course manages PRs as independent repositories, it just also offers them as refs in origin as a convenience. 
Number two does not seem like an issue. Your SCMHead implementation would merely need to encode the fork owner’s name, or the pull request number, etc., and return an appropriately-configured GitSCM when build is called. 
Nothing about SCMSource is forcing the SCM instances an implementation generates to have anything particular in common; certainly it knows nothing of hudson.plugins.git.UserRemoteConfig. Perhaps you are confused because you are extending AbstractGitSCMSource, which does currently assume that it is operating on a single remote. Either that needs to be generalized, or you just need to extend SCMSource directly. (The only valuable parts of AbstractGitSCMSource are the caching code, which ideally we would like to not use at all, though that depends on issue number one, so maybe it could be factored out into a static utility method; and SpecificRevisionBuildChooser, which is public static so it looks like it can be reused.) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [multijob-plugin] (JENKINS-26509) The build project should return success, if all phases returned success, even not all the phases have been triggered based on the designed condition

2015-08-28 Thread hudson...@java.net (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 hudsonfsc commented on  JENKINS-26509 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: The build project should return success, if all phases returned success, even not all the phases have been triggered based on the designed condition  
 
 
 
 
 
 
 
 
 
 
We have a similar constellation and also the same problem! Please fix this! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-30177) Git checkout fails when branch is not */master

2015-08-28 Thread mark.earl.wa...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite commented on  JENKINS-30177 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Git checkout fails when branch is not */master  
 
 
 
 
 
 
 
 
 
 
That's a relief. Thanks! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [acceptance-test-harness] (JENKINS-30009) Generates Dockerfile programmatically from DockerContainer

2015-08-28 Thread asotobu...@cloudbees.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Soto commented on  JENKINS-30009 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Generates Dockerfile programmatically from DockerContainer  
 
 
 
 
 
 
 
 
 
 
Well there is one use case which would be better. If you see on SSHD example in https://github.com/jenkinsci/acceptance-test-harness/blob/master/src/main/resources/org/jenkinsci/test/acceptance/docker/fixtures/SshdContainer/Dockerfile the keys are hardcoded directly, but in the test https://github.com/jenkinsci/acceptance-test-harness/blob/master/src/main/java/org/jenkinsci/test/acceptance/docker/fixtures/SshdContainer.java are get directly from the test folder where the keys where generated. Of course you can do what is done here of copying paste the keys, but this is in my opinion not the best way since you may have failures of test because of any change of keys, but not changing them in Dockerfile. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-21622) Build creates new workspace@2 (and so on) when option concurrent builds NOT checked

2015-08-28 Thread mark.earl.wa...@gmail.com (JIRA)

Title: Message Title

Mark Waite commented on JENKINS-21622

Re: Build creates new workspace@2 (and so on) when option concurrent builds NOT checked

Onur Ozardic you will need to provide much more information about the conditions which show the problem. I doubt a developer will be persuaded to spend significant time trying to guess the conditions under which you have seen the problem. Even if they do spend that time guessing more about the problem, they may guess incorrectly and fix something that is not the issue you've seen.
Please provide step by step instructions which show the problem, preferably on a clean installation of a recent Jenkins version (either the current long term support version or the most recent weekly version). You may also help by installing the support plugin and including the information from that plugin. Or, at least include the versions of plugins you're using in addition to the command line git version you have installed.

Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[JIRA] [docker-custom-build-environment-plugin] (JENKINS-30113) Environment variables aren't passed to the docker container anymore

2015-08-28 Thread nicolas.del...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nicolas De Loof commented on  JENKINS-30113 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Environment variables aren't passed to the docker container anymore  
 
 
 
 
 
 
 
 
 
 
It's not just by accident. Docker container should not inherit the full slave env (PATH for sample can be fully irrelevant) Need to build a custom env map using various env sources (scm, build parameters, build actions...).  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-30199) No aggregated test result trend graph for matrix job

2015-08-28 Thread blatinvill...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bertrand Latinville created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-30199 
 
 
 
  No aggregated test result trend graph for matrix job  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 config.xml, jenkins1.565.3.png, jenkins1.690.2.png 
 
 
 

Components:
 

 junit-plugin 
 
 
 

Created:
 

 28/Aug/15 1:54 PM 
 
 
 

Environment:
 

 Jenkins 1.690.2, Junit 1.8 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Bertrand Latinville 
 
 
 
 
 
 
 
 
 
 
I'm testing an upgrade from Jenkins 1.565.3 to Jenkins 1.690.2 
I noticed that for a matrix job, there is no Test Result Trend graph on the main page of a matrix job. The aggregated tests result of each configuration is present,  only the graph is missing. 
The direct URL which shows the graph: JENKINS_URL/job/job_name/test/ does not exist any more with 1.690.2 It only exists for each configuration: JENKINS_URL/job/job_name/axis=one/test/

[JIRA] [p4-plugin] (JENKINS-24591) Unable to run perforce commands within build steps

2015-08-28 Thread s_tunney2...@yahoo.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stephen Tunney commented on  JENKINS-24591 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Unable to run perforce commands within build steps  
 
 
 
 
 
 
 
 
 
 
P4User, P4Client, P4Port should all be exposed IMO. I would really like to see this implemented. My NAnt scripts are dying without it!!!  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-custom-build-environment-plugin] (JENKINS-29410) Compatibility with Sonar plugin (and possibly other auto installed software)

2015-08-28 Thread nicolas.del...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nicolas De Loof reopened an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
an issue remain, as we can't amend the PATH defined by container so the toolinstaller get well setup 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-29410 
 
 
 
  Compatibility with Sonar plugin (and possibly other auto installed software)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nicolas De Loof 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Closed Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-30177) Git checkout fails when branch is not */master

2015-08-28 Thread mike.ba...@32past8.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Bauer closed an issue as Not A Defect 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
This was user error on my part... 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-30177 
 
 
 
  Git checkout fails when branch is not */master  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Bauer 
 
 
 

Status:
 
 Open Closed 
 
 
 

Resolution:
 
 NotADefect 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-30177) Git checkout fails when branch is not */master

2015-08-28 Thread mike.ba...@32past8.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Bauer commented on  JENKINS-30177 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Git checkout fails when branch is not */master  
 
 
 
 
 
 
 
 
 
 
Ugh, now I feel stupid. That was exactly the problem. Thanks for sticking in there with me. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [ec2-plugin] (JENKINS-23787) EC2-plugin not spooling up stopped nodes - still in the queue ... all nodes of label ... are offline

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ebrahim Moshaya commented on  JENKINS-23787 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: EC2-plugin not spooling up stopped nodes - still in the queue ... all nodes of label ... are offline  
 
 
 
 
 
 
 
 
 
 
I'm having the same issue with Jenkins 1.626 and ec2 plugin 1.29. None of the offline ec2 slaves are starting up when the matrix job starts. Instead I have to manually start them up. Does anyone have a solution for this? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [subversion-plugin] (JENKINS-30197) Migration from Subversion 1.x to 2.5.1+ can fail (ClassCastException on SCM)

2015-08-28 Thread tom...@free.fr (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas de Grenier de Latour created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-30197 
 
 
 
  Migration from Subversion 1.x to 2.5.1+ can fail (ClassCastException on SCM)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 subversion-plugin 
 
 
 

Created:
 

 28/Aug/15 12:25 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Thomas de Grenier de Latour 
 
 
 
 
 
 
 
 
 
 
The Credentials migration code added in subversion-plugin 2.5.1 fails when hitting a job which is not (anymore?) using SubversionSCM, but which still has a subversion.credentials file in its job directory. 
SEVERE: Failed SubversionSCM.perJobCredentialsMigration java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:109) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:105) ... 8 more Caused

[JIRA] [subversion-plugin] (JENKINS-30197) Migration from Subversion 1.x to 2.5.1+ can fail (ClassCastException on SCM)

2015-08-28 Thread rec...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jess Recena Soto updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-30197 
 
 
 
  Migration from Subversion 1.x to 2.5.1+ can fail (ClassCastException on SCM)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jess Recena Soto 
 
 
 
 
 
 
 
 
 
 TheCredentialsmigrationcodeaddedinsubversion-plugin2.5.1failswhenhittingajobwhichisnot(anymore?)usingSubversionSCM,butwhichstillhasasubversion.credentialsfileinitsjobdirectory. {code} SEVERE:FailedSubversionSCM.perJobCredentialsMigrationjava.lang.Error:java.lang.reflect.InvocationTargetExceptionathudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:109)athudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:169)atorg.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)atjenkins.model.Jenkins$7.runTask(Jenkins.java:903)atorg.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)atorg.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)atjava.lang.Thread.run(Thread.java:745)Causedby:java.lang.reflect.InvocationTargetExceptionatsun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod)atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)atjava.lang.reflect.Method.invoke(Method.java:606)athudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:105)...8moreCausedby:java.lang.ClassCastException:hudson.plugins.git.GitSCMcannotbecasttohudson.scm.SubversionSCMathudson.scm.PerJobCredentialStore.migrateCredentials(PerJobCredentialStore.java:120)athudson.scm.SubversionSCM$DescriptorImpl.migratePerJobCredentials(SubversionSCM.java:1651)athudson.scm.SubversionSCM.perJobCredentialsMigration(SubversionSCM.java:1582)...13more {code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[JIRA] [teamconcert-plugin] (JENKINS-27464) Workflow integration with Team Concert plugin

2015-08-28 Thread scm_issue_l...@java.net (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-27464 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Workflow integration with Team Concert plugin  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/749c67865b40c293b15aa777ad4f263d23e1e907 Log: 

JENKINS-27464
 Noting. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [sauce-ondemand-plugin] (JENKINS-29843) Can't install Sauce OnDemand Plugin

2015-08-28 Thread toby.broy...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Toby Broyles commented on  JENKINS-29843 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Can't install Sauce OnDemand Plugin  
 
 
 
 
 
 
 
 
 
 
Sorry for the delay. I stopped jenkins and removed the directory. I left the sauce-ondemand.jpi file in place and then started it back up. I then tried the install again and received the same error. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [parameterized-trigger-plugin] (JENKINS-11257) Stopping a parent job doesn't stop the triggered child jobs

2015-08-28 Thread sschube...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sebastian Schuberth commented on  JENKINS-11257 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Stopping a parent job doesn't stop the triggered child jobs  
 
 
 
 
 
 
 
 
 
 
ikedam Do you have a convincing example for a use case where it actually makes sense to continue running the triggered jobs when the parent build has been stopped by the user? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [p4-plugin] (JENKINS-25242) p4-plugin: Doesn't do concurrent builds

2015-08-28 Thread david.pars...@gmail.com (JIRA)

Title: Message Title

David Prsson commented on JENKINS-25242

Re: p4-plugin: Doesn't do concurrent builds

I tried to get around this by using Manual (custom view) together with a workspace name like this: Jenkins-${JOB_NAME}-${NODE_NAME}-${EXECUTOR_NUMBER}-workspace. I thought this should work since the executor number is unique for concurrent builds when running on a single node (as I did), which should make the workspace name unique.
When running one build at a time, everything works fine, but when running several concurrent builds, I only managed to get the first of the concurrent builds to fetch files from the repository. Any other concurrent build's workspaces were empty. This happens every time when I launch a build while another build is running, even when the other build is done running its P4 commands.
I'm using the P4 Plugin v1.1.4 on Jenkins 1.565.3 (LTS). This issue is a blocker for us and many other large companies, requiring fast feedback for frequent commits.

Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[JIRA] [acceptance-test-harness] (JENKINS-30009) Generates Dockerfile programmatically from DockerContainer

2015-08-28 Thread ebrahim.mosh...@newvoicemedia.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick commented on  JENKINS-30009 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Generates Dockerfile programmatically from DockerContainer  
 
 
 
 
 
 
 
 
 
 
Also an advantage of the existing system is that you can work on the Dockerfile (and/or its associated resource files) without even running acceptance tests, just by using docker build -t testing src/main/resources/org/jenkinsci/test/acceptance/docker/fixtures/Whatever  docker run -ti testing /bin/bash. Since the tests can take several minutes apiece to run, this is a much more pleasant way to play with minor modifications to the container before you check your work in the actual test. I recall doing that for XvncSlaveContainer: before trying to run Jenkins and its XVNC plugin against the server, I first needed to do a lot of experimentation to get permissions and the like right, and these could be simulated just by running the container, logging in as the Jenkins user, and checking if xmessage or the like ran without errors. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-custom-build-environment-plugin] (JENKINS-30113) Environment variables aren't passed to the docker container anymore

2015-08-28 Thread scm_issue_l...@java.net (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-30113 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Environment variables aren't passed to the docker container anymore  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Nicolas De Loof Path: src/main/java/com/cloudbees/jenkins/plugins/docker_build_env/Docker.java src/main/java/com/cloudbees/jenkins/plugins/docker_build_env/DockerBuildWrapper.java http://jenkins-ci.org/commit/docker-custom-build-environment-plugin/79e47f51a82cb66bdb44bf0c5b03460edc6f0cbd Log: JENKINS-30113 configure container with a subset of build environment 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [matrix-combinations-parameter-plugin] (JENKINS-24023) Matrix unformatted

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ebrahim Moshaya commented on  JENKINS-24023 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Matrix unformatted  
 
 
 
 
 
 
 
 
 
 
I fully agree this is annoying. I would love to have the axis in a table 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [p4-plugin] (JENKINS-24591) Unable to run perforce commands within build steps

2015-08-28 Thread morne.joub...@u-blox.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Morne Joubert commented on  JENKINS-24591 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Unable to run perforce commands within build steps  
 
 
 
 
 
 
 
 
 
 
Currently the env that are set are: P4_CHANGELIST P4_CLIENT P4_PORT 
from the following code 
public void buildEnvVars(AbstractBuild?, ? build, MapString, String env) { super.buildEnvVars(build, env); 
 TagAction tagAction = build.getAction(TagAction.class); if (tagAction != null) { // Set P4_CHANGELIST value if (tagAction.getBuildChange() != null)  { String change = getChangeNumber(tagAction); env.put(P4_CHANGELIST, change); } 
 // Set P4_CLIENT workspace value if (tagAction.getClient() != null)  { String client = tagAction.getClient(); env.put(P4_CLIENT, client); } 
 // Set P4_PORT connection if (tagAction.getPort() != null)  { String port = tagAction.getPort(); env.put(P4_PORT, port); } 
 } } 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-plugin] (JENKINS-30200) Nullpointer exception while connecting to a docker container

2015-08-28 Thread gentoo.inte...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou commented on  JENKINS-30200 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Nullpointer exception while connecting to a docker container  
 
 
 
 
 
 
 
 
 
 
https://github.com/jenkinsci/docker-plugin/blob/master/CONTRIBUTING.md 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-custom-build-environment-plugin] (JENKINS-29621) EnvInject Plugin is only working to a limited extent in combination with the docker build environment

2015-08-28 Thread nicolas.del...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nicolas De Loof commented on  JENKINS-29621 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: EnvInject Plugin is only working to a limited extent in combination with the docker build environment  
 
 
 
 
 
 
 
 
 
 
Stefan Kahlhfer no, issue here is that you can't change environment for a container after it has been started, so only variable set before the build start can be used. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-custom-build-environment-plugin] (JENKINS-30113) Environment variables aren't passed to the docker container anymore

2015-08-28 Thread evan.pow...@hypori.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Evan Powell commented on  JENKINS-30113 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Environment variables aren't passed to the docker container anymore  
 
 
 
 
 
 
 
 
 
 
Certainly a fair point - and some env vars could potentially mess up the execution environment, $PATH included. 
Thanks for the update and the more extensive changeset. I had a mind to try my hand at this today, but you're already on it.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-plugin] (JENKINS-30200) Nullpointer exception while connecting to a docker container

2015-08-28 Thread ashish_b...@yahoo.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ashish Behl created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-30200 
 
 
 
  Nullpointer exception while connecting to a docker container  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Kanstantsin Shautsou 
 
 
 

Components:
 

 docker-plugin 
 
 
 

Created:
 

 28/Aug/15 3:23 PM 
 
 
 

Environment:
 

 Linux, Docker plugin, docker 1.8.1 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Ashish Behl 
 
 
 
 
 
 
 
 
 
 
Jenkins ver. 1.626 Docker plugin version: 0.12.1 


Container settings:
 Docker command: /sbin/init 3 (without custom command also crashes) Hostname: debian8_32bit_32bit_INIT3_CONTAINER DNS: Some ip address Volumes: /sys/fs/cgroup:/sys/fs/cgroup:ro Environment: container=docker Privileged : true Remote filing root: /home/jenkins labels: debian8_32bit_32bit_INIT3_CONTAINER 
Port: 22 


Problem:
 Crash when running a job. The container is started within docker server but jenkins cannot see it. Jenkins logs state: 
Aug 28, 2015 2:29:20 PM com.nirima.jenkins.plugins.docker.DockerCloud provision INFORMATION: Asked to provision 1

[JIRA] [bitbucket-plugin] (JENKINS-30166) Implement an SCMSource for BitBucket

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick commented on  JENKINS-30166 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Implement an SCMSource for BitBucket  
 
 
 
 
 
 
 
 
 
 
BTW even if the official REST API does not have special support for file contents, by spending a couple minutes browsing their web UI it seems you can get the equivalent: 

 

$ curl -Is https://bitbucket.org/jglick/yenta/raw/default/README.md | fgrep HTTP/
HTTP/1.1 200 OK
$ curl -Is https://bitbucket.org/jglick/yenta/raw/default/Jenkins | fgrep HTTP/
HTTP/1.1 404 NOT FOUND
 

 
Now how this would work on a private repository is another question. Can you send BASIC auth, etc.? Experiment. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-24352) Unneccessary line breaks in JUnit test results table since 1.576

2015-08-28 Thread kzan...@cloudbees.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Keith Zantow assigned an issue to Keith Zantow 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-24352 
 
 
 
  Unneccessary line breaks in JUnit test results table since 1.576  
 
 
 
 
 
 
 
 
 

Change By:
 
 Keith Zantow 
 
 
 

Assignee:
 
 TomFENNELLY KeithZantow 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-24352) Unneccessary line breaks in JUnit test results table since 1.576

2015-08-28 Thread kzan...@cloudbees.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Keith Zantow started work on  JENKINS-24352 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 

Change By:
 
 Keith Zantow 
 
 
 

Status:
 
 Open InProgress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [acceptance-test-harness] (JENKINS-30009) Generates Dockerfile programmatically from DockerContainer

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick commented on  JENKINS-30009 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Generates Dockerfile programmatically from DockerContainer  
 
 
 
 
 
 
 
 
 
 
It is the fixture, not the test, which defines the private keys. 
In this case it is probably a simple mistake that the Dockerfile redundandly hardcodes the public keys, rather than loading them from the resources directory where they are already defined: 

 

COPY unsafe.pub unsafe_enc_key.pub /tmp/
RUN cat /tmp/*.pub  /home/test/.ssh/authorized_keys
 

 
With that fixed, there is not much real chance of mistakes when working on the fixture, since the public and private keys are all plainly grouped in one source directory. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [acceptance-test-harness] (JENKINS-30009) Generates Dockerfile programmatically from DockerContainer

2015-08-28 Thread asotobu...@cloudbees.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Soto commented on  JENKINS-30009 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Generates Dockerfile programmatically from DockerContainer  
 
 
 
 
 
 
 
 
 
 
In any case I wanted to remove the other way, simply I wanted to add more features. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-24352) Unneccessary line breaks in JUnit test results table since 1.576

2015-08-28 Thread kzan...@cloudbees.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Keith Zantow commented on  JENKINS-24352 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Unneccessary line breaks in JUnit test results table since 1.576  
 
 
 
 
 
 
 
 
 
 
For JUnit test results specifically, fixed in: https://github.com/jenkinsci/junit-plugin/pull/26 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [p4-plugin] (JENKINS-24591) Unable to run perforce commands within build steps

2015-08-28 Thread pal...@perforce.com (JIRA)

Title: Message Title

Paul Allen commented on JENKINS-24591

Re: Unable to run perforce commands within build steps

I can add P4_USER, but how would you like me to do auth?
If the Job is running on the slave or master then in theory the local .p4ticket file should contain a valid ticket. The alternatives are less than ideal e.g. exposing the user's Password/Ticket.
I had an additional idea, not to solve this issue, but could prove to be useful:
The initial thinking behind not exposing P4PORT/P4CLIENT etc... was that the plugin would manage all P4 tasks. As the plugin uses p4java there is no need to deploy the 'p4' executable on the slave. My proposal is to add lots of additional p4 steps to the build steps, for example: add/edit/delete a file integ/copy a path sync/print a file
I know it won't help p4ant/p4maven, but perhaps people are scripting p4 commands? Feel free to spin this off onto another ISSUE if you think it could be useful.

Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[JIRA] [core] (JENKINS-30084) FlyWeightTasks tied to a label will not cause node provisioning and will be blocked forever.

2015-08-28 Thread tsack...@adobe.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tom Sackett commented on  JENKINS-30084 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: FlyWeightTasks tied to a label will not cause node provisioning and will be blocked forever.  
 
 
 
 
 
 
 
 
 
 
I think I have a use case, but it's related to jobs based on the Build Flow plugin (which also appears to be affected by this bug), rather than matrix jobs. A build flow job that polls Perforce has to be assigned to a machine that can run Perforce commands. Large organizations often put additional security on Perforce that includes limiting which machines can access Perforce servers using automation accounts, so we can't always configure the master to access Perforce. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [job-dsl-plugin] (JENKINS-30201) Job DSL plugin should expose additional Build Flow settings

2015-08-28 Thread r...@akom.net (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexander Komarov created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-30201 
 
 
 
  Job DSL plugin should expose additional Build Flow settings  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Daniel Spilker 
 
 
 

Components:
 

 job-dsl-plugin 
 
 
 

Created:
 

 28/Aug/15 4:02 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Alexander Komarov 
 
 
 
 
 
 
 
 
 
 
buildFlowJob currently supports only the buildFlow (dsl) setting. There are two other settings provided by the plugin: buildNeedsWorkspace and dslFile. 
Support for buildNeedsWorkspace is especially important due to a bug in the build flow plugin (JENKINS-22779) which prevents post steps from running unless buildNeedsWorkspace is true. 
Pull request coming shortly. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [p4-plugin] (JENKINS-24591) Unable to run perforce commands within build steps

2015-08-28 Thread s_tunney2...@yahoo.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stephen Tunney commented on  JENKINS-24591 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Unable to run perforce commands within build steps  
 
 
 
 
 
 
 
 
 
 
Add p4 lock and counters commands and you've got yourself a deal!  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-27514) Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM

2015-08-28 Thread clark.boy...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Clark Boylan commented on  JENKINS-27514 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM  
 
 
 
 
 
 
 
 
 
 
To clarify we are not using any cloud plugins so there is no single shared instance special broken here. We run an external process that boot nodes in clouds then adds them as Jenkins slaves via the Jenkins API. When the job is done running on that slave the external process is notified and it removes the slave from jenkins. As a result we add a remove a large number of slaves but all of this happens via the API talking to ssh slaves plugin. We do this because the cloud plugins do indeed have problems. But this means that the bug has to be in the ssh slaves plugin somewhere. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [cloudbees-folder-plugin] (JENKINS-25164) Provide a short $JOB_NAME inside a folder

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
Workaround inside (Unix) shell steps is 

 

${JOB_NAME##*/}
 

 
But not available in other contexts. 
Could be done easily as an EnvironmentContributor (even added to top-level jobs for the sake of consistency). Do not forget the buildEnv.jelly for documentation. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-25164 
 
 
 
  Provide a short $JOB_NAME inside a folder  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Component/s:
 
 cloudbees-folder-plugin 
 
 
 

Component/s:
 
 core 
 
 
 

Assignee:
 
 JesseGlick 
 
 
 

Priority:
 
 Minor Major 
 
 
 

Labels:
 
 folders 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [core] (JENKINS-12289) Multi-line commit messages should be configurable to appear in Email-Ext build change notifications

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Earl commented on  JENKINS-12289 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Multi-line commit messages should be configurable to appear in Email-Ext build change notifications  
 
 
 
 
 
 
 
 
 
 
What is the default content type set to in your global config? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-12289) Multi-line commit messages should be configurable to appear in Email-Ext build change notifications

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Earl commented on  JENKINS-12289 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Multi-line commit messages should be configurable to appear in Email-Ext build change notifications  
 
 
 
 
 
 
 
 
 
 
Looks like you probably need to move the pre inside your format string to be directly around the commit message format characterm. Putting it around the div would do nothing. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-12289) Multi-line commit messages should be configurable to appear in Email-Ext build change notifications

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 sthuthi bhat commented on  JENKINS-12289 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Multi-line commit messages should be configurable to appear in Email-Ext build change notifications  
 
 
 
 
 
 
 
 
 
 
I have even tried putting aroundpreem %m/em/pre. something like this. Still does not work. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-12289) Multi-line commit messages should be configurable to appear in Email-Ext build change notifications

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 sthuthi bhat commented on  JENKINS-12289 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Multi-line commit messages should be configurable to appear in Email-Ext build change notifications  
 
 
 
 
 
 
 
 
 
 
We follow git message like this: 
git first line commit message (blank) git commit message line 2 git commit message line 3 git commit message line 4 
Is that blank line causing it? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-30084) FlyWeightTasks tied to a label will not cause node provisioning and will be blocked forever.

2015-08-28 Thread te...@java.net (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 James Nord assigned an issue to valentina armenise 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-30084 
 
 
 
  FlyWeightTasks tied to a label will not cause node provisioning and will be blocked forever.  
 
 
 
 
 
 
 
 
 

Change By:
 
 James Nord 
 
 
 

Assignee:
 
 valentinaarmenise 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-30084) FlyWeightTasks tied to a label will not cause node provisioning and will be blocked forever.

2015-08-28 Thread te...@java.net (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 James Nord started work on  JENKINS-30084 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 

Change By:
 
 James Nord 
 
 
 

Status:
 
 Open InProgress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-12289) Multi-line commit messages should be configurable to appear in Email-Ext build change notifications

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Earl commented on  JENKINS-12289 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Multi-line commit messages should be configurable to appear in Email-Ext build change notifications  
 
 
 
 
 
 
 
 
 
 
View the source of the message and see what is actually being put into the email. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-12289) Multi-line commit messages should be configurable to appear in Email-Ext build change notifications

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 sthuthi bhat commented on  JENKINS-12289 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Multi-line commit messages should be configurable to appear in Email-Ext build change notifications  
 
 
 
 
 
 
 
 
 
 
So I tried putting pre around %m. Did not work as expected. Question: How to view the source of message? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-12289) Multi-line commit messages should be configurable to appear in Email-Ext build change notifications

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Earl commented on  JENKINS-12289 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Multi-line commit messages should be configurable to appear in Email-Ext build change notifications  
 
 
 
 
 
 
 
 
 
 
Depends on your mail client. You'll have to figure out how to do that. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [ghprb-plugin] (JENKINS-30184) Macros in Commit Status URL lead to bad triggered and started commit status

2015-08-28 Thread otog...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Sinyavskiy commented on  JENKINS-30184 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Macros in Commit Status URL lead to bad triggered and started commit status  
 
 
 
 
 
 
 
 
 
 
I played a little bit more with it, so only some macros do not work: $BUILD_URL, $BUILD_NUMBER, $JENKINS_URL Some do work, for example $JOB_NAME  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-12289) Multi-line commit messages should be configurable to appear in Email-Ext build change notifications

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 sthuthi bhat updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-12289 
 
 
 
  Multi-line commit messages should be configurable to appear in Email-Ext build change notifications  
 
 
 
 
 
 
 
 
 

Change By:
 
 sthuthi bhat 
 
 
 

Attachment:
 
 screenshot-1.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-12289) Multi-line commit messages should be configurable to appear in Email-Ext build change notifications

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 sthuthi bhat updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-12289 
 
 
 
  Multi-line commit messages should be configurable to appear in Email-Ext build change notifications  
 
 
 
 
 
 
 
 
 

Change By:
 
 sthuthi bhat 
 
 
 

Attachment:
 
 screenshot-1.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-12289) Multi-line commit messages should be configurable to appear in Email-Ext build change notifications

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 sthuthi bhat updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-12289 
 
 
 
  Multi-line commit messages should be configurable to appear in Email-Ext build change notifications  
 
 
 
 
 
 
 
 
 

Change By:
 
 sthuthi bhat 
 
 
 

Attachment:
 
 screenshot-1.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-12289) Multi-line commit messages should be configurable to appear in Email-Ext build change notifications

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 sthuthi bhat updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-12289 
 
 
 
  Multi-line commit messages should be configurable to appear in Email-Ext build change notifications  
 
 
 
 
 
 
 
 
 

Change By:
 
 sthuthi bhat 
 
 
 

Comment:
 
 !screenshot-1.png!Sourceoftheemail 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-12289) Multi-line commit messages should be configurable to appear in Email-Ext build change notifications

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 sthuthi bhat commented on  JENKINS-12289 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Multi-line commit messages should be configurable to appear in Email-Ext build change notifications  
 
 
 
 
 
 
 
 
 
 
 
Source of the email 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-12289) Multi-line commit messages should be configurable to appear in Email-Ext build change notifications

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 sthuthi bhat updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-12289 
 
 
 
  Multi-line commit messages should be configurable to appear in Email-Ext build change notifications  
 
 
 
 
 
 
 
 
 
 
Here is the Screenshot for source. 
 
 
 
 
 
 
 
 
 

Change By:
 
 sthuthi bhat 
 
 
 

Attachment:
 
 1.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-12289) Multi-line commit messages should be configurable to appear in Email-Ext build change notifications

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 sthuthi bhat commented on  JENKINS-12289 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Multi-line commit messages should be configurable to appear in Email-Ext build change notifications  
 
 
 
 
 
 
 
 
 
 
Attached screenshot for the source of email.  
This was written in jenkins email Default content: 
bChanges: /bbr div style=padding-left: 30px; padding-bottom: 15px; $ {CHANGES, showPaths=true, showDependencies=true, format=divb%a/b: %r %p /divdiv style=\padding-left:30px;\ — “empre%m/pre/em”/div, pathFormat=/divdiv style=\padding-left:30px;\%p} 
/div 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-12289) Multi-line commit messages should be configurable to appear in Email-Ext build change notifications

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 sthuthi bhat edited a comment on  JENKINS-12289 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Multi-line commit messages should be configurable to appear in Email-Ext build change notifications  
 
 
 
 
 
 
 
 
 
 Attachedscreenshotforthesourceofemail.ThiswaswritteninjenkinsemailDefaultcontent:bChanges:/bbrdivstyle=padding-left:30px;padding-bottom:15px;${CHANGES,showPaths=true,showDependencies=true,format=divb%a/b:%r%p/divdivstyle=\padding-left:30px;\#8212;#8220;empre%m/pre/em#8221;/div,pathFormat=/divdivstyle=\padding-left:30px;\%p}/div 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-12289) Multi-line commit messages should be configurable to appear in Email-Ext build change notifications

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 sthuthi bhat updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-12289 
 
 
 
  Multi-line commit messages should be configurable to appear in Email-Ext build change notifications  
 
 
 
 
 
 
 
 
 

Change By:
 
 sthuthi bhat 
 
 
 

Attachment:
 
 screenshot-1.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-12289) Multi-line commit messages should be configurable to appear in Email-Ext build change notifications

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 sthuthi bhat updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-12289 
 
 
 
  Multi-line commit messages should be configurable to appear in Email-Ext build change notifications  
 
 
 
 
 
 
 
 
 

Change By:
 
 sthuthi bhat 
 
 
 

Attachment:
 
 Defaultcontentjenkins.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-12289) Multi-line commit messages should be configurable to appear in Email-Ext build change notifications

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Earl commented on  JENKINS-12289 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Multi-line commit messages should be configurable to appear in Email-Ext build change notifications  
 
 
 
 
 
 
 
 
 
 
The CHANGES token may not support multiple lines, I'd have to look at the source. You can look at the html groovy template in the source code to see how the change set is presented there. 
https://github.com/jenkinsci/email-ext-plugin/blob/master/src/main/resources/hudson/plugins/emailext/templates/groovy-html.template#L31 
This will allow you to control the output more. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [openstack-cloud-plugin] (JENKINS-28789) NoSuchElementException: apiType network not found in catalog []

2015-08-28 Thread alan.q...@turn.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alan Qian commented on  JENKINS-28789 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: NoSuchElementException: apiType network not found in catalog []  
 
 
 
 
 
 
 
 
 
 
any updates or workarounds? we are seeing this too 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [openstack-cloud-plugin] (JENKINS-30136) Configuration of plugin: Cloud Instance Templates Image dropdown and Hardware dropdown contains only 'None specified'

2015-08-28 Thread alan.q...@turn.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alan Qian resolved as Duplicate 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
Duplicates https://issues.jenkins-ci.org/browse/JENKINS-28789 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-30136 
 
 
 
  Configuration of plugin: Cloud Instance Templates  Image dropdown and Hardware dropdown contains only 'None specified'  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alan Qian 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Duplicate 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [vncrecorder-plugin] (JENKINS-30204) vnc2swf fails because matrix builds have slashes in the name

2015-08-28 Thread ke...@the-b.org (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenny Root created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-30204 
 
 
 
  vnc2swf fails because matrix builds have slashes in the name  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Dimitri Tenenbaum 
 
 
 

Components:
 

 vncrecorder-plugin 
 
 
 

Created:
 

 29/Aug/15 12:00 AM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Kenny Root 
 
 
 
 
 
 
 
 
 
 
When using a matrix build, the BUILD_NAME will be something like My_Project/axis1=foo,axis2=blah which makes the outFileName My_Project/axis1=foo,axis2=blah_1.swf The writing of the file will fail because it's looking for a My_Project subdirectory. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [core] (JENKINS-12289) Multi-line commit messages should be configurable to appear in Email-Ext build change notifications

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 sthuthi bhat commented on  JENKINS-12289 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Multi-line commit messages should be configurable to appear in Email-Ext build change notifications  
 
 
 
 
 
 
 
 
 
 
pre tag around content token does not work. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-12289) Multi-line commit messages should be configurable to appear in Email-Ext build change notifications

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 sthuthi bhat commented on  JENKINS-12289 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Multi-line commit messages should be configurable to appear in Email-Ext build change notifications  
 
 
 
 
 
 
 
 
 
 
Can somebody please provide me jelly or groovy script for doing that? No where available. pre tag around content does not even work! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-12289) Multi-line commit messages should be configurable to appear in Email-Ext build change notifications

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 sthuthi bhat reopened an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-12289 
 
 
 
  Multi-line commit messages should be configurable to appear in Email-Ext build change notifications  
 
 
 
 
 
 
 
 
 

Change By:
 
 sthuthi bhat 
 
 
 

Resolution:
 
 NotADefect 
 
 
 

Status:
 
 Closed Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-12289) Multi-line commit messages should be configurable to appear in Email-Ext build change notifications

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Earl commented on  JENKINS-12289 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Multi-line commit messages should be configurable to appear in Email-Ext build change notifications  
 
 
 
 
 
 
 
 
 
 
I assume you are using the HTML content type? Can you provide your template so I can take a look? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-12289) Multi-line commit messages should be configurable to appear in Email-Ext build change notifications