Hi
- I am using clearcase plugin
- Jenkins version: 2.58
- In console log--> it was showing changes submitted by auther
- Jenkins does not show the changes from last build
- Jenkins "changes:--> Always shows "No changes from last build."
Any idea how it can be fixed?
--
You rec
A problem occurred while processing the request. Please check our bug
tracker to see if a similar problem has already been reported. If it is
already reported, please vote and put a comment on it to let us gauge the
impact of the problem. If you think this is a new issue, please file a new
iss
How can I do this right - I want the results from a job I run (I need to
run a dozen of these in succession and will email devs if one of them
fails)
try{ BuildResults = build job: 'testJob'; currentBuild.result='SUCCESS'; }
> catch(e){ currentBuild.result = 'FAILURE'; } finally {
> notify_em
Hi Tina, et all,
I'm also trying to configure the Release permission using a groovy script.
I do see that the permission is called CREATE_RELEASE inside an inner class
in the m2Release plugin code on GitHub:
https://github.com/jenkinsci/m2release-plugin/blob/2f2865cffdd7e4be2a60156f245fabc9508d
Hello guys!
Our team has experience with Jenkins. But first time we get a task when we
need to connect to database for getting list of values for select box,
which should be build parameter.
We found https://plugins.jenkins.io/extensible-choice-parameter which has
“System
Groovy Choice parame
Thanks Slide
David
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Slide
Sent: 16 May 2017 16:38
To: jenkinsci-users@googlegroups.com
Subject: Re: How to specify recipients in email-ext step in declarative script?
to: "daldrich," + recipients
Also,
to: "daldrich," + recipients
Also, you may be missing a '}' to close the script block.
On Tue, May 16, 2017 at 7:12 AM David Aldrich
wrote:
> Hi Slide
>
>
>
> Thanks. I tried the code below based on your suggestion but the syntax of
> my change isn’t quite right. Can you help please?
>
>
>
>
Hi Slide
Thanks. I tried the code below based on your suggestion but the syntax of my
change isn’t quite right. Can you help please?
post {
success {
script{ def recipients = emailextrecipients([ [$class:
'DevelopersRecipientProvider'] ])
emailext (to:
Something like this might work:
script {
def recipients = emailextrecipients([ [$class:
'DevelopersRecipientProvider'] ])
emailext(..., to: recipients)
}
On Tue, May 16, 2017 at 6:18 AM David Aldrich
wrote:
> Hi Danny,
>
>
>
> That worked (with email addresses in quotes) – thanks.
>
>
>
Hi Danny,
That worked (with email addresses in quotes) – thanks.
Do you know how I would specify ‘to:’ as a certain email address + committers?
Best regards
David
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Danny Rehelis
Sent: 16 May 2017 14:0
Hey David,
This should be pretty straightforward, try this:
post {
success {
emailext (
to: a...@me.com; a...@him.com,
subject: "SUCCESS",
body: "SUCCESS!"
)
}
failure {
emailext (
t
Cuke report plugin, and the Cuke test result plugin.
The issue is we want the output at the step level, not the scenario level.
This allows explicit manual test instructions to be part of the output.
J
On Monday, May 15, 2017 at 7:04:07 PM UTC-4, James Nord wrote:
>
> I'm pretty sure I implemente
Thank you, but is there a way to do it outside of the hooks? or do you
just have to accumulate all your output as you go and dump it out in the
after block?
On Monday, May 15, 2017 at 7:04:31 PM UTC-4, James Nord wrote:
>
> https://gist.github.com/aslakhellesoy/4072962
--
You received this me
Morgan Blackthorne (2017-05-12 20:05):
So I'm a little confused as to setting job to a value, but then
referencing build.setDescription afterwards... or should that be
job.setDescription?
// loop over jobs (possible also in Script Console)
for (item in hudson.model.Hudson.instance.item
there is a multiple SCM plugin that will let you create a build workspace
from multiple SCMs. I don't know about its triggering operations.
On Tue, May 16, 2017 at 2:42 AM, Kirill Peskov
wrote:
> Hi All!
>
> A rookie question... ;)
>
> I've got a project where 'source' code of the web applicatio
Jesse Glick has answered
in https://issues.jenkins-ci.org/browse/JENKINS-43596
I am working on something that will look like withMaven(options:
[artifacts(), findbugs(unstableOnThreshold: 5), tests(excludes:
'**/PerformanceTest')]) {…}
Cyrille
On Tuesday, May 16, 2017 at 1:52:55 AM UTC-7, Bap
On Thursday, May 11, 2017 at 1:33:33 AM UTC+1, Owen B. Mehegan wrote:
>
> I have been given the unenviable task of mapping out a process for
> upgrading from Jenkins 1.642.4 to the latest LTS (currently 2.46.2). If I
> had to do this blind and unsupported, I'd start by creating a sandbox
> Jen
I'm planning our Jenkins upgrade to the latest version but as this will be
quite a jump in versions is there any recommendations on how best to do
this. I'll be using a test box as a first step.
Is there any benefit or need to first upgrade to an intermediate step to
allow for any substantial c
One relatively easy way would be to change using the following:
http://svn/app/trunk/${revision}
The @ sign must then be added by the user. But this can be checked by using the
validating string parameter and a regular expression string as follows:
(^\@\d*$)|^$
Anything else I think will req
I tend to prefer the hierarchical approach. IMO it should /scale/ better,
being more readable/organized. Without this, you'll indeed end up with very
long options using camelCase.
2017-05-12 20:16 GMT+02:00 Cyrille Le Clerc :
> Note: Mark Lagendijk proposed a hierarchical approach for options in
Hi
I am experimenting with declarative scripts and have this simple script:
pipeline {
agent { label "mypc" }
stages {
stage('build') {
steps {
sh 'python --version'
}
}
}
post {
success {
script: emailext
21 matches
Mail list logo
