[JIRA] (JENKINS-12573) CVS plugin version 2.0 checkout failed: Can't parse date/time
[ https://issues.jenkins-ci.org/browse/JENKINS-12573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160815#comment-160815 ] Simon Strauch commented on JENKINS-12573: - The update seems to work for me. CVS checkout with numeric timezone (+0200) does work on my system. > CVS plugin version 2.0 checkout failed: Can't parse date/time > - > > Key: JENKINS-12573 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12573 > Project: Jenkins > Issue Type: Bug > Components: cvs >Affects Versions: current > Environment: Jenkins ver. 1.424.2 > Jenkins CVS Plug-in 2.0 >Reporter: Eric Co >Assignee: Michael Clarke >Priority: Blocker > Fix For: current > > Attachments: screenshot-1.jpg > > > After I upgraded the CVS plugin 2.0, got the following error: > cvs checkout -P -D 2012-01-30 16:37:44HKT -d abc abc > cvs [checkout aborted]: Can't parse date/time: 2012-01-30 16:37:44HKT -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13227) CVS plugin 2.1 does not detect changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160816#comment-160816 ] Michael Clarke commented on JENKINS-13227: -- Can you try again with the V2.2 of the CVS plugin? We've changed how we format timestamps for this version but, whilst your email thread raises the timestamp format as the potential cause of the failure, I'd expect CVS to throw an exception on failing to parse the timestamp and show a stacktrace in the polling log. If this doesn't fix it, could you confirm which version of CVS server you use and also send me a sample output of the following rlog command run from your command line (obscuring any sensitive output where needed)? if you're using a branch/tag: cvs rlog -d"22 Mar 2012 09:26:21 -0400<27 Mar 2012 12:00:00 -0400" -S -rlocationName moduleName (where locationName is your branch/tag name and moduleName is the name of the CVS module being polled) if you're using head:cvs rlog -d"22 Mar 2012 09:26:21 -0400<27 Mar 2012 12:00:00 -0400" -S moduleName (where moduleName is the name of the module being polled) Thanks > CVS plugin 2.1 does not detect changes > -- > > Key: JENKINS-13227 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13227 > Project: Jenkins > Issue Type: Bug > Components: cvs >Reporter: Guillaume Bilodeau > Labels: cvs > > As presented in the user group: > https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4 > We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS > repository for a few weeks now, without any problems. The CVS plugin (v1.6) > was using the local cvsnt install. > We've since upgraded the CVS plugin to version 2.1 (by manually pinning the > plugin) and since then, CVS changes are not detected. The CVS polling log is > triggered properly, tons of "cvs rlog" instructions are sent, but at the end > "No changes" is displayed. > Using CVS plugin 1.6 the cvs polling command looked like this (executed at > 5:26:21 PM EDT): > cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D > "Thursday, March 22, 2012 9:26:21 PM UTC" > Using CVS plugin 2.1, the last cvs checkout command looked like this > (executed at 11:56:16 AM EDT): > cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 > 11:56:16 EDT -d portailInt portailInt > We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13239) ThinBackup puts Jenkins into Shutdown (repeatedly) . . . revisited
[ https://issues.jenkins-ci.org/browse/JENKINS-13239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-13239 started by Thomas Fürer. > ThinBackup puts Jenkins into Shutdown (repeatedly) . . . revisited > -- > > Key: JENKINS-13239 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13239 > Project: Jenkins > Issue Type: Bug > Components: thinBackup >Affects Versions: current > Environment: Win7, approx 100 Projects, incremental backups weekdays, > full backup Sunday >Reporter: Frank Merrow >Assignee: Thomas Fürer > Attachments: shutdown.log > > > One of my fellow workers claimed thinBackup was taking Jenkins down, sure > enough I found that the case myself this morning. > Shutdown could not be cancelled (it would go down, but immediately be > reasserted). ThinBackup had some messages about waiting for quiet mode, but > there also seemed to be an exception related to cancelling shutdown, scanning > with my non-Java eye, it wasn't clear it the exception was thinBackup related > or not. > End of Jenkins log provided -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12510) Custom xcodebuild arguments values are not persisted
[
https://issues.jenkins-ci.org/browse/JENKINS-12510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160817#comment-160817
]
Arnaud Héritier commented on JENKINS-12510:
---
I'm sorry for this bug, I'm overwhelmed these days.
I will push a bugfix release in few minutes.
> Custom xcodebuild arguments values are not persisted
>
>
> Key: JENKINS-12510
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12510
> Project: Jenkins
> Issue Type: Bug
> Components: xcode
>Affects Versions: current
>Reporter: Richard King
>Assignee: Arnaud Héritier
>Priority: Blocker
>
> If I add a custom xcode config parameter such as SELECTED_LOCALE=en and
> click save, the custom parameter is not persisted. When I edit the project
> config again the parameter isnt there.
> My config.xml file has the following entry for the XCode plugin:
>
>
> true
> false
> In-House
> NTC
>
>
>
> ${WORKSPACE}/build/In-House-iphoneos
>
>
> SELECTED_LOCALE=${LOCALE}
> In-House
>
>
> 2.6
> 2.6
> true
> false
> ${HOME}/Library/Keychains/login.keychain
>
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13015) "Custom xcodebuild arguments" field doesn't save arguments
[ https://issues.jenkins-ci.org/browse/JENKINS-13015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Héritier closed JENKINS-13015. - Resolution: Duplicate Duplicates JENKINS-12510 Will be fixed in 1.3.1 > "Custom xcodebuild arguments" field doesn't save arguments > -- > > Key: JENKINS-13015 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13015 > Project: Jenkins > Issue Type: Bug > Components: xcode >Affects Versions: current > Environment: Jenkins 1.454, xCode integration plugin 1.3, OS: Ubuntu > server 10.04 >Reporter: Alexander Khozya > > NOTE: this issue causes broken builds on some app configurations > 1. Create freestyle job > 2. Setup project > 3. Enter something into "Custom xcodebuild arguments" for example "-arch i386" > 4. Apply and Save > 5. Don't go anywhere from this page and click Build - project will build OK > 6. Go to main page > 7. Go to project>Configure > Actual result: "Custom xcodebuild arguments" field is empty > Expected result: there is "-arch i386" parameter -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13156) Changes in XCode 4.3 make the plugin unusable out of the box
[ https://issues.jenkins-ci.org/browse/JENKINS-13156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Héritier closed JENKINS-13156. - Resolution: Not A Defect Please reopen if you have a beter idea than the doc I did > Changes in XCode 4.3 make the plugin unusable out of the box > > > Key: JENKINS-13156 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13156 > Project: Jenkins > Issue Type: Bug > Components: xcode > Environment: Mac OSX 10.7.3, XCode 4.3, Jenkins 1.456, XCode Plugin > 1.3 >Reporter: Allen Fisher > > Apple has changed how Xcode is distributed. With XC4.3, the /Developer folder > is now inside the app bundle (and possibly reorganized, I can't tell for > sure). On a fresh install of the OS with the latest version of XCode, Jenkins > throws the following error when trying to build: > Started by user anonymous > Building in workspace /Users/foo/Projects/Jenkins/fooapp > Working directory is /Users/foo/Projects/Jenkins/fooapp/Expat/Build/XCode. > [XCode] $ /usr/bin/xcodebuild -version > Error: No developer directory found at /Developer. Run /usr/bin/xcode-select > to update the developer directory path. > FATAL: Check your XCode installation. Jenkins cannot retrieve its version. > Build step 'XCode' marked build as failure > Finished: FAILURE -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12800) Can't add xcodebuild parameters including whitespace
[ https://issues.jenkins-ci.org/browse/JENKINS-12800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160820#comment-160820 ] Arnaud Héritier commented on JENKINS-12800: --- I can see the problem in the code because we split using space character. https://github.com/jenkinsci/xcode-plugin/blob/master/src/main/java/au/com/rayh/XCodeBuilder.java#L392 I don't yet know how to solve it. Perhaps using a most complexe regexp to not do it for spaces between characters ' or " but it's not easy. > Can't add xcodebuild parameters including whitespace > > > Key: JENKINS-12800 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12800 > Project: Jenkins > Issue Type: Bug > Components: xcode >Affects Versions: current >Reporter: Sven Weidauer > > I am trying to pass the parameter 'CODE_SIGN_IDENTITY="iPhone Distribution"' > to xcodebuild via the new 'custom xcodebuild arguments' field. But no matter > how I quote this it always gets split into two paramters at the whitespace > which makes the build fail. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12573) CVS plugin version 2.0 checkout failed: Can't parse date/time
[ https://issues.jenkins-ci.org/browse/JENKINS-12573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160821#comment-160821 ] Joern Muehlencord commented on JENKINS-12573: - also confirm from my end it is working > CVS plugin version 2.0 checkout failed: Can't parse date/time > - > > Key: JENKINS-12573 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12573 > Project: Jenkins > Issue Type: Bug > Components: cvs >Affects Versions: current > Environment: Jenkins ver. 1.424.2 > Jenkins CVS Plug-in 2.0 >Reporter: Eric Co >Assignee: Michael Clarke >Priority: Blocker > Fix For: current > > Attachments: screenshot-1.jpg > > > After I upgraded the CVS plugin 2.0, got the following error: > cvs checkout -P -D 2012-01-30 16:37:44HKT -d abc abc > cvs [checkout aborted]: Can't parse date/time: 2012-01-30 16:37:44HKT -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12510) Custom xcodebuild arguments values are not persisted
[
https://issues.jenkins-ci.org/browse/JENKINS-12510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160822#comment-160822
]
SCM/JIRA link daemon commented on JENKINS-12510:
Code changed in jenkins
User: Arnaud Héritier
Path:
src/main/java/au/com/rayh/XCodeBuilder.java
http://jenkins-ci.org/commit/xcode-plugin/45f6c393ee14e2c44525c4e792bc96f8eca8ff4d
Log:
JENKINS-12510 : Custom xcodebuild arguments values are not persisted
> Custom xcodebuild arguments values are not persisted
>
>
> Key: JENKINS-12510
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12510
> Project: Jenkins
> Issue Type: Bug
> Components: xcode
>Affects Versions: current
>Reporter: Richard King
>Assignee: Arnaud Héritier
>Priority: Blocker
>
> If I add a custom xcode config parameter such as SELECTED_LOCALE=en and
> click save, the custom parameter is not persisted. When I edit the project
> config again the parameter isnt there.
> My config.xml file has the following entry for the XCode plugin:
>
>
> true
> false
> In-House
> NTC
>
>
>
> ${WORKSPACE}/build/In-House-iphoneos
>
>
> SELECTED_LOCALE=${LOCALE}
> In-House
>
>
> 2.6
> 2.6
> true
> false
> ${HOME}/Library/Keychains/login.keychain
>
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12510) Custom xcodebuild arguments values are not persisted
[
https://issues.jenkins-ci.org/browse/JENKINS-12510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Héritier resolved JENKINS-12510.
---
Resolution: Fixed
A version 1.3.1 will be available in the update center.
Sorry for the long delay to fix a stupid bug like this.
Take care that there is another bug on this field (JENKINS-12800) that doesn't
allow it to use spaces in parameter values even if you escape it. I don't have
the time to investigate and find a fix for now.
> Custom xcodebuild arguments values are not persisted
>
>
> Key: JENKINS-12510
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12510
> Project: Jenkins
> Issue Type: Bug
> Components: xcode
>Affects Versions: current
>Reporter: Richard King
>Assignee: Arnaud Héritier
>Priority: Blocker
>
> If I add a custom xcode config parameter such as SELECTED_LOCALE=en and
> click save, the custom parameter is not persisted. When I edit the project
> config again the parameter isnt there.
> My config.xml file has the following entry for the XCode plugin:
>
>
> true
> false
> In-House
> NTC
>
>
>
> ${WORKSPACE}/build/In-House-iphoneos
>
>
> SELECTED_LOCALE=${LOCALE}
> In-House
>
>
> 2.6
> 2.6
> true
> false
> ${HOME}/Library/Keychains/login.keychain
>
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10197) Matrix jobs default to "locked" (and are difficult to delete)
[
https://issues.jenkins-ci.org/browse/JENKINS-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160824#comment-160824
]
Spencer Oliver commented on JENKINS-10197:
--
This seems to be fixed in 1.456
> Matrix jobs default to "locked" (and are difficult to delete)
> -
>
> Key: JENKINS-10197
> URL: https://issues.jenkins-ci.org/browse/JENKINS-10197
> Project: Jenkins
> Issue Type: Bug
> Components: core
>Affects Versions: current
> Environment: 1.418, 1.434
>Reporter: Tom Rini
>Assignee: abayer
>Priority: Critical
>
> With a matrix job now when it completes it defaults to being a "keep forever"
> type build. Only by deleting the current job can a previous job be deleted,
> in some cases.
> {noformat}
> (09:36:12 AM) Tartarus: kohsuke: With matrix jobs and 1.418 I'm seeing all of
> my jobs default to being locked, didn't see this with 1.409, any ideas?
> (09:36:32 AM) kohsuke: probably related to the partial rebuild support. Any
> ticket for this?
> (09:36:54 AM) Tartarus: Hadn't filed one yet
> (09:37:18 AM) kohsuke: Would you please? I don't think I can get it right
> now, but I don't want to forget
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10319) Ability to change the name "Compiler" as seen in a lot of the displays
[ https://issues.jenkins-ci.org/browse/JENKINS-10319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160825#comment-160825 ] SCM/JIRA link daemon commented on JENKINS-10319: Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/warnings/parser/AcuCobolParser.java src/main/java/hudson/plugins/warnings/parser/AntJavacParser.java src/main/java/hudson/plugins/warnings/parser/ArmccCompilerParser.java src/main/java/hudson/plugins/warnings/parser/BuckminsterParser.java src/main/java/hudson/plugins/warnings/parser/CoolfluxChessccParser.java src/main/java/hudson/plugins/warnings/parser/DoxygenParser.java src/main/java/hudson/plugins/warnings/parser/EclipseParser.java src/main/java/hudson/plugins/warnings/parser/ErlcParser.java src/main/java/hudson/plugins/warnings/parser/FlexSDKParser.java src/main/java/hudson/plugins/warnings/parser/Gcc4CompilerParser.java src/main/java/hudson/plugins/warnings/parser/Gcc4LinkerParser.java src/main/java/hudson/plugins/warnings/parser/GccParser.java src/main/java/hudson/plugins/warnings/parser/GhsMultiParser.java src/main/java/hudson/plugins/warnings/parser/GnatParser.java src/main/java/hudson/plugins/warnings/parser/IarParser.java src/main/java/hudson/plugins/warnings/parser/IntelCParser.java src/main/java/hudson/plugins/warnings/parser/InvalidsParser.java src/main/java/hudson/plugins/warnings/parser/JavacParser.java src/main/java/hudson/plugins/warnings/parser/MsBuildParser.java src/main/java/hudson/plugins/warnings/parser/P4Parser.java src/main/java/hudson/plugins/warnings/parser/ParserRegistry.java src/main/java/hudson/plugins/warnings/parser/PhpParser.java src/main/java/hudson/plugins/warnings/parser/PuppetLintParser.java src/main/java/hudson/plugins/warnings/parser/RobocopyParser.java src/main/java/hudson/plugins/warnings/parser/SunCParser.java src/main/java/hudson/plugins/warnings/parser/TiCcsParser.java src/main/java/hudson/plugins/warnings/parser/TnsdlParser.java src/main/java/hudson/plugins/warnings/parser/YuiCompressorParser.java src/test/java/hudson/plugins/warnings/parser/ParserRegistryIntegrationTest.java src/test/java/hudson/plugins/warnings/parser/ParserRegistryTest.java http://jenkins-ci.org/commit/warnings-plugin/b416ca53c57a8bab3f4e5e5bb61279f030d3da20 Log: [JENKINS-10319] Eat your own dogfood: use extension point to register all parsers. Compare: https://github.com/jenkinsci/warnings-plugin/compare/71bfd87...b416ca5 > Ability to change the name "Compiler" as seen in a lot of the displays > -- > > Key: JENKINS-10319 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10319 > Project: Jenkins > Issue Type: New Feature > Components: warnings >Reporter: Nigel Robbins >Assignee: Ulli Hafner >Priority: Minor > Attachments: compilerWarningsBuild.png, compilerWarningsIcon.png, > compilerWarningsList.png, compilerWarningsTrend.png > > > Hi, > Would it be possible to configure the label "Compiler Warnings". > I am using the Warnings plugin to show FlawFinder issues. > Seeing text like "FlawFinder Warnings" or maybe "FlawFinder Issues" would > enhance my display. > Can the parser name (e.g. FlawFinder in my case) be used instead of the text > "Compiler" ? > Or, maybe the ability to change the label "Compiler Warnings" to something > else ? > I can see the text "Compiler Warnings" in a number of places which I've > attached screenshots of. The "Compiler Warnings" text may also appear > elsewhere. > Great plugin by the way ! > Many thanks, > Nigel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10319) Ability to change the name "Compiler" as seen in a lot of the displays
[ https://issues.jenkins-ci.org/browse/JENKINS-10319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160826#comment-160826 ] dogfood commented on JENKINS-10319: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_warnings #371|http://ci.jenkins-ci.org/job/plugins_warnings/371/] Result = SUCCESS > Ability to change the name "Compiler" as seen in a lot of the displays > -- > > Key: JENKINS-10319 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10319 > Project: Jenkins > Issue Type: New Feature > Components: warnings >Reporter: Nigel Robbins >Assignee: Ulli Hafner >Priority: Minor > Attachments: compilerWarningsBuild.png, compilerWarningsIcon.png, > compilerWarningsList.png, compilerWarningsTrend.png > > > Hi, > Would it be possible to configure the label "Compiler Warnings". > I am using the Warnings plugin to show FlawFinder issues. > Seeing text like "FlawFinder Warnings" or maybe "FlawFinder Issues" would > enhance my display. > Can the parser name (e.g. FlawFinder in my case) be used instead of the text > "Compiler" ? > Or, maybe the ability to change the label "Compiler Warnings" to something > else ? > I can see the text "Compiler Warnings" in a number of places which I've > attached screenshots of. The "Compiler Warnings" text may also appear > elsewhere. > Great plugin by the way ! > Many thanks, > Nigel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13243) Do not replace slashes in URLs with backslashes on Windows
Henrik Skupin created JENKINS-13243: --- Summary: Do not replace slashes in URLs with backslashes on Windows Key: JENKINS-13243 URL: https://issues.jenkins-ci.org/browse/JENKINS-13243 Project: Jenkins Issue Type: Bug Components: xshell Affects Versions: current Environment: Can be reproduced on any Windows platform Reporter: Henrik Skupin When you call a script which expects an URL as parameter, the slashes will also be converted to backslashes. It results in a broken parameter for the build. So on Windows the plugin should not convert parameters which contain URLs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13244) Improve logic for shell script completion
Henrik Skupin created JENKINS-13244: --- Summary: Improve logic for shell script completion Key: JENKINS-13244 URL: https://issues.jenkins-ci.org/browse/JENKINS-13244 Project: Jenkins Issue Type: Bug Components: xshell Affects Versions: current Environment: This issue applies to all platforms Reporter: Henrik Skupin Currently you can specify a script to call by simply removing the extension and XShell will automatically add .cmd on Windows. Not sure why .sh is not getting added on Linux because it should be mostly the default extension for bash scripts. Also would it be possible to not only add the default extension but also check for alternatives? Batch files on Windows have a .cmd extension nowadays, and not sure what options exist on Linux. So would be great if the plugin could support multiple extensions, select the best match or fails when executing the shell if multiple matches exist which can't be resolved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10319) Ability to change the name "Compiler" as seen in a lot of the displays
[ https://issues.jenkins-ci.org/browse/JENKINS-10319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160827#comment-160827 ] Ulli Hafner commented on JENKINS-10319: --- Nigel, do you think the configuration of the graphs (stored in the users cookie) on the build page should be also done per graph? I.e., if you have a Java and C++ Parser, should the two graphs use the same configuration (type, size, etc.)? I think configuring each graph makes more sense to me... > Ability to change the name "Compiler" as seen in a lot of the displays > -- > > Key: JENKINS-10319 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10319 > Project: Jenkins > Issue Type: New Feature > Components: warnings >Reporter: Nigel Robbins >Assignee: Ulli Hafner >Priority: Minor > Attachments: compilerWarningsBuild.png, compilerWarningsIcon.png, > compilerWarningsList.png, compilerWarningsTrend.png > > > Hi, > Would it be possible to configure the label "Compiler Warnings". > I am using the Warnings plugin to show FlawFinder issues. > Seeing text like "FlawFinder Warnings" or maybe "FlawFinder Issues" would > enhance my display. > Can the parser name (e.g. FlawFinder in my case) be used instead of the text > "Compiler" ? > Or, maybe the ability to change the label "Compiler Warnings" to something > else ? > I can see the text "Compiler Warnings" in a number of places which I've > attached screenshots of. The "Compiler Warnings" text may also appear > elsewhere. > Great plugin by the way ! > Many thanks, > Nigel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10319) Ability to change the name "Compiler" as seen in a lot of the displays
[ https://issues.jenkins-ci.org/browse/JENKINS-10319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160828#comment-160828 ] Nigel Robbins commented on JENKINS-10319: - Hi Ulli, Yes, I agree, being able to configure each graph would be better. Maybe have the same defaults of 500 x 200 (Width x Height) but the ability to change. Thanks, Nigel > Ability to change the name "Compiler" as seen in a lot of the displays > -- > > Key: JENKINS-10319 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10319 > Project: Jenkins > Issue Type: New Feature > Components: warnings >Reporter: Nigel Robbins >Assignee: Ulli Hafner >Priority: Minor > Attachments: compilerWarningsBuild.png, compilerWarningsIcon.png, > compilerWarningsList.png, compilerWarningsTrend.png > > > Hi, > Would it be possible to configure the label "Compiler Warnings". > I am using the Warnings plugin to show FlawFinder issues. > Seeing text like "FlawFinder Warnings" or maybe "FlawFinder Issues" would > enhance my display. > Can the parser name (e.g. FlawFinder in my case) be used instead of the text > "Compiler" ? > Or, maybe the ability to change the label "Compiler Warnings" to something > else ? > I can see the text "Compiler Warnings" in a number of places which I've > attached screenshots of. The "Compiler Warnings" text may also appear > elsewhere. > Great plugin by the way ! > Many thanks, > Nigel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13245) Build not starting directly: pending - Waiting for next available executor on ...
Cees Bos created JENKINS-13245: -- Summary: Build not starting directly: pending - Waiting for next available executor on ... Key: JENKINS-13245 URL: https://issues.jenkins-ci.org/browse/JENKINS-13245 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Reporter: Cees Bos Priority: Critical Last Saterday we upgraded from 1.451 to 1.456 Sometimes when we trigger a job it comes in the queue with the message: (pending - Waiting for next available executor on .. servername ..) This even happens when the slave is totally idle, the job can start directly. After waiting for a minute it just starts ... Nothings helps to speed up the execution process -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10840) Maven "module" shows as running after build is aborted.
[ https://issues.jenkins-ci.org/browse/JENKINS-10840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160829#comment-160829 ] Ulli Hafner commented on JENKINS-10840: --- I can confirm that issue. Even after a build failed, some modules still 'blink' in order to indicate that they are still building. > Maven "module" shows as running after build is aborted. > --- > > Key: JENKINS-10840 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10840 > Project: Jenkins > Issue Type: Bug > Components: maven2 > Environment: Jenkins 1.418 >Reporter: Christian Höltje > > I have a Maven 2 job that has a single 'module'. It is set to auto-abort if > it lasts more than 15 minutes. > If it does abort, then the module for that build shows still running for > example, I have some that say the module has been running for days. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9741) Copy artifact loses file permissions
[ https://issues.jenkins-ci.org/browse/JENKINS-9741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160830#comment-160830 ] Henrik Skupin commented on JENKINS-9741: So this is still not working with version 1.21 installed. I have to copy various shell scripts from the master to nodes. Each of those scripts looses the executable permission and as result the build fails. Is there a chance to get this finally fixed? > Copy artifact loses file permissions > > > Key: JENKINS-9741 > URL: https://issues.jenkins-ci.org/browse/JENKINS-9741 > Project: Jenkins > Issue Type: Bug > Components: copyartifact > Environment: SLES 11.2, Jenkins 1.411 >Reporter: Angela Johansson >Assignee: Kohsuke Kawaguchi > > When copying an executable file, the copied file is not executable, that is > to say parts of the file permissions are lost. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13227) CVS plugin 2.1 does not detect changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160831#comment-160831 ] Guillaume Bilodeau commented on JENKINS-13227: -- Thanks for taking a look at this. CVS server is 1.11.22. I've upgraded to CVS plugin 2.2 and the behaviour is the same. Here is the output of the command: *** D:\Projets\jdevws\portailInt>cvs rlog -d"22 Mar 2012 09:26:21 -0400<27 Mar 2012 12:00:00 -0400" -S -rd-chg00014229_op_brc_preimp-op-2012-02-27 portailInt cvs rlog: Logging portailInt *** I suppose this should have provided more information. Maybe there's an error in the command itself - sorry I'm not familiar with CVS to see any... > CVS plugin 2.1 does not detect changes > -- > > Key: JENKINS-13227 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13227 > Project: Jenkins > Issue Type: Bug > Components: cvs >Reporter: Guillaume Bilodeau > Labels: cvs > > As presented in the user group: > https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4 > We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS > repository for a few weeks now, without any problems. The CVS plugin (v1.6) > was using the local cvsnt install. > We've since upgraded the CVS plugin to version 2.1 (by manually pinning the > plugin) and since then, CVS changes are not detected. The CVS polling log is > triggered properly, tons of "cvs rlog" instructions are sent, but at the end > "No changes" is displayed. > Using CVS plugin 1.6 the cvs polling command looked like this (executed at > 5:26:21 PM EDT): > cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D > "Thursday, March 22, 2012 9:26:21 PM UTC" > Using CVS plugin 2.1, the last cvs checkout command looked like this > (executed at 11:56:16 AM EDT): > cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 > 11:56:16 EDT -d portailInt portailInt > We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12585) ACCESSS: LDAP:PMA Login authed users accounts switch
[ https://issues.jenkins-ci.org/browse/JENKINS-12585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160832#comment-160832 ] Christian Höltje commented on JENKINS-12585: I have the same issue. One user can hit refresh repeatedly and get different users or even logged out. My setup is: Jenkins 1.456 JRE 7u3 Plugins of interest: Role-based Authorization Strategy Authentication: LDAP > ACCESSS: LDAP:PMA Login authed users accounts switch > -- > > Key: JENKINS-12585 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12585 > Project: Jenkins > Issue Type: Bug > Components: security >Affects Versions: current > Environment: Mac OSX: 10.6.8 Desktop > Java version: 1.6.0_29 > Access Control > * Security Realm: LDAP > * Authorization: Project-based Matrix Authorization Strategy > Jenkins: 1.448 > Apache > * Server version: Apache/2.2.17 (Unix) > * Server built: Dec 1 2010 09:58:15 >Reporter: guillermo c >Priority: Critical > > Running Jenkins behind Apache: mod_proxy with HTTPS > https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Apache > So our setup is > Open Directory group > jenkins-admin - Jenkins Admins all > dev-group-a - Developers can view kick off builds > Project-based Matrix Authorization Strategy > Admin all checked > dev-group-a checked: Overall:Read Job:Read,Build Run:Update > dev-group-b checked: Overall:Read Job:Read > issue is I'm an admin and random developer will login and see that there user > id is mine and can admin jenkins. > there has been reported cases that developer A will login and actually be > reported by jenkins as Developer B > were they can no longer trigger CI builds > My biggest concern is when users login and are reporting as admins and have > full access to jenkins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12585) SECURITY: LDAP authenticated users switch accounts randomly
[ https://issues.jenkins-ci.org/browse/JENKINS-12585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Höltje updated JENKINS-12585: --- Summary: SECURITY: LDAP authenticated users switch accounts randomly (was: ACCESSS: LDAP:PMA Login authed users accounts switch ) > SECURITY: LDAP authenticated users switch accounts randomly > --- > > Key: JENKINS-12585 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12585 > Project: Jenkins > Issue Type: Bug > Components: security >Affects Versions: current > Environment: Mac OSX: 10.6.8 Desktop > Java version: 1.6.0_29 > Access Control > * Security Realm: LDAP > * Authorization: Project-based Matrix Authorization Strategy > Jenkins: 1.448 > Apache > * Server version: Apache/2.2.17 (Unix) > * Server built: Dec 1 2010 09:58:15 >Reporter: guillermo c >Priority: Critical > > Running Jenkins behind Apache: mod_proxy with HTTPS > https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Apache > So our setup is > Open Directory group > jenkins-admin - Jenkins Admins all > dev-group-a - Developers can view kick off builds > Project-based Matrix Authorization Strategy > Admin all checked > dev-group-a checked: Overall:Read Job:Read,Build Run:Update > dev-group-b checked: Overall:Read Job:Read > issue is I'm an admin and random developer will login and see that there user > id is mine and can admin jenkins. > there has been reported cases that developer A will login and actually be > reported by jenkins as Developer B > were they can no longer trigger CI builds > My biggest concern is when users login and are reporting as admins and have > full access to jenkins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12585) SECURITY: LDAP authenticated users switch accounts randomly
[ https://issues.jenkins-ci.org/browse/JENKINS-12585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160832#comment-160832 ] Christian Höltje edited comment on JENKINS-12585 at 3/27/12 2:03 PM: - I have the same issue. One user can hit refresh repeatedly and get different users or even logged out and then back in! My setup is: Jenkins 1.456 JRE 7u3 Plugins of interest: Role-based Authorization Strategy Authentication: LDAP was (Author: docwhat): I have the same issue. One user can hit refresh repeatedly and get different users or even logged out. My setup is: Jenkins 1.456 JRE 7u3 Plugins of interest: Role-based Authorization Strategy Authentication: LDAP > SECURITY: LDAP authenticated users switch accounts randomly > --- > > Key: JENKINS-12585 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12585 > Project: Jenkins > Issue Type: Bug > Components: security >Affects Versions: current > Environment: Mac OSX: 10.6.8 Desktop > Java version: 1.6.0_29 > Access Control > * Security Realm: LDAP > * Authorization: Project-based Matrix Authorization Strategy > Jenkins: 1.448 > Apache > * Server version: Apache/2.2.17 (Unix) > * Server built: Dec 1 2010 09:58:15 >Reporter: guillermo c >Priority: Critical > > Running Jenkins behind Apache: mod_proxy with HTTPS > https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Apache > So our setup is > Open Directory group > jenkins-admin - Jenkins Admins all > dev-group-a - Developers can view kick off builds > Project-based Matrix Authorization Strategy > Admin all checked > dev-group-a checked: Overall:Read Job:Read,Build Run:Update > dev-group-b checked: Overall:Read Job:Read > issue is I'm an admin and random developer will login and see that there user > id is mine and can admin jenkins. > there has been reported cases that developer A will login and actually be > reported by jenkins as Developer B > were they can no longer trigger CI builds > My biggest concern is when users login and are reporting as admins and have > full access to jenkins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12585) SECURITY: LDAP authenticated users switch accounts randomly
[ https://issues.jenkins-ci.org/browse/JENKINS-12585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160833#comment-160833 ] Tanmay Sinha commented on JENKINS-12585: +1 This is causing major issues as users are gaining unauthorized access to controls. > SECURITY: LDAP authenticated users switch accounts randomly > --- > > Key: JENKINS-12585 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12585 > Project: Jenkins > Issue Type: Bug > Components: security >Affects Versions: current > Environment: Mac OSX: 10.6.8 Desktop > Java version: 1.6.0_29 > Access Control > * Security Realm: LDAP > * Authorization: Project-based Matrix Authorization Strategy > Jenkins: 1.448 > Apache > * Server version: Apache/2.2.17 (Unix) > * Server built: Dec 1 2010 09:58:15 >Reporter: guillermo c >Priority: Critical > > Running Jenkins behind Apache: mod_proxy with HTTPS > https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Apache > So our setup is > Open Directory group > jenkins-admin - Jenkins Admins all > dev-group-a - Developers can view kick off builds > Project-based Matrix Authorization Strategy > Admin all checked > dev-group-a checked: Overall:Read Job:Read,Build Run:Update > dev-group-b checked: Overall:Read Job:Read > issue is I'm an admin and random developer will login and see that there user > id is mine and can admin jenkins. > there has been reported cases that developer A will login and actually be > reported by jenkins as Developer B > were they can no longer trigger CI builds > My biggest concern is when users login and are reporting as admins and have > full access to jenkins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13227) CVS plugin 2.1 does not detect changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160831#comment-160831 ] Guillaume Bilodeau edited comment on JENKINS-13227 at 3/27/12 2:05 PM: --- Thanks for taking a look at this. CVS server is 1.11.22. I've upgraded to CVS plugin 2.2 and the behaviour is the same. Here is the output of the command: *** D:\Projets\jdevws\portailInt>cvs rlog -d"22 Mar 2012 09:26:21 -0400<27 Mar 2012 12:00:00 -0400" -S -rd-chg00014229_op_brc_preimp-op-2012-02-27 portailInt cvs rlog: Logging portailInt *** I suppose this should have provided more information. Maybe there's an error in the command itself - sorry I'm not familiar enough with CVS to see any... was (Author: gbilodeau): Thanks for taking a look at this. CVS server is 1.11.22. I've upgraded to CVS plugin 2.2 and the behaviour is the same. Here is the output of the command: *** D:\Projets\jdevws\portailInt>cvs rlog -d"22 Mar 2012 09:26:21 -0400<27 Mar 2012 12:00:00 -0400" -S -rd-chg00014229_op_brc_preimp-op-2012-02-27 portailInt cvs rlog: Logging portailInt *** I suppose this should have provided more information. Maybe there's an error in the command itself - sorry I'm not familiar with CVS to see any... > CVS plugin 2.1 does not detect changes > -- > > Key: JENKINS-13227 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13227 > Project: Jenkins > Issue Type: Bug > Components: cvs >Reporter: Guillaume Bilodeau > Labels: cvs > > As presented in the user group: > https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4 > We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS > repository for a few weeks now, without any problems. The CVS plugin (v1.6) > was using the local cvsnt install. > We've since upgraded the CVS plugin to version 2.1 (by manually pinning the > plugin) and since then, CVS changes are not detected. The CVS polling log is > triggered properly, tons of "cvs rlog" instructions are sent, but at the end > "No changes" is displayed. > Using CVS plugin 1.6 the cvs polling command looked like this (executed at > 5:26:21 PM EDT): > cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D > "Thursday, March 22, 2012 9:26:21 PM UTC" > Using CVS plugin 2.1, the last cvs checkout command looked like this > (executed at 11:56:16 AM EDT): > cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 > 11:56:16 EDT -d portailInt portailInt > We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12585) SECURITY: LDAP authenticated users switch accounts randomly
[ https://issues.jenkins-ci.org/browse/JENKINS-12585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160834#comment-160834 ] Christian Höltje commented on JENKINS-12585: A better description of symptoms: * I, as a user with admin powers, log in. After a while, I'll notice I'm logged in as normal user "singer". I have to log out and log back in to regain my normal account and admin powers. * "bambi" and "singer" can become me by conjuring the new hover thingies and then going to a new page. This includes admin powers. * "sniper" can hit refresh repeatedly on a page and become "singer" or logged out. "sniper" is also an admin. Note: The usernames have been changed to protect the guilty. > SECURITY: LDAP authenticated users switch accounts randomly > --- > > Key: JENKINS-12585 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12585 > Project: Jenkins > Issue Type: Bug > Components: security >Affects Versions: current > Environment: Mac OSX: 10.6.8 Desktop > Java version: 1.6.0_29 > Access Control > * Security Realm: LDAP > * Authorization: Project-based Matrix Authorization Strategy > Jenkins: 1.448 > Apache > * Server version: Apache/2.2.17 (Unix) > * Server built: Dec 1 2010 09:58:15 >Reporter: guillermo c >Priority: Critical > > Running Jenkins behind Apache: mod_proxy with HTTPS > https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Apache > So our setup is > Open Directory group > jenkins-admin - Jenkins Admins all > dev-group-a - Developers can view kick off builds > Project-based Matrix Authorization Strategy > Admin all checked > dev-group-a checked: Overall:Read Job:Read,Build Run:Update > dev-group-b checked: Overall:Read Job:Read > issue is I'm an admin and random developer will login and see that there user > id is mine and can admin jenkins. > there has been reported cases that developer A will login and actually be > reported by jenkins as Developer B > were they can no longer trigger CI builds > My biggest concern is when users login and are reporting as admins and have > full access to jenkins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12585) SECURITY: LDAP authenticated users switch accounts randomly
[ https://issues.jenkins-ci.org/browse/JENKINS-12585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160836#comment-160836 ] Christian Höltje commented on JENKINS-12585: Related bug: JENKINS-13203 This is the symptoms described with "bambi" and "singer" above (number 2). > SECURITY: LDAP authenticated users switch accounts randomly > --- > > Key: JENKINS-12585 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12585 > Project: Jenkins > Issue Type: Bug > Components: security >Affects Versions: current > Environment: Mac OSX: 10.6.8 Desktop > Java version: 1.6.0_29 > Access Control > * Security Realm: LDAP > * Authorization: Project-based Matrix Authorization Strategy > Jenkins: 1.448 > Apache > * Server version: Apache/2.2.17 (Unix) > * Server built: Dec 1 2010 09:58:15 >Reporter: guillermo c >Priority: Critical > > Running Jenkins behind Apache: mod_proxy with HTTPS > https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Apache > So our setup is > Open Directory group > jenkins-admin - Jenkins Admins all > dev-group-a - Developers can view kick off builds > Project-based Matrix Authorization Strategy > Admin all checked > dev-group-a checked: Overall:Read Job:Read,Build Run:Update > dev-group-b checked: Overall:Read Job:Read > issue is I'm an admin and random developer will login and see that there user > id is mine and can admin jenkins. > there has been reported cases that developer A will login and actually be > reported by jenkins as Developer B > were they can no longer trigger CI builds > My biggest concern is when users login and are reporting as admins and have > full access to jenkins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13203) mouse over building job until hover menu appears, on next page load I am logged in as a different user
[ https://issues.jenkins-ci.org/browse/JENKINS-13203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160835#comment-160835 ] Christian Höltje commented on JENKINS-13203: Sounds like a duplicate of JENKINS-12585 > mouse over building job until hover menu appears, on next page load I am > logged in as a different user > -- > > Key: JENKINS-13203 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13203 > Project: Jenkins > Issue Type: Bug > Components: security >Reporter: Alex Tambellini > > It seems like sometimes when I activate the hover menu and I refresh the page > I show as logged in as someone else. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12585) SECURITY: LDAP authenticated users switch accounts randomly
[ https://issues.jenkins-ci.org/browse/JENKINS-12585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160837#comment-160837 ] Christian Höltje commented on JENKINS-12585: Also: I'd be happy to help troubleshoot/debug this. I can get some of the Java experts here to help me look at thread dumps or whatever else might be useful. > SECURITY: LDAP authenticated users switch accounts randomly > --- > > Key: JENKINS-12585 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12585 > Project: Jenkins > Issue Type: Bug > Components: security >Affects Versions: current > Environment: Mac OSX: 10.6.8 Desktop > Java version: 1.6.0_29 > Access Control > * Security Realm: LDAP > * Authorization: Project-based Matrix Authorization Strategy > Jenkins: 1.448 > Apache > * Server version: Apache/2.2.17 (Unix) > * Server built: Dec 1 2010 09:58:15 >Reporter: guillermo c >Priority: Critical > > Running Jenkins behind Apache: mod_proxy with HTTPS > https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Apache > So our setup is > Open Directory group > jenkins-admin - Jenkins Admins all > dev-group-a - Developers can view kick off builds > Project-based Matrix Authorization Strategy > Admin all checked > dev-group-a checked: Overall:Read Job:Read,Build Run:Update > dev-group-b checked: Overall:Read Job:Read > issue is I'm an admin and random developer will login and see that there user > id is mine and can admin jenkins. > there has been reported cases that developer A will login and actually be > reported by jenkins as Developer B > were they can no longer trigger CI builds > My biggest concern is when users login and are reporting as admins and have > full access to jenkins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13224) JobConfigHistory not visible to Roles who have the right to configure Jobs
[ https://issues.jenkins-ci.org/browse/JENKINS-13224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160838#comment-160838 ] Igor Masen commented on JENKINS-13224: -- Hello Mirko, sorry for my late answer. I am not at the office today, so I can not test it yet. But yes you are right, the group jenkins_build_manager can see the configure job button (that's their job), but can not see the JobConfigHistory link. For a correct test with your newer snapshot I should be in my office and trying it on the testing and/or productive environment (maybe tomorrow). I don't know if it is important for you, but we are using the Jenkins-Crowd-PlugIn (https://wiki.jenkins-ci.org/display/JENKINS/Crowd+2+Plugin) to proxy the authorization to our ldap. > JobConfigHistory not visible to Roles who have the right to configure Jobs > -- > > Key: JENKINS-13224 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13224 > Project: Jenkins > Issue Type: Bug > Components: jobconfighistory >Affects Versions: current > Environment: RHEL 6.2 64-Bit, Oracle JDK 1.6.0.30, VMWare TcServer, > Jenkins 1.450, JobConfigHistory Version 1.13 >Reporter: Igor Masen >Assignee: Mirko Friedenhagen > Labels: jobconfighistory > Attachments: screenshot-with-1.424.6.jpg, screenshot_matrix.jpg > > > Hello, > we have a problem on our productive System. We have Matrix-Based Security > activated and People in Roles who have the right to configure build-jobs are > do not see the Button "Job Config History". Please look at the Screenshot > attached. The only Role who is able to see the Button in this environment is > "jenkins_admin". > Kind regards -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13224) JobConfigHistory not visible to Roles who have the right to configure Jobs
[ https://issues.jenkins-ci.org/browse/JENKINS-13224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-13224 started by Mirko Friedenhagen. > JobConfigHistory not visible to Roles who have the right to configure Jobs > -- > > Key: JENKINS-13224 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13224 > Project: Jenkins > Issue Type: Bug > Components: jobconfighistory >Affects Versions: current > Environment: RHEL 6.2 64-Bit, Oracle JDK 1.6.0.30, VMWare TcServer, > Jenkins 1.450, JobConfigHistory Version 1.13 >Reporter: Igor Masen >Assignee: Mirko Friedenhagen > Labels: jobconfighistory > Attachments: screenshot-with-1.424.6.jpg, screenshot_matrix.jpg > > > Hello, > we have a problem on our productive System. We have Matrix-Based Security > activated and People in Roles who have the right to configure build-jobs are > do not see the Button "Job Config History". Please look at the Screenshot > attached. The only Role who is able to see the Button in this environment is > "jenkins_admin". > Kind regards -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13224) JobConfigHistory not visible to Roles who have the right to configure Jobs
[ https://issues.jenkins-ci.org/browse/JENKINS-13224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-13224 stopped by Igor Masen. > JobConfigHistory not visible to Roles who have the right to configure Jobs > -- > > Key: JENKINS-13224 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13224 > Project: Jenkins > Issue Type: Bug > Components: jobconfighistory >Affects Versions: current > Environment: RHEL 6.2 64-Bit, Oracle JDK 1.6.0.30, VMWare TcServer, > Jenkins 1.450, JobConfigHistory Version 1.13 >Reporter: Igor Masen >Assignee: Mirko Friedenhagen > Labels: jobconfighistory > Attachments: screenshot-with-1.424.6.jpg, screenshot_matrix.jpg > > > Hello, > we have a problem on our productive System. We have Matrix-Based Security > activated and People in Roles who have the right to configure build-jobs are > do not see the Button "Job Config History". Please look at the Screenshot > attached. The only Role who is able to see the Button in this environment is > "jenkins_admin". > Kind regards -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13246) disk usage peridocity should be configurable
Greg Moncreaff created JENKINS-13246: Summary: disk usage peridocity should be configurable Key: JENKINS-13246 URL: https://issues.jenkins-ci.org/browse/JENKINS-13246 Project: Jenkins Issue Type: Improvement Components: disk-usage Affects Versions: current Reporter: Greg Moncreaff Assignee: vjuranek currently it runs every 60m. can be disruptive to team working environment. If run as part of build not so bad, but sweep of all jobs can be very bad. can we get a temporary cron knob to run it say only at 1am (or whenever) rather than the current every 60? can we have it skip builds/workspaces it has data for and populate the ones we know nothing about first? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13247) disk usage should not follow symlinks
Greg Moncreaff created JENKINS-13247: Summary: disk usage should not follow symlinks Key: JENKINS-13247 URL: https://issues.jenkins-ci.org/browse/JENKINS-13247 Project: Jenkins Issue Type: Bug Components: disk-usage Affects Versions: current Reporter: Greg Moncreaff Assignee: vjuranek normal du doesn't so disk usage shouldnt either. you risk circularities and jumping outside of jobs workspace if you do any follows -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13223) Filter jobs that has enabled project-based security
[ https://issues.jenkins-ci.org/browse/JENKINS-13223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jacob_robertson resolved JENKINS-13223. --- Resolution: Fixed This feature has been added to version 1.19 > Filter jobs that has enabled project-based security > --- > > Key: JENKINS-13223 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13223 > Project: Jenkins > Issue Type: New Feature > Components: view-job-filters >Reporter: Sam He >Assignee: jacob_robertson > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13129) Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup
[ https://issues.jenkins-ci.org/browse/JENKINS-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160840#comment-160840 ] Alex Lehmann commented on JENKINS-13129: https://github.com/alexlehm/jenkins/commit/2453985ca5f4cb2c824466d132fe3658020b72fe [Fixed JENKINS-13129] Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup changed bundled plugin detection, added unit test > Updating built-in plugins doesn't work, the file doesn't get pinned and is > overwritten on the next startup > -- > > Key: JENKINS-13129 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13129 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current > Environment: jenkins 1.456, tomcat 7.0.25, java 1.6.0-31 running on > windows vista >Reporter: Alex Lehmann > > I still cannot update cvs or subversion plugins without manually creating a > .pinned file. > When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file > is installed into the plugin dir, but no cvs.jpi.pinned file is created. When > restarting the tomcat server, the file is replaced by the 1.6 version from > the war directory. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13129) Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup
[ https://issues.jenkins-ci.org/browse/JENKINS-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160841#comment-160841 ] Alex Lehmann commented on JENKINS-13129: I should note that this is not a specific Windows issue, I have had the same problem with 1.456 on linux as well > Updating built-in plugins doesn't work, the file doesn't get pinned and is > overwritten on the next startup > -- > > Key: JENKINS-13129 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13129 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current > Environment: jenkins 1.456, tomcat 7.0.25, java 1.6.0-31 running on > windows vista >Reporter: Alex Lehmann > > I still cannot update cvs or subversion plugins without manually creating a > .pinned file. > When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file > is installed into the plugin dir, but no cvs.jpi.pinned file is created. When > restarting the tomcat server, the file is replaced by the 1.6 version from > the war directory. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13248) remote API no longer provides artifacts
phlav created JENKINS-13248: --- Summary: remote API no longer provides artifacts Key: JENKINS-13248 URL: https://issues.jenkins-ci.org/browse/JENKINS-13248 Project: Jenkins Issue Type: Bug Components: promoted-builds Reporter: phlav After updating Jenkins from 1.449 to 1.457, the remote API for the latest promoted build stopped returning the artifacts. For example, for a promotion process named "internal_release", accessing http://hostname:8080/job/jobname/promotion/latest/internal_release/api/xml yields only this information: Legacy code started this job. No cause information is available false 5890 jobname » promotion » internal_release #17 2012-02-21_16-44-04 false 17 SUCCESS 1329860644000 http://hostname:8080/job/jobname/promotion//internal_release/17/ A workaround to access the artifacts list would be to find a link from the promotion number to the actual build number, but this information does not seem available through the API. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13224) JobConfigHistory not visible to Roles who have the right to configure Jobs
[ https://issues.jenkins-ci.org/browse/JENKINS-13224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160842#comment-160842 ] Igor Masen commented on JENKINS-13224: -- Hello Mirko, I have tested my problem on my own computer at home (Jenkins 1.450, 1.424.6, 1.457 with JobConfiHistory 1.13, and your newest Snapshot). I can not reproduce the behaviour of my productive environment here. So stop investigating this problem further, I will test again in my office and will post my result here. > JobConfigHistory not visible to Roles who have the right to configure Jobs > -- > > Key: JENKINS-13224 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13224 > Project: Jenkins > Issue Type: Bug > Components: jobconfighistory >Affects Versions: current > Environment: RHEL 6.2 64-Bit, Oracle JDK 1.6.0.30, VMWare TcServer, > Jenkins 1.450, JobConfigHistory Version 1.13 >Reporter: Igor Masen >Assignee: Mirko Friedenhagen > Labels: jobconfighistory > Attachments: screenshot-with-1.424.6.jpg, screenshot_matrix.jpg > > > Hello, > we have a problem on our productive System. We have Matrix-Based Security > activated and People in Roles who have the right to configure build-jobs are > do not see the Button "Job Config History". Please look at the Screenshot > attached. The only Role who is able to see the Button in this environment is > "jenkins_admin". > Kind regards -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13227) CVS plugin 2.1 does not detect changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160843#comment-160843 ] Michael Clarke commented on JENKINS-13227: -- Your output shows there as being no changes between 22nd and 27th March. Are you expecting there to be some? > CVS plugin 2.1 does not detect changes > -- > > Key: JENKINS-13227 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13227 > Project: Jenkins > Issue Type: Bug > Components: cvs >Reporter: Guillaume Bilodeau > Labels: cvs > > As presented in the user group: > https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4 > We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS > repository for a few weeks now, without any problems. The CVS plugin (v1.6) > was using the local cvsnt install. > We've since upgraded the CVS plugin to version 2.1 (by manually pinning the > plugin) and since then, CVS changes are not detected. The CVS polling log is > triggered properly, tons of "cvs rlog" instructions are sent, but at the end > "No changes" is displayed. > Using CVS plugin 1.6 the cvs polling command looked like this (executed at > 5:26:21 PM EDT): > cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D > "Thursday, March 22, 2012 9:26:21 PM UTC" > Using CVS plugin 2.1, the last cvs checkout command looked like this > (executed at 11:56:16 AM EDT): > cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 > 11:56:16 EDT -d portailInt portailInt > We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13129) Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup
[ https://issues.jenkins-ci.org/browse/JENKINS-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Lehmann reassigned JENKINS-13129: -- Assignee: Alex Lehmann > Updating built-in plugins doesn't work, the file doesn't get pinned and is > overwritten on the next startup > -- > > Key: JENKINS-13129 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13129 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current > Environment: jenkins 1.456, tomcat 7.0.25, java 1.6.0-31 running on > windows vista >Reporter: Alex Lehmann >Assignee: Alex Lehmann > > I still cannot update cvs or subversion plugins without manually creating a > .pinned file. > When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file > is installed into the plugin dir, but no cvs.jpi.pinned file is created. When > restarting the tomcat server, the file is replaced by the 1.6 version from > the war directory. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13129) Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup
[ https://issues.jenkins-ci.org/browse/JENKINS-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-13129 started by Alex Lehmann. > Updating built-in plugins doesn't work, the file doesn't get pinned and is > overwritten on the next startup > -- > > Key: JENKINS-13129 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13129 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current > Environment: jenkins 1.456, tomcat 7.0.25, java 1.6.0-31 running on > windows vista >Reporter: Alex Lehmann >Assignee: Alex Lehmann > > I still cannot update cvs or subversion plugins without manually creating a > .pinned file. > When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file > is installed into the plugin dir, but no cvs.jpi.pinned file is created. When > restarting the tomcat server, the file is replaced by the 1.6 version from > the war directory. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13227) CVS plugin 2.1 does not detect changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160844#comment-160844 ] Guillaume Bilodeau commented on JENKINS-13227: -- Yes, many :) I sent the command with an even greater interval with the same results: D:\Projets\jdevws\portailInt>cvs rlog -d"01 Mar 2012 09:26:21 -0400<27 Mar 2012 12:00:00 -0400" -S -rd-chg00014229_op_brc_preimp-op-2012-02-27 portailInt cvs rlog: Logging portailInt Maybe the rlog command isn't interpreted properly by the server? > CVS plugin 2.1 does not detect changes > -- > > Key: JENKINS-13227 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13227 > Project: Jenkins > Issue Type: Bug > Components: cvs >Reporter: Guillaume Bilodeau > Labels: cvs > > As presented in the user group: > https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4 > We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS > repository for a few weeks now, without any problems. The CVS plugin (v1.6) > was using the local cvsnt install. > We've since upgraded the CVS plugin to version 2.1 (by manually pinning the > plugin) and since then, CVS changes are not detected. The CVS polling log is > triggered properly, tons of "cvs rlog" instructions are sent, but at the end > "No changes" is displayed. > Using CVS plugin 1.6 the cvs polling command looked like this (executed at > 5:26:21 PM EDT): > cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D > "Thursday, March 22, 2012 9:26:21 PM UTC" > Using CVS plugin 2.1, the last cvs checkout command looked like this > (executed at 11:56:16 AM EDT): > cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 > 11:56:16 EDT -d portailInt portailInt > We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13227) CVS plugin 2.1 does not detect changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160845#comment-160845 ] Alex Lehmann commented on JENKINS-13227: I wonder if if would be possible to set up a mock repository locally to test accessing it during a test case this would require running a cvs pserver locally though > CVS plugin 2.1 does not detect changes > -- > > Key: JENKINS-13227 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13227 > Project: Jenkins > Issue Type: Bug > Components: cvs >Reporter: Guillaume Bilodeau > Labels: cvs > > As presented in the user group: > https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4 > We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS > repository for a few weeks now, without any problems. The CVS plugin (v1.6) > was using the local cvsnt install. > We've since upgraded the CVS plugin to version 2.1 (by manually pinning the > plugin) and since then, CVS changes are not detected. The CVS polling log is > triggered properly, tons of "cvs rlog" instructions are sent, but at the end > "No changes" is displayed. > Using CVS plugin 1.6 the cvs polling command looked like this (executed at > 5:26:21 PM EDT): > cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D > "Thursday, March 22, 2012 9:26:21 PM UTC" > Using CVS plugin 2.1, the last cvs checkout command looked like this > (executed at 11:56:16 AM EDT): > cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 > 11:56:16 EDT -d portailInt portailInt > We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12585) SECURITY: LDAP authenticated users switch accounts randomly
[ https://issues.jenkins-ci.org/browse/JENKINS-12585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160846#comment-160846 ] Kohsuke Kawaguchi commented on JENKINS-12585: - Looking into this. For other people seeing this, please report * the way you run Jenkins (be it via "java -jar jenkins.war" or on some other servlet containers) * version of Jenkins > SECURITY: LDAP authenticated users switch accounts randomly > --- > > Key: JENKINS-12585 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12585 > Project: Jenkins > Issue Type: Bug > Components: security >Affects Versions: current > Environment: Mac OSX: 10.6.8 Desktop > Java version: 1.6.0_29 > Access Control > * Security Realm: LDAP > * Authorization: Project-based Matrix Authorization Strategy > Jenkins: 1.448 > Apache > * Server version: Apache/2.2.17 (Unix) > * Server built: Dec 1 2010 09:58:15 >Reporter: guillermo c >Priority: Critical > > Running Jenkins behind Apache: mod_proxy with HTTPS > https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Apache > So our setup is > Open Directory group > jenkins-admin - Jenkins Admins all > dev-group-a - Developers can view kick off builds > Project-based Matrix Authorization Strategy > Admin all checked > dev-group-a checked: Overall:Read Job:Read,Build Run:Update > dev-group-b checked: Overall:Read Job:Read > issue is I'm an admin and random developer will login and see that there user > id is mine and can admin jenkins. > there has been reported cases that developer A will login and actually be > reported by jenkins as Developer B > were they can no longer trigger CI builds > My biggest concern is when users login and are reporting as admins and have > full access to jenkins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13227) CVS plugin 2.1 does not detect changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160847#comment-160847 ] Michael Clarke commented on JENKINS-13227: -- Guillaume: I'm not aware of any CVS servers handling rlog differently from each other so am a bit surprised that you're expecting output for the command. Given your CVS client is giving the same output as our embedded CVS client does point to something strange happening on the server, although without having some way to replicate your setup/environment I'd really be guessing at what's going on. Can you try running the command 'cvs log -d"01 Mar 2012 09:00:00 -0400<27 Mar 2012 12:00:00 -0400" and let me know if you get output. Alex: the CVSClient has unit tests that create a mock CVS server by replaying a set of recorded messages, although this has problems in the way it's coded meaning the tests have to run as root on Linux and intermittently fail for no apparent reason. > CVS plugin 2.1 does not detect changes > -- > > Key: JENKINS-13227 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13227 > Project: Jenkins > Issue Type: Bug > Components: cvs >Reporter: Guillaume Bilodeau > Labels: cvs > > As presented in the user group: > https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4 > We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS > repository for a few weeks now, without any problems. The CVS plugin (v1.6) > was using the local cvsnt install. > We've since upgraded the CVS plugin to version 2.1 (by manually pinning the > plugin) and since then, CVS changes are not detected. The CVS polling log is > triggered properly, tons of "cvs rlog" instructions are sent, but at the end > "No changes" is displayed. > Using CVS plugin 1.6 the cvs polling command looked like this (executed at > 5:26:21 PM EDT): > cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D > "Thursday, March 22, 2012 9:26:21 PM UTC" > Using CVS plugin 2.1, the last cvs checkout command looked like this > (executed at 11:56:16 AM EDT): > cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 > 11:56:16 EDT -d portailInt portailInt > We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13227) CVS plugin 2.1 does not detect changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160848#comment-160848 ] Guillaume Bilodeau commented on JENKINS-13227: -- Plenty of output with the cvs log command. Here is an excerpt: D:\Projets\jdevws\portailInt>cvs log -d"01 Mar 2012 09:00:00 -0400<27 Mar 2012 12:00:00 -0400" ? work/.project ? work/build ? work/script/build.txt cvs log: Logging . RCS file: /usr/local/cvs/repcvs/PortailInternetMouvement/portailInt/.cvsignore,v Working file: .cvsignore head: 1.1 branch: locks: strict access list: symbolic names: d-chg00014229_op_impl_2012-03-25_v06: 1.1 d-chg00014229_op_impl_2012-03-25_v05: 1.1 aq_op_2012-03-25_v04: 1.1 d-chg00014229_op_impl_2012-03-25_v04: 1.1 aq_op_2012-03-25_v03: 1.1 d-chg00014229_op_impl_2012-03-25_v03: 1.1 d-chg00014229_op_impl_2012-03-25_v02: 1.1 aq_op_2012-03-25_v01: 1.1 d-chg00014229_op_impl_2012-03-25_v01: 1.1 d-chg00014229_op_brc_preimp-op-2012-02-27: 1.1.0.2 preimp_op_2012-02-27: 1.1 keyword substitution: kv total revisions: 1; selected revisions: 0 description: = RCS file: /usr/local/cvs/repcvs/PortailInternetMouvement/portailInt/Attic/PortailInt.jws,v Working file: PortailInt.jws head: 1.1 branch: locks: strict access list: symbolic names: d-chg00014229_op_impl_2012-03-25_v06: 1.1.2.1 d-chg00014229_op_impl_2012-03-25_v05: 1.1.2.1 aq_op_2012-03-25_v04: 1.1.2.1 d-chg00014229_op_impl_2012-03-25_v04: 1.1.2.1 aq_op_2012-03-25_v03: 1.1.2.1 d-chg00014229_op_impl_2012-03-25_v03: 1.1.2.1 d-chg00014229_op_impl_2012-03-25_v02: 1.1.2.1 aq_op_2012-03-25_v01: 1.1.2.1 d-chg00014229_op_impl_2012-03-25_v01: 1.1.2.1 d-chg00014229_op_brc_preimp-op-2012-02-27: 1.1.0.2 keyword substitution: kv total revisions: 2; selected revisions: 0 description: = RCS file: /usr/local/cvs/repcvs/PortailInternetMouvement/portailInt/PortailInternet.jws,v Working file: PortailInternet.jws head: 1.9 branch: locks: strict access list: symbolic names: d-chg00014229_op_brc_preimp-op-2012-02-27: 1.9.0.2 preimp_op_2012-02-27: 1.9 d-800b02_hl_tmp_2012-01-16: 1.6 d-800b02_hl_tmp_2012-01-09: 1.3 keyword substitution: kv total revisions: 10;selected revisions: 0 description: > CVS plugin 2.1 does not detect changes > -- > > Key: JENKINS-13227 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13227 > Project: Jenkins > Issue Type: Bug > Components: cvs >Reporter: Guillaume Bilodeau > Labels: cvs > > As presented in the user group: > https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4 > We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS > repository for a few weeks now, without any problems. The CVS plugin (v1.6) > was using the local cvsnt install. > We've since upgraded the CVS plugin to version 2.1 (by manually pinning the > plugin) and since then, CVS changes are not detected. The CVS polling log is > triggered properly, tons of "cvs rlog" instructions are sent, but at the end > "No changes" is displayed. > Using CVS plugin 1.6 the cvs polling command looked like this (executed at > 5:26:21 PM EDT): > cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D > "Thursday, March 22, 2012 9:26:21 PM UTC" > Using CVS plugin 2.1, the last cvs checkout command looked like this > (executed at 11:56:16 AM EDT): > cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 > 11:56:16 EDT -d portailInt portailInt > We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12585) SECURITY: LDAP authenticated users switch accounts randomly
[ https://issues.jenkins-ci.org/browse/JENKINS-12585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kohsuke Kawaguchi reassigned JENKINS-12585: --- Assignee: Kohsuke Kawaguchi > SECURITY: LDAP authenticated users switch accounts randomly > --- > > Key: JENKINS-12585 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12585 > Project: Jenkins > Issue Type: Bug > Components: security >Affects Versions: current > Environment: Mac OSX: 10.6.8 Desktop > Java version: 1.6.0_29 > Access Control > * Security Realm: LDAP > * Authorization: Project-based Matrix Authorization Strategy > Jenkins: 1.448 > Apache > * Server version: Apache/2.2.17 (Unix) > * Server built: Dec 1 2010 09:58:15 >Reporter: guillermo c >Assignee: Kohsuke Kawaguchi >Priority: Critical > > Running Jenkins behind Apache: mod_proxy with HTTPS > https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Apache > So our setup is > Open Directory group > jenkins-admin - Jenkins Admins all > dev-group-a - Developers can view kick off builds > Project-based Matrix Authorization Strategy > Admin all checked > dev-group-a checked: Overall:Read Job:Read,Build Run:Update > dev-group-b checked: Overall:Read Job:Read > issue is I'm an admin and random developer will login and see that there user > id is mine and can admin jenkins. > there has been reported cases that developer A will login and actually be > reported by jenkins as Developer B > were they can no longer trigger CI builds > My biggest concern is when users login and are reporting as admins and have > full access to jenkins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13203) mouse over building job until hover menu appears, on next page load I am logged in as a different user
[ https://issues.jenkins-ci.org/browse/JENKINS-13203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kohsuke Kawaguchi resolved JENKINS-13203. - Resolution: Duplicate Yes, it does appear to be a dupliate. > mouse over building job until hover menu appears, on next page load I am > logged in as a different user > -- > > Key: JENKINS-13203 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13203 > Project: Jenkins > Issue Type: Bug > Components: security >Reporter: Alex Tambellini > > It seems like sometimes when I activate the hover menu and I refresh the page > I show as logged in as someone else. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13227) CVS plugin 2.1 does not detect changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160849#comment-160849 ] Michael Clarke commented on JENKINS-13227: -- Interestingly the files you've listed don't have any revisions in the time range you've specified. Could you search your output and check if any have "selected revision" that isn't 0? > CVS plugin 2.1 does not detect changes > -- > > Key: JENKINS-13227 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13227 > Project: Jenkins > Issue Type: Bug > Components: cvs >Reporter: Guillaume Bilodeau > Labels: cvs > > As presented in the user group: > https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4 > We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS > repository for a few weeks now, without any problems. The CVS plugin (v1.6) > was using the local cvsnt install. > We've since upgraded the CVS plugin to version 2.1 (by manually pinning the > plugin) and since then, CVS changes are not detected. The CVS polling log is > triggered properly, tons of "cvs rlog" instructions are sent, but at the end > "No changes" is displayed. > Using CVS plugin 1.6 the cvs polling command looked like this (executed at > 5:26:21 PM EDT): > cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D > "Thursday, March 22, 2012 9:26:21 PM UTC" > Using CVS plugin 2.1, the last cvs checkout command looked like this > (executed at 11:56:16 AM EDT): > cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 > 11:56:16 EDT -d portailInt portailInt > We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9877) Static Code Analysis Plug-ins is updated between each plug-in update
[ https://issues.jenkins-ci.org/browse/JENKINS-9877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Lehmann updated JENKINS-9877: -- Environment: linux ubuntu jenkins 1.457 tomcat 7.0.26 was:linux sles jenkins 1.414 tomcat 6.0.32 this still happens in the current jenkins version > Static Code Analysis Plug-ins is updated between each plug-in update > > > Key: JENKINS-9877 > URL: https://issues.jenkins-ci.org/browse/JENKINS-9877 > Project: Jenkins > Issue Type: Bug > Components: plugin > Environment: linux ubuntu jenkins 1.457 tomcat 7.0.26 >Reporter: Alex Lehmann >Priority: Minor > Fix For: current > > Attachments: screenshot-1.jpg > > > When updating plug-ins today, I got the Static Code Analysis plug-in each > time another plugin is listed for update (see attached screenshot) > This includes the plug-ins that depend on it as well as the ones that don't > (cvs plugin) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12675) Add an option to install specific selenium version on the running nodes
[ https://issues.jenkins-ci.org/browse/JENKINS-12675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160852#comment-160852 ] Tetiana Tvardovska commented on JENKINS-12675: -- I also vote for this. Actual [Selenium 2|http://seleniumhq.org/download/] version is 2.20 already, but this plugin still uses old 2.15. If there were an option to change default used version without plugin rebuild, we could upgrade Selenium core by configuring Jenkins without disturbing plugin developers... > Add an option to install specific selenium version on the running nodes > --- > > Key: JENKINS-12675 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12675 > Project: Jenkins > Issue Type: New Feature > Components: selenium >Reporter: Richard Lavoie >Assignee: Richard Lavoie >Priority: Minor > > People have been asking over email that it would be nice to be able to use > the latest selenium version, so here is the ticket for that. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9877) Static Code Analysis Plug-ins is updated between each plug-in update
[ https://issues.jenkins-ci.org/browse/JENKINS-9877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Lehmann reopened JENKINS-9877: --- > Static Code Analysis Plug-ins is updated between each plug-in update > > > Key: JENKINS-9877 > URL: https://issues.jenkins-ci.org/browse/JENKINS-9877 > Project: Jenkins > Issue Type: Bug > Components: plugin > Environment: linux sles jenkins 1.414 tomcat 6.0.32 >Reporter: Alex Lehmann >Priority: Minor > Fix For: current > > Attachments: screenshot-1.jpg > > > When updating plug-ins today, I got the Static Code Analysis plug-in each > time another plugin is listed for update (see attached screenshot) > This includes the plug-ins that depend on it as well as the ones that don't > (cvs plugin) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13227) CVS plugin 2.1 does not detect changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160853#comment-160853 ] Guillaume Bilodeau commented on JENKINS-13227: -- RCS file: /usr/local/cvs/repcvs/PortailInternetMouvement/portailInt/Portail/src/com/xxx/pvm/portail/taglib/I18nBundleTag.java,v Working file: Portail/src/com/xxx/pvm/portail/taglib/I18nBundleTag.java head: 1.3 branch: locks: strict access list: symbolic names: d-chg00014229_op_impl_2012-03-25_v06: 1.1.2.4 d-chg00014229_op_impl_2012-03-25_v05: 1.1.2.4 aq_op_2012-03-25_v04: 1.1.2.4 d-chg00014229_op_impl_2012-03-25_v04: 1.1.2.4 aq_op_2012-03-25_v03: 1.1.2.3 d-chg00014229_op_impl_2012-03-25_v03: 1.1.2.3 d-chg00014229_op_impl_2012-03-25_v02: 1.1.2.3 aq_op_2012-03-25_v01: 1.1 d-chg00014229_op_impl_2012-03-25_v01: 1.1 d-chg00014229_op_brc_preimp-op-2012-02-27: 1.1.0.2 preimp_op_2012-02-27: 1.1 keyword substitution: kv total revisions: 8; selected revisions: 3 description: revision 1.1.2.5 date: 2012/03/23 15:42:50; author: ba0chzi; state: Exp; lines: +4 -26 Organize imports revision 1.1.2.4 date: 2012/03/13 14:18:27; author: ba0chmn; state: Exp; lines: +1 -1 Changement de scope de request ou session pour application dans le but d'améliorer les performances revision 1.1.2.3 date: 2012/03/06 21:19:03; author: ba0chmn; state: Exp; lines: +14 -8 Utilisation des services de récupération de fichier dans UCM de xxx > CVS plugin 2.1 does not detect changes > -- > > Key: JENKINS-13227 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13227 > Project: Jenkins > Issue Type: Bug > Components: cvs >Reporter: Guillaume Bilodeau > Labels: cvs > > As presented in the user group: > https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4 > We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS > repository for a few weeks now, without any problems. The CVS plugin (v1.6) > was using the local cvsnt install. > We've since upgraded the CVS plugin to version 2.1 (by manually pinning the > plugin) and since then, CVS changes are not detected. The CVS polling log is > triggered properly, tons of "cvs rlog" instructions are sent, but at the end > "No changes" is displayed. > Using CVS plugin 1.6 the cvs polling command looked like this (executed at > 5:26:21 PM EDT): > cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D > "Thursday, March 22, 2012 9:26:21 PM UTC" > Using CVS plugin 2.1, the last cvs checkout command looked like this > (executed at 11:56:16 AM EDT): > cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 > 11:56:16 EDT -d portailInt portailInt > We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12585) SECURITY: LDAP authenticated users switch accounts randomly
[ https://issues.jenkins-ci.org/browse/JENKINS-12585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160846#comment-160846 ] Kohsuke Kawaguchi edited comment on JENKINS-12585 at 3/27/12 5:14 PM: -- Looking into this. For other people seeing this, please report * the way you run Jenkins (be it via "java -jar jenkins.war" or on some other servlet containers) * version of Jenkins * The user realm that you use (does anyone see this with something other than LDAP?) was (Author: kohsuke): Looking into this. For other people seeing this, please report * the way you run Jenkins (be it via "java -jar jenkins.war" or on some other servlet containers) * version of Jenkins > SECURITY: LDAP authenticated users switch accounts randomly > --- > > Key: JENKINS-12585 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12585 > Project: Jenkins > Issue Type: Bug > Components: security >Affects Versions: current > Environment: Mac OSX: 10.6.8 Desktop > Java version: 1.6.0_29 > Access Control > * Security Realm: LDAP > * Authorization: Project-based Matrix Authorization Strategy > Jenkins: 1.448 > Apache > * Server version: Apache/2.2.17 (Unix) > * Server built: Dec 1 2010 09:58:15 >Reporter: guillermo c >Assignee: Kohsuke Kawaguchi >Priority: Critical > > Running Jenkins behind Apache: mod_proxy with HTTPS > https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Apache > So our setup is > Open Directory group > jenkins-admin - Jenkins Admins all > dev-group-a - Developers can view kick off builds > Project-based Matrix Authorization Strategy > Admin all checked > dev-group-a checked: Overall:Read Job:Read,Build Run:Update > dev-group-b checked: Overall:Read Job:Read > issue is I'm an admin and random developer will login and see that there user > id is mine and can admin jenkins. > there has been reported cases that developer A will login and actually be > reported by jenkins as Developer B > were they can no longer trigger CI builds > My biggest concern is when users login and are reporting as admins and have > full access to jenkins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13249) workspace cleanup runs on offline nodes
Erik Purins created JENKINS-13249: - Summary: workspace cleanup runs on offline nodes Key: JENKINS-13249 URL: https://issues.jenkins-ci.org/browse/JENKINS-13249 Project: Jenkins Issue Type: Bug Components: other Reporter: Erik Purins Using jenkins 1.420, jenkins offline node has its workspace folders modified when the node is marked as offline. 1. mark node as offline 2. wait for tasks to complete on node. 3. create a folder that doesn't have a matching job description string in the workspace root. 4. put some files or do some forensics in that folder. 5. wait. 6. confirm java slave agent is still running. 7. Note that eventually folder will be silently pruned, losing data. It was a surprise to me that jenkins deleted my working folder in the workspace (that didn't match any existing job) when the node was offline. Expect that when node is offline, jenkins master does not modify the state of the jenkins workspace directory, and that offline nodes queue their garbage collection or workspace cleaning for another time (when node comes back online, or next reasonable interval). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12585) SECURITY: LDAP authenticated users switch accounts randomly
[ https://issues.jenkins-ci.org/browse/JENKINS-12585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160854#comment-160854 ] Rob Petti commented on JENKINS-12585: - For those who are seeing this issue, are you all running behind a reverse-proxy? > SECURITY: LDAP authenticated users switch accounts randomly > --- > > Key: JENKINS-12585 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12585 > Project: Jenkins > Issue Type: Bug > Components: security >Affects Versions: current > Environment: Mac OSX: 10.6.8 Desktop > Java version: 1.6.0_29 > Access Control > * Security Realm: LDAP > * Authorization: Project-based Matrix Authorization Strategy > Jenkins: 1.448 > Apache > * Server version: Apache/2.2.17 (Unix) > * Server built: Dec 1 2010 09:58:15 >Reporter: guillermo c >Assignee: Kohsuke Kawaguchi >Priority: Critical > > Running Jenkins behind Apache: mod_proxy with HTTPS > https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Apache > So our setup is > Open Directory group > jenkins-admin - Jenkins Admins all > dev-group-a - Developers can view kick off builds > Project-based Matrix Authorization Strategy > Admin all checked > dev-group-a checked: Overall:Read Job:Read,Build Run:Update > dev-group-b checked: Overall:Read Job:Read > issue is I'm an admin and random developer will login and see that there user > id is mine and can admin jenkins. > there has been reported cases that developer A will login and actually be > reported by jenkins as Developer B > were they can no longer trigger CI builds > My biggest concern is when users login and are reporting as admins and have > full access to jenkins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6817) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
[ https://issues.jenkins-ci.org/browse/JENKINS-6817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160855#comment-160855 ] John Muczynski commented on JENKINS-6817: - Hi Vince, Um, you're saying you opened up a jar file and deleted the package? On the Jenkins server or on a node? (Or both?) What gave you the idea that this would help? Thanks, -John > FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: > Unexpected termination of the channel > -- > > Key: JENKINS-6817 > URL: https://issues.jenkins-ci.org/browse/JENKINS-6817 > Project: Jenkins > Issue Type: Bug > Components: clone-workspace, core >Affects Versions: current >Reporter: nirmal_patel >Assignee: abayer >Priority: Blocker > > I am seeing the same on my Windows XP master-slave setup. I am running latest > Hudson ver. 1.363 > I am using the close-workspace-scm plugin to copy my workspace from master to > slave(150). > Started by user anonymous > Building remotely on 150 > FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: > Unexpected termination of the channel > hudson.remoting.RequestAbortedException: > hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected > termination of the channel > at hudson.remoting.Request.call(Request.java:137) > at hudson.remoting.Channel.call(Channel.java:555) > at hudson.FilePath.act(FilePath.java:742) > at hudson.FilePath.act(FilePath.java:735) > at hudson.FilePath.unzip(FilePath.java:415) > at > hudson.FileSystemProvisioner$Default$WorkspaceSnapshotImpl.restoreTo(FileSystemProvisioner.java:227) > at > hudson.plugins.cloneworkspace.CloneWorkspaceSCM$Snapshot.restoreTo(CloneWorkspaceSCM.java:344) > at > hudson.plugins.cloneworkspace.CloneWorkspaceSCM.checkout(CloneWorkspaceSCM.java:126) > at hudson.model.AbstractProject.checkout(AbstractProject.java:1044) > at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:479) > at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:411) > at hudson.model.Run.run(Run.java:1253) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:127) > Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: > Unexpected termination of the channel > at hudson.remoting.Request.abort(Request.java:257) > at hudson.remoting.Channel.terminate(Channel.java:602) > at hudson.remoting.Channel$ReaderThread.run(Channel.java:893) > Caused by: java.io.IOException: Unexpected termination of the channel > at hudson.remoting.Channel$ReaderThread.run(Channel.java:875) > Caused by: java.io.EOFException > at java.io.ObjectInputStream$BlockDataInputStream.peekByte(Unknown Source) > at java.io.ObjectInputStream.readObject0(Unknown Source) > at java.io.ObjectInputStream.readObject(Unknown Source) > at hudson.remoting.Channel$ReaderThread.run(Channel.java:869) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12104) cvs-plugin doesn't catch file changes if the files are checked out with -f -r (HEAD or branch)
[ https://issues.jenkins-ci.org/browse/JENKINS-12104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160856#comment-160856 ] Alex Lehmann commented on JENKINS-12104: I still have the problem in the 2.1 plugin, the files that are not in the branch are not picked up by rlog and the changes are not noticed Building in workspace /home/lehmann/.jenkins/jobs/cvstest/workspace cvs update -d -P -f -r BRANCHTEST workspace cvs update: Updating workspace U workspace/branch1 U workspace/branch2 cvs rlog: Logging home/lehmann/cvstest cvs rlog: warning: no revision `BRANCHTEST' in `/usr/local/cvsroot/home/lehmann/cvstest/file1,v' cvs rlog: warning: no revision `BRANCHTEST' in `/usr/local/cvsroot/home/lehmann/cvstest/file2,v' cvs rlog: warning: no revision `BRANCHTEST' in `/usr/local/cvsroot/home/lehmann/cvstest/file3,v' Finished: SUCCESS (files named branch* are branched, files name file* are not) > cvs-plugin doesn't catch file changes if the files are checked out with -f -r > (HEAD or branch) > -- > > Key: JENKINS-12104 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12104 > Project: Jenkins > Issue Type: Bug > Components: cvs > Environment: suse linux, java 1.6.0-30, Jenkins 1.443, cvs-plugin 1.6 >Reporter: Alex Lehmann >Assignee: Michael Clarke >Priority: Minor > Fix For: current > > > When checking out a cvs repository with Branch and Use HEAD revision if tag > not found, the Changes list is always empty even though the build was > triggered by scm changes that are picked up the by cvs update in the build > log. > Since the use Head function was introduced by me in 1.5, maybe the update > check is broken in a way I didn't notice, I will try to fix this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12104) cvs-plugin doesn't catch file changes if the files are checked out with -f -r (HEAD or branch)
[ https://issues.jenkins-ci.org/browse/JENKINS-12104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Lehmann reopened JENKINS-12104: issue is still present or appeared again in 2.1 > cvs-plugin doesn't catch file changes if the files are checked out with -f -r > (HEAD or branch) > -- > > Key: JENKINS-12104 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12104 > Project: Jenkins > Issue Type: Bug > Components: cvs > Environment: suse linux, java 1.6.0-30, Jenkins 1.443, cvs-plugin 1.6 >Reporter: Alex Lehmann >Assignee: Michael Clarke >Priority: Minor > Fix For: current > > > When checking out a cvs repository with Branch and Use HEAD revision if tag > not found, the Changes list is always empty even though the build was > triggered by scm changes that are picked up the by cvs update in the build > log. > Since the use Head function was introduced by me in 1.5, maybe the update > check is broken in a way I didn't notice, I will try to fix this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13227) CVS plugin 2.1 does not detect changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160853#comment-160853 ] Guillaume Bilodeau edited comment on JENKINS-13227 at 3/27/12 5:52 PM: --- Right. RCS file: /usr/local/cvs/repcvs/PortailInternetMouvement/portailInt/Portail/src/com/xxx/pvm/portail/taglib/I18nBundleTag.java,v Working file: Portail/src/com/xxx/pvm/portail/taglib/I18nBundleTag.java head: 1.3 branch: locks: strict access list: symbolic names: d-chg00014229_op_impl_2012-03-25_v06: 1.1.2.4 d-chg00014229_op_impl_2012-03-25_v05: 1.1.2.4 aq_op_2012-03-25_v04: 1.1.2.4 d-chg00014229_op_impl_2012-03-25_v04: 1.1.2.4 aq_op_2012-03-25_v03: 1.1.2.3 d-chg00014229_op_impl_2012-03-25_v03: 1.1.2.3 d-chg00014229_op_impl_2012-03-25_v02: 1.1.2.3 aq_op_2012-03-25_v01: 1.1 d-chg00014229_op_impl_2012-03-25_v01: 1.1 d-chg00014229_op_brc_preimp-op-2012-02-27: 1.1.0.2 preimp_op_2012-02-27: 1.1 keyword substitution: kv total revisions: 8; selected revisions: 3 description: revision 1.1.2.5 date: 2012/03/23 15:42:50; author: ba0chzi; state: Exp; lines: +4 -26 Organize imports revision 1.1.2.4 date: 2012/03/13 14:18:27; author: ba0chmn; state: Exp; lines: +1 -1 Changement de scope de request ou session pour application dans le but d'améliorer les performances revision 1.1.2.3 date: 2012/03/06 21:19:03; author: ba0chmn; state: Exp; lines: +14 -8 Utilisation des services de récupération de fichier dans UCM de xxx was (Author: gbilodeau): RCS file: /usr/local/cvs/repcvs/PortailInternetMouvement/portailInt/Portail/src/com/xxx/pvm/portail/taglib/I18nBundleTag.java,v Working file: Portail/src/com/xxx/pvm/portail/taglib/I18nBundleTag.java head: 1.3 branch: locks: strict access list: symbolic names: d-chg00014229_op_impl_2012-03-25_v06: 1.1.2.4 d-chg00014229_op_impl_2012-03-25_v05: 1.1.2.4 aq_op_2012-03-25_v04: 1.1.2.4 d-chg00014229_op_impl_2012-03-25_v04: 1.1.2.4 aq_op_2012-03-25_v03: 1.1.2.3 d-chg00014229_op_impl_2012-03-25_v03: 1.1.2.3 d-chg00014229_op_impl_2012-03-25_v02: 1.1.2.3 aq_op_2012-03-25_v01: 1.1 d-chg00014229_op_impl_2012-03-25_v01: 1.1 d-chg00014229_op_brc_preimp-op-2012-02-27: 1.1.0.2 preimp_op_2012-02-27: 1.1 keyword substitution: kv total revisions: 8; selected revisions: 3 description: revision 1.1.2.5 date: 2012/03/23 15:42:50; author: ba0chzi; state: Exp; lines: +4 -26 Organize imports revision 1.1.2.4 date: 2012/03/13 14:18:27; author: ba0chmn; state: Exp; lines: +1 -1 Changement de scope de request ou session pour application dans le but d'améliorer les performances revision 1.1.2.3 date: 2012/03/06 21:19:03; author: ba0chmn; state: Exp; lines: +14 -8 Utilisation des services de récupération de fichier dans UCM de xxx > CVS plugin 2.1 does not detect changes > -- > > Key: JENKINS-13227 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13227 > Project: Jenkins > Issue Type: Bug > Components: cvs >Reporter: Guillaume Bilodeau > Labels: cvs > > As presented in the user group: > https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4 > We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS > repository for a few weeks now, without any problems. The CVS plugin (v1.6) > was using the local cvsnt install. > We've since upgraded the CVS plugin to version 2.1 (by manually pinning the > plugin) and since then, CVS changes are not detected. The CVS polling log is > triggered properly, tons of "cvs rlog" instructions are sent, but at the end > "No changes" is displayed. > Using CVS plugin 1.6 the cvs polling command looked like this (executed at > 5:26:21 PM EDT): > cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D > "Thursday, March 22, 2012 9:26:21 PM UTC" > Using CVS plugin 2.1, the last cvs checkout command looked like this > (executed at 11:56:16 AM EDT): > cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 > 11:56:16 EDT -d portailInt portailInt > We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12585) SECURITY: LDAP authenticated users switch accounts randomly
[ https://issues.jenkins-ci.org/browse/JENKINS-12585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160858#comment-160858 ] Christian Höltje commented on JENKINS-12585: For our setup, we use Tomcat. We use LDAP exclusively, so we don't have another realm. We are behind an apache reverse proxy. I had "sniper" try using :8080 (the non-reverse-proxied url) and he isn't losing his login. This may be because a) he has never had a cookie/session for that URL or b) the proxy is messing things up (but how?). PS: I'm 'docwhat' on IRC. > SECURITY: LDAP authenticated users switch accounts randomly > --- > > Key: JENKINS-12585 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12585 > Project: Jenkins > Issue Type: Bug > Components: security >Affects Versions: current > Environment: Mac OSX: 10.6.8 Desktop > Java version: 1.6.0_29 > Access Control > * Security Realm: LDAP > * Authorization: Project-based Matrix Authorization Strategy > Jenkins: 1.448 > Apache > * Server version: Apache/2.2.17 (Unix) > * Server built: Dec 1 2010 09:58:15 >Reporter: guillermo c >Assignee: Kohsuke Kawaguchi >Priority: Critical > > Running Jenkins behind Apache: mod_proxy with HTTPS > https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Apache > So our setup is > Open Directory group > jenkins-admin - Jenkins Admins all > dev-group-a - Developers can view kick off builds > Project-based Matrix Authorization Strategy > Admin all checked > dev-group-a checked: Overall:Read Job:Read,Build Run:Update > dev-group-b checked: Overall:Read Job:Read > issue is I'm an admin and random developer will login and see that there user > id is mine and can admin jenkins. > there has been reported cases that developer A will login and actually be > reported by jenkins as Developer B > were they can no longer trigger CI builds > My biggest concern is when users login and are reporting as admins and have > full access to jenkins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13112) Adding any post-build step as a build step causes exception
[ https://issues.jenkins-ci.org/browse/JENKINS-13112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-13112 started by domi. > Adding any post-build step as a build step causes exception > --- > > Key: JENKINS-13112 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13112 > Project: Jenkins > Issue Type: Bug > Components: conditional-buildstep > Environment: Windows Server 2008 >Reporter: Anthony Hartwig >Assignee: domi > Attachments: stacktrace.txt > > > When attempting to add a post build step as a build step, then click save, an > exception is thrown. Stack trace attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13112) Adding any post-build step as a build step causes exception
[ https://issues.jenkins-ci.org/browse/JENKINS-13112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160859#comment-160859 ] domi commented on JENKINS-13112: hmm, something seems not to be right with the version mention... postbuild steps have been introduced with core 1.433 - which is after 1.424.6 which post builds are you talking about? m2-extra-steps? (deprecated, as this is included in the core with 1.433) > Adding any post-build step as a build step causes exception > --- > > Key: JENKINS-13112 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13112 > Project: Jenkins > Issue Type: Bug > Components: conditional-buildstep > Environment: Windows Server 2008 >Reporter: Anthony Hartwig >Assignee: domi > Attachments: stacktrace.txt > > > When attempting to add a post build step as a build step, then click save, an > exception is thrown. Stack trace attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12104) cvs-plugin doesn't catch file changes if the files are checked out with -f -r (HEAD or branch)
[ https://issues.jenkins-ci.org/browse/JENKINS-12104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160860#comment-160860 ] Michael Clarke commented on JENKINS-12104: -- Can you run the following command and paste the output here: cvs rlog -d"22 Mar 2012 09:26:21 -0400<27 Mar 2012 12:00:00 -0400" -S -rBRANCHTEST cvstest (change the dates to match the start time of your previous builds)? > cvs-plugin doesn't catch file changes if the files are checked out with -f -r > (HEAD or branch) > -- > > Key: JENKINS-12104 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12104 > Project: Jenkins > Issue Type: Bug > Components: cvs > Environment: suse linux, java 1.6.0-30, Jenkins 1.443, cvs-plugin 1.6 >Reporter: Alex Lehmann >Assignee: Michael Clarke >Priority: Minor > Fix For: current > > > When checking out a cvs repository with Branch and Use HEAD revision if tag > not found, the Changes list is always empty even though the build was > triggered by scm changes that are picked up the by cvs update in the build > log. > Since the use Head function was introduced by me in 1.5, maybe the update > check is broken in a way I didn't notice, I will try to fix this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13227) CVS plugin 2.1 does not detect changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160861#comment-160861 ] Michael Clarke commented on JENKINS-13227: -- So it seems to be CVS rlog missing out changes although I don't know why. Unfortunately moving to 'log' probably isn't a suitable alternative since in only picks up changes to files in the workspace and not new files in the repository. Do you have any customisations to your CVS server or any specific hooks or triggers that may be interfering with the rlog command? > CVS plugin 2.1 does not detect changes > -- > > Key: JENKINS-13227 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13227 > Project: Jenkins > Issue Type: Bug > Components: cvs >Reporter: Guillaume Bilodeau > Labels: cvs > > As presented in the user group: > https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4 > We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS > repository for a few weeks now, without any problems. The CVS plugin (v1.6) > was using the local cvsnt install. > We've since upgraded the CVS plugin to version 2.1 (by manually pinning the > plugin) and since then, CVS changes are not detected. The CVS polling log is > triggered properly, tons of "cvs rlog" instructions are sent, but at the end > "No changes" is displayed. > Using CVS plugin 1.6 the cvs polling command looked like this (executed at > 5:26:21 PM EDT): > cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D > "Thursday, March 22, 2012 9:26:21 PM UTC" > Using CVS plugin 2.1, the last cvs checkout command looked like this > (executed at 11:56:16 AM EDT): > cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 > 11:56:16 EDT -d portailInt portailInt > We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13250) cobertura coverage dashboard portlet not using numeric sort for percent columns
Greg Moncreaff created JENKINS-13250: Summary: cobertura coverage dashboard portlet not using numeric sort for percent columns Key: JENKINS-13250 URL: https://issues.jenkins-ci.org/browse/JENKINS-13250 Project: Jenkins Issue Type: Bug Components: cobertura Affects Versions: current Reporter: Greg Moncreaff Assignee: stephenconnolly e.g. for Lines column, sort goes 93%, 8%, 7%, 29%, 15% instead of going 93%, 29%, 15%, 8%, 7% -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13112) Adding any post-build step as a build step causes exception
[ https://issues.jenkins-ci.org/browse/JENKINS-13112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160862#comment-160862 ] Anthony Hartwig commented on JENKINS-13112: --- I'm attempting to execute Publish JUnit test results. > Adding any post-build step as a build step causes exception > --- > > Key: JENKINS-13112 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13112 > Project: Jenkins > Issue Type: Bug > Components: conditional-buildstep > Environment: Windows Server 2008 >Reporter: Anthony Hartwig >Assignee: domi > Attachments: stacktrace.txt > > > When attempting to add a post build step as a build step, then click save, an > exception is thrown. Stack trace attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13227) CVS plugin 2.1 does not detect changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160863#comment-160863 ] Guillaume Bilodeau commented on JENKINS-13227: -- Not that I know of. I've called the CVS admin (it's a big company...) and he's saying that the whole thing is installed as is. I'll be digging into this with him and let you know what I can find. > CVS plugin 2.1 does not detect changes > -- > > Key: JENKINS-13227 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13227 > Project: Jenkins > Issue Type: Bug > Components: cvs >Reporter: Guillaume Bilodeau > Labels: cvs > > As presented in the user group: > https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4 > We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS > repository for a few weeks now, without any problems. The CVS plugin (v1.6) > was using the local cvsnt install. > We've since upgraded the CVS plugin to version 2.1 (by manually pinning the > plugin) and since then, CVS changes are not detected. The CVS polling log is > triggered properly, tons of "cvs rlog" instructions are sent, but at the end > "No changes" is displayed. > Using CVS plugin 1.6 the cvs polling command looked like this (executed at > 5:26:21 PM EDT): > cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D > "Thursday, March 22, 2012 9:26:21 PM UTC" > Using CVS plugin 2.1, the last cvs checkout command looked like this > (executed at 11:56:16 AM EDT): > cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 > 11:56:16 EDT -d portailInt portailInt > We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13227) CVS plugin 2.1 does not detect changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160863#comment-160863 ] Guillaume Bilodeau edited comment on JENKINS-13227 at 3/27/12 7:23 PM: --- Not that I know of. I called the CVS admin (it's a big company...) and he's saying that the whole thing is installed as is. I'll dig into this and let you know what I find. was (Author: gbilodeau): Not that I know of. I've called the CVS admin (it's a big company...) and he's saying that the whole thing is installed as is. I'll be digging into this with him and let you know what I can find. > CVS plugin 2.1 does not detect changes > -- > > Key: JENKINS-13227 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13227 > Project: Jenkins > Issue Type: Bug > Components: cvs >Reporter: Guillaume Bilodeau > Labels: cvs > > As presented in the user group: > https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4 > We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS > repository for a few weeks now, without any problems. The CVS plugin (v1.6) > was using the local cvsnt install. > We've since upgraded the CVS plugin to version 2.1 (by manually pinning the > plugin) and since then, CVS changes are not detected. The CVS polling log is > triggered properly, tons of "cvs rlog" instructions are sent, but at the end > "No changes" is displayed. > Using CVS plugin 1.6 the cvs polling command looked like this (executed at > 5:26:21 PM EDT): > cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D > "Thursday, March 22, 2012 9:26:21 PM UTC" > Using CVS plugin 2.1, the last cvs checkout command looked like this > (executed at 11:56:16 AM EDT): > cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 > 11:56:16 EDT -d portailInt portailInt > We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12585) SECURITY: LDAP authenticated users switch accounts randomly
[ https://issues.jenkins-ci.org/browse/JENKINS-12585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160864#comment-160864 ] Christian Höltje commented on JENKINS-12585: We had a long troubleshooting session on IRC today and here is our summary (please correct if I make a mistake): On my server, we use Tomcat. It is behind an apache, running a reverse proxy with mod_cache and mod_*_cache. Tomcat sends out JSESSIONID cookie when it thinks a session needs to be set and the previous JSESSIONID is expired or no JSESSIONID is set. Our thought is that some cacheable resources had also had the "Set-Cookie: JSESSIONID" header set. So when someone else loaded that cached resource, they had their JSESSIONID set to someone elses. This is born out by the fact that adding "CacheIgnoreHeaders Set-Cache" to apache seems to have fixed the problem. > SECURITY: LDAP authenticated users switch accounts randomly > --- > > Key: JENKINS-12585 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12585 > Project: Jenkins > Issue Type: Bug > Components: security >Affects Versions: current > Environment: Mac OSX: 10.6.8 Desktop > Java version: 1.6.0_29 > Access Control > * Security Realm: LDAP > * Authorization: Project-based Matrix Authorization Strategy > Jenkins: 1.448 > Apache > * Server version: Apache/2.2.17 (Unix) > * Server built: Dec 1 2010 09:58:15 >Reporter: guillermo c >Assignee: Kohsuke Kawaguchi >Priority: Critical > > Running Jenkins behind Apache: mod_proxy with HTTPS > https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Apache > So our setup is > Open Directory group > jenkins-admin - Jenkins Admins all > dev-group-a - Developers can view kick off builds > Project-based Matrix Authorization Strategy > Admin all checked > dev-group-a checked: Overall:Read Job:Read,Build Run:Update > dev-group-b checked: Overall:Read Job:Read > issue is I'm an admin and random developer will login and see that there user > id is mine and can admin jenkins. > there has been reported cases that developer A will login and actually be > reported by jenkins as Developer B > were they can no longer trigger CI builds > My biggest concern is when users login and are reporting as admins and have > full access to jenkins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13245) Build not starting directly: pending - Waiting for next available executor on ...
[ https://issues.jenkins-ci.org/browse/JENKINS-13245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160865#comment-160865 ] wbauer commented on JENKINS-13245: -- I am seeing the same issues since version 1.452. Executors are all free, but the build does not start for minutes. > Build not starting directly: pending - Waiting for next available executor on > ... > - > > Key: JENKINS-13245 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13245 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current >Reporter: Cees Bos >Priority: Critical > > Last Saterday we upgraded from 1.451 to 1.456 > Sometimes when we trigger a job it comes in the queue with the message: > (pending - Waiting for next available executor on .. servername ..) > This even happens when the slave is totally idle, the job can start directly. > After waiting for a minute it just starts ... > Nothings helps to speed up the execution process -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7246) New jre6 requirement : String.isEmpty
[ https://issues.jenkins-ci.org/browse/JENKINS-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] evernat resolved JENKINS-7246. -- Resolution: Fixed fix is committed in SeleniumhqBuilder.java, revision 40360 the plugin still needs to be released > New jre6 requirement : String.isEmpty > - > > Key: JENKINS-7246 > URL: https://issues.jenkins-ci.org/browse/JENKINS-7246 > Project: Jenkins > Issue Type: Bug > Components: seleniumhq >Affects Versions: current >Reporter: loic_lacombe >Assignee: pascal_martin > > Hi, > A selenium build was automatically launched and failed with the following > exception : > FATAL: java.lang.String.isEmpty()Z > java.lang.NoSuchMethodError: java.lang.String.isEmpty()Z > at > hudson.plugins.seleniumhq.SeleniumhqBuilder.getOthers(SeleniumhqBuilder.java:290) > at > hudson.plugins.seleniumhq.SeleniumhqBuilder.perform(SeleniumhqBuilder.java:239) > at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) > at > hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:601) > at hudson.model.Build$RunnerImpl.build(Build.java:174) > at hudson.model.Build$RunnerImpl.doRun(Build.java:138) > at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416) > at hudson.model.Run.run(Run.java:1248) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:129) > The method String.isEmpty does not exist in java 5, the build fails. > The workaround is to use length() == 0 instead of isEmpty() > I'll checkout the lastest code asap and post a patch :) > Cheers -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13165) Cloning workspace loses hidden files/directories
[ https://issues.jenkins-ci.org/browse/JENKINS-13165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160867#comment-160867 ] Christoph Thelen commented on JENKINS-13165: I have the same problem. To reproduce it I downloaded 1.457, installed "Jenkins Git Plugin" and "Jenkins Clone Workspace SCM Plugin" and set up two Jobs as follows: * "GitJob" using a Git repository, then archiving the workspace and triggering the next job. * "CloneJob" using the previously archived workspace as SCM. CloneJob's workspace will not contain the Git files (.git directory as well as all .gitignore files). Other dot-files are unaffected (eg. Eclipse .project files will be present). As owenmehegan stated, Git files were present in previous Jenkins versions. > Cloning workspace loses hidden files/directories > > > Key: JENKINS-13165 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13165 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current > Environment: Linux >Reporter: owenmehegan >Assignee: Kohsuke Kawaguchi > > I upgraded to Jenkins 1.456 today, and now my jobs that use the Clone > Workspace plugin are having problems because the workspace tar.gz that is > created when the job completes no longer includes the .git directory. In > 1.449, which I ended up downgrading back to, the default setting for files to > include always pulls that in. I've verified this by running tar -tzf on the > workspace.tar.gz; in 1.449 .git is there, in 1.456 it isn't. > I wasn't able to force Jenkins to include it either. I tried putting "**/, > **/.git" and other variations on that in the list of files to include, but > none of them seemed to work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6102) Cannot submit forms in Opera
[
https://issues.jenkins-ci.org/browse/JENKINS-6102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
evernat resolved JENKINS-6102.
--
Resolution: Cannot Reproduce
Hi Tyler,
Not reproduced by Alan and no other news.
Hopefully it was fixed by now. Anyone, please reopen of not.
> Cannot submit forms in Opera
>
>
> Key: JENKINS-6102
> URL: https://issues.jenkins-ci.org/browse/JENKINS-6102
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Environment: Opera: 10.52 (Linux)
>Reporter: R. Tyler Croy
>
> When trying to submit forms with the latest Opera builds (haven't tried on
> older versions of Opera 10) the browser will raise a JavaScript error
> "Maximum recursion depth exceeded" and then submit the form, raising the
> following exception:
> {noformat}
> net.sf.json.JSONException: A JSONObject text must begin with '{' at character
> 1 of init
> at net.sf.json.util.JSONTokener.syntaxError(JSONTokener.java:512)
> at net.sf.json.JSONObject._fromJSONTokener(JSONObject.java:839)
> at net.sf.json.JSONObject._fromString(JSONObject.java:1060)
> at net.sf.json.JSONObject.fromObject(JSONObject.java:176)
> at net.sf.json.JSONObject.fromObject(JSONObject.java:147)
> at
> org.kohsuke.stapler.RequestImpl.getSubmittedForm(RequestImpl.java:711)
> at hudson.model.Hudson.doConfigSubmit(Hudson.java:2241)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:169)
> at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:101)
> at
> org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:54)
> at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:74)
> at
> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:30)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:519)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:435)
> at org.kohsuke.stapler.Stapler.service(Stapler.java:123)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
> at winstone.ServletConfiguration.execute(ServletConfiguration.java:249)
> at winstone.RequestDispatcher.forward(RequestDispatcher.java:335)
> at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:378)
> at
> hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:94)
> at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:86)
> at winstone.FilterConfiguration.execute(FilterConfiguration.java:195)
> at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368)
> at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
> at winstone.FilterConfiguration.execute(FilterConfiguration.java:195)
> at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368)
> 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
> org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
> at
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
> at
> org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
> at
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
> at
> org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
> at
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
> at
> org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
> at
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
> at
> org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173)
> 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:66)
> at
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
> at
>
[JIRA] (JENKINS-7246) New jre6 requirement : String.isEmpty
[ https://issues.jenkins-ci.org/browse/JENKINS-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160866#comment-160866 ] evernat edited comment on JENKINS-7246 at 3/27/12 8:35 PM: --- fix is committed in SeleniumhqBuilder.java, revision 40360 (and 40361) the plugin still needs to be released was (Author: evernat): fix is committed in SeleniumhqBuilder.java, revision 40360 the plugin still needs to be released > New jre6 requirement : String.isEmpty > - > > Key: JENKINS-7246 > URL: https://issues.jenkins-ci.org/browse/JENKINS-7246 > Project: Jenkins > Issue Type: Bug > Components: seleniumhq >Affects Versions: current >Reporter: loic_lacombe >Assignee: pascal_martin > > Hi, > A selenium build was automatically launched and failed with the following > exception : > FATAL: java.lang.String.isEmpty()Z > java.lang.NoSuchMethodError: java.lang.String.isEmpty()Z > at > hudson.plugins.seleniumhq.SeleniumhqBuilder.getOthers(SeleniumhqBuilder.java:290) > at > hudson.plugins.seleniumhq.SeleniumhqBuilder.perform(SeleniumhqBuilder.java:239) > at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) > at > hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:601) > at hudson.model.Build$RunnerImpl.build(Build.java:174) > at hudson.model.Build$RunnerImpl.doRun(Build.java:138) > at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416) > at hudson.model.Run.run(Run.java:1248) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:129) > The method String.isEmpty does not exist in java 5, the build fails. > The workaround is to use length() == 0 instead of isEmpty() > I'll checkout the lastest code asap and post a patch :) > Cheers -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12585) SECURITY: LDAP authenticated users switch accounts randomly
[ https://issues.jenkins-ci.org/browse/JENKINS-12585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160864#comment-160864 ] Christian Höltje edited comment on JENKINS-12585 at 3/27/12 8:40 PM: - We had a long troubleshooting session on IRC today and here is our summary (please correct if I make a mistake): On my server, we use Tomcat. It is behind an apache, running a reverse proxy with mod_cache and mod_*_cache. Tomcat sends out JSESSIONID cookie when it thinks a session needs to be set and the previous JSESSIONID is expired or no JSESSIONID is set. Our thought is that some cacheable resources had also had the "Set-Cookie: JSESSIONID" header set. So when someone else loaded that cached resource, they had their JSESSIONID set to someone elses. This is born out by the fact that adding "CacheIgnoreHeaders Set-Cookie" to apache seems to have fixed the problem. was (Author: docwhat): We had a long troubleshooting session on IRC today and here is our summary (please correct if I make a mistake): On my server, we use Tomcat. It is behind an apache, running a reverse proxy with mod_cache and mod_*_cache. Tomcat sends out JSESSIONID cookie when it thinks a session needs to be set and the previous JSESSIONID is expired or no JSESSIONID is set. Our thought is that some cacheable resources had also had the "Set-Cookie: JSESSIONID" header set. So when someone else loaded that cached resource, they had their JSESSIONID set to someone elses. This is born out by the fact that adding "CacheIgnoreHeaders Set-Cache" to apache seems to have fixed the problem. > SECURITY: LDAP authenticated users switch accounts randomly > --- > > Key: JENKINS-12585 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12585 > Project: Jenkins > Issue Type: Bug > Components: security >Affects Versions: current > Environment: Mac OSX: 10.6.8 Desktop > Java version: 1.6.0_29 > Access Control > * Security Realm: LDAP > * Authorization: Project-based Matrix Authorization Strategy > Jenkins: 1.448 > Apache > * Server version: Apache/2.2.17 (Unix) > * Server built: Dec 1 2010 09:58:15 >Reporter: guillermo c >Assignee: Kohsuke Kawaguchi >Priority: Critical > > Running Jenkins behind Apache: mod_proxy with HTTPS > https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Apache > So our setup is > Open Directory group > jenkins-admin - Jenkins Admins all > dev-group-a - Developers can view kick off builds > Project-based Matrix Authorization Strategy > Admin all checked > dev-group-a checked: Overall:Read Job:Read,Build Run:Update > dev-group-b checked: Overall:Read Job:Read > issue is I'm an admin and random developer will login and see that there user > id is mine and can admin jenkins. > there has been reported cases that developer A will login and actually be > reported by jenkins as Developer B > were they can no longer trigger CI builds > My biggest concern is when users login and are reporting as admins and have > full access to jenkins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12104) cvs-plugin doesn't catch file changes if the files are checked out with -f -r (HEAD or branch)
[
https://issues.jenkins-ci.org/browse/JENKINS-12104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160869#comment-160869
]
Alex Lehmann edited comment on JENKINS-12104 at 3/27/12 9:43 PM:
-
$ cvs rlog -d"14 Feb 2012 09:26:21 +0100<27 Mar 2012 12:00:00 +0100" -S
-rBRANCHTEST home/lehmann/cvstest
cvs rlog: Logging home/lehmann/cvstest
RCS file: /usr/local/cvsroot/home/lehmann/cvstest/branch1,v
head: 1.3
branch:
locks: strict
access list:
symbolic names:
BRANCHTEST: 1.1.0.2
keyword substitution: kv
total revisions: 6; selected revisions: 1
description:
revision 1.1.2.3
date: 2012-03-21 11:37:34 +0100; author: lehmann; state: Exp; lines: +3 -1;
commitid: 100d4f69af6e4567;
cvstest
=
cvs rlog: warning: no revision `BRANCHTEST' in
`/usr/local/cvsroot/home/lehmann/cvstest/file1,v'
cvs rlog: warning: no revision `BRANCHTEST' in
`/usr/local/cvsroot/home/lehmann/cvstest/file2,v'
cvs rlog: warning: no revision `BRANCHTEST' in
`/usr/local/cvsroot/home/lehmann/cvstest/file3,v'
was (Author: alexlehm):
{{monospaced}}
$ cvs rlog -d"14 Feb 2012 09:26:21 +0100<27 Mar 2012 12:00:00 +0100" -S
-rBRANCHTEST home/lehmann/cvstest
cvs rlog: Logging home/lehmann/cvstest
RCS file: /usr/local/cvsroot/home/lehmann/cvstest/branch1,v
head: 1.3
branch:
locks: strict
access list:
symbolic names:
BRANCHTEST: 1.1.0.2
keyword substitution: kv
total revisions: 6; selected revisions: 1
description:
revision 1.1.2.3
date: 2012-03-21 11:37:34 +0100; author: lehmann; state: Exp; lines: +3 -1;
commitid: 100d4f69af6e4567;
cvstest
=
cvs rlog: warning: no revision `BRANCHTEST' in
`/usr/local/cvsroot/home/lehmann/cvstest/file1,v'
cvs rlog: warning: no revision `BRANCHTEST' in
`/usr/local/cvsroot/home/lehmann/cvstest/file2,v'
cvs rlog: warning: no revision `BRANCHTEST' in
`/usr/local/cvsroot/home/lehmann/cvstest/file3,v'
{{monospaced}}
> cvs-plugin doesn't catch file changes if the files are checked out with -f -r
> (HEAD or branch)
> --
>
> Key: JENKINS-12104
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12104
> Project: Jenkins
> Issue Type: Bug
> Components: cvs
> Environment: suse linux, java 1.6.0-30, Jenkins 1.443, cvs-plugin 1.6
>Reporter: Alex Lehmann
>Assignee: Michael Clarke
>Priority: Minor
> Fix For: current
>
>
> When checking out a cvs repository with Branch and Use HEAD revision if tag
> not found, the Changes list is always empty even though the build was
> triggered by scm changes that are picked up the by cvs update in the build
> log.
> Since the use Head function was introduced by me in 1.5, maybe the update
> check is broken in a way I didn't notice, I will try to fix this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12104) cvs-plugin doesn't catch file changes if the files are checked out with -f -r (HEAD or branch)
[
https://issues.jenkins-ci.org/browse/JENKINS-12104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160869#comment-160869
]
Alex Lehmann commented on JENKINS-12104:
{{monospaced}}
$ cvs rlog -d"14 Feb 2012 09:26:21 +0100<27 Mar 2012 12:00:00 +0100" -S
-rBRANCHTEST home/lehmann/cvstest
cvs rlog: Logging home/lehmann/cvstest
RCS file: /usr/local/cvsroot/home/lehmann/cvstest/branch1,v
head: 1.3
branch:
locks: strict
access list:
symbolic names:
BRANCHTEST: 1.1.0.2
keyword substitution: kv
total revisions: 6; selected revisions: 1
description:
revision 1.1.2.3
date: 2012-03-21 11:37:34 +0100; author: lehmann; state: Exp; lines: +3 -1;
commitid: 100d4f69af6e4567;
cvstest
=
cvs rlog: warning: no revision `BRANCHTEST' in
`/usr/local/cvsroot/home/lehmann/cvstest/file1,v'
cvs rlog: warning: no revision `BRANCHTEST' in
`/usr/local/cvsroot/home/lehmann/cvstest/file2,v'
cvs rlog: warning: no revision `BRANCHTEST' in
`/usr/local/cvsroot/home/lehmann/cvstest/file3,v'
{{monospaced}}
> cvs-plugin doesn't catch file changes if the files are checked out with -f -r
> (HEAD or branch)
> --
>
> Key: JENKINS-12104
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12104
> Project: Jenkins
> Issue Type: Bug
> Components: cvs
> Environment: suse linux, java 1.6.0-30, Jenkins 1.443, cvs-plugin 1.6
>Reporter: Alex Lehmann
>Assignee: Michael Clarke
>Priority: Minor
> Fix For: current
>
>
> When checking out a cvs repository with Branch and Use HEAD revision if tag
> not found, the Changes list is always empty even though the build was
> triggered by scm changes that are picked up the by cvs update in the build
> log.
> Since the use Head function was introduced by me in 1.5, maybe the update
> check is broken in a way I didn't notice, I will try to fix this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13251) Allow setting repo-url during repo init
Luciano Carvalho created JENKINS-13251: -- Summary: Allow setting repo-url during repo init Key: JENKINS-13251 URL: https://issues.jenkins-ci.org/browse/JENKINS-13251 Project: Jenkins Issue Type: Improvement Components: repo Affects Versions: current Environment: Jenkins 1.424 + Gerrit Repo plugin 1.2 Reporter: Luciano Carvalho Fix For: current On servers with no internet access, repo init will die with the error below: fatal: Cannot get https://code.google.com/p/git-repo/clone.bundle fatal: error [Errno -2] Name or service not known The only workaround is to create a "url ... insteadOf" rule in the gitconfig. It'd be nice to have the option to set it from the Build Configure interface. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13227) CVS plugin 2.1 does not detect changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160870#comment-160870 ] Sagar Khushalani commented on JENKINS-13227: I am seeing changes on HEAD, but no from branch. Not sure if this helps any. > CVS plugin 2.1 does not detect changes > -- > > Key: JENKINS-13227 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13227 > Project: Jenkins > Issue Type: Bug > Components: cvs >Reporter: Guillaume Bilodeau > Labels: cvs > > As presented in the user group: > https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4 > We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS > repository for a few weeks now, without any problems. The CVS plugin (v1.6) > was using the local cvsnt install. > We've since upgraded the CVS plugin to version 2.1 (by manually pinning the > plugin) and since then, CVS changes are not detected. The CVS polling log is > triggered properly, tons of "cvs rlog" instructions are sent, but at the end > "No changes" is displayed. > Using CVS plugin 1.6 the cvs polling command looked like this (executed at > 5:26:21 PM EDT): > cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D > "Thursday, March 22, 2012 9:26:21 PM UTC" > Using CVS plugin 2.1, the last cvs checkout command looked like this > (executed at 11:56:16 AM EDT): > cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 > 11:56:16 EDT -d portailInt portailInt > We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12585) SECURITY: LDAP authenticated users switch accounts randomly
[ https://issues.jenkins-ci.org/browse/JENKINS-12585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160871#comment-160871 ] Kohsuke Kawaguchi commented on JENKINS-12585: - Thanks to Christian for helping the trouble-shooting session. We couldn't exactly verify our hypothesis during the session. The hypothesis hinges upon having Jenkins send "Set-Cookie" header in a static resource that then gets cached by the reverse proxy, yet the code path that serves those files do not touch HTTP sessions before committing the output, and the Acegi's attempt to create a session afterward resulted in no-op, at least with Winstone. With that said, toward the end, our discussion was mainly around how to fix this, _assuming_ the hypothesis is correct. Since Jenkins as a webapp doesn't exactly know when the 'Set-Cookie' header is set on the response by the container, the solution has to be done on every single response we produce. One thought was to add "Vary: Cookie", and the other was to add "Cache-Control: private". Relevant read [here|http://stackoverflow.com/questions/6491789/http-headers-controlling-cache-and-history-mechanism], which also says IE<9 fails to locally cache the resouce if the Vary header is set (and instead if requires conditional GET.) While driving after the trouble-shooting session, another reason "Vary: Cookie" header is wrong occured to me, which is that if a request does not contain a cookie header (say it expired) and if the response contains "Set-Cookie", "Vary: Cookie" will do no good as the said resource ends up getting cached by the intermediary. So I'm inclined to start serving everything with "Cache-Control: private" unless I hear otherwise. Incidentally, http://ci.jenkins-ci.org/ appears to have this header set on the response, although Jenkins doesn't do this. I suspect haproxy or Apache are doing it. > SECURITY: LDAP authenticated users switch accounts randomly > --- > > Key: JENKINS-12585 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12585 > Project: Jenkins > Issue Type: Bug > Components: security >Affects Versions: current > Environment: Mac OSX: 10.6.8 Desktop > Java version: 1.6.0_29 > Access Control > * Security Realm: LDAP > * Authorization: Project-based Matrix Authorization Strategy > Jenkins: 1.448 > Apache > * Server version: Apache/2.2.17 (Unix) > * Server built: Dec 1 2010 09:58:15 >Reporter: guillermo c >Assignee: Kohsuke Kawaguchi >Priority: Critical > > Running Jenkins behind Apache: mod_proxy with HTTPS > https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Apache > So our setup is > Open Directory group > jenkins-admin - Jenkins Admins all > dev-group-a - Developers can view kick off builds > Project-based Matrix Authorization Strategy > Admin all checked > dev-group-a checked: Overall:Read Job:Read,Build Run:Update > dev-group-b checked: Overall:Read Job:Read > issue is I'm an admin and random developer will login and see that there user > id is mine and can admin jenkins. > there has been reported cases that developer A will login and actually be > reported by jenkins as Developer B > were they can no longer trigger CI builds > My biggest concern is when users login and are reporting as admins and have > full access to jenkins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13252) Grails build step not finding grails
Greg Pagendam-Turner created JENKINS-13252: -- Summary: Grails build step not finding grails Key: JENKINS-13252 URL: https://issues.jenkins-ci.org/browse/JENKINS-13252 Project: Jenkins Issue Type: Bug Components: grails Environment: CentOS release 6.2 (Final) Reporter: Greg Pagendam-Turner Assignee: jeffg2one I installed the grails plugin. Went to Manage Jenkins and setup a grails instance called grails_2.0.1 I selected Install automatically I selected Grails 2.0.1 Saved then created a new job that calls grails test-app target Got the following job output: [webapp] $ grails test-app -clean --non-interactive FATAL: command execution failed java.io.IOException: Cannot run program "grails" (in directory "/var/lib/jenkins/jobs/liftyourgame-grails-master/workspace/webapp"): java.io.IOException: error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:475) at hudson.Proc$LocalProc.(Proc.java:244) at hudson.Proc$LocalProc.(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:707) at hudson.Launcher$ProcStarter.start(Launcher.java:338) at hudson.Launcher$ProcStarter.join(Launcher.java:345) at com.g2one.hudson.grails.GrailsBuilder.perform(GrailsBuilder.java:217) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:700) at hudson.model.Build$RunnerImpl.build(Build.java:178) at hudson.model.Build$RunnerImpl.doRun(Build.java:139) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:470) at hudson.model.Run.run(Run.java:1404) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Caused by: java.io.IOException: java.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.(UNIXProcess.java:164) at java.lang.ProcessImpl.start(ProcessImpl.java:81) at java.lang.ProcessBuilder.start(ProcessBuilder.java:468) ... 15 more Build step 'Build With Grails' marked build as failure Recording test results An attempt to send an e-mail to empty list of recipients, ignored. Finished: FAILURE -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11867) Deployed files have a different time with original files.
[ https://issues.jenkins-ci.org/browse/JENKINS-11867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160872#comment-160872 ] gbois commented on JENKINS-11867: - Do you an idea to achieve that? > Deployed files have a different time with original files. > - > > Key: JENKINS-11867 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11867 > Project: Jenkins > Issue Type: Improvement > Components: artifactdeployer >Affects Versions: current > Environment: Windows Server 2008 using Console >Reporter: xster >Assignee: gbois > Labels: jenkins, plugin > > Deployed files have the time of deployment. > I prefer original file time. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11867) Deployed files have a different time with original files.
[ https://issues.jenkins-ci.org/browse/JENKINS-11867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-11867 started by gbois. > Deployed files have a different time with original files. > - > > Key: JENKINS-11867 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11867 > Project: Jenkins > Issue Type: Improvement > Components: artifactdeployer >Affects Versions: current > Environment: Windows Server 2008 using Console >Reporter: xster >Assignee: gbois > Labels: jenkins, plugin > > Deployed files have the time of deployment. > I prefer original file time. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12031) Maven deploys fail after upgrade to 1.442
[ https://issues.jenkins-ci.org/browse/JENKINS-12031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois updated JENKINS-12031: Assignee: (was: gbois) Component/s: (was: artifactdeployer) > Maven deploys fail after upgrade to 1.442 > - > > Key: JENKINS-12031 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12031 > Project: Jenkins > Issue Type: Bug > Components: maven2 >Affects Versions: current >Reporter: Justin Plock > Labels: build, maven, plugin > > Ever since upgrading to 1.442, I'm unable to deploy packages up in to my > Maven repository hosted in Nexus. > org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed to > deploy artifacts: Could not transfer artifact > com.company.core:dbt-core:jar:1.0.0-20111207.203519-81 from/to > com.company.sandbox > Nexus is returning a 401 response code and I've ensured my credentials are > indeed valid. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12031) Maven deploys fail after upgrade to 1.442
[ https://issues.jenkins-ci.org/browse/JENKINS-12031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] > Maven deploys fail after upgrade to 1.442 > - > > Key: JENKINS-12031 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12031 > Project: Jenkins > Issue Type: Bug > Components: maven2 >Affects Versions: current >Reporter: Justin Plock > Labels: build, maven, plugin > > Ever since upgrading to 1.442, I'm unable to deploy packages up in to my > Maven repository hosted in Nexus. > org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed to > deploy artifacts: Could not transfer artifact > com.company.core:dbt-core:jar:1.0.0-20111207.203519-81 from/to > com.company.sandbox > Nexus is returning a 401 response code and I've ensured my credentials are > indeed valid. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12360) Deploy via ssh
[ https://issues.jenkins-ci.org/browse/JENKINS-12360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-12360 started by gbois. > Deploy via ssh > -- > > Key: JENKINS-12360 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12360 > Project: Jenkins > Issue Type: Improvement > Components: artifactdeployer > Environment: Jenkins host is linux, deploy location is also running > linux >Reporter: Devin Linnington >Assignee: gbois > Labels: artifact, ssh > > I would like to be able to deploy to remote servers via ssh. I caught a > glimpse of ssh deployment in the plugin description but could not get it to > work. Is it implemented? > https://wiki.jenkins-ci.org/display/JENKINS/ArtifactDeployer+Plugin > Also some instructions in the plugin description would be hugely useful. > Thanks, > -Devin -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12360) Deploy via ssh
[ https://issues.jenkins-ci.org/browse/JENKINS-12360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160873#comment-160873 ] gbois commented on JENKINS-12360: - At the moment, only file is supported. Adding other protocols such as ssh is scheduled in my todo list for this plugin. > Deploy via ssh > -- > > Key: JENKINS-12360 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12360 > Project: Jenkins > Issue Type: Improvement > Components: artifactdeployer > Environment: Jenkins host is linux, deploy location is also running > linux >Reporter: Devin Linnington >Assignee: gbois > Labels: artifact, ssh > > I would like to be able to deploy to remote servers via ssh. I caught a > glimpse of ssh deployment in the plugin description but could not get it to > work. Is it implemented? > https://wiki.jenkins-ci.org/display/JENKINS/ArtifactDeployer+Plugin > Also some instructions in the plugin description would be hugely useful. > Thanks, > -Devin -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12565) maven 2/3 job automatically archives the artifact(s) but without the "archive artifacts checkbox" and a pattern post build deploy to fails
[ https://issues.jenkins-ci.org/browse/JENKINS-12565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-12565 started by gbois. > maven 2/3 job automatically archives the artifact(s) but without the "archive > artifacts checkbox" and a pattern post build deploy to fails > -- > > Key: JENKINS-12565 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12565 > Project: Jenkins > Issue Type: Bug > Components: artifactdeployer, core, deploy, maven2 > Environment: Jenkins 1.446 > master on rhel 6 x64 running as a service via the wrapper > slave on windows 2k3 running as a service controlled by master > build job configured as a maven2/3 project >Reporter: sbrinkmeyer >Assignee: gbois >Priority: Minor > Labels: artifact, deployment, jenkins, maven > Attachments: log and config.zip > > > created a new maven 2/3 job that runs maven up to install, used the post > build check box of deploy. on the master i can see the artifacts are > auto-archived. but the post build deploy step is not using these > auto-archived [j|e|w]ar files and or using the maven logic to determine what > the deployable files should be. > the files are archived on master at > jenkins/data/jobs/jobname/buildid/mavenmoduelnames/ as links to > jenkins/data/jobs/jobname/modules/mavenmodulename/builds/buildid/archive/... > i know the master has the files, it just is failing the deploy because the > checkbox is not selected -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11024) Some commands don't work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others
[ https://issues.jenkins-ci.org/browse/JENKINS-11024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160874#comment-160874 ] gouzi commented on JENKINS-11024: - The 'build' command does not work either, as the job name cannot be retrieved: $ java -jar jenkins-cli.jar -s http://localhost:8090 -i ~/.ssh/id_rsa build Project1 -- No such job 'Project1' java -jar jenkins-cli.jar build args... Starts a build, and optionally waits for a completion. (...) -- And Project1 does exist! > Some commands don't work when using _jenkins-cli.jar with -i switch, get-job > and update-job for sure, not certain about others > -- > > Key: JENKINS-11024 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11024 > Project: Jenkins > Issue Type: Bug > Components: cli > Environment: CLI >Reporter: Timothy Meazell > > Add keys for authenticated login. Works fine with who-am-i, enable-job, > disable-job, delete-job, create-job, but get-job and update-job fail claiming > there is no job by that name. The very same command line with enable-job (as > well as the others) works fine. > Workaround is to see if enable-job fails (which it will if there is no job by > that name, which was the point of using get-job), then delete-job and > create-job instead of update-job if the job already exists. Note that this > workaround causes the loss of job history upon deletion. > Diagnostics: > % java -jar jenkins/_jenkins-cli.jar -s http://localhost:9090/ -i > jenkins/id_rsa get-job trunk-pacman.integration.vdev-regression > No such job 'trunk-pacman.integration.vdev-regression' > java -jar jenkins-cli.jar get-job args... > Dumps the job definition XML to stdout > JOB : Name of the job > --username VAL : User name to authenticate yourself to Jenkins > --password VAL : Password for authentication. Note that passing a >password in arguments is insecure. > --password-file VAL : File that contains the password > % java -jar jenkins/_jenkins-cli.jar -s http://localhost:9090/ -i > jenkins/id_rsa enable-job trunk-pacman.integration.vdev-regression > % echo $? > 0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13242) Email Extension plugin - groovy and jelly do not update $rooturl after Jenkins URL updated
[ https://issues.jenkins-ci.org/browse/JENKINS-13242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160875#comment-160875 ] shinsato commented on JENKINS-13242: Found the problem - the java file src/main/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptor.java, in the configure method - is not checking the setting for overrideGlobalSettings before it actually does the overriding. Since I had been playing with the settings - I had entered a string in that field - so that caused the problem. It's not just for the URL setting though - all of the overridden settings can potentially trample on the defaults even if the overrideGlobalSettings checkbox is turned back off. > Email Extension plugin - groovy and jelly do not update $rooturl after > Jenkins URL updated > -- > > Key: JENKINS-13242 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13242 > Project: Jenkins > Issue Type: Bug > Components: email-ext >Affects Versions: current > Environment: Windows 2008 R2 >Reporter: shinsato > > Running the Email Extension plugin - version 2.14.1 with Jenkins 1.424.6 - I > had the Jenkins URL set incorrectly which was causing broken images and the > wrong rooturl in my email-ext status message after a job built (using the > HTML and the included templates). Fixing the Jenkins URL did not fix it. I > then upgraded to Email-ext version 2.19 with Jenkins 1.457. This also did not > fix it. I'm confused because if I "echo %rooturl%" as a Windows Batch script > as a build step - it gives the right response. I can't see any place that the > plugin could be caching this info. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [JIRA] (JENKINS-11938) Jenkins loses builds when restarted
I installed the latest Jenkins 1.457 today on a Windows Server 2003 R2 system. Was able to configure five different jobs, and it worked fine just calling CMD scripts, nothing high-tech. After a system restart or a Jenkins restart, all jobs are gone on the web page. However, the five job folders still exist in c:\Program Files\Jenkins\jobs There are NO "build.xml" files anywhere in the Jenkins directory or subdirectories beneath it. The posted workaround doesn't help me, since I don't have a /tmp folder, and this is Windows, after all. I'm stuck here, and I really want to like Jenkins, but I can't afford to lose all my work after the Jenkins service is restarted. Here's a log snippet, you can see when it tries to load the first job called "Set_eSF_version": Mar 27, 2012 9:22:16 PM winstone.Logger logInternal INFO: Beginning extraction from war file Mar 27, 2012 9:22:17 PM winstone.Logger logInternal INFO: HTTP Listener started: port=8080 Mar 27, 2012 9:22:17 PM winstone.Logger logInternal INFO: AJP13 Listener started: port=8009 Mar 27, 2012 9:22:17 PM winstone.Logger logInternal INFO: Winstone Servlet Engine v0.9.10 running: controlPort=disabled Mar 27, 2012 9:22:17 PM jenkins.InitReactorRunner$1 onAttained INFO: Started initialization Mar 27, 2012 9:22:17 PM hudson.ClassicPluginStrategy createPluginWrapper INFO: Plugin cvs.jpi is disabled Mar 27, 2012 9:22:17 PM jenkins.InitReactorRunner$1 onAttained INFO: Listed all plugins Mar 27, 2012 9:22:17 PM jenkins.InitReactorRunner$1 onAttained INFO: Prepared all plugins Mar 27, 2012 9:22:17 PM jenkins.InitReactorRunner$1 onAttained INFO: Started all plugins Mar 27, 2012 9:22:17 PM jenkins.InitReactorRunner$1 onAttained INFO: Augmented all extensions Mar 27, 2012 9:22:18 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job Set_eSF_version java.lang.NullPointerException at hudson.model.RunMap.load(RunMap.java:216) at hudson.model.AbstractProject.onLoad(AbstractProject.java:255) at hudson.model.Project.onLoad(Project.java:88) at hudson.model.Items.load(Items.java:115) at jenkins.model.Jenkins$15.run(Jenkins.java:2437) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuild er.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$6.runTask(Jenkins.java:838) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source ) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Mar 27, 2012 9:22:18 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job Build only java.lang.NullPointerException at hudson.model.RunMap.load(RunMap.java:216) at hudson.model.AbstractProject.onLoad(AbstractProject.java:255) -- View this message in context: http://jenkins.361315.n4.nabble.com/JIRA-JENKINS-11938-Jenkins-loses-builds-when-restarted-tp4124991p4510804.html Sent from the Jenkins issues mailing list archive at Nabble.com.
Re: [JIRA] (JENKINS-11938) Jenkins loses builds when restarted
I installed the latest Jenkins 1.457 today on a Windows Server 2003 R2 system. Was able to configure five different jobs, and it worked fine just calling CMD scripts, nothing high-tech. After a system restart or a Jenkins restart, all jobs are gone on the web page. However, the five job folders still exist in c:\Program Files\Jenkins\jobs There are NO "build.xml" files anywhere in the Jenkins directory or subdirectories beneath it. The posted workaround doesn't help me, since I don't have a /tmp folder, and this is Windows, after all. I'm stuck here, and I really want to like Jenkins, but I can't afford to lose all my work after the Jenkins service is restarted. Here's a log snippet, you can see when it tries to load the first job called "Set_eSF_version": Mar 27, 2012 9:22:16 PM winstone.Logger logInternal INFO: Beginning extraction from war file Mar 27, 2012 9:22:17 PM winstone.Logger logInternal INFO: HTTP Listener started: port=8080 Mar 27, 2012 9:22:17 PM winstone.Logger logInternal INFO: AJP13 Listener started: port=8009 Mar 27, 2012 9:22:17 PM winstone.Logger logInternal INFO: Winstone Servlet Engine v0.9.10 running: controlPort=disabled Mar 27, 2012 9:22:17 PM jenkins.InitReactorRunner$1 onAttained INFO: Started initialization Mar 27, 2012 9:22:17 PM hudson.ClassicPluginStrategy createPluginWrapper INFO: Plugin cvs.jpi is disabled Mar 27, 2012 9:22:17 PM jenkins.InitReactorRunner$1 onAttained INFO: Listed all plugins Mar 27, 2012 9:22:17 PM jenkins.InitReactorRunner$1 onAttained INFO: Prepared all plugins Mar 27, 2012 9:22:17 PM jenkins.InitReactorRunner$1 onAttained INFO: Started all plugins Mar 27, 2012 9:22:17 PM jenkins.InitReactorRunner$1 onAttained INFO: Augmented all extensions Mar 27, 2012 9:22:18 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job Set_eSF_version java.lang.NullPointerException at hudson.model.RunMap.load(RunMap.java:216) at hudson.model.AbstractProject.onLoad(AbstractProject.java:255) at hudson.model.Project.onLoad(Project.java:88) at hudson.model.Items.load(Items.java:115) at jenkins.model.Jenkins$15.run(Jenkins.java:2437) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuild er.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$6.runTask(Jenkins.java:838) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source ) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Mar 27, 2012 9:22:18 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job Build only java.lang.NullPointerException at hudson.model.RunMap.load(RunMap.java:216) at hudson.model.AbstractProject.onLoad(AbstractProject.java:255) -- View this message in context: http://jenkins.361315.n4.nabble.com/JIRA-JENKINS-11938-Jenkins-loses-builds-when-restarted-tp4124991p4510805.html Sent from the Jenkins issues mailing list archive at Nabble.com.
[JIRA] (JENKINS-13107) Android NDK support not present for auto-dependency download
[ https://issues.jenkins-ci.org/browse/JENKINS-13107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160876#comment-160876 ] Amy Winarske commented on JENKINS-13107: It should be fine for the most recent NDK on linux. The NDK is dependent on the SDK, 1.5 or later. Depending on which sections of the NDK documentation you read, and which version of the NDK you are using, there are also dependencies on the following: gmake (name varies by platform) - env variable GNUMAKE nawk or gnu awk windows: cygwin 1.7 or later While most linux installations won't have a problem with these dependencies, mac and windows will, as always, require special handling. > Android NDK support not present for auto-dependency download > > > Key: JENKINS-13107 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13107 > Project: Jenkins > Issue Type: New Feature > Components: android-emulator >Affects Versions: current >Reporter: Amy Winarske >Assignee: Christopher Orr > > The dependency download is very nice, but doesn't include the NDK, only the > SDK. NDK support would be a big help. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12585) SECURITY: LDAP authenticated users switch accounts randomly
[ https://issues.jenkins-ci.org/browse/JENKINS-12585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160877#comment-160877 ] Christian Höltje commented on JENKINS-12585: Just a clarification. It doesn't have to be a static asset. Tomcat could have (according to the brief description on some stackoverflow article I can't find now) sent it on any page. It doesn't send JSESSIONID on every URL requested, but has some logic for when to do it. The only thing needed to poison apache's cache would be that: a) A page that is cacheable. This isn't always just pages with an "Expires" or "Last-Modified" header. The rules are... a little esoteric at times, and who knows how apache interprets them. b) A page that sent the Set-Cookie header. Also, as you mentioned in IRC, there is no point trying to "recover" a poisoned cache. Your only real choice is to turn off the proxy-cache, or reset it with either a fix (like CacheIgnoreHeader Set-Cache) or the new as-yet-unwritten Jenkins. > SECURITY: LDAP authenticated users switch accounts randomly > --- > > Key: JENKINS-12585 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12585 > Project: Jenkins > Issue Type: Bug > Components: security >Affects Versions: current > Environment: Mac OSX: 10.6.8 Desktop > Java version: 1.6.0_29 > Access Control > * Security Realm: LDAP > * Authorization: Project-based Matrix Authorization Strategy > Jenkins: 1.448 > Apache > * Server version: Apache/2.2.17 (Unix) > * Server built: Dec 1 2010 09:58:15 >Reporter: guillermo c >Assignee: Kohsuke Kawaguchi >Priority: Critical > > Running Jenkins behind Apache: mod_proxy with HTTPS > https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Apache > So our setup is > Open Directory group > jenkins-admin - Jenkins Admins all > dev-group-a - Developers can view kick off builds > Project-based Matrix Authorization Strategy > Admin all checked > dev-group-a checked: Overall:Read Job:Read,Build Run:Update > dev-group-b checked: Overall:Read Job:Read > issue is I'm an admin and random developer will login and see that there user > id is mine and can admin jenkins. > there has been reported cases that developer A will login and actually be > reported by jenkins as Developer B > were they can no longer trigger CI builds > My biggest concern is when users login and are reporting as admins and have > full access to jenkins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11867) Deployed files have a different time with original files.
[ https://issues.jenkins-ci.org/browse/JENKINS-11867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160878#comment-160878 ] xster commented on JENKINS-11867: - I'm not a java developer, so I have no idea about implementing this. Usually Windows copy command preserves file timestamp, and gnu cp command have --preserve option. > Deployed files have a different time with original files. > - > > Key: JENKINS-11867 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11867 > Project: Jenkins > Issue Type: Improvement > Components: artifactdeployer >Affects Versions: current > Environment: Windows Server 2008 using Console >Reporter: xster >Assignee: gbois > Labels: jenkins, plugin > > Deployed files have the time of deployment. > I prefer original file time. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11309) Email notifications are sent on build failures regardless of options
[ https://issues.jenkins-ci.org/browse/JENKINS-11309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slide-O-Mix resolved JENKINS-11309. --- Resolution: Cannot Reproduce > Email notifications are sent on build failures regardless of options > > > Key: JENKINS-11309 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11309 > Project: Jenkins > Issue Type: Bug > Components: email-ext >Affects Versions: current > Environment: Jenkins 1.433 >Reporter: Uri Moszkowicz >Assignee: Slide-O-Mix > > Email notifications are sent on every build failure by default for Jenkins. > As discussed on the mailing list, if email notifications are only desired on > state changes than one should install the email-ext plugin and for each > project add still-failing triggers which all notifications unchecked. > Unfortunately, the proposed solution does not work and the emails are still > sent. Removal of $PROJECT_DEFAULT_RECIPIENTS and $DEFAULT_RECIPIENTS does not > fix the issue either. The only solution that seems to fix the problem is to > disable notifications altogether, an undesirable solution. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13253) Slave connection reset issues since 1.456
Cees Bos created JENKINS-13253:
--
Summary: Slave connection reset issues since 1.456
Key: JENKINS-13253
URL: https://issues.jenkins-ci.org/browse/JENKINS-13253
Project: Jenkins
Issue Type: Bug
Components: core
Environment: 1.456
Reporter: Cees Bos
Priority: Blocker
We upgrade from 1.451 to 1.456 and now we face several issues with connection
reset.
Due to that issue, the jobs are not successful.
On a particular machine we see this very often.
I have captured some stacktraces from the jobs:
{code}
FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException:
Connection reset
hudson.remoting.RequestAbortedException:
hudson.remoting.RequestAbortedException: java.net.SocketException: Connection
reset
at hudson.remoting.Request.call(Request.java:149)
at hudson.remoting.Channel.call(Channel.java:681)
at hudson.Launcher$RemoteLauncher.kill(Launcher.java:821)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:496)
at hudson.model.Run.run(Run.java:1410)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:238)
Caused by: hudson.remoting.RequestAbortedException: java.net.SocketException:
Connection reset
at hudson.remoting.Request.abort(Request.java:273)
at hudson.remoting.Channel.terminate(Channel.java:732)
at hudson.remoting.Channel$ReaderThread.run(Channel.java:1157)
Caused by: java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:185)
at java.io.FilterInputStream.read(FilterInputStream.java:133)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
at java.io.BufferedInputStream.read(BufferedInputStream.java:254)
at
java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2265)
at
java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2558)
at
java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2568)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1314)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:368)
at hudson.remoting.Channel$ReaderThread.run(Channel.java:1127)
{code}
{code}
Archiving artifacts
ERROR: Failed to archive artifacts: allLogs/**/*.*
hudson.util.IOException2: java.io.IOException
at
hudson.remoting.FastPipedInputStream.read(FastPipedInputStream.java:175)
at hudson.util.HeadBufferingStream.read(HeadBufferingStream.java:61)
at java.io.FilterInputStream.read(FilterInputStream.java:107)
at hudson.util.HeadBufferingStream.fillSide(HeadBufferingStream.java:83)
at hudson.FilePath$TarCompression$2.extract(FilePath.java:612)
at hudson.FilePath.copyRecursiveTo(FilePath.java:1729)
at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:116)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at
hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:678)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:656)
at hudson.model.Build$RunnerImpl.post2(Build.java:162)
at
hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:625)
at hudson.model.Run.run(Run.java:1435)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:238)
at hudson.FilePath.copyRecursiveTo(FilePath.java:1736)
at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:116)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at
hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:678)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:656)
at hudson.model.Build$RunnerImpl.post2(Build.java:162)
at
hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:625)
at hudson.model.Run.run(Run.java:1435)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:238)
Caused by: java.util.concurrent.ExecutionException:
hudson.remoting.RequestAbortedException: java.net.SocketException: Connection
reset
at hudson.remoting.Request
