MissingMethodException while using shared libraries

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:

Re: sending email for unstable builds

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/ > > >

Re: sending email for unstable builds

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

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

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

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

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

[GSoC 2019] - Jenkins project has been accepted!

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

Re: configuration of jobs maintained in SVN

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 написал: >

sending email for unstable builds

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()

Sending email for unstable build

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()

Re: configuration of jobs maintained in SVN

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

Re: configuration of jobs maintained in SVN

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

Re: Pipeline: How to modify Build History status monitor

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

configuration of jobs maintained in SVN

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

configuration of jobs maintained in SVN

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

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

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

Re: Pipeline: How to modify Build History status monitor

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

configuration of jobs maintained in SVN

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

Re: Pipeline: How to modify Build History status monitor

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