[JIRA] (JENKINS-41662) Proceed button fails (investigate)

2020-01-21 Thread jya...@howlingduck.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Yanko edited a comment on  JENKINS-41662  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Proceed button fails (investigate)   
 

  
 
 
 
 

 
 Just saw this issue for the first time today on an instance maintained by my team. * Jenkins -   [CloudBees Jenkins Distribution 2.204.1.3-rolling|https://release-notes.cloudbees.com/product/CloudBees+Jenkins+Distribution] * Blue Ocean  - v1.21.0Saw the same issue where first we got the message like{code:java}error processing input submit request... {code}Followed by subsequent attempts to submit the same input prompt giving us{code:java}JSON.parse: unexpected end of data at line 1 column 1 of the JSON data {code}The build does move on an actually do the rest of it's task and end up reporting successful This warning appears to only show itself to the submitting user if they are using the BlueOcean UI rather than the Classic Jenkins views.In our testing today, when we instead use one of the classic view UI for input... * direct input link:  {{  https:///job//job//job///input }}  * hovering over the pending  stag  stage   in classic pipeline view * clicking input link from within console log...then the submission works fine without any visible errors/warnings and the job runs through to completion.     
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit

[JIRA] (JENKINS-41662) Proceed button fails (investigate)

2020-01-21 Thread jya...@howlingduck.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Yanko commented on  JENKINS-41662  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Proceed button fails (investigate)   
 

  
 
 
 
 

 
 Just saw this issue for the first time today on an instance maintained by my team. 
 
Jenkins -   CloudBees Jenkins Distribution 2.204.1.3-rolling 
Blue Ocean  - v1.21.0 
 Saw the same issue where first we got the message like 

 

error processing input submit request...  

 Followed by subsequent attempts to submit the same input prompt giving us 

 

JSON.parse: unexpected end of data at line 1 column 1 of the JSON data  

 The build does move on an actually do the rest of it's task and end up reporting successful  This warning appears to only show itself to the submitting user if they are using the BlueOcean UI rather than the Classic Jenkins views. In our testing today, when we instead use one of the classic view UI for input... 
 
direct input link: https:///job//job//job///input 
hovering over the pending stag  in classic pipeline view 
clicking input link from within console log 
 ...then the submission works fine without any visible errors/warnings and the job runs through to completion.        
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[JIRA] (JENKINS-46441) After moving the job to a folder, the editor link is not available anymore

2019-07-17 Thread jya...@howlingduck.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Yanko commented on  JENKINS-46441  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: After moving the job to a folder, the editor link is not available anymore   
 

  
 
 
 
 

 
  I have run into this same issue today. Observations... 
 
When job catbox is at the root of jobs, the edit option is available. 
If I move the job within a folder, to SRE/catbox , then the edit option disappears 
If I move the catbox job back to the root list of jobs, the edit option re-appears 
 My Env... 
 
A multibranch pipeline, catbox, ** pointing to a git repo at github auth via ssh key 
CloudBees Jenkins 2.176.1.4 
BlueOcean 1.10.2 
 Screenshots...      
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184711.1503631317000.14799.1563396120160%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-46441) After moving the job to a folder, the editor link is not available anymore

2019-07-17 Thread jya...@howlingduck.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Yanko updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46441  
 
 
  After moving the job to a folder, the editor link is not available anymore   
 

  
 
 
 
 

 
Change By: 
 Jim Yanko  
 
 
Attachment: 
 image-2019-07-17-13-38-43-045.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184711.1503631317000.14797.1563395940559%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-46441) After moving the job to a folder, the editor link is not available anymore

2019-07-17 Thread jya...@howlingduck.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Yanko updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46441  
 
 
  After moving the job to a folder, the editor link is not available anymore   
 

  
 
 
 
 

 
Change By: 
 Jim Yanko  
 
 
Attachment: 
 image-2019-07-17-13-37-33-475.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184711.1503631317000.14791.1563395880703%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-50328) Pipeline editor not working if Script Path is set

