Re: Visualizing tests separately from different stages of a pipeline

Do I need to just give each capture a unique filename? I was trying this earlier and it appears giving them the same name only caused the first to show up on the UI :( Perhaps though I was doing something wrong... On Wednesday, August 17, 2016 at 9:24:37 PM UTC-7, James Dumay wrote: > >

Re: Visualizing tests separately from different stages of a pipeline

Joshua, I don't think there is anything stopping you from recording the test results in the Pipeline you have described. Jenkins will capture them wherever you ask it to with the JUnitArchiver however it won't record what stage it captured them from (there is an outstanding Improvement in JIRA for

Re: Visualizing tests separately from different stages of a pipeline

I to would like something like this, It seems to be a common thing to do and a real weakness of the pipeline style, If people are supposed to setup complex pipelines in a pipeline file then its pretty important that there be a way to ship out multiple result files, Even if they are

Publishing multiple test results from a jenkinsfile (or equivalent)

Hi, I am working through creating a jenkinsfile (and/or equivalent) for the openstack (nova) project we are using at godaddy, The stages are broken up into (literally the following): stage("Initiation") flows = build() node { start { net_info() } } stage("Checkout")

Re: Not able to trigger Github Organization folder job automatically

Can you confirm if this is the same behavior you are seeing? https://issues.jenkins-ci.org/browse/JENKINS-34563 If so, add your comments here so we can track all of it. On Wed, Aug 17, 2016 at 11:21 AM, Harsha Adiga wrote: > Hi Patrick, > > Any updates on this query?

Re: Multiple Jobs that are exactly the same

IMO it's a good thing to have a job per repo/project. You could probably have a look at either Job DSL plugin to version and script the fact and jobs are alike. Or use a pipeline script for all of them, using by default a standard function coming from the Pipeline Global Library Plugin. My 2

Re: Jenkinsfile Multibranch Pipeline Github Maven Checkout Directory Issues

Not sure I get what your actual issue is. Could you maybe rephrase it to say what you see, compared to what you expect, and provide the error logs and so on? Cheers Le 17 août 2016 11:02 AM, "Tony Murphy" a écrit : > Hi > > I'm using the new Jenkins Pipelines and I need

Multi-Branch Pipeline triggers interval example?

Hi, Would someone mind giving me an example of how to use the "properties" task to set a build trigger so that a multibranch pipeline build will run every 15 minutes? Somehow, both the snippet generator and the pipeline syntax generator are both errorring out on my server, so I can not find

CloudBees Docker Build/Credentials Plugin question

My Jenkins installation is using the CloudBees Docker Build and Publish Plugin version 1.2.1 and the Credentials Plugin v 1.28. When I go to configure my Docker Builder and set my Registry Credentials I can only seem to add the credentials to Global Credentials, despite creating my own

Re: Where did it move to? "Under the Build Triggers section, check Trigger builds remotely"

A little more looking and I find that it has to do with not running a 'secure' Jenkins setup. -- 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

Where did it move to? "Under the Build Triggers section, check Trigger builds remotely"

I keep seeing this in many reference articles on triggering builds. "Under the Build Triggers section, check Trigger builds remotely", however it has apparently been moved somewhere else and I can't find any references to where that is. Can someone please point me in the right direction?

Re: Not able to trigger Github Organization folder job automatically

Hi Patrick, Any updates on this query? Do you need any more information from me? Regards, Harsha On Monday, 15 August 2016 17:03:54 UTC-4, Harsha Adiga wrote: > > I think yes Jenkins is receiving the event. I can see the below line in > System Logs: > > Aug 15, 2016 4:17:13 PM INFO >

Re: LDAP groups and Role Based Authorization no playing nice.

So, was this broken at some later time on purpose? I could have sworn I have used this functionality in the past. Is this a problem in Role plugin or LDAP plugin? You mention Role plugin, but Role plugin is clearly recognizing the group for admin - it seems like there is a security problem in

Re: [pipeline][parametrized build][Jenkinsfile]Cannot use variable to checkout the parametrized build

Hi, Anybody known if this will solved or any workaround? this is the last show stoper for us to move to pipeline. I would really like to get ride of the old project. I have attach some screen capture if I wasn't clear enough. I work around most other problems but this I cannot do much. Unless

Re: Stash Integration with Jenkins Pipeline {for Code Review}

The *Bitbucket Branch Source Plugin *is still in a weird place for Bitbucket Server. Follow the discussion on https://issues.jenkins-ci.org/browse/JENKINS-33507 to see some of the issues with some of the existing Bitbucket Server plugins and the open PRs for auto-registration. On Sunday,

Jenkins Master and Slave containers sharing Jenkins home

I have a single Linux vm dedicated to running a Jenkins master container with Jenkins home mapped to an NFS mount. I have two other Linux vm's with the same mount configured and have FS Root set to that path. Am I asking for trouble by doing this? If so, any explanation would be greatly

CD Summit & Jenkins Days Fall Tour Line Up

Hello everybody, My name is Jared and I’m with DevOps.com, we are the only destination on the worldwide web dedicated to all thing DevOps. We are very proud bringing together the local CI/CD/DevOps communities to learn, network and discuss the latest trends and topics around this very hot

Building GitHub Pull Requests using Pipelines (and optionally Docker)

I blogged about building GitHub Pull Requests with Pipelines and optionally Docker: https://www.theguild.nl/building-github-pull-requests-using-jenkins-pipelines/ Hope it's useful to anyone :-) -- You received this message because you are subscribed to the Google Groups "Jenkins Users"

Re: Automated Jenkins Plugin/Dependency Management

Hey, Thanks for all the help guys. I slept on this idea for a few days because, to be honest I really didn't want to write my own package manager and re-invent the wheel. I took a step back and looked

RE: Teaching an old job new tricks

Thank you Mark From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mark Waite Sent: Wednesday, August 17, 2016 10:03 AM To: jenkinsci-users@googlegroups.com Subject: Re: Teaching an old job new tricks Labels do not have any concept of affinity as far as

Re: Teaching an old job new tricks

Labels do not have any concept of affinity as far as I know. On Wed, Aug 17, 2016 at 7:40 AM Ginga, Dick wrote: > Does the use of node label contain a notion of “affinity”. In other words, > I would like a build to go to node A always, unless node A is unavailable. >

Re: Matrix-based security does not authenticate group users in Active Directory

This was my issue For job project-base security to work with AD group/ user configured in a job, remove from AD group / user from 'configure global security' On Monday, November 18, 2013 at 12:49:10 PM UTC-5, SamL wrote: > > Hello Folks, > > We are facing an issue where Matrix-based security

RE: Teaching an old job new tricks

Does the use of node label contain a notion of “affinity”. In other words, I would like a build to go to node A always, unless node A is unavailable. I implemented my own failover by using a node label parameter with a default node of A and a “possible nodes” of the failover node. From:

Multiple Jobs that are exactly the same

We have a code base with many small repos, each repo is essentially a service. To test we have separate builds for each small repo, yet they are all pretty much identical. The problem happens when we want to make a change, we have to change every single one (over 60 builds). Is there a way

Re: LDAP groups and Role Based Authorization no playing nice.

LDAP group never works with the Role Based Authorization plugin. Only the CloudBee paid version of Role based plugin combined with Folder plugin on Enterprise Jenkins are made to work with LDAP group. -Indra From: > on

Jenkinsfile Multibranch Pipeline Github Maven Checkout Directory Issues

Hi I'm using the new Jenkins Pipelines and I need some help. I was under the illusion that once I setup my multi branch pipeline that was it as far as checkouts and branch management was concerned. But it seems that I was mistaken. I had issues where for example mvn command was not running in