Re: Still stuck on older Jenkins because of table-to-div -- what to do?
Hi, The only plugin I am sure of, is the performance-plugin, since I reported that one myself. It shouldn't be dead, since they merged a PR of mine and built a release about a week prior to me reporting this issue... Anyway, I looked into this plugin, but I can't for the life of me figure out how to layout a part of the form as a table -- since imo a part of the form *should* be a table. I'll see if I can find some time to give it another look, but I wouldn't mind if someone gave the current owner a little nudge either... :-) As for the other plugins, the list that is found here (https://issues.jenkins.io/secure/Dashboard.jspa?selectPageId=20741) doesn't have any other plugins that I have installed. It does however have some entries that say they affect the core, which in some instances is then disproved by others -- same with some of the plugins though... Since the original authors didn't come back to report on whether or not the issue is solved, I feel kind of lost on the actual status Maybe someone can look over the issues that are have component 'core' set and correct the component/close the issue? Thanks. Roland On 06.06.2021 16:10, Baptiste Mathus wrote: Hi Roland, Ulli summarized the situation very well. If you can consider providing a more specific list of plugins that you're waiting on, we can probably point you to the right path to get them fixed (become maintainer, pay someone to fix them, etc.). (very personal) rule of thumb: if the plugin has less than ~2 to 3k installs worldwide, there's close to zero chance that somebody steps up if you do not. Cheers Le ven. 4 juin 2021 à 13:44, Ullrich Hafner <mailto:ullrich.haf...@gmail.com>> a écrit : Am 04.06.2021 um 12:51 schrieb Roland Asmann mailto:roland.asm...@gmail.com>>: Hi all, Because of the table-to-div changes in 2.277.1 not working in several plugins, I am still running 2.263.4. Every time I check the list of known plugins that aren't working since this update, the list seems to grow... A different change in Jenkins a couple of years back made us setup a second Jenkins instance, because of projects that weren't able run on the new version. I am still migrating some of those projects and I really don't want to setup a 3rd instance and maintain all 3. So, how do I proceed? Can someone 'force' the plugin developers to update their plugins? No. If a plugin does not yet support 2.277.1 then the plugin is probably not maintained at all anymore. Then it would help if someone who still uses the plugin would volunteer to take over the ownership. This is how our open source model in Jenkins works. Or maybe someone can look some of the plugins over and get them running again? See above. We do not have a support policy for plugins, so if something does not work and the maintainer has no spare time to fix then it is up to the community to help here. And maybe it would be good if someone could check over all open issues in this list (https://issues.jenkins.io/secure/Dashboard.jspa?selectPageId=20741 <https://issues.jenkins.io/secure/Dashboard.jspa?selectPageId=20741>) and see if they are actually still existing/are referencing the correct plugin -- some issues were created saying it was an issue in the core, but the comments later state it was actually a plugin. I really need to know if there are still issues in the core or if it's only in some plugins, so I can decide on how to move on... Thanks. Roland -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com <mailto:jenkinsci-users+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/ff4acd22-e8c5-4dc7-8284-645c5c1375d6n%40googlegroups.com <https://groups.google.com/d/msgid/jenkinsci-users/ff4acd22-e8c5-4dc7-8284-645c5c1375d6n%40googlegroups.com?utm_medium=email_source=footer>. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com <mailto:jenkinsci-users+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/C6997362-A032-4300-B131-9E70A953CDE5%40gmail.com <https://groups.google.com/d/msgid/jenkinsci-users/C6997362-A032-4300-B131-9E70A953CDE5%40gmail.com?utm_medium=email_source=footer>. -- You received this message because you are subscribed to a topic in the Google Groups &q
Still stuck on older Jenkins because of table-to-div -- what to do?
Hi all, Because of the table-to-div changes in 2.277.1 not working in several plugins, I am still running 2.263.4. Every time I check the list of known plugins that aren't working since this update, the list seems to grow... A different change in Jenkins a couple of years back made us setup a second Jenkins instance, because of projects that weren't able run on the new version. I am still migrating some of those projects and I really don't want to setup a 3rd instance and maintain all 3. So, how do I proceed? Can someone 'force' the plugin developers to update their plugins? Or maybe someone can look some of the plugins over and get them running again? And maybe it would be good if someone could check over all open issues in this list (https://issues.jenkins.io/secure/Dashboard.jspa?selectPageId=20741) and see if they are actually still existing/are referencing the correct plugin -- some issues were created saying it was an issue in the core, but the comments later state it was actually a plugin. I really need to know if there are still issues in the core or if it's only in some plugins, so I can decide on how to move on... Thanks. Roland -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/ff4acd22-e8c5-4dc7-8284-645c5c1375d6n%40googlegroups.com.
Re: Matrix in Pipelines
Thanks for the replies. I went with hard-coding the 2 nodes, in the hopes that at some point the matrix will allow use of variables for the value. On 19.10.2020 12:27, 'christop...@googlemail.com' via Jenkins Users wrote: You mean something like a dynamic axis created by a piece of script? I had a similar issue in the past and did not find a way. There might be something with script blocks in a pipeline and dynamic stage-creation with a for-loop. When I remember right I found some examples with google when I investigated this. Roland Asmann schrieb am Montag, 19. Oktober 2020 um 10:16:51 UTC+2: Hi, Thanks for that. I see I forgot to mention something in my original post: The nodes I want to run my job on should come from a label. So I would need to get the 'values' in the matrix-part by figuring out which nodes have this label set... Can I add a simple 1-, maybe 2-line script block in my pipeline to retrieve those values and use them? On 19.10.2020 9:45, 'christop...@googlemail.com' via Jenkins Users wrote: > Hi, > > I don't exactly understand your problem. Please have a look here: > https://www.jenkins.io/blog/2019/11/22/welcome-to-the-matrix/ <https://www.jenkins.io/blog/2019/11/22/welcome-to-the-matrix/> > > you very easily can integrate matrix in a declarative pipeline. Insert > your nodes as an axis of the matrix and add an 'agent' in the stage > doing your job. > > But maybe I missed a point somewhere... > > > Roland Asmann schrieb am Sonntag, 18. Oktober 2020 um 18:23:48 UTC+2: > > Hey everybody, > > I have this job, written as a declarative pipeline, the now needs to > be run on 2 nodes instead of just 1. Before, I would use the > Matrix-Job for that, but I am not quite sure how to do this in my > pipeline... > I searched around a bit and found some example on how to do it with > a scripted pipeline, but I would prefer to stick to the declarative > format -- if possible. The reason for that is that my team is just > learning about pipelines and have just about mastered declarative. I > don't want to throw them in the deep end for scripted yet. > > Is this possible in declarative? If so, tips would be helpful. > If not, at least 1 reply telling me this would also be helpful! ;-) > > Thanks, > Roland > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-users/DLoPOi8U5NI/unsubscribe <https://groups.google.com/d/topic/jenkinsci-users/DLoPOi8U5NI/unsubscribe> <https://groups.google.com/d/topic/jenkinsci-users/DLoPOi8U5NI/unsubscribe <https://groups.google.com/d/topic/jenkinsci-users/DLoPOi8U5NI/unsubscribe>>. > To unsubscribe from this group and all its topics, send an email to > jenkinsci-use...@googlegroups.com > <mailto:jenkinsci-use...@googlegroups.com>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/5d806b70-3cab-463e-a27f-097daaa3679en%40googlegroups.com <https://groups.google.com/d/msgid/jenkinsci-users/5d806b70-3cab-463e-a27f-097daaa3679en%40googlegroups.com> > <https://groups.google.com/d/msgid/jenkinsci-users/5d806b70-3cab-463e-a27f-097daaa3679en%40googlegroups.com?utm_medium=email_source=footer <https://groups.google.com/d/msgid/jenkinsci-users/5d806b70-3cab-463e-a27f-097daaa3679en%40googlegroups.com?utm_medium=email_source=footer>>. -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus <https://www.avast.com/antivirus> -- You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/DLoPOi8U5NI/unsubscribe <https://groups.google.com/d/topic/jenkinsci-users/DLoPOi8U5NI/unsubscribe>. To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.com <mailto:jenkinsci-users+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/12a60d25-485a-4cf3-a237-a45a470ba959n%40googlegroups.com <https://groups.google.com/d/msgid/jenkinsci-users/12a60d25-485a-4cf3-a237-a45a470ba959n%40googlegroups.com?utm_medium=email_source=footer>. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe
Re: Matrix in Pipelines
Hi, Thanks for that. I see I forgot to mention something in my original post: The nodes I want to run my job on should come from a label. So I would need to get the 'values' in the matrix-part by figuring out which nodes have this label set... Can I add a simple 1-, maybe 2-line script block in my pipeline to retrieve those values and use them? On 19.10.2020 9:45, 'christop...@googlemail.com' via Jenkins Users wrote: Hi, I don't exactly understand your problem. Please have a look here: https://www.jenkins.io/blog/2019/11/22/welcome-to-the-matrix/ you very easily can integrate matrix in a declarative pipeline. Insert your nodes as an axis of the matrix and add an 'agent' in the stage doing your job. But maybe I missed a point somewhere... Roland Asmann schrieb am Sonntag, 18. Oktober 2020 um 18:23:48 UTC+2: Hey everybody, I have this job, written as a declarative pipeline, the now needs to be run on 2 nodes instead of just 1. Before, I would use the Matrix-Job for that, but I am not quite sure how to do this in my pipeline... I searched around a bit and found some example on how to do it with a scripted pipeline, but I would prefer to stick to the declarative format -- if possible. The reason for that is that my team is just learning about pipelines and have just about mastered declarative. I don't want to throw them in the deep end for scripted yet. Is this possible in declarative? If so, tips would be helpful. If not, at least 1 reply telling me this would also be helpful! ;-) Thanks, Roland -- You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/DLoPOi8U5NI/unsubscribe <https://groups.google.com/d/topic/jenkinsci-users/DLoPOi8U5NI/unsubscribe>. To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.com <mailto:jenkinsci-users+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/5d806b70-3cab-463e-a27f-097daaa3679en%40googlegroups.com <https://groups.google.com/d/msgid/jenkinsci-users/5d806b70-3cab-463e-a27f-097daaa3679en%40googlegroups.com?utm_medium=email_source=footer>. -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3276e41f-55ad-e86d-28d8-89f8f7e8f2d9%40gmail.com.
Matrix in Pipelines
Hey everybody, I have this job, written as a declarative pipeline, the now needs to be run on 2 nodes instead of just 1. Before, I would use the Matrix-Job for that, but I am not quite sure how to do this in my pipeline... I searched around a bit and found some example on how to do it with a scripted pipeline, but I would prefer to stick to the declarative format -- if possible. The reason for that is that my team is just learning about pipelines and have just about mastered declarative. I don't want to throw them in the deep end for scripted yet. Is this possible in declarative? If so, tips would be helpful. If not, at least 1 reply telling me this would also be helpful! ;-) Thanks, Roland -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/8ebffe59-9ac7-489a-9bf1-388d77ea7289n%40googlegroups.com.
Switching DB in pipeline maven integration plugin
Hey everybody, We have been using this plugin for quite some time, without any issues. Then last week, something changed (I am still not sure what, tbh) and we started to get hanging builds because of Problems connecting to the H2 DB. Searching the net, most solutions said to use an actual DB, so I setup PostgreSQL and reconfigured the plugin to use that. I don't have the final results yet, seeing how the big workload will start during the work week, but I did have a question upfront: The plugin shows that the DB is working and there is some data in there. I would like to know what happens to the old data? It doesn't appear to be moved to the PG Database, but some of the projects I checked do still show things like the built artifacts. Is the plugin using both DBs? Also, do I (at some point) need to delete the old H2, or will this shrink and die on it's own? Thank! Roland -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/117fedcc-6c29-421f-9c4f-27d08c92b916n%40googlegroups.com.
Re: NoSuchFileException on git clone after upgrade to RHEL 8
That seems to have done the trick, thanks! I am a little confused now though, because when I checked all other Linux machines, none of them actually have this part of the locale set! Ah well, it works, so I will make sure to set this on all servers after the update! On 21.06.2020 0:50, Mark Waite wrote: Usually that failure happens because the operating system default locale is not C.UTF-8 but is using the C locale instead. LC_ALL=C.UTF-8 On Sat, Jun 20, 2020, 2:45 PM Roland Asmann <mailto:roland.asm...@gmail.com>> wrote: Hi everybody, My sys-admins at work upgraded one of our servers to RHEL 8 to have me test it before all servers are upgraded. Now most of the jobs I ran on it work, one of them has an issue during cloning. I found out that the error occurs because this repository contains a file with an Umlaut in its name, though this is not an issue on my other slaves that are running RHEL 7 (and one old RHEL 6). I have configured Jenkins to use JGit so I don't have different versions on any slave (we have all kinds of different OSes in our cloud) and the feature set is the same on all slaves. Now, I need to figure out if there is a problem with RHEL 8, the way the server is configured (aka: if the admins are lying to me about the setup being the same as before) or if I need to configure something in Jenkins to make sure JGit can work with Umlauts again. In case it helps, here's the Stacktrace Jenkins logs when it tries to clone the repository: java.nio.file.NoSuchFileException: /workspace/job/._mengengerüst_erstellung_daten.feature8906747275907148543.tmp at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:244) at sun.nio.fs.AbstractFileSystemProvider.delete(AbstractFileSystemProvider.java:103) at java.nio.file.Files.delete(Files.java:1126) at org.eclipse.jgit.util.FileUtils.delete(FileUtils.java:219) Caused: java.io.IOException: Could not delete file /workspace/job/._mengengerüst_erstellung_daten.feature8906747275907148543.tmp at org.eclipse.jgit.util.FileUtils.delete(FileUtils.java:247) at org.eclipse.jgit.util.FileUtils.delete(FileUtils.java:158) at org.eclipse.jgit.dircache.DirCacheCheckout.checkoutEntry(DirCacheCheckout.java:1562) at org.eclipse.jgit.dircache.DirCacheCheckout.doCheckout(DirCacheCheckout.java:589) at org.eclipse.jgit.dircache.DirCacheCheckout.checkout(DirCacheCheckout.java:493) at org.eclipse.jgit.api.CheckoutCommand.call(CheckoutCommand.java:281) Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to slave01t at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1788) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356) at hudson.remoting.Channel.call(Channel.java:998) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146) at sun.reflect.GeneratedMethodAccessor272.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132) at com.sun.proxy.$Proxy94.execute(Unknown Source) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1217) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:125) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:93) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) Caused: org.eclipse.jgit.api.errors.JGitInternalException: Could not delete file /workspace/job/._mengengerüst_erstellung_daten.feature8906747275907148543.tmp at org.eclipse.jgit.api.CheckoutCommand.call(CheckoutCommand.java:340) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.doCheckoutWithResetAndRetry(JGitAPIImpl
NoSuchFileException on git clone after upgrade to RHEL 8
Hi everybody, My sys-admins at work upgraded one of our servers to RHEL 8 to have me test it before all servers are upgraded. Now most of the jobs I ran on it work, one of them has an issue during cloning. I found out that the error occurs because this repository contains a file with an Umlaut in its name, though this is not an issue on my other slaves that are running RHEL 7 (and one old RHEL 6). I have configured Jenkins to use JGit so I don't have different versions on any slave (we have all kinds of different OSes in our cloud) and the feature set is the same on all slaves. Now, I need to figure out if there is a problem with RHEL 8, the way the server is configured (aka: if the admins are lying to me about the setup being the same as before) or if I need to configure something in Jenkins to make sure JGit can work with Umlauts again. In case it helps, here's the Stacktrace Jenkins logs when it tries to clone the repository: java.nio.file.NoSuchFileException: /workspace/job/._mengengerüst_erstellung_daten.feature8906747275907148543.tmp at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:244) at sun.nio.fs.AbstractFileSystemProvider.delete(AbstractFileSystemProvider.java:103) at java.nio.file.Files.delete(Files.java:1126) at org.eclipse.jgit.util.FileUtils.delete(FileUtils.java:219) Caused: java.io.IOException: Could not delete file /workspace/job/ ._mengengerüst_erstellung_daten.feature8906747275907148543.tmp at org.eclipse.jgit.util.FileUtils.delete(FileUtils.java:247) at org.eclipse.jgit.util.FileUtils.delete(FileUtils.java:158) at org.eclipse.jgit.dircache.DirCacheCheckout.checkoutEntry(DirCacheCheckout.java:1562) at org.eclipse.jgit.dircache.DirCacheCheckout.doCheckout(DirCacheCheckout.java:589) at org.eclipse.jgit.dircache.DirCacheCheckout.checkout(DirCacheCheckout.java:493) at org.eclipse.jgit.api.CheckoutCommand.call(CheckoutCommand.java:281) Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to slave01t at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1788) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356) at hudson.remoting.Channel.call(Channel.java:998) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146) at sun.reflect.GeneratedMethodAccessor272.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132) at com.sun.proxy.$Proxy94.execute(Unknown Source) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1217) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:125) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:93) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) Caused: org.eclipse.jgit.api.errors.JGitInternalException: Could not delete file /workspace/job/ ._mengengerüst_erstellung_daten.feature8906747275907148543.tmp at org.eclipse.jgit.api.CheckoutCommand.call(CheckoutCommand.java:340) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.doCheckoutWithResetAndRetry(JGitAPIImpl.java:350) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.access$100(JGitAPIImpl.java:142) at org.jenkinsci.plugins.gitclient.JGitAPIImpl$1.execute(JGitAPIImpl.java:317) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:161) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:154) at hudson.remoting.UserRequest.perform(UserRequest.java:211) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at
Re: CI with Git in Jenkins
I'm sorry, I guess I wasn't quite clear on what I meant with this last
question.
What I want to know is if the consensus is to put the *empty* definition
of the polling in the Jenkinfile (so that configuring a single pipeline
works) even when using multibranch pipelines?
On 30.03.2020 18:55, Mark Waite wrote:
On Mon, Mar 30, 2020 at 10:03 AM Roland Asmann <mailto:roland.asm...@gmail.com>> wrote:
Thanks for the explanation. I do agree, I just thought it a bit weird
that there was a difference in behavior...
I still would like to know, what the consensus is to writing the
Jenkinsfile: add polling or not?
Consensus is to not add polling. The "polling must die" blog post is
still applicable, even with Pipeline. Much better to find a way to have
the git repository notify Jenkins that a commit has arrived, rather than
having Jenkins periodically ask if a commit has arrived.
Major git providers (GitHub, Bitbucket, GitLab, Gitea) provide web hooks
that will notify Jenkins. Many of those webhooks are even automatically
managed by Jenkins. Jenkins servers behind firewalls can use web hook
routing tools to receive notifications inside the firewall from a git
hosting service outside the firewall.
Mark Waite
Thanks.
On 25.03.2020 14:53, Mark Waite wrote:
> Multibranch pipelines assume that you want to build all branches
that
> include a Jenkinsfile any time the notification is received through
> notifyCommit or through a Web Hook. If you do not want one or more
> branches built on multibranch pipelines, you'll need to exclude
them.
> The Basic Branch Build Strategies plugin (
>
https://github.com/jenkinsci/basic-branch-build-strategies-plugin/blob/master/docs/user.adoc)
> provides many branch selection options.
>
> On Wed, Mar 25, 2020 at 7:39 AM Roland Asmann
mailto:roland.asm...@gmail.com>
> <mailto:roland.asm...@gmail.com
<mailto:roland.asm...@gmail.com>>> wrote:
>
> Hi everybody,
>
> Way-back-when, Kohsuke wrote this post about how to setup CI with
> Git in Jenkins:
>
https://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/
>
> I have been using this in most my builds since and am still
trying
> to get all colleagues to do the same (don't ask, my company
can be
> difficult sometimes). Anyway, the other day I noticed that in
one of
> my Jenkinsfiles, I forgot to activate the SCM polling.
However, this
> project had been building on git pushes since the start!
>
> Doing some testing on my own, I came to the following conclusion:
> - Non-pipeline jobs all need to have the polling activated to
react
> to the Git hook
> - Single pipeline jobs also need to have polling activated
> - Multibranch pipelines **don't** need to have polling activated,
> they just build whenever the git hook sends its request to
Jenkins
>
> Now, my question is, is this behavior correct? Does it mean
that for
> multibranch pipelines, I **can't** NOT do CI? (Except for
removing
> the hook, but that might influence other builds as well!) Is this
> actual behavior documented somewhere and did I just miss this
> information?
>
> And what is now the correct way to setup CI? Should I still
add the
> polling in my Jenkinsfile or, if I am sure I will be using a
> multibranch pipeline, just leave it out?
>
> Thanks.
>
> Roland
>
> --
> You received this message because you are subscribed to the
Google
> Groups "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to jenkinsci-users+unsubscr...@googlegroups.com
<mailto:jenkinsci-users%2bunsubscr...@googlegroups.com>
> <mailto:jenkinsci-users+unsubscr...@googlegroups.com
<mailto:jenkinsci-users%2bunsubscr...@googlegroups.com>>.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/jenkinsci-users/828bed5a-dda6-4782-82d9-6834b1f0e074%40googlegroups.com
>
<https://groups.google.com/d/msgid/jenkinsci-users/828bed5a-dda6-4782-82d9-6834b1f0e074%40googlegroups.com?utm_medium=email_source=footer>.
>
> --
> You received this message because you are subscribed to a topic
in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
>
https://groups.google.com/d/
Re: CI with Git in Jenkins
Thanks for the explanation. I do agree, I just thought it a bit weird that there was a difference in behavior... I still would like to know, what the consensus is to writing the Jenkinsfile: add polling or not? Thanks. On 25.03.2020 14:53, Mark Waite wrote: Multibranch pipelines assume that you want to build all branches that include a Jenkinsfile any time the notification is received through notifyCommit or through a Web Hook. If you do not want one or more branches built on multibranch pipelines, you'll need to exclude them. The Basic Branch Build Strategies plugin ( https://github.com/jenkinsci/basic-branch-build-strategies-plugin/blob/master/docs/user.adoc) provides many branch selection options. On Wed, Mar 25, 2020 at 7:39 AM Roland Asmann <mailto:roland.asm...@gmail.com>> wrote: Hi everybody, Way-back-when, Kohsuke wrote this post about how to setup CI with Git in Jenkins: https://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/ I have been using this in most my builds since and am still trying to get all colleagues to do the same (don't ask, my company can be difficult sometimes). Anyway, the other day I noticed that in one of my Jenkinsfiles, I forgot to activate the SCM polling. However, this project had been building on git pushes since the start! Doing some testing on my own, I came to the following conclusion: - Non-pipeline jobs all need to have the polling activated to react to the Git hook - Single pipeline jobs also need to have polling activated - Multibranch pipelines **don't** need to have polling activated, they just build whenever the git hook sends its request to Jenkins Now, my question is, is this behavior correct? Does it mean that for multibranch pipelines, I **can't** NOT do CI? (Except for removing the hook, but that might influence other builds as well!) Is this actual behavior documented somewhere and did I just miss this information? And what is now the correct way to setup CI? Should I still add the polling in my Jenkinsfile or, if I am sure I will be using a multibranch pipeline, just leave it out? Thanks. Roland -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com <mailto:jenkinsci-users+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/828bed5a-dda6-4782-82d9-6834b1f0e074%40googlegroups.com <https://groups.google.com/d/msgid/jenkinsci-users/828bed5a-dda6-4782-82d9-6834b1f0e074%40googlegroups.com?utm_medium=email_source=footer>. -- You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/IDXKJukzJbo/unsubscribe. To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.com <mailto:jenkinsci-users+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtF-Hx%3Ds5MvNssLoE5jDnzhhVu4HkuSvosNd_Y9zdoxmrA%40mail.gmail.com <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtF-Hx%3Ds5MvNssLoE5jDnzhhVu4HkuSvosNd_Y9zdoxmrA%40mail.gmail.com?utm_medium=email_source=footer>. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/10726501-9ed7-5d86-1147-1a83083c0a29%40gmail.com.
CI with Git in Jenkins
Hi everybody, Way-back-when, Kohsuke wrote this post about how to setup CI with Git in Jenkins: https://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/ I have been using this in most my builds since and am still trying to get all colleagues to do the same (don't ask, my company can be difficult sometimes). Anyway, the other day I noticed that in one of my Jenkinsfiles, I forgot to activate the SCM polling. However, this project had been building on git pushes since the start! Doing some testing on my own, I came to the following conclusion: - Non-pipeline jobs all need to have the polling activated to react to the Git hook - Single pipeline jobs also need to have polling activated - Multibranch pipelines **don't** need to have polling activated, they just build whenever the git hook sends its request to Jenkins Now, my question is, is this behavior correct? Does it mean that for multibranch pipelines, I **can't** NOT do CI? (Except for removing the hook, but that might influence other builds as well!) Is this actual behavior documented somewhere and did I just miss this information? And what is now the correct way to setup CI? Should I still add the polling in my Jenkinsfile or, if I am sure I will be using a multibranch pipeline, just leave it out? Thanks. Roland -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/828bed5a-dda6-4782-82d9-6834b1f0e074%40googlegroups.com.
Security for team-specific nodes
Hey everybody, I am a Jenkins admin in my company, but since the introduction of pipelines, I feel like I have lost a lot of control over Jenkins. There are a couple of things in my company that are really important for me to remain in control of, so I was hoping to get some pointers from some/all of you. As a company, we supply the Jenkins Master with several 'public' nodes. These can be used by all projects and are paid for by all. Then we have some projects that have their own, special nodes, which only they pay for. The thing is, although these slaves are configured to be used only by jobs that request their specific labels, some of the teams have figured out that some of these nodes are a lot faster than our public ones and keep using these 'private' nodes. Since the projects that supplied these servers can sometimes run ONLY on these nodes (eg because they use lots of memory or have some specific hardware connected), they are obviously unhappy when they have to wait because the nodes are running 'illegal' jobs -- not even mentioning the fact they actually pay for these nodes... Now, I was wondering if it was possible to configure nodes to be only used by certain people/groups/jobs/..., or even better, have the UI hide them from people that are not supposed to use them? We are currently using Project-based security with LDAP and the Folder Plugin --> Every Project has a Group in LDAP and a folder in Jenkins where they have their jobs. It would be great if I can somehow 'connect' a server to one or more group(s) or folder(s). Does anybody have any ideas on how to get (something like) this setup? Any suggestions are welcome! Thanks, Roland -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6fa22e96-bb24-4362-8bd5-8d25e6ede649%40googlegroups.com.
Use REST API to check if updates are available
Hi all, Is there a way to check if an update is available for Jenkins using the REST API? If not using REST, is there another way to programmatically check this? I would like to add a check for this to our Nagios-systems, so I get automatic notification when an update is available. Thanks! Roland -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/ea6e2e61-a29b-4823-af47-7e80ef0eac32%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Slave Setup Plugin -- does it copy everything every time?
Hi all, I just stumbled across the Slave Setup Plugin and I was wondering: does this plugin copy configured files every time a slave is started or does it check if the files are already on the target-system? I admit that I haven't installed the plugin, so I cant test myself, but I was hoping to add it to our cluster soon. The thing is though, that some of our slaves are geographically further away from the master and the connection to them can be very slow. I don't mind if the initial copy takes some (or a lot) of time, but if any unnecessary copying is done, it would slow everything down way too much. Also, I would like to know what is meant with the description for the pre-launch script: This can be used to start the slave machine? Doesn't Jenkins start the slave? I am thankful for any info. Roland -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Need help with Matrix-build
Hi guys, I need some help with a matrix-build. Until now, I had the build configured to run on all nodes that have a label 'deb' and 'rpm' as axis 'distro' combined with axis 'arch' which checks on 'i386' and 'x64'. This is because we are building some binaries that are specific for i386 and x64 and packaging the builds depending in either RPM or DEB. So in all, we had 4 artifacts resulting. Now, I need to add another distro-type, namely a Windows EXE. The thing is that this doesn't have to be built on both architectures, since the project will only create a 32-bit binary. I know I can set the matrix to invalidate the combination 'exe' and 'x64', but that is not exactly doing what I want. If I would do this, it would never build my EXE on a 64-bit node, but I would like to have these nodes included in the build-pool as well! The nodes will need to have the label 'x64' set for some other builds I have, so changing them to 'i386' is also not an option. So, the question is, how can I setup the build to run the following 'combinations': - deb x i386 - deb x x64 - rpm x i386 - rpm x x64 - exe and have the 'exe' run on any available machine that has the label 'exe', no matter if it has the label 'i386' or 'x64'? Any help is greatly appreciated! Roland -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Need help with Matrix-build
I'm not quite sure what you mean with 'literate builds'... Do you mean splitting them in multiple jobs? On Thursday, October 3, 2013 6:27:10 PM UTC+2, Stephen Connolly wrote: Of course with literate builds you get a much easier way: Here's the markdown you'd have # Environments * `debian` * `i386` * `x64` * `redhat` * `i386` * `x64` * `windows` # Build * `debian` whatever command you use to make the deb * `redhat` rpmbuild blah blah blah * `windows` whatever command you use to make the exe On 3 October 2013 17:11, Roland Asmann roland...@gmail.com javascript:wrote: Hi guys, I need some help with a matrix-build. Until now, I had the build configured to run on all nodes that have a label 'deb' and 'rpm' as axis 'distro' combined with axis 'arch' which checks on 'i386' and 'x64'. This is because we are building some binaries that are specific for i386 and x64 and packaging the builds depending in either RPM or DEB. So in all, we had 4 artifacts resulting. Now, I need to add another distro-type, namely a Windows EXE. The thing is that this doesn't have to be built on both architectures, since the project will only create a 32-bit binary. I know I can set the matrix to invalidate the combination 'exe' and 'x64', but that is not exactly doing what I want. If I would do this, it would never build my EXE on a 64-bit node, but I would like to have these nodes included in the build-pool as well! The nodes will need to have the label 'x64' set for some other builds I have, so changing them to 'i386' is also not an option. So, the question is, how can I setup the build to run the following 'combinations': - deb x i386 - deb x x64 - rpm x i386 - rpm x x64 - exe and have the 'exe' run on any available machine that has the label 'exe', no matter if it has the label 'i386' or 'x64'? Any help is greatly appreciated! Roland -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Need help with Matrix-build
Thanks Curtis, I'll check it out! On 03.10.2013 19:55, Curtis Kline wrote: Roland, have you looked at the Build Flow plugin? I am using that instead of the matrix builds in some circumstances. Curtis On Thu, Oct 3, 2013 at 9:11 AM, Roland Asmann roland.asm...@gmail.com mailto:roland.asm...@gmail.com wrote: Hi guys, I need some help with a matrix-build. Until now, I had the build configured to run on all nodes that have a label 'deb' and 'rpm' as axis 'distro' combined with axis 'arch' which checks on 'i386' and 'x64'. This is because we are building some binaries that are specific for i386 and x64 and packaging the builds depending in either RPM or DEB. So in all, we had 4 artifacts resulting. Now, I need to add another distro-type, namely a Windows EXE. The thing is that this doesn't have to be built on both architectures, since the project will only create a 32-bit binary. I know I can set the matrix to invalidate the combination 'exe' and 'x64', but that is not exactly doing what I want. If I would do this, it would never build my EXE on a 64-bit node, but I would like to have these nodes included in the build-pool as well! The nodes will need to have the label 'x64' set for some other builds I have, so changing them to 'i386' is also not an option. So, the question is, how can I setup the build to run the following 'combinations': - deb x i386 - deb x x64 - rpm x i386 - rpm x x64 - exe and have the 'exe' run on any available machine that has the label 'exe', no matter if it has the label 'i386' or 'x64'? Any help is greatly appreciated! Roland -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com mailto:jenkinsci-users%2bunsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups Jenkins Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/0ujfEFyJ5Xs/unsubscribe. To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Need help with Matrix-build
Quite a nice read! This might be a step in the right direction!
One question though: currently I control the whole build with a single
Perl script. It doesn't matter if I'm on Windows or Linux (eg it reads
env-vars I set on the nodes)... So how would I write that with literate
builds? Add another environment above the three you mentioned? Or is
there another way to describe the build without having to reference the
environments?
On 03.10.2013 19:55, Stephen Connolly wrote:
http://jenkins-ci.org/content/literate-builds-wtf
On Thursday, 3 October 2013, Roland Asmann wrote:
I'm not quite sure what you mean with 'literate builds'... Do you
mean splitting them in multiple jobs?
On Thursday, October 3, 2013 6:27:10 PM UTC+2, Stephen Connolly wrote:
Of course with literate builds you get a much easier way:
Here's the markdown you'd have
# Environments
* `debian`
* `i386`
* `x64`
* `redhat`
* `i386`
* `x64`
* `windows`
# Build
* `debian`
whatever command you use to make the deb
* `redhat`
rpmbuild blah blah blah
* `windows`
whatever command you use to make the exe
On 3 October 2013 17:11, Roland Asmann roland...@gmail.com wrote:
Hi guys,
I need some help with a matrix-build. Until now, I had the
build configured to run on all nodes that have a label 'deb'
and 'rpm' as axis 'distro' combined with axis 'arch' which
checks on 'i386' and 'x64'.
This is because we are building some binaries that are
specific for i386 and x64 and packaging the builds depending
in either RPM or DEB. So in all, we had 4 artifacts resulting.
Now, I need to add another distro-type, namely a Windows
EXE. The thing is that this doesn't have to be built on both
architectures, since the project will only create a 32-bit
binary.
I know I can set the matrix to invalidate the combination
'exe' and 'x64', but that is not exactly doing what I want.
If I would do this, it would never build my EXE on a 64-bit
node, but I would like to have these nodes included in the
build-pool as well! The nodes will need to have the label
'x64' set for some other builds I have, so changing them to
'i386' is also not an option.
So, the question is, how can I setup the build to run the
following 'combinations':
- deb x i386
- deb x x64
- rpm x i386
- rpm x x64
- exe
and have the 'exe' run on any available machine that has the
label 'exe', no matter if it has the label 'i386' or 'x64'?
Any help is greatly appreciated!
Roland
--
You received this message because you are subscribed to the
Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails
from it, send an email to jenkinsci-use...@__googlegroups.com.
For more options, visit
https://groups.google.com/__groups/opt_out
https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google
Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it,
send an email to jenkinsci-users+unsubscr...@googlegroups.com
javascript:_e({}, 'cvml',
'jenkinsci-users%2bunsubscr...@googlegroups.com');.
For more options, visit https://groups.google.com/groups/opt_out.
--
Sent from my phone
--
You received this message because you are subscribed to a topic in the
Google Groups Jenkins Users group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/jenkinsci-users/0ujfEFyJ5Xs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups Jenkins
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Collect artifacts from multi-config build and upload to a server
Sorry for my very late reply! After checking and updating some of my plugins, I actually found what I needed in the 'Publish over SSH'-plugin, which has the option to send everything over the master node. On Monday, September 2, 2013 8:47:04 AM UTC+2, Baptiste Mathus wrote: Inside jenkins, under manage plugins, have you had a look at the plugins containing the word SSH? Why/in what area don't they suit your needs? Cheers Le 29 août 2013 23:26, Roland Asmann roland...@gmail.com javascript: a écrit : Hi all, I currently have an environment set up with 5-7 jenkins instances. I have several multi-config jobs, that run on 2-3 machines. What I need is a way to collect the artifacts that are created on the nodes onto the master (which is the server running the lightweight multi-config job) and upload the artifacts to an external server from here (using SSH). The reason this needs to be done from the master is because of the SSH-key and firewall-settings. The setup in jenkins has only 3 machines that are always the same, the others are VMs run by colleagues and can be completely new instances (different IP, etc). I've been looking at several plugins, but I still haven't found a way to achieve what I want. Can someone tell me which plugin(s) could help me out with this? Thanks! -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
GIT Plugin
Hi, We are switching from SVN to GIT, and I am now looking into how to get/keep our projects running on Jenkins. I have some questions about the GIT-plugin, which I hope someone here might be able to answer. With the SVN-plugin and multi config job, the master checked out the latest version and 'told' the slaves which version to use for the build. Does the GIT-plugin do the same? Since my testing repository is small, the checkout is very fast and I am unable to simulate a check-in during the update on master. Also, if I use the option to make a 'shallow clone', will I still be able to see the changes made since my last build or only those that were in the last push to the server? For now, it's not a problem to do a full clone, the repo will be very small, but if it will grow as large as our SVN did, the shallow-option will be a real performance-gain. Thanks! Roland -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Collect artifacts from multi-config build and upload to a server
Hi all, I currently have an environment set up with 5-7 jenkins instances. I have several multi-config jobs, that run on 2-3 machines. What I need is a way to collect the artifacts that are created on the nodes onto the master (which is the server running the lightweight multi-config job) and upload the artifacts to an external server from here (using SSH). The reason this needs to be done from the master is because of the SSH-key and firewall-settings. The setup in jenkins has only 3 machines that are always the same, the others are VMs run by colleagues and can be completely new instances (different IP, etc). I've been looking at several plugins, but I still haven't found a way to achieve what I want. Can someone tell me which plugin(s) could help me out with this? Thanks! -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Matrix-jobs heavy job plugin
Hi, I was playing around with the matrix-jobs and found that this type of job will not run if the 'heavy job plugin' is set to a value other than '1'. Since I need to set some weights for my projects to correctly scale in my build-cluster, I was wondering if anybody knows a way to get this done? Thanks. Roland -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
