[JIRA] [core] (JENKINS-17715) Display Name is not shown
Philip Schiffer commented on JENKINS-17715 Display Name is not shown Same behaviour here too with 1.512 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scripttrigger] (JENKINS-17566) Severe polling error when using script trigger
thetaphi commented on JENKINS-17566 Severe polling error when using script trigger I have ScriptTrigger 0.23 running with Jenkins 1.512. Still the same issue. Sometimes it works (looks like it works after startup of Jenkins), but at some time it stops working and the above message is in the log. Unfortunately there is nothing else in Jenkin's main logs, so I have nothing else (like a stack trace). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cobertura] (JENKINS-8441) There should be a cobertura summary item on the build status page
sogabe assigned JENKINS-8441 to sogabe There should be a cobertura summary item on the build status page Change By: sogabe (27/Apr/13 10:57 AM) Assignee: stephenconnolly sogabe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cobertura] (JENKINS-8441) There should be a cobertura summary item on the build status page
SCM/JIRA link daemon commented on JENKINS-8441 There should be a cobertura summary item on the build status page Code changed in jenkins User: ssogabe Path: src/main/resources/hudson/plugins/cobertura/CoberturaBuildAction/summary.jelly src/main/resources/hudson/plugins/cobertura/CoberturaBuildAction/summary_ja.properties http://jenkins-ci.org/commit/cobertura-plugin/189f1729520c13675da6e598eb03142e8c0ee9c3 Log: FIXED JENKINS-8441 There should be a cobertura summary item on the build status page Compare: https://github.com/jenkinsci/cobertura-plugin/compare/60fd99a5cbdc...189f1729520c This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cobertura] (JENKINS-8441) There should be a cobertura summary item on the build status page
SCM/JIRA link daemon resolved JENKINS-8441 as Fixed There should be a cobertura summary item on the build status page Change By: SCM/JIRA link daemon (27/Apr/13 10:57 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] [git] (JENKINS-17763) Git plugin clean workspace blows away private maven repository
magnayn created JENKINS-17763 Git plugin clean workspace blows away private maven repository Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 27/Apr/13 11:01 AM Description: When you select "Clean repository workspace", this executes the equivalent of 'git -fdx' in $WORKSPACE If you have 'local maven repository' selected, then there is a maven repo in $WORKSPACE/.repository. So this option deletes the whole repo, which is not what is wanted. I'm not sure what the most reasonable fix is, though. Clearly 'git -fdx -e .repository' will probably work, but it's a bit... 'magic' Project: Jenkins Priority: Major Reporter: magnayn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cobertura] (JENKINS-9977) Cobertura results are not presented at the build specific page
sogabe resolved JENKINS-9977 as Duplicate Cobertura results are not presented at the build specific page Change By: sogabe (27/Apr/13 11:36 AM) 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] [copyartifact] (JENKINS-17606) Copy Artifact's fingerprinting creates second hudson.tasks.Fingerprinter_-FingerprintAction section with just the artifacts copied
Marc Sanfacon updated JENKINS-17606 Copy Artifacts fingerprinting creates second hudson.tasks.Fingerprinter_-FingerprintAction section with just the artifacts copied Change By: Marc Sanfacon (27/Apr/13 2:46 PM) Priority: Critical Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-11564) Line number anchors for jobName/number/consoleFull
David Langeland commented on JENKINS-11564 Line number anchors for jobName/number/consoleFull I would really, really appreciate this feature - being able to jump to a specifc line in the console output using an URL would be neat. Did you have any progress since your last update? Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17754) exception shown on saving empty tools
Sandro Felicioni assigned JENKINS-17754 to Sandro Felicioni exception shown on saving empty tools Change By: Sandro Felicioni (27/Apr/13 9:01 PM) Assignee: SandroFelicioni This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17754) exception shown on saving empty tools
Sandro Felicioni
commented on JENKINS-17754
exception shown on saving empty tools
Hi Viktor
Thanks for the report, I confirm the same behavior on MAC OS X (Lion). However the steps to reproduce the error were slightly different:
1. Install new Jenkins
2. Go to Configuring (e.g. http://localhost:8080/jenkins/configure), tick Tools Locations
3. Hit the add button under Tool Locations, but let the fields empty!
4. Click save/apply
Then I get a RuntimeException:
javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.tools.ToolLocationNodeProperty from {"locations":{"key":"","home":""}}
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:719)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [security] (JENKINS-17764) 'Trigger Builds Remotely' with ?token not working when Matrix Authorization Strategy is used
Stuart Montgomery
created JENKINS-17764
Trigger Builds Remotely with ?token not working when Matrix Authorization Strategy is used
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
security
Created:
27/Apr/13 11:25 PM
Description:
I have Global Security configured to use LDAP with "Project-based Matrix Authorization Strategy" enabled. Anonymous user has the "Job Build" privilege, and no other privileges.
I want an automated script to be able to trigger a build using the "Trigger Builds Remotely" feature, where I specify a "?token=token" value and the standard authentication should be bypassed, as long as the token value matches the one I set in the job's Configure page.
The documentation seems to indicate this should work:
https://wiki.jenkins-ci.org/display/JENKINS/Quick+and+Simple+Security
So specifically, I am expecting this HTTP request to work:
curl -i https://jenkinsHost/job/[ProjectName]/build?token=[token]
But I get
[~]$ curl -i https://jenkinsHost/job/ProjectName/build?token=test
HTTP/1.1 403 Forbidden
Date: Sat, 27 Apr 2013 23:17:03 GMT
Server: Winstone Servlet Engine v0.9.10
Content-Type: text/html;charset=UTF-8
Content-Length: 629
X-Powered-By: Servlet/2.5 (Winstone/0.9.10)
Set-Cookie: JSESSIONID.e9bc4765=e1f0a30b9f04b3740bae527a7822b2d5; Path=/; HttpOnly
Connection: close
htmlheadmeta http-equiv='refresh' content='1;url=""
script
window.location.replace('/login?from=%2Fjob%2FProjectName%2Fbuild%3Ftoken%3Dtest');/script
/head
body style='background-color:white; color:white;'
Authentication required
/body/html
When I DO use API authentication, the request works:
curl -i --username "test_user:API_KEY" https://hostname/job/ProjectName/build?token=test
But again, according to the documentation I think it is supposed to bypass the global authentication if ?token is present and matches the project token I configure. Why is this not working? What other information/logs can I provide?
Environment:
Jenkins 1.512, RedHat Linux. Also seeing this on 1.480.3 (current LTS release)
Project:
Jenkins
Labels:
jenkins
Priority:
Major
Reporter:
Stuart Montgomery
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [security] (JENKINS-17764) 'Trigger Builds Remotely' with ?token not working when Matrix Authorization Strategy is used
Stuart Montgomery
updated JENKINS-17764
Trigger Builds Remotely with ?token not working when Matrix Authorization Strategy is used
Change By:
Stuart Montgomery
(27/Apr/13 11:26 PM)
Description:
IhaveGlobalSecurityconfiguredtouseLDAPwithProject-basedMatrixAuthorizationStrategyenabled.AnonymoususerhastheJobBuildprivilege,andnootherprivileges.IwantanautomatedscripttobeabletotriggerabuildusingtheTriggerBuildsRemotelyfeature,whereIspecifya?token=[token]valueandthestandardauthenticationshouldbebypassed,aslongasthe[token]valuematchestheoneIsetinthejobsConfigurepage.Thedocumentationseemstoindicatethisshouldwork:https://wiki.jenkins-ci.org/display/JENKINS/Quick+and+Simple+SecuritySospecifically,IamexpectingthisHTTPrequesttowork:{noformat}curl-ihttps://jenkinsHost/job/
[
ProjectName
]
/build?token=
[token]
test
{noformat}ButIget{noformat}[~]$curl-ihttps://jenkinsHost/job/ProjectName/build?token=testHTTP/1.1403ForbiddenDate:Sat,27Apr201323:17:03GMTServer:WinstoneServletEnginev0.9.10Content-Type:text/html;charset=UTF-8Content-Length:629X-Powered-By:Servlet/2.5(Winstone/0.9.10)Set-Cookie:JSESSIONID.e9bc4765=e1f0a30b9f04b3740bae527a7822b2d5;Path=/;HttpOnlyConnection:closehtmlheadmetahttp-equiv=refreshcontent=1;url="">scriptwindow.location.replace(/login?from=%2Fjob%2FProjectName%2Fbuild%3Ftoken%3Dtest);/script/headbodystyle=background-color:white;color:white;Authenticationrequired/body/html{noformat}WhenIDOuseAPIauthentication,therequestworks:{noformat}curl-i--usernametest_user:API_KEYhttps://hostname/job/ProjectName/build?token=test{noformat}Butagain,accordingtothedocumentationIthinkitissupposedtobypasstheglobalauthenticationif?tokenispresentandmatchestheprojecttokenIconfigure.Whyisthisnotworking?Whatotherinformation/logscanIprovide?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [security] (JENKINS-17764) 'Trigger Builds Remotely' with ?token not working when Matrix Authorization Strategy is used
Stuart Montgomery
updated JENKINS-17764
Trigger Builds Remotely with ?token not working when Matrix Authorization Strategy is used
Change By:
Stuart Montgomery
(27/Apr/13 11:29 PM)
Description:
IhaveGlobalSecurityconfiguredtouseLDAPwithProject-basedMatrixAuthorizationStrategyenabled.AnonymoususerhastheJobBuildprivilege,andnootherprivileges
(inparticular,theanonymoususerdoesNOThaveOverallReadprivilege,sinceIdontwanteveryonetobeabletoviewthelistofjobsandothergeneralinformation)
.IwantanautomatedscripttobeabletotriggerabuildusingtheTriggerBuildsRemotelyfeature,whereIspecifya?token=[token]valueandthestandardauthenticationshouldbebypassed,aslongasthe[token]valuematchestheoneIsetinthejobsConfigurepage.Thedocumentationseemstoindicatethisshouldwork:https://wiki.jenkins-ci.org/display/JENKINS/Quick+and+Simple+SecuritySospecifically,IamexpectingthisHTTPrequesttowork:{noformat}curl-ihttps://jenkinsHost/job/ProjectName/build?token=test{noformat}ButIget{noformat}[~]$curl-ihttps://jenkinsHost/job/ProjectName/build?token=testHTTP/1.1403ForbiddenDate:Sat,27Apr201323:17:03GMTServer:WinstoneServletEnginev0.9.10Content-Type:text/html;charset=UTF-8Content-Length:629X-Powered-By:Servlet/2.5(Winstone/0.9.10)Set-Cookie:JSESSIONID.e9bc4765=e1f0a30b9f04b3740bae527a7822b2d5;Path=/;HttpOnlyConnection:closehtmlheadmetahttp-equiv=refreshcontent=1;url="">scriptwindow.location.replace(/login?from=%2Fjob%2FProjectName%2Fbuild%3Ftoken%3Dtest);/script/headbodystyle=background-color:white;color:white;Authenticationrequired/body/html{noformat}WhenIDOuseAPIauthentication,therequestworks:{noformat}curl-i--usernametest_user:API_KEYhttps://hostname/job/ProjectName/build?token=test{noformat}Butagain,accordingtothedocumentationIthinkitissupposedtobypasstheglobalauthenticationif?tokenispresentandmatchestheprojecttokenIconfigure.Whyisthisnotworking?Whatotherinformation/logscanIprovide?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving 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-17759) Email notification source tries to indent HTML from console output
SCM/JIRA link daemon commented on JENKINS-17759 Email notification source tries to indent HTML from console output Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/plugins/CssInliner.java src/test/java/hudson/plugins/emailext/plugins/CssInlinerTest.java http://jenkins-ci.org/commit/email-ext-plugin/fd016daf6695875f03320474848000201a4409c8 Log: Fixed JENKINS-17759 Turned off pretty printing in the CssInliner. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17759) Email notification source tries to indent HTML from console output
Alex Earl resolved JENKINS-17759 as Fixed Email notification source tries to indent HTML from console output Turned off pretty printing in the css inliner (jsoup). Change By: Alex Earl (28/Apr/13 4:19 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] [email-ext] (JENKINS-17742) Pick Up Committer from Upstream Job
Alex Earl resolved JENKINS-17742 as Wont Fix Pick Up Committer from Upstream Job This can be done now with a SCRIPT content token in the recipients. Change By: Alex Earl (28/Apr/13 4:38 AM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17675) Allow the Pre-send script to be a file or call a scriptler script
Alex Earl resolved JENKINS-17675 as Fixed Allow the Pre-send script to be a file or call a scriptler script Allow content tokens to be used in the pre-send script. Change By: Alex Earl (28/Apr/13 4:41 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] [m2release] (JENKINS-17765) add to CLI the ability of release project using M2 Release Plugin
morlajb created JENKINS-17765 add to CLI the ability of release project using M2 Release Plugin Issue Type: Improvement Assignee: teilo Components: m2release Created: 28/Apr/13 4:45 AM Description: will be great to build a 'nightly' release to make sure it works ... Project: Jenkins Priority: Major Reporter: morlajb This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
