[JIRA] [maven] (JENKINS-21554) NPE after Waiting for Jenkins to finish collecting data
Juha Syrjälä commented on JENKINS-21554 NPE after Waiting for Jenkins to finish collecting data The bug strikes also with Jenkins 1.532.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/groups/opt_out.
[JIRA] [integrity-plugin] (JENKINS-21993) [Integrity] Add a label to existing checkpoint
Thorsten Liepert created JENKINS-21993 [Integrity] Add a label to existing checkpoint Issue Type: Improvement Assignee: Cletus DSouza Components: integrity-plugin Created: 28/Feb/14 8:37 AM Description: We are using the release-plug-in in a release project, where we rebuild a given checkpoint (parameterized build) with compiler settings for release. Here it would be great if there could be a post build step to label the checkpoint again with a release label. This would be great for following which checkpoint was actual released and which was skipped. Project: Jenkins Priority: Minor Reporter: Thorsten Liepert This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-19121) Build pipeline plugin no longer prompts for parameters of parameterised job
Jonas Bang Christensen commented on JENKINS-19121 Build pipeline plugin no longer prompts for parameters of parameterised job Can confirm this is an issue with Jenkins 1.532.2 and build-pipeline-plugin 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/groups/opt_out.
[JIRA] [http_request] (JENKINS-21994) Add HTTP header
R Y created JENKINS-21994 Add HTTP header Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: http_request Created: 28/Feb/14 9:26 AM Project: Jenkins Priority: Critical Reporter: R Y This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cppcheck] (JENKINS-17540) ConversionException reading build.xml
James Howe commented on JENKINS-17540 ConversionException reading build.xml Maybe it's due to JENKINS-12124 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [walldisplay] (JENKINS-12932) Wall Display plugin running in Google Chrome seems to have a memory leak
evernat resolved JENKINS-12932 as Incomplete Wall Display plugin running in Google Chrome seems to have a memory leak No response from the reporter, so resolving as incomplete. Change By: evernat (28/Feb/14 10:37 AM) 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/groups/opt_out.
[JIRA] [rtc] (JENKINS-21964) Build definition and workspace name should accept parameters and/or environment variables.
Heather Fraser-Dube assigned JENKINS-21964 to Unassigned Build definition and workspace name should accept parameters and/or environment variables. Change By: Heather Fraser-Dube (28/Feb/14 10:58 AM) Assignee: DeluanQuintão This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-626) permanent url for svn revision of a build
Danny Staple commented on JENKINS-626 permanent url for svn revision of a build How does this now work since the "primitive XPath result sets now forbidden"? I can query without "text()" and have the surrounding XML - but that requires additional SED or other transformation to de-xml it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-20940) Project source of a multi-config project inside a folder not working
ikedam commented on JENKINS-20940 Project source of a multi-config project inside a folder not working JENKINS-19833 is released in copyartifact-plugin 1.29. Can you try the latest version and see the problem is resolved? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [rtc] (JENKINS-21964) Build definition and workspace name should accept parameters and/or environment variables.
Heather Fraser-Dube commented on JENKINS-21964 Build definition and workspace name should accept parameters and/or environment variables. Another option would be use the Hudson/Jenkins integration provided by RTC. There you could set up a build definition that references your Jenkins build. When requesting a build of the rtc build definition you can pick the workspace you want built. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ui-changes] (JENKINS-13442) Default icon size should be configurable
Steven Christou assigned JENKINS-13442 to Steven Christou Default icon size should be configurable Change By: Steven Christou (28/Feb/14 11:16 AM) Assignee: StevenChristou This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-20112) Can't access artifacts of upstream matrix jobs
ikedam commented on JENKINS-20112 Cant access artifacts of upstream matrix jobs I added following features: Supports "authorized" job. You can authorize jobs with Authorize Project plugin (introdeced in 1.29). Added configuration to specify which jobs can copy artifacts of that job. See https://github.com/jenkinsci/copyartifact-plugin/pull/27 for a screen shot (introduced in 1.30). Would you try them? I hope you like it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-19132) Copy Artifact Plugin with parameterized project name incompatible with Github Authorization Settings
ikedam commented on JENKINS-19132 Copy Artifact Plugin with parameterized project name incompatible with Github Authorization Settings Copyartifact 1.30 provides a configuration to specify which projects can copy artifacts of that project. See https://github.com/jenkinsci/copyartifact-plugin/pull/27 for a screen shop. This would help 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/groups/opt_out.
[JIRA] [copy-to-slave] (JENKINS-21983) CopyToSlave exception when source contain a file starting with a .dot
Antoine Musso commented on JENKINS-21983 CopyToSlave exception when source contain a file starting with a .dot I have inserted /slave/ by mistake while doing the bug report. After some more investigation, it seems the issue is because of some file permissions (the copy is made by the jenkins master to a directory owned by the jenkins slave on that machine). Will look at it again and might well close this bug. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20892) /{view,computer,user}/*/builds /job/*/buildTimeTrend block HTTP response on build record loading
SCM/JIRA link daemon
commented on JENKINS-20892
/{view,computer,user}/*/builds /job/*/buildTimeTrend block HTTP response on build record loading
Code changed in jenkins
User: Jesse Glick
Path:
core/src/main/java/hudson/util/RunList.java
http://jenkins-ci.org/commit/jenkins/537e94a09c8fa88607d998162b5a62eac3fe11d5
Log:
JENKINS-20892 Noting that RunList.getFirstBuild (used by BuildTimelineWidget) breaks lazy loading.
(cherry picked from commit a586609c4a2f2083a7f40a6055776afbf2b1f1c7)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20892) /{view,computer,user}/*/builds /job/*/buildTimeTrend block HTTP response on build record loading
SCM/JIRA link daemon
commented on JENKINS-20892
/{view,computer,user}/*/builds /job/*/buildTimeTrend block HTTP response on build record loading
Code changed in jenkins
User: Jesse Glick
Path:
core/src/main/java/hudson/model/User.java
http://jenkins-ci.org/commit/jenkins/46d4a638182d149b105414eadf172157e4fcb96e
Log:
JENKINS-20892 /user//rssLatest should use getAllItems to check in folders, just like /user//builds does.
(cherry picked from commit ece93739dd291d03c673664afe6b4aaa00f07ef1)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20892) /{view,computer,user}/*/builds /job/*/buildTimeTrend block HTTP response on build record loading
SCM/JIRA link daemon
commented on JENKINS-20892
/{view,computer,user}/*/builds /job/*/buildTimeTrend block HTTP response on build record loading
Code changed in jenkins
User: Jesse Glick
Path:
core/src/main/java/hudson/Functions.java
core/src/main/java/hudson/model/BuildTimelineWidget.java
core/src/main/java/hudson/model/Job.java
core/src/main/java/hudson/model/User.java
core/src/main/java/hudson/util/RunList.java
core/src/main/java/jenkins/widgets/BuildListTable.java
core/src/main/resources/hudson/model/BuildTimelineWidget/control.jelly
core/src/main/resources/hudson/model/Job/buildTimeTrend.jelly
core/src/main/resources/hudson/model/User/builds.jelly
core/src/main/resources/lib/hudson/buildListTable.jelly
http://jenkins-ci.org/commit/jenkins/ef6343be19fc990e0fcdab31d4d3f30c56baba0b
Log:
JENKINS-20892 Partial fix of poor scalability in /builds and related displays.
(cherry picked from commit c5e23739fa85a6fe93ad90a35da4051a2767c874)
Compare: https://github.com/jenkinsci/jenkins/compare/f61086b56cec...ef6343be19fc
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20892) /{view,computer,user}/*/builds /job/*/buildTimeTrend block HTTP response on build record loading
SCM/JIRA link daemon
commented on JENKINS-20892
/{view,computer,user}/*/builds /job/*/buildTimeTrend block HTTP response on build record loading
Code changed in jenkins
User: Jesse Glick
Path:
core/src/main/java/hudson/model/User.java
http://jenkins-ci.org/commit/jenkins/915000b5a0a4c33e02104e47c4b9420192531e07
Log:
JENKINS-20892 Introduced method so that /user//rssLatest can check UserIdCause just like /user//builds already was.
(cherry picked from commit 76af02eed23f43ebd7fde094d939339705b1ef0f)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17012) ERROR: Publisher hudson.tasks.Mailer aborted due to exception
evernat commented on JENKINS-17012 ERROR: Publisher hudson.tasks.Mailer aborted due to exception Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-5396) Support tags instead of branches
Hermien Pellissier commented on JENKINS-5396 Support tags instead of branches I installed the experimental plugin with this change, and it works beautifully. Thanks Jesse! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [other] (JENKINS-21995) Disappeared workspaces during concurrent builds - Bug or feature?
HOR H
created JENKINS-21995
Disappeared workspaces during concurrent builds - Bug or feature?
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
other
Created:
28/Feb/14 1:10 PM
Description:
I have 3 computers. One computer works as master (M) the two others (S1, S2) as slave.
Jenkins version is 1.551
OS is Windows7, Server 2003/8
The builds runs only on the slaves.
I have one Job defined. This job runs a batch with individual parameters. Parallel build for the job is enabled. The job uses a custom workspace, e.g. D:\jenkins-ws\${JOB_NAME}\workspace
I noticed the following behavior if I run this job concurrent.
1. I’m on the Jenkins master, and run the job. Job is scheduled on Slave S1.
2. Build is running on S1, in the WebUI I see a Workspace 1 (W1) under Jenkins/Job
3. I’m starting the job again (maybe with other parameter), Job is scheduled on Slave 2
4. In the WebUI the workspace W1 disappears and a Workspace W2 for the second job is shown
After finishing of both jobs the workspace directories exist on the corresponding slave machines, but not I the WebUI - there’s only the second workspace reachable.
e.g. https://machine:8080/job/job/ws/2
If I try the address https://machine:8080/job/job/ws/1 then I got an error 404.
If I restart the Jenkins machines the behavior stays: only the workspaces of the latest of identical concurrent jobs are shown.
Why the first job is dropped in the UI? How can I change the behavior so that all workspace of concurrent builds of the same jobs a shown?
Due Date:
28/Feb/14 12:00 AM
Environment:
Windows 7/2003/2008
Project:
Jenkins
Priority:
Major
Reporter:
HOR H
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copy-to-slave] (JENKINS-21983) CopyToSlave exception when source contain a file starting with a .dot
Antoine Musso resolved JENKINS-21983 as Not A Defect CopyToSlave exception when source contain a file starting with a .dot Turned out to be a file permission issue. The jenkins user could not write to the destination and the error message 'No such file or directory' made it very confusing. Everything for me now :-] Change By: Antoine Musso (28/Feb/14 1:49 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21969) Performance issue with search box
Jesse Glick updated JENKINS-21969 Performance issue with search box Change By: Jesse Glick (28/Feb/14 1:58 PM) Labels: performance This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21978) Couldn't find any revision to build. Verify the repository and branch configuration for this job.
Benn Sundsrud commented on JENKINS-21978 Couldnt find any revision to build. Verify the repository and branch configuration for this job. We're seeing the same error in 2.0.3 on Jenkins 1.552 trying to build tags/$tagVersion passed in via build param. Other builds that specify branches work fine, only building tags fails. Rolling back the git plugin to 2.0 works, leaving git-client 1.6.3. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21978) Couldn't find any revision to build. Verify the repository and branch configuration for this job.
Mark Waite resolved JENKINS-21978 as Duplicate Couldnt find any revision to build. Verify the repository and branch configuration for this job. Duplicate of JENKINS-21952 Change By: Mark Waite (28/Feb/14 2:49 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21984) java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014
Jesse Glick reopened JENKINS-21984 java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014 Still broken in LTS. Checked in a fresh 1.532.2 installation (UC was OK but tool installations were not). Also UpdateSiteTest.updateDirectlyWithJson is failing, since it is using a downloaded copy of data, which I can fix. Change By: Jesse Glick (28/Feb/14 3:33 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21984) java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014
SCM/JIRA link daemon commented on JENKINS-21984 java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014 Code changed in jenkins User: Jesse Glick Path: test/src/test/java/hudson/model/UpdateSiteTest.java http://jenkins-ci.org/commit/jenkins/334ce1be691c96ad63642c8301c4f0417a0705c3 Log: JENKINS-21984 Disabling cert check on updateDirectlyWithJson since the certificate is now expired, and it is no good to have a test which is known to start failing at a particular time in the future! Compare: https://github.com/jenkinsci/jenkins/compare/a0d6e5286d94...334ce1be691c This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21984) java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014
Jesse Glick commented on JENKINS-21984 java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014 Ah, of course: UpdateCenterTest checks only UC metadata, whereas it is tool installer metadata which appears to still have a bad signature. Would need a new test for that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-5396) Support tags instead of branches
cowwoc commented on JENKINS-5396 Support tags instead of branches (Confused) Is this fix part of the public plugin? Or is it not released to the public yet? Last time I checked I didn't see a separate "tag" UI field. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-21996) Jenkins removes conditional build steps
Sajajd Rehman created JENKINS-21996 Jenkins removes conditional build steps Issue Type: Bug Assignee: Mirko Friedenhagen Components: jobconfighistory Created: 28/Feb/14 4:01 PM Description: It looks like looking at Job history page there are quite a few changes done by Jenkins as "system" and "anonymous" user. Sometimes these changes are just time change etc but we observed that sometimes Jenkins deletes conditional build steps. This has happened many times and not sure its plugin or Hudson or whoever it is makes life harder as this causes lots of issues with build jobs as complete steps are missing. Environment: Jenkins 1.551, jobconfighistory plugin is 2.4 Project: Jenkins Priority: Major Reporter: Sajajd Rehman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-17680) Upgrade to new Copy Artifacts version erases all job names to copy from
ikedam resolved JENKINS-17680 as Fixed Upgrade to new Copy Artifacts version erases all job names to copy from Change By: ikedam (28/Feb/14 4:25 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-5396) Support tags instead of branches
Jesse Glick commented on JENKINS-5396 Support tags instead of branches It is currently only on the experimental update center. I can push a general 1.50 release, though; probably about time. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-17600) Unable to find build for artifact copy using specific build number and current slave.jar
ikedam commented on JENKINS-17600 Unable to find build for artifact copy using specific build number and current slave.jar What does slaves version mean? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18680) View.onJobRenamed should be deprecated
Jesse Glick updated JENKINS-18680 View.onJobRenamed should be deprecated Change By: Jesse Glick (28/Feb/14 4:32 PM) Labels: apifolders lts-candidate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Equilibra talento con experiencia.
-- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-19244) jenkins random hang during startup - Solaris and Linux
XiVO DeV TEAM commented on JENKINS-19244 jenkins random hang during startup - Solaris and Linux We had the same problem: Jenkins randomly (but very often) hangs at startup during the loading of jobs. Adding the option -Dhudson.model.parallelLoad=false did not solve the problem. Looking at the jtrace, we saw one thread blocking on the plugin "Throttle Concurrent Builds Plugin". We fixed the problem by downgrading the plugin "Throttle Concurrent Builds Plugin" from 1.8.1 to 1.8. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-16185) CopyArtifact plugin can't copy from not anonymous redeable jobs
ikedam commented on JENKINS-16185 CopyArtifact plugin cant copy from not anonymous redeable jobs You use a variable to specify a job name tocopy from, don't you? I added following features. Supports "authorized" job. You can authorize jobs with Authorize Project plugin (introdeced in 1.29). Added configuration to specify which jobs can copy artifacts of that job. See https://github.com/jenkinsci/copyartifact-plugin/pull/27 for a screen shot (introduced in 1.30). They must help you. Would you try them? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dependency-check-jenkins] (JENKINS-21990) DependencyCheck aborted due to exception
Steve Springett updated JENKINS-21990 DependencyCheck aborted due to exception Change By: Steve Springett (28/Feb/14 4:56 PM) Environment: OS:OpenSUSE12.2Jenkinsmasterversion:1.522Jenkinsslavejarversion:2.28Staticanalysispluginversion:1.54 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21997) LeftItem.executable == null during QueueListener.onLeft
Jesse Glick created JENKINS-21997 LeftItem.executable == null during QueueListener.onLeft Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: core Created: 28/Feb/14 5:21 PM Description: The QueueListener.onLeft listener callback sounds useful, except when it is called you cannot use LeftItem.getExecutable()—it is always null (even for a build which was not canceled). https://github.com/jenkinsci/jenkins/blob/334ce1be691c96ad63642c8301c4f0417a0705c3/core/src/main/java/hudson/model/Executor.java#L207 Queue.onStartExecuting is called, which triggers the listener. Immediately afterward, WorkUnit.setExecutable is called, but that is too late for the listener. The fix would presumably be to have onStartExecuting return its LeftItem, and make Executor.run be responsible for calling QueueListener.onLeft in this case. (The other case is Queue.cancel.) Or perhaps it suffices to call Queue.onStartExecuting after WorkUnit.setExecutable. Unclear if that is safe; onStartExecuting also removes the BuildableItem from pendings, and is synchronized, so maybe that would introduce a race condition. Project: Jenkins Priority: Minor 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/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-14654) fails to copy artifact from matrix to matrix with label as parameter
ikedam commented on JENKINS-14654 fails to copy artifact from matrix to matrix with label as parameter You have to grant permissions also to anonymous users. Alternately, I added following features: Supports "authorized" job. You can authorize jobs with Authorize Project plugin (introdeced in 1.29). Added configuration to specify which jobs can copy artifacts of that job. See https://github.com/jenkinsci/copyartifact-plugin/pull/27 for a screen shot (introduced in 1.30). Would you try them? I think they help 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/groups/opt_out.
[JIRA] [core] (JENKINS-21997) LeftItem.executable == null during QueueListener.onLeft
Jesse Glick commented on JENKINS-21997 LeftItem.executable == null during QueueListener.onLeft The workaround is to use a RunListener to wait for a build to start, then call .executor.currentWorkUnit.context and match it to LeftItem.outcome. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21984) java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014
dogfood commented on JENKINS-21984 java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014 Integrated in jenkins_main_trunk #3203 JENKINS-21984 Checking stable UC as well. Cannot reproduce certificate problem in test. (Revision c87b7daf79f8613de7bfd3ee6745f66d5d1a14a3) JENKINS-21984 Disabling cert check on updateDirectlyWithJson since the certificate is now expired, and it is no good to have a test which is known to start failing at a particular time in the future! (Revision 334ce1be691c96ad63642c8301c4f0417a0705c3) Result = SUCCESS Jesse Glick : c87b7daf79f8613de7bfd3ee6745f66d5d1a14a3 Files : test/src/test/java/hudson/model/UpdateCenterTest.java Jesse Glick : 334ce1be691c96ad63642c8301c4f0417a0705c3 Files : test/src/test/java/hudson/model/UpdateSiteTest.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-13463) Upgraded to 1.21 and now cannot copy from Matrix Builds
ikedam commented on JENKINS-13463 Upgraded to 1.21 and now cannot copy from Matrix Builds Please report how you configure your job. Especially, do you use variables to specify the job to copy from? If it doesn't matter, please attach config.xml of the job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-19446) Deadlock while parallel deletion/rename of jobs
SCM/JIRA link daemon commented on JENKINS-19446 Deadlock while parallel deletion/rename of jobs Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/hudson/model/AbstractItem.java http://jenkins-ci.org/commit/jenkins/41baac80fbf559aa3eb30c635abe0386815fd67f Log: FIXED JENKINS-19446 Defer the notification to avoid deadlock. (cherry picked from commit a5755cb3e1f901c98a2263a3ae1851489cb8e47b) Conflicts: 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/groups/opt_out.
[JIRA] [artifactdeployer] (JENKINS-19664) Archived artifact of promoted build corrupted after download!
Kevin Welker commented on JENKINS-19664 Archived artifact of promoted build corrupted after download! We see this periodically too. Are you running out of the native winstone container, or are you running in another container like Tomcat? We are currently running right out of the jar using the included Winstone container. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [buildgraph-view] (JENKINS-19470) Build Graph not displaying
Luke Woydziak edited a comment on JENKINS-19470 Build Graph not displaying We'll wait for the release. By-the-way, my company just sponsored this issue so hopefully we can get a release soon. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [buildgraph-view] (JENKINS-19470) Build Graph not displaying
Luke Woydziak commented on JENKINS-19470 Build Graph not displaying We'll wait for the release. By-the-way, my company just sponsored this issue sod hopefully we can get a release soon. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plugin] (JENKINS-21998) Testlink plugin - Unable to retrieve test-steps
Sebastien Girard created JENKINS-21998 Testlink plugin - Unable to retrieve test-steps Issue Type: Bug Assignee: Unassigned Components: plugin Created: 28/Feb/14 6:31 PM Description: I am trying to retrieve the total number of test-steps in the current test case, but the env variable 'TESTLINK_TESTCASE_STEP_TOTAL' always returns the value 0 even though my test case has several test-steps (manual and automatic). I tried with 'Single Build Step' as well as 'Iterative Test Build Steps'. Please advise... Environment: Testlink 1.9.7 Jenkins 1.515 Jenkins TestLink Plugin 3.10 Project: Jenkins Priority: Minor Reporter: Sebastien Girard This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21999) Computer does not exist returns NPE
Steven Christou created JENKINS-21999 Computer does not exist returns NPE Issue Type: Bug Affects Versions: current Assignee: Steven Christou Components: core Created: 28/Feb/14 6:36 PM Description: If a computer does not exist, or a slave does not exist createLaucher throws a NPE. FATAL: null java.lang.NullPointerException at hudson.model.Slave.createLauncher(Slave.java:347) at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:617) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:553) at hudson.model.Run.execute(Run.java:1665) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:246) Fix Versions: current Project: Jenkins Priority: Major Reporter: Steven Christou This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21999) Computer does not exist returns NPE
Steven Christou
updated JENKINS-21999
Computer does not exist returns NPE
Change By:
Steven Christou
(28/Feb/14 6:37 PM)
Description:
Ifacomputer
doesnotexist,
or
a
slavedoesnotexistcreateLaucherthrowsaNPE.{noformat}FATAL:nulljava.lang.NullPointerException athudson.model.Slave.createLauncher(Slave.java:347) athudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:617) athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:553) athudson.model.Run.execute(Run.java:1665) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:246){noformat}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-22000) No history shown in overviews for jobs inside folders
Jesse Glick
created JENKINS-22000
No history shown in overviews for jobs inside folders
Issue Type:
Bug
Assignee:
Mirko Friedenhagen
Components:
jobconfighistory
Created:
28/Feb/14 6:41 PM
Description:
2.6-SNAPSHOT. Even if you have asked to track item group changes (I suppose it does not matter here), if you say create a job inside a folder, you cannot find this event anywhere. The Job Configuration History for the job lists its creation, but the same page for the containing folder lists nothing, and the root history page also lists nothing (I suppose because JobConfigHistoryRootAction.getJobConfigs(type) calls collect("") which seems to specifically exclude jobs not at top level).
Project:
Jenkins
Priority:
Major
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/groups/opt_out.
[JIRA] [core] (JENKINS-22001) Do not solve JENKINS-19446 by delivering events asynchronously
Jesse Glick created JENKINS-22001 Do not solve JENKINS-19446 by delivering events asynchronously Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: core Created: 28/Feb/14 6:59 PM Description: As I wrote there: The current fix is just no good. It delivers events asynchronously, which makes the system unpredictable, and ruins functional tests. Better IMHO would be to call just save() asynchronously. Project: Jenkins Labels: threads robustness Priority: Major 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/groups/opt_out.
[JIRA] [core] (JENKINS-19446) Deadlock while parallel deletion/rename of jobs
Jesse Glick commented on JENKINS-19446 Deadlock while parallel deletion/rename of jobs Filed JENKINS-22001 for the problematic 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/groups/opt_out.
[JIRA] [core] (JENKINS-22001) Do not solve JENKINS-19446 by delivering events asynchronously
Jesse Glick assigned JENKINS-22001 to Jesse Glick Do not solve JENKINS-19446 by delivering events asynchronously Change By: Jesse Glick (28/Feb/14 7:06 PM) Assignee: KohsukeKawaguchi JesseGlick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-22001) Do not solve JENKINS-19446 by delivering events asynchronously
Jesse Glick started work on JENKINS-22001 Do not solve JENKINS-19446 by delivering events asynchronously Change By: Jesse Glick (28/Feb/14 7:20 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-22001) Do not solve JENKINS-19446 by delivering events asynchronously
SCM/JIRA link daemon commented on JENKINS-22001 Do not solve JENKINS-19446 by delivering events asynchronously Code changed in jenkins User: Jesse Glick Path: src/test/java/com/cloudbees/hudson/plugins/folder/FolderTest.java http://jenkins-ci.org/commit/cloudbees-folder-plugin/a8117f59702e8a2ccdf3a9720924718b508b9b83 Log: Updating comment to note JENKINS-22001. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-22002) Copy Artifact doesn't support jobs in different Folders
Walter Kacynski created JENKINS-22002 Copy Artifact doesnt support jobs in different Folders Issue Type: Bug Assignee: Unassigned Attachments: cloudbees-support(1).zip Components: copyartifact Created: 28/Feb/14 7:44 PM Description: When we use copy artifact version 1.30 but it doesn't seem to resolve jobs across different folders. If the source job and target job are within the same folder then we are able to use this plugin correctly. Project: Jenkins Priority: Major Reporter: Walter Kacynski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17022) XML-Tag attachBuildLog ist not written to config.xml
evernat updated JENKINS-17022 XML-Tag attachBuildLog ist not written to config.xml Change By: evernat (28/Feb/14 8:08 PM) Component/s: email-ext Component/s: plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17022) XML-Tag attachBuildLog ist not written to config.xml
evernat resolved JENKINS-17022 as Duplicate XML-Tag attachBuildLog ist not written to config.xml Change By: evernat (28/Feb/14 8:09 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plugin] (JENKINS-21998) Testlink plugin - Unable to retrieve test-steps
Sebastien Girard commented on JENKINS-21998 Testlink plugin - Unable to retrieve test-steps Seems to be related to closed issue : JENKINS-10904 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-22003) Null pointer on notifyCommit
jpschewe created JENKINS-22003 Null pointer on notifyCommit Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 28/Feb/14 8:46 PM Description: When using the notifyCommit hook I get the stack trace below. When using Jenkins 1.532.1 and Git plugin 2.0.1 this worked. The build does get kicked off though. javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) 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:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) 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:135) 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 winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at
[JIRA] [core] (JENKINS-19446) Deadlock while parallel deletion/rename of jobs
SCM/JIRA link daemon commented on JENKINS-19446 Deadlock while parallel deletion/rename of jobs Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/AbstractItem.java core/src/main/java/hudson/model/Job.java test/src/test/java/hudson/model/ListViewTest.java http://jenkins-ci.org/commit/jenkins/00d27176f3a452e38bd0caafebe78c7bc2fa822f Log: FIXED JENKINS-22001 Simpler fix of JENKINS-19446 that does not introduce asynchronous behavior. Compare: https://github.com/jenkinsci/jenkins/compare/334ce1be691c...00d27176f3a4 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-22001) Do not solve JENKINS-19446 by delivering events asynchronously
SCM/JIRA link daemon commented on JENKINS-22001 Do not solve JENKINS-19446 by delivering events asynchronously Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/AbstractItem.java core/src/main/java/hudson/model/Job.java test/src/test/java/hudson/model/ListViewTest.java http://jenkins-ci.org/commit/jenkins/00d27176f3a452e38bd0caafebe78c7bc2fa822f Log: FIXED JENKINS-22001 Simpler fix of JENKINS-19446 that does not introduce asynchronous behavior. Compare: https://github.com/jenkinsci/jenkins/compare/334ce1be691c...00d27176f3a4 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-19446) Deadlock while parallel deletion/rename of jobs
SCM/JIRA link daemon commented on JENKINS-19446 Deadlock while parallel deletion/rename of jobs Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/ListView.java core/src/main/java/jenkins/model/Jenkins.java http://jenkins-ci.org/commit/jenkins/3aa0dd5368444728b608bce9790e59983dabbc8a Log: JENKINS-19446 Saving Jenkins configuration in onRenamed/onDeleted is often overkill. This is already handled by ListView.Listener (other kinds of views are now responsible for their own listeners). And handled better—if there are no actual changes (because you have no such views, or they do not mention this job), there is no need to save. Also moving the actual saving in those remaining cases out of the lock on the ListView itself, just in case. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-22003) Null pointer on notifyCommit
jpschewe commented on JENKINS-22003 Null pointer on notifyCommit Correction, it is NOT triggering builds. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-19194) Recipients not being saved
A Bader commented on JENKINS-19194 Recipients not being saved @Alex Earl I am still seeing this issue with Jenkins v1.539 and Mailer version 1.8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-19446) Deadlock while parallel deletion/rename of jobs
dogfood commented on JENKINS-19446 Deadlock while parallel deletion/rename of jobs Integrated in jenkins_main_trunk #3204 JENKINS-19446 Saving Jenkins configuration in onRenamed/onDeleted is often overkill. (Revision 3aa0dd5368444728b608bce9790e59983dabbc8a) FIXED JENKINS-22001 Simpler fix of JENKINS-19446 that does not introduce asynchronous behavior. (Revision 00d27176f3a452e38bd0caafebe78c7bc2fa822f) Result = SUCCESS Jesse Glick : 3aa0dd5368444728b608bce9790e59983dabbc8a Files : core/src/main/java/jenkins/model/Jenkins.java core/src/main/java/hudson/model/ListView.java Jesse Glick : 00d27176f3a452e38bd0caafebe78c7bc2fa822f Files : test/src/test/java/hudson/model/ListViewTest.java core/src/main/java/hudson/model/AbstractItem.java core/src/main/java/hudson/model/Job.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-22003) Null pointer on notifyCommit
Mark Waite resolved JENKINS-22003 as Fixed Null pointer on notifyCommit I believe this has been fixed in https://github.com/jenkinsci/git-plugin/commit/46e39047abd016f6907819d4001cc2f4982a620f . That should be included in the next release of git-plugin, probably release 2.0.4. Change By: Mark Waite (28/Feb/14 11:07 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-21932) Job hangs if one of multiple triggered builds was aborted
ikedam commented on JENKINS-21932 Job hangs if one of multiple triggered builds was aborted It reproduced easily also in my environment. Amazing. It would require a fix in Jenkins core as @oleg_nenashev points. How I reproduce: Install parameterized-trigger plugin Create a node "slave1" from Manage Jenkins Manage Nodes New Node No need to launch that node. Create a free style project "downstream1". Check "Restrict where this project can be run" (this is displayed only when there are slaves) and enter "slave1" to "Label _expression_" Create a free style project "downstream2". Create a free style project "upstream" Add "Trigger/call builds on other projects" "downstream1,downstream2" for "Projects to build" Check Block until the triggered projects finish their builds Click "Build Now" of "upstream". Cancel the build of "downstream1" that should be pending. Result: "upstream" should finish, but actually does not finish. Environments: Windows 8 Jenkins 1.532.1 JDK 1.7.0_45 Parameterized Trigger plugin 2.22 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-21932) Job hangs if one of multiple triggered builds was aborted
ikedam assigned JENKINS-21932 to ikedam Job hangs if one of multiple triggered builds was aborted Change By: ikedam (28/Feb/14 11:20 PM) Assignee: huybrechts 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/groups/opt_out.
[JIRA] [jira] (JENKINS-22004) JIRA does NOT create new ticket for build failure for a new build project.(Create new issue plugin bug). Occurs when the new job build results are all failures
chris vecchione created JENKINS-22004 JIRA does NOT create new ticket for build failure for a new build project.(Create new issue plugin bug). Occurs when the new job build results are all failures Issue Type: Bug Assignee: Unassigned Components: jira Created: 28/Feb/14 11:20 PM Description: JIRA does NOT create new issue (ticket) for a new build job IF there are no build successes. In other words: 1) I create a new Jenkins free project (build job) 2) The first execution - build job #1 - fails. 3) JIRA does not create a ticket (Create jira issue plugin does not work). It seems I need a build successful first and manual JIRA build jobname synchronization on jira administrative site. Project: Jenkins Priority: Major Reporter: chris vecchione This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jira] (JENKINS-22004) JIRA does NOT create new ticket for build failure for a new build project.(Create new issue plugin bug). Occurs when the new job build results are all failures
chris vecchione commented on JENKINS-22004 JIRA does NOT create new ticket for build failure for a new build project.(Create new issue plugin bug). Occurs when the new job build results are all failures To add: the create jira issue plugin ONLY executes when the new jenkins build project: 1)had a previous build successful 2) and manually synched on jira administrative site This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [throttle-concurrents] (JENKINS-19986) Throttle Concurrent Builds plugin doesn't appear to work
jpschewe commented on JENKINS-19986 Throttle Concurrent Builds plugin doesnt appear to work I just upgraded to Jenkins 1.532.2 and Throttle Concurrent Builds 1.8.1 and I'm still seeing 2 jobs from the same category build at the same time on the same node when there is a limit of 1 job per node for the specified category. In this case one job is from a matrix job and one is a free-style project job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21309) Git plugins changes URL for Bitbucket is incorrect
Mark Waite resolved JENKINS-21309 as Fixed Git plugins changes URL for Bitbucket is incorrect As far as I can tell, this is fixed in git-client-plugin 1.6.3 and git-plugin 2.0.3. I'm not aware of any change which should have fixed it, but it seems to be fixed. I created a job using https://bitbucket.org/markewaite/git-client-plugin and confirmed that the bitbucket URL link for changes shows the individual changes as expected. Change By: Mark Waite (28/Feb/14 11:29 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-19194) Recipients not being saved
Alex Earl commented on JENKINS-19194 Recipients not being saved Ah, interesting, so its not the normal Mailer plugin that you are seeing the issue with? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-19194) Recipients not being saved
A Bader commented on JENKINS-19194 Recipients not being saved The only mail-related plugin I have installed is https://wiki.jenkins-ci.org/display/JENKINS/Mailer version 1.8. Seems like the normal one to me. My point is that I'm getting different behavior depending on the jenkins job type. In my Maven 2/3 jobs, I don't have the option of an email post-build action, only the "build settings" checkbox. This one fails to save the recipients list. In a free-style job there's no build settings section; there's an email post-build action. This one saves the recipients list, but doesn't appear to actually send emails. Hope that makes sense. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-19194) Recipients not being saved
Alex Earl commented on JENKINS-19194 Recipients not being saved Maven jobs use the MavenMailer class in the UI (https://github.com/jenkinsci/maven-plugin/blob/master/src/main/java/hudson/maven/reporters/MavenMailer.java), the "Email Notification" is the Mailer plugin, which uses a different UI setup. If you are seeing the issue with Maven jobs, then the issue is most likely with the MavenMailer for saving the recipients, not the Mailer plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-21554) NPE after Waiting for Jenkins to finish collecting data
Daniel Tehranian commented on JENKINS-21554 NPE after Waiting for Jenkins to finish collecting data Hi Juha, You're not using the DSL plugin to generate your jobs as well are you? Dan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [shelve-project-plugin] (JENKINS-8063) Seemingly harmless stacktrace when shelving/unshelving projects in Hudson 1.383 and 1.384
ben patterson assigned JENKINS-8063 to ben patterson Seemingly harmless stacktrace when shelving/unshelving projects in Hudson 1.383 and 1.384 Change By: ben patterson (01/Mar/14 1:18 AM) Assignee: ashlux benpatterson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [shelve-project-plugin] (JENKINS-8063) Seemingly harmless stacktrace when shelving/unshelving projects in Hudson 1.383 and 1.384
ben patterson started work on JENKINS-8063 Seemingly harmless stacktrace when shelving/unshelving projects in Hudson 1.383 and 1.384 Change By: ben patterson (01/Mar/14 1:18 AM) Status: Reopened InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [shelve-project-plugin] (JENKINS-8063) Seemingly harmless stacktrace when shelving/unshelving projects in Hudson 1.383 and 1.384
ben patterson commented on JENKINS-8063 Seemingly harmless stacktrace when shelving/unshelving projects in Hudson 1.383 and 1.384 Fix checked in; will close at next release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [shelve-project-plugin] (JENKINS-9169) Exception after shelving the project
ben patterson resolved JENKINS-9169 as Cannot Reproduce Exception after shelving the project Unable to reproduce. Stacktrace looks like it's from a Jenkins snapshot version. Closing this issue for now. Change By: ben patterson (01/Mar/14 1:22 AM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [shelve-project-plugin] (JENKINS-9169) Exception after shelving the project
ben patterson closed JENKINS-9169 as Cannot Reproduce Exception after shelving the project Change By: ben patterson (01/Mar/14 1:22 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [shelve-project-plugin] (JENKINS-20987) Shelve-Project Plugin - The shelved projects still appear under ALL view
ben patterson commented on JENKINS-20987 Shelve-Project Plugin - The shelved projects still appear under ALL view This issue should go away with a page refresh. Otherwise I'm unable to reproduce it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-22005) Repeating/Duplicating promotion parameters
Clecio Varjao created JENKINS-22005 Repeating/Duplicating promotion parameters Issue Type: Bug Assignee: Clecio Varjao Components: promoted-builds Created: 01/Mar/14 2:53 AM Description: When there is a job with multiple promotion processes, the parameters are getting mixed up among promotion processes. 1) Create a job (Job001) a) add Promotion Process (PROM0) i) check "Only when manually approved" criteria ii) add a String parameter (name: param_1, default_value: PROM0_v1) ii) add a String parameter (name: param_2, default_value: PROM0_v2) b) add Promotion Process (PROM1) i) check "Only when manually approved" criteria ii) add a String parameter (name: param_1, default_value: PROM1_v1) ii) add a String parameter (name: param_2, default_value: PROM1_v2) c) add Promotion Process (PROM2) i) check "Only when manually approved" criteria ii) add a String parameter (name: param_1, default_value: PROM2_v1) ii) add a String parameter (name: param_2, default_value: PROM2_v2) 2) Do a Build 3) Approve "PROM0" 4) Approve "PROM1" 5) BUG: PROM1 parameters will have duplicate parameter fields mixed up between PROM0 and PROM1 Environment: Since: 2.15 Project: Jenkins Priority: Minor Reporter: Clecio Varjao This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-22005) Repeating/Duplicating promotion parameters
Clecio Varjao resolved JENKINS-22005 as Fixed Repeating/Duplicating promotion parameters pending https://github.com/jenkinsci/promoted-builds-plugin/pull/39 Change By: Clecio Varjao (01/Mar/14 5:46 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-12410) Downstream jobs not associated with upstream parent job properly
ikedam commented on JENKINS-12410 Downstream jobs not associated with upstream parent job properly I could not reproduce the problem, too. Jenkins 1.532.1 + Email-ext 2.37.2 + Parameterized-trigger 2.22. What I tried: Run parameterized trigger without parameters as a publisher from multi-configuration project, and always send email to requester in the downstream. Run non-blocking parameterized trigger without parameters as a builder from multi-configuration project, and always send email to requester in the downstream. Run blocking parameterized trigger without parameters as a builder from multi-configuration project, and always send email to requester in the downstream. I think it is already resolved in some version: There is another ticket JENKINS-12300, which seems same to this and it is reported as resolved (I'm not sure how it is resolved). Current codes of email-ext seems completely different from that of Email-ext 2.28. I'll close this ticket as Resolved if there is no new reports in one month. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
