Hello Everybody,
we need to identify the currently logged-in user in an Extensible Choice
Parameter with Choice Provider System Groovy Choice Parameter. We tried the
following:
* User.current()
* Jenkins.getAuthentication()
* Build.getCause ... which works in a build step but
I got the following stacktrace as my build aborted. I manually invoked
the build again and it worked fine. Any ideas?
[INFO] All coverage checks have been met.
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
I can acc the Problem. Here is my stacktrace on jenkins 1.552
ERROR: Publisher hudson.plugins.deploy.DeployPublisher aborted due to
exceptionorg.codehaus.cargo.container.ContainerException
http://stacktrace.jenkins-ci.org/search?query=org.codehaus.cargo.container.ContainerException:
Failed
On 09/10/14 15:38, Alon Nisser wrote:
Is there a way to achieve that? getting the status of other jobs and
checking if last run was success?
I don't want to automatically run this deployment job on the upstream
success, but to trigger this manually. but still safeguard by checking
upstream
What version of email-ext do you have installed?
On Fri, Oct 24, 2014 at 11:31 AM, Sam T stalebb...@modeln.com wrote:
I have inherited a system that runs groovy to generate emails as a post
build action. The system has not been changed at all and the groovy
postbuild action and email has been
My apologies for not providing more detailed information. My jenkins is at
version 1.494 . This is the way the job is setup. This job is created using
multijob plugin where you can fire off other jobs and chain them together.
There are three postbuild actions configured for this job in this
I am getting conflicting results now. After removing the groovy postbuild
task, one of my jobs sends email but another job keeps failing with this
error message.
So, perhaps this is a base groovy error with the extended-email plugin
after all. Here is the error message.
Oct 24, 2014 8:53:22 PM
That error really isn't important, it shouldn't be marked SEVERE, it's not
actually an error. I don't think it relates to what you are seeing.
On Fri, Oct 24, 2014 at 9:40 PM, Sam T stalebb...@modeln.com wrote:
I am getting conflicting results now. After removing the groovy postbuild
task, one