2019-06-05 Thread jya...@howlingduck.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Yanko commented on  JENKINS-50328  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline editor not working if Script Path is set   
 

  
 
 
 
 

 
 Just discovered this problem today while working on team adoption of Jenkins / BlueOcean. In our case, dev started out with placing the Jenkinsfile at the repo path /build/Jenkinsfile rather than at /Jenkinsfile and defining the path to the jenkinsfile in the job here http:///jenkins/job//configure As others have mentioned, builds do run, but the BlueOcean editor does not show any stages or steps when a user looks there.  This in turn creates confusion since they see the steps in the build results screen, but not in the editor screen where they expect to see them. At this point, I'm concerned of the psychology at play when working with teams to get started using this.  One of the selling points on BlueOcean to management is that it makes it easy to use and build the job steps, and the code gets commited to your repo easily.   So changes can be made in a UI or by hand. In practice, when one project keeps the Jenkinsfile at root and another stores it elsewhere, this confuses the newer user who may be looking at a job configured by someone else for inspiration on how to add steps to a project/pipeline they are working on themselves when they see stages and steps in one project that but another appears to have no steps when they look at it in the UI.            
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189375.152167439.22104.1559759280251%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [brakeman] (JENKINS-22420) Post-Build Action not available (freestyle or multi-config)

2014-03-30 Thread jya...@howlingduck.com (JIRA) 














































Jim Yanko
 created  JENKINS-22420


Post-Build Action not available (freestyle or multi-config)















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


brakeman



Created:


30/Mar/14 5:03 PM



Description:


Brakeman Plugin v0.7 is noted as installed currently, yet the Post-Build Action for Brakeman does not appear in the select menu of jobs for either job type supported by my jenkins instance.


	project_freestyle_SAMPLE
	project_multiconfig_SAMPLE



Currently I am seeing this in Jenkins v1.554










Project:


Jenkins



Priority:


Major



Reporter:


Jim Yanko

























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] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted

2013-02-05 Thread jya...@howlingduck.com (JIRA) 














































Jim Yanko
 commented on  JENKINS-16163


NullPointerException when sending post build emails - all triggers appear to be impacted















Apologies for being absent recently on this for a while...

#1 'Jenkins Mailer Plugin' is disabled 

I'll see about updating to newer Jenkins today to see if the problem is still reproducible.




























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] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted

2013-02-05 Thread jya...@howlingduck.com (JIRA) 














































Jim Yanko
 commented on  JENKINS-16163


NullPointerException when sending post build emails - all triggers appear to be impacted















#1 updating Jenkins instance to v1.500 (latest)
#2 clicked button to 'manage old data' and below is basically what I see, many lines from many jobs which all seem to reference the same thing

	
	
		CannotResolveClassException: hudson.tasks.MailMessageIdAction : hudson.tasks.MailMessageIdAction
	
	




hudson.model.FreeStyleBuild	xxxJOBNAMExxx #2	CannotResolveClassException: hudson.tasks.MailMessageIdAction : hudson.tasks.MailMessageIdAction
hudson.model.FreeStyleBuild	JOBNAMExxx #7326	CannotResolveClassException: hudson.tasks.MailMessageIdAction : hudson.tasks.MailMessageIdAction
hudson.model.FreeStyleBuild	JOBNAMExxx #16004	CannotResolveClassException: hudson.tasks.MailMessageIdAction : hudson.tasks.MailMessageIdAction




























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] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted

2013-02-05 Thread jya...@howlingduck.com (JIRA) 












































 
Jim Yanko
 edited a comment on  JENKINS-16163


NullPointerException when sending post build emails - all triggers appear to be impacted

















	updated Jenkins instance to v1.500 (latest)
	clicked button to 'manage old data' and below is basically what I see, many lines from many jobs which all seem to reference the same thing  CannotResolveClassException: hudson.tasks.MailMessageIdAction : hudson.tasks.MailMessageIdAction



Here's what it looks like with job names masked

hudson.model.FreeStyleBuild	xxxJOBNAMExxx #2	CannotResolveClassException: hudson.tasks.MailMessageIdAction : hudson.tasks.MailMessageIdAction
hudson.model.FreeStyleBuild	JOBNAMExxx #7326	CannotResolveClassException: hudson.tasks.MailMessageIdAction : hudson.tasks.MailMessageIdAction
hudson.model.FreeStyleBuild	JOBNAMExxx #16004	CannotResolveClassException: hudson.tasks.MailMessageIdAction : hudson.tasks.MailMessageIdAction




























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] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted

2013-02-05 Thread jya...@howlingduck.com (JIRA) 














































Jim Yanko
 commented on  JENKINS-16163


NullPointerException when sending post build emails - all triggers appear to be impacted















Ah...

ok, will enable the Mailer plugin and see what happens...



























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] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted

2013-02-05 Thread jya...@howlingduck.com (JIRA) 














































Jim Yanko
 commented on  JENKINS-16163


