Announcing the Pipeline Authoring SIG

Hey all! Now that DevOps World/Jenkins World season has wrapped up, I'm officially kicking off the Pipeline Authoring SIG. I proposed it in https://groups.google.com/forum/#!topic/jenkinsci-dev/nJ1XWyzBMSw, but now I've started creating the infrastructure for the SIG, including the

Re: Pipeline checkout persistence issue

ll to checkout > because it does a full checkout by default. > > Either way, the default checkout seems to be the cause of my headaches and > I now know how to get around it, thanks. > > James > > > > On Wed, 17 Oct 2018 at 11:25, Andrew Bayer wrote: > >> You

Re: Pipeline checkout persistence issue

You might want to add "skipDefaultCheckout(true)" to your options - it could be that the automatic checkout that happens whenever you enter an agent is messing things up. A. On Wed, Oct 17, 2018 at 11:40 AM James Chapman wrote: > Hello Jenkins users, > > I have a pipeline job that run across a

Re: Pipeline build not stopping when stage marked as failed

a wrote: > I think I've stripped out everything that I shouldn't share :) > > not doing anything fancy. the dependency check runs and fails the build > but the steps after it run even though it failed. > > On Monday, 15 October 2018 15:28:19 UTC+1, Andrew Bayer wrote: >>

Re: Pipeline build not stopping when stage marked as failed

Can you attach your Jenkinsfile? Thanks. On Mon, Oct 15, 2018 at 10:59 AM Paul D'Ambra wrote: > Hi, thanks for the link? > > I find the pipeline documentation a bit limited... there are no examples > of usage in that link. Are you saying I need to "wrap" the dependency check > stage in some way

Re: Does the Declarative Pipeline Plugin Assume /bin/sh for Shell Command Step (sh) when Running on Agent Node?

It uses the default shell, yes - i.e., "sh -c ...", as you can see at https://github.com/jenkinsci/durable-task-plugin/blob/c1ee6607c6939e8917762419c8474fecec06172c/src/main/java/org/jenkinsci/plugins/durabletask/BourneShellScript.java#L141-L165. The actual content of the step, i.e., "ls -la" in

Re: Declarative pipeline - override pipeline level agent

Top level docker agents can't be overridden - but you can use the kubernetes plugin in Declarative ( https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/test/resources/org/csanchez/jenkins/plugins/kubernetes/pipeline/declarative.groovy e.g.) which may be what you're looking for. A. On

Re: Declarative script: How to escape 'Program Files (x86)'?

