[JIRA] [envinject-plugin] (JENKINS-25860) Can't overide job parameters variable values in envinject definition field
Ricardo García Fernández resolved JENKINS-25860 as Not A Defect Cant overide job parameters variable values in envinject definition field I've found the functionality defined in changelist: https://github.com/jenkinsci/envinject-plugin/commit/f99197cea54c828365736984c6c4e184774e6b12 Best regards! and thanks a lot for your work. Change By: Ricardo García Fernández (11/Dec/14 8:02 AM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp-plugin] (JENKINS-25765) Plugin does not appear as post build action or flexible publish action as of 1.2.0
Patrick Nollet commented on JENKINS-25765 Plugin does not appear as post build action or flexible publish action as of 1.2.0 Are you using Java 7? I had a similar problem with Java 6 when the plugin failed to initialize. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-26011) POODLE Attack and SSLv3 on Jenkins Subversion Plugin
Erez Harari created JENKINS-26011 POODLE Attack and SSLv3 on Jenkins Subversion Plugin Issue Type: Bug Assignee: Unassigned Attachments: svn.log Components: subversion-plugin Created: 11/Dec/14 8:55 AM Description: Following POODLE Attack and SSLv3, our SVN administrator disabled SSLv3 and SSLv2 on apache server. Since them we have experienced SVN checkout consistent failures on Jenkins! Please see attached log errors. Is there a way to tune Jenkins SVN Plugin not to try using SSLv3 and SSLv2 at all? Is there a plan to fix this issue? see attached log file Environment: windows Project: Jenkins Priority: Critical Reporter: Erez Harari This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-flow-plugin] (JENKINS-25420) Stack trace thrown even with simply failure fail in parallel block
Andrey Sorokovikov commented on JENKINS-25420 Stack trace thrown even with simply failure fail in parallel block in the plugin build flow 0.17 the same problem This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26012) Multuple Parameters links
Dmitrijs Sahlovs created JENKINS-26012 Multuple Parameters links Issue Type: Bug Assignee: Unassigned Attachments: Double parameters.png Components: core, promoted-builds-plugin Created: 11/Dec/14 9:38 AM Description: For all jobs, which could be promoted I have multiple links to "Parameters" page(see screenshot). For some jobs I can see even three links to this page. Environment: Jenkins v1.576 Promoted builds plugin v 2.17 Project: Jenkins Priority: Minor Reporter: Dmitrijs Sahlovs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26013) In build history, again make visible if a link was visited
Martin Rust
created JENKINS-26013
In build history, again make visible if a link was visited
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
11/Dec/14 9:39 AM
Description:
Up to Jenkins 1.592, in build history it was possible to distinguish if a link to a specific build was visited or not, because the CSS did not overwrite the default colors for visited/non-visited link.
In 1.593 the links are black, no matter if visited or not.
I request to restore the old behaviour.
This probably takes in war/src/main/webapp/css/style.css
in this block (around line 976) to remove the line color: black;:
.pane.build-name a,
.pane.build-name a:visited {
color: black;
text-decoration: underline;
}
or alternatively, to set up different colors for a and a:visited
Project:
Jenkins
Priority:
Minor
Reporter:
Martin Rust
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-10864) Matrix project page does not show test result information, though aggregate test result information does exist.
Vladimir Dobriakov reopened JENKINS-10864 Matrix project page does not show test result information, though aggregate test result information does exist. Still does not work with the newest Matrix Project Plugin: 1.4 Jenkins: 1.593 On the matrix project page like /job/cucumber-split there is no link to latest aggregated test results. On the page for a certain build like /job/cucumber-split/32 there is no link to aggregated test results. If I go to a certain build for the axis like /job/cucumber-split/part_to_test=1/32/ I can see link for 'Test Result' and there is even a link 'Aggregated Test Result' but the linked page does not contain AGGREGATED test results - the results for part_to_test=2 are not included. I also tried manually listing the sub jobs as explained in https://issues.jenkins-ci.org/browse/JENKINS-7976?focusedCommentId=152296page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-152296 Aggregate downstream test results uncheck 'Automatically aggregate all downstream tests'; under 'Jobs to aggregate' put 'cucumber-split/part_to_test=1, cucumber-split/part_to_test=2'. Same result: now aggregated results. Change By: Vladimir Dobriakov (11/Dec/14 9:45 AM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26013) In build history, again make visible if a link was visited
Martin Rust commented on JENKINS-26013 In build history, again make visible if a link was visited It seems to be this commit that made all build links black: https://github.com/jenkinsci/jenkins/commit/cb9036c45527223525cc1b48020a8ed777020c1a This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [http_request] (JENKINS-26014) No preemptive authentication
Angel López Cima created JENKINS-26014 No preemptive authentication Issue Type: Bug Assignee: Janario Oliveira Attachments: http_request-1.8.6-preemptive.patch Components: http_request Created: 11/Dec/14 10:57 AM Description: Some servers doesn't send a authentication challange response (401), so the authentication header is not sent in the next request attempt (default behaviour in the Apache Commons Http Client). To send always the authentication header, the preemptive authentication must be enabled. In the case of Apache Commons Http Client, the AuthCache must be present in the HttpContext. I attached a patch that solves this. Environment: Jenkins 1.590. HTTP Request Plugin 1.8.6 Project: Jenkins Priority: Minor Reporter: Angel López Cima This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26015) Layout broken since 1.593
Benjamin Dewez
created JENKINS-26015
Layout broken since 1.593
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
ScreenShot001.jpg, ScreenShot002.jpg, ScreenShot052.jpg, ScreenShot053.jpg, ScreenShot056.jpg
Components:
core
Created:
11/Dec/14 11:20 AM
Description:
Our previous version was 1.574 and everything works fine.
We have tested the latest version 1.593 in our ACC and the CSS is broken.
On Chrome v39 - Everything works fine when we are not logged.
On chrome v39 - The CSS is broken when we are logged.
On IE9 - CSS works better than on Chrome but style broken with the tab pane.
It seems that's everything is ok on Firefox.
I think that the error comes with the style "element.style { witdh : ...px } applied on
div id="main-panel" class="col-sm-15 col-md-17 col-lg-18 col-xlg-20" style="width: 1555px;"
For me , the main-panel.jelly is OK but CSS from responsive-grid.css or the _javascript_ are in charge of this error.
Thx for your help
Project:
Jenkins
Labels:
jenkins
layout
chrome
firefox
ie
css
jelly
1.593
Priority:
Major
Reporter:
Benjamin Dewez
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-25525) Add support for the git clone timeout option
Daniel Spilker resolved JENKINS-25525 as Fixed Add support for the git clone timeout option Will be released in 1.28. Change By: Daniel Spilker (11/Dec/14 11:36 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-16345) CLI does not work through reverse proxy
Susanne Lindgren
reopened JENKINS-16345
CLI does not work through reverse proxy
Same problem: cli works when accessing the server directly, but not when accessed via an nginx proxy.
Jenkins version 1.593. No configuration done before testing cli, so everything is default. jenkins-cli.jar newly downloaded from this jenkins. Cli tests done on the jenkins server.
Jenkins is running directly (without container), installed and started as:
$ wget http://mirrors.jenkins-ci.org/war/1.593/jenkins.war
$ /usr/bin/java -Xms256m -Xmx1024m -DJENKINS_HOME=/home/esusedl/.jenkins-sjk2 -jar /home/esusedl/.jenkins-sjk2/jenkins.war --httpPort=8080 --httpsPort=8081 --ajp13Port=-1 --prefix=/sjk2
When using cli towards the server directly it works fine:
$ /usr/bin/java -jar jenkins-cli.jar -s https://jenkins_server_fqdn:8081/jenkins -noCertificateCheck version
Skipping HTTPS certificate checks altogether. Note that this is not secure at all.
Enter passphrase for /home/myuser/.ssh/id_rsa:
WARN Failed to authenticate with your SSH keys. Proceeding as anonymous
1.593
$ /usr/bin/java -jar jenkins-cli.jar -s https://jenkins_proxy_fqdn/jenkins -noCertificateCheck version
Skipping HTTPS certificate checks altogether. Note that this is not secure at all.
Enter passphrase for /home/myuser/.ssh/id_rsa:
Exception in thread "main" java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:579)
at hudson.cli.CLI.connectViaCliPort(CLI.java:203)
at hudson.cli.CLI.init(CLI.java:126)
at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:72)
at hudson.cli.CLI._main(CLI.java:466)
at hudson.cli.CLI.main(CLI.java:382)
Suppressed: java.io.EOFException: unexpected stream termination
at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:331)
at hudson.remoting.Channel.init(Channel.java:421)
at hudson.remoting.Channel.init(Channel.java:400)
at hudson.remoting.Channel.init(Channel.java:396)
at hudson.remoting.Channel.init(Channel.java:385)
at hudson.remoting.Channel.init(Channel.java:377)
at hudson.remoting.Channel.init(Channel.java:353)
at hudson.cli.CLI.connectViaHttp(CLI.java:157)
at hudson.cli.CLI.init(CLI.java:130)
... 3 more
$ /usr/bin/java -version
java version "1.7.0_45"
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)
Jenkins server: RHEL 6.5 x86_64 with a self-signed certificate.
Jenkins proxy server: RHEL 6.5 x86_64 with a verisign certificate. Nginx config for the jenkins instance:
location /jenkins {
sendfile off;
proxy_pass https://jenkins_server_fqdn:8081/jenkins;
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}
Change By:
Susanne Lindgren
(11/Dec/14 11:42 AM)
Resolution:
Incomplete
Status:
Resolved
Reopened
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] [xvnc-plugin] (JENKINS-25424) Exception when editing nodes
Oliver Gondža resolved JENKINS-25424 as Fixed Exception when editing nodes Fixed in 1.21 Change By: Oliver Gondža (11/Dec/14 11:50 AM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26016) PTC Plugin: Request to add postbuild action to label a project
Paul Sharpe created JENKINS-26016 PTC Plugin: Request to add postbuild action to label a project Issue Type: New Feature Assignee: Cletus DSouza Components: integrity-plugin Created: 11/Dec/14 11:55 AM Description: My use case: PTC Plugin checkpoints project and then creates the workspace. Jenkins performs the build and tests. I then have a manual promotion step to approve the build. On that promotion, I then want to label the checkpoint to indicate it is approved. So I could do with an action to add a label to the checkpoint that was created (I believe that the checkpoint reference is stored in an environment variable already). Hopefully you can implement this for me? Project: Jenkins Priority: Minor Reporter: Paul Sharpe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25369) DNS multicast error messages
Andreas Katzig assigned JENKINS-25369 to Andreas Katzig DNS multicast error messages Change By: Andreas Katzig (11/Dec/14 12:40 PM) Assignee: AndreasKatzig This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25369) DNS multicast error messages
Andreas Katzig assigned JENKINS-25369 to Unassigned DNS multicast error messages unintentional self assign, sorry. Change By: Andreas Katzig (11/Dec/14 12:42 PM) Assignee: AndreasKatzig This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-26011) POODLE Attack and SSLv3 on Jenkins Subversion Plugin
Jesse Glick commented on JENKINS-26011 POODLE Attack and SSLv3 on Jenkins Subversion Plugin What version of Jenkins? What version of the Subversion plugin? What version of the JRE and OS? https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue#Howtoreportanissue-WhatinformationtoprovideforEnvironmentandDescription This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-16345) CLI does not work through reverse proxy
Daniel Beck commented on JENKINS-16345 CLI does not work through reverse proxy Susanne Lindgren: I still see no bug. If Jenkins is running on a different host than the reverse proxy that is the canonical URL for Jenkins, you need to set the system property hudson.TcpSlaveAgentListener.hostName as described on https://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+properties. Alternatively, forward the TCP slave agent port from the proxy to the correct host in e.g. iptables. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle-plugin] (JENKINS-15457) Passwords leaked in logs
Poul Henriksen commented on JENKINS-15457 Passwords leaked in logs I'm having the same issue. Is this still "In Progress" as the status indicates? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-26017) always getting this error with maven projectjava.nio.file.DirectoryNotEmptyException: /jenkins/jobs/builds/lastFailedBuild
Amgad Hanafy created JENKINS-26017 always getting this error with maven projectjava.nio.file.DirectoryNotEmptyException: /jenkins/jobs/builds/lastFailedBuild Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 11/Dec/14 1:20 PM Description: Dec 11, 2014 10:01:21 AM INFO hudson.model.Run execute Project #84 main build action completed: FAILURE Dec 11, 2014 10:01:21 AM WARNING jenkins.model.PeepholePermalink updateCache Failed to update hudson.maven.MavenModuleSet@f8fa970Project lastFailedBuild permalink for Project #84 java.nio.file.DirectoryNotEmptyException: /jenkins/jobs/builds/lastFailedBuild at sun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:254) at sun.nio.fs.AbstractFileSystemProvider.delete(AbstractFileSystemProvider.java:115) at java.nio.file.Files.delete(Files.java:1088) at sun.reflect.GeneratedMethodAccessor850.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) at java.lang.reflect.Method.invoke(Method.java:619) at hudson.Util.deleteFile(Util.java:247) at hudson.util.AtomicFileWriter.commit(AtomicFileWriter.java:113) at jenkins.model.PeepholePermalink.writeSymlink(PeepholePermalink.java:200) at jenkins.model.PeepholePermalink.updateCache(PeepholePermalink.java:150) at jenkins.model.PeepholePermalink$RunListenerImpl.onCompleted(PeepholePermalink.java:237) at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:199) at hudson.model.Run.execute(Run.java:1810) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Dec 11, 2014 10:01:21 AM WARNING jenkins.model.PeepholePermalink updateCache Failed to update hudson.maven.MavenModuleSet@f8fa970Project lastUnsuccessfulBuild permalink for Project #84 java.nio.file.DirectoryNotEmptyException: /jenkins/jobs/Project/builds/lastUnsuccessfulBuild at sun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:254) at sun.nio.fs.AbstractFileSystemProvider.delete(AbstractFileSystemProvider.java:115) at java.nio.file.Files.delete(Files.java:1088) at sun.reflect.GeneratedMethodAccessor850.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) at java.lang.reflect.Method.invoke(Method.java:619) at hudson.Util.deleteFile(Util.java:247) at hudson.util.AtomicFileWriter.commit(AtomicFileWriter.java:113) at jenkins.model.PeepholePermalink.writeSymlink(PeepholePermalink.java:200) at jenkins.model.PeepholePermalink.updateCache(PeepholePermalink.java:150) at jenkins.model.PeepholePermalink$RunListenerImpl.onCompleted(PeepholePermalink.java:237) at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:199) at hudson.model.Run.execute(Run.java:1810) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Environment: Jenkins ver. 1.590 Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 2014-08-11T23:58:10+03:00) Java version: 1.6.0, vendor: IBM Corporation Default locale: en_US, platform encoding: ISO8859-1 OS name: aix, version: 7.1, arch: ppc64, family: unix Project: Jenkins Priority: Major Reporter: Amgad Hanafy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators.
[JIRA] [pmd-plugin] (JENKINS-24873) Wrong number of new warnings
Sergey Ryazantsev updated JENKINS-24873 Wrong number of new warnings Change By: Sergey Ryazantsev (11/Dec/14 1:40 PM) Attachment: new_build_1_sum.png Attachment: new_build_2_new.png Attachment: new_build_2_sum.png Attachment: new_build_3_new.png Attachment: new_build_3_sum.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pmd-plugin] (JENKINS-24873) Wrong number of new warnings
Sergey Ryazantsev reopened JENKINS-24873 Wrong number of new warnings Hello, Ulli. I've faced with related problem on another project. Test case: Start the first build. See summary result. Change source code, check "Use delta for new warnings" check box and start the second build. The numbers of new NORMAL priority warnings are different: 2 in sum result and 3 on new warning page. Uncheck "Use delta for new warnings" check box and start the third build. The numbers of new NORMAL priority warnings become the same: 3 in sum result and 3 on new warning page. It seems that is case "Use delta for new warnings" check box is checked, another algorithm is used only for build summary page. But for a new warnings page generation is used the same algorithm as in case "Use delta for new warnings" check box is unchecked. I suppose that number of new warnings of particular priority on new warning page should always be the same as om build summary page. Change By: Sergey Ryazantsev (11/Dec/14 1:40 PM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pmd-plugin] (JENKINS-24873) Wrong number of new warnings
Sergey Ryazantsev edited a comment on JENKINS-24873 Wrong number of new warnings Hello, Ulli. I've faced with related problem on another project. Test case: Start the first build. See summary result. Change source code, check "Use delta for new warnings" check box and start the second build. The numbers of new NORMAL priority warnings are different: 2 in sum result and 3 on new warning page. Uncheck "Use delta for new warnings" check box and start the third build. The numbers of new NORMAL priority warnings become the same: 3 in sum result and 3 on new warning page. It seems that is case "Use delta for new warnings" check box is checked, another algorithm is used only for build summary page. But for a new warnings page generation is used the same algorithm as in case "Use delta for new warnings" check box is unchecked. I suppose that number of new warnings of a particular priority on new warning page should always be the same as on build summary page. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25499) Warning on console about toNormalizedIconNameClass
Walter Kacynski commented on JENKINS-25499 Warning on console about toNormalizedIconNameClass Just upgraded to 1.580.1.1 and I am experiencing this message as well. Is there a loss of functionality this this 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/d/optout.
[JIRA] [claim-plugin] (JENKINS-7824) Claim plugin: Allow assigning builds/tests to other users
David Resnick commented on JENKINS-7824 Claim plugin: Allow assigning builds/tests to other users This has been rolled out and is fantastic! For some reason, no email is sent when assigning to someone else. Is there some configuration I'm missing for this feature? If not I will open an issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-26010) Workflow plugin not working with with Gerrit event
Jesse Glick assigned JENKINS-26010 to rsandell Workflow plugin not working with with Gerrit event Change By: Jesse Glick (11/Dec/14 2:31 PM) Assignee: JesseGlick rsandell This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-26010) Workflow plugin not working with with Gerrit event
Jesse Glick updated JENKINS-26010 Workflow plugin not working with with Gerrit event The problem is in the Gerrit Trigger plugin, which needs to be a TriggerParameterizedJobMixIn.ParameterizedJob rather than a TriggerAbstractProject. And DescriptorImpl.isApplicable has to actually check the type! Change By: Jesse Glick (11/Dec/14 2:31 PM) Labels: workflow Component/s: gerrit-trigger-plugin Component/s: workflow-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/d/optout.
[JIRA] [core] (JENKINS-25842) User Permissions Wiped After Jenkins Restart
Daniel Beck resolved JENKINS-25842 as Cannot Reproduce User Permissions Wiped After Jenkins Restart Issue needs instructions how to reproduce it. Change By: Daniel Beck (11/Dec/14 2:49 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-25868) Endless builds triggered despite no SCM change
Daniel Beck commented on JENKINS-25868 Endless builds triggered despite no SCM change You have two modules. Both have a URL and a local path. Please provide both for the two modules (they can be redacted enough to be recognizable, but retain the overall structure). Try switching the module order as well. Try using Workspace Cleanup Plugin and deleting the complete workspace before a build. (In all possible combinations.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp-plugin] (JENKINS-26018) HockeyApp plugin does not support DMG or PKG files
Gregory Klein created JENKINS-26018 HockeyApp plugin does not support DMG or PKG files Issue Type: Improvement Assignee: Unassigned Attachments: uploadDMGToHockeyApp.sh Components: hockeyapp-plugin Created: 11/Dec/14 2:54 PM Description: The current HockeyApp plugin does not provide support for DMG and PKG files. It is possible however to use their API to upload these two file types, it's just a little trickier to do that than it is to upload an IPA or APK file. My teammate and I have written a script that uses curl to upload DMG and PKG files by using an existing app ID and API token (similar to how the HockeyApp plugin work now) to create a new 'version' for the app and then to 'update' that version with the DMG or PKG file. We know that it's possible, and are currently using a mix between your plugin, which is desired, and our script across the multiple build jobs that are set up for various products so that we can get them over to HockeyApp as a post build action. Adding support for these two file types would be incredibly beneficial to us, and most likely to several other developers as well. I have attached the script that we wrote so you can get an idea of how this is done using curl. Thanks for your time. Environment: - Using HockeyApp Plugin 1.2.0 Project: Jenkins Labels: plugin jenkins improvement HockeyApp DMG PKG Priority: Major Reporter: Gregory Klein This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-25868) Endless builds triggered despite no SCM change
Paul Meathrel edited a comment on JENKINS-25868 Endless builds triggered despite no SCM change Here is an example of the settings which cause the issue. I will try the other things suggested This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-25868) Endless builds triggered despite no SCM change
Paul Meathrel commented on JENKINS-25868 Endless builds triggered despite no SCM change Here is an example of the settings which cause the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-25868) Endless builds triggered despite no SCM change
Paul Meathrel updated JENKINS-25868 Endless builds triggered despite no SCM change Change By: Paul Meathrel (11/Dec/14 2:59 PM) Attachment: svn.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-25868) Endless builds triggered despite no SCM change
Daniel Beck commented on JENKINS-25868 Endless builds triggered despite no SCM change My guess it's because both modules are being checked out into the same directory. I'd be surprised if any other Subversion client handled this correctly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp-plugin] (JENKINS-25765) Plugin does not appear as post build action or flexible publish action as of 1.2.0
Steven Shipton commented on JENKINS-25765 Plugin does not appear as post build action or flexible publish action as of 1.2.0 Thanks, that fixed it. Java 7 hasn't been required until now so perhaps should be added to the documentation for this plugin, unless this is a Jenkins requirement? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-25015) RemoteValidationException when using Mark JIRA Version as Released
Nathan Lindshield commented on JENKINS-25015 RemoteValidationException when using Mark JIRA Version as Released Having exact same issue. Can create a Jira version using the same key, get same error that the key doesn't exist This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp-plugin] (JENKINS-25765) Plugin does not appear as post build action or flexible publish action as of 1.2.0
Steven Shipton updated JENKINS-25765 Plugin does not appear as post build action or flexible publish action as of 1.2.0 Change By: Steven Shipton (11/Dec/14 3:06 PM) Environment: Jenkins1.590 Java6 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp-plugin] (JENKINS-25765) Plugin does not appear as post build action or flexible publish action as of 1.2.0
Steven Shipton resolved JENKINS-25765 as Fixed Plugin does not appear as post build action or flexible publish action as of 1.2.0 Change By: Steven Shipton (11/Dec/14 3:05 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-17291) No separate view for multijob builds.
jony17 commented on JENKINS-17291 No separate view for multijob builds. This would be great. It's a mess if you have a lot of big multijobs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-20528) Unable to link to Jira
Nathan Lindshield commented on JENKINS-20528 Unable to link to Jira Get same result: In Jenkins Manage Jenkins Configure System JIRA the validate setting button returns success no matter what URL I have entered. The only time it fails is if I have no 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/d/optout.
[JIRA] [jira-plugin] (JENKINS-20528) Unable to link to Jira
Nathan Lindshield edited a comment on JENKINS-20528 Unable to link to Jira Get same result: "In Jenkins Manage Jenkins Configure System JIRA the validate setting button returns success no matter what URL I have entered. The only time it fails is if I have no 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/d/optout.
[JIRA] [subversion-plugin] (JENKINS-25868) Endless builds triggered despite no SCM change
Paul Meathrel commented on JENKINS-25868 Endless builds triggered despite no SCM change OK that makes sense, so a configuration error at our end. I will check the details on this and come back to you. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26019) build with form submission does not return queue location
A. Sam.
created JENKINS-26019
build with form submission does not return queue location
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
11/Dec/14 3:35 PM
Description:
related to JENKINS-23235 and JENKINS-13546.
When creating builds using /build, the result is a 201 response where the Location header points to the queue item that represents the new build. Example:
curl -X POST "https://myjenkins/job/plainJob/build" --insecure --include
HTTP/1.1 201 Created
Date: Thu, 11 Dec 2014 15:23:38 GMT
Server: Jetty(winstone-2.8)
Location: https://myjenkins/queue/item/39/
Content-Length: 0
Content-Type: text/plain
For parameterized builds with a form submission the response however contain the queue location:
curl -X POST "https://myjenkins/job/formJob" --insecure -F json='{"parameter": {"name":"ID", "value":"260"}}' --include
HTTP/1.1 100 Continue
HTTP/1.1 201 Created
Date: Thu, 11 Dec 2014 15:24:20 GMT
Server: Jetty(winstone-2.8)
Location: https://myjenkins/job/formJob/
Content-Length: 0
Content-Type: text/plain
Project:
Jenkins
Priority:
Major
Reporter:
A. Sam.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26020) Will not start builds even though there are available slots on executor
Christian Bremer created JENKINS-26020 Will not start builds even though there are available slots on executor Issue Type: Bug Assignee: Unassigned Attachments: ThreadDump - After doing disconnect and connect.log, ThreadDump - No jobs can be schedule on node.log Components: core Created: 11/Dec/14 3:45 PM Description: Sometimes our nodes won't be able to start new builds even though there are free slots available. A workaround for the slaves is to disconnect/connect the slave and it will start to schedule builds again. I have observed that when this happens for a slave the slave has fewer threads ongoing than an idle slave. Attaching thread dumps when this happens and after doing an disconnect/connect. We have seen this issue both on Windows(jlnp) slaves and linux(ssh) slaves as well as on the master node which is running linux. Environment: LTS 1.580.1 Project: Jenkins Priority: Critical Reporter: Christian Bremer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26019) build with form submission does not return queue location
A. Sam.
updated JENKINS-26019
build with form submission does not return queue location
Change By:
A. Sam.
(11/Dec/14 3:49 PM)
Description:
relatedtoJENKINS-23235andJENKINS-13546.Whencreatingbuildsusing/build,theresultisa201responsewheretheLocationheaderpointstothequeueitemthatrepresentsthenewbuild.Example:curl-XPOSThttps://myjenkins/job/plainJob/build--insecure--includeHTTP/1.1201CreatedDate:Thu,11Dec201415:23:38GMTServer:Jetty(winstone-2.8)Location:https://myjenkins/queue/item/39/Content-Length:0Content-Type:text/plainForparameterizedbuildswithaformsubmissiontheresponsehowever
doesnot
containthequeuelocation:curl-XPOSThttps://myjenkins/job/formJob--insecure-Fjson={parameter:[{name:ID,value:260}]}--includeHTTP/1.1100ContinueHTTP/1.1201CreatedDate:Thu,11Dec201415:24:20GMTServer:Jetty(winstone-2.8)Location:https://myjenkins/job/formJob/Content-Length:0Content-Type:text/plain
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26019) build with form submission does not return queue location
A. Sam.
updated JENKINS-26019
build with form submission does not return queue location
Change By:
A. Sam.
(11/Dec/14 3:53 PM)
Description:
relatedtoJENKINS-23235andJENKINS-13546.Whencreatingbuildsusing/build,theresultisa201responsewheretheLocationheaderpointstothequeueitemthatrepresentsthenewbuild.Example:curl-XPOSThttps://myjenkins/job/plainJob/build--insecure--includeHTTP/1.1201CreatedDate:Thu,11Dec201415:23:38GMTServer:Jetty(winstone-2.8)Location:https://myjenkins/queue/item/39/Content-Length:0Content-Type:text/plain
Forparameterized
Iwouldexpectthatparametrized
buildswith
a
formsubmission
wouldpointto
the
responsehoweverdoesnotcontainthe
queue
itemaswell.However
location
headeronlycontainsthejoblinkitself
:curl-XPOSThttps://myjenkins/job/formJob--insecure-Fjson={parameter:[{name:ID,value:260}]}--includeHTTP/1.1100ContinueHTTP/1.1201CreatedDate:Thu,11Dec201415:24:20GMTServer:Jetty(winstone-2.8)Location:https://myjenkins/job/formJob/Content-Length:0Content-Type:text/plain
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-plugin] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Brian Krische commented on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration So any idea what release will include this fix? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-plugin] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Jesse Glick commented on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration 1.594, currently in RC. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-plugin] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Daniel Beck commented on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration Looks to be scheduled for Jenkins 1.595 to be released around Dec 21 according to the changelog at http://jenkins-ci.org/changelog (click 'upcoming changes'). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-plugin] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Daniel Beck edited a comment on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration sigh Updating the changelog... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-plugin] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Daniel Beck edited a comment on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration (confused comment removed) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-plugin] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Jesse Glick commented on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration I just updated the changelog; forgot to do so when merging. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [claim-plugin] (JENKINS-7824) Claim plugin: Allow assigning builds/tests to other users
Ninian commented on JENKINS-7824 Claim plugin: Allow assigning builds/tests to other users Whether emails are sent or not is configurable: Go to Manage Jenkins-Configure System, then look for the 'Claim' section. There should be a check-box there "Send emails when assigning/claiming builds". This was added to allow preservation of the previous behaviour, which is that no mail is sent if someone claimed a build failure. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-26021) xunit published results don't show up or hides maven test results in maven projects
Kevin Browder created JENKINS-26021 xunit published results dont show up or hides maven test results in maven projects Issue Type: Bug Assignee: Gregory Boissinot Components: maven-plugin, xunit-plugin Created: 11/Dec/14 5:08 PM Description: If xunit publisher is used as a pre-step in a maven job then the maven test results don't show up on the front page, if the xunit publish is put after maven then the maven tests don't show up on the front page. It seems like in either case the results should be merged. Environment: Jenkins 1.592, Maven integration plugin 2.8, xunit plugin 1.92 Project: Jenkins Priority: Major Reporter: Kevin Browder This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [coverity-plugin] (JENKINS-26022) Coverity - plugin ignores Job's working directory while performing commit operation
Harsh Sangal created JENKINS-26022 Coverity - plugin ignores Jobs working directory while performing commit operation Issue Type: Bug Assignee: Ken Dang Components: coverity-plugin Created: 11/Dec/14 5:14 PM Description: Observed the following issue while using coverity plugin: Used the Coverity plugin for Build-Analysis-Commit operations.. Build and Analysis ran successfully. MY-WORKSPACE $ "C:\Program Files\Coverity\Coverity Static Analysis\bin\cov-build" --dir Report ant -f Code\MyProj\build.xml compile_debug MY-WORKSPACE $ "C:\Program Files\Coverity\Coverity Static Analysis\bin\cov-analyze" --dir Report --java In commit command, the plugin didn't use the WORKSPACE folder as working directory instead switched to slave's root directory and the command failed. $ "C:\Program Files\Coverity\Coverity Static Analysis\bin\cov-commit-defects" --dir Report --host xy.xyz.xy.xyz --dataport 9090 --stream ABC-XYZ --user abc-xyz ERROR Specified intermediate directory c:/jenkinsci/Report doesn't contain any usable data Coverity cov-commit-defects returned 2, aborting... Build step 'Coverity' changed build result to FAILURE It would be nice to have it fixed as it is already such a nice and feature rich plugin. Also plugin can support to accept environment variables/Jenkins parameters in its configuration fields which currently it does not. Environment: Jenkins ver. 1.592 Name Maven ID License Coverity plugin org.jenkins-ci.plugins:coverity:1.4.1 Eclipse Public License saaj-impl com.sun.xml.messaging.saaj:saaj-impl:1.3.1 xws-security com.sun.xml.xws:xws-security:3.0 Project: Jenkins Priority: Major Reporter: Harsh Sangal This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-26021) xunit published results don't show up or hides maven test results in maven projects
Kevin Browder commented on JENKINS-26021 xunit published results dont show up or hides maven test results in maven projects It may be worth noting that in the case where the xunit results reporter is used as a pre-step you can drill down into the maven module to see tests, the tests just don't get combined into the front page. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-26023) {{Too many levels of symbolic links}} exception during the initial sync
Stavros Vagionitis
created JENKINS-26023
{{Too many levels of symbolic links}} exception during the initial sync
Issue Type:
Bug
Assignee:
Frédéric Camblor
Components:
scm-sync-configuration-plugin
Created:
11/Dec/14 5:45 PM
Description:
After the installation of the GIT plugin and the restart of Jenkins following the instructions provided here. I added the repository that I want the configurations to be saved and saved the System configuration. After some time I get the following error
Stack trace
javax.servlet.ServletException: Caught error while checking for symbolic links
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631)
at org.kohsuke.stapler.Stapler.service(Stapler.java:225)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46)
at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103)
at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:79)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at
[JIRA] [scm-sync-configuration-plugin] (JENKINS-26023) Too many levels of symbolic links exception during the initial sync
Stavros Vagionitis
updated JENKINS-26023
Too many levels of symbolic links exception during the initial sync
Change By:
Stavros Vagionitis
(11/Dec/14 5:46 PM)
Summary:
{{
Toomanylevelsofsymboliclinks
}}
exceptionduringtheinitialsync
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [rebuild-plugin] (JENKINS-26024) Does not work with workflows
Jesse Glick created JENKINS-26024 Does not work with workflows Issue Type: Bug Assignee: Jesse Glick Components: rebuild-plugin Created: 11/Dec/14 5:51 PM Description: java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowRun cannot be cast to hudson.model.AbstractBuild at com.sonyericsson.rebuild.RebuildActionFactory.createFor(RebuildActionFactory.java:50) Project: Jenkins Labels: workflow Priority: Critical Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rebuild-plugin] (JENKINS-26024) Does not work with workflows
Jesse Glick commented on JENKINS-26024 Does not work with workflows https://github.com/jenkinsci/rebuild-plugin/commit/1ca3940c62a79e5e8aba616aa4d79f2e33f24652 avoids the exception but does not make the action actually available and functional. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-plugin] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
dogfood commented on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration Integrated in jenkins_main_trunk #3866 JENKINS-25533 Noting merge of #1477. (Revision 97bc2dd44416ae45e604e634b4d5fcfa839ab2aa) Result = SUCCESS jesse glick : 97bc2dd44416ae45e604e634b4d5fcfa839ab2aa Files : changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-view-column-plugin] (JENKINS-26025) Build History window does not show all builds
Mike Guyre created JENKINS-26025 Build History window does not show all builds Issue Type: Bug Assignee: Unassigned Attachments: build_history_window.jpg, build_list.txt Components: build-view-column-plugin Created: 11/Dec/14 6:03 PM Description: The build history for one of our projects only shows 8 builds when the build folder for the project has over 53 build numbers listed Environment: Windows7 Project: Jenkins Priority: Minor Reporter: Mike Guyre This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rebuild-plugin] (JENKINS-26024) Does not work with workflows
Jesse Glick started work on JENKINS-26024 Does not work with workflows Change By: Jesse Glick (11/Dec/14 6:03 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/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-26023) Too many levels of symbolic links exception during the initial sync
Stavros Vagionitis
updated JENKINS-26023
Too many levels of symbolic links exception during the initial sync
Change By:
Stavros Vagionitis
(11/Dec/14 6:24 PM)
Description:
AftertheinstallationoftheGITpluginandtherestartofJenkinsfollowingtheinstructionsprovided[here|https://wiki.jenkins-ci.org/display/JENKINS/SCM+Sync+configuration+plugin].IaddedtherepositorythatIwanttheconfigurationstobesavedandsavedthe{{Systemconfiguration}}.AftersometimeIgetthefollowingerror{noformat}Stacktracejavax.servlet.ServletException:Caughterrorwhilecheckingforsymboliclinks atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:858) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:631) atorg.kohsuke.stapler.Stapler.service(Stapler.java:225) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:848) atorg.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) athudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46) athudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) athudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:79) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) athudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) athudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) athudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) atorg.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) atorg.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) atorg.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
[JIRA] [git-client-plugin] (JENKINS-26026) Submodules gives java.lang.UnsupportedOperationException with jGit
Thomas Suckow created JENKINS-26026 Submodules gives java.lang.UnsupportedOperationException with jGit Issue Type: Bug Assignee: Nicolas De Loof Components: git-client-plugin Created: 11/Dec/14 6:43 PM Description: When submodules are enabled with jGit building gives: FATAL: not implemented yet java.lang.UnsupportedOperationException: not implemented yet at org.jenkinsci.plugins.gitclient.JGitAPIImpl.setupSubmoduleUrls(JGitAPIImpl.java:2125) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:326) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:301) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:260) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:701) at ..remote call to b4531083cc3f@we13196(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:752) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:179) at com.sun.proxy.$Proxy100.setupSubmoduleUrls(Unknown Source) at org.jenkinsci.plugins.gitclient.RemoteGitImpl.setupSubmoduleUrls(RemoteGitImpl.java:477) at hudson.plugins.git.extensions.impl.SubmoduleOption.onCheckoutCompleted(SubmoduleOption.java:82) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1006) at hudson.scm.SCM.checkout(SCM.java:484) at hudson.model.AbstractProject.checkout(AbstractProject.java:1265) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528) at hudson.model.Run.execute(Run.java:1759) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Environment: Jenkins: 1.592 GIT client plugin: 1.12.0 GIT plugin: 2.3.1 Project: Jenkins Labels: jgit submodules Priority: Minor Reporter: Thomas Suckow This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an
[JIRA] [gerrit-trigger-plugin] (JENKINS-23152) builds getting lost due to GerritTrigger
eguess74 commented on JENKINS-23152 builds getting lost due to GerritTrigger Hi, This is becoming a real mess for us as gerrit keeps referring to the builds that are not showing in the Jenkins GUI and all build numbers are getting messed up. Can the fix be somehow pushed forward? 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/d/optout.
[JIRA] [xcode-plugin] (JENKINS-22130) keychain with the same name already exists error with developer profile import
lacostej resolved JENKINS-22130 as Fixed keychain with the same name already exists error with developer profile import Fixed in 1.4.5 Change By: lacostej (11/Dec/14 8:46 PM) Status: Open Resolved Assignee: lacostej Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-21387) If Provide version number flag selected and only Marketing or Technical version is specified parameter does not expose other, non-specified version via environm
lacostej closed JENKINS-21387 as Fixed If Provide version number flag selected and only Marketing or Technical version is specified parameter does not expose other, non-specified version via environment variables Change By: lacostej (11/Dec/14 8:49 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-26011) POODLE Attack and SSLv3 on Jenkins Subversion Plugin
Erez Harari commented on JENKINS-26011 POODLE Attack and SSLv3 on Jenkins Subversion Plugin Windows 2008 server java 1.7.0_25 Jenkins 1.512 Subversion plugin 1.39 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-26027) Upon upgrade to 1.4.1 or later, provideApplicationVersion should be true if version or shortVersion is defined
lacostej created JENKINS-26027 Upon upgrade to 1.4.1 or later, provideApplicationVersion should be true if version or shortVersion is defined Issue Type: Bug Assignee: lacostej Components: xcode-plugin Created: 11/Dec/14 8:57 PM Project: Jenkins Priority: Minor Reporter: lacostej This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-26027) Upon upgrade to 1.4.1 or later, provideApplicationVersion should be true if version or shortVersion is defined
lacostej resolved JENKINS-26027 as Fixed Upon upgrade to 1.4.1 or later, provideApplicationVersion should be true if version or shortVersion is defined See 77cab92 Change By: lacostej (11/Dec/14 8:58 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-19886) NPE in Xcode plugin
lacostej closed JENKINS-19886 as Fixed NPE in Xcode plugin Change By: lacostej (11/Dec/14 9:02 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-19886) NPE in Xcode plugin
lacostej commented on JENKINS-19886 NPE in Xcode plugin This was released in 1.4.2. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-19886) NPE in Xcode plugin
lacostej resolved JENKINS-19886 as Fixed NPE in Xcode plugin Change By: lacostej (11/Dec/14 9:02 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-12800) Can't add xcodebuild parameters including whitespace
lacostej commented on JENKINS-12800 Cant add xcodebuild parameters including whitespace I suspect this was fixed back in 2013. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-12800) Can't add xcodebuild parameters including whitespace
lacostej closed JENKINS-12800 as Fixed Cant add xcodebuild parameters including whitespace Change By: lacostej (11/Dec/14 9:04 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-12800) Can't add xcodebuild parameters including whitespace
lacostej resolved JENKINS-12800 as Fixed Cant add xcodebuild parameters including whitespace Change By: lacostej (11/Dec/14 9:04 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-login-plugin] (JENKINS-26028) Google Plugin
Bob Balli created JENKINS-26028 Google Plugin Issue Type: Bug Assignee: recampbell Attachments: Google Login Problem.docx Components: google-login-plugin Created: 11/Dec/14 9:05 PM Description: I wanted to use Role based strategy with Google login but when i try to click role based option with Google Login as my security releam. This spoiled my security configuration and by default any user can do anything even though i am not logged in using my Google id. I was wondering if Google Login Plugin can come with Role based strategy. This will give me an option to assign Roles to user as well. Environment: Jenkins Version 1.593 Windows 8 Project: Jenkins Labels: plugin jenkins Priority: Major Reporter: Bob Balli This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-26021) xunit published results don't show up or hides maven test results in maven projects
Kevin Browder updated JENKINS-26021 xunit published results dont show up or hides maven test results in maven projects Change By: Kevin Browder (11/Dec/14 9:12 PM) Description: Ifxunitpublisherisusedasapre-stepinamavenjobthenthemaventestresultsdontshowuponthefrontpage,ifthexunitpublishisputaftermaventhenthe maven xunit testsdontshowuponthefrontpage.Itseemslikeineithercasetheresultsshouldbemerged. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-24271) Re-execute and Force permissions must be separated
Guillaume Paradis commented on JENKINS-24271 Re-execute and Force permissions must be separated I also have the same requirement. Any ETA on resolution? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-26011) POODLE Attack and SSLv3 on Jenkins Subversion Plugin
Jesse Glick resolved JENKINS-26011 as Incomplete POODLE Attack and SSLv3 on Jenkins Subversion Plugin Reopen if the problem continues to occur with the current release of the plugin. Change By: Jesse Glick (11/Dec/14 9:17 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-22568) Subversion polling not work when Repository URL value is variable - E125002: Malformed URL '${SVN_REPO_VARIABLE}'
Daniel Beck
commented on JENKINS-22568
Subversion polling not work when Repository URL value is variable - E125002: Malformed URL ${SVN_REPO_VARIABLE}
Env-Inject adds variables to the build environment. These are unavailable during polling. So it's no surprise if that doesn't work. Workarounds are to reuse previous build's environment or something like that, which can have insane side effects.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-24271) Re-execute and Force permissions must be separated
Uldis Karlovs-Karlovskis assigned JENKINS-24271 to Uldis Karlovs-Karlovskis Re-execute and Force permissions must be separated Change By: Uldis Karlovs-Karlovskis (11/Dec/14 9:20 PM) Assignee: RenateKazaka UldisKarlovs-Karlovskis This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-24271) Re-execute and Force permissions must be separated
Uldis Karlovs-Karlovskis commented on JENKINS-24271 Re-execute and Force permissions must be separated I have it done on my test env but there is an issue to rename priviledge/security role during upgrade of plugin. Anyone has example how to do it in right way? Planning to finish on January or February. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25912) Workspace remains on disk after job has been ( deleted, moved, renamed )
Daniel Beck updated JENKINS-25912 Workspace remains on disk after job has been ( deleted, moved, renamed ) Straightforward workaround present (remove workspaces manually), therefore reducing priority. Additional scenario: Roaming jobs probably also retain their older workspaces on other nodes when deleting the current one. Change By: Daniel Beck (11/Dec/14 9:31 PM) Priority: Major Minor Labels: jenkinssecurity workspace This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-24874) Xcode plugin hangs when using xcode6
lacostej
commented on JENKINS-24874
Xcode plugin hangs when using xcode6
I would like to implement a fix for this with something like
diff --git a/src/main/java/au/com/rayh/XCodeBuilder.java b/src/main/java/au/com/rayh/XCodeBuilder.java
index 5e7971b..56a7da0 100644
--- a/src/main/java/au/com/rayh/XCodeBuilder.java
+++ b/src/main/java/au/com/rayh/XCodeBuilder.java
@@ -480,7 +480,8 @@ public class XCodeBuilder extends Builder {
commandLine.add("-project");
commandLine.add(xcodeProjectFile);
}
-returnCode = launcher.launch().envs(envs).cmds(commandLine).stdout(listener).pwd(projectRoot).start().joinWithTimeout(10, TimeUnit.SECONDS, listener);
+// xcode 6 can timeout upon listing the environment. Let's use a default harcoded timeout.
+returnCode = launcher.launch().envs(envs).cmds(commandLine).stdout(listener).pwd(projectRoot).start().joinWithTimeout(10, TimeUnit.SECONDS, listener);
if (returnCode 0) return false;
}
listener.getLogger().println(Messages.XCodeBuilder_DebugInfoLineDelimiter());
(it would require an adapted listener to handle the error appropriately and display a tip.
But I am unable to create a case so far.
I tested the following on the command line:
me@here ~/ echo $DEVELOPER_DIR
/Applications/Xcode6.0.1.app/Contents/Developer
me@here ~/ xcodebuild -version
Xcode 6.0.1
Build version 6A317
me@here ~/ xcodebuild -list
Information about project "Unity-iPhone":
Targets:
Unity-iPhone
Unity-iPhone Tests
Build Configurations:
Release
Debug
If no build configuration is specified and -scheme is not passed then "Release" is used.
Schemes:
Unity-iPhone
me@here ~/ mv ./Unity-iPhone.xcodeproj/xcshareddata/xcschemes/Unity-iPhone.xcscheme ..
me@here ~/ xcodebuild -list
Information about project "Unity-iPhone":
Targets:
Unity-iPhone
Unity-iPhone Tests
Build Configurations:
Release
Debug
If no build configuration is specified and -scheme is not passed then "Release" is used.
This project contains no schemes.
me@here ~/ mv ../Unity-iPhone.xcscheme ./Unity-iPhone.xcodeproj/xcshareddata/xcschemes/
me@here ~/ mv ./Unity-iPhone.xcodeproj/xcshareddata ..
me@here ~/ xcodebuild -list
Information about project "Unity-iPhone":
Targets:
Unity-iPhone
Unity-iPhone Tests
Build Configurations:
Release
Debug
If no build configuration is specified and -scheme is not passed then "Release" is used.
This project contains no schemes.
me@here ~/ xcodebuild -list -project Unity-iPhone.xcodeproj
Information about project "Unity-iPhone":
Targets:
Unity-iPhone
Unity-iPhone Tests
Build Configurations:
Release
Debug
If no build configuration is specified and -scheme is not passed then "Release" is used.
This project contains no schemes.
So I am unable to get xcodebuild -list to hang even if I remove the whole ./Unity-iPhone.xcodeproj/xcshareddata/
Any tip ?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-26009) Triggering Workflow using parameterized-trigger-plugin
ikedam commented on JENKINS-26009 Triggering Workflow using parameterized-trigger-plugin Please describe the detailed steps 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 and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-26029) Add FAILURE_OR_BETTER Trigger Threshold
ikedam created JENKINS-26029 Add FAILURE_OR_BETTER Trigger Threshold Issue Type: Bug Assignee: ikedam Components: parameterized-trigger-plugin Created: 11/Dec/14 9:59 PM Description: https://github.com/jenkinsci/parameterized-trigger-plugin/pull/76 This Threshold is missing in compare to original Jenkins Trigger Thresholds. ALWAYS is not the same, as ALWAYS also triggers the next build if the user abort the running job. So if you have a Pipeline with 15 Steps and last 10 Steps are connected by ALWAYS, you have to abort 10 jobs in a row. FAILURE_OR_BETTER is the better choice for this. Project: Jenkins Priority: Minor Reporter: ikedam This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-26029) Add FAILURE_OR_BETTER Trigger Threshold
ikedam updated JENKINS-26029 Add FAILURE_OR_BETTER Trigger Threshold Change By: ikedam (11/Dec/14 9:59 PM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-26009) Triggering Workflow using parameterized-trigger-plugin
Andrew Lin commented on JENKINS-26009 Triggering Workflow using parameterized-trigger-plugin Create a WORKFLOW project A Create a FREESTYLE project B In the freestyle project B, Add a build step of "Trigger/call builds on other projects" Projects to build: A will get an error that states "A is not buildable" Also, there is no post build in WORKFLOW project. I'm not quite sure if this is the same bug This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26030) Build deletion fails due to file lock
Jesse Glick
created JENKINS-26030
Build deletion fails due to file lock
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
11/Dec/14 10:14 PM
Description:
After running a trivial flow
node {}
on Windows, trying to delete it fails due to a lock error on 3.log, the one with (one line of) output.
Deleting a build of an empty flow works, as does a flow
echo 'hello'
so the problem might be specific to ExecutorStep.
Project:
Jenkins
Labels:
lock
leak
Priority:
Critical
Reporter:
Jesse Glick
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-16376) BuildStepMonitor.BUILD makes concurrent builds wait, could be changed to BuildStepMonitor.NONE?
Sandeep Dhingra commented on JENKINS-16376 BuildStepMonitor.BUILD makes concurrent builds wait, could be changed to BuildStepMonitor.NONE? We need this to be change for performance publisher plugin too. Can I contribute? https://github.com/jenkinsci/performance-plugin/search?utf8=%E2%9C%93q=BuildStepMonitor+getRequiredMonitorService 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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26030) Build deletion fails due to file lock
Jesse Glick started work on JENKINS-26030 Build deletion fails due to file lock Change By: Jesse Glick (11/Dec/14 10:33 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/d/optout.
[JIRA] [core] (JENKINS-23797) Update offline cause message picks incorrect message from DiskSpace cause
Oliver Gondža resolved JENKINS-23797 as Fixed Update offline cause message picks incorrect message from DiskSpace cause Should be fixed in 1.595. Change By: Oliver Gondža (11/Dec/14 10:42 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23797) Update offline cause message picks incorrect message from DiskSpace cause
Oliver Gondža assigned JENKINS-23797 to Oliver Gondža Update offline cause message picks incorrect message from DiskSpace cause Change By: Oliver Gondža (11/Dec/14 10:42 PM) Assignee: OliverGondža This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-16376) BuildStepMonitor.BUILD makes concurrent builds wait, could be changed to BuildStepMonitor.NONE?
Alex Earl commented on JENKINS-16376 BuildStepMonitor.BUILD makes concurrent builds wait, could be changed to BuildStepMonitor.NONE? Please open a new issue for the performance plugin. This issue is for email-ext. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-login-plugin] (JENKINS-26028) Google Plugin
recampbell closed JENKINS-26028 as Not A Defect Google Plugin Change By: recampbell (11/Dec/14 10:49 PM) Status: Open Closed Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-login-plugin] (JENKINS-26028) Google Plugin
recampbell commented on JENKINS-26028 Google Plugin Looking at your configuration, you have checked "Administrator" for Anonymous users. You probably want to revoke access to that role entirely. Please use the Jenkins user list for these types of questions: https://groups.google.com/forum/#!forum/jenkinsci-users Closing since this is 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 and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-26031) Parameterized trigger plugin should expose downstream builds to the XML/JSON API
abayer created JENKINS-26031 Parameterized trigger plugin should expose downstream builds to the XML/JSON API Issue Type: Improvement Assignee: huybrechts Components: parameterized-trigger-plugin Created: 11/Dec/14 10:58 PM Description: Currently, you can't get any information on the downstream builds triggered by the parameterized trigger plugin via the XML/JSON API. That seems silly. =) Project: Jenkins Priority: Minor Reporter: abayer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-26032) BuildStepMonitor.BUILD makes concurrent builds wait, could be changed to BuildStepMonitor.NONE?
Sandeep Dhingra created JENKINS-26032 BuildStepMonitor.BUILD makes concurrent builds wait, could be changed to BuildStepMonitor.NONE? Issue Type: Bug Assignee: Jesse Glick Components: email-ext-plugin Created: 11/Dec/14 11:14 PM Description: We perform many concurrent builds in one job and are using the email-ext plugin. Sometimes and older build takes longer time to finish and then the new jobs just waits to be finished because BuildStepMonitor.BUILD is configured in the plugin. Could this one line be changed? Project: Jenkins Priority: Major Reporter: Sandeep Dhingra This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