NullPointerException when sending post build emails - all triggers appear to be impacted















Thanks Alex!

I've got my instance working with v1.500 now.   Mail is sending as it should be it seems.

Wish I'd realized that enabling the Mailer would fix this sooner...

...removed from core in 1.494. Since you are running a version after that you need to have it enabled. Email-ext, as with many plugins, is built against version 1.480.2 which is the most recent lts release. This "workaround" will be required until something = 1.494 is promoted to lts
...my issues started when I attempted to update to anything newer than 1.493 

If anything else, for those who are troubleshooting similar issue in the near future, they'll need to know of the workaround you mentioned.




























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] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted

2013-01-14 Thread jya...@howlingduck.com (JIRA) 














































Jim Yanko
 commented on  JENKINS-16163


NullPointerException when sending post build emails - all triggers appear to be impacted















Went to: Manage Jenkins/Configure System/Extended E-mail Notification

I set the override settings for Extended Email Notify as follows...


[x] Override Global Settings	
SMTP server		[ localhost]
Default user E-mail suffix	[ hostname.env.domain.com  ]	
System Admin E-mail Address [ us...@hostname.env.domain.com ]


Notably, I set the override to use a diff acct name for the email address from the default by adding the '2' so I could confirm the override setting was being used to send the email.

With Jenkins 1.493 (and email ext v 2.25)

	Ran a few builds of the sample job to force failure and success.
	Got emails from user2 address for each (indicates the override setting worked)



Upgraded Jenkins to 1.498 (and email ext v 2.25)

	Ran a few builds of the sample job to force failure and success.
	each that should have sent email failed to send message for the status change
	
		ERROR: Could not send email as a part of the post-build publishers.
	
	



Rolling back Jenkins to 1.493 (and email ext v 2.25)

	Ran a few builds of the sample job to force failure and success.
	Got emails from user2 address for each (indicates the override setting worked)



Following is from the console log from the forced failure condition with Jenkins 1.498 installed...


...
Starting the test @ Mon Jan 14 20:33:47 UTC 2013 (1358195627471)
Waiting for possible shutdown message on port 4445
Tidying up ...@ Mon Jan 14 20:33:51 UTC 2013 (1358195631145)
... end of run
Performance: Percentage of errors greater or equal than 5% sets the build as unstable
Performance: Percentage of errors greater or equal than 10% sets the build as failure
Performance: Recording JMeter reports '*.jtl'
Performance: Parsing JMeter report file results.jtl
Performance: File results.jtl reported 60.0% of errors [FAILURE]. Build status is: FAILURE
Build step 'Publish Performance test result report' changed build result to FAILURE
Recording fingerprints
IRC notifier plugin: Sending notification to: #alerts
Checking for post-build
Performing post-build step
Checking if email needs to be generated
Email was triggered for: First Failure
Trigger Success was overridden by another trigger and will not send an email.
Sending email for trigger: First Failure
Overriding default server settings, creating our own session
ERROR: Could not send email as a part of the post-build publishers.
java.lang.NullPointerException
	at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:439)
	at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:297)
	at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:289)
	at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:249)
	at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:785)
	at hudson.model.Build$BuildExecution.cleanUp(Build.java:192)
	at hudson.model.Run.execute(Run.java:1587)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:236)
Some error occured trying to send the email...check the Jenkins log
Finished: FAILURE


Just realized that I am seeing the following message each time I get back to version 1.493 when I go to the Manage Jenkins page.   Is this significant to the issue at hand? 


Manage Jenkins

You have data stored in an older format and/or unreadable data.   
New version of Jenkins (1.498) is available for download (changelog). Or Upgrade Automatically


If I follow the manage link, it basically only gives me an option to 'discard unreadable data' and nothing else.



























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