I'd guess you need to escape the spaces in the original string? I dunno - I don't have a Windows environment handy to test on. A. On Wed, Apr 18, 2018 at 6:28 AM, David Aldrich wrote: > My declarative script contains: > > > > environment { > >

Re: Creating Threads in Jenkins Pipeline

No, that's why we have parallel. On Oct 12, 2017 11:53, "Nitish Kumar" wrote: > Hi, > > Is there anyway by which I can run multiple threads in Jenkins Pipeline > without using parallel construct? > > Thanks > > -- > You received this message because you are subscribed

Re: Does 'trigger' directive in pipeline actually mean only retrigger?

Yeah, the job has to run at least once after you've added the triggers directive for it to register, and then it'll be fine. A. On Fri, Sep 22, 2017 at 12:54 PM, Vineet Naik wrote: > Hi, > > I have created a job (Jenkins ver. 2.60.3) using pipeline definition and > it's

Re: Derative Pipeline: unstable build / best practices

What's the output of your tests? If they're generating either junit output or another format that can be read by https://wiki.jenkins.io/display/JENKINS/xUnit+Plugin, and you're using junit or xunit to add those test results to your build, any test failure will result in the build being set to

Re: build user id in declarative pipeline

Put the rest of your steps inside the {} A. On Tue, Sep 12, 2017 at 3:09 PM Russ Cox wrote: > Hi, I'm using Jenkins to run a bunch of self service jobs and need to be > able to determine the user id of the person who ran a job. > > We've been doing this with the scripted

Re: GitHub pull request for pipelines

I think you'll find that multi branch does the trick - I had been using various pull request builder plugins previously, and multi branch gave me just about everything that the pull request builders did with a much smoother experience overall. A. On Tue, Sep 12, 2017 at 7:28 PM Sharon Grubner

Re: Invoking a declarative pipeline from shared libraries

See https://issues.jenkins-ci.org/browse/JENKINS-46547 - this will probably make it into Declarative 1.3, landing hopefully end of October. On Wed, Sep 13, 2017 at 2:25 PM Sebastien Crete wrote: > Where you define your shared libraries ? > > with shared-lib in DP i

FYI: Declarative 1.2 beta available in experimental update center

Just a heads up - Declarative Pipelines has a beta for the upcoming 1.2 release available in the experimental update center now, 1.2-beta-4. You can learn about what's in this release at https://wiki.jenkins.io/display/JENKINS/Pipeline+Model+Definition+Plugin, but the main changes are the

Re: Growing config.xml with GitLab plugin

news! Do we just upgrade all the plugins > to get the fix? > > Qiang > > > > On Friday, June 16, 2017 at 9:08:33 AM UTC-5, Andrew Bayer wrote: > >> Yup, that was entirely my bad, but is now fixed. Sorry about that! >> >> A. >> > On Fri, Jun 16,

Re: Growing config.xml with GitLab plugin

?focusedCommentId=302837=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-302837 in the Jenkins Script Console to manually clean up the bogus properties. A. On Fri, Jun 16, 2017 at 10:07 AM, Andrew Bayer <andrew.ba...@gmail.com> wrote: > Yup, that was entirely my bad, but is

Re: Growing config.xml with GitLab plugin

Yup, that was entirely my bad, but is now fixed. Sorry about that! A. On Fri, Jun 16, 2017 at 1:09 AM, Dan Tran wrote: > we encounter similar issue with declarative pipeline upgrade > https://groups.google.com/forum/#!topic/jenkinsci-users/lAyx4kof0wU > > For you case, you

Re: Can environment directive be used in post?

Fwiw, in this case, you'd want to use withCredentials rather than withEnv. A. On Jun 15, 2017 8:18 AM, "Idan Adar" wrote: > Thanks. I ended doing what I needed doing as part of the last stage > instead of in post. > > On Wednesday, June 14, 2017 at 9:54:06 PM UTC+3, Kevin Burnett

Re: Declarative multibranch pipeline: StackOverflowException after trying to specify agent label

Or just install the now-released 1.1.6. Everything does have to build to get fixed, but you can bypass that by running the script at https://issues.jenkins-ci.org/browse/JENKINS-44809?focusedCommentId=302837=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-302837 in the

Re: Declarative multibranch pipeline: StackOverflowException after trying to specify agent label

So this ended up being an actual bug in Declarative. Sigh. Working on it. A. On Sun, Jun 11, 2017 at 8:12 AM ST wrote: > FYI: Downgrading didn't help, not sure what you mean by "dashboard or > monitor". The only similar plugin names I've installed are > >-

Re: Checkout from multiple SCMs/repos in declarative pipeline?

Yeah, you can use something like stages { stage("foo") { steps { dir("some-dir") { checkout ... } } } On Thu, Jun 8, 2017 at 12:02 PM, Mark Waite wrote: > The scripted pipeline has a dir() and a ws() command which can be used as > a

Re: declarative: how can agent { docker { image 'foo:latest' }} really get the latest version?

It's running on the agent. If the behavior here is wrong, please do open a JIRA. Thanks! A. On Fri, May 19, 2017 at 1:30 PM Matt Stave wrote: > If you run such a job the 1st time, all is well. > If you run it again, it may or may not decide to grab the latest version > vs.

Re: fileExists on declarative pipeline

If statements, variable assignment, and the like are only allowed in Declarative if they're within a script {...} block inside the steps {...} block. A. On Mon, May 22, 2017 at 9:43 AM Thiago Carvalho Davila < thiago.dav...@serpro.gov.br> wrote: > Hello, > > I want to run unit tests only if

Re: Declarative script: specify build trigger in GUI or script?

A couple questions - is this being specified in a Jenkinsfile coming from SCM? Have you run the build once? A. On Mon, May 22, 2017 at 10:00 AM David Aldrich wrote: > Hi, > > I'm confused about how to specify a build trigger for a declarative > script. I want the

Re: sshagent with Declarative Jenkinsfile

I believe it should be - just use the standard sshagent syntax inside the steps block. A. On Mon, Apr 17, 2017 at 7:09 PM, Svend Sorensen wrote: > Is it possible to use the SSH Agent Plugin with a declarative Jenkinsfile? > I haven't found any examples online. > >

Re: Groovy Security Advisory

Basically, the Groovy plugin (and a bunch of other plugins with Groovy scripting involved) now go through the script security process. So by default, not everything is white listed in a system Groovy script. There are no changes to non-system Groovy scripts, and you can approve scripts or

Re: Declarative pipelines per branch and reusable stages (keeping it DRY)

That is the case, yes. And that validation is expecting to find pipeline { ... } at the top-level of the Jenkinsfile - pretty much everything else depends on that. A. On Thu, Apr 13, 2017 at 1:28 PM, Kenneth Brooks wrote: > Got a chance to play around with some of

Re: Declarative Syntax: ability to run multiple stages inside a single agent

Are you wanting to use the same node for most, if not all, of the pipeline? If so, just use the top level agent directive. A. On Wed, Apr 12, 2017 at 1:18 PM Kenneth Brooks wrote: > As a user, I want to run multiple stages inside a single agent. > > Today we use the

Re: How to replace withCredentials([usernamePassword ... with credentials(...)

FOO = credentials('id') will create environment variables FOO_USR and FOO_PWD On Apr 6, 2017 8:42 AM, "Idan Adar" wrote: Perhaps Robert (CCed) can help? On Thursday, April 6, 2017 at 6:26:00 PM UTC+3, Idan Adar wrote: > > In declarative pipeline, one can use credentials()

Re: Valid use of environment directive

No, that's definitely not intended to work that way, and it probably won't work. On Apr 6, 2017 9:09 AM, "Idan Adar" wrote: > Yes, that's how I do it in my actual Jenkinsfile, but I thought maybe in a > Declarative pipeline this works differently... > > On Thursday, April 6, 2017

Re: Access build duration inside declarative pipeline

, March 21, 2017 at 2:19:18 PM UTC+13, Andrew Bayer wrote: >> >> And a PR up at https://github.com/jenkinsci/workflow-support-plugin/ >> pull/33 >> >> On Mon, Mar 20, 2017 at 6:11 PM, Andrew Bayer <andrew...@gmail.com> >> wrote: >> >>> This

Re: Access build duration inside declarative pipeline

And a PR up at https://github.com/jenkinsci/workflow-support-plugin/pull/33 On Mon, Mar 20, 2017 at 6:11 PM, Andrew Bayer <andrew.ba...@gmail.com> wrote: > This is more of a general Pipeline matter than just Declarative, fwiw. > I've opened https://issues.jenkins-ci.org/browse/J

Re: Access build duration inside declarative pipeline

This is more of a general Pipeline matter than just Declarative, fwiw. I've opened https://issues.jenkins-ci.org/browse/JENKINS-42952 for this and will get a PR up shortly. A. On Mar 20, 2017 15:41, "Nick Le Mouton" wrote: Hi, My current jobs use the Slack plugin

Re: Future of 'pipeline' in the context of Blue Ocean?

The Blue Ocean visualization works equally well for any Pipeline, whether Scripted or Declarative. The Pipeline editor in Blue Ocean only works with Declarative, but that's the only difference. On Mar 12, 2017 17:19, "Gardell, Steven" wrote: > Not surprisingly the Blue

Re: Interactive input with new DSL

Actually, "agent none" on a stage does nothing. I'm still trying to find an effective way to solve this use case in Declarative. A. On Mon, Mar 6, 2017 at 2:25 PM R. Tyler Croy wrote: > (replies inline) > > On Mon, 06 Mar 2017, Travis Camechis wrote: > > > So if you define

Re: Double changes in Declarative Pipeline job

This isn't Declarative specific, fwiw. I'll try to take another look at the change log logic this week. A. On Sun, Feb 26, 2017 at 9:33 PM Andreas Magnusson < andreas.ch.magnus...@gmail.com> wrote: > We happily using Declarative Pipeline here, however I've noticed from the > very beginning that

Re: [Declarative Pipeline] Configure System -->Pipeline Model Definition reset after restart

Actually, I've created the JIRA - https://issues.jenkins-ci.org/browse/JENKINS-42027 On Tue, Feb 14, 2017 at 12:40 PM, Andrew Bayer <andrew.ba...@gmail.com> wrote: > Verified - per-folder config settings persist, but global config settings > do not. Whacky. We'll fix it, but pl

Re: [Declarative Pipeline] Configure System -->Pipeline Model Definition reset after restart

Verified - per-folder config settings persist, but global config settings do not. Whacky. We'll fix it, but please do open that JIRA. A. On Tue, Feb 14, 2017 at 12:36 PM, Andrew Bayer <andrew.ba...@gmail.com> wrote: > Ah, the label and registry settings - could you please op

Re: [Declarative Pipeline] Configure System -->Pipeline Model Definition reset after restart

Ah, the label and registry settings - could you please open a JIRA for that? On Tue, Feb 14, 2017 at 11:50 AM, Dan Tran wrote: > > all the settings at Manage Jenkins --> Configure System --> Pipeline > Model Definition are empty after jenkins restart > > The jobs are

Re: [Declarative Pipeline] currentBuild.result is not set

Yup - currentBuild.result isn't actually set until either something is explicitly setting the status (like a failure or unstable) or the build ends, at which point it's set to success if still null. So basically null is equivalent to success. A. On Sat, Feb 11, 2017 at 9:49 AM Dan Tran

Re: [Declarative pipeline] Setting environment variable based on other environment var

I'm on a plane right now so can't find it, but there's an open ticket for this and we'll be looking into it shortly. A. On Feb 8, 2017 08:19, "Staffan Forsell" wrote: > Using the following declarative pipeline: > > pipeline { > agent any > environment { > WSROOT =

Re: [Declarative Pipeline] Using Dockerfile not in root of checkout

I've got a PR up for this now - https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/107 A. On Sun, Feb 5, 2017 at 9:01 PM, Staffan Forsell wrote: > Hmmm, of course I found https://issues.jenkins-ci.org/browse/JENKINS-41668 > a couple of minutes later... > > On

Re: [Declarative Pipeline] Running all stages under a sub directory

Seems related to https://issues.jenkins-ci.org/browse/JENKINS-41118 but distinct - open a JIRA and we'll triage it when we go through feature requests late next week or the week after to figure out what comes next. =) A. On Mon, Jan 30, 2017 at 10:45 PM, Dan Tran wrote: > Hi

Re: how to setup pipeline {agent} from the private Docker hub repo?

We recently added registry support to Declarative - register the credentials needed for the private registry in Jenkins' UI and then you can do: agent { docker { image "image name" registryUrl "https://wherever; registryCredentialsId "credsId" } } On Fri, Jan 27, 2017 at 9:43 AM

Re: Timeout message unclear. Bug?

Can you post your full pipeline? It looks like there are other errors going on here. A. On Tue, Jan 17, 2017 at 10:31 AM, Sam K wrote: > In declarative pipeline, I've created a timeout block like so > > timeout(time:1, unit:'HOURS') { > > // Do something here > > } > >

Re: [Declarative Pipeline] Non-executed stages report success

017 at 11:50:10 AM UTC-6, Andrew Bayer wrote: > > That's actually addressed with Blue Ocean - we mark failed stages with a > special tag that Blue Ocean knows to treat as a failure. I think we could > probably do the same in stage view - could you possibly open a JIRA for > that?

Re: [Declarative pipepipe] Reusable stages ?

No, it is not. You can put the contents of the steps block into a library function and call that, but not the entire stage or stages blocks. A. On Sat, Jan 7, 2017 at 10:52 PM Dan Tran wrote: > > Hi > > is it doable to place "stages" block into a jenkinsfile lib for reuse >

Re: [Declarative Pipeline] TestNg report

That should still work - though it'd be great if the testng plugin could get a "@Symbol("testng")" annotation added to its descriptor! A. On Thu, Jan 5, 2017 at 2:17 AM, Dan Tran wrote: > > Hi > > Current pipeline, this is the snippet for testng report > > step([$class:

Re: [Declarative Pipeline] Non-executed stages report success

That's actually addressed with Blue Ocean - we mark failed stages with a special tag that Blue Ocean knows to treat as a failure. I think we could probably do the same in stage view - could you possibly open a JIRA for that? Thanks! A. On Jan 3, 2017 15:52, "Chris Carson"

Re: Jenkins Pipeline - fail a stage but continue the build

There's no *easy* way to do this - in Declarative + Blue Ocean, we now have this capability, but it relies on adding some additional metadata to the "failed" stage that Blue Ocean reads. That said, if you don't care about the visualization (i.e., the stage is marked as passed in Blue Ocean or the

Re: [Declarative Pipeline] default params not working after checkout

This is using param.xyz? That should be getting the default value - if it's not, definitely open a JIRA. On Jan 2, 2017 18:21, "Dan Tran" wrote: > Hi > > My Jenkinsfile has a few parameters with default values and are fed into > maven step via -Dxxx=${param.yyy} > > the

Re: declarative pipeline with File Data Provider

Could you open a JIRA regarding configFileProvider support in Declarative? Feels like this is something we should make more elegant. A. On Jan 1, 2017 01:16, "Dan Tran" wrote: Hi, I am experimenting with declarative pipeline and try to port this

Re: Declarative Piepline: conditional execution of stage/steps depending on branch

s/etc... usable in normal > stages so i can execute a stage only if the previous one is success? > > Le lundi 21 novembre 2016 20:25:46 UTC+1, Andrew Bayer a écrit : >> >> Hi - >> >> In the latest release of Declarative Pipelines (0.6), we've got a new >>

Re: Block Jobs from running on same nodes

Yup, that's exactly the use case Throttle Concurrent Builds plugin was written for. =) On Dec 8, 2016 07:59, "Andrew Gray" wrote: > Hey all, > > Is there a known way to be able to block a job from running on some node > ONLY IF there are other specified jobs running on that

Re: Declarative Piepline: conditional execution of stage/steps depending on branch

Hi - In the latest release of Declarative Pipelines (0.6), we've got a new "when" section on stages to do exactly what you want - https://github.com/jenkinsci/pipeline-model-definition-plugin/wiki/Advanced#controlling-when-stages-execute A. On Wed, Oct 26, 2016 at 9:09 AM, Eddard

Re: Trigger from pipeline model definition plugin

So the symbol on SCMTrigger was originally "scm", which turned out not to work in Pipeline due to overlapping with the auto-generated "scm" global variable. I changed the symbol to "pollScm" as of core Jenkins 2.22, but that means it won't work in Declarative on earlier core versions. In scripted

Re: New version of Declarative Pipelines (pipeline-model-definition-plugin) released

Wiki page restored, and I already did the incompatible version thingie. =) A. On Thu, Nov 3, 2016 at 1:15 PM, James Dumay <jdu...@cloudbees.com> wrote: > Thanks Andrew for all your work to improve the ease-of-use for Pipeline! > > > On Thursday, November 3, 2016 at 4:29:02

New version of Declarative Pipelines (pipeline-model-definition-plugin) released

FYI - I've released version 0.5 of Declarative Pipelines today, and it does have a significant syntax change that breaks compatibility with earlier versions. See https://github.com/jenkinsci/pipeline-model-definition-plugin/wiki/Version-History-and-Changes#version-05 for more info, but the gist is

Re: New Pipeline plugin: Pipeline Model Definition

gt; On Tuesday, August 30, 2016 at 12:33:30 PM UTC-5, Andrew Bayer wrote: >> >> Hey all - >> >> I've released a first preliminary version (0.1) of a new plugin, >> Pipeline: Model Definition. It's intended to provide a more >> config-like/declarative way to define

Re: Pipeline stage deprecated without block

Basically, the new syntax is: stage("Checkout") { checkout scm } A. On Thu, Sep 1, 2016 at 6:04 PM, Mark Waite wrote: > Thanks for asking the question! I see the same message and didn't find an > explanation (at least that I understood) of the intention for a

Re: Jenkins-LSCI (Life Sciences Continuous Integration) name trademark and usage question

I believe this needs board approval. A. On Thu, Sep 1, 2016 at 7:25 AM, Ioannis Moutsatsos wrote: > Greetings to all; > > We have developed a number of scientific applications based on Jenkins-CI. > Essentially we are able to deliver scientific workflows and data

Re: New Pipeline plugin: Pipeline Model Definition

Oh, and I'll be presenting on this at Jenkins World on Thursday the 15th in the afternoon, with a demo during lunch time, and will be around to chat all week. =) A. On Tue, Aug 30, 2016 at 10:32 AM, Andrew Bayer <andrew.ba...@gmail.com> wrote: > Hey all - > > I've released a fi

New Pipeline plugin: Pipeline Model Definition

Hey all - I've released a first preliminary version (0.1) of a new plugin, Pipeline: Model Definition. It's intended to provide a more config-like/declarative way to define Pipelines, with features like better syntactic/semantic error messages, an easy way to specify notifications or post-build

Re: What I miss with Pipeline: Console output from each node

Yeah, we still need parallel execution split out in the visualization and log view... A. On Wed, Jun 1, 2016 at 10:31 AM, Patrick Wolf wrote: > Yes, as Craig mentioned this is partly solved using Stage View but the log > view should be much more informative and readable

Re: Multibranch pipeline, problem running scripts

You need to do a "checkout scm" once you're in the node block. Also, try "sh ./myscript.sh" rather than .execute(). A. On Monday, May 30, 2016, Adalberto Castelo wrote: > Hello! > > I'm new to jenkins, and I'm trying to get a simple multibranch pipeline to > work.

Re: plugin info

Assuming you're using a freestyle job, that's the Maven task in Jenkins core. If you're using a Maven job, up that's the Maven plugin. On Friday, February 12, 2016, Irfan Sayed wrote: > Hello, > > I need to verify the build option "invoke top level maven targets" is from >

Re: Generate pipeline jobs like with job-dsl

You can actually generate Pipeline jobs *with* Job DSL - look for the "workflow" stuff in the Job DSL API Viewer - https://jenkinsci.github.io/job-dsl-plugin/#path/workflowJob A. On Tue, Feb 9, 2016 at 3:27 AM, Carlos Lucas wrote: > Hi, > > Nowadays, we are using a

Re: How can I POST data to a remote service in Jenkins pipeline/workflow?

So using HTTPBuilder from Pipeline is not a good idea - see https://issues.jenkins-ci.org/browse/JENKINS-26192 - there's work in progress on https://github.com/jenkinsci/http-request-plugin/pull/13 for adding Pipeline support to the http-request-plugin, which is probably the direction you'd want

Re: How to List Plugin on Main Plugins Page

I've added the "plugin-must-be-labeled" label to your plugin wiki page. That should eventually get it to show up in the bottom section of the page, until you give it a more appropriate label. A. On Mon, Feb 1, 2016 at 11:15 AM, Steve Taylor < steve.tay...@openmakesoftware.com> wrote: > > I have

NOTICE: Plugins without wiki pages will stop appearing in the Update Center

As of today or tomorrow, depending on when https://github.com/jenkinsci/backend-update-center2/pull/34 is merged, plugins without wiki pages will no longer show up in the Update Center. New plugins without wiki pages added since June already didn't show up, but now already-existing plugins are

Re: Looking for a Plugin to hook Build Deletion

You can see an example of doing something like that at https://github.com/jenkinsci/associated-files-plugin/blob/master/src/main/groovy/org/jenkinsci/plugins/associatedfiles/AssociatedFilesRunListener.groovy . A. On Tue, Dec 22, 2015 at 1:11 PM, John Mellor wrote: >

Re: Workflows and SCM Polling

I believe that if you pass "poll: true" to the "scm" step, it'll use that particular scm config for polling. A. On Mon, Dec 21, 2015 at 11:05 AM, Mark Bidewell wrote: > I am considering Workflows to automate build and release. Can a workflow > be called in a CI polling

Re: Looking for input: Workflow scripting best practices

<d...@fortysix.ch> wrote: > This might be an interesting one: > http://technologyconversations.com/2015/12/08/blue-green-deployment-to-docker-swarm-with-jenkins-workflow-plugin/ > /Domi > > On 10 Dec 2015, at 15:47, Andrew Bayer <andrew.ba...@gmail.com> wrote: > >

Looking for input: Workflow scripting best practices

Hey all! I'm about to start working on a resource for Workflow scripting best practices, and thought I'd ask y'all if you have any good pointers to start from - existing blog posts, docs, etc, examples of what you think are particularly good Workflow scripts in GitHub or elsewhere, and so on.

Re: Looking for input: Workflow scripting best practices

t; might be useful . . ? > > On Thu, Dec 10, 2015 at 9:47 AM, Andrew Bayer <andrew.ba...@gmail.com> > wrote: > >> Hey all! >> >> I'm about to start working on a resource for Workflow scripting best >> practices, and thought I'd ask y'all if you have any goo

Re: JDK installer from java.sun.com is asking for the JDK ID

I've seen it in the latest LTS - only thing I've found that clears it up is restarting a few times and force-updating. I think it might be the cert issues on tool installer metadata that Kohsuke's supposed to fix. =) A. On Wed, Dec 9, 2015 at 10:32 AM, Baptiste Mathus wrote: >

Re: [workflow] How do you approach multiproject builds in workflow?

This is a really good question. The most Workflow-y way to do this would be the "one big workflow" model. My instincts, admittedly, are to break it up more so that each project can be built independently as well as part of the whole Workflow - I haven't yet found an elegant way to do that in a

Re: disable disk usage calculation

Yeah, I tried hacking it to not do that, and, well, it either kept doing it or just didn't work. I haven't actually played with https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Simple+Disk+Usage+Plugin yet, but I believe it's intended to address a lot of the performance problems with the disk

Re: disable disk usage calculation

vascript:_e(%7B%7D,'cvml','jenkinsci-users@googlegroups.com');>> on > behalf of Andrew Bayer <andrew.ba...@gmail.com > <javascript:_e(%7B%7D,'cvml','andrew.ba...@gmail.com');>> > Reply-To: "jenkinsci-users@googlegroups.com > <javascript:_e(%7B%7D,'cv

Re: How to use Throttle Concurrent in WorkFlow

Thanks - I'll dig into this later this week. A. On Mon, Nov 30, 2015 at 7:29 AM, Dave Lawrence wrote: > JIRA created. > > https://issues.jenkins-ci.org/browse/JENKINS-31801 > > Thanks, > > Dave > > -- > You received this message because you are subscribed to the Google

Re: How to use Throttle Concurrent in WorkFlow

Could you open a JIRA for this? I'll try to take a look. A. On Thu, Nov 26, 2015 at 10:28 AM, wrote: > > Hello, > > Le lundi 16 novembre 2015 19:00:32 UTC+1, Dave Lawrence a écrit : >> >> I am looking to use Throttle Concurrent Builds in a WorkFlow. >> > >

Re: Workflow question - children jobs as steps?

Yeah, separate component jobs using the global library to replace the "generic" jobs we've used for building packages on all the different platforms we support, and the "full" build launching the component jobs via workflow as well seems to be the direction that's making sense for the use case.

Workflow question - children jobs as steps?

Hey! I'm working on migrating an existing build setup with a number of individual "component" builds that both can run individually and run as part of a "full" build. I'm using the parameterized trigger plugin for all this - the component builds behave slightly differently depending on whether

Re: Make auto-installed tools available to Freestyle projects

The tool environment plugin is exactly what you're looking for. On Friday, October 9, 2015, Shane Turner wrote: > Thanks for the reply, Arnaud. > > > > I should have been more clear though. In my case, I want to have Maven > available for a shell script build step. In

Re: losing build history in configuration matrix jobs

Could you open a bug for this? A. On Thu, Nov 29, 2012 at 3:28 AM, Michaël Serisier michael.seris...@gmail.com wrote: Hi all, I have several jobs set to use a configuration matrix. Since I upgraded to 1.492, it looks like builds are lost after each Jenkins restart. This happens for some

Re: Builds of new configuration in a matrix build are lost after some time.

Any luck with 1.492? I'm seeing this with 1.490. A. On Wed, Nov 28, 2012 at 1:13 AM, B.Latinville blatinvill...@gmail.comwrote: I created a new job yesterday, copy from one existing matrix job. I run a single build, could see the build results. This morning it was not visible any more. I

Re: Updates site with old certificate

I'm making sure this gets Kohsuke's attention tomorrow morning Europe time. A. On Wed, Apr 18, 2012 at 2:58 PM, Alex Butum alex.bu...@gmail.com wrote: There is an open JIRA issue regarding this problem: https://issues.jenkins-ci.org/browse/JENKINS-13499 On Wednesday, 18 April 2012 21:05:25

Re: Groovy Plugin: Obtain upstream builds?

I think you'd have to use the system groovy build step to do this, but it should be possible there. A. On Tue, Mar 20, 2012 at 10:08 AM, Nicky Ramone nixe...@gmail.com wrote: Hi. Is it possible to obtain the upstream build objects in a groovy script executed by the Groovy Plugin? You can