[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
Andréas Berg commented on JENKINS-18578 Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable This issue is not about the Jenkins working directory. It is about the default jar cache location. Yes, using the slave FS root as default should work for both environments. master is after all just another slave. 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/groups/opt_out.
[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
Felix Roethenbacher commented on JENKINS-18578 Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable Actually, it is related to the Jenkins working/home directory (see JENKINS-18459) as this is where Jenkins usually is given read/write access. In an environment where Jenkins WAR is running inside an existing Tomcat application server with user 'tomcat7', Jenkins fails as the user does not have write access to the user's home directory (usually that's '/usr/share/tomcat7') for security reasons. If the slave FS root solves this problem, that's perfect. Just make sure that the actual user running Jenkins has write access to this directory. 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/groups/opt_out.
[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
Andréas Berg commented on JENKINS-18578 Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable Good point, your case is actually even worse than ours then, as it fails due to this. We only get decreased performance and the risk of garbage filling up the home directory quota, at which point it will fail for us too. 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/groups/opt_out.
[JIRA] [core] (JENKINS-20740) Wiki needs update since Jetty in Jenkins 1.535
evernat created JENKINS-20740 Wiki needs update since Jetty in Jenkins 1.535 Issue Type: Bug Assignee: Jesse Glick Components: core Created: 24/Nov/13 1:12 PM Description: Since Jetty in Jenkins v1.535, "Meet Jenkins" and other pages are out of date in the wiki. I am not authorized to edit the "Meet Jenkins" page. By the way, "JRE 1.5" should also be changed to "JRE 1.6" in the "Meeting Jenkins" page. Need update: https://wiki.jenkins-ci.org/display/JENKINS/Meet+Jenkins https://wiki.jenkins-ci.org/display/JENKINS/Containers https://wiki.jenkins-ci.org/display/JENKINS/Winstone Project: Jenkins Priority: Major Reporter: evernat 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/groups/opt_out.
[JIRA] [build-flow] (JENKINS-20741) Build has been executing for null in Build-flow jobs
Roberto González
created JENKINS-20741
Build has been executing for null in Build-flow jobs
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
build-flow
Created:
24/Nov/13 5:19 PM
Description:
If the user makes a flow that has a N jobs in parallel (N given by another job, or param), the main job cant calculate the time that the actual build has been executing.
Example:
def jobB= {
tests= parallel(
(0..lastPos).collect { ctr
return {
ignore(UNSTABLE) {
ejec= build (
"JOB_TEST", params like array[ctr]...)
}
}
}
)
}
//we launch the builds
def job2= { [ jobA, jobB ].each{it()} }
parallel(job1, job2)
}
this example launchs job1 and job2 in parallel, and job2 triggers jobA, and then N builds of jobB, where N is the size of an array.
so we have main job job1--
-jobA-jobB(1)--/
jobB(2)---/
and N builds of jobB.
If we have this example, when the main job is running, we hover the mouse in the loading bar of the job we can see "Build has been executing for null"
Project:
Jenkins
Labels:
plugin
build-flow
Priority:
Minor
Reporter:
Roberto González
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/groups/opt_out.
[JIRA] [ec2] (JENKINS-20742) EC2 plugin does not delete slaves that failed to start
Stefan Zier created JENKINS-20742 EC2 plugin does not delete slaves that failed to start Issue Type: Bug Affects Versions: current Assignee: Francis Upton Components: ec2 Created: 24/Nov/13 6:10 PM Description: When the EC2 plugin starts up slaves and the startup fails (either because the script fails or the EC2 instance never becomes accessible), Jenkins never deletes the slave, and the instance burns money until somebody manually shuts it down. Environment: Jenkins 1.540 EC2 Plugin 1.20 Ubuntu 12.04 LTS Fix Versions: current Project: Jenkins Priority: Major Reporter: Stefan Zier 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/groups/opt_out.
[JIRA] [perforce] (JENKINS-18583) [MultipleSCM integration] - Perforce SCM does not work in MultipleSCMs
Oleg Nenashev
updated JENKINS-18583
[MultipleSCM integration] - Perforce SCM does not work in MultipleSCMs
Change By:
Oleg Nenashev
(24/Nov/13 6:16 PM)
Summary:
[MultipleSCMintegration]-
ViewMapisemptyincaseofmultiple
PerforceSCM
instances
doesnotworkinMultipleSCMs
Description:
Initialdescription:{quote}
UsageofPerforcepluginintheset-upofmultipleSCMsectionleadstoJavaexceptionwithnoexplanationsoffailure.
SeemsthatPerforcepluginsomehowignoresViewMapparametersinnewInstancehandler.
{quote}Therealissues:-MultipleSCMsuseDataBoundConstructorinsteadofnewInstance-radioBlocknamesarenotunique-...
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/groups/opt_out.
[JIRA] [cobertura] (JENKINS-20706) Make Cobertura plug-in support multi-configuration (matrix) jobs
Marc Abramowitz commented on JENKINS-20706 Make Cobertura plug-in support multi-configuration (matrix) jobs I submitted a PR that supports matrix projects in a very simplistic way: https://github.com/jenkinsci/cobertura-plugin/pull/22 This doesn't attempt to merge the coverage results from different matrix runs. It simply uses the coverage from the last matrix run as the coverage for the matrix build. Hopefully, this can be extended to some kind of intelligent aggregation of the coverage results. 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/groups/opt_out.
[JIRA] [cobertura] (JENKINS-20706) Make Cobertura plug-in support multi-configuration (matrix) jobs
Marc Abramowitz stopped work on JENKINS-20706 Make Cobertura plug-in support multi-configuration (matrix) jobs Change By: Marc Abramowitz (24/Nov/13 6:17 PM) Status: InProgress Open 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/groups/opt_out.
[JIRA] [cobertura] (JENKINS-20706) Make Cobertura plug-in support multi-configuration (matrix) jobs
Marc Abramowitz started work on JENKINS-20706 Make Cobertura plug-in support multi-configuration (matrix) jobs Change By: Marc Abramowitz (24/Nov/13 6:17 PM) Status: Open InProgress 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/groups/opt_out.
[JIRA] [perforce] (JENKINS-18583) [MultipleSCM integration] - Perforce SCM does not work in MultipleSCMs
SCM/JIRA link daemon commented on JENKINS-18583 [MultipleSCM integration] - Perforce SCM does not work in MultipleSCMs Code changed in jenkins User: Oleg Nenashev Path: src/main/java/hudson/plugins/perforce/PerforceSCM.java src/main/java/hudson/plugins/perforce/config/CleanTypeConfig.java src/main/java/hudson/plugins/perforce/config/DepotType.java src/main/java/hudson/plugins/perforce/config/MaskViewConfig.java src/main/java/hudson/plugins/perforce/config/WorkspaceCleanupConfig.java src/main/resources/hudson/plugins/perforce/PerforceSCM/config.jelly src/test/java/hudson/plugins/perforce/PerforceSCMTest.java http://jenkins-ci.org/commit/perforce-plugin/02350700b588acc39d774c30d43c53e7ff108d53 Log: JENKINS-18583 - Refactoring of PerforceSCM to remove newInstance() This change removes need in newInstance() handler and also provides classes for future refactoring. In addition, the change adds instance IDs to config.jelly, therefore there won't be conflicts between radioButtons(). Resolves https://issues.jenkins-ci.org/browse/JENKINS-18583 Signed-off-by: Oleg Nenashev nenas...@synopsys.com 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/groups/opt_out.
[JIRA] [core] (JENKINS-20675) Java platform binary has stopped working message appears when starting Jenkins 1.540
Florian Herbel updated JENKINS-20675 Java platform binary has stopped working message appears when starting Jenkins 1.540 Change By: Florian Herbel (24/Nov/13 6:33 PM) Priority: Major Critical 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/groups/opt_out.
[JIRA] [perforce] (JENKINS-18783) Perforce plugin help file missing
SCM/JIRA link daemon commented on JENKINS-18783 Perforce plugin help file missing Code changed in jenkins User: Rob Petti Path: src/main/resources/hudson/plugins/perforce/PerforceSCM/config.jelly http://jenkins-ci.org/commit/perforce-plugin/3f42586b0288b8f27592d34c02fa3fbc7333525f Log: FIXED JENKINS-18783 typo in help path for charset options 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/groups/opt_out.
[JIRA] [perforce] (JENKINS-18583) [MultipleSCM integration] - Perforce SCM does not work in MultipleSCMs
SCM/JIRA link daemon commented on JENKINS-18583 [MultipleSCM integration] - Perforce SCM does not work in MultipleSCMs Code changed in jenkins User: Rob Petti Path: src/main/java/hudson/plugins/perforce/PerforceSCM.java src/main/java/hudson/plugins/perforce/config/CleanTypeConfig.java src/main/java/hudson/plugins/perforce/config/DepotType.java src/main/java/hudson/plugins/perforce/config/MaskViewConfig.java src/main/java/hudson/plugins/perforce/config/WorkspaceCleanupConfig.java src/main/resources/hudson/plugins/perforce/PerforceSCM/config.jelly src/test/java/hudson/plugins/perforce/PerforceSCMTest.java http://jenkins-ci.org/commit/perforce-plugin/4c8e35c5219d89118c5ee87352e692d63d43485d Log: Merge pull request #33 from jenkinsci/multiple-scm-instatination-fix IN_PROGRESSJENKINS-18583 - Fixed PerforceSCM instatination forn Multiple SCMs Compare: https://github.com/jenkinsci/perforce-plugin/compare/02d2fcf2a206...4c8e35c5219d 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/groups/opt_out.
[JIRA] [build-flow] (JENKINS-20741) Build has been executing for null in Build-flow jobs
Roberto González
updated JENKINS-20741
Build has been executing for null in Build-flow jobs
Change By:
Roberto González
(24/Nov/13 7:30 PM)
Attachment:
schema-jenkins.JPG
Description:
IftheusermakesaflowthathasaNjobsinparallel(Ngivenbyanotherjob,orparam),themainjobcantcalculatethetimethattheactualbuildhasbeenexecuting.Example:defjobB={tests=parallel((0..lastPos).collect{ctrreturn{ignore(UNSTABLE){ejec=build(JOB_TEST,paramslikearray[ctr]...)}}})}//welaunchthebuildsdefjob2={[jobA,jobB].each{it()}}parallel(job1,job2)}thisexamplelaunchsjob1andjob2inparallel,andjob2triggersjobA,andthenNbuildsofjobB,whereNisthesizeofanarray.
sowehavemain
theschemaofthe
job
---job1---
isattachedasaimage
\---jobA---jobB(1)---/\-jobB(2)---/andNbuildsofjobB.
Ifwehavethisexample,whenthemainjobisrunning,wehoverthemouseintheloadingbarofthejobwecanseeBuildhasbeenexecutingfornull
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/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-20743) How to obtain the secret to use when starting a slave with java from a scheduled task?
Davy Van Nieuwenborgh created JENKINS-20743 How to obtain the secret to use when starting a slave with java from a scheduled task? Issue Type: Bug Assignee: Unassigned Components: vsphere-cloud Created: 24/Nov/13 8:33 PM Description: When you make a dumb slave using Java Web Start, you get a command to start the slave from the command line in the slave overview page. This command contains a part "-secret HEXSTRING". When creating a vsphere slave with java webstart as secondary start option, there is no way to retrieve the secret to use to get the slave started, unless I missed something. The only work around for now seems to create the slave first as a dumb slave, then write down the secret, drop the slave and recreate it as a vsphere slave with the same name, as it seems the secret is determined by the name. This seems a strange way of doing things and introduces double work. Environment: Windows Project: Jenkins Priority: Major Reporter: Davy Van Nieuwenborgh 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/groups/opt_out.
[JIRA] [cli] (JENKINS-20744) Don't hold off building until saved for jobs copied from API
Daniel Beck created JENKINS-20744 Dont hold off building until saved for jobs copied from API Issue Type: Bug Assignee: Unassigned Components: cli, core Created: 24/Nov/13 8:37 PM Description: By default, Jenkins does not allow building jobs that have just been copied until they are re-saved. This is to prevent accidentally scheduled builds before the user is able to customize a newly cloned job (JENKINS-2494). Jobs copied from the API don't need the same protection after copying. In fact, as there is no simple way to save a job without changing anything about its configuration using the CLI, it needs to behave differently. Project: Jenkins Priority: Major Reporter: Daniel Beck 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/groups/opt_out.
[JIRA] [cli] (JENKINS-20744) Don't hold off building until saved for jobs copied from CLI
Daniel Beck updated JENKINS-20744 Dont hold off building until saved for jobs copied from CLI Change By: Daniel Beck (24/Nov/13 8:41 PM) Summary: Dontholdoffbuildinguntilsavedforjobscopiedfrom API CLI Description: Bydefault,Jenkinsdoesnotallowbuildingjobsthathavejustbeencopieduntiltheyarere-saved.Thisistopreventaccidentallyscheduledbuildsbeforetheuserisabletocustomizeanewlyclonedjob(JENKINS-2494).Jobscopiedfromthe API CLI dontneedthesameprotectionaftercopying.Infact,asthereisnosimplewaytosaveajobwithoutchanginganythingaboutitsconfigurationusingtheCLI,itneedstobehavedifferently. 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/groups/opt_out.
[JIRA] [cli] (JENKINS-20744) Don't hold off building until saved for jobs copied from CLI
Daniel Beck commented on JENKINS-20744 Dont hold off building until saved for jobs copied from CLI https://github.com/jenkinsci/jenkins/pull/1034 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/groups/opt_out.
[JIRA] [jclouds-jenkins] (JENKINS-18173) JClouds fails accessing OpenStack-nova (java.lang.NullPointerException: tenant)
ahmed Baig commented on JENKINS-18173 JClouds fails accessing OpenStack-nova (java.lang.NullPointerException: tenant) Hi, Will this issue ever be resolved? I am waiting on this for 3+ months. Without this plugin I'm Using SSH which is ugly way to do. Jaroslav Henner, I wonder if you found any work around? Can you please share it if you found? Jenkins team this is excellent highly usable plugin. I sincerely request team to please resolve ASAP. Thanks in Advance, wabmca 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/groups/opt_out.
[JIRA] [core] (JENKINS-16781) Job and Project naming convention
Joris van der Pol commented on JENKINS-16781 Job and Project naming convention @Daniel Beck: ok, that explains the job/project convention. With that in mind, I don't see a problem. I'll close this 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/groups/opt_out.
[JIRA] [core] (JENKINS-16781) Job and Project naming convention
Joris van der Pol closed JENKINS-16781 as Not A Defect Job and Project naming convention Change By: Joris van der Pol (24/Nov/13 10:24 PM) Status: Open Closed Resolution: NotADefect 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/groups/opt_out.
[JIRA] [delivery-pipeline] (JENKINS-20717) Add pipelines to view dymacally with regexp
Patrik Boström assigned JENKINS-20717 to Patrik Boström Add pipelines to view dymacally with regexp Change By: Patrik Boström (24/Nov/13 10:41 PM) Assignee: PatrikBoström 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/groups/opt_out.
[JIRA] [git] (JENKINS-20446) Git Plugin 2.0 has changed contents of GIT_BRANCH
Kevin Burge commented on JENKINS-20446 Git Plugin 2.0 has changed contents of GIT_BRANCH I'm guessing this was done to avoid having to add another variable for the repository name? 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/groups/opt_out.
[JIRA] [core] (JENKINS-18366) Jetty should be used rather than Winstone for embedded deployments
Joshua Wherrett commented on JENKINS-18366 Jetty should be used rather than Winstone for embedded deployments Hi, I am having trouble getting the Jenkins webpage up using a Solaris 10 server (JRE 1.6.0_26-b03). The log shows Jenkins started successfully (Jenkins is fully up and running). However when I try to connect using a web browser (tried IE and Firefox from Jenkins server localhost and remote machines) it hangs indefinitely. Checking netstat shows the connection is ESTABLISHED. All versions of Jenkins prior to 1.535 work perfectly under Solaris 10 and no versions after 1.534 work. So I can only assume it was the introduction of Jetty in 1.535 that has caused this issue. Cheers, Josh 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/groups/opt_out.
[JIRA] [jclouds] (JENKINS-20745) Failed to create slave on hpcloud-compute (AuthorizationException)
carman yuk
created JENKINS-20745
Failed to create slave on hpcloud-compute (AuthorizationException)
Issue Type:
Bug
Affects Versions:
current
Assignee:
abayer
Components:
jclouds, jclouds-jenkins
Created:
25/Nov/13 5:04 AM
Description:
When JClouds plugin starts a slave (e.g. click on "Provision via JClouds - servername" button in Manage Nodes page) from configured hpcloud-compute profile, exception occurs with following stack trace
javax.servlet.ServletException: java.lang.RuntimeException: org.jclouds.compute.RunNodesException: error running 1 node group(hpcloud) location(az-1.region-a.geo-1) image(75845) size(100) options({loginPrivateKeyPresent=true, scriptPresent=true, userMetadata={Name=hpcloud}, generateKeyPair=true, userData=[B@2721})
Execution failures:
0 error[s]
Node failures:
1) AuthorizationException on node az-1.region-a.geo-1/3052239:
org.jclouds.rest.AuthorizationException: (ubuntu:rsa[fingerprint(e7:c5:be:98:d9:fe:6e:61:7a:ea:57:7c:93:ea:7f:77),sha1(a6:b5:5b:8e:24:fe:a7:ab:92:ae:5b:df:bb:a9:ce:0b:f3:13:03:90)]@15.185.118.224:22) (ubuntu:rsa[fingerprint(e7:c5:be:98:d9:fe:6e:61:7a:ea:57:7c:93:ea:7f:77),sha1(a6:b5:5b:8e:24:fe:a7:ab:92:ae:5b:df:bb:a9:ce:0b:f3:13:03:90)]@15.185.118.224:22) error acquiring {hostAndPort=15.185.118.224:22, loginUser=ubuntu, ssh=null, connectTimeout=6, sessionTimeout=6} (out of retries - max 7): Exhausted available authentication methods
at org.jclouds.sshj.SshjSshClient.propagate(SshjSshClient.java:380)
at org.jclouds.sshj.SshjSshClient.acquire(SshjSshClient.java:201)
at org.jclouds.sshj.SshjSshClient.connect(SshjSshClient.java:221)
at org.jclouds.compute.callables.RunScriptOnNodeAsInitScriptUsingSsh.call(RunScriptOnNodeAsInitScriptUsingSsh.java:76)
at org.jclouds.compute.strategy.CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.call(CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:125)
at org.jclouds.compute.strategy.CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.apply(CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:146)
at org.jclouds.compute.strategy.CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.apply(CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:53)
at com.google.common.util.concurrent.Futures$1.apply(Futures.java:720)
at com.google.common.util.concurrent.Futures$ChainingListenableFuture.run(Futures.java:859)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: net.schmizz.sshj.userauth.UserAuthException: Exhausted available authentication methods
at net.schmizz.sshj.userauth.UserAuthImpl.authenticate(UserAuthImpl.java:114)
at net.schmizz.sshj.SSHClient.auth(SSHClient.java:205)
at net.schmizz.sshj.SSHClient.authPublickey(SSHClient.java:305)
at net.schmizz.sshj.SSHClient.authPublickey(SSHClient.java:324)
at org.jclouds.sshj.SSHClientConnection.create(SSHClientConnection.java:142)
at org.jclouds.sshj.SSHClientConnection.create(SSHClientConnection.java:38)
at org.jclouds.sshj.SshjSshClient.acquire(SshjSshClient.java:191)
... 10 more
Caused by: net.schmizz.sshj.userauth.UserAuthException: publickey auth failed
at net.schmizz.sshj.userauth.UserAuthImpl.handle(UserAuthImpl.java:157)
at net.schmizz.sshj.transport.TransportImpl.handle(TransportImpl.java:474)
at net.schmizz.sshj.transport.Decoder.decode(Decoder.java:127)
at net.schmizz.sshj.transport.Decoder.received(Decoder.java:195)
at net.schmizz.sshj.transport.Reader.run(Reader.java:72)
1 error[s]
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:735)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:799)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:239)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:685)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:799)
at
[JIRA] [jclouds] (JENKINS-20745) JClouds plugin failed to create slave on hpcloud-compute (AuthorizationException)
carman yuk updated JENKINS-20745 JClouds plugin failed to create slave on hpcloud-compute (AuthorizationException) Change By: carman yuk (25/Nov/13 6:13 AM) Summary: Failed JCloudspluginfailed tocreateslaveonhpcloud-compute(AuthorizationException) 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/groups/opt_out.
[JIRA] [jclouds] (JENKINS-20746) JClouds plugin does not add slave to Jenkins after created a server from customized image in hpcloud-compute
carman yuk updated JENKINS-20746 JClouds plugin does not add slave to Jenkins after created a server from customized image in hpcloud-compute Change By: carman yuk (25/Nov/13 6:25 AM) Summary: JCloud JClouds plugindoesnotaddslavetoJenkinsaftercreatedaserverfromcustomizedimageinhpcloud-compute 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/groups/opt_out.
[JIRA] [jclouds] (JENKINS-20746) JCloud plugin does not add slave to Jenkins after created a server from customized image in hpcloud-compute
carman yuk created JENKINS-20746 JCloud plugin does not add slave to Jenkins after created a server from customized image in hpcloud-compute Issue Type: Bug Assignee: abayer Components: jclouds, jclouds-jenkins Created: 25/Nov/13 6:25 AM Description: The server in HP Cloud is already created and active, but it has never been added to Jenkins as node. The issue happens if the specified image to create node is from customized image but not happen if the image is provided by HP Cloud. Environment: == Version == jclouds-jenkins version: 2.3 Jenkins: 1.533 ssh-credentials: 0.3 ssh-slaves: 0.25 Project: Jenkins Labels: plugin jenkins slave Priority: Major Reporter: carman yuk 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/groups/opt_out.
[JIRA] [core] (JENKINS-20664) radiator-view plugin stop work after upgrade to 1.539
David Resnick assigned JENKINS-20664 to David Resnick radiator-view plugin stop work after upgrade to 1.539 Change By: David Resnick (25/Nov/13 6:45 AM) Assignee: howama DavidResnick 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/groups/opt_out.
[JIRA] [core] (JENKINS-20664) radiator-view plugin stop work after upgrade to 1.539
David Resnick started work on JENKINS-20664 radiator-view plugin stop work after upgrade to 1.539 Change By: David Resnick (25/Nov/13 6:44 AM) Status: Open InProgress 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/groups/opt_out.
[JIRA] [android-emulator] (JENKINS-20560) Custom-tools plugin breaks path for android-emulator
SCM/JIRA link daemon resolved JENKINS-20560 as Fixed Custom-tools plugin breaks path for android-emulator Change By: SCM/JIRA link daemon (25/Nov/13 7:17 AM) Status: InProgress 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/groups/opt_out.
[JIRA] [android-emulator] (JENKINS-20560) Custom-tools plugin breaks path for android-emulator
SCM/JIRA link daemon commented on JENKINS-20560 Custom-tools plugin breaks path for android-emulator Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/cloudbees/jenkins/plugins/customtools/CustomToolInstallWrapper.java src/main/java/com/synopsys/arc/jenkinsci/plugins/customtools/PathsList.java http://jenkins-ci.org/commit/customtools-plugin/1ed68b4a65642113f4a61da08aa5f2e4da5d5b4b Log: FIXED JENKINS-20560 - Custom-tools should not override global paths inside nested launchers I've also refactored retrieval of paths list. Related to: https://issues.jenkins-ci.org/browse/JENKINS-20560 Signed-off-by: Oleg Nenashev nenas...@synopsys.com 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/groups/opt_out.
[JIRA] [android-emulator] (JENKINS-20560) Custom-tools plugin breaks path for android-emulator
SCM/JIRA link daemon commented on JENKINS-20560 Custom-tools plugin breaks path for android-emulator Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/cloudbees/jenkins/plugins/customtools/CustomToolInstallWrapper.java src/main/java/com/synopsys/arc/jenkinsci/plugins/customtools/PathsList.java src/test/java/com/cloudbees/jenkins/plugins/customtools/CustomToolInstallWrapperTest.java http://jenkins-ci.org/commit/customtools-plugin/6c81ebbc162d9ccfaba9750d977a68c9f5dacc0e Log: Merge pull request #13 from synopsys-arc-oss/JENKINS_20560_FIX FIXED JENKINS-20560 - Custom-tools should not override global paths in... Compare: https://github.com/jenkinsci/customtools-plugin/compare/5d9a150ffd10...6c81ebbc162d 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/groups/opt_out.
[JIRA] [android-emulator] (JENKINS-20560) Custom-tools plugin breaks path for android-emulator
SCM/JIRA link daemon commented on JENKINS-20560 Custom-tools plugin breaks path for android-emulator Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/cloudbees/jenkins/plugins/customtools/CustomToolInstallWrapper.java src/main/java/com/synopsys/arc/jenkinsci/plugins/customtools/PathsList.java src/test/java/com/cloudbees/jenkins/plugins/customtools/CustomToolInstallWrapperTest.java http://jenkins-ci.org/commit/customtools-plugin/84cac80f50b70aa1f31ba23b1a169e4a69ce7425 Log: JENKINS-20560 - Don't try to override empty paths Caused by the initial fix of https://issues.jenkins-ci.org/browse/JENKINS-20560 Signed-off-by: Oleg Nenashev nenas...@synopsys.com 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/groups/opt_out.
