Re: Break init scripts up in to re-usable classes

(replies inline) On Mon, 12 Mar 2018, Edd Grant wrote: > Hi folks, > > I'm using the init hook script mechanism ($JENKINS_HOME/init.groovy.d) to > programmatically configure Jenkins. I'm building up quite a library of code > and want to split it out in to re-usable classes, to keep things >

Re: withMaven dependency trigger - Need help to understand the error message

I believe I don't have the scenario that you described. Mine is more like Project A, B, and C depends on D, after D builds, A, B, and C are not built So I need to troubleshoot, to see what I missed from my setup -D On Monday, March 12, 2018 at 9:00:20 AM UTC-7, Cyrille Le Clerc wrote:

Re: Break init scripts up in to re-usable classes

Gah, spotted a typo. Just to avoid confusion [3] should say "rather than adding it to the *war*", not the jar. Cheers, Edd On Monday, 12 March 2018 21:57:42 UTC, Edd Grant wrote: > > Hi folks, > > I'm using the init hook script mechanism ($JENKINS_HOME/init.groovy.d) to > programmatically

Break init scripts up in to re-usable classes

Hi folks, I'm using the init hook script mechanism ($JENKINS_HOME/init.groovy.d) to programmatically configure Jenkins. I'm building up quite a library of code and want to split it out in to re-usable classes, to keep things maintainable and make it easier to write well focused tests etc. I

Re: AWS CodePipeline Jenkins Plugin Stacktrace Help

That looks like a bug in the AWS code pipeline plugin. You'll likely need to submit a bug report in Jira. Mark Waite On Mon, Mar 12, 2018 at 1:33 PM Ricky Sanders wrote: > Need some help from the community > > > *My specs are the following* > > AWS Linux US-EAST

AWS CodePipeline Jenkins Plugin Stacktrace Help

Need some help from the community *My specs are the following* AWS Linux US-EAST Recent Jenkins ver. 2.110 java-1.8.0-openjdk-devel AWS CodePipeline Plugin Version .34 *Issue* When attempting to complete the Integrating Jenkins with AWS CodePipeline tutorial on AWS

Re: Pipeline Build Step lightweight checkout?

Nevermind me, I'm a liar. When I added the aggregate build I also switched from a branch build to a PR-Merge build, which necessitates a full checkout to properly resolve the Jenkinsfile I suppose On Friday, March 9, 2018 at 5:27:37 PM UTC, Steven Foster wrote: > > Hi there, > > I'm using a

Re: jenkins command line use with google Login Oauth2....

Hi, Same problem here. I'm trying to install plugin via jenkins-cli (with ansible or from localhost) and can't authenticate because of Google Login Plugin. Any advance on this issue? Is there any way to bypass google authentication or using an own's database jenkins user? El martes, 24 de

Re: withMaven dependency trigger - Need help to understand the error message

> How can I troubleshoot this? I discussed this feature with Arnaud Héritier today for another use case. My understanding is that it is "work as design" and that you ask for an improvement to disable this JENKINS-46313 Avoid excessive triggering of downstream jobs

Directory does not exist while compilling just through Jenkins

Hello, I am trying to compile one repo with a jenkinsfile from a remote git, when a change is detected, but while it tries to compile I receive this error: :: error: (1180) directory "dist/default/production" does not exist And I really dont know why, since I am able to compile manually in

Re: Is the "checkout scm" step necessary in multi-branch pipelines?

I think it's a feature of declarative syntax rather than multibranch. In declarative, every time a node is allocated it comes with a checkout scm by default. On Monday, March 12, 2018 at 12:50:53 PM UTC, Behrang wrote: > > In my pipeline I don't have this step and everything is working fine,

Is the "checkout scm" step necessary in multi-branch pipelines?

In my pipeline I don't have this step and everything is working fine, but most articles I see on the web have this step in their Jenkinsfile, for example this one from the official Jenkins web site: https://jenkins.io/blog/2015/12/03/pipeline-as-code-with-multibranch-workflows-in-jenkins/ --

Re: Jenkins slave: tool download not using proxy

Changed my setup a bit. Using JNLP now instead of docker attach and configured the proxy settings as environment vars and as JVM opts, but still the tool download fails: [Pipeline] }[Pipeline] // stage [Pipeline] stage[Pipeline] { (SonarQube analysis)[Pipeline] script[Pipeline] {[Pipeline]

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

Hi, I have got Jenkins *version 2.108* *Steps:* 1. I downloaded Weekly support Jenkins-2.108 2. I installed the Jenkins via Jenkins.msi 3. When the initial http://localhost:8080/ opened it asked me to unlock Jenkins so I did that. 4. Then it asked me to Install Suggested Plugins

Hwo to configure Jenkins API TO fisheye

Hi Exports, Can you please explain how configure Jenkins API TO fisheye with exm. -- *Best Regards ,* *Venkata Reddy* -- 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,