[JIRA] (JENKINS-35314) p4 Plugin does not trigger Pipeline builds
Title: Message Title Kevin Sim commented on JENKINS-35314 Re: p4 Plugin does not trigger Pipeline builds Hi Kyle Mott, Paul Allen, May I ask if Pipeline plugin 2.x versions are compatible with this new trigger feature in p4-plugin? I couldn't get it running on my setup 1. Pipeline 2.x 2. p4-plugin 1.4.1 But if it working if I were to use 1.6 pipeline as specified in https://github.com/jenkinsci/p4-plugin/blob/master/pom.xml 1. Pipeline 1.6 2. p4-plugin 1.4.1 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-36221) Add workflow support for pyenv-plugin
Title: Message Title
Matt Traynham created an issue
Jenkins / JENKINS-36221
Add workflow support for pyenv-plugin
Issue Type:
Improvement
Assignee:
Unassigned
Components:
pyenv-plugin
Created:
2016/Jun/25 2:29 AM
Environment:
Jenkins 2.10/Ubuntu 16
Labels:
plugin workflow
Priority:
Minor
Reporter:
Matt Traynham
It would be nice to have workflow support for the pyenv-plugin, maybe as a wrapper? A tool would be cool too... With the plugin installed currently, this can be somewhat achieved by simply hacking out the locations and using pyenv as is.
env.PYENV_VERSION = "2.7.11"
env.PYENV_ROOT = "${env.HOME}/.pyenv"
env.PATH = "${env.PYENV_ROOT}/shims:${env.PYENV_ROOT}/bin:${env.PATH}"
// -s flag will only download 2.7.11 if it doesn't exist already
sh "pyenv install -s ${env.PYENV_VERSION}; eval \"\$(pyenv init -)\"; pyenv shell ${env.PYENV_VERSION}"
There is a problem with this though. pyenv can run into concurrency issues while re-hashing. The plugin actually seems to have support for handling this with a file lock, but it would be a bit complicated to "redo" that functionality in a pipeline. I imagine it would be more beneficial just to expose this as a wrapper or installable version tools. Some references to the current semaphore locking system:
[JIRA] (JENKINS-27668) Add support for multiple git repositories in a single workspace
Title: Message Title James Sandlin commented on JENKINS-27668 Re: Add support for multiple git repositories in a single workspace Jacob Keller: Read comments above and read the documentation of the multi-scm plugin. It was written as a POC; it was not written for everyone to use and accept as "the best Jenkins has to offer". It is not a production ready plugin. We currently do use the muti-scm plugin and we have problems weekly due to the fact that "This plugin is more of a proof-of-concept than a robust and fully functional component. It does work in my particular build environment, and is meant to serve as a demonstration of what might be possible with more work." This is a limitation in Jenkins and anyone who accepts a POC plugin as a real solution needs to back up and think a bit. 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-29078) hudson.triggers.Trigger$Cron doRun throwing a NullPointerException
Title: Message Title gene lzr edited a comment on JENKINS-29078 Re: hudson.triggers.Trigger$Cron doRun throwing a NullPointerException Nevermind. Was looking at the wrong cron job . Ran the script provided by [~danielbeck] and it printed out the name of the right job that had a null trigger in config.xml.The configuration history plugin shows two changes yesterday, with 1 minute difference (see attachments).[^Untitled spreadsheet - Sheet1 (1).pdf] [^Untitled spreadsheet - Sheet2.pdf] The user says he was editing other jobs at that time but doesn't recall modifying this particular one. But even if he edited it by mistake, it's still not clear what caused Jenkins to save null triggers, as well as remove a bunch of other configuration options.Even if we can't reproduce this issue in full details, can you guys add a check for a null trigger? It's *REALLY* bad that one job with messed up configuration file causes the whole system to intermittently skip some scheduled jobs. The issue should be isolated to one 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-29078) hudson.triggers.Trigger$Cron doRun throwing a NullPointerException
Title: Message Title gene lzr commented on JENKINS-29078 Re: hudson.triggers.Trigger$Cron doRun throwing a NullPointerException Nevermind. Was looking at the wrong cron. Ran the script provided by Daniel Beck and it printed out the name of the right job that had a null trigger in config.xml. The configuration history plugin shows two changes yesterday, with 1 minute difference (see attachments). Untitled spreadsheet - Sheet1 (1).pdf Untitled spreadsheet - Sheet2.pdf The user says he was editing other jobs at that time but doesn't recall modifying this particular one. But even if he edited it by mistake, it's still not clear what caused Jenkins to save null triggers, as well as remove a bunch of other configuration options. Even if we can't reproduce this issue in full details, can you guys add a check for a null trigger? It's REALLY bad that one job with messed up configuration file causes the whole system to intermittently skip some scheduled jobs. The issue should be isolated to one 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-29078) hudson.triggers.Trigger$Cron doRun throwing a NullPointerException
Title: Message Title gene lzr updated an issue Jenkins / JENKINS-29078 hudson.triggers.Trigger$Cron doRun throwing a NullPointerException Change By: gene lzr Attachment: Untitled spreadsheet - Sheet2.pdf 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-29078) hudson.triggers.Trigger$Cron doRun throwing a NullPointerException
Title: Message Title gene lzr updated an issue Jenkins / JENKINS-29078 hudson.triggers.Trigger$Cron doRun throwing a NullPointerException Change By: gene lzr Attachment: Untitled spreadsheet - Sheet1 (1).pdf 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-29078) hudson.triggers.Trigger$Cron doRun throwing a NullPointerException
Title: Message Title gene lzr commented on JENKINS-29078 Re: hudson.triggers.Trigger$Cron doRun throwing a NullPointerException The issue happened again, this time the config history plugin is installed and it shows that the job haven't been modified since 2015. But the cron stopped running a couple of days ago (even though it should be running every minute). 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-36154) Multi-branch pipelines using branches with non-standard characters result in 404's against certain REST API endpoints
Title: Message Title Vivek Pandey started work on JENKINS-36154 Change By: Vivek Pandey 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-19949) logout doesn't work when using openid with google apps auth
Title: Message Title James Nord reopened an issue Jenkins / JENKINS-19949 logout doesn't work when using openid with google apps auth Change By: James Nord Resolution: Won't Fix Status: Resolved 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-19949) logout doesn't work when using openid with google apps auth
Title: Message Title James Nord commented on JENKINS-19949 Re: logout doesn't work when using openid with google apps auth Can this v-feature-v make it possible that someone logged into the company's Jenkins on a publicly available terminal and someone else can directly get into the Jenkins Well if you can get the Jenkins Cookie from that public terminal yes. But if you can do that - you can probably get the sign on information for the SSO provider anyway - so the fact you can't logout is not really a major concern. So on a public terminal iff the sso provider does not support single sign out you would need to logout of the SSO provider and *then* log out of Jenkins. (doing it the other way around would mean you would get logged back into jenkins as soon as you logged out). 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-19949) logout doesn't work when using openid with google apps auth
Title: Message Title James Nord commented on JENKINS-19949 Re: logout doesn't work when using openid with google apps auth Nahh... This is a bug - when the logout happens - I bet you are redirecting to the root of jenkins and anonymous does not have read access. This will kick the authentication in again (normally this would be a form, but for SSO its a redirect to a different server with some special information) which then redirects you back to Jenkins with the magic which means you are logged in... Jenkins maintains its own cookine and unless the SSO provider is also doing single sign out (not may are) then you need to delete the Jenkins cookie and sign out of SSO for a tru sign out. However it is usefull and desired at times to logout of just a single app and not the whole SSO. (this will not stop you signing back in - but the sign in should not be immediate as you logout). basically override getPostLogOutUrl() to redirect to a page that anonymous can read on Jenkins - or maybe even to the SSO providers global logout page (or be fancy and redirect to the Jenkins page that give the user an option to go to the SSO providers single signout page - should it support 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-16350) "logout" link doesn't work
Title: Message Title James Nord stopped work on JENKINS-16350 Change By: James Nord Status: In Progress Open 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-25260) Artifact and Artifact checksum deploy order required otherwise artifactory Error 404
Title: Message Title Will Saxon commented on JENKINS-25260 Re: Artifact and Artifact checksum deploy order required otherwise artifactory Error 404 We just ran into this today, investigating the Jenkins plugin 'Generic integration' vs. the 'AntIvy integration' since the latter is causing other problems with another tool we use. We used Ivy to publish to a local path in the workspace, then used the Generic integration to send everything under $(WORKSPACE)/localPath/** to Artifactory. This was failing with the 404 above. Since we know the file extensions for our artifacts are going to be .zip and .xml, we just changed the artifacts to be $(WORKSPACE)/localPath/*/.zip and $(WORKSPACE)/localPath/*/.xml instead. This bypasses the error at the expense of putting more configuration in Jenkins. 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-25260) Artifact and Artifact checksum deploy order required otherwise artifactory Error 404
Title: Message Title Will Saxon edited a comment on JENKINS-25260 Re: Artifact and Artifact checksum deploy order required otherwise artifactory Error 404 We just ran into this today, investigating the Jenkins plugin 'Generic integration' vs. the 'AntIvy integration' since the latter is causing other problems with another tool we use.We used Ivy to publish to a local path in the workspace, then used the Generic integration to send everything under $(WORKSPACE)/localPath/** to Artifactory. This was failing with the 404 above. Since we know the file extensions for our artifacts are going to be .zip and .xml, we just changed the artifacts to be $(WORKSPACE)/localPath/**/*.zip and $(WORKSPACE)/localPath/**/*.xml instead. This bypasses the error at the expense of putting more configuration in Jenkins. Also note this is still an issue with Jenkins 1.651.1, Artifactory 4.8.2 and the Artifactory plugin 2.4.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-16350) "logout" link doesn't work
Title: Message Title James Nord commented on JENKINS-16350 Re: "logout" link doesn't work The default behaviour of Jenkins is not to force a login. The default behaviour if you don't have permissions and are not logged and request a restricted page in is to redirect to the login page to *start a login*. By default this is the username/password form, but this can be changed by the Security Realm which is the case here. There are several things here that are important - note the "restricted page" on logout the realm is redirecting to the root of Jenkins which may well be a restricted page depending on your security setup. So there are 2 things that you can do. 1) change the login to take an intermediary form that requires the user to take action (ie a separate Login with GitHub button) 2) do not redirect to a page that requires authentication when you log out. I went for option 2 as in the normal use case it is one less button to click. 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-36120) Parameterized build parameters no longer available during promotion
Title: Message Title Patrick Conant commented on JENKINS-36120 Re: Parameterized build parameters no longer available during promotion FWIW, adding the hudson.model.ParametersAction.keepUndefinedParameters parameter (as documented in the Jenkins Security Advisory 2016-05-11) proved to be a suitable workaround for our scenarios. 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-16350) "logout" link doesn't work
Title: Message Title James Nord started work on JENKINS-16350 Change By: James Nord Status: Reopened 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-35723) Tabs on result summary are not visible on non-HDPI screens
Title: Message Title Cliff Meyers commented on JENKINS-35723 Re: Tabs on result summary are not visible on non-HDPI screens James Dumay I tested this on a Windows 8.1 machine, 24" 1920x1200 display from 2006 and could not repro, although that was after I had incorporated some fixes for JENKINS-36102. Can I resolve this for now or do you have any more details on how I can repro? 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-36102) Result header on Safari cuts off tabs
Title: Message Title Cliff Meyers commented on JENKINS-36102 Re: Result header on Safari cuts off tabs PR: https://github.com/jenkinsci/jenkins-design-language/pull/67 As far as I can tell the issue was not related to that, at least killing all of the DOM in the "content" pane has no effect. The fix ain't the prettiest thing but after fiddling for quite some time, it seems fair. 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-16350) "logout" link doesn't work
Title: Message Title James Nord reopened an issue This is a bug in the github-oauth plugin not Jenkins. Jenkins / JENKINS-16350 "logout" link doesn't work Change By: James Nord Resolution: Won't Fix Status: Resolved Reopened Assignee: Sam Gleske James Nord 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 Goo
[JIRA] (JENKINS-36220) BlueOcean should show failing builds on front page
Title: Message Title Spike Washburn updated an issue Jenkins / JENKINS-36220 BlueOcean should show failing builds on front page Change By: Spike Washburn Summary: BlueOcean should show failing builds onfront 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-36220) BlueOcean should show failing builds in main list view
Title: Message Title Spike Washburn updated an issue Jenkins / JENKINS-36220 BlueOcean should show failing builds in main list view Change By: Spike Washburn Summary: BlueOcean should show failing builds on front page in main list 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-36220) BlueOcean should show failing builds on
Title: Message Title Spike Washburn created an issue Jenkins / JENKINS-36220 BlueOcean should show failing builds on Issue Type: Improvement Assignee: James Dumay Attachments: Screen Shot 2016-06-24 at 2.40.56 PM.png, Screen Shot 2016-06-24 at 2.41.16 PM.png Components: blueocean-plugin Created: 2016/Jun/24 6:54 PM Labels: blueocean Priority: Minor Reporter: Spike Washburn If I look at the front page of Jenkins in BlueOcean, I can't see which pipelines are currently failing as easily as I could in Jenkins classic. Notice in the attached screenshots that is it clear that the Blue Ocean Docker Image pipeline is failing in the Jenkins classic UI, but it is much less obvious in the BlueOcean UI. The little cloud over the Sun isn't nearly as obvious as the giant red ball. Suggested improvement: make failing pipelines more obvious from the list view pages...especially for the "main" branch. Considerations: The Jenkins classic UI shows both the current build and the Weather – which in't necessarily the best approach either. Multi-branch builds make it hard to know the "current build" that is of interest vs those that are noise and should be ignored (from the high level glance).
[JIRA] (JENKINS-36160) Credentials defined in the folder should be available to the folder
Title: Message Title Jesse Glick commented on JENKINS-36160 Re: Credentials defined in the folder should be available to the folder Antonio Muñiz stephenconnolly did this fix the issue that the Add dropdown in, say, http://jenkins/job/some-multibranch/pipeline-syntax/ with, say, the git step selected, offered only Jenkins and not the (computed) folder itself? 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-34173) DescribableModel rejects PasswordParameterValue due to use of Secret
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-34173 DescribableModel rejects PasswordParameterValue due to use of Secret Currently there is no special binding for Secret. Probably it would be safe enough to create one, since there is already a SecretPickle that allows it to be serialized to program.dat encrypted, though there could be a window of vulnerability when the program is extracting the plaintext from something like an environment variable. Change By: Jesse Glick Summary: Pipeline snippet generator - build job with password parameter DescribableModel rejects PasswordParameterValue due to use of Secret Component/s: structs-plugin Component/s: workflow-plugin Labels: plugin workflow Add Comment
[JIRA] (JENKINS-31967) Specifying decimal numbers for JUnit health factor in Workflow snippets results in invalid code
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-31967 Specifying decimal numbers for JUnit health factor in Workflow snippets results in invalid code Change By: Jesse Glick Component/s: structs-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-32476) Code Snippet Generator for 'step' should use class FQDN in case of collisions
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32476 Code Snippet Generator for 'step' should use class FQDN in case of collisions Change By: Jesse Glick Component/s: structs-plugin Component/s: workflow-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-32159) Reference documentation generation fails for parallel step
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32159 Reference documentation generation fails for parallel step Change By: Jesse Glick Summary: Errors with DescribableHelper.Schema Reference documentation generation fails for parallel 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-32476) Code Snippet Generator for 'step' should use class FQDN in case of collisions
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32476 Code Snippet Generator for 'step' should use class FQDN in case of collisions Change By: Jesse Glick Labels: workflow 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-33217) DescribableHelper does not detect stray parameters
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-33217 DescribableHelper does not detect stray parameters Change By: Jesse Glick Component/s: structs-plugin Component/s: workflow-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-28510) DescribableHelper error with @DataBoundSetter on Map
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-28510 DescribableHelper error with @DataBoundSetter on Map Change By: Jesse Glick Component/s: structs-plugin Component/s: workflow-plugin Labels: plugin step workflow 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-35918) Structs plugin is delisted from UC. Default Jenkins 2 installation is failing
Title: Message Title Jesse Glick resolved as Fixed Jenkins / JENKINS-35918 Structs plugin is delisted from UC. Default Jenkins 2 installation is failing Change By: Jesse Glick 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-35709) Structs plugin dropped from update site?
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-35709 Structs plugin dropped from update site? Change By: Jesse Glick 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-36102) Result header on Safari cuts off tabs
Title: Message Title Cliff Meyers started work on JENKINS-36102 Change By: Cliff Meyers 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-35723) Tabs on result summary are not visible on non-HDPI screens
Title: Message Title Cliff Meyers started work on JENKINS-35723 Change By: Cliff Meyers 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-36128) Duration never live reloads for running pipelines
Title: Message Title Cliff Meyers resolved as Fixed Jenkins / JENKINS-36128 Duration never live reloads for running pipelines Change By: Cliff Meyers 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-36219) Changelogs not displayed for Mercurial branch projects
Title: Message Title Jesse Glick started work on JENKINS-36219 Change By: Jesse Glick 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-36154) Multi-branch pipelines using branches with non-standard characters result in 404's against certain REST API endpoints
Title: Message Title Cliff Meyers commented on JENKINS-36154 Re: Multi-branch pipelines using branches with non-standard characters result in 404's against certain REST API endpoints Yes, I think we should use the generated links wherever possible. It will eliminate this entire class of bug (at least in terms of REST integration; unfortunately we still need to do some encoding in the UI's URLs and routes as previously discussed). Hopefully relying on these links will make the UI less brittle if the API changes down the road. 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-36219) Changelogs not displayed for Mercurial branch projects
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-36219 Changelogs not displayed for Mercurial branch projects Issue Type: Bug Assignee: Jesse Glick Components: mercurial-plugin Created: 2016/Jun/24 5:53 PM Labels: multibranch Priority: Major Reporter: Jesse Glick If you create a multibranch Pipeline using the Mercurial source, you expect noninitial builds of the branch projects to display changelogs from those branches. But they do not. The root cause seems to have been that MercurialSCM.getKey was overly specific, preventing the baseline from being passed from one build to the next in changelog calculation. Whereas for RevisionType.BRANCH the branch name ought to be included in the key, when MercurialSCMSource.build constructs a one-off MercurialSCM binding the revision number, it is inappropriate for the key to include the revision. Git was unaffected since it completely ignores baselines (sigh). Subversion was unaffected since getKey was already implemented to strip revisions from the URLs. Add
[JIRA] (JENKINS-36166) Internal Server Error on creating new job from Jenkins API written in Node.js
Title: Message Title Mirko Friedenhagen assigned an issue to Unassigned Jenkins / JENKINS-36166 Internal Server Error on creating new job from Jenkins API written in Node.js Change By: Mirko Friedenhagen Assignee: Mirko Friedenhagen 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-35920) Build parameter not passed on for Maven Repository Artifact
Title: Message Title Christoph Linder commented on JENKINS-35920 Re: Build parameter not passed on for Maven Repository Artifact Affected plugin: Repository Connector Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Repository+Connector+Plugin) Steps to reproduce: Configure the plugin (i.e.: setup the maven repo) Create new job (freestyle) Select "This project is parameterized" Add "Maven Repository Artifact" and setup something suitable (i.E.: property "FOO", group "org.apache.commons", artifact "commons-lang3" Add Build Step -> Execute shell On a Linux-Jenkins: echo found: $FOO On a Windows-Jenkins: echo found: %FOO% Start the build with the parameter. Expected result: somewhere in the build log, the chosen parameter value shoud appear, e.g.: "found RELEASE" Actual result (value missing): "found" 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-30598) Support "Around" like "Before" and "After"
Title: Message Title Brian Cassidy commented on JENKINS-30598 Re: Support "Around" like "Before" and "After" For what it's worth, as of version 0.10.0, cucumber.js no longer supports around hooks – so I no longer see an issue! However, it appears other implementations (Ruby, for eg.) still support that hook. 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-36196) Organization folder and multi-branch projects should support folder-level credentials
Title: Message Title Antonio Muñiz closed an issue as Fixed Jenkins / JENKINS-36196 Organization folder and multi-branch projects should support folder-level credentials Change By: Antonio Muñiz 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-36066) Credentials visibility
Title: Message Title Antonio Muñiz closed an issue as Fixed Verified, JENKINS-36160 fixes this. Jenkins / JENKINS-36066 Credentials visibility Change By: Antonio Muñiz 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-34737) SCM polling is not being performed in multibranch pipeline with Mercurial SCM
Title: Message Title Jesse Glick resolved as Not A Defect Branch projects (the children) do not poll in isolation. Rather, the multibranch project (the parent folder) subsumes that function as part of branch indexing. If there are new heads on existing branches, new branch project builds will be triggered. You need merely check the box Periodically if not otherwise run in the folder configuration. Jenkins / JENKINS-34737 SCM polling is not being performed in multibranch pipeline with Mercurial SCM Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36166) Internal Server Error on creating new job from Jenkins API written in Node.js
Title: Message Title Mirko Friedenhagen commented on JENKINS-36166 Re: Internal Server Error on creating new job from Jenkins API written in Node.js Hello, what makes ypu think I could hell Herr, I know almost nothing about nodejs. 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-33024) XmlSlurper.parseText() not whitelisted
Title: Message Title Bob Hong commented on JENKINS-33024 Re: XmlSlurper.parseText() not whitelisted I have the same use case as Flavio. Can you recommend a sandbox friendly workaround to parse the groupId, artifactId, and version from my pom.xml that does not require approvals? 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-36154) Multi-branch pipelines using branches with non-standard characters result in 404's against certain REST API endpoints
Title: Message Title Vivek Pandey commented on JENKINS-36154 Re: Multi-branch pipelines using branches with non-standard characters result in 404's against certain REST API endpoints Michael Neale Either in UI code encodes the branch name, UI code does it now for multi branch project today. Or the self link is generated with right encoding and link is used to call them. I discussed this with Cliff Meyers and he likes this idea. Regardless, I need to fix the generated link anyways. 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-36218) Pubsub event enrichment @ExtensionPoint
Title: Message Title Tom FENNELLY created an issue Jenkins / JENKINS-36218 Pubsub event enrichment @ExtensionPoint Issue Type: Story Assignee: Tom FENNELLY Components: sse-gateway-plugin Created: 2016/Jun/24 4:22 PM Priority: Critical Reporter: Tom FENNELLY The default bare-bones thin events are sometimes not enough e.g. Blue Ocean needs some additional info about Job events, such as whether or not it's a muti-branch job, the Jenkins org the job belongs to etc. At the moment, Blue Ocean is fudging this by parsing the job url and making a few assumptions. This is dodgy and we should fix it before we go too far. Allowing BO to define an @Extension point impl that adds the few extra fields it needs would be good because then it would not longer need to make any assumptions. Add Comment
[JIRA] (JENKINS-36217) Must update IAM roles in the documetnation
Title: Message Title
Cesar Tron-Lozai created an issue
Jenkins / JENKINS-36217
Must update IAM roles in the documetnation
Issue Type:
Task
Assignee:
Jan Roehrich
Components:
amazon-ecs-plugin
Created:
2016/Jun/24 4:20 PM
Environment:
jenkins: 2.9, Amazon EC2 Container Service plugin: 1.3
Priority:
Major
Reporter:
Cesar Tron-Lozai
The privileges listed in the documentation are not enough to successfully start a task in the ECS cluster. The resources "arn:aws:ecs:::task-definition/jenkins-slave:*" must be added. For example: { "Version": "2012-10-17", "Statement": [ { "Sid": "Stmt1452746887373", "Action": [ "ecs:DescribeClusters", "ecs:RunTask", "ecs:StopTask" ], "Effect": "Allow", "Resource": [ "arn:aws:ecs:::cluster/", "arn:aws:ecs:::task-definition/jenkins-slave:*" ] } , { "Sid": "Stmt1452779658000", "Effect": "Allow", "Action": [ "ecs:RegisterTaskDefinition", "ecs:ListClusters" ], "Resource": [ "*" ] } ] }
Add Comment
[JIRA] (JENKINS-28121) Mercurial GeneralSCM step does not create intermediary directories.
Title: Message Title Jesse Glick started work on JENKINS-28121 Change By: Jesse Glick 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-28121) Mercurial GeneralSCM step does not create intermediary directories.
Title: Message Title Jesse Glick updated JENKINS-28121 Jenkins / JENKINS-28121 Mercurial GeneralSCM step does not create intermediary directories. Change By: Jesse Glick Status: Reopened Open 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-33142) Gearman plugin does not provide any slave when Jenkins is configured to use the Mesos plugin
Title: Message Title Davi Diorio Mendes commented on JENKINS-33142 Re: Gearman plugin does not provide any slave when Jenkins is configured to use the Mesos plugin I have the same problem, but I am using the docker plugin to provision slaves. If the are jobs at gearman queue when I trigger a job manually the jenkins with the slaves gets the jobs from gearman. After all slaves are down the jenkins gets no more jobs from gearman queue. 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-28121) Mercurial GeneralSCM step does not create intermediary directories.
Title: Message Title Jesse Glick reopened an issue I think I have it: you have to have an installation with caching enabled, and be cloning from a non-file-protocol source. Otherwise --rev is added, which implies --pull, which (for some reason) creates intermediate directories for you. Jenkins / JENKINS-28121 Mercurial GeneralSCM step does not create intermediary directories. Change By: Jesse Glick Resolution: Cannot Reproduce Status: Resolved 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 Grou
[JIRA] (JENKINS-33731) iam user is not authorized to perform: ecs:RegisterTaskDefinition on resource: *
Title: Message Title Cesar Tron-Lozai commented on JENKINS-33731 Re: iam user is not authorized to perform: ecs:RegisterTaskDefinition on resource: * I had the same issue. This is a mistake in the documentation. You should add the following resources in your AWS policy: "arn:aws:ecs:::task-definition/jenkins-slave:*" I found this by connecting to my instance and using aws ecs commands 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-36091) Add "request body" POST to Pipeline workflow to http-request
Title: Message Title Janario Oliveira closed an issue as Duplicate Jenkins / JENKINS-36091 Add "request body" POST to Pipeline workflow to http-request Change By: Janario Oliveira Status: Resolved Closed 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-36203) requestBody field is not available for Pipeline Step
Title: Message Title Janario Oliveira closed an issue as Fixed Jenkins / JENKINS-36203 requestBody field is not available for Pipeline Step Change By: Janario Oliveira Status: Resolved Closed 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-28121) Mercurial GeneralSCM step does not create intermediary directories.
Title: Message Title Jesse Glick commented on JENKINS-28121 Re: Mercurial GeneralSCM step does not create intermediary directories. Workaround would be simple: precede checkout with, say, writeFile file: '.junk', text: ''. But of course I would like to learn how to 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 https://groups.google.com/d/optout.
[JIRA] (JENKINS-27916) GString not flattened to String by DSL inside a map
Title: Message Title Frédéric Chuong commented on JENKINS-27916 Re: GString not flattened to String by DSL inside a map In Groovy, you have to escape symbols for map literals keys: [(requiredFile): 'xxx'] http://groovy-lang.org/groovy-dev-kit.html#_map_literals : Map keys are strings by default: [a:1] is equivalent to ['a':1]. This can be confusing if you define a variable named a and that you want the value of a to be the key in your map. If this is the case, then you must escape the key by adding parenthesis That means the workaround of using a GString as a key should not be needed 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-35920) Build parameter not passed on for Maven Repository Artifact
Title: Message Title Daniel Beck commented on JENKINS-35920 Re: Build parameter not passed on for Maven Repository Artifact What plugin is affected, and what does your job configuration look like? Could you provide complete steps to reproduce from scratch? 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-32481) git plugin does not retry when submodule update fails
Title: Message Title Jacob Keller commented on JENKINS-32481 Re: git plugin does not retry when submodule update fails Yea this didn't get pulled into 2.5 I believe. 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-27668) Add support for multiple git repositories in a single workspace
Title: Message Title Jacob Keller commented on JENKINS-27668 Re: Add support for multiple git repositories in a single workspace You can use Multiple SCM plugin for this. Just be sure that you order the repositories so that the "most root" subdirectory is cloned first, otherwise Git plugin will erase the files due to how git-clone requires an empty directory. 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-36216) Documentation for nested objects is unclear
Title: Message Title Daniel Spilker created an issue Jenkins / JENKINS-36216 Documentation for nested objects is unclear Issue Type: Bug Assignee: Jesse Glick Attachments: screenshot.png Components: workflow-plugin Created: 2016/Jun/24 3:07 PM Priority: Minor Reporter: Daniel Spilker Attributes for nested objects are shown on the same level as the containing attribute. See https://jenkins.io/doc/pipeline/steps/htmlpublisher/ or the attached screenshot. target is a nested object and all other options belong to the nested object, but all options are shown on the same level. The options are nested in the HTML structure, so it seems to be a CSS problem. Add Comment
[JIRA] (JENKINS-31993) Workflow Multibranch doesn't create workspace directory
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-31993
Workflow Multibranch doesn't create workspace directory
Change By:
Jesse Glick
A newly created multibranch workflow job doesn't create its " {{ workspace/$ \ {proj \ } " }} directory before trying to clone its repository to find the {{ Jenkinsfile }} to run. Using Mercurial, the job for the default branch tries to clone the repository to " {{ workspace/$ \ {proj \ }/default@script " }} and fails because the parent directory doesn't exist. Symptom:{ quote code:none } $ "C:\Program Files\TortoiseHg\hg.exe" --config auth.jenkins.prefix=* --config --config --config "auth.jenkins.schemes=http https" clone --noupdate C:\Jenkins\hgcache\AD53F80F6916C32F1510B2DC580E2777B26FE751-myjob-myuser "C:\Jenkins\workspace\myjob\default@script"abort: The system cannot find the path specified: 'C:\Jenkins\workspace\myjob\default@script'{ quote code }To reproduce:# Install Jenkins, Workflow Aggregator, Workflow Multibranch# Configure Hg in Jenkins global settings# Create a Multibranch Workflow job from an Hg repository
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-3481) Incorrect WebSVN path generation
Title: Message Title Thorsten Kohlhepp updated an issue Jenkins / JENKINS-3481 Incorrect WebSVN path generation Change By: Thorsten Kohlhepp Comment: Hi, we have updated the websvn2 to work with websvn 2.3.3 [^WebSVN2.jar]. Please review and update it on 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-3481) Incorrect WebSVN path generation
Title: Message Title Thorsten Kohlhepp updated an issue Jenkins / JENKINS-3481 Incorrect WebSVN path generation Change By: Thorsten Kohlhepp Attachment: WebSVN2.zip 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-3481) Incorrect WebSVN path generation
Title: Message Title Thorsten Kohlhepp commented on JENKINS-3481 Re: Incorrect WebSVN path generation the websvn2 plugin doesn't work with websvn 2.3.3 We have added a version which works Please can you check if it works and update the plugin. Thanks WebSVN2.zip 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-8213) links generated for WebSVN don't work with 2.3.1
Title: Message Title Thorsten Kohlhepp updated an issue Jenkins / JENKINS-8213 links generated for WebSVN don't work with 2.3.1 Change By: Thorsten Kohlhepp Attachment: WebSVN2.zip 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-36091) Add "request body" POST to Pipeline workflow to http-request
Title: Message Title Janario Oliveira resolved as Duplicate I've just approved a pull request on JENKINS-36203 I'm going to release it soon. Thanks, for the report Jenkins / JENKINS-36091 Add "request body" POST to Pipeline workflow to http-request Change By: Janario Oliveira 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.
[JIRA] (JENKINS-8213) links generated for WebSVN don't work with 2.3.1
Title: Message Title Thorsten Kohlhepp updated an issue Jenkins / JENKINS-8213 links generated for WebSVN don't work with 2.3.1 Change By: Thorsten Kohlhepp Comment: the websvn2 plugin doesn't work with websvn 2.3.3We have added a version which worksPlease can you check if it works and update the plugin. Thanks [^WebSVN2.zip] 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-8213) links generated for WebSVN don't work with 2.3.1
Title: Message Title Thorsten Kohlhepp commented on JENKINS-8213 Re: links generated for WebSVN don't work with 2.3.1 the websvn2 plugin doesn't work with websvn 2.3.3 We have added a version which works Please can you check if it works and update the plugin. Thanks WebSVN2.zip 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-8213) links generated for WebSVN don't work with 2.3.1
Title: Message Title Thorsten Kohlhepp commented on JENKINS-8213 Re: links generated for WebSVN don't work with 2.3.1 the websvn2 plugin doesn't work with websvn 2.3.3 We have added a version which works Please can you check if it works and update the plugin. Thanks [^WebSVN2.zip] 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-8213) links generated for WebSVN don't work with 2.3.1
Title: Message Title Thorsten Kohlhepp updated an issue Jenkins / JENKINS-8213 links generated for WebSVN don't work with 2.3.1 Change By: Thorsten Kohlhepp Comment: the websvn2 plugin doesn't work with websvn 2.3.3We have added a version which works [^WebSVN2.zip] Please can you check if it works and update the plugin. 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-27927) Some interface idioms do not work in Groovy CPS
Title: Message Title Frédéric Chuong commented on JENKINS-27927 Re: Some interface idioms do not work in Groovy CPS Upstream issue: https://github.com/cloudbees/groovy-cps/issues/26 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-36203) requestBody field is not available for Pipeline Step
Title: Message Title Janario Oliveira resolved as Fixed Thanks for the pull request. Jenkins / JENKINS-36203 requestBody field is not available for Pipeline Step Change By: Janario Oliveira 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-8213) links generated for WebSVN don't work with 2.3.1
Title: Message Title Thorsten Kohlhepp updated an issue Jenkins / JENKINS-8213 links generated for WebSVN don't work with 2.3.1 Change By: Thorsten Kohlhepp Comment: the websvn2 plugin doesn't work with websvn 2.3.3We have added a version which works [^WebSVN2.jar] Please can you check if it works and update the plugin. 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-8213) links generated for WebSVN don't work with 2.3.1
Title: Message Title Thorsten Kohlhepp commented on JENKINS-8213 Re: links generated for WebSVN don't work with 2.3.1 the websvn2 plugin doesn't work with websvn 2.3.3 We have added a version which works [^WebSVN2.zip] Please can you check if it works and update the plugin. 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-36203) requestBody field is not available for Pipeline Step
Title: Message Title Janario Oliveira started work on JENKINS-36203 Change By: Janario Oliveira 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-28121) Mercurial GeneralSCM step does not create intermediary directories.
Title: Message Title Jesse Glick resolved as Cannot Reproduce Working OK for me in Jenkins 1.651.3 with up-to-date Pipeline plugins and version 1.54 of the Mercurial plugin. Jenkins / JENKINS-28121 Mercurial GeneralSCM step does not create intermediary directories. Change By: Jesse Glick 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 jenkins
[JIRA] (JENKINS-36215) Weblogic Deployer plugin 3.3 issue
Title: Message Title
Bharath Natarajan updated an issue
Jenkins / JENKINS-36215
Weblogic Deployer plugin 3.3 issue
Change By:
Bharath Natarajan
We are trying to deploy a .war file into a weblogic server from Windows node using weblogic deployer plugin. Jenkins Master is on Linux while slave node 'CAO.EWDV.VZK' is on Windows. We are getting below error while trying to do this. Can someone help us in resolving this issue. Started by user Natarajan, Bharath[EnvInject] - Loading node environment variables.Building remotely on CAO.EWDV.VZK in workspace D:\OneJenkinsVZ\workspace\CAO.EWDV.Vzkauthoring.Vzk.Deploy_DEV[ CAO WeblogicDeploymentPlugin] - Pay attention of Jdk version {selected version is 1 . EWDV 8 . Vzkauthoring 0_25} compatibility with Weblogic Deployer API (see Oracle documentation) . Vzk [WeblogicDeploymentPlugin] - The JDK /usr/java/jdk1 . Deploy_DEV 8.0_25/jre will be used.[WeblogicDeploymentPlugin ] $ sh - xe C:\Users\tnsh\AppData\Local\Temp\3\hudson682326336128695604 Retrieving artifacts recorded [filtered resources on vzkauthoring . sh war]... The system cannot find [WeblogicDeploymentPlugin] - 2 files found under del[WeblogicDeploymentPlugin] - the file specified following resource ['vzknowledge.war'] doesn't match vzkauthoring.war FATAL [WeblogicDeploymentPlugin] - the following resource recorded /apps/opt/jenkinsnfs/internal-vd/jnmisc/del/vzkauthoring.war is eligible.[WeblogicDeploymentPlugin] - Deploying the artifact on the following target : command execution failed (name=DEV-DELETE-LATER-LINX) (host=ewdsacovn54.ebiz.verizon.com) (port=2001) [WeblogicDeploymentPlugin] - UNDEPLOYING ARTIFACT...$ /usr/ java /jdk1 . 8.0_25/jre/bin/java -Xms256M -Xmx256M -cp /apps/opt/jenkinsnfs/internal-vd/jnmisc/weblogic/wlfullclient.jar weblogic.Deployer -debug -remote -verbose -noexit -name vzkauthoring -targets WLS_Cluster -adminurl t3://ewdsacovn54.ebiz.verizon.com:2001 -userconfigfile /apps/opt/jenkinsnfs/internal-vd/jnmisc/temp/myuserconfigfile.secure -userkeyfile /apps/opt/jenkinsnfs/internal-vd/jnmisc/temp/myuserkeyfile.secure -undeployjava. io.IOException: Cannot run program " sh" (in directory "D:\OneJenkinsVZ\workspace\CAO /usr/java/jdk1 . EWDV 8 . Vzkauthoring.Vzk.Deploy_DEV 0_25/jre/bin/java " ) : CreateProcess error=2, The system cannot find the file specifiedat java.lang.ProcessBuilder.start(Unknown Source)at hudson.Proc$LocalProc.(Proc.java:244)at hudson.Proc$LocalProc.(Proc.java:216)at hudson.Launcher$LocalLauncher.launch(Launcher.java:815)at hudson.Launcher$ProcStarter.start(Launcher.java:381)at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1148)at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1113)at hudson.remoting.UserRequest.perform(UserRequest.java:120)at hudson.remoting.UserRequest.perform(UserRequest.java:48)at hudson.remoting.Request$2.run(Request.java:326)at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)at java.util.concurrent.FutureTask.run(Unknown Source)at java.util.concurrent.ThreadPoolExecu
[JIRA] (JENKINS-3481) Incorrect WebSVN path generation
Title: Message Title Thorsten Kohlhepp commented on JENKINS-3481 Re: Incorrect WebSVN path generation Hi, we have updated the websvn2 to work with websvn 2.3.3 WebSVN2.jar. Please review and update it on 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-3481) Incorrect WebSVN path generation
Title: Message Title Thorsten Kohlhepp updated an issue Jenkins / JENKINS-3481 Incorrect WebSVN path generation Change By: Thorsten Kohlhepp Attachment: WebSVN2.jar 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-8213) links generated for WebSVN don't work with 2.3.1
Title: Message Title Thorsten Kohlhepp commented on JENKINS-8213 Re: links generated for WebSVN don't work with 2.3.1 the websvn2 plugin doesn't work with websvn 2.3.3 We have added a version which works WebSVN2.jar Please can you check if it works and update the plugin. 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-8213) links generated for WebSVN don't work with 2.3.1
Title: Message Title Thorsten Kohlhepp updated an issue Jenkins / JENKINS-8213 links generated for WebSVN don't work with 2.3.1 Change By: Thorsten Kohlhepp Attachment: WebSVN2.jar 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-36215) Weblogic Deployer plugin 3.3 issue
Title: Message Title Bharath Natarajan created an issue Jenkins / JENKINS-36215 Weblogic Deployer plugin 3.3 issue Issue Type: Bug Assignee: Raphael CHAUMIER Components: weblogic-deployer-plugin Created: 2016/Jun/24 2:43 PM Environment: Jenkins 1.642.2, Weblogic Deployer Plug-in 3.3, GNU/Linux, Java1.8.0_25, Weblogic 10.3.4 Labels: plugin weblogic-deployer-plugin-3.3 Priority: Minor Reporter: Bharath Natarajan We are trying to deploy a .war file into a weblogic server from Windows node using weblogic deployer plugin. Jenkins Master is on Linux while slave node 'CAO.EWDV.VZK' is on Windows. We are getting below error while trying to do this. Can someone help us in resolving this issue. Started by user Natarajan, Bharath [EnvInject] - Loading node environment variables. Building remotely on CAO.EWDV.VZK in workspace D:\OneJenkinsVZ\workspace\CAO.EWDV.Vzkauthoring.Vzk.Deploy_DEV [CAO.EWDV.Vzkauthoring.Vzk.Deploy_DEV] $ sh -xe C:\Users\tnsh\AppData\Local\Temp\3\hudson682326336128695604.sh The system cannot find the file specified FATAL: command execution failed java.io.IOException: Cannot run program "sh" (in directory "D:\OneJenkinsVZ\workspace\CAO.EWDV.Vzkauthoring.Vzk.Deploy_DEV"): CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessBuilder.start(Unknown Source) at hudson.Proc$LocalProc.(Proc.java:244) at hudson.Proc$LocalProc.(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:815) at hudson.Launcher$ProcStarter.start(Launcher.java:381) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1148) at hudson.La
[JIRA] (JENKINS-36214) Image.run should use @tmp so .container is not kept around
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-36214 Image.run should use @tmp so .container is not kept around Issue Type: Bug Assignee: Jesse Glick Components: docker-workflow-plugin Created: 2016/Jun/24 1:54 PM Priority: Minor Reporter: Jesse Glick Image.run currently writes .container to the workspace and never deletes it. It could try to delete it in a finally block, but better would be to use pwd tmp: true to write it to the associated temporary directory. Add Comment
[JIRA] (JENKINS-36213) build-step - obtain environment variables from a non-pipeline job
Title: Message Title
Benjamin Herbert created an issue
Jenkins / JENKINS-36213
build-step - obtain environment variables from a non-pipeline job
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
2016/Jun/24 1:20 PM
Labels:
pipeline-build-step-plugin environment-variables
Priority:
Minor
Reporter:
Benjamin Herbert
One of my "Build Flow Plugin" jobs uses an environment variable FUU set by job1. It could be retrieved like: {{def b = build( "job1") def fuu = b.environment.get( "FUU" )}} Note, that job1 is a freestyle (non-pipeline) job. As Build Flow is deprecated, I am in the process to migrate this job to the pipeline plugin. I would expect that I can access the environment variables by using a snippet like {{def b = build 'job1' def b.buildVariables.FUU}} This does only return null in this case. It works correctly if job1 is a pipeline step, which I find counter intuitive.
Add Comment
[JIRA] (JENKINS-33443) Init script fails to create ~/.hudson-run-init on completion and runs multiple times
Title: Message Title Perrin Morrow commented on JENKINS-33443 Re: Init script fails to create ~/.hudson-run-init on completion and runs multiple times We've been seeing this behaviour too, but not consistently. Some of the time the file is created, and I can't see any obvious pattern. I am currently running a patched version of the plugin in our staging environment, with extra logging around the creation of the file to see why it might be failing. But so far it has created the file every time. It's possible my call to waitCompletion(sess); which I added to get the exit status may have caused it to work more reliably. I'll do some more testing next week. 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-17651) Allow more than 1 line as indicator
Title: Message Title Alokkumar Mahajan edited a comment on JENKINS-17651 Re: Allow more than 1 line as indicator Hello,Not sure if this is the same problem i am facing.I am trying to match an indicator (to get total and failed tests count) for below Test String:3 tests total, 1 passed, 2 failed::3 tests total, 3 passed, 0 failed::6 critical tests, 4 passed, 2 failed6 tests total, 4 passed, 2 failed==Output: C:\tests\Administration\output.xml***I am using regex as . \ *(\d+) tests total.*.*([1-9]\d*) failed.*.*\n=.*\nOutput:. \ * but its not working. Using . \ *(\d+) tests total.*.*([1-9]\d*) failed.* works but it returns the first occurrence which i don't want.Any comments please?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-17651) Allow more than 1 line as indicator
Title: Message Title Alokkumar Mahajan edited a comment on JENKINS-17651 Re: Allow more than 1 line as indicator Hello,Not sure if this is the same problem i am facing.I am trying to match an indicator (to get total and failed tests count) for below Test String:3 tests total, 1 passed, 2 failed::3 tests total, 3 passed, 0 failed::6 critical tests, 4 passed, 2 failed6 tests total, 4 passed, 2 failed==Output: C:\tests\Administration\output.xml***I am using regex as .*(\d+) tests total.*.*([1-9]\d*) failed.*.*\n=.*\nOutput:.* but its not working. Using .*(\d+) tests total.*.*([1-9]\d*) failed.* works but it returns the first occurrence which i don't want.Any comments please?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-17651) Allow more than 1 line as indicator
Title: Message Title Alokkumar Mahajan edited a comment on JENKINS-17651 Re: Allow more than 1 line as indicator Hello,Not sure if this is the same problem i am facing.I am trying to match an indicator (to get total and failed tests count) for below Test String:3 tests total, 1 passed, 2 failed::3 tests total, 3 passed, 0 failed::6 critical tests, 4 passed, 2 failed6 tests total, 4 passed, 2 failed==Output: C:\tests\Administration\output.xml***I am using regex as .*(\d+) tests total.*.*([1-9]\d*) failed.*.*\n=.*\nOutput: .* but its not working. Using .*(\d+) tests total.*.*([1-9]\d*) failed.* works but it returns the first occurrence which i don't want.Any comments please?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-36212) persisted configuration includes cache internals.
Title: Message Title
James Nord updated an issue
Jenkins / JENKINS-36212
persisted configuration includes cache internals.
Change By:
James Nord
When you configure the AD plugin (1.47 ) with a cache the main jenkins config contains the internals of the cache implementation and not the spcific cache configuration.The plugin should just persist the cache configuration (ttl/count) and recreate the caches on demand to prevent being tied to internal cache implementation/api changes.{code:xml|title=config.xml} internal.localbindusersomevaluesomeServer:3268RECURSIVEfalse 256 30 STRONGSTRONG3000256INSTANCE4INSTANCESTRONGSTRONG3000256INSTANCE4INSTANCE{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are
[JIRA] (JENKINS-36212) persisted configuration includes cache internals.
Title: Message Title James Nord created an issue Jenkins / JENKINS-36212 persisted configuration includes cache internals. Issue Type: Bug Assignee: Félix Belzunce Arcos Components: active-directory-plugin Created: 2016/Jun/24 11:45 AM Priority: Minor Reporter: James Nord When you configure the AD plugin with a cache the main jenkins config contains the internals of the cache implementation and not the spcific cache configuration. The plugin should just persist the cache configuration (ttl/count) and recreate the caches on demand to prevent being tied to internal cache implementation/api changes. config.xml "hudson.plugins.active_directory.ActiveDirectorySecurityRealm" plugin="active-directory@1.47"> internal.local binduser somevalue someServer:3268 RECURSIVE false 256 30 "com.google.common.cache.LocalCache$LocalManualCache" resolves-to="com.google.common.cache.LocalCache$ManualSerializationProxy"> STRONG STRONG "com.google.common.base.Equivalences$Equals"/> "com.google.common.base.Equivalences$Equals" reference="../keyEquivalence"/> 300 0 256 "com.google.common.cache.CacheBuilder$OneWeigher">INSTANCE 4 "com.google.common.cache.CacheBuilder$NullListener">INSTANCE "com.google.common.cache.LocalCache$LocalManualCache" resolves-to="com.google.common.cache.LocalCache$ManualSerializationProxy"> STRONG STRONG "com.google.common.base.Equivalences$Equals" reference="../../userCache/keyEquivalence"/> "com.google.common.base.Equivalences$
[JIRA] (JENKINS-34546) Access Denied missing Job/Create Permission on New Item within Folder
Title: Message Title Jesse Glick resolved as Won't Fix Harmless, and solved in Jenkins 2.0. Jenkins / JENKINS-34546 Access Denied missing Job/Create Permission on New Item within Folder Change By: Jesse Glick Status: Open Resolved 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 https://groups.google.c
[JIRA] (JENKINS-36196) Organization folder and multi-branch projects should support folder-level credentials
Title: Message Title Antonio Muñiz commented on JENKINS-36196 Re: Organization folder and multi-branch projects should support folder-level credentials Spike Washburn I think this duplicates JENKINS-36066 (which is probably collaterally fixed given JENKINS-36160 is fixed. Need to test 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-21627) Stack trace javax.servlet.ServletException: java.lang.IllegalStateException: Form too large 238293>200000
Title: Message Title pratik muluk commented on JENKINS-21627 Re: Stack trace javax.servlet.ServletException: java.lang.IllegalStateException: Form too large 238293>20 Thank You Daniel issue got resolved 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-36211) Karaoke mode: User should follow along with stages when watching a pipeline result execute
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-36211 Karaoke mode: User should follow along with stages when watching a pipeline result execute Change By: Michael Neale As stages progress (ie the list of nodes finish, and there is no more log to see) focus should shift to the next flow node (stage). In the case of a parallel branch, it can focus on the topmost branch until it is completed. In scope: * Step through of the experience of following a pipeline along with execution as shown by:https://docs.google.com/presentation/d/1jz_3mTH4rEldWlrHnm_04kHNtldItDhMXW2l3Ehqjio/edit#slide=id.g140c50d20d_0_0 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-35841) Developer can tail the log of an executing stage
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-35841 Developer can tail the log of an executing stage Change By: Michael Neale https://projects.invisionapp.com/share/WA699WS3J#/screens/138961660In scope* Clicking on an executing stage should display its tailing logs* When opened, the most recently executing stage logs should be displayed* Step through of the experience of following a pipeline along with execution as shown by:https://docs.google.com/presentation/d/1jz_3mTH4rEldWlrHnm_04kHNtldItDhMXW2l3Ehqjio/edit#slide=id.g140c50d20d_0_0* Tailing of a log for a while build (eg freestyle) that may not have steps/stagesOut of scope* Everything 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://group
[JIRA] (JENKINS-36211) Karaoke mode: User should follow along with stages when watching a pipeline result execute
Title: Message Title Michael Neale commented on JENKINS-36211 Re: Karaoke mode: User should follow along with stages when watching a pipeline result execute A plan C is that, like there is 3 second log polling for logs, it could check for a change in stage graph state, and move accordingly (Plan C that is, not ideal, but it could 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.
