date:20130526

Re: Single-User Permission Issues in LTS

2013-05-26 Thread Johannes Wienke

Hi,

I found some potential debugging help in the logs. Maybe this helps:

May 24, 2013 5:28:24 AM winstone.Logger logInternal
INFO: While serving
http://ourserver/view/macos/job/that-job/configSubmit:
hudson.security.AccessDeniedException2: userxxx is missing the Build
permission
May 24, 2013 5:28:26 AM winstone.Logger logInternal
SEVERE: Error while serving
http://ourserver/view/macos/job/that-job/configSubmit
java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor2202.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151)
at
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583)
at org.kohsuke.stapler.Stapler.service(Stapler.java:214)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
at
winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
at
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at
hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at
winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at
winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at
hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
at
winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at
org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50)
at
winstone.Filt

Re: jenkins e-mail ext DEFAULT_CONTENT does not expand

2013-05-26 Thread Vladimir Zak

I had there this
${BUILD_LOG,maxlines=500} which did not work now but before the update it
works more than a year.

No I have there
${BUILD_LOG,maxLines=500} and it works correctly.

zakyn


2013/5/26 Slide 

> You need a space before format, also why are you setting the format to
> empty string.
>  On May 26, 2013 4:07 AM, "Vladimir Zak"  wrote:
>
>> Hi,
>> I have the same problem. The strings are not replaced by URl for example
>> - $BUILD_URL is not replaced.
>>
>> In subjects it is replaced but NOT replaced in the other places.
>>
>> zakyn
>>
>> $PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS!$PROJECT_URL
>> $BUILD_URL 
>> Tests
>>
>> $FAILED_TESTS
>>
>> Changes  [%a] %m %p${CHANGES,format=" "}
>>
>>
>>
>>
>>
>> 2013/4/24 windycity 
>>
>>>
>>> Attach log.
>>>
>>>
>>> Jessica
>>>
>>> On Wednesday, April 24, 2013 4:04:04 PM UTC-5, windycity wrote:

 We are using tomcat, I have logs at 
 tomcat/apache-tomcat-6.0.35/**logs/catalina.out,
 is that the right one? But this one does not have any Jenkins error. Build
 #23 is the trouble one.

 Jessica

 On Wednesday, April 24, 2013 3:36:18 PM UTC-5, slide wrote:
>
> No, I mean the actual stderr type logs for the Jenkins app itself, it
> would be in different places depending on how you are running Jenkins.
> Could be in the tomcat logs, etc.
>
>
> On Wed, Apr 24, 2013 at 1:33 PM, windycity  wrote:
>
>> By jenkins log, do you mean $JENKINS_HOME/jobs/project/**builds/#/log
>> file?  If this is the file you refer, it does have build errors, but
>> sending mail seems fine.
>>
>> Sending e-mails to: j...@cboe.com
>> channel stopped
>> Sending e-mails to: j...@cboe.com
>> Email was triggered for: Failure
>> Sending email for trigger: Failure
>> Sending email to: j...@cboe.com
>> Finished: FAILURE
>>
>> If this is not the log you refer, would you please let me know where
>> should be the log file?
>>
>> Thanks much,
>>
>> Jessica
>>
>>
>>
>> On Wednesday, April 24, 2013 3:13:54 PM UTC-5, slide wrote:
>>
>>> Do you have any errors in jenkins logs?
>>>
>>>
>>> On Wed, Apr 24, 2013 at 12:43 PM, windycity wrote:
>>>
 I am looking at this file, actually, I figure

 ${JELLY_SCRIPT,template="html"}

 is the problem, if I get rid of this, everything seems working,
 though I do not understand why. Somebody else put this in global
 configuration, maybe this format is wrong, maybe it should be
 ${JELLY_SCRIPT, html}?


  Following is the content of ExtendedEmailPublisher xml file from
 the root of JENKINS_HOME

 Thanks much!

 Jessica

 
 >>> plugin="email-ext@2.28">
   
 http://openjdk2a:**80**81/jenkins/
 
   address not configured yet
 
   false
   text/html
   ${MAVEN_**PREBUI**LD_VERSION} $PROJECT_NAME -
 Build # $BUILD_NUMBER - $BUILD_STATUS!
   $PROJECT_NAME ${MAVEN_PREBUILD_VERSION}  - Build #
 $BUILD_NUMBER - $BUILD_STATUS:
 
 Check console output at $BUILD_URL to view the results.
 
 ${JELLY_SCRIPT,template="html"}
   -1
   j...@cboe.com

   
   false
   false
   false
   false
 



 On Wednesday, April 24, 2013 2:33:08 PM UTC-5, slide wrote:

> My apologies, I need the ExtendedEmailPublisher xml file from the
> root of JENKINS_HOME.
>
>
> On Wed, Apr 24, 2013 at 10:03 AM, windycity wrote:
>
>>
>> Here attached are the global and project config files, please let
>> me know what is wrong.
>>
>> Thanks much for all your help!
>>
>> Jessica
>>
>>
>> On Wednesday, April 24, 2013 8:59:51 AM UTC-5, slide wrote:
>>
>>> pre-build/post build added token
>>> MIME-Version: 1.0
>>> Content-Type: multipart/alternative;
>>> boundary="=_Part_**8**9_9798859.1366811681215"
>>>
>>> --=_Part_89_9798859.**136681**1681215
>>> Content-Type: text/plain; charset="utf-8"
>>> Content-Transfer-Encoding: 7bit
>>>
>>> They are expanded the same way, so I need more information (like
>>> your
>>> global and project config XML) to try and determine the issue.
>>>
>>> Sent from my Windows Phone
>>> From: windycity
>>> Sent: 4/24/2013 6:54
>>> To: jenkins...@googlegroups.**com
>>> S

config.xml missing after install

2013-05-26 Thread Tom Brus

Hi,

I install jenkins on ubuntu (in a script) and I would like to tweak the 
config.xml file (to add security stuff).
The problem is that right after install the config.xml file is missing. 
Jenkins is running properly though.
If I browse to my new jenkins and do something (e.g. set security) the 
config.xml file is generated.
But I do not want any manual interaction at this stage.

Is there a way to force jenkins to write that file so I can tweak it?

Thanks,
Tom

-- 
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, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Single-User Permission Issues in LTS

2013-05-26 Thread Johannes Wienke

Hi,

we are facing a permission issue with the current LTS version of
jenkins. Our setup uses a single LDAP server for authentication. In one
of our matrix jobs I have enabled specific permissions for a single LDAP
user so that this user can administer the whole job. In the
configuration page this user is correctly recognized from LDAP (the
person icon is shown) and has got all permissions for that job. While
this user can actually open the preferences page for this job, saving
modifications to the configuration results in the error message:

"userxxx is missing the Build permissions"

Any idea what could cause this? Or are there known issues?

I browsed through the config.xml for that job and the build permission
is definitely set for the user.

Thanks for any support,
Johannes



signature.asc
Description: OpenPGP digital signature

Re: jenkins e-mail ext DEFAULT_CONTENT does not expand

2013-05-26 Thread Slide

You need a space before format, also why are you setting the format to
empty string.
On May 26, 2013 4:07 AM, "Vladimir Zak"  wrote:

> Hi,
> I have the same problem. The strings are not replaced by URl for example -
> $BUILD_URL is not replaced.
>
> In subjects it is replaced but NOT replaced in the other places.
>
> zakyn
>
> $PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS!$PROJECT_URL
> $BUILD_URL  Tests
>
> $FAILED_TESTS
>
> Changes  [%a] %m %p${CHANGES,format=" "}
>
>
>
>
>
> 2013/4/24 windycity 
>
>>
>> Attach log.
>>
>>
>> Jessica
>>
>> On Wednesday, April 24, 2013 4:04:04 PM UTC-5, windycity wrote:
>>>
>>> We are using tomcat, I have logs at 
>>> tomcat/apache-tomcat-6.0.35/**logs/catalina.out,
>>> is that the right one? But this one does not have any Jenkins error. Build
>>> #23 is the trouble one.
>>>
>>> Jessica
>>>
>>> On Wednesday, April 24, 2013 3:36:18 PM UTC-5, slide wrote:

 No, I mean the actual stderr type logs for the Jenkins app itself, it
 would be in different places depending on how you are running Jenkins.
 Could be in the tomcat logs, etc.


 On Wed, Apr 24, 2013 at 1:33 PM, windycity  wrote:

> By jenkins log, do you mean $JENKINS_HOME/jobs/project/**builds/#/log
> file?  If this is the file you refer, it does have build errors, but
> sending mail seems fine.
>
> Sending e-mails to: j...@cboe.com
> channel stopped
> Sending e-mails to: j...@cboe.com
> Email was triggered for: Failure
> Sending email for trigger: Failure
> Sending email to: j...@cboe.com
> Finished: FAILURE
>
> If this is not the log you refer, would you please let me know where
> should be the log file?
>
> Thanks much,
>
> Jessica
>
>
>
> On Wednesday, April 24, 2013 3:13:54 PM UTC-5, slide wrote:
>
>> Do you have any errors in jenkins logs?
>>
>>
>> On Wed, Apr 24, 2013 at 12:43 PM, windycity  wrote:
>>
>>> I am looking at this file, actually, I figure
>>>
>>> ${JELLY_SCRIPT,template="html"}
>>>
>>> is the problem, if I get rid of this, everything seems working,
>>> though I do not understand why. Somebody else put this in global
>>> configuration, maybe this format is wrong, maybe it should be
>>> ${JELLY_SCRIPT, html}?
>>>
>>>
>>>  Following is the content of ExtendedEmailPublisher xml file from
>>> the root of JENKINS_HOME
>>>
>>> Thanks much!
>>>
>>> Jessica
>>>
>>> 
>>> >> plugin="email-ext@2.28">
>>>   
>>> http://openjdk2a:**80**81/jenkins/
>>> 
>>>   address not configured yet
>>> 
>>>   false
>>>   text/html
>>>   ${MAVEN_**PREBUI**LD_VERSION} $PROJECT_NAME -
>>> Build # $BUILD_NUMBER - $BUILD_STATUS!
>>>   $PROJECT_NAME ${MAVEN_PREBUILD_VERSION}  - Build #
>>> $BUILD_NUMBER - $BUILD_STATUS:
>>> 
>>> Check console output at $BUILD_URL to view the results.
>>> 
>>> ${JELLY_SCRIPT,template="html"}
>>>   -1
>>>   j...@cboe.com
>>>
>>>   
>>>   false
>>>   false
>>>   false
>>>   false
>>> 
>>>
>>>
>>>
>>> On Wednesday, April 24, 2013 2:33:08 PM UTC-5, slide wrote:
>>>
 My apologies, I need the ExtendedEmailPublisher xml file from the
 root of JENKINS_HOME.


 On Wed, Apr 24, 2013 at 10:03 AM, windycity wrote:

>
> Here attached are the global and project config files, please let
> me know what is wrong.
>
> Thanks much for all your help!
>
> Jessica
>
>
> On Wednesday, April 24, 2013 8:59:51 AM UTC-5, slide wrote:
>
>> pre-build/post build added token
>> MIME-Version: 1.0
>> Content-Type: multipart/alternative;
>> boundary="=_Part_**8**9_9798859.1366811681215"
>>
>> --=_Part_89_9798859.**136681**1681215
>> Content-Type: text/plain; charset="utf-8"
>> Content-Transfer-Encoding: 7bit
>>
>> They are expanded the same way, so I need more information (like
>> your
>> global and project config XML) to try and determine the issue.
>>
>> Sent from my Windows Phone
>> From: windycity
>> Sent: 4/24/2013 6:54
>> To: jenkins...@googlegroups.**com
>> Subject: jenkins e-mail ext DEFAULT_CONTENT does not expand
>> pre-build/post build added token
>> I use jenkin's configuration pre-build and post build "Execute
>> Groovy
>> System Script"-> command to get a token $MAVE_PREBUIL_VERSION and
>> $MAVEN_POSTBUILD_MAVEN, and put this at e-mail ext plugin
>> configuration. In
>>

Re: [1.509.1 LTS] Massive performance issues

2013-05-26 Thread Vladimir Zak

Hi,

I think it is because of the dashboard plugin.
Is this problem already reported?

Vladimir


2013/5/21 Steffen Breitbach 

> Hi Arnaud!
>
>
> On 19.05.2013 11:48, Arnaud Héritier wrote:
>
>> I have such issue and downgraded back to 1.480.3 LTS.
>>
>
> I'm also looking into this as a possible fix for our current situation.
>
> Did you face any issues after downgrading to 1.480.3 LTS ?
>
>
> Regards
>   Steffen
>
> --
> 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, send an
> email to 
> jenkinsci-users+unsubscribe@**googlegroups.com
> .
> For more options, visit 
> https://groups.google.com/**groups/opt_out
> .
>
>
>

-- 
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, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: jenkins e-mail ext DEFAULT_CONTENT does not expand

2013-05-26 Thread Vladimir Zak

Hi,

I used the last one LTS version of jenkins, email-ext-plugin -
2.30.2

I found only this

Email was triggered for: Before Build
Sending email for trigger: Before Build
Error evaluating token: Undefined parameter maxlines in token BUILD_LOG
Sending email to:

The new one is maxLines - after the change it seems to run OK.


Were the tokens changed? I used them for really long time heavily and I
hope it has not been changed massively.

zakyn





2013/5/26 Vladimir Zak 

> Hi,
> I have the same problem. The strings are not replaced by URl for example -
> $BUILD_URL is not replaced.
>
> In subjects it is replaced but NOT replaced in the other places.
>
> zakyn
>
> $PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS!
> $PROJECT_URL
> $BUILD_URL  Tests
>
> $FAILED_TESTS
>
> Changes  [%a] %m %p${CHANGES,format=" "}
>
>
>
>
>
> 2013/4/24 windycity 
>
>>
>> Attach log.
>>
>>
>> Jessica
>>
>> On Wednesday, April 24, 2013 4:04:04 PM UTC-5, windycity wrote:
>>>
>>> We are using tomcat, I have logs at 
>>> tomcat/apache-tomcat-6.0.35/**logs/catalina.out,
>>> is that the right one? But this one does not have any Jenkins error. Build
>>> #23 is the trouble one.
>>>
>>> Jessica
>>>
>>> On Wednesday, April 24, 2013 3:36:18 PM UTC-5, slide wrote:

 No, I mean the actual stderr type logs for the Jenkins app itself, it
 would be in different places depending on how you are running Jenkins.
 Could be in the tomcat logs, etc.


 On Wed, Apr 24, 2013 at 1:33 PM, windycity  wrote:

> By jenkins log, do you mean $JENKINS_HOME/jobs/project/**builds/#/log
> file?  If this is the file you refer, it does have build errors, but
> sending mail seems fine.
>
> Sending e-mails to: j...@cboe.com
> channel stopped
> Sending e-mails to: j...@cboe.com
> Email was triggered for: Failure
> Sending email for trigger: Failure
> Sending email to: j...@cboe.com
> Finished: FAILURE
>
> If this is not the log you refer, would you please let me know where
> should be the log file?
>
> Thanks much,
>
> Jessica
>
>
>
> On Wednesday, April 24, 2013 3:13:54 PM UTC-5, slide wrote:
>
>> Do you have any errors in jenkins logs?
>>
>>
>> On Wed, Apr 24, 2013 at 12:43 PM, windycity  wrote:
>>
>>> I am looking at this file, actually, I figure
>>>
>>> ${JELLY_SCRIPT,template="html"}
>>>
>>> is the problem, if I get rid of this, everything seems working,
>>> though I do not understand why. Somebody else put this in global
>>> configuration, maybe this format is wrong, maybe it should be
>>> ${JELLY_SCRIPT, html}?
>>>
>>>
>>>  Following is the content of ExtendedEmailPublisher xml file from
>>> the root of JENKINS_HOME
>>>
>>> Thanks much!
>>>
>>> Jessica
>>>
>>> 
>>> >> plugin="email-ext@2.28">
>>>   
>>> http://openjdk2a:**80**81/jenkins/
>>> 
>>>   address not configured yet
>>> 
>>>   false
>>>   text/html
>>>   ${MAVEN_**PREBUI**LD_VERSION} $PROJECT_NAME -
>>> Build # $BUILD_NUMBER - $BUILD_STATUS!
>>>   $PROJECT_NAME ${MAVEN_PREBUILD_VERSION}  - Build #
>>> $BUILD_NUMBER - $BUILD_STATUS:
>>> 
>>> Check console output at $BUILD_URL to view the results.
>>> 
>>> ${JELLY_SCRIPT,template="html"}
>>>   -1
>>>   j...@cboe.com
>>>
>>>   
>>>   false
>>>   false
>>>   false
>>>   false
>>> 
>>>
>>>
>>>
>>> On Wednesday, April 24, 2013 2:33:08 PM UTC-5, slide wrote:
>>>
 My apologies, I need the ExtendedEmailPublisher xml file from the
 root of JENKINS_HOME.


 On Wed, Apr 24, 2013 at 10:03 AM, windycity wrote:

>
> Here attached are the global and project config files, please let
> me know what is wrong.
>
> Thanks much for all your help!
>
> Jessica
>
>
> On Wednesday, April 24, 2013 8:59:51 AM UTC-5, slide wrote:
>
>> pre-build/post build added token
>> MIME-Version: 1.0
>> Content-Type: multipart/alternative;
>> boundary="=_Part_**8**9_9798859.1366811681215"
>>
>> --=_Part_89_9798859.**136681**1681215
>> Content-Type: text/plain; charset="utf-8"
>> Content-Transfer-Encoding: 7bit
>>
>> They are expanded the same way, so I need more information (like
>> your
>> global and project config XML) to try and determine the issue.
>>
>> Sent from my Windows Phone
>> From: windycity
>> Sent: 4/24/2013 6:54
>>

Re: jenkins e-mail ext DEFAULT_CONTENT does not expand

2013-05-26 Thread Vladimir Zak

Hi,
I have the same problem. The strings are not replaced by URl for example -
$BUILD_URL is not replaced.

In subjects it is replaced but NOT replaced in the other places.

zakyn

$PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS!$PROJECT_URL
$BUILD_URL <$BUILD_URL/artifact/Installation/InstallationKit> Tests

$FAILED_TESTS

Changes  [%a] %m %p${CHANGES,format=" "}





2013/4/24 windycity 

>
> Attach log.
>
>
> Jessica
>
> On Wednesday, April 24, 2013 4:04:04 PM UTC-5, windycity wrote:
>>
>> We are using tomcat, I have logs at 
>> tomcat/apache-tomcat-6.0.35/**logs/catalina.out,
>> is that the right one? But this one does not have any Jenkins error. Build
>> #23 is the trouble one.
>>
>> Jessica
>>
>> On Wednesday, April 24, 2013 3:36:18 PM UTC-5, slide wrote:
>>>
>>> No, I mean the actual stderr type logs for the Jenkins app itself, it
>>> would be in different places depending on how you are running Jenkins.
>>> Could be in the tomcat logs, etc.
>>>
>>>
>>> On Wed, Apr 24, 2013 at 1:33 PM, windycity  wrote:
>>>
 By jenkins log, do you mean $JENKINS_HOME/jobs/project/**builds/#/log
 file?  If this is the file you refer, it does have build errors, but
 sending mail seems fine.

 Sending e-mails to: j...@cboe.com
 channel stopped
 Sending e-mails to: j...@cboe.com
 Email was triggered for: Failure
 Sending email for trigger: Failure
 Sending email to: j...@cboe.com
 Finished: FAILURE

 If this is not the log you refer, would you please let me know where
 should be the log file?

 Thanks much,

 Jessica



 On Wednesday, April 24, 2013 3:13:54 PM UTC-5, slide wrote:

> Do you have any errors in jenkins logs?
>
>
> On Wed, Apr 24, 2013 at 12:43 PM, windycity  wrote:
>
>> I am looking at this file, actually, I figure
>>
>> ${JELLY_SCRIPT,template="html"}
>>
>> is the problem, if I get rid of this, everything seems working,
>> though I do not understand why. Somebody else put this in global
>> configuration, maybe this format is wrong, maybe it should be
>> ${JELLY_SCRIPT, html}?
>>
>>
>>  Following is the content of ExtendedEmailPublisher xml file from the
>> root of JENKINS_HOME
>>
>> Thanks much!
>>
>> Jessica
>>
>> 
>> > plugin="email-ext@2.28">
>>   
>> http://openjdk2a:**80**81/jenkins/
>> 
>>   address not configured yet
>> 
>>   false
>>   text/html
>>   ${MAVEN_**PREBUI**LD_VERSION} $PROJECT_NAME -
>> Build # $BUILD_NUMBER - $BUILD_STATUS!
>>   $PROJECT_NAME ${MAVEN_PREBUILD_VERSION}  - Build #
>> $BUILD_NUMBER - $BUILD_STATUS:
>> 
>> Check console output at $BUILD_URL to view the results.
>> 
>> ${JELLY_SCRIPT,template="html"}
>>   -1
>>   j...@cboe.com
>>
>>   
>>   false
>>   false
>>   false
>>   false
>> 
>>
>>
>>
>> On Wednesday, April 24, 2013 2:33:08 PM UTC-5, slide wrote:
>>
>>> My apologies, I need the ExtendedEmailPublisher xml file from the
>>> root of JENKINS_HOME.
>>>
>>>
>>> On Wed, Apr 24, 2013 at 10:03 AM, windycity wrote:
>>>

 Here attached are the global and project config files, please let
 me know what is wrong.

 Thanks much for all your help!

 Jessica


 On Wednesday, April 24, 2013 8:59:51 AM UTC-5, slide wrote:

> pre-build/post build added token
> MIME-Version: 1.0
> Content-Type: multipart/alternative;
> boundary="=_Part_**8**9_9798859.1366811681215"
>
> --=_Part_89_9798859.**136681**1681215
> Content-Type: text/plain; charset="utf-8"
> Content-Transfer-Encoding: 7bit
>
> They are expanded the same way, so I need more information (like
> your
> global and project config XML) to try and determine the issue.
>
> Sent from my Windows Phone
> From: windycity
> Sent: 4/24/2013 6:54
> To: jenkins...@googlegroups.**com
> Subject: jenkins e-mail ext DEFAULT_CONTENT does not expand
> pre-build/post build added token
> I use jenkin's configuration pre-build and post build "Execute
> Groovy
> System Script"-> command to get a token $MAVE_PREBUIL_VERSION and
> $MAVEN_POSTBUILD_MAVEN, and put this at e-mail ext plugin
> configuration. In
> both global and project session, DEFAULT_SUBJECT can extent these
> Tokens,
> but DEFAULT_CONTENT can not, is this a known issue or I am not
> using it
> right?
>
> $DEFAULT_SUBJECT, ${MAVEN_PREBUILD_VERSION},
> ${MAVEN_POSTBUILD_VERSION}
> Above

Re: Single-User Permission Issues in LTS

Re: jenkins e-mail ext DEFAULT_CONTENT does not expand

config.xml missing after install

Single-User Permission Issues in LTS

Re: jenkins e-mail ext DEFAULT_CONTENT does not expand

Re: [1.509.1 LTS] Massive performance issues

Re: jenkins e-mail ext DEFAULT_CONTENT does not expand

Re: jenkins e-mail ext DEFAULT_CONTENT does not expand

8 matches

Site Navigation

Mail list logo

Footer information