MissingMethodException while using shared libraries

2019-02-28 Thread Kaliyug Antagonist 


Cloudbees 2.121.3.1


Partial Jenkinsfile of the main component that is failing viz. Alfaclient:

properties([parameters([string(defaultValue: "", description: "List of 
components", name: 'componentsToUpdate'),
string(defaultValue: 
"refs%2Fheads%2Fproject%2Fintegration", description: "BuildInfo CommitID", 
name: 'commitId'),
string(defaultValue: "", description: "Tag to release, 
e.g. 1.1.0-integration", name: 'releaseTag'),
string(defaultValue: "", description: "Forked buildInfo 
repo. Be aware right commit ID!!!", name: 'fork')]),
[$class: 'BuildDiscarderProperty', strategy: [$class: 
'LogRotator', artifactDaysToKeepStr: '', artifactNumToKeepStr: '', 
daysToKeepStr: '7', numToKeepStr: '5']],
disableConcurrentBuilds()])

@Library(['jenkins-shared-utilities@integration/CICD-344-refactor-bitbucket-notify-handler','jenkins-shared-stages@integration/CICD-344-refactor-bitbucket-notify-handler','jenkins-shared-pipelines@integration/CICD-344-refactor-bitbucket-notify-handler'])
 _
.
.
.
returnValue = componentPipeline {
componentsToUpdate = rewriteDependencies
commitId = buildInfoCommitId
runOnForkedRepo = forkedRepo
}


The componentPipeline in the above code is a scripted pipeline located in 
vars of *jenkins-shared-pipelines* The partial Jenkinsfile(which doesn't do 
much!) of jenkins-shared-pipelines

#!groovy

@Library(['jenkins-shared-utilities@integration/CICD-344-refactor-bitbucket-notify-handler','jenkins-shared-stages@integration/CICD-344-refactor-bitbucket-notify-handler'])
 _


Partial code for componentPipeline:

def call(body) {
def config = [:]
body.resolveStrategy = Closure.DELEGATE_FIRST
def componentName = null
body.delegate = config
body()
def rewriteDependency = config.componentsToUpdate
def buildInfoCommitId = config.commitId
def forkedBuildInfo = config.runOnForkedRepo

def PIPELINE_NAME = "Component Pipeline"
.
.
.
setupSharedUtils(callingScript: this)
.
.
.
def build_status = "ok"
stage(CLEAN_STAGE) {
.
.
.
bitbucketUtilities.notifyBuildStart("Build ${env.BUILD_ID} started 
at ${env.BUILD_TIMESTAMP}", PIPELINE_NAME)

}
stage(GET_BUILD_INFO) {
.
.
.
build_status = "${COMPILE_STAGE} failed in build ${env.BUILD_ID} 
with exit code ${exit_code}"
bitbucketUtilities.notifyBuildFail(build_status, PIPELINE_NAME)

}   

}


Now comes the main library viz. *jenkins-shared-utilities*. It has the 
following structure: 


*vars* containing scripts that would act as global variables for components 
like *Alfaclient*.

bitbucketUtilities.groovy

import groovy.transform.Field
import com.jenkins.utilities.bitbucket.*
import com.cloudbees.groovy.cps.NonCPS

@Field final String STEP_NAME = getClass().getName()
@Field final BitbucketBuildOperationsHandler bitbucketUtilities = new 
BitbucketBuildOperationsHandler(this,env)

@NonCPS
def notifyBuildStart(String message, String displayName) {

//Remove
println "bitbucketUtilities global vars, env: "+env
validateCall(this, message, displayName)

bitbucketUtilities.notifyBuildStart(message, displayName)
}

@NonCPS
def notifyBuildSuccess(String message, String displayName) {

//Remove
println "bitbucketUtilities global vars, env: "+env

 validateCall(this, message, displayName)

bitbucketUtilities.notifyBuildSuccess(message, displayName)
}

@NonCPS
def notifyBuildFail(String message, String displayName) {

//Remove
println "bitbucketUtilities global vars, env: "+env

validateCall(this, message, displayName)

bitbucketUtilities.notifyBuildFail(message, displayName)
}

@NonCPS
private void validateCall(def script, String message, String displayName) {

if(message == null || message.isEmpty()) {
script.error("[ERROR][${script.STEP_NAME}] Build message not provided")
}

if(displayName == null || displayName.isEmpty()){
script.error("[ERROR][${script.STEP_NAME}] displayName not provided!")
}

}

setupSharedUtils.groovy

import groovy.transform.Field
import com.jenkins.utilities.ServiceLocator

void call(Map parameters = [:]) {
if (parameters?.callingScript == null) {
step.error(
"[ERROR][setupSharedUtils] No reference to surrounding script " +
"provided with key 'callingScript', e.g. 'callingScript: this'.")
} else {
parameters.callingScript.serviceLocator = ServiceLocator.getInstance()
}
}


*src* packages containing classes like BitbucketBuildOperationsHandler

class BitbucketBuildOperationsHandler implements  Serializable {

private def script
private def env
//TODO: Think if this should be an enum but iterating it will be an overhead
private static

Re: sending email for unstable builds

2019-02-28 Thread Faad Sayaou 
thanks @Simon and @Sagar for your responses.  'currentBuild.currentResult'
is definitely what i needed and works as intended.

On Fri, 1 Mar 2019 at 06:37, Simon Bayer  wrote:

> Check This if u need post build actions for different build status:
> https://jenkins.io/doc/pipeline/tour/post/
>
>
>  Ursprüngliche Nachricht 
> Von: Simon Bayer 
> Datum: 01.03.19 06:32 (GMT+01:00)
> An: jenkinsci-users@googlegroups.com
> Betreff: Re: sending email for unstable builds
>
> Dear Faad, dear Sagar,
> U could check the global variable  'currentBuild.currentResult' in e.g.
> post build actions. Maybe it suits your needs. Doks:
> https://opensource.triology.de/jenkins/pipeline-syntax/globals#currentBuild
>
> Best regards
>
>
>  Ursprüngliche Nachricht 
> Von: Sagar Utekar 
> Datum: 01.03.19 03:06 (GMT+01:00)
> An: jenkinsci-users@googlegroups.com
> Betreff: Re: sending email for unstable builds
>
> You can check the status of build by using BUILD_STATUS, if it is unstable
> then send a mail
>
> On Fri, 1 Mar 2019, 02:11 Faad Sayaou,  wrote:
>
>> Hi everyone
>> I am using the extended email plugin for notification when the build
>> fails by using try catch. I will also like to send email when the build is
>> unstable. Below is the structure of my pipeline
>>
>> node {
>>
>>try
>>{
>>
>> stage('Checkout') {
>> cleanWs()
>> checkout scm
>>
>> }
>>
>>
>> stage('Restore') {
>>
>> sh "dotnet restore  $proj"
>>
>>}
>>
>> stage('Build') {
>> sh "dotnet restore  $proj"
>>
>>}
>> stage ('Unit test') {
>>
>>sh "dotnet test  $test"
>>}
>>}
>> } catch (err) {
>>  emailext body:
>> ' ${JOB_NAME} ${BUILD_NUMBER} is failing! Somebody should do 
>> something about that. 
>> https://jenkins-ma.com/job/Test/${BUILD_NUMBER}/console 
>> ',
>>  subject: 'FAILURE', to: 'someEmail..'
>> }
>>
>>
>> I will like to send not only when the pipeline fails but when the build
>> is unstable. thanks
>>
>> --
>> 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 jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/2c7db49d-68ef-4c41-8cd2-39ff6855ad83%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CANYh6tf5h6_LAafRrKLROquy3mO95puNkbMY0%3DATh5uRnkXeyw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/DM6PR15MB3452B3FF105E05324B50A9C4AC760%40DM6PR15MB3452.namprd15.prod.outlook.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 

*Best Regards / Mit freundlichen Grüßen,*

*Faad Sayaou,*

*Embedded Systems for Mechatronics Masters student | FH Dortmund | Germany*

*Fachhochschule Dortmund*

*University of Applied Sciences and Arts*

*Email*: f aad...@gmail.com

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAL2KjjQ-6Q66229-Zh-5BRYtMvRANN-dmOZCwteJ7Re9n%3D1Tcw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: sending email for unstable builds

2019-02-28 Thread Simon Bayer 
Check This if u need post build actions for different build status: 
https://jenkins.io/doc/pipeline/tour/post/


 Ursprüngliche Nachricht 
Von: Simon Bayer 
Datum: 01.03.19 06:32 (GMT+01:00)
An: jenkinsci-users@googlegroups.com
Betreff: Re: sending email for unstable builds

Dear Faad, dear Sagar,
U could check the global variable  'currentBuild.currentResult' in e.g. post 
build actions. Maybe it suits your needs. Doks: 
https://opensource.triology.de/jenkins/pipeline-syntax/globals#currentBuild

Best regards


 Ursprüngliche Nachricht 
Von: Sagar Utekar 
Datum: 01.03.19 03:06 (GMT+01:00)
An: jenkinsci-users@googlegroups.com
Betreff: Re: sending email for unstable builds

You can check the status of build by using BUILD_STATUS, if it is unstable then 
send a mail

On Fri, 1 Mar 2019, 02:11 Faad Sayaou, 
mailto:faad...@gmail.com>> wrote:
Hi everyone
I am using the extended email plugin for notification when the build fails by 
using try catch. I will also like to send email when the build is unstable. 
Below is the structure of my pipeline

node {

   try
   {

stage('Checkout') {
cleanWs()
checkout scm

}


stage('Restore') {

sh "dotnet restore  $proj"

   }

stage('Build') {
sh "dotnet restore  $proj"

   }
stage ('Unit test') {

   sh "dotnet test  $test"
   }
   }
} catch (err) {
 emailext body:
' ${JOB_NAME} ${BUILD_NUMBER} is failing! Somebody should do 
something about that. 
https://jenkins-ma.com/job/Test/${BUILD_NUMBER}/console',
 subject: 'FAILURE', to: 'someEmail..'
}

I will like to send not only when the pipeline fails but when the build is 
unstable. thanks

--
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 
jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/2c7db49d-68ef-4c41-8cd2-39ff6855ad83%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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 
jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANYh6tf5h6_LAafRrKLROquy3mO95puNkbMY0%3DATh5uRnkXeyw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/DM6PR15MB3452B3FF105E05324B50A9C4AC760%40DM6PR15MB3452.namprd15.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.

Re: sending email for unstable builds

2019-02-28 Thread Simon Bayer 
Dear Faad, dear Sagar,
U could check the global variable  'currentBuild.currentResult' in e.g. post 
build actions. Maybe it suits your needs. Doks: 
https://opensource.triology.de/jenkins/pipeline-syntax/globals#currentBuild

Best regards


 Ursprüngliche Nachricht 
Von: Sagar Utekar 
Datum: 01.03.19 03:06 (GMT+01:00)
An: jenkinsci-users@googlegroups.com
Betreff: Re: sending email for unstable builds

You can check the status of build by using BUILD_STATUS, if it is unstable then 
send a mail

On Fri, 1 Mar 2019, 02:11 Faad Sayaou, 
mailto:faad...@gmail.com>> wrote:
Hi everyone
I am using the extended email plugin for notification when the build fails by 
using try catch. I will also like to send email when the build is unstable. 
Below is the structure of my pipeline

node {

   try
   {

stage('Checkout') {
cleanWs()
checkout scm

}


stage('Restore') {

sh "dotnet restore  $proj"

   }

stage('Build') {
sh "dotnet restore  $proj"

   }
stage ('Unit test') {

   sh "dotnet test  $test"
   }
   }
} catch (err) {
 emailext body:
' ${JOB_NAME} ${BUILD_NUMBER} is failing! Somebody should do 
something about that. 
https://jenkins-ma.com/job/Test/${BUILD_NUMBER}/console',
 subject: 'FAILURE', to: 'someEmail..'
}

I will like to send not only when the pipeline fails but when the build is 
unstable. thanks

--
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 
jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/2c7db49d-68ef-4c41-8cd2-39ff6855ad83%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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 
jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANYh6tf5h6_LAafRrKLROquy3mO95puNkbMY0%3DATh5uRnkXeyw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/DM6PR15MB3452322898E87D82EF2A5E41AC760%40DM6PR15MB3452.namprd15.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.

Re: sending email for unstable builds

2019-02-28 Thread Sagar Utekar 
You can check the status of build by using BUILD_STATUS, if it is unstable
then send a mail

On Fri, 1 Mar 2019, 02:11 Faad Sayaou,  wrote:

> Hi everyone
> I am using the extended email plugin for notification when the build fails
> by using try catch. I will also like to send email when the build is
> unstable. Below is the structure of my pipeline
>
> node {
>
>try
>{
>
> stage('Checkout') {
> cleanWs()
> checkout scm
>
> }
>
>
> stage('Restore') {
>
> sh "dotnet restore  $proj"
>
>}
>
> stage('Build') {
> sh "dotnet restore  $proj"
>
>}
> stage ('Unit test') {
>
>sh "dotnet test  $test"
>}
>}
> } catch (err) {
>  emailext body:
> ' ${JOB_NAME} ${BUILD_NUMBER} is failing! Somebody should do 
> something about that. https://jenkins-ma.com/job/Test/${BUILD_NUMBER}/console 
> ',
>  subject: 'FAILURE', to: 'someEmail..'
> }
>
>
> I will like to send not only when the pipeline fails but when the build is
> unstable. thanks
>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/2c7db49d-68ef-4c41-8cd2-39ff6855ad83%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANYh6tf5h6_LAafRrKLROquy3mO95puNkbMY0%3DATh5uRnkXeyw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC 2019] - Jenkins project has been accepted!

2019-02-28 Thread Rick 
Good to hear this. And thanks to the Jenkins GSoC org team.

Best regards,
Rick

On Fri, Mar 1, 2019 at 5:13 AM Oleg Nenashev  wrote:

> Dear all,
>
> On behalf of the Jenkins Google Summer of Code
>  org team, I am happy to announce
> that the Jenkins project *has been accepted* to GSoC this year. Congrats
> and thanks to all mentors, org admins and students who has contributed to
> it!
>
> Just to provide some numbers, this is the biggest GSoC ever, 206
> organizations participate in GSoC this year. And it will be hopefully the
> biggest year for Jenkins as well. We have 25 project ideas
>  and more than 30
> potential mentors (and counting!). It is already more than in 2016 and 2018
> all together. There are many plugins, SIGs and sub-projects which have
> already joined GSoC this year. And we have already received messages and
> first contributions from dozens of students, yey!
>
> *What's next?* GSoC is officially announced, and please expect more more
> students to contact projects in our Gitter channels and mailing lists
> . This year there will be
> less traffic in the Developer mailing lists until projects are announced,
> because communications move to SIG and sub-project channels. Student
> project proposal deadline is April 9th, and we will be working hard in
> order to help students to find interesting projects, to explore the area,
> and to prepare their project proposals. We will send more information to
> mentors and students in separate emails.
>
> *I am a student. How to join the project?* We invite you to follow the student
> guidelines  and to reach out
> to potential mentors using chats and mailing lists listed in project ideas.
> If you do not see anything interesting, you can propose your own project
> idea  or check
> out ideas in other organizations
> , you can even
> propose your Jenkins-related ideas there.
>
> *And what about mentors?* We are also looking for more project ideas and
> for Jenkins contributors/users who are passionate about Jenkins and want to
> mentor students. No hardcore experience required, mentors can study the
> project internals together with students and technical advisors. We are
> especially interested in ideas beyond the Java stack, and in ideas focusing
> new technologies and areas (e.g. Kubernetes, IoT, Go, whatever). This
> blogpost 
> by Martin d'Anjou provides the guidelines. If you want to propose a new
> project idea, please do so by March 11th so that students have time to
> explore them. You can also join already published project ideas as a
> potential mentor.
>
> Stay tuned for more announcements about GSoC. If you want to know more
> about the project, consider joining our Gitter channel
>  and the jenkinsci-gsoc-all-public
>  mailing
> list.
>
> Best regards,
> Oleg Nenashev
> Jenkins GSoC org team
> https://jenkins.io/projects/gsoc/
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAbXu1J4XbF6zg56Qgq1g07%3DtLBH1h2g8ZDjUNQhL%2BLYA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
https://github.com/LinuxSuRen

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAMM7nTHQNbj38VdfPErRPsS3%3DwkgzuRJ9gJVq1g9RdwkAaexFA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[GSoC 2019] - Jenkins project has been accepted!

2019-02-28 Thread Oleg Nenashev 
Dear all,

On behalf of the Jenkins Google Summer of Code
 org team, I am happy to announce
that the Jenkins project *has been accepted* to GSoC this year. Congrats
and thanks to all mentors, org admins and students who has contributed to
it!

Just to provide some numbers, this is the biggest GSoC ever, 206
organizations participate in GSoC this year. And it will be hopefully the
biggest year for Jenkins as well. We have 25 project ideas
 and more than 30
potential mentors (and counting!). It is already more than in 2016 and 2018
all together. There are many plugins, SIGs and sub-projects which have
already joined GSoC this year. And we have already received messages and
first contributions from dozens of students, yey!

*What's next?* GSoC is officially announced, and please expect more more
students to contact projects in our Gitter channels and mailing lists
. This year there will be less
traffic in the Developer mailing lists until projects are announced,
because communications move to SIG and sub-project channels. Student
project proposal deadline is April 9th, and we will be working hard in
order to help students to find interesting projects, to explore the area,
and to prepare their project proposals. We will send more information to
mentors and students in separate emails.

*I am a student. How to join the project?* We invite you to follow the student
guidelines  and to reach out to
potential mentors using chats and mailing lists listed in project ideas. If
you do not see anything interesting, you can propose your own project idea
 or check out
ideas in other organizations
, you can even propose
your Jenkins-related ideas there.

*And what about mentors?* We are also looking for more project ideas and
for Jenkins contributors/users who are passionate about Jenkins and want to
mentor students. No hardcore experience required, mentors can study the
project internals together with students and technical advisors. We are
especially interested in ideas beyond the Java stack, and in ideas focusing
new technologies and areas (e.g. Kubernetes, IoT, Go, whatever). This
blogpost 
by Martin d'Anjou provides the guidelines. If you want to propose a new
project idea, please do so by March 11th so that students have time to
explore them. You can also join already published project ideas as a
potential mentor.

Stay tuned for more announcements about GSoC. If you want to know more
about the project, consider joining our Gitter channel
 and the jenkinsci-gsoc-all-public
 mailing
list.

Best regards,
Oleg Nenashev
Jenkins GSoC org team
https://jenkins.io/projects/gsoc/

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPfivLAbXu1J4XbF6zg56Qgq1g07%3DtLBH1h2g8ZDjUNQhL%2BLYA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: configuration of jobs maintained in SVN

2019-02-28 Thread DmitryB 
Try to look at https://docs.openstack.org/infra/jenkins-job-builder/
It allows to define jobs with yaml files, support job templating, allow to 
use builder scripts as separate files (e.g. for codestyle checking)

четверг, 28 февраля 2019 г., 22:33:08 UTC+4 пользователь Matthias Apitz 
написал:
>
>
> Hello, 
>
> I've setup a Jenkins server on SuSE Linux SLES12 and have the jobs in: 
>
> $ ls -l /var/lib/jenkins/jobs/ 
> total 12 
> drwxr-xr-x 3 jenkins jenkins 4096 Feb 23 00:00 Jerome_Head 
> drwxr-xr-x 3 jenkins jenkins 4096 Feb 28 01:00 
> Statistic-Installation-Job-V7.0 
> drwxr-xr-x 3 jenkins jenkins 4096 Feb 28 01:00 TPv70-nightly-build 
> ... 
> $ ls -l /var/lib/jenkins/jobs/TPv70-nightly-build/config.xml 
> -rw-r--r-- 1 jenkins jenkins 3162 Feb 27 11:40 
> /var/lib/jenkins/jobs/TPv70-nightly-build/config.xml 
>
> I'd like to edit the jobs with the normal editor in Linux, esp. the 
> sometimes complex build step script written in shell or perl, and have all 
> this, at least the config.xml file of each of my 50 jobs, under SVN 
> version control. 
>
> After modifying any jobs config.xml, the Jenkins server process must be 
> restarted to get the changes in effect (and visible in the browser 
> interface). Is there any other way to inform Jenkings about the change 
> and let it reload the modified job config? 
>
> Thanks 
>
> matthias 
>
>
> -- 
> Matthias Apitz, ✉ gu...@unixarea.de , http://www.unixarea.de/ 
> +49-176-38902045 
> Public GnuPG key: http://www.unixarea.de/key.pub 
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/c3957fd2-fece-4454-9f78-0d85eb53b260%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

sending email for unstable builds

2019-02-28 Thread Faad Sayaou 
Hi everyone
I am using the extended email plugin for notification when the build fails 
by using try catch. I will also like to send email when the build is 
unstable. Below is the structure of my pipeline 

node {
   
   try 
   {
 
stage('Checkout') {
cleanWs()
checkout scm

}


stage('Restore') {

sh "dotnet restore  $proj"

   }

stage('Build') {
sh "dotnet restore  $proj"

   }
stage ('Unit test') {

   sh "dotnet test  $test"
   } 
   }
} catch (err) {
 emailext body: 
' ${JOB_NAME} ${BUILD_NUMBER} is failing! Somebody should do 
something about that. https://jenkins-ma.com/job/Test/${BUILD_NUMBER}/console 
',
 subject: 'FAILURE', to: 'someEmail..'
}


I will like to send not only when the pipeline fails but when the build is 
unstable. thanks

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/2c7db49d-68ef-4c41-8cd2-39ff6855ad83%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Sending email for unstable build

2019-02-28 Thread Faad Sayaou 
Hi everyone
I am using the extended email plugin for notification when the build fails 
by using try catch. I will also like to send email when the build is 
unstable. Below is the structure of my pipeline 

node {
   
   try 
   {
 
stage('Checkout') {
cleanWs()
checkout scm

}


stage('Restore') {

sh "dotnet restore  $proj"

   }

stage('Build') {
sh "dotnet restore  $proj"

   }
stage ('Unit test') {

   sh "dotnet test  $test"
   } 
   }
} catch (err) {
 emailext body: 
' ${JOB_NAME} ${BUILD_NUMBER} is failing! Somebody should do 
something about that. 
https://jenkins-map.1worldsync.com/job/Test/${BUILD_NUMBER}/console 
',
 subject: 'FAILURE', to: 'someEmail..'
}


I will like to send not only when the pipeline fails but when the build is 
unstable. thanks 

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/18dd58b1-9352-4b31-ab90-5aecd326003a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: configuration of jobs maintained in SVN

2019-02-28 Thread Mark Waite 
Restart the Jenkins server is the safest and most reliable way to reload
modified job configurations.

There is a "Reload Configuration from Disc" in the "Manage Jenkins" page,
but it is not as safe or as reliable as restarting Jenkins (based on bug
reports to the Jenkins project).

Mark Waite

On Thu, Feb 28, 2019 at 10:48 AM Matthias Apitz  wrote:

>
> Hello,
>
> I've setup a Jenkins server on SuSE Linux SLES12 and have the jobs in:
>
> $ ls -l /var/lib/jenkins/jobs/
> total 12
> drwxr-xr-x 3 jenkins jenkins 4096 Feb 23 00:00 Jerome_Head
> drwxr-xr-x 3 jenkins jenkins 4096 Feb 28 01:00
> Statistic-Installation-Job-V7.0
> drwxr-xr-x 3 jenkins jenkins 4096 Feb 28 01:00 TPv70-nightly-build
> ...
> $ ls -l /var/lib/jenkins/jobs/TPv70-nightly-build/config.xml
> -rw-r--r-- 1 jenkins jenkins 3162 Feb 27 11:40
> /var/lib/jenkins/jobs/TPv70-nightly-build/config.xml
>
> I'd like to edit the jobs with the normal editor in Linux, esp. the
> sometimes complex build step script written in shell or perl, and have all
> this, at least the config.xml file of each of my 50 jobs, under SVN
> version control.
>
> After modifying any jobs config.xml, the Jenkins server process must be
> restarted to get the changes in effect (and visible in the browser
> interface). Is there any other way to inform Jenkings about the change
> and let it reload the modified job config?
>
> Thanks
>
> matthias
>
>
> --
> Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/
> +49-176-38902045
> Public GnuPG key: http://www.unixarea.de/key.pub
>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/20190228055907.GA2945%40c720-r342378
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtHKMCsV%2BsoMJW%3DAVADMbUYGnc1%3DHKNc8YybCAQtYPnFfQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: configuration of jobs maintained in SVN

2019-02-28 Thread Eric Pyle 
You could look at using the reload-job command in Jenkins CLI 
(documentation: https://jenkins.io/doc/book/managing/cli/). Or 
similarly, use the update-job command to read the updated job 
configuration from standard input and use it to update the job, which 
automatically includes refreshing the job.


On 2/28/2019 1:18 PM, Matthias Apitz wrote:

Hello,

I've setup a Jenkins server on SuSE Linux SLES12 and have the jobs in:

$ ls -l /var/lib/jenkins/jobs/
total 12
drwxr-xr-x 3 jenkins jenkins 4096 Feb 23 00:00 Jerome_Head
drwxr-xr-x 3 jenkins jenkins 4096 Feb 28 01:00 Statistic-Installation-Job-V7.0
drwxr-xr-x 3 jenkins jenkins 4096 Feb 28 01:00 TPv70-nightly-build
...
$ ls -l /var/lib/jenkins/jobs/TPv70-nightly-build/config.xml
-rw-r--r-- 1 jenkins jenkins 3162 Feb 27 11:40 
/var/lib/jenkins/jobs/TPv70-nightly-build/config.xml

I'd like to edit the jobs with the normal editor in Linux, esp. the
sometimes complex build step script written in shell or perl, and have all
this, at least the config.xml file of each of my 50 jobs, under SVN version 
control.

After modifying any jobs config.xml, the Jenkins server process must be
restarted to get the changes in effect (and visible in the browser
interface). Is there any other way to inform Jenkings about the change
and let it reload the modified job config?

Thanks

matthias




--
Eric Pyle
Siemens PLM Software
Lebanon, NH
+1 603-277-3060
eric.p...@siemens.com
http://www.siemens.com/plm

--
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/017e14d8-a208-d6e3-7de0-8213d98b1c27%40siemens.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline: How to modify Build History status monitor

2019-02-28 Thread Mike Craig 
Thank you!

On Thu, Feb 28, 2019 at 9:48 AM Simon Bayer  wrote:

> Hi Mike, u could use the object 'currentbuild' to modify the job
> description. Its available in declarative pipeline builds (e.g. with
> multiproject pipeline plugin). Furthermore the build status can be set. But
> beware: if u set the status to 'failure', Post build actions for failures
> will not be triggered. Use the default step 'error' instead.
>
> Script-Example:
> script {
> currentBuild.description = 'Jenkins is awesome'
> currentBuild.status = 'success'
> }
>
> Greets
>
>
>
>  Ursprüngliche Nachricht 
> Von: Mike Craig 
> Datum: 27.02.19 23:12 (GMT+01:00)
> An: Jenkins Users 
> Betreff: Pipeline: How to modify Build History status monitor
>
> Hello,
>
> Prior to using declarative pipeline, we were able to modify the Build
> History to indicate information we wanted to see.
> We are using a shared "terraform-deploy" pipeline now and would like to
> modify this build history to display which project (aka component) was
> built in that run.
>
> [image: build history.png]
>
> Thank you,
>
> Mike
>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/c7a6018e-3600-42f7-91c5-56caeae99bdc%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/GY9ouPE496U/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/BN8PR15MB3441DF5E5735C011915B8C2BAC750%40BN8PR15MB3441.namprd15.prod.outlook.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAEmhiT8N1a3mDG2ZQX8B%2BexpCCE41V_SpCb9C99aw9pK0QooBQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

configuration of jobs maintained in SVN

2019-02-28 Thread Matthias Apitz 


Hello,

I've setup a Jenkins server on SuSE Linux SLES12 and have the jobs in:

$ ls -l /var/lib/jenkins/jobs/
total 12
drwxr-xr-x 3 jenkins jenkins 4096 Feb 23 00:00 Jerome_Head
drwxr-xr-x 3 jenkins jenkins 4096 Feb 28 01:00 Statistic-Installation-Job-V7.0
drwxr-xr-x 3 jenkins jenkins 4096 Feb 28 01:00 TPv70-nightly-build
...
$ ls -l /var/lib/jenkins/jobs/TPv70-nightly-build/config.xml
-rw-r--r-- 1 jenkins jenkins 3162 Feb 27 11:40 
/var/lib/jenkins/jobs/TPv70-nightly-build/config.xml

I'd like to edit the jobs with the normal editor in Linux, esp. the
sometimes complex build step script written in shell or perl, and have all
this, at least the config.xml file of each of my 50 jobs, under SVN version 
control.

After modifying any jobs config.xml, the Jenkins server process must be
restarted to get the changes in effect (and visible in the browser
interface). Is there any other way to inform Jenkings about the change
and let it reload the modified job config?

Thanks

matthias


-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/20190228183259.GA2927%40c720-r342378.
For more options, visit https://groups.google.com/d/optout.

configuration of jobs maintained in SVN

2019-02-28 Thread Matthias Apitz 
Hello,

I've setup a Jenkins server on SuSE Linux SLES12 and have the jobs in:

$ ls -l /var/lib/jenkins/jobs/
total 12
drwxr-xr-x 3 jenkins jenkins 4096 Feb 23 00:00 Jerome_Head
drwxr-xr-x 3 jenkins jenkins 4096 Feb 28 01:00 Statistic-Installation-Job-V7.0
drwxr-xr-x 3 jenkins jenkins 4096 Feb 28 01:00 TPv70-nightly-build
...
$ ls -l /var/lib/jenkins/jobs/TPv70-nightly-build/config.xml
-rw-r--r-- 1 jenkins jenkins 3162 Feb 27 11:40 
/var/lib/jenkins/jobs/TPv70-nightly-build/config.xml

I'd like to edit the jobs with the normal editor in Linux, esp. the
sometimes complex build step script written in shell or perl, and have all
this, at least the config.xml file of each of my 50 jobs, under SVN version 
control.

After modifying any jobs config.xml, the Jenkins server process must be
restarted to get the changes in effect (and visible in the browser
interface). Is there any other way to inform Jenkings about the change
and let it reload the modified job config?

Thanks

matthias


-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/20190228181816.GA2643%40c720-r342378.
For more options, visit https://groups.google.com/d/optout.

Re: An error occurred during installation: No such plugin: cloudbees-folder

2019-02-28 Thread jinesh . 3c 
Had the same problem but solved.
Just remember the necessary plugins and uncheck all of them.
install and then you can get access to.
Later on, you can install those plugins.
Thanks

>
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f8321b44-c737-4a2c-a3ed-3ac2cf35433c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline: How to modify Build History status monitor

2019-02-28 Thread Simon Bayer 
Hi Mike, u could use the object 'currentbuild' to modify the job description. 
Its available in declarative pipeline builds (e.g. with multiproject pipeline 
plugin). Furthermore the build status can be set. But beware: if u set the 
status to 'failure', Post build actions for failures will not be triggered. Use 
the default step 'error' instead.

Script-Example:
script {
currentBuild.description = 'Jenkins is awesome'
currentBuild.status = 'success'
}

Greets



 Ursprüngliche Nachricht 
Von: Mike Craig 
Datum: 27.02.19 23:12 (GMT+01:00)
An: Jenkins Users 
Betreff: Pipeline: How to modify Build History status monitor

Hello,

Prior to using declarative pipeline, we were able to modify the Build History 
to indicate information we wanted to see.
We are using a shared "terraform-deploy" pipeline now and would like to modify 
this build history to display which project (aka component) was built in that 
run.


[build history.png]

Thank you,

Mike


--
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 
jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/c7a6018e-3600-42f7-91c5-56caeae99bdc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/BN8PR15MB3441DF5E5735C011915B8C2BAC750%40BN8PR15MB3441.namprd15.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.

configuration of jobs maintained in SVN

2019-02-28 Thread Matthias Apitz 


Hello,

I've setup a Jenkins server on SuSE Linux SLES12 and have the jobs in:

$ ls -l /var/lib/jenkins/jobs/
total 12
drwxr-xr-x 3 jenkins jenkins 4096 Feb 23 00:00 Jerome_Head
drwxr-xr-x 3 jenkins jenkins 4096 Feb 28 01:00 Statistic-Installation-Job-V7.0
drwxr-xr-x 3 jenkins jenkins 4096 Feb 28 01:00 TPv70-nightly-build
...
$ ls -l /var/lib/jenkins/jobs/TPv70-nightly-build/config.xml
-rw-r--r-- 1 jenkins jenkins 3162 Feb 27 11:40 
/var/lib/jenkins/jobs/TPv70-nightly-build/config.xml

I'd like to edit the jobs with the normal editor in Linux, esp. the
sometimes complex build step script written in shell or perl, and have all
this, at least the config.xml file of each of my 50 jobs, under SVN version 
control.

After modifying any jobs config.xml, the Jenkins server process must be
restarted to get the changes in effect (and visible in the browser
interface). Is there any other way to inform Jenkings about the change
and let it reload the modified job config?

Thanks

matthias


-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/20190228055907.GA2945%40c720-r342378.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline: How to modify Build History status monitor

2019-02-28 Thread Mike Craig 
Perfect, thank you for the reference! Having a "how-to" question, and
mapping that to a documentation section is the hardest part for me. :)

On Wed, Feb 27, 2019 at 10:55 PM Andreas Magnusson <
andreas.ch.magnus...@gmail.com> wrote:

> Not quite sure what you want to do, but we modify currentBuild.displayName
> and currentBuild.description from within our pipeline.
> They are documented under Pipeline Syntax | Global Variable Reference
>
> /Andreas
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/GY9ouPE496U/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/bbf0bdca-3bd6-4e4d-a163-7e282fa25336%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAEmhiT_oNe5EgZdEdKshof0hGVhQCEVY_toocGT%3D5AOrgsCY%2Bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.