Re: How to make variables available to all build steps/action in a job

2012-03-20 Thread Jan Seidel
sorry for the gibberish in the text. I'm a bit tired and in a hurry ... e.g fugred instead of figured ;) On 20 Mrz., 11:56, Jan Seidel wrote: > Hi folks, thanks for you replies :) > > @shanz just fugred it out tonight, was just a bit late to let you > know. > > @Didier your approach won't work as

Re: How to make variables available to all build steps/action in a job

2012-03-20 Thread Jan Seidel
Hi folks, thanks for you replies :) @shanz just fugred it out tonight, was just a bit late to let you know. @Didier your approach won't work as the env variables you are pointing to are somewhat static. You can't modiefy them from within a job at build time. This would require 3 stages. Manipulat

Re: How to make variables available to all build steps/action in a job

2012-03-20 Thread shanz
Oh yes, you need to define subject up near the top of the script and change the final call to send_mail(). Eg: import smtplib import os from email.MIMEMultipart import MIMEMultipart from email.MIMEBase import MIMEBase from email.MIMEText import MIMEText from email.Utils import COMMASPACE, formatdat

Re: How to make variables available to all build steps/action in a job

2012-03-19 Thread Jan Seidel
Hi Shanz, this script works like a charm :) I have modified it to my needs so the mail body is streamed from a text file but am struggling with a minor problem. The subject remains empty. I tried to assign it a sentence like: subject = "new XX integrations for asia available" with all kind of

Re: How to make variables available to all build steps/action in a job

2012-03-19 Thread Didier Durand
Hi, You can go into Jenkins Configure > Global Properties & there set env variables that are available to all jobs. regards didier Le lundi 19 mars 2012 09:59:09 UTC+1, Jan Seidel a écrit : > > Hi Shanz, > > *uhm* mkey... I am not familiar with python but I will give it a try. > Seems to be

Re: How to make variables available to all build steps/action in a job

2012-03-19 Thread dpreilan
Have you try the inject environment plugins? Also, there is a place on top of job configurations to set variables as well. I have use the inject environment variables as a build setup. For example step1, do some logic, write some variables to a property file. step2, use the inject variable build se

Re: How to make variables available to all build steps/action in a job

2012-03-19 Thread Jan Seidel
Hi Shanz, *uhm* mkey... I am not familiar with python but I will give it a try. Seems to be quite convenient to adapt the properties to my needs. Thanks for your feedback :) Take care Jan On 16 Mrz., 16:34, shanz wrote: > I found that a python script gave me more flexibility in what I could >

Re: How to make variables available to all build steps/action in a job

2012-03-16 Thread shanz
I found that a python script gave me more flexibility in what I could attach to an email... import smtplib import os from email.MIMEMultipart import MIMEMultipart from email.MIMEBase import MIMEBase from email.MIMEText import MIMEText from email.Utils import COMMASPACE, formatdate from email impo

How to make variables available to all build steps/action in a job

2012-03-16 Thread Jan Seidel
Hi folks, I am going nuts here ... I want to create an action that composes and sends an email notification if a build has been build and was tested successfully. My idea was to implement a promotion into the release build job that has to promoted manually. This way can managers and tester simple