Virtualbox plugin : failed to launch slave agent via java web start

Hi, I used the folk on Github which supports virtualbox 5.1.6. Then I installed and configured the node, it could run the virtualbox after I clicked the launch button, but it always failed to set the agent online. The log is shown below. I have Jenkins ver. 2.89.2 and virtualbox 5.1.6

Re: How to get Multibranch Pipeline tab under New Items

Apparently the plugins I installed were all right, I just needed to upgrade to jenkins 2.76 On Tuesday, January 2, 2018 at 10:27:11 AM UTC-8, ri...@rijosimon.com wrote: > > What plugins do I need to install to get Multibranch Pipeline tab under > New Items? I installed a few that I thought I

Re: Virtualbox plugin : failed to launch slave agent via java web start

-- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails

Re: Releasing with declarative pipeline

OK, I've made a small amount of progress. I've learned that: 1. The release plugin doesn't work with pipeline 2. The promoted build plugin doesn't work with pipeline 3. Some users are using the "input" command to cause the build to hang for a few days, and then be able to make a release. This

Re: github quota limit when scanning with the addition of tags

On 3 January 2018 at 14:41, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > This is the limitation of 5000 requests per hour. > > Ideally we would look into caching the github responses so that duplicate > requests could be eliminated... but my preliminary analysis shows that > would

Re: Declarative pipeline "when" tag is pushed

Steven Foster 于2017年12月21日 周四上午9:54写道： > I think you can get that with this: > > when { > expression { > env.TAG_NAME != null > } > } > Thanks,it works > > You get the env.TAG_NAME from the branch api when it's a tag build. > A shortcut would be

Re: Releasing with declarative pipeline

I've not used that plugin in the past, but there are a couple of examples in the below test: - https://github.com/jenkinsci/release-plugin/blob/master/src/test/java/hudson/plugins/release/pipeline/ReleaseStepTest.java -- You received this message because you are subscribed to the Google

Re: Virtualbox plugin : failed to launch slave agent via java web start

-- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails

Re: Virtualbox plugin : failed to launch slave agent via java web start

-- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails

Re: Releasing with declarative pipeline

Hi Ari, AFAIK, the release plugin is supported with pipelines: https://issues.jenkins-ci.org/browse/JENKINS-40765 (release 2.7+). Regarding the promoted build plugin, I'm afraid it's still an open topic: https://issues.jenkins-ci.org/browse/JENKINS-36089 Input command is the one I used in the

Re: Long delay sending emails

The logging in the email-ext plugin didn't provide much information, other than that it takes approx. the same time for each committer in the build. ie 1min / committer. Google helped me to enable logging on the Active Directory plugin, and I have found the following: 1) We have our domain name

Does Job DSL plugin support Hidden Parameter and Extensible Choice Parameter?

Hello, I need to write a job DSL that supports Hidden Parameter and Extensible Choice Parameter . Are these parameters supported in Job DSL plugin? Thanks! Vicki -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this

Re: Releasing with declarative pipeline

I’m not really sure how to read that. I tried pipeline { release { } } But got an error. Maybe it needs to contain steps? Or stages? Ari On 4 January 2018 at 1:54:02am, Victor Martinez ( victormartinezru...@gmail.com) wrote: I've not used that plugin in the past, but there are a couple of

Re: github quota limit when scanning with the addition of tags

> > There are only two good reasons to scan periodically: > 1. To recover from missed events (keep in mind that follow-up commits will > typically recover anyway, so the only case here is a commit before bedtime > not being built by morning because that event was not delivered by GitHub) >

Re: Releasing with declarative pipeline

I just ran a raw example and it basically triggers another job with some arguments. stage("Build") { node { sh 'echo mvn' } } stage("Release") { release 'archive' } Where archive is just a basic job with some basic hello world in the release section It looks like a kind of

Re: How to use podTemplate in a declarative pipeline with the kubernetes-plugin.

Hey All, Is volume support still in development? I would like to use declarative syntax with k8s plugin, but our agent containers share persistence across pod with volume mounts. -- Best Tim Zhukov On Friday, September 22, 2017 at 12:11:28 PM UTC-4, Vincent Heet wrote: > > Hi Chris, > > No

Re: Does Job DSL plugin support Hidden Parameter and Extensible Choice Parameter?

Many thanks! On Wednesday, January 3, 2018 at 1:55:43 PM UTC-8, Victor Martinez wrote: > > JobDSL supports mostly all the plugins, further details: > Automatically-Generated-DSL > > > You can find its api details

Re: Does Job DSL plugin support Hidden Parameter and Extensible Choice Parameter?

JobDSL supports mostly all the plugins, further details: Automatically-Generated-DSL You can find its api details below: - /plugin/job-dsl/api-viewer/index.html#plugin/extensible-choice-parameter -

Re: Releasing with declarative pipeline

Ah OK. That doesn't seem terribly useful since the other job then cannot be a pipeline because it doesn't support a release stage. What's really needed here is simpler: the ability to put a button in the Jenkins UI with an arbitrary name (like "release") and which triggers the build while

Re: Releasing with declarative pipeline

I am using Git though, I'm not sure about the current availability of this functionality for SVN -- 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

Re: Releasing with declarative pipeline

I have been using the multibranch project's tag build functionality to achieve this. An environment variable is provided when running a tag build, so the pipeline can have a stage which checks for the presence of that variable. Using multibranch to build a single branch seems a little counter

Re: Releasing with declarative pipeline

I think that's a great idea. The main downsides I see are: * the multibranch plugin (which I use already) is pretty flaky. I find it will sometimes reset all the branches to be enabled even though I try to disable old branches to get them out of the view * if you create a lot of branches you

Re: How to use podTemplate in a declarative pipeline with the kubernetes-plugin.

I don't think it is possible, a volumes field would need to be added to KubernetesDeclarativeAgent https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/pipeline/KubernetesDeclarativeAgent.java On Wed, Jan 3, 2018 at 4:46 PM, Tim Zhukov

Re: Kubernetes plugin ( want to run slave as pod )

Hi @carlos in jenkins kubernetes plugin configuration we need to mention in the container template Working directory /home/jenkins command to run slave agent ? arguments to pass to the command ${computer.jnlpmac} ${computer.name} is this correrct what i am given and what is that

Re: Releasing with declarative pipeline

Thanks Victor, Do you have any pointers or examples of the docs for declaration configuration of the release plugin? Ari On Thursday, 4 January 2018 01:23:34 UTC+11, Victor Martinez wrote: > > Hi Ari, > > AFAIK, the release plugin is supported with pipelines: >

github quota limit when scanning with the addition of tags

Now that we've added *Discover tags*[1 ] and a *Build everything*[2 ] strategy, we're running into Github quota limits quite frequently. 18:58:09

Re: HowTo set pipeline step description

+1 for Slava Dubrovskiy's question: 'Is it possible to disable this feature?' Especially when referencing ENV variables which should be masked, this is problematic in the UI for exposing the values of those variables. On Monday, December 4, 2017 at 11:09:34 AM UTC-8, Victor Martinez wrote: >