[JIRA] [ghprb-plugin] (JENKINS-29151) ghprb ignores Commit Status Context field value and uses default
Title: Message Title Mike Dubman created an issue Jenkins / JENKINS-29151 ghprb ignores Commit Status Context field value and uses default Issue Type: Bug Assignee: Honza Brzdil Attachments: jen.png Components: ghprb-plugin Created: 30/Jun/15 6:40 PM Environment: linux rhel6 Labels: ghprb github Priority: Minor Reporter: Mike Dubman Hi, After upgrading to latest jenkins (1.617) and ghprb plugin to the version 1.24.3 - the COmmit Status Context appears as default and not as configured (Mellanox). Example is here: https://github.com/open-mpi/ompi-release/pull/345
[JIRA] [tap-plugin] (JENKINS-29153) tap plugin fails job when not have to
Title: Message Title Mike Dubman created an issue Jenkins / JENKINS-29153 tap plugin fails job when not have to Issue Type: Bug Assignee: Bruno P. Kinoshita Attachments: tap.pdf Components: tap-plugin Created: 30/Jun/15 7:05 PM Environment: rhel6 Labels: tapResults Priority: Minor Reporter: Mike Dubman Hi, more details in the attached pdf. short version - tap plugins fails job while configured not to.
[JIRA] [ghprb-plugin] (JENKINS-27659) java.io.IOException: Cannot determine sha1 of the commit. The status cannot be reported
Mike Dubman created JENKINS-27659 java.io.IOException: Cannot determine sha1 of the commit. The status cannot be reported Issue Type: Bug Assignee: Honza Brázdil Components: ghprb-plugin Created: 28/Mar/15 5:46 PM Description: The PR in question is https://github.com/open-mpi/ompi-release/pull/218 The jenkins server is publicly accessible (link to jenkins job is inside PR). Other PRs from the same project working fine, only this one has this issue. Environment: jenkins server, monitors github PR for opensource projects. Project: Jenkins Labels: exception Priority: Major Reporter: Mike Dubman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Mike Dubman commented on JENKINS-21861 option to include attachment with console.txt from failed slaves it does not for matrix projects This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Mike Dubman commented on JENKINS-21861 option to include attachment with console.txt from failed slaves Hi ALex, yes - this is still an issue for "Matrix projects". works as advertised on "freestyle" projects. I tried to change "send log for all slaves" and for "master only" - it did not help. Currently, as a work-around we have some ugly script to fetch consoles and attach to the outgoing email. We could have screen sharing session if needed to demo the problem - but it is the same as in screenshot. Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Mike Dubman commented on JENKINS-21861 option to include attachment with console.txt from failed slaves Alex We can have a screen-sharing session to show you what is meant here. Please drop me a line if interested. Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-timeout] (JENKINS-24279) run custom shell script on Build timeout as pre-on-timeout hook
Mike Dubman updated JENKINS-24279 run custom shell script on Build timeout as pre-on-timeout hook Change By: Mike Dubman (15/Aug/14 5:53 AM) Description: Hi,Isthatpossibletoallowrunningshellscript /inline commandbeforetakingactionwhentimeoutoccures(actionlikefail/abort).Theuse-caseforthisrequestistoextractstacktraceswithgstackorgdbfromhangingjobbeforebuild-timeoutabortsit?Also,asadditionpre-ontimeoutaction,plugincansendemailtospecificaddressandwaitforsomesentinelfiletoberemovedbyuser.Thiswillallowdevelopertoconnecttothehangingjob,examine/debughang,removesentinelfileandjobwillresumeabort/failroutine.Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-timeout] (JENKINS-24279) run custom shell script on Build timeout as pre-on-timeout hook
Mike Dubman created JENKINS-24279 run custom shell script on Build timeout as pre-on-timeout hook Issue Type: Improvement Affects Versions: current Assignee: Kohsuke Kawaguchi Components: build-timeout Created: 15/Aug/14 5:52 AM Description: Hi, Is that possible to allow running shell script command before taking action when timeout occures (action like fail/abort). The use-case for this request is to extract stacktraces with "gstack" or "gdb" from hanging job before build-timeout aborts it? Also, as addition pre-ontimeout action, plugin can send email to specific address and wait for some sentinel file to be removed by user. This will allow developer to connect to the hanging job, examine/debug hang, remove sentinel file and job will resume abort/fail routine. Thanks Environment: linux Project: Jenkins Labels: build-tmeout Priority: Major Reporter: Mike Dubman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Mike Dubman commented on JENKINS-21861 option to include attachment with console.txt from failed slaves Actually, our projects of type: Build multi-configuration project This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Mike Dubman commented on JENKINS-21861 option to include attachment with console.txt from failed slaves hmmm.. interesting, we have tens projects (multi-configuration projects) and mail sent from master always look like this: hpc-ompi-shmem - Build # 2217 - Still Failing: Git: origin/master 368c6bb3261e77d1c12f473ed692ca21bf28c7d3 Check console output at http://hpc-master.lab.mtl.com:8080/job/hpc-ompi-shmem/2217/ to view the results. Build log: ... Started by an SCM change EnvInject - Loading node environment variables. Building on master in workspace /scrap/jenkins/workspace/hpc-ompi-shmem-2 Deleting project workspace... done Checkout:hpc-ompi-shmem-2 / /scrap/jenkins/workspace/hpc-ompi-shmem-2 - hudson.remoting.LocalChannel@7fd2c81d Using strategy: Default Last Built Revision: Revision 9fe0dd82ba28da9e918d0c8495c42d04dac628ac (origin/master, origin/HEAD) Cloning the remote Git repository Cloning repository http://bgate.mellanox.com:8080/git/ompi-vendor.git git --version git version 1.8.4.3 Fetching upstream changes from origin Seen branch in repository origin/HEAD Seen branch in repository origin/master Seen branch in repository origin/mellanox-master Seen branch in repository origin/mellanox-shmem-from-v1.6 Seen branch in repository origin/mellanox-test_branch Seen branch in repository origin/mellanox-v1.6 Seen branch in repository origin/mellanox-v1.7 Seen branch in repository origin/ompi-hcoll-datatype Seen branch in repository origin/test_branch Seen branch in repository origin/v1.6 Seen branch in repository origin/v1.7 Seen 11 remote branches Multiple candidate revisions Scheduling another build to catch up with hpc-ompi-shmem Commencing build of Revision 368c6bb3261e77d1c12f473ed692ca21bf28c7d3 (origin/master, origin/HEAD) Checking out Revision 368c6bb3261e77d1c12f473ed692ca21bf28c7d3 (origin/master, origin/HEAD) Warning : There are multiple branch changesets here No emails were triggered. Triggering r-vmb-rhel6-u3-x86-64 Triggering r-vmb-fedora14-x86-64 Triggering r-vmb-rhel5-u10-x86-64 Triggering r-vmb-rhel6-u2-x86-64 Triggering r-vmb-rhel6-u4-x86-64 Triggering hpc-test-node Triggering r-vmb-sles11-sp3-x86-64 Triggering r-vmb-rhel5-u9-x86-64 Triggering r-vmb-centos5-u7-x86-64 Triggering r-vmb-sles11-sp1-x86-64 Triggering r-vmb-fedora16-x86-64 Triggering r-vmb-fedora17-x86-64 Triggering r-vmb-rhel5-u8-x86-64 Triggering r-vmb-ubuntu13-u10-x86-64 Triggering r-vmb-rhel7-u0-beta-x86-64 Triggering r-vmb-rhel6-u5-x86-64 Triggering r-vmb-sles11-sp2-x86-64 Triggering r-vmb-ole6-u2-x86-64 Triggering r-vmb-centos6-u0-x86-64 Triggering r-vmb-rhel6-u1-x86-64 Triggering r-vmb-ubuntu12-u4-x86-64 Triggering r-vmb-sles11-sp0-x86-64 r-vmb-rhel6-u3-x86-64 completed with result SUCCESS r-vmb-fedora14-x86-64 completed with result SUCCESS r-vmb-rhel5-u10-x86-64 completed with result SUCCESS r-vmb-rhel6-u2-x86-64 completed with result SUCCESS r-vmb-rhel6-u4-x86-64 completed with result SUCCESS hpc-test-node completed with result FAILURE r-vmb-sles11-sp3-x86-64 completed with result SUCCESS r-vmb-rhel5-u9-x86-64 completed with result SUCCESS r-vmb-centos5-u7-x86-64 completed with result SUCCESS r-vmb-sles11-sp1-x86-64 completed with result SUCCESS r-vmb-fedora16-x86-64 completed with result SUCCESS r-vmb-fedora17-x86-64 completed with result SUCCESS r-vmb-rhel5-u8-x86-64 completed with result SUCCESS r-vmb-ubuntu13-u10-x86-64 completed with result SUCCESS r-vmb-rhel7-u0-beta-x86-64 completed with result SUCCESS r-vmb-rhel6-u5-x86-64 completed with result SUCCESS r-vmb-sles11-sp2-x86-64 completed with result SUCCESS r-vmb-ole6-u2-x86-64 completed with result SUCCESS r-vmb-centos6-u0-x86-64 completed with result SUCCESS r-vmb-rhel6-u1-x86-64 completed with result SUCCESS r-vmb-ubuntu12-u4-x86-64 completed with result SUCCESS r-vmb-sles11-sp0-x86-64 completed with result SUCCESS Email was triggered for: Failure Sending email for trigger: Failure This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send
[JIRA] [email-ext] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Mike Dubman updated JENKINS-21861 option to include attachment with console.txt from failed slaves Change By: Mike Dubman (24/Feb/14 5:40 AM) Attachment: matrixCap.PNG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Mike Dubman commented on JENKINS-21861 option to include attachment with console.txt from failed slaves tried all options - same result. matrix projects - this is a plugin to create jenkins job: we use: Build multi-configuration project wizard and it contains "matrix setup" to define run dimensions (per OS, per lib version, ...) - see attached This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Mike Dubman commented on JENKINS-21861 option to include attachment with console.txt from failed slaves Thank you for looking into this! On your system you probably run job on jenkins "master" machine, hence its console contains all job output. Jenkins can be configured to run jobs on "slaves" nodes only (master is not in use), so master serves for launching jobs only but real work is done by slaves and only slaves console contain job`s output. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Mike Dubman updated JENKINS-21861 option to include attachment with console.txt from failed slaves multi-slave jenkins config, no master used. Change By: Mike Dubman (23/Feb/14 6:24 AM) Attachment: multi-slave-config-Capture.JPG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21228) add shell variable into pre-send groovy script context
Mike Dubman commented on JENKINS-21228 add shell variable into pre-send groovy script context yes, thanks! will open two feature requests for other items. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21228) add shell variable into pre-send groovy script context
Mike Dubman resolved JENKINS-21228 as Fixed add shell variable into pre-send groovy script context managed script will do the trick Change By: Mike Dubman (18/Feb/14 8:46 PM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21228) add shell variable into pre-send groovy script context
Mike Dubman closed JENKINS-21228 as Fixed add shell variable into pre-send groovy script context +1 Change By: Mike Dubman (18/Feb/14 8:46 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Mike Dubman created JENKINS-21861 option to include attachment with console.txt from failed slaves Issue Type: Improvement Assignee: Alex Earl Components: email-ext Created: 18/Feb/14 8:51 PM Description: 1. It would be nice to have configuration checkbox in email-ext, to attach zip file with job console logs from failed slaves, like: failed_console.zip: slave1_console.txt slave2_console.txt slave3_console.txt Currently, the build.zip from master node is ~useless because all interesting info is at slaves and requires manual work to extract. 2. Also, the build.zip attached in the email-ext contains file named "log", can you change it to log.txt to let "double click" open it in notepad automatically? Project: Jenkins Priority: Major Reporter: Mike Dubman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21228) add shell variable into pre-send groovy script context
Mike Dubman
commented on JENKINS-21228
add shell variable into pre-send groovy script context
What do you mean it accepts "string script" only
I cannot specify the /path/to/external/script.groovy in the "pre-send textfield" as it expects groovy script to feed into evaluate()
So, current workaround is to create GroovyShell object and call its "evaluate(new File("/path/to/external/script.groovy"))
But, this work-around leads to a lot of code-copy (the external groovy script will not inherit msg,cancel, build objects which should be populated into new groovyshell object).
I would need more information as to why you can't just the attach build log feature to attach the log from the build slave.
I did not find a way to extract slave console log from file system and use wget. When email-ext is configured to run from parent, there is no easy way to fetch console logs from slave (AFAIK)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21228) add shell variable into pre-send groovy script context
Mike Dubman commented on JENKINS-21228 add shell variable into pre-send groovy script context Thanks you for quick reply. The problem with setting $DEFAULT_PRESEND_SCRIPT is that it accepts "string script" only. having a way to load script from file is more friendly for admin who can "vi" and change behave, w/o changing jenkins config. What type of security hole do you mean? The job config is a privilege operation and available for sys-adm type users. btw, the reason I wish to have it, is to be able fetch console log from failed slaves and attach it to the email. Currently, we do it as part of post-build action script on every slave, which "wget"`s console into file which is then picked by pre-send script from parent job. Do you see more elegant way to do it from pre-send script only? Thanks!!! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21228) add shell variable into pre-send groovy script context
Mike Dubman
created JENKINS-21228
add shell variable into pre-send groovy script context
Issue Type:
Improvement
Affects Versions:
current
Assignee:
Alex Earl
Components:
email-ext
Created:
05/Jan/14 7:44 AM
Description:
Please add "shell" variable into GroovyShell context used to run "pre-send" script (see the patch).
This will make possible to "source" external SAME groovy pre-send script from many projects, like this:
shell.evaluate("/usr/local/jenkins/pre-send.groovy")
diff --git a/src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java b/src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java
index 72a9354..e39150e 100755
a/src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java
+++ b/src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java
@@ -404,6 +404,7 @@ public class ExtendedEmailPublisher extends Notifier implements MatrixAggregatab
binding.setVariable("triggered", ImmutableMultimap.copyOf(context.getTriggered()));
GroovyShell shell = new GroovyShell(cl, binding, cc);
+binding.setVariable("shell", shell);
StringWriter out = new StringWriter();
PrintWriter pw = new PrintWriter(out);
Project:
Jenkins
Labels:
pre-send
Priority:
Trivial
Reporter:
Mike Dubman
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
