[JIRA] (JENKINS-30709) SCM env vars for multiple scm's plugin not useful with multiple git repos
Title: Message Title Eric Veiras commented on JENKINS-30709 Re: SCM env vars for multiple scm's plugin not useful with multiple git repos Hello, is there any documentation about this functionnality? How can I retrieve this env vars from each SCM used? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38753) Flow diagram allows text between nodes to bleed over each other
Title: Message Title Michael Neale edited a comment on JENKINS-38753 Re: Flow diagram allows text between nodes to bleed over each other This needs a design for how we actually truncate (and allow users to see the full one). Or don't truncate, whatever. To be tackled in next sprint. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-27299) Refactor Disable Build feature out of AbstractProject for Workflow Compatibility
Title: Message Title Michael Bickett commented on JENKINS-27299 Re: Refactor Disable Build feature out of AbstractProject for Workflow Compatibility +1 for this feature request please! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38756) "Karaoke" mode should have a "resume" button/link
Title: Message Title Michael Neale commented on JENKINS-38756 Re: "Karaoke" mode should have a "resume" button/link This will go away with the accidental selection problem but I think there is still a chance that it is not obvious enough how to make it go back to follow along. Scrolling down should make it follow along, as should clicking the next expected stage, so likely a bug as well. I might put this as a design ticket to think about how to make it clearer karaoke has paused (and thus, how to resume). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38756) "Karaoke" mode should have a "resume" button/link
Title: Message Title
Michael Neale updated an issue
Jenkins / JENKINS-38756
"Karaoke" mode should have a "resume" button/link
Change By:
Michael Neale
Design problem: it is easy to get out of "karaoke mode" (ie follow along) but not always obvious how to get back into it. The idea of stopping following along is to stop eyeballs being dragged away from what they were reading. The suggestion here is an explicit "resume following along" type action, worth thinking about. --- spake the tyler Each line in the scrolling console output is actually clickable, and if you're daft enough to click the link the URL gets modified with something like {{#step-9-log-1109}}Even if I page-down to the end, the page ceases to follow the log until I hit my browsers back button or remove the {{#step-9-log-1109}}.I think it would be nice to give a visual indication to the user that scrolling has been paused and a link/button to click to resume scrolling with the console output.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38771) Redirect to referrer from login page
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-38771 Redirect to referrer from login page Issue Type: Bug Assignee: Tomas Westling Components: kerberos-sso-plugin Created: 2016/Oct/06 7:34 AM Priority: Minor Reporter: Oliver Gondža Kerberos in anonymous mode redirects to / after login. Would be better to use referrer or the explicit get parameter in case Jenkins redirected user to login page (not sure when this happens exactly). Add Comment This message was sent by Atlass
[JIRA] (JENKINS-38756) "Karaoke" mode should have a "resume" button/link
Title: Message Title
Michael Neale updated an issue
Jenkins / JENKINS-38756
"Karaoke" mode should have a "resume" button/link
Change By:
Michael Neale
Design problem: it is easy to get out of "karaoke mode" (ie follow along) but not always obvious how to get back into it. The idea of stopping following along is to stop eyeballs being dragged away from what they were reading. The suggestion here is an explicit "resume following along" type action, worth thinking about. There may be bugs to do with not being able to resume via the current gestures (scrollling and clicking) they will be a separate issue. --- spake the tyler Each line in the scrolling console output is actually clickable, and if you're daft enough to click the link the URL gets modified with something like {{#step-9-log-1109}}Even if I page-down to the end, the page ceases to follow the log until I hit my browsers back button or remove the {{#step-9-log-1109}}.I think it would be nice to give a visual indication to the user that scrolling has been paused and a link/button to click to resume scrolling with the console output.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38772) Add support for multiple versions with advanced local usage
Title: Message Title Pavel Savshenko created an issue Jenkins / JENKINS-38772 Add support for multiple versions with advanced local usage Issue Type: New Feature Assignee: Unassigned Components: pyenv-plugin Created: 2016/Oct/06 7:35 AM Labels: plugin jenkins Priority: Minor Reporter: Pavel Savshenko PyEnv is smart enough to interpret PYENV_VERSION=1.2:3.4 as local versions 1.2 and 3.4. It would be nice if we could specify these; as well as specify multiple versions in .python-versions. Currently I see only two small issues when trying to do the above: The plugin attempts to install a version of python exactly matching PYENV_VERSION. To support multiple versions we'd have to split the value by ":". The plugin reads .python-versions as is, so it ends up specifying multiple versions as line break separated "1.2\n3.4" which again fails for installation, as well as usage. Here we'd have to split by "line-break" and then join again by ":".
[JIRA] (JENKINS-38042) Update the UI to use the "display name" property rather than the "name" for Pipelines and Folders
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38042 Update the UI to use the "display name" property rather than the "name" for Pipelines and Folders Change By: Michael Neale Sprint: pacific indian Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38773) Using RHEL server every time build fail through CVS
Title: Message Title Benedikt Weber created an issue Jenkins / JENKINS-38773 Using RHEL server every time build fail through CVS Issue Type: Bug Assignee: Unassigned Components: cvs-plugin Created: 2016/Oct/06 7:36 AM Environment: Jenkins 2.7.4 LTS, RHEL 6.8, OpenJDK 1.7.0_19 64-Bit, CVS-Plugin 2.12 Priority: Major Reporter: Benedikt Weber FATAL: null java.lang.NullPointerException at org.apache.commons.digester.Digester.getXMLReader(Digester.java:1068) at org.apache.commons.digester.Digester.parse(Digester.java:1871) at hudson.scm.CVSChangeLogSet.parse(CVSChangeLogSet.java:118) at hudson.scm.CVSChangeLogParser.parse(CVSChangeLogParser.java:43) at hudson.scm.CVSChangeLogParser.parse(CVSChangeLogParser.java:38) at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:911) at hudson.model.AbstractBuild.access$600(AbstractBuild.java:105) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:616) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) ERROR: Build step failed with exception java.lang.NullPointerException at org.apache.commons.digester.Digester.getXMLReader(Digester.java:1068) at org.apache.commons.digester.Digester.parse(Digester.java:1871) at hudson.scm.CVSChangeLogSet.parse(CVSChangeLogSet.java:118) at hudson.scm.CVSChangeLogParser.parse(CVSChangeLogParser.java:43) at hudson.scm.CVSChangeLogParser.parse(CVSChangeLogParser.java:38) at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:911) at
[JIRA] (JENKINS-38774) Fix the logout feature
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-38774 Fix the logout feature Issue Type: Bug Assignee: Tomas Westling Components: kerberos-sso-plugin Created: 2016/Oct/06 7:39 AM Priority: Minor Reporter: Oliver Gondža The reason this does not work (at least for basic auth) is, the browser keeps sending the username/password (that is how basic auth work) with every request so after dropping the session it get recreated immediately. Add Comment This message was sent by Atla
[JIRA] (JENKINS-38773) Using RHEL server every time build fail through CVS
Title: Message Title Benedikt Weber commented on JENKINS-38773 Re: Using RHEL server every time build fail through CVS The majority of builds with checkout from CVS fails with the NPE above. After many retries it will work. The number of retries needed varies every time. Possibly similar to https://issues.jenkins-ci.org/browse/JENKINS-32732 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38775) Selecting a line in karaoke mode stops follow along in a way that can't be resumed
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-38775 Selecting a line in karaoke mode stops follow along in a way that can't be resumed Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Oct/06 7:47 AM Priority: Minor Reporter: Michael Neale If you select a line in karaoke mode, it pauses the follow along, but in a way that can't be resumed To reproduce: Run a pipeline job, follow along Select a line (say, click on line number) - not the URI changes slightly There is no way to follow along by scrolling Add Comment
[JIRA] (JENKINS-38775) Selecting a line in karaoke mode stops follow along in a way that can't be resumed
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38775 Selecting a line in karaoke mode stops follow along in a way that can't be resumed Change By: Michael Neale If you select a line in karaoke mode, it pauses the follow along, but in a way that can't be resumedTo reproduce: Run a pipeline job, follow alongSelect a line (say, click on line number) - not the URI changes slightlyThere is no way to follow along by scrolling at allThe pipeline does not update with status of subsequent stages Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38756) "Karaoke" mode should have a "resume" button/link
Title: Message Title
Michael Neale updated an issue
Jenkins / JENKINS-38756
"Karaoke" mode should have a "resume" button/link
Change By:
Michael Neale
Design problem: it is easy to get out of "karaoke mode" (ie follow along) but not always obvious how to get back into it. The idea of stopping following along is to stop eyeballs being dragged away from what they were reading. The suggestion here is an explicit "resume following along" type action, worth thinking about. There may be bugs to do with not being able to resume via the current gestures (scrollling and clicking) they will be a separate issue. MN Note: I have no idea what makes karaoke start or stop - I think this needs a good redesign think, it causes too much surprise.--- spake the tyler Each line in the scrolling console output is actually clickable, and if you're daft enough to click the link the URL gets modified with something like {{#step-9-log-1109}}Even if I page-down to the end, the page ceases to follow the log until I hit my browsers back button or remove the {{#step-9-log-1109}}.I think it would be nice to give a visual indication to the user that scrolling has been paused and a link/button to click to resume scrolling with the console output.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38756) "Karaoke" mode should have a "resume" button/link
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38756 "Karaoke" mode should have a "resume" button/link Change By: Michael Neale Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38700) EnvInjectPluginTest is failing
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38700 Re: EnvInjectPluginTest is failing Code changed in jenkins User: Manuel Franco Path: src/main/java/org/jenkinsci/test/acceptance/plugins/envinject/EnvInjectConfig.java http://jenkins-ci.org/commit/acceptance-test-harness/6bf03c2ab36db681f45c3a20e53881fa91d8ce86 Log: JENKINS-38700 fix properties path in 'EnvInjectConfig' Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38700) EnvInjectPluginTest is failing
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38700 Re: EnvInjectPluginTest is failing Code changed in jenkins User: Oliver Gondža Path: src/main/java/org/jenkinsci/test/acceptance/plugins/envinject/EnvInjectConfig.java http://jenkins-ci.org/commit/acceptance-test-harness/f4110be229f0967fba71fedf0125d1231710db64 Log: Merge pull request #197 from mafraba/JENKINS-38700 JENKINS-38700 fix properties path in 'EnvInjectConfig' Compare: https://github.com/jenkinsci/acceptance-test-harness/compare/3dfdfd3290a1...f4110be229f0 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Anton Lundin commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Edit the select drop down and just add the inside the containing the right credentials. You can copy the options tag from a working svn configuration page. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38750) Pipeline failure doesn't expand/show what the failure actually is
Title: Message Title Michael Neale assigned an issue to Vivek Pandey Jenkins / JENKINS-38750 Pipeline failure doesn't expand/show what the failure actually is Change By: Michael Neale Assignee: Vivek Pandey Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-31389) SVN changelog per build not taking into account locations of script vs. checkout step
Title: Message Title Martin Vehovsky resolved as Cannot Reproduce Cannot reproduce anymore.. Jenkins / JENKINS-31389 SVN changelog per build not taking into account locations of script vs. checkout step Change By: Martin Vehovsky Status: Reopened Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more option
[JIRA] (JENKINS-38750) Pipeline failure doesn't expand/show what the failure actually is
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38750 Pipeline failure doesn't expand/show what the failure actually is Change By: Michael Neale Attachment: Screen Shot 2016-10-06 at 7.04.24 pm.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38750) Pipeline failure doesn't expand/show what the failure actually is
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38750 Pipeline failure doesn't expand/show what the failure actually is Change By: Michael Neale Attachment: Screen Shot 2016-10-06 at 7.04.34 pm.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38750) Pipeline failure doesn't expand/show what the failure actually is
Title: Message Title Michael Neale commented on JENKINS-38750 Re: Pipeline failure doesn't expand/show what the failure actually is Vivek Pandey the bismuth stuff may help here, not sure. Looking at classic stage view - it isn't much better. It doesn't show the specific error for the log for that step (which seems wrong). However, it does show it in a mouseover that you can sometimes see. Which is unreadably formatter, but implies the data is there somehow... ON mouse over you see the missing tool error: To confirm when you look at logs in classic you don't see it either: Vivek Pandey assigning you to take a look if there is something we can do. I think I will open a ticket against the tool step. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38750) Pipeline failure doesn't expand/show what the failure actually is
Title: Message Title Michael Neale closed an issue as Duplicate Actually no closing this - moving instead to a pipeline bug. Jenkins / JENKINS-38750 Pipeline failure doesn't expand/show what the failure actually is Change By: Michael Neale Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options,
[JIRA] (JENKINS-38776) tool step does not report failures in its log
Title: Message Title
Michael Neale created an issue
Jenkins / JENKINS-38776
tool step does not report failures in its log
Issue Type:
Bug
Assignee:
rsandell
Attachments:
Screen Shot 2016-10-06 at 7.04.34 pm.png
Components:
pipeline, pipeline-utility-steps-plugin
Created:
2016/Oct/06 8:14 AM
Priority:
Minor
Reporter:
Michael Neale
If you attempt to install a tool that doesn't exist, the step will fail, but there is nothing in the steps log. You would see something like the attached in the stage view. The log should explain what is missing in the tool:(problem isn't with stage view, but is with the steps output) To reproduce:
node {
stage 'Checkout'
checkout scm
stage 'Build'
def mvnHome = tool 'NONSENSE'
}
and look at the stage graph to see that it has no output
[JIRA] (JENKINS-38759) Console output in Blue Ocean omits useful node information
Title: Message Title Michael Neale commented on JENKINS-38759 Re: Console output in Blue Ocean omits useful node information tyler croy it would be good if you could also look at the classic stage view - to see if it includes it there (I think it includes some detail) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38759) Console output in Blue Ocean omits useful node information
Title: Message Title Michael Neale edited a comment on JENKINS-38759 Re: Console output in Blue Ocean omits useful node information [~201604291_tyler] it would be good if you could also look at the classic stage view - to see if it includes it there (I think it includes some detail) Based on primitive experiments, it looks like it may include more. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38759) Console output in Blue Ocean omits useful node information
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38759 Console output in Blue Ocean omits useful node information Change By: Michael Neale Attachment: Screen Shot 2016-10-06 at 7.04.24 pm.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-36041) default ldap timeouts are innapropriate.
Title: Message Title James Nord commented on JENKINS-36041 Re: default ldap timeouts are innapropriate. It's all in the PR. Direct link https://github.com/jenkinsci/active-directory-plugin/pull/37/commits/a037bde7e17fdfc9286644cd7a905f7b8e398ed2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38768) [android] Emulator did not appear to start; giving up on Windows
Title: Message Title Christopher Orr commented on JENKINS-38768 Re: [android] Emulator did not appear to start; giving up on Windows Under the Advanced options, where you added -noaudio, could you try instead adding -verbose there, and attach the full log, please? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38777) Signing for "Unity-iPhone" requires a development team
Title: Message Title Kristofer Boman created an issue Jenkins / JENKINS-38777 Signing for "Unity-iPhone" requires a development team Issue Type: Bug Assignee: lacostej Components: unity3d-plugin, xcode-plugin Created: 2016/Oct/06 8:22 AM Environment: Plugins: Jenkins 2.19.1 Unity3D-plugin 1.3 xcode-plugin 1.4.11 Operating System: macOS Sierra Ide Xcode 8 Web Browser Safari Labels: xcode unity signing provisioning ios Priority: Blocker Reporter: Kristofer Boman I recently setup a Macbook Pro with jenkins to automatically build Unity iOS projects. No mather the settings i use for signing the .ipa file i get === BUILD TARGET Unity-iPhone OF PROJECT Unity-iPhone WITH CONFIGURATION Release === Check dependencies Signing for "Unity-iPhone" requires a development team. Select a development team in the project editor. Code signing is required for product type 'Application' in SDK 'iOS 10.0' ** BUILD FAILED ** The following build commands failed: Check dependencies (1 failure) Build step 'Xcode' marked build as failure Finished: FAILURE How can i set the team automatically so the signing works? Full log from Xcode build step Exiting batchmode successfully now! [UnityTest] $ /bin/sh /var/folders/9d/lhvckkyx4hs8vhc_yqw8ynnrgn/T/hudson6913529922758759577.sh Working directory is /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins. [BadMen-Jenkins] $ /usr/bin/xcodebuild -version Xcode 8.0 Build version 8A218a Fetching marketing version number (CFBundleShortVersionString) from project. [BadMen-Jenkins] $ /usr/bin/agvtool mvers -terse1 Found marketi
[JIRA] (JENKINS-36041) default ldap timeouts are innapropriate.
Title: Message Title James Nord commented on JENKINS-36041 Re: default ldap timeouts are innapropriate. Not use for the moment DEFAULT_LDAP_CONNECTION_TIMEOUT since JDK-8139721, JDK-8139942 breaks the plugin usage Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38759) Console output in Blue Ocean omits useful node information
Title: Message Title Michael Neale assigned an issue to Vivek Pandey Jenkins / JENKINS-38759 Console output in Blue Ocean omits useful node information Change By: Michael Neale Assignee: Vivek Pandey Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38759) Console output in Blue Ocean omits useful node information
Title: Message Title
Michael Neale updated an issue
Jenkins / JENKINS-38759
Console output in Blue Ocean omits useful node information
Change By:
Michael Neale
MN Summary: more information is needed than is exposed currently as steps in blue ocean (and possibly classic, but that isn't clear just yet) - more investigation needed. An unpleasant fallback is to resort to viewing full log, but that isn't obvious or nice. It appears that the console output doesn't include the "node allocation" information which is useful when trying to debug systemic issues in Jenkins agents.Take [this Jenkinsfile|https://github.com/jenkins-infra/infra-statistics/blob/master/Jenkinsfile] which can execute on one of a number of agents. We had some issues where an agent was misbehaving, resulting in failures like:{code}WARNING: Failed to execute: select name,version,instanceid from plugin where month >= 1466636926735 and name NOT LIKE 'privateplugin%' and version NOT LIKE '%(private)'order by name,version desc,instanceid because: [SQLITE_IOERR] Some kind of disk I/O error occurred (disk I/O error){code}LOLWUT aside, the beginning of the "classic" Console Output view includes:{code}Started by user rtylerReplayed #8Connecting to https://api.github.com using jenkinsadmin/** (GitHub access token for jenkinsadmin)[Pipeline] nodeRunning on kelp in /home/jenkins/agent-workspace/workspace/Infra/infra-statistics/master[Pipeline] {[Pipeline] checkoutFetching changes from 2 remote Git repositoriesChecking out Revision 4c2c3e9a24627421e7cd17d725a7a42bfe5a06e7 (master)[Pipeline] tool[Pipeline] tool[Pipeline] stage (Sync raw data and census files){code}A screenshot from the Blue Ocean detail page for this run is attached. Suffice it to say, there is no information in the detail page about what nodes this Pipeline run executed on :(
Add Comment
[JIRA] (JENKINS-38700) EnvInjectPluginTest is failing
Title: Message Title Manuel Franco resolved as Fixed Jenkins / JENKINS-38700 EnvInjectPluginTest is failing Change By: Manuel Franco Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38759) Console output in Blue Ocean omits useful node information
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38759 Console output in Blue Ocean omits useful node information Change By: Michael Neale Sprint: atlantic Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38759) Console output in Blue Ocean omits useful node information
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38759 Console output in Blue Ocean omits useful node information Change By: Michael Neale Sprint: atlantic pacific Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38759) Console output in Blue Ocean omits useful node information
Title: Message Title Michael Neale commented on JENKINS-38759 Re: Console output in Blue Ocean omits useful node information Vivek Pandey I thought this may be of interest while you are digging into bismuth. It would be wonderful if we could surface this extra information as steps. If this isn't possible, perhaps we should close this and either rethink the design to show the full log in some cases, or ... don't know what else. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38759) Console output in Blue Ocean omits useful node information
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38759 Console output in Blue Ocean omits useful node information Change By: Michael Neale Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38751) Blue Ocean should provide an "escape" link to get back to a classic view of a Pipeline/job
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38751 Blue Ocean should provide an "escape" link to get back to a classic view of a Pipeline/job Change By: Michael Neale Sprint: indian Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38751) Blue Ocean should provide an "escape" link to get back to a classic view of a Pipeline/job
Title: Message Title Michael Neale commented on JENKINS-38751 Re: Blue Ocean should provide an "escape" link to get back to a classic view of a Pipeline/job Putting this in as a design task as this likely is cross cutting. There a lots of place we could have a subtle "escape" link, would be interested to know what it could look like (should there be one, could there be many, one for each function that blue ocean doesn't yet do) etc. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38778) Reserved node leaked from 'DisposableQueue'
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-38778 Reserved node leaked from 'DisposableQueue' Issue Type: Bug Assignee: Scott Hebert Components: foreman-node-sharing-plugin Created: 2016/Oct/06 8:41 AM Priority: Major Reporter: Pavel Janoušek I've detected a situation when reserved node wasn't put into disposable queue and was reserved forever. I've tried to find out the possible path/place where an exception occurred and ForemanSharedNode.terminate() wasn't invoked, but I failed. What I can see from the log is: [ForemanAPI] Reserving host X [ForemanAPI] Retrieving ip="AA.BB.CC.DD" for X [ForemanSharedNode] Instancing a new ForemanSharedNode: name='X', label='LABEL' [hudson.slaves.NodeProvisioner] (jenkins.util.Timer [#10]) Started provisioning LABEL from Foreman-test with 1 executors. Remaining excess workload: 0 X, AA.BB.CC.DD and LABEL are obfuscated only. The third reported line is produced by not released branch yet (see here). Nothing else was reported for node X. In that time 3 nodes were reserved while network to Foreman was dropped, the first detection was in: 2016-10-06 03:50:34,331 INFO [STDOUT] (jenkins.util.Timer [#10]) 03:50:34,330 ERROR [ForemanAPI] Unhandled exception getting JENKINS_LABEL for Y 2016-10-06 03:50:34,331 INFO [STDOUT] (jenkins.util.Timer [#10]) 03:50:34,331 ERROR [ForemanSharedNodeCloud] com.fasterxml.jackson.databind.JsonMappingException: No content to map due to end-of-input at [Source: ; line: 1, column: 1] 2016-10-06 03:50:34
[JIRA] (JENKINS-38768) [android] Emulator did not appear to start; giving up on Windows
Title: Message Title Louie Mandi commented on JENKINS-38768 Re: [android] Emulator did not appear to start; giving up on Windows This is the logs after I put -verbose. Looks the same. Started by user Louie Mandigal [EnvInject] - Loading node environment variables. Building in workspace C:\Program Files (x86)\Jenkins\workspace\Run Android Emulator $ C:\Users\louie.d.p.mandigal\AppData\Local\Android\sdk/tools/android.bat list target [android] Using Android SDK: C:\Users\louie.d.p.mandigal\AppData\Local\Android\sdk [android] Waiting 30 seconds before starting emulator... $ C:\Users\louie.d.p.mandigal\AppData\Local\Android\sdk/platform-tools/adb.exe start-server daemon not running. starting it now on port 5815 * daemon started successfully * $ C:\Users\louie.d.p.mandigal\AppData\Local\Android\sdk/platform-tools/adb.exe start-server [android] Starting Android emulator $ C:\Users\louie.d.p.mandigal\AppData\Local\Android\sdk/tools/emulator.exe -engine classic -ports 5794,5795 -report-console tcp:5851,max=60 -prop persist.sys.language=de -prop persist.sys.country=DE -avd hudson_de-DE_160_HVGA_android-18_armeabi-v7a -no-snapshot-load -no-snapshot-save -no-window -verbose [android] Emulator did not appear to start; giving up [android] Stopping Android emulator $ C:\Users\louie.d.p.mandigal\AppData\Local\Android\sdk/platform-tools/adb.exe kill-server ERROR: Step ‘Publish Cucumber test result report’ failed: No test reports that matches found. Configuration error? Finished: NOT_BUILT Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38758) Export and use badges/shields
Title: Message Title Thorsten Scherler updated an issue Jenkins / JENKINS-38758 Export and use badges/shields Change By: Thorsten Scherler Attachment: Screenshot from 2016-10-06 10-43-20.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38758) Export and use badges/shields
Title: Message Title Thorsten Scherler commented on JENKINS-38758 Re: Export and use badges/shields Yeah, lots of different stuff. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38267) job-fan-in-plugin: UI: configuration shows always first option "Trigger only if build is stable", despite what is really configured in config.xml of job
Title: Message Title Richard Kettelerij commented on JENKINS-38267 Re: job-fan-in-plugin: UI: configuration shows always first option "Trigger only if build is stable", despite what is really configured in config.xml of job We've also ran into this issue. I've submitted a pull request to fix it: https://github.com/jenkinsci/job-fan-in-plugin/pull/2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-36133) Animate in steps when stage node is clicked
Title: Message Title Michael Neale commented on JENKINS-36133 Re: Animate in steps when stage node is clicked Brody Maclean I am really not that fond of animating this. nothign I have seen (mocked up or otherwise) looks better than what we have already to my eyes, and just seems to slow things down. Would you mind having a think if this is warranted? (this is the second time we have tried to implement it, it caused various problems in the past). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-36133) Animate in steps when stage node is clicked
Title: Message Title Michael Neale updated JENKINS-36133 Jenkins / JENKINS-36133 Animate in steps when stage node is clicked Change By: Michael Neale Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-36133) Animate in steps when stage node is clicked
Title: Message Title Michael Neale updated JENKINS-36133 Jenkins / JENKINS-36133 Animate in steps when stage node is clicked Change By: Michael Neale Status: In Review Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38640) Unstash painfully slow for large artifacts (due to compression?)
Title: Message Title Oleg Nenashev commented on JENKINS-38640 Re: Unstash painfully slow for large artifacts (due to compression?) External Workspace Manager (https://github.com/jenkinsci/external-workspace-manager-plugin/blob/master/README.md) could be a workaround. With this plugin you can share the entire workspace on filer instead of stashing particular files and getting overhead on the Jenkins side. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-36041) default ldap timeouts are inappropriate
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-36041 default ldap timeouts are inappropriate Change By: Baptiste Mathus Summary: default ldap timeouts are innapropriate. inappropriate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38266) Lock released, but waiting acquirers won't continue to work
Title: Message Title
Nicolas PENCREACH commented on JENKINS-38266
Re: Lock released, but waiting acquirers won't continue to work
I just encountered the same issue. For testing purpose I reserved my resource from Jenkins UI (a maintenance scenario) and continue my build which was paused by an input. The lock worked as expected. But when I unreserved the resource from UI, the build still paused (no other build in progress). I tried to pause/resume the build without result and finished by aborting it. Here is my console log : {{[Pipeline] milestone Trying to pass milestone 40 [Pipeline] stage [Pipeline] { (Déploiement recette) [Pipeline] input Input requested Approved by Administrateur [Pipeline] lock Trying to acquire lock on [immodem-staging-server] [immodem-staging-server] is locked, waiting... Pausing Resuming Aborted by Administrateur [Pipeline] // lock [Pipeline] } [Pipeline] // stage [Pipeline] End of Pipeline Finished: ABORTED}} And the part of my pipeline script {{milestone 40 stage('Déploiement recette') { // Approbation de déploiement en recette avec demande d'un nom de tag à créer def tag = input message: 'Déployer la version en recette ?', ok: 'Déployer', parameters: [ [$class: 'TextParameterDefinition', defaultValue: 'vXXX', description: 'Tagger la version dans GIT', name: 'Tag'] ], submitter: 'admin' // Déploiement du nouveau package lock(resource:'immodem-staging-server', inversePrecedence: true) { milestone 50 node { } } }}}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this
[JIRA] (JENKINS-38266) Lock released, but waiting acquirers won't continue to work
Title: Message Title
Nicolas PENCREACH edited a comment on JENKINS-38266
Re: Lock released, but waiting acquirers won't continue to work
I just encountered the same issue.For testing purpose I reserved my resource from Jenkins UI (a maintenance scenario) and continue my build which was paused by an input. The lock worked as expected.But when I unreserved the resource from UI, the build still paused (no other build in progress).I tried to pause/resume the build without result and finished by aborting it.Here is my console log : {{ [Pipeline] milestoneTrying to pass milestone 40[Pipeline] stage[Pipeline] { (Déploiement recette)[Pipeline] inputInput requestedApproved by Administrateur[Pipeline] lockTrying to acquire lock on [immodem-staging-server][immodem-staging-server] is locked, waiting...PausingResumingAborted by Administrateur[Pipeline] // lock[Pipeline] }[Pipeline] // stage[Pipeline] End of PipelineFinished: ABORTED }} And the part of my pipeline script {{ milestone 40stage('Déploiement recette') { // Approbation de déploiement en recette avec demande d'un nom de tag à créer def tag = input message: 'Déployer la version en recette ?', ok: 'Déployer', parameters: [[$class: 'TextParameterDefinition', defaultValue: 'vXXX', description: 'Tagger la version dans GIT', name: 'Tag'] ], submitter: 'admin' // Déploiement du nouveau package lock(resource:'immodem-staging-server', inversePrecedence: true) {milestone 50node {} }} }}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from
[JIRA] (JENKINS-38768) [android] Emulator did not appear to start; giving up on Windows
Title: Message Title Christopher Orr commented on JENKINS-38768 Re: [android] Emulator did not appear to start; giving up on Windows Ok, so probably the emulator didn't get created properly, and the plugin is hiding some sort of error message. Can you run the command shown in the log (without the `-report-console` stuff) on your machine, and see what it says? emulator.exe -engine classic -prop persist.sys.language=de -prop persist.sys.country=DE -avd hudson_de-DE_160_HVGA_android-18_armeabi-v7a -no-snapshot-load -no-snapshot-save -no-window -verbose Do you see any errors in the job where the emulator was first created (with android.bat create avd ...)? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38266) Lock released, but waiting acquirers won't continue to work
Title: Message Title
Nicolas PENCREACH edited a comment on JENKINS-38266
Re: Lock released, but waiting acquirers won't continue to work
I just encountered the same issue.For testing purpose I reserved my resource from Jenkins UI (a maintenance scenario) and continue my build which was paused by an input. The lock worked as expected.But when I unreserved the resource from UI, the build still paused (no other build in progress).I tried to pause/resume the build without result and finished by aborting it.Here is my console log : {noformat} [Pipeline] milestoneTrying to pass milestone 40[Pipeline] stage[Pipeline] { (Déploiement recette)[Pipeline] inputInput requestedApproved by Administrateur[Pipeline] lockTrying to acquire lock on [immodem-staging-server][immodem-staging-server] is locked, waiting...PausingResumingAborted by Administrateur[Pipeline] // lock[Pipeline] }[Pipeline] // stage[Pipeline] End of PipelineFinished: ABORTED {noformat} And the part of my pipeline script {code:groovy} milestone 40stage('Déploiement recette') { // Approbation de déploiement en recette avec demande d'un nom de tag à créer def tag = input message: 'Déployer la version en recette ?', ok: 'Déployer', parameters: [[$class: 'TextParameterDefinition', defaultValue: 'vXXX', description: 'Tagger la version dans GIT', name: 'Tag'] ], submitter: 'admin' // Déploiement du nouveau package lock(resource:'immodem-staging-server', inversePrecedence: true) {milestone 50node {} }} {code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Is
[JIRA] (JENKINS-38779) Group Attribute while setting up Saml SSO
Title: Message Title Priyadarshi Peter created an issue Jenkins / JENKINS-38779 Group Attribute while setting up Saml SSO Issue Type: Task Assignee: Ben McCann Attachments: jenkins_settings.docx, saml-response.txt Components: saml-plugin Created: 2016/Oct/06 9:33 AM Priority: Critical Reporter: Priyadarshi Peter Hi Team, Issue:We need help in figuring out what should be put in Group Attribute field Explanation: We have successfully setup Saml sso in jenkins. We want to use Saml groups for Authentication as well as Authorization. As of now Authentication is working fine with multiple Saml groups. We want to authorize users based on which group he/she belongs to. After going through the document provided in the Jenkins(Saml Plugin) site,we came to know that we have to specify the Group Attribute and only then it should be able to Authorize Users. As per the Saml Response we have given the Group Attribute as "blueGroups" , but it doesn't authorize the users. Please check the attached file for saml response. Please Note:while adding the group names in the "Role Based Strategy Plugin" group icon is not coming.
[JIRA] (JENKINS-38780) Pipeline jobs are not marked as stuck in the build queue
Title: Message Title Pierre-Gildas MILLON created an issue Jenkins / JENKINS-38780 Pipeline jobs are not marked as stuck in the build queue Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Oct/06 9:39 AM Priority: Minor Reporter: Pierre-Gildas MILLON When a pipeline jobs has been waiting for a slave for too long in the build queue (relative to it's execution time), the clock icon (representing the isStuck() getter of a job) is not shown. Add Comment This message was sent by A
[JIRA] (JENKINS-30196) SVN Exception : svn: E210004: Malformed network data
Title: Message Title Gilles-Henri de La Rivière assigned an issue to Manuel Recena Soto Jenkins / JENKINS-30196 SVN Exception : svn: E210004: Malformed network data Change By: Gilles-Henri de La Rivière Assignee: Gilles-Henri de La Rivière Manuel Recena Soto Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-30196) SVN Exception : svn: E210004: Malformed network data
Title: Message Title Gilles-Henri de La Rivière assigned an issue to Gilles-Henri de La Rivière Jenkins / JENKINS-30196 SVN Exception : svn: E210004: Malformed network data Change By: Gilles-Henri de La Rivière Assignee: Manuel Recena Soto Gilles-Henri de La Rivière Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-36041) default ldap timeouts are inappropriate
Title: Message Title James Nord commented on JENKINS-36041 Re: default ldap timeouts are inappropriate [https://bugs.openjdk.java.net/browse/JDK-8139721 | JDK-8139721] However the workaround seems not to work... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38777) Signing for "Unity-iPhone" requires a development team
Title: Message Title Kristofer Boman updated an issue Jenkins / JENKINS-38777 Signing for "Unity-iPhone" requires a development team Change By: Kristofer Boman I recently setup a Macbook Pro with jenkins to automatically build Unity iOS projects. No mather the settings i use for signing the .ipa file i get*=== BUILD TARGET Unity-iPhone OF PROJECT Unity-iPhone WITH CONFIGURATION Release === Check dependencies Signing for "Unity-iPhone" requires a development team. Select a development team in the project editor. Code signing is required for product type 'Application' in SDK 'iOS 10.0' ** BUILD FAILED ** The following build commands failed: Check dependencies (1 failure) Build step 'Xcode' marked build as failure Finished: FAILURE* How can i set the team automatically so the signing works? *Full log from Xcode build step* Exiting batchmode successfully now! [UnityTest] $ /bin/sh /var/folders/9d/lhvckkyx4hs8vhc_yqw8ynnrgn/T/hudson6913529922758759577.sh Working directory is /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins. [BadMen-Jenkins] $ /usr/bin/xcodebuild -version Xcode 8.0 Build version 8A218a Fetching marketing version number (CFBundleShortVersionString) from project. [BadMen-Jenkins] $ /usr/bin/agvtool mvers -terse1 Found marketing version (CFBundleShortVersionString): 1.0. Marketing version (CFBundleShortVersionString) found in project configuration: 1.0. Fetching technical version number (CFBundleVersion) from project. [BadMen-Jenkins] $ /usr/bin/agvtool vers -terse No marketing version found (CFBundleVersion) Technical version (CFBundleVersion) found in project configuration: . Marketing version (CFBundleShortVersionString) used by Jenkins to produce the IPA: 1.0 Technical version (CFBundleVersion) used by Jenkins to produce the IPA: Cleaning build directory: /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins/Build/AdHoc Cleaning up test-reports : /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins/test-reports [BadMen-Jenkins] $ /usr/bin/security list-keychains -s /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security default-keychain -d user -s /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security unlock-keychain -p /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security show-keychain-info /Users/kristoferboman/Library/Keychains/login.keychain Keychain "/Users/kristoferboman/Library/Keychains/login.keychain" no-timeout === == Available provisioning profiles [BadMen-Jenkins] $ /usr/bin/security find-identity -p codesigning -v 1) E47B932AF536F96E88FE3177D94F3909B8DA46F2 "iPhone Developer: Kristofer Boman (98UA3U6J4X)" 2) A4E8CFDBE536D56BF5BD7206FE799DB46AE5B323 "iPhone Distribution: SOZAP AB (3KH49E5UZT)" 2 valid identities found == Can we find the requested provisioning profile ? [BadMen-Jenkins] $ /usr/bin/security find-c
[JIRA] (JENKINS-38777) Signing for "Unity-iPhone" requires a development team
Title: Message Title Kristofer Boman updated an issue Jenkins / JENKINS-38777 Signing for "Unity-iPhone" requires a development team Change By: Kristofer Boman I recently setup a Macbook Pro with jenkins to automatically build Unity iOS projects. No mather the settings i use for signing the .ipa file i get *=== BUILD TARGET Unity-iPhone OF PROJECT Unity-iPhone WITH CONFIGURATION Release === Check dependencies Signing for "Unity-iPhone" requires a development team. Select a development team in the project editor. Code signing is required for product type 'Application' in SDK 'iOS 10.0' ** BUILD FAILED ** The following build commands failed: Check dependencies (1 failure) Build step 'Xcode' marked build as failure Finished: FAILURE* How can i set the team automatically so the signing works? *Full log from Xcode build step* Exiting batchmode successfully now! [UnityTest] $ /bin/sh /var/folders/9d/lhvckkyx4hs8vhc_yqw8ynnrgn/T/hudson6913529922758759577.sh Working directory is /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins. [BadMen-Jenkins] $ /usr/bin/xcodebuild -version Xcode 8.0 Build version 8A218a Fetching marketing version number (CFBundleShortVersionString) from project. [BadMen-Jenkins] $ /usr/bin/agvtool mvers -terse1 Found marketing version (CFBundleShortVersionString): 1.0. Marketing version (CFBundleShortVersionString) found in project configuration: 1.0. Fetching technical version number (CFBundleVersion) from project. [BadMen-Jenkins] $ /usr/bin/agvtool vers -terse No marketing version found (CFBundleVersion) Technical version (CFBundleVersion) found in project configuration: . Marketing version (CFBundleShortVersionString) used by Jenkins to produce the IPA: 1.0 Technical version (CFBundleVersion) used by Jenkins to produce the IPA: Cleaning build directory: /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins/Build/AdHoc Cleaning up test-reports : /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins/test-reports [BadMen-Jenkins] $ /usr/bin/security list-keychains -s /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security default-keychain -d user -s /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security unlock-keychain -p /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security show-keychain-info /Users/kristoferboman/Library/Keychains/login.keychain Keychain "/Users/kristoferboman/Library/Keychains/login.keychain" no-timeout === == Available provisioning profiles [BadMen-Jenkins] $ /usr/bin/security find-identity -p codesigning -v 1) E47B932AF536F96E88FE3177D94F3909B8DA46F2 "iPhone Developer: Kristofer Boman (98UA3U6J4X)" 2) A4E8CFDBE536D56BF5BD7206FE799DB46AE5B323 "iPhone Distribution: SOZAP AB (3KH49E5UZT)" 2 valid identities found == Can we find the requested provisioning profile ? [BadMen-Jenkins] $ /usr/bin/security find-ce
[JIRA] (JENKINS-38777) Signing for "Unity-iPhone" requires a development team
Title: Message Title Kristofer Boman updated an issue Jenkins / JENKINS-38777 Signing for "Unity-iPhone" requires a development team Change By: Kristofer Boman I recently setup a Macbook Pro with jenkins to automatically build Unity iOS projects. No mather the settings i use for signing the .ipa file i get *=== BUILD TARGET Unity-iPhone OF PROJECT Unity-iPhone WITH CONFIGURATION Release === Check dependencies Signing for "Unity-iPhone" requires a development team. Select a development team in the project editor. Code signing is required for product type 'Application' in SDK 'iOS 10.0' ** BUILD FAILED ** The following build commands failed: Check dependencies (1 failure) Build step 'Xcode' marked build as failure Finished: FAILURE*How can i set the team automatically so the signing works?*Full log from Xcode build step* Exiting batchmode successfully now! [UnityTest] $ /bin/sh /var/folders/9d/lhvckkyx4hs8vhc_yqw8ynnrgn/T/hudson6913529922758759577.sh Working directory is /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins. [BadMen-Jenkins] $ /usr/bin/xcodebuild -version Xcode 8.0 Build version 8A218a Fetching marketing version number (CFBundleShortVersionString) from project. [BadMen-Jenkins] $ /usr/bin/agvtool mvers -terse1 Found marketing version (CFBundleShortVersionString): 1.0. Marketing version (CFBundleShortVersionString) found in project configuration: 1.0. Fetching technical version number (CFBundleVersion) from project. [BadMen-Jenkins] $ /usr/bin/agvtool vers -terse No marketing version found (CFBundleVersion) Technical version (CFBundleVersion) found in project configuration: . Marketing version (CFBundleShortVersionString) used by Jenkins to produce the IPA: 1.0 Technical version (CFBundleVersion) used by Jenkins to produce the IPA: Cleaning build directory: /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins/Build/AdHoc Cleaning up test-reports : /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins/test-reports [BadMen-Jenkins] $ /usr/bin/security list-keychains -s /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security default-keychain -d user -s /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security unlock-keychain -p /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security show-keychain-info /Users/kristoferboman/Library/Keychains/login.keychain Keychain "/Users/kristoferboman/Library/Keychains/login.keychain" no-timeout === == Available provisioning profiles [BadMen-Jenkins] $ /usr/bin/security find-identity -p codesigning -v 1) E47B932AF536F96E88FE3177D94F3909B8DA46F2 "iPhone Developer: Kristofer Boman (98UA3U6J4X)" 2) A4E8CFDBE536D56BF5BD7206FE799DB46AE5B323 "iPhone Distribution: SOZAP AB (3KH49E5UZT)" 2 valid identities found == Can we find the requested provisioning profile ? [BadMen-Jenkins] $ /usr/bin/security f
[JIRA] (JENKINS-38777) Signing for "Unity-iPhone" requires a development team
Title: Message Title Kristofer Boman updated an issue Jenkins / JENKINS-38777 Signing for "Unity-iPhone" requires a development team Change By: Kristofer Boman I recently setup a Macbook Pro with jenkins to automatically build Unity iOS projects. No mather the settings i use for signing the .ipa file i get * * === BUILD TARGET Unity-iPhone OF PROJECT Unity-iPhone WITH CONFIGURATION Release === Check dependencies Signing for "Unity-iPhone" requires a development team. Select a development team in the project editor. Code signing is required for product type 'Application' in SDK 'iOS 10.0' ** BUILD FAILED ** The following build commands failed: Check dependencies (1 failure) Build step 'Xcode' marked build as failure Finished: FAILURE** How can i set the team automatically so the signing works? *Full log from Xcode build step* Exiting batchmode successfully now! [UnityTest] $ /bin/sh /var/folders/9d/lhvckkyx4hs8vhc_yqw8ynnrgn/T/hudson6913529922758759577.sh Working directory is /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins. [BadMen-Jenkins] $ /usr/bin/xcodebuild -version Xcode 8.0 Build version 8A218a Fetching marketing version number (CFBundleShortVersionString) from project. [BadMen-Jenkins] $ /usr/bin/agvtool mvers -terse1 Found marketing version (CFBundleShortVersionString): 1.0. Marketing version (CFBundleShortVersionString) found in project configuration: 1.0. Fetching technical version number (CFBundleVersion) from project. [BadMen-Jenkins] $ /usr/bin/agvtool vers -terse No marketing version found (CFBundleVersion) Technical version (CFBundleVersion) found in project configuration: . Marketing version (CFBundleShortVersionString) used by Jenkins to produce the IPA: 1.0 Technical version (CFBundleVersion) used by Jenkins to produce the IPA: Cleaning build directory: /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins/Build/AdHoc Cleaning up test-reports : /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins/test-reports [BadMen-Jenkins] $ /usr/bin/security list-keychains -s /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security default-keychain -d user -s /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security unlock-keychain -p /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security show-keychain-info /Users/kristoferboman/Library/Keychains/login.keychain Keychain "/Users/kristoferboman/Library/Keychains/login.keychain" no-timeout === == Available provisioning profiles [BadMen-Jenkins] $ /usr/bin/security find-identity -p codesigning -v 1) E47B932AF536F96E88FE3177D94F3909B8DA46F2 "iPhone Developer: Kristofer Boman (98UA3U6J4X)" 2) A4E8CFDBE536D56BF5BD7206FE799DB46AE5B323 "iPhone Distribution: SOZAP AB (3KH49E5UZT)" 2 valid identities found == Can we find the requested provisioning profile ? [BadMen-Jenkins] $ /usr/bin/security
[JIRA] (JENKINS-38777) Signing for "Unity-iPhone" requires a development team
Title: Message Title Kristofer Boman updated an issue Jenkins / JENKINS-38777 Signing for "Unity-iPhone" requires a development team Change By: Kristofer Boman I recently setup a Macbook Pro with jenkins to automatically build Unity iOS projects. No mather the settings i use for signing the .ipa file i get *=== BUILD TARGET Unity-iPhone OF PROJECT Unity-iPhone WITH CONFIGURATION Release === Check dependencies Signing for "Unity-iPhone" requires a development team. Select a development team in the project editor. Code signing is required for product type 'Application' in SDK 'iOS 10.0' ** BUILD FAILED ** The following build commands failed: Check dependencies (1 failure) Build step 'Xcode' marked build as failure Finished: FAILURE * How can i set the team automatically so the signing works? *Full log from Xcode build step* Exiting batchmode successfully now! [UnityTest] $ /bin/sh /var/folders/9d/lhvckkyx4hs8vhc_yqw8ynnrgn/T/hudson6913529922758759577.sh Working directory is /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins. [BadMen-Jenkins] $ /usr/bin/xcodebuild -version Xcode 8.0 Build version 8A218a Fetching marketing version number (CFBundleShortVersionString) from project. [BadMen-Jenkins] $ /usr/bin/agvtool mvers -terse1 Found marketing version (CFBundleShortVersionString): 1.0. Marketing version (CFBundleShortVersionString) found in project configuration: 1.0. Fetching technical version number (CFBundleVersion) from project. [BadMen-Jenkins] $ /usr/bin/agvtool vers -terse No marketing version found (CFBundleVersion) Technical version (CFBundleVersion) found in project configuration: . Marketing version (CFBundleShortVersionString) used by Jenkins to produce the IPA: 1.0 Technical version (CFBundleVersion) used by Jenkins to produce the IPA: Cleaning build directory: /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins/Build/AdHoc Cleaning up test-reports : /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins/test-reports [BadMen-Jenkins] $ /usr/bin/security list-keychains -s /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security default-keychain -d user -s /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security unlock-keychain -p /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security show-keychain-info /Users/kristoferboman/Library/Keychains/login.keychain Keychain "/Users/kristoferboman/Library/Keychains/login.keychain" no-timeout === == Available provisioning profiles [BadMen-Jenkins] $ /usr/bin/security find-identity -p codesigning -v 1) E47B932AF536F96E88FE3177D94F3909B8DA46F2 "iPhone Developer: Kristofer Boman (98UA3U6J4X)" 2) A4E8CFDBE536D56BF5BD7206FE799DB46AE5B323 "iPhone Distribution: SOZAP AB (3KH49E5UZT)" 2 valid identities found == Can we find the requested provisioning profile ? [BadMen-Jenkins] $ /usr/bin/security find-c
[JIRA] (JENKINS-38777) Signing for "Unity-iPhone" requires a development team
Title: Message Title Kristofer Boman updated an issue Jenkins / JENKINS-38777 Signing for "Unity-iPhone" requires a development team Change By: Kristofer Boman I recently setup a Macbook Pro with jenkins to automatically build Unity iOS projects. No mather the settings i use for signing the .ipa file i get * * === BUILD TARGET Unity-iPhone OF PROJECT Unity-iPhone WITH CONFIGURATION Release === Check dependencies Signing for "Unity-iPhone" requires a development team. Select a development team in the project editor. Code signing is required for product type 'Application' in SDK 'iOS 10.0' ** BUILD FAILED ** The following build commands failed: Check dependencies (1 failure) Build step 'Xcode' marked build as failure Finished: FAILURE * * How can i set the team automatically so the signing works? *Full log from Xcode build step* Exiting batchmode successfully now! [UnityTest] $ /bin/sh /var/folders/9d/lhvckkyx4hs8vhc_yqw8ynnrgn/T/hudson6913529922758759577.sh Working directory is /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins. [BadMen-Jenkins] $ /usr/bin/xcodebuild -version Xcode 8.0 Build version 8A218a Fetching marketing version number (CFBundleShortVersionString) from project. [BadMen-Jenkins] $ /usr/bin/agvtool mvers -terse1 Found marketing version (CFBundleShortVersionString): 1.0. Marketing version (CFBundleShortVersionString) found in project configuration: 1.0. Fetching technical version number (CFBundleVersion) from project. [BadMen-Jenkins] $ /usr/bin/agvtool vers -terse No marketing version found (CFBundleVersion) Technical version (CFBundleVersion) found in project configuration: . Marketing version (CFBundleShortVersionString) used by Jenkins to produce the IPA: 1.0 Technical version (CFBundleVersion) used by Jenkins to produce the IPA: Cleaning build directory: /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins/Build/AdHoc Cleaning up test-reports : /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins/test-reports [BadMen-Jenkins] $ /usr/bin/security list-keychains -s /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security default-keychain -d user -s /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security unlock-keychain -p /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security show-keychain-info /Users/kristoferboman/Library/Keychains/login.keychain Keychain "/Users/kristoferboman/Library/Keychains/login.keychain" no-timeout === == Available provisioning profiles [BadMen-Jenkins] $ /usr/bin/security find-identity -p codesigning -v 1) E47B932AF536F96E88FE3177D94F3909B8DA46F2 "iPhone Developer: Kristofer Boman (98UA3U6J4X)" 2) A4E8CFDBE536D56BF5BD7206FE799DB46AE5B323 "iPhone Distribution: SOZAP AB (3KH49E5UZT)" 2 valid identities found == Can we find the requested provisioning profile ? [BadMen-Jenkins] $ /usr/bin/security
[JIRA] (JENKINS-38777) Signing for "Unity-iPhone" requires a development team
Title: Message Title Kristofer Boman updated an issue Jenkins / JENKINS-38777 Signing for "Unity-iPhone" requires a development team Change By: Kristofer Boman I recently setup a Macbook Pro with jenkins to automatically build Unity iOS projects. No mather the settings i use for signing the .ipa file i get *=== BUILD TARGET Unity-iPhone OF PROJECT Unity-iPhone WITH CONFIGURATION Release === Check dependencies Signing for "Unity-iPhone" requires a development team. Select a development team in the project editor. Code signing is required for product type 'Application' in SDK 'iOS 10.0' ** BUILD FAILED ** The following build commands failed: Check dependencies (1 failure) Build step 'Xcode' marked build as failure Finished: FAILURE*How can i set the team automatically so the signing works? *Full log from Xcode build step* Exiting batchmode successfully now! [UnityTest] $ /bin/sh /var/folders/9d/lhvckkyx4hs8vhc_yqw8ynnrgn/T/hudson6913529922758759577.sh Working directory is /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins. [BadMen-Jenkins] $ /usr/bin/xcodebuild -version Xcode 8.0 Build version 8A218a Fetching marketing version number (CFBundleShortVersionString) from project. [BadMen-Jenkins] $ /usr/bin/agvtool mvers -terse1 Found marketing version (CFBundleShortVersionString): 1.0. Marketing version (CFBundleShortVersionString) found in project configuration: 1.0. Fetching technical version number (CFBundleVersion) from project. [BadMen-Jenkins] $ /usr/bin/agvtool vers -terse No marketing version found (CFBundleVersion) Technical version (CFBundleVersion) found in project configuration: . Marketing version (CFBundleShortVersionString) used by Jenkins to produce the IPA: 1.0 Technical version (CFBundleVersion) used by Jenkins to produce the IPA: Cleaning build directory: /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins/Build/AdHoc Cleaning up test-reports : /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins/test-reports [BadMen-Jenkins] $ /usr/bin/security list-keychains -s /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security default-keychain -d user -s /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security unlock-keychain -p /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security show-keychain-info /Users/kristoferboman/Library/Keychains/login.keychain Keychain "/Users/kristoferboman/Library/Keychains/login.keychain" no-timeout === == Available provisioning profiles [BadMen-Jenkins] $ /usr/bin/security find-identity -p codesigning -v 1) E47B932AF536F96E88FE3177D94F3909B8DA46F2 "iPhone Developer: Kristofer Boman (98UA3U6J4X)" 2) A4E8CFDBE536D56BF5BD7206FE799DB46AE5B323 "iPhone Distribution: SOZAP AB (3KH49E5UZT)" 2 valid identities found == Can we find the requested provisioning profile ? [BadMen-Jenkins] $ /usr/bin/security fi
[JIRA] (JENKINS-38777) Signing for "Unity-iPhone" requires a development team
Title: Message Title Kristofer Boman updated an issue Jenkins / JENKINS-38777 Signing for "Unity-iPhone" requires a development team Change By: Kristofer Boman I recently setup a Macbook Pro with jenkins to automatically build Unity iOS projects. No mather the settings i use for signing the .ipa file i get _ === BUILD TARGET Unity-iPhone OF PROJECT Unity-iPhone WITH CONFIGURATION Release === Check dependencies Signing for "Unity-iPhone" requires a development team. Select a development team in the project editor. Code signing is required for product type 'Application' in SDK 'iOS 10.0' BUILD FAILED The following build commands failed: Check dependencies (1 failure) Build step 'Xcode' marked build as failure Finished: FAILURE_ FAILURE How can i set the team automatically so the signing works? *Full log from Xcode build step* Exiting batchmode successfully now! [UnityTest] $ /bin/sh /var/folders/9d/lhvckkyx4hs8vhc_yqw8ynnrgn/T/hudson6913529922758759577.sh Working directory is /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins. [BadMen-Jenkins] $ /usr/bin/xcodebuild -version Xcode 8.0 Build version 8A218a Fetching marketing version number (CFBundleShortVersionString) from project. [BadMen-Jenkins] $ /usr/bin/agvtool mvers -terse1 Found marketing version (CFBundleShortVersionString): 1.0. Marketing version (CFBundleShortVersionString) found in project configuration: 1.0. Fetching technical version number (CFBundleVersion) from project. [BadMen-Jenkins] $ /usr/bin/agvtool vers -terse No marketing version found (CFBundleVersion) Technical version (CFBundleVersion) found in project configuration: . Marketing version (CFBundleShortVersionString) used by Jenkins to produce the IPA: 1.0 Technical version (CFBundleVersion) used by Jenkins to produce the IPA: Cleaning build directory: /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins/Build/AdHoc Cleaning up test-reports : /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins/test-reports [BadMen-Jenkins] $ /usr/bin/security list-keychains -s /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security default-keychain -d user -s /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security unlock-keychain -p /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security show-keychain-info /Users/kristoferboman/Library/Keychains/login.keychain Keychain "/Users/kristoferboman/Library/Keychains/login.keychain" no-timeout === == Available provisioning profiles [BadMen-Jenkins] $ /usr/bin/security find-identity -p codesigning -v 1) E47B932AF536F96E88FE3177D94F3909B8DA46F2 "iPhone Developer: Kristofer Boman (98UA3U6J4X)" 2) A4E8CFDBE536D56BF5BD7206FE799DB46AE5B323 "iPhone Distribution: SOZAP AB (3KH49E5UZT)" 2 valid identities found == Can we find the requested provisioning profile ? [BadMen-Jenkins] $ /usr/bin/security fi
[JIRA] (JENKINS-38777) Signing for "Unity-iPhone" requires a development team
Title: Message Title Kristofer Boman updated an issue Jenkins / JENKINS-38777 Signing for "Unity-iPhone" requires a development team Change By: Kristofer Boman I recently setup a Macbook Pro with jenkins to automatically build Unity iOS projects. No mather the settings i use for signing the .ipa file i get * _ === BUILD TARGET Unity-iPhone OF PROJECT Unity-iPhone WITH CONFIGURATION Release === Check dependencies Signing for "Unity-iPhone" requires a development team. Select a development team in the project editor. Code signing is required for product type 'Application' in SDK 'iOS 10.0' BUILD FAILED The following build commands failed: Check dependencies (1 failure) Build step 'Xcode' marked build as failure Finished: FAILURE* FAILURE_ How can i set the team automatically so the signing works? *Full log from Xcode build step* Exiting batchmode successfully now! [UnityTest] $ /bin/sh /var/folders/9d/lhvckkyx4hs8vhc_yqw8ynnrgn/T/hudson6913529922758759577.sh Working directory is /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins. [BadMen-Jenkins] $ /usr/bin/xcodebuild -version Xcode 8.0 Build version 8A218a Fetching marketing version number (CFBundleShortVersionString) from project. [BadMen-Jenkins] $ /usr/bin/agvtool mvers -terse1 Found marketing version (CFBundleShortVersionString): 1.0. Marketing version (CFBundleShortVersionString) found in project configuration: 1.0. Fetching technical version number (CFBundleVersion) from project. [BadMen-Jenkins] $ /usr/bin/agvtool vers -terse No marketing version found (CFBundleVersion) Technical version (CFBundleVersion) found in project configuration: . Marketing version (CFBundleShortVersionString) used by Jenkins to produce the IPA: 1.0 Technical version (CFBundleVersion) used by Jenkins to produce the IPA: Cleaning build directory: /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins/Build/AdHoc Cleaning up test-reports : /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins/test-reports [BadMen-Jenkins] $ /usr/bin/security list-keychains -s /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security default-keychain -d user -s /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security unlock-keychain -p /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security show-keychain-info /Users/kristoferboman/Library/Keychains/login.keychain Keychain "/Users/kristoferboman/Library/Keychains/login.keychain" no-timeout === == Available provisioning profiles [BadMen-Jenkins] $ /usr/bin/security find-identity -p codesigning -v 1) E47B932AF536F96E88FE3177D94F3909B8DA46F2 "iPhone Developer: Kristofer Boman (98UA3U6J4X)" 2) A4E8CFDBE536D56BF5BD7206FE799DB46AE5B323 "iPhone Distribution: SOZAP AB (3KH49E5UZT)" 2 valid identities found == Can we find the requested provisioning profile ? [BadMen-Jenkins] $ /usr/bin/security
[JIRA] (JENKINS-38777) Signing for "Unity-iPhone" requires a development team
Title: Message Title Kristofer Boman updated an issue Jenkins / JENKINS-38777 Signing for "Unity-iPhone" requires a development team Change By: Kristofer Boman *I recently setup a Macbook Pro with jenkins to automatically build Unity iOS projects. No mather the settings i use for signing the .ipa file i get *=== BUILD TARGET Unity-iPhone OF PROJECT Unity-iPhone WITH CONFIGURATION Release === Check dependencies Signing for "Unity-iPhone" requires a development team. Select a development team in the project editor. Code signing is required for product type 'Application' in SDK 'iOS 10.0' BUILD FAILED The following build commands failed: Check dependencies (1 failure) Build step 'Xcode' marked build as failure Finished: FAILURE*How can i set the team automatically so the signing works?**Full log from Xcode build step* Exiting batchmode successfully now! [UnityTest] $ /bin/sh /var/folders/9d/lhvckkyx4hs8vhc_yqw8ynnrgn/T/hudson6913529922758759577.sh Working directory is /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins. [BadMen-Jenkins] $ /usr/bin/xcodebuild -version Xcode 8.0 Build version 8A218a Fetching marketing version number (CFBundleShortVersionString) from project. [BadMen-Jenkins] $ /usr/bin/agvtool mvers -terse1 Found marketing version (CFBundleShortVersionString): 1.0. Marketing version (CFBundleShortVersionString) found in project configuration: 1.0. Fetching technical version number (CFBundleVersion) from project. [BadMen-Jenkins] $ /usr/bin/agvtool vers -terse No marketing version found (CFBundleVersion) Technical version (CFBundleVersion) found in project configuration: . Marketing version (CFBundleShortVersionString) used by Jenkins to produce the IPA: 1.0 Technical version (CFBundleVersion) used by Jenkins to produce the IPA: Cleaning build directory: /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins/Build/AdHoc Cleaning up test-reports : /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins/test-reports [BadMen-Jenkins] $ /usr/bin/security list-keychains -s /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security default-keychain -d user -s /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security unlock-keychain -p /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security show-keychain-info /Users/kristoferboman/Library/Keychains/login.keychain Keychain "/Users/kristoferboman/Library/Keychains/login.keychain" no-timeout === == Available provisioning profiles [BadMen-Jenkins] $ /usr/bin/security find-identity -p codesigning -v 1) E47B932AF536F96E88FE3177D94F3909B8DA46F2 "iPhone Developer: Kristofer Boman (98UA3U6J4X)" 2) A4E8CFDBE536D56BF5BD7206FE799DB46AE5B323 "iPhone Distribution: SOZAP AB (3KH49E5UZT)" 2 valid identities found == Can we find the requested provisioning profile ? [BadMen-Jenkins] $ /usr/bin/security find-certifica
[JIRA] (JENKINS-38777) Signing for "Unity-iPhone" requires a development team
Title: Message Title Kristofer Boman updated an issue Jenkins / JENKINS-38777 Signing for "Unity-iPhone" requires a development team Change By: Kristofer Boman * I recently setup a Macbook Pro with jenkins to automatically build Unity iOS projects. No mather the settings i use for signing the .ipa file i get* === BUILD TARGET Unity-iPhone OF PROJECT Unity-iPhone WITH CONFIGURATION Release === Check dependencies Signing for "Unity-iPhone" requires a development team. Select a development team in the project editor. Code signing is required for product type 'Application' in SDK 'iOS 10.0' BUILD FAILED The following build commands failed: Check dependencies (1 failure) Build step 'Xcode' marked build as failure Finished: FAILURE * How can i set the team automatically so the signing works?* *Full log from Xcode build step* Exiting batchmode successfully now! [UnityTest] $ /bin/sh /var/folders/9d/lhvckkyx4hs8vhc_yqw8ynnrgn/T/hudson6913529922758759577.sh Working directory is /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins. [BadMen-Jenkins] $ /usr/bin/xcodebuild -version Xcode 8.0 Build version 8A218a Fetching marketing version number (CFBundleShortVersionString) from project. [BadMen-Jenkins] $ /usr/bin/agvtool mvers -terse1 Found marketing version (CFBundleShortVersionString): 1.0. Marketing version (CFBundleShortVersionString) found in project configuration: 1.0. Fetching technical version number (CFBundleVersion) from project. [BadMen-Jenkins] $ /usr/bin/agvtool vers -terse No marketing version found (CFBundleVersion) Technical version (CFBundleVersion) found in project configuration: . Marketing version (CFBundleShortVersionString) used by Jenkins to produce the IPA: 1.0 Technical version (CFBundleVersion) used by Jenkins to produce the IPA: Cleaning build directory: /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins/Build/AdHoc Cleaning up test-reports : /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins/test-reports [BadMen-Jenkins] $ /usr/bin/security list-keychains -s /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security default-keychain -d user -s /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security unlock-keychain -p /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security show-keychain-info /Users/kristoferboman/Library/Keychains/login.keychain Keychain "/Users/kristoferboman/Library/Keychains/login.keychain" no-timeout === == Available provisioning profiles [BadMen-Jenkins] $ /usr/bin/security find-identity -p codesigning -v 1) E47B932AF536F96E88FE3177D94F3909B8DA46F2 "iPhone Developer: Kristofer Boman (98UA3U6J4X)" 2) A4E8CFDBE536D56BF5BD7206FE799DB46AE5B323 "iPhone Distribution: SOZAP AB (3KH49E5UZT)" 2 valid identities found == Can we find the requested provisioning profile ? [BadMen-Jenkins] $ /usr/bin/securit
[JIRA] (JENKINS-38777) Signing for "Unity-iPhone" requires a development team
Title: Message Title Kristofer Boman updated an issue Jenkins / JENKINS-38777 Signing for "Unity-iPhone" requires a development team Change By: Kristofer Boman *I recently setup a Macbook Pro with jenkins to automatically build Unity iOS projects. No mather the settings i use for signing the .ipa file i get *=== BUILD TARGET Unity-iPhone OF PROJECT Unity-iPhone WITH CONFIGURATION Release === Check dependencies Signing for "Unity-iPhone" requires a development team. Select a development team in the project editor. Code signing is required for product type 'Application' in SDK 'iOS 10.0' BUILD FAILED The following build commands failed: Check dependencies (1 failure) Build step 'Xcode' marked build as failure Finished: FAILURE*How can i set the team automatically so the signing works? **Full log from Xcode build step* Exiting batchmode successfully now! [UnityTest] $ /bin/sh /var/folders/9d/lhvckkyx4hs8vhc_yqw8ynnrgn/T/hudson6913529922758759577.sh Working directory is /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins. [BadMen-Jenkins] $ /usr/bin/xcodebuild -version Xcode 8.0 Build version 8A218a Fetching marketing version number (CFBundleShortVersionString) from project. [BadMen-Jenkins] $ /usr/bin/agvtool mvers -terse1 Found marketing version (CFBundleShortVersionString): 1.0. Marketing version (CFBundleShortVersionString) found in project configuration: 1.0. Fetching technical version number (CFBundleVersion) from project. [BadMen-Jenkins] $ /usr/bin/agvtool vers -terse No marketing version found (CFBundleVersion) Technical version (CFBundleVersion) found in project configuration: . Marketing version (CFBundleShortVersionString) used by Jenkins to produce the IPA: 1.0 Technical version (CFBundleVersion) used by Jenkins to produce the IPA: Cleaning build directory: /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins/Build/AdHoc Cleaning up test-reports : /Users/kristoferboman/.jenkins/workspace/UnityTest/Exports/iOS/BadMen-Jenkins/test-reports [BadMen-Jenkins] $ /usr/bin/security list-keychains -s /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security default-keychain -d user -s /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security unlock-keychain -p /Users/kristoferboman/Library/Keychains/login.keychain [BadMen-Jenkins] $ /usr/bin/security show-keychain-info /Users/kristoferboman/Library/Keychains/login.keychain Keychain "/Users/kristoferboman/Library/Keychains/login.keychain" no-timeout === == Available provisioning profiles [BadMen-Jenkins] $ /usr/bin/security find-identity -p codesigning -v 1) E47B932AF536F96E88FE3177D94F3909B8DA46F2 "iPhone Developer: Kristofer Boman (98UA3U6J4X)" 2) A4E8CFDBE536D56BF5BD7206FE799DB46AE5B323 "iPhone Distribution: SOZAP AB (3KH49E5UZT)" 2 valid identities found == Can we find the requested provisioning profile ? [BadMen-Jenkins] $ /usr/bin/security find-certific
[JIRA] (JENKINS-37353) Last update of rvm-plugin disabled all my rvm configurations.
Title: Message Title Jeremy Venezia commented on JENKINS-37353 Re: Last update of rvm-plugin disabled all my rvm configurations. Updated jenkins and all my plugins. All my RVM configurations were wiped again... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-37353) Last update of rvm-plugin disabled all my rvm configurations.
Title: Message Title Jeremy Venezia updated an issue Jenkins / JENKINS-37353 Last update of rvm-plugin disabled all my rvm configurations. Change By: Jeremy Venezia Issue Type: Improvement Bug Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38768) [android] Emulator did not appear to start; giving up on Windows
Title: Message Title Louie Mandi updated an issue Jenkins / JENKINS-38768 [android] Emulator did not appear to start; giving up on Windows Change By: Louie Mandi Attachment: Emulator Error.PNG Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38778) Reserved node leaked from 'DisposableQueue'
Title: Message Title Pavel Janoušek started work on JENKINS-38778 Change By: Pavel Janoušek Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38412) Starvation can occur if job isn't restricted
Title: Message Title Pavel Janoušek commented on JENKINS-38412 Re: Starvation can occur if job isn't restricted PR sent. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38366) Instance of ForemanSharedNode should be NORMAL if label == null
Title: Message Title Pavel Janoušek commented on JENKINS-38366 Re: Instance of ForemanSharedNode should be NORMAL if label == null PR sent. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38778) Reserved node leaked from 'DisposableQueue'
Title: Message Title Pavel Janoušek assigned an issue to Pavel Janoušek Jenkins / JENKINS-38778 Reserved node leaked from 'DisposableQueue' Change By: Pavel Janoušek Assignee: Scott Hebert Pavel Janoušek Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38690) JNLPv4 Thread storm
Title: Message Title James Nord started work on JENKINS-38690 Change By: James Nord Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38768) [android] Emulator did not appear to start; giving up on Windows
Title: Message Title Louie Mandi commented on JENKINS-38768 Re: [android] Emulator did not appear to start; giving up on Windows When I try command you posted above on command line. I got this error "Qt5Core.dll is missing." Please see the attached snapshot. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38781) p4 unshelve not updating changes
Title: Message Title Morne Joubert created an issue Jenkins / JENKINS-38781 p4 unshelve not updating changes Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2016/Oct/06 10:43 AM Priority: Minor Reporter: Morne Joubert I am trying to use the standalone p4 unshelve in the pipeline code. This works fine, except that it doesn't update the SCM changes / getAffectedFiles() ? at all. This is done correctly in the normal sync step in a job when a shelved cl is passed in. If this works then i can implement JENKINS-32761 using pipeline code. At the moment this bug means i cannot move to using pipelines in some cases. If i can get a hint on where to make the changes then i could see if i can help Add Comment
[JIRA] (JENKINS-38782) Perform form validation on config page
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-38782 Perform form validation on config page Issue Type: Bug Assignee: Tomas Westling Components: kerberos-sso-plugin Created: 2016/Oct/06 10:58 AM Priority: Minor Reporter: Oliver Gondža Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenki
[JIRA] (JENKINS-37621) Post-Build Checkpoint fail with NoSuchElementException
Title: Message Title PTC ALM commented on JENKINS-37621 Re: Post-Build Checkpoint fail with NoSuchElementException Hi Marcus, we tried reproducing this issue with a #s project configuration, but unable to reproduce this. Could you attach the IntegritySCM log (Log Level : All ) for the entire build (Refer Troubleshooting section in https://wiki.jenkins-ci.org/display/JENKINS/PTC+Integrity+Plugin%20#Troubleshooting) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-33796) Make Repository Connector Plugin Pipeline Compatible
Title: Message Title Matthias Balke commented on JENKINS-33796 Re: Make Repository Connector Plugin Pipeline Compatible I need pipeline support too. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-33796) Make Repository Connector Plugin Pipeline Compatible
Title: Message Title
Matthias Balke edited a comment on JENKINS-33796
Re: Make Repository Connector Plugin Pipeline Compatible
I need pipeline support too. For the time beeing until this is supported, is there a workaround using {{step}}?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] (JENKINS-33079) Handling prebuild checkpoint results in Pipeline
Title: Message Title
PTC ALM commented on JENKINS-33079
Re: Handling prebuild checkpoint results in Pipeline
Hi Matthias, Whenever the MKSSI_BUILD environment variable is updated, the MKSSI_PROJECT (the si project configuration path) environment variable is updated just before it as below from the plugin codebase:
env.put("MKSSI_PROJECT", siProject.getConfigurationPath());
env.put("MKSSI_BUILD", siProject.getProjectRevision());
MKSSI_BUILD & MKSSI_PROJECT variables are coupled with each other even for parallel pipeline builds and can be used to identify each other in context.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] (JENKINS-38745) Data loss due to Artifactory plugin after upgrade
Title: Message Title Eyal Ben Moshe commented on JENKINS-38745 Re: Data loss due to Artifactory plugin after upgrade Thanks for reporting this. We are looking into it. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38783) Jobs waiting forever when http server not responding on custom tools request
Title: Message Title Bernd Meyer created an issue Jenkins / JENKINS-38783 Jobs waiting forever when http server not responding on custom tools request Issue Type: Bug Assignee: Oleg Nenashev Components: customtools-plugin Created: 2016/Oct/06 11:42 AM Environment: Docker Jenkins LTS 1.642.1 Custom Tools Plugin 0.4.4 Priority: Critical Reporter: Bernd Meyer We recently had an issue with our http server we utilize to serve the custom tools configured in Jenkins. The server was not responding while our test jobs tried to retrieve the custom tool assigned to them. Instead of running into a timeout they waited forever. The jobs did not react on my tries to abort/stop them, so i had to restart Jenkins. I could not get any information from the logs (neither system nor job releated) concerning this issue. Add Comment
[JIRA] (JENKINS-38248) Log should only be linkable from its line number
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38248 Re: Log should only be linkable from its line number Code changed in jenkins User: Thorsten Scherler Path: src/main/js/page_objects/blueocean/bluePipelineRunDetail.js http://jenkins-ci.org/commit/blueocean-acceptance-test/e44e76a15431774f4916a07d48f9b1c5cdb0e9e3 Log: JENKINS-38248 less flaky tests Compare: https://github.com/jenkinsci/blueocean-acceptance-test/compare/9fe22e2d0237...e44e76a15431 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38248) Log should only be linkable from its line number
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38248 Re: Log should only be linkable from its line number Code changed in jenkins User: Thorsten Scherler Path: src/test/js/log-karaoke/stages.js http://jenkins-ci.org/commit/blueocean-acceptance-test/7b662263d0777c724f761c1f129892998f684b45 Log: JENKINS-38248 fix typo Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-37621) Post-Build Checkpoint fail with NoSuchElementException
Title: Message Title Marcus Dilger updated an issue Jenkins / JENKINS-37621 Post-Build Checkpoint fail with NoSuchElementException Change By: Marcus Dilger Attachment: DetailLog_2016-10-06.txt Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-37621) Post-Build Checkpoint fail with NoSuchElementException
Title: Message Title Marcus Dilger commented on JENKINS-37621 Re: Post-Build Checkpoint fail with NoSuchElementException Hi. Thank you for Investigation. Log attached. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Alan Ranciato commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Anton Lundin sorry for my ignorance - where Are the html files located that you're modifying? I assume you are doing this post - compile on your running version? Thx Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Sorin Sbarnea reopened an issue I am reopening this issue because clearly the new current behaviour is even worse than it was when the bug was opened in the first place. If we generate directory names that are ~80 characters long we can expect trouble. Not to mention that putting all of them in a single folder could generate some other scalability issues. Until we have a proper change of the default behaviour (what we really should have!) people encountering this can do add this to /etc/default/jenkins: -Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=40 – probably it would be safe to put even a shorter value, like 20. The default number seems to be ridiculous high, somewhere between 80-90. This feature did broke out Jenkins which was already tuned to workaround the shebang PATH limitations by moving the home directory of Jenkins user to /j folder, as opposed to /var/lib/jenkins. This was enough for us but now is not anymore. Jenkins / JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named. Change By: Sorin Sbarnea Resolution: Fixed Status: Resolved Reopened Add Comment
[JIRA] (JENKINS-31154) 2.0: provide better workflow visualization out of the box
Title: Message Title Daniel Serodio commented on JENKINS-31154 Re: 2.0: provide better workflow visualization out of the box paul r unfortunately I'm afraid the Retry feature is exclusive to Cloudbees' Jenkins Enterprise. I'm also currently using Build Pipeline Plugin and I really miss the Retry feature. I hope Cloudbees decides to make this feature free/open source. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38784) User details update should be separated into a separate thread
Title: Message Title Félix Belzunce Arcos created an issue Jenkins / JENKINS-38784 User details update should be separated into a separate thread Issue Type: Improvement Assignee: Félix Belzunce Arcos Components: active-directory-plugin Created: 2016/Oct/06 12:36 PM Priority: Minor Reporter: Félix Belzunce Arcos User details update should be separated into a separate thread at: https://github.com/jenkinsci/active-directory-plugin/blob/1ea9f9785a6f9e6193e62f6fe67a569a5a50092b/src/main/java/hudson/plugins/active_directory/ActiveDirectoryUnixAuthenticationProvider.java#L369 We should be returning the user details and not waiting to update... the update can take place in the background. Add Comment
[JIRA] (JENKINS-38777) Signing for "Unity-iPhone" requires a development team
Title: Message Title Steven Shipton commented on JENKINS-38777 Re: Signing for "Unity-iPhone" requires a development team I managed to work around this issue by supplying the team as a command line argument. In Advanced Xcode build options -> Custom xcodebuild arguments Add DEVELOPMENT_TEAM=XXX where XXX = your developer prefix code You can get your prefix code from the Apple developer center: https://developer.apple.com/account/ios/identifier/bundle then pick an app to expand and copy the value from Prefix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-38356) Matrix Authorization Strategy Plugin - Block inheritance of global authorization matrix - This overrides administrators privileges
Title: Message Title Arnaud Héritier assigned an issue to Unassigned Jenkins / JENKINS-38356 Matrix Authorization Strategy Plugin - Block inheritance of global authorization matrix - This overrides administrators privileges Change By: Arnaud Héritier Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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.
