Hi,
To allow certain signatures in Groovy Sandbox go to Manage Jenkins
- In-process Script Approval.
Please note that if you catch this kind of exceptions the signatures will
not appear there.
Timur
суббота, 7 февраля 2015 г., 10:57:08 UTC+3 пользователь Baptiste Mathus
написал:
IIUC, for
Hi Christoph,
I use the plain Jenkins parameters for that, (checkmark for This build is
parameterized).
The parameters passed then appear inside the Groovy script as variables but
not environment values.
If you need to set env value you can do the following inside your Groovy
script:
Hi Eric,
You need to understand first what exactly you want to be run and at which
point.
From the quick glance it could be running Chef on already provisioned
server (use SSH to do that when you need it) or creating a new server in
the cloud for running tests etc on it. (It's likely there are
Hi all,
How should I clean the checkout directory using GenericSCM step of
workflow-plugin?
The snippet generator generates the line like the following:
checkout scm: [$class: 'GitSCM', branches: [[name: '*/master']],
extensions: [object of type
Hi Dillon,
You need to wrap your code inside node { ... } block.
You can also use the ws { ... } block to explicitly allocate a workspace.
Don't know yet what is the use case for this as node {} works fine for me.
Regards,
Timur
вторник, 3 февраля 2015 г., 3:32:35 UTC+3 пользователь Dillon
://github.com/jenkinsci/workflow-plugin/tree/master/scm-step (at
least that's what I would expect it to be). Did you try using an additional
General SCM step with the Cleanup workdir option active?
/Thomas
On Sunday, February 1, 2015 at 1:45:16 AM UTC+1, Timur Batyrshin wrote:
Hi Thomas
setting the Locale module directory, I had to add a dir
{ } instruction. Without that the script started in the wrong directory. I
guess, that these are Subversion related issues.
/Thomas
On Monday, January 19, 2015 at 11:05:19 AM UTC+1, Timur Batyrshin wrote:
Hi,
I'd like to store the script
Hi Rob,
AFAIK, git command of workflow plugin does not support that.
Use GeneralSCM for that, like described
at
https://github.com/jenkinsci/workflow-plugin/blob/master/scm-step/README.md#generic-scm-step.
I've defined for that a special function at the start of my workflow script:
def
Hi Cyrille,
For cloning repositories I use the credentialsId, like:
checkout changelog: true, poll: true, scm: [$class: 'GitSCM', branches:
[[name: 'remotes/origin/master']], userRemoteConfigs: [[credentialsId:
'6ab75e78-83c6-423f-97ce-3198c52211a7', url: 'https://github.com/X']]]
You
Hi,
I'd like to store the script for running the flow in Git but it looks like
I can't do the SCM checkout before running the flow.
I could write some additional lines in the flow script (one for checkout
and one load command) but the checkout commands
are too large in the current state (like:
Hi,
Actually I've found that you can browse per parallel branch output by going
to Running Steps in the left job menu.
Can this be made more explicit for the end-user?
Should I create a ticket for that?
Thanks,
Timur
вторник, 13 января 2015 г., 19:14:49 UTC+3 пользователь Timur Batyrshin
Hi,
I've just started to use the new workflow plugin and it looks great.
But I can't get readable output for parallel jobs -- it is heavily
intermixed and hardly readable (see below).
My test flow:
parallel cApps: {
node {
// C applications built by make
dir('c-apps') {
checkout
12 matches
Mail list logo
