There are two things that might make your life easier:
1) Jenkinsfile, you can put this into your source control and then it will
be executed as if it were in the web ui. You just change the option in the
job setup to "Pipeline script from SCM" instead of "Pipeline script". Then
when you push upda
I'm new to Jenkins and am learning how to write groovy scripts for
pipelines. Right now I write my code in VS Code and copy & paste it into
the Jenkins' project, save and build. This gets pretty tedious and time
consuming. Is there a better way to develop scripts without having to
either develo
I have installed a custom plugin and selected restart after installation.
Jenkins is unable to restart after shutdown and showing the following error
in logs.
*hudson.util.PluginServletFilter.addFilter Filter instance is registered too
early: org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenCha
That's correct, right now they can only be created in the root folder.
Please file an issue in JIRA if you'd like request an enhancement for this.
Thanks,
Cliff
On Thu, Oct 26, 2017 at 10:36 AM, wrote:
> Does Blue Ocean support creating new pipelines inside folders? It seems to
> only create a
Thanks Robert,
it helps a lot just knowing what the two different systems are called
(declarative vs. scripted).
Cheers,
C
On Tuesday, 31 October 2017 09:53:58 UTC-5, Robert Hales wrote:
>
> There are 2 different syntaxes. Declarative is the pipeline{} style.
> scripted doesn't necessarily sta
There are 2 different syntaxes. Declarative is the pipeline{} style.
scripted doesn't necessarily start with node{}, but uses that heavily.
Scripted syntax is basically a straight groovy code DSL. Use it when you
need to do more complex and interesting things and aren't afraid to get
down into
Looking at some pipeline scripting examples, I see that there are two
different ways to script a pipeline. One begins with pipeline {} the other
with node {}. What is the difference between the two, and when would I use
one or the other?
thanks,
C
--
You received this message because you are
The powershell step in pipeline is provided by the same plugin that
provides the bat and sh steps. It's separate to the powershell plugin
which is for freestyle jobs.
On 31 Oct 2017 12:51 pm, "itchymuzzle" wrote:
Doesn’t answer my original question, but is a valid work around.
#! /usr/bin/e
Doesn’t answer my original question, but is a valid work around.
#! /usr/bin/env groovy
pipeline {
agent {label 'windows'}
parameters {
string(name: 'Version', defaultValue: '0.1', description: 'What is
the release version?')
}
environment {
PYTHONPATH = "..
Hi
There are many older builds for redhat rpm.
But only the lastest build is available for windows and mac.
Could you make the older builds for them available?
Regards.
Masaru
--
You received this message because you are subscribed to the Google Groups "Jenkins
Users" group.
To unsubscribe fr
Hi,
I have an equivalent problem. I've created an issue
(https://issues.jenkins-ci.org/browse/JENKINS-47479) that was rejected, so
here I am.
When using the jenkins maven build, I got the same error. When i use a
freestyle job, passing the settings in the command line, it works.
How to see th
Hi,
I simply use two *sh* steps, one to start the database and the other to
launch the tests.
More or less like this:
node () {
> // Run mysql
> def mysqlOpts = "..."
> sh "docker --rm -d ${mysqlOpts} mysql"
>
> timeout(time: 120, unit: 'SECONDS') {
> waitUntil {
> // Wait until
12 matches
Mail list logo
