Hi Rajendra. Thank you so much for this news. Would really appreciate
help on implementing this. Could you please guide me through?
On Thursday, September 27, 2018 at 9:44:16 PM UTC-4, rajendraprasad reddy
wrote:
>
> Hi ,
> I did similar implementation for monitoring my Jenkins instance. But
Hi ,
I did similar implementation for monitoring my Jenkins instance. But I
never used a plugin to do that , instead of plugins I used groovy script to
prepare mail body content and sending this mail body to intended recipient
list.
Using groovy it is possible to get any information of Jenkins
I am on the way to office , after reaching to office I can provide you
sample groovy script and required configuration I can share with you.
With that info you can implement in time.
Thanks,
rajendra
On 28-Sep-2018 8:21 AM, wrote:
Hi Rajendra. Thank you so much for this news. Would really
Hi,
Thanks a lot for this information. Very useful.
I’ll give you feedback once I tested that.
Christophe.
> Le 26 sept. 2018 à 19:38, Ivan Fernandez Calvo a
> écrit :
>
> HI,
>
> Take a look to https://issues.jenkins-ci.org/browse/JENKINS-42856
>
Hi
Is there a plugin to scan the Jenkins console log and determine the type of
the failure (Infrastructure / Artifactory etc..)? and take action ..
instead of marking the build as failed /warning.
Regards,
Basanta
--
You received this message because you are subscribed to the Google Groups
https://plugins.jenkins.io/build-failure-analyzer ?
On Thu, Sep 27, 2018 at 12:10 PM wrote:
> Hi
>
> Is there a plugin to scan the Jenkins console log and determine the type
> of the failure (Infrastructure / Artifactory etc..)? and take action ..
> instead of marking the build as failed
Hi,
I am getting a git checkout issue "cannot checkout from starting point
error" when triggering the scripts through Jenkins pipeline. As a
workaround I created a new pipeline (copied from the error pipeline) and
then tried to checkout and it worked successfully.
But after 10-12 builds I am
Any help on this. Little urgent.
On Wednesday, September 26, 2018 at 3:29:23 PM UTC-4, gotvi...@gmail.com
wrote:
>
> I'm looking to generate a report, as a job, which will provide the global
> metrics of my Jenkins instance. I need details in the report like (1) How
> many jobs ran? (2) # of
(replies inline)
On Wed, 26 Sep 2018, gotviser...@gmail.com wrote:
> I'm looking to generate a report, as a job, which will provide the global
> metrics of my Jenkins instance. I need details in the report like (1) How
> many jobs ran? (2) # of failed and successful jobs and every possible
>
Thanks for the info Tyler.
On Thursday, September 27, 2018 at 10:46:20 AM UTC-4, R Tyler Croy wrote:
>
> (replies inline)
>
> On Wed, 26 Sep 2018, gotvi...@gmail.com wrote:
>
> > I'm looking to generate a report, as a job, which will provide the
> global
> > metrics of my Jenkins instance.
We have been exploring Hygiene it not only helps with Jenkins metrics and
also acts as a central dashboard for all your CI/CD tool set.
Take a look at here https://github.com/Hygieia/Hygieia.
HTH
On Wednesday, September 26, 2018 at 12:29:23 PM UTC-7, gotvi...@gmail.com
wrote:
>
> I'm looking
Thanks a lot Vishal. Will explore this.
On Thursday, September 27, 2018 at 1:12:48 PM UTC-4, Vishal Raina wrote:
>
> We have been exploring Hygiene it not only helps with Jenkins metrics and
> also acts as a central dashboard for all your CI/CD tool set.
> Take a look at here
I am having trouble defining agents for my build pipeline. I need to use 2
docker images as agents for entire pipe. first 4 steps uses one image and
last two steps uses another one. I don't want to repeat agent statement in
every stage.
It was easy with scripted pipe. I defined all my images
Trying to find the answer why it doesn't work for case when I use def
jobBuild = build job: 'myjob', propagate: false,
*wait:false*
On Wednesday, May 17, 2017 at 12:55:33 PM UTC+3, Bill Dennis wrote:
>
> Ah just saw you need the job to call all builds even if one fails. You can
> do it with a
SO far I tried following but with all I keep hitting ‘Jenkins’ doesn’t have
label ‘docker’
Try 1 : Trying to override top-level agent. I get ‘Jenkins’ doesn’t have
label ‘docker’ and build hangs there
pipeline {
agent {
docker {
image 'maven:3-alpine'
Top level docker agents can't be overridden - but you can use the
kubernetes plugin in Declarative (
https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/test/resources/org/csanchez/jenkins/plugins/kubernetes/pipeline/declarative.groovy
e.g.) which may be what you're looking for.
A.
On
It uses the default shell, yes - i.e., "sh -c ...", as you can see at
https://github.com/jenkinsci/durable-task-plugin/blob/c1ee6607c6939e8917762419c8474fecec06172c/src/main/java/org/jenkinsci/plugins/durabletask/BourneShellScript.java#L141-L165.
The actual content of the step, i.e., "ls -la" in
would that be useful without kubernetes cluster? And isn't this a common
requirements? Without it my pipe looks like following. It's littered with
same agent section in many stages. It works though.
#!/bin/groovy
def scmVars
pipeline {
agent { label 'master'}
stages {
18 matches
Mail list logo