[JIRA] [gerrit-trigger] (JENKINS-21067) New server config not reachable if using a prefix in URL
Björn Pedersen commented on JENKINS-21067 New server config not reachable if using a prefix in URL Thanks, working again in beta4 now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cli] (JENKINS-21086) jenkins-cli requires Overall/Read permission for anonymous to perform a safe-shutdown
Roman Shiryaev
updated JENKINS-21086
jenkins-cli requires Overall/Read permission for anonymous to perform a safe-shutdown
Change By:
Roman Shiryaev
(19/Dec/13 8:06 AM)
Description:
Previously(Jenkins1.534)wewereusingjenkins-clitoautomatesafeshutdown.Butafterupgradetover.1.544itstoppedworking.OurconfigurationusesProject-basedMatrixAuthorizationStrategy.Hereare3mainuserswhoinvolvedintotheshutdownprocedure:*Anonymous-allpermissionsunset.*authenticated-Overall/Read,Job/Read,Job/Build*specialjenkins-cliuser-withOverall/Administer
permission
Andhereisthecommandtoperformasafeshutdown{code}java-jarjenkins-cli.jar-shttp://localhost:8080safe-shutdown--username$JCLIUSER--password$JCLIPASSWD{code}SoithasbeenworkingperfectlywiththeaboveconfigurationuntilIupgradedJenkinsto1.544Nowthecommandthrowstheerror{quote}hudson.security.AccessDeniedException2:anonymousismissingtheOverall/Readpermission athudson.security.ACL.checkPermission(ACL.java:54) athudson.model.Node.checkPermission(Node.java:418) athudson.cli.declarative.CLIRegisterer$1.main(CLIRegisterer.java:180) athudson.cli.CliManagerImpl.main(CliManagerImpl.java:92) atsun.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:622) athudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:299) athudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:280) athudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:239) athudson.remoting.UserRequest.perform(UserRequest.java:118) athudson.remoting.UserRequest.perform(UserRequest.java:48) athudson.remoting.Request$2.run(Request.java:328) athudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) athudson.cli.CliManagerImpl$1.call(CliManagerImpl.java:63) athudson.remoting.InterceptingExecutorService$2.call(InterceptingExecutorService.java:95) atjava.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) atjava.util.concurrent.FutureTask.run(FutureTask.java:166) atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) atjava.lang.Thread.run(Thread.java:701){quote}Ofcourse,ifIgrantthepermissiontoAnonymous,itwillwork.ButIassumethisisunsafe.
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-21086) jenkins-cli requires Overall/Read permission for anonymous to perform a safe-shutdown
Roman Shiryaev
updated JENKINS-21086
jenkins-cli requires Overall/Read permission for anonymous to perform a safe-shutdown
Change By:
Roman Shiryaev
(19/Dec/13 8:06 AM)
Description:
Previously(Jenkins1.534)wewereusingjenkins-clitoautomatesafeshutdown.Butafterupgradetover.1.544itstoppedworking.Ourconfiguration
is
usesProject-basedMatrixAuthorizationStrategy.Hereare3mainuserswhoinvolvedintotheshutdownprocedure:*Anonymous-allpermissionsunset.*authenticated-Overall/Read,Job/Read,Job/Build*specialjenkins-cliuser-withOverall/AdministerAndhereisthecommandtoperformasafeshutdown{code}java-jarjenkins-cli.jar-shttp://localhost:8080safe-shutdown--username$JCLIUSER--password$JCLIPASSWD{code}SoithasbeenworkingperfectlywiththeaboveconfigurationuntilIupgradedJenkinsto1.544Nowthecommandthrowstheerror{quote}hudson.security.AccessDeniedException2:anonymousismissingtheOverall/Readpermission athudson.security.ACL.checkPermission(ACL.java:54) athudson.model.Node.checkPermission(Node.java:418) athudson.cli.declarative.CLIRegisterer$1.main(CLIRegisterer.java:180) athudson.cli.CliManagerImpl.main(CliManagerImpl.java:92) atsun.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:622) athudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:299) athudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:280) athudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:239) athudson.remoting.UserRequest.perform(UserRequest.java:118) athudson.remoting.UserRequest.perform(UserRequest.java:48) athudson.remoting.Request$2.run(Request.java:328) athudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) athudson.cli.CliManagerImpl$1.call(CliManagerImpl.java:63) athudson.remoting.InterceptingExecutorService$2.call(InterceptingExecutorService.java:95) atjava.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) atjava.util.concurrent.FutureTask.run(FutureTask.java:166) atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) atjava.lang.Thread.run(Thread.java:701){quote}Ofcourse,ifIgrantthepermissiontoAnonymous,itwillwork.ButIassumethisisunsafe.
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-21086) jenkins-cli requires Overall/Read permission for anonymous to perform a safe-shutdown
Roman Shiryaev created JENKINS-21086 jenkins-cli requires Overall/Read permission for anonymous to perform a safe-shutdown Issue Type: Bug Assignee: Unassigned Components: cli Created: 19/Dec/13 8:05 AM Description: Previously (Jenkins 1.534) we were using jenkins-cli to automate safe shutdown. But after upgrade to ver. 1.544 it stopped working. Our configuration is uses Project-based Matrix Authorization Strategy. Here are 3 main users who involved into the shutdown procedure: Anonymous - all permissions unset. authenticated - Overall/Read, Job/Read, Job/Build special jenkins-cli user - with Overall/Administer And here is the command to perform a safe shutdown java -jar jenkins-cli.jar -s http://localhost:8080 safe-shutdown --username "$JCLIUSER" --password "$JCLIPASSWD" So it has been working perfectly with the above configuration until I upgraded Jenkins to 1.544 Now the command throws the error hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission at hudson.security.ACL.checkPermission(ACL.java:54) at hudson.model.Node.checkPermission(Node.java:418) at hudson.cli.declarative.CLIRegisterer$1.main(CLIRegisterer.java:180) at hudson.cli.CliManagerImpl.main(CliManagerImpl.java:92) 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:622) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:299) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:280) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:239) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at hudson.cli.CliManagerImpl$1.call(CliManagerImpl.java:63) at hudson.remoting.InterceptingExecutorService$2.call(InterceptingExecutorService.java:95) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:701) Of course, if I grant the permission to Anonymous, it will work. But I assume this is unsafe. Environment: amd64, Ubuntu 12.04.3 LTS, Openjdk 6b27-1.12.6-1ubuntu0.12.04.4 Project: Jenkins Priority: Major Reporter: Roman Shiryaev 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 commented on JENKINS-20664 radiator-view plugin stop work after upgrade to 1.539 I'm wondering how much backward compatibility I should worry about. I imagine that it won't be hard to fix this to work on 1.532.1, but that would probably break it for older Jenkins releases. Would anyone like to give feedback on that? 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] [mailer] (JENKINS-21045) maven 2/3 projects cannot store emailaddress
Olli Varis commented on JENKINS-21045 maven 2/3 projects cannot store emailaddress I'm sorry but how can you update Maven Integration plugin to 2.1 when it's bundled with Jenkins? We are using latest (LTS) Jenkins 1.532.1? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cli] (JENKINS-20744) Don't hold off building until saved for jobs copied from CLI
Magnus Jacobsson reopened JENKINS-20744 Dont hold off building until saved for jobs copied from CLI This still seems to be a problem. I use the python jenkinsapi to copy a job and then get it's config, modify it and update it. After that, the job is not buildable. If I disable it and reenable it, it's buildable again. Change By: Magnus Jacobsson (19/Dec/13 8:33 AM) Resolution: Fixed Status: Resolved Reopened 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] [mailer] (JENKINS-19194) Recepients not being saved
Antonio Garcia-Dominguez commented on JENKINS-19194 Recepients not being saved I have also been affected by this issue since I updated my Jenkins installation from 1.509.4 to 1.532.1 (the latest "stable" .deb). 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] [mailer] (JENKINS-19194) Recipients not being saved
Antonio Garcia-Dominguez updated JENKINS-19194 Recipients not being saved Change By: Antonio Garcia-Dominguez (19/Dec/13 8:52 AM) Summary: Recepients Recipients notbeingsaved 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 resolved JENKINS-20744 as Fixed Dont hold off building until saved for jobs copied from CLI The third party 'JenkinsAPI' for Python uses the Jenkins XML API, which is outside the scope of this issue. This is just about the Jenkins CLI (using jenkins-cli.jar). AFAICT JenkinsAPI even uses the same HTTP request as users on the UI would to copy jobs, which means at least the copy alone would be infeasible to change without breaking the 'hold off build' feature in web browsers. Change By: Daniel Beck (19/Dec/13 9:25 AM) Status: Reopened 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] [delivery-pipeline] (JENKINS-21009) Allow manual trigger
Patrik Boström assigned JENKINS-21009 to Patrik Boström Allow manual trigger Change By: Patrik Boström (19/Dec/13 9:47 AM) 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] [core] (JENKINS-21087) Don't hold off building until saved for jobs copied and updated from REST API
Magnus Jacobsson
created JENKINS-21087
Dont hold off building until saved for jobs copied and updated from REST API
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
core
Created:
19/Dec/13 10:03 AM
Description:
Jenkins version 1.544.
I use the python jenkinsapi-0.2.16-py2.7 to copy a job and then get it's config, modify it and update it.
After that, the job is not buildable. If I disable it and reenable it again, it's buildable again.
I think this is a regression when JENKINS-2494 was fixed. It worked well some Jenkins versions back. Se also JENKINS-20744 which deals with a similar problem for the CLI.
This is my python function that configures the job (XXX = censored info):
def create_job(template_job, new_job, enable=True, verbose=False, debug=False, **context):
"""
Create a job from a template job.
"""
j = jenkins.Jenkins('http://XXX', username='XXX', password='XXX')
if j.has_job(template_job):
templ_job = j.get_job(template_job)
else:
print "Couldn't find template job " + template_job
sys.exit(1)
if not j.has_job(new_job):
if verbose:
print "Creating new job " + new_job
job = j.copy_job(template_job, new_job)
else:
job = j.get_job(new_job)
if verbose:
print "Modifying already existing job " + new_job
config = templ_job.get_config()
new_config = create_config(config, enable, **context)
job.update_config(new_config)
Project:
Jenkins
Priority:
Major
Reporter:
Magnus Jacobsson
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
Magnus Jacobsson commented on JENKINS-20744 Dont hold off building until saved for jobs copied from CLI OK, thanks. I filed JENKINS-21087 to deal with the REST API. 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-21070) Set build displayname does not work
Patrik Boström commented on JENKINS-21070 Set build displayname does not work The first job in the pipeline can just use "Create Delivery Pipeline version". So make sure that the first job entered in the delivery pipeline view as the initial job are configured with "Build Environment" "Create Delivery Pipeline version" "Set build displayname". 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] [active-directory] (JENKINS-9258) Remember me on this computer, still getting asked to log in after a few hours
Andrey Regentov commented on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours @James, no I did not because logins worked as supposed (with short usernames) with empty "Bind DN" field and I didn't want to store and update password in one more place (though it is stored not in plaintext). Now I tried to do set "Bind DN" and removed the "--sessionTimeout" crutch. WHOAA now it works as supposed, I'm happy, thanks. So we can say that (at least for my case) it logins well, but bails out without "bind DN"; logins well and remembers well with "bind DN" set. But how could it be explained? 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-21086) jenkins-cli requires Overall/Read permission for anonymous to perform a safe-shutdown
Roman Shiryaev updated JENKINS-21086 jenkins-cli requires Overall/Read permission for anonymous to perform a safe-shutdown Change By: Roman Shiryaev (19/Dec/13 11:03 AM) Environment: amd64 Version1.544 ,Ubuntu12.04.3LTS, amd64, Openjdk6b27-1.12.6-1ubuntu0.12.04.4 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] [m2release] (JENKINS-21088) Normalize line endings in git repo
Anders Hammar created JENKINS-21088 Normalize line endings in git repo Issue Type: Task Assignee: teilo Components: m2release Created: 19/Dec/13 11:04 AM Description: It seems as there are files in the git repo with CRLF line endings, which causes changes by non-Windows users to show up as the entire file has changed (as the line ending will be converted to LF. This will also happen for Windows users with recommended git settings (core.autocrlf=true). This is not good as it makes it difficult to see what was actually changed. The git repo needs to be normalized on line endings (LF). Also, a .gitattributes file should be added to prevent the same problem from happen again. See: https://help.github.com/articles/dealing-with-line-endings http://adaptivepatchwork.com/2012/03/01/mind-the-end-of-your-line/ Environment: n/a Project: Jenkins Priority: Major Reporter: Anders Hammar 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-21087) Don't hold off building until saved for jobs copied and updated from REST API
Daniel Beck commented on JENKINS-21087 Dont hold off building until saved for jobs copied and updated from REST API Seems like huson.model.Job does clear the holdOffBuildUntilUserSave flag when calling save(), but not when calling updateByXml(…). This can probably solved by implementing updateByXml(…) in Job calling super's implementation and clearing the flag. 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-21089) archiving artefacts from beaglebone fails
Steve Osselton created JENKINS-21089 archiving artefacts from beaglebone fails Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 19/Dec/13 11:42 AM Description: I run a Jenkins job on my BealgleBone, the job builds fine and produces a tar.gz artefact. The post build task "Archive the artefacts" just hangs when trying to retrieve the artefact. Have verified the artefact is present and has been built OK. Not sure what is going on here, have exactly the same build running on a raspberry pi with no problems. Have tried using both openJDK and an Oracle JDK on the target, but makes no difference. Environment: Host: Linux ubuntu12.04 Jenkins 1.544 Target: BeagleBone Black Ubuntu 12.04.3 LTS (GNU/Linux 3.8.13-bone30 armv7l) Project: Jenkins Priority: Major Reporter: Steve Osselton 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] [subversion] (JENKINS-14282) Double forwardslash in SVN URL causes Jenkins to repeatedly build
evernat commented on JENKINS-14282 Double forwardslash in SVN URL causes Jenkins to repeatedly build I do not reproduce this issue: using the SVN URL http://javamelody.googlecode.com/svn//trunk/javamelody-core, I get only a second build with the following log: Lancé par un changement dans la base de code Building in workspace C:\Applis\Jenkins\jobs\test\workspace Switching from http://javamelody.googlecode.com/svn/trunk/javamelody-core to http://javamelody.googlecode.com/svn//trunk/javamelody-core Switching to http://javamelody.googlecode.com/svn//trunk/javamelody-core at revision '2013-12-19T12:38:05.296 +0100' At revision 3599 no revision recorded for http://javamelody.googlecode.com/svn//trunk/javamelody-core in the previous build So there is only a second build with a switch and no repeated builds. 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] [subversion] (JENKINS-14282) Double forwardslash in SVN URL causes Jenkins to repeatedly build
evernat resolved JENKINS-14282 as Fixed Double forwardslash in SVN URL causes Jenkins to repeatedly build I think that this issue was fixed with JENKINS-2556 and https://github.com/jenkinsci/subversion-plugin/commit/6f3538ce695914395c3080741e117da0ff444ef3 in the subversion plugin v1.48. So resolving as fixed. Change By: evernat (19/Dec/13 11:59 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [shiningpanda] (JENKINS-21090) virtualenv task creating a new virtualenv without the clean flag set
Mobpro Mobpro created JENKINS-21090 virtualenv task creating a new virtualenv without the clean flag set Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: shiningpanda Created: 19/Dec/13 12:06 PM Description: A job with some standard steps in it like: VirtualEnv Builder clean=True $ pip install -r requirements.txt VirtualEnv Builder clean=False $ python manage.py syncdb --noinput VirtualEnv Builder clean=False $ python manage.py migrate VirtualEnv Builder clean=False $ python manage.py tests Will decide to create an entirely new virtualenv at one of the steps that have clean not set. This of course breaks the build and makes the job useless I had this multiple times before in other jobs and the only solution seems to be to clear out all the steps and recreate them and then hope that it will work as expected. Environment: Jenkins ver. 1.544 ShiningPanda Plugin ver 0.20 All other plugins are up to date at the time of writing this ticket. Project: Jenkins Priority: Major Reporter: Mobpro Mobpro 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-21091) Config flip-flopping
James Howe created JENKINS-21091 Config flip-flopping Issue Type: Bug Assignee: Rob Petti Components: perforce Created: 19/Dec/13 12:07 PM Description: The firstChange property seems to change between 0 and -1 for no apparent reason, and with no user interaction. This is very annoying if you're keeping job configs under version control. Environment: Jenkins 1.538 Plugin 1.3.26 Project: Jenkins Priority: Minor Reporter: James Howe 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-21034) Jenkins Startup Deadlock - QueueSorter.installDefaultQueueSorter and Queue.init
Magnus Sandberg assigned JENKINS-21034 to Magnus Sandberg Jenkins Startup Deadlock - QueueSorter.installDefaultQueueSorter and Queue.init Change By: Magnus Sandberg (19/Dec/13 12:11 PM) Assignee: bklarson MagnusSandberg 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] [shiningpanda] (JENKINS-21090) virtualenv task creating a new virtualenv without the clean flag set
Mobpro Mobpro
commented on JENKINS-21090
virtualenv task creating a new virtualenv without the clean flag set
log showing the wrong behavior:
[xxx] $ /usr/bin/python2.7 /tmp/shiningpanda/69ecf1f1/virtualenv.py /tmp/shiningpanda/69ecf1f1/virtualenvs/d41d8cd9
New python executable in /tmp/shiningpanda/69ecf1f1/virtualenvs/d41d8cd9/bin/python2.7
Also creating executable in /tmp/shiningpanda/69ecf1f1/virtualenvs/d41d8cd9/bin/python
Installing setuptools...done.
Installing pip...done.
[xxx] $ /bin/sh -xe /tmp/shiningpanda7270660549103376519.sh
+ pip install -r requirements.txt --use-mirrors
...
...
...
Successfully installed {{ lots of packages }}
Cleaning up...
[xxx] $ /bin/sh -xe /tmp/shiningpanda4247388076512291355.sh
+ python manage.py syncdb --noinput
...
...
...
(use ./manage.py migrate to migrate these)
[xxx] $ /bin/sh -xe /tmp/shiningpanda398325920697469798.sh
+ python manage.py migrate
...
...
...
Installed 0 object(s) from 0 fixture(s)
[xxx] $ /usr/bin/python2.7 /tmp/shiningpanda/69ecf1f1/virtualenv.py --distribute /tmp/shiningpanda/69ecf1f1/virtualenvs/d41d8cd9
New python executable in /tmp/shiningpanda/69ecf1f1/virtualenvs/d41d8cd9/bin/python2.7
Also creating executable in /tmp/shiningpanda/69ecf1f1/virtualenvs/d41d8cd9/bin/python
Installing distribute...done.
Installing pipdone.
[xxx] $ /bin/sh -xe /tmp/shiningpanda4593669991197625391.sh
+ python manage.py test --traceback --failfast
Traceback (most recent call last):
File "manage.py", line 8, in module
from django.core.management import execute_from_command_line
ImportError: No module named django.core.management
Build step 'Virtualenv Builder' marked build as failure
Finished: FAILURE
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-21034) Jenkins Startup Deadlock - QueueSorter.installDefaultQueueSorter and Queue.init
Magnus Sandberg commented on JENKINS-21034 Jenkins Startup Deadlock - QueueSorter.installDefaultQueueSorter and Queue.init Does this happen on a "normal" restart or only directly after the upgrade? Does this only happen after a upgrade of Priority Sorter or in other situations as well? Did you have a huge queue at restart or does this happen with any queue size? 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] [shiningpanda] (JENKINS-21090) virtualenv task creating a new virtualenv without the clean flag set
Mobpro Mobpro commented on JENKINS-21090 virtualenv task creating a new virtualenv without the clean flag set When having removed and recreated all the steps the build work again. It seems that somehow the Jenkins UI and the actual parameters on which the steps are executed are different / not in sync. I have not found a way in Jenkins to show the real parameter data instead of what is shown in the "Configure" page to confirm this. 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-21034) Jenkins Startup Deadlock - QueueSorter.installDefaultQueueSorter and Queue.init
Rob van Oostrum commented on JENKINS-21034 Jenkins Startup Deadlock - QueueSorter.installDefaultQueueSorter and Queue.init @Magnus: I've had this happen after plugin upgrades as well. Yesterday I restarted after upgrading the JDK on Jenkins' server and it deadlocked. Once it deadlocks, restarting again just results in another deadlock. see previous answer I believe my queue had only 2 items in it when I restarted yesterday. It may have been a couple more than that, but not a huge number by any stretch. 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-21092) Adaptable UI for Mobile Devices
Bruno Meneguello created JENKINS-21092 Adaptable UI for Mobile Devices Issue Type: New Feature Assignee: Unassigned Attachments: proto.png Components: core Created: 19/Dec/13 12:50 PM Description: Jenkins interface is targeted for desktop browsers, with large screens and mouse pointers. Frequently I use Jenkins via mobile devices with 4" screens and I need to zoom in and out to be able to read and click. I suggest to tune the UI to adapt to small/medium/large screens. The layout changes needn't to be radical. Just being able to flow the screen vertically and allow the elements to be shrinked horizontally to fit on small device screens help a lot. Environment: mobile Project: Jenkins Priority: Major Reporter: Bruno Meneguello 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] [matrix-auth] (JENKINS-21093) Can't install in Jenkins 1.542 version and greater
Ricardo García Fernández created JENKINS-21093 Cant install in Jenkins 1.542 version and greater Issue Type: Bug Assignee: Jesse Glick Components: matrix-auth Created: 19/Dec/13 1:11 PM Description: I can't install the plugin to manage project based autorization in Jenkins 1.542 to 1.544 version. Required Core 1.535 Thanks! Environment: Jenkins 1.542, Jenkins 1.544 Project: Jenkins Priority: Critical Reporter: Ricardo García Fernández 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] [m2release] (JENKINS-21088) Normalize line endings in git repo
Anders Hammar commented on JENKINS-21088 Normalize line endings in git repo Pull request sent. 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] [m2release] (JENKINS-21088) Normalize line endings in git repo
Anders Hammar assigned JENKINS-21088 to Anders Hammar Normalize line endings in git repo Change By: Anders Hammar (19/Dec/13 1:14 PM) Assignee: teilo AndersHammar 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-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
emanuelez commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) A proposed fix here: https://github.com/jenkinsci/git-client-plugin/pull/44 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-21091) Config flip-flopping
James Howe commented on JENKINS-21091 Config flip-flopping The clientOwner also appears and disappears in a similar fashion, but not at the same time. 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-21070) Set build displayname does not work
Patrice Matignon commented on JENKINS-21070 Set build displayname does not work So in effect, for any other job in the pipeline this function is ineffective? If so, I think this restriction 1) is not made very clear ; and 2) might not be fully justified. If you agree, I could enter a couple different JIRA's. 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-21070) Set build displayname does not work
Patrik Boström commented on JENKINS-21070 Set build displayname does not work I agree it is not clear that the version of the pipeline is set by the first job build display name. It can also be done with the Build Setter Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Build+Name+Setter+Plugin). I will make sure that the wiki will have that information. Just to understand your problem better, do you want to set the version later in the pipeline? 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-21070) Set build displayname does not work
Patrice Matignon commented on JENKINS-21070 Set build displayname does not work Thanks for the quick feedback Patrick. Yes, I have some "pre-release" tasks in the first stage, that can't really determine the pipeline version yet (at least not the way I want it). Also, if any job in the pipeline has the "Set Delivery Pipeline Version" section in its configuration, it implies that the pipeline version could be set/reset at any time during the build flow within that instance. And why couldn't it ? 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] [websphere-deployer] (JENKINS-20891) Websphere Deployer fails to deploy to remote server
Reza Tabrizi commented on JENKINS-20891 Websphere Deployer fails to deploy to remote server there is no lastSuccessful directory in under the "test" directory within the job folder. When I kick of the build in Jenkins, the ear files are being archived here for example: D:\Program Files\Jenkins\jobs\test\modules\another_directoy\builds\2013-01-18_13-25-30\archive\another_directory\test\1.1 I put **/test.ear as the value of ear path as suggested in the documentations. Am I missing something? 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] [xunit] (JENKINS-21094) NullPointerException at org.jenkinsci.plugins.xunit.XUnitPublisher.performTests(XUnitPublisher.java:178)
James Green created JENKINS-21094 NullPointerException at org.jenkinsci.plugins.xunit.XUnitPublisher.performTests(XUnitPublisher.java:178) Issue Type: Bug Assignee: Gregory Boissinot Components: xunit Created: 19/Dec/13 2:12 PM Description: We had a test fail and saw this at the end: channel stopped ANALYSIS-COLLECTOR Computing warning deltas based on reference build #389 xUnit INFO - Starting to record. ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception java.lang.NullPointerException at org.jenkinsci.plugins.xunit.XUnitPublisher.performTests(XUnitPublisher.java:178) at org.jenkinsci.plugins.xunit.XUnitPublisher.performXUnit(XUnitPublisher.java:120) at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:95) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1030) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706) at hudson.model.Run.execute(Run.java:1703) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Finished: FAILURE We now have the test working again but the stack trace above continues. Not sure how to clear the build now. Environment: Jenkins 1544, latest plugins. Project: Jenkins Priority: Major Reporter: James Green 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] [call-remote-job] (JENKINS-21005) API calls return 404 error when asking for JOB information. API returns data for non-Job information.
Bill Williams commented on JENKINS-21005 API calls return 404 error when asking for JOB information. API returns data for non-Job information. That is the problem. I created a new job and I can see data when I call the API: PS C:\Windows\system32 D:\Download\JenkinsApi.ps1 DEBUG: http://localhost:8080/job/TestApi/api/xml freeStyleProjectdescription/descriptiondisplayNameTestApi/displayNamenameTestApi/nameurlhttp://171.206.60.154:8080/job/TestApi//urlbuildabletrue/buildablecolornotbuilt/colorinQueuefalse/inQueuekeepDependenciesfalse/keepDepende nciesnextBuildNumber1/nextBuildNumberproperty/propertyconcurrentBuildfalse/concurrentBuildscm/scm/freeStyleProject What do I have to do to see the other jobs? 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] [matrix-auth] (JENKINS-21093) Can't install in Jenkins 1.542 version and greater
Jesse Glick resolved JENKINS-21093 as Cannot Reproduce Cant install in Jenkins 1.542 version and greater The plugin is bundled in the Jenkins WAR. It does not need to be installed at all. Change By: Jesse Glick (19/Dec/13 2:23 PM) Status: Open Resolved Resolution: CannotReproduce 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] [mailer] (JENKINS-21045) maven 2/3 projects cannot store emailaddress
Jesse Glick commented on JENKINS-21045 maven 2/3 projects cannot store emailaddress Bundled plugins can be upgraded. https://wiki.jenkins-ci.org/display/JENKINS/Pinned+Plugins But the 2.1 version of the Maven plugin requires Jenkins 1.238 or later. It cannot be run in LTS. (Or perhaps it could, but there might be various severe errors.) https://github.com/jenkinsci/maven-plugin/commit/e01eb60574c45b6c16091bfd91a05aa36071df68 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] [mailer] (JENKINS-21045) maven 2/3 projects cannot store emailaddress
Jesse Glick edited a comment on JENKINS-21045 maven 2/3 projects cannot store emailaddress Bundled plugins can be upgraded. https://wiki.jenkins-ci.org/display/JENKINS/Pinned+Plugins But the 2.1 version of the Maven plugin requires Jenkins 1.538 or later. It cannot be run in LTS. (Or perhaps it could, but there might be various severe errors.) https://github.com/jenkinsci/maven-plugin/commit/e01eb60574c45b6c16091bfd91a05aa36071df68 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-21092) Adaptable UI for Mobile Devices
Jesse Glick updated JENKINS-21092 Adaptable UI for Mobile Devices Change By: Jesse Glick (19/Dec/13 2:31 PM) Labels: gui 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-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
lz1asl commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) Can't wait for updated plugin version, well done emanuelez! 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-19453) Slave launcher fails after NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins$MasterComputer
Jesse Glick commented on JENKINS-19453 Slave launcher fails after NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins$MasterComputer Build of this alone applied to 1.532.1: http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/main/jenkins-war/1.532.1.JENKINS-19453/jenkins-war-1.532.1.JENKINS-19453.war 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] [call-remote-job] (JENKINS-21005) API calls return 404 error when asking for JOB information. API returns data for non-Job information.
takeshi ito
commented on JENKINS-21005
API calls return 404 error when asking for JOB information. API returns data for non-Job information.
Most simlest ansuer is set TestApi work same as SubCode. Use TestApi, and give up to call SubCode.
If, If you have to call SubCode, Your way is full of trials and tribulations.
If I am you, I'll set TestApi same as SubCode.
You must keep TestApi callable via api.
And get diff,
{home}/.jenkins/jobs/TestApi/config.xml
to{home}/.jenkins/jobs/SubCode/config.xml
The diff is probrem.
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] [m2release] (JENKINS-21088) Normalize line endings in git repo
SCM/JIRA link daemon commented on JENKINS-21088 Normalize line endings in git repo Code changed in jenkins User: jtnord Path: .gitattributes pom.xml src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseAction.java src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseBadgeAction.java src/main/java/org/jvnet/hudson/plugins/m2release/ReleaseCause.java src/main/java/org/jvnet/hudson/plugins/m2release/dashboard/RecentReleasesPortlet.java src/main/java/org/jvnet/hudson/plugins/m2release/nexus/Stage.java src/main/java/org/jvnet/hudson/plugins/m2release/nexus/StageAction.java src/main/java/org/jvnet/hudson/plugins/m2release/nexus/StageClient.java src/main/java/org/jvnet/hudson/plugins/m2release/nexus/StageException.java src/main/resources/org/jvnet/hudson/plugins/m2release/M2ReleaseAction/failed.jelly src/main/resources/org/jvnet/hudson/plugins/m2release/M2ReleaseAction/index.jelly src/main/resources/org/jvnet/hudson/plugins/m2release/M2ReleaseBadgeAction/badge.jelly src/main/resources/org/jvnet/hudson/plugins/m2release/Messages.properties src/main/resources/org/jvnet/hudson/plugins/m2release/ReleaseCause/description.jelly src/main/resources/org/jvnet/hudson/plugins/m2release/ReleaseCause/description.properties src/main/resources/org/jvnet/hudson/plugins/m2release/dashboard/RecentReleasesPortlet/config.jelly src/main/resources/org/jvnet/hudson/plugins/m2release/dashboard/RecentReleasesPortlet/main.jelly src/main/resources/org/jvnet/hudson/plugins/m2release/dashboard/RecentReleasesPortlet/portlet.jelly src/test/java/org/jvnet/hudson/plugins/m2release/M2ReleaseArgumentInterceptorActionTest.java src/test/java/org/jvnet/hudson/plugins/m2release/nexus/StageClientTest.java src/test/java/org/jvnet/hudson/plugins/m2release/nexus/StageTest.java src/test/resources/org/jvnet/hudson/plugins/m2release/nexus/stageClientTest/activity__closed_failed.xml src/test/resources/org/jvnet/hudson/plugins/m2release/nexus/stageClientTest/activity__closed_ok.xml src/test/resources/org/jvnet/hudson/plugins/m2release/nexus/stageClientTest/profile_repositories.xml src/test/resources/org/jvnet/hudson/plugins/m2release/nexus/stageClientTest/repository__transitioned.xml src/test/resources/org/jvnet/hudson/plugins/m2release/nexus/stageClientTest/repository__transitioning.xml src/test/resources/org/jvnet/hudson/plugins/m2release/nexus/stageClientTest/status__bad_perms.xml src/test/resources/org/jvnet/hudson/plugins/m2release/nexus/stageClientTest/status__ok_perms.xml src/test/resources/org/jvnet/hudson/plugins/m2release/nexus/stageTest/service/local/staging/profiles test/pom.xml test/src/main/java/test/Hello.java http://jenkins-ci.org/commit/m2release-plugin/e70a17d791e6b76d5e565f1887c903ecd3872569 Log: Merge pull request #16 from andham/JENKINS-21088 FIXED JENKINS-21088 Normalize line endings in git repo Compare: https://github.com/jenkinsci/m2release-plugin/compare/f3426cc37b57...e70a17d791e6 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] [m2release] (JENKINS-21088) Normalize line endings in git repo
SCM/JIRA link daemon resolved JENKINS-21088 as Fixed Normalize line endings in git repo Change By: SCM/JIRA link daemon (19/Dec/13 2:39 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plot] (JENKINS-21095) Make 'Data series legend label' data source independent
Ruud Althuizen created JENKINS-21095 Make Data series legend label data source independent Issue Type: Improvement Assignee: nidaley Components: plot Created: 19/Dec/13 2:46 PM Description: For my project I create multiple projects and want to track their ROM and RAM usage. To have a complete overview, I want to have all ROM statistics in a single plot, and all RAM statistics in another plot. With the 'java properties file' source, it's possible to define a custom label. Right now I'm using .csv files instead. The problem that I run into is that all my data series all define the their own RAM value, which means that only the last value is remembered. The solution for me would be to make the 'Data series legend label' field available for all data source types. In my case I'd call the plot 'ROM usage' and each data series by the projects name. Project: Jenkins Priority: Major Reporter: Ruud Althuizen 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-18680) View.onJobRenamed should be deprecated
Daniel Beck commented on JENKINS-18680 View.onJobRenamed should be deprecated Also affected are users' views when renaming top-level (or any level really) jobs because they don't get notified either. 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-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
Peter Phillips commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) The git syntax to remove the credentials is incorrect. It should be: git config --local --unset credential.helper However, in my case, the finally block with the incorrect command was just masking the true error. With emanuelez's fix in place I now get the same error as the first stack trace i.e.: stdout: stderr: error: unknown option `store=C:WindowsTEMPgit5425335305109688552.credentials' usage: git credential-store options action --file path fetch and store credentials in path 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] [call-remote-job] (JENKINS-21005) API calls return 404 error when asking for JOB information. API returns data for non-Job information.
Bill Williams commented on JENKINS-21005 API calls return 404 error when asking for JOB information. API returns data for non-Job information. It is a security issue. When I set Anonymous to Read, it works. This is very misleading because Jenkins should return a 403 error (or something other than a 404). Thanks to your help, I will be able to figure out how to make this work. Thanks again! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [call-remote-job] (JENKINS-21005) API calls return 404 error when asking for JOB information. API returns data for non-Job information.
takeshi ito commented on JENKINS-21005 API calls return 404 error when asking for JOB information. API returns data for non-Job information. Awesome. Finally close this Ticket please. 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] [call-remote-job] (JENKINS-21005) API calls return 404 error when asking for JOB information. API returns data for non-Job information.
Bill Williams commented on JENKINS-21005 API calls return 404 error when asking for JOB information. API returns data for non-Job information. One more note. Even if you use the API token and send credentials of one of the user accounts to read the API, if you don't have Anonymous set to read, you will get a 404 (Not Found) error. Seems like a bug but I don't care anymore as long as there is a workaround. Thanks again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cloudbees-folder] (JENKINS-18028) ItemListener.onMoved
Jesse Glick assigned JENKINS-18028 to Jesse Glick ItemListener.onMoved Change By: Jesse Glick (19/Dec/13 3:20 PM) Assignee: JesseGlick 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] [cloudbees-folder] (JENKINS-18028) ItemListener.onMoved
Jesse Glick started work on JENKINS-18028 ItemListener.onMoved Change By: Jesse Glick (19/Dec/13 3:20 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] [security] (JENKINS-14612) Auto Created users: Can't change password
evernat commented on JENKINS-14612 Auto Created users: Cant change password I do not reproduce the issue: the configure screen opens up for my server. Do you reproduce the issue with a recent Jenkins version? If yes, can you look in the server logs to see if there is an exception with a stack-trace for that action? 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] [call-remote-job] (JENKINS-21005) API calls return 404 error when asking for JOB information. API returns data for non-Job information.
Bill Williams resolved JENKINS-21005 as Not A Defect API calls return 404 error when asking for JOB information. API returns data for non-Job information. Change By: Bill Williams (19/Dec/13 3:21 PM) Status: Open Resolved 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] [matrix-auth] (JENKINS-21093) Can't install in Jenkins 1.542 version and greater
Ricardo García Fernández commented on JENKINS-21093 Cant install in Jenkins 1.542 version and greater I have this problem related to: version 1.532 is not installed and works. but in version 1.544 I have installed the plugin and I can't configure security per Job. Global Configuration works both. I'll continue testing environments. 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] [scm-sync-configuration] (JENKINS-21096) scm-sync-configuration: Store artifacts in git, is this really intended?
Torbjörn Axelsson created JENKINS-21096 scm-sync-configuration: Store artifacts in git, is this really intended? Issue Type: Bug Affects Versions: current Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 19/Dec/13 3:44 PM Description: When I pulled the scm-config repository I was suprised to se 6 GB of data being pulled down. I seems that all the artifacts are stored in git. Is this really intended? The artifacts are not xml files, it is the content of jobs/buildname/builds/ that is stored. I thought this was just storing configuration. Project: Jenkins Priority: Major Reporter: Torbjörn Axelsson 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-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
emanuelez commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) Well spotted Peter. Now I also use --unset in the pull request. 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] [scm-sync-configuration] (JENKINS-21096) scm-sync-configuration: Store artifacts in git, is this really intended?
Frédéric Camblor commented on JENKINS-21096 scm-sync-configuration: Store artifacts in git, is this really intended? This reminds me of JENKINS-17545 and a bug in the scan() method used, and which was fixed prior to version 0.0.7.2 Which version of the plugin are you using ? 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] [s3] (JENKINS-19725) Unable to unmarshall response (Couldn't initialize a SAX driver to create an XMLReader)
K Daniels commented on JENKINS-19725 Unable to unmarshall response (Couldnt initialize a SAX driver to create an XMLReader) I am also seeing this, fresh installation of Jenkins (1.424.6) with the S3 plugin. 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
Morgan Sveen commented on JENKINS-20664 radiator-view plugin stop work after upgrade to 1.539 David, let's consider our case. We are running 1.532.1 - this is a LTS. From what I gather, no version of this plugin will work with the most current LTS. Was there no integration testing done for this plugin with Jenkins versions over the last few months? Previous versions of the radiator plugin will work with previous versions of Jenkins. If you make a clear note of this, folks will be able to download and use the relevant version of this plugin and you won't need to worry too much about backwards compatibility. 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
Morgan Sveen edited a comment on JENKINS-20664 radiator-view plugin stop work after upgrade to 1.539 David, let's consider our case. We are running Jenkins 1.532.1 - this is a LTS. From what I gather, no version of this plugin will work with the most current Jenkins LTS. Was there no integration testing done for this plugin with Jenkins versions over the last few months? Previous versions of the radiator plugin will work with previous versions of Jenkins. If you make a clear note of this, folks will be able to download and use the relevant version of this plugin and you won't need to worry too much about backwards compatibility. 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] [scm-sync-configuration] (JENKINS-21096) scm-sync-configuration: Store artifacts in git, is this really intended?
Torbjörn Axelsson commented on JENKINS-21096 scm-sync-configuration: Store artifacts in git, is this really intended? We are running 0.0.7.3 on Jenkins 1.543 However, upon closer examination the files saved are from 2013-10-31_11-17-51/ (and earlier) at which point we might very well have used a version prior to 0.0.7.2 Should have looked closer before reporting the problem. Thanks for a very good (and addictive) plugin and a really rapid response. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
emanuelez
commented on JENKINS-21016
Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
I can't really see how File.createTempFile("git", ".credentials").getAbsolutePath() can produce a string with no slashes...
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-21097) Add line breaking for columns LastSuccessfulBuild, LastFailedBuild, etc
Nickolay Rumyantsev created JENKINS-21097 Add line breaking for columns LastSuccessfulBuild, LastFailedBuild, etc Issue Type: Improvement Assignee: Unassigned Attachments: Line_breaks.png Components: core Created: 19/Dec/13 4:37 PM Description: Since 1.517 job names and some other long strings that are displayed by Jenkins are splitted with wbr tag which allows to break them into a number of lines. It would be great to do the same for string in other view columns like LastSuccessfulBuild, LastFailedBuild, because sometimes the build name is customised and become very long. In this case most of the visual space is taken by this columns. I've added a screenshot with explanation. Project: Jenkins Priority: Minor Reporter: Nickolay Rumyantsev 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] [scm-sync-configuration] (JENKINS-21096) scm-sync-configuration: Store artifacts in git, is this really intended?
Torbjörn Axelsson closed JENKINS-21096 as Fixed scm-sync-configuration: Store artifacts in git, is this really intended? Change By: Torbjörn Axelsson (19/Dec/13 4:44 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-21096) scm-sync-configuration: Store artifacts in git, is this really intended?
Torbjörn Axelsson resolved JENKINS-21096 as Fixed scm-sync-configuration: Store artifacts in git, is this really intended? The issues is fixed in a version we already have upgraded to. Change By: Torbjörn Axelsson (19/Dec/13 4:44 PM) Status: Open Resolved Assignee: FrédéricCamblor TorbjörnAxelsson 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] [matrix-auth] (JENKINS-21093) Can't install in Jenkins 1.542 version and greater
Jesse Glick commented on JENKINS-21093 Cant install in Jenkins 1.542 version and greater So it sounds like in 1.544 the plugin is installed, but not fully functional? Are you sure you configured project-based matrix auth, not global matrix auth? It is working fine for me in a fresh $JENKINS_HOME where I started 1.544, installed Mock Security Realm, configured global security to use Mock Security Realm and Project-Based Matrix Auth, and created a job: the checkbox to enable security for this job was shown as expected. 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] [cloudbees-folder] (JENKINS-20008) Need core API corresponding to ItemGroupModifier
SCM/JIRA link daemon commented on JENKINS-20008 Need core API corresponding to ItemGroupModifier Code changed in jenkins User: Jesse Glick Path: src/main/java/com/cloudbees/hudson/plugins/folder/Folder.java src/main/java/com/cloudbees/hudson/plugins/folder/relocate/ItemGroupModifier.java http://jenkins-ci.org/commit/cloudbees-folder-plugin/a7966ad20fbd6b8d794a3e23554f9c640d33ac60 Log: JENKINS-20008 Using DirectlyModifiableTopLevelItemGroup.remove. 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] [websphere-deployer] (JENKINS-20891) Websphere Deployer fails to deploy to remote server
Greg Peters edited a comment on JENKINS-20891 Websphere Deployer fails to deploy to remote server Reza, This is a bug that's currently being worked on (there is no workaround at this time). Please provide the OS name version that's running Jenkins. Also provide the version of Jenkins. Please expect ~2 weeks for the update. 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-client] (JENKINS-21074) Git Client plugin fails to install on fresh Jenkins installation
Peter Miklosko commented on JENKINS-21074 Git Client plugin fails to install on fresh Jenkins installation Nicolas De Loof let me know if you need anymore details in regards of this bug 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] [websphere-deployer] (JENKINS-20891) Websphere Deployer fails to deploy to remote server
Greg Peters updated JENKINS-20891 Websphere Deployer fails to deploy to remote server Change By: Greg Peters (19/Dec/13 5:46 PM) Labels: jenkinsjobplugin Priority: Major Blocker 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] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
cowwoc commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification Jesse, I just reproduced the problem. Unfortunately I didn't have the logger enabled so we missed an opportunity. I did notice something very interesting though: 1. A build failed and tried to send an email to an auto-generated user with underscores 2. I went into Jenkins - People and sure enough the user's email address had underscores 3. I rebooted Jenkins and went into Manage Jenkins - Manage Users and all of a sudden that same user no longer had underscores in the email address. It's not clear whether the reboot or Manage Users fixed the email address, but that's another clue of what's going on. I've enabled the logger, so the next time this happens I will catch it. 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] [websphere-deployer] (JENKINS-20891) Websphere Deployer fails to deploy to remote server
Reza Tabrizi commented on JENKINS-20891 Websphere Deployer fails to deploy to remote server jenkins:1.532 OS: Windows Server 2k8 R2 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-21070) Set build displayname does not work
Julian M.
edited a comment on JENKINS-21070
Set build displayname does not work
Hi Patrik, thanks for getting back to me so fast. I understand it sets the displayname only in the first job. But for me, it is NOT setting it in the initial job, where I activated this option.
My setup is:
1. job: Activated "Create delivery pipeline" + "Set build displayname"
2-4 job: Set ${PIPELINE_VERSION} by using the Build Setter plugin
Still, my builds are named #26 for example. I am still using Jenkins 1.518 (because we built a lot of legacy Java 5 projects, which do not build good on newer versions), perhaps this could be an 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] [delivery-pipeline] (JENKINS-21070) Set build displayname does not work
Julian M.
commented on JENKINS-21070
Set build displayname does not work
Hi Patrick, thanks for getting back to me so fast. I understand it sets the displayname only in the first job. But for me, it is NOT setting it in the initial job, where I activated this option.
My setup is:
1. job: Activated "Create delivery pipeline" + "Set build displayname"
2-4 job: Set ${PIPELINE_VERSION} by using the Build Setter plugin
Still, my builds are named #26 for example. I am still using Jenkins 1.518 (because we built a lot of legacy Java 5 projects, which do not build good on newer versions), perhaps this could be an 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-18678) Builds disappear some time after renaming job
Arvind Ramalingam commented on JENKINS-18678 Builds disappear some time after renaming job Daniel: The issue I am facing is that latter one. I understand what reload configuration does but I dont prefer doing it as there are issues with gerrit trigger plugin re running all the patch sets again.But thanks for you confirmation that it is a one time activity and the renamed jobs should have build history. Cool I will test out the new LTS This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21098) VM crash with no information in jenkins log
Bill Brown created JENKINS-21098 VM crash with no information in jenkins log Issue Type: Bug Assignee: Unassigned Attachments: hs_err_pid29421.log.txt Components: core Created: 19/Dec/13 7:47 PM Description: Hello. Jenkins has been crashing after one day or two days up routinely for the past year or so. I don't have the version handy for when this started. I'm currently using 1.543 I'm attaching the latest jvm crash report. The last three look the same and it seems to crash during SAM polling. Is this a known issue or is there something you can recommend for me to work around this? Thanks. Environment: vm_info: OpenJDK 64-Bit Server VM (20.0-b12) for linux-amd64 JRE (1.6.0_24-b24), built on Oct 31 2013 07:52:48 by mockbuild with gcc 4.1.2 20080704 (Red Hat 4.1.2-54) Project: Jenkins Labels: crash scm maven Priority: Major Reporter: Bill Brown 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-21091) Config flip-flopping
Rob Petti commented on JENKINS-21091 Config flip-flopping I can't say I've ever seen that before. clientOwner definitely shouldn't change unless you change it, but firstChange might change it's value if you change the way the plugin syncs (syncing to head one build, then syncing to a changeset the next build, etc). Another possibility is that these values are (at least partially) transient, and that deserialization during startup is causing the issue. Do you frequently restart Jenkins or reload configuration from disk? 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-21070) Set build displayname does not work
Patrik Boström
commented on JENKINS-21070
Set build displayname does not work
Hi Julian,
I tried Jenkins 1.518 with Delivery Pipeline Plugin 0.6.7.
Created a job "a" with "Create Delivery Pipeline version", "set display name" and template 1.0.0.${BUILD_NUMBER}
Created a job "b" with Build Name Setter with build name ${ENV,var="PIPELINE_VERSION"}.
Job a triggers b.
Both build are named with the version 1.0.0.1 after the first build.
So I cant reproduce your problem.
The plugin supports Jenkins 1.509 and greater so the your version of Jenkins should not be the problem.
Can you give me some more details?
What JVM and version are used for Jenkins?
What template are you using for the version in the first job?
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-20461) Git Plugin 2.0: fails to clone repo
Nathan Nutter commented on JENKINS-20461 Git Plugin 2.0: fails to clone repo This does seem to be a duplicate of JENKINS-20258. 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] [scm-sync-configuration] (JENKINS-21096) scm-sync-configuration: Store artifacts in git, is this really intended?
Frédéric Camblor commented on JENKINS-21096 scm-sync-configuration: Store artifacts in git, is this really intended? Great ! 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-21070) Set build displayname does not work
Patrik Boström assigned JENKINS-21070 to Patrik Boström Set build displayname does not work Change By: Patrik Boström (19/Dec/13 8:08 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] [delivery-pipeline] (JENKINS-20717) Add pipelines to view dymacally with regexp
Patrik Boström commented on JENKINS-20717 Add pipelines to view dymacally with regexp I have created a branch called "regexp" which has a suggested implementation of feature. Please check it out and give feedback. 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-21010) Better representation of parallel stages
Patrik Boström commented on JENKINS-21010 Better representation of parallel stages This is something that we should look at. 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] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Jesse Glick commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification If you figure out how to reproduce it from scratch then I can fix it. I am pretty sure the problem somehow lies with a userId getting passed from one place to another without a User context, and then Jenkins serializing the user record at the wrong time, but I do not know the sequence of events that makes this happen to some people some times. 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-21099) Don't give useless build time estimates
Daniel Beck created JENKINS-21099 Dont give useless build time estimates Issue Type: Improvement Assignee: Unassigned Components: core Created: 19/Dec/13 9:18 PM Description: Disregarding jobs where there are significant differences (e.g. parameters causing every other build to do twice the work) between builds, we use the estimated build time mostly to determine 'by when do we have a result?'. There is some (±5-10%, the longer the duration the less variation) variation between durations of successful builds, but it's still good enough for an estimate based on how the UI works. Unfortunately, this commit changed computation of build duration estimates: https://github.com/jenkinsci/jenkins/commit/04d85eb476bdc57eb7ac3c2bb34e91be5b55c487 Before: Use the average of the last up to three successful builds. Use fewer if no three successful builds exist. If there are no successful builds, don't attempt to provide an estimate. Now: Only look at the last six builds. Use the average of the last up to three successful builds of those. If there are fewer than three successful builds, also use the latest failed (but not aborted) builds to get three builds to base the estimate on. If three or fewer completed builds exist, use those. So, if there's only one successful build among the last six builds, it will also consider the latest two failed builds for the estimate. If there are no successful builds, use the build duration until previous build failures as estimate. Taking into account failing builds makes the estimate completely meaningless. It doesn't tell you anything, because the data it uses is all over the place (and it uses too few data points for more sophisticated estimates). For a job that often fails after ~2-3 hours but takes 10 hours to complete successfully, this will often reduce the estimate to just ~5 hours. Even just considering one failed and two successful builds will result in an estimate of 7.5, which is way off the actual duration to get a successful build. Build failures should be considered exceptional conditions. For non-fatal issues, builds can be marked unstable. So failures should not be used in estimating build durations, as some unreliable component used in a build will completely distort build durations. I'd rather have it use the average of the last N (e.g. 3 or 5) successful builds, and if there are fewer than M (e.g. 1, or 3), just give no estimate at all. For jobs that also have wildly varying durations for successful builds, it might actually be useful to not provide an estimated duration this would make it explicit that Jenkins has no confidence in providing an estimate. 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] [core] (JENKINS-21099) Don't give useless build time estimates by considering failed builds' durations
Daniel Beck updated JENKINS-21099 Dont give useless build time estimates by considering failed builds durations Change By: Daniel Beck (19/Dec/13 9:24 PM) Summary: Dontgiveuselessbuildtimeestimates byconsideringfailedbuildsdurations Description: Disregardingjobswheretherearesignificantdifferences(e.g.parameterscausingeveryotherbuildtodotwicethework)betweenbuilds,weusetheestimatedbuildtimemostlytodetermine_bywhendowehavearesult?_.Thereissome(±5-10%,thelongerthedurationthelessvariation)variationbetweendurationsofsuccessfulbuilds,butitsstillgoodenoughforanestimatebasedonhowtheUIworks.Unfortunately,thiscommitchangedcomputationofbuilddurationestimates:https://github.com/jenkinsci/jenkins/commit/04d85eb476bdc57eb7ac3c2bb34e91be5b55c487*Before:*Usetheaverageofthelastuptothreesuccessfulbuilds.Usefewerifnothreesuccessfulbuildsexist.Iftherearenosuccessfulbuilds,dontattempttoprovideanestimate.*Now:*Onlylookatthelastsixbuilds.Usetheaverageofthelastuptothreesuccessfulbuildsofthose.Iftherearefewerthanthreesuccessfulbuilds,alsousethelatestfailed(butnotaborted)buildstogetthreebuildstobasetheestimateon.Ifthreeorfewercompletedbuildsexist,usethose.So,iftheresonlyonesuccessfulbuildamongthelastsixbuilds,itwillalsoconsiderthelatesttwofailedbuildsfortheestimate.*Iftherearenosuccessfulbuilds,usethebuilddurationuntilpreviousbuildfailuresasestimate*. Notgoingfarbackinthejobhistoryisagoodideatoensurecomputationisquick.FillingupthelistofcandidatebuildswithfailedbuildsOTOH,isnot. *Takingintoaccountfailingbuildsmakestheestimatecompletelymeaningless.*Itdoesnttellyouanything,becausethedataitusesisallovertheplace(anditusestoofewdatapointsformoresophisticatedestimates).Forajobthatoftenfailsafter~2-3hoursbuttakes10hourstocompletesuccessfully,thiswilloftenreducetheestimatetojust~5hours.Evenjustconsideringonefailedandtwosuccessfulbuildswillresultinanestimateof7.5,whichiswayofftheactualdurationtogetasuccessfulbuild.*Buildfailuresshouldbeconsideredexceptionalconditions.*Fornon-fatalissues,buildscanbemarkedunstable.*Sofailuresshouldnotbeusedinestimatingbuilddurations,*assomeunreliablecomponentusedinabuildwillcompletelydistortbuilddurations. Surprisingly,thechangeonlyconsiders_completed_buildsandexcludes_aborted_buildsfromtheestimate.Thisrespectsthestatusofabortedbuildsasexceptionalandunfitforbuildestimates(unlesscausedbytheBuildTimeoutPlugin…).Butfailedbuildsarenomoreusefultobuildanestimateon! IdratherhaveitusetheaverageofthelastN(e.g.3or5)_successful_builds,andiftherearefewerthanM(e.g.1,or3),*justgivenoestimateatall.*Forjobsthatalsohavewildlyvaryingdurationsforsuccessfulbuilds,itmightactuallybeusefultonotprovideanestimatedduration--thiswouldmakeit*explicitthatJenkinshasnoconfidenceinprovidinganestimate.* 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-21099) Don't give useless build time estimates by considering failed builds' durations
Daniel Beck updated JENKINS-21099 Dont give useless build time estimates by considering failed builds durations Change By: Daniel Beck (19/Dec/13 9:40 PM) Description: Disregardingjobswheretherearesignificantdifferences(e.g.parameterscausingeveryotherbuildtodotwicethework)betweenbuilds,we We usetheestimatedbuildtimemostlytodetermine_bywhen do will wehavearesult?_.Thereissome(±5-10%,thelongerthedurationthelessvariation)variationbetweendurationsofsuccessfulbuilds,butitsstillgoodenoughforanestimate basedonhowtheUIworks (disregardingjobswheretherearesignificantdifferencesbetweenbuildsduetoe . g.parameters). Unfortunately,thiscommitchangedcomputationofbuilddurationestimates:https://github.com/jenkinsci/jenkins/commit/04d85eb476bdc57eb7ac3c2bb34e91be5b55c487*Before:*Usetheaverageofthelastuptothreesuccessfulbuilds.Usefewerifnothreesuccessfulbuildsexist.Iftherearenosuccessfulbuilds,dontattempttoprovideanestimate.*Now:*Onlylookatthelastsixbuilds.Usetheaverageofthelastuptothreesuccessfulbuildsofthose.Iftherearefewerthanthreesuccessfulbuilds,alsousethelatestfailed(butnotaborted)buildstogetthreebuildstobasetheestimateon.Ifthreeorfewercompletedbuildsexist,usethose.So,iftheresonlyonesuccessfulbuildamongthelastsixbuilds,itwillalsoconsiderthelatesttwofailedbuildsfortheestimate.*Iftherearenosuccessfulbuilds,usethebuilddurationuntilpreviousbuildfailuresasestimate*.Notgoingfarbackinthejobhistoryisagoodideatoensurecomputationisquick.FillingupthelistofcandidatebuildswithfailedbuildsOTOH,isnot.*Takingintoaccountfailingbuildsmakestheestimatecompletelymeaningless.*Itdoesnttellyouanything,becausethedataitusesisallovertheplace(anditusestoofewdatapointsformoresophisticatedestimates).Forajobthatoftenfailsafter~2-3hoursbuttakes10hourstocompletesuccessfully,thiswilloftenreducetheestimatetojust~5hours.Evenjustconsideringonefailedandtwosuccessfulbuildswillresultinanestimateof7.5,whichiswayofftheactualdurationtogetasuccessfulbuild.*Buildfailuresshouldbeconsideredexceptionalconditions.*Fornon-fatalissues,buildscanbemarkedunstable.*Sofailuresshouldnotbeusedinestimatingbuilddurations,*assomeunreliablecomponentusedinabuildwillcompletelydistortbuilddurations.Surprisingly,thechangeonlyconsiders_completed_buildsandexcludes_aborted_buildsfromtheestimate.Thisrespectsthestatusofabortedbuildsasexceptionalandunfitforbuildestimates(unlesscausedbytheBuildTimeoutPlugin…).Butfailedbuildsarenomoreusefultobuildanestimateon!IdratherhaveitusetheaverageofthelastN(e.g.3or5)_successful_builds,andiftherearefewerthanM(e.g.1,or3),*justgivenoestimateatall.*Forjobsthatalsohavewildlyvaryingdurationsforsuccessfulbuilds,itmightactuallybeusefultonotprovideanestimatedduration--thiswouldmakeit*explicitthatJenkinshasnoconfidenceinprovidinganestimate.* 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-20461) Git Plugin 2.0: fails to clone repo
Mark Waite resolved JENKINS-20461 as Duplicate Git Plugin 2.0: fails to clone repo Duplicate of JENKINS-20258 Change By: Mark Waite (19/Dec/13 9:45 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20461) Git Plugin 2.0: fails to clone repo
Mark Waite commented on JENKINS-20461 Git Plugin 2.0: fails to clone repo It seems like "don't prune the local branches" is an easy work around. Are there serious problems if you don't prune the local branches? 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] [checkstyle] (JENKINS-21084) Jenkins can't see workspace files created on a slave node
Ulli Hafner commented on JENKINS-21084 Jenkins cant see workspace files created on a slave node I see, this has nothing to do with the analysis plug-ins. Seems that your workspace setup is broken. Maybe it would help to discuss the problem on the mailing list, this seems to be a configuration problem and not a bug. First of all, the workspace needs to be visible to Jenkins. 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-21084) Jenkins can't see workspace files created on a slave node
Ulli Hafner updated JENKINS-21084 Jenkins cant see workspace files created on a slave node Change By: Ulli Hafner (19/Dec/13 9:51 PM) Assignee: UlliHafner Due Date: 31/Dec/13 Component/s: core Component/s: checkstyle 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-21084) Jenkins can't see workspace files created on a slave node
Ulli Hafner resolved JENKINS-21084 as Not A Defect Jenkins cant see workspace files created on a slave node I think you need to clarify how you did compose your slave workspace. Change By: Ulli Hafner (19/Dec/13 9:51 PM) Status: Open Resolved 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] [core] (JENKINS-20993) org.apache.commons.jelly.JellyTagException when Logging in
Scott MacDonald commented on JENKINS-20993 org.apache.commons.jelly.JellyTagException when Logging in Still an issue in 1.5444 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-18680) View.onJobRenamed should be deprecated
Jesse Glick started work on JENKINS-18680 View.onJobRenamed should be deprecated Change By: Jesse Glick (19/Dec/13 11:05 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.