[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted

2013-01-14 Thread jya...@howlingduck.com (JIRA) 














































Jim Yanko
 commented on  JENKINS-16163


NullPointerException when sending post build emails - all triggers appear to be impacted















Allrighty - I'll keep my eyes open for it :-D



























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

[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted

2013-01-11 Thread jya...@howlingduck.com (JIRA) 














































Jim Yanko
 commented on  JENKINS-16163


NullPointerException when sending post build emails - all triggers appear to be impacted















@Slide-O-Mix

I found some time today to look at this again...

Found and enabled debug in the global config for Jenkins.

I used a sample job that I could easily force to success or failure condition by resetting a timeout value.   
This particular job was set to send an email on FIRST FAILURE and FIXED conditions.


	Installed Email-ext plugin 2.25
	Installed Jenkins 1.498
	Forced a Failure with the sample job
	Forced a Success with the sample job
	NOTE: the "Jenkins Mailer Plugin" is installed by not enabled currently



Below is the console output from when the sample job came into FIXED status...



Starting the test @ Fri Jan 11 23:44:08 UTC 2013 (1357947848086)
Waiting for possible shutdown message on port 4445
Tidying up ...@ Fri Jan 11 23:44:21 UTC 2013 (1357947861454)
... end of run
Performance: Percentage of errors greater or equal than 5% sets the build as unstable
Performance: Percentage of errors greater or equal than 10% sets the build as failure
Performance: Recording JMeter reports '*.jtl'
Performance: Parsing JMeter report file results.jtl
Performance: File results.jtl reported 0.0% of errors [SUCCESS]. Build status is: SUCCESS
Recording fingerprints
IRC notifier plugin: Sending notification to: #alerts
Checking for post-build
Performing post-build step
Checking if email needs to be generated
Email was triggered for: Fixed
Trigger Success was overridden by another trigger and will not send an email.
Sending email for trigger: Fixed
NOT overriding default server settings, using Mailer to create session
ERROR: Could not send email as a part of the post-build publishers.
java.lang.NullPointerException
	at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:431)
	at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:297)
	at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:289)
	at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:249)
	at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:785)
	at hudson.model.Build$BuildExecution.cleanUp(Build.java:192)
	at hudson.model.Run.execute(Run.java:1587)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:236)
Some error occured trying to send the email...check the Jenkins log
Finished: SUCCESS




























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

[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted

2013-01-11 Thread jya...@howlingduck.com (JIRA) 












































 
Jim Yanko
 edited a comment on  JENKINS-16163


NullPointerException when sending post build emails - all triggers appear to be impacted
















screenshot of my Ext Email Notification config (jenkins global config page)
 see attached  jenkins_config_email_ext.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

[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted

2013-01-11 Thread jya...@howlingduck.com (JIRA) 














































Jim Yanko
 updated  JENKINS-16163


NullPointerException when sending post build emails - all triggers appear to be impacted
















screenshot of my Ext Email Notification config (jenkins global config page)





Change By:


Jim Yanko
(11/Jan/13 11:54 PM)




Attachment:


jenkins_config_email_ext.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

[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted

2013-01-11 Thread jya...@howlingduck.com (JIRA) 












































 
Jim Yanko
 edited a comment on  JENKINS-16163


NullPointerException when sending post build emails - all triggers appear to be impacted
















@Slide-O-Mix

I found some time today to look at this again...

Found and enabled debug in the global config for Jenkins.

I used a sample job that I could easily force to success or failure condition by resetting a timeout value.   
This particular job was set to send an email on FIRST FAILURE and FIXED conditions.


	Installed Email-ext plugin 2.25
	Installed Jenkins 1.498
	Forced a Failure with the sample job
	Forced a Success with the sample job
	NOTE: the "Jenkins Mailer Plugin" is installed but not enabled currently



Below is the console output from when the sample job came into FIXED status...



Starting the test @ Fri Jan 11 23:44:08 UTC 2013 (1357947848086)
Waiting for possible shutdown message on port 4445
Tidying up ...@ Fri Jan 11 23:44:21 UTC 2013 (1357947861454)
... end of run
Performance: Percentage of errors greater or equal than 5% sets the build as unstable
Performance: Percentage of errors greater or equal than 10% sets the build as failure
Performance: Recording JMeter reports '*.jtl'
Performance: Parsing JMeter report file results.jtl
Performance: File results.jtl reported 0.0% of errors [SUCCESS]. Build status is: SUCCESS
Recording fingerprints
IRC notifier plugin: Sending notification to: #alerts
Checking for post-build
Performing post-build step
Checking if email needs to be generated
Email was triggered for: Fixed
Trigger Success was overridden by another trigger and will not send an email.
Sending email for trigger: Fixed
NOT overriding default server settings, using Mailer to create session
ERROR: Could not send email as a part of the post-build publishers.
java.lang.NullPointerException
	at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:431)
	at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:297)
	at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:289)
	at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:249)
	at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:785)
	at hudson.model.Build$BuildExecution.cleanUp(Build.java:192)
	at hudson.model.Run.execute(Run.java:1587)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:236)
Some error occured trying to send the email...check the Jenkins log
Finished: SUCCESS




























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

