[JIRA] (JENKINS-50433) unable to load shared library from gerrit pull request branch
Title: Message Title Sorin Sbarnea updated JENKINS-50433 Closing as I am no longer using jenkins so I cannot reproduce it (or the fix) Jenkins / JENKINS-50433 unable to load shared library from gerrit pull request branch Change By: Sorin Sbarnea Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189489.1522158981000.20117.1557241440907%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46096) Pipeline stage view rendered at bottom of page, below build history
Title: Message Title Sorin Sbarnea commented on JENKINS-46096 Re: Pipeline stage view rendered at bottom of page, below build history I removed myself as I managed to move from Jenkins to Zuul. It would still be nice if somoene could fix it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46096) Pipeline stage view rendered at bottom of page, below build history
Title: Message Title Sorin Sbarnea assigned an issue to Sam Van Oort Jenkins / JENKINS-46096 Pipeline stage view rendered at bottom of page, below build history Change By: Sorin Sbarnea Assignee: Sorin Sbarnea Sam Van Oort Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43379) WARN: java.lang.InterruptedException: no matches found within 10000
Title: Message Title Sorin Sbarnea closed an issue as Won't Do I am closing this becase this seems to be the only way to silence notifications on a bug and I am not allowed to change reporter to avoid these. If someone else has the power to change reported and reopen the bug feel free, if not create a new bug. Jenkins / JENKINS-43379 WARN: java.lang.InterruptedException: no matches found within 1 Change By: Sorin Sbarnea Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51260) global environment variables are not expanded (interpolated) in pipelines
Title: Message Title Sorin Sbarnea commented on JENKINS-51260 Re: global environment variables are not expanded (interpolated) in pipelines Yes, EnvInject plugin is installed but we are not using it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19393) global search should not jump to exact result if more than one result is found
Title: Message Title Sorin Sbarnea edited a comment on JENKINS-19393 Re: global search should not jump to exact result if more than one result is found What is making this issue even worse is that if you happen to search using a string which happens to be username, you will be redirected to the user page instead of getting all jobs which contain this username.As one practice to mark WIP jobs with username suffix, you can only imagine that the search box fails to deliver expected results and a confusing manner.Does anyone knows a way to disable the redirect to user page feature in global search? Also raised as JENKINS-51506 as this ticket is not exactly a duplication. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51506) search box wrongly redirects to user page when search text matches a user
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-51506 search box wrongly redirects to user page when search text matches a user Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-05-23 12:47 Priority: Minor Reporter: Sorin Sbarnea If you search using a string which happens to be username, you will be redirected to the user page instead of getting all jobs which contain this username. As one practice to mark WIP jobs with username suffix or prefix, you can only imagine that the search box fails to deliver expected results and provides a confusing behavior. We need at least an admin option to disable searching for users in the search box, I can hardly find a real use for this feature. Alternatively search for user could be enabled using a smart syntax like the one used by gerrit or google: "user:foo". Add Comment
[JIRA] (JENKINS-19393) global search should not jump to exact result if more than one result is found
Title: Message Title Sorin Sbarnea commented on JENKINS-19393 Re: global search should not jump to exact result if more than one result is found What is making this issue even worse is that if you happen to search using a string which happens to be username, you will be redirected to the user page instead of getting all jobs which contain this username. As one practice to mark WIP jobs with username suffix, you can only imagine that the search box fails to deliver expected results and a confusing manner. Does anyone knows a way to disable the redirect to user page feature in global search? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51260) global environment variables are not expanded (interpolated) in pipelines
Title: Message Title
Sorin Sbarnea created an issue
Jenkins / JENKINS-51260
global environment variables are not expanded (interpolated) in pipelines
Issue Type:
Bug
Assignee:
Unassigned
Components:
core, pipeline
Created:
2018-05-11 10:36
Priority:
Critical
Reporter:
Sorin Sbarnea
On Freestyle jobs defining a Jenkins global variable like this would work as expected:
XDG_CACHE_HOME=${HOME}/.cache/${EXECUTOR_NUMBER}
Note: behavior is the same regardless if brackets are used or not when you define the variables. Freestyle "set" result (correct):
XDG_CACHE_HOME=/home/builder/.cache/2
Pipeline "set" result (incorrect):
XDG_CACHE_HOME=${HOME}/.cache/${EXECUTOR_NUMBER}
This problem is essential because it prevents Jenkins administrators from using environment variables to fix/workaround execution problems. Effectively this breaks any job that needs to define variables that are relative to something else, like workspace, home,
[JIRA] (JENKINS-19130) environment variables aren't expanded by description setter
Title: Message Title Sorin Sbarnea updated an issue Jenkins / JENKINS-19130 environment variables aren't expanded by description setter Change By: Sorin Sbarnea Summary: environment variables aren't expanded by description setter Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19129) Environment variables not expanded in plot configuration
Title: Message Title Sorin Sbarnea updated an issue Jenkins / JENKINS-19129 Environment variables not expanded in plot configuration Change By: Sorin Sbarnea Summary: Environment variables not expanded in plot configuration Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30148) Allocate shorter workspace if it will be too long for reasonable use inside build
Title: Message Title Sorin Sbarnea commented on JENKINS-30148 Re: Allocate shorter workspace if it will be too long for reasonable use inside build Any change of having this fixed, ever, at least for normal pipelines? Here is one real life example: /home/rhos-ci/jenkins/workspace/DFG-storage-cinder-20_director-rhel-virthost-3cont_2comp-ipv4-vxlan-netapp-nfs-external-ssbarnea With the mention that limiting the job name is impossible, there are tens of people creating jobs and no way to enforce a limit, in addition that an attempt to rename >1000 existing jobs would be an epic failure. The only thing where it may be possible to cut few characters is on jenkins slave HOME directory and subfolder, but other than this nope. Even so, changing this would be quite complex too as it would involve lots of slaves type which are created by various people where almost for sure you will endup with some not using the shortened home directory workaround. Still, even if I manage to pick the minimum possible home directory, of "/j" it will clearly not be enough to make virtuaenvs working because job names will continue to be too long. ** Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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 Sorin Sbarnea reopened an issue As of latest version of the plugin and Jenkins (LTS) 2.89.4 this plugin does not expose any pipeline functionality. /pipeline-syntax/ - does not contain any ssh function listed (ticket screenshot is outdated because now the dropdown contains function names) /pipeline-syntax/html – does not contain any "ssh" occurence Jenkins log does not report any errors or warnings related to ssh plugin, and it was restarted after installation. Jenkins / JENKINS-27963 Please add support for jenkins pipeline plugin to publish-over-ssh Change By: Sorin Sbarnea Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-4888) Incorrect expiry HTTP header
Title: Message Title Sorin Sbarnea commented on JENKINS-4888 Re: Incorrect expiry HTTP header Daniel Beck I think that the problem is still valid in 2018 and is not limited to a specific plugin. A backdated expire header would force the client to check if the resource was modified all the time, even if it would receive a 304 (not modified) response back. If you consider that a normal Jenkins web page can have 70-120 resources, this would have serious performance implication on both server and client: server will get lots of extra bogus requests and on high load machine this is not to be ignored. client would not load the resource until it gets the confirmation that it was not modified from the server, so slower page loads, one of the common Jenkins complains from the users. example-of-static-resource-with-backdated-expire-header Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50922) console output is displayed only on job main page not on build one
Title: Message Title Sorin Sbarnea updated an issue Jenkins / JENKINS-50922 console output is displayed only on job main page not on build one Change By: Sorin Sbarnea Component/s: display-console-output-plugin Component/s: console-tail-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50922) console output is displayed only on job main page not on build one
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-50922 console output is displayed only on job main page not on build one Issue Type: Task Assignee: Unassigned Components: console-tail-plugin Created: 2018-04-21 06:43 Priority: Minor Reporter: Sorin Sbarnea While seeing the console output tail is very useful as it may save people from going to a new page it seems that it does not display on build page, only on job page. Most CI results put a comment with a link to the build, not the job and for good reasons. Still when used clicks it he will not be able to see the console output summary/tail. Add Comment
[JIRA] (JENKINS-36783) Artifact download links rely on mime type to determine download vs. view
Title: Message Title Sorin Sbarnea edited a comment on JENKINS-36783 Re: Artifact download links rely on mime type to determine download vs. view Maybe someone can give me a hint on this: I observed that for .log files Jenkins works as expected but I do also have shell files (.sh) which are always downloaded, even when I click the view link (left side).Where can this be changed so people can view these files? I have the impression that this bug was not really sorted because Jenkins should be able to return different Content-Disposition header for the left side links (view), and for right side (download). At this moment these urls look identical which makes me believe there is no way for jenkins to know what headers to return.I do remember that the old UI had different URLs, so this seems like a UX regression from this point of view. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36783) Artifact download links rely on mime type to determine download vs. view
Title: Message Title Sorin Sbarnea commented on JENKINS-36783 Re: Artifact download links rely on mime type to determine download vs. view Maybe someone can give me a hint on this: I observed that for .log files Jenkins works as expected but I do also have shell files (.sh) which are always downloaded, even when I click the view link (left side). Where can this be changed so people can view these files? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50795) jenkins search java.lang.NullPointerException at hudson.search.FixedSet.find(FixedSet.java:53)
Title: Message Title Sorin Sbarnea commented on JENKINS-50795 Re: jenkins search java.lang.NullPointerException at hudson.search.FixedSet.find(FixedSet.java:53) Let me know if there is something else I can do to test. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50795) jenkins search java.lang.NullPointerException at hudson.search.FixedSet.find(FixedSet.java:53)
Title: Message Title
Sorin Sbarnea updated an issue
Jenkins / JENKINS-50795
jenkins search java.lang.NullPointerException at hudson.search.FixedSet.find(FixedSet.java:53)
Change By:
Sorin Sbarnea
When using the search box from a job pages (as opposed to main jenkins page), user may get a null pointer exception instead of the search results. Even refreshing the page gives the same results. Going to home page and performing the same search works well. Example of It seems that the stacktrace appears only when the search url: is performed from inside a build page. Explanation: {code:java}https:// foo-bar-qe-jenkins example . rhev com/search/?q=foobar - ci - vms.eng.some2. - stacktracehttps:// example.com/job/ util foo/search/?q=foobar - monitor - long - running- workshttps://example.com/ job/ foo/ 12105/search/?q= DDD foobar - abcdefg - sometext - 13_director-rhel-virthost-3cont_2comp_3ceph-ipv4-vxlan-hahannnsd stacktrace {code} {code:java}java.lang.NullPointerExceptionat hudson.search.FixedSet.find(FixedSet.java:53)at hudson.search.Search$Mode$1.find(Search.java:209)at hudson.search.Search.find(Search.java:383)at hudson.search.Search.find(Search.java:262)at hudson.search.Search.doIndex(Search.java:85)at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343)at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184)at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117)at org.kohsuke.stapler.IndexDispatcher.dispatch(IndexDispatcher.java:26)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715)Caused: javax.servlet.ServletExceptionat org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:765)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845)at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:209)at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845)at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845)at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248)at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)at org.kohsuke.stapler.Stapler.service(Stapler.java:238)at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:841)at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650)at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154)at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:225)at hudson.util.PluginServletFilter$1.doFilter(Pl
[JIRA] (JENKINS-50795) jenkins search java.lang.NullPointerException at hudson.search.FixedSet.find(FixedSet.java:53)
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-50795 jenkins search java.lang.NullPointerException at hudson.search.FixedSet.find(FixedSet.java:53) Issue Type: Improvement Assignee: Unassigned Components: core Created: 2018-04-13 15:19 Environment: jenkins-2.89.3 Priority: Major Reporter: Sorin Sbarnea When using the search box from a job pages (as opposed to main jenkins page), user may get a null pointer exception instead of the search results. Even refreshing the page gives the same results. Going to home page and performing the same search works well. Example of search url: https://foo-bar-qe-jenkins.rhev-ci-vms.eng.some2.example.com/job/util-monitor-long-running-job/12105/search/?q=DDD-abcdefg-sometext-13_director-rhel-virthost-3cont_2comp_3ceph-ipv4-vxlan-hahannnsd java.lang.NullPointerException at hudson.search.FixedSet.find(FixedSet.java:53) at hudson.search.Search$Mode$1.find(Search.java:209) at hudson.search.Search.find(Search.java:383) at hudson.search.Search.find(Search.java:262) at hudson.search.Search.doIndex(Search.java:85) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184)
[JIRA] (JENKINS-50746) statistics-gatherer-plugin should be able to feed data into mongodb
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-50746 statistics-gatherer-plugin should be able to feed data into mongodb Issue Type: Improvement Assignee: Maxime Charron Components: statistics-gatherer-plugin Created: 2018-04-11 17:57 Priority: Minor Reporter: Sorin Sbarnea Data gathered by statistics-gatherer-plugin is in JSON format and it would be extremely useful to have an option to configure the plugin to post data to a mongodb instance. Currently there is a very similar functionality already implemented into Build-failure-analyzer plugin (BFA), which is able to feed information into mongodb. Add Comment
[JIRA] (JENKINS-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title Sorin Sbarnea commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Few minutes ago I raised https://issues.jenkins-ci.org/browse/JENKINS-50433 which states that there is no way to tell git plugin to pull gerrit branches because there is no way to convince it to remove "-h" from "git ls-remote". Any tricks/workarounds to make this work? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50433) unable to load shared library from gerrit pull request branch
Title: Message Title Sorin Sbarnea updated an issue Jenkins / JENKINS-50433 unable to load shared library from gerrit pull request branch Change By: Sorin Sbarnea Environment: git-3.7.0jenkins-2.89 (LTS) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50433) unable to load shared library from gerrit pull request branch
Title: Message Title
Sorin Sbarnea updated an issue
Jenkins / JENKINS-50433
unable to load shared library from gerrit pull request branch
Change By:
Sorin Sbarnea
It seems that is not possible to load a shared library from a CRs gerrit branch, mostly because current *GitSCMSource* plugin fails to see gerrit branches, and tuning the rawRefSpecs parameter seems to have no effect on it. {code:java}library identifier: 'temp-lib@master', retriever: modernSCM([$class: 'GitSCMSource',remote: 'https://review.gerrithub.io/rhos-infra/foobar',excludes: '',includes: '*',rawRefSpecs: '+refs/heads/*:refs/remotes/origin/* +refs/tags/*:refs/remotes/origin/tags/* +refs/changes/*:refs/remotes/changes/*']){code}Example of using git ls-remote on gerrit repository: {code:java}git ls-remote git ls-remote https://review.gerrithub.io/rhos-infra/foobar558aca4bf8d2eb357caa72292abb94b3b87cc41f HEADa6b8fced01ebdd09930ff75768d3c437567e2f81 refs/changes/78/386678/1ad71ed9c8a225eb11531322ef928b89ca74eba5e refs/changes/82/386682/173969f31bbc57a53b903b3c16ade1b991cbf11f7 refs/changes/82/386682/2cd404f64f7840bf2d92a830186159c809ff2450e refs/changes/84/386684/1f05cf74695e6c5731ccbeb5d98de113031ff0c70 refs/changes/84/386684/265e65cae35fc55779db0afe56e9bd28554e5c074 refs/changes/85/386685/1c96845ab149d8f1908f46ad279088e4fb1a77dae refs/changes/85/386685/289fbd1f054b2d1f3d0c417235b0e37299a36c078 refs/changes/85/386685/3558aca4bf8d2eb357caa72292abb94b3b87cc41f refs/heads/master{code}As you can see, ls-remote is able to detect gerrit branches without problems. Still, I we check the console log of the job, we will find that Jenkins is trying to perform a "git ls-remote -t -h ..." which is filtering out the remote branches that we are interested about.I was not able to find any option to tell it not to do this.
Add Comment
[JIRA] (JENKINS-50433) unable to load shared library from gerrit pull request branch
Title: Message Title Sorin Sbarnea updated an issue Jenkins / JENKINS-50433 unable to load shared library from gerrit pull request branch Change By: Sorin Sbarnea Component/s: git-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50433) unable to load shared library from gerrit pull request branch
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-50433 unable to load shared library from gerrit pull request branch Issue Type: Task Assignee: Unassigned Components: workflow-cps-global-lib-plugin Created: 2018-03-27 13:56 Priority: Minor Reporter: Sorin Sbarnea It seems that is not possible to load a shared library from a CRs gerrit branch, mostly because current GitSCMSource plugin fails to see gerrit branches, and tuning the rawRefSpecs parameter seems to have no effect on it. library identifier: 'temp-lib@master', retriever: modernSCM( [$class: 'GitSCMSource', remote: 'https://review.gerrithub.io/rhos-infra/foobar', excludes: '', includes: '*', rawRefSpecs: '+refs/heads/*:refs/remotes/origin/* +refs/tags/*:refs/remotes/origin/tags/* +refs/changes/*:refs/remotes/changes/*' ]) Example of using git ls-remote on gerrit repository: git ls-remote git ls-remote https://review.gerrithub.io/rhos-infra/foobar 558aca4bf8d2eb357caa72292abb94b3b87cc41f HEAD a6b8fced01ebdd09930ff75768d3c437567e2f81 refs/changes/78/386678/1 ad71ed9c8a225eb11531322ef928b89ca74eba5e refs/changes/82/386682/1 73969f31bbc57a53b903b3c16ade1b991cbf11f7 refs/changes/82/386682/2 cd404f64f7840bf2d92a830186159c809ff2450e refs/changes/84/386684/1 f05cf74695e6c5731ccbeb5d98de113031ff0c70 refs/changes/84/386684/2 65e65cae35fc55779db0afe56e9bd28554e5c074 refs/changes/85/386685/1 c96845ab149d8f1908f46ad279088e4fb1a77dae refs/changes/85/386685/2 89fbd1f054b2d1f3d0c417235b0e37299a36c078 refs/
[JIRA] (JENKINS-48721) I/O error writing PNG file
Title: Message Title Sorin Sbarnea edited a comment on JENKINS-48721 Re: I/O error writing PNG file We got a very similar error after upgrading our Jenkins from 2.73 LTS to 2.89 LTS.See log at [ https://gist.github.com/ssbarnea/aec8ea4500c1103c2611bea556a81c31 ]Any idea what is causing it and if there is a workaround? For the moment we disabled the graph generation inside BFA config. Looking at the trace I have reasons to believe that is not a BFA bug. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48721) I/O error writing PNG file
Title: Message Title Sorin Sbarnea commented on JENKINS-48721 Re: I/O error writing PNG file We got a very similar error after upgrading our Jenkins from 2.73 LTS to 2.89 LTS. See log at https://gist.github.com/ssbarnea/aec8ea4500c1103c2611bea556a81c31 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50352) gerit-plugin is not yet published as a plugin
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-50352 gerit-plugin is not yet published as a plugin Issue Type: Task Assignee: lucamilanesio Components: gerrit-plugin Created: 2018-03-22 21:47 Priority: Critical Reporter: Sorin Sbarnea It seems that gerit-plugin is not published as a plugin, so the only way to install it is for the user to compile it locally and upload the gerrit-plugin.hpi to the jenkins server. Even if the plugin is not considered stable, it should be published to Jenkins update sites and marked as experimental. PS. I tried to add support for gerrit-plugin inside jenkins-job-builder but my CR was blocked by this bug. Add Comment
[JIRA] (JENKINS-41866) Robot Framework creates artifacts owned by root user
Title: Message Title Sorin Sbarnea closed an issue as Cannot Reproduce This is clearly not a bug and a local configuration mistake on you Jenkins. Jenkins user should never be able to gain root access, or to create files owned by other user, and on correctly configured system it does not. Jenkins / JENKINS-41866 Robot Framework creates artifacts owned by root user Change By: Sorin Sbarnea Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issu
[JIRA] (JENKINS-50143) BFA documents multi-line match example that does not work
Title: Message Title
Sorin Sbarnea updated an issue
Jenkins / JENKINS-50143
BFA documents multi-line match example that does not work
Change By:
Sorin Sbarnea
Documentation of the plugin from [https://wiki.jenkins-ci.org/display/JENKINS/Build+Failure+Analyzer] states that user can use a pattern like below for matching multi-lines. {code:java} some words here(.*\s)and some words here {code} Testing with latest release of the plugin from Jenkins proved that the multiline match does never happen.In fact I was unable to create any pattern that matches more than one line.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50143) BFA documents multi-line match example that does not work
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-50143 BFA documents multi-line match example that does not work Issue Type: Task Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 2018-03-13 13:59 Priority: Critical Reporter: Sorin Sbarnea Documentation of the plugin from https://wiki.jenkins-ci.org/display/JENKINS/Build+Failure+Analyzer states that user can use a pattern like below for matching multi-lines. some words here(.*\s)and some words here Testing with latest release of the plugin from Jenkins proved that the multiline match does never happen. In fact I was unable to create any pattern that matches more than one line. Add Comment
[JIRA] (JENKINS-49983) NullPointerException from gerrit plugin due to lack of configuration
Title: Message Title Sorin Sbarnea commented on JENKINS-49983 Re: NullPointerException from gerrit plugin due to lack of configuration This happens when you configure gerrit without authetication, which is ok for reading until you attempt to add a comment. The normal behaviour would be to have a clear message that sounds like "Failed to perform xxx as this requires authentication" instead NullPointerException stacktrace. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49983) NullPointerException from gerrit plugin due to lack of configuration
Title: Message Title Sorin Sbarnea updated an issue Jenkins / JENKINS-49983 NullPointerException from gerrit plugin due to lack of configuration Change By: Sorin Sbarnea Priority: Critical Minor Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49985) hudson.remoting.ProxyException: org.codehaus.groovy.runtime.typehandling.GroovyCastException: Cannot cast object '{"labels":{"Verified":1}}' with class 'com.google.gson.JsonObje
Title: Message Title
Sorin Sbarnea created an issue
Jenkins / JENKINS-49985
hudson.remoting.ProxyException: org.codehaus.groovy.runtime.typehandling.GroovyCastException: Cannot cast object '{"labels":{"Verified":1}}' with class 'com.google.gson.JsonObject' to class 'com.google.gson.JsonElement'
Issue Type:
Task
Assignee:
lucamilanesio
Components:
gerrit-plugin
Created:
2018-03-07 12:42
Priority:
Critical
Reporter:
Sorin Sbarnea
Error while trying to add Verified label to Gerrit.
hudson.remoting.ProxyException: org.codehaus.groovy.runtime.typehandling.GroovyCastException: Cannot cast object '{"labels":{"Verified":1}}' with class 'com.google.gson.JsonObject' to class 'com.google.gson.JsonElement'
at org.codehaus.groovy.runtime.typehandling.DefaultTypeTransformation.continueCastOnSAM(DefaultTypeTransformation.java:405)
at org.codehaus.groovy.runtime.typehandling.DefaultTypeTransformation.continueCastOnNumber(DefaultTypeTransformation.java:319)
at org.codehaus.groovy.runtime.typehandling.DefaultTypeTransformation.castToType(DefaultTypeTransformation.java:232)
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.castToType(ScriptBytecodeAdapter.java:603)
at Unknown.Unknown(Unknown)
at jenkins.plugins.gerrit.workflow.Gerrit.post(jar:file:/var/lib/jenkins/plugins/gerrit/WEB-INF/lib/gerrit.jar!/jenkins/plugins/gerrit/workflow/Gerrit.groovy:69)
at com.cloudbees.groovy.cps.CpsDefaultGroovyMethods.each(CpsDefaultGroovyMethods:2030)
at com.cloudbees.groovy.cps.CpsDefaultGroovyMethods.each(CpsDefaultGroovyMethods:2015)
at com.cloudbees.groovy.cps.CpsDefaultGroovyMethods.each(CpsDefaultGroovyMethods:2056)
at jenkins.plugins.gerrit.workflow.Gerrit.post(jar:file:/var/lib/jenkins/plugins/gerrit/WEB-INF/lib/gerrit.jar!/jenkins/plugins/gerrit/workflow/Gerrit.groovy:66)
at ___cps.transform___(Nativ
[JIRA] (JENKINS-49983) NullPointerException from gerrit plugin due to lack of configuration
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-49983 NullPointerException from gerrit plugin due to lack of configuration Issue Type: Task Assignee: lucamilanesio Components: gerrit-plugin Created: 2018-03-07 12:17 Priority: Critical Reporter: Sorin Sbarnea It seems that the most basic use case of gerrit plugin documented at https://wiki.jenkins.io/display/JENKINS/Gerrit+Code+Review+Plugin does not mention how the user is supposed to configure access to Gerrit server, or even to mention which Gerrit server should be used. java.lang.NullPointerException at com.cloudbees.plugins.credentials.CredentialsProvider.findCredentialById(CredentialsProvider.java:874) at com.cloudbees.plugins.credentials.CredentialsProvider.findCredentialById(CredentialsProvider.java:852) at org.jenkinsci.plugins.credentialsbinding.MultiBinding.getCredentials(MultiBinding.java:151) at org.jenkinsci.plugins.credentialsbinding.impl.UsernamePasswordMultiBinding.bind(UsernamePasswordMultiBinding.java:76) at org.jenkinsci.plugins.credentialsbinding.impl.BindingStep$Execution.start(BindingStep.java:114) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:229) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:108) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:19) at jenkins.plugins.gerrit.workflow.Gerrit.post(jar:file:/var/lib/jenkins/plugins/gerrit/WEB-INF/lib/gerrit.jar!/jenkins/plugins/gerrit/w
[JIRA] (JENKINS-49897) gerrit-plugin pr branch names are incorrectly name
Title: Message Title Sorin Sbarnea updated an issue Jenkins / JENKINS-49897 gerrit-plugin pr branch names are incorrectly name Change By: Sorin Sbarnea Component/s: workflow-multibranch-plugin Component/s: multi-branch-project-plugin (not Pipeline) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49897) gerrit-plugin pr branch names are incorrectly name
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-49897 gerrit-plugin pr branch names are incorrectly name Issue Type: Bug Assignee: lucamilanesio Components: gerrit-plugin Created: 2018-03-03 18:58 Priority: Major Reporter: Sorin Sbarnea It seems that there are some naming problem with how gerrit-plugin is exposing the PR branches to Jenkins. A) On BlueOcean UI PR branches are named "C-123456/2" which is problematic for two reasons: string is too long to be correctly displayed in UI, which allows only ~6 chars. B) BlueOcean: exposed branch name exposes internals of gerrit implementation of temporary branches which is useless to the user "56/123456/2". 56/ prefix is only the last part of the original changeset and used for hashing folder name. last number is the version of the patchset. But from the logical point of view a PR/CR should be a single branch, regardless how many patchsets are build inside it. It makes sense to have a numeric only branch name, like "123456". C) On Classic UI, the PR branch is recognised as a normal branch and not as a PR. The PR tab is not created. Clearly the Classic UI is able to display PR separately because they do this correctly for GitHub based branch sources. Even more funny is that if someone configures two SCM sources on the same multibrach project, one as Gerrit and one as GitHub, the display of PR/CR is made correct. This means that simple existence of GitHub SCM branch make the multibranch display them correctly.
[JIRA] (JENKINS-49897) gerrit-plugin pr branch names are incorrectly name
Title: Message Title Sorin Sbarnea updated an issue Jenkins / JENKINS-49897 gerrit-plugin pr branch names are incorrectly name Change By: Sorin Sbarnea Component/s: multi-branch-project-plugin (not Pipeline) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49767) parsing junit tests can produce huge messages (DDOS)
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-49767 parsing junit tests can produce huge messages (DDOS) Issue Type: Bug Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 2018-02-27 12:18 Priority: Critical Reporter: Sorin Sbarnea It seems that enabling "Treat failed test cases (as indicated by JUnit/xUnit/... publishers) as failure causes." option can cause serious problems because the messages returned have not size limit. We identified messages of over 2MB being returned which would break Gerrit integration making it it fail to post the result due to message size. I think that BFA should cut any message to a reasonable limit (like 4Kb or so) in order to avoid breaking consumers. Add Comment
[JIRA] (JENKINS-49713) gerrit-plugin exposes change-requests as normal branches instead of pull-requests
Title: Message Title Sorin Sbarnea updated an issue Jenkins / JENKINS-49713 gerrit-plugin exposes change-requests as normal branches instead of pull-requests Change By: Sorin Sbarnea It seems that when using gerrit-plugin in combination with multibranch-pipelines, we get all discovered branches as normal branches instead of having them split between real-branches and temporary ones (pull-requests).I am attaching screenshots of a sample github repository and a gerrit sample repository, so it is clearly visible that multibranch-pipeline does treat CRs as branches instead of PRs (they are not displayed in their separated tab).This is also likely to affect the Blue Ocean gui too and it may be a real deal for users that do have lots of production branches and open pull requests. I know for sure that having 5-10 production branches and 5-50 open CRs is not uncommon. Another issue spotted here is that the patchset version is included in the branch name, which is a real issue because it means that a Jenkins will create a new temporary branch for each updated changeset, instead of using a single one with multiple builds. Having the build history in one place is key as it allows users (and reviewers) to see how execution changed in time. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49713) gerrit-plugin exposes change-requests as normal branches instead of pull-requests
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-49713 gerrit-plugin exposes change-requests as normal branches instead of pull-requests Issue Type: Bug Assignee: lucamilanesio Attachments: multibranch-github.png, mutibranch-gerrit.png Components: gerrit-plugin Created: 2018-02-23 10:24 Priority: Major Reporter: Sorin Sbarnea It seems that when using gerrit-plugin in combination with multibranch-pipelines, we get all discovered branches as normal branches instead of having them split between real-branches and temporary ones (pull-requests). I am attaching screenshots of a sample github repository and a gerrit sample repository, so it is clearly visible that multibranch-pipeline does treat CRs as branches instead of PRs (they are not displayed in their separated tab). This is also likely to affect the Blue Ocean gui too and it may be a real deal for users that do have lots of production branches and open pull requests. I know for sure that having 5-10 production branches and 5-50 open CRs is not uncommon.
[JIRA] (JENKINS-49695) Could not fetch branches from source while using Discover open changes
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-49695 Could not fetch branches from source while using Discover open changes Issue Type: Bug Assignee: lucamilanesio Components: gerrit-plugin, workflow-multibranch-plugin Created: 2018-02-22 12:25 Environment: gerrit-plugin-1.1.0 jenkins-2.89.4 Priority: Minor Reporter: Sorin Sbarnea It seems that by default multibranch-pipeline and git-review setup does not discover any branches in gerrit projects, even after adding "Filter by name (with wildcards)" with defaults settings (include *, exclude: ) — which seems to have no effect. Once we add "Discover open changes" to the config, Jenkins starts to discover open branches on gerritbut detection seems to be buggy because I see some failures in the logs: Started [Thu Feb 22 12:15:18 GMT 2018] Starting branch indexing... > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://review.gerrithub.io/pycontribs/powertape > git config remote.origin.url https://review.gerrithub.io/pycontribs/powertape # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://review.gerrithub.io/pycontribs/powertape > git config remote.origin.url https://review.gerrithub.io/pycontribs/powertape # timeout=10 Fetching & pruning origin... Fetching upstream changes from origin > git --version # timeout=10 > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* --
[JIRA] (JENKINS-49692) Could not update folder level actions from source
Title: Message Title Sorin Sbarnea edited a comment on JENKINS-49692 Re: Could not update folder level actions from source It seems that his bug is caused by the missing *.git* suffix on the git repository URL, something that is optional for git clone command, which works with and without it.Documentation states that the parameter is the same as the one used by git clone.Even Gerrit sample project cloning commands do advertise the URLs without .git prefix, exactly the ones that not working with the plugin. I also tested with freestyle and pipeline project types, and both of them work well without the .git suffix on the URLs. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49692) Could not update folder level actions from source
Title: Message Title Sorin Sbarnea commented on JENKINS-49692 Re: Could not update folder level actions from source It seems that his bug is caused by the missing .git suffix on the git repository URL, something that is optional for git clone command, which works with and without it. Documentation states that the parameter is the same as the one used by git clone. Even Gerrit sample project cloning commands do advertise the URLs without .git prefix, exactly the ones that not working with the plugin. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49692) Could not update folder level actions from source
Title: Message Title Sorin Sbarnea updated an issue Jenkins / JENKINS-49692 Could not update folder level actions from source Change By: Sorin Sbarnea Environment: gerrit-plugin-1.1.0 jenkins-2.89.4 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49692) Could not update folder level actions from source
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-49692 Could not update folder level actions from source Issue Type: Bug Assignee: lucamilanesio Components: gerrit-plugin, workflow-multibranch-plugin Created: 2018-02-22 11:23 Environment: gerrit-plugin-1.1.0 Priority: Major Reporter: Sorin Sbarnea It seems that after configuring a new Multibranch Pipeline project with Gerrit SCM using HTTPS as the source, user would get the exception below while trying to scan for branches: [Thu Feb 22 11:04:09 UTC 2018] Starting branch indexing... ERROR: [Thu Feb 22 11:04:09 UTC 2018] Could not update folder level actions from source dc268e61-3582-471b-97d0-d30b9a99a4a4 java.lang.NullPointerException at jenkins.scm.api.trait.SCMSourceContext.withTraits(SCMSourceContext.java:245) at jenkins.plugins.gerrit.AbstractGerritSCMSource.retrieveActions(AbstractGerritSCMSource.java:214) at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:746) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:591) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:276) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:978) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) [Thu Feb 22 11:04:09 UTC 2018] Finished branch indexing. Indexing took 14 ms FATAL: Failed to recompute children of test-jjb-multibranch java.lang.NullPointerEx
[JIRA] (JENKINS-46324) Support for ConsoleNote
Title: Message Title Sorin Sbarnea commented on JENKINS-46324 Re: Support for ConsoleNote Any updates on the ansicolor issue? This become the No1 reason that prevents adoption of the blueocean UI: nobody wants to lose ansicolor. I am in a position when nobody wants to use blueocean because lack of coloring and where I cannot disable ansibecolor on old ui. We really need a solution that works for both user interfaces. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46290) Project checkout fails (ERROR: Could not determine exact tip revision of master)
Title: Message Title Sorin Sbarnea reopened an issue I am reopening the issue because I found a way to replicate the issue: this happens when there was a forced push on the git server. The client needs to be able to detect this and to abort the build probably? Also, I suspect similar thing may happen if the workspace is not cleanup and there is a forced push on remote git. To prevent a permanent failure of all future jobs we need an option to perform a forced pull when such error occurs — as in a self-repairing local clone. Jenkins / JENKINS-46290 Project checkout fails (ERROR: Could not determine exact tip revision of master) Change By: Sorin Sbarnea Resolution: Incomplete Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49463) jenkins needs a DRY mode which disables schedulers
Title: Message Title Sorin Sbarnea updated an issue Jenkins / JENKINS-49463 jenkins needs a DRY mode which disables schedulers Change By: Sorin Sbarnea At this moment is impossible to keep a hot-swap backup Jenkins instance running because all schedulers will start builds.The workaround of disabling jobs in order to prevent them from starting on a schedule does work only for the most basic deployments, ones that probably do not need a backup. * production may have disabled jobs on normal use, disabling all on backup copy would prevent us from enabling back the correct ones if needed. * disabled jobs cannot be manually triggered by users, it means that if they want to run them on the 2nd server, they need to enable them.The only safe way to enable this is to add a DRY option that tells Jenkins to: * not trigger any timer based schedulers (just ignore them) * not trigger on incoming SCM changes (silent skip) * allow only manual job triggering * skip sending emailsAs it can be seen some of these features depend on plugins and it would be up to the plugin authors to implement this feature. Still, the core Jenkins needs to be able to expose this "DRY" property.Ideally this property should be configurable without having to restart Jenkins so we can implement a failover service from main Jenkins master to secondary one. Still, if there are technical reasons which would not make this possible, even a JAVA_OPTS option would be acceptable. Current workarounds * job timers/schedulers - no workaround other than disabling all the jobs on secondary server which can be a serious issue for those using configuration management and lots of jobs. * email delivery can be prevented at firewall level, really ugly and with side effects on logs * gerrit triggers can be configured to be offline which means that will not trigger new builds but they can be used to manually trigger specific changesets. Bad part is that this means config change which would make a sync with primary server much more complex as we would have to patch the config. Add Comment
[JIRA] (JENKINS-49463) jenkins needs a DRY mode which disables schedulers
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-49463 jenkins needs a DRY mode which disables schedulers Issue Type: Epic Assignee: Unassigned Components: core Created: 2018-02-08 17:51 Priority: Major Reporter: Sorin Sbarnea At this moment is impossible to keep a hot-swap backup Jenkins instance running because all schedulers will start builds. The workaround of disabling jobs in order to prevent them from starting on a schedule does work only for the most basic deployments, ones that probably do not need a backup. production may have disabled jobs on normal use, disabling all on backup copy would prevent us from enabling back the correct ones if needed. disabled jobs cannot be manually triggered by users, it means that if they want to run them on the 2nd server, they need to enable them. The only safe way to enable this is to add a DRY option that tells Jenkins to: not trigger any timer based schedulers (just ignore them) not trigger on incoming SCM changes (silent skip) allow only manual job triggering skip sending emails As it can be seen some of these features depend on plugins and it would be up to the plugin authors to implement this feature. Still, the core Jenkins needs to be able to expose this "DRY" property. Ideally this property should be configurable without having to restart Jenkins so we can implement a failover service from main Jenkins master to
[JIRA] (JENKINS-1267) cc.xml reports failure for last build, although the last build was unstable/successful
Title: Message Title Sorin Sbarnea updated JENKINS-1267 Jenkins / JENKINS-1267 cc.xml reports failure for last build, although the last build was unstable/successful Change By: Sorin Sbarnea Status: Closed In Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-1267) cc.xml reports failure for last build, although the last build was unstable/successful
Title: Message Title Sorin Sbarnea commented on JENKINS-1267 Re: cc.xml reports failure for last build, although the last build was unstable/successful Kohsuke Kawaguchi, now after 9 years, could we revise that decision and start to expose this information inside cc.xml files? There is nothing preventing us from exposing the extended status as a new property. The reality is that for big projects it is normal to have unstable builds because you always have bugs that are not sorted. Also this practice is important for test driven development, where we are supposed to add tests for bugs before fixing them. Fixing a bug could take, well, years or forever. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33022) Allow Git shallow clone in Multibranch pipeline
Title: Message Title Sorin Sbarnea commented on JENKINS-33022 Re: Allow Git shallow clone in Multibranch pipeline Somehow it seems that adding the exception is not possible in all cases. I get the same exception and but I the Process Script Approval does not prompt me to add it, and as you know it has not list that I could manually update. Due to this I raised https://issues.jenkins-ci.org/browse/JENKINS-42860 If you have a hint on how can I address this it would be extremely useful. I only hope it would NOT involve patching some files on Jenkins master because these pipeline jobs do run on multiple masters (at least 4) and on some of them I do not even have direct access. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42099) Support for API keys instead of username+password
Title: Message Title Sorin Sbarnea commented on JENKINS-42099 Re: Support for API keys instead of username+password How about webhook + token? The reality is that most big deployments are using some form of SSO with 2FA which renders username/password authentication useless. The user trying to configure Jenkins is almost not sure an admin on the IM server so he cannot create new accounts. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22660) More flexible UI for approved signatures
Title: Message Title Sorin Sbarnea commented on JENKINS-22660 Re: More flexible UI for approved signatures Jesse Glick Do we need to restart Jenkins when we update scriptApproval.xml? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25804) Whitelisted signature presets for Java standard APIs and Jenkins core APIs
Title: Message Title Sorin Sbarnea commented on JENKINS-25804 Re: Whitelisted signature presets for Java standard APIs and Jenkins core APIs I also have a problem related to this, It seems that I need to add "hudson.plugins.git.GitSCM getBranches" because my jobs fail with this error: org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches The big problem is that is currently impossible to approve these because this is never reaching the scriptApproval page, which also does not allow us to introduce free-form text. How to solve this? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41654) Please release a new version with virtualenv 15.1.0 bundled, to support Python 3.6
Title: Message Title Sorin Sbarnea commented on JENKINS-41654 Re: Please release a new version with virtualenv 15.1.0 bundled, to support Python 3.6 I would that this is an essential fix, not only for Python 3.6. For example due to the outdated virtualenv that is used by shiningpanda we are forced to introduce a pip and setuptools upgrade as part of each job because some python packages are failing to install with the ancient default pip/setuptools installed by default. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-2885) Not all jobs show-up in cc.xml report
Title: Message Title Sorin Sbarnea commented on JENKINS-2885 Re: Not all jobs show-up in cc.xml report Please do NOT delete the cc.xml, it is extremely useful because currently is the only standardized API implemented by most CI servers. Everyone supports it and there are lots of tools consuming it. Even if Jenkins is the leader, it should not break so many tools by removing it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37817) checkout scm should be able to override extensions/settings
Title: Message Title Sorin Sbarnea commented on JENKINS-37817 Re: checkout scm should be able to override extensions/settings Any updates on this? I find really confusing that the getBranches permission cannot be approved at never reaches the Script approval list. Have a look at this sample pipeline that replicates the error: https://github.com/pycontribs/powertape/blob/master/Jenkinsfile#L72 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37322) Pipeline documentation missing archiveArtifact documetnation
Title: Message Title Sorin Sbarnea updated an issue Jenkins / JENKINS-37322 Pipeline documentation missing archiveArtifact documetnation Change By: Sorin Sbarnea When you go to [ http://jenkins_install/job/some_pipeline_job/pipeline-syntax/html ] or [https://github.com/jenkinsci/pipeline-plugin/blob/master/TUTORIAL.md] you get a page documenting the DSL in Jenkinsfile.'archive' is listed as a deprecated step. Users are told to use 'archiveArtifacts' instead, but it's not actually documented anywhere on the page.Sorry if the component is wrong, it was hard to choose. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37322) Pipeline documentation missing archiveArtifact documetnation
Title: Message Title Sorin Sbarnea commented on JENKINS-37322 Re: Pipeline documentation missing archiveArtifact documetnation Any updates on this? Finding anything related to pipelines seems to be a real struggle as writing and linking documentation seems to be an implied step in developing. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42860) RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches
Title: Message Title Sorin Sbarnea updated an issue Jenkins / JENKINS-42860 RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches Change By: Sorin Sbarnea Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42860) RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-42860 RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches Issue Type: Improvement Assignee: Sam Gleske Components: github-oauth-plugin, github-organization-folder-plugin Created: 2017/Mar/16 8:57 PM Environment: jenkins instance configured with github organization plugin and github authorization too. Priority: Critical Reporter: Sorin Sbarnea It seems that I get this exception which is NOT logged inside the script approver which means there is not way to approve it. org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches This happened with this pipeline https://github.com/pycontribs/powertape/blob/master/Jenkinsfile Now, the interesting thing is that if you configure a this project in jenkins using the pipeline type of of job and setting the source as SCM, it will work. So this problem is specific to this way of configuring the jobs.
[JIRA] (JENKINS-41200) Developer can see ANSI color in log file
Title: Message Title Sorin Sbarnea commented on JENKINS-41200 Re: Developer can see ANSI color in log file I would not consider the lack of ANSI support as minor issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41200) Developer can see ANSI color in log file
Title: Message Title Sorin Sbarnea edited a comment on JENKINS-41200 Re: Developer can see ANSI color in log file I would not consider the lack of ANSI support as a * minor * issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42779) groovy.lang.MissingFieldException: No such field: binding for class: WorkflowScript
Title: Message Title
Sorin Sbarnea created an issue
Jenkins / JENKINS-42779
groovy.lang.MissingFieldException: No such field: binding for class: WorkflowScript
Issue Type:
Improvement
Assignee:
Unassigned
Components:
pipeline
Created:
2017/Mar/14 11:15 PM
Priority:
Critical
Reporter:
Sorin Sbarnea
I tried to print all pipeline variables in a loop and I got an exception from groovy.
// put this inside stage block:
for (k in this.binding.variables) {
try {
v = this.binding.variables[k]
println "$k = $v";
}
catch(Exception ex) {
println("Catching the exception: ${ex}");
}
}
groovy.lang.MissingFieldException: No such field: binding for class: WorkflowScript
at groovy.lang.MetaClassImpl.getAttribute(MetaClassImpl.java:2823)
at groovy.lang.MetaClassImpl.getAttribute(MetaClassImpl.java:3759)
at org.codehaus.groovy.runtime.InvokerHelper.getAttribute(InvokerHelper.java:145)
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getField(ScriptBytecodeAdapter.java:306)
at org.kohsuke.groovy.sandbox.impl.Checker$6.call(Checker.java:325)
at org.kohsuke.groovy.sandbox.GroovyInterceptor.onGetAttribute(GroovyInterceptor.java:80)
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetAttribute(SandboxInterceptor.java:380)
at org.kohsuke.groovy.sandbox.impl.Checker$6.call(Checker.java:322)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetAttribute(Checker.java:319)
at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getAttribute(SandboxInvoker.java
[JIRA] (JENKINS-28722) Integrate the Build Failure Analyzer plugin with Claim plugin
Title: Message Title Sorin Sbarnea commented on JENKINS-28722 Re: Integrate the Build Failure Analyzer plugin with Claim plugin Any updates on this? I would really be useful to see this fixed. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42755) BFA fails to catch pipeline related exceptions
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-42755 BFA fails to catch pipeline related exceptions Issue Type: Improvement Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 2017/Mar/14 2:15 PM Priority: Critical Reporter: Sorin Sbarnea Here is an interesting bug related to BFA and pipelines. When the job runs BFA fails to spot the exception as this exceptions seems to reach stdout after BFA runs. If I force the BFA to rescan the builds it will spot it. I find this behaviour confusing, can we fix it? [Pipeline] } [Pipeline] // timestamps [Pipeline] End of Pipeline [BFA] Scanning build for known causes... [BFA] No failure causes found [BFA] Done. 0s org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method groovy.lang.GroovyObject invokeMethod java.lang.String java.lang.Object (org.jenkinsci.plugins.workflow.cps.CpsClosure2 scm java.util.LinkedHashMap) at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectMethod(StaticWhitelist.java:183) at
[JIRA] (JENKINS-37116) Add support for Jenkins Pipeline to the shiningpanda-plugin
Title: Message Title Sorin Sbarnea commented on JENKINS-37116 Re: Add support for Jenkins Pipeline to the shiningpanda-plugin While trying to find a better way to use virtualenvs inside (bigger) pipelines, I found encountered this https://codegists.com/code/jenkins-pipeline-dsl/ and https://codegists.com/snippet/groovy/build-jobgroovy_joebew42_groovy which seems to use two interesting syntaxes. Still I was not able to identify which plugins do expose these new commands. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40625) Handling virtualenv and nodeenv in jenkins pipeline plugin
Title: Message Title Sorin Sbarnea updated an issue Jenkins / JENKINS-40625 Handling virtualenv and nodeenv in jenkins pipeline plugin Change By: Sorin Sbarnea Labels: pipeline virtualenv Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40625) Handling virtualenv and nodeenv in jenkins pipeline plugin
Title: Message Title Sorin Sbarnea commented on JENKINS-40625 Re: Handling virtualenv and nodeenv in jenkins pipeline plugin Oleg Nenashev, I think that the user noted a real issue with the pipelines, one that we are ware about. Because this is a very common use case I think Jenkins should provide clear clear documentation about it. Reactivating the venv on each sh line is insane, hard to maintain and likely to break. We need to find a nice and clean solution for this, one that benefits from the power of DSL. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42682) parameters values should be able to expand values of ther parameters
Title: Message Title
Sorin Sbarnea created an issue
Jenkins / JENKINS-42682
parameters values should be able to expand values of ther parameters
Issue Type:
Improvement
Assignee:
Unassigned
Attachments:
Jenkins 2017-03-10 20-45-05.png
Components:
core
Created:
2017/Mar/10 8:53 PM
Labels:
parameters
Priority:
Major
Reporter:
Sorin Sbarnea
Is seem that currently it is impossible to user values of already defined parameters in order to simplify parameter usage and avoid repetition (DRY principle). I will give this bash example in order to explain value expansions as they work in bash (probably the most known syntax.
#!/bin/bash
PARAM1="AAA"
PARAM2="Some $AAA text"
PARAM3="Other ${AAA} text"
PARAM4="3th example which resolves ${AAA:-ZZZ} as ZZZ when AAA is not defined"
If we want to put these 4 parameters in Jenkins we have no option for allowing the user to than only the value of PARAM1, because Jenkins does not perform variable expansion of the default values. You may wonder why this is so important because sounds like a really weird use case. For this reason I will provide one screenshot from our current build parameters. As you can imagine we do have other branches for other numeric values than "11.0". At this moment if a user wants to build a specific branch the
[JIRA] (JENKINS-37116) Add support for Jenkins Pipeline to the shiningpanda-plugin
Title: Message Title Sorin Sbarnea commented on JENKINS-37116 Re: Add support for Jenkins Pipeline to the shiningpanda-plugin I don't know if this helps others but because of the multiple bugs related to shining panda, including the jobs executed on parallel, we decided to replace it with shell script and manage the virtualenv management ourselves. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32715) virtualenv creation blows up on concurrent jobs started at the same-ish time
Title: Message Title Sorin Sbarnea updated an issue Jenkins / JENKINS-32715 virtualenv creation blows up on concurrent jobs started at the same-ish time Change By: Sorin Sbarnea Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20058) Ability to change the favicon for Jenkins
Title: Message Title Sorin Sbarnea edited a comment on JENKINS-20058 Re: Ability to change the favicon for Jenkins How did you inject the _javascript_ code into Jenkins? I really don't to end-up with GreaseMonkey -like client plugins.Having the same icon on all Jenkins instances is insane from the UX point of view. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20058) Ability to change the favicon for Jenkins
Title: Message Title Sorin Sbarnea commented on JENKINS-20058 Re: Ability to change the favicon for Jenkins How did you inject the _javascript_ code into Jenkins? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34273) Extend quantity configuration to Pipeline lock step
Title: Message Title Sorin Sbarnea edited a comment on JENKINS-34273 Re: Extend quantity configuration to Pipeline lock step Thanks for fixing this. I observed that currently there is no way to configure the quantity of specific resource and we are forced to add lots of duplicated resources in order to overcome this. Still this does not scale and after 5-10 clones it becomes too hard to add additional. Due to this I raise raised JENKINS-42339 for adding a quantity inside the configure screen. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34273) Extend quantity configuration to Pipeline lock step
Title: Message Title Sorin Sbarnea commented on JENKINS-34273 Re: Extend quantity configuration to Pipeline lock step Thanks for fixing this. I observed that currently there is no way to configure the quantity of specific resource and we are forced to add lots of duplicated resources in order to overcome this. Still this does not scale and after 5-10 clones it becomes too hard to add additional. Due to this I raise JENKINS-42339 for adding a quantity inside the configure screen. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42339) each lockable resource should have a quantity field which defaults to 1
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-42339 each lockable resource should have a quantity field which defaults to 1 Issue Type: Improvement Assignee: Unassigned Components: lockable-resources-plugin Created: 2017/Feb/27 10:09 AM Priority: Major Reporter: Sorin Sbarnea It seems the current implementation for the quantity does require jenkins administrators to define different duplicated/identical resources because they cannot define a quantity. This is a serious scalability resources which make harder to implement resources locking for resources that are supposed to be in bigger numbers like: total RAM available or total number of VCPUs. For example in our testing cloud we do have 300 GB RAM and 300 VCPU limit. Now is effectively impossible to use the locking plugin for this because we would have to create 600 resource entries in the config, probably the browser will crash before we would be able to add all of these Add Comment
[JIRA] (JENKINS-41858) Label + Quantity is sometimes not honored
Title: Message Title Sorin Sbarnea closed an issue as Duplicate Jenkins / JENKINS-41858 Label + Quantity is sometimes not honored Change By: Sorin Sbarnea Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41486) the timestamper format is not rememembered across jobs
Title: Message Title Sorin Sbarnea updated an issue Jenkins / JENKINS-41486 the timestamper format is not rememembered across jobs Change By: Sorin Sbarnea Attachment: sahara-tempest-rhos-coreci #137_rhos-7.0-patches Console [Jenkins] 2017-02-22 16-33-55.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-41486) the timestamper format is not rememembered across jobs
Title: Message Title Sorin Sbarnea commented on JENKINS-41486 Re: the timestamper format is not rememembered across jobs Steven G Brown I was able to identify the bug: the cookie is saved but it is useless because it is saved with the full job-execution path. So the value is remembered for /foo-job/123 which is making it kinda useless. I do have hundreds of different job names with thousands of executions and I was expecting to remember this preference for the entire jenkins instance ( path = / ) not for a specific job. Also the current implementation has another side-effect bug: it does clutter jenkins instance with cookies for each job, and is contributing to another known jenkins bug when the max cookie size limit is reached. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41279) bfa graphs apear below the bottom of the left sidebard instead of the left side
Title: Message Title Sorin Sbarnea closed an issue as Fixed Jenkins / JENKINS-41279 bfa graphs apear below the bottom of the left sidebard instead of the left side Change By: Sorin Sbarnea Status: Open Closed Assignee: Tomas Westling Sorin Sbarnea Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33039) linenumbers and simple theme are incompatible as output becomes unusable
Title: Message Title Sorin Sbarnea closed an issue as Cannot Reproduce Jenkins / JENKINS-33039 linenumbers and simple theme are incompatible as output becomes unusable Change By: Sorin Sbarnea Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-7887) Inconsistency regarding plugin names inside pluginManger pages
Title: Message Title Sorin Sbarnea closed an issue as Won't Do Jenkins / JENKINS-7887 Inconsistency regarding plugin names inside pluginManger pages Change By: Sorin Sbarnea Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22328) ubuntu switch to jenkins debian distribution fails because: subprocess installed post-installation script returned error exit status 1
Title: Message Title Sorin Sbarnea closed an issue as Cannot Reproduce Jenkins / JENKINS-22328 ubuntu switch to jenkins debian distribution fails because: subprocess installed post-installation script returned error exit status 1 Change By: Sorin Sbarnea Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-7484) Perforce plugin always complaining: Unable to check workspace against depot
Title: Message Title Sorin Sbarnea closed an issue as Cannot Reproduce Jenkins / JENKINS-7484 Perforce plugin always complaining: Unable to check workspace against depot Change By: Sorin Sbarnea Status: Reopened Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27682) SEVERE: Access exception trying to look up email address in Crowd
Title: Message Title Sorin Sbarnea closed an issue as Cannot Reproduce Jenkins / JENKINS-27682 SEVERE: Access exception trying to look up email address in Crowd Change By: Sorin Sbarnea Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22328) ubuntu switch to jenkins debian distribution fails because: subprocess installed post-installation script returned error exit status 1
Title: Message Title Sorin Sbarnea resolved as Cannot Reproduce Jenkins / JENKINS-22328 ubuntu switch to jenkins debian distribution fails because: subprocess installed post-installation script returned error exit status 1 Change By: Sorin Sbarnea Status: Reopened Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-18447) Failed to detect the environment for automatic JDK installation : Windows 2008 Server Slave
Title: Message Title Sorin Sbarnea closed an issue as Cannot Reproduce Jenkins / JENKINS-18447 Failed to detect the environment for automatic JDK installation : Windows 2008 Server Slave Change By: Sorin Sbarnea Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29105) java.io.IOException: Cannot run program
Title: Message Title Sorin Sbarnea closed an issue as Cannot Reproduce Expired: not using Windows anymore so if someone else is able to reproduce the bug feel free to reopen it. Jenkins / JENKINS-29105 java.io.IOException: Cannot run program Change By: Sorin Sbarnea Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@go
[JIRA] (JENKINS-7507) ERROR: Unexpected error in launching a slave - java.net.UnknownHostException
Title: Message Title Sorin Sbarnea closed an issue as Cannot Reproduce Jenkins / JENKINS-7507 ERROR: Unexpected error in launching a slave - java.net.UnknownHostException Change By: Sorin Sbarnea Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-7551) Execute Python script fails with "SyntaxError: invalid syntax" if you have command line parameters
Title: Message Title Sorin Sbarnea closed an issue as Cannot Reproduce Jenkins / JENKINS-7551 Execute Python script fails with "SyntaxError: invalid syntax" if you have command line parameters Change By: Sorin Sbarnea Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9241) maven2: java.lang.IllegalArgumentException: /usr/bin/mvn without lib directory
Title: Message Title Sorin Sbarnea closed an issue as Cannot Reproduce Jenkins / JENKINS-9241 maven2: java.lang.IllegalArgumentException: /usr/bin/mvn without lib directory Change By: Sorin Sbarnea Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-7490) console-parser should get the parsing rules directly from a textbox in the project config
Title: Message Title Sorin Sbarnea closed an issue as Won't Do Jenkins / JENKINS-7490 console-parser should get the parsing rules directly from a textbox in the project config Change By: Sorin Sbarnea Status: In Progress Closed Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-7494) Plugin to show user pictures in hudson: gravatar or images stored on a remote http server
Title: Message Title Sorin Sbarnea closed an issue as Fixed Jenkins / JENKINS-7494 Plugin to show user pictures in hudson: gravatar or images stored on a remote http server Change By: Sorin Sbarnea Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-7433) Violations plugin fails to load pylint result files, throwing an exception
Title: Message Title Sorin Sbarnea updated an issue Jenkins / JENKINS-7433 Violations plugin fails to load pylint result files, throwing an exception Change By: Sorin Sbarnea Summary: Violations plugin fails to load pyling pylint result files, throwing an exception Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-7433) Violations plugin fails to load pylint result files, throwing an exception
Title: Message Title Sorin Sbarnea closed an issue as Cannot Reproduce Jenkins / JENKINS-7433 Violations plugin fails to load pylint result files, throwing an exception Change By: Sorin Sbarnea Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
