[JIRA] [artifact-promotion-plugin] (JENKINS-30169) Artifactory plugin creates empty commits
Title: Message Title Martin Steiger updated an issue Jenkins / JENKINS-30169 Artifactory plugin creates empty commits Change By: Martin Steiger Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [configurationslicing-plugin] (JENKINS-25320) UnsupportedOperationException when updating "Max # of builds to keep"
Title: Message Title mdonohue commented on JENKINS-25320 Re: UnsupportedOperationException when updating "Max # of builds to keep" Following up on Ninian's comment: Does this still reproduce with the 1.40 release of configurationslicing? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [configurationslicing-plugin] (JENKINS-22551) Changes Saved on Execution Slicer not Saved in config.xml
Title: Message Title mdonohue commented on JENKINS-22551 Re: Changes Saved on Execution Slicer not Saved in config.xml i hadn't heard of the inheritance-plugin before. it seems at odds with the design of the configuration slicing plugin. If anything, I would just put in a warning on the configuration slicing screen explaining that they don't play nice together. Pick one strategy, rather than trying to mix them. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-22802) assets.car code sign failure
Title: Message Title lacostej commented on JENKINS-22802 Re: assets.car code sign failure This is because we need to use the new archivePath argument I think. See http://stackoverflow.com/a/24310447/311450 See also JENKINS-30362 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-30228) [xcode-plugin] Custom xcodebuild arguments should be textarea to make use easier
Title: Message Title lacostej commented on JENKINS-30228 Re: [xcode-plugin] Custom xcodebuild arguments should be textarea to make use easier Thanks ! Do you feel like trying to submit a patch ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-29480) Xcode plugin: dSYMs for embedded frameworks are not packaged
Title: Message Title lacostej commented on JENKINS-29480 Re: Xcode plugin: dSYMs for embedded frameworks are not packaged Hello, thanks for the bug report ! It's my understanding that xcodebuild manages the dSYM generation itself. Have you checked that building the app using xcode manually does add the embedded frameworks symbols as well ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30376) More equals methods on Jenkins runtime objects
Title: Message Title Sam Gleske commented on JENKINS-30376 Re: More equals methods on Jenkins runtime objects Hi Mark Waite, was my explanation sufficient? Would you like me to elaborate on any points I made? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mstest-plugin] (JENKINS-30576) MSTestPublisher removed from job's config.xml when reloaded from disk
Title: Message Title Ivo Bellin Salarin commented on JENKINS-30576 Re: MSTestPublisher removed from job's config.xml when reloaded from disk Hello Kjartan, Thanks for your feedback. I am not able to reproduce this issue neither in my test environment nor in the production one. Could you please have a look at the Jenkins logs, in order to see if some error has been logged? Thanks in advance, Ivo Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-29165) Code sign failed, app will be rejected
Title: Message Title lacostej closed an issue as Won't Fix Bug in Xcode. Patch PackageApplication with xcode < 7 is a workaround Jenkins / JENKINS-29165 Code sign failed, app will be rejected Change By: lacostej Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-29165) Code sign failed, app will be rejected
Title: Message Title lacostej commented on JENKINS-29165 Re: Code sign failed, app will be rejected This is a problem inside xcodebuild itself, as the command that does this is the PackageApplication script part of xcode. I've notified Apple long time ago and haven't heard from them. Other xcodebuild wrapper projects work-around this by patching the PackageApplication step. See https://github.com/fastlane/gym/blob/a9c2fd83b9529fdf00f79f9ec97b238539bc7e3f/lib/assets/package_application_patches/0001_codesign_args_patch.diff Xcode 7 comes with its own way of exporting the archive which should work around this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-29165) Code sign failed, app will be rejected
Title: Message Title
lacostej updated an issue
Jenkins / JENKINS-29165
Code sign failed, app will be rejected
Change By:
lacostej
I'm building an IPA from an Xcode project generated from Unity and using the Xcode plugin to compile the Unity Xcode project into an IPA, which succeeds.I did however need to work around an issue with changes to app signing by Apple as can be read here: https://developer.apple.com/library/mac/technotes/tn2206/_index.html#//apple_ref/doc/uid/DTS40007919-CH1-TNTAG205 Note that it says the app will be rejected if it does not comply to these new rules, even though the app installs and runs just fine.At first these changes failed my build, for which I had to add the following to the Custom x-code build arguments:CODE_SIGN_RESOURCE_RULES_PATH=$(SDKROOT)/ResourceRules.plistIn order to fix a failure related to the changes in app signing, as described here:http://stackoverflow.com/questions/26516442/how-do-we-manually-fix-resourcerules-plist-cannot-read-resources-error-afterWhile this stopped the build from failing I still find the following in the logs: (please note I've changed the project name, company name and user name everywhere, some things are confidential) {code} _"Output directory: '/Users/Shared/Jenkins/Home/jobs/Project X iOS/workspace/Builds/Completed/iOS/IPA/2440 2015.07.01.ipa'Temporary Directory: '/tmp/sd10Ip_V0_' (will NOT be deleted on exit when verbose set)+ /bin/cp -Rp /Users/Shared/Jenkins/Home/jobs/Project X iOS/workspace/Builds/Completed/iOS/Project X.app /tmp/sd10Ip_V0_/PayloadProgram /bin/cp returned 0 : []### Checking original app+ /usr/bin/codesign --verify - /Users/Shared/Jenkins/Home/jobs/Project X iOS/workspace/Builds/Completed/iOS/Project X.appProgram /usr/bin/codesign returned 1 : [/Users/Shared/Jenkins/Home/jobs/Project X iOS/workspace/Builds/Completed/iOS/Project X.app: resource envelope is obsolete (custom omit rules)]Codesign check fails : /Users/Shared/Jenkins/Home/jobs/Project X iOS/workspace/Builds/Completed/iOS/Project X.app: resource envelope is obsolete (custom omit rules)"_ {code} and when attempting to be re-signed: {code} _"### Codesigning '/Users/me/Library/MobileDevice/Provisioning Profiles/GenericInHouseDistributionNoDomain.mobileprovision' with 'iPhone Distribution: Company Name'+ /usr/bin/codesign --force --preserve-metadata=identifier,entitlements,resource-rules --sign iPhone Distribution: Company Name. --resource-rules=/tmp/awnWzkayhO/Payload/Project X.app/ResourceRules.plist --entitlements /tmp/awnWzkayhO/entitlements_plist0PcvLRzr /tmp/awnWzkayhO/Payload/Project X.appProgram /usr/bin/codesign returned 0 : [Warning: usage of --preserve-metadata with option "resource-rules" (deprecated in Mac OS X >= 10.10)!Warning: --resource-rules has been deprecated in Mac OS X >= 10.10!"_ {code} Also when manually verifying the code signing of the app with the Terminal I get the following response:_"/Users/Shared/Jenkins/Home/jobs/Project X iOS/workspace/Builds/Completed/iOS/Project X.app: resource envelope is obsolete (custom omit rules)"_Some googling has led me to discover that changes were made to code signing by Apple in recent updates to OS X / Xcode, deprecating --resource-rules in the _codesign_ command and requiring some other additions, as can be read here: http://stackoverflow.
[JIRA] [xcode-plugin] (JENKINS-28563) allow configuration of derivedDataPath parameter
Title: Message Title lacostej commented on JENKINS-28563 Re: allow configuration of derivedDataPath parameter Thanks ! Would you try adding a pull request ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-28267) When building IPA - Expand 'Output directory' with extra variables
Title: Message Title lacostej commented on JENKINS-28267 Re: When building IPA - Expand 'Output directory' with extra variables If I read the code correctly, right now the code does the following 1. prepare the ipaOutputPath 2. remove existing ipas and dsyms in the global ipaOutputPath 3. for each app a. build the ipa into the ipaOutputPath Your proposal requires us to make the change of making the ipaOutputPath to be app specific. Cleaning in the loop will not work in the same way. I don't use projects that contain multiple apps. I would be happy to know more about those use cases to make sure they don't conflict with this change. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-28163) Codesign verification now needs --no-strict parameter
Title: Message Title lacostej closed an issue as Not A Defect Jenkins / JENKINS-28163 Codesign verification now needs --no-strict parameter Change By: lacostej Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-28256) Xcode plugin does not work when using workspaces
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28256 Re: Xcode plugin does not work when using workspaces Code changed in jenkins User: Jerome Lacoste Path: src/main/java/au/com/rayh/XCodeBuilder.java http://jenkins-ci.org/commit/xcode-plugin/e75d097bd129888d2e5e448556c8b7573694eb4f Log: [FIXED JENKINS-28256] only prepend -allTargets for -project builds Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-28256) Xcode plugin does not work when using workspaces
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-28256 Xcode plugin does not work when using workspaces Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-28256) Xcode plugin does not work when using workspaces
Title: Message Title lacostej commented on JENKINS-28256 Re: Xcode plugin does not work when using workspaces Thanks for the patch ! I suspect it would be cleaner if we were searching for wether the project option is set or not. Making a commit. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30480) documentation of any change in build configuration
Title: Message Title Ronny Borchert commented on JENKINS-30480 Re: documentation of any change in build configuration I installed the plugin, and will try it. thx for this information Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27854) iOS Unit Tests hang after Jenkins Update
Title: Message Title lacostej closed an issue as Won't Fix See above comment Jenkins / JENKINS-27854 iOS Unit Tests hang after Jenkins Update Change By: lacostej Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27854) iOS Unit Tests hang after Jenkins Update
Title: Message Title lacostej commented on JENKINS-27854 Re: iOS Unit Tests hang after Jenkins Update This is a most probably a bug in Xcode 6.2. See http://stackoverflow.com/questions/25380365/timeout-when-running-xcodebuild-tests-under-xcode-6-via-ssh Can be worked around by "converting your Jenkins configuration from being a LaunchDaemon to being a LaunchAgent" Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-29487) stringRep should be a non-empty string, but it's an empty string
Title: Message Title lacostej commented on JENKINS-29487 Re: stringRep should be a non-empty string, but it's an empty string Here's a potential workaround: "set the SDK in Xcode plugin to the value returned by xcodebuild -sdk" See http://stackoverflow.com/questions/31492286/jenkins-xcode-plugin-stringrep-should-be-a-non-empty-string-but-its-an-empty-s Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-30591) Xcode 7: Unit Test failure related to unparseable date
Title: Message Title lacostej commented on JENKINS-30591 Re: Xcode 7: Unit Test failure related to unparseable date Not sure why the jira / github integration didn't kick in at all, it should have linked the PR / commit to this} Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-30591) Xcode 7: Unit Test failure related to unparseable date
Title: Message Title lacostej edited a comment on JENKINS-30591 Re: Xcode 7: Unit Test failure related to unparseable date Not sure why the jira / github integration didn't kick in at all, it should have linked the PR / commit to this } Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-30591) Xcode 7: Unit Test failure related to unparseable date
Title: Message Title lacostej commented on JENKINS-30591 Re: Xcode 7: Unit Test failure related to unparseable date See https://github.com/jenkinsci/xcode-plugin/pull/63 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc-plugin] (JENKINS-30602) Xvnc plugin only looks for .pid files not .log files
Title: Message Title Hays Clark commented on JENKINS-30602 Re: Xvnc plugin only looks for .pid files not .log files Very strange... my job was throwing the error above until I unchecked the "Create a dedicated Xauthority file per build?" checkbox, which fixed by Jenkins job; however, the "Can't find file /home/jenkins/.vnc/[...].pid" error no longer shows up. Starting applications specified in /home/jenkins/.vnc/xstartup Log file is /home/jenkins/.vnc/f49349b862b0:25.log ... 84 of 84 tests passed. All tests passed! Terminating xvnc. $ vncserver -kill :25 Killing Xvnc4 process ID 165 Finished: SUCCESS Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc-plugin] (JENKINS-30602) Xvnc plugin only looks for .pid files not .log files
Title: Message Title Hays Clark updated an issue Jenkins / JENKINS-30602 Xvnc plugin only looks for .pid files not .log files Change By: Hays Clark Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc-plugin] (JENKINS-30602) Xvnc plugin only looks for .pid files not .log files
Title: Message Title Hays Clark edited a comment on JENKINS-30602 Re: Xvnc plugin only looks for .pid files not .log files Hrm after looking at the plug-in code [(line 229 of Xvnc.java) ]( | https://github.com/jenkinsci/xvnc-plugin/blob/master/src/main/java/hudson/plugins/xvnc/Xvnc.java#L229 ) ] , I'm wondering if the actual bug is in Xvnc server when 'kill' is called on the pid. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc-plugin] (JENKINS-30602) Xvnc plugin only looks for .pid files not .log files
Title: Message Title Hays Clark commented on JENKINS-30602 Re: Xvnc plugin only looks for .pid files not .log files Hrm after looking at the plug-in code [(line 229 of Xvnc.java)](https://github.com/jenkinsci/xvnc-plugin/blob/master/src/main/java/hudson/plugins/xvnc/Xvnc.java#L229), I'm wondering if the actual bug is in Xvnc server when 'kill' is called on the pid. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc-plugin] (JENKINS-30602) Xvnc plugin only looks for .pid files not .log files
Title: Message Title
Hays Clark created an issue
Jenkins / JENKINS-30602
Xvnc plugin only looks for .pid files not .log files
Issue Type:
Bug
Assignee:
Levon Saldamli
Components:
xvnc-plugin
Created:
23/Sep/15 12:47 AM
Priority:
Major
Reporter:
Hays Clark
I short, it seems like the latest version of Xvnc is outputting a .log file by default, and the Jenkins Xvnc plug-in is only looking for .pid files when cleaning up after the job has run. It seems like all that needs to be done is look for both .pid and .log files in the cleanup step.
Example log file:
Started by user Foo
...
Starting xvnc
[Job Name] $ vncserver :66 -geometry 1280x1024 -depth 24
sh: 1: Syntax error: "(" unexpected
sh: 1: Syntax error: "(" unexpected
New '36e5ed42de5a:66 (jenkins)' desktop is 36e5ed42de5a:66
Starting applications specified in /home/jenkins/.vnc/xstartup
Log file is /home/jenkins/.vnc/36e5ed42de5a:66.log
...
Terminating xvnc.
$ vncserver -kill :66
Can't find file /home/jenkins/.vnc/36e5ed42de5a:66.pid
You'll have to kill the Xvnc4 process manually
Finished: SUCCESS
Role: UI Developer with Java Script + Angular JS||ONLY LOCAL
Hi Partners, Hope this reach you in good time. Please check the bellow job details and send me your updated resume if you are available and interested At cha...@intellilinktech.com or reach me at 732-400-1778 x102 *Role: UI Developer with Java Script + Angular JS* *Location: Bay Area, CA* *Duration: Long Term* *Need Locals only* Thanks & Regards ? CHAKRI Sr.Recruiter Email: cha...@intellilinktech.com IntelliLink Technologies Inc. G/Y ID: chrakri.sreeinfo Ph: *732-400-1778 Ext:102* Fax: 732-200-0646 www.intellilinktech.com -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Role:Java Backend with Spring and REST||ONLY LOCAL
Hi Partners, Hope this reach you in good time. Please check the bellow job details and send me your updated resume if you are available and interested At cha...@intellilinktech.com or reach me at 732-400-1778 x102 *Role:* *Java Backend with Spring and REST* *Location: Bay Area, CA* *Duration: Long Term* *Need Locals only* Thanks & Regards ? CHAKRI Sr.Recruiter Email: cha...@intellilinktech.com IntelliLink Technologies Inc. G/Y ID: chrakri.sreeinfo Ph: *732-400-1778 Ext:102* Fax: 732-200-0646 www.intellilinktech.com -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-30601) GitHub Pull Request Builder cannot set commit status on GitHub Enterprise 2.1
Title: Message Title Geoffrey Begen created an issue Jenkins / JENKINS-30601 GitHub Pull Request Builder cannot set commit status on GitHub Enterprise 2.1 Issue Type: Bug Assignee: Honza Brázdil Components: ghprb-plugin Created: 22/Sep/15 11:18 PM Priority: Major Reporter: Geoffrey Begen Our organization recently updated to GitHub Enterprise 2.1 from 11.10.340. When this happened, our job to build pull requests stopped updating the pull request status. The console output from the job reads: Setting status of ... to SUCCESS with url ... and message: 'Build finished. ... tests run, ... skipped, ... failed.' Could not update commit status of the Pull Request on GitHub. java.io.IOException: Failed to deserialize [] at org.kohsuke.github.Requester.parse(Requester.java:464) at org.kohsuke.github.Requester._to(Requester.java:227) at org.kohsuke.github.Requester.to(Requester.java:194) at org.kohsuke.github.GHRepository.createCommitStatus(GHRepository.java:829) at org.jenkinsci.plugins.ghprb.extensions.status.GhprbSimpleStatus.createCommitStatus(GhprbSimpleStatus.java:179) at org.jenkinsci.plugins.ghprb.extensions.status.GhprbSimpleStatus.onBuildComplete(GhprbSimpleStatus.java:160) at org.jenkinsci.plugins.ghprb.GhprbBuilds.onCompleted(GhprbBuilds.java:167) at org.jenkinsci.plugins.ghprb.GhprbBuildListener.onCompleted(GhprbBuildListener.java:27) at org.jenkinsci.plugins.ghprb.GhprbBuildListener.onCompleted(GhprbBuildListener.java:12) at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:199) at hudson.
[JIRA] [p4-plugin] (JENKINS-29703) Jenkins unable to sync workspace
Title: Message Title Michael Rose commented on JENKINS-29703 Re: Jenkins unable to sync workspace I was able to recover by disconnecting the node that was giving problems and launching the slave agent again. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-21342) CliGitAPIImpl is hard-coded to use LocalLauncher
Title: Message Title Nicolas De Loof commented on JENKINS-21342 Re: CliGitAPIImpl is hard-coded to use LocalLauncher please see https://github.com/jenkinsci/git-client-plugin/pull/186 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-slaves-plugin] (JENKINS-30600) git isn't ran inside build container
Title: Message Title Nicolas De Loof created an issue Jenkins / JENKINS-30600 git isn't ran inside build container Issue Type: Bug Assignee: Nicolas De Loof Components: docker-slaves-plugin, git-client-plugin Created: 22/Sep/15 10:25 PM Priority: Minor Reporter: Nicolas De Loof Using docker-slaves, the checkout build phase is ran with commands inside the remoting container (which by change has git) not inside the configured build container. This is due to git-client to create it's own LocalLauncher vs using the Node's one. Add Comment
[JIRA] [jira-plugin] (JENKINS-30246) Create Jira Issue not working
Title: Message Title owenmehegan commented on JENKINS-30246 Re: Create Jira Issue not working Part of my issue was just that I had configured the plugin incorrectly for connecting to JIRA. But here: https://github.com/jenkinsci/jira-plugin/blob/master/src/main/java/hudson/plugins/jira/JiraCreateIssueNotifier.java#L242 The plugin seems to try to find an existing JIRA issue, and if it can't, it just uses println to log something to the console without any other context. Using the Jenkins logger class, and maybe a better error message (it's not actually looking for a file), would help. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-30591) Xcode 7: Unit Test failure related to unparseable date
Title: Message Title lacostej resolved as Fixed Jenkins / JENKINS-30591 Xcode 7: Unit Test failure related to unparseable date Change By: lacostej Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifact-promotion-plugin] (JENKINS-30169) Artifactory plugin creates empty commits
Title: Message Title hcguersoy commented on JENKINS-30169 Re: Artifactory plugin creates empty commits Hi Martin, I don't see any involvement of the artifact-promotion-plugin. If I overlooked something give me pls a hint. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-29604) git-client CLI implementation does not propogate username
Title: Message Title Jacob Keller commented on JENKINS-29604 Re: git-client CLI implementation does not propogate username I can't really help further at this point. Until submodules are properly supported with credentials this may be an issue. I do not know how Windows is configuring SSH and why it wouldn't read the ssh configuration file. The issue is that we don't support specifying credentials in submodules at this time, so it uses the defaults. I believe that the defaults are not working because of difference in user that is somehow corrected in your command line example. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20262) Fix for JENKINS-18629 caused a regression in several plugins
Title: Message Title Jesse Glick commented on JENKINS-20262 Re: Fix for JENKINS-18629 caused a regression in several plugins Daniel Beck it was actually Kohsuke Kawaguchi who wrote that. From looking at DataBoundResolvable, it does sound like the same thing. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-30580) Trigger MultiJob Plugin Phases upon Job Completion
Title: Message Title
Christian Goetze commented on JENKINS-30580
Re: Trigger MultiJob Plugin Phases upon Job Completion
Currently, the multijob plugin allows you to group sub-jobs into phases, which get executed sequentially:
phase1 {
left1()
right1()
...
}
phase2 {
left2()
right2()
...
}
phase3 {
aggregate()
}
In this example, phase1 will launch left1() and right1(), phase2 will wait until left1() and right1() completes and then launch left2() and right2(). phase3 waits until phase2 completes, then launches aggregate().
The desired modification is to add a property to the phase which explicitly lists the jobs to wait on prior to launching, so, for example, in this case we would say:
leftPhase1 {
left1()
}
leftPhase2(waitFor: [ left1 ]) {
left2()
}
rightPhase1 {
right1()
}
rightPhase2(waitFor: [ right1 ]) {
right2()
}
aggregatePhase(waitFor: [ left2, right2 ]) {
aggregate()
}
This means that multiple phases can be running at a given time.
Launching new jobs as soon as their prerequisite jobs complete will generally lead to a better schedule than having to lockstep the phases, and is certainly better than linearizing the build. It is easy to see that the new method will always deliver the shortest build time as long as sufficient executors are available. Since we are usually not too much constrained by the number of executors, this will most certainly improve build times.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [git-client-plugin] (JENKINS-29604) git-client CLI implementation does not propogate username
Title: Message Title Peter Toft commented on JENKINS-29604 Re: git-client CLI implementation does not propogate username I just tested this approach (and thank you for helping) - but I see the same problem. I use git-bash, which on the command line works fine (even with submodules). If you have other tricks or want help testing - let me know, I can support. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20262) Fix for JENKINS-18629 caused a regression in several plugins
Title: Message Title Daniel Beck commented on JENKINS-20262 Re: Fix for JENKINS-18629 caused a regression in several plugins define an interface in Stapler that allows an object to nominate its own replacement Jesse Glick Is https://github.com/stapler/stapler/blob/master/core/src/main/java/org/kohsuke/stapler/DataBoundResolvable.java what you meant here? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-22542 Re: Subversion polling not work with externals or variables in URL - E200015: No credential to try. Hi, I said I found the bug but if you configure the additional credentials in a right way, everything works fine. In my case, I configured a credentials (in additional credentials) using this realm example real. It is very important that the realm is written rightly. Here you can see two console outputs (SCM Polling): Started on Sep 22, 2015 10:24:00 PM Received SCM poll call on master for JENKINS-22542 on Sep 22, 2015 10:24:00 PM svn://192.168.1.106/JENKINS-22542 is at revision 7 svn://192.168.1.106/external1 is at revision 4 svn://192.168.1.106/external2 is at revision 1 Done. Took 0.18 sec No changes Started on Sep 22, 2015 10:26:00 PM Received SCM poll call on master for JENKINS-22542 on Sep 22, 2015 10:26:00 PM svn://192.168.1.106/JENKINS-22542 is at revision 8 (changed from 7) svn://192.168.1.106/external1 is at revision 4 svn://192.168.1.106/external2 is at revision 1 Done. Took 24 ms Changes found Regards, Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [notification-plugin] (JENKINS-30599) Add a "Job Failed" event type
Title: Message Title Jason Mathison created an issue Jenkins / JENKINS-30599 Add a "Job Failed" event type Issue Type: Improvement Assignee: Unassigned Components: notification-plugin Created: 22/Sep/15 8:28 PM Priority: Minor Reporter: Jason Mathison We have a number of Jenkins jobs that are chained together as the binary is built once and then deployed and tested in multiple environments. Getting a notification for each part that completes throws a lot of chaff into our meeting room, however we would want to see any failures that occur. My suggestion is to have an "Event type" of "Job Failed" that I can use to only get notifications if the job failed. Add Comment
[JIRA] [git-client-plugin] (JENKINS-29604) git-client CLI implementation does not propogate username
Title: Message Title Jacob Keller commented on JENKINS-29604 Re: git-client CLI implementation does not propogate username I do not know where the ssh configuration will be taken from in Windows, sorry. I would consult the documentation of Git-for-Windows or the SSH package you have installed to use with Git. I would assume it would be under %APPDATA%/.ssh/config of the user running Jenkins, which in your case appears to be Administrator. This works on linux either because jenkins itself is already running as "jenkins" user, or you have an .ssh/user configuration correctly setup for use "jenkins". Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-testresult-plugin] (JENKINS-30598) Support "Around" like "Before" and "After"
Title: Message Title
Brian Cassidy created an issue
Jenkins / JENKINS-30598
Support "Around" like "Before" and "After"
Issue Type:
Improvement
Assignee:
James Nord
Components:
cucumber-testresult-plugin
Created:
22/Sep/15 7:31 PM
Priority:
Minor
Reporter:
Brian Cassidy
Perhaps I'm wrong here, but...
When I did my first build parsing the cucumber.js's json output, i received the following error:
{{ERROR: Step: {Around } name: {null} received before previous step: {Around }
name: {null}
handled! Maybe caused by broken JSON, see #
JENKINS-21835
}}
I tried to grep the plugin source for "around" and didn't find anything of note, though there are plenty of mentions of "before" and "after."
So, if this plugin doesn't recognize the "around" keyword, it would be nice if did much like "before" and "after"
[JIRA] [cucumber-testresult-plugin] (JENKINS-30597) Context menu arrows return 404
Title: Message Title Brian Cassidy created an issue Jenkins / JENKINS-30597 Context menu arrows return 404 Issue Type: Bug Assignee: James Nord Components: cucumber-testresult-plugin Created: 22/Sep/15 7:26 PM Priority: Minor Reporter: Brian Cassidy As you hover over a feature, scenario, etc, a down-arrow appears. If you click on the arrow, a contextMenu xhr request fires in the background. Unfortunately, they all seem to fail with a 404 not found response. So, either this plugin doesn't support that functionality and they should be hidden, or something else is wrong and is breaking the menus. Add Comment
[JIRA] [cmakebuilder-plugin] (JENKINS-30070) Automatic download and installation of cmake from cmake.org
Title: Message Title Martin Weber commented on JENKINS-30070 Re: Automatic download and installation of cmake from cmake.org Guillaume Egles Thanks for reporting this. Which JRE is installed on your system? The plugin in fact compares the java system property os.arch against "amd64". IIRC, "amd64" is documented for the 64-bit JRE provided by Apple, but maybe OpenJDK uses a different value. A related problem: cmake.org has both binaries for OS "Darwin" and "Darwin64" and uses "universal" and "x86_64" for the architecture value, which is confusing. Maybe you can explain what that mean. With your knowledge of java on OS X, please inspect the mapping code at link https://github.com/jenkinsci/cmakebuilder-plugin/blob/master/src/main/java/hudson/plugins/cmake/CmakeInstaller.java#L373 and make suggestions, if you can understand java code. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-29604) git-client CLI implementation does not propogate username
Title: Message Title Peter Toft commented on JENKINS-29604 Re: git-client CLI implementation does not propogate username Jacob Keller when you write "your Windows home directory" - where is this? My Jenkins root is "C:\Program Files (x86)\Jenkins" Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-metadata-plugin] (JENKINS-29939) Repository password should not be stored unencrypted
Title: Message Title Marc Rohlfs closed an issue as Fixed Fixed with release 1.3.0 Jenkins / JENKINS-29939 Repository password should not be stored unencrypted Change By: Marc Rohlfs Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-metadata-plugin] (JENKINS-29940) Information about currently used artifact
Title: Message Title Marc Rohlfs closed an issue as Fixed Fixed with release 1.3.0 Jenkins / JENKINS-29940 Information about currently used artifact Change By: Marc Rohlfs Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-metadata-plugin] (JENKINS-29567) Invalid artifact URL when packaging is not specified
Title: Message Title Marc Rohlfs closed an issue as Fixed Fixed with release 1.3.0 Jenkins / JENKINS-29567 Invalid artifact URL when packaging is not specified Change By: Marc Rohlfs Status: Open Closed Assignee: Gesh Markov Marc Rohlfs Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-29604) git-client CLI implementation does not propogate username
Title: Message Title Peter Toft commented on JENKINS-29604 Re: git-client CLI implementation does not propogate username I did try to inject a .ssh/config with User jenkins but I might have placed my .ssh (for Windows Jenkins) in the wrong place No dice... Again for Linux Jenkins - everything works Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cas-plugin] (JENKINS-30524) Having the ability to configure two URLs (public and inter-application)
Title: Message Title Jean-Yves CRONIER commented on JENKINS-30524 Re: Having the ability to configure two URLs (public and inter-application) Thanks a lot ! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [websphere-deployer-plugin] (JENKINS-30593) Unable to connect to WebSphere 8.5 when credentials are supplied
Title: Message Title Nick Harvey commented on JENKINS-30593 Re: Unable to connect to WebSphere 8.5 when credentials are supplied FWIW, I also get the warning WARNING: ADMC0046W: The system failed to load properties from com.ibm.SOAP.configURL: file:null/properties/soap.client.props in jenkins.err.log every time I test the connection (failure or successful test), not sure if that's relevant though. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-30596) Pin changelist now working with CheckOnlyImpl
Title: Message Title Michael Rose assigned an issue to Paul Allen Jenkins / JENKINS-30596 Pin changelist now working with CheckOnlyImpl Change By: Michael Rose Assignee: Paul Allen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-30596) Pin changelist now working with CheckOnlyImpl
Title: Message Title Michael Rose created an issue Jenkins / JENKINS-30596 Pin changelist now working with CheckOnlyImpl Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 22/Sep/15 6:39 PM Environment: P4 plugin 1.3.1 Priority: Minor Reporter: Michael Rose When using the workflow plugin. This syncs the workspace to changelist foo: checkout $class: 'PerforceScm', populate [$class: 'ForceCleanImpl', pin: 'foo', ... This always syncs the workspace to the head revision: checkout $class: 'PerforceScm', populate [$class: 'CheckOnlyImpl', pin: 'foo', ...
[JIRA] [git-client-plugin] (JENKINS-29604) git-client CLI implementation does not propogate username
Title: Message Title Jacob Keller commented on JENKINS-29604 Re: git-client CLI implementation does not propogate username Yes, so the problem is that submodules do not have credential support yet. You can't change the username, and the default case in Windows has ssh pick up the administrator account name. In linux, I suspect you're already running as Jenkins so this works. This is an issue with submodules, and this bug is not referring to submodule behavior. I am currently working on a solution to this. We could probably fix this also by using our username in the .git/config file when we initialize submodules, but I am not sure how to automatically change that. I believe this is the intended reason that .gitmodules is separate from .git/config's notion of submodules. In any repsect, that is kind of moot because once we have proper credential support that issue goes away. For now, just know that submodules do not work reliably, and your best bet is add a ssh configuration file in windows that tells ssh what user to use. This should be in your Windows home directory under .ssh/config Regards, Jake Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-29604) git-client CLI implementation does not propogate username
Title: Message Title Peter Toft commented on JENKINS-29604 Re: git-client CLI implementation does not propogate username The problem is that if we have multiple users, then I cannot use "git add submodule ssh://ANYUSERNAME@server/repo" since it will only work for ANYUSERNAME Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-29604) git-client CLI implementation does not propogate username
Title: Message Title Peter Toft commented on JENKINS-29604 Re: git-client CLI implementation does not propogate username True that - I check out the main repo as ssh://jenkins@server/repo However I can see (on Windows still) that I can check out ssh://server/repo - but the submodules, no go! I also use configure -> Git plugin -> Global Config user.name Value set to "jenkins", which might be explain that the main module can check out without the user set in the repo path. But no dice for the submodules Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-29604) git-client CLI implementation does not propogate username
Title: Message Title Jacob Keller commented on JENKINS-29604 Re: git-client CLI implementation does not propogate username In Linux, I suspect the same username is the one running the jenkins instance, where as in Windows, I supsect that jenkins is running as Administrator. Are you actually specifying credentials to use for the main repo? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-30594) ${sha1} env variable doesn't work correctly
Title: Message Title
Mark Waite resolved as Not A Defect
Jenkins / JENKINS-30594
${sha1} env variable doesn't work correctly
Change By:
Mark Waite
Status:
Reopened Resolved
Resolution:
Not A Defect
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-30594) ${sha1} env variable doesn't work correctly
Title: Message Title
Mark Waite reopened an issue
Jenkins / JENKINS-30594
${sha1} env variable doesn't work correctly
Change By:
Mark Waite
Resolution:
Fixed
Status:
Closed Reopened
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-30594) ${sha1} env variable doesn't work correctly
Title: Message Title
Rusty Bailey closed an issue as Fixed
Nevermind... I changed it back to $ {sha1}
and it seems to be working again. Don't know why that was happening...
Jenkins / JENKINS-30594
${sha1} env variable doesn't work correctly
Change By:
Rusty Bailey
Status:
Open Closed
Resolution:
Fixed
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-api-plugin] (JENKINS-30595) Obtain SCMHead from Item
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-30595 Obtain SCMHead from Item Change By: Jesse Glick Labels: api multibranch Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-api-plugin] (JENKINS-30595) Obtain SCMHead from Item
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-30595 Obtain SCMHead from Item Issue Type: Improvement Assignee: Unassigned Components: scm-api-plugin Created: 22/Sep/15 5:33 PM Labels: api Priority: Major Reporter: Jesse Glick In some cases an SCMSource implementation will receive a Job (branch project) from somewhere, such as a listener, and need to know which SCMHead it corresponds to. This information is not currently retrievable directly; you have to assume that every BranchProjectFactory creates children whose Job.name matches SCMHead.name, as both WorkflowMultiBranchProjectFactory and LiterateMultibranchProject.ProjectFactoryImpl in fact do, and as MultiBranchProject itself seems to require (cf. Javadoc for getOrCreateBranchItemsFor). Would be nicer for scm-api to include some API letting you map Item to SCMHead. The implementation in branch-api would just call BranchProjectFactory.getBranch. Thus you could reliably get this reverse mapping without a branch-api dependency.
[JIRA] [maven-metadata-plugin] (JENKINS-29567) Invalid artifact URL when packaging is not specified
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29567 Re: Invalid artifact URL when packaging is not specified Code changed in jenkins User: Marc Rohlfs Path: src/main/lombok/eu/markov/jenkins/plugin/mvnmeta/MavenMetadataParameterDefinition.java http://jenkins-ci.org/commit/maven-metadata-plugin/e40394130fa3de1daff0858988951cac52578af9 Log: Merge pull request #8 from silpion/bugfix/JENKINS-29567_default-packaging Bugfix JENKINS-29567: Invalid artifact URL when packaging is not specified Compare: https://github.com/jenkinsci/maven-metadata-plugin/compare/783b38de8ff0...e40394130fa3 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [repository-connector-plugin] (JENKINS-30554) Complete ability to manually deploy artifacts TO a repository
Title: Message Title Brantone assigned an issue to Brantone Jenkins / JENKINS-30554 Complete ability to manually deploy artifacts TO a repository Change By: Brantone Assignee: Brantone Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-29604) git-client CLI implementation does not propogate username
Title: Message Title Peter Toft commented on JENKINS-29604 Re: git-client CLI implementation does not propogate username I am using submodules What is also baffling to understand is that I have exactly the same Linux setup - which works like a charm. But Windows breaks as discusssed above. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-30504) Occasional StackOverflow using `downstreamParameterized` publisher
Title: Message Title Ray H commented on JENKINS-30504 Re: Occasional StackOverflow using `downstreamParameterized` publisher Cheers. I should have specifically mentioned use of `gradle` to do this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30480) documentation of any change in build configuration
Title: Message Title Christoph Obexer commented on JENKINS-30480 Re: documentation of any change in build configuration I just noticed that there is a plug-in that does exactly that: https://wiki.jenkins-ci.org/display/JENKINS/JobConfigHistory+Plugin plus it allows to view the difference and revert to a specific version. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-29604) git-client CLI implementation does not propogate username
Title: Message Title Peter Toft commented on JENKINS-29604 Re: git-client CLI implementation does not propogate username I made a clean sheet installation earlier today. No success Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-30504) Occasional StackOverflow using `downstreamParameterized` publisher
Title: Message Title Daniel Spilker resolved as Fixed Will be released in 1.39. Jenkins / JENKINS-30504 Occasional StackOverflow using `downstreamParameterized` publisher Change By: Daniel Spilker Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-30504) Occasional StackOverflow using `downstreamParameterized` publisher
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30504 Re: Occasional StackOverflow using `downstreamParameterized` publisher Code changed in jenkins User: Daniel Spilker Path: docs/Home.md http://jenkins-ci.org/commit/job-dsl-plugin/b0d37e65593bb0cd267c811f63c7c922427639b1 Log: Merge branch ' JENKINS-30504 ' Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/feb3bb1ff48b...b0d37e65593b Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Role:-Big Data Engineer – Java/Hadoop||MD
*Hi Professional* *Consultant required for the below mentioned requirement. Kindly send me the updated resume with the contact details **@ cha...@intellilinktech.com * *Role:-Big Data Engineer – Java/Hadoop* Location: Chevy Chase, MD *USC or GC only.No h1’s. * *Application Developer (Big Data Tools)* · Minimum of 3 years of Java development experience · Deep knowledge of Web Services, SOA, HTTPS, WSDL, SOAP · Minimum 2 years of experience in Hadoop AND MapReduce AND Oozie AND Hive AND Pig · Minimum 2 years of experience in HBase OR Cassandra OR MongoDB OR any other NoSQL DB · Minimum 5 years of programming experience in either core Java OR C OR C++ OR Scala · Minimum 2 years of scripting experience in either Python OR Perl OR Shell scripting · Experience in REST API AND WebServices AND MQ Experience Thanks & Regards ? CHAKRI Sr.Recruiter Email: cha...@intellilinktech.com IntelliLink Technologies Inc. G/Y ID: chrakri.sreeinfo Ph: *732-400-1778 Ext:102* Fax: 732-200-0646 www.intellilinktech.com -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-29604) git-client CLI implementation does not propogate username
Title: Message Title Jacob Keller commented on JENKINS-29604 Re: git-client CLI implementation does not propogate username The current implementation does not support submodule credentials, this is a known regression/issue and I am currently working on how to fix this. If you aren't using submodules (seem to be as per the above), please make sure you're using a credentials setup, and not just assuming the username will propogate. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-29604) git-client CLI implementation does not propogate username
Title: Message Title Peter Toft commented on JENKINS-29604 Re: git-client CLI implementation does not propogate username Unless I am missing something - then I don't see this as fixed yet. With Jenkins for Windows 1.630 and git client plugin 1.19.0 it still breaks for me. when Git submodules use the ssh://server/module.git notation (no username). The submodules are being checked out with the Windows administrator ID and not the same ID as the main module. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-30348) Additional classpath locks up JAR files
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30348 Re: Additional classpath locks up JAR files Code changed in jenkins User: Ray Huang Path: job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/common/DownstreamTriggerParameterContext.groovy http://jenkins-ci.org/commit/job-dsl-plugin/d37b1a84bfd182c904ee85a3aa004cee92d86f03 Log: Explicitly set `delegate` on `predefinedProps` See [[https://issues.jenkins-ci.org/browse/JENKINS-30348 | Jenkins-30348]]. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-30594) ${sha1} env variable doesn't work correctly
Title: Message Title
Rusty Bailey updated an issue
Jenkins / JENKINS-30594
${sha1} env variable doesn't work correctly
Change By:
Rusty Bailey
I'm having trouble locating the actual source of the problem, but I will tell you what I do know. In Jenkins, we recently had several Git-related plugins updated:- [Git plugin](https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin): 2.2.7 -> 2.4.0- [GitHub plugin](https://wiki.jenkins-ci.org/display/JENKINS/Github+Plugin): 1.9.1 -> 1.13.3- [GitHub Pull Request Builder](https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin): 1.16-5 -> 1.27After that happened, any jobs that were referencing the ` {{ ${sha1} ` }} variable for the "Branch Specifier" said this in the console output and errored out:{ { code} } 09:29:54 using GIT_SSH to set credentials 09:29:54 > C:\Program Files (x86)\Git\bin\git.exe -c core.askpass=true fetch --tags --progress g...@github.com:repoowner/somereponame.git +refs/pull/*:refs/remotes/origin/pr/*09:30:24 > C:\Program Files (x86)\Git\bin\git.exe rev-parse "{origin/pr/63/merge}^{commit}" # timeout=1009:30:24 > C:\Program Files (x86)\Git\bin\git.exe rev-parse "refs/remotes/origin/{origin/pr/63/merge}^{commit}" # timeout=1009:30:24 > C:\Program Files (x86)\Git\bin\git.exe rev-parse "{origin/pr/63/merge}^{commit}" # timeout=1009:30:24 ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.{ { code} } Then I changed it to ` {{ $sha1 ` }} , and it seems to work correctly: ``` {code} 10:25:05 using GIT_SSH to set credentials 10:25:05 > C:\Program Files (x86)\Git\bin\git.exe -c core.askpass=true fetch --tags --progress g...@github.com:repoowner/somereponame.git +refs/pull/*:refs/remotes/origin/pr/*10:25:36 > C:\Program Files (x86)\Git\bin\git.exe rev-parse "refs/remotes/origin/pr/63/merge^{commit}" # timeout=1010:25:36 > C:\Program Files (x86)\Git\bin\git.exe rev-parse "refs/remotes/origin/origin/pr/63/merge^{commit}" # timeout=1010:25:36 Checking out Revision bc1e977a7ef8ad5f04cc9d5ff569e5b9aeb137bc (refs/remotes/origin/pr/63/merge) ``` {code} Did anything change with the env variables? Opened issue in Github PR Builder here: https://github.com/janinko/ghprb/issues/330#issuecomment-142326222
Add Comment
[JIRA] [git-plugin] (JENKINS-30594) ${sha1} env variable doesn't work correctly
Title: Message Title
Rusty Bailey updated an issue
Jenkins / JENKINS-30594
${sha1} env variable doesn't work correctly
Change By:
Rusty Bailey
I'm having trouble locating the actual source of the problem, but I will tell you what I do know. In Jenkins, we recently had several Git-related plugins updated:- [Git plugin](https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin): 2.2.7 -> 2.4.0- [GitHub plugin](https://wiki.jenkins-ci.org/display/JENKINS/Github+Plugin): 1.9.1 -> 1.13.3- [GitHub Pull Request Builder](https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin): 1.16-5 -> 1.27After that happened, any jobs that were referencing the {{${sha1}}} variable for the "Branch Specifier" said this in the console output and errored out:{code}09:29:54 using GIT_SSH to set credentials 09:29:54 > C:\Program Files (x86)\Git\bin\git.exe -c core.askpass=true fetch --tags --progress g...@github.com:repoowner/somereponame.git +refs/pull/*:refs/remotes/origin/pr/*09:30:24 > C:\Program Files (x86)\Git\bin\git.exe rev-parse "{origin/pr/63/merge}^{commit}" # timeout=1009:30:24 > C:\Program Files (x86)\Git\bin\git.exe rev-parse "refs/remotes/origin/{origin/pr/63/merge}^{commit}" # timeout=1009:30:24 > C:\Program Files (x86)\Git\bin\git.exe rev-parse "{origin/pr/63/merge}^{commit}" # timeout=1009:30:24 ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.{code}Then I changed it to {{$sha1}}, and it seems to work correctly:{code}10:25:05 using GIT_SSH to set credentials 10:25:05 > C:\Program Files (x86)\Git\bin\git.exe -c core.askpass=true fetch --tags --progress g...@github.com:repoowner/somereponame.git +refs/pull/*:refs/remotes/origin/pr/*10:25:36 > C:\Program Files (x86)\Git\bin\git.exe rev-parse "refs/remotes/origin/pr/63/merge^{commit}" # timeout=1010:25:36 > C:\Program Files (x86)\Git\bin\git.exe rev-parse "refs/remotes/origin/origin/pr/63/merge^{commit}" # timeout=1010:25:36 Checking out Revision bc1e977a7ef8ad5f04cc9d5ff569e5b9aeb137bc (refs/remotes/origin/pr/63/merge){code}Did anything change with the env variables? Opened issue in Github PR Builder here: https://github.com/janinko/ghprb/issues/330#issuecomment-142326222
Add Comment
[JIRA] [git-plugin] (JENKINS-30594) ${sha1} env variable doesn't work correctly
Title: Message Title
Rusty Bailey updated an issue
Jenkins / JENKINS-30594
${sha1} env variable doesn't work correctly
Change By:
Rusty Bailey
I'm having trouble locating the actual source of the problem, but I will tell you what I do know. In Jenkins, we recently had several Git-related plugins updated:- [Git plugin](https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin): 2.2.7 -> 2.4.0- [GitHub plugin](https://wiki.jenkins-ci.org/display/JENKINS/Github+Plugin): 1.9.1 -> 1.13.3- [GitHub Pull Request Builder](https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin): 1.16-5 -> 1.27After that happened, any jobs that were referencing the `${sha1}` variable for the "Branch Specifier" said this in the console output and errored out: ``` {{code}} 09:29:54 using GIT_SSH to set credentials 09:29:54 > C:\Program Files (x86)\Git\bin\git.exe -c core.askpass=true fetch --tags --progress g...@github.com:repoowner/somereponame.git +refs/pull/*:refs/remotes/origin/pr/*09:30:24 > C:\Program Files (x86)\Git\bin\git.exe rev-parse "{origin/pr/63/merge}^{commit}" # timeout=1009:30:24 > C:\Program Files (x86)\Git\bin\git.exe rev-parse "refs/remotes/origin/{origin/pr/63/merge}^{commit}" # timeout=1009:30:24 > C:\Program Files (x86)\Git\bin\git.exe rev-parse "{origin/pr/63/merge}^{commit}" # timeout=1009:30:24 ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. ``` {{code}} Then I changed it to `$sha1`, and it seems to work correctly:```10:25:05 using GIT_SSH to set credentials 10:25:05 > C:\Program Files (x86)\Git\bin\git.exe -c core.askpass=true fetch --tags --progress g...@github.com:repoowner/somereponame.git +refs/pull/*:refs/remotes/origin/pr/*10:25:36 > C:\Program Files (x86)\Git\bin\git.exe rev-parse "refs/remotes/origin/pr/63/merge^{commit}" # timeout=1010:25:36 > C:\Program Files (x86)\Git\bin\git.exe rev-parse "refs/remotes/origin/origin/pr/63/merge^{commit}" # timeout=1010:25:36 Checking out Revision bc1e977a7ef8ad5f04cc9d5ff569e5b9aeb137bc (refs/remotes/origin/pr/63/merge)```Did anything change with the env variables? Opened issue in Github PR Builder here: https://github.com/janinko/ghprb/issues/330#issuecomment-142326222
Add Comment
[JIRA] [git-plugin] (JENKINS-30594) ${sha1} env variable doesn't work correctly
Title: Message Title
Rusty Bailey created an issue
Jenkins / JENKINS-30594
${sha1} env variable doesn't work correctly
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
22/Sep/15 3:54 PM
Environment:
jenkins v1.629 Git plugin: 2.4.0 GitHub plugin: 1.13.3 GitHub Pull Request Builder: 1.27
Priority:
Minor
Reporter:
Rusty Bailey
I'm having trouble locating the actual source of the problem, but I will tell you what I do know. In Jenkins, we recently had several Git-related plugins updated:
[Git plugin](https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin): 2.2.7 -> 2.4.0
[GitHub plugin](https://wiki.jenkins-ci.org/display/JENKINS/Github+Plugin): 1.9.1 -> 1.13.3
[GitHub Pull Request Builder](https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin): 1.16-5 -> 1.27
[JIRA] [dashboard-view-plugin] (JENKINS-30229) Dashboard Padding CSS issues with 1.626
Title: Message Title Kyle Martinez reopened an issue I have reassigned this issue for the dashboard-view-plugin. Please let me know if there are any other details needed for this bug. Jenkins / JENKINS-30229 Dashboard Padding CSS issues with 1.626 Change By: Kyle Martinez Resolution: Incomplete Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-30483) Pull request is not triggered if Prevent Cross Site Request Forgery exploits is enabled
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-30483 Pull request is not triggered if Prevent Cross Site Request Forgery exploits is enabled Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-30483) Pull request is not triggered if Prevent Cross Site Request Forgery exploits is enabled
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30483 Re: Pull request is not triggered if Prevent Cross Site Request Forgery exploits is enabled Code changed in jenkins User: David Tanner Path: src/main/java/org/jenkinsci/plugins/ghprb/GhprbCrumbExclusion.java http://jenkins-ci.org/commit/ghprb-plugin/1889113dd45d644c7dc9129b6ed8e12d1523358b Log: Merge pull request #176 from fbelzunc/ JENKINS-30483 [FIXED JENKINS-30483] Pull request is not triggered if CSR is enabled Compare: https://github.com/jenkinsci/ghprb-plugin/compare/8c958718352f...1889113dd45d Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-29850) Add author github repo URL
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29850 Re: Add author github repo URL Code changed in jenkins User: Antoine Duprat Path: src/main/java/org/jenkinsci/plugins/ghprb/GhprbBuilds.java src/main/java/org/jenkinsci/plugins/ghprb/GhprbCause.java src/main/java/org/jenkinsci/plugins/ghprb/GhprbPullRequest.java src/main/java/org/jenkinsci/plugins/ghprb/GhprbTrigger.java src/test/java/org/jenkinsci/plugins/ghprb/GhprbPullRequestTest.java src/test/java/org/jenkinsci/plugins/ghprb/GhprbRepositoryTest.java http://jenkins-ci.org/commit/ghprb-plugin/9f6a58814424e54bbe05fe686a9f348c2628bfc0 Log: JENKINS-29850 Add author github repo URL Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-30115) ghprb - Allow downstream jobs to add GitHub status messages
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30115 Re: ghprb - Allow downstream jobs to add GitHub status messages Code changed in jenkins User: Kevin Suwala Path: src/main/java/org/jenkinsci/plugins/ghprb/GhprbBuilds.java src/main/java/org/jenkinsci/plugins/ghprb/GhprbCustomStatus.java src/main/java/org/jenkinsci/plugins/ghprb/GhprbCustomStatusListener.java src/main/java/org/jenkinsci/plugins/ghprb/GhprbCustomStatusRepoPasser.java src/main/java/org/jenkinsci/plugins/ghprb/GhprbTrigger.java src/main/resources/org/jenkinsci/plugins/ghprb/GhprbCustomStatus/config.jelly src/main/resources/org/jenkinsci/plugins/ghprb/GhprbCustomStatus/help-context.html src/main/resources/org/jenkinsci/plugins/ghprb/GhprbCustomStatus/help-message.html src/main/resources/org/jenkinsci/plugins/ghprb/GhprbCustomStatus/help.html http://jenkins-ci.org/commit/ghprb-plugin/9470f35cc66ab4beefa83e885c26b0923da4a88a Log: JENKINS-30115 Allow downstream jobs to attach GitHub status messages to pulled repo Added support for GitHub contexts and messages to be added from downstream jobs Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view-plugin] (JENKINS-30229) Dashboard Padding CSS issues with 1.626
Title: Message Title Kyle Martinez updated an issue Jenkins / JENKINS-30229 Dashboard Padding CSS issues with 1.626 Change By: Kyle Martinez Component/s: dashboard-view-plugin Component/s: core After upgrading jenkins to 1.626 there are dramatic padding issues with the tabBarContainer div. I believe this has to do with the dashboard-view-plugin. We are currently using version 2.9.6 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-13272) "Build History" view for a node: missing build time information
Title: Message Title Michael Rose commented on JENKINS-13272 Re: "Build History" view for a node: missing build time information This would be very useful in helping to track down nodes that are configured with less resources. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [websphere-deployer-plugin] (JENKINS-30593) Unable to connect to WebSphere 8.5 when credentials are supplied
Title: Message Title Nick Harvey created an issue Jenkins / JENKINS-30593 Unable to connect to WebSphere 8.5 when credentials are supplied Issue Type: Bug Assignee: Unassigned Components: websphere-deployer-plugin Created: 22/Sep/15 3:02 PM Environment: Jenkins ver. 1.628, running directly as a Windows Service hosted on Windows Server 2008 WebSphere ver. 8.5 WebSphere Deployer Plugin ver. 1.3.4 Priority: Minor Reporter: Nick Harvey When configuring my Jenkins build to deploy to WebSphere, the connection test will succeed if I do not provide credentials (user / pw fields are blank). If I enter credentials, it will continue to succeed, but deployments fail with the error Error deploying to IBM WebSphere Application Server: org.jenkinsci.plugins.websphere.services.deployment.DeploymentServiceException: Could not determine if artifact 'patient-portal-schedule-ear' is installed: ADMA0089E: The AppManagement MBean is not found. If I then restart Jenkins, any connection test done with credentials provided fails with the error
[JIRA] [job-dsl-plugin] (JENKINS-30504) Occasional StackOverflow using `downstreamParameterized` publisher
Title: Message Title
Daniel Spilker commented on JENKINS-30504
Re: Occasional StackOverflow using `downstreamParameterized` publisher
OK, now I'm able to reproduce this.
build.gradle
apply plugin: 'groovy'
defaultTasks 'runJobDsl'
repositories {
maven {
url 'http://repo.jenkins-ci.org/public/'
}
}
dependencies {
compile 'org.jenkins-ci.plugins:job-dsl-core:1.38'
}
task wrapper(type: Wrapper) {
gradleVersion = '2.3'
}
task runJobDsl(type: JavaExec) {
main = 'javaposse.jobdsl.Run'
classpath = sourceSets.main.runtimeClasspath
workingDir = 'jobs'
args 'MyJobs.groovy'
}
jobs/MyJobs.groovy
job('example') {
publishers {
downstreamParameterized {
trigger('MyJob') {
condition('SUCCESS')
parameters {
concurrentBuild()
predefinedProp('Param1', 'foo')
predefinedProp('Param2', 'bar')
}
}
}
}
}
But I still can't reproduce this in Jenkins or using the standalone jar:
wget http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/job-dsl-core/1.38/job-dsl-core-1.38-standalone.jar
java -jar job-dsl-core-1.38-standalone.jar jobs/MyJobs.groovy
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-22008) buildTimeTrend only shows the last 20 builds
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-22008 Re: buildTimeTrend only shows the last 20 builds Jesse Glick Thanks so much for your clue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-29703) Jenkins unable to sync workspace
Title: Message Title Michael Rose commented on JENKINS-29703 Re: Jenkins unable to sync workspace It hasn't happened in a while, but it just happened again this morning. I still do not know what causes it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-30515) scm (git) command does not fail correctly when it cannot look up credentials
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-30515 scm (git) command does not fail correctly when it cannot look up credentials Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-choices-plugin] (JENKINS-30592) An AC Reactive Reference is always displayed unless it references a parameter
Title: Message Title Ioannis Moutsatsos created an issue Jenkins / JENKINS-30592 An AC Reactive Reference is always displayed unless it references a parameter Issue Type: Bug Assignee: Bruno P. Kinoshita Components: active-choices-plugin Created: 22/Sep/15 2:45 PM Environment: Active Choices Plugin v 1.2 Priority: Minor Reporter: Ioannis Moutsatsos When an AC Reactive Reference parameter does not reference any parameters, even though it is set to 'Hidden HTML' it is still displayed in the UI. Current Workaround: Include a build parameter (or even a no existent dummy parameter) as a Referenced parameter to hide a 'Hidden HTML' type reactive reference. However, th is workaround hack should not be necessary. The parameter option type should be honored independent of the referenced parameters.
[JIRA] [websphere-deployer-plugin] (JENKINS-30250) StackOverflowError in Websphere Deployer
Title: Message Title Rusty Bentz commented on JENKINS-30250 Re: StackOverflowError in Websphere Deployer Does the same user have to be used for both Jenkins and Websphere, or just not root? I will check the same on my end. Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-30515) scm (git) command does not fail correctly when it cannot look up credentials
Title: Message Title Jesse Glick assigned an issue to Mark Waite Do not see any reason to believe this is a Workflow-specific issue. Jenkins / JENKINS-30515 scm (git) command does not fail correctly when it cannot look up credentials Change By: Jesse Glick Component/s: workflow-plugin Assignee: Mark Waite Labels: diagnostics ux workflow Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.goo
[JIRA] [copy-to-slave-plugin] (JENKINS-29257) FATAL: java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: hudson/remoting/JarCacheSupport$1
Title: Message Title Joe Keslin commented on JENKINS-29257 Re: FATAL: java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: hudson/remoting/JarCacheSupport$1 Still having this issue and restarting the slave doesn't seem to be fixing it for me now. I'm thinking it has to do with a possible file permission issue with the zip file created when transferring the directory. My scripts directory (/var/lib/jenkins/userContent/scripts) is checked into svn and I have the "Include ant defaults" option under advanced unchecked. The value I have in the "Files to copy" parameter is: scripts/ Paths are relative to is set to "$JENKINS_HOME/userContent" I'm running jenkins version 1.563, SSH Slaves 1.10, Copy To Slave Plugin 1.4.4 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-26102) Workflow step to wait for approval
Title: Message Title Arkadiusz Skalski commented on JENKINS-26102 Re: Workflow step to wait for approval my apologize. I've searched the page and found the wrong entry. Was waiting so long for that feature. Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
