The release notes for something you're building seem like they should come from 
a file in the source control system rather than being submitted to the Jenkins 
job through a web page.  That will allow the release notes to be tied to the 
same tags and branches as the source code they are documenting.

If the author of the release notes submits them to the source control system, 
then your build scripts can package them, and if you really need to create a 
link to those release notes from the Jenkins job description, you could use the 
description setter plugin or one of the other plugins (like the sidebar links 
plugin).

If you allow hard coded paths / file names, it seems like you won't be able to 
run the job on slaves, unless you're also planning on making the same hard 
coded path visible on all slaves.  If the release notes are in the source 
control system, then you can reference them with relative paths, just as you 
reference other files from your build scripts.

Mark Waite



>________________________________
> From: Jan Seidel <wakkal...@gmail.com>
>To: jenkinsci-users@googlegroups.com 
>Sent: Thursday, June 28, 2012 3:55 AM
>Subject: I need to drop text from Jenkins into a text file before build
> 
>
>Hi folks,
>
>I need an option that allows me to drop special notes into a plain text file.
>This must happen before some Jenkins jobs start to run as that text will be 
>pasted into release notes.
>It must handle hardcoded locations/filenames.
>
>In best case does each job have its own textarea/editor which points to a 
>specific file.
>I was thinking about plugins. There is afaik a plugin that allows JScript but 
>I'm not sure if this also applies on pages from jobs. If so a plain wysiwyg 
>editor could be added if it supports hardcoded paths/file names (hints about a 
>good editor are highly appreciated).
>
>It should be located either in the description of a jobs main page or on the 
>configuration page of the build.
>Using the built-in text parameter is not working well. The content is passed 
>throug the entire build pipeline, prohibits certain characters and may even 
>wreck the ant calls to build.
>I was also thinking about installing a mini web-server and add a link to that 
>server to manipulate from outside but this is absolutely not my favorite 
>approach.
>
>Do you have any ideas, suggestions or even plugins at hand for this task?
>
>Cheers
>Jan
>
>
>

Reply via email to