[JIRA] (JENKINS-36121) Github Branch Source plugin trips api rate limit
Title: Message Title Dominic Scheirlinck edited a comment on JENKINS-36121 Re: Github Branch Source plugin trips api rate limit My hacky fix branch is at https://github.com/vend/github-branch-source-plugin/pull/1 - - it'll only work for PR builds for now . - Comments welcome.In this implementation, each PR event webhook triggers up to two builds (merged/unmerged), and takes about one Github API request to do so (I think, checking the collaborators for .isTrusted? Maybe 2-3). Pushes to a PR that is already open won't trigger a build, which is a shame (need to rewrite this logic into a pull event subscriber too). But editing the PR, or adding/removing a label should. 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-36121) Github Branch Source plugin trips api rate limit
Title: Message Title Dominic Scheirlinck edited a comment on JENKINS-36121 Re: Github Branch Source plugin trips api rate limit My hacky fix branch is at https://github.com/vend/github-branch-source-plugin/pull/1 -- it'll only work for PR builds for now.- Comments welcome.In this implementation, each PR event webhook triggers up to two builds (merged/unmerged), and takes about one Github API request to do so (I think, checking the collaborators for .isTrusted? Maybe 2-3). Pushes to a PR that is already open won't trigger a build, which is a shame (need to rewrite this logic into a pull event subscriber too). But editing the PR, or adding/removing a label should. 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-36121) Github Branch Source plugin trips api rate limit
Title: Message Title Dominic Scheirlinck edited a comment on JENKINS-36121 Re: Github Branch Source plugin trips api rate limit My hacky fix branch is at https://github.com/vend/github-branch-source-plugin/pull/1 - - it'll only work for PR builds for now. - Comments welcome.In this implementation, each PR event webhook triggers up to two builds (merged/unmerged), and takes about one Github API request to do so (I think, checking the collaborators for .isTrusted? Maybe 2-3). Pushes to a PR that is already open won't trigger a build, which is a shame (need to rewrite this logic into a pull event subscriber too). But editing the PR, or adding/removing a label should. 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-36121) Github Branch Source plugin trips api rate limit
Title: Message Title Dominic Scheirlinck edited a comment on JENKINS-36121 Re: Github Branch Source plugin trips api rate limit Had a quick go at a throwaway implementation of a fix. Mainly a hacky use of ParameterizedJobMixIn.scheduleBuild2 to schedule a new build for the branches specified in a push event. - However, I quickly ran into JENKINS-37920 - GBS's GitHubWebhookListenerImpl cannot receive the information it needs from github-plugin. (I notice github-plugin also correctly deals with the secret if one is configured, so if it weren't for the fact it's so hard to get the relevant information out, we could easily check for an authenticated webhook, parse the list of branches/PRs, and do the right thing) - In the meantime, I've had to completely disable webhooks.If you simply created a few dozen branches in the multibranch-demo repo, you'd be easily able to reproduce this issue after a few pushes. After all, the set up instructions say to "Add a new webhook, ask to Send me everything" - which is a configuration in which branch indexing will trigger several times as you just click around GitHub e.g. adding labels to PRs. 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-37607) Get user name from google?
Title: Message Title Muaaz Saleem commented on JENKINS-37607 Re: Get user name from google? I think you could use the user email to assign permissions, at least for matrix based security. For example "b...@company.com". 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-37748) Configuration no longer editable from the Config Page
Title: Message Title Muaaz Saleem closed an issue as Not A Defect The fields were right-aligned, had to scroll to see them. Jenkins / JENKINS-37748 Configuration no longer editable from the Config Page Change By: Muaaz Saleem Status: Open Closed 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
[JIRA] (JENKINS-37748) Configuration no longer editable from the Config Page
Title: Message Title Muaaz Saleem commented on JENKINS-37748 Re: Configuration no longer editable from the Config Page Indeed they were right aligned. 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-37914) Many Times JENKINS_HOME is Invalid
Title: Message Title
zhao wu commented on JENKINS-37914
Re: Many Times JENKINS_HOME is Invalid
thanks Mark Waite it's working node("master") { // Insert your steps here }
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-37702) Unbuilt pipelines show up as unknown if favourited
Title: Message Title James Dumay commented on JENKINS-37702 Re: Unbuilt pipelines show up as unknown if favourited Cliff Meyers mate thats perfect. Nice 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-37323) Ensure that Pipeline Graph can handle stage blocks
Title: Message Title James Dumay commented on JENKINS-37323 Re: Ensure that Pipeline Graph can handle stage blocks Vivek Pandey if you could attach some screenshots here with what Michael Neale was referring to that would be perfect. 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 Laurențiu Păncescu edited a comment on JENKINS-10912 Re: Browser/JS memory leak in dashboard I see a significant memory leak on [ci.centos.org|https://ci.centos.org] - it doesn't affect just the Dashboard. The memory usage for that tab increases to 1.7GB in Chrome and 1GB in Safari, over less than 3 hours (I also see this with Firefox on both OS X and Linux, although the memory increase seems less steep). I posted [details on the centos-devel mailing list|https://lists.centos.org/pipermail/centos-devel/2016-August/015122.html].The Chrome Developer Tools point to refreshPart from hudson-behavior.js as the culprit. Indeed, using 'delete node' from the Inspector to remove the #buildQueue and #executors divs stops the memory leak. I created a self-contained test to illustrate the problem, using just plain _javascript_, without any external libraries: [https://github.com/lpancescu/xhr-memory-leak].The least intrusive fix for Jenkins would be to remove the call to refreshPart from function f, and use setInterval instead of setTimer setTimeout (this is what noleak.html from my test repo does). The more elegant solution would be to use Ajax. PeriodicUpdater PeriodicalUpdater from Prototype.js, which is designed for this use case. If you tell me which variant you prefer, I can send you a pull request on GitHub. 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-10912) Browser/JS memory leak in dashboard
Title: Message Title Laurențiu Păncescu commented on JENKINS-10912 Re: Browser/JS memory leak in dashboard I implemented the 'elegant' way in my test repo (noleak-prototype.html) and tested for 6 hours. It doesn't leak memory, but I can't use it in a Jenkins context, since the server response includes the divs whose content should be replaced, and I'd still need to rebind the behaviors to the received DOM tree anyway. The 'minimal' fix is better in this case - please see pull request #2539. 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-35859) Create a static mini-site for JDL
Title: Message Title Michael Neale updated JENKINS-35859 nice work! http://jenkinsci.github.io/jenkins-design-language/docs Jenkins / JENKINS-35859 Create a static mini-site for JDL Change By: Michael Neale Status: In Review 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
[JIRA] (JENKINS-37954) Running job has incorrect stage selected before steps start executing
Title: Message Title Michael Neale commented on JENKINS-37954 Re: Running job has incorrect stage selected before steps start executing ideally the graph still showed, and yes, "tricking" it is fine (or even not selecting nodes). This was included as part of the design as it sets up expectation for the user of how much work the pipeline has to do (same as stage view does in classic) and is a much wanted feature, so that needs to be in there. 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-35859) Create a static mini-site for JDL
Title: Message Title Michael Neale started work on JENKINS-35859 Change By: Michael Neale 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-35859) Create a static mini-site for JDL
Title: Message Title Michael Neale updated JENKINS-35859 Jenkins / JENKINS-35859 Create a static mini-site for JDL Change By: Michael Neale Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35859) Create a static mini-site for JDL
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-35859 Create a static mini-site for JDL Change By: Michael Neale Sprint: 1.0-m1 , 1.0-beta-1 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-37832) Any API 401 should redirect to login page
Title: Message Title Ivan Meredith started work on JENKINS-37832 Change By: Ivan Meredith 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-37971) support the github plugin for exclusions
Title: Message Title Jae Gangemi created an issue Jenkins / JENKINS-37971 support the github plugin for exclusions Issue Type: New Feature Assignee: Joel Johnson Components: ez-templates-plugin Created: 2016/Sep/05 9:30 PM Priority: Minor Reporter: Jae Gangemi please add support for ignoring the github plugin "github@1.21.1"> url display even better would be to allow the projectUrl to be ignored but the displayName cloned (it can be used to set the name of the status set on a branch. Add Comment
[JIRA] (JENKINS-37970) allow exclusions to be configured for a template
Title: Message Title Jae Gangemi created an issue Jenkins / JENKINS-37970 allow exclusions to be configured for a template Issue Type: New Feature Assignee: Joel Johnson Components: ez-templates-plugin Created: 2016/Sep/05 9:26 PM Priority: Minor Reporter: Jae Gangemi it would be great to be able to configure the exclusions a child template should use from the parent itself. for example, right now i have to manually exclude the scm section for every project i create. Add Comment This message
[JIRA] (JENKINS-37956) Missing notification about request with bad secret for GitHub plugin
Title: Message Title Kirill Merkushev commented on JENKINS-37956 Re: Missing notification about request with bad secret for GitHub plugin Good point 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-37969) use of SSH slave connection instead of JNLP ?
Title: Message Title squalou jenkins created an issue Jenkins / JENKINS-37969 use of SSH slave connection instead of JNLP ? Issue Type: Improvement Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2016/Sep/05 7:40 PM Priority: Minor Reporter: squalou jenkins Hi, for practical reasons I won't disclose here, I'm not in position of using JNLP connections between my slaves and my masters. Would it be possible to use ssh connections ? (like docker plugin, which I've used so far) Add Comment
[JIRA] (JENKINS-25874) Maven Project plugin to use Credentials plugin
Title: Message Title Dominik Bartholdi resolved as Not A Defect Jenkins / JENKINS-25874 Maven Project plugin to use Credentials plugin Change By: Dominik Bartholdi 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-36678) Configuration File Provider fails when inside Folder named with Spaces
Title: Message Title Dominik Bartholdi resolved as Not A Defect Jenkins / JENKINS-36678 Configuration File Provider fails when inside Folder named with Spaces Change By: Dominik Bartholdi 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-33358) Groovy and PermGen memory leak
Title: Message Title
Craig Rodrigues commented on JENKINS-33358
Re: Groovy and PermGen memory leak
I am also encountering problems with my Jenkins system where the Jenkins process consumes so much memory that the operating system Out of Memory (OOM) killer kills the process. I'm making extensive use of Pipeline. My system is: {{ OS: FreeBSD (9.3-RELEASE-p43) Architecture: amd64 64bit Java Home: /usr/local/openjdk8/jre Java Version: 1.8.0_102 JVM: OpenJDK 64-Bit Server VM (25.102-b14, mixed mode) Java Vendor: Oracle Corporation Jenkins version 2.18 }} I grabbed a heapdump, which I have placed at: https://people.freebsd.org/~rodrigc/jenkins/heapdump/ How do I tell if groovy is the source of the memory leak?
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-36420) Allow to configure the client idle timeout.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36420 Re: Allow to configure the client idle timeout. Code changed in jenkins User: Oleg Nenashev Path: war/pom.xml http://jenkins-ci.org/commit/jenkins/d154604e7b92b49c86442f55b064dec94ba90a0b Log: Update to SSHD module 1.7 (#2534) Summary of changes: JENKINS-36420(https://issues.jenkins-ci.org/browse/JENKINS-36420) - Allow setting up the the client idle timeout Upgrade to the new parent POM FindBugs cleanup, in particular https://github.com/jenkinsci/sshd-module/commit/66162e707189e6bda5708cf856e71b6130160cc1 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-37954) Running job has incorrect stage selected before steps start executing
Title: Message Title Thorsten Scherler updated JENKINS-37954 Jenkins / JENKINS-37954 Running job has incorrect stage selected before steps start executing Change By: Thorsten Scherler 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-37954) Running job has incorrect stage selected before steps start executing
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37954 Re: Running job has incorrect stage selected before steps start executing Code changed in jenkins User: Thorsten Scherler Path: src/main/js/page_objects/blueocean/bluePipelineRunDetail.js src/test/js/queued.js http://jenkins-ci.org/commit/blueocean-acceptance-test/bf9a61d827674e1aeb9d56930941b94e96543931 Log: JENKINS-37954 better selector for the queued empty state 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-37968) schedule build on parametrised jobs randomly fails when the form is not loaded before timeout
Title: Message Title valentina armenise started work on JENKINS-37968 Change By: valentina armenise 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-37968) schedule build on parametrised jobs randomly fails when the form is not loaded before timeout
Title: Message Title valentina armenise assigned an issue to valentina armenise Jenkins / JENKINS-37968 schedule build on parametrised jobs randomly fails when the form is not loaded before timeout Change By: valentina armenise Assignee: Oliver Gondža valentina armenise 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-37954) Running job has incorrect stage selected before steps start executing
Title: Message Title Thorsten Scherler commented on JENKINS-37954 Re: Running job has incorrect stage selected before steps start executing James Dumay how important is that you see the steps? The steps are based on the last successful run of a pipeline. In theory we do not know the steps until we are processing them. Current solution is simply not showing the steps when the job is queued. I would need to look into "tricking" the pipelineGraph to show the first node selected, but IMO the suggested implementation is cleaner. but your 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-37954) Running job has incorrect stage selected before steps start executing
Title: Message Title Thorsten Scherler updated an issue Jenkins / JENKINS-37954 Running job has incorrect stage selected before steps start executing Change By: Thorsten Scherler Attachment: Screenshot from 2016-09-05 18-40-47.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-37968) schedule build on parametrised jobs randomly fails when the form is not loaded before timeout
Title: Message Title valentina armenise created an issue Jenkins / JENKINS-37968 schedule build on parametrised jobs randomly fails when the form is not loaded before timeout Issue Type: Bug Assignee: Oliver Gondža Components: acceptance-test-harness Created: 2016/Sep/05 4:24 PM Priority: Minor Reporter: valentina armenise Sometimes when executing `job.scheduleBuild()` on a parametrised job selenium test fails with org.openqa.selenium.NoSuchElementException: Unable to locate By.xpath: .//input[./@type = 'submit' or ./@type = 'reset' or ./@type = 'image' or ./@type = 'button'][((./@id = 'Build' or ./@name = 'Build' or contains(./@value, 'Build')) or contains(./@title, 'Build'))] | .//input[./@type = 'image'][contains(./@alt, 'Build')] | .//button[(((./@id = 'Build' or contains(./@value, 'Build')) or contains(normalize-space(.), 'Build')) or contains(./@title, 'Build'))] | .//input[./@type = 'image'][contains(./@alt, 'Build')] in http://172.17.0.1:55457/job/matrixJob/build?delay=0sec For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html Build info: version: '2.53.0', revision: '35ae25b1534ae328c771e0856c93e187490ca824', time: '2016-03-15 10:43:46' System info: host: 'ip-172-18-64-125', ip: '127.0.0.1', os.name: 'Linux', os.arch: 'amd64', os.version: '4.2.0-42-generic', java.version: '1.8.0_40' Driver info: driver.version: unknown at org.openqa.selenium.support.ui.FluentWait.timeoutException(FluentWait.java:292) at org.jenkinsci.test.acceptance.junit.Wait.timeoutException(Wait.java:143) at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:261) at org.jenkinsci.test.acceptance.junit.Wait.until(Wait.java:74) at org.jenkinsci.test.acceptance.po.CapybaraPortingLayerImpl.find(CapybaraPortingLayerImpl.java:197) at
[JIRA] (JENKINS-37926) Job configuration settings lost and Jenkins crashes if setting "This project is parameterized" is set with no parameter added.
Title: Message Title Panagiotis Galatsanos commented on JENKINS-37926 Re: Job configuration settings lost and Jenkins crashes if setting "This project is parameterized" is set with no parameter added. I just confirmed with a fresh build that issue is solved in latest master code with commit: 0b517705f5 on 15 Jul. PR: https://github.com/jenkinsci/jenkins/pull/2444 How can be checked if the commit is also included on the next LTS release in order to close this ticket? 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-37954) Running job has incorrect stage selected before steps start executing
Title: Message Title Thorsten Scherler started work on JENKINS-37954 Change By: Thorsten Scherler 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-31468) Allow the usage of parameters in Reconfigure VM
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-31468 Allow the usage of parameters in Reconfigure VM Change By: pjdarton Issue Type: Bug Improvement 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-31819) vSphere-cloud plugin 2.7 does not work with vSphere 6.0
Title: Message Title pjdarton commented on JENKINS-31819 Re: vSphere-cloud plugin 2.7 does not work with vSphere 6.0 FYI we're using plugin 2.13 with vSphere 6 and, whilst there are issues, it would not be correct to simply state that "it doesn't work". I would suggest that unless the scope of this issue can be narrowed down to something more specific, this issue should be 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-37967) dynamic choice parameter not compatible with folder + windows slave
Title: Message Title Raphaël UNIQUE updated an issue Jenkins / JENKINS-37967 dynamic choice parameter not compatible with folder + windows slave Change By: Raphaël UNIQUE Attachment: jenkins.log 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-37666) Proceeding step is sometimes erroneously expanded
Title: Message Title Thorsten Scherler updated JENKINS-37666 Jenkins / JENKINS-37666 Proceeding step is sometimes erroneously expanded Change By: Thorsten Scherler 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-27906) Fail to read NUnit3 output xml
Title: Message Title Tal Auslander commented on JENKINS-27906 Re: Fail to read NUnit3 output xml This also affects .NET Core testing, in which the output format cannot be changed to NUnit 2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36850) vSphere keeps info on Slave that has been shutdown / deleted
Title: Message Title pjdarton commented on JENKINS-36850 Re: vSphere keeps info on Slave that has been shutdown / deleted I've not got to the bottom of this one myself, but FYI what I see on my setup is that I'm told that there's 1 VM in the bucket, and that's regardless of the number of VMs I've got. I suspect that vSphere.java isn't asking the right question of the vSphere server. FYI the plugin doesn't "remember" the current list of slaves in the bucket - it just asks vSphere for a count of all the VMs (each time, every time) and also assumes that "they're all yours". That's why restarting Jenkins didn't change 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-37967) dynamic choice parameter not compatible with folder + windows slave
Title: Message Title Raphaël UNIQUE updated an issue Jenkins / JENKINS-37967 dynamic choice parameter not compatible with folder + windows slave Change By: Raphaël UNIQUE Attachment: Config.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-36878) vSphere plugin not respecting or saving per slave instance Cap
Title: Message Title pjdarton commented on JENKINS-36878 Re: vSphere plugin not respecting or saving per slave instance Cap I've been doing some digging and the issue goes much deeper than just the problems with the configuration. Even after fixing the configuration load/save issues so that the code knows what the instance cap should be, it still doesn't obey it. This is because it doesn't keep track of what slaves it has kicked off, and it doesn't seem to be able to count the number within vSphere, so each time Jenkins asks for more, it initiates the cloning of more slaves (until the slaves start coming online and providing the capacity that Jenkins is asking for, at which point Jenkins stops asking for more). I've got some a local build which fixes that, but it's a non-trivial change. 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-37967) dynamic choice parameter not compatible with folder + windows slave
Title: Message Title
Raphaël UNIQUE updated an issue
Jenkins / JENKINS-37967
dynamic choice parameter not compatible with folder + windows slave
Change By:
Raphaël UNIQUE
if i use a dynamic choice parameter in a job executed on a (remote) windows slave, it works. {code:java}List listDir = new ArrayList();new File(System.getenv("HOMEPATH")).eachDir() { dir -> listDir.add(dir.getName() )} return listDir.reverse() {code} but if this job is in a folder (https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Folders+Plugin ), it does not work (the paramter field is emptyin the jenkins log, i can see:{code:java}sept. 05, 2016 5:41:49 PM com.seitenbau.jenkins.plugins.dynamicparameter.BaseParameterDefinition executeScriptAVERTISSEMENT: No label is assigned to project; script for parameter '' will be executed on mastersept. 05, 2016 5:41:49 PM com.seitenbau.jenkins.plugins.dynamicparameter.util.JenkinsUtils executeGRAVE: Cannot access class pathgroovy.lang.GroovyRuntimeException: Ambiguous method overloading for method java.io.File#.Cannot resolve which method to invoke for [null] due to overlapping prototypes between:[class java.lang.String][class java.net.URI]at groovy.lang.MetaClassImpl.chooseMostSpecificParams(MetaClassImpl.java:3240)...sept. 05, 2016 5:41:49 PM com.seitenbau.jenkins.plugins.dynamicparameter.BaseParameterDefinition getScriptResultAsListINFOS: Script parameter with name '' is not a instance of java.util.List the parameter value is : null{code}
Add Comment
This message
[JIRA] (JENKINS-37967) dynamic choice parameter not compatible with folder + windows slave
Title: Message Title Raphaël UNIQUE created an issue Jenkins / JENKINS-37967 dynamic choice parameter not compatible with folder + windows slave Issue Type: Bug Assignee: Unassigned Components: dynamicparameter-plugin Created: 2016/Sep/05 3:44 PM Priority: Major Reporter: Raphaël UNIQUE if i use a dynamic choice parameter in a job executed on a (remote) windows slave, it works. but if this job is in a folder (https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Folders+Plugin ), it does not work (the paramter field is empty in the jenkins log, i can see: sept. 05, 2016 5:41:49 PM com.seitenbau.jenkins.plugins.dynamicparameter.BaseParameterDefinition executeScript AVERTISSEMENT: No label is assigned to project; script for parameter '' will be executed on master sept. 05, 2016 5:41:49 PM com.seitenbau.jenkins.plugins.dynamicparameter.util.JenkinsUtils execute GRAVE: Cannot access class path groovy.lang.GroovyRuntimeException: Ambiguous method overloading for method java.io.File#. Cannot resolve which method to invoke for [null] due to overlapping prototypes between: [class java.lang.String] [class java.net.URI] at groovy.lang.MetaClassImpl.chooseMostSpecificParams(MetaClassImpl.java:3240) ... sept. 05, 2016 5:41:49 PM com.seitenbau.jenkins.plugins.dynamicparameter.BaseParameterDefinition getScriptResultAsList INFOS: Script parameter with name '' is not a instance of java.util.List the parameter value is : null
[JIRA] (JENKINS-37666) Proceeding step is sometimes erroneously expanded
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37666 Re: Proceeding step is sometimes erroneously expanded Code changed in jenkins User: Thorsten Scherler Path: PULL_REQUEST_TEMPLATE src/main/js/page_objects/blueocean/bluePipelineBranch.js src/test/js/edgeCases/folder.js http://jenkins-ci.org/commit/blueocean-acceptance-test/56f41884c033113a7fa40eaa2e577cf33e2d9dd3 Log: Merge remote-tracking branch 'origin/master' into JENKINS-37666 Compare: https://github.com/jenkinsci/blueocean-acceptance-test/compare/edcbedd7f754...56f41884c033 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-37888) Upgrade to latest yavijava release
Title: Message Title pjdarton commented on JENKINS-37888 Re: Upgrade to latest yavijava release +1 We were getting a bunch of exceptions of the form: SEVERE org.jenkinsci.plugins.vSphereCloudProvisionedSlave _terminate org.jenkinsci.plugins.vsphere.tools.VSphereException: java.rmi.RemoteException: Exception in SoapClient.invoke:; nested exception is: java.lang.IllegalAccessException: Class com.vmware.vim25.ws.XmlGenDom can not access a member of class java.util.Calendar with modifiers "protected" at org.jenkinsci.plugins.vsphere.tools.VSphere.(VSphere.java:66) at org.jenkinsci.plugins.vsphere.tools.VSphere.connect(VSphere.java:80) at org.jenkinsci.plugins.vSphereCloud.vSphereInstance(vSphereCloud.java:228) at org.jenkinsci.plugins.vSphereCloudProvisionedSlave._terminate(vSphereCloudProvisionedSlave.java:71) at hudson.slaves.AbstractCloudSlave.terminate(AbstractCloudSlave.java:67) at org.jenkinsci.plugins.RunOnceCloudRetentionStrategy$1$1.run(RunOnceCloudRetentionStrategy.java:108) at hudson.model.Queue._withLock(Queue.java:1315) at hudson.model.Queue.withLock(Queue.java:1192) at org.jenkinsci.plugins.RunOnceCloudRetentionStrategy$1.run(RunOnceCloudRetentionStrategy.java:102) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.rmi.RemoteException: Exception in SoapClient.invoke:; nested exception is: java.lang.IllegalAccessException: Class com.vmware.vim25.ws.XmlGenDom can not access a member of class java.util.Calendar with modifiers "protected" at com.vmware.vim25.ws.XmlGenDom.fromXML(XmlGenDom.java:123) at com.vmware.vim25.ws.SoapClient.unMarshall(SoapClient.java:212) at com.vmware.vim25.ws.WSClient.invoke(WSClient.java:93) at com.vmware.vim25.ws.VimStub.login(VimStub.java:1732) at com.vmware.vim25.mo.SessionManager.login(SessionManager.java:153) at com.vmware.vim25.mo.ServiceInstance.login(ServiceInstance.java:238) at com.vmware.vim25.mo.ServiceInstance.constructServiceInstance(ServiceInstance.java:131) at com.vmware.vim25.mo.ServiceInstance.(ServiceInstance.java:79) at com.vmware.vim25.mo.ServiceInstance.(ServiceInstance.java:69) at org.jenkinsci.plugins.vsphere.tools.VSphere.(VSphere.java:64) ... 14 more Caused by: java.lang.IllegalAccessException: Class com.vmware.vim25.ws.XmlGenDom can not access a member of class java.util.Calendar with modifiers "protected" at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:102) at java.lang.Class.newInstance(Class.java:436) at com.vmware.vim25.ws.XmlGenDom.fromXml(XmlGenDom.java:219) at com.vmware.vim25.ws.XmlGenDom.fromXml(XmlGenDom.java:329) at com.vmware.vim25.ws.XmlGenDom.fromXML(XmlGenDom.java:210) at com.vmware.vim25.ws.XmlGenDom.fromXML(XmlGenDom.java:120) ... 23 more We edited the pom to use version 6.0.04, rebuilt, and the problem went away. 6.0.04 seems stable from our point of view... This was a killer issue for us before we did that.
[JIRA] (JENKINS-37666) Proceeding step is sometimes erroneously expanded
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37666 Re: Proceeding step is sometimes erroneously expanded Code changed in jenkins User: Thorsten Scherler Path: src/main/js/page_objects/blueocean/bluePipelineRunDetail.js src/test/js/failing.js src/test/js/log-karaoke/stages.js src/test/resources/test_scripts/noStagesFailing.groovy http://jenkins-ci.org/commit/blueocean-acceptance-test/edcbedd7f75458969608e25d8f0d0e3574fd9958 Log: JENKINS-37666 Implement test for regression of clicking steps sometimes resulted in weird state 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-37914) Many Times JENKINS_HOME is Invalid
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-37914 Many Times JENKINS_HOME is Invalid Change By: Mark Waite Component/s: workflow-basic-steps-plugin Component/s: git-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-37914) Many Times JENKINS_HOME is Invalid
Title: Message Title
Mark Waite commented on JENKINS-37914
Re: Many Times JENKINS_HOME is Invalid
If you must run job steps on a specific node, then that needs to be defined in the node definition. Your pipeline definition says:
node {
// Insert your steps here
}
If you really want to require that the pipeline only execute on the master node, then your definition should be:
node("master") {
// Insert your steps here
}
It is usually not good to require a specific node for a stage, but sometimes it is unavoidable (for example, if your organization only allows code signing from a specific node, or if a commercial tool is only available on a single node).
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-18989) Cannot get Plugin to honor Java Jar added via "Additional groovy classpath"
Title: Message Title Ayrat Natfullin commented on JENKINS-18989 Re: Cannot get Plugin to honor Java Jar added via "Additional groovy classpath" Also the original question was about "Additional groovy classpath": in Jenkins ver. 1.619 it works. I've moved all logic to java uber jar, added jar to classpath in Groovy Script Post Build action and is able to make http requests from Java. 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-18989) Cannot get Plugin to honor Java Jar added via "Additional groovy classpath"
Title: Message Title
Ayrat Natfullin edited a comment on JENKINS-18989
Re: Cannot get Plugin to honor Java Jar added via "Additional groovy classpath"
Also spent hours trying to make it working but got lots various errors.Finally could make it working the following way:Groovy file:{code:java}class GitlabPostbuildReporter { def managerpublic GitlabPostbuildReporter(Object manager){if(manager == null) { throw new RuntimeException("Manager object can't be null")}this.manager = manager }public def report() {// do work with manager objectmanager.addBadge("db_in.gif", "Stored to DB") }}{code}On Jenkins side create a groovy script post build action:{code: groovy java }// Ayrat Natfullin: this code passes manager object to external groovy script // so you may operate with current jobimport hudson.model.* import groovy.lang.GroovyClassLoader;import groovy.lang.GroovyObject; import java.io.File;// short ref for printing out in Jenkins consoleout = manager.listener.logger.def file = new File("D:/tools/Jenkins/scripts/GitlabPostbuildReporter.groovy")// this helps you to make sure script exists and Jenkins has access to itout(file.exists())// Loading script using String parameter doesn't work so switch to using File insteadClass groovy = this.class.classLoader.parseClass(new File("D:/tools/Jenkins/scripts/GitlabPostbuildReporter.groovy"));GroovyObject groovyObj = (GroovyObject) groovy.newInstance(manager);// example of how to print out all existing methodsout(groovyObj.metaClass.methods*.name.sort().unique());// call report that will add Badge icon to current build (see script above)groovyObj.report();{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-18989) Cannot get Plugin to honor Java Jar added via "Additional groovy classpath"
Title: Message Title
Ayrat Natfullin edited a comment on JENKINS-18989
Re: Cannot get Plugin to honor Java Jar added via "Additional groovy classpath"
Also spent hours trying to make it working but got lots various errors.Finally could make it working the following way:Groovy file:{code: groovy java }class GitlabPostbuildReporter { def managerpublic GitlabPostbuildReporter( ) {}public GitlabPostbuildReporter( Object manager){if(manager == null) { throw new RuntimeException("Manager object musn can 't be null")}this.manager = manager }public def report() {// do work with manager object manager.addBadge("db_in.gif", "Stored to DB") }}{code}On Jenkins side create a groovy script post build action:{code:groovy}// Ayrat Natfullin: this code passes manager object to external groovy script // so you may operate with current jobs using Jenkin's manager object job import hudson.model.* import groovy.lang.GroovyClassLoader;import groovy.lang.GroovyObject; import java.io.File;// short ref for printing out in Jenkins consoleout = manager.listener.logger.def file = new File("D:/tools/Jenkins/scripts/GitlabPostbuildReporter.groovy")// this helps you to make sure script exists and Jenkins has access to itout(file.exists())// Loading script using String parameter doesn't work so switch to using File insteadClass groovy = this.class.classLoader.parseClass(new File("D:/tools/Jenkins/scripts/GitlabPostbuildReporter.groovy"));GroovyObject groovyObj = (GroovyObject) groovy.newInstance(manager);// example of how to print out all existing methodsout(groovyObj.metaClass.methods*.name.sort().unique());// call report that will add Badge icon to current build (see script above)groovyObj.report();{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-18989) Cannot get Plugin to honor Java Jar added via "Additional groovy classpath"
Title: Message Title
Ayrat Natfullin edited a comment on JENKINS-18989
Re: Cannot get Plugin to honor Java Jar added via "Additional groovy classpath"
Also spent hours try trying to make it working but got lots various errors.Finally could make it working the following way :Groovy file:{code:groovy}class GitlabPostbuildReporter { def managerpublic GitlabPostbuildReporter() {}public GitlabPostbuildReporter(Object manager){if(manager == null) { throw new RuntimeException("Manager object musn't be null")}this.manager = manager }public def report() {// do work with manager object manager.addBadge("db_in.gif", "Stored to DB") }}{code}On Jenkins side create a groovy script post build action:{code:groovy}// Ayrat Natfullin: this code passes manager object to external groovy script // so you may operate with current jobs using Jenkin's manager objectimport hudson.model.* import groovy.lang.GroovyClassLoader;import groovy.lang.GroovyObject; import java.io.File;// short ref for printing out in Jenkins consoleout = manager.listener.logger.def file = new File("D:/tools/Jenkins/scripts/GitlabPostbuildReporter.groovy")// this helps you to make sure script exists and Jenkins has access to itout(file.exists())// Loading script using String parameter doesn't work so switch to using File insteadClass groovy = this.class.classLoader.parseClass(new File("D:/tools/Jenkins/scripts/GitlabPostbuildReporter.groovy"));GroovyObject groovyObj = (GroovyObject) groovy.newInstance(manager);// example of how to print out all existing methodsout(groovyObj.metaClass.methods*.name.sort().unique());// call report that will add Badge icon to current build (see script above)groovyObj.report();{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-18989) Cannot get Plugin to honor Java Jar added via "Additional groovy classpath"
Title: Message Title
Ayrat Natfullin commented on JENKINS-18989
Re: Cannot get Plugin to honor Java Jar added via "Additional groovy classpath"
Also spent hours try to make it working but got lots various errors. Finally could make it working: Groovy file:
Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
class GitlabPostbuildReporter {
def manager
public GitlabPostbuildReporter() {}
public GitlabPostbuildReporter(Object manager){
if(manager == null) {
throw new RuntimeException("Manager object musn't be null")
}
this.manager = manager
}
public def report() {
// do work with manager object
manager.addBadge("db_in.gif", "Stored to DB")
}
}
On Jenkins side create a groovy script post build action:
Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
// Ayrat Natfullin: this code passes manager object to external groovy script
// so you may operate with current jobs using Jenkin's manager object
import hudson.model.*
import groovy.lang.GroovyClassLoader;
import groovy.lang.GroovyObject;
import java.io.File;
// short ref for printing out in Jenkins console
out = manager.listener.logger.
def file = new File("D:/tools/Jenkins/scripts/GitlabPostbuildReporter.groovy")
// this helps you to make sure script exists and Jenkins has access to it
out(file.exists())
// Loading script using String parameter doesn't work so switch to using File instead
Class groovy = this.class.classLoader.parseClass(new File("D:/tools/Jenkins/scripts/GitlabPostbuildReporter.groovy"));
GroovyObject groovyObj = (GroovyObject) groovy.newInstance(manager);
// example of how to print out all existing methods
out(groovyObj.metaClass.methods*.name.sort().unique());
// call report that will add Badge icon to current build (see script above)
groovyObj.report();
[JIRA] (JENKINS-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Title: Message Title
Leonardo Zanivan commented on JENKINS-28335
Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support)
There's a workaround using ssh-agent-plugin:
sshagent(['git-credentials-id']) {
sh "git push origin master"
}
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 Laurențiu Păncescu Depending on how extensive the change for PeriodicUpdater is, it'll probably be easier to get the apparently minimal fix of setInterval integrated. If it's easy enough to do so enough, you could also open two PRs and indicate they are alternative solutions. 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-37966) File Descriptor leaks when parsing Groovy Class files in Stapler (Groovy UI)
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-37966 File Descriptor leaks when parsing Groovy Class files in Stapler (Groovy UI) Change By: Oleg Nenashev Summary: File Descriptor leaks when parsing Groovy Class files in Stapler ( Grrovy Groovy UI) 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-37966) File Descriptor leaks when parsing Groovy Class files in Stapler (Grrovy UI)
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-37966 File Descriptor leaks when parsing Groovy Class files in Stapler (Grrovy UI) Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Sep/05 1:20 PM Environment: jenkins-2.7.3 staple 1.243 (default for this version) Labels: stapler Priority: Minor Reporter: Oleg Nenashev It happens due to the issue similar to JENKINS-37041. JarUrlConnection is not being processed correctly. Potential impact is low since we are not going to replace the files on the flight #796 /Users/nenashev/Documents/.../test/plugins/git/WEB-INF/lib/git.jar by thread:Handling GET /jenkins/job/FooTimestamped/configure from 0:0:0:0:0:0:0:1 : RequestHandlerThread[#22] Job/configure.jelly Project/configure-entries.jelly AbstractProject/configure-common.jelly AbstractProject/configure-scm.jellytag GitSCM/DescriptorImpl/config.jelly on Mon Sep 05 15:02:56 CEST 2016 at java.io.FileInputStream.(FileInputStream.java:139) at java.io.FileInputStream.(FileInputStream.java:93) at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90) at sun.net.www.protocol.file.FileURLConnection.initializeHeaders(FileURLConnection.java:110) at sun.net.www.protocol.file.FileURLConnection.getHeaderField(FileURLConnection.java:146) at sun.net.www.protocol.jar.JarURLConnection.getHeaderField(JarURLConnection.java:228) at
[JIRA] (JENKINS-37966) File Descriptor leaks when parsing Groovy Class files in Stapler (Grrovy UI)
Title: Message Title Oleg Nenashev commented on JENKINS-37966 Re: File Descriptor leaks when parsing Groovy Class files in Stapler (Grrovy UI) CC Mark Waite and Kirill Merkushev since their plugins are affected. Not a big problem since the impact is not visible 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-37965) REGRESSION react developer tools stopped working
Title: Message Title Thorsten Scherler created an issue Jenkins / JENKINS-37965 REGRESSION react developer tools stopped working Issue Type: Bug Assignee: Unassigned Attachments: Screenshot from 2016-09-05 15-15-24.png Components: blueocean-plugin Created: 2016/Sep/05 1:18 PM Priority: Minor Reporter: Thorsten Scherler Clicking on the React Developer leads to an error in the console. Add Comment
[JIRA] (JENKINS-37893) When using Multiple Publisher Templates with Flexible publisher it will configure back to the one highest in Alphabetical order
Title: Message Title ikedam assigned an issue to Alex Taylor What's "publisher template"? Jenkins / JENKINS-37893 When using Multiple Publisher Templates with Flexible publisher it will configure back to the one highest in Alphabetical order Change By: ikedam Assignee: bap Alex Taylor 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-33786) Compatibility with Folders plugin - jobs in folders not showing in HP ALM
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-33786 Compatibility with Folders plugin - jobs in folders not showing in HP ALM Change By: Arnaud Héritier HP ALM is showing jobs at the root-level only, but doesn't appear to work with jobs in folders. 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 Laurențiu Păncescu commented on JENKINS-10912 Re: Browser/JS memory leak in dashboard I see a significant memory leak on ci.centos.org - it doesn't affect just the Dashboard. The memory usage for that tab increases to 1.7GB in Chrome and 1GB in Safari, over less than 3 hours (I also see this with Firefox on both OS X and Linux, although the memory increase seems less steep). I posted details on the centos-devel mailing list. The Chrome Developer Tools point to refreshPart from hudson-behavior.js as the culprit. Indeed, using 'delete node' from the Inspector to remove the #buildQueue and #executors divs stops the memory leak. I created a self-contained test to illustrate the problem, using just plain _javascript_, without any external libraries: https://github.com/lpancescu/xhr-memory-leak. The least intrusive fix for Jenkins would be to remove the call to refreshPart from function f, and use setInterval instead of setTimer (this is what noleak.html from my test repo does). The more elegant solution would be to use Ajax.PeriodicUpdater from Prototype.js, which is designed for this use case. If you tell me which variant you prefer, I can send you a pull request on GitHub. 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-37374) Jenkins 2.7.2 unable to see groovy section in global configuration menu
Title: Message Title Daniel Beck resolved as Not A Defect Jenkins / JENKINS-37374 Jenkins 2.7.2 unable to see groovy section in global configuration menu 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-31050) Slave goes offline during the build
Title: Message Title varun shrivastava commented on JENKINS-31050 Re: Slave goes offline during the build I have the same problem my version of jenkins is 2.7.2-1.1 and jdk 1.8.0_51 WARNING: Computer.threadPoolForRemoting 10973 for VM06-OASTEST terminated java.io.EOFException at org.jenkinsci.remoting.nio.NioChannelHub$3.run(NioChannelHub.java:614) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) SEVERE: A thread (TCP agent connection handler #12285 with /10.254.1.94:62697/223645) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code. hudson.remoting.RequestAbortedException: java.io.EOFException at hudson.remoting.Request.abort(Request.java:303) at hudson.remoting.Channel.terminate(Channel.java:847) at org.jenkinsci.remoting.nio.NioChannelHub$3.run(NioChannelHub.java:614) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at ..remote call to VM06-OASTEST(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416) at hudson.remoting.Request.call(Request.java:172) at hudson.remoting.Channel.call(Channel.java:780) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:508) at jenkins.slaves.JnlpSlaveAgentProtocol$Handler.jnlpConnect(JnlpSlaveAgentProtocol.java:127) at jenkins.slaves.DefaultJnlpSlaveReceiver.handle(DefaultJnlpSlaveReceiver.java:69) at jenkins.slaves.JnlpSlaveAgentProtocol2$Handler2.run(JnlpSlaveAgentProtocol2.java:60) at jenkins.slaves.JnlpSlaveAgentProtocol2.handle(JnlpSlaveAgentProtocol2.java:32) at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:182) Caused by: java.io.EOFException at org.jenkinsci.remoting.nio.NioChannelHub$3.run(NioChannelHub.java:614) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
[JIRA] (JENKINS-25323) Coverity Plugin 1.4.1 : Issues with starting a build after selecting Coverity as Post Build action
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25323 Re: Coverity Plugin 1.4.1 : Issues with starting a build after selecting Coverity as Post Build action Code changed in jenkins User: Andrius Ordojan Path: pom.xml src/main/java/hudson/plugins/clearcase/util/BuildUtils.java src/test/java/hudson/plugins/clearcase/AbstractClearCaseScmTest.java src/test/java/hudson/plugins/clearcase/ClearCaseSCMTest.java http://jenkins-ci.org/commit/clearcase-plugin/837f02ca4cbe182a3178e19c67b55d48dd80986d Log: Updated jenkins core and fixed issue JENKINS-25323 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-25323) Coverity Plugin 1.4.1 : Issues with starting a build after selecting Coverity as Post Build action
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25323 Re: Coverity Plugin 1.4.1 : Issues with starting a build after selecting Coverity as Post Build action Code changed in jenkins User: Mads Nielsen Path: pom.xml src/main/java/hudson/plugins/clearcase/util/BuildUtils.java src/test/java/hudson/plugins/clearcase/AbstractClearCaseScmTest.java src/test/java/hudson/plugins/clearcase/ClearCaseSCMTest.java http://jenkins-ci.org/commit/clearcase-plugin/bf34cae5973013b83af46a669cfb7595c2f299fa Log: Merge pull request #33 from Praqma/JENKINS-25323 JENKINS-25323 Compare: https://github.com/jenkinsci/clearcase-plugin/compare/d27f8ec2ed99...bf34cae59730 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-37964) Integrate with lucene-search plugin to be able to search build by failure.
Title: Message Title Sofer Athlan-Guyot commented on JENKINS-37964 Re: Integrate with lucene-search plugin to be able to search build by failure. After asking lucene to rescan everything I was able to find build using the title of the failure. So what could be added would be specific field in the lucene search for tag, title, description. It is less important though. The other problem is that for new failure, you have to : rescan all the build inside failure management and then rescan everything with lucene. This is less than convenient, even if doable. 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-37582) Stacktrace when creating Users/Group
Title: Message Title Félix Belzunce Arcos started work on JENKINS-37582 Change By: Félix Belzunce Arcos 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-37964) Integrate with lucene-search plugin to be able to search build by failure.
Title: Message Title Sofer Athlan-Guyot created an issue Jenkins / JENKINS-37964 Integrate with lucene-search plugin to be able to search build by failure. Issue Type: New Feature Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 2016/Sep/05 11:25 AM Priority: Minor Reporter: Sofer Athlan-Guyot Hi, it would be useful to search for failed build based on error. Integrating with the Lucene-Search would be great. It should then be possible to searchi on error tag, or error title, ... Currently I don't see how to do that, but maybe I miss something. This is somehow related to https://issues.jenkins-ci.org/browse/JENKINS-23978 as ordering would be a first step in looking for the relevant build easily. Regards, Add Comment
[JIRA] (JENKINS-37323) Ensure that Pipeline Graph can handle stage blocks
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37323 Re: Ensure that Pipeline Graph can handle stage blocks Code changed in jenkins User: Thorsten Scherler Path: src/test/js/log-karaoke/stages.js src/test/resources/test_scripts/stages-with-wait.groovy http://jenkins-ci.org/commit/blueocean-acceptance-test/d1ebf33b61197b57a7db256061ef179a7b8786e1 Log: JENKINS-37323 Implement test cases with new syntax 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-37374) Jenkins 2.7.2 unable to see groovy section in global configuration menu
Title: Message Title Igor Tere commented on JENKINS-37374 Re: Jenkins 2.7.2 unable to see groovy section in global configuration menu omg sorry. close issue. 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-37374) Jenkins 2.7.2 unable to see groovy section in global configuration menu
Title: Message Title Valerie Fernandes commented on JENKINS-37374 Re: Jenkins 2.7.2 unable to see groovy section in global configuration menu In 1.6x this option is available under Configure System. Now you need to go to "Global Tool Configuration" in "Manage Jenkins" or just access the url /configureTools see screenshot 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-37374) Jenkins 2.7.2 unable to see groovy section in global configuration menu
Title: Message Title Valerie Fernandes updated an issue Jenkins / JENKINS-37374 Jenkins 2.7.2 unable to see groovy section in global configuration menu Change By: Valerie Fernandes Attachment: screenshot-1.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-37374) Jenkins 2.7.2 unable to see groovy section in global configuration menu
Title: Message Title Igor Tere commented on JENKINS-37374 Re: Jenkins 2.7.2 unable to see groovy section in global configuration menu attached jpg how it on version Jenkins 1.605. I dont see such option for Jenkins 2.7.2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37374) Jenkins 2.7.2 unable to see groovy section in global configuration menu
Title: Message Title Igor Tere updated an issue Jenkins / JENKINS-37374 Jenkins 2.7.2 unable to see groovy section in global configuration menu Change By: Igor Tere Attachment: Capture.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-37374) Jenkins 2.7.2 unable to see groovy section in global configuration menu
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-37374 Jenkins 2.7.2 unable to see groovy section in global configuration menu Change By: Daniel Beck Labels: ,groovy+jenkins groovy, groovy-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-37374) Jenkins 2.7.2 unable to see groovy section in global configuration menu
Title: Message Title Igor Tere commented on JENKINS-37374 Re: Jenkins 2.7.2 unable to see groovy section in global configuration menu Yes. 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-37374) Jenkins 2.7.2 unable to see groovy section in global configuration menu
Title: Message Title Valerie Fernandes commented on JENKINS-37374 Re: Jenkins 2.7.2 unable to see groovy section in global configuration menu Are you looking for "Groovy installations" under "Global Tool Configuration" in "Manage Jenkins" ? /configureTools 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-33607) getServerLicenseData: no corresponding wsdl operation
Title: Message Title varun kalra commented on JENKINS-33607 Re: getServerLicenseData: no corresponding wsdl operation Hello, I have been facing the similar issue, since I have upgraded to checkmarx 8.0. I have tried all the versions of checkmarx plugin but still am facing the same issue. Can some one please help me out with this? Any help would be appreciated. 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-35269) Job configuration UI Layout is broken
Title: Message Title Valerie Fernandes commented on JENKINS-35269 Re: Job configuration UI Layout is broken Similar issue while enabling project based security. It drags the entire UI horizontally to the right on chrome and Firefox but not IE. In addition i also noticed that if the screen size is large with a resolution of 1920*1080, I do not face this issue on any browser. 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-37402) Enable project-based security causing job configure page to overflow in right
Title: Message Title Valerie Fernandes commented on JENKINS-37402 Re: Enable project-based security causing job configure page to overflow in right Is this duplicate of https://issues.jenkins-ci.org/browse/JENKINS-35269 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-36896) Stack Trace on startup
Title: Message Title james Dengel commented on JENKINS-36896 Re: Stack Trace on startup This also causes as issue for me hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.WebAppMain$3.run(WebAppMain.java:244) Caused by: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269) at jenkins.InitReactorRunner.run(InitReactorRunner.java:45) at jenkins.model.Jenkins.executeReactor(Jenkins.java:1010) at jenkins.model.Jenkins.(Jenkins.java:878) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:227) Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:110) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:999) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:104) ... 8 more Caused by: java.io.IOException: Tried to treat 'C:\Program Files (x86)\Jenkins\jobs\z_old_jobs\jobs\Deploy_scm_installer\lastSuccessful' as a directory, but could not get a listing at com.github.mjdetullio.jenkins.plugins.multibranch.TemplateDrivenMultiBranchProject.getConfigFiles(TemplateDrivenMultiBranchProject.java:717) at com.github.mjdetullio.jenkins.plugins.multibranch.TemplateDrivenMultiBranchProject.getConfigFiles(TemplateDrivenMultiBranchProject.java:732) at com.github.mjdetullio.jenkins.plugins.multibranch.TemplateDrivenMultiBranchProject.getConfigFiles(TemplateDrivenMultiBranchProject.java:732) at com.github.mjdetullio.jenkins.plugins.multibranch.TemplateDrivenMultiBranchProject.getConfigFiles(TemplateDrivenMultiBranchProject.java:732) at com.github.mjdetullio.jenkins.plugins.multibranch.TemplateDrivenMultiBranchProject.getConfigFiles(TemplateDrivenMultiBranchProject.java:732) at com.github.mjdetullio.jenkins.plugins.multibranch.TemplateDrivenMultiBranchProject.migrate(TemplateDrivenMultiBranchProject.java:758) ... 13 more removing the file did solve my issue, however i doubt very much this is a root cause fix. Add
[JIRA] (JENKINS-18989) Cannot get Plugin to honor Java Jar added via "Additional groovy classpath"
Title: Message Title Anna Bredikhina commented on JENKINS-18989 Re: Cannot get Plugin to honor Java Jar added via "Additional groovy classpath" Hi! I am doing the same like Zach in the last comment but getting error message groovy.lang.MissingPropertyException: No such property: XXX for class: Script1 does anyone have any idea why it can happen? 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-37963) Stages not shown
Title: Message Title Michael Neale commented on JENKINS-37963 Re: Stages not shown great, ok if I close this as a duplicate? should be available shortly. 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-37963) Stages not shown
Title: Message Title
Alex Soto commented on JENKINS-37963
Re: Stages not shown
Right, if using stage '' instead of stage(''){} form (labeled one) it works as expected.
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-37963) Stages not shown
Title: Message Title Michael Neale assigned an issue to Vivek Pandey Jenkins / JENKINS-37963 Stages not shown Change By: Michael Neale Assignee: Vivek Pandey Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37963) Stages not shown
Title: Message Title Michael Neale commented on JENKINS-37963 Re: Stages not shown I think this is the same thing addressed by https://issues.jenkins-ci.org/browse/JENKINS-37323 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-37963) Stages not shown
Title: Message Title Alex Soto created an issue Jenkins / JENKINS-37963 Stages not shown Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Sep/05 9:16 AM Priority: Major Reporter: Alex Soto When running next pipeline script https://gist.github.com/lordofthejars/be8c2384db1ce5207f0336e690e3367c and after its execution, you get next screen https://postimg.org/image/yvaeo4hc5/ instead of something like https://jenkins.io/images/post-images/blueocean/pipeline-run.png I am running Jenkins 2.20 and blue ocean 1.0.0-b01. Add Comment
[JIRA] (JENKINS-35367) EMail-Ext Extended Pipeline Support - Templates
Title: Message Title clausfod commented on JENKINS-35367 Re: EMail-Ext Extended Pipeline Support - Templates Any news on having the Template support via the Pipeline 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-30700) Make Cobertura plug-in support the workflow plugin
Title: Message Title clausfod commented on JENKINS-30700 Re: Make Cobertura plug-in support the workflow plugin What is the status for making the Cobertura plugin Pipeline ready ? 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-27963) Please add support for jenkins pipeline plugin to publish-over-ssh
Title: Message Title clausfod commented on JENKINS-27963 Re: Please add support for jenkins pipeline plugin to publish-over-ssh You can of course do it all yourselve with the SSH Agent plugin - but the nice features provided by the Publish Over SSH plugin is not available unless you "code" it yourselve. So I would like to know also - Is the plugin planned to be available from the Pipeline 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-37955) CSS warnings in safari
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37955 CSS warnings in safari Change By: James Dumay Sprint: 1.0-beta- 2 1 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-33289) nullpointerexception when clicking on 'show diffs' on a job config history page (since 1.651 update)
Title: Message Title stino spash reopened an issue I see the same bug on Jenkins 2.7.1 with org.jenkins-ci.plugins:jobConfigHistory:2.12 com.googlecode.java-diff-utils:diffutils:1.2.1 Jenkins / JENKINS-33289 nullpointerexception when clicking on 'show diffs' on a job config history page (since 1.651 update) Change By: stino spash Resolution: Fixed 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
[JIRA] (JENKINS-32148) highlight test result lines on hover
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32148 Re: highlight test result lines on hover Code changed in jenkins User: Oliver Gondža Path: src/main/resources/hudson/tasks/junit/CaseResult/list.jelly src/main/resources/hudson/tasks/junit/ClassResult/body.jelly src/main/resources/hudson/tasks/junit/ClassResult/list.jelly src/main/resources/hudson/tasks/test/AggregatedTestResultPublisher/TestResultAction/index.jelly src/main/resources/hudson/tasks/test/MetaTabulatedResult/body.jelly src/main/resources/hudson/tasks/test/MetaTabulatedResult/list.jelly src/main/resources/lib/hudson/test/aggregated-failed-tests.jelly src/test/resources/hudson/tasks/test/TrivialTestResult/body.jelly http://jenkins-ci.org/commit/junit-plugin/15568e0b4b957fe3d8ec78250f18db51c17bc97c Log: Merge pull request #55 from dirk-thomas/stripped_and_hover JENKINS-32148 use alternate background for table rows, highlight row on hover Compare: https://github.com/jenkinsci/junit-plugin/compare/8319d7e408dd...15568e0b4b95 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-37914) Many Times JENKINS_HOME is Invalid
Title: Message Title
zhao wu commented on JENKINS-37914
Re: Many Times JENKINS_HOME is Invalid
Mark Waite i was in master node,but some time i get this log, Running on alpha_service01 in /home/jhd/jenkins/workspace/alpha_service01_customer_service alpha_service01 is Remote node Jenkinsfile
node {
def subjectMessage = ""
def failMessage = ""
try {
stage 'Checkout'
sh "pwd"
git credentialsId: 'ssh', url: 'git@172.16.61.211:service/xxx.git'
stage 'Build'
sh "/usr/local/maven/apache-maven-3.3.9/bin/mvn -Dmaven.test.skip=true clean package -P alpha"
stage 'stash'
stash includes: 'xxx/target/*.war', name:'xxx.war'
node('alpha_service01') {
stage 'unstash'
unstash 'xxx.war'
writeFile encoding: 'utf-8', file: 'deploy.sh', text: '''#!/bin/bash
//some code
'''
stage 'Restart'
sh "sh -x deploy.sh"
}
} catch (e) {
throw e
}finally {
mail bcc: '', body: "Job '${env.JOB_NAME}' (${env.BUILD_NUMBER}) ${env.BUILD_URL}", cc: '', from: '', replyTo: '', subject: message, to: 'xxx'
}
}
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-37914) Many Times JENKINS_HOME is Invalid
Title: Message Title zhao wu updated an issue Jenkins / JENKINS-37914 Many Times JENKINS_HOME is Invalid Change By: zhao wu Attachment: 1.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-32004) HP Automation Tools Unable to Export Job Results to QC
Title: Message Title sergio costa edited a comment on JENKINS-32004 Re: HP Automation Tools Unable to Export Job Results to QC Sorry, at this moment I can't reproduce it and I'm not sure if I already tried the latest version. I will try to reproduce it as soon as possible , and I will let you know . 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-32004) HP Automation Tools Unable to Export Job Results to QC
Title: Message Title sergio costa commented on JENKINS-32004 Re: HP Automation Tools Unable to Export Job Results to QC Sorry, at this moment I can't reproduce it and I'm not sure if I already tried the latest version. I will try to reproduce it as soon as possible. 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.