[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted

2013-01-11 Thread jya...@howlingduck.com (JIRA) 














































Jim Yanko
 commented on  JENKINS-16163


NullPointerException when sending post build emails - all triggers appear to be impacted















As noted above, mail still didn't send when I upped to Jenkins 1.498.  However, when I downgraded Jenkins, and kept the updated Email-ext plugin, mail does send.


	Installed Email-ext plugin 2.25
	Installed Jenkins 1.498
	Force Failure with sample job - mail does not send
	Force Success with sample job - mail does not send
	Attached screenshot and config info to JENKINS-16163
	Rolling back to Jenkins 1.493 (did not downgrade Email-ext plugin)
	Force Failure with sample job - mail sends
	Force Success with sample job - mail sends




Sample from console log of FIXED status change with Jenkins 1.493  Email-ext plugin 2.25 

Checking for post-build
	Performing post-build step
	Checking if email needs to be generated
	Email was triggered for: Fixed
	Trigger Success was overridden by another trigger and will not send an email.
	Sending email for trigger: Fixed
	NOT overriding default server settings, using Mailer to create session
	messageContentType = text/plain; charset=UTF-8
	Adding recipients from recipient list
	Setting In-Reply-To since last build was not successful
	Successfully created MimeMessage
	Sending email to: xx...@xxx.com
	Finished: SUCCESS




























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

[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted

2013-01-11 Thread jya...@howlingduck.com (JIRA) 














































Jim Yanko
 updated  JENKINS-16163


NullPointerException when sending post build emails - all triggers appear to be impacted
















attaching screenshot of the config with v 2.25 of the email ext plugin installed

 jenkins_config_email_ext_2.25 





Change By:


Jim Yanko
(12/Jan/13 12:12 AM)




Attachment:


jenkins_config_email_ext_2.25.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

[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted

2013-01-04 Thread jya...@howlingduck.com (JIRA) 














































Jim Yanko
 commented on  JENKINS-16163


NullPointerException when sending post build emails - all triggers appear to be impacted















Tried updating my installation to 1.496 today - seems that I still get the same issue with this version.


	installed new version today -
Jenkins ver. 1.496 = mail not sending




	rolled back -
Jenkins ver. 1.493 = mail sends as expected




Not sure if you need more log info from my particular installation at this point or not.   

Where do I enable debug mode and grab the build log after doing so?  Didn't see anything in the main jenkins config page for this.



























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

[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted

2012-12-18 Thread jya...@howlingduck.com (JIRA) 














































Jim Yanko
 created  JENKINS-16163


NullPointerException when sending post build emails - all triggers appear to be impacted















Issue Type:


Bug



Affects Versions:


current



Assignee:


Slide-O-Mix



Components:


email-ext



Created:


18/Dec/12 9:20 PM



Description:


NullPointerException when sending post build emails - all triggers appear to be impacted

Seems there may be a conflict between

	Jenkins ver. 1.494
	Jenkins Email Extension Plugin ver. 2.25  2.24.1



I upgraded my jenkins instance yesterday from 1.493 to 1.494 and then noticed that builds no longer sent email alerts as expected when status changed.

Am using the Email Extension Plugin to trigger email alerts mainly when build meets the following conditions:

	first time failure
	fixed



To get things working again, I needed to rollback my jenkins instance to v 1.493 as it appeared that with both ver. 2.25  2.24.1 of the mail plugin, mail did not send properly.   As soon as I rolled back the jenkins version, mail started working properly again.


	20121217	updated jenkins to v1.494 (and plugins)
	20121218	noticed all email notifications are failing with null pointer error (irc alerts still work)
	20121218 downgraded mail plugin to 2.24.1 (from 2.25.0) - still failing to send emails (all statuses)
	20121218 downgraded jenkins to 1.493 (from 1.494) - mail now sends successfully



Info from build log for a build was triggered as 'fixed' (same type of error seen for build that was triggered as 'first failure')


IRC notifier plugin: Sending notification to: #alerts
Email was triggered for: Fixed
Trigger Success was overridden by another trigger and will not send an email.
Sending email for trigger: Fixed
ERROR: Could not send email as a part of the post-build publishers.
java.lang.NullPointerException
	at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:431)
	at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:297)
	at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:289)
	at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:249)
	at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:779)
	at hudson.model.Build$BuildExecution.cleanUp(Build.java:192)
	at hudson.model.Run.execute(Run.java:1587)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:236)
Finished: SUCCESS





Project:


Jenkins



Priority:


Major



Reporter:


Jim Yanko

























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