[JIRA] (JENKINS-40422) Inferring credentials resolves wrong credential
Title: Message Title Raul Arabaolaza resolved as Fixed Jenkins / JENKINS-40422 Inferring credentials resolves wrong credential Change By: Raul Arabaolaza 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-40422) Inferring credentials resolves wrong credential
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40422 Re: Inferring credentials resolves wrong credential Code changed in jenkins User: Raúl Arabaolaza Barquin Path: src/main/java/org/jenkinsci/plugins/pipeline/githubstatusnotification/GitHubStatusNotificationStep.java http://jenkins-ci.org/commit/pipeline-githubnotify-step-plugin/9ddafe848d297abfc4fbd7f3d7a11fc1edc6b110 Log: Merge pull request #2 from jenkinsci/JENKINS-40422 JENKINS-40422 Inferring credentials resolves wrong credential Compare: https://github.com/jenkinsci/pipeline-githubnotify-step-plugin/compare/ecf5373b47ac...9ddafe848d29 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-40494) Administrative monitor for installed unsafe plugins
Title: Message Title Daniel Beck commented on JENKINS-40494 Re: Administrative monitor for installed unsafe plugins Using UpdateSite this way would introduce weirdness related to multiple update sites. Not sure I'm a fan of that. Investigating… 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-39876) gogs-webhook-plugin always forgot secret after restart
Title: Message Title Ke Li commented on JENKINS-39876 Re: gogs-webhook-plugin always forgot secret after restart sander v things got right under 1.0.8. Thank you for your great job! 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-39876) gogs-webhook-plugin always forgot secret after restart
Title: Message Title Ke Li closed an issue as Fixed Problem solved with the newly released 1.0.8 Jenkins / JENKINS-39876 gogs-webhook-plugin always forgot secret after restart Change By: Ke Li Status: In Progress Closed 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-40664) Ecs Plugin fails to launch slave in Version 1.7
Title: Message Title Edward Willett created an issue Jenkins / JENKINS-40664 Ecs Plugin fails to launch slave in Version 1.7 Issue Type: Bug Assignee: Jan Roehrich Components: amazon-ecs-plugin Created: 2016/Dec/23 8:24 PM Environment: Jenkins Version 2.19.4 Amazon ECS plugin 1.7 only additional dependent plugins installed. Labels: plugin jenkins Priority: Major Reporter: Edward Willett Every time I install the plugin and try to create a new slave I get the following error in the slave configure logs. Stack trace javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/jenkins_home/war/WEB-INF/lib/jenkins-core-2.19.4.jar!/hudson/model/Computer/configure.jelly:43:71: No page found 'configure-entries.jelly' for class com.cloudbees.jenkins.plugins.amazonecs.ECSSlave This is a new system so I have the luxury of completely redoing the installation if required for troubleshooting assistance.
[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project
Title: Message Title Daniel Beck commented on JENKINS-40596 Re: 400 upon opening direct link of project in a GitHub organization project Patrice Bouillet On the /manage URL, for administrators, is there a message about reverse proxy being broken? Not correctly handling URL encoded forward slashes is specifically tested by this test. If so, follow the instructions and fix your configuration. 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-40657) can create instances of utilities from a shared libraries
Title: Message Title Andrew Bayer commented on JENKINS-40657 Re: can create instances of utilities from a shared libraries PR up with tests to verify this works (assuming Zot is made Serializable) - https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/81 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-40657) can create instances of utilities from a shared libraries
Title: Message Title Andrew Bayer started work on JENKINS-40657 Change By: Andrew Bayer 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-40657) can create instances of utilities from a shared libraries
Title: Message Title Andrew Bayer updated JENKINS-40657 Jenkins / JENKINS-40657 can create instances of utilities from a shared libraries Change By: Andrew Bayer 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-40657) can create instances of utilities from a shared libraries
Title: Message Title Andrew Bayer commented on JENKINS-40657 Re: can create instances of utilities from a shared libraries Huh, that ends up as an instance of org.jenkinsci.plugins.workflow.cps.DSL. 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-40188) Unable to use build step with boolean parameterized parameter
Title: Message Title
Patrick Wolf commented on JENKINS-40188
Re: Unable to use build step with boolean parameterized parameter
Andrew Bayer aurelien leboulanger I came across this a few weeks ago as well and found that it works if I don't use all CAPS. This works:
parameters{
booleanParam(defaultValue: true, description: '', name: 'skip')
}
This would not:
parameters{
booleanParam(defaultValue: true, description: '', name: 'SKIP')
}
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-40657) can create instances of utilities from a shared libraries
Title: Message Title Andrew Bayer commented on JENKINS-40657 Re: can create instances of utilities from a shared libraries Also, what's steps that you're passing to new Zot(steps)? I'm confused about that. 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-40012) Unable to set concurrency for a stage
Title: Message Title
Patrick Wolf commented on JENKINS-40012
Re: Unable to set concurrency for a stage
milestone step doesn't create concurrency it aborts older runs when a newer run has already passed it. You would want to use the lock step from the "Lockable Resources Plugin". https://jenkins.io/blog/2016/10/16/stage-lock-milestone/
pipeline {
agent any
stages {
stage("Foo") {
steps {
lock("myresource") {
echo "foo"
}
}
}
}
}
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-10912) Browser/JS memory leak in dashboard
Title: Message Title Daniel Beck commented on JENKINS-10912 Re: Browser/JS memory leak in dashboard Labels: 2.19.4-fixed It's not rocket science 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-39571) Jenkins doesn't start after plugin update
Title: Message Title Daniel Beck commented on JENKINS-39571 Re: Jenkins doesn't start after plugin update M U Let me present the other side of this: We're already dealing with way more reported issues than we can handle. Issues that aren't actually actionable, or are incomplete, just end up wasting time we could spend more productively elsewhere. For example, I've spent probably several weeks of full time work over 3 years trying to track down issues that were fixed and released by the time a bug was filed against an older version of Jenkins. Therefore we added, in bold red letters, with red border, below the 'Summary' field when creating a new issue: Please read our JIRA guidelines before creating an issue. The first sentence, a "notice" on the linked wiki page, on yellow "note" background, with "warning" symbol next to it: The Jenkins JIRA is not a support site. If you need assistance or have general questions, visit us in chat, or email one of the mailing lists. This is followed by quite detailed instructions what to do before filing a bug, and what information to provide. So don't be surprised then if issues that look like requests for help, and don't provide crucial information, receive negative responses. And to clarify – it's not like we're not reading IRC or the mailing lists either and just want you to go away; the three people responding to you here are among the most active users there! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39571) Jenkins doesn't start after plugin update
Title: Message Title Daniel Beck commented on JENKINS-39571 Re: Jenkins doesn't start after plugin update Oleg Nenashev I +1 Jesse. Our JIRA never was a support site and never will be. There is no bug here. I've closed hundreds of "How do I" and "How to fix" issues over the years as Not a Defect – is has nothing to do with stats, but this just pollutes our issue tracker and makes the actual issues more difficult to find. 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-39720) Highlight form fields that have been modified
Title: Message Title Daniel Beck commented on JENKINS-39720 Re: Highlight form fields that have been modified As the user (or indeed _javascript_) modifies the form fields, e.g. a doFillXYZItems AJAX call repopulates a drop down with a list that does not contain the current selection (which will change the selection to the first in the list) then those fields and selects will get a CSS style attached (or some other mechanism but CSS seems most flexible) so that they can be rendered as "dirty" or "modified" All pristine AJAX form fields will be considered changed then. Seems like a bad idea. For a while my fix to JENKINS-21720 had this problem until Antonio Muñiz fixed 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-12121) Coverity plugin should support interactive configuration of analysis and checkers
Title: Message Title Shami Willms closed an issue as Won't Fix I think there is room for UI improvements...but I don't find this bug very actionable and I think we need to rethink the configuration as a whole...not just the 'analysis and checker' options on their own. Jenkins / JENKINS-12121 Coverity plugin should support interactive configuration of analysis and checkers Change By: Shami Willms Status: Open Closed Resolution: Won't Fix 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
[JIRA] (JENKINS-40380) AJAX callbacks generate 403s for expired sessions which can trigger an IPS
Title: Message Title Daniel Beck resolved as Duplicate Jenkins / JENKINS-40380 AJAX callbacks generate 403s for expired sessions which can trigger an IPS Change By: Daniel Beck Status: Open Resolved 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, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32710) Configure AD Authorization with Groovy
Title: Message Title Benjamin Goldman commented on JENKINS-32710 Re: Configure AD Authorization with Groovy John Mickey question: the documentation (read the code...) implies that both site and server can be blank and optional. thoughts on how we can reconcile this? 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-40421) Too many levels of symbolic links/Archiving artifact stuck
Title: Message Title Daniel Beck commented on JENKINS-40421 Re: Too many levels of symbolic links/Archiving artifact stuck Weirdly enough the archiving code is supposed to detect cycles and abort. I think there are other issues related to this. 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-40419) Jenkins authentication failes with "cannot be cast to hudson.model.UserProperty"
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-40419 Jenkins authentication failes with "cannot be cast to hudson.model.UserProperty" Change By: Daniel Beck Component/s: ci-game-plugin Component/s: core 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-40663) strings cut-n-pasted from Description should not contain NUL or VT
Title: Message Title Daniel Beck resolved as Duplicate Jenkins / JENKINS-40663 strings cut-n-pasted from Description should not contain NUL or VT Change By: Daniel Beck Status: Open Resolved 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, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40622) Add the ability to fold/unfold similar actions in build menu
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-40622 Add the ability to fold/unfold similar actions in build menu Change By: Daniel Beck Component/s: core 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-40622) Add the ability to fold/unfold similar actions in build menu
Title: Message Title Daniel Beck commented on JENKINS-40622 Re: Add the ability to fold/unfold similar actions in build menu Just needs a fix in Git to not dump new actions for every SCM call. 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-40449) Parameters from properties files and current build parameters do not work together
Title: Message Title Daniel Beck commented on JENKINS-40449 Re: Parameters from properties files and current build parameters do not work together need be defined in downstream job before to use it. If it is the way works, Then this is ok. SECURITY-170 in https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11 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-40449) Parameters from properties files and current build parameters do not work together
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-40449 Parameters from properties files and current build parameters do not work together Change By: Daniel Beck Component/s: parameterized-trigger-plugin Component/s: core 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-39575) Uninstalling plugin removes a dependency used by another installed plugin
Title: Message Title Daniel Beck resolved as Cannot Reproduce No response by reporter in 1+ month. Jenkins / JENKINS-39575 Uninstalling plugin removes a dependency used by another installed plugin Change By: Daniel Beck Status: Open 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 options, visit
[JIRA] (JENKINS-38761) Unable to see Jenkins installed plugins
Title: Message Title Daniel Beck resolved as Not A Defect This is an issue tracker, not a support site. Jenkins / JENKINS-38761 Unable to see Jenkins installed plugins Change By: Daniel Beck Status: Open Resolved Resolution: Not A Defect 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-33894) Overlapping of text while installing plugins
Title: Message Title Daniel Beck resolved as Cannot Reproduce This has been resolved a while ago. Jenkins / JENKINS-33894 Overlapping of text while installing plugins Change By: Daniel Beck Status: Open 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 options, visit
[JIRA] (JENKINS-9337) Would be very useful if plugin manager showed use-count for installed plugins
Title: Message Title Daniel Beck resolved as Fixed https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Usage+Plugin+%28Community%29 (Not going to be a core feature) Jenkins / JENKINS-9337 Would be very useful if plugin manager showed use-count for installed plugins Change By: Daniel Beck Status: Open 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
[JIRA] (JENKINS-13684) Highlight incompatible installed plugins
Title: Message Title Daniel Beck resolved as Cannot Reproduce For a while now Jenkins shows error messages as administrative warnings because it refuses to load plugins requiring a newer version of Jenkins. Jenkins / JENKINS-13684 Highlight incompatible installed plugins Change By: Daniel Beck Status: Open 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
[JIRA] (JENKINS-40663) strings cut-n-pasted from Description should not contain NUL or VT
Title: Message Title Mark Hudson created an issue Jenkins / JENKINS-40663 strings cut-n-pasted from Description should not contain NUL or VT Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Dec/23 7:06 PM Priority: Minor Reporter: Mark Hudson It seems that Jenkins inserts a VerticalTAB character sequence in long lines in the Job description display in the Build History. Since a common workflow is to cut-and-paste a value from the Description into the input of another job, we had to installed a snippet of shell script to strip out those characters. The fix should either be that the Description doesn't get those invisible characters inserted, or that Job input parameters should strip the characters. $ echo -n "123456789-0" | od -ac 000 1 2 3 4 5 b nul vt 6 7 8 9 - 0 1 2 3 4 5 342 200 213 6 7 8 9 - 0 Add Comment
[JIRA] (JENKINS-39443) Sanitise description string as it may contains troublesome chars
Title: Message Title
Mark Hudson updated an issue
Jenkins / JENKINS-39443
Sanitise description string as it may contains troublesome chars
Change By:
Mark Hudson
jenkins swarm client can setup node description which is reported by Jenkins as unsafe.This is done with option -description which passes this as node name seen in Jenkins node list. One example is jenkins-swarm.jar -description "swarm_ip:127.0.0.1" , char --the {{ : }} colon char will cause Jenkins to rise error anytime when swarm node configuration is being saved (this leads to no save action). There may be other outcomes with non valid node descriptions.
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-40662) Deep-linking to Run Details screen with no tab specified causes problem when closing modal
Title: Message Title Cliff Meyers created an issue Jenkins / JENKINS-40662 Deep-linking to Run Details screen with no tab specified causes problem when closing modal Issue Type: Bug Assignee: Cliff Meyers Components: blueocean-plugin Created: 2016/Dec/23 6:48 PM Priority: Minor Reporter: Cliff Meyers Repro Steps: Deep link to a run details URL without specifying a tab, e.g. https://ci.blueocean.io/blue/organizations/jenkins/blueocean/detail/task%2FJENKINS-40256-integrate-new-form-controls/2 Close the modal Expected behavior: Activity tab displays recent runs Actual behavior: Header is displayed but there is no content beneath it Dev notes: This only happens when deeplinking to the general URL for the run without specifying a tab (e.g. /pipeline , /changes , etc). The UI issues a redirect to /pipeline but after closing the modal it doesn't update the URL correctly. We need to make the logic a bit more robust: May want to check history length when making determination on whether to go back or navigate to fallback URL May want to use history navigation rather than relying on the "opener URL" If possible, add a new API that simply "goes back" so that
[JIRA] (JENKINS-40601) Cannot create pipelineView with job-dsl 1.53
Title: Message Title Daniel Spilker commented on JENKINS-40601 Re: Cannot create pipelineView with job-dsl 1.53 You need to install the Build Pipeline plugin. The line above the stack trace in the log should something like this: Warning: (script, line 1) plugin 'build-pipeline-plugin' needs to be installed The next release will improve the output. 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-40601) Cannot create pipelineView with job-dsl 1.53
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40601 Re: Cannot create pipelineView with job-dsl 1.53 Code changed in jenkins User: Daniel Spilker Path: docs/Home.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/DslFactory.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/ViewFactory.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/JobParentSpec.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/PluginASTTransformationSpec.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/views/NestedViewSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/c2f0f09fb13b1bb6cc36c9a24841a573acb7daf6 Log: improved error message when a plugin is missing [FIXES JENKINS-40601] 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-40601) Cannot create pipelineView with job-dsl 1.53
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40601 Re: Cannot create pipelineView with job-dsl 1.53 Code changed in jenkins User: Daniel Spilker Path: docs/Home.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/DslFactory.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/ViewFactory.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/JobParentSpec.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/PluginASTTransformationSpec.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/views/NestedViewSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/86131780161cd884fcd762f9fdcec45ce4eef060 Log: Merge pull request #974 from daspilker/JENKINS-40601 JENKINS-40601 improved error message when a plugin is missing Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/b5a7a3e5f64c...86131780161c 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-40601) Cannot create pipelineView with job-dsl 1.53
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-40601 Cannot create pipelineView with job-dsl 1.53 Change By: SCM/JIRA link daemon Status: Open 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-21244) Un-escaped $ in module file name passed in command line to weblogic.jar results in the input file not found deployer
Title: Message Title Raphael CHAUMIER updated an issue Jenkins / JENKINS-21244 Un-escaped $ in module file name passed in command line to weblogic.jar results in the input file not found deployer Change By: Raphael CHAUMIER Labels: weblogic- deployer_plugin_4 deployer-plugin-3 . 0 7 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-40641) weblogic deployer plugin does not work in Windows OS
Title: Message Title Raphael CHAUMIER updated an issue Jenkins / JENKINS-40641 weblogic deployer plugin does not work in Windows OS Change By: Raphael CHAUMIER Labels: weblogic-deployer-plugin-3. 6 7 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-40641) weblogic deployer plugin does not work in Windows OS
Title: Message Title Raphael CHAUMIER updated an issue Jenkins / JENKINS-40641 weblogic deployer plugin does not work in Windows OS Change By: Raphael CHAUMIER Labels: weblogic-deployer-plugin-3.6 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-30648) Disabling Emma Code Coverage plugin
Title: Message Title Simon Steinkrüger commented on JENKINS-30648 Re: Disabling Emma Code Coverage plugin Any Update on this? 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-30648) Disabling Emma Code Coverage plugin
Title: Message Title Simon Steinkrüger edited a comment on JENKINS-30648 Re: Disabling Emma Code Coverage plugin Any Update update on this? 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-40661) error when restoring worksapce archive
Title: Message Title Jason Ford created an issue Jenkins / JENKINS-40661 error when restoring worksapce archive Issue Type: Bug Assignee: Unassigned Components: clone-workspace-scm-plugin Created: 2016/Dec/23 5:08 PM Environment: Jenkins 2.37 clone-workspace-scm plugin .6 jre1.8.0_73 Labels: plugin Priority: Minor Reporter: Jason Ford Here is the errror java.io.IOException: central directory is empty, can't expand corrupt archive. 16:17:02 at org.apache.tools.zip.ZipFile.populateFromCentralDirectory(ZipFile.java:329). There are 2 jobs linked and I'm manually able to open each workspace zip file from each side. It started when the workspace grew to 4 GB. After further research it seems there was a java limitation for zip files that was resolved in 1.7.55 using ZIP64(tm) format extensions. Am I missing something? I'm not sure how to resolve this issue.
[JIRA] (JENKINS-14832) Cov-commit-defects CWD is not the workspace directory
Title: Message Title Joel Briggs closed an issue as Fixed Closing old bug (I think this has been resolved in a past release) Jenkins / JENKINS-14832 Cov-commit-defects CWD is not the workspace directory Change By: Joel Briggs Status: Open Closed 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
[JIRA] (JENKINS-37584) P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Title: Message Title Karl Wirth commented on JENKINS-37584 Re: P4 plugin : P4_CHANGELIST not available in workflow (pipeline) It's the summary page of the job. Usually 'Status' on the left hand side. However based on the output above I think the answer is 'yes' and it includes '3798904'. Can you please post your Jenkins server version, OS the build job and server are on and how you are triggering the build (for example Perforce trigger, polling, Swarm review) and I'll try and reproduce the problem when I return to the office after the holiday break (if it hasn't been solved by others in the meantime). 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-16901) Coverity plugin seems to prevent other build processes from running.
Title: Message Title Joel Briggs closed an issue as Won't Fix Closing old bug (I think this has been resolved in a past release) Jenkins / JENKINS-16901 Coverity plugin seems to prevent other build processes from running. Change By: Joel Briggs Status: Open Closed Resolution: Won't Fix 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
[JIRA] (JENKINS-14830) BZ 99064 - Intermediate directory is not deleted
Title: Message Title Joel Briggs assigned an issue to Ken Dang Jenkins / JENKINS-14830 BZ 99064 - Intermediate directory is not deleted Change By: Joel Briggs Summary: BZ 99064 - Intermediate directory is not deleted Assignee: Josh Vinson Ken Dang 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-40657) can create instances of utilities from a shared libraries
Title: Message Title Andrew Bayer commented on JENKINS-40657 Re: can create instances of utilities from a shared libraries Huh, the first error is interesting. There's definitely a parsing error going on there. I'll dig into it. The second error looks like a fairly straightforward one - if you throw implements Serializable on Zot, it should work, I think? 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-37584) P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Title: Message Title squalou jenkins commented on JENKINS-37584 Re: P4 plugin : P4_CHANGELIST not available in workflow (pipeline) I copy / pasted you snippet, still getting 'null'. Changed the sync'd path to be sure somehting was done, tried again, I have lots of output too... but still null . What do you mean by 'status page' ? P4 Task: reverting all pending and shelved revisions. ... p4 revert /data/jenkins/slave/workspace/testNewP4/... + ... rm [abandoned files] duration: (11ms) P4 Task: cleaning workspace to match have list. ... p4 reconcile -w -f /data/jenkins/slave/workspace/testNewP4/... + duration: (18ms) P4 Task: syncing files at change: 389 ... p4 sync /data/jenkins/slave/workspace/testNewP4/...@389 + duration: (147ms) P4 Task: saving built changes. Found last change 3769363 on syncID jenkins-NODE_NAME-testNewP4 ... p4 client -o jenkins-master-testNewP4 + ... p4 info + ... p4 changes //jenkins-master-testNewP4/...@3769363,389 + ... p4 user -o xx+ ... p4 describe -s 389 + ... p4 fixes -c389 + ... p4 changes -l -m1 @3799947 + ... p4 user -o xx+ ... p4 describe -s 3799947 + ... p4 fixes -c3799947 + ... p4 changes -l -m1 @3798904 + --%< snip snip --%<-- ... done [Pipeline] echo null [Pipeline] } [Pipeline] // node Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34590) Fail to generate correct input step with choice param syntax from snippet generator
Title: Message Title Gael Stehagen commented on JENKINS-34590 Re: Fail to generate correct input step with choice param syntax from snippet generator In case people are coming here as I did. I resolved it with using default snippet from current generator, but instead of the created array, I used the string option with inline line breaks. Otherwise I had to get the 'new ChoiceParameterDefinition(...)' method whitelisted. So I ended up with: ... choice(choices: "option1\noption2\noption3\n", description: 'delimiters within string', name: 'my param'), 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-37584) P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Title: Message Title
Karl Wirth commented on JENKINS-37584
Re: P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
This is the example that works for me on Jenkins 2.19.4 in a 'pipeline' job:
node {
stage 'Stage 1'
echo 'Hello World 1'
p4sync charset: 'none',
credential: 'localhost',
depotPath: '//depot/pipelinetrig',
populate:
[
$class: 'AutoCleanImpl',
delete: true,
modtime: false,
parallel:
[
enable: false,
minbytes: '1024',
minfiles: '1',
path: '/usr/local/bin/p4',
threads: '4'
],
pin: '',
quiet: false,
replace: true
]
println env.P4_CHANGELIST
}
This returns:
...cut...
P4 Task: saving built changes.
Found last change 715 on syncID jenkins-NODE_NAME-Localhost-Pipeline-Triggered
... p4 client -o jenkins-master-Localhost-Pipeline-Triggered +
... p4 info +
... p4 changes //jenkins-master-Localhost-Pipeline-Triggered/...@715,716 +
... p4 changes -l -m1 @716 +
... p4 user -o super +
... p4 describe -s 716 +
... p4 fixes -c716 +
... done
[Pipeline] echo
716
Note that my output had a lot more information. Was there a built changelist reported on the status page?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38268) Parallel step and closure scope
Title: Message Title Joe George commented on JENKINS-38268 Re: Parallel step and closure scope We experience this too, it's quite annoying and hard to work around. 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-37584) P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Title: Message Title squalou jenkins reopened an issue Jenkins / JENKINS-37584 P4 plugin : P4_CHANGELIST not available in workflow (pipeline) Change By: squalou jenkins Resolution: Fixed Status: Closed Reopened 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-23767) Unexpected termination of the channel Caused by: java.io.EOFException
Title: Message Title Ruslan Khamidullin commented on JENKINS-23767 Re: Unexpected termination of the channel Caused by: java.io.EOFException What about fix? 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-37584) P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Title: Message Title
squalou jenkins edited a comment on JENKINS-37584
Re: P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Does this really work for anyone ?Personally with p4 plugin v1.4.12 I get a 'null' when trying this :{code} stage ('sync'){ node ('myNode'){def p4ws='myMaster-${JOB_NAME}'def p4vmap='//depot/'+BRANCH+'/.ci/jenkins/... //'+p4ws+'/...' def populateClassName = 'ForceCleanImpl' checkout([$class: 'PerforceScm', credential: 'PERFORCE-READONLY', populate: [$class: populateClassName, have: true, quiet: true], workspace: [ $class: 'ManualWorkspaceImpl', name: p4ws, spec: [view: p4vmap, allwrite: false] ] ]) println env.P4_CHANGELIST } }{code}{noformat}P4 Task: saving built changes p4 client -o ci-mx-test-p4web-testNewP4 +... p4 info +... done[Pipeline] echonull{noformat}
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-37584) P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Title: Message Title
squalou jenkins commented on JENKINS-37584
Re: P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Does this really work for anyone ? Personally I get a 'null' when trying this :
stage ('sync'){
node ('myNode'){
def p4ws='myMaster-${JOB_NAME}'
def p4vmap='//depot/'+BRANCH+'/.ci/jenkins/... //'+p4ws+'/...'
def populateClassName = 'ForceCleanImpl'
checkout([$class: 'PerforceScm', credential: 'PERFORCE-READONLY',
populate: [$class: populateClassName, have: true, quiet: true],
workspace: [
$class: 'ManualWorkspaceImpl',
name: p4ws,
spec: [view: p4vmap, allwrite: false]
]
])
println env.P4_CHANGELIST
}
}
P4 Task: saving built changes.
... p4 client -o ci-mx-test-p4web-testNewP4 +
... p4 info +
... done
[Pipeline] echo
null
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
[JIRA] (JENKINS-40651) Kubernetes plugin 0.10 failing to start pipeline with message failed to mkdirs
Title: Message Title Jesse Redl commented on JENKINS-40651 Re: Kubernetes plugin 0.10 failing to start pipeline with message failed to mkdirs Thanks for following up. We're using the https://hub.docker.com/r/jenkinsci/jnlp-slave/ image for our podTemplate. Here is capture of the volumes we are mounting. All secrets exist and work correctly on version 0.9 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-40651) Kubernetes plugin 0.10 failing to start pipeline with message failed to mkdirs
Title: Message Title Jesse Redl updated an issue Jenkins / JENKINS-40651 Kubernetes plugin 0.10 failing to start pipeline with message failed to mkdirs Change By: Jesse Redl Attachment: volumes.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-25858) java.io.IOException: Unexpected termination of the channel
Title: Message Title Ruslan Khamidullin commented on JENKINS-25858 Re: java.io.IOException: Unexpected termination of the channel David Carlton but I'm getting the same with just *ssh-slaves-plugin*. 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-12122) Coverity plugin console output is not human friendly
Title: Message Title Joel Briggs closed an issue as Fixed This was fixed in a previous release Jenkins / JENKINS-12122 Coverity plugin console output is not human friendly Change By: Joel Briggs Status: Open Closed 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-12116) Coverity plugin uses rootUrl in AJAX requests, which may be different than specified host:port
Title: Message Title Joel Briggs closed an issue as Won't Fix Closing old bug Jenkins / JENKINS-12116 Coverity plugin uses rootUrl in AJAX requests, which may be different than specified host:port Change By: Joel Briggs Status: Open Closed Resolution: Won't Fix 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
[JIRA] (JENKINS-40555) Add a @Symbol for Custom Tools and populate environment
Title: Message Title Andrew Bayer commented on JENKINS-40555 Re: Add a @Symbol for Custom Tools and populate environment Yeah, nodejs is simpler - see https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/tasks/Maven.java#L487 for something that definitely works. 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-26525) When a job is selected from the Jenkins UI, a tag library exception is thrown and none of the job options are clickable
Title: Message Title karthik raju updated JENKINS-26525 Jenkins / JENKINS-26525 When a job is selected from the Jenkins UI, a tag library exception is thrown and none of the job options are clickable Change By: karthik raju Status: Resolved In 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-30529) Import failed when trying to import from another centos version jenkins
Title: Message Title John Zhang commented on JENKINS-30529 Re: Import failed when trying to import from another centos version jenkins To me, the problem is because of Maven. I tried to import a list of project. All the projects that have nothing to do with Maven were imported successfully. However, all the Maven projects failed. I tried to manually copy a Maven project from the jobs directory in the old Jenkins server to the new server, and manage to build it. During this process, I did a lot of Maven configuration, e.g. install maven-related Jenkins plugins, set the Maven in the global tools, etc. After all of these work, I can import the maven jobs now. Fantastic! 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-40660) Parallel Test Stage in Blue Ocean marks build as successful before completing
Title: Message Title Roni Frantchi created an issue Jenkins / JENKINS-40660 Parallel Test Stage in Blue Ocean marks build as successful before completing Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2016-12-23 at 14.47.40.png Components: blueocean-plugin Created: 2016/Dec/23 1:03 PM Labels: blueocean Priority: Critical Reporter: Roni Frantchi See screenshot below. My pipeline consists of three main stages really; 1. Checkout the code. 2. Build the app, deploy JARs to Artifactory. 3. Run all unit tests - a step that is executed using the Parallel Test Plugin to spread the load across several nodes and executors. In steps 1 and 2, the build state is "in progress", has a blue header. As soon as it starts step 3, and before completing it, it changes the build state to "Successful", even though, it is in fact still in progress. The header turns green, but the log, available "stop" action as well as the workflow below, shows that it is in fact, still in progress. Here's a scrubbed version of my `Jenkinsfile` too: Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml #!groovy
[JIRA] (JENKINS-40659) Add possibility to filter with start and end date
Title: Message Title Stefan Fattinger created an issue Jenkins / JENKINS-40659 Add possibility to filter with start and end date Issue Type: Improvement Assignee: Yoann Dubreuil Components: build-metrics-plugin Created: 2016/Dec/23 12:58 PM Priority: Major Reporter: Stefan Fattinger Currently it is only possible to filter for a specific range up until now. Because i want to evaluate the metrics between a date range, f.e. the statistic for a specific development iteration, it would be helpful to implement a start and end date. Otherwise i have to exactly run the plugin at the end of the iteration - if i am not available at this time, the metrics are not completely correct. Add Comment
[JIRA] (JENKINS-40654) Make plugin compatible with storage backends compatible with Amazon S3 (OpenStack Swift...)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40654 Re: Make plugin compatible with storage backends compatible with Amazon S3 (OpenStack Swift...) Code changed in jenkins User: Cyrille Le Clerc Path: README.md src/main/java/hudson/plugins/s3/ClientHelper.java src/main/java/hudson/plugins/s3/Entry.java http://jenkins-ci.org/commit/s3-plugin/2d1b795c62f8bc37ac02c69e4fb24bfc5b1092e6 Log: JENKINS-40654 @Jimilian’s recommendations Document `classpath://com/amazonaws/partitions/override/endpoints.json` and `hudson.plugins.s3.DEFAULT_AMAZON_S3_REGION` in README.md Use `@nonnull` and `@nullable` in helper methods (not in the whole ClientHelper class to not change too many things at once) Cleanup imports 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-40654) Make plugin compatible with storage backends compatible with Amazon S3 (OpenStack Swift...)
Title: Message Title
SCM/JIRA link daemon commented on JENKINS-40654
Re: Make plugin compatible with storage backends compatible with Amazon S3 (OpenStack Swift...)
Code changed in jenkins User: Cyrille Le Clerc Path: src/main/java/hudson/plugins/s3/ClientHelper.java src/main/java/hudson/plugins/s3/Entry.java src/main/java/hudson/plugins/s3/S3BucketPublisher.java http://jenkins-ci.org/commit/s3-plugin/ff7d34914fbd52a9e44ae7029194d0351c1671c8 Log: JENKINS-40654 Load the list of Amazon S3 regions from c.a.r.RegionMetadataProvider, stop relying on a static lists and constants.
Adapt the http proxy logic of the plugin to discover the S3 endpoint hostname with `com.amazonaws.regions.Region#getServiceEndpoint("s3")` instead of the hardcoded constant `s3.amazonaws.com`
Replace
`com.amazonaws.regions.Regions` by `com.amazonaws.regions.RegionUtils#getRegionsForService("s3")`
`com.amazonaws.services.s3.model.Region` by `com.amazonaws.regions.Region`
For the default region used in some places of the plugin, introduce the system property `hudson.plugins.s3.DEFAULT_AMAZON_S3_REGION` to override the default `us-east-1`. Note that it would be better to no longer rely on a default AWS Region and to ask the user to specify the desired AWS Region.
The list of AWS regions can be overridden specifying a file `classpath://com/amazonaws/partitions/override/endpoints.json` matching the format defined in https://github.com/aws/aws-sdk-java/blob/master/aws-java-sdk-core/src/main/resources/com/amazonaws/partitions/endpoints.json . A solution to add this file in the classpath of Jenkins is to use the `java` command line parameter `-Xbootclasspath/a:/path/to/boot/classpath/folder/` and to locate `com/amazonaws/partitions/override/endpoints.json` in `/path/to/boot/classpath/folder/`.
Add Comment
[JIRA] (JENKINS-40654) Make plugin compatible with storage backends compatible with Amazon S3 (OpenStack Swift...)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40654 Re: Make plugin compatible with storage backends compatible with Amazon S3 (OpenStack Swift...) Code changed in jenkins User: Akbashev Alexander Path: README.md src/main/java/hudson/plugins/s3/ClientHelper.java src/main/java/hudson/plugins/s3/Entry.java src/main/java/hudson/plugins/s3/S3BucketPublisher.java http://jenkins-ci.org/commit/s3-plugin/945f3315a246888482561d12406fa39b84f8a3f2 Log: Merge pull request #100 from cyrille-leclerc/master JENKINS-40654 Make plugin compatible with storage backends compatible with Amazon S3 (OpenStack Swift...) Compare: https://github.com/jenkinsci/s3-plugin/compare/92247d2d099b...945f3315a246 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-19145) Builds fail because of "slave went offline during the build"
Title: Message Title Ruslan Khamidullin commented on JENKINS-19145 Re: Builds fail because of "slave went offline during the build" So any progress on this? I'm getting exact the same problem with Mac Pro node connected via ssh. 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-40658) Same name for all tests
Title: Message Title Artyom Boyko updated an issue Jenkins / JENKINS-40658 Same name for all tests Change By: Artyom Boyko Attachment: Снимок экрана 2016-12-23 в 12.47.40.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-40658) Same name for all tests
Title: Message Title Artyom Boyko updated an issue Jenkins / JENKINS-40658 Same name for all tests Change By: Artyom Boyko My tests output results in the stdout like this:SauceOnDemandSessionID=d41d8cd98f00b204e9800998ecf8427e job-name=AU_DNA_PayPal_phoenixSauceOnDemandSessionID=c2f2e61a3e763a1ae3b1f9f12599 job-name=AU_DNA_PhoenixBut in the results table, my tests name all the same. In this example it's "AU_DNA_PayPal_phoenix". It's strange, because everything else is correct, even links to Sauce Labs. !Снимок экрана 2016-12-23 в 12.47.40.png|thumbnail! 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-40658) Same name for all tests
Title: Message Title Artyom Boyko created an issue Jenkins / JENKINS-40658 Same name for all tests Issue Type: Bug Assignee: Gavin Mogan Components: sauce-ondemand-plugin Created: 2016/Dec/23 10:47 AM Priority: Minor Reporter: Artyom Boyko My tests output results in the stdout like this: SauceOnDemandSessionID=d41d8cd98f00b204e9800998ecf8427e job-name=AU_DNA_PayPal_phoenix SauceOnDemandSessionID=c2f2e61a3e763a1ae3b1f9f12599 job-name=AU_DNA_Phoenix But in the results table, my tests name all the same. In this example it's "AU_DNA_PayPal_phoenix". It's strange, because everything else is correct, even links to Sauce Labs. Add Comment
[JIRA] (JENKINS-39615) Global Pipeline Libraries triggers the 'poll SCM' of jobs
Title: Message Title Julien Pivotto commented on JENKINS-39615 Re: Global Pipeline Libraries triggers the 'poll SCM' of jobs "(and yes, I know, polling is evil, whenever I can I have triggers configured on modern scm to push jobs, but sometimes it's just not possible, believe me you don't want to know all the why's)" It is not evil. We use polling without schedule (https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-Pushnotificationfromrepository) so it is more pushing than polling, and still have the problem. 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-39615) Global Pipeline Libraries triggers the 'poll SCM' of jobs
Title: Message Title Julien Pivotto edited a comment on JENKINS-39615 Re: Global Pipeline Libraries triggers the 'poll SCM' of jobs I even tried to add the hudson.plugins.git.extensions.impl.IgnoreNotifyCommit() extention without success.EDIT: confirmed that works it does not 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-39615) Global Pipeline Libraries triggers the 'poll SCM' of jobs
Title: Message Title Julien Pivotto edited a comment on JENKINS-39615 Re: Global Pipeline Libraries triggers the 'poll SCM' of jobs [~squalou] A workaround that might work: !wa.png|thumbnail!EDIT: confirmed that it does not 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-26379) Jenkins - ssh connection exception
Title: Message Title John Zhang commented on JENKINS-26379 Re: Jenkins - ssh connection exception I have the same error and I use IP instead of hostname, and then the problem disappeared. This should be 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-39504) PmdPluginTest might fail due to plugins installation order
Title: Message Title Evaristo Gutierrez updated JENKINS-39504 Test won't fail if installation order takes into account optional dependencies. Jenkins / JENKINS-39504 PmdPluginTest might fail due to plugins installation order Change By: Evaristo Gutierrez Status: In Review Closed Resolution: Won't Fix 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
[JIRA] (JENKINS-40657) can create instances of utilities from a shared libraries
Title: Message Title
Dominik Bartholdi created an issue
Jenkins / JENKINS-40657
can create instances of utilities from a shared libraries
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2016/Dec/23 10:06 AM
Priority:
Critical
Reporter:
Dominik Bartholdi
I have the following class in my shared library - as described at [1]:
package org.foo;
class Zot {
def steps
Zot(steps){
this.steps = steps
}
def echo(msg) {
steps.sh "echo ${msg}"
}
}
and use it like this in the pipeline:
@org.jenkinsci.plugins.workflow.libs.Library('yooture@zotonly')
import org.foo.Zot
pipeline {
agent any
stages {
stage ('prepare') {
steps {
script {
def z = new Zot(steps)
z.echo("hello")
}
}
}
}
}
it fails with this:
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url g...@bitbucket.org:yooture/yooture-jenkins-pipeline-libraries.git # timeout=10
Fetching upstream changes from g...@bitbucket.org:yooture/yooture-jenkins-pipeline-libraries.git
> git --version # timeout=10
> git fetch --tags --progress
[JIRA] (JENKINS-40656) Update maven-metadata.xml after upload
Title: Message Title Bogdan Suta created an issue Jenkins / JENKINS-40656 Update maven-metadata.xml after upload Issue Type: New Feature Assignee: Suresh Kumar Components: nexus-artifact-uploader-plugin Created: 2016/Dec/23 10:02 AM Priority: Minor Reporter: Bogdan Suta Right now the plugin does not update the maven-metadata.xml and such the version information of the uploaded artifacts is not available for use in other jobs. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-40653) CulpritsRecipientProvider does not work with pipeline
Title: Message Title Makson Lee commented on JENKINS-40653 Re: CulpritsRecipientProvider does not work with pipeline thanks. 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-40655) Fatal error when scanning a repository containing a large number of branches and pull requests
Title: Message Title Philippe MOSSIERE created an issue Jenkins / JENKINS-40655 Fatal error when scanning a repository containing a large number of branches and pull requests Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2016-12-23 at 10.32.02.png Components: github-branch-source-plugin Created: 2016/Dec/23 9:57 AM Environment: GitHub Branch Source Plugin 2.0.0-beta-1 Labels: jenkins plugin Priority: Blocker Reporter: Philippe MOSSIERE I use the last release of GitHub Branch Source Plugin 2.0.0-beta-1, who's catch perfectly specific events, many thank's for this release, but I encounter an error when I scan a large public repository , I get a Fatal error after scan 30 pull requests.
[JIRA] (JENKINS-37557) Permission denied when using repo plugin with ssh-agent plugin in pipeline jobs
Title: Message Title Andreas Naumann updated an issue Jenkins / JENKINS-37557 Permission denied when using repo plugin with ssh-agent plugin in pipeline jobs Change By: Andreas Naumann Priority: Minor Critical 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-37557) Permission denied when using repo plugin with ssh-agent plugin in pipeline jobs
Title: Message Title Andreas Naumann commented on JENKINS-37557 Re: Permission denied when using repo plugin with ssh-agent plugin in pipeline jobs Same here. Since using credentials is not possible, the SSH-Agent support is crucial. Without it, I cant use this plugin at all and need to checkout in the shell step.. needless to say this is not what Jenkins is about. Blocker for me! 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-40101) Different behavior between debian container using docker.inside
Title: Message Title Andras Kovi commented on JENKINS-40101 Re: Different behavior between debian container using docker.inside Interesting, this error manifests only with the 'wheezy' image. 'jessie' works fine. 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-40654) Make plugin compatible with storage backends compatible with Amazon S3 (OpenStack Swift...)
Title: Message Title Cyrille Le Clerc commented on JENKINS-40654 Re: Make plugin compatible with storage backends compatible with Amazon S3 (OpenStack Swift...) See https://github.com/jenkinsci/s3-plugin/pull/100 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-40654) Make plugin compatible with storage backends compatible with Amazon S3 (OpenStack Swift...)
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-40654
Make plugin compatible with storage backends compatible with Amazon S3 (OpenStack Swift...)
Change By:
Cyrille Le Clerc
Storage systems that are compatible with Amazon S3 (OpenStack Swift...) have to change the Amazon S3 endpoints configuration.To do this with the AWS SDK, you have to provide a file {{classpath://com/amazonaws/partitions/override/endpoints.json}} using the JSON format defined in [com/amazonaws/partitions/endpoints.json| https://github.com/aws/aws-sdk-java/blob/master/aws-java-sdk-core/src/main/resources/com/amazonaws/partitions/endpoints.json ]
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-40654) Make plugin compatible with storage backends compatible with Amazon S3 (OpenStack Swift...)
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-40654
Make plugin compatible with storage backends compatible with Amazon S3 (OpenStack Swift...)
Change By:
Cyrille Le Clerc
Storage systems that are compatible with Amazon S3 (OpenStack Swift...) have to change the Amazon S3 endpoints configuration.To do this with the AWS SDK, you have to provide a file {{classpath://com/amazonaws/partitions/override/endpoints.json}} using the JSON format defined in [com/amazonaws/partitions/endpoints.json|https://github.com/aws/aws-sdk-java/blob/master/aws-java-sdk-core/src/main/resources/com/amazonaws/partitions/endpoints.json ) ]
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-40654) Make plugin compatible with storage backends compatible with Amazon S3 (OpenStack Swift...)
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-40654 Make plugin compatible with storage backends compatible with Amazon S3 (OpenStack Swift...) Issue Type: Improvement Assignee: Alexander A Components: s3-plugin Created: 2016/Dec/23 9:11 AM Priority: Minor Reporter: Cyrille Le Clerc Storage systems that are compatible with Amazon S3 (OpenStack Swift...) have to change the Amazon S3 endpoints configuration. To do this with the AWS SDK, you have to provide a file classpath://com/amazonaws/partitions/override/endpoints.json using the JSON format defined in [com/amazonaws/partitions/endpoints.json|https://github.com/aws/aws-sdk-java/blob/master/aws-java-sdk-core/src/main/resources/com/amazonaws/partitions/endpoints.json) Add Comment
[JIRA] (JENKINS-40508) Performance Plugin: Bugs in SimpleBuildStep performanceReport and View
Title: Message Title Hendrik Brinkmann updated an issue Jenkins / JENKINS-40508 Performance Plugin: Bugs in SimpleBuildStep performanceReport and View Change By: Hendrik Brinkmann Summary: Performance Plugin: Bugs in SimpleBuildStep performanceReport and View 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-38110) Library section within declarative syntax to explicitly load shared libraries
Title: Message Title Dominik Bartholdi commented on JENKINS-38110 Re: Library section within declarative syntax to explicitly load shared libraries Peter Leibiger see JENKINS-40642 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-40555) Add a @Symbol for Custom Tools and populate environment
Title: Message Title Dominik Bartholdi commented on JENKINS-40555 Re: Add a @Symbol for Custom Tools and populate environment Andrew Bayer not sure I understand - you mean nodejs (JENKINS-40624) is simpler? any pointers? 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-850) search box should match non-casesensitively
Title: Message Title Andrea Gerster assigned an issue to dogfood Jenkins / JENKINS-850 search box should match non-casesensitively Change By: Andrea Gerster Assignee: Andrea Gerster dogfood 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-850) search box should match non-casesensitively
Title: Message Title Andrea Gerster updated an issue Jenkins / JENKINS-850 search box should match non-casesensitively Change By: Andrea Gerster Comment: As an everyday Jenkins user in a quite big company, I never came across any use-case where one would want to use the Jenkins search case-sensitively. We are all used to google-like searchfields that show results with even the slightest equality to the typed string.So I propose to radically remove the 'case insensitive' user setting and instead always let Jenkins search case insensitively as the nowadays user would expect it 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-40653) CulpritsRecipientProvider does not work with pipeline
Title: Message Title David van Laatum closed an issue as Fixed ver 2.53 released will show up in updates in the next few hours or you can download from https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/email-ext/2.53/email-ext-2.53.hpi and install manually Jenkins / JENKINS-40653 CulpritsRecipientProvider does not work with pipeline Change By: David van Laatum Status: Open Closed 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
[JIRA] (JENKINS-40651) Kubernetes plugin 0.10 failing to start pipeline with message failed to mkdirs
Title: Message Title Carlos Sanchez commented on JENKINS-40651 Re: Kubernetes plugin 0.10 failing to start pipeline with message failed to mkdirs what jnlp slave are you using ? are you mountin volumes in there ? seems it doesn't have permissions 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.
