on for doing so?
>
> On Fri, Aug 5, 2016 at 9:37 AM, John D. Ament
> wrote:
>
>> Sure, pagination will help. But can I also disable non-pipeline jobs?
>>
>>
>> On Thu, Aug 4, 2016 at 7:29 PM James Dumay wrote:
>>
>>> It really is coming! Should
on 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 wrote:
>> >
>> > We have a large number of jobs in our j
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 bein
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
"
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+
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 s
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
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
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
ent
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.
>
> I
he *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.
>
>
cause of the durability).
>
> My 2 cents
> Le 24 déc. 2015 3:46 AM, "John D. Ament" > 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.
>>
>>
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, foll
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)
>>
&g
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 ou
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
you just edit the job configuration and delete the “Archive
> Artifacts” post-build step?
>
>
>
> *From:* John D. Ament [mailto:john.d...@gmail.com ]
> *Sent:* 14 October 2014 01:50
> *To:* jenkins...@googlegroups.com
> *Subject:* Disabling archiving artifacts
>
&g
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 pract
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
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
3 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
> >:
>
> All,
>
> Is it po
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 subscrib
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
> 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
>>
>> Hi
>>
>> We're playing around with git at work, and I&#
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
25 matches
Mail list logo
