Re: Performance issue of blue ocean with large job count
Every module of every job gets included. At a minimum only the top projects should show up. Note that we do have plain old maven projects. John On Thu, Aug 4, 2016 at 7:38 PM James Dumay <jdu...@cloudbees.com> wrote: > Do you want to exclude non-pipeline jobs from the listing? If so what is > your motivation for doing so? > > On Fri, Aug 5, 2016 at 9:37 AM, John D. Ament <john.d.am...@gmail.com> > wrote: > >> Sure, pagination will help. But can I also disable non-pipeline jobs? >> >> >> On Thu, Aug 4, 2016 at 7:29 PM James Dumay <jdu...@cloudbees.com> wrote: >> >>> It really is coming! Should be in next weeks alpha release :) >>> >>> >>> On Thursday, August 4, 2016 at 10:01:41 PM UTC+10, Daniel Beck wrote: >>> >>>> Pagination is currently being worked on and should be done in a week or >>>> two IIRC. I learned when I complained about the 100% CPU usage in some >>>> views :-) >>>> >>>> > On 28.07.2016, at 15:32, John D. Ament <john.d...@gmail.com> wrote: >>>> > >>>> > We have a large number of jobs in our jenkins. Very few of them are >>>> actual pipelines though. Looking at blue ocean, it seems like it should >>>> only be picking up pipelines. The response to load the initial JSON is > 1 >>>> minute and is very slow to render. Is there any way to cut down the jobs >>>> being shown in blue ocean? >>>> > >>>> > -- >>>> > 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. >>>> >>> > To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-users/290c1580-22f1-4404-95e1-b06fc232b001%40googlegroups.com. >>>> >>>> > For more options, visit https://groups.google.com/d/optout. >>>> >>>> -- >>> 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/SZ4mOZNCwJo/unsubscribe >>> . >>> To unsubscribe from this group and all its topics, 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/87669fbb-b587-4e1f-854e-7d76d935732e%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-users/87669fbb-b587-4e1f-854e-7d76d935732e%40googlegroups.com?utm_medium=email_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >> 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/SZ4mOZNCwJo/unsubscribe >> . >> To unsubscribe from this group and all its topics, 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/CAOqetn8DvcooT%3DVpwgD3cifPiV%2Bh6OZo07EkW1f3SiVJRnV_4w%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-users/CAOqetn8DvcooT%3DVpwgD3cifPiV%2Bh6OZo07EkW1f3SiVJRnV_4w%40mail.gmail.com?utm_medium=email_source=footer> >> . > > >> For more options, visit https://groups.google.com/d/optout. >> > -- > James Dumay > Product Manager > CloudBees, Inc. > Skype: jdumaycb Twitter: i386 > > -- > 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/SZ4mOZNCwJo/unsubscribe. > To unsubscribe from this group and all its topics, 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/CAErbOvQ_HhDL3ZtDYBuvwn7cXr4Ws6SzsztSqWAna%2BggRbCodA%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-users/CAErbOvQ_HhDL3ZtDYBuvwn7cXr4Ws6SzsztSqWAna%2BggRbCodA%40mail.gmail.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CAOqetn_SSMkxo_3fTRKXHTxCWpdNo_RUf4h0%2Bgfa1EfcrnSxnQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Performance issue of blue ocean with large job count
Sure, pagination will help. But can I also disable non-pipeline jobs? On Thu, Aug 4, 2016 at 7:29 PM James Dumay <jdu...@cloudbees.com> wrote: > It really is coming! Should be in next weeks alpha release :) > > > On Thursday, August 4, 2016 at 10:01:41 PM UTC+10, Daniel Beck wrote: > >> Pagination is currently being worked on and should be done in a week or >> two IIRC. I learned when I complained about the 100% CPU usage in some >> views :-) >> >> > On 28.07.2016, at 15:32, John D. Ament <john.d...@gmail.com> wrote: >> > >> > We have a large number of jobs in our jenkins. Very few of them are >> actual pipelines though. Looking at blue ocean, it seems like it should >> only be picking up pipelines. The response to load the initial JSON is > 1 >> minute and is very slow to render. Is there any way to cut down the jobs >> being shown in blue ocean? >> > >> > -- >> > 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. >> > > To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/290c1580-22f1-4404-95e1-b06fc232b001%40googlegroups.com. >> >> > For more options, visit https://groups.google.com/d/optout. >> >> -- > 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/SZ4mOZNCwJo/unsubscribe. > To unsubscribe from this group and all its topics, 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/87669fbb-b587-4e1f-854e-7d76d935732e%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/87669fbb-b587-4e1f-854e-7d76d935732e%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CAOqetn8DvcooT%3DVpwgD3cifPiV%2Bh6OZo07EkW1f3SiVJRnV_4w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Performance issue of blue ocean with large job count
We have a large number of jobs in our jenkins. Very few of them are actual pipelines though. Looking at blue ocean, it seems like it should only be picking up pipelines. The response to load the initial JSON is > 1 minute and is very slow to render. Is there any way to cut down the jobs being shown in blue ocean? -- 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/290c1580-22f1-4404-95e1-b06fc232b001%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: BlueOcean JavaScript Error
Removing cucumber did fix it. On Thursday, July 28, 2016 at 7:11:02 AM UTC-4, John D. Ament wrote: > > Experimental update with Jenkins 2.15. looks like a compatibility issue > with cucumber though. -- 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/91a4e33c-3449-4cca-a6af-71d532e8499a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: BlueOcean JavaScript Error
Experimental update with Jenkins 2.15. looks like a compatibility issue with cucumber though. -- 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/2dcf6679-67e2-4674-8aaa-0d2ba54e50d8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: BlueOcean JavaScript Error
(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.kohsuke.stapler.export.MethodProperty.getValue(MethodProperty.java:66) at org.kohsuke.stapler.export.Property.safeGetValue(Property.java:145) ... 116 more Caused by: java.lang.ClassCastException: hudson.tasks.test.AggregatedTestResultAction$1 cannot be cast to hudson.tasks.test.TestResult at hudson.tasks.test.AbstractTestResultAction.findCorrespondingResult(AbstractTestResultAction.java:252) at hudson.tasks.test.TestResult.getPreviousResult(TestResult.java:146) at org.jenkinsci.plugins.cucumber.jsontestsupport.ScenarioResult.getStatus(ScenarioResult.java:258) ... 122 more On Wednesday, July 27, 2016 at 10:16:50 PM UTC-4, John D. Ament wrote: > > Was recommended to try the blue ocean plugin for jenkins. After setting > it up, in my existing jenkins instance. I get the screen "No pipelines > found" even though I have pipelines, and found the following javascript > error: > > jenkins-js-extension.js:15863 SyntaxError: Unexpected token > in JSON at position 10362880(anonymous function) @ > jenkins-js-extension.js:15863 > jenkins-js-extension.js:15863 SyntaxError: Unexpected token (…)(anonymous > function) @ jenkins-js-extension.js:15863 > -- 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/0fc92799-58d1-4af7-a3ae-b9949aa6b145%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
BlueOcean JavaScript Error
Was recommended to try the blue ocean plugin for jenkins. After setting it up, in my existing jenkins instance. I get the screen "No pipelines found" even though I have pipelines, and found the following javascript error: jenkins-js-extension.js:15863 SyntaxError: Unexpected token in JSON at position 10362880(anonymous function) @ jenkins-js-extension.js:15863 jenkins-js-extension.js:15863 SyntaxError: Unexpected token (…)(anonymous function) @ jenkins-js-extension.js:15863 -- 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/b35fc4d2-183e-45d1-bca9-e916506f024c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
EC2 Integration with Pipeline - only waiting for one node at a time?
Hi, I've begun trying out pipeline w/ EC2 support. We spin up dynamic nodes to run some of our heavier tests. It looks like with Pipeline, only a single request is made to spin up a node whereas with the Build Pipeline plugin multiple requests are made (because its multiple jobs). This adds a delay as it does take a couple of minutes for the machine to boot. Is it possible to force it to request a new node? John -- 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/88738005-5f50-4127-9a5a-1f43a60a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Pipeline plugin - archive/unarchive performance
Hey So after a long while I've been able to pick up my work on using the pipeline plugin. Anyways, I've started hacking at hooking it up to our staging environment. One step is run on our master node, and the other step is run on a dynamically provisioned EC2 instance. I'm archiving the entire workspace and copying it to the other node. It looks like the folder size is 1.8 gb. How exactly does archiving work? Are you zipping, copying over and extracting? Or are you syncing file by file? The speed to do this unarchiving step is pretty long. It takes > 10 mins to run. John -- 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/b00bb9bd-061d-4bc7-9a25-7f290ca9cc9e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Approaches for sharing workspace in a pipeline
Ok, so I think I got something. If I use "**/*" on the unarchive step, I get everything. Not quite what I expected, but it works. On Thursday, December 24, 2015 at 1:20:16 PM UTC-5, John D. Ament wrote: > > Creating the archive doesn't seem to be an issue. > > Its the unarchive step where things don't quite work for me. If I read > this info, it implies that the mapping step is not required. > https://github.com/jenkinsci/workflow-plugin/blob/master/basic-steps/src/main/resources/org/jenkinsci/plugins/workflow/steps/ArtifactUnarchiverStep/config.jelly#L31 > > However, if mapping isn't set, an exception gets thrown: > https://github.com/jenkinsci/workflow-plugin/blob/master/basic-steps/src/main/java/org/jenkinsci/plugins/workflow/steps/ArtifactUnarchiverStepExecution.java#L39 > > And in fact, the expanding of the archive is keyed off of this mapping > config. > https://github.com/jenkinsci/workflow-plugin/blob/master/basic-steps/src/main/java/org/jenkinsci/plugins/workflow/steps/ArtifactUnarchiverStepExecution.java#L42 > > It looks like it may be straight forward enough to add an unarchive all > option, and if that works I may try that out instead. > > John > > On Thursday, December 24, 2015 at 12:55:30 PM UTC-5, Brian Ray wrote: >> >> Isn't the "get everything" Ant regex something like or ***/**? >> >> If you continue looking at workflow, also check out the *stash* and *unstash >> *steps. Similar purpose and syntax but more applicable to intermediate >> stages where you don't need to retain the artifacts. You can also refer to >> the batch of *stash*ed artifacts by an arbitrary logical name for >> downstream *unstash*ing. >> >> On Thursday, December 24, 2015 at 6:53:56 AM UTC-8, John D. Ament wrote: >>> >>> Hi, >>> >>> I definitely thought about workflow. It looks promising. >>> >>> One question though - I can't seem to archive/unarchive everything. It >>> looks like to use unarchiver you need to know the paths that will be >>> exposed, and instead I'd like to just get everything, including class >>> files. Is that possible? >>> >>> John >>> >>> On Thursday, December 24, 2015 at 1:49:01 AM UTC-5, Baptiste Mathus >>> wrote: >>>> >>>> Hi John, >>>> >>>> Not sure what you call a pipeline job, do you mean 'workflow job'? or >>>> do you use the term in a generic way and actually have many (freestyle) >>>> jobs you're coordinating? >>>> >>>> If the latter, then it really seems like a use case for a workflow job >>>> (using the workflow plugin). Using/archiving etc. artifacts and being able >>>> to share the ws during the build is gonna be both more natural and more >>>> maintainable (and more robust because of the durability). >>>> >>>> My 2 cents >>>> Le 24 déc. 2015 3:46 AM, "John D. Ament" <john.d...@gmail.com> a >>>> écrit : >>>> >>>>> Hi, >>>>> >>>>> I was wondering if anyone had any best practices or tips to share on >>>>> have a common workspace for a pipeline job. >>>>> >>>>> Basically, I have a series of pipeline jobs and I want them to have a >>>>> single workspace for the duration of the job chain. I compile the >>>>> artifacts once, running unit tests, followed by a suite of integration >>>>> and >>>>> BDD tests. It's a fairly complicated build, including generating an app >>>>> server and minifying a lot of javascript for our UI. Some of these steps >>>>> are pretty long, and in total we have 4 pipeline steps. I figure by >>>>> doing >>>>> this once, I would cut out about 40 minutes of rebuild time in my >>>>> pipeline. >>>>> >>>>> One idea I had was to use the clone workspace plugin to copy them, >>>>> https://wiki.jenkins-ci.org/display/JENKINS/Clone+Workspace+SCM+Plugin, >>>>> but it seems like this isn't pipeline sensitive since each step in the >>>>> pipeline should be building the same commit. I also thought about >>>>> copying >>>>> artifacts, but it seems like its a huge number of artifacts. Could I >>>>> build >>>>> a zip with the contents? >>>>> >>>>> Any thoughts? >>>>> >>>>> Thanks! >>>>> >>>>> John >>>
Re: Approaches for sharing workspace in a pipeline
Creating the archive doesn't seem to be an issue. Its the unarchive step where things don't quite work for me. If I read this info, it implies that the mapping step is not required. https://github.com/jenkinsci/workflow-plugin/blob/master/basic-steps/src/main/resources/org/jenkinsci/plugins/workflow/steps/ArtifactUnarchiverStep/config.jelly#L31 However, if mapping isn't set, an exception gets thrown: https://github.com/jenkinsci/workflow-plugin/blob/master/basic-steps/src/main/java/org/jenkinsci/plugins/workflow/steps/ArtifactUnarchiverStepExecution.java#L39 And in fact, the expanding of the archive is keyed off of this mapping config. https://github.com/jenkinsci/workflow-plugin/blob/master/basic-steps/src/main/java/org/jenkinsci/plugins/workflow/steps/ArtifactUnarchiverStepExecution.java#L42 It looks like it may be straight forward enough to add an unarchive all option, and if that works I may try that out instead. John On Thursday, December 24, 2015 at 12:55:30 PM UTC-5, Brian Ray wrote: > > Isn't the "get everything" Ant regex something like or ***/**? > > If you continue looking at workflow, also check out the *stash* and *unstash > *steps. Similar purpose and syntax but more applicable to intermediate > stages where you don't need to retain the artifacts. You can also refer to > the batch of *stash*ed artifacts by an arbitrary logical name for > downstream *unstash*ing. > > On Thursday, December 24, 2015 at 6:53:56 AM UTC-8, John D. Ament wrote: >> >> Hi, >> >> I definitely thought about workflow. It looks promising. >> >> One question though - I can't seem to archive/unarchive everything. It >> looks like to use unarchiver you need to know the paths that will be >> exposed, and instead I'd like to just get everything, including class >> files. Is that possible? >> >> John >> >> On Thursday, December 24, 2015 at 1:49:01 AM UTC-5, Baptiste Mathus wrote: >>> >>> Hi John, >>> >>> Not sure what you call a pipeline job, do you mean 'workflow job'? or do >>> you use the term in a generic way and actually have many (freestyle) jobs >>> you're coordinating? >>> >>> If the latter, then it really seems like a use case for a workflow job >>> (using the workflow plugin). Using/archiving etc. artifacts and being able >>> to share the ws during the build is gonna be both more natural and more >>> maintainable (and more robust because of the durability). >>> >>> My 2 cents >>> Le 24 déc. 2015 3:46 AM, "John D. Ament" <john.d...@gmail.com> a écrit : >>> >>>> Hi, >>>> >>>> I was wondering if anyone had any best practices or tips to share on >>>> have a common workspace for a pipeline job. >>>> >>>> Basically, I have a series of pipeline jobs and I want them to have a >>>> single workspace for the duration of the job chain. I compile the >>>> artifacts once, running unit tests, followed by a suite of integration and >>>> BDD tests. It's a fairly complicated build, including generating an app >>>> server and minifying a lot of javascript for our UI. Some of these steps >>>> are pretty long, and in total we have 4 pipeline steps. I figure by doing >>>> this once, I would cut out about 40 minutes of rebuild time in my pipeline. >>>> >>>> One idea I had was to use the clone workspace plugin to copy them, >>>> https://wiki.jenkins-ci.org/display/JENKINS/Clone+Workspace+SCM+Plugin, >>>> but it seems like this isn't pipeline sensitive since each step in the >>>> pipeline should be building the same commit. I also thought about copying >>>> artifacts, but it seems like its a huge number of artifacts. Could I >>>> build >>>> a zip with the contents? >>>> >>>> Any thoughts? >>>> >>>> Thanks! >>>> >>>> John >>>> >>>> -- >>>> 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. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-users/3c25d084-56c8-4242-a6e0-a0b347ea0af8%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/jenkinsci-users/3c25d084-56c8-4242-a6e0-a0b347ea0af8%40googlegroups.com?utm_medium=email_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- 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/3a074a74-c6e4-4354-a75e-4b286ebff524%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Approaches for sharing workspace in a pipeline
Hi, I definitely thought about workflow. It looks promising. One question though - I can't seem to archive/unarchive everything. It looks like to use unarchiver you need to know the paths that will be exposed, and instead I'd like to just get everything, including class files. Is that possible? John On Thursday, December 24, 2015 at 1:49:01 AM UTC-5, Baptiste Mathus wrote: > > Hi John, > > Not sure what you call a pipeline job, do you mean 'workflow job'? or do > you use the term in a generic way and actually have many (freestyle) jobs > you're coordinating? > > If the latter, then it really seems like a use case for a workflow job > (using the workflow plugin). Using/archiving etc. artifacts and being able > to share the ws during the build is gonna be both more natural and more > maintainable (and more robust because of the durability). > > My 2 cents > Le 24 déc. 2015 3:46 AM, "John D. Ament" <john.d...@gmail.com > > a écrit : > >> Hi, >> >> I was wondering if anyone had any best practices or tips to share on have >> a common workspace for a pipeline job. >> >> Basically, I have a series of pipeline jobs and I want them to have a >> single workspace for the duration of the job chain. I compile the >> artifacts once, running unit tests, followed by a suite of integration and >> BDD tests. It's a fairly complicated build, including generating an app >> server and minifying a lot of javascript for our UI. Some of these steps >> are pretty long, and in total we have 4 pipeline steps. I figure by doing >> this once, I would cut out about 40 minutes of rebuild time in my pipeline. >> >> One idea I had was to use the clone workspace plugin to copy them, >> https://wiki.jenkins-ci.org/display/JENKINS/Clone+Workspace+SCM+Plugin, >> but it seems like this isn't pipeline sensitive since each step in the >> pipeline should be building the same commit. I also thought about copying >> artifacts, but it seems like its a huge number of artifacts. Could I build >> a zip with the contents? >> >> Any thoughts? >> >> Thanks! >> >> John >> >> -- >> 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 . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/3c25d084-56c8-4242-a6e0-a0b347ea0af8%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-users/3c25d084-56c8-4242-a6e0-a0b347ea0af8%40googlegroups.com?utm_medium=email_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- 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/84538971-9e6d-4fc0-9f5d-beee2e68262b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Approaches for sharing workspace in a pipeline
Hi, I was wondering if anyone had any best practices or tips to share on have a common workspace for a pipeline job. Basically, I have a series of pipeline jobs and I want them to have a single workspace for the duration of the job chain. I compile the artifacts once, running unit tests, followed by a suite of integration and BDD tests. It's a fairly complicated build, including generating an app server and minifying a lot of javascript for our UI. Some of these steps are pretty long, and in total we have 4 pipeline steps. I figure by doing this once, I would cut out about 40 minutes of rebuild time in my pipeline. One idea I had was to use the clone workspace plugin to copy them, https://wiki.jenkins-ci.org/display/JENKINS/Clone+Workspace+SCM+Plugin, but it seems like this isn't pipeline sensitive since each step in the pipeline should be building the same commit. I also thought about copying artifacts, but it seems like its a huge number of artifacts. Could I build a zip with the contents? Any thoughts? Thanks! John -- 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/3c25d084-56c8-4242-a6e0-a0b347ea0af8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Locating extra junit xml files
My build uses maven to kick off some grunt tasks to test my javascript code. The grunt tests use jasmine and output junit styled xml files. These XML files are not picked up in my build in jenkins. Any idea how I can get jenkins to load these files? -- 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/62f79755-dd51-4dae-b13d-faeaf4ced86c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Locating extra junit xml files
On Monday, November 2, 2015 at 5:29:07 PM UTC-5, R Tyler Croy wrote: > > (replies inline) > > On Mon, 02 Nov 2015, John D. Ament wrote: > > > My build uses maven to kick off some grunt tasks to test my javascript > > code. The grunt tests use jasmine and output junit styled xml files. > > These XML files are not picked up in my build in jenkins. Any idea how > I > > can get jenkins to load these files? > > > Have you configured a post-build action "Publish JUnit Test Reports" and > told > Jenkins where it can find those JUnit XML files? > I don't even see that option. Debugging. > > Usually if you're not seeing the test reports you expect means that this > field > needs a new pattern to find the XML files, e.g. `build/reports/**/*.xml` > For the other maven jobs, they're going to target/surefire-reports. I told the UI guys to drop them there, but not being picked up. I'm guessing its different? > > > > - R. Tyler Croy > > -- > Code: <https://github.com/rtyler> > Chatter: <https://twitter.com/agentdero> > > % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F > -- > -- 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/0d5792fc-0b6d-4dd9-95cd-1b362e09be10%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Locating extra junit xml files
It would appear I'm hitting https://issues.jenkins-ci.org/browse/JENKINS-9980 :-( On Monday, November 2, 2015 at 5:37:04 PM UTC-5, John D. Ament wrote: > > > > On Monday, November 2, 2015 at 5:29:07 PM UTC-5, R Tyler Croy wrote: >> >> (replies inline) >> >> On Mon, 02 Nov 2015, John D. Ament wrote: >> >> > My build uses maven to kick off some grunt tasks to test my javascript >> > code. The grunt tests use jasmine and output junit styled xml files. >> > These XML files are not picked up in my build in jenkins. Any idea >> how I >> > can get jenkins to load these files? >> >> >> Have you configured a post-build action "Publish JUnit Test Reports" and >> told >> Jenkins where it can find those JUnit XML files? >> > > I don't even see that option. Debugging. > > >> >> Usually if you're not seeing the test reports you expect means that this >> field >> needs a new pattern to find the XML files, e.g. `build/reports/**/*.xml` >> > > For the other maven jobs, they're going to target/surefire-reports. I > told the UI guys to drop them there, but not being picked up. I'm guessing > its different? > > >> >> >> >> - R. Tyler Croy >> >> -- >> Code: <https://github.com/rtyler> >> Chatter: <https://twitter.com/agentdero> >> >> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F >> -- >> > -- 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/db90e734-f7cd-4d6a-9ae4-097b4e2f600e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Disabling archiving artifacts
That's what I thought at first, but it turns out the step wasn't even configured when it was doing its archiving. Based on the docs I figured it shouldn't be archiving artifacts. On Tuesday, October 14, 2014 4:26:19 AM UTC-4, matthew...@diamond.ac.uk wrote: Can’t you just edit the job configuration and delete the “Archive Artifacts” post-build step? *From:* John D. Ament [mailto:john.d...@gmail.com javascript:] *Sent:* 14 October 2014 01:50 *To:* jenkins...@googlegroups.com javascript: *Subject:* Disabling archiving artifacts Hi, I have a job, in which I use Artifactory for storing artifacts. I don't particularly care about archiving artifacts and would prefer to turn it off as it serves no purpose for me. I tried setting the following configuration when archiving: Files to archive: (blank) Excludes: ** (check) Do not fail build if archiving returns nothing (check) Use default excludes However this causes this output: *20:44:09* ERROR: No artifacts are configured for archiving. *20:44:09* You probably forgot to set the file pattern, so please go back to the configuration and specify it. *20:44:09* If you really did mean to archive all the files in the workspace, please specify ** *20:44:09* Build step 'Archive the artifacts' changed build result to FAILURE I'm on Jenkins 1.579. I'm not sure why it would be complaining about this, as I'd rather have it off. John -- -- 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.
Disabling archiving artifacts
Hi, I have a job, in which I use Artifactory for storing artifacts. I don't particularly care about archiving artifacts and would prefer to turn it off as it serves no purpose for me. I tried setting the following configuration when archiving: Files to archive: (blank) Excludes: ** (check) Do not fail build if archiving returns nothing (check) Use default excludes However this causes this output: *20:44:09* ERROR: No artifacts are configured for archiving.*20:44:09* You probably forgot to set the file pattern, so please go back to the configuration and specify it.*20:44:09* If you really did mean to archive all the files in the workspace, please specify ***20:44:09* Build step 'Archive the artifacts' changed build result to FAILURE I'm on Jenkins 1.579. I'm not sure why it would be complaining about this, as I'd rather have it off. John -- 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.
Re: sudo: no tty present and no askpass program specified jenkins
are you sure it's NOPASSWD? Seems like you need to turn off require tty in your sudoers file. On Monday, October 13, 2014 4:21:39 PM UTC-4, Jeffrey Parker wrote: That is exactly what the problem is, but the bigger issue is running sudo commands in a script like this is generally bad practice. The more correct way to do it is to make sure that all files are already owned by the correct user or that the user that is running the command has permission to change ownership of those files. On Monday, October 13, 2014 3:15:16 PM UTC-5, Richard Bywater wrote: From my rudimentary knowledge, it doesn't look like NOPASSWD has been specified for running that command and so I'd expect it to prompt for the password (and hence get the issue you are seeing). I could be wrong though as I don't have a setup available to me which has similar sudoers settings :) Richard. On Tue, Oct 14, 2014 at 12:05 AM, niraj nandane niraj@gmail.com wrote: sudo -u root chown habdbsync some files This stmt is making above no tty output On Mon, Oct 13, 2014 at 4:33 PM, niraj nandane niraj@gmail.com wrote: output of sudo -l (habdbsync) NOPASSWD: ALL, (habdbsync) !/bin/sh, !/bin/ksh, !/bin/csh, !/bin/tcsh, !/bin/zsh, !/bin/bash, (habdbsync) !/bin/su, (habdbsync) !/usr/bin/ssh, !/usr/bin/scp, !/usr/bin/slogin (root) /bin/chown habdbsync /devbuild/* (root) /bin/chown -R root\:root /devbuild/* (root) /bin/chown root\:root /devbuild/* (root) /bin/true On Mon, Oct 13, 2014 at 3:41 PM, Richard Bywater ric...@byh2o.com wrote: Hmm my sudo is a bit rusty - but perhaps you could list the output of sudo -ll which I think will make it a bit easier to read. Also what command/s is the build doing when it gets prompted (and I assume Jenkins is running as the user skhandeb?) Richard. PS Please keep discussions on the list as that way others can jump in and help out if they see the potential issue :) On Mon, Oct 13, 2014 at 11:02 PM, niraj nandane niraj@gmail.com wrote: Hi, The idea is the buildmachine have access for 3 hrs to build server. When i run build on build machine without using jenkins its get completed and dont ask ever password . The script i run also have sudo stmts. But when we run same script from jenkins its say above error. The output of sudo -l is User skhandeb may run the following commands on this host: (habdbsync) NOPASSWD: ALL, (habdbsync) !/bin/sh, !/bin/ksh, !/bin/csh, !/bin/tcsh, !/bin/zsh, !/bin/bash, (habdbsync) !/bin/su, (habdbsync) !/usr/bin/ssh, !/usr/bin/scp, !/usr/bin/slogin (root) /bin/chown habdbsync /devbuild/* (root) /bin/chown -R root\:root /devbuild/* (root) /bin/chown root\:root /devbuild/* (root) /bin/true -- Thanks and regards-- Niraj Nandane(Vit pune) -- 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/JUpplb7mV3k/unsubscribe . To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Thanks and regards-- Niraj Nandane(Vit pune) -- Thanks and regards-- Niraj Nandane(Vit pune) -- 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/d/optout. -- 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.
Re: Findbugs plugin - tell Jenkins where to find the XML file
My results are currently inconsistent with two projects. In both projects, my maven command line is the same, e.g. clean install deploy findbugs:findbugs In one project, Jenkins is picking up the findbugsXml.xml and running findbugs against it. In the other, no I do not see the FINDBUGS output in the console. Both are using findbugs 2.5.2. On Thursday, November 21, 2013 6:16:55 PM UTC-5, Ullrich Hafner wrote: In a maven job every child module XML should be picked up automatically. How do you start findbugs? Which version of the maven findbugs plugin are you using? Newer version should produce a findbugsXml.xml file and not the outdated find bugs.xml file... Are there logging messages in the console log of your build that start with [FINDBUGS]? Am Donnerstag, 21. November 2013 schrieb John D. Ament : So if I have a multi module project, where the root pom.xml doesn't have findbugs, but instead one of the child modules has it, there's not possibility to have a maven job pick up that findbugs.xml file in my-submodule/target/findbugs.xml ? On Thursday, November 21, 2013 4:15:53 PM UTC-5, Ullrich Hafner wrote: For Maven jobs, the file name is automatically derived from the pom. For Freestyle jobs, you can enter the filename in the advanced section. Ulli Am 21.11.2013 um 19:52 schrieb John D. Ament john.d...@gmail.com: All, Is it possible to tell Jenkins where to find the findbugs xml file after running a build? I have a multi module project, and want Jenkins to be able to run findbugs analysis on all of the XML files and report against it that way. John -- 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. -- 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. -- 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.
Findbugs plugin - tell Jenkins where to find the XML file
All, Is it possible to tell Jenkins where to find the findbugs xml file after running a build? I have a multi module project, and want Jenkins to be able to run findbugs analysis on all of the XML files and report against it that way. John -- 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: Findbugs plugin - tell Jenkins where to find the XML file
So if I have a multi module project, where the root pom.xml doesn't have findbugs, but instead one of the child modules has it, there's not possibility to have a maven job pick up that findbugs.xml file in my-submodule/target/findbugs.xml ? On Thursday, November 21, 2013 4:15:53 PM UTC-5, Ullrich Hafner wrote: For Maven jobs, the file name is automatically derived from the pom. For Freestyle jobs, you can enter the filename in the advanced section. Ulli Am 21.11.2013 um 19:52 schrieb John D. Ament john.d...@gmail.comjavascript: : All, Is it possible to tell Jenkins where to find the findbugs xml file after running a build? I have a multi module project, and want Jenkins to be able to run findbugs analysis on all of the XML files and report against it that way. John -- 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.
Jacoco plugin failing, at least I think
Hi all We recently updated our jenkins instance to everything latest. This included updating our jacoco plugin to 1.0.13 from 1.0.12. Since then, I've noticed that our code coverage reports are no longer working. The build just abruptly fails. We're on RHEL6. Are there any logs I can look at to see why it might be failing? I checked jenkins.log but nothing was really in it. Thanks, John -- 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: git plugin - pulling in pull requests from Stash
Well, the first issue I ran into is that the git plugin won't accept refs/pull-requests/*/merge, saying it's an illegal wildcard. On Mon, Aug 12, 2013 at 7:24 AM, Vincent Latombe vincent.lato...@gmail.com wrote: Hi, I don't have all the settings in mind, but you need to tweak the refspec to achieve this. Also, it may be better to fetch refs/pull-requests/*/merge-clean because you'll always get a non-conflicting commit. Vincent 2013/8/11 John D. Ament john.d.am...@gmail.com Hi We're playing around with git at work, and I've been working with Jenkins for a long while (though this is the first time I'm having an issue that didn't seem to work as expected). Using the git plugin, I'd like to polling for remotes that match the pattern refs/pull-requests/*/merge . See below for a list of what I'm seeing: $ git ls-remote http://foo@localhost:7990/scm/foo/foo_1.git | grep refs/pull-requests/ | grep merge | grep -v clean Password for 'http://foo@localhost:7990': 6de02b00d273df20ea639f085ad921f070cf1212refs/pull-requests/1/merge 3b5530128e1c5fecf27fa76b11d92e8c1967ac29refs/pull-requests/2/merge I set this as my branch in the git settings, but I'm pretty sure it's wrong. So is there a way to tell the git plugin in Jenkins to pull from these locations? 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. -- 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/YtGL1UYPJ_E/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.
git plugin - pulling in pull requests from Stash
Hi We're playing around with git at work, and I've been working with Jenkins for a long while (though this is the first time I'm having an issue that didn't seem to work as expected). Using the git plugin, I'd like to polling for remotes that match the pattern refs/pull-requests/*/merge . See below for a list of what I'm seeing: $ git ls-remote http://foo@localhost:7990/scm/foo/foo_1.git | grep refs/pull-requests/ | grep merge | grep -v clean Password for 'http://foo@localhost:7990': 6de02b00d273df20ea639f085ad921f070cf1212refs/pull-requests/1/merge 3b5530128e1c5fecf27fa76b11d92e8c1967ac29refs/pull-requests/2/merge I set this as my branch in the git settings, but I'm pretty sure it's wrong. So is there a way to tell the git plugin in Jenkins to pull from these locations? 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.
