[JIRA] (JENKINS-16501) Logged in users should have read only permissions automatically
Pardeep Chahal created JENKINS-16501 Logged in users should have read only permissions automatically Issue Type: New Feature Assignee: Kohsuke Kawaguchi Components: openid, role-strategy, security Created: 28/Jan/13 7:58 AM Description: I have enabled openID google apps in Jenkins and it is working fine. Only issue is I need to give read only permissions to new users. Is it possible for new logged in users to get read only permissions automatically. I also want to give job-creater permissions to some users by my own. But logged in users should have read only permission by default. Please suggest Due Date: 29/Jan/13 12:00 AM Project: Jenkins Priority: Major Reporter: Pardeep Chahal 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] (JENKINS-11337) Git plugin only triggers a build for one branch
Ahmed Mubbashir Khan commented on JENKINS-11337 Git plugin only triggers a build for one branch Is there any update on 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] (JENKINS-16482) SSH slave connection issues after Jenkins update
tiainpa commented on JENKINS-16482 SSH slave connection issues after Jenkins update We removed Smart Jenkins plugin and now we can connect slaves using JNLP. Something prevents SSH slaves working still.. 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] (JENKINS-16448) WORKSPACE env variable is incorrect for matrix project
Magnus Jacobsson commented on JENKINS-16448 WORKSPACE env variable is incorrect for matrix project No, I only have access to one Jenkins server (and it's not clean). 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] (JENKINS-16233) EnvInject plugin using a cached value for ${WORKSPACE}
Magnus Jacobsson
commented on JENKINS-16233
EnvInject plugin using a cached value for ${WORKSPACE}
I see the same problem, see https://issues.jenkins-ci.org/browse/JENKINS-16448.
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, send email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16451) Clean workspace plugin chmods the top-level directory to complete crap
vjuranek commented on JENKINS-16451 Clean workspace plugin chmods the top-level directory to complete crap This is not an issue of ws cleanup plugin, but rather in Jenkins core as it uses Jenkins core functionality or deleting workspaces. It's usually caused by a file, which cannot be deteled (e.g. still open by another process). In such cases Jenkins tries to chmod upper directory (i.e. it's a feature, not a bug), which sometimes (especially on Unix) results into what you described. Moving into the "core" component. 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16451) Workspace cleanup chmods the top-level directory to complete crap
vjuranek updated JENKINS-16451 Workspace cleanup chmods the top-level directory to complete crap Change By: vjuranek (28/Jan/13 9:09 AM) Summary: Cleanworkspaceplugin Workspacecleanup chmodsthetop-leveldirectorytocompletecrap Component/s: core Component/s: 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] (JENKINS-16451) Workspace cleanup chmods the top-level directory to complete crap
Yury Pukhalsky commented on JENKINS-16451 Workspace cleanup chmods the top-level directory to complete crap Aha, ok. I think there are such files, alright. But yet it's very harsh behaviour — render the thing unusable Sometimes i even have workspace/ directory getting the Number of the Beast (albeit i haven't yet pinpointed it) and that is much worse. PS. As you seem to be alive, the 14875 is core bug too? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16496) latest version of jobConfigHistory fails on the first run when using a matrix job
Mirko Friedenhagen assigned JENKINS-16496 to Kathi Stutz latest version of jobConfigHistory fails on the first run when using a matrix job Kathi, what happens when this is the first execution and in https://github.com/kstutz/jobConfigHistory-plugin/blob/9626f165d5034bad20660e2bc047c641d1f13cc5/src/main/java/hudson/plugins/jobConfigHistory/JobConfigBadgeAction.java#L56 the nextBuildNumber is 1? We need to check for the length of builds as well, probably. Change By: Mirko Friedenhagen (28/Jan/13 9:25 AM) Assignee: MirkoFriedenhagen KathiStutz 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] (JENKINS-16095) Heap memory leak (possibly jclouds plugin related)
onemanbucket commented on JENKINS-16095 Heap memory leak (possibly jclouds plugin related) We've used a jclouds-plugin build based on jclouds 1.6.0-snapshot, for a week now and the leak seems to be gone. 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] (JENKINS-16502) Permission to see an executor/slave
Christian Meyer created JENKINS-16502 Permission to see an executor/slave Issue Type: New Feature Assignee: Christian Meyer Components: core Created: 28/Jan/13 9:35 AM Description: In our environment it would be very helpful to be able to set Permissions, who can see specific executors/slaves. It should be like with jobs/projects, where the method "hasPermission()" is called, before you get all Items of the jenkins-instance. So it would be just needed in the Computer.java a new attribute "Permission VIEW", and in the Jenkins.java in the Method "getComputer()" the check, if the user has the Permission to see this slave. Project: Jenkins Priority: Minor Reporter: Christian Meyer 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16451) Workspace cleanup chmods the top-level directory to complete crap
vjuranek commented on JENKINS-16451 Workspace cleanup chmods the top-level directory to complete crap yes, definitely agree that it's a bug, "a feature, not a bug" was a kind of (probably inappropriate) joke 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14875) It takes aeons to delete large workspace on slow disks
vjuranek commented on JENKINS-14875 It takes aeons to delete large workspace on slow disks Hi, it can be an issue in apache DirectoryScanner or and issue in Jenkins core whicih deletes the directories. My tip is, that it's and Jenkins core issue as it deletes directories recursively so if you have a capacious sub-directory structure, I can imagine it takes quite a long time to delete it. Could you please run a test job without any filter and check how long it takes to delete this structure without nay filter to be sure that the issue is in way how Jenkins deletes the directories? Thanks and sorry for the delay to response this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14875) It takes aeons to delete large workspace on slow disks
Yury Pukhalsky commented on JENKINS-14875 It takes aeons to delete large workspace on slow disks I cannot… Unfortunately the setup has long been demolished. 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14875) It takes aeons to delete large workspace on slow disks
vjuranek commented on JENKINS-14875 It takes aeons to delete large workspace on slow disks never mind, once I have some spare time, I'll try to reproduce. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16018) Not all builds show in the build history dashboard on job
Ric Klaren commented on JENKINS-16018 Not all builds show in the build history dashboard on job Same issue with 1.498 on Centos 6. The problem is temporarily resolved after a jenkins restart. No obvious errors/warnings in the jenkins logs regarding the misbehaving jobs After a restart, the issue may reappear after a night (we run a nightly clean then, so it may be a file handle issue) Today we increased the file handle limits for the jenkins user see if that helps. 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16503) Support for Github statues API
François Garillot created JENKINS-16503 Support for Github statues API Issue Type: Improvement Assignee: Unassigned Components: github Created: 28/Jan/13 11:19 AM Description: It would be AWESOME if the github-plugin could support the commit status API, especially when doing CI on pull requests: https://github.com/blog/1227-commit-status-api I'd love to see that a build is pending/successful/failed on a PR. Project: Jenkins Priority: Major Reporter: François Garillot 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] (JENKINS-16499) NPE when new job by copy from existing one
Stefan Brausch commented on JENKINS-16499 NPE when new job by copy from existing one Which version of the jobconfighistory plugin do you use in your 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] (JENKINS-16165) Configure screen stuck in LOADING state
Brian Preuß commented on JENKINS-16165 Configure screen stuck in LOADING state Zeitstempel: 28.01.2013 12:59:05 Fehler: TypeError: $(...) is undefined Quelldatei: https://hostname:port/path/adjuncts/89bcf893/lib/form/radioBlock/radioBlock.js Zeile: 53 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] (JENKINS-15704) Incomplete list of builds when I go to JobName/api/json
pedro reis commented on JENKINS-15704 Incomplete list of builds when I go to JobName/api/json This happens also in Python Remote API. This started to happen when upgraded to Jenkins 1.491. The "lastBuild" element is immediately updated but the "builds" element is not! (And this caused problems in our building and dependencies system) 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] (JENKINS-15583) building builds (running builds) do not show up anymore in the list of builds of a job (json API)
pedro reis commented on JENKINS-15583 building builds (running builds) do not show up anymore in the list of builds of a job (json API) This problem also occurs at python api. I think we can use "lastBuild" element instead of "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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-755) Default JDK meaning in project options is confusing.
S Stack commented on JENKINS-755 Default JDK meaning in project options is confusing. JDK mismatch just caused an important deploy here to fail. Worse, some jobs don't even show the JDK drop-down in their configuration screen. This means we have to modify the job config.xml directly. Completely agree "default" is misleading. Is "default" the 2nd JDK defined? Please consider removing this ambiguity which can cause incidents at the worst possible moment. Thanks. 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] (JENKINS-16499) NPE when new job by copy from existing one
Dirk Kuypers commented on JENKINS-16499 NPE when new job by copy from existing one I have the same issue since upgrading to 1.500 and I am using version 2.1.1 of the jobconfighistory 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] (JENKINS-16504) Builds were failing
Anup T S created JENKINS-16504 Builds were failing Issue Type: Bug Assignee: Unassigned Components: other Created: 28/Jan/13 1:30 PM Description: Hi Team, Builds are failing and i could see the below errors in catalina.out log.May i know what could be the reason please? It sayd Java heap size issue but we have set Xmx for 6GB. Jan 28, 2013 1:48:42 AM hudson.triggers.SafeTimerTask run SEVERE: Timer task hudson.model.LoadStatistics$LoadStatisticsUpdater@1efa7ea7 failed java.lang.OutOfMemoryError: Java heap space Jan 28, 2013 1:48:42 AM hudson.slaves.ChannelPinger$1 onDead INFO: Ping failed. Terminating the channel. java.io.IOException: SSH channel is closed. (Close requested by remote) at com.trilead.ssh2.channel.ChannelManager.sendData(ChannelManager.java:383) at com.trilead.ssh2.channel.ChannelOutputStream.write(ChannelOutputStream.java:63) at java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1838) at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(ObjectOutputStream.java:1747) at java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:1249) at java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1203) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1387) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) at java.io.ObjectOutputStream.writeFatalException(ObjectOutputStream.java:1538) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:329) at hudson.remoting.Command.writeTo(Command.java:81) at hudson.remoting.ClassicCommandTransport.write(ClassicCommandTransport.java:41) at hudson.remoting.Channel.send(Channel.java:496) at hudson.remoting.Request.callAsync(Request.java:208) at hudson.remoting.Channel.callAsync(Channel.java:690) at hudson.remoting.PingThread.ping(PingThread.java:99) at hudson.remoting.PingThread.run(PingThread.java:81) Jan 28, 2013 1:49:22 AM hudson.slaves.ChannelPinger$1 onDead SEVERE: Failed to terminate the channel: java.io.IOException: SSH channel is closed. (Close requested by remote) at com.trilead.ssh2.channel.ChannelManager.sendData(ChannelManager.java:383) at com.trilead.ssh2.channel.ChannelOutputStream.write(ChannelOutputStream.java:63) at java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1838) at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(ObjectOutputStream.java:1747) at java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:1249) at java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1203) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1387) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) at java.io.ObjectOutputStream.writeFatalException(ObjectOutputStream.java:1538) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:329) at hudson.remoting.Command.writeTo(Command.java:81) at hudson.remoting.ClassicCommandTransport.write(ClassicCommandTransport.java:41) at hudson.remoting.Channel.send(Channel.java:496) : Due Date: 28/Jan/13 12:00 AM Environment: production Project: Jenkins Priority: Major Reporter: Anup T S This message is automatically generated by JIRA. If you think it was sent incorrectly,
[JIRA] (JENKINS-16165) Configure screen stuck in LOADING state
Brian Preuß edited a comment on JENKINS-16165 Configure screen stuck in LOADING state Same bug with Jenkins 1.500, ClearCase Plugin 1.3.13 and without Email-ext-plugin Firefox 18.0.1 shows this error in the _javascript_ console: Zeitstempel: 28.01.2013 12:59:05 Fehler: TypeError: $(...) is undefined Quelldatei: https://hostname:port/path/adjuncts/89bcf893/lib/form/radioBlock/radioBlock.js Zeile: 53 Downgrading to ClearCase Plugin 1.3.12 resolved this issue for us. 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] (JENKINS-16505) Adding a plugin mixing authentication via proxy and ldap permissions
Dominique Arnou created JENKINS-16505 Adding a plugin mixing authentication via proxy and ldap permissions Issue Type: New Feature Affects Versions: current Assignee: Kohsuke Kawaguchi Components: active-directory, ldap, reverse-proxy-auth Created: 28/Jan/13 2:11 PM Description: In the Global Security panel, I would like to select the authentication via HTTP Header by reverse proxy while maintaining authorizations via ldap groups. To do this, the connection properties to ldap should be filled regardless of the authentication module or authorization module chosen Project: Jenkins Priority: Major Reporter: Dominique Arnou 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16499) NPE when new job by copy from existing one
Pei-Tang Huang commented on JENKINS-16499 NPE when new job by copy from existing one @stefanbrausch: I think the version of JobConfigHistory is irrelevant. You can try the steps in the first comment to test if you can reproduce this problem without any plugins installed. 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16488) doNotifyCommit fails after update to 1.45
Jan Klass edited a comment on JENKINS-16488 doNotifyCommit fails after update to 1.45 After working through some job and jenkins settings, and today updating to Jenkins 1.50 the doNotifyCommit commithooks work again with the subversion plugin 1.45. 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15583) building builds (running builds) do not show up anymore in the list of builds of a job (json API)
janick reynders commented on JENKINS-15583 building builds (running builds) do not show up anymore in the list of builds of a job (json API) @pedro "lastBuild" just returns the last build. If you run multiple builds of the same job concurrently, then "allBuilds" is the only property that contains all the running builds (in addition to the builds from "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] (JENKINS-16506) Incorrect build links on Multijob build summary page
William Roberts created JENKINS-16506 Incorrect build links on Multijob build summary page Issue Type: Bug Assignee: Unassigned Components: jenkins-multijob-plugin Created: 28/Jan/13 2:38 PM Description: My Jenkins is configured to use "http://myhost:2020/jenkins" as the Jenkins URL. This setting is respected in most places in the MultiJob plugin, e.g. the top-level view of the job has the correct links to the individual jobs in each phase. However, in the main view of each complete build of the multijob, e.g. http://myhost:2020/jenkins/job/nightly-EFS-sequence/11/ the links to the builds of the individual jobs are wrong. e.g. EFS distribution nightly-EFS-dist-to-Dev build #11 ( 44 min ) has the "build #11" link set to http://myhost:2020/job/nightly-EFS-dist-to-Dev/11/ Environment: Jenkins Multijob plugin version 1.7, running in Jenkins 1.480.1 Project: Jenkins Priority: Minor Reporter: William Roberts 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16492) Upgrade from 0.12 to 0.13 breaks server
Juan Basso updated JENKINS-16492 Upgrade from 0.12 to 0.13 breaks server I am having the same issue. I can't access the jenkins web interface at all. Change By: Juan Basso (28/Jan/13 2:56 PM) 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16492) Upgrade from 0.12 to 0.13 breaks server
James Smith commented on JENKINS-16492 Upgrade from 0.12 to 0.13 breaks server Same here - I've just set up the github oauth plugin on a new server, and am having exactly the same error after github login. 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] (JENKINS-15583) building builds (running builds) do not show up anymore in the list of builds of a job (json API)
pedro reis commented on JENKINS-15583 building builds (running builds) do not show up anymore in the list of builds of a job (json API) @janick In python I don't see any "allBuilds". There is only: builds, firstBuild, lastBuild, lastCompletedBuild, lastFailedBuild, lastStableBuild, lastSuccessfulBuild, lastUnstableBuild, lastUnsuccessfulBuild, 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16507) Add ability to restart job from the step that failed
Ken Sherrill created JENKINS-16507 Add ability to restart job from the step that failed Issue Type: New Feature Assignee: Unassigned Components: core Created: 28/Jan/13 3:16 PM Description: We are using Jenkins Enterprise as our build server. We'd like to be able to restart a failed job from the build step that failed, rather than having to run the entire job from the beginning. This would save many hours of rebuilding, especially in cases where multiple jobs are in a pipeline. Environment: Jenkins ver. 1.466.1 Project: Jenkins Priority: Major Reporter: Ken Sherrill 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] (JENKINS-16508) Performance Plugin: HTTP Status Code Sometimes '0' In Performance Samples Table
Michael Nyika created JENKINS-16508 Performance Plugin: HTTP Status Code Sometimes 0 In Performance Samples Table Issue Type: Bug Assignee: Manuel Carrasco Attachments: http_status_code_zero.jpg Components: performance-plugin Created: 28/Jan/13 3:22 PM Description: Sometimes the HTTP Status Code Column, in the 'Performance Samples' table, indicates a value of Zero (0). Other values are legitimate HTTP status codes, such as 200, 500, 503, etc. Could it be that the response was not large enough to contain the response code header valueor there was just a problem reading the response and interpreting it? If so, then i would understand the value '0'. If this is not the case, perhaps a fix of some kind is needed. I have attached a screenshot if it helps. Environment: Linux (CentOS, Jenkins 1.481, Performance Plugin v1.8 Project: Jenkins Labels: plugin jenkins exception status http code Priority: Minor Reporter: Michael Nyika 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] (JENKINS-15583) building builds (running builds) do not show up anymore in the list of builds of a job (json API)
janick reynders commented on JENKINS-15583 building builds (running builds) do not show up anymore in the list of builds of a job (json API) yes it's a hidden property: it will be returned if you ask for it explicitly (using the "tree" query parameter: see "Controlling the amount of data you fetch") 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] (JENKINS-16368) Hardcoded protocol in some links
Jesse Glick commented on JENKINS-16368 Hardcoded protocol in some links @kutzi I think you mean just simple absolute URIs like /computer/slaveXYZ; a network-path reference would be to a different server using the same protocol (//elsewhere.net/something), which is not needed for anything in Jenkins AFAIK. 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] (JENKINS-15583) building builds (running builds) do not show up anymore in the list of builds of a job (json API)
Jesse Glick commented on JENKINS-15583 building builds (running builds) do not show up anymore in the list of builds of a job (json API) This is still an apparent regression and needs to be fixed, not worked around in clients. 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] (JENKINS-16089) Standard view columns interact force builds to be eagerly loaded
Jesse Glick assigned JENKINS-16089 to Justin Santa Barbara Standard view columns interact force builds to be eagerly loaded Change By: Jesse Glick (28/Jan/13 4:52 PM) Assignee: JesseGlick JustinSantaBarbara 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16491) Changes since last successfull build Plugin - View Detail links are broken
Jesse Glick updated JENKINS-16491 Changes since last successfull build Plugin - View Detail links are broken Change By: Jesse Glick (28/Jan/13 5:29 PM) Assignee: NicolasDeLoof Component/s: changes-since-last-success Component/s: 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] (JENKINS-16509) Allow more concurrent polling actions
James Westby created JENKINS-16509 Allow more concurrent polling actions Issue Type: Bug Assignee: Gregory Boissinot Components: scripttrigger Created: 28/Jan/13 5:29 PM Description: Hi, We're using ScriptTrigger and are finding it a great addition to Jenkins, thanks for working on it. We've recently added a lot more jobs using ScriptTrigger, and have run in to a concurrency limitation. Each job runs a script that takes a few seconds, and we'd like to poll very frequently. However, we're finding that there's a limit to the number of jobs that we can have in this configuration as only one script is run at a time (despite the fact that we have many slaves to run the scripts) I have two suggestions for improvements here: 1. Implement equals() on the Runnable objects so that the jenkins queue will drop duplicate jobs from the queue. This won't allow more to be run, but it will stop the queue from overflowing if the rate of jobs is greater than the single executor can handle. 2. Allow for configuration of the allowed concurrency, the same way the built-in SCM trigger does (https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/triggers/SCMTrigger.java#L224). Then we could increase the concurrency to match the number of slaves and poll a lot more frequently. Thanks, James Project: Jenkins Priority: Major Reporter: James Westby 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] (JENKINS-16368) Hardcoded protocol in some links
kutzi commented on JENKINS-16368 Hardcoded protocol in some links Actually, I was thinking about network-path reference as this bug - as I understand it - is that in some places Jenkins#getRootUrl() is used to construct intra-Jenkins links. Indeed, using absolute URIs in this case would be the even better solution. I find it quite strange that the value of getRootUrl doesn't always return the same - configured - value, but based on the 'current' protocol something different. But that was already so before this fix, so it doesn't actually worsen the situation. 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] (JENKINS-16368) Hardcoded protocol in some links
kutzi edited a comment on JENKINS-16368 Hardcoded protocol in some links Actually, I was thinking about network-path reference as this bug - as I understand it - is that in some places Jenkins#getRootUrl() is used to construct intra-Jenkins links. Indeed, using absolute URIs in this case would be the even better solution. I find it quite strange that the value of getRootUrl doesn't always return the same - configured - value, but based on the 'current' request something different. But that was already so before this fix, so it doesn't actually worsen the situation. 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16368) Hardcoded protocol in some links
kutzi commented on JENKINS-16368 Hardcoded protocol in some links Looking at it again, it actually does worsen the situation, as previously I was either getting the configured value or getRootUrlFromRequest() - which is also (kind of) mentioned in the Javadoc. Now I have 3 different return values, based on the context. 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] (JENKINS-11669) Parameterized trigger from a multi-configuration project triggers downstream jobs twice
cjo9900 commented on JENKINS-11669 Parameterized trigger from a multi-configuration project triggers downstream jobs twice Tracked this down to the fact that hudson.Tasks.BuildTrigger.execute() is called from AbstractBuild.cleanup() and from the Parameterizedtrigger.BuildTrigger.MatrixAggregator.endbuild(). This seemed to be caused by commit on jenkins back in 2010-11-05 https://github.com/jenkinsci/jenkins/commit/1d6ef2063eebaba39973c6dd56343e1912611db7 and the change to the parameterized trigger added before it in 2010-07-01 https://github.com/jenkinsci/parameterized-trigger-plugin/commit/3c302ccf324de5eadf5b244d2ef1ee1a78caf0d7 So to fix this issue the parameterized trigger plugin should not create the MatrixAggregator, if the version of jenkins is newer than 1.387 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] (JENKINS-16510) NPE on Maven3 Project - after Upgrading from 1.489 to 1.500
Jan Mederer created JENKINS-16510 NPE on Maven3 Project - after Upgrading from 1.489 to 1.500 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: maven Created: 28/Jan/13 6:16 PM Description: After upgrading Jenkins from Version 1.489 to 1.500 with reindexing, all the Maven3 Project doesnt work anymore. The same Build in the Freestyle Jobs works fine, but theres no possibility to run maven-release. Heres the error: 18:59:40 [JENKINS] Archiving disabled 18:59:41 Warte bis Jenkins die Datensammlung abgeschlossen hat 18:59:41 mavenExecutionResult exceptions not empty 18:59:41 message : Internal error: java.lang.NullPointerException 18:59:41 cause : null 18:59:41 Stack trace : 18:59:41 org.apache.maven.InternalErrorException: Internal error: java.lang.NullPointerException 18:59:41 at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128) 18:59:41 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95) 18:59:41 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) 18:59:41 at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) 18:59:41 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) 18:59:41 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) 18:59:41 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) 18:59:41 at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) 18:59:41 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 18:59:41 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 18:59:41 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 18:59:41 at java.lang.reflect.Method.invoke(Method.java:597) 18:59:41 at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) 18:59:41 at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) 18:59:41 at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158) 18:59:41 at hudson.maven.Maven3Builder.call(Maven3Builder.java:100) 18:59:41 at hudson.maven.Maven3Builder.call(Maven3Builder.java:66) 18:59:41 at hudson.remoting.UserRequest.perform(UserRequest.java:118) 18:59:41 at hudson.remoting.UserRequest.perform(UserRequest.java:48) 18:59:41 at hudson.remoting.Request$2.run(Request.java:326) 18:59:41 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 18:59:41 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) 18:59:41 at java.util.concurrent.FutureTask.run(FutureTask.java:138) 18:59:41 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 18:59:41 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 18:59:41 at java.lang.Thread.run(Thread.java:662) 18:59:41 Caused by: java.lang.NullPointerException 18:59:41 at hudson.maven.reporters.TestMojo.getReportFiles(TestMojo.java:104) 18:59:41 at hudson.maven.reporters.SurefireArchiver.postExecute(SurefireArchiver.java:125) 18:59:41 at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:443) 18:59:41 at hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:425) 18:59:41 at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87) 18:59:41 at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42) 18:59:41 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:228) 18:59:41 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) 18:59:41 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) 18:59:41 at
[JIRA] (JENKINS-16492) Upgrade from 0.12 to 0.13 breaks server
Kevin Bond commented on JENKINS-16492 Upgrade from 0.12 to 0.13 breaks server Also having this issue, how can I revert the 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] (JENKINS-11669) Parameterized trigger from a multi-configuration project triggers downstream jobs twice
cjo9900 assigned JENKINS-11669 to cjo9900 Parameterized trigger from a multi-configuration project triggers downstream jobs twice Change By: cjo9900 (28/Jan/13 6:30 PM) Assignee: huybrechts cjo9900 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] (JENKINS-11669) Parameterized trigger from a multi-configuration project triggers downstream jobs twice
cjo9900 started work on JENKINS-11669 Parameterized trigger from a multi-configuration project triggers downstream jobs twice Change By: cjo9900 (28/Jan/13 6:30 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] (JENKINS-16492) Upgrade from 0.12 to 0.13 breaks server
Juan Basso commented on JENKINS-16492 Upgrade from 0.12 to 0.13 breaks server You can disable the authentication in the config, restart and re-configure to another auth system until the it get fixed. To disable the authentication, go in the box, jenkins folder, edit the jenkins.xml. Change the key "useSecurity" to false, and delete the key "authorizationStrategy" completely. Restart the jenkins and all users will be administrator, so go in manage and setup wherever you want, except github oauth Btw, don't forget to backup your configuration file (jenkins.xml) before change 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-11669) Parameterized trigger from a multi-configuration project triggers downstream jobs twice
cjo9900 commented on JENKINS-11669 Parameterized trigger from a multi-configuration project triggers downstream jobs twice Pull request https://github.com/jenkinsci/parameterized-trigger-plugin/pull/33 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] (JENKINS-16368) Hardcoded protocol in some links
Jesse Glick
reopened JENKINS-16368
Hardcoded protocol in some links
The Javadoc could be edited, but I think it is necessary to reconsider the fix, which is just a workaround for missing logic in ConsoleNote.
My understanding of the bug is that we are talking about links within a single Jenkins master. E.g. https://server/job/stuff/1/console should link to https://computer/someslave not http://computer/someslave even if Jenkins “thinks” it is running as http://computer/. Therefore the link must be a complete URL, so hacking Jenkins.rootUrl is necessary (or the Jenkins admin needs to set the root URL to https://computer/ and accept HTTP - HTTPS redirection as being the lesser evil).
The issue here is that AbstractBuildExecution.run calls ModelHyperlinkNote.encodeTo("/computer/someslave", …), and HyperlinkNote.annotate translates /computer/someslave to http://server/computer/someslave (before the current fix). It does this because it has no other way of determining an absolute URI: you could be running Jenkins with a web app context path like http://computer/ci/, or you could be running Jenkins behind a reverse proxy that maps http://localhost:8080/ to http://mycorp.com/ci/, etc., so /computer/someslave cannot be guaranteed to resolve to anything useful. Nor can //computer/someslave, so network-path references are irrelevant.
The best fix (IMO) would be to produce a relative URI, ../../../computer/someslave in this case, which will not only preserve scheme but would work correctly even in the face of an incorrect Jenkins.rootUrl setting. The difficulty is that HyperlinkNote.annotate now needs to take its Object context and determine its URL relative to the context root; and there seems to be no standard interface for this. For example, Run.getUrl does not implement any method. Perhaps such an interface could be introduced retroactively, in which case contexts assignable to this interface could result in relative URIs (with absolute URLs being used as a fallback).
Change By:
Jesse Glick
(28/Jan/13 6:51 PM)
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, send email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16368) Hardcoded protocol in some links
kutzi edited a comment on JENKINS-16368 Hardcoded protocol in some links We could have a new method in Jenkins which returns the rootUrl without protocol, so ModelHyperlinkNote could use absolute URIs, like you mentioned. Or am I misunderstanding the issue? Forget it. I think you already answered this with the proxy example. 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16368) Hardcoded protocol in some links
kutzi commented on JENKINS-16368 Hardcoded protocol in some links Agree that this seems like a workaround. Moreover the fix doesn't seem to be complete as HTTPS might terminate in the reverse proxy, so Stapler.getCurrentRequest().getScheme() would return 'http' So the only 'correct' way to operate Jenkins under https seems to simply configure the rootUrl to start with https. Otherwise it's IMO simply a configuration error. 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] (JENKINS-16495) Saving global settings causes cross site request forgery option to be disabled
Jesse Glick updated JENKINS-16495 Saving global settings causes cross site request forgery option to be disabled @domi/@imod (confusing!), this is a regression from https://github.com/jenkinsci/jenkins/pull/628 I guess? Change By: Jesse Glick (28/Jan/13 7:12 PM) Priority: Minor Major 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16511) Jenkins Behind Proxy Sends JNLP Agent Incorrect URL
John Cook
created JENKINS-16511
Jenkins Behind Proxy Sends JNLP Agent Incorrect URL
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Attachments:
http-dump.txt
Components:
master-slave
Created:
28/Jan/13 7:14 PM
Description:
Once I upgraded to Jenkins 1.5, my slave agent ("mac-mini") could no longer connect. Here's an example session (I changed the hostname and credentials to protect the guilty):
$ java -jar ./slave.jar -jnlpCredentials myuser:mypassword -jnlpUrl https://ci.mydomain.com/jenkins/computer/mac-mini/slave-agent.jnlp -noCertificateCheck
Skipping HTTPS certificate checks altoghether. Note that this is not secure at all.
Jan 28, 2013 1:45:43 PM hudson.remoting.jnlp.Main$CuiListener init
INFO: Hudson agent is running in headless mode.
Jan 28, 2013 1:45:43 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Locating server among http://ci.mydomain.com/jenkins/, http://127.0.0.1:8080/jenkins/
Jan 28, 2013 1:45:43 PM hudson.remoting.jnlp.Main$CuiListener error
SEVERE: http://ci.mydomain.com/jenkins/tcpSlaveAgentListener/ is invalid: 301 Moved Permanently
java.lang.Exception: http://ci.mydomain.com/jenkins/tcpSlaveAgentListener/ is invalid: 301 Moved Permanently
at hudson.remoting.Engine.run(Engine.java:168)
I then used Charles Proxy to capture the HTTP traffic to see what was going on. I've attached a file of that capture, but the relevant problem is here:
argument-url/argumentargumenthttp://ci.mydomain.com/jenkins//argument
The problem is that the slave is being told to connect via HTTP, but (thanks to our proxy) it is only available via HTTPS. I checked my configuration and it is correct. I believe the issue is caused by this change on January 15th: https://github.com/jenkinsci/jenkins/commit/460e508155187918e8c0f4fd0bb66a99cfe78527#L0R1877 . The protocol of the request as far as Jenkins knows is HTTP. However the client needs to use the HTTPS protocol I configured for our root URL.
Environment:
Jenkins on port 8080, Apache proxy for SSL connections.
Project:
Jenkins
Labels:
slave
proxy
url
Priority:
Blocker
Reporter:
John Cook
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] (JENKINS-16511) Jenkins Behind Proxy Sends JNLP Agent Incorrect URL
John Cook
updated JENKINS-16511
Jenkins Behind Proxy Sends JNLP Agent Incorrect URL
Change By:
John Cook
(28/Jan/13 7:17 PM)
Description:
OnceIupgradedtoJenkins1.5,myslaveagent(mac-mini)couldnolongerconnect.Heresanexamplesession(Ichangedthehostnameandcredentialstoprotecttheguilty):
{code}
$java-jar./slave.jar-jnlpCredentialsmyuser:mypassword-jnlpUrlhttps://ci.mydomain.com/jenkins/computer/mac-mini/slave-agent.jnlp-noCertificateCheckSkippingHTTPScertificatechecksaltoghether.Notethatthisisnotsecureatall.Jan28,20131:45:43PMhudson.remoting.jnlp.Main$CuiListenerinitINFO:Hudsonagentisrunninginheadlessmode.Jan28,20131:45:43PMhudson.remoting.jnlp.Main$CuiListenerstatusINFO:Locatingserveramong[http://ci.mydomain.com/jenkins/,http://127.0.0.1:8080/jenkins/]Jan28,20131:45:43PMhudson.remoting.jnlp.Main$CuiListenererrorSEVERE:http://ci.mydomain.com/jenkins/tcpSlaveAgentListener/isinvalid:301MovedPermanentlyjava.lang.Exception:http://ci.mydomain.com/jenkins/tcpSlaveAgentListener/isinvalid:301MovedPermanently athudson.remoting.Engine.run(Engine.java:168)
{code}
IthenusedCharlesProxytocapturetheHTTPtraffictoseewhatwasgoingon.Iveattachedafileofthatcapture,buttherelevantproblemishere:
{code}
argument-url/argumentargumenthttp://ci.mydomain.com/jenkins//argument
{code}
TheproblemisthattheslaveisbeingtoldtoconnectviaHTTP,but(thankstoourproxy)itisonlyavailableviaHTTPS.Icheckedmyconfigurationanditiscorrect.Ibelievetheissueiscausedby
[
thischangeonJanuary15th
:
|
https://github.com/jenkinsci/jenkins/commit/460e508155187918e8c0f4fd0bb66a99cfe78527#L0R1877
]
.TheprotocoloftherequestasfarasJenkinsknowsisHTTP.HowevertheclientneedstousetheHTTPSprotocolIconfiguredforourrootURL.
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] (JENKINS-16482) SSH slave connection issues after Jenkins update
Jesse Glick updated JENKINS-16482 SSH slave connection issues after Jenkins update Change By: Jesse Glick (28/Jan/13 7:18 PM) Component/s: smart-jenkins Component/s: master-slave Component/s: ssh-slaves Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16482) SSH slave connection issues after Jenkins update
Jesse Glick assigned JENKINS-16482 to Yi Hu SSH slave connection issues after Jenkins update Change By: Jesse Glick (28/Jan/13 7:19 PM) Assignee: KohsukeKawaguchi YiHu 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] (JENKINS-16511) Jenkins Behind Proxy Sends JNLP Agent Incorrect URL
John Cook
updated JENKINS-16511
Jenkins Behind Proxy Sends JNLP Agent Incorrect URL
Change By:
John Cook
(28/Jan/13 7:21 PM)
Description:
OnceIupgradedtoJenkins1.5,myslaveagent(mac-mini)couldnolongerconnect.Heresanexamplesession(Ichangedthehostnameandcredentialstoprotecttheguilty):{code}$java-jar./slave.jar-jnlpCredentialsmyuser:mypassword-jnlpUrlhttps://ci.mydomain.com/jenkins/computer/mac-mini/slave-agent.jnlp-noCertificateCheckSkippingHTTPScertificatechecksaltoghether.Notethatthisisnotsecureatall.Jan28,20131:45:43PMhudson.remoting.jnlp.Main$CuiListenerinitINFO:Hudsonagentisrunninginheadlessmode.Jan28,20131:45:43PMhudson.remoting.jnlp.Main$CuiListenerstatusINFO:Locatingserveramong[http://ci.mydomain.com/jenkins/,http://127.0.0.1:8080/jenkins/]Jan28,20131:45:43PMhudson.remoting.jnlp.Main$CuiListenererrorSEVERE:http://ci.mydomain.com/jenkins/tcpSlaveAgentListener/isinvalid:301MovedPermanentlyjava.lang.Exception:http://ci.mydomain.com/jenkins/tcpSlaveAgentListener/isinvalid:301MovedPermanently athudson.remoting.Engine.run(Engine.java:168){code}IthenusedCharlesProxytocapturetheHTTPtraffictoseewhatwasgoingon.Iveattachedafileofthatcapture,buttherelevantproblemishere:{code:xml}argument-url/argumentargumenthttp://ci.mydomain.com/jenkins//argument{code}TheproblemisthattheslaveisbeingtoldtoconnectviaHTTP,but(thankstoourproxy)
it
Jenkins
isonlyavailableviaHTTPS.Icheckedmyconfigurationanditiscorrect.Ibelievetheissueiscausedby[thischangeonJanuary15th|https://github.com/jenkinsci/jenkins/commit/460e508155187918e8c0f4fd0bb66a99cfe78527#L0R1877].Theprotocoloftherequest
asfaras
fromApacheto
Jenkins
knows
*
is
*
HTTP
.However
,however
theclient
needsto
must
use
the
HTTPS
protocol
as
Iconfigured
for
ourrootURL.
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] (JENKINS-16511) Jenkins behind a proxy sends JNLP agents incorrect URL
John Cook updated JENKINS-16511 Jenkins behind a proxy sends JNLP agents incorrect URL Change By: John Cook (28/Jan/13 7:22 PM) Summary: Jenkins BehindProxySends behindaproxysends JNLP AgentIncorrect agentsincorrect URL 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] (JENKINS-16368) Hardcoded protocol in some links
John Cook commented on JENKINS-16368 Hardcoded protocol in some links Oh wow, as I was writing my HTTPS proxy bug report, you guys were talking about this very thing! 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] (JENKINS-16368) Hardcoded protocol in some links
Jesse Glick commented on JENKINS-16368 Hardcoded protocol in some links OK, that is a serious regression so I am going to back out the change immediately, pending a better solution (or clearer description of the tradeoffs of the current solution). 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] (JENKINS-16511) Jenkins behind a proxy sends JNLP agents incorrect URL
Jesse Glick resolved JENKINS-16511 as Duplicate Jenkins behind a proxy sends JNLP agents incorrect URL Change By: Jesse Glick (28/Jan/13 7:36 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16368) Hardcoded protocol in some links
SCM/JIRA link daemon commented on JENKINS-16368 Hardcoded protocol in some links Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/jenkins/model/Jenkins.java core/src/test/java/jenkins/model/JenkinsGetRootUrlTest.java http://jenkins-ci.org/commit/jenkins/40dcfcb18178aa1cd2e73688492b4c4578be6968 Log: JENKINS-16368 Reverted faulty fix. You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group, send email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. 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] (JENKINS-16512) v1.3.x perforce plugin doesn't work with the latest perforce 2012.2
Sherrie Ma created JENKINS-16512 v1.3.x perforce plugin doesnt work with the latest perforce 2012.2 Issue Type: Bug Assignee: Rob Petti Components: perforce Created: 28/Jan/13 8:01 PM Description: We’ve upgraded our perforce from 2012.1 to 2012.2, which supports ssl. But with the new version, the perforce plugin is having problem before the sync. It’s trying to run “p4 where” command at // level, instead of the changelist. This was a fixed bug back in 2011 in v1.2.9, which worked with the latest 2012.2. However, the newer 1.3.x won’t work. 1.3.x work fine with perforce 2012.1 with no problem. Upgraded to the latest jenkins, but no difference. copying a segment of the log: === Started by user admin Building remotely on blinnv12g in workspace /scratch/linux86/jks/perforce_test2/dev Using remote perforce client: jkspilot2_p4-161040911 dev $ /usr/local/bin/p4 workspace -o jkspilot2_p4-161040911 dev $ /usr/local/bin/p4 login -p dev $ /usr/local/bin/p4 -P 6BD4xxx workspace -o jkspilot2_p4-161040911 Last build changeset: 277259 dev $ /usr/local/bin/p4 -P 6BD4xxx counter change dev $ /usr/local/bin/p4 -P 6BD4xxx -s changes //jkspilot2_p4-161040911/...@277260,@277278 dev $ /usr/local/bin/p4 -P 6BD4xxx describe -s 277277 dev $ /usr/local/bin/p4 -P 6BD4xxx -G where //... Caught exception communicating with perforce. P4 Where Parsing Error: Some commands just want to watch the database churn. com.tek42.perforce.PerforceException: P4 Where Parsing Error: Some commands just want to watch the database churn. at hudson.plugins.perforce.PerforceSCMHelper.parseWhereMapping(PerforceSCMHelper.java:159) at com.tek42.perforce.parse.Changes.calculateWorkspacePaths(Changes.java:82) at com.tek42.perforce.parse.Changes.getChangelist(Changes.java:71) at com.tek42.perforce.parse.Changes.getChangelistsFromNumbers(Changes.java:425) at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:662) at hudson.model.AbstractProject.checkout(AbstractProject.java:1325) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:682) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:587) at hudson.model.Run.execute(Run.java:1543) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) ERROR: Unable to communicate with perforce. P4 Where Parsing Error: Some commands just want to watch the database churn. Email was triggered for: Failure Sending email for trigger: Failure Sending email to: s...@xxx.com Finished: FAILURE === Project: Jenkins Priority: Major Reporter: Sherrie Ma 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16368) Hardcoded protocol in some links
Oliver Gondža commented on JENKINS-16368 Hardcoded protocol in some links I agree, it's a regression. As far as I can say the root url is sent via mail or rss, so I think relative urls wont do. 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] (JENKINS-16512) v1.3.x perforce plugin doesn't work with the latest perforce 2012.2
Rob Petti commented on JENKINS-16512 v1.3.x perforce plugin doesnt work with the latest perforce 2012.2 Where command has always been executed at that level, and will only ever return the DepotViewWorkspace map. This is a very low intensity command that simply generates a more useful version of your view. I invite you to try it for yourself. The issue is that your perforce server or client is returning an error with junk data: "Some commands just want to watch the database churn." I'm assuming this is part of some trigger that you or your administrators have added. You will need to remove 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16512) v1.3.x perforce plugin doesn't work with the latest perforce 2012.2
Rob Petti edited a comment on JENKINS-16512 v1.3.x perforce plugin doesnt work with the latest perforce 2012.2 Where command has always been executed at that level, and will only ever return the DepotViewWorkspace map. This is a very low intensity command that simply generates a more useful version of your view. I invite you to try it for yourself. The issue is that your perforce server or client is returning an error with junk data: "Some commands just want to watch the database churn." I'm assuming this is part of some trigger that you or your administrators have added. You will need to remove 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16512) v1.3.x perforce plugin doesn't work with the latest perforce 2012.2
Sherrie Ma commented on JENKINS-16512 v1.3.x perforce plugin doesnt work with the latest perforce 2012.2 Thanks, Rob. I've tried to use a lower version of this perforce plugin v1.2.9. It won't give this error. Particularly, when using v1.2.9, the "p4 -G where" command right before the error is like this: === dev $ /usr/local/bin/p4 -P 6BD4xxx -s sync //jenkinspilot2_test_p4-161040911/...@362136 === , instead of: === dev $ /usr/local/bin/p4 -P 6BD4xxx -s sync //... === I find this very similar to a bug related to p4 where parsing that was fixed in v1.2.9, and it's indeed a working version for us. And if the breakage was caused by a trigger that worked with 2012.1 but wouldn't work with 2012.2, any suggestion of how to identify it? Thanks! 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] (JENKINS-16494) Jenkins Grails Plugin 1.6.3 does not install a runtime correctly
Jesse Glick resolved JENKINS-16494 as Cannot Reproduce Jenkins Grails Plugin 1.6.3 does not install a runtime correctly Testing against OSS Jenkins I get a dropdown for Version from 2.2.0 downward, as http://updates.jenkins-ci.org/updates/com.g2one.hudson.grails.GrailsInstaller.json supplies; when used, http://dist.springframework.org.s3.amazonaws.com/release/GRAILS/grails-2.2.0.zip is unpacked and run as expected. Same when running against Jenkins Enterprise 1.466.12.1. You should have seen in your log file, sometime after installing the plugin: …date… hudson.model.DownloadService$Downloadable doPostBack INFO: Obtained the updated data file for com.g2one.hudson.grails.GrailsInstaller As for the generic installation from URL, delete the Label (you misinterpret it; see inline help); and you must set grails-2.1.1 in the Subdirectory of extracted archive field. With those changes, the generic installation works for me too. While inspecting the code I found some erroneous logic which I have submitted a fix for in https://github.com/jenkinsci/grails-plugin/pull/4 but I do not see any obvious reason why the bad code would have led to the symptoms you describe. Change By: Jesse Glick (28/Jan/13 8:51 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16368) Hardcoded protocol in some links
dogfood commented on JENKINS-16368 Hardcoded protocol in some links Integrated in jenkins_main_trunk #2224 JENKINS-16368 Reverted faulty fix. (Revision 40dcfcb18178aa1cd2e73688492b4c4578be6968) Result = SUCCESS Jesse Glick : 40dcfcb18178aa1cd2e73688492b4c4578be6968 Files : changelog.html core/src/test/java/jenkins/model/JenkinsGetRootUrlTest.java core/src/main/java/jenkins/model/Jenkins.java 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16431) the projects not order by my order of input
cjo9900 resolved JENKINS-16431 as Not A Defect the projects not order by my order of input Change By: cjo9900 (28/Jan/13 9:03 PM) Status: Open Resolved Assignee: huybrechts cjo9900 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] (JENKINS-16431) the projects not order by my order of input
cjo9900 commented on JENKINS-16431 the projects not order by my order of input Ordering of the dependencies when triggering downstream is done in the Build trigger (part of core not parametrised trigger plugin) And as such does not treat any Downstream job in preference to another unless multiple downstream jobs are also linked, so that a which are triggered by multiple jobs run later. i.e. A triggers B and C B triggers C In this case A would trigger B first as C could be triggered from B also. See code @ https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/tasks/BuildTrigger.java#L199 If you want jobs to run in priority order i.e. C first then B, have a look at the Priority Sorter Plugin which can cause jobs to run in a preference order when there is limited executors. https://wiki.jenkins-ci.org/display/JENKINS/Priority+Sorter+Plugin Closing this as this is not a bug and is core functionality that expects all jobs to be equal. 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] (JENKINS-10147) Add 'poll SCM' option to build step
cjo9900 commented on JENKINS-10147 Add poll SCM option to build step As this has popped to the top of the list and I am trying to look at all of these issues, I can see that this issue could be resolved when the Run condition branch is added. In this case you could create a run condition that could poll a project for changes before triggering other builds, and this then keeps the changes needed seperate from this plugin. As in most cases this is not a requirement for triggering a downstream build. 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] (JENKINS-10147) Add 'poll SCM' option to build step
cjo9900 edited a comment on JENKINS-10147 Add poll SCM option to build step As this has popped to the top of the list and I am trying to look at all of these issues, I can see that this issue could be resolved when the Run condition branch is added. In this case you could create a run condition that could poll a project for changes before triggering other builds, and this then keeps the changes needed separate from this plugin. As in most cases this is not a requirement for triggering a downstream build. Note: I have requested reviews on the pending pull requests, and will look at getting a new release done soon. 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16368) Hardcoded protocol in some links
Jesse Glick commented on JENKINS-16368 Hardcoded protocol in some links The root URL is indeed used in some mail messages, RSS, etc., but this is a different use case from what was originally filed—these cases are not using ConsoleAnnotator, and there is in general no current Stapler request anyway. (Maybe for RSS, definitely not for mail.) For such miscellaneous cases, where Jenkins must of necessity emit a complete URL, the administrator must configure the Jenkins root URL manually. The question is whether in generated pages containing internal links, especially console logs, we can use relative URLs to ensure that the link targets are correct even if the Jenkins root URL was not correctly configured. 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16512) v1.3.x perforce plugin doesn't work with the latest perforce 2012.2
Rob Petti commented on JENKINS-16512 v1.3.x perforce plugin doesnt work with the latest perforce 2012.2 That's a 'sync' command, not a 'where' command. The reason 1.2.9 works for you is because that version does not try to obtain the 'where' map. Ask your perforce administrators if they have any triggers that contain the phrase: "Some commands just want to watch the database churn." I have downloaded 2012.2, and have confirmed that this is NOT an error built-in to perforce, which means your admins are doing something to intentionally block certain commands. 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16368) Hardcoded protocol in some links
kutzi commented on JENKINS-16368 Hardcoded protocol in some links I'd argue that the root URL must always be configured correctly. There's already a big warning on the global config page if you don't. Maybe we can still improve the documentation a bit to make the situation clearer for users. And then I'd close this a not-a-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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16513) Duplicate builds being triggered upon github merges.
Miles Georgi created JENKINS-16513 Duplicate builds being triggered upon github merges. Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: github Created: 28/Jan/13 10:38 PM Description: Hi there, we're seeing some strange behavior that might be a bug in this plugin. Merges performed on github are triggering two builds it seems instead of one. One thing that is odd is that often the push is attributed to a user that did not perform the merge nor did they contribute any commits to the branch. I'm sure this probably isn't enough information to reproduce this bug locally, and the project this is happening in is closed source. Sorry about that. I have turned on some additional logging. Please let me know what information I can provide to assist. Project: Jenkins Priority: Major Reporter: Miles Georgi 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] (JENKINS-3265) Reload Configuration from Disk (or POSTing config.xml) loses info on running builds
Kevin Scaldeferri commented on JENKINS-3265 Reload Configuration from Disk (or POSTing config.xml) loses info on running builds We are running 1.479 and I still see this bug. I'd like to suggest that it should be 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16495) Saving global settings causes cross site request forgery option to be disabled
domi commented on JENKINS-16495 Saving global settings causes cross site request forgery option to be disabled I'll have a look at ist after my vacations - Sorry that will march earliest 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16495) Saving global settings causes cross site request forgery option to be disabled
Youssuf ElKalay commented on JENKINS-16495 Saving global settings causes cross site request forgery option to be disabled I don't mind taking a stab at a bug fix if someone could direct me where in the code to look. The object model is a little tough to navigate. 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] (JENKINS-3265) Reload Configuration from Disk (or POSTing config.xml) loses info on running builds
Jesse Glick commented on JENKINS-3265 Reload Configuration from Disk (or POSTing config.xml) loses info on running builds @kscaldef best to have a fully reproducible test case, ideally based on a trunk version. 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] (JENKINS-16495) Saving global settings causes cross site request forgery option to be disabled
Jesse Glick commented on JENKINS-16495 Saving global settings causes cross site request forgery option to be disabled @buildscientist: core/src/main/java/hudson/security/csrf/GlobalCrumbIssuerConfiguration.java and core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/config.groovy and core/src/main/java/jenkins/model/Jenkins.java 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] (JENKINS-14387) Cause of rebuilt job should be Cause.UserIdCause
SCM/JIRA link daemon commented on JENKINS-14387 Cause of rebuilt job should be Cause.UserIdCause Code changed in jenkins User: rinokadijk Path: src/main/java/com/sonyericsson/rebuild/RebuildAction.java src/main/java/com/sonyericsson/rebuild/RebuildActionFactory.java src/main/java/com/sonyericsson/rebuild/RebuildLastCompletedBuildAction.java src/main/java/com/sonyericsson/rebuild/RebuildProjectActionFactory.java src/main/java/com/sonyericsson/rebuild/Rebuilder.java src/test/java/com/sonyericsson/rebuild/RebuildValidatorTest.java http://jenkins-ci.org/commit/rebuild-plugin/da8dc719490747641822383b1b9299fa3bf9ce9f Log: -Fixed (RebuildActionFactory): JENKINS-14905 Make "Rebuild" button available for builds before plugin installation time -Fixed in test: JENKINS-14387 Cause of rebuilt job should be Cause.UserIdCause -Added new feature: Rebuild Last on project level (see attached screenshot) -Added HtmlUnit test to validate Rebuild and Rebuild links 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] (JENKINS-14905) Make Rebuild button available for builds before plugin installation time
SCM/JIRA link daemon commented on JENKINS-14905 Make Rebuild button available for builds before plugin installation time Code changed in jenkins User: shemeersulaiman Path: src/main/java/com/sonyericsson/rebuild/RebuildAction.java src/main/java/com/sonyericsson/rebuild/RebuildActionFactory.java src/main/java/com/sonyericsson/rebuild/RebuildLastCompletedBuildAction.java src/main/java/com/sonyericsson/rebuild/RebuildProjectActionFactory.java src/main/java/com/sonyericsson/rebuild/RebuildValidator.java src/main/java/com/sonyericsson/rebuild/Rebuilder.java src/test/java/com/sonyericsson/rebuild/RebuildValidatorTest.java http://jenkins-ci.org/commit/rebuild-plugin/1bcd410a6585210b17053659ed411926632f3d46 Log: Merge pull request #5 from rinokadijk/master "Rebuild Last" Action and JENKINS-14905 Compare: https://github.com/jenkinsci/rebuild-plugin/compare/3f147ceb5cbc...1bcd410a6585 You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. 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] (JENKINS-13644) Rebuild plugin can't rebuild when using parameters specified by copyartifact
SCM/JIRA link daemon commented on JENKINS-13644 Rebuild plugin cant rebuild when using parameters specified by copyartifact Code changed in jenkins User: rinokadijk Path: src/main/java/com/sonyericsson/rebuild/RebuildAction.java http://jenkins-ci.org/commit/rebuild-plugin/b46fdf3d077fd237175a36db893435d195a7bbec Log: JENKINS-13644 - Rebuild plugin can't rebuild when using parameters specified by copyartifact -If the build parameter is of type buildselector (copyartifact plugin), then use the createValue from SimpleParameterDefinition to load the parameter. However, the copyartifact plugin should support the createValue(request, jsonObject). As soon as the copyartifact supports this method, this fix could be disabled. 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] (JENKINS-14905) Make Rebuild button available for builds before plugin installation time
SCM/JIRA link daemon commented on JENKINS-14905 Make Rebuild button available for builds before plugin installation time Code changed in jenkins User: rinokadijk Path: src/main/java/com/sonyericsson/rebuild/RebuildAction.java src/main/java/com/sonyericsson/rebuild/RebuildActionFactory.java src/main/java/com/sonyericsson/rebuild/RebuildLastCompletedBuildAction.java src/main/java/com/sonyericsson/rebuild/RebuildProjectActionFactory.java src/main/java/com/sonyericsson/rebuild/Rebuilder.java src/test/java/com/sonyericsson/rebuild/RebuildValidatorTest.java http://jenkins-ci.org/commit/rebuild-plugin/da8dc719490747641822383b1b9299fa3bf9ce9f Log: -Fixed (RebuildActionFactory): JENKINS-14905 Make "Rebuild" button available for builds before plugin installation time -Fixed in test: JENKINS-14387 Cause of rebuilt job should be Cause.UserIdCause -Added new feature: Rebuild Last on project level (see attached screenshot) -Added HtmlUnit test to validate Rebuild and Rebuild links 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] (JENKINS-3265) Reload Configuration from Disk (or POSTing config.xml) loses info on running builds
Kevin Scaldeferri commented on JENKINS-3265 Reload Configuration from Disk (or POSTing config.xml) loses info on running builds Jesse, I'm a little unclear what constitutes a "fully reproducible test case" in this situation. The description of this bug seems pretty well detailed and matches exactly what I see on our installation. To summarize: while builds are running, click the "Reload configuration from disk" link, the existing builds continue to show as in progress on the front page, but are gone from the project page, and the links to the builds from the front page are broken (404). If I log into the machine, all the builds appear to be present, but those that were running when I reloaded the config aren't available from the UI. 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.
