Glottr Report for Locale 'fr'

MISSING

CLI.NoSuchFileExists
05.03.2013 22:30:19, no SCM information
No such file exists: {0}

MISSING

CLI.NoURL
05.03.2013 22:30:19, no SCM information
Neither -s nor the JENKINS_URL env var is specified.

MISSING

CLI.Usage
05.03.2013 22:30:19, no SCM information
Jenkins CLI Usage: java -jar jenkins-cli.jar [-s URL] command [opts...] args... Options: -s URL : the server URL (defaults to the JENKINS_URL env var) -i KEY : SSH private key file used for authentication -p HOST:PORT : HTTP proxy host and port for HTTPS proxy tunneling. See http://jenkins-ci.org/https-proxy-tunnel -noCertificateCheck : bypass HTTPS certificate check entirely. Use with caution The available commands depend on the server. Run the 'help' command to see the list.

MISSING

CLI.VersionMismatch
05.03.2013 22:30:19, no SCM information
Version mismatch. This CLI cannot work with this Jenkins server.

core/src/main/resources/hudson/AboutJenkins/index_fr.properties

Files

MISSING

No information recorded
14.06.2013 07:43:03, no SCM information
No information recorded

CURRENT

about
29.04.2013 12:15:14, no SCM information	30.05.2013 20:09:20, no SCM information
About Jenkins {0}	A propos de Jenkins {0}

CURRENT

blurb
29.04.2013 12:15:14, no SCM information	30.05.2013 20:09:20, no SCM information
<a href="http://jenkins-ci.org/">Jenkins</a> is a community-developed open-source continuous integration server.	<a href="http://jenkins-ci.org/">Jenkins</a> est un serveur d''intégration continue développé par la communauté open-source.

CURRENT

dependencies
29.04.2013 12:15:14, no SCM information	30.05.2013 20:09:20, no SCM information
Jenkins depends on the following 3rd party libraries.	Jenkins dépend des librairies externes suivantes

CURRENT

plugin.dependencies
29.04.2013 12:15:14, no SCM information	30.05.2013 20:09:20, no SCM information
License and dependency information for plugins:	Licence et informations de dépendance pour les plugins :

core/src/main/resources/hudson/Messages_fr.properties

Files

MISSING

FilePath.did_not_manage_to_validate_may_be_too_sl
01.08.2013 07:43:47, no SCM information
Did not manage to validate {0} (may be too slow)

MISSING

PluginManager.ConfigureUpdateCenterPermission.Description
01.08.2013 07:43:47, no SCM information
The "configure update center" permission allows a user to configure update sites and proxy settings.

MISSING

PluginManager.PluginDoesntSupportDynamicLoad.RestartRequired
01.08.2013 07:43:47, no SCM information
{0} plugin doesn’t support dynamic loading. Jenkins needs to be restarted for the update to take effect

MISSING

PluginManager.PluginIsAlreadyInstalled.RestartRequired
01.08.2013 07:43:47, no SCM information
{0} plugin is already installed. Jenkins needs to be restarted for the update to take effect

MISSING

PluginManager.UploadPluginsPermission.Description
01.08.2013 07:43:47, no SCM information
The "upload plugin" permission allows a user to upload arbitrary plugins.

OUTDATED

AboutJenkins.Description
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
See the version and license information.	Afficher les informations de version et de licence
(old value)

OUTDATED

AboutJenkins.DisplayName
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
About Jenkins	A propos de Jenkins
(old value)

OUTDATED

FilePath.TildaDoesntWork
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
‘~’ is only supported in a Unix shell and nowhere else.	''~'' n''est supporté que sur les shells Unix.
(old value)

OUTDATED

FilePath.validateAntFileMask.doesntMatchAndSuggest
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
‘{0}’ doesn’t match anything, but ‘{1}’ does. Perhaps that’s what you mean?	''{0}'' ne correspond à rien, mais ''{1}'' oui. Peut-être est-ce cela que vous voulez dire?
(old value)

OUTDATED

FilePath.validateAntFileMask.doesntMatchAnything
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
‘{0}’ doesn’t match anything	''{0}'' ne correspond à rien
(old value)

OUTDATED

FilePath.validateAntFileMask.doesntMatchAnythingAndSuggest
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
‘{0}’ doesn’t match anything: even ‘{1}’ doesn’t exist	''{0}'' ne correspond à rien : même ''{1}'' n'existe pas
(old value)

OUTDATED

FilePath.validateAntFileMask.portionMatchAndSuggest
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
‘{0}’ doesn’t match anything, although ‘{1}’ exists	''{0}'' ne correspond à rien, même si ''{1}'' existe
(old value)

OUTDATED

FilePath.validateAntFileMask.portionMatchButPreviousNotMatchAndSuggest
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
‘{0}’ doesn’t match anything: ‘{1}’ exists but not ‘{2}’	''{0}'' ne correspond à rien : ''{1}'' existe mais pas ''{2}''
(old value)

OUTDATED

FilePath.validateAntFileMask.whitespaceSeprator
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
Whitespace can no longer be used as the separator. Please Use ‘,’ as the separator instead.	Les espaces ne peuvent plus être utilisés comme séparateurs. Merci d''utiliser maintenant '','' comme séparateur à la place.
(old value)

OUTDATED

FilePath.validateRelativePath.noSuchDirectory
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
No such directory: ‘{0}’	Aucun répertoire correspondant : ''{0}''
(old value)

OUTDATED

FilePath.validateRelativePath.noSuchFile
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
No such file: ‘{0}’	Aucun fichier correspondant : ''{0}''
(old value)

OUTDATED

FilePath.validateRelativePath.notDirectory
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
‘{0}’ is not a directory	''{0}'' n''est pas un répertoire
(old value)

OUTDATED

FilePath.validateRelativePath.notFile
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
‘{0}’ is not a file	''{0}'' n''est pas un fichier
(old value)

OUTDATED

FilePath.validateRelativePath.wildcardNotAllowed
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
Wildcard is not allowed here	L''utilisation des Wildcard n''est pas autorisée ici
(old value)

OUTDATED

PluginManager.DisplayName
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
Plugin Manager	Gestion des plugins
(old value)

OUTDATED

PluginManager.PortNotANumber
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
Port is not a number	Le port n''est pas un nombre
(old value)

OUTDATED

PluginManager.PortNotInRange
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
Port doesn’t range from {0} to {1}	Le port n''est pas dans l''intervalle de {0} à {1}
(old value)

OUTDATED

Util.day
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
{0} {0,choice,0#days\|1#day\|1<days}	{0} j
(old value)

OUTDATED

Util.hour
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
{0} hr	{0} h
(old value)

OUTDATED

Util.millisecond
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
{0} ms	{0} ms
(old value)

OUTDATED

Util.minute
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
{0} min	{0} mn
(old value)

OUTDATED

Util.month
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
{0} mo	{0} mo.
(old value)

OUTDATED

Util.pastTime
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
{0}	{0}
(old value)

OUTDATED

Util.second
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
{0} sec	{0} s
(old value)

OUTDATED

Util.year
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
{0} yr	{0} an.
(old value)

core/src/main/resources/hudson/PluginManager/PluginCycleDependenciesMonitor/message.jelly (Master)

Files

MISSING

PluginCycles
04.02.2013 00:16:05, no SCM information
The following plugins are deactivated because of cyclic dependencies, most likely you can resolve the issue by updating these to a newer version.

core/src/main/resources/hudson/PluginManager/PluginUpdateMonitor/message.jelly (Master)

Files

checkUpdates_fr.properties

MISSING

RequiredPluginUpdates
04.02.2013 00:16:05, no SCM information
The following plugins require an update.

core/src/main/resources/hudson/PluginManager/advanced_fr.properties

Files

advanced.jelly

advanced_fr.properties

MISSING

Other Sites
29.04.2013 12:15:14, no SCM information
Other Sites

MISSING

URL
29.04.2013 12:15:14, no SCM information
URL

MISSING

Update Center
29.04.2013 12:15:14, no SCM information
Update Center

OUTDATED

Check now
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:05, no SCM information
Check now	Vérifier maintenant
(old value)

OUTDATED

File
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:05, no SCM information
File	Fichier
(old value)

OUTDATED

HTTP Proxy Configuration
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:05, no SCM information
HTTP Proxy Configuration	Configuration du proxy HTTP
(old value)

OUTDATED

Submit
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:05, no SCM information
Submit	Soumettre
(old value)

OUTDATED

Update Site
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:05, no SCM information
Update Site	Site de mise à jour
(old value)

OUTDATED

Upload
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:05, no SCM information
Upload	Soumettre
(old value)

OUTDATED

Upload Plugin
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:05, no SCM information
Upload Plugin	Soumettre un plugin
(old value)

ORPHANED

No Proxy for
	04.02.2013 00:16:05, no SCM information
	Pas de proxy pour

ORPHANED

Password
	04.02.2013 00:16:05, no SCM information
	Mot de passe

ORPHANED

Port
	04.02.2013 00:16:05, no SCM information
	—

ORPHANED

Proxy Needs Authorization
	04.02.2013 00:16:05, no SCM information
	Le proxy nécessite une authentification

ORPHANED

Server
	04.02.2013 00:16:05, no SCM information
	Serveur

ORPHANED

User name
	04.02.2013 00:16:05, no SCM information
	Nom d''utilisateur

CURRENT

lastUpdated
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Update information obtained: {0} ago	Dernière mise à jour: il y a {0}

CURRENT

uploadtext
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
You can upload a .hpi file to install a plugin from outside the central plugin repository.	Indiquez ici le chemin vers un plugin à ajouter à ce serveur Jenkins

core/src/main/resources/hudson/PluginManager/available_fr.properties

Files

available.jelly

available_fr.properties

ORPHANED

Available
	04.02.2013 00:16:05, no SCM information
	Disponibles

ORPHANED

Installed
	04.02.2013 00:16:05, no SCM information
	Installés

ORPHANED

Updates
	04.02.2013 00:16:05, no SCM information
	Mises à jour

core/src/main/resources/hudson/PluginManager/checkUpdates_fr.properties

Files

checkUpdates.jelly

MISSING

Update Center
04.02.2013 00:16:05, no SCM information
Update Center

CURRENT

Checking Updates...
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Checking Updates...	Recherche des mises à jour...

CURRENT

Done
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Done	Terminé

CURRENT

Go back to update center
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Go back to update center	Retourner à la page principale des mises à jour

core/src/main/resources/hudson/PluginManager/index_fr.properties

Files

CURRENT

All
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
All	Tous

CURRENT

None
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
None	Aucun

CURRENT

Select
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Select	Sélectionnez

CURRENT

UpdatePageDescription
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
This page lists updates to the plugins you currently use.	Cette page liste les mises à jour des plugins en cours d''utilisation.

CURRENT

UpdatePageLegend
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Disabled rows are already upgraded, awaiting restart. Shaded but selectable rows are <a href="{0}">in progress or failed</a>.	Les lignes désactivées sont déjà mises à jour et attendent un redémarrage. Les lignes grisées mais sélectionnables sont <a href="{0}">en cours ou en échec</a>.

core/src/main/resources/hudson/PluginManager/installed_fr.properties

Files

installed.jelly

installed_fr.properties

MISSING

No description available.
30.05.2013 20:09:20, no SCM information
No description available.

MISSING

Uninstall
30.05.2013 20:09:20, no SCM information
Uninstall

MISSING

Uninstallation pending
30.05.2013 20:09:20, no SCM information
Uninstallation pending

MISSING

Update Center
30.05.2013 20:09:20, no SCM information
Update Center

OUTDATED

Changes will take effect when you restart Jenkins
30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:05, no SCM information
Changes will take effect when you restart Jenkins	Les changements seront pris en compte après un redémarrage de Jenkins
(old value)

OUTDATED

Enabled
30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:05, no SCM information
Enabled	Activé
(old value)

OUTDATED

Name
30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:05, no SCM information
Name	Nom
(old value)

OUTDATED

No plugins installed.
30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:05, no SCM information
No plugins installed.	Aucun plugin n''est installé.
(old value)

OUTDATED

Pinned
30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:05, no SCM information
Pinned	Epinglé
(old value)

OUTDATED

Previously installed version
30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:05, no SCM information
Previously installed version	Version précédente
(old value)

OUTDATED

Restart Once No Jobs Are Running
30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:05, no SCM information
Restart Once No Jobs Are Running	Redémarrer quand tous les travaux sont finis
(old value)

OUTDATED

Uncheck to disable the plugin
30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:05, no SCM information
Uncheck to disable the plugin	Décochez pour désactiver le plugin
(old value)

OUTDATED

Unpin
30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:05, no SCM information
Unpin	Détacher
(old value)

OUTDATED

Version
30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:05, no SCM information
Version	Version
(old value)

ORPHANED

New plugins will take effect once you restart Jenkins
	04.02.2013 00:16:05, no SCM information
	Les nouveaux plugins seront pris en compte après un redémarrage de Jenkins

CURRENT

downgradeTo
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Downgrade to {0}	Rétrograder vers {0}

CURRENT

wiki.url
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
http://wiki.jenkins-ci.org/display/JENKINS/Pinned+Plugins	http://wiki.jenkins-ci.org/display/JENKINS/Pinned+Plugins

core/src/main/resources/hudson/PluginManager/sidepanel_fr.properties

Files

sidepanel.groovy

MISSING

Update Center
04.02.2013 00:16:05, no SCM information
Update Center

CURRENT

Back to Dashboard
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Back to Dashboard	Retour au tableau de bord

CURRENT

Manage Jenkins
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Manage Jenkins	Administrer Jenkins

core/src/main/resources/hudson/PluginManager/sites.jelly (Master)

Files

sites.jelly

thirdPartyLicenses_fr.properties

MISSING

Add...
04.02.2013 00:16:05, no SCM information
Add...

MISSING

Remove
04.02.2013 00:16:05, no SCM information
Remove

MISSING

Update Center
04.02.2013 00:16:05, no SCM information
Update Center

core/src/main/resources/hudson/PluginManager/tabBar_fr.properties

Files

tabBar.jelly

tabBar_fr.properties

MISSING

Sites
04.02.2013 00:16:05, no SCM information
Sites

CURRENT

Advanced
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Advanced	Avancé

CURRENT

Available
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Available	Disponibles

CURRENT

Installed
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Installed	Installés

CURRENT

Updates
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Updates	Mises à jour

core/src/main/resources/hudson/PluginManager/table_fr.properties

Files

table.jelly

table_fr.properties

MISSING

Download now and install after restart
04.02.2013 00:16:05, no SCM information
Download now and install after restart

MISSING

Filter
04.02.2013 00:16:05, no SCM information
Filter

MISSING

Inactive
04.02.2013 00:16:05, no SCM information
Inactive

MISSING

Install without restart
04.02.2013 00:16:05, no SCM information
Install without restart

MISSING

Update Center
04.02.2013 00:16:05, no SCM information
Update Center

CURRENT

Check to install the plugin
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Check to install the plugin	Cochez pour installer le plugin

CURRENT

Click this heading to sort by category
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Click this heading to sort by category	Cliquez sur cette rubrique pour trier par catégorie

CURRENT

Install
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Install	Installer

CURRENT

Installed
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Installed	Installée

CURRENT

Name
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Name	Nom

CURRENT

No updates
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
No updates	Pas de mises à jour

CURRENT

Version
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Version	Version

CURRENT

compatWarning
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Warning: New version not compatible with installed version. Jobs using this plugin may need to be reconfigured.	Avertissement: Cette nouvelle version n''est pas compatible avec la version installée. Il peut être nécessaire de reconfigurer les tâches utilisant ce plugin.

CURRENT

coreWarning
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Warning: This plugin is built for Jenkins {0} or newer. It may or may not work in your Jenkins.	Ce plugin est construit pour Jenkins {0} ou une version plus récente. Il pourrait ne pas fonctionner avec votre version de Jenkins.

core/src/main/resources/hudson/PluginWrapper/thirdPartyLicenses_fr.properties

Files

thirdPartyLicenses.jelly

MISSING

3rd Party Dependencies
04.02.2013 00:16:05, no SCM information
3rd Party Dependencies

CURRENT

No information recorded
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
No information recorded	Aucune information renseignée

CURRENT

about
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
About {0}	A propos de {0}

core/src/main/resources/hudson/PluginWrapper/uninstall.groovy (Master)

Files

uninstall.groovy

MISSING

Yes
04.02.2013 00:16:05, no SCM information
Yes

MISSING

msg
04.02.2013 00:16:05, no SCM information
You are about to uninstall the <b>{0}</b> plugin. This will remove the plugin binary from your $JENKINS_HOME, but it will leave the configuration files of the plugin untouched.

MISSING

title
04.02.2013 00:16:05, no SCM information
Uninstalling {0} plugin

core/src/main/resources/hudson/ProxyConfiguration/config_fr.properties

Files

MISSING

No Proxy Host
04.02.2013 00:16:05, no SCM information
No Proxy Host

EMPTY

Port
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Port	—

ORPHANED

No Proxy for
	04.02.2013 00:16:05, no SCM information
	Pas de proxy pour

ORPHANED

Proxy Needs Authorization
	04.02.2013 00:16:05, no SCM information
	Le proxy nécessite une authentification

CURRENT

Password
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Password	Mot de passe

CURRENT

Server
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Server	Serveur

CURRENT

User name
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
User name	Nom d''utilisateur

core/src/main/resources/hudson/ProxyConfiguration/help-name_fr.html

Files

help-name.html

help-name_fr.html

CURRENT

04.02.2013 00:16:05, no SCM information

<div>
If your Jenkins server sits behind a firewall and does not have the direct access to the internet,
and if your server JVM is not configured appropriately
(<a href="http://download.oracle.com/javase/6/docs/technotes/guides/net/properties.html">See JDK networking properties for more details</a>)
to enable internet connection, you can specify the HTTP proxy server name in this field to allow Jenkins
to install plugins on behalf of you. Note that Jenkins uses HTTPS to communicate with the update center to download plugins.

<p>
The value you submit here will be set as <tt>http.proxyHost</tt> system property. Leaving this field empty
causes this property to be unset, which means Jenkins will try to connect to the host directly.

<p>
If you are unsure about the value, check the browser proxy configuration.
</div>

<div>
Si votre serveur Jenkins se trouve derrière un firewall, qu'il n'a pas d'accès direct à internet et
que la JVM de votre serveur n'est pas configurée de façon à permettre l'accès à internet (voir
<a href="http://download.oracle.com/javase/6/docs/technotes/guides/net/properties.html">les propriétés réseau du JDK pour plus d'informations</a>),
vous pouvez spécifier le nom d'un serveur proxy HTTP pour permettre à Jenkins
d'installer des plugins pour vous.
Notez que Jenkins utilise HTTPS pour communiquer avec le serveur de mise à jour pour télécharger les plugins.

<p>
La valeur placée ici sera positionnée dans la propriété système <tt>http.proxyHost</tt>.
Si ce champ est vide, la propriété ne sera pas positionnée; Jenkins tentera donc de se
connecter directement au site.

<p>
Si vous ne savez pas quelle valeur indiquer, regardez la configuration proxy de votre navigateur web.
</div>

core/src/main/resources/hudson/ProxyConfiguration/help-noProxyHost.html (Master)

Files

help-noProxyHost.html

MISSING

04.02.2013 00:16:05, no SCM information
<div> Specify host name patterns that shouldn't go through the proxy, one host per line. "" is the wild card host name (such as ".cloudbees.com" or "www*.jenkins-ci.org") </div>

core/src/main/resources/hudson/ProxyConfiguration/help-port_fr.html

Files

help-port.html

help-port_fr.html

CURRENT

04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
<div> This field works in conjunction with the proxy server field to specify the HTTP proxy port. </div>	<div> Ce champ est le numéro de port du proxy HTTP, utilisé avec le nom du serveur. </div>

core/src/main/resources/hudson/ProxyConfiguration/help-userName.html (Master)

Files

help-userName.html

MISSING

04.02.2013 00:16:05, no SCM information

<div>
This field works in conjunction with the proxy server field
to specify the username used to authenticate with the proxy.

<p>
If this proxy requires Microsofts <a href="http://en.wikipedia.org/wiki/NTLM">NTLM</a>
authentication scheme then the domain name can be encoded
within the username by prefixing the domain name followed
by a back-slash '\' before the username, e.g "ACME\John Doo".
</div>

core/src/main/resources/hudson/cli/Messages.properties (Master)

Files

MISSING

BuildCommand.CLICause.CannotBuildConfigNotSaved
11.09.2013 17:02:11, no SCM information
Cannot build {0} because its configuration has not been saved.

MISSING

BuildCommand.CLICause.CannotBuildDisabled
11.09.2013 17:02:11, no SCM information
Cannot build {0} because it is disabled.

MISSING

BuildCommand.CLICause.CannotBuildUnknownReasons
11.09.2013 17:02:11, no SCM information
Cannot build {0} for unknown reasons.

MISSING

BuildCommand.CLICause.ShortDescription
11.09.2013 17:02:11, no SCM information
Started by command line by {0}

MISSING

BuildCommand.ShortDescription
11.09.2013 17:02:11, no SCM information
Builds a job, and optionally waits until its completion.

MISSING

CopyJobCommand.ShortDescription
11.09.2013 17:02:11, no SCM information
Copies a job.

MISSING

CreateJobCommand.ShortDescription
11.09.2013 17:02:11, no SCM information
Creates a new job by reading stdin as a configuration XML file.

MISSING

CreateNodeCommand.ShortDescription
11.09.2013 17:02:11, no SCM information
Creates a new node by reading stdin as a XML configuration.

MISSING

DeleteBuildsCommand.ShortDescription
11.09.2013 17:02:11, no SCM information
Deletes build record(s).

MISSING

GetJobCommand.ShortDescription
11.09.2013 17:02:11, no SCM information
Dumps the job definition XML to stdout

MISSING

GetNodeCommand.ShortDescription
11.09.2013 17:02:11, no SCM information
Dumps the node definition XML to stdout

MISSING

GroovyCommand.ShortDescription
11.09.2013 17:02:11, no SCM information
Executes the specified Groovy script.

MISSING

GroovyshCommand.ShortDescription
11.09.2013 17:02:11, no SCM information
Runs an interactive groovy shell.

MISSING

HelpCommand.ShortDescription
11.09.2013 17:02:11, no SCM information
Lists all the available commands.

MISSING

InstallPluginCommand.DidYouMean
11.09.2013 17:02:11, no SCM information
{0} looks like a short plugin name. Did you mean ‘{1}’?

MISSING

InstallPluginCommand.InstallingFromUpdateCenter
11.09.2013 17:02:11, no SCM information
Installing {0} from update center

MISSING

InstallPluginCommand.InstallingPluginFromLocalFile
11.09.2013 17:02:11, no SCM information
Installing a plugin from local file: {0}

MISSING

InstallPluginCommand.InstallingPluginFromUrl
11.09.2013 17:02:11, no SCM information
Installing a plugin from {0}

MISSING

InstallPluginCommand.NoUpdateCenterDefined
11.09.2013 17:02:11, no SCM information
Note that no update center is defined in this Jenkins.

MISSING

InstallPluginCommand.NoUpdateDataRetrieved
11.09.2013 17:02:11, no SCM information
No update center data is retrieved yet from: {0}

MISSING

InstallPluginCommand.NotAValidSourceName
11.09.2013 17:02:11, no SCM information
{0} is neither a valid file, URL, nor a plugin artifact name in the update center

MISSING

InstallPluginCommand.ShortDescription
11.09.2013 17:02:11, no SCM information
Installs a plugin either from a file, an URL, or from update center.

MISSING

InstallToolCommand.ShortDescription
11.09.2013 17:02:11, no SCM information
Performs automatic tool installation, and print its location to stdout. Can be only called from inside a build.

MISSING

ListChangesCommand.ShortDescription
11.09.2013 17:02:11, no SCM information
Dumps the changelog for the specified build(s).

MISSING

ListJobsCommand.ShortDescription
11.09.2013 17:02:11, no SCM information
Lists all jobs in a specific view or item group.

MISSING

ListPluginsCommand.ShortDescription
11.09.2013 17:02:11, no SCM information
Outputs a list of installed plugins.

MISSING

LoginCommand.ShortDescription
11.09.2013 17:02:11, no SCM information
Saves the current credential to allow future commands to run without explicit credential information.

MISSING

LogoutCommand.ShortDescription
11.09.2013 17:02:11, no SCM information
Deletes the credential stored with the login command.

MISSING

MailCommand.ShortDescription
11.09.2013 17:02:11, no SCM information
Reads stdin and sends that out as an e-mail.

MISSING

SetBuildDescriptionCommand.ShortDescription
11.09.2013 17:02:11, no SCM information
Sets the description of a build.

MISSING

SetBuildDisplayNameCommand.ShortDescription
11.09.2013 17:02:11, no SCM information
Sets the displayName of a build

MISSING

SetBuildParameterCommand.ShortDescription
11.09.2013 17:02:11, no SCM information
Update/set the build parameter of the current build in progress

MISSING

SetBuildResultCommand.ShortDescription
11.09.2013 17:02:11, no SCM information
Sets the result of the current build. Works only if invoked from within a build.

MISSING

UpdateJobCommand.ShortDescription
11.09.2013 17:02:11, no SCM information
Updates the job definition XML from stdin. The opposite of the get-job command

MISSING

UpdateNodeCommand.ShortDescription
11.09.2013 17:02:11, no SCM information
Updates the node definition XML from stdin. The opposite of the get-node command

MISSING

VersionCommand.ShortDescription
11.09.2013 17:02:11, no SCM information
Outputs the current version.

MISSING

WhoAmICommand.ShortDescription
11.09.2013 17:02:11, no SCM information
Reports your credential and permissions

core/src/main/resources/hudson/diagnosis/HudsonHomeDiskUsageMonitor/index_fr.properties

Files

CURRENT

JENKINS_HOME is almost full
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
JENKINS_HOME is almost full	JENKINS_HOME est presque plein

CURRENT

blurb
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
<tt>JENKINS_HOME</tt> is almost full	<tt>JENKINS_HOME</tt> est presque plein

CURRENT

description.1
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Your <tt>JENKINS_HOME</tt> ({0}) is almost full. When this directory completely fills up, it'll wreak havoc because Jenkins can't store any more data.	Votre répertoire <tt>JENKINS_HOME</tt> ({0}) est presque plein. Quand il n''y aura plus d''espace disponible dans ce répertoire, Jenkins aura un comportement erratique, car il ne pourra plus stocker de données.

CURRENT

description.2
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
To prevent that problem, you should act now.	Pour éviter ce problème, vous devez agir maintenant.

CURRENT

solution.1
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Clean up some files from this partition to make more room.	Supprimez des fichiers sur cette partition afin de faire plus de place.

CURRENT

solution.2
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Move <tt>JENKINS_HOME</tt> to a bigger partition. See <a href="http://wiki.jenkins-ci.org/display/JENKINS/Administering+Jenkins">our Wiki</a> for how to do this.	Déplacez <tt>JENKINS_HOME</tt> sur une partition plus grande. Consultez <a href="http://wiki.jenkins-ci.org/display/JENKINS/Administering+Jenkins">notre Wiki</a> pour la démarche à suivre.

core/src/main/resources/hudson/diagnosis/HudsonHomeDiskUsageMonitor/message_fr.properties

Files

CURRENT

Dismiss
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Dismiss	J''ai compris

CURRENT

Tell me more
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Tell me more	Je veux en savoir plus

CURRENT

blurb
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Your Jenkins data directory "{0}" (AKA <tt>JENKINS_HOME</tt>) is almost full. You should act on it before it gets completely full.	Votre répertoire de données Jenkins "{0}" (c-à-d <tt>JENKINS_HOME</tt>) est presque plein. Vous devriez agir avant qu''il soit complètement rempli.

core/src/main/resources/hudson/diagnosis/MemoryUsageMonitor/index_fr.properties

Files

CURRENT

JVM Memory Usage
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
JVM Memory Usage	Utilisation mémoire par la JVM

CURRENT

Long
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Long	Longue

CURRENT

Medium
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Medium	Moyenne

CURRENT

Short
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Short	Courte

CURRENT

Timespan
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Timespan	Durée de vie

core/src/main/resources/hudson/diagnosis/Messages.properties (Master)

Files

MISSING

MemoryUsageMonitor.TOTAL
04.02.2013 00:16:05, no SCM information
Total

MISSING

MemoryUsageMonitor.USED
04.02.2013 00:16:05, no SCM information
Used

MISSING

OldDataMonitor.Description
04.02.2013 00:16:05, no SCM information
Scrub configuration files to remove remnants from old plugins and earlier versions.

MISSING

OldDataMonitor.DisplayName
04.02.2013 00:16:05, no SCM information
Manage Old Data

core/src/main/resources/hudson/diagnosis/NullIdDescriptorMonitor/message.jelly (Master)

Files

MISSING

blurb
04.02.2013 00:16:05, no SCM information
The following extensions have no ID value and therefore likely cause a problem. Please upgrade these plugins if they are not the latest, and if they are the latest, please file a bug so that we can fix them.

MISSING

problem
04.02.2013 00:16:05, no SCM information
Descriptor {0} from plugin {2} with display name {1}

core/src/main/resources/hudson/diagnosis/OldDataMonitor/manage_fr.properties

Files

manage.jelly

manage_fr.properties

MISSING

Resave data files with structure changes no newer than Jenkins
04.02.2013 00:16:05, no SCM information
Resave data files with structure changes no newer than Jenkins

MISSING

blurb.5
04.02.2013 00:16:05, no SCM information
(downgrade as far back as the selected version may still be possible)

CURRENT

Discard Unreadable Data
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Discard Unreadable Data	Supprimer les données non lisibles

CURRENT

Error
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Error	Erreur

CURRENT

Manage Old Data
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Manage Old Data	Gestion des données périmées

CURRENT

Name
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Name	Nom

CURRENT

No old data was found.
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
No old data was found.	Aucune donnée obsolète n''a été trouvée.

CURRENT

Type
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Type	Type

CURRENT

Unreadable Data
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Unreadable Data	Données illisibles

CURRENT

Upgrade
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Upgrade	Mettre à jour

CURRENT

Version
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Version	Version

CURRENT

blurb.1
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
When there are changes in how data is stored on disk, Jenkins uses the following strategy: data is migrated to the new structure when it is loaded, but the file is not resaved in the new format. This allows for downgrading Jenkins if needed. However, it can also leave data on disk in the old format indefinitely. The table below lists files containing such data, and the Jenkins version(s) where the data structure was changed.	Lorsqu''''''il y a des changements dans la façon de stocker les données sur le disque, Jenkins utilise la stratégie suivante: les données sont migrées vers la nouvelle structure lors de son chargement, mais le fichier n''''''est pas sauvé dans le nouveau format. Cela permet de ramener Jenkins à une version antérieure si besoin. Cependant, cela peut aussi laisser des données dans le vieux format indéfiniment. La table ci-dessous liste les fichiers contenant de telles données, ainsi que les versions de Jenkins où la structure de données a été modifiée.

CURRENT

blurb.2
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Sometimes errors occur while reading data (if a plugin adds some data and that plugin is later disabled, if migration code is not written for structure changes, or if Jenkins is downgraded after it has already written data not readable by the older version). These errors are logged, but the unreadable data is then skipped over, allowing Jenkins to startup and function properly.	Parfois des erreurs apparaissent lors de la lecture de données de configuration (si un plugin ajoute des données et que ce plugin est désactivé ultérieurement, si le code de migration ne prend pas en compte les changements de structure, ou si Jenkins est ramené en arrière après qu''''''il ait déjà écrit des données non lisibles par l''''''ancienne version). Ces erreurs sont loggées, mais les données non lisibles sont ensuite ignorées, permettant à Jenkins de démarrer et fonctionner correctement.

CURRENT

blurb.3
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
The form below may be used to resave these files in the current format. Doing so means a downgrade to a Jenkins release older than the selected version will not be able to read the data stored in the new format. Note that simply using Jenkins to create and configure jobs and run builds can save data that may not be readable by older Jenkins releases, even when this form is not used. Also if any unreadable data errors are reported in the right side of the table above, note that this data will be lost when the file is resaved.	Le formulaire ci-dessous peut être utilisé pour re-sauvegarder ces fichiers dans le format actuel. Cela implique qu''une réinstallation de Jenkins à une version antérieure à la version sélectionnée ne sera pas capable de lire les données stockées dans le nouveau format. Notez que simplement utiliser Jenkins pour créer et configurer des jobs et exécuter des builds peut sauver des données qui ne sont pas lisible par des versions plus vielles de Jenkins, même si ce formulaire est utilisé. De plus, si des erreurs concernant des données illisibles sont reportées sur la partie droite du tableau ci-dessus, notez que ces données seront perdues lorsque le fichier sera re-sauvegardé.

CURRENT

blurb.4
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Eventually the code supporting these data migrations may be removed. Compatibility will be retained for at least 150 releases since the structure change. Versions older than this are in bold above, and it is recommended to resave these files.	Le code supportant ces migrations de données pourra finalement être enlevé. La compatibilité sera conservée pendant au moins 150 releases depuis le changement de structure. Les versions plus anciennes que cela sont en gras ci-dessus, et il est recommandé de re-sauvegarder ces fichiers.

CURRENT

blurb.6
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
It is acceptable to leave unreadable data in these files, as Jenkins will safely ignore it. To avoid the log messages at Jenkins startup you can permanently delete the unreadable data by resaving these files using the button below.	Il est acceptable de laisser des données illisible dans ces fichiers, puisque Jenkins les ignorera. Pour éviter les messages de log au démarrage de Jenkins, vous pouvez supprimer définitivement les données illisibles en re-sauvant ces fichiers en utilisant le bouton ci-dessous.

core/src/main/resources/hudson/diagnosis/OldDataMonitor/message_fr.properties

Files

CURRENT

Dismiss
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Dismiss	Abandonner

CURRENT

Manage
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Manage	Gérer

CURRENT

You have data stored in an older format and/or unreadable data.
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
You have data stored in an older format and/or unreadable data.	Vous avez des données stockées dans un vieux format et/ou des données illisibles

core/src/main/resources/hudson/diagnosis/ReverseProxySetupMonitor/message_fr.properties

Files

CURRENT

Dismiss
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Dismiss	Rejeter

CURRENT

More Info
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
More Info	Plus d''informations

CURRENT

blurb
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
It appears that your reverse proxy set up is broken.	Il semble que votre configuration "reverse proxy" soit erronée

core/src/main/resources/hudson/diagnosis/TooManyJobsButNoView/message_fr.properties

Files

CURRENT

Create a view now
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Create a view now	Créer une vue maintenant

CURRENT

Dismiss
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Dismiss	J''ai compris

CURRENT

blurb
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
There appears to be a large number of jobs. Did you know that you can organize your jobs to different views? You can click '+' in the top page to create a new view any time.	Il semble y avoir un grand nombre de jobs. Saviez-vous que vous pouvez organiser vos jobs dans des vues séparées ? Pour cela, cliquez sur le ''+'' dans la page principale pour créer une nouvelle vue à tout moment.

core/src/main/resources/hudson/fsp/Messages_fr.properties

Files

OUTDATED

WorkspaceSnapshotSCM.IncorrectJobType
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:05, no SCM information
{0} isn’t a job that has a workspace.	Le job {0} n''a pas de workspace.
(old value)

OUTDATED

WorkspaceSnapshotSCM.NoBuild
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:05, no SCM information
There’s no qualifying build for the {0} permalink in {1}	Il n''a pas de build pour le permalink {0} dans {1}
(old value)

OUTDATED

WorkspaceSnapshotSCM.NoSuchJob
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:05, no SCM information
No such job ‘{0}’ exists. Perhaps you meant ‘{1}’?	Il n''y a pas de ''{0}''. Vouliez-vous dire ''{1}''?
(old value)

OUTDATED

WorkspaceSnapshotSCM.NoSuchPermalink
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:05, no SCM information
No such permalink ‘{0}’ exists for {1}	Il n''y a pas de permalink ''{0}'' pour {1}
(old value)

OUTDATED

WorkspaceSnapshotSCM.NoWorkspace
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:05, no SCM information
{0} {1} doesn’t have a workspace snapshot attached, probably because when the build was done, no other jobs needed its workspace snapshot. Please run another build in {0} to get the workspace snapshot taken.	{0} {1} n''a pas de snapshot de workspace attaché, probablement parce que quand le build s''est achevé, pas d''autre job n''avait besoin de son snapshot de workspace. Veuillez lancer un nouveau build dans {0} pour capturer le snapshot de workspace.
(old value)

core/src/main/resources/hudson/init/impl/Messages.properties (Master)

Files

MISSING

GroovyInitScript.init
04.02.2013 00:16:05, no SCM information
Executing user-defined init script

MISSING

InitialUserContent.init
04.02.2013 00:16:05, no SCM information
Preparing initial user content

core/src/main/resources/hudson/lifecycle/Messages_fr.properties

Files

MISSING

WindowsSlaveInstaller.ConfirmInstallation
01.08.2013 07:43:47, no SCM information
This will install a slave agent as a Windows service, so that a Jenkins slave starts automatically when the machine boots.

MISSING

WindowsSlaveInstaller.DotNetRequired
01.08.2013 07:43:47, no SCM information
.NET Framework 2.0 or later is required for this feature

MISSING

WindowsSlaveInstaller.InstallationSuccessful
01.08.2013 07:43:47, no SCM information
Installation was successful. Would you like to start the service now?

MISSING

WindowsSlaveInstaller.RootFsDoesntExist
01.08.2013 07:43:47, no SCM information
Slave root directory ‘{0}’ doesn’t exist

OUTDATED

WindowsInstallerLink.Description
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:05, no SCM information
Installs Jenkins as a Windows service to this system, so that Jenkins starts automatically when the machine boots.	Installe Jenkins comme un service Windows pour ce système, afin que Jenkins puisse se lancer automatiquement au démarrage de la machine.
(old value)

OUTDATED

WindowsInstallerLink.DisplayName
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:05, no SCM information
Install as Windows Service	Installer en tant que Service Windows
(old value)

core/src/main/resources/hudson/lifecycle/WindowsInstallerLink/_restart_fr.properties

Files

_restart.jelly

_restart_fr.properties

CURRENT

Please wait while Jenkins is restarting
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Please wait while Jenkins is restarting	Veuillez patienter pendant le redémarrage de Jenkins

CURRENT

blurb
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
You should be taken automatically to the new Jenkins in a few seconds. If for some reasons the service fails to start, check Windows event log for errors and consult <a href="http://wiki.jenkins-ci.org/display/JENKINS/Jenkins+windows+service+fails+to+start">online wiki page</a>.	Vous devriez être emmené automatiquement vers la nouvelle instance de Jenkins dans quelques secondes. Si par hasard le service ne parvient pas à se lancer, vérifiez les logs d''évènements Windows et consultez <a href="http://wiki.jenkins-ci.org/display/JENKINS/Jenkins+windows+service+fails+to+start">la page wiki</a>.

core/src/main/resources/hudson/lifecycle/WindowsInstallerLink/index_fr.properties

Files

CURRENT

Install
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Install	Installation

CURRENT

Install as Windows Service
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Install as Windows Service	Installer en tant que Service Windows

CURRENT

Installation Complete
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Installation Complete	Installation terminée

CURRENT

Installation Directory
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Installation Directory	Répertoire d''installation

CURRENT

Yes
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Yes	Oui

CURRENT

installBlurb
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Installing Jenkins as a Windows service allows you to start Jenkins as soon as the machine starts, and regardless of who is interactively using Jenkins.	L''installation de Jenkins en tant que service Windows vous permet de lancer Jenkins dés le démarrage de la machine, quel que soit l''utilisateur qui interagit avec Jenkins.

CURRENT

restartBlurb
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Installation is successfully completed. Do you want to stop this Jenkins and start a newly installed Windows service?	L''installation s''est achevée correctement. Voulez-vous arrêter cette instance de Jenkins et lancer ce nouveau service Windows?

core/src/main/resources/hudson/logging/LogRecorder/configure_fr.properties

Files

EMPTY

Logger
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:05, no SCM information
Logger	—

EMPTY

Loggers
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:05, no SCM information
Loggers	—

OUTDATED

List of loggers and the log levels to record
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:05, no SCM information
List of loggers and the log levels to record	Liste des loggers et des niveaux de log à enregistrer
(old value)

OUTDATED

Log level
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:05, no SCM information
Log level	Niveau de log
(old value)

OUTDATED

Name
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:05, no SCM information
Name	Nom
(old value)

OUTDATED

Save
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:05, no SCM information
Save	Enregistrer
(old value)

core/src/main/resources/hudson/logging/LogRecorder/delete_fr.properties

Files

CURRENT

Are you sure about deleting this log recorder?
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Are you sure about deleting this log recorder?	Etes-vous certain de vouloir effacer cet enregistreur de log?

CURRENT

Yes
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Yes	Oui

core/src/main/resources/hudson/logging/LogRecorder/sidepanel_fr.properties

Files

CURRENT

Back to Loggers
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Back to Loggers	Retourner aux loggers

CURRENT

Configure
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Configure	Configurer

CURRENT

Delete
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Delete	Supprimer

CURRENT

Log records
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Log records	Enregistrements de log

core/src/main/resources/hudson/logging/LogRecorderManager/all_fr.properties

Files

all.jelly

all_fr.properties

OUTDATED

Jenkins Log
23.07.2013 16:05:31, no SCM information	04.02.2013 00:16:05, no SCM information
Jenkins Log	Log Jenkins
(old value)

core/src/main/resources/hudson/logging/LogRecorderManager/feeds_fr.properties

Files

feeds.jelly

feeds_fr.properties

EMPTY

> SEVERE
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
> SEVERE	—

EMPTY

> WARNING
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
> WARNING	—

CURRENT

All
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
All	Tout

core/src/main/resources/hudson/logging/LogRecorderManager/index_fr.properties

Files

EMPTY

Log
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:05, no SCM information
Log	—

OUTDATED

Add new log recorder
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:05, no SCM information
Add new log recorder	Ajouter un nouvel enregistreur de log
(old value)

OUTDATED

All Jenkins Logs
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:05, no SCM information
All Jenkins Logs	Tous les logs Jenkins
(old value)

OUTDATED

Log Recorders
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:05, no SCM information
Log Recorders	Enregistreurs de log
(old value)

OUTDATED

Name
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:05, no SCM information
Name	Nom
(old value)

core/src/main/resources/hudson/logging/LogRecorderManager/levels_fr.properties

Files

levels.jelly

levels_fr.properties

MISSING

Adjust Levels
04.02.2013 00:16:05, no SCM information
Adjust Levels

MISSING

defaultLoggerMsg
04.02.2013 00:16:05, no SCM information
Logger with no name is the default logger. This level will be inherited by all loggers without a configured level.

CURRENT

Level
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Level	Niveau

CURRENT

Logger Configuration
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Logger Configuration	Configuration du logger

CURRENT

Name
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Name	Nom

CURRENT

Submit
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Submit	Envoyer

CURRENT

url
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
http://wiki.jenkins-ci.org//x/YYI5Ag	http://wiki.jenkins-ci.org/display/JENKINS/Logger+Configuration

core/src/main/resources/hudson/logging/LogRecorderManager/new_fr.properties

Files

new.jelly

new_fr.properties

CURRENT

Name
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Name	Nom

core/src/main/resources/hudson/logging/LogRecorderManager/sidepanel_fr.properties

Files

CURRENT

All Logs
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
All Logs	Tous les logs

CURRENT

Back to Dashboard
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Back to Dashboard	Retour au tableau de bord

CURRENT

Log Levels
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Log Levels	Niveaux des logs

CURRENT

Logger List
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Logger List	Liste des loggers

CURRENT

Manage Jenkins
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Manage Jenkins	Administrer Jenkins

CURRENT

New Log Recorder
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
New Log Recorder	Nouveau enregistreur de log

core/src/main/resources/hudson/logging/Messages.properties (Master)

Files

MISSING

LogRecorderManager.DisplayName
28.02.2013 15:26:35, no SCM information
log

MISSING

LogRecorderManager.init
28.02.2013 15:26:35, no SCM information
Initialing log recorders

core/src/main/resources/hudson/markup/RawHtmlMarkupFormatter/config_fr.properties

Files

CURRENT

blurb
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Treat the text as HTML and use it as is without any translation	Considérer le texte comme du HTML et l''utiliser sans le traduire

CURRENT

disableSyntaxHighlighting
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Disable syntax highlighting	Désactiver la coloration syntaxique

core/src/main/resources/hudson/matrix/DefaultMatrixExecutionStrategyImpl/config.groovy (Master)

Files

help-hasTouchStoneCombinationFilter.html

MISSING

Execute touchstone builds first
04.02.2013 00:16:05, no SCM information
Execute touchstone builds first

MISSING

Execution order of builds
04.02.2013 00:16:05, no SCM information
Execution order of builds

MISSING

Filter
04.02.2013 00:16:05, no SCM information
Filter

MISSING

Required result
04.02.2013 00:16:05, no SCM information
Required result

MISSING

Run each configuration sequentially
04.02.2013 00:16:05, no SCM information
Run each configuration sequentially

MISSING

Stable
04.02.2013 00:16:05, no SCM information
Stable

MISSING

Unstable
04.02.2013 00:16:05, no SCM information
Unstable

MISSING

required.result.description
29.04.2013 12:15:14, no SCM information
Execute the rest of the combinations only if the touchstone builds has (at least) the selected result.

core/src/main/resources/hudson/matrix/DefaultMatrixExecutionStrategyImpl/help-hasTouchStoneCombinationFilter.html (Master)

Files

help-runSequentially.html

MISSING

04.02.2013 00:16:05, no SCM information
<div> Use a touchstone build if you want to run a sanity check before building all the combinations. You can select a number of combinations using a combination filter. These will be built first. If the result satisfies the result condition, the rest of the combinations will be built. </div>

core/src/main/resources/hudson/matrix/DefaultMatrixExecutionStrategyImpl/help-runSequentially.html (Master)

Files

MISSING

04.02.2013 00:16:05, no SCM information
<div> With this option checked, Jenkins builds each configuration in a sequence. This can be useful if your configuration needs to access the shared resource like database, as well as to avoid crowding out other jobs. </div>

core/src/main/resources/hudson/matrix/LabelAxis/config.jelly (Master)

Files

MISSING

Individual nodes
04.02.2013 00:16:05, no SCM information
Individual nodes

MISSING

Labels
04.02.2013 00:16:05, no SCM information
Labels

MISSING

Name
04.02.2013 00:16:05, no SCM information
Name

MISSING

Node/Label
04.02.2013 00:16:05, no SCM information
Node/Label

core/src/main/resources/hudson/matrix/LabelAxis/help-labels_fr.html

Files

help-labels.html

help-labels_fr.html

OUTDATED

22.03.2013 09:10:52, no SCM information	04.02.2013 00:16:05, no SCM information
<div> Specify nodes where builds are performed. <ul> <li> If none is selected, Jenkins will choose an available node to perform a build (this is the same behavior as the free-style project when "tie this project to node" is not selected). This is useful when the project doesn't have a dependency on any particular node, as it allows Jenkins to utilize nodes in an optimal fashion. <li> If one is selected, Jenkins will always run the build on the specified node (if you select one from "individual nodes") or one of the nodes that belongs to the label (if you select one from "labels"). This is useful when the build is required to run on a specific computer, or a subset of computers. For example, maybe your build requires MacOS X. <li> If multiple values are selected, the configuration matrix will be expanded to include all of them, and builds will be performed on all of the selected nodes/labels. This is useful, for example, when you'd like to run tests on Windows, Linux, and Solaris. </ul> <br> During a build, the selected node name / label name for the given run is available as the "label" axis. See the help of "axes" below for more information about how to access the axis value. </div>	<div> Spécifiez ici les machines (noeuds) sur lesquelles les builds sont exécutés. <ul> <li> Si aucune n'est sélectionnée, Jenkins choisira une des machines disponibles pour l'exécution du build (ce comportement est le même pour les projets free-style quand l'option "attacher ce projet au noeud" n'est pas sélectionnée). C'est utile quand le projet n'a pas de dépendance avec une machine particulière; Jenkins peut en effet ainsi utiliser les noeuds de façon optimale. <li> Si une machine est sélectionnée, Jenkins lancera toujours le build dessus (si vous en sélectionnez une parmi les "noeuds spécifiques") ou sur une des machines qui appartiennent à un libellé (si vous en choisissez une dans "libellé"). C'est pratique quand le build doit tourner sur un ordinateur particulier ou sur un sous-ensemble d'ordinateurs. Par exemple, si votre build nécessite MacOS X. <li> Si de multiples valeurs sont sélectionnées, la matrice de configuration sera étendue de façon à les inclure toutes et les builds seront exécutés sur tous les noeuds ou libellés. Cela est utile, par exemple, quand vous souhaitez lancer des tests sur Windows, Linux et Solaris. </ul> <br> Au cours d'un build, le nom du noeud ou du libellé sélectionné pour un lancement donné est visible sous l'axe "libellé". Référez-vous à l'aide sur les "axes" ci-dessous pour plus d'informations sur l'accès à la valeur de l'axe. </div>
(old value)

core/src/main/resources/hudson/matrix/LabelAxis/help.html (Master)

Files

MISSING

04.02.2013 00:16:05, no SCM information
<div> This axis lets you run the same build on multiple slaves (by specifying those slaves either by their labels or their individual names.) This is useful for example to cross-compile your C projects on multiple platforms, testing your Java projects on different OSes, and so on. </div>

core/src/main/resources/hudson/matrix/LabelExpAxis/config.jelly (Master)

Files

MISSING

Label Expressions
04.02.2013 00:16:05, no SCM information
Label Expressions

MISSING

Name
04.02.2013 00:16:05, no SCM information
Name

core/src/main/resources/hudson/matrix/LabelExpAxis/help-labelExpr.html (Master)

Files

help-labelExpr.html

MISSING

04.02.2013 00:16:05, no SCM information
<div> This is similar to "Slave" axis, but you can use label expressions, not just plain label names. Each line represents one label expression (i.e. one value of this axis). </div>

core/src/main/resources/hudson/matrix/LabelExpAxis/help.html (Master)

Files

MISSING

04.02.2013 00:16:05, no SCM information
<div> This axis lets you run the same build on multiple slaves (much like the "slaves" axis), but this is more advanced in that it lets you use boolean expressions (such as <tt>foo&&bar</tt>) </div>

core/src/main/resources/hudson/matrix/MatrixBuild/ajaxMatrix_fr.properties

Files

ajaxMatrix.jelly

ajaxMatrix_fr.properties

CURRENT

Not run
29.04.2013 12:15:14, no SCM information	30.05.2013 20:09:20, no SCM information
Not run	Non lancé

core/src/main/resources/hudson/matrix/MatrixBuild/confirmDeleteAll.jelly (Master)

Files

confirmDeleteAll.jelly

MISSING

Are you sure about deleting the build and all configurations in this build?
04.02.2013 00:16:05, no SCM information
Are you sure about deleting the build and all configurations in this build?

MISSING

Warning
04.02.2013 00:16:05, no SCM information
Warning

MISSING

Yes
04.02.2013 00:16:05, no SCM information
Yes

MISSING

cannotMsg
29.04.2013 12:15:14, no SCM information
Cannot delete this build: {0}

core/src/main/resources/hudson/matrix/MatrixBuild/delete.jelly (Master)

Files

MISSING

Delete Build
29.04.2013 12:15:14, no SCM information
Delete Build

MISSING

Delete this build and all configurations in this build
29.04.2013 12:15:14, no SCM information
Delete this build and all configurations in this build

core/src/main/resources/hudson/matrix/MatrixProject/ajaxMatrix_fr.properties

Files

ajaxMatrix.jelly

ajaxMatrix_fr.properties

CURRENT

Not configured
29.04.2013 12:15:14, no SCM information	30.05.2013 20:09:20, no SCM information
Not configured	Non configuré

core/src/main/resources/hudson/matrix/MatrixProject/configure-entries_fr.properties

Files

help-childCustomWorkspace.html

MISSING

Add axis
21.06.2013 06:36:29, no SCM information
Add axis

MISSING

Directory
21.06.2013 06:36:29, no SCM information
Directory

MISSING

Directory for sub-builds
21.06.2013 06:36:29, no SCM information
Directory for sub-builds

MISSING

Display Name
21.06.2013 06:36:29, no SCM information
Display Name

MISSING

Execution Strategy
21.06.2013 06:36:29, no SCM information
Execution Strategy

MISSING

Use custom workspace
21.06.2013 06:36:29, no SCM information
Use custom workspace

OUTDATED

Advanced Project Options
21.06.2013 06:36:29, no SCM information	04.02.2013 00:16:05, no SCM information
Advanced Project Options	Options Avancées du projet
(old value)

OUTDATED

Combination Filter
21.06.2013 06:36:29, no SCM information	04.02.2013 00:16:05, no SCM information
Combination Filter	Filtre sur les combinaisons
(old value)

OUTDATED

Configuration Matrix
21.06.2013 06:36:29, no SCM information	04.02.2013 00:16:05, no SCM information
Configuration Matrix	Matrice de configuration
(old value)

OUTDATED

Filter
21.06.2013 06:36:29, no SCM information	04.02.2013 00:16:05, no SCM information
Filter	Filtre
(old value)

ORPHANED

Add more axis
	04.02.2013 00:16:05, no SCM information
	Ajouter des axes

ORPHANED

Axes
	04.02.2013 00:16:05, no SCM information
	—

ORPHANED

Build on multiple nodes
	04.02.2013 00:16:05, no SCM information
	Lancer les builds sur plusieurs noeuds

ORPHANED

Delete
	04.02.2013 00:16:05, no SCM information
	Supprimer

ORPHANED

Individual nodes
	04.02.2013 00:16:05, no SCM information
	Les noeuds

ORPHANED

Labels
	04.02.2013 00:16:05, no SCM information
	Etiquettes

ORPHANED

Name
	04.02.2013 00:16:05, no SCM information
	Nom

ORPHANED

Node
	04.02.2013 00:16:05, no SCM information
	Noeud

ORPHANED

Values
	04.02.2013 00:16:05, no SCM information
	Valeurs

core/src/main/resources/hudson/matrix/MatrixProject/help-childCustomWorkspace.html (Master)

Files

MISSING

28.02.2013 15:26:35, no SCM information

<div>
Override the workspace directory assigned to each configuration build.

<p>
By default, Jenkins runs each configuration build in its own unique directory
(this happens by appending the name and the value of the axes to the workspace of the overall matrix execution,
for example, <tt>/path/to/slaveroot/job/someMatrixJob/axis1/value1/axis2/value2/</tt>). Specifying this value
allows you to override this behaviour.

<p>
A common value used here is ".", indicating that all the configuration builds run on the same
directory as the overall matrix execution.

<p>
The path specified here can be either absolute or relative. If relative, it is resolved against the workspace
of the overall matrix execution. The value can also contains environment variable references. Environment variables
include all the axis values, so for example if you specify <tt>$FOO</tt> when you define
two axes FOO=[a,b] and BAR=[x,y], then FOO=a,BAR=x and FOO=a,BAR=y will build in somewhere like
<tt>/slaveroot/job/someMatrixJob/a/</tt> while FOO=b,BAR=x and FOO=b,BAR=y will build in
<tt>/slaveroot/job/someMatrixJob/b/</tt>. In this way, you can be selective about what subset
of configuration builds share the same workspace and what doesn't.

<p>
Environment variables include special tokens
<tt>${COMBINATION}</tt>, which expands to <tt>axis1/value1/axis2/value2/...</tt>, and
<tt>${SHORT_COMBINATION}</tt>, which expands to 8 character string unique to each configuration.

</div>

core/src/main/resources/hudson/matrix/MatrixProject/help-slaveAffinity.html (Master)

Files

help-slaveAffinity.html

MISSING

21.06.2013 06:36:29, no SCM information
<div> A matrix project needs to first execute what we call the "parent build", which checks out a copy of the source tree and capture its state to ensure all the individual builds will check out the same state. <p> If you need to control where this parent build runs, please use this option to specify its label/slave. </div>

core/src/main/resources/hudson/matrix/MatrixProject/index_fr.properties

Files

newJobDetail_fr.properties

MISSING

Project name
30.05.2013 20:09:20, no SCM information
Project name

OUTDATED

Latest Test Result
30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:05, no SCM information
Latest Test Result	Derniers résultats de test
(old value)

OUTDATED

Project
30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:05, no SCM information
Project	projet
(old value)

core/src/main/resources/hudson/matrix/MatrixProject/newJobDetail_fr.properties

Files

newJobDetail.jelly

CURRENT

body
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Suitable for projects that need a large number of different configurations, such as testing on multiple environments, platform-specific builds, etc.	Adapté aux projets qui nécessitent un grand nombre de configurations différentes, comme des environnements de test multiples, des binaires spécifiques à une plateforme, etc.

core/src/main/resources/hudson/matrix/Messages_fr.properties

Files

MISSING

JDKAxis.DisplayName
14.06.2013 07:43:03, no SCM information
JDK

MISSING

LabelAxis.DisplayName
14.06.2013 07:43:03, no SCM information
Slaves

MISSING

LabelExpAxis.DisplayName
14.06.2013 07:43:03, no SCM information
Label expression

MISSING

MatrixBuild.Completed
14.06.2013 07:43:03, no SCM information
{0} completed with result {1}

MISSING

MatrixBuild.depends_on_this
14.06.2013 07:43:03, no SCM information
{0} depends on this.

MISSING

MatrixProject.DuplicateAxisName
14.06.2013 07:43:03, no SCM information
Duplicate axis name

MISSING

MatrixProject.Pronoun
14.06.2013 07:43:03, no SCM information
Multi-configuration project

MISSING

MatrixRun.KeptBecauseOfParent
14.06.2013 07:43:03, no SCM information
Kept because {0} is kept

MISSING

TextArea.DisplayName
14.06.2013 07:43:03, no SCM information
User-defined Axis

OUTDATED

MatrixBuild.AppearsCancelled
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:05, no SCM information
{0} appears to be cancelled	{0} semble annulé
(old value)

OUTDATED

MatrixBuild.Cancelled
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:05, no SCM information
Cancelled {0}	{0} a été annulé
(old value)

OUTDATED

MatrixBuild.Interrupting
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:05, no SCM information
Interrupting {0}	{0} en cours d''interruption
(old value)

OUTDATED

MatrixBuild.Triggering
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:05, no SCM information
Triggering {0}	Lancement de {0}
(old value)

OUTDATED

MatrixConfiguration.Pronoun
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:05, no SCM information
Configuration	Configuration
(old value)

OUTDATED

MatrixProject.DisplayName
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:05, no SCM information
Build multi-configuration project	Construire un projet multi-configuration
(old value)

core/src/main/resources/hudson/matrix/TextAxis/config.jelly (Master)

Files

MISSING

Name
04.02.2013 00:16:05, no SCM information
Name

MISSING

Values
04.02.2013 00:16:05, no SCM information
Values

core/src/main/resources/hudson/matrix/TextAxis/help-valueString_fr.html

Files

help-valueString.html

help-valueString_fr.html

CURRENT

04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
<div> Values assigned to variables. Multiple values are separated by whitespace or newlines. Use shell quoting syntax for a value that contains whitespace. </div>	<div> Valeurs à assigner aux variables. Les valeurs multiples sont séparées par des espaces ou des retours à la ligne. </div>

core/src/main/resources/hudson/model/AbstractBuild/changes_fr.properties

Files

changes.jelly

changes_fr.properties

CURRENT

Changes
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Changes	Changements

core/src/main/resources/hudson/model/AbstractBuild/index_fr.properties

Files

MISSING

beingExecuted
04.02.2013 00:16:05, no SCM information
Build has been executing for {0}

EMPTY

log
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:05, no SCM information
log	—

OUTDATED

Build
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:05, no SCM information
Build	Compilation
(old value)

OUTDATED

Build Artifacts
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:05, no SCM information
Build Artifacts	Artefacts de la construction
(old value)

OUTDATED

Changes in dependency
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:05, no SCM information
Changes in dependency	Changements dans les dépendances
(old value)

OUTDATED

Downstream Builds
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:05, no SCM information
Downstream Builds	Builds en aval
(old value)

OUTDATED

Failed to determine
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:05, no SCM information
Failed to determine	Impossible à déterminer
(old value)

OUTDATED

Not yet determined
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:05, no SCM information
Not yet determined	Non encore déterminé
(old value)

OUTDATED

Took
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:05, no SCM information
Took	A pris
(old value)

OUTDATED

Upstream Builds
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:05, no SCM information
Upstream Builds	Builds en amont
(old value)

OUTDATED

detail
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:05, no SCM information
detail	détails
(old value)

OUTDATED

none
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:05, no SCM information
none	aucun
(old value)

OUTDATED

on
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:05, no SCM information
on	sur
(old value)

ORPHANED

Build number
	04.02.2013 00:16:05, no SCM information
	Numéro de build

ORPHANED

Permalinks
	04.02.2013 00:16:05, no SCM information
	Liens permanents

CURRENT

startedAgo
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Started {0} ago	Démarré il y a {0}

core/src/main/resources/hudson/model/AbstractBuild/sidepanel_fr.properties

Files

configure-common_fr.properties

ORPHANED

Back to Project
	04.02.2013 00:16:05, no SCM information
	Retour au projet

ORPHANED

Changes
	04.02.2013 00:16:05, no SCM information
	Changements

ORPHANED

Console Output
	04.02.2013 00:16:05, no SCM information
	Sortie console

ORPHANED

Status
	04.02.2013 00:16:05, no SCM information
	Statut

ORPHANED

raw
	04.02.2013 00:16:05, no SCM information
	brut

CURRENT

Next Build
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Next Build	Construction suivante

CURRENT

Previous Build
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Previous Build	Construction précédente

core/src/main/resources/hudson/model/AbstractBuild/tasks_fr.properties

Files

tasks.jelly

tasks_fr.properties

ORPHANED

Build Now
	04.02.2013 00:16:05, no SCM information
	Construire maintenant

ORPHANED

Build scheduled
	04.02.2013 00:16:05, no SCM information
	Construction planifiée

ORPHANED

Configure
	04.02.2013 00:16:05, no SCM information
	Configurer

CURRENT

Back to Project
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Back to Project	Retour au Projet

CURRENT

Changes
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Changes	Changements

CURRENT

Console Output
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Console Output	Sortie Console

CURRENT

Edit Build Information
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Edit Build Information	Informations du Build

CURRENT

Status
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Status	Statut

CURRENT

View Build Information
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
View Build Information	Voir les infos de compilation

CURRENT

View as plain text
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
View as plain text	Version texte simple

CURRENT

raw
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
raw	brut

core/src/main/resources/hudson/model/AbstractItem/configure-common_fr.properties

Files

configure-common.jelly

MISSING

Display Name
04.02.2013 00:16:05, no SCM information
Display Name

OUTDATED

JDK to be used for this project
21.06.2013 06:36:29, no SCM information	04.02.2013 00:16:05, no SCM information
JDK to be used for this project	Le JDK à utiliser pour ce projet
(old value)

ORPHANED

Execute concurrent builds if necessary
	04.02.2013 00:16:05, no SCM information
	Exécuter les builds en parallèle si nécessaire

ORPHANED

Node
	04.02.2013 00:16:05, no SCM information
	Noeud

ORPHANED

Tie this project to a node
	04.02.2013 00:16:05, no SCM information
	Associer ce projet à un noeud

CURRENT

Advanced Project Options
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Advanced Project Options	Options avancées du projet

CURRENT

default.value
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
(Default)	(Valeur par défaut)

core/src/main/resources/hudson/model/AbstractItem/delete_fr.properties

Files

help-concurrentBuild.html

OUTDATED

Yes
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:05, no SCM information
Yes	Oui
(old value)

OUTDATED

blurb
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:05, no SCM information
Are you sure about deleting the {0} ‘{1}’?	Etes vous sure de vouloir supprimer ce {0} "{1}"?
(old value)

ORPHANED

Are you sure about deleting the job?
	04.02.2013 00:16:05, no SCM information
	Etes-vous sûr de vouloir supprimer ce job?

core/src/main/resources/hudson/model/AbstractItem/help-concurrentBuild.html (Master)

Files

help-displayNameOrNull.html

MISSING

29.04.2013 12:15:14, no SCM information

<div>
If this option is checked, Jenkins will schedule and execute multiple builds concurrently (provided
that you have sufficient executors and incoming build requests.) This is useful on builds and test jobs that
take a long time, as each build will only contain a smaller number of changes, and the total turn-around
time decreases due to the shorter time a build request spends waiting for the previous build to complete.
It is also very useful with parameterized builds, whose individual executions are independent from each other.

<p>
For other kinds of jobs, allowing concurrent executions of multiple builds may be problematic,
for example if it assumes a monopoly on a certain resource, like database, or for jobs where you use Jenkins
as a cron replacement.

<p>
If you use a custom workspace and enable this option, all your builds will run on the same workspace,
thus unless a care is taken by your side, it'll likely to collide with each other.
Otherwise, even when they are run on the same node, Jenkins will use different workspaces to keep
them isolated.

<p>
When Jenkins creates different workspaces for isolation, Jenkins appends "@<I>num</I>" to the
workspace directory name, e.g. "@2". The separator "@" can be configured by setting the system property
"hudson.slaves.WorkspaceList" to the desired separator string on the Jenkins command line.
E.g. "-Dhudson.slaves.WorkspaceList=-" will use a dash as separator.
</div>

core/src/main/resources/hudson/model/AbstractItem/help-displayNameOrNull.html (Master)

Files

help-slaveAffinity_fr.html

MISSING

04.02.2013 00:16:05, no SCM information
<div> If set, the optional display name is shown for the project throughout the Jenkins web GUI. As it is for display purposes only, the display name is not required to be unique amongst projects. <br /> If the display name is not set, the Jenkins web GUI will default to showing the project name. </div>

core/src/main/resources/hudson/model/AbstractItem/help-slaveAffinity_fr.html

Files

help-slaveAffinity.html

CURRENT

21.06.2013 06:36:29, no SCM information

<div>
Sometimes a project can only be successfully built on a particular slave
(or master). If so, this option forces Jenkins to always build this project
on a specific computer.

If there is a group of machines that the job can be built on, you can specify
that label as the node to tie on, which will cause Jenkins to build the
project on any of the machines with that label.

<p>
Otherwise, uncheck the box so that Jenkins can schedule builds on available
nodes, which results in faster turn-around time.

<p>
This option is also useful when you'd like to make sure that a project can
be built on a particular node.
</div>

<div>
Parfois, un projet ne peut être construit que sur une machine-esclave
particulière. Dans ce cas, cette option force Jenkins à toujours
construire ce projet sur cette machine.

Si cette stratégie n'est pas nécessaire, décochez la case afin que
Jenkins puisse programmer des builds sur les machines les plus
disponibles, ce qui donnera un meilleur temps de réponse.

<p>
Cette option est également utile quand vous souhaitez vous assurer qu'un
projet peut réellement être construit sur un noeud (machine)
particulier.
</div>

core/src/main/resources/hudson/model/AbstractItem/noWorkspace_fr.properties

Files

noWorkspace.jelly

noWorkspace_fr.properties

MISSING

The workspace was wiped out and no build has been done since then.
04.02.2013 00:16:05, no SCM information
The workspace was wiped out and no build has been done since then.

CURRENT

A project won't have any workspace until at least one build is performed.
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
A project won't have any workspace until at least one build is performed.	Un projet n'a pas de workspace avant un premier build.

CURRENT

Error: no workspace
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Error: no workspace	Erreur: pas de workspace

CURRENT

The project was renamed recently and no build was done under the new name.
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
The project was renamed recently and no build was done under the new name.	Le projet a été renommé récemment et aucun build n'a été fait avec ce nouveau nom.

CURRENT

The slave this project has run on for the last time was removed.
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
The slave this project has run on for the last time was removed.	La machine esclave sur laquelle ce projet a été lancé pour la dernière fois a été retirée.

CURRENT

There's no workspace for this project. Possible reasons are:
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
There's no workspace for this project. Possible reasons are:	Il n'y a pas de workspace existant pour ce projet. Les raisons possibles sont:

CURRENT

li3
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
The workspace directory ({0}) is removed outside Jenkins.	Le répertoire workspace ({0}) a été déplacé hors de Jenkins.

CURRENT

text
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
<a href="{0}/{1}build">Run a build</a> to have Jenkins create a workspace.	<a href="{0}/{1}build">Lancer un build</a> afin de faire créer un workspace par Jenkins.

core/src/main/resources/hudson/model/AbstractModelObject/descriptionForm_fr.properties

Files

descriptionForm.jelly

descriptionForm_fr.properties

CURRENT

Submit
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Submit	Envoyer

core/src/main/resources/hudson/model/AbstractModelObject/editDescription_fr.properties

Files

editDescription.jelly

editDescription_fr.properties

CURRENT

Submit
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Submit	Envoyer

core/src/main/resources/hudson/model/AbstractModelObject/error_fr.properties

Files

error.jelly

error_fr.properties

CURRENT

Detail...
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Detail...	Détails...

CURRENT

Error
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Error	Erreur

core/src/main/resources/hudson/model/AbstractProject/changes_fr.properties

Files

changes.jelly

changes_fr.properties

CURRENT

Changes
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Changes	Modifications

CURRENT

changes.title
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
{0} Changes	Changements dans {0}

CURRENT

from.label
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
from #{0}	de #{0}

CURRENT

to.label
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
to #{0}	à #{0}

core/src/main/resources/hudson/model/AbstractProject/help-assignedLabelString.html (Master)

Files

help-assignedLabelString.html

MISSING

28.02.2013 15:26:35, no SCM information

<div>
If you want to always run this project on a specific node/slave, just specify its name.
This works well when you have a small number of nodes.

<p>
As the size of the cluster grows, it becomes useful not to tie projects to specific slaves,
as it hurts resource utilization when slaves may come and go. For such situation, assign labels
to slaves to classify their capabilities and characteristics, and specify a boolean expression
over those labels to decide where to run.

<h3>Valid Operators</h3>
<p>
The following operators are supported, in the order of precedence.
<dl>
<dt>(expr)</dt>
<dd>parenthesis</dd>

<dt>!expr</dt>
<dd>negation</dd>

<dt>expr&&expr</dt>
<dd>
and
</dd>

<dt>expr||expr</dt>
<dd>
or
</dd>

<dt>a -> b</dt>
<dd>
"implies" operator. Equivalent to <tt>!a|b</tt>.
For example, <tt>windows->x64</tt> could be thought of as "if run on a Windows slave,
that slave must be 64bit." It still allows Jenkins to run this build on linux.
</dd>

<dt>a <-> b</dt>
<dd>
"if and only if" operator. Equivalent to <tt>a&&b || !a&&!b</tt>.
For example, <tt>windows<->sfbay</tt> could be thought of as "if run on a Windows slave,
that slave must be in the SF bay area, but if not on Windows, it must not be in the bay area."
</dd>
</dl>
<p>
All operators are left-associative (i.e., a->b->c <-> (a->b)->c )
An expression can contain whitespace for better readability, and it'll be ignored.

<p>
Label names or slave names can be quoted if they contain unsafe characters. For example,
<tt>"jenkins-solaris (Solaris)" || "Windows 2008"</tt>
</div>

core/src/main/resources/hudson/model/AbstractProject/main_fr.properties

Files

makeDisabled_fr.properties

MISSING

Latest Aggregated Test Result
20.09.2013 10:05:40, no SCM information
Latest Aggregated Test Result

OUTDATED

Last Successful Artifacts
20.09.2013 10:05:40, no SCM information	04.02.2013 00:16:05, no SCM information
Last Successful Artifacts	Derniers artefacts obtenus avec succès
(old value)

OUTDATED

Latest Test Result
20.09.2013 10:05:40, no SCM information	04.02.2013 00:16:05, no SCM information
Latest Test Result	Derniers résultats des tests
(old value)

OUTDATED

Recent Changes
20.09.2013 10:05:40, no SCM information	04.02.2013 00:16:05, no SCM information
Recent Changes	Changements récents
(old value)

OUTDATED

Workspace
20.09.2013 10:05:40, no SCM information	04.02.2013 00:16:05, no SCM information
Workspace	Espace de travail
(old value)

ORPHANED

Latest Console output
	04.02.2013 00:16:05, no SCM information
	Dernière sortie de la console

core/src/main/resources/hudson/model/AbstractProject/makeDisabled_fr.properties

Files

makeDisabled.jelly

CURRENT

Disable Project
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Disable Project	Désactiver le Projet

CURRENT

Enable
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
Enable	Activer

CURRENT

This project is currently disabled
04.02.2013 00:16:05, no SCM information	04.02.2013 00:16:05, no SCM information
This project is currently disabled	Ce projet est actuellement désactivé

core/src/main/resources/hudson/model/AbstractProject/requirePOST.jelly (Master)

Files

requirePOST.jelly

MISSING

Form post required
19.02.2013 07:05:52, no SCM information
Form post required

MISSING

Proceed
19.02.2013 07:05:52, no SCM information
Proceed

MISSING

use_post
19.02.2013 07:05:52, no SCM information
You must use POST method to trigger builds. (From scripts you may instead pass a per-project authentication token, or authenticate with your API token.) If you see this page, it may be because a plugin offered a GET link; file a bug report for that plugin.

core/src/main/resources/hudson/model/AbstractProject/sidepanel_fr.properties

Files

svn-password_fr.properties

MISSING

View Configuration
14.06.2013 07:43:03, no SCM information
View Configuration

MISSING

delete.confirm
29.04.2013 12:15:14, no SCM information
Are you sure about deleting the {0} ‘{1}’?

OUTDATED

Back to Dashboard
14.06.2013 07:43:03, no SCM information	29.04.2013 12:15:14, no SCM information
Back to Dashboard	Retour au tableau de bord
(old value)

OUTDATED

Build scheduled
14.06.2013 07:43:03, no SCM information	29.04.2013 12:15:14, no SCM information
Build scheduled	Construction programmée
(old value)

OUTDATED

Changes
14.06.2013 07:43:03, no SCM information	29.04.2013 12:15:14, no SCM information
Changes	Modifications
(old value)

OUTDATED

Configure
14.06.2013 07:43:03, no SCM information	29.04.2013 12:15:14, no SCM information
Configure	Configurer
(old value)

OUTDATED

Status
14.06.2013 07:43:03, no SCM information	29.04.2013 12:15:14, no SCM information
Status	État
(old value)

OUTDATED

Workspace
14.06.2013 07:43:03, no SCM information	29.04.2013 12:15:14, no SCM information
Workspace	Espace de travail
(old value)

CURRENT

Wipe Out Workspace
29.04.2013 12:15:14, no SCM information	29.04.2013 12:15:14, no SCM information
Wipe Out Current Workspace	Effacer le répertoire de travail courant

CURRENT

delete
29.04.2013 12:15:14, no SCM information	29.04.2013 12:15:14, no SCM information
Delete {0}	Supprimer ce {0}

CURRENT

wipe.out.confirm
29.04.2013 12:15:14, no SCM information	29.04.2013 12:15:14, no SCM information
Are you sure about wiping out the workspace?	Voulez-vous vraiment effacer le répertoire de travail?

core/src/main/resources/hudson/model/AbstractProject/svn-password_fr.properties

Files

svn-password.jelly

OUTDATED

alternative.introduction
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
A preferable approach is to do the following steps:	Une meilleure approche est de suivre les étapes suivantes:
(old value)

OUTDATED

explanation.introduction
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
While subversion allows you to specify the ‘--password’ option explicitly in the command line, this is generally not desirable when you are using Jenkins, because:	Bien que Subversion vous permette de passer l''option '--password' en clair dans la ligne de commande, ça n''est en général pas souhaitable quand vous utilisez Jenkins. En effet:
(old value)

OUTDATED

final.words
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
Note that this approach still doesn’t really make your password secure, it just makes it a bit harder to read.	Notez bien que cette approche ne rend pas votre mot de passe complètement sécurisé; il devient simplement un peu plus difficile à lire.
(old value)

OUTDATED

reason.1
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
People can read your password by using <tt>pargs</tt>.	On peut lire votre mot de passe en utilisant <tt>pargs</tt>;
(old value)

OUTDATED

reason.2
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
Password will be stored in a clear text in Jenkins.	Votre mot de passe sera enregistré en clair dans Jenkins
(old value)

OUTDATED

step.1
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
Logon to the server that runs Jenkins, by using the same user account Jenkins uses.	Se logguer sur le serveur qui fait tourner Jenkins, en utilisant le même compte utilisateur que Jenkins;
(old value)

OUTDATED

step.2
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
Manually run <tt>svn co ...</tt>	Lancer manuellement <tt>svn co ...</tt>;
(old value)

OUTDATED

step.3
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
Subversion asks you the password interactively. Type in the password.	Subversion vous demande votre mot de passe de façon intéractive. Tapez votre mot de passe;
(old value)

OUTDATED

step.4
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
Subversion stores it in its authentication cache, and for successive <tt>svn co ...</tt> it will use the password stored in the cache.	Subversion le stocke dans son cache d''authentification; pour les demandes <tt>svn co ...</tt> futures, il utilisera le mot de passe de son cache.
(old value)

CURRENT

How to set Subversion password?
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
How to set Subversion password?	Comment positionner le mot de passe Subversion?

core/src/main/resources/hudson/model/AbstractProject/wipeOutWorkspaceBlocked_fr.properties

Files

wipeOutWorkspaceBlocked.jelly

wipeOutWorkspaceBlocked_fr.properties

MISSING

Error: Wipe Out Workspace blocked by SCM
04.02.2013 00:16:06, no SCM information
Error: Wipe Out Workspace blocked by SCM

MISSING

The SCM for this project has blocked this attempt to wipe out the project's workspace.
04.02.2013 00:16:06, no SCM information
The SCM for this project has blocked this attempt to wipe out the project's workspace.

ORPHANED

Error
	04.02.2013 00:16:06, no SCM information
	Wipe Out Workspace blocked by SCM=Erreur : La suppression de l''''espace de travail a été bloquée par le SCM

ORPHANED

The SCM for this project has blocked this attempt to wipe out the project''s workspace.
	04.02.2013 00:16:06, no SCM information
	Le SCM de ce projet a bloqué la tentative de suppression de l''''espace de travail de ce projet

core/src/main/resources/hudson/model/AgentSlave/config_fr.properties

Files

CURRENT

launch command
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
launch command	commande de lancement

core/src/main/resources/hudson/model/AllView/newViewDetail_fr.properties

Files

newViewDetail_fr.properties

CURRENT

blurb
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
This view shows all the jobs on Jenkins.	Cette vue montre montre tous les jobs Jenkins.

core/src/main/resources/hudson/model/AllView/noJob_fr.properties

Files

noJob.jelly

noJob_fr.properties

OUTDATED

login
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
<a href="{0}/{1}?from={2}">Log in</a> to create new jobs.	Vous devez vous <a href="{0}/{1}?from={2}">identifier</a> pour créer des nouveaux jobs.
(old value)

OUTDATED

newJob
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
Please <a href="newJob">create new jobs</a> to get started.	Veuillez <a href="newJob">créez un nouveau job</a> pour démarrer.
(old value)

OUTDATED

signup
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
If you don’t already have an account, you can <a href="signup">sign-up</a> now.	Si vous n''avez pas déjà un compte, vous pouvez vous<a href="signup">enregistrer</a>.
(old value)

CURRENT

Welcome to Jenkins!
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Welcome to Jenkins!	Bienvenue sur Jenkins !

core/src/main/resources/hudson/model/BooleanParameterDefinition/config_fr.properties

Files

CURRENT

Default Value
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Default Value	Valeur par défaut

CURRENT

Description
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Description	Description

CURRENT

Name
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Name	Nom

core/src/main/resources/hudson/model/BuildAuthorizationToken/config_fr.properties

Files

description_fr.properties

MISSING

or
04.02.2013 00:16:06, no SCM information
or

CURRENT

Authentication Token
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Authentication Token	Jeton d''authentification

CURRENT

Optionally append `&cause=Cause+Text` to provide text that will be included in the recorded build cause.
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Optionally append <tt>&cause=Cause+Text</tt> to provide text that will be included in the recorded build cause.	Optionnellement, ajoute le suffixe <tt>&cause=Cause+Text</tt> pour fournir du texte qui sera inclu dans la cause enregistrée pour le build.

CURRENT

Trigger builds remotely
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Trigger builds remotely	Déclencher les builds à distance

CURRENT

Use the following URL to trigger build remotely:
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Use the following URL to trigger build remotely:	Utilisez l''URL qui suit pour lancer un build à distance:

CURRENT

e.g., from scripts
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
e.g., from scripts	Par exemple, à partir de scripts

core/src/main/resources/hudson/model/Cause/UpstreamCause/description_fr.properties

Files

description.jelly

MISSING

caused_by
04.02.2013 00:16:06, no SCM information
originally caused by:

CURRENT

started_by_project
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Started by upstream project <a href="{3}/{2}">{0}</a> build number <a href="{3}/{2}{1}/">{1}</a>	Lancé par le projet amont <a href="{3}/{2}">{0}</a> avec le numéro de build <a href="{3}/{2}{1}/">{1}</a>

core/src/main/resources/hudson/model/Cause/UserCause/description_fr.properties

Files

description.jelly

description_fr.properties

CURRENT

started_by_user
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Started by user <a href="{1}/user/{0}">{0}</a>	Lancé par l''utilisateur <a href="{1}/user/{0}">{0}</a>

core/src/main/resources/hudson/model/Cause/UserIdCause/description_fr.properties

Files

description.jelly

description_fr.properties

CURRENT

started_by_anonymous
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Started by anonymous user	Lancé par l''usager anonyme

CURRENT

started_by_user
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Started by user <a href="{2}/user/{0}">{1}</a>	Lancé par l''utilisateur <a href="{2}/user/{0}">{1}</a>

core/src/main/resources/hudson/model/CauseAction/summary_fr.properties

Files

summary.jelly

summary_fr.properties

CURRENT

Ntimes
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
({0} times)	({0} fois)

core/src/main/resources/hudson/model/ChoiceParameterDefinition/config_fr.properties

Files

CURRENT

Choices
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Choices	Choix

CURRENT

Description
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Description	Description

CURRENT

Name
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Name	Nom

core/src/main/resources/hudson/model/Computer/_script_fr.properties

Files

_script.jelly

_script_fr.properties

CURRENT

This execution happens in the slave agent JVM.
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
This execution happens in the slave agent JVM.	Cette exécution a lieu sur la JVM de l''agent Jenkins sur l''esclave.

core/src/main/resources/hudson/model/Computer/builds_fr.properties

Files

builds.jelly

builds_fr.properties

CURRENT

title
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Build History on {0}	Historique du build de {0}

core/src/main/resources/hudson/model/Computer/configure_fr.properties

Files

MISSING

title
04.02.2013 00:16:06, no SCM information
{0} Configuration

ORPHANED

Name is mandatory
	04.02.2013 00:16:06, no SCM information
	Le nom est obligatoire

CURRENT

Name
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Name	Nom

CURRENT

Save
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Save	Enregistrer

core/src/main/resources/hudson/model/Computer/delete_fr.properties

Files

CURRENT

Are you sure about deleting the slave?
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Are you sure about deleting the slave?	Etes-vous sûr de vouloir supprimer cet esclave?

CURRENT

Yes
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Yes	Oui

core/src/main/resources/hudson/model/Computer/index_fr.properties

Files

MISSING

Created by
29.04.2013 12:15:14, no SCM information
Created by

MISSING

anonymous user
29.04.2013 12:15:14, no SCM information
anonymous user

MISSING

submit.updateOfflineCause
01.08.2013 07:43:47, no SCM information
Update offline reason

OUTDATED

Labels:
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:06, no SCM information
Labels:	Libellés :
(old value)

OUTDATED

None
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:06, no SCM information
None	Aucun
(old value)

OUTDATED

submit.not.temporarilyOffline
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
Mark this node temporarily offline	Marquer ce nœud comme temporairement hors ligne
(old value)

OUTDATED

submit.temporarilyOffline
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
Bring this node back online	Ce noeud est de nouveau en ligne
(old value)

OUTDATED

title.no_manual_launch
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
This node’s availability policy is: “{0}” Currently, this mandates that the node be offline.	Ce noeud a une stratégie de disponiblité de type "{0}". Actuellement, cela oblige le noeud a être déconnecté.
(old value)

OUTDATED

title.projects_tied_on
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
Projects tied to {0}	Projets rattachés à {0}
(old value)

core/src/main/resources/hudson/model/Computer/markOffline.jelly (Master)

Files

markOffline.jelly

MISSING

blurb
04.02.2013 00:16:06, no SCM information
You can optionally explain why you are taking this node offline, so that others can see why:

MISSING

submit
04.02.2013 00:16:06, no SCM information
Mark this node temporarily offline

MISSING

title
04.02.2013 00:16:06, no SCM information
Taking {0} Offline

core/src/main/resources/hudson/model/Computer/setOfflineCause.jelly (Master)

Files

setOfflineCause.jelly

MISSING

blurb
04.02.2013 00:16:06, no SCM information
You can set or update the reason why this node offline, so that others can see why:

MISSING

submit
04.02.2013 00:16:06, no SCM information
Update reason

MISSING

title
04.02.2013 00:16:06, no SCM information
Set {0} Offline Reason

core/src/main/resources/hudson/model/Computer/sidepanel_fr.properties

Files

CURRENT

Back to List
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Back to List	Retour à la liste

CURRENT

Build History
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Build History	Historique des builds

CURRENT

Configure
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Configure	Configurer

CURRENT

Delete Slave
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Delete Slave	Supprimer l''esclave

CURRENT

Load Statistics
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Load Statistics	Statistiques d''utilisation

CURRENT

Script Console
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Script Console	Console de script

CURRENT

Status
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Status	Statut

core/src/main/resources/hudson/model/ComputerSet/_new_fr.properties

Files

_new.jelly

_new_fr.properties

CURRENT

Name
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Name	Nom

CURRENT

Name is mandatory
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Name is mandatory	Le nom est obligatoire

CURRENT

Save
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Save	Enregistrer

core/src/main/resources/hudson/model/ComputerSet/configure_fr.properties

Files

MISSING

Node Monitoring Configuration
04.02.2013 00:16:06, no SCM information
Node Monitoring Configuration

MISSING

OK
04.02.2013 00:16:06, no SCM information
OK

CURRENT

Preventive Node Monitoring
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Preventive Node Monitoring	Surveillance préventive des nœuds

core/src/main/resources/hudson/model/ComputerSet/index_fr.properties

Files

MISSING

Data obtained
29.04.2013 12:15:14, no SCM information
Data obtained

MISSING

Nodes
29.04.2013 12:15:14, no SCM information
Nodes

OUTDATED

Configure
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:06, no SCM information
Configure	Configurer
(old value)

OUTDATED

Name
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:06, no SCM information
Name	Nom
(old value)

OUTDATED

Refresh status
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:06, no SCM information
Refresh status	Rafraîchir le statut
(old value)

core/src/main/resources/hudson/model/ComputerSet/new_fr.properties

Files

new.jelly

new_fr.properties

CURRENT

Copy Existing Node
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Copy Existing Node	Copier un noeud existant

CURRENT

Node name
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Node name	Nom du noeud

core/src/main/resources/hudson/model/ComputerSet/sidepanel_fr.properties

Files

CURRENT

Back to Dashboard
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Back to Dashboard	Retour au tableau de bord

CURRENT

Configure
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Configure	Configurer

CURRENT

Manage Jenkins
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Manage Jenkins	Administrer Jenkins

CURRENT

New Node
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
New Node	Nouveau nœud

core/src/main/resources/hudson/model/DirectoryBrowserSupport/dir_fr.properties

Files

dir.jelly

dir_fr.properties

CURRENT

No files in directory
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
No files in directory	Aucun fichier dans ce répertoire

CURRENT

all files in zip
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
all files in zip	Tous les fichiers dans un zip

CURRENT

view
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
view	vue

core/src/main/resources/hudson/model/EnvironmentContributor/EnvVarsHtml/index_fr.properties

Files

index.groovy

ORPHANED

The following variables are available to shell scripts
	04.02.2013 00:16:06, no SCM information
	Les variables suivantes sont mises à disposition des scripts shell

CURRENT

Available Environmental Variables
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Available Environmental Variables	Variables d'environnement disponibles

core/src/main/resources/hudson/model/Executor/causeOfDeath.jelly (Master)

Files

causeOfDeath.jelly

MISSING

Back
04.02.2013 00:16:06, no SCM information
Back

MISSING

Restart this thread
04.02.2013 00:16:06, no SCM information
Restart this thread

MISSING

Thread has died
04.02.2013 00:16:06, no SCM information
Thread has died

MISSING

Thread is still alive
04.02.2013 00:16:06, no SCM information
Thread is still alive

MISSING

more info
04.02.2013 00:16:06, no SCM information
more info

core/src/main/resources/hudson/model/FileParameterDefinition/config_fr.properties

Files

CURRENT

Description
04.02.2013 00:16:06, no SCM information	30.05.2013 20:09:20, no SCM information
Description	Description

CURRENT

File location
04.02.2013 00:16:06, no SCM information	30.05.2013 20:09:20, no SCM information
File location	Emplacement du fichier

core/src/main/resources/hudson/model/FileParameterValue/value_fr.properties

Files

value.jelly

value_fr.properties

CURRENT

view
04.02.2013 00:16:06, no SCM information	30.05.2013 20:09:20, no SCM information
view	vues

core/src/main/resources/hudson/model/Fingerprint/index_fr.properties

Files

newJobDetail_fr.properties

OUTDATED

Back to Dashboard
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:06, no SCM information
Back to Dashboard	Retour au tableau de bord
(old value)

OUTDATED

This file has been used in the following places
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:06, no SCM information
This file has been used in the following places	Ce fichier a été utilisé aux endroits suivants
(old value)

OUTDATED

This file has not been used anywhere else.
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:06, no SCM information
This file has not been used anywhere else.	Ce fichier n''a été utilisé nulle part ailleurs.
(old value)

OUTDATED

Usage
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:06, no SCM information
Usage	Utilisation
(old value)

OUTDATED

outside Jenkins
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:06, no SCM information
outside Jenkins	hors Jenkins
(old value)

CURRENT

introduced
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Introduced {0} ago	Introduit il y a {0}

core/src/main/resources/hudson/model/FreeStyleProject/newJobDetail_fr.properties

Files

newJobDetail.jelly

CURRENT

body
04.02.2013 00:16:06, no SCM information	30.05.2013 20:09:20, no SCM information
This is the central feature of Jenkins. Jenkins will build your project, combining any SCM with any build system, and this can be even used for something other than software build.	Ceci est la fonction principale de Jenkins qui sert à builder (construire) votre projet. <br> Vous pouvez intégrer tous les outils de gestion de version avec tous les systèmes de build. <br> Il est même possible d''utiliser Jenkins pour tout autre chose qu''un build logiciel.

core/src/main/resources/hudson/model/JDK/config_fr.properties

Files

buildTimeTrend_fr.properties

CURRENT

Name
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Name	Nom

core/src/main/resources/hudson/model/Job/buildTimeTrend_fr.properties

Files

buildTimeTrend.jelly

CURRENT

Build
29.04.2013 12:15:14, no SCM information	30.05.2013 20:09:20, no SCM information
Build	Build

CURRENT

Build Time Trend
29.04.2013 12:15:14, no SCM information	30.05.2013 20:09:20, no SCM information
Build Time Trend	Tendance des temps des builds

CURRENT

Duration
29.04.2013 12:15:14, no SCM information	30.05.2013 20:09:20, no SCM information
Duration	Durée

CURRENT

More than 1 builds are needed for the trend report.
29.04.2013 12:15:14, no SCM information	30.05.2013 20:09:20, no SCM information
More than 1 builds are needed for the trend report.	Plus de 1 build est nécessaire pour le rapport de tendance.

CURRENT

Slave
29.04.2013 12:15:14, no SCM information	30.05.2013 20:09:20, no SCM information
Slave	Esclave

CURRENT

Timeline
29.04.2013 12:15:14, no SCM information	30.05.2013 20:09:20, no SCM information
Timeline	Chronologie

CURRENT

title
04.02.2013 00:16:06, no SCM information	30.05.2013 20:09:20, no SCM information
{0} Build time trend	{0} Courbe de tendance de la durée du build

core/src/main/resources/hudson/model/Job/configure_fr.properties

Files

CURRENT

Description
19.02.2013 07:05:52, no SCM information	30.05.2013 20:09:20, no SCM information
Description	Description

CURRENT

Discard Old Builds
19.02.2013 07:05:52, no SCM information	30.05.2013 20:09:20, no SCM information
Discard Old Builds	Supprimer les anciens builds

CURRENT

LOADING
19.02.2013 07:05:52, no SCM information	30.05.2013 20:09:20, no SCM information
LOADING	CHARGEMENT

CURRENT

Save
19.02.2013 07:05:52, no SCM information	30.05.2013 20:09:20, no SCM information
Save	Sauver

CURRENT

Strategy
19.02.2013 07:05:52, no SCM information	30.05.2013 20:09:20, no SCM information
Strategy	Stratégie

CURRENT

name
04.02.2013 00:16:06, no SCM information	30.05.2013 20:09:20, no SCM information
{0} name	Nom du {0}

core/src/main/resources/hudson/model/Job/index_fr.properties

Files

OUTDATED

Project name
20.09.2013 10:05:40, no SCM information	30.05.2013 20:09:20, no SCM information
Project name	Nom du projet
(old value)

core/src/main/resources/hudson/model/Job/permalinks_fr.properties

Files

permalinks.jelly

permalinks_fr.properties

CURRENT

Permalinks
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Permalinks	Liens permanents

core/src/main/resources/hudson/model/Job/rename_fr.properties

Files

rename.jelly

rename_fr.properties

MISSING

configWasSaved
12.07.2013 12:08:38, no SCM information
All other configuration options were saved.

MISSING

newNameInUse
12.07.2013 12:08:38, no SCM information
The name {0} is already in use.

MISSING

noRenameWhileBuilding
12.07.2013 12:08:38, no SCM information
Unable to rename a job while it is building.

OUTDATED

Yes
12.07.2013 12:08:38, no SCM information	04.02.2013 00:16:06, no SCM information
Yes	Oui
(old value)

OUTDATED

description
12.07.2013 12:08:38, no SCM information	04.02.2013 00:16:06, no SCM information
Are you sure about renaming {0} to {1}?	Voulez-vous vraiment renommer {0} en {1}?
(old value)

ORPHANED

No
	04.02.2013 00:16:06, no SCM information
	Non

core/src/main/resources/hudson/model/Label/index_fr.properties

Files

OUTDATED

Nodes:
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:06, no SCM information
Nodes:	Noeuds:
(old value)

OUTDATED

None
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:06, no SCM information
None	Aucun
(old value)

OUTDATED

Projects
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:06, no SCM information
Projects	Projets
(old value)

core/src/main/resources/hudson/model/Label/sidepanel_fr.properties

Files

CURRENT

Back to Dashboard
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Back to Dashboard	Retour au tableau de bord

CURRENT

Load Statistics
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Load Statistics	Statistiques de l''utilisation du système

CURRENT

Overview
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Overview	Vue générale

core/src/main/resources/hudson/model/ListView/configure-entries_fr.properties

Files

MISSING

Add Job Filter
01.08.2013 07:43:47, no SCM information
Add Job Filter

MISSING

Recurse in subfolders
01.08.2013 07:43:47, no SCM information
Recurse in subfolders

OUTDATED

Add column
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
Add column	Ajouter une colonne
(old value)

OUTDATED

All selected jobs
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
All selected jobs	Toutes les tâches sélectionnées
(old value)

OUTDATED

Columns
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
Columns	Colonnes
(old value)

OUTDATED

Disabled jobs only
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
Disabled jobs only	Uniquement les tâches désactivées
(old value)

OUTDATED

Enabled jobs only
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
Enabled jobs only	Uniquement les tâches activées
(old value)

OUTDATED

Job Filters
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
Job Filters	Filtres pour les tâches
(old value)

OUTDATED

Jobs
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
Jobs	Tâches
(old value)

OUTDATED

Regular expression
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
Regular expression	Expression régulière
(old value)

OUTDATED

Status Filter
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
Status Filter	État du filtre
(old value)

OUTDATED

Use a regular expression to include jobs into the view
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
Use a regular expression to include jobs into the view	Utilisez une expression régulière pour inclure les jobs dans la vue
(old value)

core/src/main/resources/hudson/model/ListView/newViewDetail_fr.properties

Files

newViewDetail_fr.properties

CURRENT

blurb
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Shows items in a simple list format. You can choose which jobs are to be displayed in which view.	Montre les jobs dans une simple liste. Vous pouvez choisir les jobs à afficher dans chaque vue.

core/src/main/resources/hudson/model/LoadStatistics/main_fr.properties

Files

CURRENT

Load statistics graph
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Load statistics graph	Graphique des statistiques de charge

CURRENT

Long
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Long	Longue

CURRENT

Medium
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Medium	Moyenne

CURRENT

Short
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Short	Courte

CURRENT

Timespan
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Timespan	Durée

CURRENT

blurb
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Load statistics keep track of three key metrics of resource utilization: <dl> <dt>Total number of executors</dt> <dd>For a computer, this is the number of executors that the computer has. For a label, this is the sum of all executors across all computers in this label. For the entire Jenkins, this is the sum of all executors across all computers in this Jenkins installation. Other than configuration changes, this value can also change when slaves go offline. </dd> <dt>Number of busy executors</dt> <dd>This line tracks the number of executors (among the executors counted above) that are carrying out builds. The ratio of this to the total number of executors gives you the resource utilization. If all your executors are busy for a prolonged period of time, consider adding more computers to your Jenkins cluster.</dd><dt>Queue length</dt><dd>This is the number of jobs that are in the build queue, waiting for an available executor (of this computer, of this label, or in this Jenkins, respectively.) This doesn't include jobs that are in the quiet period, nor does it include jobs that are in the queue because earlier builds are still in progress. If this line ever goes above 0, that means your Jenkins will run more builds by adding more computers.</dd></dl>The graph is exponential moving average of periodically collected data values. 3 timespans are updated every 10 seconds, 1 minute, and 1 hour respectively.	Les statistiques d''utilisation du système permettre de garder trace de trois métriques de mesure de la charge: <dl> <dt>Nombre total d''exécuteurs</dt> <dd>Pour un ordinateur, il s''agit du nombre d''exécuteurs de cet ordinateur. Pour un libellé, cela correspond à la somme des exécuteurs sur tous les ordinateurs possédant ce libellé. Pour Jenkins, il s''agit de la somme de tous les exécuteurs disponibles sur tous les ordinateurs rattachés à cette installation de Jenkins. En dehors des changements de configuration, cette valeur peut également changer quand les esclaves se déconnectent. </dd> <dt>Nombre d''exécuteurs occupés</dt> <dd>Cette ligne donne le nombre d''exécuteurs (parmi ceux comptés ci-dessus) qui s''occupent des builds. Le ratio de ce nombre avec le nombre total d''exécuteurs donne l''utilisation des ressources. Si tous vos exécuteurs sont occupés pendant une période prolongée, pensez à ajouter plusieurs d''ordinateurs à votre cluster Jenkins.</dd><dt>Longueur de la file d''attente</dt><dd>C''est le nombre de jobs qui sont dans la file des builds, en attente d''un exécuteur disponible (respectivement pour cet ordinateur, pour ce libellé ou pour Jenkins en général). Cela n''inclue pas les jobs qui sont dans la 'période silencieuse' (quiet period ou période de délai), ni les jobs qui sont dans la file à cause de builds précédents toujours en cours. Si cette ligne dépasse 0, cela signifie que Jenkins pourra lancer plus de builds en ajoutant des ordinateurs. </dd></dl>Ce graphe est une moyenne glissante exponentielle de données collectées périodiquement. Les périodes de mise à jour sont respectivement toutes les 10 secondes, toutes les minutes et toutes les heures.

CURRENT

title
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Load statistics: {0}	Statistiques de l''utilisation du système: {0}

core/src/main/resources/hudson/model/Messages_fr.properties

Files

MISSING

AbstractBuild.BuildingInWorkspace
20.09.2013 10:05:40, no SCM information
in workspace {0}

MISSING

AbstractBuild.BuildingOnMaster
20.09.2013 10:05:40, no SCM information
Building on master

MISSING

AbstractBuild_Building
20.09.2013 10:05:40, no SCM information
Building

MISSING

AbstractItem.NoSuchJobExists
20.09.2013 10:05:40, no SCM information
No such job ‘{0}’ exists. Perhaps you meant ‘{1}’?

MISSING

AbstractItem.Pronoun
20.09.2013 10:05:40, no SCM information
Job

MISSING

AbstractProject.AssignedLabelString.InvalidBooleanExpression
20.09.2013 10:05:40, no SCM information
Invalid boolean expression: {0}

MISSING

AbstractProject.AssignedLabelString.NoMatch
20.09.2013 10:05:40, no SCM information
There's no slave/cloud that matches this assignment

MISSING

AbstractProject.AssignedLabelString_NoMatch_DidYouMean
20.09.2013 10:05:40, no SCM information
There’s no slave/cloud that matches this assignment. Did you mean ‘{1}’ instead of ‘{0}’?

MISSING

AbstractProject.AwaitingBuildForWorkspace
20.09.2013 10:05:40, no SCM information
Awaiting build to get a workspace.

MISSING

AbstractProject.CancelPermission.Description
20.09.2013 10:05:40, no SCM information
This permission grants the ability to cancel a build.

MISSING

AbstractProject.CustomWorkspaceEmpty
20.09.2013 10:05:40, no SCM information
Custom workspace is empty.

MISSING

AbstractProject.DiscoverPermission.Description
20.09.2013 10:05:40, no SCM information
This permission grants discover access to jobs. Lower than read permissions, it allows you to redirect anonymous users to the login page when they try to access a job url. Without it they would get a 404 error and wouldn't be able to discover project names.

MISSING

AbstractProject.DownstreamBuildInProgress
20.09.2013 10:05:40, no SCM information
Downstream project {0} is already building.

MISSING

AbstractProject.ExtendedReadPermission.Description
20.09.2013 10:05:40, no SCM information
This permission grants read-only access to project configurations. Please be aware that sensitive information in your builds, such as passwords, will be exposed to a wider audience by granting this permission.

MISSING

AbstractProject.NoBuilds
20.09.2013 10:05:40, no SCM information
No existing build. Scheduling a new one.

MISSING

AbstractProject.UpstreamBuildInProgress
20.09.2013 10:05:40, no SCM information
Upstream project {0} is already building.

MISSING

AbstractProject.WipeOutPermission.Description
20.09.2013 10:05:40, no SCM information
This permission grants the ability to wipe out the contents of a workspace.

MISSING

AbstractProject.build_with_parameters
20.09.2013 10:05:40, no SCM information
Build with Parameters

MISSING

BallColor.NotBuilt
20.09.2013 10:05:40, no SCM information
Not built

MISSING

BooleanParameterDefinition.DisplayName
20.09.2013 10:05:40, no SCM information
Boolean Value

MISSING

BuildAuthorizationToken.InvalidTokenProvided
20.09.2013 10:05:40, no SCM information
Invalid token provided.

MISSING

CLI.cancel-quiet-down.shortDescription
20.09.2013 10:05:40, no SCM information
Cancel the effect of the "quiet-down" command.

MISSING

CLI.clear-queue.shortDescription
20.09.2013 10:05:40, no SCM information
Clears the build queue

MISSING

CLI.connect-node.shortDescription
20.09.2013 10:05:40, no SCM information
Reconnect to a node

MISSING

CLI.delete-job.shortDescription
20.09.2013 10:05:40, no SCM information
Deletes a job

MISSING

CLI.delete-node.shortDescription
20.09.2013 10:05:40, no SCM information
Deletes a node

MISSING

CLI.disable-job.shortDescription
20.09.2013 10:05:40, no SCM information
Disables a job

MISSING

CLI.disconnect-node.shortDescription
20.09.2013 10:05:40, no SCM information
Disconnects from a node

MISSING

CLI.enable-job.shortDescription
20.09.2013 10:05:40, no SCM information
Enables a job

MISSING

CLI.keep-build.shortDescription
20.09.2013 10:05:40, no SCM information
Mark the build to keep the build forever.

MISSING

CLI.offline-node.shortDescription
20.09.2013 10:05:40, no SCM information
Stop using a node for performing builds temporarily, until the next "online-node" command.

MISSING

CLI.online-node.shortDescription
20.09.2013 10:05:40, no SCM information
Resume using a node for performing builds, to cancel out the earlier "offline-node" command.

MISSING

CLI.quiet-down.shortDescription
20.09.2013 10:05:40, no SCM information
Quiet down Jenkins, in preparation for a restart. Don’t start any builds.

MISSING

CLI.reload-configuration.shortDescription
20.09.2013 10:05:40, no SCM information
Discard all the loaded data in memory and reload everything from file system. Useful when you modified config files directly on disk.

MISSING

CLI.restart.shortDescription
20.09.2013 10:05:40, no SCM information
Restart Jenkins

MISSING

CLI.safe-restart.shortDescription
20.09.2013 10:05:40, no SCM information
Safely restart Jenkins

MISSING

CLI.wait-node-offline.shortDescription
20.09.2013 10:05:40, no SCM information
Wait for a node to become offline

MISSING

CLI.wait-node-online.shortDescription
20.09.2013 10:05:40, no SCM information
Wait for a node to become online

MISSING

Cause.RemoteCause.ShortDescriptionWithNote
20.09.2013 10:05:40, no SCM information
Started by remote host {0} with note: {1}

MISSING

Cause.UpstreamCause.CausedBy
20.09.2013 10:05:40, no SCM information
originally caused by:

MISSING

ChoiceParameterDefinition.DisplayName
20.09.2013 10:05:40, no SCM information
Choice

MISSING

Computer.BadChannel
20.09.2013 10:05:40, no SCM information
Slave node offline or not a remote channel (such as master node).

MISSING

Computer.BuildPermission.Description
20.09.2013 10:05:40, no SCM information
This permission allows users to run jobs as them on slaves.

MISSING

Computer.ConnectPermission.Description
20.09.2013 10:05:40, no SCM information
This permission allows users to connect slaves or mark slaves as online.

MISSING

Computer.CreatePermission.Description
20.09.2013 10:05:40, no SCM information
This permission allows users to create slaves.

MISSING

Computer.DisconnectPermission.Description
20.09.2013 10:05:40, no SCM information
This permission allows users to disconnect slaves or mark slaves as temporarily offline.

MISSING

Computer.ExtendedReadPermission.Description
20.09.2013 10:05:40, no SCM information
This permission allows users to read slave configuration.

MISSING

Computer.NoSuchSlaveExists
20.09.2013 10:05:40, no SCM information
No such slave "{0}" exists. Did you mean "{1}"?

MISSING

ComputerSet.DisplayName
20.09.2013 10:05:40, no SCM information
nodes

MISSING

Descriptor.From
20.09.2013 10:05:40, no SCM information
(from <a href="{1}">{0}</a>)

MISSING

HealthReport.EmptyString
20.09.2013 10:05:40, no SCM information
—

MISSING

Hudson.NodeBeingRemoved
20.09.2013 10:05:40, no SCM information
Node is being removed

MISSING

Hudson.NodeDescription
20.09.2013 10:05:40, no SCM information
the master Jenkins node

MISSING

Hudson.NotANonNegativeNumber
20.09.2013 10:05:40, no SCM information
Number may not be negative

MISSING

Hudson.RunScriptsPermission.Description
20.09.2013 10:05:40, no SCM information
The "run scripts" permission is necessary for running groovy scripts via the groovy console or groovy cli command.

MISSING

Hudson.USER_CONTENT_README
20.09.2013 10:05:40, no SCM information
Files in this directory will be served under your http://server/jenkins/userContent/

MISSING

Item.CONFIGURE.description
20.09.2013 10:05:40, no SCM information
Change the configuration of a job.

MISSING

Item.CREATE.description
20.09.2013 10:05:40, no SCM information
Create a new job.

MISSING

Item.DELETE.description
20.09.2013 10:05:40, no SCM information
Delete a job.

MISSING

Item.READ.description
20.09.2013 10:05:40, no SCM information
See a job. (You may deny this permission but allow Discover to force an anonymous user to log in to see the job.)

MISSING

Jenkins.CheckDisplayName.DisplayNameNotUniqueWarning
20.09.2013 10:05:40, no SCM information
The display name, "{0}", is already in use by another job and could cause confusion and delay.

MISSING

Jenkins.CheckDisplayName.NameNotUniqueWarning
20.09.2013 10:05:40, no SCM information
The display name, "{0}", is used as a name by a job and could cause confusing search results.

MISSING

Jenkins.NotAllowedName
20.09.2013 10:05:40, no SCM information
"{0}" is not allowed name

MISSING

Label.GroupOf
20.09.2013 10:05:40, no SCM information
group of {0}

MISSING

Label.InvalidLabel
20.09.2013 10:05:40, no SCM information
invalid label

MISSING

Label.ProvisionedFrom
20.09.2013 10:05:40, no SCM information
Provisioned from {0}

MISSING

MultiStageTimeSeries.EMPTY_STRING
20.09.2013 10:05:40, no SCM information
—

MISSING

MyViewsProperty.ViewExistsCheck.AlreadyExists
20.09.2013 10:05:40, no SCM information
A view with name {0} already exists

MISSING

MyViewsProperty.ViewExistsCheck.NotExist
20.09.2013 10:05:40, no SCM information
A view with name {0} does not exist

MISSING

Node.BecauseNodeIsReserved
20.09.2013 10:05:40, no SCM information
{0} is reserved for jobs tied to it

MISSING

Node.LabelMissing
20.09.2013 10:05:40, no SCM information
{0} doesn’t have label {1}

MISSING

Node.LackingBuildPermission
20.09.2013 10:05:40, no SCM information
{0} doesn’t have a permission to run on {1}

MISSING

PasswordParameterDefinition.DisplayName
20.09.2013 10:05:40, no SCM information
Password Parameter

MISSING

Permalink.LastUnstableBuild
20.09.2013 10:05:40, no SCM information
Last unstable build

MISSING

Permalink.LastUnsuccessfulBuild
20.09.2013 10:05:40, no SCM information
Last unsuccessful build

MISSING

ProxyView.DisplayName
20.09.2013 10:05:40, no SCM information
Include a global view

MISSING

ProxyView.NoSuchViewExists
20.09.2013 10:05:40, no SCM information
Global view {0} does not exist

MISSING

Queue.init
20.09.2013 10:05:40, no SCM information
Restoring the build queue

MISSING

ResultTrend.Aborted
20.09.2013 10:05:40, no SCM information
Aborted

MISSING

ResultTrend.Failure
20.09.2013 10:05:40, no SCM information
Failure

MISSING

ResultTrend.Fixed
20.09.2013 10:05:40, no SCM information
Fixed

MISSING

ResultTrend.NotBuilt
20.09.2013 10:05:40, no SCM information
Not built

MISSING

ResultTrend.NowUnstable
20.09.2013 10:05:40, no SCM information
Now unstable

MISSING

ResultTrend.StillFailing
20.09.2013 10:05:40, no SCM information
Still failing

MISSING

ResultTrend.StillUnstable
20.09.2013 10:05:40, no SCM information
Still unstable

MISSING

ResultTrend.Success
20.09.2013 10:05:40, no SCM information
Success

MISSING

ResultTrend.Unstable
20.09.2013 10:05:40, no SCM information
Unstable

MISSING

Run.ArtifactsPermission.Description
20.09.2013 10:05:40, no SCM information
This permission grants the ability to retrieve the artifacts produced by builds. If you don’t want an user to access the artifacts, you can do so by revoking this permission.

MISSING

Run.InProgressDuration
20.09.2013 10:05:40, no SCM information
{0} and counting

MISSING

Run.Summary.Aborted
20.09.2013 10:05:40, no SCM information
aborted

MISSING

Run.Summary.BackToNormal
20.09.2013 10:05:40, no SCM information
back to normal

MISSING

Run.Summary.BrokenForALongTime
20.09.2013 10:05:40, no SCM information
broken for a long time

MISSING

Run.Summary.BrokenSince
20.09.2013 10:05:40, no SCM information
broken since build {0}

MISSING

Run.Summary.BrokenSinceThisBuild
20.09.2013 10:05:40, no SCM information
broken since this build

MISSING

Run.Summary.LessTestsFailing
20.09.2013 10:05:40, no SCM information
{0} less {0,choice,0#tests are\|1#test is\|1<tests are} failing (total {1})

MISSING

Run.Summary.MoreTestsFailing
20.09.2013 10:05:40, no SCM information
{0} more {0,choice,0#tests are\|1#test is\|1<tests are} failing (total {1})

MISSING

Run.Summary.NotBuilt
20.09.2013 10:05:40, no SCM information
not built

MISSING

Run.Summary.Stable
20.09.2013 10:05:40, no SCM information
stable

MISSING

Run.Summary.TestFailures
20.09.2013 10:05:40, no SCM information
{0} {0,choice,0#test failures\|1#test failure\|1<test failures}

MISSING

Run.Summary.TestsStartedToFail
20.09.2013 10:05:40, no SCM information
{0} {0,choice,0#tests\|1#test\|1<tests} started to fail

MISSING

Run.Summary.TestsStillFailing
20.09.2013 10:05:40, no SCM information
{0} {0,choice,0#tests are\|1#test is\|1<tests are} still failing

MISSING

Run.Summary.Unknown
20.09.2013 10:05:40, no SCM information
?

MISSING

Run.Summary.Unstable
20.09.2013 10:05:40, no SCM information
unstable

MISSING

Run._is_waiting_for_a_checkpoint_on_
20.09.2013 10:05:40, no SCM information
{0} is waiting for a checkpoint on {1}

MISSING

RunParameterDefinition.DisplayName
20.09.2013 10:05:40, no SCM information
Run Parameter

MISSING

Slave.Network.Mounted.File.System.Warning
20.09.2013 10:05:40, no SCM information
Are you sure you want to use network mounted file system for FS root? Note that this directory does not need to be visible to the master.

MISSING

Slave.Remote.Director.Mandatory
20.09.2013 10:05:40, no SCM information
Remote directory is mandatory

MISSING

Slave.the_remote_root_must_be_an_absolute_path
20.09.2013 10:05:40, no SCM information
The remote root must be an absolute path.

MISSING

TextParameterDefinition.DisplayName
20.09.2013 10:05:40, no SCM information
Text Parameter

MISSING

UpdateCenter.DownloadButNotActivated
20.09.2013 10:05:40, no SCM information
Downloaded Successfully. Will be activated during the next boot

MISSING

UpdateCenter.PluginCategory.builder
20.09.2013 10:05:40, no SCM information
Build Tools

MISSING

UpdateCenter.PluginCategory.buildwrapper
20.09.2013 10:05:40, no SCM information
Build Wrappers

MISSING

UpdateCenter.PluginCategory.cli
20.09.2013 10:05:40, no SCM information
Command Line Interface

MISSING

UpdateCenter.PluginCategory.cluster
20.09.2013 10:05:40, no SCM information
Cluster Management and Distributed Build

MISSING

UpdateCenter.PluginCategory.external
20.09.2013 10:05:40, no SCM information
External Site/Tool Integrations

MISSING

UpdateCenter.PluginCategory.listview-column
20.09.2013 10:05:40, no SCM information
List view columns

MISSING

UpdateCenter.PluginCategory.maven
20.09.2013 10:05:40, no SCM information
Maven

MISSING

UpdateCenter.PluginCategory.misc
20.09.2013 10:05:40, no SCM information
Miscellaneous

MISSING

UpdateCenter.PluginCategory.must-be-labeled
20.09.2013 10:05:40, no SCM information
Uncategorized

MISSING

UpdateCenter.PluginCategory.notifier
20.09.2013 10:05:40, no SCM information
Build Notifiers

MISSING

UpdateCenter.PluginCategory.page-decorator
20.09.2013 10:05:40, no SCM information
Page Decorators

MISSING

UpdateCenter.PluginCategory.post-build
20.09.2013 10:05:40, no SCM information
Other Post-Build Actions

MISSING

UpdateCenter.PluginCategory.report
20.09.2013 10:05:40, no SCM information
Build Reports

MISSING

UpdateCenter.PluginCategory.scm
20.09.2013 10:05:40, no SCM information
Source Code Management

MISSING

UpdateCenter.PluginCategory.scm-related
20.09.2013 10:05:40, no SCM information
Source Code Management related

MISSING

UpdateCenter.PluginCategory.slaves
20.09.2013 10:05:40, no SCM information
Slave Launchers and Controllers

MISSING

UpdateCenter.PluginCategory.trigger
20.09.2013 10:05:40, no SCM information
Build Triggers

MISSING

UpdateCenter.PluginCategory.ui
20.09.2013 10:05:40, no SCM information
User Interface

MISSING

UpdateCenter.PluginCategory.unrecognized
20.09.2013 10:05:40, no SCM information
Misc ({0})

MISSING

UpdateCenter.PluginCategory.upload
20.09.2013 10:05:40, no SCM information
Artifact Uploaders

MISSING

UpdateCenter.PluginCategory.user
20.09.2013 10:05:40, no SCM information
Authentication and User Management

MISSING

UpdateCenter.init
20.09.2013 10:05:40, no SCM information
Initialing update center

MISSING

UpdateCenter.n_a
20.09.2013 10:05:40, no SCM information
N/A

MISSING

View.MissingMode
20.09.2013 10:05:40, no SCM information
No view type is specified

MISSING

View.ReadPermission.Description
20.09.2013 10:05:40, no SCM information
This permission allows users to see views (implied by generic read access).

OUTDATED

AbstractBuild.BuildingRemotely
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Building remotely on {0}	Construction à distance sur {0}
(old value)

OUTDATED

AbstractBuild.KeptBecause
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
This build is kept because of {0}.	conservé à cause de {0}
(old value)

OUTDATED

AbstractProject.Aborted
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Aborted	Annulé
(old value)

OUTDATED

AbstractProject.BuildInProgress
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Build #{0} is already in progress{1}	Le build #{0} est déjà en cours {1}
(old value)

OUTDATED

AbstractProject.BuildNow
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Build Now	Lancer un build
(old value)

OUTDATED

AbstractProject.BuildPermission.Description
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
This permission grants the ability to start a new build.	Ce droit permet de démarrer un nouveau build.
(old value)

OUTDATED

AbstractProject.Disabled
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Build disabled	Build désactivé
(old value)

OUTDATED

AbstractProject.ETA
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
(ETA:{0})	(fin prévue à: {0})
(old value)

OUTDATED

AbstractProject.NewBuildForWorkspace
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Scheduling a new build to get a workspace.	Demande d''un nouveau build afin d''avoir un répertoire de travail
(old value)

OUTDATED

AbstractProject.NoSCM
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
No SCM	Pas d''outil de gestion de version
(old value)

OUTDATED

AbstractProject.NoWorkspace
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
No workspace is available, so can’t check for updates.	Pas répertoire de travail disponible, donc impossible de récupérer les mises à jour.
(old value)

OUTDATED

AbstractProject.PollingABorted
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
SCM polling aborted	Scrutation de l''outil de gestion de version annulée
(old value)

OUTDATED

AbstractProject.Pronoun
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Project	Projet
(old value)

OUTDATED

AbstractProject.ScmAborted
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
SCM check out aborted	Récupération des mises à jour à partir de l''outil de gestion de version annulée
(old value)

OUTDATED

AbstractProject.WorkspaceOffline
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Workspace is offline.	Le répertoire de travail est déconnecté.
(old value)

OUTDATED

AbstractProject.WorkspacePermission.Description
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
This permission grants the ability to retrieve the contents of a workspace Jenkins checked out for performing builds. If you don’t want an user to access the source code, you can do so by revoking this permission.	Ce droit permet d''obtenir le contenu d''un répertoire de travail récupéré par Jenkins pour réaliser des builds. Si vous ne voulez pas qu''un utilisateur ait accès au code source, vous pouvez retirer ce droit.
(old value)

OUTDATED

Api.MultipleMatch
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
XPath "{0}" matched {1} nodes. Create XPath that only matches one, or use the "wrapper" query parameter to wrap them all under a root element.	Le XPath "{0}" correspond à {1} noeud(s). Merci de fournir un XPath qui ne correspond qu''à un seul noeud, ou utilisez le paramètre de requète "wrapper" pour les encapsuler tous dans un élément racine.
(old value)

OUTDATED

Api.NoXPathMatch
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
XPath {0} didn’t match	Pas de correspondance avec le XPath {0}
(old value)

OUTDATED

BallColor.Aborted
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Aborted	Annulé
(old value)

OUTDATED

BallColor.Disabled
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Disabled	Désactivé
(old value)

OUTDATED

BallColor.Failed
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Failed	En échec
(old value)

OUTDATED

BallColor.InProgress
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
In progress	En cours
(old value)

OUTDATED

BallColor.Pending
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Pending	En attente
(old value)

OUTDATED

BallColor.Success
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Success	Succès
(old value)

OUTDATED

BallColor.Unstable
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Unstable	Instable
(old value)

OUTDATED

Cause.LegacyCodeCause.ShortDescription
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Legacy code started this job. No cause information is available	Ce job a été lancé par du code legacy. Pas d''information sur les causes
(old value)

OUTDATED

Cause.RemoteCause.ShortDescription
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Started by remote host {0}	Démarré à distance par {0}
(old value)

OUTDATED

Cause.UpstreamCause.ShortDescription
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Started by upstream project "{0}" build number {1}	Démarré par le projet amont "{0}" de numéro de build {1}
(old value)

OUTDATED

Cause.UserCause.ShortDescription
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Started by user {0}	Démarré par l''utilisateur {0}
(old value)

OUTDATED

Cause.UserIdCause.ShortDescription
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Started by user {0}	Démarré par l''utilisateur {0}
(old value)

OUTDATED

Computer.Caption
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Slave {0}	Esclave {0}
(old value)

OUTDATED

Computer.ConfigurePermission.Description
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
This permission allows users to configure slaves.	Ce droit permet aux utilisateurs de configurer les esclaves.
(old value)

OUTDATED

Computer.DeletePermission.Description
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
This permission allows users to delete existing slaves.	Ce droit permet aux utilisateurs de supprimer les esclaves.
(old value)

OUTDATED

Computer.Permissions.Title
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Slave	Esclave
(old value)

OUTDATED

ComputerSet.NoSuchSlave
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
No such slave: {0}	Cet esclave n''existe pas : {0}
(old value)

OUTDATED

ComputerSet.SlaveAlreadyExists
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Slave called ‘{0}’ already exists	L''esclave appelé ''{0}'' existe déjà
(old value)

OUTDATED

ComputerSet.SpecifySlaveToCopy
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Specify which slave to copy	Spécifiez l''esclave à copier
(old value)

OUTDATED

Executor.NotAvailable
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
N/A	N/A
(old value)

OUTDATED

ExternalJob.DisplayName
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Monitor an external job	Contrôler un job externe
(old value)

OUTDATED

ExternalJob.Pronoun
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
External Job	Job
(old value)

OUTDATED

FileParameterDefinition.DisplayName
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
File Parameter	Paramètre fichier
(old value)

OUTDATED

FreeStyleProject.DisplayName
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Build a free-style software project	Construire un projet free-style
(old value)

OUTDATED

Hudson.AdministerPermission.Description
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
This permission grants the ability to make system-wide configuration changes, as well as perform highly sensitive operations that amounts to full local system access (within the scope granted by the underlying OS.)	Ce droit permet de faire des changements de configuration au niveau de tout le système, et de réaliser des opérations très délicates qui nécessitent un accès complet à tout le système (dans les limites autorisées par l''OS sous-jacent).
(old value)

OUTDATED

Hudson.BadPortNumber
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Bad port number {0}	Numéro de port incorrect {0}
(old value)

OUTDATED

Hudson.Computer.Caption
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Master	Maître
(old value)

OUTDATED

Hudson.Computer.DisplayName
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
master	maître
(old value)

OUTDATED

Hudson.ControlCodeNotAllowed
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
No control code is allowed: {0}	Code de contrôle non autorisé
(old value)

OUTDATED

Hudson.DisplayName
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Jenkins	Jenkins
(old value)

OUTDATED

Hudson.JobAlreadyExists
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
A job already exists with the name ‘{0}’	Un job existe déjà avec le nom ''{0}''
(old value)

OUTDATED

Hudson.NoJavaInPath
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
java is not in your PATH. Maybe you need to <a href="{0}/configure">configure JDKs</a>?	java n''est pas dans votre PATH. Peut-être avez-vous besoin de <a href=''{0}/configure''>configurer les JDKs</a>?
(old value)

OUTDATED

Hudson.NoName
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
No name is specified	Aucune nom n''est spécifié
(old value)

OUTDATED

Hudson.NoSuchDirectory
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
No such directory: {0}	Le répertoire n''existe pas: {0}
(old value)

OUTDATED

Hudson.NotADirectory
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
{0} is not a directory	{0} n''est pas un répertoire
(old value)

OUTDATED

Hudson.NotANegativeNumber
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Not a negative number	Ceci n''est pas un nombre négatif
(old value)

OUTDATED

Hudson.NotANumber
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Not a number	Ceci n''est pas un nombre
(old value)

OUTDATED

Hudson.NotAPlugin
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
{0} is not a Jenkins plugin	{0} n''est pas un plugin Jenkins
(old value)

OUTDATED

Hudson.NotAPositiveNumber
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Not a positive number	Ceci n''est pas un nombre positif
(old value)

OUTDATED

Hudson.NotJDKDir
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
{0} doesn’t look like a JDK directory	{0} ne semble pas être un répertoire contenant un JDK
(old value)

OUTDATED

Hudson.NotUsesUTF8ToDecodeURL
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Your container doesn’t use UTF-8 to decode URLs. If you use non-ASCII characters as a job name etc, this will cause problems. See <a href="http://wiki.jenkins-ci.org/display/JENKINS/Containers">Containers</a> and <a href="http://wiki.jenkins-ci.org/display/JENKINS/Tomcat#Tomcat-i18n">Tomcat i18n</a> for more details.	Votre conteneur n''utilise pas UTF-8 pour décoder les URLs. Si vous utilisez des caractères non-ASCII dans le nom d''un job ou autre, cela causera des problèmes. Consultez les pages sur les <a href=''http://wiki.jenkins-ci.org/display/JENKINS/Containers''>conteneurs</a> et sur <a href=''http://wiki.jenkins-ci.org/display/JENKINS/Tomcat#Tomcat-i18n''>Tomcat i18n</a> pour plus de détails.
(old value)

OUTDATED

Hudson.Permissions.Title
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Overall	Global
(old value)

OUTDATED

Hudson.ReadPermission.Description
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
The read permission is necessary for viewing almost all pages of Jenkins. This permission is useful when you don’t want unauthenticated users to see Jenkins pages — revoke this permission from the anonymous user, then add "authenticated" pseudo-user and grant the read access.	Le droit en lecture est nécessaire pour voir la plupart des pages de Jenkins. Ce droit est utile quand vous ne voulez pas que les utilisateurs non authentifiés puissent voir les pages Jenkins — retirez ce droit à l''utilisateur anonymous, puis ajoutez le pseudo-utilisateur "authenticated" et accordez-lui le droit en lecture.
(old value)

OUTDATED

Hudson.UnsafeChar
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
‘{0}’ is an unsafe character	''{0}'' est un caractère dangereux
(old value)

OUTDATED

Hudson.ViewAlreadyExists
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
A view already exists with the name "{0}"	Une vue existe déjà avec le nom "{0}"
(old value)

OUTDATED

Hudson.ViewName
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
All	Tous
(old value)

OUTDATED

Item.Permissions.Title
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Job	Job
(old value)

OUTDATED

Job.AllRecentBuildFailed
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
All recent builds failed.	Tous les builds récents ont échoué.
(old value)

OUTDATED

Job.BuildStability
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Build stability: {0}	Stabilité du build: {0}
(old value)

OUTDATED

Job.NOfMFailed
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
{0} out of the last {1} builds failed.	{0} des {1} derniers builds ont échoué.
(old value)

OUTDATED

Job.NoRecentBuildFailed
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
No recent builds failed.	Aucun build récent n''a échoué.
(old value)

OUTDATED

Job.Pronoun
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Project	job
(old value)

OUTDATED

Job.minutes
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
mins	mn
(old value)

OUTDATED

ListView.DisplayName
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
List View	Vue liste
(old value)

OUTDATED

LoadStatistics.Legends.BusyExecutors
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Busy executors	Nb d''exécuteurs occupés
(old value)

OUTDATED

LoadStatistics.Legends.QueueLength
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Queue length	Longueur de la file d''attente
(old value)

OUTDATED

LoadStatistics.Legends.TotalExecutors
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Total executors	Nb total d''exécuteurs
(old value)

OUTDATED

ManageJenkinsAction.DisplayName
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Manage Jenkins	Administrer Jenkins
(old value)

OUTDATED

MyView.DisplayName
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
My View	Ma vue
(old value)

OUTDATED

MyViewsProperty.DisplayName
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
My Views	Mes vues
(old value)

OUTDATED

MyViewsProperty.GlobalAction.DisplayName
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
My Views	Mes vues
(old value)

OUTDATED

Node.Mode.EXCLUSIVE
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Leave this machine for tied jobs only	Réserver cette machine pour les jobs qui lui sont attachés seulement
(old value)

OUTDATED

Node.Mode.NORMAL
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Utilize this slave as much as possible	Utiliser cet esclave autant que possible
(old value)

OUTDATED

ParameterAction.DisplayName
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Parameters	Paramètres
(old value)

OUTDATED

ParametersDefinitionProperty.DisplayName
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Parameters	Paramètres
(old value)

OUTDATED

Permalink.LastBuild
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Last build	Dernier build
(old value)

OUTDATED

Permalink.LastFailedBuild
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Last failed build	Dernier build en échec
(old value)

OUTDATED

Permalink.LastStableBuild
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Last stable build	Dernier build stable
(old value)

OUTDATED

Permalink.LastSuccessfulBuild
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Last successful build	Dernier build avec succès
(old value)

OUTDATED

Queue.AllNodesOffline
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
All nodes of label ‘{0}’ are offline	Tous les esclaves avec le libellé ''{0}'' sont hors ligne
(old value)

OUTDATED

Queue.BlockedBy
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Blocked by {0}	Bloqué par {0}
(old value)

OUTDATED

Queue.HudsonIsAboutToShutDown
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Jenkins is about to shut down	Jenkins est sur le point de se fermer
(old value)

OUTDATED

Queue.InProgress
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
A build is already in progress	Un build est déjà en cours
(old value)

OUTDATED

Queue.InQuietPeriod
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
In the quiet period. Expires in {0}	En période d''attente. Expire dans {0}
(old value)

OUTDATED

Queue.NodeOffline
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
{0} is offline	{0} est hors ligne
(old value)

OUTDATED

Queue.Unknown
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
???	???
(old value)

OUTDATED

Queue.WaitingForNextAvailableExecutor
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Waiting for next available executor	En attente du prochain exécuteur disponible
(old value)

OUTDATED

Queue.WaitingForNextAvailableExecutorOn
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Waiting for next available executor on {0}	En attente du prochain exécuteur disponible sur {0}
(old value)

OUTDATED

Run.BuildAborted
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Build was aborted	Le build a été annulé
(old value)

OUTDATED

Run.DeletePermission.Description
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
This permission allows users to manually delete specific builds from the build history.	Cette option permet aux utilisateurs de supprimer manuellement des builds spécifiques dans l''historique de build.
(old value)

OUTDATED

Run.MarkedExplicitly
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
This record is explicitly marked to be kept.	marqué explicitement pour conservé l''enregistrement
(old value)

OUTDATED

Run.Permissions.Title
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Run	Historique des builds
(old value)

OUTDATED

Run.UnableToDelete
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Unable to delete {0}: {1}	Impossible de supprimer {0}: {1}
(old value)

OUTDATED

Run.UpdatePermission.Description
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
This permission allows users to update description and other properties of a build, for example to leave notes about the cause of a build failure.	Cette option permet aux utilisateurs de mettre à jour la description et d''autres propriétés d''un build, par exemple pour laisser des notes sur la cause d''échec d''un build.
(old value)

OUTDATED

Slave.InvalidConfig.Executors
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Invalid slave configuration for {0}. Invalid # of executors.	Configuration esclave invalide pour {0}. Nombre d''exécuteurs invalide.
(old value)

OUTDATED

Slave.InvalidConfig.NoName
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Invalid slave configuration. Name is empty	Configuration esclave invalide. Le nom est vide.
(old value)

OUTDATED

Slave.InvalidConfig.NoRemoteDir
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Invalid slave configuration for {0}. No remote directory given	Configuration esclave invalide pour {0}. Pas de répertoire distant fourni
(old value)

OUTDATED

Slave.Launching
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
{0} Launching slave agent	{0} Lancement de l''agent esclave
(old value)

OUTDATED

Slave.Terminated
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
{0} slave agent was terminated	{0} l''agent esclave a été terminé
(old value)

OUTDATED

Slave.UnableToLaunch
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Unable to launch the slave agent for {0}{1}	Impossible de lancer l''agent esclave pour {0} {1}
(old value)

OUTDATED

Slave.UnixSlave
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
This is a Unix slave	Ceci est un esclave Unix
(old value)

OUTDATED

Slave.WindowsSlave
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
This is a Windows slave	Ceci est un esclave Windows
(old value)

OUTDATED

StringParameterDefinition.DisplayName
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
String Parameter	Paramètre String
(old value)

OUTDATED

UpdateCenter.Status.CheckingInternet
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Checking internet connectivity	Vérification de la connexion à internet
(old value)

OUTDATED

UpdateCenter.Status.CheckingJavaNet
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Checking update center connectivity	Vérification de la connexion à jenkins-ci.org
(old value)

OUTDATED

UpdateCenter.Status.ConnectionFailed
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
<span class=error>Failed to connect to {0}. Perhaps you need to <a href="../pluginManager/advanced">configure HTTP proxy?</a></span>	<span class=error>Echec lors de la connexion à {0}. Peut-être devez-vous <a href="../pluginManager/advanced">configurer le proxy HTTP.</a></span>
(old value)

OUTDATED

UpdateCenter.Status.Success
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
Success	Succès
(old value)

OUTDATED

UpdateCenter.Status.UnknownHostException
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
<span class=error>Failed to resolve host name {0}. Perhaps you need to <a href="../pluginManager/advanced">configure HTTP proxy?</a></span>	<span class=error>Impossible de résoudre le nom de host {0}. Peut-être devez-vous <a href="../pluginManager/advanced">configurer un proxy HTTP?</a></span>
(old value)

OUTDATED

View.ConfigurePermission.Description
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
This permission allows users to change the configuration of views.	Ce droit permet aux utilisateurs de changer la configuration des vues.
(old value)

OUTDATED

View.CreatePermission.Description
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
This permission allows users to create new views.	Ce droit permet aux utilisateurs de créer des nouvelles vues.
(old value)

OUTDATED

View.DeletePermission.Description
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
This permission allows users to delete existing views.	Ce droit permet aux utilisateurs de supprimer des vues existantes.
(old value)

OUTDATED

View.Permissions.Title
20.09.2013 10:05:40, no SCM information	23.07.2013 16:05:31, no SCM information
View	Vues
(old value)

core/src/main/resources/hudson/model/MyView/newViewDetail_fr.properties

Files

newViewDetail_fr.properties

CURRENT

blurb
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
This view automatically displays all the jobs that the current user has an access to.	Cette vue n''a pas de job associé.

core/src/main/resources/hudson/model/MyView/noJob_fr.properties

Files

noJob.jelly

noJob_fr.properties

CURRENT

blurb
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
This view has no jobs.	Cette vue n''a pas de job associé.

core/src/main/resources/hudson/model/MyViewsProperty/config_fr.properties

Files

CURRENT

Default View
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Default View	Vue par défaut

CURRENT

description
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
The view selected by default when navigating to the users' private views	La vue sélectionnée par défaut lors de la navigation dans les vues privées de l''utilisateur

core/src/main/resources/hudson/model/MyViewsProperty/newView_fr.properties

Files

newView.jelly

newView_fr.properties

CURRENT

View name
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
View name	Nom de la vue

core/src/main/resources/hudson/model/NoFingerprintMatch/index_fr.properties

Files

help-numExecutors_fr.html

OUTDATED

cause.1
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
Perhaps the file was not created under Jenkins. Maybe it’s a version that someone built locally on his/her own machine.	Le fichier n''a peut-être pas été créé par Jenkins.Peut-être est-ce une version que quelqu''un a construit localement sur sa propre machine.
(old value)

OUTDATED

cause.2
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
Perhaps the projects are not set up correctly and not recording fingerprints. Check the project setting.	Peut-être que les projets n''ont pas été configurés pour enregistrer les empreintes. Vérifiez la configuration du projet
(old value)

OUTDATED

description
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
The fingerprint {0} did not match any of the recorded data.	L''empreinte numérique {0} ne correspond pas aux empreintes déjà enregistrées.
(old value)

CURRENT

Back to Dashboard
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Back to Dashboard	Retour au tableau de bord

CURRENT

No matching record found
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
No matching record found	Aucune donnée correspondante trouvée

core/src/main/resources/hudson/model/Node/help-labelString_fr.html

Files

help-labelString.html

help-labelString_fr.html

CURRENT

04.02.2013 00:16:06, no SCM information

<div>
Labels (AKA tags) are used for grouping multiple slaves into one logical group.
Use spaces between each label. For instance 'regression java6' will assign a
node the labels 'regression' and 'java6'.

<p>
For example, if you have multiple Windows slaves and you have jobs that require
Windows, then you can configure all your Windows slaves to have the label 'windows',
then tie the job to the 'windows' label. This allows your job to run on any
of your Windows slaves but not on anywhere else.
</div>

<div>
Les libellés (ou tags) sont utilisés pour grouper plusieurs esclaves
dans un groupe logique.

<p>
Par exemple, si vous avez de multiples esclaves Windows et des jobs qui
nécessitent Windows, taggez vos esclaves Windows avec 'windows',
puis rattachez les jobs à ce tag. Cela pemettra à vos jobs de ne
s'exécuter que sur les esclaves Windows et pas sur les autres.
</div>

core/src/main/resources/hudson/model/Node/help-name_fr.html

Files

help-name.html

help-name_fr.html

CURRENT

04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
<div> Name that uniquely identifies a slave within this Jenkins installation. <p> This value could be any string, and doesn't have to be the same as the slave host name, but it's often convenient to make them the same. </div>	<div> Un nom qui identifie de façon unique un esclave dans le contexte d'une installation de Jenkins. <p> Cette valeur peut être une String quelconque et ne doit pas nécessairement être égale au nom de la machine esclave. Néanmoins, il est souvent pratique que ces deux valeurs soient les mêmes. </div>

core/src/main/resources/hudson/model/Node/help-numExecutors_fr.html

Files

help-numExecutors.html

CURRENT

04.02.2013 00:16:06, no SCM information

<div>
This controls the number of concurrent builds that Jenkins can perform. So the value
affects the overall system load Jenkins may incur.
A good value to start with would be the number of processors on your system.

<p>
Increasing this value beyond that would cause each build to take longer, but it could increase
the overall throughput, because it allows CPU to build one project while another build is waiting
for I/O.

<p>
When using Jenkins in the master/slave mode, setting this value to 0 would prevent the master
from doing any building on its own. Slaves may not have zero executors, but may be
temporarily disabled using the button on the slave's status page.
</div>

<div>
Ceci contr�le le nombre de builds simultan�s que Jenkins peut ex�cuter.
Cette valeur impacte donc la charge g�n�rale du syst�me.
Une bonne valeur pour commencer serait le nombre de processeurs sur
votre syst�me.

<p>
Un nombre de builds simultan�s sup�rieur � cette valeur augmentera la
dur�e individuelle de chaque build. N�anmoins, la capacit� globale
peut �tre sup�rieure, puisqu'un processeur peut se charger d'un build
pendant qu'un autre build est en attente sur les entr�es/sorties.

<p>
En mode ma�tre/esclave, une valeur de 0 garantit que le ma�tre ne fera
pas lui-m�me de build.
</div>

core/src/main/resources/hudson/model/ParametersAction/index_fr.properties

Files

CURRENT

Build
04.02.2013 00:16:06, no SCM information	30.05.2013 20:09:20, no SCM information
Build	Build

CURRENT

Parameters
04.02.2013 00:16:06, no SCM information	30.05.2013 20:09:20, no SCM information
Parameters	Paramètres

core/src/main/resources/hudson/model/ParametersDefinitionProperty/config_fr.properties

Files

CURRENT

Add Parameter
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Add Parameter	Ajouter un paramètre

CURRENT

This build is parameterized
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
This build is parameterized	Ce build a des paramètres

core/src/main/resources/hudson/model/ParametersDefinitionProperty/index_fr.properties

Files

OUTDATED

Build
28.06.2013 06:41:00, no SCM information	30.05.2013 20:09:20, no SCM information
Build	Build
(old value)

OUTDATED

LOADING
28.06.2013 06:41:00, no SCM information	30.05.2013 20:09:20, no SCM information
LOADING	CHARGEMENT
(old value)

CURRENT

description
04.02.2013 00:16:06, no SCM information	30.05.2013 20:09:20, no SCM information
This build requires parameters:	Ce build nécessite des paramètres :

core/src/main/resources/hudson/model/PasswordParameterDefinition/config_fr.properties

Files

CURRENT

Default Value
04.02.2013 00:16:06, no SCM information	30.05.2013 20:09:20, no SCM information
Default Value	Valeur par défaut

CURRENT

Description
04.02.2013 00:16:06, no SCM information	30.05.2013 20:09:20, no SCM information
Description	Description

CURRENT

Name
04.02.2013 00:16:06, no SCM information	30.05.2013 20:09:20, no SCM information
Name	Nom

core/src/main/resources/hudson/model/PermalinkProjectAction/Permalink/link_fr.properties

Files

link.jelly

link_fr.properties

CURRENT

format
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
{0} ({1}), {2} ago	{0} ({1}), il y a {2}

core/src/main/resources/hudson/model/ProxyView/configure-entries_fr.properties

Files

CURRENT

The name of a global view that will be shown.
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
The name of a global view that will be shown.	Le nom de la vue globale qui sera affichée.

CURRENT

View name
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
View name	Nom de la vue

core/src/main/resources/hudson/model/ProxyView/newViewDetail.jelly (Master)

Files

artifacts-index_fr.properties

MISSING

Shows the content of a global view.
04.02.2013 00:16:06, no SCM information
Shows the content of a global view.

core/src/main/resources/hudson/model/Run/KeepLogBuildBadge/badge_fr.properties

Files

badge.jelly

badge_fr.properties

CURRENT

Keep this build forever
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Keep this build forever	Garder ce build indéfiniment

core/src/main/resources/hudson/model/Run/artifacts-index_fr.properties

Files

artifacts-index.jelly

CURRENT

Build Artifacts
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Build Artifacts	Artefacts du build

core/src/main/resources/hudson/model/Run/configure_fr.properties

Files

confirmDelete_fr.properties

CURRENT

Description
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Description	Description

CURRENT

DisplayName
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
DisplayName	Nom à afficher

CURRENT

LOADING
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
LOADING	CHARGEMENT

CURRENT

Save
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Save	Sauvegarder

core/src/main/resources/hudson/model/Run/confirmDelete_fr.properties

Files

confirmDelete.jelly

OUTDATED

cannotMsg
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:06, no SCM information
Cannot delete this build: {0}	Impossible de supprimer ce build, parce qu''il est {0}
(old value)

CURRENT

Are you sure about deleting the build?
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Are you sure about deleting the build?	Etes-vous sûr de vouloir supprimer le build?

CURRENT

Warning
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Warning	Avertissement

CURRENT

Yes
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Yes	Oui

core/src/main/resources/hudson/model/Run/console_fr.properties

Files

console.jelly

console_fr.properties

CURRENT

Console Output
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Console Output	Sortie Console

CURRENT

skipSome
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Skipping {0,number,integer} KB.. <a href="{1}">Full Log</a>	Saute {0,number,integer} Ko. <a href="{1}">Log complet</a>

core/src/main/resources/hudson/model/Run/delete-retry.jelly (Master)

Files

delete-retry.jelly

MISSING

Not successful
01.08.2013 07:43:47, no SCM information
Deletion of the build failed

MISSING

Retry delete
01.08.2013 07:43:47, no SCM information
Retry delete

MISSING

Show reason
01.08.2013 07:43:47, no SCM information
Show reason

core/src/main/resources/hudson/model/Run/delete_fr.properties

Files

CURRENT

Delete this build
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Delete Build	Supprimer cette construction

core/src/main/resources/hudson/model/Run/logKeep_fr.properties

Files

logKeep.jelly

logKeep_fr.properties

OUTDATED

Don't keep this build forever
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:06, no SCM information
Don't keep this build forever	Ne pas conserver ce build sans limite de temps
(old value)

OUTDATED

Keep this build forever
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:06, no SCM information
Keep this build forever	Conserver ce build sans limite de temps
(old value)

core/src/main/resources/hudson/model/RunParameterDefinition/config_fr.properties

Files

help-launcher_fr.properties

MISSING

All Builds
30.05.2013 20:09:20, no SCM information
All Builds

MISSING

Completed Builds Only
30.05.2013 20:09:20, no SCM information
Completed Builds Only

MISSING

Filter
30.05.2013 20:09:20, no SCM information
Filter

MISSING

Stable Builds Only
30.05.2013 20:09:20, no SCM information
Stable Builds Only

MISSING

Successful Builds Only
30.05.2013 20:09:20, no SCM information
Successful Builds Only

EMPTY

Description
30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:06, no SCM information
Description	—

OUTDATED

Name
30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:06, no SCM information
Name	Nom
(old value)

OUTDATED

Project
30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:06, no SCM information
Project	Projet
(old value)

core/src/main/resources/hudson/model/Slave/help-launcher_fr.properties

Files

help-launcher.jelly

CURRENT

Controls how Jenkins starts this slave.
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Controls how Jenkins starts this slave.	Contrôle la façon dont Jenkins démarre l''esclave.

core/src/main/resources/hudson/model/Slave/help-remoteFS_fr.html

Files

help-remoteFS.html

help-remoteFS_fr.html

CURRENT

04.02.2013 00:16:06, no SCM information

<div>
<p>
A slave needs to have a directory dedicated to Jenkins. Specify
the absolute path of this work directory on the slave, such as
'/var/jenkins' or 'c:\jenkins'. This should be a path local to the slave
machine. There's no need for this path to be visible from the master,
under normal circumstances.

<p>
Slaves do not maintain important data (other than active workspaces
of projects last built on it), so you can possibly set the slave
workspace to a temporary directory. The only downside of doing this
is that you may lose the up-to-date workspace if the slave is turned off.
</div>

<div>
<p>
Un esclave a besoin d'un répertoire dédié à Jenkins. Spécifiez ici le
chemin absolu vers le répertoire de travail sur l'esclave, par exemple
'/var/jenkins' ou 'c:\jenkins'. Cela doit être un chemin local à la machine
esclave. En règle générale, il n'est pas nécessaire que ce chemin soit
visible depuis le maître.

<p>
Les esclaves ne conservent pas de données importantes (autres que les
répertoires de travail des derniers builds des projets); vous pouvez donc
positionner le répertoire du travail de l'esclave dans un répertoire
temporaire.
Le seul défaut de ce choix est que vous perdrez le dernier workspace à
jour si la machine esclave est éteinte.
</div>

core/src/main/resources/hudson/model/StringParameterDefinition/config_fr.properties

Files

CURRENT

Default Value
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Default Value	Valeur par défaut

CURRENT

Description
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Description	Description

CURRENT

Name
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Name	Nom

core/src/main/resources/hudson/model/TaskAction/log_fr.properties

Files

log.jelly

log_fr.properties

CURRENT

Clear error to retry
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Clear error to retry	Supprimez l''erreur pour réessayer

core/src/main/resources/hudson/model/TextParameterDefinition/config.jelly (Master)

Files

MISSING

Default Value
04.02.2013 00:16:06, no SCM information
Default Value

MISSING

Description
04.02.2013 00:16:06, no SCM information
Description

MISSING

Name
04.02.2013 00:16:06, no SCM information
Name

core/src/main/resources/hudson/model/TreeView/sidepanel2_fr.properties

Files

sidepanel2.jelly

sidepanel2_fr.properties

CURRENT

New View
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
New View	Nouvelle vue

core/src/main/resources/hudson/model/UpdateCenter/ConnectionCheckJob/row_fr.properties

Files

row.jelly

row_fr.properties

CURRENT

Preparation
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Preparation	Préparation

core/src/main/resources/hudson/model/UpdateCenter/CoreUpdateMonitor/message_fr.properties

Files

CURRENT

NewVersionAvailable
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
New version of Jenkins ({0}) is available for <a href="{1}">download</a> (<a href="http://jenkins-ci.org/changelog.html">changelog</a>).	Une nouvelle version de Jenkins ({0}) est <a href="{1}">disponible</a> (<a href="http://jenkins-ci.org/changelog.html">changelog</a>).

CURRENT

Or Upgrade Automatically
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Or Upgrade Automatically	Ou mettre à jour automatiquement

CURRENT

UpgradeComplete
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Upgrade to Jenkins {0} is complete, awaiting <a href="{1}/safeRestart">restart</a>.	Mise à jour vers Jenkins {0} est terminée, en attente de <a href="{1}/safeRestart">redémarrage</a>.

CURRENT

UpgradeProgress
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Upgrade to Jenkins {0} is <a href="{1}">in progress or failed</a>.	Mise à jour vers Jenkins {0} est <a href="{1}">en cours ou en échec</a>.

core/src/main/resources/hudson/model/UpdateCenter/DownloadJob/Failure/status_fr.properties

Files

CURRENT

Details
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Details	Détails

CURRENT

Failure
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Failure	Échec

core/src/main/resources/hudson/model/UpdateCenter/DownloadJob/Installing/status_fr.properties

Files

CURRENT

Installing
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Installing	En cours d''installation

core/src/main/resources/hudson/model/UpdateCenter/DownloadJob/Pending/status_fr.properties

Files

CURRENT

Pending
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Pending	En cours

core/src/main/resources/hudson/model/UpdateCenter/DownloadJob/Success/status_fr.properties

Files

CURRENT

Success
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Success	Succès

core/src/main/resources/hudson/model/UpdateCenter/RestartJenkinsJob/Canceled/status.jelly (Master)

Files

MISSING

Canceled
04.02.2013 00:16:06, no SCM information
Canceled

core/src/main/resources/hudson/model/UpdateCenter/RestartJenkinsJob/Failure/status_fr.properties

Files

CURRENT

Failure
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Failure	Échec

core/src/main/resources/hudson/model/UpdateCenter/RestartJenkinsJob/Pending/status_fr.properties

Files

CURRENT

Pending
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Pending	En cours

core/src/main/resources/hudson/model/UpdateCenter/RestartJenkinsJob/Running/status.jelly (Master)

Files

MISSING

Running
04.02.2013 00:16:06, no SCM information
Running

core/src/main/resources/hudson/model/UpdateCenter/RestartJenkinsJob/row_fr.properties

Files

row.jelly

row_fr.properties

CURRENT

Restarting Jenkins
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Restarting Jenkins	Redémarrer Jenkins

core/src/main/resources/hudson/model/UpdateCenter/body_fr.properties

Files

body.jelly

body_fr.properties

MISSING

Go back to the top page
04.02.2013 00:16:06, no SCM information
Go back to the top page

MISSING

you can start using the installed plugins right away
04.02.2013 00:16:06, no SCM information
you can start using the installed plugins right away

CURRENT

warning
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Restart Jenkins when installation is complete and no jobs are running	Redémarrer Jenkins quand l''''installation est terminée et qu''''aucun job n''''est en cours

core/src/main/resources/hudson/model/UpdateCenter/index_fr.properties

Files

OUTDATED

Installing Plugins/Upgrades
29.08.2013 16:34:29, no SCM information	04.02.2013 00:16:06, no SCM information
Installing Plugins/Upgrades	Installation/Mise à jour des Plugins
(old value)

OUTDATED

Update Center
29.08.2013 16:34:29, no SCM information	04.02.2013 00:16:06, no SCM information
Update Center	Centre de mise à jour
(old value)

ORPHANED

Schedule Restart
	04.02.2013 00:16:06, no SCM information
	Programmer un redémarrage

ORPHANED

warning
	04.02.2013 00:16:06, no SCM information
	Une fois l''installation terminée, Jenkins doit être redémarré pour prendre en compte les nouveaux plugins.

core/src/main/resources/hudson/model/UpdateCenter/sidepanel_fr.properties

Files

CURRENT

Back to Dashboard
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Back to Dashboard	Retour au tableau de bord

CURRENT

Manage Jenkins
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Manage Jenkins	Administrer Jenkins

CURRENT

Manage Plugins
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Manage Plugins	Gestion des Plugins

core/src/main/resources/hudson/model/UsageStatistics/global_fr.properties

Files

global.groovy

help-usageStatisticsCollected.html

CURRENT

statsBlurb
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Help make Jenkins better by sending anonymous usage statistics and crash reports to the Jenkins project.	Aidez-nous à améliorer Jenkins en envoyant sous forme anonyme les statistiques d''utilisation et les rapports de crash au projet Jenkins.

core/src/main/resources/hudson/model/UsageStatistics/help-usageStatisticsCollected_fr.html

Files

help-usageStatisticsCollected_fr.html

CURRENT

04.02.2013 00:16:06, no SCM information

<div>
Knowing how Jenkins is used is a tremendous help in guiding the direction of the development, especially
for open-source projects where users are inheritenly hard to track down. When this option is enabled,
Jenkins periodically send information about your usage of Jenkins.

<p>
Specifically, it contains the following information:

<ul>
<li>Your Jenkins version
<li>For your master and each slave, OS type, and # of executors
<li>Plugins that are installed and their versions
<li>Number jobs per each job type in your Jenkins
</ul>

<p>
The information doesn't contain anything that identifies you or allows us to contact you
(except information inherently revealed by HTTP, such as the IP address). Tabulated
data of these usage statistics submissions will be shared with the community.

<p>
You can read <a href="http://jenkins.361315.n4.nabble.com/request-for-comments-tracking-usage-metrics-td375557.html">
the discussion of this mechanism in the community</a>, and you are welcome to add your voice here.
</div>

<div>
Comprendre comment Jenkins est utilisé est d'une grande aide pour guider les développements,
particulièrement pour les projets open-source où les utilisateurs sont typiquement difficiles
à connaitre. Quand cette option est activée, Jenkins envoie périodiquement des informations sur votre
utilisation de Jenkins.

<p>
Plus précisément, il envoie les informations suivantes:

<ul>
<li>Votre version de Jenkins
<li>Pour le Jenkins maître et pour chaque esclave, le type d'OS et le nombre d'exécuteurs
<li>Les plugins qui sont installés et leurs versions
<li>Le nombre de jobs pour chaque type de job dans votre installation de Jenkins
</ul>

<p>
Cette information ne contient rien qui vous identifie ou qui nous permet de vous contacter
(hors certaines informations intrinsèques à HTTP, comme votre adresse IP).
Les données compilées de ces statistiques d'utilisation selon partagées avec la communauté.

<p>
N'hésitez pas à lire <a href="http://jenkins.361315.n4.nabble.com/request-for-comments-tracking-usage-metrics-td375557.html">
la discussion sur ce mécanisme</a> et à contribuer aux débats.
</div>

core/src/main/resources/hudson/model/User/builds_fr.properties

Files

builds.jelly

builds_fr.properties

CURRENT

title
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Builds for {0}	Builds de {0}

core/src/main/resources/hudson/model/User/configure_fr.properties

Files

OUTDATED

title
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
User ‘{0}’ Configuration	Configuration de l''utilisateur ''{0}''
(old value)

CURRENT

Description
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Description	Présentation

CURRENT

Save
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Save	Sauvegarder

CURRENT

Your name
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Your name	Votre nom

core/src/main/resources/hudson/model/User/delete_fr.properties

Files

CURRENT

Are you sure about deleting the user from Jenkins?
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Are you sure about deleting the user from Jenkins?	Êtes-vous sûr de vouloir supprimer cet utilisateur de Jenkins?

CURRENT

Yes
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Yes	Oui

core/src/main/resources/hudson/model/User/index_fr.properties

Files

MISSING

Groups
04.02.2013 00:16:06, no SCM information
Groups

CURRENT

Jenkins User Id
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Jenkins User Id	Identifiant d''utilisateur Jenkins

core/src/main/resources/hudson/model/User/sidepanel_fr.properties

Files

ORPHANED

My Views
	04.02.2013 00:16:06, no SCM information
	Mes vues

CURRENT

Builds
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Builds	Builds

CURRENT

Configure
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Configure	Configurer

CURRENT

Delete
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Delete	Supprimer

CURRENT

People
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
People	Personnes

CURRENT

Status
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Status	Statut

core/src/main/resources/hudson/model/View/AsynchPeople/index_fr.properties

Files

MISSING

blurb
30.05.2013 20:09:20, no SCM information
Includes all known “users”, including login identities which the current security realm can enumerate, as well as people mentioned in commit messages in recorded changelogs.

OUTDATED

All People
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
All People	Tout le monde
(old value)

OUTDATED

Last Active
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
Last Active	Dernière activité
(old value)

OUTDATED

Name
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
Name	Nom complet
(old value)

OUTDATED

On
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
On	Sur
(old value)

OUTDATED

People
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
People	Personnes
(old value)

OUTDATED

User Id
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:06, no SCM information
User Id	Identifiant
(old value)

core/src/main/resources/hudson/model/View/People/index.jelly (Master)

Files

MISSING

People
04.02.2013 00:16:06, no SCM information
People

core/src/main/resources/hudson/model/View/builds_fr.properties

Files

builds.jelly

builds_fr.properties

CURRENT

Export as plain XML
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Export as plain XML	Exporter au format XML

CURRENT

buildHistory
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Build History of {0}	Historique des constructions de {0}

core/src/main/resources/hudson/model/View/configure_fr.properties

Files

MISSING

Edit View
04.02.2013 00:16:06, no SCM information
Edit View

MISSING

OK
04.02.2013 00:16:06, no SCM information
OK

CURRENT

Description
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Description	Description

CURRENT

Filter build executors
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Filter build executors	Filtrer les lanceurs de build

CURRENT

Filter build queue
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Filter build queue	Filtrer la file d''attente de build

CURRENT

Name
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Name	Nom

core/src/main/resources/hudson/model/View/delete_fr.properties

Files

CURRENT

Are you sure about deleting the view?
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Are you sure about deleting the view?	Etes-vous sûr de vouloir supprimer la vue?

CURRENT

Yes
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:06, no SCM information
Yes	Oui

core/src/main/resources/hudson/model/View/index_fr.properties

Files

OUTDATED

Dashboard
20.09.2013 10:05:40, no SCM information	04.02.2013 00:16:06, no SCM information
Dashboard	Tableau de bord
(old value)

core/src/main/resources/hudson/model/View/newJob_fr.properties

Files

newJob.jelly

newJob_fr.properties

CURRENT

CopyExisting
04.02.2013 00:16:06, no SCM information	29.04.2013 12:15:14, no SCM information
Copy existing {0}	Copier un {0} existant

CURRENT

JobName
04.02.2013 00:16:06, no SCM information	29.04.2013 12:15:14, no SCM information
{0} name	Nom du {0}

CURRENT

NewJob
04.02.2013 00:16:06, no SCM information	29.04.2013 12:15:14, no SCM information
New {0}	Nouveau {0}

core/src/main/resources/hudson/model/View/noJob_fr.properties

Files

noJob.jelly

noJob_fr.properties

CURRENT

description_1
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:07, no SCM information
This view has no jobs associated with it.	Cette vue n''a aucun job associé.

CURRENT

description_2
04.02.2013 00:16:06, no SCM information	04.02.2013 00:16:07, no SCM information
You can either <a href="configure">add some existing jobs</a> to this view or create a <a href="newJob">new job</a> in this view.	Veuillez <a href="configure">en ajouter</a>.

core/src/main/resources/hudson/model/View/sidepanel_fr.properties

Files

OUTDATED

Build History
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
Build History	Historique des constructions
(old value)

OUTDATED

Check File Fingerprint
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
Check File Fingerprint	Vérifier les empreintes numériques
(old value)

OUTDATED

Delete View
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
Delete View	Supprimer la vue
(old value)

OUTDATED

Edit View
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
Edit View	Éditer la vue
(old value)

OUTDATED

People
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
People	Utilisateurs
(old value)

OUTDATED

Project Relationship
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
Project Relationship	Relations entre les projets
(old value)

CURRENT

NewJob
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
New {0}	Nouveau {0}

core/src/main/resources/hudson/model/labels/LabelAtom/configure_fr.properties

Files

CURRENT

Name
04.02.2013 00:16:07, no SCM information	30.05.2013 20:09:20, no SCM information
Name	Nom

CURRENT

Save
04.02.2013 00:16:07, no SCM information	30.05.2013 20:09:20, no SCM information
Save	Sauver

CURRENT

title
04.02.2013 00:16:07, no SCM information	30.05.2013 20:09:20, no SCM information
{0} Config	{0} Configuration

core/src/main/resources/hudson/model/queue/Messages.properties (Master)

Files

MISSING

QueueSorter.installDefaultQueueSorter
04.02.2013 00:16:07, no SCM information
Installing default queue sorter

core/src/main/resources/hudson/node_monitors/AbstractDiskSpaceMonitor/config_fr.properties

Files

help-freeSpaceThreshold.html

CURRENT

Free Space Threshold
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Free Space Threshold	Seuil d''espace libre

core/src/main/resources/hudson/node_monitors/AbstractDiskSpaceMonitor/help-freeSpaceThreshold.html (Master)

Files

MISSING

04.02.2013 00:16:07, no SCM information
<div> This option configures the amount of minimum amount of free disk space desired for a slave's proper operation, such as "1.5GB", "100KB", etc. If a slave is found to have less free disk space than this amount, it will be marked offline. </div>

core/src/main/resources/hudson/node_monitors/ArchitectureMonitor/help.html (Master)

Files

MISSING

04.02.2013 00:16:07, no SCM information
<div> This monitor just shows the architecture of the slave for your information. It never marks the slave offline. </div>

core/src/main/resources/hudson/node_monitors/ClockMonitor/help.html (Master)

Files

MISSING

04.02.2013 00:16:07, no SCM information
<div> This monitors the clock difference between the master and nodes. While Jenkins itself is generally capable of tolerating clock differences between systems, version control activities and distributed file access (such as NFS, Windows file shares) tend to have strange problems when systems involved have different clocks. <p> To keep clocks in sync, refer to NTP. </div>

core/src/main/resources/hudson/node_monitors/DiskSpaceMonitor/help.html (Master)

Files

MISSING

04.02.2013 00:16:07, no SCM information
<div> This monitors the available disk space of <tt>$JENKINS_HOME</tt> on each slave, and if it gets below a threshold, the slave will be marked offline. <p> This directory is where all your builds are performed, so if it fills up, all the builds will fail. </div>

core/src/main/resources/hudson/node_monitors/DiskSpaceMonitorDescriptor/DiskSpace/cause.jelly (Master)

Files

MISSING

blurb
04.02.2013 00:16:07, no SCM information
Disk space is too low. Only {0}GB left on {1}.

core/src/main/resources/hudson/node_monitors/Messages_fr.properties

Files

MISSING

AbstractNodeMonitorDescriptor.NoDataYet
01.08.2013 07:43:47, no SCM information
Not yet

MISSING

DiskSpaceMonitor.MarkedOnline
01.08.2013 07:43:47, no SCM information
Putting {0} back online as there is enough disk space again

MISSING

TemporarySpaceMonitor.DisplayName
01.08.2013 07:43:47, no SCM information
Free Temp Space

OUTDATED

ArchitectureMonitor.DisplayName
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Architecture	Architecture
(old value)

OUTDATED

ClockMonitor.DisplayName
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Clock Difference	Différence entre les horloges
(old value)

OUTDATED

DiskSpaceMonitor.DisplayName
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Free Disk Space	Espace disque disponible
(old value)

OUTDATED

DiskSpaceMonitor.MarkedOffline
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Making {0} offline temporarily due to the lack of disk space	Déconnexion temporaire de {0} par cause de manque d''espace disque
(old value)

OUTDATED

ResponseTimeMonitor.DisplayName
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Response Time	Temps de réponse
(old value)

OUTDATED

ResponseTimeMonitor.MarkedOffline
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Making {0} offline because it’s not responding	{0} est marqué comme déconnecté temporairement, parce qu''il ne répond pas
(old value)

OUTDATED

ResponseTimeMonitor.TimeOut
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Time out for last {0} try	Time out du dernier essai {0}
(old value)

OUTDATED

SwapSpaceMonitor.DisplayName
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Free Swap Space	Espace de swap disponible
(old value)

core/src/main/resources/hudson/node_monitors/MonitorMarkedNodeOffline/message_fr.properties

Files

MISSING

blurb
01.08.2013 07:43:47, no SCM information
Jenkins took some slaves offline because <a href="{0}/computer/">their key health metrics</a> went below a threshold. If you don’t want Jenkins to do this, <a href="{0}/computer/configure">change the setting</a>.

CURRENT

Dismiss
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Dismiss	Cacher

core/src/main/resources/hudson/node_monitors/ResponseTimeMonitor/Data/cause.jelly (Master)

Files

MISSING

Ping response time is too long or timed out.
04.02.2013 00:16:07, no SCM information
Ping response time is too long or timed out.

core/src/main/resources/hudson/node_monitors/ResponseTimeMonitor/help.html (Master)

Files

MISSING

04.02.2013 00:16:07, no SCM information

<div>
This monitors the round trip network response time from the master to the slave, and if it
goes above a threshold repeatedly, it marks the slave offline.

<p>
This is useful for detecting unresponsive slaves, or other network problems that clog the
communication channel. More specifically, the master sends a no-op command to the slave,
and checks the time it takes to get back the result of this no-op command.
</div>

core/src/main/resources/hudson/node_monitors/SwapSpaceMonitor/help.html (Master)

Files

MISSING

04.02.2013 00:16:07, no SCM information

<div>
This monitors the available virtual memory space of the computer (commonly known as "swap space"),
and if it goes below a threshold, the slave is marked offline.

<p>
The exact definition of the swap space is platform dependent.

<ul>
<li>
On Windows, this value is
<a href="http://msdn.microsoft.com/en-us/library/aa366589(VS.85).aspx">the available space in the page file</a>,
but because Windows is capable of expanding the page file size automatically, the value doesn't really mean much.

<li>
On Linux, this value is obtained from <tt>/proc/meminfo</tt>.

<li>
On other Unix systems, this value is obtained by executing the <tt>top</tt> command.
</ul>

<p>
If you have an operating system where this value is not reported, please let us know so that we can improve this.
</div>

core/src/main/resources/hudson/node_monitors/TemporarySpaceMonitor/help.html (Master)

Files

MISSING

04.02.2013 00:16:07, no SCM information

<div>
This monitors the available disk space of the temporary directory, and if it gets below a certain threshold
the node will be made offline.

<p>
Java tools and tests/builds often create files in the temporary directory, and may not function
properly if there's no available space.

<p>
More specifically, it checks the available disk space of a partition
that includes directory designated by the <tt>java.io.tmpdir</tt> system property.
To check where this directory is on a given slave, go to <tt>${rootURL}/computer/SLAVENAME/systemInfo</tt>.
</div>

core/src/main/resources/hudson/os/solaris/ZFSInstaller/MigrationCompleteNotice/message_fr.properties

Files

EMPTY

OK
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
OK	—

CURRENT

Data was successfully migrated to ZFS.
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Data was successfully migrated to ZFS.	Les données ont été transferrées sur ZFS.

core/src/main/resources/hudson/os/solaris/ZFSInstaller/MigrationFailedNotice/index_fr.properties

Files

CURRENT

ZFS Migration Problem
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
ZFS Migration Problem	Problème de migration ZFS

core/src/main/resources/hudson/os/solaris/ZFSInstaller/MigrationFailedNotice/message_fr.properties

Files

askRootPassword_fr.properties

MISSING

See the log for more details
04.02.2013 00:16:07, no SCM information
See the log for more details

CURRENT

ZFS migration failed.
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
ZFS migration failed.	La migration ZFS a échoué.

core/src/main/resources/hudson/os/solaris/ZFSInstaller/askRootPassword_fr.properties

Files

askRootPassword.jelly

EMPTY

OK
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
OK	—

CURRENT

Password
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Password	Mot de passe

CURRENT

Permission Denied
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Permission Denied	Permission refusée

CURRENT

See errors...
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
See errors...	Voir les erreurs...

CURRENT

Username
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Username	Nom d''utilisateur

CURRENT

blurb
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
It appears that the current user account lacks necessary permissions to create a ZFS file system. Please provide the username and the password that's capable of doing this, such as root.	Il semble que le compte utilisateur courant n''a pas les permissions nécessaires pour créer un système de fichier ZFS. Veuillez renseigner un nom d''utilisateur et mot de passe qui le peut, comme root par exemple.

core/src/main/resources/hudson/os/solaris/ZFSInstaller/confirm_fr.properties

Files

confirm.jelly

confirm_fr.properties

CURRENT

Restart itself so that the migration can be done without worrying about concurrent data modifications
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Restart itself so that the migration can be done without worrying about concurrent data modifications	Redémarrage afin d''éviter les problèmes de modifications de données concurrentes pendant la migration

CURRENT

Start migration
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Start migration	Démarrer la migration

CURRENT

You will need the root password of the system to do this.
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
You will need the root password of the system to do this.	Vous aurez besoin du mot de passe root pour faire cela.

CURRENT

ZFS file system creation
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
ZFS file system creation	Création du système de fichier ZFS

CURRENT

blurb
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Jenkins will perform the following steps to migrate your existing data to a ZFS file system.	Jenkins exécutera les étapes suivantes pour migrer vos données existantes vers un système ZFS.

CURRENT

create
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Create a new ZFS file system <tt>{0}</tt> and copy all the data into it	Créer un nouveau système de fichier ZFS <tt>{0}</tt> et y copier toutes les données

CURRENT

delete
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Delete <tt>{0}.backup</tt>	Supprimer <tt>{0}.backup</tt>

CURRENT

mount
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Mount a new ZFS file system at <tt>{0}</tt>	Monter un système de fichier ZFS sur <tt>{0}</tt>

CURRENT

rename
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Rename <tt>{0}</tt> to <tt>{0}.backup</tt>	Renommer <tt>{0}</tt> en <tt>{0}.backup</tt>

core/src/main/resources/hudson/os/solaris/ZFSInstaller/message_fr.properties

Files

CURRENT

No, thank you
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
No, thank you	Non, merci

CURRENT

Yes, please
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Yes, please	Oui !

CURRENT

blurb
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
You are running on Solaris. Would you like Jenkins to create a ZFS file system for you so that you can get the most out of Solaris?	Vous êtes sur Solaris. Voulez-vous que Jenkins crée un système de fichier ZFS afin que vous puissiez tirer parti de Solaris au maximum ?

core/src/main/resources/hudson/os/windows/ManagedWindowsServiceAccount/AnotherUser/config.groovy (Master)

Files

MISSING

Password
04.02.2013 00:16:07, no SCM information
Password

MISSING

User name
04.02.2013 00:16:07, no SCM information
User name

core/src/main/resources/hudson/os/windows/ManagedWindowsServiceConnector/config.jelly (Master)

Files

MISSING

Administrator user name
04.02.2013 00:16:07, no SCM information
Administrator user name

MISSING

Password
04.02.2013 00:16:07, no SCM information
Password

core/src/main/resources/hudson/os/windows/ManagedWindowsServiceLauncher/AccountInfo/config.groovy (Master)

Files

MISSING

Password
04.02.2013 00:16:07, no SCM information
Password

MISSING

User name
04.02.2013 00:16:07, no SCM information
User name

core/src/main/resources/hudson/os/windows/ManagedWindowsServiceLauncher/config_fr.properties

Files

MISSING

JVM options
04.02.2013 00:16:07, no SCM information
JVM options

MISSING

Path to java executable
04.02.2013 00:16:07, no SCM information
Path to java executable

MISSING

Run service as
04.02.2013 00:16:07, no SCM information
Run service as

MISSING

blurb
04.02.2013 00:16:07, no SCM information
This launch method relies on DCOM and is often associated with <a href="https://wiki.jenkins-ci.org/display/JENKINS/Windows+slaves+fail+to+start+via+DCOM" target="_blank">subtle problems</a>. Consider using <b>Launch slave agents using Java Web Start</b> instead, which also permits installation as a Windows service but is generally considered more reliable.

ORPHANED

Log on using a different account
	04.02.2013 00:16:07, no SCM information
	Se connecter en utilisant un utilisateur différent

ORPHANED

User name
	04.02.2013 00:16:07, no SCM information
	Nom d''utilisateur

CURRENT

Administrator user name
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Administrator user name	Nom de l''utilisateur administrateur

CURRENT

Host
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Host	Hôte

CURRENT

Password
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Password	Mot de passe

core/src/main/resources/hudson/os/windows/ManagedWindowsServiceLauncher/help-host_fr.html

Files

help-host.html

help-host_fr.html

CURRENT

04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
<div> Provide the host name of the Windows host if different to the name of the Slave. </div>	<div> Fournissez le nom de la machine Windows s'il est différent du nom de l'esclave. </div>

core/src/main/resources/hudson/os/windows/ManagedWindowsServiceLauncher/help-javaPath.html (Master)

Files

help-javaPath.html

MISSING

28.02.2013 15:26:35, no SCM information
<div> Path to the Java executable to be used on this node. Defaults to "java", assuming JRE is installed and available on system PATH (i.e. C:\Windows\system32\java.exe in most cases) </div>

core/src/main/resources/hudson/os/windows/ManagedWindowsServiceLauncher/help-logOn.html (Master)

Files

help-logOn.html

MISSING

04.02.2013 00:16:07, no SCM information

<div>
Sometimes the administrator account that can install a service remotely
might not be the user account you want to run your Jenkins slave
(one reason you might want to do this is to run your builds/tests in more restricted account
because you don't trust them. Another reason you might want to do this is to run
slaves in some domain user account.)

This option lets you do this. If left unchecked, this Jenkins slave will
run as the 'SYSTEM' user, who has full access to the local system.
</div>

core/src/main/resources/hudson/os/windows/ManagedWindowsServiceLauncher/help-userName_fr.html

Files

help-userName.html

help-userName_fr.html

CURRENT

04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
<div> Provide the name of the Windows user who has the administrative access on this computer, such as 'Administrator'. This information is necessary to start a process remotely. <p> To specify a domain user, enter values like 'DOMAIN\Administrator'. </div>	<div> Fournissez le nom d'un utilisateur Windows qui a des droits d'accès en administration sur cet ordinateur, par exemple 'Administrator'. Cette information est nécessaire pour démarrer un processus à distance. <p> Quand vous donnez le nom d'un utilisateur sur le domaine, entrez des valeurs du type 'DOMAIN\Administrator'. </div>

core/src/main/resources/hudson/os/windows/ManagedWindowsServiceLauncher/help_fr.properties

Files

help.jelly

help_fr.properties

CURRENT

blurb
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Starts a Windows slave by <a href="http://en.wikipedia.org/wiki/Windows_Management_Instrumentation">a remote management facility</a> built into Windows. Suitable for managing Windows slaves. Slaves need to be IP reachable from the master.	Lance un esclave Windows en utilisant <a href="http://en.wikipedia.org/wiki/Windows_Management_Instrumentation">un système de gestion à distance</a> intégré à Windows. Cela convient uniquement pour gérer des esclaves sous Windows. Les esclaves doivent être accessibles par IP par le maître.

core/src/main/resources/hudson/os/windows/Messages_fr.properties

Files

MISSING

ManagedWindowsServiceLauncher.AccessDenied
04.02.2013 00:16:07, no SCM information
Access is denied. See http://wiki.jenkins-ci.org/display/JENKINS/Windows+slaves+fail+to+start+via+DCOM for more information about how to resolve this.

MISSING

ManagedWindowsServiceLauncher.CopyingSlaveJar
04.02.2013 00:16:07, no SCM information
Copying slave.jar

MISSING

ManagedWindowsServiceLauncher.UnregisteringService
04.02.2013 00:16:07, no SCM information
Unregistering the service

CURRENT

ManagedWindowsServiceLauncher.ConnectingTo
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Connecting to {0}	Connexion à {0}

CURRENT

ManagedWindowsServiceLauncher.ConnectingToPort
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Connecting to port {0}	Connexion au port {0}

CURRENT

ManagedWindowsServiceLauncher.CopyingSlaveExe
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Copying jenkins-slave.exe	Copie de jenkins-slave.exe

CURRENT

ManagedWindowsServiceLauncher.CopyingSlaveXml
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Copying jenkins-slave.xml	Copie de jenkins-slave.xml

CURRENT

ManagedWindowsServiceLauncher.DisplayName
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Let Jenkins control this Windows slave as a Windows service	Permet à Jenkins de contrôler cet esclave Windows en tant que service Windows

CURRENT

ManagedWindowsServiceLauncher.DotNetRequired
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
.NET Framework 2.0 or later is required on this computer to run a Jenkins slave as a Windows service	Le Framework .NET version 2.0 ou plus est nécessaire sur cet ordinateur pour lancer un esclave Jenkins en tant que service Windows

CURRENT

ManagedWindowsServiceLauncher.InstallingSlaveService
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Installing the Jenkins slave service	Installation du service esclave Windows

CURRENT

ManagedWindowsServiceLauncher.RegisteringService
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Registering the service	Enregistrement du service

CURRENT

ManagedWindowsServiceLauncher.ServiceDidntRespond
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
The service did not respond. Perhaps it failed to launch?	Le service n''a pas répondu. Peut-être n''a-t-il pas pu se lancer?

CURRENT

ManagedWindowsServiceLauncher.StartingService
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Starting the service	Démarrage du service

CURRENT

ManagedWindowsServiceLauncher.StoppingService
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Stopping the service	Arrêt du service

CURRENT

ManagedWindowsServiceLauncher.WaitingForService
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Waiting for the service to become ready	Attente que le service soit disponible

core/src/main/resources/hudson/scheduler/Messages_fr.properties

Files

MISSING

CronTab.do_you_really_mean_every_minute_when_you
29.04.2013 12:15:14, no SCM information
Do you really mean "every minute" when you say "{0}"? Perhaps you meant "{1}"

MISSING

CronTab.spread_load_evenly_by_using_rather_than_
29.04.2013 12:15:14, no SCM information
Spread load evenly by using ‘{0}’ rather than ‘{1}’

OUTDATED

BaseParser.MustBePositive
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
step must be positive, but found {0}	L''interval doit être une valeur positive. {0} est incorrect
(old value)

OUTDATED

BaseParser.OutOfRange
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
{0} is an invalid value. Must be within {1} and {2}	{0} est une valeur invalide. Elle doit être comprise entre {1} et {2}
(old value)

OUTDATED

BaseParser.StartEndReversed
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
You mean {0}-{1}?	Voulez-vous dire {0}-{1}?
(old value)

OUTDATED

CronTabList.InvalidInput
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
Invalid input: "{0}": {1}	Entrée invalide: "{0}": {1}
(old value)

core/src/main/resources/hudson/scm/AbstractScmTagAction/inProgress_fr.properties

Files

inProgress.jelly

inProgress_fr.properties

CURRENT

Tagging is in progress:
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Tagging is in progress:	Application d''un nom (tag) est en cours:

core/src/main/resources/hudson/scm/EmptyChangeLogSet/digest_fr.properties

Files

digest.jelly

digest_fr.properties

CURRENT

No changes.
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
No changes.	Aucun changement.

core/src/main/resources/hudson/scm/Messages_fr.properties

Files

project-changes_fr.properties

CURRENT

NullSCM.DisplayName
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
None	Aucune

CURRENT

SCM.Permissions.Title
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
SCM	Gestion de version

CURRENT

SCM.TagPermission.Description
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
This permission allows users to create a new tag in the source code repository for a given build.	Cette option permet aux utilisateurs de crÃ©er un nouveau tag dans l''outil de gestion de code source pour un build donnÃ©.

core/src/main/resources/hudson/scm/SCM/project-changes_fr.properties

Files

project-changes.jelly

OUTDATED

No builds.
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
No builds.	Aucun build.
(old value)

OUTDATED

No changes in any of the builds.
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
No changes in any of the builds.	Aucun changement dans les builds.
(old value)

OUTDATED

detail
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
detail	détail
(old value)

core/src/main/resources/hudson/search/Messages.properties (Master)

Files

MISSING

UserSearchProperty.DisplayName
04.02.2013 00:16:07, no SCM information
Setting for search

core/src/main/resources/hudson/search/Search/search-failed.jelly (Master)

Files

search-failed.jelly

MISSING

Nothing seems to match.
04.02.2013 00:16:07, no SCM information
Nothing seems to match.

MISSING

Search for
04.02.2013 00:16:07, no SCM information
Search for

core/src/main/resources/hudson/search/UserSearchProperty/config.jelly (Master)

Files

MISSING

Case-sensitivity
04.02.2013 00:16:07, no SCM information
Case-sensitivity

MISSING

Insensitive search tool
04.02.2013 00:16:07, no SCM information
Insensitive search tool

core/src/main/resources/hudson/security/AuthorizationMatrixProperty/config_fr.properties

Files

CURRENT

Enable project-based security
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Enable project-based security	Activer la sécurité basée projet

core/src/main/resources/hudson/security/FederatedLoginService/UnclaimedIdentityException/error.jelly (Master)

Files

error.jelly

MISSING

blurb
04.02.2013 00:16:07, no SCM information
{0} "{1}" is not associated with any of the Jenkins user account. Note that if you already have a user account and is trying to associate a {0} with your account, this is a wrong place. To do so, <ol><li>Login <li>Click on your name <li>Click on the "Configure" link, and then <li>associate a new {0} from that page</ol>

MISSING

loginError
04.02.2013 00:16:07, no SCM information
Login Error: unassociated {0}

core/src/main/resources/hudson/security/GlobalMatrixAuthorizationStrategy/config_fr.properties

Files

MISSING

Toggle all
04.02.2013 00:16:07, no SCM information
Toggle all

CURRENT

Add
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Add	Ajouter

CURRENT

Anonymous
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Anonymous	Anonyme

CURRENT

Remove user/group
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Remove user/group	Supprimer utilisateur/groupe

CURRENT

User/group
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
User/group	Utilisateur/groupe

CURRENT

User/group to add
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
User/group to add	Utilisateur/groupe à ajouter

core/src/main/resources/hudson/security/GlobalMatrixAuthorizationStrategy/help_fr.html

Files

CURRENT

04.02.2013 00:16:07, no SCM information

<div>
In this scheme, you can configure who can do what by using a big table.

<p>
Each column represents a permission. Hover the mouse over the permission names to get
more information about what they represent.

<p>
Each row represents a user or a group (often called 'role', depending on the security realm.)
This includes a special user 'anonymous', which represents unauthenticated users, as well
as 'authenticated', which represents all authenticated users (IOW, everyone except anonymous users.)
Use the text box below the table to add new users/groups/roles to the table, and click the
<tt>[x]</tt> icon to remove it from the table.

<p>
Permissions are additive. That is, if an user X is in group A, B, and C, then
the permissions that this user actually has are the union of all permissions given to
X, A, B, C, and anonymous.
</div>

<div>

Cette option vous permet de configurer qui fait quoi dans un grand tableau.

<p>
Chaque colonne représente une autorisation. Faites glisser la souris au
dessus du nom d'une autorisation pour obtenir plus d'information sur
ce qu'elle représente.

<p>
Chaque ligne représente un utilisateur ou un groupe (souvent appelé
'rôle', selon les royaumes -realms- de sécurité).
On y trouve un utilisateur spécial 'anonymous' qui représente
les utilisateurs non authentifiés, ainsi qu'un utilisateur 'authenticated',
qui représente les utilisateurs authentifiés (c-à-d, tout le monde, à
l'exception des utilisateurs anonymes).
Utilisez le texte sous la table pour ajouter des nouveaux
utilisateurs/groupes/rôles à la table et cliquez sur l'icône
<tt>[x]</tt> pour les supprimer.

<p>
Les autorisations s'ajoutent les unes aux autres. En clair, si un
utilisateur X est présent dans les groupes A, B et C, alors les
autorisations associées à cet utilisateur sont l'union de toutes les
autorisations accordées à X, A, B, C et anonymous.
</div>

core/src/main/resources/hudson/security/GlobalSecurityConfiguration/config_fr.properties

Files

help-slaveAgentPort_fr.html

ORPHANED

Default view
	24.02.2013 10:14:59, no SCM information
	Vue par défaut

ORPHANED

Global properties
	24.02.2013 10:14:59, no SCM information
	Propriétés globales

ORPHANED

Home directory
	24.02.2013 10:14:59, no SCM information
	Répertoire Home

ORPHANED

JDK installations
	24.02.2013 10:14:59, no SCM information
	Installations des JDK

ORPHANED

JDKs
	24.02.2013 10:14:59, no SCM information
	JDK

ORPHANED

LOADING
	24.02.2013 10:14:59, no SCM information
	CHARGEMENT

ORPHANED

List of JDK installations on this system
	24.02.2013 10:14:59, no SCM information
	Liste des installations de JDK sur ce système.

ORPHANED

System Message
	24.02.2013 10:14:59, no SCM information
	Message du système

ORPHANED

name
	24.02.2013 10:14:59, no SCM information
	Nom

ORPHANED

no.such.JDK
	24.02.2013 10:14:59, no SCM information
	<span class=error>Ce JDK n''existe pas</span>

ORPHANED

statsBlurb
	24.02.2013 10:14:59, no SCM information
	Aidez-nous à améliorer Jenkins en envoyant sous forme anonyme les statistiques d''utilisation et les rapports de crash au projet Jenkins.

core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-slaveAgentPort_fr.html

Files

help-slaveAgentPort.html

CURRENT

04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
<div> Jenkins uses a TCP port to communicate with slave agents launched via JNLP. Normally this port is chosen randomly to avoid collisions, but this would make securing the system difficult. If you are not using JNLP slaves, it's recommend to disable this TCP port. Alternatively, you can specify the fixed port number so that you can configure your firewall accordingly. </div>	<div> Jenkins utilise un port TCP pour communiquer avec les agents-esclaves lancés par JNLP. Normalement, ce numéro de port est choisi au hasard pour éviter les collisions, mais cela peut compliquer la sécurisation du système. Vous pouvez donc spécifier un numéro de port fixe afin de permettre la configuration de votre firewall. </div>

core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity_fr.html

Files

help-useSecurity.html

help-useSecurity_fr.html

CURRENT

04.02.2013 00:16:07, no SCM information

<div>
If enabled, you have to login with a username and a password that has the "admin" role
before changing the configuration or running a new build (look for the "login" link
at the top right portion of the page).
Configuration of user accounts is specific to the web container you are using.
(For example, in Tomcat, by default, it looks for <tt>$TOMCAT_HOME/conf/tomcat-users.xml</tt>)

<p>
If you are using Jenkins in an intranet (or other "trusted" environment), it's usually
desirable to leave this checkbox off, so that each project developer can configure their own
project without bothering you.

<p>
If you are exposing Jenkins to the internet, you must turn this on. Jenkins launches
processes, so insecure Jenkins is a sure way of being hacked.

<p>
For more information about security and Jenkins, see
<a href="http://wiki.jenkins-ci.org/display/JENKINS/Securing+Jenkins">this document</a>.
</div>

<div>
Si cette option est activée, vous devrez vous connecter avec un nom d'utilisateur
et un mot de passe qui ont le rôle "admin" pour pouvoir changer la configuration ou
lancer un nouveau build (utiliser le lien "login" en haut à droite de cette page).
La configuration des comptes utilisateurs est spécifique au conteneur web que vous
utilisez. Par exemple, par défaut, Tomcat utilise
<tt>$TOMCAT_HOME/conf/tomcat-users.xml</tt>).

<p>
Si vous utilisez Jenkins sur un intranet (ou d'autres environnements "de confiance"),
il est souvent préférable de laisser cette case décochée, ce qui permet à chaque
développeur de configurer son propre projet sans vous déranger.

<p>
Si vous exposez Jenkins sur internet, vous devez activer cette option. Jenkins lance des
processes, donc une installation non-sécurisée de Jenkins est un bon moyen d'attirer
les hackers.

<p>
Pour plus d'informations sur la sécurité dans Jenkins, voir
<a href="http://wiki.jenkins-ci.org/display/JENKINS/Securing+Jenkins">ce document</a>.
</div>

core/src/main/resources/hudson/security/GlobalSecurityConfiguration/index_fr.properties

Files

index.groovy

EMPTY

Markup Formatter
04.02.2013 00:16:07, no SCM information	08.02.2013 16:23:41, no SCM information
Markup Formatter	—

CURRENT

Access Control
04.02.2013 00:16:07, no SCM information	08.02.2013 16:23:41, no SCM information
Access Control	Contrôle de l''accès

CURRENT

Authorization
04.02.2013 00:16:07, no SCM information	08.02.2013 16:23:41, no SCM information
Authorization	Autorisations

CURRENT

Enable security
04.02.2013 00:16:07, no SCM information	08.02.2013 16:23:41, no SCM information
Enable security	Activer la sécurité

CURRENT

LOADING
04.02.2013 00:16:07, no SCM information	08.02.2013 16:23:41, no SCM information
LOADING	CHARGEMENT

CURRENT

Save
04.02.2013 00:16:07, no SCM information	08.02.2013 16:23:41, no SCM information
Save	Enregistrer

CURRENT

Security Realm
04.02.2013 00:16:07, no SCM information	08.02.2013 16:23:41, no SCM information
Security Realm	Royaume pour la sécurité (Realm)

CURRENT

TCP port for JNLP slave agents
04.02.2013 00:16:07, no SCM information	08.02.2013 16:23:41, no SCM information
TCP port for JNLP slave agents	Port TCP pour les agents esclaves JNLP

core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/Details/config_fr.properties

Files

CURRENT

Confirm Password
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Confirm Password	Confirmer le mot de passe

CURRENT

Password
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Password	Mot de passe

core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/_entryForm_fr.properties

Files

_entryForm.jelly

_entryForm_fr.properties

MISSING

Sign up
04.02.2013 00:16:07, no SCM information
Sign up

EMPTY

Enter text as shown
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Enter text as shown	—

CURRENT

Confirm password
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Confirm password	Confirmation du mot de passe

CURRENT

E-mail address
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
E-mail address	Adresse mél

CURRENT

Full name
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Full name	Nom

CURRENT

Password
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Password	Mot de passe

CURRENT

Username
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Username	Nom d''utilisateur

core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/addUser_fr.properties

Files

addUser.jelly

addUser_fr.properties

CURRENT

Create User
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Create User	Créer un utilisateur

core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/config_fr.properties

Files

MISSING

Captcha Support
04.02.2013 00:16:07, no SCM information
Captcha Support

MISSING

Enable captcha on sign up
04.02.2013 00:16:07, no SCM information
Enable captcha on sign up

CURRENT

Allow users to sign up
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Allow users to sign up	Autoriser les utilisateurs à s''inscrire

core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/firstUser.jelly (Master)

Files

firstUser.jelly

MISSING

Create First Admin User
04.02.2013 00:16:07, no SCM information
Create First Admin User

core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/index_fr.properties

Files

MISSING

User Id
29.04.2013 12:15:14, no SCM information
User Id

OUTDATED

Name
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
Name	Nom
(old value)

OUTDATED

Users
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
Users	Utilisateurs
(old value)

CURRENT

blurb
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
These users can log into Jenkins. This is a sub set of <a href="../asynchPeople">this list</a>, which also contains auto-created users who really just made some commits on some projects and have no direct Jenkins access.	Ces utilisateurs peuvent se logguer sur Jenkins. C''est le groupe contenant <a href="../asynchPeople">cette liste</a>, qui contient également les utilisateus créés automatiquement qui ont simplement fait des commits sur certains projets et n''ont pas d''accès direct à Jenkins.

core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/loginLink_fr.properties

Files

loginLink.jelly

loginLink_fr.properties

CURRENT

sign up
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
sign up	Créer un compte

core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/sidepanel_fr.properties

Files

signupWithFederatedIdentity.jelly

CURRENT

Back to Dashboard
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Back to Dashboard	Retour au tableau de bord

CURRENT

Create User
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Create User	Créer un utilisateur

CURRENT

Manage Jenkins
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Manage Jenkins	Administrer Jenkins

core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/signup_fr.properties

Files

signup.jelly

signup_fr.properties

CURRENT

Sign up
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Sign up	S''inscrire

core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/signupWithFederatedIdentity_fr.properties

Files

signupWithFederatedIdentity_fr.properties

CURRENT

Sign up
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Sign up	S''inscrire

core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/success_fr.properties

Files

success.jelly

success_fr.properties

CURRENT

Success
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Success	Succès

CURRENT

description
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
You are now logged in. Go back to <a href="..">the top page</a>.	Vous êtes maintenant connecté. Retournez à <a href="..">la page principale</a>.

core/src/main/resources/hudson/security/LegacySecurityRealm/config.jelly (Master)

Files

MISSING

Unprotected URLs
04.02.2013 00:16:07, no SCM information
Unprotected URLs

MISSING

blurb
04.02.2013 00:16:07, no SCM information
These URLs (and URLs starting with these prefixes plus a /) should require no authentication. If possible, configure your container to pass these requests straight to Jenkins without requiring login.

core/src/main/resources/hudson/security/Messages_fr.properties

Files

MISSING

AccessDeniedException2.MissingPermission
01.08.2013 07:43:47, no SCM information
{0} is missing the {1} permission

MISSING

HudsonPrivateSecurityRealm.CreateAccount.InvalidEmailAddress
01.08.2013 07:43:47, no SCM information
Invalid e-mail address

MISSING

HudsonPrivateSecurityRealm.CreateAccount.PasswordNotMatch
01.08.2013 07:43:47, no SCM information
Password didn't match

MISSING

HudsonPrivateSecurityRealm.CreateAccount.PasswordRequired
01.08.2013 07:43:47, no SCM information
Password is required

MISSING

HudsonPrivateSecurityRealm.CreateAccount.TextNotMatchWordInImage
01.08.2013 07:43:47, no SCM information
Text didn't match the word shown in the image

MISSING

HudsonPrivateSecurityRealm.CreateAccount.UserNameAlreadyTaken
01.08.2013 07:43:47, no SCM information
User name is already taken

MISSING

HudsonPrivateSecurityRealm.CreateAccount.UserNameRequired
01.08.2013 07:43:47, no SCM information
User name is required

MISSING

HudsonPrivateSecurityRealm.WouldYouLikeToSignUp
01.08.2013 07:43:47, no SCM information
This {0} {1} is new to Jenkins. Would you like to sign up?

MISSING

LDAPSecurityRealm.InvalidPortNumber
01.08.2013 07:43:47, no SCM information
Invalid port number

MISSING

LDAPSecurityRealm.SyntaxOfServerField
01.08.2013 07:43:47, no SCM information
Syntax of server field is SERVER or SERVER:PORT or ldaps://SERVER[:PORT]

MISSING

LDAPSecurityRealm.UnableToConnect
01.08.2013 07:43:47, no SCM information
Unable to connect to {0} : {1}

MISSING

LDAPSecurityRealm.UnknownHost
01.08.2013 07:43:47, no SCM information
Unknown host: {0}

MISSING

PAMSecurityRealm.BelongToGroup
01.08.2013 07:43:47, no SCM information
{0} needs to belong to group {1} to read /etc/shadow

MISSING

PAMSecurityRealm.CurrentUser
01.08.2013 07:43:47, no SCM information
Current User

MISSING

PAMSecurityRealm.ReadPermission
01.08.2013 07:43:47, no SCM information
Jenkins needs to be able to read /etc/shadow

MISSING

PAMSecurityRealm.RunAsUserOrBelongToGroupAndChmod
01.08.2013 07:43:47, no SCM information
Either Jenkins needs to run as {0} or {1} needs to belong to group {2} and ‘chmod g+r /etc/shadow’ needs to be done to enable Jenkins to read /etc/shadow

MISSING

PAMSecurityRealm.Success
01.08.2013 07:43:47, no SCM information
Success

MISSING

PAMSecurityRealm.Uid
01.08.2013 07:43:47, no SCM information
uid: {0}

MISSING

PAMSecurityRealm.User
01.08.2013 07:43:47, no SCM information
User ‘{0}’

OUTDATED

AuthorizationStrategy.DisplayName
01.08.2013 07:43:47, no SCM information	05.03.2013 12:11:24, no SCM information
Anyone can do anything	Tout le monde a accès à toutes les fonctionnalités
(old value)

OUTDATED

FullControlOnceLoggedInAuthorizationStrategy.DisplayName
01.08.2013 07:43:47, no SCM information	05.03.2013 12:11:24, no SCM information
Logged-in users can do anything	Les utilisateurs connectés peuvent tout faire
(old value)

OUTDATED

GlobalMatrixAuthorizationStrategy.DisplayName
01.08.2013 07:43:47, no SCM information	05.03.2013 12:11:24, no SCM information
Matrix-based security	Sécurité basée sur une matrice
(old value)

OUTDATED

GlobalSecurityConfiguration.Description
01.08.2013 07:43:47, no SCM information	05.03.2013 12:11:24, no SCM information
Secure Jenkins; define who is allowed to access/use the system.	Sécuriser Jenkins; définir qui est autorisé à accéder au système.
(old value)

OUTDATED

GlobalSecurityConfiguration.DisplayName
01.08.2013 07:43:47, no SCM information	05.03.2013 12:11:24, no SCM information
Configure Global Security	Configurer la sécurité globale
(old value)

OUTDATED

HudsonPrivateSecurityRealm.Details.DisplayName
01.08.2013 07:43:47, no SCM information	05.03.2013 12:11:24, no SCM information
Password	Mot de passe
(old value)

OUTDATED

HudsonPrivateSecurityRealm.Details.PasswordError
01.08.2013 07:43:47, no SCM information	05.03.2013 12:11:24, no SCM information
The confirmed password is not the same as the one entered. Please make sure to type the same password twice.	Le mot de passe de confirmation n''est pas le même que le premier mot de passe. Merci de vous assurer que les mots de passe sont les mêmes dans les deux cases.
(old value)

OUTDATED

HudsonPrivateSecurityRealm.DisplayName
01.08.2013 07:43:47, no SCM information	05.03.2013 12:11:24, no SCM information
Jenkins’s own user database	Base de données des utilisateurs de Jenkins
(old value)

OUTDATED

HudsonPrivateSecurityRealm.ManageUserLinks.Description
01.08.2013 07:43:47, no SCM information	05.03.2013 12:11:24, no SCM information
Create/delete/modify users that can log in to this Jenkins	Créer/supprimer/modifier les utilisateurs qui peuvent se logger sur ce serveur Jenkins
(old value)

OUTDATED

HudsonPrivateSecurityRealm.ManageUserLinks.DisplayName
01.08.2013 07:43:47, no SCM information	05.03.2013 12:11:24, no SCM information
Manage Users	Gérer les utilisateurs
(old value)

OUTDATED

LDAPSecurityRealm.DisplayName
01.08.2013 07:43:47, no SCM information	05.03.2013 12:11:24, no SCM information
LDAP	LDAP
(old value)

OUTDATED

LegacyAuthorizationStrategy.DisplayName
01.08.2013 07:43:47, no SCM information	05.03.2013 12:11:24, no SCM information
Legacy mode	Mode legacy
(old value)

OUTDATED

LegacySecurityRealm.Displayname
01.08.2013 07:43:47, no SCM information	05.03.2013 12:11:24, no SCM information
Delegate to servlet container	Déléguer au conteneur de servlets
(old value)

OUTDATED

PAMSecurityRealm.DisplayName
01.08.2013 07:43:47, no SCM information	05.03.2013 12:11:24, no SCM information
Unix user/group database	Base de données des utilisateurs & des groupes Unix
(old value)

OUTDATED

Permission.Permissions.Title
01.08.2013 07:43:47, no SCM information	05.03.2013 12:11:24, no SCM information
N/A	N/A
(old value)

OUTDATED

ProjectMatrixAuthorizationStrategy.DisplayName
01.08.2013 07:43:47, no SCM information	05.03.2013 12:11:24, no SCM information
Project-based Matrix Authorization Strategy	Stratégie d''authorisation matricielle basée sur les projets
(old value)

OUTDATED

UserDetailsServiceProxy.UnableToQuery
01.08.2013 07:43:47, no SCM information	05.03.2013 12:11:24, no SCM information
Unable to query user information: {0}	Impossible de récupérer les informations utilisateur: {0}
(old value)

core/src/main/resources/hudson/security/ProjectMatrixAuthorizationStrategy/help.html (Master)

Files

MISSING

04.02.2013 00:16:07, no SCM information

<div>
This mode is an extension to "Matrix-based security" that allows additional ACL matrix to be defined
for each project separately (which is done on the job configuration screen.)

<p>
This allows you to say things like "Joe can access project A, B, and C but he can't see D."
See the help of "Matrix-based security" for the concept of matrix-based security in general.

<p>
ACLs are additive, so the access rights granted below will be effective for all the projects.
</div>

core/src/main/resources/hudson/security/SecurityRealm/loginLink_fr.properties

Files

loginLink.jelly

loginLink_fr.properties

CURRENT

login
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
log in	S''identifier

core/src/main/resources/hudson/security/csrf/DefaultCrumbIssuer/config_fr.properties

Files

help-excludeClientIPFromCrumb.html

CURRENT

Enable proxy compatibility
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Enable proxy compatibility	Activer la compatibilité proxy

core/src/main/resources/hudson/security/csrf/DefaultCrumbIssuer/help-excludeClientIPFromCrumb.html (Master)

Files

MISSING

04.02.2013 00:16:07, no SCM information
<div> Some HTTP proxies filter out information that the default crumb issuer uses to calculate the nonce value. If an HTTP proxy sits between your browser client and your Jenkins server and you receive a 403 response when submitting a form to Jenkins, checking this option may help. Using this option makes the nonce value easier to forge. </div>

core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/config_fr.properties

Files

MISSING

Crumb Algorithm
19.02.2013 07:05:52, no SCM information
Crumb Algorithm

MISSING

Crumbs
19.02.2013 07:05:52, no SCM information
Crumbs

OUTDATED

Prevent Cross Site Request Forgery exploits
19.02.2013 07:05:52, no SCM information	04.02.2013 00:16:07, no SCM information
Prevent Cross Site Request Forgery exploits	Se protéger contre les exploits de type Cross Site Request Forgery
(old value)

core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/help-csrf.html (Master)

Files

help-csrf.html

MISSING

04.02.2013 00:16:07, no SCM information

<div>
A cross site request forgery (or CSRF/XSRF) is an exploit that enables
an unauthorized third party to take actions on a web site as you. In Jenkins,
this could allow someone to delete jobs, builds or change Jenkins' configuration.
<p>
When this option is enabled, Jenkins will check for a generated nonce value, or
"crumb", on any request that may cause a change on the Jenkins server. This
includes any form submission and calls to the remote API.
<p>
More information about CSRF exploits can be found <a href="http://www.owasp.org/index.php/Cross-Site_Request_Forgery">here</a>.
</div>

core/src/main/resources/hudson/security/csrf/Messages.properties (Master)

Files

MISSING

DefaultCrumbIssuer.DisplayName
04.02.2013 00:16:07, no SCM information
Default Crumb Issuer

core/src/main/resources/hudson/slaves/AbstractCloudImpl/help-instanceCapStr.html (Master)

Files

help-instanceCapStr.html

MISSING

04.02.2013 00:16:07, no SCM information

<div>
You can place the upward limit to the number of slaves that Jenkins may launch from this cloud.
This is useful for avoiding surprises in the billing statement.

<P>
For example, if this field is 3, Jenkins will only launch a new instance
as long as total number of instances you run on this cloud doesn't exceed this number. In this way,
even in the worst case of Jenkins starting instances and forgetting about them,
you have an upper bound in the number of instances that are concurrently executed.

<p>
Leave this field empty to remove a cap.
</div>

core/src/main/resources/hudson/slaves/CommandConnector/config.jelly (Master)

Files

MISSING

Launch command
04.02.2013 00:16:07, no SCM information
Launch command

core/src/main/resources/hudson/slaves/CommandLauncher/config_fr.properties

Files

CURRENT

Launch command
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Launch command	Commande de lancement

core/src/main/resources/hudson/slaves/CommandLauncher/help-command_fr.html

Files

help-command.html

help-command_fr.html

OUTDATED

28.02.2013 15:26:35, no SCM information	04.02.2013 00:16:07, no SCM information
<div> Command to be used to launch a slave agent program, which controls the slave computer and communicates with the master. Jenkins assumes that the executed program launches the <tt>slave.jar</tt> program on the correct slave machine. <p> A copy of <tt>slave.jar</tt> can be downloaded from <a href="${rootURL}/jnlpJars/slave.jar"><tt>here</tt></a>. <p> In a simple case, this could be something like "ssh <i>hostname</i> java -jar ~/bin/slave.jar". However, it is often a good idea to write a small shell script, like the following, on a slave so that you can control the location of Java and/or slave.jar, as well as set up any environment variables specific to this slave node, such as PATH. <pre> #!/bin/sh exec java -jar ~/bin/slave.jar </pre> <p> You can use any command to run a process on the slave machine, such as RSH, as long as stdin/stdout of this process will be connected to "java -jar ~/bin/slave.jar" eventually. <p> In a larger deployment, it is also worth considering to load <tt>slave.jar</tt> from a NFS-mounted common location, so that you don't have to update this file every time you update Jenkins. <p> Setting this to "ssh -v <i>hostname</i>" may be useful for debugging connectivity issue. </div>	<div> La commande à utiliser pour lancer un agent esclave, qui contrôle la machine-esclave et communique avec la machine-maître. <h3>Les agents esclaves JNLP</h3> <p> Laissez ce champ vide si vous souhaitez lancer les esclaves par JNLP. Avec cette configuration, la page d'information sur les esclaves (jenkins/computer/***/) aura une icône de lancement JNLP. Vous pouvez cliquer sur ce lien pour lancer un agent esclave par JNLP. <p> Ce mode est utile pour les esclaves Windows qui n'ont généralement pas de mécanisme d'exécution à distance. <h3>Les agents esclaves ssh/rsh</h3> <p> Quand une commande est spécifiée dans ce champ, elle est exécutée sur le maître et Jenkins suppose que le programme exécuté lance le programme <tt>slave.jar</tt> sur la bonne machine esclave. <p> Une copie du <tt>slave.jar</tt> est disponible dans le répertoire <a href="${rootURL}/jnlpJars/slave.jar"><tt>WEB-INF/slave.jar</tt></a>. <p> Pour un cas simple, cette commande pourrait être du type "ssh <i>hostname</i> java -jar ~/bin/slave.jar". Cela dit, il est généralement préférable d'écrire un petit script sur l'esclave, comme celui qui suit, afin de gérer le répertoire d'installation de Java et/ou de slave.jar. Vous pouvez aussi positionner des variables d'environnement spécifiques à cette machine esclave, comme le PATH. <pre> #!/bin/sh exec java -jar ~/bin/slave.jar </pre> <p> Vous pouvez utiliser n'importe quelle commande d'exécution d'un process sur la machine-esclave, comme RSH, du moment que les sorties stdin/stdout de ce process sont au final connectées sur "java -jar ~/bin/slave.jar". <p> Dans un déploiement à plus grande échelle, on peut envisager de charger <tt>slave.jar</tt> à partir d'une location commune montée par NFS, afin de ne pas nécessiter la mise à jour de ce fichier à chaque mise à jour de Jenkins. <p> Mettre la valeur "ssh -v <i>hostname</i>" dans ce champ peut être utile pour débugger les problèmes de connexion. </div>
(old value)

core/src/main/resources/hudson/slaves/CommandLauncher/help_fr.properties

Files

help.jelly

help_fr.properties

CURRENT

blurb
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Starts a slave by having Jenkins execute a command from the master. Use this when the master is capable of remotely executing a process on a slave, such as through ssh/rsh.	Lance un esclave en demandant à Jenkins d''exécuter une commande à partir de la machine maître. Utilisez cela quand le maître est capable d''exécuter à distance des processus sur la machine esclave, par exemple par ssh/rsh.

core/src/main/resources/hudson/slaves/ComputerLauncher/main_fr.properties

Files

MISSING

Relaunch slave agent
04.02.2013 00:16:07, no SCM information
Relaunch slave agent

MISSING

launchingDescription
04.02.2013 00:16:07, no SCM information
This node is being launched.

CURRENT

Launch slave agent
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Launch slave agent	Lancer l''agent esclave

CURRENT

See log for more details
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
See log for more details	Voir les logs pour plus de détails

core/src/main/resources/hudson/slaves/DelegatingComputerLauncher/config.jelly (Master)

Files

MISSING

Actual launch method
04.02.2013 00:16:07, no SCM information
Actual launch method

core/src/main/resources/hudson/slaves/DumbSlave/configure-entries_fr.properties

Files

newInstanceDetail_fr.properties

EMPTY

Description
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Description	—

CURRENT

# of executors
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
# of executors	Nb d''exécuteurs

CURRENT

Availability
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Availability	Disponibilité

CURRENT

Labels
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Labels	Étiquettes

CURRENT

Launch method
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Launch method	Méthode de lancement

CURRENT

Node Properties
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Node Properties	Propriétés du nœud

CURRENT

Remote FS root
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Remote FS root	Répertoire de travail du système distant

core/src/main/resources/hudson/slaves/DumbSlave/newInstanceDetail_fr.properties

Files

newInstanceDetail.jelly

OUTDATED

detail
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Adds a plain, dumb slave to Jenkins. This is called "dumb" because Jenkins doesn’t provide higher level of integration with these slaves, such as dynamic provisioning. Select this type if no other slave types apply — for example such as when you are adding a physical computer, virtual machines managed outside Jenkins, etc.	Ajoute un esclave simple à Jenkins. Cet esclave est dit "passif" ("dumb") car Jenkins ne fournit pas d''intégration d''un niveau plus élevé pour ce type d''esclave, comme le provisioning dynamique. Sélectionnez ce type si aucun autre type d''esclave ne s''applique — par exemple quand vous ajoutez un ordinateur physique, une machine virtuelle gérée séparément de Jenkins, etc.
(old value)

core/src/main/resources/hudson/slaves/EnvironmentVariablesNodeProperty/config_fr.properties

Files

CURRENT

List of key-value pairs
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
List of key-value pairs	Liste des paires clé-valeur

CURRENT

name
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
name	nom

CURRENT

value
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
value	valeur

core/src/main/resources/hudson/slaves/JNLPLauncher/config_fr.properties

Files

CURRENT

JVM options
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
JVM options	Options de la JVM

CURRENT

Tunnel connection through
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Tunnel connection through	Connexion par tunnel via

core/src/main/resources/hudson/slaves/JNLPLauncher/help-vmargs_fr.html

Files

help-vmargs.html

help-vmargs_fr.html

CURRENT

04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
<div> If the slave JVM should be launched with additional VM arguments, such as "-Xmx256m", specify those here. List of all the options are available <a href="http://java.sun.com/javase/technologies/hotspot/vmoptions.jsp" target="_new">here</a>. </div>	<div> Si la JVM esclave doit être lancée avec des arguments supplémentaires, comme "-Xmx256m", indiquez-les ici. La liste de toutes options disponibles est disponible <a href="http://java.sun.com/javase/technologies/hotspot/vmoptions.jsp" target="_new">ici</a>. </div>

core/src/main/resources/hudson/slaves/JNLPLauncher/help_fr.properties

Files

help.jelly

help_fr.properties

CURRENT

blurb
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Starts a slave by launching an agent program through <a href="http://en.wikipedia.org/wiki/Java_Web_Start">JNLP</a>. The launch in this case is initiated by the slave, thus slaves need not be IP reachable from the master (e.g. behind the firewall.) It is still possible to start a launch without GUI, for example as a Windows service.	Lance un esclave en démarrant un agent par <a href="http://en.wikipedia.org/wiki/Java_Web_Start">JNLP</a>. Le lancement dans ce cas est initié par l''esclave ; ainsi, les esclaves n''ont pas besoin d''être accessibles par IP par la machine maître (par exemple s''ils sont derrière un firewall.) Il reste possible de lancer un démarrage sans GUI, par exemple par un service Windows.

core/src/main/resources/hudson/slaves/JNLPLauncher/main_fr.properties

Files

MISSING

Connect slave to Jenkins one of these ways:
14.06.2013 07:43:03, no SCM information
Connect slave to Jenkins one of these ways:

MISSING

Launch agent from browser on slave
14.06.2013 07:43:03, no SCM information
Launch agent from browser on slave

MISSING

Or if the slave is headless:
14.06.2013 07:43:03, no SCM information
Or if the slave is headless:

MISSING

Run from slave command line:
14.06.2013 07:43:03, no SCM information
Run from slave command line:

OUTDATED

Connected via JNLP agent.
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:07, no SCM information
Connected via JNLP agent.	Connecté via l''agent JNLP.
(old value)

OUTDATED

launch agent
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:07, no SCM information
launch agent	lancer l''agent
(old value)

CURRENT

configure.link.text
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Go to system config screen and change it	Allez à l''écran de configuration du système et changez-le

CURRENT

slaveAgentPort.disabled
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
TCP port for JNLP slave agents is disabled.	Le port TCP pour l''esclave JNLP est désactivé.

core/src/main/resources/hudson/slaves/Messages_fr.properties

Files

MISSING

ComputerLauncher.JavaVersionResult
01.08.2013 07:43:47, no SCM information
{0} -version returned {1}.

MISSING

ComputerLauncher.NoJavaFound
01.08.2013 07:43:47, no SCM information
Java version {0} was found but 1.5 or later is needed.

MISSING

ComputerLauncher.UknownJavaVersion
01.08.2013 07:43:47, no SCM information
Couldn’t figure out the Java version of {0}

MISSING

ConnectionActivityMonitor.OfflineCause
01.08.2013 07:43:47, no SCM information
Repeated ping attempts failed

MISSING

NodeDescripter.CheckName.Mandatory
01.08.2013 07:43:47, no SCM information
Name is mandatory

MISSING

NodeProvisioner.EmptyString
01.08.2013 07:43:47, no SCM information
—

MISSING

OfflineCause.DisconnectedFromCLI
01.08.2013 07:43:47, no SCM information
Disconnected from CLI

MISSING

RetentionStrategy.Demand.OfflineIdle
01.08.2013 07:43:47, no SCM information
Offline because computer was idle; it will be relaunched when needed.

MISSING

SimpleScheduledRetentionStrategy.FinishedUpTime
01.08.2013 07:43:47, no SCM information
Computer has finished its scheduled uptime

MISSING

SlaveComputer.DisconnectedBy
01.08.2013 07:43:47, no SCM information
Disconnected by {0}{1}

OUTDATED

CommandLauncher.NoLaunchCommand
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
No launch command specified	Aucune commande de lancement spécifiée
(old value)

OUTDATED

CommandLauncher.displayName
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
Launch slave via execution of command on the Master	Lancer l''esclave via l''exécution d''une commande sur le maître
(old value)

OUTDATED

ComputerLauncher.abortedLaunch
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
Launching slave process aborted.	Lancement de l''esclave annulé.
(old value)

OUTDATED

ComputerLauncher.unexpectedError
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
Unexpected error in launching a slave. This is probably a bug in Jenkins	Erreur inattendue au lancement d''un esclave. Probablement un bug dans Jenkins
(old value)

OUTDATED

DumbSlave.displayName
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
Dumb Slave	Esclave passif
(old value)

OUTDATED

EnvironmentVariablesNodeProperty.displayName
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
Environment variables	Variables d''environnement
(old value)

OUTDATED

JNLPLauncher.displayName
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
Launch slave agents via Java Web Start	Lancer les agents esclaves par JNLP
(old value)

OUTDATED

OfflineCause.LaunchFailed
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
This node is offline because Jenkins failed to launch the slave agent on it.	Ce noeud est déconnecté parce que Jenkins n''a pas réussi à lancer l''agent esclave dessus.
(old value)

OUTDATED

RetentionStrategy.Always.displayName
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
Keep this slave on-line as much as possible	Garder cet esclave en ligne autant que possible
(old value)

OUTDATED

RetentionStrategy.Demand.displayName
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
Take this slave on-line when in demand and off-line when idle	Mettre cet esclave en ligne à la demande et hors-ligne si inutilisé
(old value)

OUTDATED

SimpleScheduledRetentionStrategy.displayName
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
Take this slave on-line according to a schedule	Déconnecte cet esclave selon des horaires
(old value)

core/src/main/resources/hudson/slaves/OfflineCause/ChannelTermination/cause.jelly (Master)

Files

MISSING

Connection was broken
04.02.2013 00:16:07, no SCM information
Connection was broken

core/src/main/resources/hudson/slaves/OfflineCause/LaunchFailed/cause_fr.properties

Files

cause_fr.properties

CURRENT

See log for more details
04.02.2013 00:16:07, no SCM information	30.05.2013 20:09:20, no SCM information
See log for more details	Voir les logs pour plus de détails

core/src/main/resources/hudson/slaves/RetentionStrategy/Demand/config_fr.properties

Files

ORPHANED

Idle delay is mandatory.
	04.02.2013 00:16:07, no SCM information
	Le délai d''inactivité est obligatoire.

ORPHANED

In demand delay is mandatory.
	04.02.2013 00:16:07, no SCM information
	Le délai d''attente suite à une demande est obligatoire.

CURRENT

Idle delay
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Idle delay	Délai d''inactivité

CURRENT

Idle delay is mandatory and must be a number.
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Idle delay is mandatory and must be a number.	Le délai d''inactivité est obligatoire et doit être un nombre.

CURRENT

In demand delay
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
In demand delay	Délai d''attente lors d''une demande

CURRENT

In demand delay is mandatory and must be a number.
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
In demand delay is mandatory and must be a number.	Le délai d''attende est obligatoire et doit être un nombre.

core/src/main/resources/hudson/slaves/RetentionStrategy/Scheduled/config_fr.properties

Files

CURRENT

Shutdown Schedule
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Shutdown Schedule	Heure d''arrêt

CURRENT

Startup Schedule
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Startup Schedule	Heure de démarrage

core/src/main/resources/hudson/slaves/SimpleScheduledRetentionStrategy/config_fr.properties

Files

MISSING

Scheduled Uptime is mandatory and must be a number.
04.02.2013 00:16:07, no SCM information
Scheduled Uptime is mandatory and must be a number.

MISSING

uptime.description
04.02.2013 00:16:07, no SCM information
The number of minutes to keep the node up for. If this is longer than the startup schedule, then the node will remain constantly on-line.

ORPHANED

Scheduled Uptime is mandatory.
	04.02.2013 00:16:07, no SCM information
	La durée est obligatoire.

CURRENT

Keep on-line while jobs are running
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Keep on-line while jobs are running	Garder actif tant que des jobs sont en cours.

CURRENT

Scheduled Uptime
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Scheduled Uptime	Durée du mode actif

CURRENT

Startup Schedule
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Startup Schedule	Démarrage prévu

core/src/main/resources/hudson/slaves/SlaveComputer/disconnect_fr.properties

Files

disconnect.jelly

disconnect_fr.properties

MISSING

blurb
04.02.2013 00:16:07, no SCM information
You can optionally explain why you are taking this node offline, so that others can see why:

CURRENT

Are you sure about disconnecting?
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Are you sure about disconnecting?	Etes-vous sûr de vouloir vous déconnecter?

CURRENT

Yes
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Yes	Oui

CURRENT

disconnect
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
disconnect	déconnexion

core/src/main/resources/hudson/slaves/SlaveComputer/log.jelly (Master)

Files

log.jelly

MISSING

Log Records
23.07.2013 16:05:31, no SCM information
Log Records

core/src/main/resources/hudson/slaves/SlaveComputer/sidepanel2_fr.properties

Files

sidepanel2.jelly

sidepanel2_fr.properties

EMPTY

Log
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Log	—

CURRENT

Disconnect
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Disconnect	Déconnexion

CURRENT

System Information
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
System Information	Informations sur le système

core/src/main/resources/hudson/slaves/SlaveComputer/systemInfo_fr.properties

Files

systemInfo.jelly

systemInfo_fr.properties

CURRENT

Environment Variables
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Environment Variables	Variables d''environnement

CURRENT

System Information
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
System Information	Informations sur le système

CURRENT

System Properties
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
System Properties	Propriétés du système

CURRENT

Thread Dump
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Thread Dump	Dump du thread

core/src/main/resources/hudson/slaves/SlaveComputer/threadDump.jelly (Master)

Files

threadDump.jelly

MISSING

Thread Dump
04.02.2013 00:16:07, no SCM information
Thread Dump

MISSING

title
04.02.2013 00:16:07, no SCM information
{0} Thread Dump

core/src/main/resources/hudson/tasks/ArtifactArchiver/config_fr.properties

Files

help-allowEmptyArchive.html

MISSING

allowEmptyArchive
22.03.2013 09:10:52, no SCM information
Do not fail build if archiving returns nothing

OUTDATED

Excludes
22.03.2013 09:10:52, no SCM information	04.02.2013 00:16:07, no SCM information
Excludes	Excluant
(old value)

OUTDATED

Files to archive
22.03.2013 09:10:52, no SCM information	04.02.2013 00:16:07, no SCM information
Files to archive	Fichiers à archiver
(old value)

OUTDATED

lastBuildOnly
22.03.2013 09:10:52, no SCM information	04.02.2013 00:16:07, no SCM information
Discard all but the last successful/stable artifact to save disk space	Supprime tous les artefacts, à l''exception du dernier artefact stable ou construit avec succès, afin de gagner de l''espace disque
(old value)

core/src/main/resources/hudson/tasks/ArtifactArchiver/help-allowEmptyArchive.html (Master)

Files

MISSING

22.03.2013 09:10:52, no SCM information
<div> Normally, a build fails if archiving returns zero artifacts. This option allows the archiving process to return nothing without failing the build. Instead, the build will simply throw a warning. </div>

core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_fr.html

Files

help-artifacts.html

help-artifacts_fr.html

OUTDATED

29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
<div> You can use wildcards like 'module/dist/*/.zip'. See <a href='http://ant.apache.org/manual/Types/fileset.html'> the includes attribute of Ant fileset</a> for the exact format. The base directory is <a href='ws/'>the workspace</a>. You can only archive files that are located in your workspace. </div>	<div> Vous pouvez utilisez ici des wildcards du type 'module/dist/*/.zip'. Voir <a href='http://ant.apache.org/manual/Types/fileset.html'> les @includes d'un fileset Ant</a> pour le format exact. Le répertoire de base est <a href='ws/'>le workspace</a>. </div>
(old value)

core/src/main/resources/hudson/tasks/ArtifactArchiver/help-excludes_fr.html

Files

help-excludes.html

help-excludes_fr.html

CURRENT

04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
<div> Optionally specify <a href='http://ant.apache.org/manual/Types/fileset.html'>the 'excludes' pattern</a>, such as "foo/bar/*/". A file that matches this mask will not be archived even if it matches the mask specified in 'files to archive' section. </div>	<div> Spécifie <a href='http://ant.apache.org/manual/Types/fileset.html'>un pattern d'exclusion</a> optionel, du type "foo/bar/*/". Un fichier qui correspond à ce pattern ne sera pas archivé, même s'il correspond au masque spécifié dans la section 'fichiers à archiver'. </div>

core/src/main/resources/hudson/tasks/ArtifactArchiver/help-latestOnly_fr.html

Files

help-latestOnly.html

help-latestOnly_fr.html

CURRENT

04.02.2013 00:16:07, no SCM information

<div>
<p>
If checked, Jenkins will discard most artifacts from older builds.
Artifacts from the last stable former build (if any) are kept, and also those
from the last unstable build if that is newer, and from the last failed
build if that is newer.
</p>
<p>
This option saves disk space, but still lets you safely create permalinks
such as <code>.../lastStableBuild/artifact/...</code> or
<code>.../lastSuccessfulBuild/artifact/...</code> or
<code>.../lastCompletedBuild/artifact/...</code>.
</p>
<p>
(Since the current build is still running, Jenkins conservatively assumes
that it might yet fail in a publisher - so it keeps at least one older build's
artifacts around.)
</p>
</div>

<div>
<p>
Si cette option est activée, Jenkins supprimera la plupart des artefacts des
builds les plus anciens.
Les artefacts du dernier build stable (s'il existe) seront conservés, ainsi que
ceux du dernier build instable s'il est plus récent, et ceux du dernier build
en échec s'il est plus récent.
</p>
<p>
Cette option fait gagner de l'espace disque, tout en vous permettant de créer
des links permalinks sans problèmes, comme
<code>.../lastStableBuild/artifact/...</code> ou
<code>.../lastSuccessfulBuild/artifact/...</code> ou
<code>.../lastCompletedBuild/artifact/...</code>.
</p>
<p>
(Puisque le build courant est en cours, Jenkins suppose par précaution qu'il peut
échouer dans un publisher à la fin - il conserve donc les artefacts d'au moins
un build plus ancien.)
</p>
</div>

core/src/main/resources/hudson/tasks/ArtifactArchiver/help_fr.html

Files

OUTDATED

28.06.2013 06:41:00, no SCM information	04.02.2013 00:16:07, no SCM information
<div> Archives the build artifacts (for example, distribution zip files or jar files) so that they can be downloaded later. Archived files will be accessible from the Jenkins webpage. <br /> Normally, Jenkins keeps artifacts for a build as long as a build log itself is kept, but if you don't need old artifacts and would rather save disk space, you can do so. </div> <br/> <div> Note that the Maven job type automatically archives any produced Maven artifacts. Any artifacts configured here will be archived on top of that. Automatic artifact archiving can be disabled under the advanced Maven options. </div>	<div> Archive certains artefacts du build (par exemple, les fichiers zip de la distribution ou les fichiers jar) afin permettre leur téléchargement. Les fichiers archivés sont accessibles à partir de la page Jenkins du build. <br /> En général, Jenkins conserve les artefacts d'un build aussi longtemps que le log du build. Néanmoins, si vous n'avez pas besoin des vieux artefacts et préférez économiser de l'espace disque, il est possible de les supprimer. </div>
(old value)

core/src/main/resources/hudson/tasks/BatchFile/config_fr.properties

Files

CURRENT

Command
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Command	Commande

CURRENT

description
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
See <a href="{0}/env-vars.html" target=_new>the list of available environment variables</a>	Voir <a href="{0}/env-vars.html" target=_new>la liste des variables d''environnement disponibles</a>

core/src/main/resources/hudson/tasks/BuildTrigger/config_fr.properties

Files

OUTDATED

Projects to build
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:07, no SCM information
Projects to build	Projets à construire
(old value)

OUTDATED

Trigger even if the build fails
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:07, no SCM information
Trigger even if the build fails	Déclencher même si le build échoue
(old value)

OUTDATED

Trigger even if the build is unstable
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:07, no SCM information
Trigger even if the build is unstable	Déclencher même si le build est instable
(old value)

OUTDATED

Trigger only if build succeeds
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:07, no SCM information
Trigger only if build succeeds	Déclencher uniquement si le build réussit
(old value)

core/src/main/resources/hudson/tasks/Fingerprinter/FingerprintAction/index_fr.properties

Files

EMPTY

Age
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:07, no SCM information
Age	—

OUTDATED

File
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:07, no SCM information
File	Fichier
(old value)

OUTDATED

Original owner
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:07, no SCM information
Original owner	Propriétaire original
(old value)

OUTDATED

Recorded Fingerprints
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:07, no SCM information
Recorded Fingerprints	Empreintes numériques enregistrées
(old value)

OUTDATED

more details
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:07, no SCM information
more details	plus de détails
(old value)

OUTDATED

outside Jenkins
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:07, no SCM information
outside Jenkins	hors Jenkins
(old value)

OUTDATED

this build
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:07, no SCM information
this build	ce build
(old value)

core/src/main/resources/hudson/tasks/Fingerprinter/config_fr.properties

Files

OUTDATED

description
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Can use wildcards like ‘module/dist/*/.zip’. See the <a href="{0}">@includes of Ant fileset</a> for the exact format. The base directory is <a href="ws/">the workspace</a>.	Les wildcards du type ''module/dist/*/.zip'' sont autorisés. Voir le format exact des <a href="{0}">@includes des filesets Ants</a>. Le répertoire de base est le <a href="ws/">répertoire de travail (workspace)</a>.
(old value)

CURRENT

Files to fingerprint
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Files to fingerprint	Fichiers à marquer d''une empreinte numérique

CURRENT

Fingerprint all archived artifacts
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Fingerprint all archived artifacts	Marquer d''une empreinte numérique tous les artefacts archivés

CURRENT

Keep the build logs of dependencies
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Keep the build logs of dependencies	Conserver les logs de build des dépendances

core/src/main/resources/hudson/tasks/LogRotator/config_fr.properties

Files

MISSING

Days to keep artifacts
05.03.2013 12:11:24, no SCM information
Days to keep artifacts

MISSING

Max # of builds to keep with artifacts
05.03.2013 12:11:24, no SCM information
Max # of builds to keep with artifacts

MISSING

if not empty, artifacts from builds older than this number of days will be deleted, but the logs, history, reports, etc for the build will be kept
05.03.2013 12:11:24, no SCM information
if not empty, artifacts from builds older than this number of days will be deleted, but the logs, history, reports, etc for the build will be kept

MISSING

if not empty, only up to this number of builds have their artifacts retained
05.03.2013 12:11:24, no SCM information
if not empty, only up to this number of builds have their artifacts retained

OUTDATED

Days to keep builds
05.03.2013 12:11:24, no SCM information	04.02.2013 00:16:07, no SCM information
Days to keep builds	Nombre de jours de conservation des builds
(old value)

OUTDATED

Max # of builds to keep
05.03.2013 12:11:24, no SCM information	04.02.2013 00:16:07, no SCM information
Max # of builds to keep	Nombre maximum de builds à conserver
(old value)

OUTDATED

if not empty, build records are only kept up to this number of days
05.03.2013 12:11:24, no SCM information	04.02.2013 00:16:07, no SCM information
if not empty, build records are only kept up to this number of days	si non vide, les enregistrements de build seront conservés au maximum ce nombre de jours
(old value)

OUTDATED

if not empty, only up to this number of build records are kept
05.03.2013 12:11:24, no SCM information	04.02.2013 00:16:07, no SCM information
if not empty, only up to this number of build records are kept	si non vide, pas plus de ce nombre de builds ne sera conservé
(old value)

core/src/main/resources/hudson/tasks/Maven/MavenInstallation/config_fr.properties

Files

ORPHANED

List of Maven installations on this system. Both maven 1 and 2 are supported.
	04.02.2013 00:16:07, no SCM information
	Liste des installations de Maven sur ce système. Maven 1 et Maven 2 sont supportés tous les deux.

ORPHANED

Maven
	04.02.2013 00:16:07, no SCM information
	—

ORPHANED

Maven installation
	04.02.2013 00:16:07, no SCM information
	Installations de Maven

CURRENT

Name
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Name	Nom

core/src/main/resources/hudson/tasks/Maven/config_fr.properties

Files

MISSING

Global Settings file
18.05.2013 17:17:16, no SCM information
Global Settings file

MISSING

Settings file
18.05.2013 17:17:16, no SCM information
Settings file

EMPTY

POM
18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:07, no SCM information
POM	—

OUTDATED

Default
18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:07, no SCM information
Default	Par défaut
(old value)

OUTDATED

Goals
18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:07, no SCM information
Goals	Cibles Maven
(old value)

OUTDATED

JVM Options
18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:07, no SCM information
JVM Options	Options de la JVM
(old value)

OUTDATED

Maven Version
18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:07, no SCM information
Maven Version	Version de Maven
(old value)

OUTDATED

Properties
18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:07, no SCM information
Properties	Propriétés
(old value)

OUTDATED

Use private Maven repository
18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:07, no SCM information
Use private Maven repository	Utiliser un repository Maven privé
(old value)

core/src/main/resources/hudson/tasks/Maven/help-settings.html (Master)

Files

help-settings.html

MISSING

28.02.2013 15:26:35, no SCM information

<div>
The settings element in the <code>settings.xml</code> file contains elements used
to define values which configure Maven execution in various ways, like the <code>pom.xml</code>,
but should not be bundled to any specific project, or distributed to an audience.
These include values such as the local repository location, alternate remote repository servers,
and authentication information.
<br>
There are two locations where a <code>settings.xml</code> file per default may live:

<ul>
<li>The Maven install - default: <code>$M2_HOME/conf/settings.xml</code></li>
<li>A user's install - default: <code>${user.home}/.m2/settings.xml</code></li>
</ul>

The former settings.xml are also called global settings, the latter settings.xml are
referred to as user settings. If both files exists, their contents gets merged,
with the user-specific settings.xml being dominant.
<p>
see also: <a href="http://maven.apache.org/settings.html"><code>settings.xml</code> reference</a>
</div>

core/src/main/resources/hudson/tasks/Messages_fr.properties

Files

MISSING

ArtifactArchiver.ARCHIVING_ARTIFACTS
01.08.2013 07:43:47, no SCM information
Archiving artifacts

MISSING

BuildTrigger.NoProjectSpecified
01.08.2013 07:43:47, no SCM information
No project specified

MISSING

BuildTrigger.you_have_no_permission_to_build_
01.08.2013 07:43:47, no SCM information
You have no permission to build {0}

MISSING

InstallFromApache
01.08.2013 07:43:47, no SCM information
Install from Apache

OUTDATED

Ant.DisplayName
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Invoke Ant	Appeler Ant
(old value)

OUTDATED

Ant.ExecFailed
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
command execution failed.	L''exécution de la commande a échoué.
(old value)

OUTDATED

Ant.ExecutableNotFound
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Cannot find executable from the chosen Ant installation "{0}"	Impossible de trouver l''exécutable correspondant à l''installation de Ant choisie "{0}"
(old value)

OUTDATED

Ant.GlobalConfigNeeded
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Maybe you need to configure where your Ant installations are?	Avez-vous configuré l''endroit où se trouvent les installations de Ant?
(old value)

OUTDATED

Ant.NotADirectory
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
{0} is not a directory	{0} n''est pas un répertoire
(old value)

OUTDATED

Ant.NotAntDirectory
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
{0} doesn’t look like an Ant directory	{0} ne semble pas être un répertoire Ant
(old value)

OUTDATED

Ant.ProjectConfigNeeded
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Maybe you need to configure the job to choose one of your Ant installations?	Avez-vous configuré le job de façon à choisir une de vos installations de Ant?
(old value)

OUTDATED

ArtifactArchiver.DeletingOld
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Deleting old artifacts from {0}	Suppression des anciens artefacts de {0}
(old value)

OUTDATED

ArtifactArchiver.DisplayName
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Archive the artifacts	Archiver des artefacts
(old value)

OUTDATED

ArtifactArchiver.FailedToArchive
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Failed to archive artifacts: {0}	Echec lors de l''archivage des artefacts: {0}
(old value)

OUTDATED

ArtifactArchiver.NoIncludes
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
No artifacts are configured for archiving. You probably forgot to set the file pattern, so please go back to the configuration and specify it. If you really did mean to archive all the files in the workspace, please specify "**"	Aucun artefact n''est configuré pour l''archivage. Vous avez probablement oublié de positionner le pattern pour les noms des fichiers; merci de retourner à la configuration et de le spécifier. Si vous souhaitez réellement archiver tous les fichiers dans le workspace, indiquez "**".
(old value)

OUTDATED

ArtifactArchiver.NoMatchFound
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
No artifacts found that match the file pattern "{0}". Configuration error?	Aucun artefact ne correspond au pattern "{0}". Erreur de configuration?
(old value)

OUTDATED

BatchFile.DisplayName
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Execute Windows batch command	Exécuter une ligne de commande batch Windows
(old value)

OUTDATED

BuildTrigger.Disabled
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
{0} is disabled. Triggering skipped	{0} est désactivé. Lancement non fait.
(old value)

OUTDATED

BuildTrigger.DisplayName
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Build other projects	Construire d''autres projets (projets en aval)
(old value)

OUTDATED

BuildTrigger.InQueue
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
{0} is already in the queue	{0} est déjà en file d''attente
(old value)

OUTDATED

BuildTrigger.NoSuchProject
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
No such project ‘{0}’. Did you mean ‘{1}’?	Pas de projet ''{0}''. Vouliez-vous dire ''{1}''?
(old value)

OUTDATED

BuildTrigger.NotBuildable
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
{0} is not buildable	{0} ne peut pas être construit
(old value)

OUTDATED

BuildTrigger.Triggering
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Triggering a new build of {0}	Lancement d''un nouveau build de {0}
(old value)

OUTDATED

CommandInterpreter.CommandFailed
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
command execution failed	L''exécution de la commande a échoué.
(old value)

OUTDATED

CommandInterpreter.UnableToDelete
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Unable to delete script file {0}	Impossible de supprimer le fichier de script {0}
(old value)

OUTDATED

CommandInterpreter.UnableToProduceScript
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Unable to produce a script file	Impossible de produire un fichier de script
(old value)

OUTDATED

Fingerprinter.Aborted
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Aborted	Annulé
(old value)

OUTDATED

Fingerprinter.Action.DisplayName
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
See Fingerprints	Voir les empreintes numériques
(old value)

OUTDATED

Fingerprinter.DigestFailed
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Failed to compute digest for {0}	Impossible de calculer le résumé pour {0}
(old value)

OUTDATED

Fingerprinter.DisplayName
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Record fingerprints of files to track usage	Enregistrer les empreintes numériques des fichiers pour en suivre l''utilisation
(old value)

OUTDATED

Fingerprinter.Failed
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Failed to record fingerprints	Impossible d''enregistrer les empreintes numériques
(old value)

OUTDATED

Fingerprinter.FailedFor
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
failed to record fingerprint for {0}	Impossible d''enregistrer les empreintes numériques pour {0}
(old value)

OUTDATED

Fingerprinter.NoArchiving
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Build artifacts are supposed to be fingerprinted, but build artifact archiving is not configured	Les artefacts du build sont supposés recevoir une empreinte numérique, mais l''archivage n''a pas été activé
(old value)

OUTDATED

Fingerprinter.NoWorkspace
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Unable to record fingerprints because there’s no workspace	Impossible d''enregistrer les empreintes numériques, parce qu''il n''y a pas de répertoire de travail
(old value)

OUTDATED

Fingerprinter.Recording
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Recording fingerprints	Enregistrement des empreintes numériques
(old value)

OUTDATED

JavadocArchiver.DisplayName
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Publish Javadoc	Publier les Javadocs
(old value)

OUTDATED

JavadocArchiver.DisplayName.Generic
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Document	Documentation du code
(old value)

OUTDATED

JavadocArchiver.DisplayName.Javadoc
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Javadoc	Javadoc
(old value)

OUTDATED

JavadocArchiver.NoMatchFound
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
No javadoc found in {0}: {1}	Pas de javadoc trouvé dans {0}: {1}
(old value)

OUTDATED

JavadocArchiver.Publishing
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Publishing Javadoc	Publication des Javadocs
(old value)

OUTDATED

JavadocArchiver.UnableToCopy
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Unable to copy Javadoc from {0} to {1}	Impossible de copier les Javadocs de {0} vers {1}
(old value)

OUTDATED

Maven.DisplayName
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Invoke top-level Maven targets	Invoquer les cibles Maven de haut niveau
(old value)

OUTDATED

Maven.ExecFailed
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
command execution failed	L''exécution de la commande a échoué.
(old value)

OUTDATED

Maven.NoExecutable
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Couldn’t find any executable in {0}	Impossible de trouver un exécutable dans {0}
(old value)

OUTDATED

Maven.NotADirectory
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
{0} is not a directory	{0} n''est pas un répertoire
(old value)

OUTDATED

Maven.NotMavenDirectory
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
{0} doesn’t look like a Maven directory	{0} ne semble pas être un répertoire Maven
(old value)

OUTDATED

Shell.DisplayName
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Execute shell	Exécuter un script shell
(old value)

OUTDATED

TestJavadocArchiver.DisplayName.Javadoc
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Test Javadoc	Test Javadoc
(old value)

core/src/main/resources/hudson/tasks/Shell/config_fr.properties

Files

CURRENT

Command
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Command	Commande

CURRENT

description
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
See <a href="{0}/env-vars.html" target=_new>the list of available environment variables</a>	Voir <a href="{0}/env-vars.html" target=_new>la liste des variables d''environnement disponibles</a>

core/src/main/resources/hudson/tasks/Shell/global_fr.properties

Files

global.groovy

CURRENT

Shell
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Shell	Shell

CURRENT

Shell executable
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Shell executable	Exécutable pour le Shell

core/src/main/resources/hudson/tasks/Shell/help_fr.html

Files

CURRENT

04.02.2013 00:16:07, no SCM information

<div>
Runs a shell script (defaults to <tt>sh</tt>, but this is configurable) for building the project.
The script will be run with the workspace as the current directory. Type in the contents of your shell
script. If your shell script has no header line like <tt>#!/bin/sh</tt> —, then the shell configured
system-wide will be used, but you can also use the header line to write script in another language
(like <tt>#!/bin/perl</tt>) or control the options that shell uses.

<p>
By default, the shell will be invoked with the "-ex" option. So all of the commands are printed before being executed,
and the build is considered a failure if any of the commands exits with a non-zero exit code. Again, add the
<tt>#!/bin/...</tt> line to change this behavior.

<p>
As a best practice, try not to put a long shell script in here. Instead, consider adding the shell script
in SCM and simply call that shell script from Jenkins (via <tt>bash -ex myscript.sh</tt> or something like that),
so that you can track changes in your shell script.
</div>

<div>
Lance un script Shell (par d�faut � l'aide de <tt>sh</tt>, mais cela est configurable) pour construire le projet.
Le script sera lanc� avec le workspace comme r�pertoire courant.
Entrez le contenu de votre script shell. Si votre script n'a pas de ligne de titre du type <tt>#!/bin/sh</tt>,
alors le shell configur� pour l'ensemble du syst�me sera utilis�.
Si votre script contient une telle ligne, vous pourrez utiliser un autre langage de script
(comme <tt>#!/bin/perl</tt>) ou contr�ler les options que le shell utilise.

<p>
Par d�faut, le shell sera invoqu� avec l'option "-ex". Par cons�quent, toutes les commandes seront
affich�es avant d'�tre ex�cut�es et le build sera consid�r� en �chec si l'une de ces commandes
renvoie un code de retour diff�rent de z�ro.
Encore une fois, vous pouvez ajouter la ligne <tt>#!/bin/...</tt> pour modifier ce comportement.

<p>
Une bonne pratique est de ne pas mettre un long script ici. A la place, pensez � ajouter le script shell
dans l'outil de gestion de configuration et appelez simplement ce script depuis Jenkins.
Ainsi, vous garderez trace des changements apport�s � votre script.
</div>

core/src/main/resources/hudson/tasks/junit/CaseResult/index_fr.properties

Files

MISSING

Skip Message
18.05.2013 17:17:16, no SCM information
Skip Message

EMPTY

Stacktrace
18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:07, no SCM information
Stacktrace	—

OUTDATED

Error Message
18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:07, no SCM information
Error Message	Message d''erreur
(old value)

OUTDATED

Standard Error
18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:07, no SCM information
Standard Error	Sortie d''erreur standard
(old value)

OUTDATED

Standard Output
18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:07, no SCM information
Standard Output	Sortie standard
(old value)

CURRENT

failingFor
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Failing for the past {0} {0,choice,0#builds\|1#build\|1<builds}	En échec depuis {0} {0,choice,0#build\|1#build\|1<builds}

CURRENT

since.after
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
' '	' '

CURRENT

since.before
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Since' '	Depuis' '

CURRENT

skippedFor
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Skipped for the past {0} {0,choice,0#builds\|1#build\|1<builds}	Build sauté depuis {0} {0,choice,0#build\|1#build\|1<builds}

CURRENT

took
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Took {0}.	A duré {0}.

core/src/main/resources/hudson/tasks/junit/CaseResult/list_fr.properties

Files

list.jelly

list_fr.properties

OUTDATED

Build
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
Build	Construction
(old value)

OUTDATED

Test Description
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
Test Description	Description
(old value)

OUTDATED

Test Duration
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
Test Duration	Durée
(old value)

OUTDATED

Test Result
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
Test Result	Résultat
(old value)

core/src/main/resources/hudson/tasks/junit/CaseResult/summary.jelly (Master)

Files

summary.jelly

MISSING

Error Details
04.02.2013 00:16:07, no SCM information
Error Details

MISSING

Stack Trace
04.02.2013 00:16:07, no SCM information
Stack Trace

core/src/main/resources/hudson/tasks/junit/ClassResult/body_fr.properties

Files

body.jelly

body_fr.properties

OUTDATED

All Tests
18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:07, no SCM information
All Tests	Tous les tests
(old value)

OUTDATED

Duration
18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:07, no SCM information
Duration	Durée
(old value)

OUTDATED

Status
18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:07, no SCM information
Status	Statut
(old value)

OUTDATED

Test name
18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:07, no SCM information
Test name	Nom du test
(old value)

core/src/main/resources/hudson/tasks/junit/ClassResult/list.jelly (Master)

Files

list.jelly

MISSING

Build
29.04.2013 12:15:14, no SCM information
Build

MISSING

Description
29.04.2013 12:15:14, no SCM information
Description

MISSING

Duration
29.04.2013 12:15:14, no SCM information
Duration

MISSING

Fail
29.04.2013 12:15:14, no SCM information
Fail

MISSING

Skip
29.04.2013 12:15:14, no SCM information
Skip

MISSING

Total
29.04.2013 12:15:14, no SCM information
Total

core/src/main/resources/hudson/tasks/junit/History/index_fr.properties

Files

MISSING

More than 1 builds are needed for the chart.
04.02.2013 00:16:07, no SCM information
More than 1 builds are needed for the chart.

MISSING

Newer
04.02.2013 00:16:07, no SCM information
Newer

MISSING

Older
04.02.2013 00:16:07, no SCM information
Older

CURRENT

title
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
History for {0}	Historique pour {0}

core/src/main/resources/hudson/tasks/junit/JUnitResultArchiver/config_fr.properties

Files

MISSING

Retain long standard output/error
04.02.2013 00:16:07, no SCM information
Retain long standard output/error

OUTDATED

description
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
<a href="{0}">Fileset ‘includes’</a> setting that specifies the generated raw XML report files, such as ‘myproject/target/test-reports/*.xml’. Basedir of the fileset is <a href="ws/">the workspace root</a>.	Une configuration du type <a href="{0}">Fileset ''includes''</a> qui indique où se trouvent les fichiers XML des rapports de test, par exemple ''myproject/target/test-reports/*.xml''. Le répertoire de base (basedir) du fileset est <a href="ws/">la racine du workspace</a>.
(old value)

CURRENT

Test report XMLs
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Test report XMLs	XML des rapports de test

core/src/main/resources/hudson/tasks/junit/JUnitResultArchiver/help-keepLongStdio.html (Master)

Files

help-keepLongStdio.html

MISSING

04.02.2013 00:16:07, no SCM information

<div>
If checked, any standard output or error from a test suite will be retained
in the test results after the build completes. (This refers only to additional
messages printed to console, not to a failure stack trace.) Such output is
always kept if the test failed, but by default lengthy output from passing
tests is truncated to save space. Check this option if you need to see every
log message from even passing tests, but beware that Jenkins's memory consumption
can substantially increase as a result, even if you never look at the test results!
</div>

core/src/main/resources/hudson/tasks/junit/Messages_fr.properties

Files

MISSING

JUnitParser.DisplayName
04.02.2013 00:16:07, no SCM information
JUnit Parser

MISSING

JUnitParser.TestResultLocationMessage
04.02.2013 00:16:07, no SCM information
JUnit xml files:

MISSING

JUnitParser.no_workspace_found
04.02.2013 00:16:07, no SCM information
No workspace found for {0}

MISSING

JUnitResultArchiver.BadXML
04.02.2013 00:16:07, no SCM information
Incorrect XML attributes for test results found in {0}

MISSING

TestResult.getDisplayName
04.02.2013 00:16:07, no SCM information
Test Results

CURRENT

CaseResult.Status.Failed
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Failed	En échec

CURRENT

CaseResult.Status.Fixed
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Fixed	Corrigés

CURRENT

CaseResult.Status.Passed
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Passed	En succès

CURRENT

CaseResult.Status.Regression
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Regression	Régressions

CURRENT

CaseResult.Status.Skipped
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Skipped	Non lancés

CURRENT

ClassResult.getTitle
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Test Result : {0}	Résultats des tests : {0}

CURRENT

JUnitResultArchiver.DisplayName
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Publish JUnit test result report	Publier le rapport des résultats des tests JUnit

CURRENT

JUnitResultArchiver.NoTestReportFound
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
No test report files were found. Configuration error?	Aucun fichier de rapport de test n''a été trouvé. Erreur de configuration?

CURRENT

JUnitResultArchiver.Recording
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Recording test results	Enregistrement des résultats des tests

CURRENT

JUnitResultArchiver.ResultIsEmpty
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
None of the test reports contained any result	Aucun des rapports de test ne contient de résultat

CURRENT

PackageResult.getChildTitle
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Class	Class

CURRENT

PackageResult.getTitle
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Test Result : {0}	Résultats des tests : {0}

CURRENT

TestResult.getChildTitle
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Package	Package

CURRENT

TestResult.getTitle
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Test Result	Résultats des tests

core/src/main/resources/hudson/tasks/test/AbstractTestResultAction/summary_fr.properties

Files

summary.jelly

summary_fr.properties

OUTDATED

Show all failed tests
18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:07, no SCM information
Show all failed tests	Montrer tous les tests en échec
(old value)

core/src/main/resources/hudson/tasks/test/AggregatedTestResultPublisher/TestResultAction/index_fr.properties

Files

EMPTY

Fingerprinting not enabled on this build. Test aggregation requires fingerprinting.
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
Fingerprinting not enabled on this build. Test aggregation requires fingerprinting.	—

EMPTY

N/A
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
N/A	—

EMPTY

Test
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
Test	—

EMPTY

Total
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
Total	—

OUTDATED

Drill Down
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
Drill Down	En profondeur
(old value)

OUTDATED

Fail
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
Fail	Echec
(old value)

OUTDATED

last successful job is not fingerprinted
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
last successful job is not fingerprinted	le dernier job executé avec succès n''a pas d''empreinte numérique
(old value)

OUTDATED

test result not available
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
test result not available	les derniers résultats de test ne sont pas disponibles
(old value)

core/src/main/resources/hudson/tasks/test/AggregatedTestResultPublisher/config_fr.properties

Files

MISSING

Include failed builds in results
04.02.2013 00:16:07, no SCM information
Include failed builds in results

CURRENT

Automatically aggregate all downstream tests
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Automatically aggregate all downstream tests	Assembler automatiquement tous les tests en aval

CURRENT

Jobs to aggregate
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Jobs to aggregate	Jobs à consolider

core/src/main/resources/hudson/tasks/test/Messages_fr.properties

Files

CURRENT

AbstractTestResultAction.TestsDescription
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
{0}: {1} {1,choice,0#tests\|1#test\|1<tests} failing out of a total of {2} {2,choice,1#test\|1<tests}.	{0}: {1} tests en échec sur un total de {2} tests.

CURRENT

AbstractTestResultAction.fail
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
{0}: {1} {1,choice,0#failures\|1#failure\|1<failures}	{0}: {1} {1,choice,0#échec\|1#échec\|1<échecs}

CURRENT

AbstractTestResultAction.getDisplayName
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Test Result	Résultats des tests

CURRENT

AbstractTestResultAction.skip
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
{0}: {1} {1,choice,0#skips\|1#skip\|1<skips}	{0}: {1} {1,choice,0#ignoré\|1#ignoré\|1<ignorés}

CURRENT

AbstractTestResultAction.test
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
{0}: {1} {1,choice,0#tests\|1#test\|1<tests}	{0}: {1} {1,choice,0#tests\|1#test\|1<tests}

CURRENT

AbstractTestResultAction.zeroTestDescription
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
{0}: 0 tests in total.	{0}: 0 test au total.

CURRENT

AggregatedTestResultPublisher.DisplayName
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Aggregate downstream test results	Consolider les résultats des tests en aval

CURRENT

AggregatedTestResultPublisher.Title
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Aggregated Test Result	Résultats consolidés des tests

core/src/main/resources/hudson/tasks/test/MetaTabulatedResult/body_fr.properties

Files

body.jelly

body_fr.properties

OUTDATED

Age
18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:07, no SCM information
Age	Age
(old value)

OUTDATED

All Failed Tests
18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:07, no SCM information
All Failed Tests	Tous les tests qui ont échoué
(old value)

OUTDATED

All Tests
18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:07, no SCM information
All Tests	Tous les tests
(old value)

OUTDATED

Duration
18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:07, no SCM information
Duration	Durée
(old value)

OUTDATED

Fail
18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:07, no SCM information
Fail	Échec
(old value)

OUTDATED

Loading...
18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:07, no SCM information
Loading...	Chargement...
(old value)

OUTDATED

Skip
18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:07, no SCM information
Skip	Passé
(old value)

OUTDATED

Test Name
18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:07, no SCM information
Test Name	Nom du test
(old value)

OUTDATED

Total
18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:07, no SCM information
Total	Total
(old value)

OUTDATED

diff
18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:07, no SCM information
diff	diff
(old value)

core/src/main/resources/hudson/tasks/test/MetaTabulatedResult/list.jelly (Master)

Files

list.jelly

MISSING

Build
29.04.2013 12:15:14, no SCM information
Build

MISSING

Description
29.04.2013 12:15:14, no SCM information
Description

MISSING

Duration
29.04.2013 12:15:14, no SCM information
Duration

MISSING

Fail
29.04.2013 12:15:14, no SCM information
Fail

MISSING

Skip
29.04.2013 12:15:14, no SCM information
Skip

MISSING

Total
29.04.2013 12:15:14, no SCM information
Total

core/src/main/resources/hudson/tasks/test/TestObject/sidepanel_fr.properties

Files

CURRENT

History
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
History	Historique

CURRENT

Next Build
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Next Build	Build suivant

CURRENT

Previous Build
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Previous Build	Build Précédent

core/src/main/resources/hudson/tasks/test/TestResult/index_fr.properties

Files

floatingBox_fr.properties

CURRENT

took
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Took {0}.	A pris {0}.

core/src/main/resources/hudson/tasks/test/TestResultProjectAction/floatingBox_fr.properties

Files

floatingBox.jelly

CURRENT

Test Result Trend
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Test Result Trend	Tendance des résultats des tests

CURRENT

enlarge
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
enlarge	agrandir

CURRENT

just show failures
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
just show failures	montrer les échecs seulement

CURRENT

show test # and failure #
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
show test # and failure #	montrer tous les résultats des tests

core/src/main/resources/hudson/tools/CommandInstaller/config_fr.properties

Files

MISSING

Tool Home
04.02.2013 00:16:07, no SCM information
Tool Home

CURRENT

Command
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Command	Commande

core/src/main/resources/hudson/tools/CommandInstaller/help-command.html (Master)

Files

help-command.html

MISSING

04.02.2013 00:16:07, no SCM information
<div> Command to run on the slave node to install the tool. The command will always be run, so it should be a quick no-op if the tool is already installed. </div>

core/src/main/resources/hudson/tools/CommandInstaller/help-toolHome.html (Master)

Files

help-toolHome.html

MISSING

04.02.2013 00:16:07, no SCM information
<div> Resulting home directory of the tool. (May be a relative path if the command unpacked a tool in place.) </div>

core/src/main/resources/hudson/tools/CommandInstaller/help.html (Master)

Files

MISSING

04.02.2013 00:16:07, no SCM information

<p>
Runs a shell command of your choice to install the tool. Ubuntu example,
assuming the Jenkins user is in <code>/etc/sudoers</code>:
</p>
<pre>sudo apt-get --yes install openjdk-6-jdk</pre>
<p>
(In this case specify e.g. <code>/usr/lib/jvm/java-6-openjdk-i386</code> as the home directory.)
</p>
<p>
As another example, to install an older version of Sun JDK 6 for (x86) Linux,
you can use the obsolete <a href="http://jdk-distros.java.net/">DLJ</a>:
</p>
<pre>bin=jdk-6u13-dlj-linux-i586.bin
if [ \! -f $bin ]
then
wget --no-verbose http://download.java.net/dlj/binaries/$bin
sh $bin --unpack --accept-license
fi</pre>
<p>
(In this case specify <code>jdk1.6.0_13</code> as the home directory.)
</p>

core/src/main/resources/hudson/tools/DownloadFromUrlInstaller/config_fr.properties

Files

CURRENT

Version
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Version	Version

core/src/main/resources/hudson/tools/InstallSourceProperty/config_fr.properties

Files

CURRENT

Add Installer
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Add Installer	Ajouter un installateur

CURRENT

Delete Installer
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Delete Installer	Supprimer un installateur

core/src/main/resources/hudson/tools/InstallSourceProperty/help.html (Master)

Files

MISSING

04.02.2013 00:16:07, no SCM information

<div>
Choose this option to let Jenkins install this tool for you on demand,
to the location you configured above.

<p>
If you check this option, you'll then be asked to configure a series
of "installer"s for this tool, where each installer defines how
Jenkins will try to install this tool.

<p>
For a platform-independent tool (such as Ant), configuring multiple installers
for a single tool makes not much sense, but for a platform dependent tool,
multiple installer configurations allow you to run a different set up script
depending on the slave environment.
</div>

core/src/main/resources/hudson/tools/JDKInstaller/DescriptorImpl/credentialOK.jelly (Master)

Files

credentialOK.jelly

MISSING

Close
04.02.2013 00:16:07, no SCM information
Close

MISSING

Credential is saved
04.02.2013 00:16:07, no SCM information
Credential is saved

core/src/main/resources/hudson/tools/JDKInstaller/DescriptorImpl/enterCredential.jelly (Master)

Files

enterCredential.jelly

MISSING

Enter Your Oracle Account
04.02.2013 00:16:07, no SCM information
Enter Your Oracle Account

MISSING

OK
04.02.2013 00:16:07, no SCM information
OK

MISSING

Password
04.02.2013 00:16:07, no SCM information
Password

MISSING

Username
04.02.2013 00:16:07, no SCM information
Username

MISSING

description
04.02.2013 00:16:07, no SCM information
To access older versions of JDK, you need to have <a href="http://jenkins-ci.org/oracleAccountSignup">Oracle Account</a>.

core/src/main/resources/hudson/tools/JDKInstaller/config_fr.properties

Files

OUTDATED

I agree to the Java SE Development Kit License Agreement
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:07, no SCM information
I agree to the Java SE Development Kit License Agreement	J''approuve accord de licence Java SE Development Kit
(old value)

OUTDATED

Version
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:07, no SCM information
Version	Version
(old value)

core/src/main/resources/hudson/tools/Messages_fr.properties

Files

MISSING

CommandInstaller.DescriptorImpl.displayName
04.02.2013 00:16:07, no SCM information
Run Command

MISSING

CommandInstaller.no_command
04.02.2013 00:16:07, no SCM information
Must provide a command to run.

MISSING

CommandInstaller.no_toolHome
04.02.2013 00:16:07, no SCM information
Must provide a tool home directory.

MISSING

InstallSourceProperty.DescriptorImpl.displayName
04.02.2013 00:16:07, no SCM information
Install automatically

MISSING

JDKInstaller.DescriptorImpl.displayName
04.02.2013 00:16:07, no SCM information
Install from java.sun.com

MISSING

JDKInstaller.DescriptorImpl.doCheckAcceptLicense
04.02.2013 00:16:07, no SCM information
You must agree to the license to download the JDK.

MISSING

JDKInstaller.DescriptorImpl.doCheckId
04.02.2013 00:16:07, no SCM information
Define JDK ID

MISSING

JDKInstaller.FailedToInstallJDK
04.02.2013 00:16:07, no SCM information
Failed to install JDK. Exit code={0}

MISSING

JDKInstaller.RequireOracleAccount
04.02.2013 00:16:07, no SCM information
Installing JDK requires Oracle account. <a href="{0}" target="_new">Please enter your username/password</a>

MISSING

JDKInstaller.UnableToInstallUntilLicenseAccepted
04.02.2013 00:16:07, no SCM information
Unable to auto-install JDK until the license is accepted.

MISSING

ZipExtractionInstaller.DescriptorImpl.displayName
04.02.2013 00:16:07, no SCM information
Extract .zip/.tar.gz

MISSING

ZipExtractionInstaller.bad_connection
04.02.2013 00:16:07, no SCM information
Server rejected connection.

MISSING

ZipExtractionInstaller.could_not_connect
04.02.2013 00:16:07, no SCM information
Could not connect to URL.

MISSING

ZipExtractionInstaller.malformed_url
04.02.2013 00:16:07, no SCM information
Malformed URL.

CURRENT

ToolLocationNodeProperty.displayName
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Tool Locations	Emplacement des outils

core/src/main/resources/hudson/tools/ToolInstallation/config.jelly (Master)

Files

MISSING

Installation directory
04.02.2013 00:16:07, no SCM information
Installation directory

MISSING

Name
04.02.2013 00:16:07, no SCM information
Name

core/src/main/resources/hudson/tools/ToolInstallation/global_fr.properties

Files

global.jelly

CURRENT

description
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
List of {0} installations on this system	Nombre d''''installations {0} sur ce système

CURRENT

label.add
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Add {0}	Ajouter {0}

CURRENT

label.delete
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Delete {0}	Supprimer {0}

CURRENT

title
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
{0} installations	{0} installations

core/src/main/resources/hudson/tools/ToolLocationNodeProperty/config_fr.properties

Files

CURRENT

Home
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Home	Site

CURRENT

List of tool locations
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
List of tool locations	Liste des emplacements où les outils peuvent être trouvés

CURRENT

Name
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Name	Nom

core/src/main/resources/hudson/tools/ZipExtractionInstaller/config_fr.properties

Files

CURRENT

Download URL for binary archive
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Download URL for binary archive	URL de l''archive du binaire

CURRENT

Subdirectory of extracted archive
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Subdirectory of extracted archive	Sous-dossier d''extraction de l''archive

core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-subdir.html (Master)

Files

help-subdir.html

MISSING

04.02.2013 00:16:07, no SCM information
<div> Optional subdirectory of the downloaded and unpacked archive to use as the tool's home directory. </div>

core/src/main/resources/hudson/tools/ZipExtractionInstaller/help-url.html (Master)

Files

help-url.html

MISSING

04.02.2013 00:16:07, no SCM information
<div> URL from which to download the tool in binary form. Should be either a ZIP or a GZip-compressed TAR file. The timestamp on the server will be compared to the local version (if any) so you can publish updates easily. The URL must be accessible from the Jenkins master but need not be accessible from slaves. </div>

core/src/main/resources/hudson/tools/ZipExtractionInstaller/help.html (Master)

Files

MISSING

04.02.2013 00:16:07, no SCM information
<div> Downloads a tool archive and installs it within Jenkins's working directory. Example: <code>http://apache.promopeddler.com/ant/binaries/apache-ant-1.7.1-bin.zip</code> (or whatever mirror is closest to your server) and specify a subdir of <code>apache-ant-1.7.1</code>. </div>

core/src/main/resources/hudson/tools/label.jelly (Master)

Files

label.jelly

MISSING

Label
14.06.2013 07:43:03, no SCM information
Label

core/src/main/resources/hudson/triggers/Messages_fr.properties

Files

CURRENT

SCMTrigger.BuildAction.DisplayName
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Polling Log	Log de scrutation

CURRENT

SCMTrigger.DisplayName
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Poll SCM	Scrutation de l''outil de gestion de version

CURRENT

SCMTrigger.SCMTriggerCause.ShortDescription
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Started by an SCM change	Lancé par un changement dans la base de code

CURRENT

SCMTrigger.getDisplayName
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
{0} Polling Log	Log du dernier accès à {0}

CURRENT

TimerTrigger.DisplayName
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Build periodically	Construire périodiquement

CURRENT

TimerTrigger.MissingWhitespace
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
You appear to be missing whitespace between * and *.	Il semble manquer un espace entre * et *.

CURRENT

TimerTrigger.TimerTriggerCause.ShortDescription
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Started by timer	Lancé par une alarme périodique

CURRENT

Trigger.init
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Initializing timer for triggers	Initialisation des minuteurs des déclencheurs

core/src/main/resources/hudson/triggers/SCMTrigger/AdministrativeMonitorImpl/message_fr.properties

Files

EMPTY

blurb
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
There are more SCM polling activities scheduled than handled, so the threads are not keeping up with the demands. <a href='descriptor/hudson.triggers.SCMTrigger/'>Check if your polling is hanging, and/or increase the number of threads if necessary</a>.	—

core/src/main/resources/hudson/triggers/SCMTrigger/BuildAction/index_fr.properties

Files

CURRENT

Polling Log
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Polling Log	Journal de déclenchement

CURRENT

View as plain text
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
View as plain text	Voir en texte

CURRENT

blurb
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
This page captures the polling log that triggered this build.	Cette page affiche le journal de ce qui a déclenché cette build.

core/src/main/resources/hudson/triggers/SCMTrigger/DescriptorImpl/index_fr.properties

Files

CURRENT

Current SCM Polling Activities
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Current SCM Polling Activities	Activités en cours de scrutation de la gestion de version

CURRENT

No polling activity is in progress.
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
No polling activity is in progress.	Pas d''activité de scrutation en corus.

CURRENT

Project
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Project	Projet

CURRENT

Running for
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Running for	En cours depuis

CURRENT

The following polling activities are currently in progress:
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
The following polling activities are currently in progress:	Les activités de scrutation suivantes sont en cours:

CURRENT

clogged
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
There are more SCM polling activities scheduled than handled, so the threads are not keeping up with the demands. Check if your polling is hanging, and/or increase the number of threads if necessary.	bouché

core/src/main/resources/hudson/triggers/SCMTrigger/SCMAction/index_fr.properties

Files

CURRENT

Polling has not run yet.
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Polling has not run yet.	La scrutation n''a pas encore eu lieu.

CURRENT

title
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
{0}	Dernier {0}

core/src/main/resources/hudson/triggers/SCMTrigger/config_fr.properties

Files

MISSING

Ignore post-commit hooks
04.02.2013 00:16:07, no SCM information
Ignore post-commit hooks

CURRENT

Schedule
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Schedule	Planning

core/src/main/resources/hudson/triggers/SCMTrigger/global_fr.properties

Files

global.jelly

help-ignorePostCommitHooks.html

CURRENT

Max # of concurrent polling
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Max # of concurrent polling	Nombre maximum d''interrogations parallèles

CURRENT

SCM Polling
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
SCM Polling	Interrogation de la base de code

core/src/main/resources/hudson/triggers/SCMTrigger/help-ignorePostCommitHooks.html (Master)

Files

help-pollingThreadCount.html

MISSING

04.02.2013 00:16:07, no SCM information
<div> Ignore changes notified by SCM post-commit hooks. <p> This can be useful if you want to prevent some long-running jobs (e.g. reports) starting because of every commit, but still want to run them periodic if SCM changes have occurred. <p> Note that this option needs to be supported by the SCM plugin, too! The subversion-plugin supports this since version 1.44. </div>

core/src/main/resources/hudson/triggers/SCMTrigger/help-pollingThreadCount_fr.html

Files

help-pollingThreadCount_fr.html

CURRENT

04.02.2013 00:16:07, no SCM information

<div>
If you use SCM polling to trigger a new build for a large number of projects,
you may want to limit the number of concurrent polling activities to avoid
overloading the server.

<p>
Setting a positive number sets the upper bound to the number of concurrent polling.
Leaving the field empty will make it unbounded.
</div>

<div>
Si vous utilisez la scrutation de l'outil de gestion de version pour
déclencher un nouveau build pour un grand nombre de projets, vous
souhaiterez peut-être limiter le nombre de scrutations parallèles, afin
d'éviter de surcharger le serveur.

<p>
Un nombre positif indique la limite supérieure du nombre de scrutations
parallèles.
Laissez le champ vide pour supprimer toute limite supérieure.
</div>

core/src/main/resources/hudson/triggers/SCMTrigger/help_fr.html

Files

CURRENT

04.02.2013 00:16:07, no SCM information

<div>
Configure Jenkins to poll changes in SCM.

<p>
Note that this is going to be an expensive operation for CVS, as every polling
requires Jenkins to scan the entire workspace and verify it with the server.
Consider setting up a "push" trigger to avoid this overhead, as described in
<a href="https://wiki.jenkins-ci.org/display/JENKINS/Building+a+software+project">this document</a>
</div>

<div>
Demande à Jenkins de scruter les changements dans l'outil de gestion de
version.

<p>
Notez que cette opération est consommatrice de ressources pour CVS,
car chaque scrutation signifie que Jenkins va scanner l'ensemble du
workspace et le comparer avec le serveur.
Envisagez d'utiliser un trigger de type 'push' pour éviter cette
surcharge, comme décrit dans
<a href="https://wiki.jenkins-ci.org/display/JENKINS/Building+a+software+project">ce document</a>.
</div>

core/src/main/resources/hudson/triggers/TimerTrigger/config_fr.properties

Files

CURRENT

Schedule
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Schedule	Planning

core/src/main/resources/hudson/triggers/TimerTrigger/help-spec_fr.html

Files

help-spec.html

help-spec_fr.html

OUTDATED

29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:07, no SCM information
<div> This field follows the syntax of cron (with minor differences). Specifically, each line consists of 5 fields separated by TAB or whitespace: <pre>MINUTE HOUR DOM MONTH DOW</pre> <table> <tr> <td>MINUTE</td> <td>Minutes within the hour (0–59)</td> </tr> <tr> <td>HOUR</td> <td>The hour of the day (0–23)</td> </tr> <tr> <td>DOM</td> <td>The day of the month (1–31)</td> </tr> <tr> <td>MONTH</td> <td>The month (1–12)</td> </tr> <tr> <td>DOW</td> <td>The day of the week (0–7) where 0 and 7 are Sunday.</td> </tr> </table> <p> To specify multiple values for one field, the following operators are available. In the order of precedence, </p> <ul> <li><code></code> specifies all valid values</li> <li><code>M-N</code> specifies a range of values</li> <li><code>M-N/X</code> or <code>/X</code> steps by intervals of X through the specified range or whole valid range</li> <li><code>A,B,...,Z</code> enumerates multiple values</li> </ul> <p> To allow periodically scheduled tasks to produce even load on the system, the symbol <code>H</code> (for “hash”) should be used wherever possible. For example, using <code>0 0 * * </code> for a dozen daily jobs will cause a large spike at midnight. In contrast, using <code>H H * </code> would still execute each job once a day, but not all at the same time, better using limited resources. </p><p> The <code>H</code> symbol can be used with a range. For example, <code>H H(0-7) * </code> means some time between 12:00 AM (midnight) to 7:59 AM. You can also use step intervals with <code>H</code>, with or without ranges. </p><p> The <code>H</code> symbol can be thought of as a random value over a range, but it actually is a hash of the job name, not a random function, so that the value remains stable for any given project. </p> <p> Empty lines and lines that start with <code>#</code> will be ignored as comments. </p><p> In addition, <code>@yearly</code>, <code>@annually</code>, <code>@monthly</code>, <code>@weekly</code>, <code>@daily</code>, <code>@midnight</code>, and <code>@hourly</code> are supported as convenient aliases. These use the hash system for automatic balancing. For example, <code>@hourly</code> is the same as <code>H * * </code> and could mean at any time during the hour. <code>@midnight</code> actually means some time between 12:00 AM and 2:59 AM. </p><p> Examples: </p> <pre> # every fifteen minutes (perhaps at :07, :22, :37, :52) H/15 * * * # every ten minutes in the first half of every hour (three times, perhaps at :04, :14, :24) H(0-29)/10 * * * * # once every two hours every weekday (perhaps at 10:38 AM, 12:38 PM, 2:38 PM, 4:38 PM) H 9-16/2 * * 1-5 # once a day on the 1st and 15th of every month except December H H 1,15 1-11 * </pre> </div>	<div> Ce champ suit la syntaxe de cron (avec des différences mineures). Chaque ligne consiste en 5 champs séparés par des TABs ou des espaces : <pre>MINUTES HEURES JOURMOIS MOIS JOURSEMAINE</pre> <table> <tr> <td>MINUTES</td> <td>Les minutes dans une heure (0-59)</td> </tr> <tr> <td>HEURES</td> <td>Les heures dans une journée (0-23)</td> </tr> <tr> <td>JOURMOIS</td> <td>Le jour dans un mois (1-31)</td> </tr> <tr> <td>MOIS</td> <td>Le mois (1-12)</td> </tr> <tr> <td>JOURSEMAINE</td> <td>Le jour de la semaine (0-7) où 0 et 7 représentent le dimanche </td> </tr> </table> <p> Pour spécifier des valeurs multiples pour un champ, utilisez les opérateurs suivants. Par ordre de précédence : </p> <ul> <li>'' représente l'ensemble des valeurs possibles.</li> <li>'M-N' représente une liste bornée, telle que "1-5"</li> <li>'M-N/X' ou '/X' permettent de spécifier des sauts de valeur X dans la liste. Par exemple, "/15" dans le champ MINUTES est équivalent à "0,15,30,45" et "1-6/2" à "1,3,5"</li> <li>'A,B,...,Z' permet de spécifier des valeurs multiples, comme "0,30" ou "1,3,5"</li> </ul> <p> Les lignes vides et les lignes qui commencent par '#' seront considérées comme des commentaires et ignorées. </p> <p> Par ailleurs, les mots-clefs '@yearly', '@annually', '@monthly', '@weekly', '@daily', '@midnight' et '@hourly' sont supportés. </p> <table> <tr> <td>Exemples</td> <td> <pre> # toutes les minutes * * * * # toutes les 5 minutes après l'heure 5 * * * * </pre> </td> </tr> </table> </div>
(old value)

core/src/main/resources/hudson/triggers/TimerTrigger/help_fr.html

Files

OUTDATED

28.02.2013 15:26:35, no SCM information	04.02.2013 00:16:07, no SCM information
<div> Provides a <a href="http://en.wikipedia.org/wiki/cron">cron</a>-like feature to periodically execute this project. <p> This feature is primarily for using Jenkins as a cron replacement, and it is <b>not ideal for continuously building software projects</b>. When people first start continuous integration, they are often so used to the idea of regularly scheduled builds like nightly/weekly that they use this feature. However, the point of continuous integration is to start a build as soon as a change is made, to provide a quick feedback to the change. To do that you need to <a href="https://wiki.jenkins-ci.org/display/JENKINS/Building+a+software+project">hook up SCM change notification to Jenkins</a>. <p> So, before using this feature, stop and ask yourself if this is really what you want. </div>	<div> Fournit une fonctionnalité de type <a href="http://en.wikipedia.org/wiki/cron">cron</a> afin d'exécuter le projet périodiquement. <p> Cette fonction est prévue principalement pour utiliser Jenkins comme un remplacement de cron. <b>Elle n'est pas faite pour la construction continue de projets logiciel</b>. Quand quelqu'un débute avec l'intégration continue, il est souvent tellement habitué à l'idée d'un lancement de build toutes les nuits ou toutes les semaines, qu'il préfère utiliser cette fonctionnalité. Néanmoins, l'intérêt de l'intégration continue est de lancer un build à chaque changement dans la base de code, afin de donner un retour rapide sur ce changement. Pour cela, vous devez <a href="https://wiki.jenkins-ci.org/display/JENKINS/Building+a+software+project">associer la notification des changements de l'outil de gestion de version à Jenkins.</a>. <p> Donc, avant d'utiliser cette fonctionnalité, demandez-vous si c'est bien ce que vous voulez faire. </div>
(old value)

core/src/main/resources/hudson/util/AWTProblem/index_fr.properties

Files

CURRENT

Error
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Error	Erreur

CURRENT

errorMessage
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
AWT is not properly configured on this server. Perhaps you need to run your container with "-Djava.awt.headless=true"?	AWT n''est pas configuré correctement sur ce serveur. Peut-être devez-vous lancer votre conteneur avec "-Djava.awt.headless=true"?

core/src/main/resources/hudson/util/AdministrativeError/message.jelly (Master)

Files

MISSING

See the log for more details
04.02.2013 00:16:07, no SCM information
See the log for more details

core/src/main/resources/hudson/util/DoubleLaunchChecker/index_fr.properties

Files

MISSING

label
01.08.2013 07:43:47, no SCM information
Ignore this problem and keep using Jenkins anyway

OUTDATED

message
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
Jenkins detected that you appear to be running more than one instance of Jenkins that share the same home directory ''{0}’. This greatly confuses Jenkins and you will likely experience strange behaviors, so please correct the situation.	Jenkins a détecté que vous utilisez plusieurs instances de Jenkins qui partagent un même répertoire home ''{0}''. Ceci rend Jenkins instable et vous risquez de constater des comportements incorrects. Merci de corriger le problème.
(old value)

CURRENT

Error
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Error	Erreur

CURRENT

Other Jenkins
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Other Jenkins	L''autre instance de Jenkins

CURRENT

This Jenkins
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
This Jenkins	Cette instance de Jenkins

core/src/main/resources/hudson/util/HudsonFailedToLoad/index_fr.properties

Files

CURRENT

Error
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Error	Erreur

core/src/main/resources/hudson/util/HudsonIsLoading/index_fr.properties

Files

CURRENT

Please wait while Jenkins is getting ready to work
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Please wait while Jenkins is getting ready to work	Merci d''attendre que Jenkins soit prêt

CURRENT

Your browser will reload automatically when Jenkins is ready.
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Your browser will reload automatically when Jenkins is ready.	Votre navigateur web sera rafraîchi automatiquement lorsque Jenkins sera prêt.

core/src/main/resources/hudson/util/HudsonIsRestarting/index_fr.properties

Files

CURRENT

Please wait while Jenkins is restarting
04.02.2013 00:16:07, no SCM information	24.02.2013 10:14:59, no SCM information
Please wait while Jenkins is restarting	Veuillez attendre pendant que Jenkins redémarre

CURRENT

Your browser will reload automatically when Jenkins is ready.
04.02.2013 00:16:07, no SCM information	24.02.2013 10:14:59, no SCM information
Your browser will reload automatically when Jenkins is ready.	Votre navigateur se connectera automatiquement quand Jenkins sera prêt

core/src/main/resources/hudson/util/IncompatibleAntVersionDetected/index_fr.properties

Files

OUTDATED

errorMessage
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:07, no SCM information
We detected that your servlet container is loading an older version of Ant by itself, thereby preventing Jenkins from loading its own newer copy. (Ant classes are loaded from {0}) <br> Perhaps can you override Ant in your container by copying one from Jenkins’s <tt>WEB-INF/lib</tt>, or can you set up the classloader delegation to child-first so that Jenkins sees its own copy first?	Nous avons détecté que votre conteneur de servlets charge de lui-même une ancienne version de Ant, ce qui empèche Jenkins de charger sa propre copie de Ant, plus récente. (les classes de Ant sont chargées à partir de {0}) <br> Peut-être pouvez-vous surcharger Ant dans votre conteneur en copiant un exemplaire à partir du répertoire <tt>WEB-INF/lib</tt> de Jenkins? Ou tentez de positionner la délégation classloader en child-first afin que Jenkins puisse voir sa propre copie d''abord.
(old value)

CURRENT

Error
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Error	Erreur

core/src/main/resources/hudson/util/IncompatibleServletVersionDetected/index_fr.properties

Files

CURRENT

Error
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Error	Erreur

CURRENT

errorMessage
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
We detected that your servlet container does not support Servlet 2.4 (servlet API is loaded from {0})	Nous avons détecté que votre conteneur de servlets ne supporte pas Servlet 2.4 (l''API servlet est chargée à partir de {0})

core/src/main/resources/hudson/util/IncompatibleVMDetected/index.jelly (Master)

Files

MISSING

Detected JVM
04.02.2013 00:16:07, no SCM information
Detected JVM

MISSING

Error
04.02.2013 00:16:07, no SCM information
Error

MISSING

OS Name
04.02.2013 00:16:07, no SCM information
OS Name

MISSING

VM Name
04.02.2013 00:16:07, no SCM information
VM Name

MISSING

Vendor
04.02.2013 00:16:07, no SCM information
Vendor

MISSING

Version
04.02.2013 00:16:07, no SCM information
Version

MISSING

errorMessage
04.02.2013 00:16:07, no SCM information
We detected that your JVM is not supported by Jenkins. This is due to the limitation is one of the libraries that Jenkins uses, namely XStream. See <a href="http://xstream.codehaus.org/faq.html">this FAQ</a> for more details.

core/src/main/resources/hudson/util/InsufficientPermissionDetected/index.jelly (Master)

Files

MISSING

Error
04.02.2013 00:16:07, no SCM information
Error

MISSING

errorMessage.1
04.02.2013 00:16:07, no SCM information
We detected that Jenkins does not have sufficient permission to run, as indicated by the stack trace below. Most likely cause of this problem is that the security manger is on. If that was intended, you need to grant sufficient permissions for Jenkins to run. Otherwise, or if you have no idea what a security manager is, then the easiest way to fix the problem is simply to turn the security manager off.

MISSING

errorMessage.2
04.02.2013 00:16:07, no SCM information
For how to turn off security manager in your container, refer to <a href="http://wiki.jenkins-ci.org/display/JENKINS/Containers"> Container-specific documentations</a> of Jenkins.

core/src/main/resources/hudson/util/JNADoublyLoaded/index.jelly (Master)

Files

MISSING

Failed to load JNA
04.02.2013 00:16:07, no SCM information
Failed to load JNA

MISSING

blurb
04.02.2013 00:16:07, no SCM information
Another instance of JNA is already loaded in another classloader, thereby making it impossible for Jenkins to load its own copy. <a href="http://wiki.jenkins-ci.org/display/JENKINS/JNA+is+already+loaded">See Wiki for more details</a>.

core/src/main/resources/hudson/util/JenkinsReloadFailed/index.groovy (Master)

Files

index.groovy

MISSING

Error
04.02.2013 00:16:07, no SCM information
Error

MISSING

msg
04.02.2013 00:16:07, no SCM information
Jenkins was interrupted while it was reloading data from disk. To prevent unexpected data loss, Jenkins has ceased to function. Please restart Jenkins.

core/src/main/resources/hudson/util/Messages_fr.properties

Files

MISSING

FormFieldValidator.did_not_manage_to_validate_may_be_too_sl
28.02.2013 15:26:35, no SCM information
Did not manage to validate {0} (may be too slow)

MISSING

FormValidation.Error.Details
28.02.2013 15:26:35, no SCM information
(show details)

MISSING

FormValidation.ValidateRequired
28.02.2013 15:26:35, no SCM information
Required

MISSING

HttpResponses.Saved
28.02.2013 15:26:35, no SCM information
Saved

CURRENT

ClockDifference.Ahead
28.02.2013 15:26:35, no SCM information	28.02.2013 15:26:35, no SCM information
{0} ahead	{0} en avance

CURRENT

ClockDifference.Behind
28.02.2013 15:26:35, no SCM information	28.02.2013 15:26:35, no SCM information
{0} behind	{0} en retard

CURRENT

ClockDifference.Failed
28.02.2013 15:26:35, no SCM information	28.02.2013 15:26:35, no SCM information
Failed to check	Impossible à vérifier

CURRENT

ClockDifference.InSync
28.02.2013 15:26:35, no SCM information	28.02.2013 15:26:35, no SCM information
In sync	Synchronisé

core/src/main/resources/hudson/util/NoHomeDir/index.jelly (Master)

Files

MISSING

Error
04.02.2013 00:16:07, no SCM information
Error

MISSING

errorMessage.1
01.08.2013 07:43:47, no SCM information
Unable to create the home directory ‘{0}’. This is most likely a permission problem.

MISSING

errorMessage.2
01.08.2013 07:43:47, no SCM information
To change the home directory, use <tt>JENKINS_HOME</tt> environment variable or set the <tt>JENKINS_HOME</tt> system property. See <a href="http://wiki.jenkins-ci.org/display/JENKINS/Containers">Container-specific documentation</a> for more details of how to do this.

core/src/main/resources/hudson/util/NoTempDir/index_fr.properties

Files

EMPTY

description
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Unable to create a temporary file. This is most likely caused by a mis-configuration of the container. The JVM seems to be told to use "{0}" as the temporary directory. Does this directory exist and is it writable?	—

CURRENT

Error
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
Error	Erreur

core/src/main/resources/hudson/views/BuildButtonColumn/column_fr.properties

Files

MISSING

Build scheduled
14.06.2013 07:43:03, no SCM information
Build scheduled

MISSING

Schedule a build with parameters
14.06.2013 07:43:03, no SCM information
Schedule a build with parameters

OUTDATED

Schedule a build
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:07, no SCM information
Schedule a build	Programmer une compilation
(old value)

core/src/main/resources/hudson/views/DefaultMyViewsTabBar/myViewTabs_fr.properties

Files

myViewTabs.jelly

myViewTabs_fr.properties

CURRENT

New View
04.02.2013 00:16:07, no SCM information	04.02.2013 00:16:07, no SCM information
New View	Nouvelle Vue

core/src/main/resources/hudson/views/DefaultViewsTabBar/viewTabs_fr.properties

Files

viewTabs.jelly

viewTabs_fr.properties

CURRENT

New View
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
New View	Nouvelle vue

core/src/main/resources/hudson/views/GlobalDefaultViewConfiguration/config_fr.properties

Files

CURRENT

Default view
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Default view	Vue par défaut

core/src/main/resources/hudson/views/LastDurationColumn/column_fr.properties

Files

OUTDATED

N/A
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:08, no SCM information
N/A	N/A
(old value)

core/src/main/resources/hudson/views/LastDurationColumn/columnHeader_fr.properties

Files

CURRENT

Last Duration
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Last Duration	Dernière Durée

core/src/main/resources/hudson/views/LastFailureColumn/column_fr.properties

Files

OUTDATED

N/A
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:08, no SCM information
N/A	N/A
(old value)

core/src/main/resources/hudson/views/LastFailureColumn/columnHeader_fr.properties

Files

CURRENT

Last Failure
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Last Failure	Dernier Echec

core/src/main/resources/hudson/views/LastStableColumn/column_fr.properties

Files

OUTDATED

N/A
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:08, no SCM information
N/A	N/A
(old value)

core/src/main/resources/hudson/views/LastStableColumn/columnHeader_fr.properties

Files

CURRENT

Last Stable
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Last Stable	Dernière stable

core/src/main/resources/hudson/views/LastSuccessColumn/column_fr.properties

Files

OUTDATED

N/A
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:08, no SCM information
N/A	N/A
(old value)

core/src/main/resources/hudson/views/LastSuccessColumn/columnHeader_fr.properties

Files

CURRENT

Last Success
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Last Success	Dernier Succès

core/src/main/resources/hudson/views/Messages.properties (Master)

Files

MISSING

BuildButtonColumn.DisplayName
04.02.2013 00:16:08, no SCM information
Build Button

MISSING

DefaultMyViewsTabsBar.DisplayName
04.02.2013 00:16:08, no SCM information
Default My Views TabBar

MISSING

DefaultViewsTabsBar.DisplayName
04.02.2013 00:16:08, no SCM information
Default Views TabBar

MISSING

JobColumn.DisplayName
04.02.2013 00:16:08, no SCM information
Name

MISSING

LastDurationColumn.DisplayName
04.02.2013 00:16:08, no SCM information
Last Duration

MISSING

LastFailureColumn.DisplayName
04.02.2013 00:16:08, no SCM information
Last Failure

MISSING

LastStableColumn.DisplayName
04.02.2013 00:16:08, no SCM information
Last Stable

MISSING

LastSuccessColumn.DisplayName
04.02.2013 00:16:08, no SCM information
Last Success

MISSING

StatusColumn.DisplayName
04.02.2013 00:16:08, no SCM information
Status

MISSING

WeatherColumn.DisplayName
04.02.2013 00:16:08, no SCM information
Weather

core/src/main/resources/hudson/views/MyViewsTabBar/GlobalConfigurationImpl/config.groovy (Master)

Files

MISSING

Views Tab Bar
04.02.2013 00:16:08, no SCM information
Views Tab Bar

core/src/main/resources/hudson/views/MyViewsTabBar/GlobalConfigurationImpl/help-myViewsTabBar.html (Master)

Files

help-myViewsTabBar.html

MISSING

28.02.2013 15:26:35, no SCM information

<div>
If you have multiple views defined in My Views, then the default My Views TabBar becomes too long. The MyViewsTabBar
Extension Point provides facility for plugins to provide their own implementation of My Views TabBar.
This DropDown, lists all the available My Views TabBar implementation. Only one TabBar implementation can
be active at a time for My Views. Select one from the DropDown list.
</div>

core/src/main/resources/hudson/views/StatusColumn/columnHeader_fr.properties

Files

CURRENT

Status of the last build
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Status of the last build	Statut de la dernière compilation

core/src/main/resources/hudson/views/ViewsTabBar/GlobalConfigurationImpl/config.groovy (Master)

Files

MISSING

Views Tab Bar
04.02.2013 00:16:08, no SCM information
Views Tab Bar

core/src/main/resources/hudson/views/ViewsTabBar/GlobalConfigurationImpl/help-viewsTabBar.html (Master)

Files

help-viewsTabBar.html

MISSING

04.02.2013 00:16:08, no SCM information
<div> If you have multiple views defined, then the default Views TabBar becomes too long. The ViewsToolBar Extension Point provides facility for plugins to provide their own implementation of Views TabBar. This DropDown, lists all the available Views TabBar implementation. Only one TabBar implementation can be active at a time. Select one from the DropDown list. </div>

core/src/main/resources/hudson/views/WeatherColumn/columnHeader_fr.properties

Files

CURRENT

Weather report showing aggregated status of recent builds
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Weather report showing aggregated status of recent builds	Graphe montrant les statuts de toutes les constructions récentes

core/src/main/resources/hudson/widgets/BuildHistoryWidget/entries_fr.properties

Files

entries.jelly

entries_fr.properties

OUTDATED

cancel this build
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:08, no SCM information
cancel this build	annuler ce build
(old value)

OUTDATED

pending
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:08, no SCM information
pending	à lancer
(old value)

core/src/main/resources/hudson/widgets/HistoryWidget/entry_fr.properties

Files

entry.jelly

entry_fr.properties

OUTDATED

Console Output
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:08, no SCM information
Console Output	Sortie Console
(old value)

ORPHANED

Console output
	04.02.2013 00:16:08, no SCM information
	Sortie de la console

core/src/main/resources/hudson/widgets/HistoryWidget/index_fr.properties

Files

OUTDATED

More ...
29.08.2013 16:34:29, no SCM information	04.02.2013 00:16:08, no SCM information
More ...	Détails...
(old value)

OUTDATED

for all
29.08.2013 16:34:29, no SCM information	04.02.2013 00:16:08, no SCM information
for all	toutes les constructions
(old value)

OUTDATED

for failures
29.08.2013 16:34:29, no SCM information	04.02.2013 00:16:08, no SCM information
for failures	de tous les échecs
(old value)

OUTDATED

trend
29.08.2013 16:34:29, no SCM information	04.02.2013 00:16:08, no SCM information
trend	Tendances
(old value)

core/src/main/resources/hudson/widgets/Messages_fr.properties

Files

CURRENT

BuildHistoryWidget.DisplayName
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Build History	Historique des builds

core/src/main/resources/jenkins/diagnostics/SecurityIsOffMonitor/message_fr.properties

Files

CURRENT

Dismiss
29.04.2013 12:15:14, no SCM information	30.05.2013 20:09:20, no SCM information
Dismiss	Cacher ce message

CURRENT

Setup Security
29.04.2013 12:15:14, no SCM information	30.05.2013 20:09:20, no SCM information
Setup Security	Configuration de la sécurité

CURRENT

blurb
29.04.2013 12:15:14, no SCM information	30.05.2013 20:09:20, no SCM information
Unsecured Jenkins allows anyone on the network to launch processes on your behalf. Consider at least enabling authentication to discourage misuse.	La non sécurisation de Jenkins permet à quiconque sur le réseau de lancer des processus en votre nom. Envisager au moins une authentification permettant de décourager les abus.

core/src/main/resources/jenkins/diagnostics/ooom/Messages.properties (Master)

Files

MISSING

Problem.DisplayName
01.08.2013 07:43:47, no SCM information
{0} builds have inconsistent timestamps in <a href="{2}">{1}</a>

core/src/main/resources/jenkins/diagnostics/ooom/OutOfOrderBuildMonitor/message.groovy (Master)

Files

message.groovy

MISSING

Correct those problems by moving offending records to a backup folder
01.08.2013 07:43:47, no SCM information
Correct those problems by moving offending records to a backup folder

MISSING

Dismiss this message
01.08.2013 07:43:47, no SCM information
Dismiss this message

MISSING

buildsAreOutOfOrder
01.08.2013 07:43:47, no SCM information
Some projects have builds whose timestamps are inconsistent. <a href="http://jenkins-ci.org/issue/18289">These will confuse Jenkins when it tries to look up build records</a>.

MISSING

completed
01.08.2013 07:43:47, no SCM information
Out-of-order builds were swept under the carpet. <a href="{0}/log">You can check the log</a>.

MISSING

inProgress
01.08.2013 07:43:47, no SCM information
Out-of-order builds are being swept under the carpet. <a href="{0}/log">You can check the log</a>.

MISSING

problem
01.08.2013 07:43:47, no SCM information
{0} builds in <a href="{2}">{1}</a>

core/src/main/resources/jenkins/management/AsynchronousAdministrativeMonitor/log.groovy (Master)

Files

log.groovy

MISSING

Log: ${my.displayName}
01.08.2013 07:43:47, no SCM information
Log: ${my.displayName}

core/src/main/resources/jenkins/management/Messages_fr.properties

Files

MISSING

CliLink.DisplayName
04.02.2013 00:16:08, no SCM information
Jenkins CLI

MISSING

SystemLogLink.DisplayName
04.02.2013 00:16:08, no SCM information
System Log

CURRENT

CliLink.Description
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Access/manage Jenkins from your shell, or from your script.	Accéder ou gérer Jenkins depuis votre shell ou depuis votre script.

CURRENT

ConfigureLink.Description
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Configure global settings and paths.	Configurer les paramètres généraux et les chemins de fichiers.

CURRENT

ConfigureLink.DisplayName
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Configure System	Configurer le système

CURRENT

ConsoleLink.Description
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Executes arbitrary script for administration/trouble-shooting/diagnostics.	Exécute des scripts arbitraires pour l''administration, la résolution de problèmes ou pour un diagnostic.

CURRENT

ConsoleLink.DisplayName
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Script Console	Console de script

CURRENT

NodesLink.Description
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Add, remove, control and monitor the various nodes that Jenkins runs jobs on.	Ajouter, supprimer, contrôler et monitorer les divers nœuds que Jenkins utilise pour exécuter les jobs.

CURRENT

NodesLink.DisplayName
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Manage Nodes	Gérer les nœuds

CURRENT

PluginsLink.Description
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Add, remove, disable or enable plugins that can extend the functionality of Jenkins.	Ajouter, supprimer, activer ou désactiver des plugins qui peuvent étendre les fonctionnalités de Jenkins.

CURRENT

PluginsLink.DisplayName
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Manage Plugins	Gestion des plugins

CURRENT

ReloadLink.Description
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Discard all the loaded data in memory and reload everything from file system. Useful when you modified config files directly on disk.	Supprimer toutes les données en mémoire et recharger tout à partir du système de fichiers. Utile quand vous modifiez les fichiers de configuration directement sur le disque.

CURRENT

ReloadLink.DisplayName
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Reload Configuration from Disk	Recharger la configuration à partir du disque

CURRENT

ShutdownLink.Description
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Stops executing new builds, so that the system can be eventually shut down safely.	Cesser d''exécuter de nouveaux builds, afin que le système puisse se fermer.

CURRENT

ShutdownLink.DisplayName_cancel
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Cancel Shutdown	Annuler la fermeture

CURRENT

ShutdownLink.DisplayName_prepare
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Prepare for Shutdown	Préparer à la fermeture

CURRENT

StatisticsLink.Description
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Check your resource utilization and see if you need more computers for your builds.	Vérifiez l''utilisation des ressources et décidez si vous avez besoin d''ordinateurs supplémentaires pour vos builds.

CURRENT

StatisticsLink.DisplayName
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Load Statistics	Statistiques d''utilisation

CURRENT

SystemInfoLink.Description
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Displays various environmental information to assist trouble-shooting.	Affiche diverses informations relatives au système pour aider à la résolution de problêmes.

CURRENT

SystemInfoLink.DisplayName
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
System Information	Informations sur le système

CURRENT

SystemLogLink.Description
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
System log captures output from <tt>java.util.logging</tt> output related to Jenkins.	Le log système capture la sortie <tt>java.util.logging</tt> relative à Jenkins.

core/src/main/resources/jenkins/management/PluginsLink/info_fr.properties

Files

info.jelly

info_fr.properties

CURRENT

updates available
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
updates available	mises à jour disponibles

core/src/main/resources/jenkins/model/ArtifactManagerConfiguration/config.groovy (Master)

Files

MISSING

Artifact Management for Builds
20.09.2013 10:05:40, no SCM information
Artifact Management for Builds

core/src/main/resources/jenkins/model/CauseOfInterruption/UserInterruption/summary.groovy (Master)

Files

summary.groovy

MISSING

blurb
04.02.2013 00:16:08, no SCM information
Aborted by user <a href="{1}">{0}</a>

core/src/main/resources/jenkins/model/CoreEnvironmentContributor/buildEnv_fr.properties

Files

buildEnv.groovy

buildEnv_fr.properties

MISSING

${name}.blurb
29.04.2013 12:15:14, no SCM information
${name}.blurb

ORPHANED

BUILD_ID.blurb
	04.02.2013 00:16:08, no SCM information
	L'identifiant du build courant, par exemple "2005-08-22_23-59-59" (YYYY-MM-DD_hh-mm-ss)

ORPHANED

BUILD_NUMBER.blurb
	04.02.2013 00:16:08, no SCM information
	Le numéro du build courant, par exemple "153"

ORPHANED

BUILD_TAG.blurb
	04.02.2013 00:16:08, no SCM information
	Le texte "jenkins-<i>$'{'JOB_NAME}</i>-<i>$'{'BUILD_NUMBER}</i>", facile à placer dans un fichier de ressource, ou un jar, pour identification future.

ORPHANED

BUILD_URL.blurb
	04.02.2013 00:16:08, no SCM information
	—

ORPHANED

EXECUTOR_NUMBER.blurb
	04.02.2013 00:16:08, no SCM information
	Le numéro unique qui identifie l'exécuteur courant (parmi les exécuteurs d'une même machine) qui a contruit ce build. Il s'agit du numéro que vous voyez dans le "statut de l'exécuteur du build", sauf que la numérotation commence à 0 et non à 1.

ORPHANED

JENKINS_HOME.blurb
	04.02.2013 00:16:08, no SCM information
	—

ORPHANED

JENKINS_URL.blurb
	04.02.2013 00:16:08, no SCM information
	L'URL complète de Jenkins, au format <tt>http://server:port/jenkins/</tt>

ORPHANED

JOB_NAME.blurb
	04.02.2013 00:16:08, no SCM information
	Nom du projet de ce build, par exemple "foo"

ORPHANED

JOB_URL.blurb
	04.02.2013 00:16:08, no SCM information
	—

ORPHANED

NODE_LABELS.blurb
	04.02.2013 00:16:08, no SCM information
	—

ORPHANED

NODE_NAME.blurb
	04.02.2013 00:16:08, no SCM information
	—

ORPHANED

WORKSPACE.blurb
	04.02.2013 00:16:08, no SCM information
	Le chemin absolu vers le répertoire de travail.

core/src/main/resources/jenkins/model/GlobalCloudConfiguration/config_fr.properties

Files

MISSING

Delete cloud
04.02.2013 00:16:08, no SCM information
Delete cloud

EMPTY

Cloud
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Cloud	—

CURRENT

Add a new cloud
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Add a new cloud	Ajouter un nouveau cloud

core/src/main/resources/jenkins/model/GlobalNodePropertiesConfiguration/config_fr.properties

Files

OUTDATED

Global properties
21.06.2013 06:36:29, no SCM information	04.02.2013 00:16:08, no SCM information
Global properties	Propriétés globales
(old value)

core/src/main/resources/jenkins/model/GlobalProjectNamingStrategyConfiguration/config.groovy (Master)

Files

MISSING

namingStrategyTitel
04.02.2013 00:16:08, no SCM information
Naming Strategy

MISSING

strategy
04.02.2013 00:16:08, no SCM information
Strategy

MISSING

useNamingStrategy
04.02.2013 00:16:08, no SCM information
Restrict project naming

core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/config_fr.properties

Files

CURRENT

Quiet period
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Quiet period	Période d''attente

core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod_fr.html

Files

help-quietPeriod.html

help-quietPeriod_fr.html

CURRENT

04.02.2013 00:16:08, no SCM information

<div>
If set, a newly scheduled build waits for this many seconds before actually being built.
This is useful for:
<ul>
<li>
Collapsing multiple CVS change notification e-mails into one (some CVS changelog
e-mail generation scripts generate multiple e-mails in quick succession when
a commit spans across directories).
</li>
<li>
If your coding style is such that you commit one logical change in a few cvs/svn
operations, then setting a longer quiet period would prevent Jenkins from building
it prematurely and reporting a failure.
</li>
<li>
Throttling builds. If your Jenkins installation is too busy with too many builds,
setting a longer quiet period can reduce the number of builds.
</li>
</ul>
If not explicitly set at project-level, the system-wide default value is used.
</div>

<div>
Si cette option est activée, un build attendra le nombre de secondes
indiqué avant de réellement s'exécuter.
Cela est utile pour :
<ul>
<li>
Agréger de multiples emails de notification de changements CVS dans
un seul (certains scripts de génération d'email relatif aux
changements dans CVS génèrent de nombreux messages en rafale,
lorsqu'un commit concerne plusieurs répertoires).
</li>
<li>
Selon vos habitudes de codage, vous introduisez peut-être une erreur de
logique dans certaines opérations cvs/svn. Dans ce cas, une période
d'attente plus longue évitera que Jenkins lance un build
prématurement et indique un échec.
</li>
<li>
La gestion des ressources. Si votre installation de Jenkins est
surchargée par de nombreux builds, une période d'attente plus longue
pourra réduire ce nombre.
</li>
</ul>
Si cette valeur n'est pas positionnée explicitement au niveau du projet,
une valeur par défaut pour toute l'installation de Jenkins sera
utilisée.
</div>

core/src/main/resources/jenkins/model/GlobalSCMRetryCountConfiguration/config_fr.properties

Files

CURRENT

SCM checkout retry count
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
SCM checkout retry count	Nombre de tentatives de checkout SCM

core/src/main/resources/jenkins/model/Jenkins/MasterComputer/configure_fr.properties

Files

_safeRestart_fr.properties

MISSING

Description
22.03.2013 09:10:52, no SCM information
Description

OUTDATED

# of executors
22.03.2013 09:10:52, no SCM information	19.02.2013 07:05:52, no SCM information
# of executors	Nb d''exécuteurs
(old value)

OUTDATED

Labels
22.03.2013 09:10:52, no SCM information	19.02.2013 07:05:52, no SCM information
Labels	Libellés
(old value)

OUTDATED

Node Properties
22.03.2013 09:10:52, no SCM information	19.02.2013 07:05:52, no SCM information
Node Properties	Propriétés du nœud
(old value)

OUTDATED

Save
22.03.2013 09:10:52, no SCM information	19.02.2013 07:05:52, no SCM information
Save	Enregistrer
(old value)

core/src/main/resources/jenkins/model/Jenkins/_cli_fr.properties

Files

_cli.jelly

_cli_fr.properties

MISSING

Available Commands
04.02.2013 00:16:08, no SCM information
Available Commands

MISSING

blurb
04.02.2013 00:16:08, no SCM information
You can access various features in Jenkins through a command-line tool. See <a href="http://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI">the Wiki</a> for more details of this feature.To get started, download <a href="{0}/jnlpJars/jenkins-cli.jar">jenkins-cli.jar</a>, and run it as follows:

CURRENT

Jenkins CLI
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Jenkins CLI	Ligne de commande (CLI) Jenkins

core/src/main/resources/jenkins/model/Jenkins/_restart_fr.properties

Files

_restart.jelly

_restart_fr.properties

CURRENT

Are you sure about restarting Jenkins?
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Are you sure about restarting Jenkins?	Êtes-vous sûr de vouloir redémarrer Jenkins?

CURRENT

Yes
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Yes	Oui

core/src/main/resources/jenkins/model/Jenkins/_safeRestart_fr.properties

Files

_safeRestart.jelly

CURRENT

Are you sure about restarting Jenkins? Jenkins will restart once all running jobs are finished.
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Are you sure about restarting Jenkins? Jenkins will restart once all running jobs are finished.	Êtes-vous sûr de vouloir redémarrer Jenkins? Jenkins redémarrera une fois tous les jobs terminés.

CURRENT

Yes
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Yes	Oui

core/src/main/resources/jenkins/model/Jenkins/accessDenied.jelly (Master)

Files

accessDenied.jelly

MISSING

Access Denied
12.07.2013 12:08:38, no SCM information
Access Denied

MISSING

Jenkins Login
12.07.2013 12:08:38, no SCM information
Jenkins Login

core/src/main/resources/jenkins/model/Jenkins/configure_fr.properties

Files

fingerprintCheck_fr.properties

MISSING

Configure System
06.03.2013 21:41:00, no SCM information
Configure System

OUTDATED

Build Record Root Directory
06.03.2013 21:41:00, no SCM information	24.02.2013 10:14:59, no SCM information
Build Record Root Directory	Répertoire racine des builds
(old value)

OUTDATED

Home directory
06.03.2013 21:41:00, no SCM information	24.02.2013 10:14:59, no SCM information
Home directory	Répertoire Home
(old value)

OUTDATED

LOADING
06.03.2013 21:41:00, no SCM information	24.02.2013 10:14:59, no SCM information
LOADING	CHARGEMENT
(old value)

OUTDATED

Save
06.03.2013 21:41:00, no SCM information	24.02.2013 10:14:59, no SCM information
Save	Enregistrer
(old value)

OUTDATED

System Message
06.03.2013 21:41:00, no SCM information	24.02.2013 10:14:59, no SCM information
System Message	Message du système
(old value)

OUTDATED

Workspace Root Directory
06.03.2013 21:41:00, no SCM information	24.02.2013 10:14:59, no SCM information
Workspace Root Directory	Répertoire racine de l''espace de travail (workspace)
(old value)

ORPHANED

Default view
	24.02.2013 10:14:59, no SCM information
	Vue par défaut

ORPHANED

Global properties
	24.02.2013 10:14:59, no SCM information
	Propriétés globales

ORPHANED

JDK installations
	24.02.2013 10:14:59, no SCM information
	Installations des JDK

ORPHANED

JDKs
	24.02.2013 10:14:59, no SCM information
	JDK

ORPHANED

List of JDK installations on this system
	24.02.2013 10:14:59, no SCM information
	Liste des installations de JDK sur ce système.

ORPHANED

name
	24.02.2013 10:14:59, no SCM information
	Nom

ORPHANED

no.such.JDK
	24.02.2013 10:14:59, no SCM information
	<span class=error>Ce JDK n''existe pas</span>

ORPHANED

statsBlurb
	24.02.2013 10:14:59, no SCM information
	Aidez-nous à améliorer Jenkins en envoyant sous forme anonyme les statistiques d''utilisation et les rapports de crash au projet Jenkins.

core/src/main/resources/jenkins/model/Jenkins/downgrade_fr.properties

Files

downgrade.jelly

downgrade_fr.properties

CURRENT

Restore the previous version of Jenkins
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Restore the previous version of Jenkins	Restaurer la version précédente de Jenkins

CURRENT

buttonText
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Downgrade to {0}	Revenir à la version {0}

core/src/main/resources/jenkins/model/Jenkins/fingerprintCheck_fr.properties

Files

fingerprintCheck.jelly

MISSING

fingerprint.link
01.08.2013 07:43:47, no SCM information
https://wiki.jenkins-ci.org/display/JENKINS/Fingerprint

OUTDATED

description
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:08, no SCM information
Got a jar file but don’t know which version it is? <br /> Find that out by checking the fingerprint against the database in Jenkins	Vous avez un fichier jar mais vous ne connaissez pas sa version ?<br />Vous pourrez la trouver en comparant l''empreinte numérique avec celles dans la base de données de Jenkins
(old value)

CURRENT

Check
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Check	Vérifier

CURRENT

Check File Fingerprint
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Check File Fingerprint	Vérifier l''empreinte numérique

CURRENT

File to check
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
File to check	Fichier à vérifier

CURRENT

more details
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
more details	plus de détails

core/src/main/resources/jenkins/model/Jenkins/help-markupFormatter.html (Master)

Files

help-markupFormatter.html

MISSING

04.02.2013 00:16:08, no SCM information

<div>
In such places as project description, user description, view description, and build description,
Jenkins allows users to enter some free-form text that describes something.

This configuration determines how such free-form text is converted to HTML. By default, Jenkins treats
the text as HTML and use it as-is unmodified (and this is default mainly because of the backward compatibility.)

<p>
While this is convenient and people often use it to load <iframe>, <script>. and so on to
mash up data from other sources, this capability enables malicious users to mount
<a href="http://en.wikipedia.org/wiki/Cross-site_scripting">XSS attacks</a>.
If the risk outweighs the benefit, install additional markup formatter plugins and use them.
</div>

core/src/main/resources/jenkins/model/Jenkins/help-rawBuildsDir.html (Master)

Files

help-rawBuildsDir.html

help-rawWorkspaceDir.html

MISSING

28.02.2013 15:26:35, no SCM information

<div>
Specify where Jenkins would store records of the past builds.
This value can include the following variables.

<ul>
<li><tt>${JENKINS_HOME}</tt> — Jenkins home directory.
<li><tt>${ITEM_ROOTDIR}</tt> — Root directory of a job for which the default workspace is allocated.
<li><tt>${ITEM_FULL_NAME}</tt> — '/'-separated job name, like "foo/bar".
</ul>

<p>
Changing this value allows you to put build records on a bigger but slow disk,
while keeping JENKINS_HOME on highly available backed up drive, for example.
Default value is <tt>${ITEM_ROOTDIR}/builds</tt>.
</div>

core/src/main/resources/jenkins/model/Jenkins/help-rawWorkspaceDir.html (Master)

Files

MISSING

11.03.2013 23:40:57, no SCM information

<div>
Specify where Jenkins would store job workspaces on the master node.
(It has no effect on builds run on slaves.)
This value can include the following variables.

<ul>
<li><tt>${JENKINS_HOME}</tt> — Jenkins home directory.
<li><tt>${ITEM_ROOTDIR}</tt> — Root directory of a job for which the default workspace is allocated.
<li><tt>${ITEM_FULL_NAME}</tt> — '/'-separated job name, like "foo/bar".
</ul>

<p>
Changing this value allows you to put workspaces on SSD, SCSI, or even ram disks.
Default value is <tt>${ITEM_ROOTDIR}/workspace</tt>.
</div>

core/src/main/resources/jenkins/model/Jenkins/legend_fr.properties

Files

legend.jelly

legend_fr.properties

OUTDATED

blue
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
The last build was successful.	Le dernier build s''est achevé avec succès.
(old value)

OUTDATED

blue_anime
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
The last build was successful. A new build is in progress.	Le dernier build s''est achevé avec succès. Un nouveau build est en cours.
(old value)

OUTDATED

grey
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
The project has never been built before, or the project is disabled.	Le projet n''a jamais été construit avant ou est désactivé.
(old value)

OUTDATED

grey_anime
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
The first build of the project is in progress.	Le premier build du projet est en cours.
(old value)

OUTDATED

health-00to20
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
Project health is 20% or less. You can hover the mouse over the project’s icon for a more detailed explanation.	La santé du projet est en dessous de 20%. Vous pouvez passer votre souris au dessus de l''icône du projet pour plus d''informations.
(old value)

OUTDATED

health-21to40
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
Project health is over 20% and up to 40%. You can hover the mouse over the project’s icon for a more detailed explanation.	La santé du projet est entre 20% et 40%. Vous pouvez passer votre souris au dessus de l''icône du projet pour plus d''informations.
(old value)

OUTDATED

health-41to60
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
Project health is over 40% and up to 60%. You can hover the mouse over the project’s icon for a more detailed explanation.	La santé du projet est entre 40% et 60%. Vous pouvez passer votre souris au dessus de l''icône du projet pour plus d''informations.
(old value)

OUTDATED

health-61to80
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
Project health is over 60% and up to 80%. You can hover the mouse over the project’s icon for a more detailed explanation.	La santé du projet est entre 60% et 80%. Vous pouvez passer votre souris au dessus de l''icône du projet pour plus d''informations.
(old value)

OUTDATED

health-81plus
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
Project health is over 80%. You can hover the mouse over the project’s icon for a more detailed explanation.	La santé du projet est au dessus de 80%. Vous pouvez passer votre souris au dessus de l''icône du projet pour plus d''informations.
(old value)

OUTDATED

red
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
The last build fatally failed.	Le dernier build est en échec.
(old value)

OUTDATED

red_anime
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
The last build fatally failed. A new build is in progress.	Le dernier build est en échec. Un nouveau build est en cours.
(old value)

OUTDATED

yellow
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
The last build was successful but unstable.This is primarily used to represent test failures.	Le dernier build s''est achevé avec succès mais est instable. Cela est utilisé principalement pour représenter des échecs sur les tests.
(old value)

OUTDATED

yellow_anime
01.08.2013 07:43:47, no SCM information	30.05.2013 20:09:20, no SCM information
The last build was successful but unstable. A new build is in progress.	Le dernier build s''est achevé avec succès mais est instable. Un nouveau build est en cours.
(old value)

core/src/main/resources/jenkins/model/Jenkins/load-statistics.jelly (Master)

Files

load-statistics.jelly

MISSING

Load Statistics
04.02.2013 00:16:08, no SCM information
Load Statistics

core/src/main/resources/jenkins/model/Jenkins/login_fr.properties

Files

login_fr.properties

CURRENT

Password
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Password	Mot de passe

CURRENT

Remember me on this computer
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Remember me on this computer	Conserver mes informations sur cet ordinateur

CURRENT

User
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
User	Utilisateur

CURRENT

login
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
log in	S''identifier

CURRENT

signUp
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
<a href="signup">Create an account</a> if you are not a member yet.	<a href="signup">Créez un compte</a> si vous n''êtes pas encore membre.

core/src/main/resources/jenkins/model/Jenkins/loginError_fr.properties

Files

loginError.jelly

loginError_fr.properties

MISSING

Login Error
04.02.2013 00:16:08, no SCM information
Login Error

CURRENT

If you are a system administrator and suspect this to be a configuration problem, see the server console output for more details.
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
If you are a system administrator and suspect this to be a configuration problem, see the server console output for more details.	Si vous êtes administrateur système et que vous souspconer un problème de configuration, reportez vous à la sortie console pour plus de détail

CURRENT

Invalid login information. Please try again.
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Invalid login information. Please try again.	Identification invalide. Merci d''essayer à nouveau.

CURRENT

Try again
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Try again	Essayez à nouveau.

core/src/main/resources/jenkins/model/Jenkins/manag_.groovy (Master)

Files

manag_.groovy

MISSING

Cancel Shutdown
04.02.2013 00:16:08, no SCM information
Cancel Shutdown

MISSING

Configure System
04.02.2013 00:16:08, no SCM information
Configure System

MISSING

Configure global settings and paths.
04.02.2013 00:16:08, no SCM information
Configure global settings and paths.

MISSING

Manage Jenkins
04.02.2013 00:16:08, no SCM information
Manage Jenkins

MISSING

Prepare for Shutdown
04.02.2013 00:16:08, no SCM information
Prepare for Shutdown

MISSING

Stops executing new builds, so that the system can be eventually shut down safely.
04.02.2013 00:16:08, no SCM information
Stops executing new builds, so that the system can be eventually shut down safely.

core/src/main/resources/jenkins/model/Jenkins/manage_fr.properties

Files

manage.jelly

manage_fr.properties

MISSING

are.you.sure
29.04.2013 12:15:14, no SCM information
{0}: are you sure?

OUTDATED

Manage Jenkins
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:08, no SCM information
Manage Jenkins	Administrer Jenkins
(old value)

core/src/main/resources/jenkins/model/Jenkins/newView_fr.properties

Files

newView.jelly

newView_fr.properties

MISSING

New View
29.04.2013 12:15:14, no SCM information
New View

OUTDATED

View name
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:08, no SCM information
View name	Nom de la vue
(old value)

core/src/main/resources/jenkins/model/Jenkins/noPrincipal.jelly (Master)

Files

noPrincipal.jelly

MISSING

blurb
04.02.2013 00:16:08, no SCM information
The web container doesn't seem to be configured to do authentication. Check the container documentation and/or also consult <tt>jenkins-users@googlegroups.com</tt>

core/src/main/resources/jenkins/model/Jenkins/oops.jelly (Master)

Files

oops.jelly

projectRelationship-help.jelly

MISSING

Bug tracker
28.06.2013 06:41:00, no SCM information
Bug tracker

MISSING

Jenkins project
28.06.2013 06:41:00, no SCM information
Jenkins project

MISSING

Mailing Lists
28.06.2013 06:41:00, no SCM information
Mailing Lists

MISSING

Oops!
28.06.2013 06:41:00, no SCM information
Oops!

MISSING

Stack trace
28.06.2013 06:41:00, no SCM information
Stack trace

MISSING

Twitter: @jenkinsci
28.06.2013 06:41:00, no SCM information
Twitter: @jenkinsci

MISSING

checkJIRA
28.06.2013 06:41:00, no SCM information
Please check <a href="https://issues.jenkins-ci.org/">our bug tracker</a> to see if a similar problem has already been reported.

MISSING

checkML
28.06.2013 06:41:00, no SCM information
<a href="http://jenkins-ci.org/content/mailing-lists">The users list</a> might be also useful in understanding what has happened.

MISSING

pleaseReport
28.06.2013 06:41:00, no SCM information
If you think this is a new issue, please file a new issue.

MISSING

problemHappened
28.06.2013 06:41:00, no SCM information
A problem occurred while processing the request.

MISSING

stackTracePlease
28.06.2013 06:41:00, no SCM information
When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins.

MISSING

vote
28.06.2013 06:41:00, no SCM information
If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem.

core/src/main/resources/jenkins/model/Jenkins/projectRelationship-help_fr.properties

Files

projectRelationship-help_fr.properties

MISSING

The downstream project records the fingerprints of the upstream files it uses
04.02.2013 00:16:08, no SCM information
The downstream project records the fingerprints of the upstream files it uses

OUTDATED

Title
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:08, no SCM information
What’s "project relationship"?	Que sont les "relations entre projets"?
(old value)

OUTDATED

body
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:08, no SCM information
When you have projects that depend on each other, Jenkins can track which build of the upstream project is used by which build of the downstream project, by using the records created by <a href="https://wiki.jenkins-ci.org/display/JENKINS/Fingerprint">the fingerprint support</a>.	Lorsque vous avez des projets qui dépendent les uns des autres, Jenkins peut tracer quel build de projet en amont est utilisé par quel build de projet en aval, en utilisant les enregistrements créés par <a href="https://wiki.jenkins-ci.org/display/JENKINS/Fingerprint">le support de l''empreinte numérique</a>.
(old value)

ORPHANED

The downstream project records the fingerprints of the upstream jar files it uses
	04.02.2013 00:16:08, no SCM information
	Le projet en aval enregistre les empreintes numériques des fichiers jar en amont qu''il utilise

CURRENT

For this feature to work, the following conditions need to be met:
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
For this feature to work, the following conditions need to be met:	Pour que cette fonctionnalité marche, les conditions suivantes sont requises:

CURRENT

The upstream project records the fingerprints of its build artifacts
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
The upstream project records the fingerprints of its build artifacts	Le projet en amont enregistre les empreintes numériques de ses artefacts de build

CURRENT

This allows Jenkins to correlate two projects.
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
This allows Jenkins to correlate two projects.	Cela permet à Jenkins de mettre en corrélation deux projets.

core/src/main/resources/jenkins/model/Jenkins/projectRelationship_fr.properties

Files

projectRelationship.jelly

projectRelationship_fr.properties

MISSING

There are no fingerprint records that connect these two projects.
04.02.2013 00:16:08, no SCM information
There are no fingerprint records that connect these two projects.

CURRENT

Compare
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Compare	Comparer

CURRENT

Project Relationship
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Project Relationship	Relations entre les projets

CURRENT

downstream project
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
downstream project	projet en aval

CURRENT

upstream project
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
upstream project	projet en amont

core/src/main/resources/jenkins/model/Jenkins/systemInfo_fr.properties

Files

systemInfo.jelly

systemInfo_fr.properties

MISSING

No plugins installed.
04.02.2013 00:16:08, no SCM information
No plugins installed.

MISSING

Plugins
04.02.2013 00:16:08, no SCM information
Plugins

MISSING

System Information
04.02.2013 00:16:08, no SCM information
System Information

MISSING

Thread Dumps
04.02.2013 00:16:08, no SCM information
Thread Dumps

MISSING

threadDump_blurb
04.02.2013 00:16:08, no SCM information
Visit <a href="{0}">this page</a> for master and slave thread dumps.

CURRENT

Enabled
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Enabled	En effet

CURRENT

Environment Variables
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Environment Variables	Variables d''environnement

CURRENT

Name
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Name	Nom

CURRENT

Pinned
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Pinned	Repéré

CURRENT

System Properties
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
System Properties	Propriétés système

CURRENT

Version
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Version	Version

core/src/main/resources/jenkins/model/Jenkins/threadDump.jelly (Master)

Files

threadDump.jelly

MISSING

Thread Dump
04.02.2013 00:16:08, no SCM information
Thread Dump

MISSING

Thread dump
04.02.2013 00:16:08, no SCM information
Thread dump

core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/config_fr.properties

Files

help-adminAddress_fr.html

MISSING

Jenkins Location
04.02.2013 00:16:08, no SCM information
Jenkins Location

MISSING

System Admin e-mail address
04.02.2013 00:16:08, no SCM information
System Admin e-mail address

ORPHANED

System Admin E-mail Address
	04.02.2013 00:16:08, no SCM information
	Adresse email de l''administrateur systËme

CURRENT

Jenkins URL
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Jenkins URL	URL de Jenkins

core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-adminAddress_fr.html

Files

help-adminAddress.html

CURRENT

04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
<div> Notification e-mails from Jenkins to project owners will be sent with this address in the from header. This can be just "foo@acme.org" or it could be something like "Jenkins Daemon <foo@acme.org>" </div>	<div> Les emails de notification envoyés par Jenkins aux propriétaires des projets seront envoyés avec cette adresse dans le champ expéditeur. Cela peut être simplement "foo@acme.org" ou quelque chose comme "Jenkins Daemon <foo@acme.org>" </div>

core/src/main/resources/jenkins/model/JenkinsLocationConfiguration/help-url_fr.html

Files

help-url.html

help-url_fr.html

CURRENT

04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
<div> Optionally specify the HTTP address of the Jenkins installation, such as <tt>http://yourhost.yourdomain/jenkins/</tt>. This value is used to let Jenkins know how to refer to itself, ie. to display images or to create links in emails. <p> This is necessary because Jenkins cannot reliably detect such a URL from within itself. </div>	<div> Spécifie optionnellement l'adresse HTTP de l'installation de Jenkins, comme <tt>http://yourhost.yourdomain/jenkins/</tt>. Cette valeur est utilisée pour mettre des liens dans les emails envoyés par Jenkins. <p> Cela est nécessaire parce que Jenkins ne peut pas détecter de façon fiable sa propre URL. </div>

core/src/main/resources/jenkins/model/MasterBuildConfiguration/config_fr.properties

Files

CURRENT

# of executors
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
# of executors	Nb d''exécuteurs

CURRENT

Labels
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Labels	Libellés

core/src/main/resources/jenkins/model/Messages_fr.properties

Files

MISSING

CLI.cancel-quiet-down.shortDescription
01.08.2013 07:43:47, no SCM information
Cancel the effect of the "quiet-down" command.

MISSING

CLI.keep-build.shortDescription
01.08.2013 07:43:47, no SCM information
Mark the build to keep the build forever.

MISSING

CLI.quiet-down.shortDescription
01.08.2013 07:43:47, no SCM information
Quiet down Jenkins, in preparation for a restart. Don’t start any builds.

MISSING

CLI.reload-configuration.shortDescription
01.08.2013 07:43:47, no SCM information
Discard all the loaded data in memory and reload everything from file system. Useful when you modified config files directly on disk.

MISSING

CLI.restart.shortDescription
01.08.2013 07:43:47, no SCM information
Restart Jenkins

MISSING

CLI.safe-restart.shortDescription
01.08.2013 07:43:47, no SCM information
Safely restart Jenkins

MISSING

CLI.safe-shutdown.shortDescription
01.08.2013 07:43:47, no SCM information
Puts Jenkins into the quiet mode, wait for existing builds to be completed, and then shut down Jenkins.

MISSING

CLI.shutdown.shortDescription
01.08.2013 07:43:47, no SCM information
Immediately shuts down Jenkins server

MISSING

CauseOfInterruption.ShortDescription
01.08.2013 07:43:47, no SCM information
Aborted by {0}

MISSING

DefaultProjectNamingStrategy.DisplayName
01.08.2013 07:43:47, no SCM information
Default

MISSING

Hudson.JobNameConventionNotApplyed
01.08.2013 07:43:47, no SCM information
‘{0}’ does not match the job name convention pattern {1}

MISSING

Hudson.NodeBeingRemoved
01.08.2013 07:43:47, no SCM information
Node is being removed

MISSING

Hudson.NodeDescription
01.08.2013 07:43:47, no SCM information
the master Jenkins node

MISSING

Mailer.Address.Not.Configured
01.08.2013 07:43:47, no SCM information
address not configured yet <nobody@nowhere>

MISSING

Mailer.Localhost.Error
01.08.2013 07:43:47, no SCM information
Please set a valid host name, instead of localhost

MISSING

PatternProjectNamingStrategy.DisplayName
01.08.2013 07:43:47, no SCM information
Pattern

MISSING

PatternProjectNamingStrategy.NamePatternInvalidSyntax
01.08.2013 07:43:47, no SCM information
regular expression's syntax is invalid.

MISSING

PatternProjectNamingStrategy.NamePatternRequired
01.08.2013 07:43:47, no SCM information
Name Pattern is required

OUTDATED

Hudson.BadPortNumber
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:08, no SCM information
Bad port number {0}	Numéro de port incorrect {0}
(old value)

OUTDATED

Hudson.Computer.Caption
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:08, no SCM information
Master	Maître
(old value)

OUTDATED

Hudson.Computer.DisplayName
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:08, no SCM information
master	maître
(old value)

OUTDATED

Hudson.ControlCodeNotAllowed
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:08, no SCM information
No control code is allowed: {0}	Code de contrôle non autorisé
(old value)

OUTDATED

Hudson.DisplayName
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:08, no SCM information
Jenkins	Jenkins
(old value)

OUTDATED

Hudson.JobAlreadyExists
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:08, no SCM information
A job already exists with the name ‘{0}’	Un job existe déjà avec le nom ''{0}''
(old value)

OUTDATED

Hudson.NoJavaInPath
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:08, no SCM information
java is not in your PATH. Maybe you need to <a href="{0}/configure">configure JDKs</a>?	java n''est pas dans votre PATH. Peut-être avez-vous besoin de <a href=''{0}/configure''>configurer les JDKs</a>?
(old value)

OUTDATED

Hudson.NoName
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:08, no SCM information
No name is specified	Aucune nom n''est spécifié
(old value)

OUTDATED

Hudson.NotUsesUTF8ToDecodeURL
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:08, no SCM information
Your container doesn’t use UTF-8 to decode URLs. If you use non-ASCII characters as a job name etc, this will cause problems. See <a href="http://wiki.jenkins-ci.org/display/JENKINS/Containers">Containers</a> and <a href="http://wiki.jenkins-ci.org/display/JENKINS/Tomcat#Tomcat-i18n">Tomcat i18n</a> for more details.	Votre conteneur n''utilise pas UTF-8 pour décoder les URLs. Si vous utilisez des caractères non-ASCII dans le nom d''un job ou autre, cela causera des problèmes. Consultez les pages sur les <a href=''http://wiki.jenkins-ci.org/display/JENKINS/Containers''>conteneurs</a> et sur <a href=''http://wiki.jenkins-ci.org/display/JENKINS/Tomcat#Tomcat-i18n''>Tomcat i18n</a> pour plus de détails.
(old value)

OUTDATED

Hudson.ReadPermission.Description
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:08, no SCM information
The read permission is necessary for viewing almost all pages of Jenkins. This permission is useful when you don’t want unauthenticated users to see Jenkins pages — revoke this permission from the anonymous user, then add "authenticated" pseudo-user and grant the read access.	Le droit en lecture est nécessaire pour voir la plupart des pages de Jenkins. Ce droit est utile quand vous ne voulez pas que les utilisateurs non authentifiés puissent voir les pages Jenkins — retirez ce droit à l''utilisateur anonymous, puis ajoutez le pseudo-utilisateur "authenticated" et accordez-lui le droit en lecture.
(old value)

OUTDATED

Hudson.UnsafeChar
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:08, no SCM information
‘{0}’ is an unsafe character	''{0}'' est un caractère dangereux
(old value)

OUTDATED

Hudson.ViewAlreadyExists
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:08, no SCM information
A view already exists with the name "{0}"	Une vue existe déjà avec le nom "{0}"
(old value)

OUTDATED

Hudson.ViewName
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:08, no SCM information
All	Tous
(old value)

core/src/main/resources/jenkins/model/ProjectNamingStrategy/PatternProjectNamingStrategy/config.groovy (Master)

Files

MISSING

description
20.09.2013 10:05:40, no SCM information
Description

MISSING

forceExistingJobs
20.09.2013 10:05:40, no SCM information
force existing

MISSING

namePattern
20.09.2013 10:05:40, no SCM information
Name Pattern

core/src/main/resources/jenkins/model/ProjectNamingStrategy/PatternProjectNamingStrategy/help-description.html (Master)

Files

help-description.html

MISSING

20.09.2013 10:05:40, no SCM information
<p> Provide a human-readable description to explain naming constraints. Will be used as error message when job name does not match pattern </p>

core/src/main/resources/jenkins/mvn/DefaultGlobalSettingsProvider/help.html (Master)

Files

MISSING

04.02.2013 00:16:08, no SCM information
<div> Use default maven settings (<tt>$HOME/.m2/settings.xml</tt>) as set on build node. </div>

core/src/main/resources/jenkins/mvn/DefaultSettingsProvider/help.html (Master)

Files

MISSING

04.02.2013 00:16:08, no SCM information
<div> Use default maven settings (<tt>$HOME/.m2/settings.xml</tt>) as set on build node. </div>

core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/config.jelly (Master)

Files

MISSING

File path
04.02.2013 00:16:08, no SCM information
File path

core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help-path.html (Master)

Files

help-path.html

MISSING

04.02.2013 00:16:08, no SCM information
<div> Path to settings.xml file, relative to project workspace or absolute (variables are supported). </div>

core/src/main/resources/jenkins/mvn/FilePathGlobalSettingsProvider/help.html (Master)

Files

MISSING

04.02.2013 00:16:08, no SCM information
<div> Use a custom global <tt>settings.xml</tt> file from job workspace. Such a file is checked out from SCM as part of the job or a well known location. </div>

core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/config.jelly (Master)

Files

MISSING

File path
04.02.2013 00:16:08, no SCM information
File path

core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help-path.html (Master)

Files

help-path.html

MISSING

04.02.2013 00:16:08, no SCM information
<div> Path to settings.xml file, relative to project workspace or absolute (variables are supported). </div>

core/src/main/resources/jenkins/mvn/FilePathSettingsProvider/help.html (Master)

Files

MISSING

04.02.2013 00:16:08, no SCM information
<div> Use a custom <tt>settings.xml</tt> file. Such a file is checked out from SCM as part of the job or a well known location. </div>

core/src/main/resources/jenkins/mvn/GlobalMavenConfig/config.groovy (Master)

Files

MISSING

Default global settings provider
18.05.2013 17:17:16, no SCM information
Default global settings provider

MISSING

Default settings provider
18.05.2013 17:17:16, no SCM information
Default settings provider

MISSING

Maven Configuration
18.05.2013 17:17:16, no SCM information
Maven Configuration

core/src/main/resources/jenkins/mvn/Messages.properties (Master)

Files

MISSING

DefaultGlobalSettingsProvider.DisplayName
04.02.2013 00:16:08, no SCM information
Use default maven global settings

MISSING

DefaultSettingsProvider.DisplayName
04.02.2013 00:16:08, no SCM information
Use default maven settings

MISSING

FilePathGlobalSettingsProvider.DisplayName
04.02.2013 00:16:08, no SCM information
Global settings file on filesystem

MISSING

FilePathSettingsProvider.DisplayName
04.02.2013 00:16:08, no SCM information
Settings file in filesystem

core/src/main/resources/jenkins/security/ApiTokenProperty/config.groovy (Master)

Files

MISSING

API Token
04.02.2013 00:16:08, no SCM information
API Token

MISSING

Change API Token
04.02.2013 00:16:08, no SCM information
Change API Token

MISSING

Show API Token
04.02.2013 00:16:08, no SCM information
Show API Token

MISSING

Show API token
04.02.2013 00:16:08, no SCM information
Show API token

core/src/main/resources/jenkins/security/ApiTokenProperty/help-apiToken.html (Master)

Files

help-apiToken.html

MISSING

04.02.2013 00:16:08, no SCM information
<div> This API token can be used for authenticating yourself in the REST API call. See <a href="https://wiki.jenkins-ci.org/display/JENKINS/Remote+access+API">our wiki</a> for more details. The API token should be protected like your password, as it allows other people to access Jenkins as you. </div>

core/src/main/resources/jenkins/security/Messages.properties (Master)

Files

MISSING

ApiTokenProperty.ChangeToken.Success
01.08.2013 07:43:47, no SCM information
<div>Updated</div>

MISSING

ApiTokenProperty.DisplayName
01.08.2013 07:43:47, no SCM information
API Token

MISSING

RekeySecretAdminMonitor.DisplayName
01.08.2013 07:43:47, no SCM information
Re-keying

core/src/main/resources/jenkins/security/QueueItemAuthenticatorConfiguration/config.groovy (Master)

Files

MISSING

Access Control for Builds
14.06.2013 07:43:03, no SCM information
Access Control for Builds

core/src/main/resources/jenkins/security/RekeySecretAdminMonitor/message.groovy (Master)

Files

message.groovy

booleanRadio_fr.properties

MISSING

Dismiss this message
01.08.2013 07:43:47, no SCM information
Dismiss this message

MISSING

Re-key in background now
01.08.2013 07:43:47, no SCM information
Re-key in background now

MISSING

Re-keying currently scheduled during the next startup
01.08.2013 07:43:47, no SCM information
Re-keying currently scheduled during the next startup

MISSING

Schedule a re-key during the next startup
01.08.2013 07:43:47, no SCM information
Schedule a re-key during the next startup

MISSING

pleaseRekeyAsap
04.02.2013 00:16:08, no SCM information
Because of <a href="https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-01-04">a security vulnerability</a> discovered earlier, we need to change the encryption key used to protect secrets in your configuration files on the disk. This process scans a large portion of your <tt>$JENKINS_HOME</tt> ({0}), find encrypted data, re-key them, which will take some time. See <a href="http://jenkins-ci.org/rekey">this document</a> for more implications about different ways of doing this (or not doing this.) This operation can be safely run in background, but cautious users are recommended to take backups.

MISSING

rekeyHadProblems
04.02.2013 00:16:08, no SCM information
Re-keying has completed, but there were problems. <a href="{0}">Please check the log</a>.

MISSING

rekeyInProgress
04.02.2013 00:16:08, no SCM information
Re-keying is in progress. <a href="{0}/log">You can check the log</a>.

MISSING

rekeySuccessful
04.02.2013 00:16:08, no SCM information
Secrets in your <tt>$JENKINS_HOME</tt> has been re-keyed successfully. <a href="{0}/log">Please check the log</a>, confirm the success, and then dismiss or re-run.

core/src/main/resources/lib/form/advanced_fr.properties

Files

advanced.jelly

advanced_fr.properties

MISSING

customizedFields
29.08.2013 16:34:29, no SCM information
One or more fields in this block have been edited.

OUTDATED

Advanced
29.08.2013 16:34:29, no SCM information	04.02.2013 00:16:08, no SCM information
Advanced	Avancé
(old value)

core/src/main/resources/lib/form/apply_fr.properties

Files

apply.jelly

apply_fr.properties

OUTDATED

Apply
21.06.2013 06:36:29, no SCM information	30.05.2013 20:09:20, no SCM information
Apply	Appliquer
(old value)

core/src/main/resources/lib/form/booleanRadio_fr.properties

Files

booleanRadio.jelly

OUTDATED

No
29.08.2013 16:34:29, no SCM information	30.05.2013 20:09:20, no SCM information
No	Non
(old value)

OUTDATED

Yes
29.08.2013 16:34:29, no SCM information	30.05.2013 20:09:20, no SCM information
Yes	Oui
(old value)

core/src/main/resources/lib/form/breadcrumb-config-outline_fr.properties

Files

breadcrumb-config-outline.jelly

breadcrumb-config-outline_fr.properties

CURRENT

configuration
04.02.2013 00:16:08, no SCM information	30.05.2013 20:09:20, no SCM information
configuration	configuration

core/src/main/resources/lib/form/expandableTextbox_fr.properties

Files

expandableTextbox.jelly

expandableTextbox_fr.properties

CURRENT

tooltip
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Click to expand to multiple lines<br />where you can use new lines instead of space.<br />To revert back to single line, write everything in one line then submit.	Cliquez pour obtenir des lignes multiples<br />et pouvoir utiliser des nouvelles lignes plutôt que des espaces.<br />Pour retourner sur une ligne unique, écrivez tout sur une seule ligne et envoyez vos changements.

core/src/main/resources/lib/form/helpArea_fr.properties

Files

helpArea.jelly

helpArea_fr.properties

CURRENT

Loading...
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Loading...	Chargement...

core/src/main/resources/lib/form/hetero-list_fr.properties

Files

hetero-list.jelly

hetero-list_fr.properties

CURRENT

Add
04.02.2013 00:16:08, no SCM information	30.05.2013 20:09:20, no SCM information
Add	Ajouter

core/src/main/resources/lib/form/repeatable_fr.properties

Files

repeatable.jelly

repeatable_fr.properties

CURRENT

Add
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Add	Ajouter

core/src/main/resources/lib/form/repeatableDeleteButton_fr.properties

Files

repeatableDeleteButton.jelly

repeatableDeleteButton_fr.properties

CURRENT

Delete
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Delete	Supprimer

core/src/main/resources/lib/form/serverTcpPort_fr.properties

Files

serverTcpPort.groovy

serverTcpPort_fr.properties

CURRENT

Disable
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Disable	Désactivé

CURRENT

Fixed
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Fixed	Fixe

CURRENT

Random
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Random	Au hasard

core/src/main/resources/lib/form/slave-mode_fr.properties

Files

slave-mode.jelly

slave-mode_fr.properties

CURRENT

Usage
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Usage	Utilisation

core/src/main/resources/lib/form/textarea_fr.properties

Files

textarea.jelly

textarea_fr.properties

OUTDATED

Hide preview
29.08.2013 16:34:29, no SCM information	04.02.2013 00:16:08, no SCM information
Hide preview	Masquer l''aperçu
(old value)

OUTDATED

Preview
29.08.2013 16:34:29, no SCM information	04.02.2013 00:16:08, no SCM information
Preview	Aperçu
(old value)

core/src/main/resources/lib/hudson/artifactList_fr.properties

Files

artifactList.jelly

artifactList_fr.properties

CURRENT

View
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
View	Afficher

core/src/main/resources/lib/hudson/buildCaption_fr.properties

Files

buildCaption.jelly

buildCaption_fr.properties

OUTDATED

Progress
19.02.2013 07:05:52, no SCM information	04.02.2013 00:16:08, no SCM information
Progress	Avancement
(old value)

OUTDATED

cancel
19.02.2013 07:05:52, no SCM information	04.02.2013 00:16:08, no SCM information
cancel	Annuler
(old value)

core/src/main/resources/lib/hudson/buildHealth_fr.properties

Files

buildHealth.jelly

buildHealth_fr.properties

CURRENT

Description
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Description	Description

core/src/main/resources/lib/hudson/buildListTable_fr.properties

Files

buildListTable.jelly

buildListTable_fr.properties

MISSING

Click to center timeline on event
30.05.2013 20:09:20, no SCM information
Click to center timeline on event

OUTDATED

Build
30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:08, no SCM information
Build	Construction
(old value)

OUTDATED

Console output
30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:08, no SCM information
Console output	Sortie console
(old value)

OUTDATED

Status
30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:08, no SCM information
Status	État
(old value)

OUTDATED

Time Since
30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:08, no SCM information
Time Since	Temps écoulé
(old value)

core/src/main/resources/lib/hudson/buildProgressBar_fr.properties

Files

buildProgressBar.jelly

buildProgressBar_fr.properties

CURRENT

text
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Started {0} ago<br> Estimated remaining time: {1}	Démarré il y a {0}<br/> Temps restant estimé : {1}

core/src/main/resources/lib/hudson/editableDescription_fr.properties

Files

editableDescription.jelly

editableDescription_fr.properties

CURRENT

add description
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
add description	ajouter une description

CURRENT

edit description
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
edit description	Modifier la description

core/src/main/resources/lib/hudson/executors_fr.properties

Files

executors.jelly

executors_fr.properties

MISSING

Unknown Task
30.05.2013 20:09:20, no SCM information
Unknown Task

OUTDATED

Build Executor Status
30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:08, no SCM information
Build Executor Status	État du lanceur de constructions
(old value)

OUTDATED

Building
30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:08, no SCM information
Building	En cours d''éxecution
(old value)

OUTDATED

Dead
30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:08, no SCM information
Dead	Hors service
(old value)

OUTDATED

Idle
30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:08, no SCM information
Idle	En attente
(old value)

OUTDATED

Offline
30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:08, no SCM information
Offline	Déconnecté
(old value)

OUTDATED

Status
30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:08, no SCM information
Status	Statut
(old value)

OUTDATED

offline
30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:08, no SCM information
offline	déconnecté
(old value)

OUTDATED

suspended
30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:08, no SCM information
suspended	suspendu
(old value)

OUTDATED

terminate this build
30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:08, no SCM information
terminate this build	arrêter ce build
(old value)

ORPHANED

Master
	04.02.2013 00:16:08, no SCM information
	Maître

core/src/main/resources/lib/hudson/iconSize_fr.properties

Files

iconSize.jelly

iconSize_fr.properties

CURRENT

Icon
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Icon	Icône

core/src/main/resources/lib/hudson/listScmBrowsers_fr.properties

Files

listScmBrowsers.jelly

listScmBrowsers_fr.properties

EMPTY

Auto
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Auto	—

CURRENT

Repository browser
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Repository browser	Navigateur de la base de code

core/src/main/resources/lib/hudson/newFromList/form_fr.properties

Files

form.jelly

form_fr.properties

CURRENT

Copy from
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Copy from	Copier à partir de

core/src/main/resources/lib/hudson/node_fr.properties

Files

node.jelly

node_fr.properties

OUTDATED

master
29.04.2013 12:15:14, no SCM information	04.02.2013 00:16:08, no SCM information
master	maître
(old value)

core/src/main/resources/lib/hudson/project/build-permalink_fr.properties

Files

build-permalink.jelly

build-permalink_fr.properties

CURRENT

format
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
{0} (#{1}), {2} ago	{0} (#{1}), il y a {2}

core/src/main/resources/lib/hudson/project/config-assignedLabel.jelly (Master)

Files

config-assignedLabel.jelly

config-blockWhenDownstreamBuilding.jelly

MISSING

Label Expression
21.06.2013 06:36:29, no SCM information
Label Expression

MISSING

Restrict where this project can be run
21.06.2013 06:36:29, no SCM information
Restrict where this project can be run

core/src/main/resources/lib/hudson/project/config-blockWhenDownstreamBuilding_fr.properties

Files

config-blockWhenDownstreamBuilding_fr.properties

CURRENT

Block build when downstream project is building
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Block build when downstream project is building	Empêcher le build quand un projet en aval est en cours de build

core/src/main/resources/lib/hudson/project/config-blockWhenUpstreamBuilding_fr.properties

Files

config-blockWhenUpstreamBuilding.jelly

config-blockWhenUpstreamBuilding_fr.properties

CURRENT

Block build when upstream project is building
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Block build when upstream project is building	Empêcher le build quand un projet en amont est en cours de build

core/src/main/resources/lib/hudson/project/config-buildWrappers_fr.properties

Files

config-buildWrappers.jelly

config-buildWrappers_fr.properties

CURRENT

Build Environment
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Build Environment	Environnements de Build

core/src/main/resources/lib/hudson/project/config-builders_fr.properties

Files

config-builders.jelly

config-builders_fr.properties

EMPTY

Build
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Build	—

CURRENT

Add build step
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Add build step	Ajouter une étape au build

core/src/main/resources/lib/hudson/project/config-concurrentBuild_fr.properties

Files

config-concurrentBuild.jelly

config-concurrentBuild_fr.properties

CURRENT

title.concurrentbuilds
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Execute concurrent builds if necessary	Exécuter des builds simultanément si nécessaire

core/src/main/resources/lib/hudson/project/config-customWorkspace_fr.properties

Files

config-customWorkspace.jelly

config-customWorkspace_fr.properties

CURRENT

Directory
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Directory	Répertoire

CURRENT

Use custom workspace
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Use custom workspace	Utiliser un répertoire de travail spécifique

core/src/main/resources/lib/hudson/project/config-disableBuild_fr.properties

Files

config-disableBuild.jelly

config-disableBuild_fr.properties

CURRENT

Disable Build
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Disable Build	Désactiver le Build

CURRENT

No new builds will be executed until the project is re-enabled.
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
No new builds will be executed until the project is re-enabled.	Aucun nouveau build ne sera exécuté jusqu''à ce que le projet soit réactivé.

core/src/main/resources/lib/hudson/project/config-publishers_fr.properties

Files

config-publishers.jelly

config-publishers_fr.properties

CURRENT

Post-build Actions
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Post-build Actions	Actions à la suite du build

core/src/main/resources/lib/hudson/project/config-publishers2_fr.properties

Files

config-publishers2.jelly

config-publishers2_fr.properties

MISSING

Add post-build action
04.02.2013 00:16:08, no SCM information
Add post-build action

CURRENT

Post-build Actions
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Post-build Actions	Actions à la suite du build

core/src/main/resources/lib/hudson/project/config-quietPeriod_fr.properties

Files

config-quietPeriod.jelly

config-quietPeriod_fr.properties

CURRENT

Number of seconds
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Number of seconds	Nombre de secondes

CURRENT

Quiet period
04.02.2013 00:16:08, no SCM information	04.02.2013 00:16:08, no SCM information
Quiet period	Période d''attente

core/src/main/resources/lib/hudson/project/config-retryCount_fr.properties

Files

config-retryCount.jelly

config-retryCount_fr.properties

CURRENT

Retry Count
04.02.2013 00:16:08, no SCM information	24.02.2013 10:14:59, no SCM information
Retry Count	Nombre de ré-essais

CURRENT

SCM checkout retry count
04.02.2013 00:16:08, no SCM information	24.02.2013 10:14:59, no SCM information
SCM checkout retry count	Nombre de retentatives de checkout du SCM

core/src/main/resources/lib/hudson/project/config-scm_fr.properties

Files

config-scm.jelly

config-scm_fr.properties

MISSING

Advanced Source Code Management
04.02.2013 00:16:09, no SCM information
Advanced Source Code Management

MISSING

SCM Checkout Strategy
04.02.2013 00:16:09, no SCM information
SCM Checkout Strategy

CURRENT

Source Code Management
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Source Code Management	Gestion de code source

core/src/main/resources/lib/hudson/project/config-trigger_fr.properties

Files

config-trigger.jelly

config-trigger_fr.properties

CURRENT

Build Triggers
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Build Triggers	Ce qui déclenche le build

core/src/main/resources/lib/hudson/project/config-upstream-pseudo-trigger_fr.properties

Files

config-upstream-pseudo-trigger.jelly

config-upstream-pseudo-trigger_fr.properties

MISSING

Project names
19.02.2013 07:05:52, no SCM information
Project names

OUTDATED

Build after other projects are built
19.02.2013 07:05:52, no SCM information	04.02.2013 00:16:09, no SCM information
Build after other projects are built	Construire à la suite d''autres projets (projets en amont)
(old value)

OUTDATED

Multiple projects can be specified like 'abc, def'
19.02.2013 07:05:52, no SCM information	04.02.2013 00:16:09, no SCM information
Multiple projects can be specified like 'abc, def'	Plusieurs projets peuvent être spécifiés en les séparant par des virgules: 'abc, def'
(old value)

ORPHANED

Projects names
	04.02.2013 00:16:09, no SCM information
	Noms des projets

core/src/main/resources/lib/hudson/project/matrix_fr.properties

Files

matrix.jelly

matrix_fr.properties

CURRENT

Configuration Matrix
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Configuration Matrix	Matrice de Configuration

CURRENT

Configurations
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Configurations	Configurations

core/src/main/resources/lib/hudson/project/upstream-downstream_fr.properties

Files

upstream-downstream.jelly

upstream-downstream_fr.properties

CURRENT

Downstream Projects
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Downstream Projects	Projets en aval

CURRENT

Upstream Projects
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Upstream Projects	Projets en amont

core/src/main/resources/lib/hudson/propertyTable_fr.properties

Files

propertyTable.jelly

propertyTable_fr.properties

OUTDATED

Name
23.07.2013 16:05:31, no SCM information	04.02.2013 00:16:09, no SCM information
Name	Nom
(old value)

OUTDATED

Value
23.07.2013 16:05:31, no SCM information	04.02.2013 00:16:09, no SCM information
Value	Valeur
(old value)

core/src/main/resources/lib/hudson/queue_fr.properties

Files

queue.jelly

queue_fr.properties

MISSING

Unknown Task
14.06.2013 07:43:03, no SCM information
Unknown Task

MISSING

WaitingFor
04.02.2013 00:16:09, no SCM information
Waiting for {0}

OUTDATED

Build Queue
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:09, no SCM information
Build Queue	File d''attente des constructions
(old value)

OUTDATED

Jenkins is going to shut down. No further builds will be performed.
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:09, no SCM information
Jenkins is going to shut down. No further builds will be performed.	Jenkins est en cours de fermeture. Aucun nouveau build ne sera lancé.
(old value)

OUTDATED

No builds in the queue.
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:09, no SCM information
No builds in the queue.	File d''attente des constructions vide
(old value)

OUTDATED

cancel
14.06.2013 07:43:03, no SCM information	04.02.2013 00:16:09, no SCM information
cancel	Annuler
(old value)

ORPHANED

appears to be stuck
	04.02.2013 00:16:09, no SCM information
	semble être bloqué

core/src/main/resources/lib/hudson/rssBar_fr.properties

Files

rssBar.jelly

rssBar_fr.properties

OUTDATED

Legend
29.08.2013 16:34:29, no SCM information	04.02.2013 00:16:09, no SCM information
Legend	Légende
(old value)

OUTDATED

for all
29.08.2013 16:34:29, no SCM information	04.02.2013 00:16:09, no SCM information
for all	pour toutes
(old value)

OUTDATED

for failures
29.08.2013 16:34:29, no SCM information	04.02.2013 00:16:09, no SCM information
for failures	pour tous les échecs
(old value)

OUTDATED

for just latest builds
29.08.2013 16:34:29, no SCM information	04.02.2013 00:16:09, no SCM information
for just latest builds	juste pour les derniers échecs
(old value)

core/src/main/resources/lib/hudson/scriptConsole_fr.properties

Files

scriptConsole.jelly

scriptConsole_fr.properties

MISSING

description2
01.08.2013 07:43:47, no SCM information
All the classes from all the plugins are visible. <tt>jenkins.</tt>, <tt>jenkins.model.</tt>, <tt>hudson.</tt>, and <tt>hudson.model.</tt> are pre-imported.

OUTDATED

description
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:09, no SCM information
Type in an arbitrary <a href="http://groovy.codehaus.org/Home">Groovy script</a> and execute it on the server. Useful for trouble-shooting and diagnostics. Use the ‘println’ command to see the output (if you use <tt>System.out</tt>, it will go to the server’s stdout, which is harder to see.) Example:	Entrez ici un <a href="http://groovy.codehaus.org/Home">script Groovy</a> quelconque pour l''''exécuter sur le serveur.<br>Utile pour la résolution de problèmes et le diagnostique.<br>Utilisez la commande ''''println'''' pour voir la sortie (si vous utilisez <tt>System.out</tt>, cela ira vers la sortie standard du serveur, ce qui est plus complexe à voir.) <br>Par exemple :
(old value)

CURRENT

Result
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Result	Résultat

CURRENT

Run
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Run	Exécuter

CURRENT

Script Console
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Script Console	Console de script

core/src/main/resources/lib/hudson/test-result_fr.properties

Files

test-result.jelly

test-result_fr.properties

CURRENT

1failure
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
1 failure {0}	1 échec {0}

CURRENT

multifailures
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
{0} failures {1}	{0} échecs {1}

CURRENT

no failures
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
no failures	aucun échec

CURRENT

no tests
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
no tests	pas de test

core/src/main/resources/lib/hudson/thirdPartyLicenses_fr.properties

Files

thirdPartyLicenses.jelly

thirdPartyLicenses_fr.properties

MISSING

Maven ID
04.02.2013 00:16:09, no SCM information
Maven ID

CURRENT

License
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
License	Licence

CURRENT

Name
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Name	Nom

core/src/main/resources/lib/layout/breadcrumbBar_fr.properties

Files

breadcrumbBar.jelly

breadcrumbBar_fr.properties

CURRENT

DISABLE AUTO REFRESH
29.04.2013 12:15:15, no SCM information	30.05.2013 20:09:20, no SCM information
DISABLE AUTO REFRESH	ANNULER LE RAFRAÎCHISSEMENT AUTOMATIQUE

CURRENT

ENABLE AUTO REFRESH
29.04.2013 12:15:15, no SCM information	30.05.2013 20:09:20, no SCM information
ENABLE AUTO REFRESH	ACTIVER LE RAFRAÎCHISSEMENT AUTOMATIQUE

core/src/main/resources/lib/layout/layout_fr.properties

Files

layout.jelly

layout_fr.properties

OUTDATED

Page generated
29.08.2013 16:34:29, no SCM information	30.05.2013 20:09:20, no SCM information
Page generated	Page générée le
(old value)

OUTDATED

search
29.08.2013 16:34:29, no SCM information	30.05.2013 20:09:20, no SCM information
search	rechercher
(old value)

CURRENT

logout
04.02.2013 00:16:09, no SCM information	30.05.2013 20:09:20, no SCM information
log out	Se déconnecter

CURRENT

searchBox.url
04.02.2013 00:16:09, no SCM information	30.05.2013 20:09:20, no SCM information
http://wiki.jenkins-ci.org/display/JENKINS/Search+Box	http://wiki.jenkins-ci.org/display/JENKINS/Search+Box

core/src/main/resources/lib/layout/main-panel_fr.properties

Files

main-panel.jelly

main-panel_fr.properties

CURRENT

Jenkins is going to shut down
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Jenkins is going to shut down	Jenkins va s''éteindre

core/src/main/resources/lib/layout/progressiveRendering_fr.properties

Files

progressiveRendering.jelly

progressiveRendering_fr.properties

CURRENT

progressMessage
04.02.2013 00:16:09, no SCM information	30.05.2013 20:09:20, no SCM information
Computation in progress.	Calcul en cours.

core/src/main/resources/lib/layout/task_fr.properties

Files

task.jelly

task_fr.properties

OUTDATED

Done.
14.06.2013 07:43:03, no SCM information	30.05.2013 20:09:20, no SCM information
Done.	Fait.
(old value)

core/src/main/resources/lib/test/bar_fr.properties

Files

bar.jelly

bar_fr.properties

CURRENT

No tests
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
No tests	Pas de test

CURRENT

failures
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
failures	{0} échecs

CURRENT

skipped
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
skipped	Non passés

CURRENT

tests
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
tests	{0} tests

maven-plugin/src/main/resources/hudson/maven/MavenBuild/actions_fr.properties

Files

actions.jelly

actions_fr.properties

OUTDATED

Executed Mojos
28.06.2013 06:41:00, no SCM information	04.02.2013 00:16:09, no SCM information
Executed Mojos	Mojos exécutés
(old value)

maven-plugin/src/main/resources/hudson/maven/MavenBuild/executedMojos_fr.properties

Files

executedMojos.jelly

executedMojos_fr.properties

OUTDATED

Build in progress.
28.06.2013 06:41:00, no SCM information	30.05.2013 20:09:20, no SCM information
Build in progress.	Build en cours
(old value)

OUTDATED

Duration
28.06.2013 06:41:00, no SCM information	30.05.2013 20:09:20, no SCM information
Duration	Durée
(old value)

OUTDATED

Executed Mojos
28.06.2013 06:41:00, no SCM information	30.05.2013 20:09:20, no SCM information
Executed Mojos	Mojos exécutés
(old value)

OUTDATED

Execution
28.06.2013 06:41:00, no SCM information	30.05.2013 20:09:20, no SCM information
Execution	Exécution
(old value)

OUTDATED

Fingerprint
28.06.2013 06:41:00, no SCM information	30.05.2013 20:09:20, no SCM information
Fingerprint	Empreinte numérique
(old value)

OUTDATED

Goal
28.06.2013 06:41:00, no SCM information	30.05.2013 20:09:20, no SCM information
Goal	Goal
(old value)

OUTDATED

No mojos executed.
28.06.2013 06:41:00, no SCM information	30.05.2013 20:09:20, no SCM information
No mojos executed.	Aucun mojo n''a été exécuté
(old value)

OUTDATED

Plugin
28.06.2013 06:41:00, no SCM information	30.05.2013 20:09:20, no SCM information
Plugin	Plugin
(old value)

OUTDATED

Version
28.06.2013 06:41:00, no SCM information	30.05.2013 20:09:20, no SCM information
Version	Version
(old value)

OUTDATED

fingerprint
28.06.2013 06:41:00, no SCM information	30.05.2013 20:09:20, no SCM information
fingerprint	empreinte numérique
(old value)

maven-plugin/src/main/resources/hudson/maven/MavenModule/configure-entries_fr.properties

Files

EMPTY

Build
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Build	—

EMPTY

Goals
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Goals	—

CURRENT

Build Settings
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Build Settings	Configuration du Build

maven-plugin/src/main/resources/hudson/maven/MavenModuleSet/actions_fr.properties

Files

actions.jelly

actions_fr.properties

OUTDATED

Delete All Disabled Modules
28.06.2013 06:41:00, no SCM information	04.02.2013 00:16:09, no SCM information
Delete All Disabled Modules	Supprimer tous les modules désactivés
(old value)

OUTDATED

Modules
28.06.2013 06:41:00, no SCM information	04.02.2013 00:16:09, no SCM information
Modules	Modules
(old value)

maven-plugin/src/main/resources/hudson/maven/MavenModuleSet/configure-entries_fr.properties

Files

deleteAllDisabledModules.jelly

MISSING

Global Settings file
04.02.2013 00:16:09, no SCM information
Global Settings file

MISSING

Post Steps
04.02.2013 00:16:09, no SCM information
Post Steps

MISSING

Pre Steps
04.02.2013 00:16:09, no SCM information
Pre Steps

MISSING

Send e-mail for each failed module
04.02.2013 00:16:09, no SCM information
Send e-mail for each failed module

MISSING

Settings file
04.02.2013 00:16:09, no SCM information
Settings file

MISSING

Strategy
04.02.2013 00:16:09, no SCM information
Strategy

MISSING

criteriaDescription
28.02.2013 15:26:35, no SCM information
Should the post-build steps run only for successful builds, etc.

MISSING

runAlways
28.02.2013 15:26:35, no SCM information
Run regardless of build result

MISSING

runIfStable
28.02.2013 15:26:35, no SCM information
Run only if build succeeds

MISSING

runIfSuccessful
28.02.2013 15:26:35, no SCM information
Run only if build succeeds or is unstable

OUTDATED

Maven Version.error.1
28.02.2013 15:26:35, no SCM information	04.02.2013 00:16:09, no SCM information
Jenkins needs to know where your Maven 2/3 is installed.	Jenkins a besoin de savoir où Maven2/3 est installÈ.
(old value)

OUTDATED

Maven Version.error.2
28.02.2013 15:26:35, no SCM information	04.02.2013 00:16:09, no SCM information
Please do so from <a href="{0}/configure" target="_new">the system configuration</a>.	Veuillez le faire dans <a href="{0}/configure" target="_new">la configuration systËme</a>.
(old value)

ORPHANED

Alternate settings file
	04.02.2013 00:16:09, no SCM information
	Fichier settings alternatif

ORPHANED

Block build when dependency building
	04.02.2013 00:16:09, no SCM information
	Bloquer le build pendant la construction des dépendances

ORPHANED

Goals
	04.02.2013 00:16:09, no SCM information
	Goals

ORPHANED

Post-Build Run Criteria
	04.02.2013 00:16:09, no SCM information
	Critère pour exécuter le post-build

ORPHANED

Steps to run after mvn build
	04.02.2013 00:16:09, no SCM information
	Étapes à lancer après le build maven

ORPHANED

Steps to run before mvn build
	04.02.2013 00:16:09, no SCM information
	Étapes à lancer avant le build maven

ORPHANED

Use private maven repository
	04.02.2013 00:16:09, no SCM information
	Utiliser un repository Maven privé

CURRENT

Add post-build step
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Add post-build step	Ajouter une étape post-build

CURRENT

Add pre-build step
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Add pre-build step	Ajouter une étape pré-build

CURRENT

Build
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Build	Build

CURRENT

Build Settings
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Build Settings	Configuration du build

CURRENT

Build modules in parallel
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Build modules in parallel	Construire les modules en parallêle

CURRENT

Build whenever a SNAPSHOT dependency is built
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Build whenever a SNAPSHOT dependency is built	Lance un build à chaque fois qu''une dépendance SNAPSHOT est construite

CURRENT

Disable automatic artifact archiving
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Disable automatic artifact archiving	Désactive l'achivage automatique des artefacts

CURRENT

Disable triggering of downstream projects
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Disable triggering of downstream projects	Désactive le lancement des projets en aval

CURRENT

Goals and options
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Goals and options	Goals et options

CURRENT

Incremental build - only build changed modules
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Incremental build - only build changed modules	Construction incrémentale - ne faire la construction (build) que pour les modules changés

CURRENT

Maven Validation Level
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Maven Validation Level	Niveau de validation du POM Maven

CURRENT

Maven Version
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Maven Version	Version de Maven

CURRENT

Process Plugins during Pom parsing
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Process Plugins during Pom parsing	Analyse les plugins pendant la lecture du POM

CURRENT

Resolve Dependencies during Pom parsing
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Resolve Dependencies during Pom parsing	Effectue la résolution de dépendances pendant la lecture du POM

CURRENT

Root POM
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Root POM	POM Racine

CURRENT

Run Headless
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Run Headless	Exécuter sans environnement graphique

CURRENT

Use private Maven repository
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Use private Maven repository	Utilise un repository Maven privé

maven-plugin/src/main/resources/hudson/maven/MavenModuleSet/deleteAllDisabledModules_fr.properties

Files

deleteAllDisabledModules_fr.properties

CURRENT

Are you sure about deleting all the disabled modules?
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Are you sure about deleting all the disabled modules?	Êtes-vous sûr(e) de vouloir supprimer tous les modules désactivés ?

CURRENT

Yes
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Yes	Oui

maven-plugin/src/main/resources/hudson/maven/MavenModuleSet/disabled_fr.properties

Files

disabled.jelly

disabled_fr.properties

OUTDATED

description
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:09, no SCM information
These modules are no longer a part of the project, but left for archival purpose.If you’d like to delete them permanently, choose "delete all disabled modules" from left.	Ces modules ne font plus partie du projet; ils sont conservés pour archivage.Si vous souhaitez les supprimer de façon permanente, sélectionnez "supprimer tous les modules désactivés" sur la gauche.
(old value)

OUTDATED

title
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:09, no SCM information
Project {0}	Projet {0}
(old value)

CURRENT

Disabled
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Disabled	Désactivé

CURRENT

Modules
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Modules	Modules

maven-plugin/src/main/resources/hudson/maven/MavenModuleSet/global_fr.properties

Files

global.jelly

help-localRepository.html

MISSING

Local Maven Repository
04.02.2013 00:16:09, no SCM information
Local Maven Repository

CURRENT

Global MAVEN_OPTS
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Global MAVEN_OPTS	MAVEN_OPTS global

CURRENT

Maven Project Configuration
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Maven Project Configuration	Configuration des projets Maven

maven-plugin/src/main/resources/hudson/maven/MavenModuleSet/help-localRepository.html (Master)

Files

MISSING

04.02.2013 00:16:09, no SCM information
<div> Specifies the default setting of the local repository location when jobs do not specify one. See the per-job configuration of this (under the "Advanced" button) for more discussion of what this option means. </div>

maven-plugin/src/main/resources/hudson/maven/MavenModuleSet/index_fr.properties

Files

newJobDetail_fr.properties

OUTDATED

Last Successful Artifacts
28.06.2013 06:41:00, no SCM information	04.02.2013 00:16:09, no SCM information
Last Successful Artifacts	Derniers artefacts construits avec succès
(old value)

OUTDATED

Latest Test Result
28.06.2013 06:41:00, no SCM information	04.02.2013 00:16:09, no SCM information
Latest Test Result	Derniers résultats des tests
(old value)

OUTDATED

Recent Changes
28.06.2013 06:41:00, no SCM information	04.02.2013 00:16:09, no SCM information
Recent Changes	Changements récents
(old value)

OUTDATED

Workspace
28.06.2013 06:41:00, no SCM information	04.02.2013 00:16:09, no SCM information
Workspace	Espace de travail
(old value)

ORPHANED

This project is currently disabled
	04.02.2013 00:16:09, no SCM information
	Ce projet est actuellement désactivé

maven-plugin/src/main/resources/hudson/maven/MavenModuleSet/modules_fr.properties

Files

modules.jelly

modules_fr.properties

OUTDATED

A build is in progress to parse the list of modules from POM.
21.06.2013 06:36:29, no SCM information	04.02.2013 00:16:09, no SCM information
A build is in progress to parse the list of modules from POM.	Un build est en cours de parcours de la liste des modules fournis par le POM.
(old value)

OUTDATED

Disabled
21.06.2013 06:36:29, no SCM information	04.02.2013 00:16:09, no SCM information
Disabled	Désactivés
(old value)

OUTDATED

Modules
21.06.2013 06:36:29, no SCM information	04.02.2013 00:16:09, no SCM information
Modules	Modules
(old value)

CURRENT

text
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Please <a href="build?delay=0sec">perform a build</a> so that Jenkins can parse the list of modules from POM.	Merci de <a href="build?delay=0sec">lancer un build</a> afin que Jenkins puisse parcourir la liste des modules à partir du POM.

maven-plugin/src/main/resources/hudson/maven/MavenModuleSet/newJobDetail_fr.properties

Files

newJobDetail.jelly

OUTDATED

body
28.02.2013 15:26:35, no SCM information	04.02.2013 00:16:09, no SCM information
Build a maven 2/3 project. Jenkins takes advantage of your POM files and drastically reduces the configuration.	Construit un projet avec maven2/3. Jenkins utilise directement vos fichiers POM et diminue radicalement l''effort de configuration. Cette fonctionnalité est encore en bêta mais elle est disponible afin d''obtenir vos retours.
(old value)

maven-plugin/src/main/resources/hudson/maven/MavenModuleSetBuild/main_fr.properties

Files

MISSING

noRun
01.08.2013 07:43:47, no SCM information
didn’t run

OUTDATED

Module Builds
28.06.2013 06:41:00, no SCM information	04.02.2013 00:16:09, no SCM information
Module Builds	Construction du module
(old value)

maven-plugin/src/main/resources/hudson/maven/MavenProbeAction/envVars_fr.properties

Files

envVars.jelly

envVars_fr.properties

CURRENT

Environment Variables
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Environment Variables	Variables d''Environnement

maven-plugin/src/main/resources/hudson/maven/MavenProbeAction/index_fr.properties

Files

CURRENT

description
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Obtain information about the running Maven process by clicking links from the left. Often useful for trouble-shooting problems.	Obtenez des informations sur le process Maven en cours en cliquant les liens sur la gauche. Utile pour corriger des problèmes.

maven-plugin/src/main/resources/hudson/maven/MavenProbeAction/sidepanel_fr.properties

Files

systemProperties_fr.properties

OUTDATED

Environment Variables
28.06.2013 06:41:00, no SCM information	04.02.2013 00:16:09, no SCM information
Environment Variables	Variables d''environnement
(old value)

OUTDATED

Script Console
28.06.2013 06:41:00, no SCM information	04.02.2013 00:16:09, no SCM information
Script Console	Console de script
(old value)

OUTDATED

System Properties
28.06.2013 06:41:00, no SCM information	04.02.2013 00:16:09, no SCM information
System Properties	Propriétés système
(old value)

OUTDATED

Thread Dump
28.06.2013 06:41:00, no SCM information	04.02.2013 00:16:09, no SCM information
Thread Dump	Dump du thread
(old value)

maven-plugin/src/main/resources/hudson/maven/MavenProbeAction/systemProperties_fr.properties

Files

systemProperties.jelly

CURRENT

System Properties
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
System Properties	Propriétés système

maven-plugin/src/main/resources/hudson/maven/MavenProbeAction/threads_fr.properties

Files

threads.jelly

threads_fr.properties

CURRENT

Thread Dump
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Thread Dump	Dump du Thread

maven-plugin/src/main/resources/hudson/maven/Messages_fr.properties

Files

MISSING

MavenBuild.KeptBecauseOfParent
01.08.2013 07:43:47, no SCM information
Kept because {0} is kept

MISSING

MavenModuleSet.AlternateSettingsRelativePath
01.08.2013 07:43:47, no SCM information
Alternate settings file must be a relative path.

MISSING

MavenModuleSet.Pronoun
01.08.2013 07:43:47, no SCM information
Maven project

MISSING

MavenModuleSet.readResolve_missingConfigProvider
01.08.2013 07:43:47, no SCM information
ERROR: 'config-file-provider' is not installed or disabled, therefore the config can't be fully loaded!!

MISSING

MavenModuleSet.readResolve_updateConfigProvider
01.08.2013 07:43:47, no SCM information
ERROR: Please update the 'config-file-provider' plugin, the current version is not supported anymore! (id={0})

MISSING

MavenModuleSetBuild.DownloadedArtifact
01.08.2013 07:43:47, no SCM information
Downloaded artifact {0}{1}

MISSING

MavenModuleSetBuild.FailedToTransfer
01.08.2013 07:43:47, no SCM information
Failed to transfer {0}

MISSING

MavenModuleSetBuild.FoundModuleWithoutProject
01.08.2013 07:43:47, no SCM information
Found a module with path {0} but no associated project

MISSING

MavenModuleSetBuild.NoMavenConfigured
01.08.2013 07:43:47, no SCM information
A Maven installation needs to be available for this project to be built.Either your server has no Maven installations defined, or the requested Maven version does not exist.

MISSING

MavenModuleSetBuild.NoMavenInstall
01.08.2013 07:43:47, no SCM information
A Maven installation needs to be available for this project to be built. Either your server has no Maven installations defined, or the requested Maven version does not exist.

MISSING

MavenModuleSetBuild.NoSuchAlternateSettings
01.08.2013 07:43:47, no SCM information
No such settings file {0} exists Please verify that your alternate settings file is specified properly and exists in the workspace.

MISSING

MavenModuleSetBuild.NoSuchPOMFile
01.08.2013 07:43:47, no SCM information
No such file {0} Perhaps you need to specify the correct POM file path in the project configuration?

MISSING

MavenModuleSetBuild.SettinsgXmlAndPrivateRepository
01.08.2013 07:43:47, no SCM information
Using settings.xml at {0} and private repository at {1}

MISSING

MavenVersionCallable.MavenHomeDoesntExist
01.08.2013 07:43:47, no SCM information
Maven Home {0} doesn’t exist

MISSING

MavenVersionCallable.MavenHomeIsNotDirectory
01.08.2013 07:43:47, no SCM information
Maven Home {0} is not a directory

MISSING

PluginImpl.updateConfiProvider
01.08.2013 07:43:47, no SCM information
The current installed version of 'config-file-provider' is not compatible with this core anymore (requires >= 2.3)

MISSING

RedeployPublisher.RepositoryURL.Mandatory
01.08.2013 07:43:47, no SCM information
Repository URL is mandatory

OUTDATED

MavenBuild.FailedEarlier
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:09, no SCM information
Build failed before it gets to this module	Le build a échoué avant d''atteindre ce module
(old value)

OUTDATED

MavenBuild.Triggering
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:09, no SCM information
Triggering a new build of {0}	Lancement d''un nouveau build de {0}
(old value)

OUTDATED

MavenBuilder.Aborted
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:09, no SCM information
Aborted	Annulé
(old value)

OUTDATED

MavenBuilder.AsyncFailed
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:09, no SCM information
Asynchronous execution failure	Erreur d''exécution asynchrone
(old value)

OUTDATED

MavenBuilder.Failed
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:09, no SCM information
Maven failed with error.	Maven a échoué avec une erreur.
(old value)

OUTDATED

MavenBuilder.Waiting
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:09, no SCM information
Waiting for Jenkins to finish collecting data	En attente que Jenkins finisse de récupérer les données
(old value)

OUTDATED

MavenModule.Pronoun
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:09, no SCM information
Module	Module
(old value)

OUTDATED

MavenModuleSet.DiplayName
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:09, no SCM information
Build a maven2/3 project	Construire un projet maven2/3
(old value)

OUTDATED

MavenModuleSetBuild.DiscoveredModule
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:09, no SCM information
Discovered a new module {0} {1}	Un nouveau module {0} {1} a été trouvé
(old value)

OUTDATED

MavenModuleSetBuild.FailedToParsePom
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:09, no SCM information
Failed to parse POMs	Echec à la lecture des POMs
(old value)

OUTDATED

MavenProbeAction.DisplayName
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:09, no SCM information
Monitor Maven Process	Surveiller un process Maven
(old value)

OUTDATED

MavenProcessFactory.ClassWorldsNotFound
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:09, no SCM information
No classworlds*.jar found in {0} -- Is this a valid maven2/3 directory?	Pas de fichier classworlds*.jar trouvé dans {0} -- Est-ce un répertoire maven2/3 valide?
(old value)

OUTDATED

MavenRedeployer.DisplayName
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:09, no SCM information
Deploy to Maven repository	Déployer vers un repository Maven
(old value)

OUTDATED

ProcessCache.Reusing
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:09, no SCM information
Reusing existing maven process	Réutilisation du process Maven existant
(old value)

OUTDATED

RedeployPublisher.getDisplayName
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:09, no SCM information
Deploy artifacts to Maven repository	Déployer les artefacts dans le repository Maven
(old value)

OUTDATED

ReleaseAction.DisplayName
01.08.2013 07:43:47, no SCM information	04.02.2013 00:16:09, no SCM information
Release New Version	Livrer une nouvelle version
(old value)

ORPHANED

MavenModuleSetBuild.NoSuchFile
	04.02.2013 00:16:09, no SCM information
	Pas de fichier {0} Avez-vous spécifié le bon chemin vers le fichier POM dans la configuration du projet?

maven-plugin/src/main/resources/hudson/maven/RedeployPublisher/config_fr.properties

Files

MISSING

Release environment variable
04.02.2013 00:16:09, no SCM information
Release environment variable

CURRENT

Assign unique versions to snapshots
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Assign unique versions to snapshots	Affecter des numéros de version uniques aux snapshots

CURRENT

Deploy even if the build is unstable
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Deploy even if the build is unstable	Déploiment même si le build est instable.

CURRENT

Repository ID
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Repository ID	Identifiant du repository

CURRENT

Repository URL
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Repository URL	URL du repository

maven-plugin/src/main/resources/hudson/maven/RedeployPublisher/help-evenIfUnstable.html (Master)

Files

help-evenIfUnstable.html

MISSING

04.02.2013 00:16:09, no SCM information
<div> If checked, the deployment will be performed even if the build is unstable. <p> This can be useful if the same build definition is being used for continuous integration and to deploy nightly snapshots. </p> </div>

maven-plugin/src/main/resources/hudson/maven/RedeployPublisher/help-id_fr.html

Files

help-id.html

help-id_fr.html

CURRENT

04.02.2013 00:16:09, no SCM information

<div>
For some repository URL (such as <tt>scpexe</tt>), Maven may require
additional configuration (such as user name, executable path, etc.)

Maven wants you to specify this in <tt>~/.m2/settings.xml</tt> of
the user that runs Jenkins, and this ID value is used to retrieve
the setting information from this file (that is, the <server>
element with this ID value will be consulted for various
protocol-specific configuration values.)

<p>
See
<a href="http://maven.apache.org/plugins/maven-deploy-plugin/usage.html">the maven-deploy-plugin usage
page</a> for more details.
</div>

maven-plugin/src/main/resources/hudson/maven/RedeployPublisher/help-releaseEnvVar.html (Master)

Files

help-releaseEnvVar.html

help-uniqueVersion_fr.html

MISSING

04.02.2013 00:16:09, no SCM information
<div> If the given variable name is set to "true" the deploy steps is skipped. Useful when using m2 release plugin. </div>

maven-plugin/src/main/resources/hudson/maven/RedeployPublisher/help-uniqueVersion_fr.html

Files

help-uniqueVersion.html

CURRENT

04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
<div> If checked, the deployment will assign timestamp-based unique version number to the deployed artifacts, when their versions end with <tt>-SNAPSHOT</tt>. <p> To the best of my knowledge, this is almost never a useful option especially for CI servers like Jenkins. </div>	<div> If checked, the deployment will assign timestamp-based unique version number to the deployed artifacts, when their versions end with <tt>-SNAPSHOT</tt>. <p> To the best of my knowledge, this is almost never a useful option especially for CI servers like Jenkins. </div>

maven-plugin/src/main/resources/hudson/maven/RedeployPublisher/help-url_fr.html

Files

help-url.html

help-url_fr.html

CURRENT

04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
<div> Specify the URL of the Maven repository to deploy artifacts to, such as <tt>scp://server.acme.org/export/home/maven/repository/</tt> </div>	<div> Specify the URL of the Maven repository to deploy artifacts to, such as <tt>scp://server.acme.org/export/home/maven/repository/</tt> </div>

maven-plugin/src/main/resources/hudson/maven/RedeployPublisher/help_fr.html

Files

OUTDATED

28.02.2013 15:26:35, no SCM information	04.02.2013 00:16:09, no SCM information
<div> Deploy artifacts to a Maven repository. In comparison with the standard <tt>mvn deploy</tt>, this feature allows you to deploy artifacts after the entire build is confirmed to be successful. <p> This prevents a typical problem in Maven, where some modules are deployed before a critical failure is discovered later down the road, rendering the repository state inconsistent. <p> Note that regardless of this configuration, you can always manually come back to Jenkins and deploy any of the past artifacts to any repository of your choice, after the fact. <p> <b>To use this feature you shouldn't deactivate the automatic artifact archiving.</b> </p> </div>	<div> <!-- please do not translate this file until this feature stabilizes a bit more (March 9th, 2008) --> Deploy artifacts to a Maven repository. In comparison with the standard <tt>mvn deploy</tt>, this feature allows you to deploy artifacts after the entire build is confirmed to be successful. <p> This prevents a typical problem in Maven, where some modules are deployed before a critical failure is discovered later down the road, rendering the repository state inconsistent. <p> Note that regardless of this configuration, you can always manually come back to Jenkins and deploy any of the past artifacts to any repository of your choice, after the fact. <p> <b>To use this feature you shouldn't deactivate the automatic artifact archiving.</b> </p> </div>
(old value)

maven-plugin/src/main/resources/hudson/maven/reporters/MavenAbstractArtifactRecord/badge_fr.properties

Files

badge.jelly

badge_fr.properties

OUTDATED

Deployed to repository
28.06.2013 06:41:00, no SCM information	04.02.2013 00:16:09, no SCM information
Deployed to repository	Déployé sur le repository
(old value)

maven-plugin/src/main/resources/hudson/maven/reporters/MavenAbstractArtifactRecord/index_fr.properties

Files

OUTDATED

OK
28.06.2013 06:41:00, no SCM information	30.05.2013 20:09:20, no SCM information
OK	OK
(old value)

OUTDATED

Redeploy Artifacts
28.06.2013 06:41:00, no SCM information	30.05.2013 20:09:20, no SCM information
Redeploy Artifacts	Redéployer les artefacts
(old value)

OUTDATED

This page allows you to redeploy the build artifacts to a repository after the fact.
28.06.2013 06:41:00, no SCM information	30.05.2013 20:09:20, no SCM information
This page allows you to redeploy the build artifacts to a repository after the fact.	Cette page vous permet de redéployer les artefacts vers un repository après coup.
(old value)

maven-plugin/src/main/resources/hudson/maven/reporters/Messages_fr.properties

Files

MISSING

MavenTestJavadocArchiver.DisplayName
04.02.2013 00:16:09, no SCM information
Publish Test javadoc

CURRENT

BuildInfoRecorder.DisplayName
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Record build information	Enregistrer les informations du build

CURRENT

HistoryWidgetImpl.Displayname
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Deployment History	Historique des déploiements

CURRENT

MavenAbstractArtifactRecord.Displayname
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Redeploy Artifacts	Redéployer les artefacts

CURRENT

MavenArtifact.DeployingAttachedArtifact
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Deploying the attached artifact {0}	Déploiement de l''artefact attaché {0}

CURRENT

MavenArtifact.DeployingMainArtifact
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Deploying the main artifact {0}	Déploiement de l''artefact principal {0}

CURRENT

MavenArtifactArchiver.DisplayName
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Archive the artifacts	Archiver les artefacts

CURRENT

MavenArtifactArchiver.FailedToInstallToMaster
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Failed to install artifact to the master	Echec à l''installation de l''artefact sur le maître

CURRENT

MavenFingerprinter.DisplayName
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Record fingerprints	Enregistrer les empreintes numériques

CURRENT

MavenJavadocArchiver.DisplayName
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Publish javadoc	Publier les javadocs

CURRENT

MavenJavadocArchiver.FailedToCopy
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Unable to copy Javadoc from {0} to {1}	Impossible de copier les javadocs de {0} vers {1}

CURRENT

MavenJavadocArchiver.NoDestDir
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Unable to obtain the destDir from javadoc mojo	Impossible d''obtenir le répertoire de destination à partir du plugin javadoc

CURRENT

MavenMailer.DisplayName
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
E-mail Notification	Notification par email

CURRENT

MavenSiteArchiver.DisplayName
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Maven-generated site	Site généré par Maven

CURRENT

ReportAction.DisplayName
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Maven reports	Rapports Maven

CURRENT

ReportCollector.DisplayName
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Record Maven reports	Enregister les rapports Maven

CURRENT

ReportCollector.OutsideSite
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Maven report output goes to {0}, which is outside project reporting path{1}	La sortie des rapports Maven se fait vers {0}, soit hors du chemin de rapport projet {1}

CURRENT

SurefireArchiver.DisplayName
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Publish surefire reports	Publier les rapports Surefire

CURRENT

SurefireArchiver.NoReportsDir
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Unable to obtain the reportsDirectory from surefire:test mojo	Impossible d''obtenir le chemin vers les rapports à partir du plugin surefire:test

CURRENT

SurefireArchiver.Recording
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
[JENKINS] Recording test results	[JENKINS] Enregistrement des résultats des tests

maven-plugin/src/main/resources/hudson/maven/reporters/SurefireAggregatedReport/index_fr.properties

Files

CURRENT

Fail
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Fail	Echec

CURRENT

Module
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Module	Module

CURRENT

Test Result
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Test Result	Résultat des tests

CURRENT

Total
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
Total	Total

CURRENT

diff
04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
diff	Différence

maven-plugin/src/main/webapp/aggregator_fr.html

Files

aggregator.html

aggregator_fr.html

CURRENT

04.02.2013 00:16:09, no SCM information

<div>
<p>
If checked, Jenkins will run individual module builds as separate builds. On a project
with a large number of modules, or on a project where modules take a long time to build,
setting this option to true may speed up the whole build, as different modules can be built
in parallel.

<p>
Otherwise, leave it unchecked and Jenkins will build this maven project like you'd normally
do from command line.

<p>
When your build uses "aggregator-style" multi-module aware mojos, you'd have to leave this
option unchecked so that the mojo will have access to all of your modules.

<p>
Historically, this has been the default mode of the native maven project up until Jenkins 1.133.
So if your project was created before that, you might want to uncheck this.

</div>

<div>
<p>
Si cette option est sélectionnée, Jenkins lancera les builds de chaque
module comme des builds séparés.
Sur un projet avec un grand nombre de modules ou sur un projet où les
modules prennent du temps pour se construire, cette option permet
d'accélérer le build dans sa globalité, puisque les sous-modules peuvent
être construits en parallèle.

<p>
Si cette option n'est *pas* cochée, Jenkins construira le projet comme
lors d'un lancement classique en ligne de commande.

<p>
Si votre build utilise des mojos "aggregator" qui tirent parti des
multi-modules, laissez cette option déchochée, afin que les mojos
aient accès à tous vos modules.

<p>
Historiquement, c'était l'option par défaut pour les projets 'natifs' maven
jusqu'à Jenkins 1.333. Si votre projet a été créé avant cette version,
laissez plutôt cette option décochée.
</div>

maven-plugin/src/main/webapp/archivingDisabled.html (Master)

Files

archivingDisabled.html

MISSING

28.02.2013 15:26:35, no SCM information
<div> If checked, Jenkins will not automatically archive all artifacts generated by this project. If you wish to archive the results of this build within Jenkins, you will need to use the "Archive the Artifacts" post-build action below. </div>

maven-plugin/src/main/webapp/downstreamDisabled.html (Master)

Files

downstreamDisabled.html

ignore-upstrem-changes.html

MISSING

04.02.2013 00:16:09, no SCM information
<div> <p> If checked, Jenkins will not schedule build of downstream Jobs. </div>

maven-plugin/src/main/webapp/goals_fr.html

Files

goals.html

goals_fr.html

CURRENT

04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
<div> Specifies the goals to execute, such as "clean install" or "deploy". This field can also accept any other command line options to Maven, such as "-e" or "-Dmaven.test.skip=true". </div>	<div> Spécifie les goals (cibles Maven) à exécuter, comme "clean install" ou "deploy". Ce champ peut accepter toutes les options en ligne de commande Maven, comme "-e" ou "-Dmaven.test.skip=true". </div>

maven-plugin/src/main/webapp/ignore-upstrem-changes_fr.html

Files

ignore-upstrem-changes_fr.html

CURRENT

04.02.2013 00:16:09, no SCM information

<div>
If checked, Jenkins will parse the POMs of this project, and see if any of its snapshot dependencies
are built on this Jenkins as well. If so, Jenkins will set up build dependency relationship so that
whenever the dependency job is built and a new SNAPSHOT jar is created, Jenkins will schedule a build
of this project.

<p>
This is convenient for automatically performing continuous integration. Jenkins will check the snapshot
dependencies from the <dependency> element in the POM, as well as <plugin>s and
<extension>s used in POMs.

<p>
If this behavior is problematic, uncheck this option.
</div>

<div>
Si cette case est cochée, Jenkins parcourera les fichiers POM de ce
projet et verra si une des dépendances SNAPSHOT sont construites
également sur ce serveur Jenkins. Dans ce cas, Jenkins positionnera une
relation dépendance de build, de façon à ce que, à chaque fois que le job
dont il dépend est construit et qu'un nouveau jar SNAPSHOT est créé,
Jenkins programme un nouveau build pour ce projet.

<p>
Cela est pratique pour obtenir une intégration continue automatique.
Jenkins vérifiera que les dépendances SNAPSHOT de l'élément
<dependency> dans le POM, ainsi que les <plugin>s et les
<extension>s utilisés dans les POMs.

<p>
Si ce comportement est problématique, décochez cette option.
</div>

maven-plugin/src/main/webapp/incremental.html (Master)

Files

incremental.html

MISSING

04.02.2013 00:16:09, no SCM information

<div>
<p>
If checked, Jenkins will only build any modules with changes from SCM
and any modules which depend on those changed modules, using Maven's
"-amd -pl group1:artifact1,group1:artifact2" command-line
options. If the SCM reports no changes to any modules, however, all
modules will be
built. See <a href="http://docs.codehaus.org/display/MAVEN/Make+Like+Reactor+Mode">http://docs.codehaus.org/display/MAVEN/Make+Like+Reactor+Mode</a>
for more information on the Maven behavior this utilizes.

<p>
This functionality requires Maven 2.1 or later, and will not have
any impact if "Build modules in parallel" is selected.

</div>

maven-plugin/src/main/webapp/maven-opts_fr.html

Files

maven-opts.html

maven-opts_fr.html

CURRENT

04.02.2013 00:16:09, no SCM information

<div>
Specify JVM options needed when launching Maven as an external process.
Also see <a href="http://maven.apache.org/maven-1.x/reference/command-line.html">MAVEN_OPTS documentation</a>
(even though this is for Maven 1.x it still applies to Maven 2.x)

<p>
Shell-like environment variable expansions work in this field, by using the <tt>${VARIABLE}</tt> syntax.
</div>

<div>
Indique quelles options passer à la JVM quand Maven se lance dans un
process externe. Voir aussi la
<a href="http://maven.apache.org/maven-1.x/reference/command-line.html">documentation MAVEN_OPTS</a>
(bien qu'elle soit écrite pour Maven 1.x, elle reste valable pour Maven
2.x).

<p>
Les expansions de variables à la Shell sont valables dans ce champ,
avec une syntaxe du type <tt>${VARIABLE}</tt>.
</div>

maven-plugin/src/main/webapp/module-goals_fr.html

Files

module-goals.html

module-goals_fr.html

CURRENT

04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
<div> Specifies the goals for this module, <em>if it's build alone</em>. Defaults to the goals of <a href="../configure">the parent's configuration</a>. Note: when building the whole job, the goals of the parent are taken in any case! </div>	<div> Par défaut (si ce champ est laissé tel quel ou vide), tous les modules se construisent avec les mêmes goals ou phases, tels que spécifiés dans la <a href="../configure">configuration du parent</a>. Vous pouvez les remplacer au cas par cas en spécifiant une autre valeur ici. </div>

maven-plugin/src/main/webapp/per-module-email.html (Master)

Files

per-module-email.html

private-repository_fr.html

MISSING

04.02.2013 00:16:09, no SCM information
<div> If checked, Jenkins will send an e-mail notifications for each module (e.g. failed, unstable). </div>

maven-plugin/src/main/webapp/private-repository_fr.html

Files

private-repository.html

CURRENT

04.02.2013 00:16:09, no SCM information

<div>
Normally, Jenkins uses the local Maven repository as determined by Maven — the exact process
seems to be undocumented, but it's <tt>~/.m2/repository</tt> and can be overridden by
<localRepository> in <tt>~/.m2/settings.xml</tt> (see <a href="http://maven.apache.org/settings.html">the reference</a> for more details.)

<p>
This normally means that all the jobs that are executed on the same node shares a single Maven repository.
The upside of this is that you can save the disk space, but the downside of this is that sometimes those
builds could interfere with each other. For example, you might end up having builds incorrectly succeed,
just because your have all the dependencies in your local repository, despite that fact that none of the
repositories in POM might have them.

<p>
There are also some reported problems regarding having concurrent Maven processes trying to use the same local
repository.

<p>
When this option is checked, Jenkins will tell Maven to use <tt>$WORKSPACE/.repository</tt> as the local Maven repository.
This means each job will get its own isolated Maven repository just for itself. It fixes the above problems,
at the expense of additional disk space consumption.

<p>
When using this option, consider setting up a Maven artifact manager so that you don't have to hit
remote Maven repositories too often.

<p>
If you'd prefer to activate this mode in all the Maven jobs executed on Jenkins, refer to the technique described
<a href="http://jenkins.361315.n4.nabble.com/Hudson-on-2-4-8-16-core-boxes-td371215.html#a371217">here</a>.
</div>

<div>
Normalement, Jenkins utilise le repository Maven local que Maven détermine lui-même —
le process exact ne semble pas documenté mais ce répertoire est généralement <tt>~/.m2/repository</tt>.
Il peut être modifié par le paramêtre <localRepository> dans le fichier <tt>~/.m2/settings.xml</tt>
(voir <a href="http://maven.apache.org/settings.html">la référence</a> pour plus de détails.)

<p>
Cela signifie que, normalement, tous les jobs qui sont exécutés sur le même noeud (même machine) partagent
un repository Maven unique. L'avantage, c'est que vous économisez de l'espace disque. Par contre, il
peut aussi arriver que ces builds interfèrent les uns avec les autres. Par exemple, vous pouvez finir
par avoir des builds qui s'achèvent avec succès incorrectement, simplement parce que toutes les
dépendances sont déjà dans votre repository local, alors que les repositories spécifiés dans le POM
ne les contiennent pas.

<p>
Il semble aussi y avoir des problèmes quand des process Maven concurrents tendent d'accéder au même
repository local.

<p>
Quand cette option est sélectionnée, Jenkins demandera à Maven d'utiliser <tt>$WORKSPACE/.repository</tt>
comme répertoire local Maven.
Du coup, chaque job aura son propre repository Maven parfaitement isolé. Cela règle les problèmes
cités ci-dessus, en échange de plus d'espace disque.

<p>
Si vous utilisez cette option, pensez à mettre en place un gestionnaire d'artefacts Maven. Ainsi,
vous ne serez pas forcés d'accéder aux repositories Maven distants trop fréquemment.

<p>
Si vous préférez activer ce mode pour tous les jobs Maven exécutés par Jenkins, référez-vous à la
technique décrite
<a href="http://jenkins.361315.n4.nabble.com/Hudson-on-2-4-8-16-core-boxes-td371215.html#a371217">ici</a>.
</div>

maven-plugin/src/main/webapp/root-pom_fr.html

Files

root-pom.html

root-pom_fr.html

CURRENT

04.02.2013 00:16:09, no SCM information	04.02.2013 00:16:09, no SCM information
<div> If your workspace has the top-level <tt>pom.xml</tt> in somewhere other than the 1st module's root directory, specify the path (relative to the module root) here, such as <tt>parent/pom.xml</tt>. <br> If left empty, defaults to <tt>pom.xml</tt> </div>	<div> <!-- OUTDATED --> Si votre <tt>pom.xml</tt> du plus haut niveau se trouve dans un répertoire différent du répertoire racine du workspace, spécifiez ici le chemin (de façon relative à la racine du répertoire de travail), par exemple <tt>parent/pom.xml</tt>. <br> Si ce champ est vide, la valeur par défaut est <tt>pom.xml</tt>. </div>

maven-plugin/src/main/webapp/run-headless_fr.html

Files

run-headless.html

run-headless_fr.html

CURRENT

04.02.2013 00:16:09, no SCM information

<div>
<p>
If build doesn't requires access to desktop (only using command line tools and tests) this option can be checked.
<p>
This option allow Jenkins to configure the build process in headless mode. Usefull on OSX to avoid boring Dock icon
to take focus, this option may also in future release be used to select slave adequate instance.
</div>

<div>
<p>
Si le build ne n&eacute,cessite pas un accè à l'environnement graphique (s'il n'utilise que des outils
en ligne de commande) cette option peut être activ�e.
<p>
Cette option permet à Jenkins de lancer le processus de build en mode <em>'headless'</em>. Ceci est
particulièrement intéressant sur OSX pour éviter qu'une icône Java prenne le focus en sautillant
dans le Dock. Cette option pourrait à l'avenir servir à sélectionner un esclave adapté.
</div>

osx/Library/Documentation/Jenkins/command-line-preferences.html (Master)

Files

command-line-preferences.html

combinationfilter_fr.html

MISSING

23.07.2013 16:05:31, no SCM information

<html>
<head>
<title>Jenkins command-line preferences</title>
</head>
<body>
<h1>Jenkins command-line preferences</h1>

<p><a href="https://wiki.jenkins-ci.org/display/JENKINS/Starting+and+Accessing+Jenkins">The Jenkins Wiki page</a> tells you how to change settings like which port number Jenkins will listen to. These settings need to be specified on the command line when Jenkins is started.

<h4>Launch daemon</h4>

<p>For the Mac, Jenkins is deployed as a launch daemon. (If you want to know more about launchd and daemons, see <a href="http://developer.apple.com/library/mac/#technotes/tn2083/_index.html">here</a> and <a href="http://developer.apple.com/library/mac/#documentation/MacOSX/Conceptual/BPSystemStartup/Articles/LaunchOnDemandDaemons.html">here</a>)

<p>The launch daemon picks up the command line options from a standard preferences file, <tt>/Library/Preferences/org.jenkins-ci.plist</tt>. If the file does not exist, built-in defaults are used. The preference files are manipulated using the standard utility <tt>defaults</tt>.

<h4>How To Use the defaults Command</h4>

<p>To view all settings in the file, run:
<tt>defaults read /Library/Preferences/org.jenkins-ci</tt>

<p>To get the value of a single setting, run:
<tt>defaults read /Library/Preferences/org.jenkins-ci SETTING</tt>

<p>To set the value of a setting, run:
<tt>defaults write /Library/Preferences/org.jenkins-ci SETTING VALUE</tt>

<p>For more information, see <tt>man defaults</tt>

<h4>Supported Settings</h4>

<p>The list of settings supported by the Jenkins launch daemon (see <a href="http://winstone.sourceforge.net/#commandLine">documentation</a>):

<ul>
<li>prefix
<li>httpPort
<li>httpListenAddress
<li>httpsPort
<li>httpsListenAddress
<li>ajp13Port
<li>ajp13ListenAddress
</ul>

<p>Additionally, you can set also these:

<ul>
<li>war (Full path name to jenkins.war file. Defaults to <tt>/Applications/Jenkins/jenkins.war</tt>)
<li>JENKINS_HOME (Full path to JENKINS_HOME directory where Jenkins keeps its files. Defaults to <tt>/Users/Shared/Jenkins</tt>)
<li>minHeapSize (Passed to java command-line <tt>-Xms</tt> parameter. Defaults to 256m on 64bit architectures and 64m on 32bit)
<li>heapSize (Passed to java command-line <tt>-Xmx</tt> parameter. Defaults to 512m on 64bit architectures and 128m on 32bit)
<li>minPermGen (Passed to java command-line <tt>-XX:PermSize</tt> parameter. Defaults to 256m on 64bit architectures and 64m on 32bit)
<li>permGen (Passed to java command-line <tt>-XX:MaxPermSize</tt> parameter. Defaults to 512m on 64bit architectures and 128m on 32bit)
</ul>

</body>
</html>

war/src/main/webapp/help/LogRecorder/logger_fr.html

Files

logger.html

logger_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
Specify a set of logger names and the corresponding log levels that
this log recorder will collect. For example, if you specify
<tt>hudson.model.Hudson</tt> and <tt>info</tt>, any logs recorded
for <tt>hudson.model.Hudson</tt> or its descendants with the log level
info or above will show up in this log recorder.

<p>
If you have multiple entries, a log entry that matches any of them
will be collected.

<p>
Also see <a href="http://wiki.jenkins-ci.org/display/JENKINS/Logger+Configuration">
this document</a> for more about logging in Java and Jenkins.
</div>

<div>
Spécifie une collection de noms de loggueurs et de leurs niveaux de log que l'enregistreur de log
collectera. Par exemple, si vous spécifiez <tt>hudson.model.Hudson</tt> et <tt>info</tt>, tous les logs
enregistrés pour <tt>hudson.model.Hudson</tt> ou ses descendants avec le niveau info ou supérieur,
appraitront dans cet enregistreur de log.

<p>
Si vous avez des entrées multiples, une demande de log qui correspond à l'un d'entre eux sera bien enregistrée.

<p>
Voyez également <a href="http://wiki.jenkins-ci.org/display/JENKINS/Logger+Configuration">
ce document</a> pour plus de détails sur le logging en Java et avec Jenkins.
</div>

war/src/main/webapp/help/LogRecorder/name_fr.html

Files

name.html

name_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information	04.02.2013 00:16:10, no SCM information
<div> Specify a name that uniquely identifies this log recoder among others. By using a log recorder, you can group related logs into one file for easier inspection, and by using multiple log recorders, you can create multiple such groups. </div>	<div> Spécifiez un nom qui identifie cet enregistreur de log de façon unique parmi les autres. Un enregistreur de log vous permet de regrouper les logs sur un même thème dans un seul fichier pour consultation. En utilisant plusieurs enregistreurs de log, vous pouvez créer ainsi de multiples groupes. </div>

war/src/main/webapp/help/matrix/axes_fr.html

Files

axes.html

axes_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
If your configuration matrix needs additional axes, you can specify them here.
<p>
For example, let's say you are trying to run a test for your database application,
and you need to test it with three databases: MySQL, PostgreSQL, and Oracle. Your
build script is designed so that you can test with a particular database by doing
<tt>ant -Ddatabase=mysql</tt>.
<p>
This is the concept of an axis. You can have a variable called "database",
which takes three values. When you configure it, Jenkins will run 3 builds, each with
different values assigned to the "database" variable to exhaustively cover
the configuration matrix.
<p>
Variables specified here are made available to the build as environment variables.
In addition, for Ant and Maven, variables are also exposed as properties, as if
<tt>-D<i>variableName</i>=<i>value</i></tt> are specified on the command line.
<p>
When multiple axes are specified, all of the possible combinations of axes are built
exhaustively. Multiple values in labels and JDKs are treated in the same way. So
if you specify jdk=[JDK5,JDK6], database=[mysql,postgresql,oracle], container=[jetty,tomcat],
then each build will consists of 2x3x2=12 different sub-builds.
</div>

<div>
Si votre matrice de configuration a besoin d'axes supplémentaires,
vous pouvez les spécifiez ici.
<p>
Par exemple, supposons que vous voulez lancer un test pour une
application de base de données et que vous devez la tester avec trois
bases : MySQL, PostgreSQL et Oracle.
Votre script de build est conçu de façon à spécifier la base à tester
ainsi :
<tt>ant -Ddatabase=mysql</tt>.
<p>
Un axe, c'est ça. Vous pouvez avoir une variable "database",
qui prend trois valeurs possibles. Quand vous configurez l'axe, Jenkins
lancera 3 builds, avec les 3 valeurs possibles assignées à la variable
"database" afin de couvrir toutes combinaisons de configurations
possibles (la matrice des configurations).
<p>
Les variables spécifiées ici sont disponibles pour le build comme
variables d'environnement.
De plus, pour Ant et Maven, les variables sont également exposées en
tant que propriétés, comme si elles étaient passées avec
<tt>-D<i>nomVariable</i>=<i>valeur</i></tt> en ligne de commande.
<p>
Quand plusieurs axes sont spécifiés, toutes les combinaisons d'axe
possibles sont construites de façon exhaustive. Les valeurs multiples
pour les labels et les JDKs sont traitées de la même façon. Par exemple,
si vous spécifiez jdk=[JDK5,JDK6], database=[mysql,postgresql,oracle],
container=[jetty,tomcat], alors chaque build exhaustif consistera en
2x3x2=12 sous-builds différents.
</div>

war/src/main/webapp/help/matrix/combinationfilter_fr.html

Files

combinationfilter.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
By default, Jenkins builds all the possible combinations of axes exhaustively. But sometimes this is too many,
or may contain combinations that don't make sense.
In such a situation, you can make the matrix sparse by filtering out combinations that you don't want through
a Groovy expression that returns true or false.

<p>
When you specify a Groovy expression here, only the combinations that result in <b>true</b>
will be built. In evaluating the expression, axes are exposed as variables (with their values set
to the current combination evaluated).

<h4>Filtering based on values</h4>
<p>
For example, let's say you are building on different operating systems for
different compilers. Assume that your slave labels are <b>label=[linux,solaris]</b> and you have
created an axis as <b>compiler=[gcc,cc].</b>

Any of the following expressions will filter out <b>cc</b> builds on <b>linux</b>. Depending on
how you think about this constraint, you'll probably find some more intuitive than others.

<center>
<table>
<tr>
<td>Read "if both linux and cc, it's invalid"</td>
<td>
<pre>!(label=="linux" && compiler=="cc")</pre>
</td>
</tr>
<tr>
<td>Read "for a combination to be valid, it has to be either on solaris or on gcc."</td>
<td>
<pre>label=="solaris" || compiler=="gcc"</pre>
</td>
</tr>
<tr>
<td>Read "if on Solaris, just do cc"</td>
<td>
<pre>(label=="solaris").implies(compiler=="cc")</pre>
</td>
</tr>
</table>
</center>

<h4>Sparsening of the matrix</h4>
<p>
In addition to the specific filtering rules based on values, one can also use a special
variable "<tt>index</tt>", which can be used to sparsen the matrix.

<p>
For example, <tt>index%2==0</tt> would cut the matrix size in half by removing one
combination per every 2 combinations, in such a way that the coverage is still reasonable.
Similarly, <tt>index%3!=0</tt> would cut the matrix size into 66% by throwing
away every 1 out of 3 combinations.
</div>

<div>
Par défaut, Jenkins builde toutes les combinaisons possibles de tous les axes, de façon exhaustive. Parfois,
cela fait trop de combinaisons ou certaines combinaisons n'ont pas de sens.
Dans ce cas, vous pouvez réduire la matrice en filtrant les combinaisons que vous ne voulez pas à l'aide
d'une expression Groovy qui retourne vrai ou faux.

<p>
Quand vous spécifiez une expression Groovy ici, seules les combinaisons qui retournent <b>true</b>
seront construites. Lors de l'évaluation de l'expression, les axes sont exposés comme des variables
(avec leurs valeurs positionnées sur la combinaison courante).

<h4>Filtre basé sur les valeurs</h4>
<p>
Par exemple, disons que vous buildez sur des systèmes d'exploitation différents, pour des compilateurs
différents. Supposons que les libellés de vos esclaves sont <b>label=[linux,solaris]</b> et que vous
avez un axe <b>compiler=[gcc,cc].</b>

Chacune des expressions suivantes filtreront (c-à-d retireront) les builds <b>cc</b> sur <b>linux</b>.
Selon la façon dont vous envisagez cette contrainte, vous trouverez certaines expressions plus claires
que d'autres.

<center>
<table>
<tr>
<td>Lire "si simultanément linux et cc, alors c'est invalide"</td>
<td>
<pre>!(label=="linux" && compiler=="cc")</pre>
</td>
</tr>
<tr>
<td>Lire "pour qu'une combinaison soit valide, elle doit être soit sur solaris, soit utiliser gcc."</td>
<td>
<pre>label=="solaris" || compiler=="gcc"</pre>
</td>
</tr>
<tr>
<td>Lire "quand on est sur solaris, n'utiliser que cc"</td>
<td>
<pre>(label=="solaris").implies(compiler=="cc")</pre>
</td>
</tr>
</table>
</center>

<h4>Limitation de la matrice</h4>
<p>
En plus des règles de filtrage basées sur les valeurs, on peut également utiliser une
variable spéciale "<tt>index</tt>" qui peut être utilisée pour diminuer la matrice.

<p>
Par exemple, <tt>index%2==0</tt> diminuerait la matrice de moitié en retirant 1 combinaison sur 2,
de façon à ce que la couverture reste raisonnable.
De même, <tt>index%3!=0</tt> réduirait la matrice à 66% en supprimant 1 combinaison sur 3.
</div>

war/src/main/webapp/help/matrix/jdk_fr.html

Files

jdk.html

jdk_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
Specify the JDK(s) with which builds are performed. If none is selected,
the default JDK is used (no explicit <tt>JAVA_HOME</tt>, and <tt>java</tt> command
is assumed to be in <tt>PATH</tt>.) If multiple JDKs are selected,
the configuration matrix will include all of the specified JDKs.
<br>
Selecting multiple values is typically useful when this job is running tests,
and you need to run tests on multiple different versions of JDKs.
<br>
During a build, the selected JDK value for the given run is available as the "jdk" axis.
See the help of "axes" below for more information about how to access the axis value.
</div>

<div>
Spécifie le(s) JDK avec le(s)quel(s) les builds seront exécutés. Si aucun
n'est donné, le JDK par défaut est utilisé (pas de variable
<tt>JAVA_HOME</tt> explicite; on suppose que la commande <tt>java</tt>
est dans le <tt>PATH</tt>). Si de multiples JDK sont précisés, la
matrice de configuration incluera tous ces JDK.
<br>
Avoir de multiples valeurs est utile typiquement quand le job exécute des
tests et que vous devez les lancer sur plusieurs versions différentes
du JDK.
<br>
Au cours d'un build, le JDK sélectionné est visible dans l'axe 'jdk'.
Référez-vous à l'aide sur les 'axes' ci-dessous pour plus d'information
sur l'accès à la valeur d'un axe.
</div>

war/src/main/webapp/help/parameter/boolean-default_fr.html

Files

boolean-default.html

boolean-default_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information	04.02.2013 00:16:10, no SCM information
<div> Specifies the default value of the field. </div>	<div> Spécifit la valeur par défaut de ce champ. </div>

war/src/main/webapp/help/parameter/boolean_fr.html

Files

boolean.html

boolean_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information	04.02.2013 00:16:10, no SCM information
<div> Defines a simple boolean parameter, which you can use during a build, either as an environment variable, or through variable substitution in some other parts of the configuration. The string value will be 'true' or 'false'. </div>	<div> Définit un paramètre booléen simple. La valeur de la chaîne de caractères de sera 'true' ou 'false'. Vous pouvez l'utiliser dans un build, comme variable d'environnement ou dans d'autres endroits de la configuration à l'aide de la substituion de variables. </div>

war/src/main/webapp/help/parameter/choice-choices_fr.html

Files

choice-choices.html

choice-choices_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information	04.02.2013 00:16:10, no SCM information
<div> The potential choices, one per line. The value on the first line will be the default. </div>	<div> Les choix possibles, un par ligne. La valeur sur la première ligne sera la valeur par défaut. </div>

war/src/main/webapp/help/parameter/choice_fr.html

Files

choice.html

choice_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information	04.02.2013 00:16:10, no SCM information
<div> Defines a simple string parameter, which can be selected from a list. You can use it during a build, either as an environment variable, or through variable substitution in some other parts of the configuration.. </div>	<div> Définit un paramètre simple comme une chaîne de caractères, qui peut être sélectionnée dans une liste. Vous pouvez l'utiliser dans un build, comme variable d'environnement ou dans d'autres endroits de la configuration à l'aide de la substituion de variables. </div>

war/src/main/webapp/help/parameter/description_fr.html

Files

CURRENT

04.02.2013 00:16:10, no SCM information	04.02.2013 00:16:10, no SCM information
<div> A description that will be shown to the user later. </div>	<div> Une description qui sera montrée à l'utilisateur plus tard. </div>

war/src/main/webapp/help/parameter/file-name_fr.html

Files

file-name.html

file-name_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information	04.02.2013 00:16:10, no SCM information
<div> Specifies the location, relative in the workspace, where the uploaded file will be placed (for example, like "<tt>jaxb-ri/data.zip</tt>") </div>	<div> Spécifie la location, relative au workspace, où le fichier uploadé sera placé (par exemple, "<tt>jaxb-ri/data.zip</tt>"). </div>

war/src/main/webapp/help/parameter/file_fr.html

Files

file.html

file_fr.html

OUTDATED

18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:10, no SCM information
<div> Accepts a file submission from a browser as a build parameter. The uploaded file will be placed at the specified location in the workspace, which your build can then access and use. <p>This is useful for many situations, such as:<ol> <li>Letting people run tests on the artifacts they built.</li> <li>Automating the upload/release/deployment process by allowing the user to place the file.</li> <li>Perform data processing by uploading a dataset.</li> </ol> <p> The name of the submitted file is available in the environment variable whose name is the same as file location. For example, if you set the file location to be <tt>abc.zip</tt>, then <tt>${abc.zip}</tt> would give you the original file name passed from the browser (such as <tt>my.zip</tt>.) The name will not include the directory name portion. </p> <p> File upload is optional. If a user chooses not to upload anything, Jenkins will simply skips this parameter and will not place anything (but it also will not delete anything that's already in the workspace.) </p> </div>	<div> Prend un fichier passé par un navigateur web comme paramètre de build. Le fichier uploadé sera placé à l'endroit spécifié dans le workspace, auquel votre build pourra ensuite accéder. <p>Cela est utile pour de nombreuses situations, telles que :<ol> <li>Permettre aux utilisateurs de lancer des tests sur les artefacts qu'ils ont construits ;</li> <li>Automatiser la procédure de upload/livraison/déploiement en permettant à l'utilisateur de placer directement le fichier ;</li> <li>Réaliser du traitement de données en uploadant une collection de données.</li> </ol> <p>Il est possible de ne rien uploader. Dans ce cas, et si aucun fichier n'est déjà présent à l'endroit spécifié dans le workspace, alors rien ne se passera. Si par contre il existe déjà un fichier dans le workspace, alors ce fichier sera gardé tel quel.</p> </div>
(old value)

war/src/main/webapp/help/parameter/name_fr.html

Files

name.html

name_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information	04.02.2013 00:16:10, no SCM information
<div> The name of the parameter <p> These parameters are exposed to build as environment variables. </div>	<div> Le nom du paramètre. <p> Notez que quand ce champ est exposé comme une variable d'environnement, le nom sera toujours en majuscules (c-à-d que le paramètre "foo" sera exposé en tant que "FOO"). Dans Ant, par exemple, vous pourrez y accéder avec ${env.FOO}. </div>

war/src/main/webapp/help/parameter/run-filter.html (Master)

Files

run-filter.html

block-downstream-building.html

MISSING

30.05.2013 20:09:20, no SCM information
<div> Filter the list of builds which are included in the drop-down list. <pre> 'All Builds' - List all builds including in-progress builds. 'Completed Builds Only' - List all completed builds. 'Successful Builds Only' - List all Successful builds (Stable and Unstable) 'Stable Builds Only' - List all Stable builds. </pre> </div>

war/src/main/webapp/help/parameter/run-project_fr.html

Files

run-project.html

run-project_fr.html

OUTDATED

30.05.2013 20:09:20, no SCM information	04.02.2013 00:16:10, no SCM information
<div> Defines the job from which the user can pick runs. The last run will be the default. These parameters are exposed to build as environment variables: <pre> PARAMETER_NAME=<i><jenkins_url></i>/job/<i><job_name>/<run_number></i>/ PARAMETER_NAME_JOBNAME=<i><job_name></i> PARAMETER_NAME_NUMBER=<i><run_number></i> PARAMETER_NAME_NAME=<i><display_name></i> PARAMETER_NAME_RESULT=<i><run_result></i> </pre> </div>	<div> Définit le job à partir duquel l'utilisateur peut choisir des exécutions. Le dernier lancement sera celui par défaut. </div>
(old value)

war/src/main/webapp/help/parameter/run_fr.html

Files

run.html

run_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information	04.02.2013 00:16:10, no SCM information
<div> Defines a run parameter, where users can pick a single run of a certain project. The absolute url of this run will be exposed as an environment variable, or through variable substitution in some other parts of the configuration. In the build this can be used to query Jenkins for further information. </div>	<div> Définit un paramètre d'exécution, que les utilisateurs pourront choisir pour une exécution unique d'un certain projet. L'URL absolue de cette exécution sera exposée comme une variable d'environnement ou à travers la substitution de variables dans certaines parties de la configuration. Dans le build, cela peut être utilisé pour demander plus d'informations à Jenkins. </div>

war/src/main/webapp/help/parameter/string-default_fr.html

Files

string-default.html

string-default_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information	04.02.2013 00:16:10, no SCM information
<div> Specifies the default value of the field, which allows the user to save typing the actual value. </div>	<div> Spécifie la valeur par défaut du champ, ce qui permet à l'utilisateur d'éviter de la taper à la main. </div>

war/src/main/webapp/help/parameter/string_fr.html

Files

string.html

string_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
Defines a simple text parameter, where users can enter a string value,
which you can use during a build, either as an environment variable, or
through variable substitution in some other parts of the configuration.
</div>

<div>
Définit un paramètre textuel simple, où les utilisateurs peuvent
entrer une valeur de type String. Il peut être utilisé dans un build
comme variable d'environnement, ou dans d'autres endroits de la
configuration, grâce à la substitution de variables.

<p>
Notez que, lorsque ce champ est exposé comme variable d'environnement,
il sera toujours en majuscules (par exemple, le paramètre "foo"
sera exposé sous le nom "FOO".)
</div>

war/src/main/webapp/help/project-config/batch_fr.html

Files

batch.html

batch_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
Runs a Windows batch script for building the project.
The script will be run with the workspace as the current directory.

The text you enter in the text box will be executed as a batch file, and a build
will be considered a failure if at the end of the execution %ERRORLEVEL% is not 0.

<p>
If you already have a batch file in SCM, you can just type in the path of that batch file
(again relative to the workspace directory), and simply execute that.
</div>

<div>
Lance un script batch Windows pour construire le projet.
Le script sera lancé avec le répertoire workspace comme répertoire de
travail.

Le texte que vous entrez dans la zone de texte sera exécuté comme
un fichier batch et un build sera considéré comme un échec si, à la fin de
l'exécution, la valeur %ERRORLEVEL% est différente de 0.
<p>
Si vous avez déjà un fichier batch en gestion de version, vous pouvez
entrer le chemin vers ce fichier batch (de façon relative au
répertoire de travail) et l'exécuter directement.
</div>

war/src/main/webapp/help/project-config/block-downstream-building.html (Master)

Files

block-upstream-building.html

MISSING

04.02.2013 00:16:10, no SCM information
<div> When this option is checked, Jenkins will prevent the project from building when a child of this project is in the queue, or building. The children include the direct as well as the transitive children. </div>

war/src/main/webapp/help/project-config/block-upstream-building.html (Master)

Files

MISSING

04.02.2013 00:16:10, no SCM information
<div> When this option is checked, Jenkins will prevent the project from building when a dependency of this project is in the queue, or building. The dependencies include the direct as well as the transitive dependencies. </div>

war/src/main/webapp/help/project-config/custom-workspace_fr.html

Files

custom-workspace.html

custom-workspace_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
For each job on Jenkins, Jenkins allocates a unique "workspace directory." This is the directory
where the code is checked out and builds happen. Normally you should let Jenkins allocate
and clean up workspace directories, but in several situations this is problematic,
and in such case, this option lets you specify the workspace location manually.

<p>
One such situation is where paths are hard-coded and the code needs to be built on a specific location.
While there's no doubt that such a build is not ideal, this option allows you to get going in such a situation.

<p>
Another situation where this is useful is when you are using the project type not to perform
a software build, but execution of a certain batch task, perhaps as a cron replacement. In such case,
you can use this option to map the relevant directory as the workspace, so that people can look at files
through the Jenkins web UI, and you can kick relevant commands more easily.

<p>
If you are in a distributed build environment, unless you tie a job to a specific node, Jenkins may still
move around jobs to different slaves. Sometimes this is desirable, sometimes this is not. Also,
you can map multiple projects to have the same workspace, but if you do so, make sure concurrent executions
of those jobs won't have nasty interferance with each other.

<p>
If this path is relative, it's resolved against the "remote FS root" directory of the slave, or <tt>$JENKINS_HOME</tt>
on the master.
</div>

<div>
Pour chaque job, Jenkins alloue un "répertoire de travail" unique. Il s'agit du répertoire
où le code est placé en provenance de l'outil de gestion de configuration et où les builds ont lieu.
En règle générale, vous devriez laisser Jenkins allouer et nettoyer les répertoires de travail, mais
dans certaines circonstances, cela peut poser problème. Cette option vous permet de spécifier
le répertoire de travail manuellement.

<p>
Un exemple d'une telle situation est quand les chemins sont codés en dur et que le code a besoin
d'être construit à partir d'un emplacement spécifique.
Il est certain qu'une telle configuration de build est déconseillée, mais cette option vous
permet néanmoins d'avencer dans ces circonstances.

<p>
Un autre cas où cette option est utile est lorsque vous utilisez le type de projet 'free-style', non
pour construire un projet logiciel mais pour exécuter certaines tâches en batch, par exemple à la
place d'un cron. Dans ce cas, utilisez cette option pour allouer un répertoire spécifique
au répertoire de travail du batch, afin que les utilisateurs puissent accéder aux fichiers directement
à travers l'interface web de Jenkins. Il sera également possible de lancer les commandes plus
facilement.

<p>
Si vous êtes dans un environnement distribué, à moins d'associer un job à un noeud (une machine) spécifique,
Jenkins sera toujours capable de déporter des jobs sur différentes machines esclaves, même si cette option
est utilisée. Parfois, cela est souhaitable; parfois, non.<br>
Par ailleurs, il est possible d'associer plusieurs projets à un même répertoire de travail;
assurez-vous dans ce cas que des exécutions concurrentes de ces jobs n'interfèrent pas de façon
adverse les unes avec les autres.
</div>

war/src/main/webapp/help/project-config/defaultView.html (Master)

Files

defaultView.html

MISSING

04.02.2013 00:16:10, no SCM information
<div> If you have multiple views defined, you can choose the one to be used as the Jenkins top page. This is useful for larger Jenkins deployments where the 'All' view is too long to be a practical view. (Choosing another view as the default allows you to delete the 'All' view, if so desired.) </div>

war/src/main/webapp/help/project-config/description_fr.html

Files

parameterized-build_fr.html

OUTDATED

18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:10, no SCM information
<div> This description is placed on the project top page so that visitors can know what this job is about. You can use any HTML tags (or markup in the configured language) here. </div>	<div> Cette description est placée sur la page principale du projet afin d'expliquer aux utilisateurs l'intérêt de ce job. Vous pouvez utiliser des tags HTML. </div>
(old value)

war/src/main/webapp/help/project-config/disable_fr.html

Files

disable.html

disable_fr.html

OUTDATED

28.02.2013 15:26:35, no SCM information	04.02.2013 00:16:10, no SCM information
<div> Sometimes you want to temporarily stop building a project. For example, maybe you are in the middle of a large migration and you know new builds are going to fail. Or maybe a project is built every hour but you know that the CVS server will be down for the next 24 hours. <p> When this option is set, no new build is performed on this project. This allows you to disable new builds without changing any of the build dependency chain or changing the notification set up. </div>	<div> <p> De temps en temps, vous aurez besoin d'arrêter temporairement la construction d'un projet. Par exemple, si vous êtes au milieu d'une importante migration et que vous savez que les prochains builds vont échouer. Ou si un projet est reconstruit toutes les heures, mais que vous savez que CVS sera indisponible pour les prochaines 24 heures. <p> Quand cette option est activée, aucun build n'est exécuté sur ce projet. Cela vous permet de désactiver les futurs builds sans modifier les chaines de dépendance entre projets ou les paramètres de notification. </div>
(old value)

war/src/main/webapp/help/project-config/downstream_fr.html

Files

downstream.html

downstream_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
Trigger builds of the other projects once a build is successfully completed.
Multiple projects can be specified by using comma, like "abc, def".

<p>
Other than the obvious use case where you'd like to build other projects that have a dependency
on the current project, this can also be useful to split a long build process in to multiple
stages (such as the build portion and the test portion).
</div>

<div>
Déclenche la construction d'autres projets à la suite d'un build achevé
avec succès. De multiples projets peuvent être spécifiés à l'aide de
virgules. ex : "abc, def".

<p>
En dehors des cas classiques où vous désirez construire d'autres projets
qui ont une dépendance avec le projet courant, il peut être utile de
décomposer un long build en plusieurs étapes (avec par exemple une partie
compilation, puis une partie test).
</div>

war/src/main/webapp/help/project-config/fingerprint_fr.html

Files

fingerprint.html

fingerprint_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
Jenkins can record the 'fingerprint' of files (most often jar files) to keep track
of where/when those files are produced and used. When you have inter-dependent
projects on Jenkins, this allows you to quickly find out answers to questions like:

<ul>
<li>
I have <tt>foo.jar</tt> on my HDD but which build number of FOO did it come from?
</li>
<li>
My BAR project depends on <tt>foo.jar</tt> from the FOO project.
</li>
<li><ul>
<li>
Which build of <tt>foo.jar</tt> is used in BAR #51?
</li>
<li>
Which build of BAR contains my bug fix to <tt>foo.jar</tt> #32?
</li>
</ul></li>
</ul>

<p>
To use this feature, all of the involved projects (not just the project
in which a file is produced, but also the projects in which the file
is used) need to use this and record fingerprints.

<p>
See <a href="http://wiki.jenkins-ci.org/display/JENKINS/Fingerprint">this document</a>
for more details.
</div>

<div>
Jenkins est capable d'enregistrer une empreinte numérique unique, ou
'fingerprint', des fichiers (généralement des fichiers jar) pour
conserver la trace de quand et où ces fichiers
sont produits et utilisés. Quand vous avez des projets
inter-dépendants avec Jenkins, cela vous permet de répondre facilement
à des questions telles que :

<ul>
<li>
J'ai <tt>toto.jar</tt> sur mon disque dur, mais de quel numéro de
build provient-il?
</li>
<li>
Mon projet TITI dépend de <tt>toto.jar</tt> du projet TOTO.
</li>
<li><ul>
<li>
Quel build de <tt>toto.jar</tt> est utilisé dans TUTU #51?
</li>
<li>
Quel build de TATA contient ma correction de bug reporté sur
<tt>toto.jar</tt> #32?
</li>
</ul></li>
</ul>

<p>
Pour utiliser cette fonctionnalité, tous les projets concernés (pas
seulement le projet d'où provient un fichier, mais aussi tous les
projets qui l'utilisent) doivent activer cette option et
enregistrer les empreintes numériques.

<p>
Voir
<a href="http://wiki.jenkins-ci.org/display/JENKINS/Fingerprint">ce document</a>
pour plus de details.
</div>

war/src/main/webapp/help/project-config/javadoc-keep-all_fr.html

Files

javadoc-keep-all.html

javadoc-keep-all_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
If you check this option, Jenkins will retain Javadoc for each successful build.
This allows you to browse Javadoc for older builds, at the expense of additional
disk space requirement.

<p>
If you leave this option unchecked, Jenkins will only keep the latest Javadoc,
so older Javadoc will be overwritten as new builds succeed.
</div>

<div>
Si vous cochez cette option, Jenkins conservera les javadocs de chaque build passé avec succès.
Cela permet de naviguer dans les javadocs de build plus anciens, au prix d'une utilisation
plus importante de l'espace disque.

<p>
Si vous laissez cette option décochée, Jenkins ne conservera que les derniers javadocs.
Les anciens javadocs seront donc remplacés à chaque nouveau build qui passe avec succès.
</div>

war/src/main/webapp/help/project-config/log-rotation_fr.html

Files

log-rotation.html

log-rotation_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

20.09.2013 10:05:40, no SCM information

<div>
This controls the disk consumption of Jenkins by managing how long you'd like to keep
records of the builds (such as console output, build artifacts, and so on.)
Jenkins offers two criteria:

<ol>
<li>
Driven by age. You can have Jenkins delete a record if it reaches a certain age
(for example, 7 days old.)
<li>
Driven by number. You can have Jenkins make sure that it only maintains up to
N build records. If a new build is started, the oldest record will
be simply removed.
</ol>

Jenkins also allows you to mark an individual build as 'Keep this log forever', to
exclude certain important builds from being discarded automatically.
The last stable and last successful build are always kept as well.
</div>

<div>
Contrôle la quantité d'espace disque utilisée par Jenkins en vous permettant de gérer
la durée de conservation des éléments créés par les builds (tels que la sortie
console, les artefacts des builds, etc.)

Jenkins propose deux critères :
<ol>
<li>
Gestion par l'âge. Vous pouvez faire supprimer par Jenkins un élément
s'il a plus d'un certain âge (par exemple, plus de 7 jours).
<li>
Gestion par la quantité. Vous pouvez demander à Jenkins de maintenir
un maximum de N objets. Si un nouveau build est lancé, l'élément le
plus ancien sera supprimé.
</ol>

Jenkins vous permet également de marquer un build particulier comme
'A conserver de façon permanente', afin de vous assurer que des builds
importants ne sont pas supprimés automatiquement.
Le dernier build stable et le dernier build exécuté avec succès sont également toujours conservés.
</div>

war/src/main/webapp/help/project-config/mailer_fr.html

Files

mailer.html

mailer_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
If configured, Jenkins will send out an e-mail to the specified recipients
when a certain important event occurs.

<ol>
<li>Every failed build triggers a new e-mail.
<li>A successful build after a failed (or unstable) build triggers a new e-mail,
indicating that a crisis is over.
<li>An unstable build after a successful build triggers a new e-mail,
indicating that there's a regression.
<li>Unless configured, every unstable build triggers a new e-mail,
indicating that regression is still there.
</ol>

For lazy projects where unstable builds are the norm, Uncheck "Send e-mail for every unstable build".
</div>

<div>
Jenkins a la capacité d'envoyer des emails aux destinaires spécifiés
lorsque certains évènements importants ont eu lieu.

<ol>
<li>Chaque build en échec provoque l'envoi d'un mail.
<li>Un build qui passe avec succès après un build en échec
provoque l'envoi d'un mail, ce qui permet de savoir qu'une situation
de crise est résolue.
<li>Un build instable après un build avec succès provoque l'envoi
d'un mail, indiquant ainsi qu'il y a eu une régression.
<li>Sauf configuration contraire, chaque build instable
provoque l'envoi d'un mail, indiquant ainsi qu'une régression est
toujours d'actualité.
</ol>

Pour les projets qui ne suivent pas les bonnes pratiques et
où les builds instables sont la norme, décochez la case
"Envoyer un email à chaque build instable".
</div>

war/src/main/webapp/help/project-config/parameterized-build_fr.html

Files

parameterized-build.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
When you are using Jenkins for various automations, it's sometimes convenient
to be able to "parameterize" a build, by requiring a set of user inputs to
be made available to the build process. For example, you might be setting up
an on-demand test job, where the user can submit a zip file of the binaries to be tested.

<p>
This section configures what parameters your build takes. Parameters are distinguished
by their names, and so you can have multiple parameters provided that they have different names.

<p>
See <a href="http://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build">the Wiki topic</a>
for more discussions about this feature.
</div>

<div>
Il est parfois pratique de "paramètriser" certaines automatisations, en demandant des informations
à l'utilisateur.
Par exemple, vous pourriez proposer un job de test à la demande, où l'utilisateur peut soumettre un
fichier zip des binaires à tester.

<p>
Cette section configure les paramètres que prend votre build. Les paramètres sont identifiés par leurs
noms. Vous pouvez donc avoir des multiples paramètres, du moment qu'ils ont des noms distincts.

<p>
Consultez <a href="http://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build">cette page Wiki</a>
pour plus de discussions autour de cette fonctionnalité.
</div>

war/src/main/webapp/help/project-config/scmCheckoutRetryCount.html (Master)

Files

scmCheckoutRetryCount.html

MISSING

04.02.2013 00:16:10, no SCM information
<div> If a build fails to checkout from the repository, Jenkins will retry the specified number of times before giving up. </div>

war/src/main/webapp/help/project-config/triggerRemotely_fr.html

Files

triggerRemotely.html

triggerRemotely_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
Enable this option if you would like to trigger new builds
by accessing a special predefined URL (convenient for scripts).
<p>One typical example
for this feature would be to trigger new build from the source
control system's hook script, when somebody has just committed
a change into the repository, or from a script that parses
your source control email notifications.</p>
<p>You'll need to provide an authorization token in the form of
a string so that only those who know it would be able to remotely
trigger this project's builds.</p>
</div>

<div>
Activez cette option si vous souhaitez déclencher des builds
en accédant à une URL particulière (pratique pour les scripts).
<p>Un exemple typique serait de déclencher un build à partir
d'un hook sur l'outil de gestion de version, à chaque
fois que quelqu'un ajoute une modification dans la base de
code, ou à partir d'un script qui lit les notifications envoyées
par mail par l'outil de gestion de version.
</p>
<p>Il vous faudra fournir des informations d'autorisation sous forme
d'une chaine de caractères, afin que seuls ceux qui la connaissent
soient à même de déclencher les builds de ce projet à distance.</p>
</div>

war/src/main/webapp/help/project-config/upstream_fr.html

Files

upstream.html

upstream_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
<p>
Set up a trigger so that when some other projects finish building,
a new build is scheduled for this project. This is convenient for running
an extensive test after a build is complete, for example.
</p><p>
This configuration is the opposite view of the "Build other projects" section
in the "Post-build Actions". Updating one will change the other automatically.
</p>
</div>

<div>
<p>
Positionne un déclencheur de build, de façon à ce qu'à la suite du build
de certains projets, un build soit lancé pour ce projet.
Cela est utile pour lancer un long test après la construction d'un
projet, par exemple.
</p><p>
Cette configuration est l'inverse de la section "Construire d'autres
projets" dans "Actions post-build'. Changer l'un modifiera l'autre
automatiquement.
</p>
</div>

war/src/main/webapp/help/run-config/description.html (Master)

Files

MISSING

18.05.2013 17:17:16, no SCM information
<div> This description is placed on the build top page so that visitors can know what this build did. You can use any HTML tags (or markup in the configured language) here. </div>

war/src/main/webapp/help/run-config/displayName.html (Master)

Files

displayName.html

MISSING

04.02.2013 00:16:10, no SCM information
<div> If set, this text is used instead of the default "#NNN" to point to this build. Leave this empty to use the default. </div>

war/src/main/webapp/help/scm-browsers/list.html (Master)

Files

list.html

full-control-once-logged-in.html

MISSING

04.02.2013 00:16:10, no SCM information
<div> Adds links in "changes" views within Jenkins to an external system for browsing the details of those changes. The "Auto" selection attempts to infer the repository browser from other jobs, if supported by the SCM and a job with matching SCM details can be found. </div>

war/src/main/webapp/help/security/container-realm_fr.html

Files

container-realm.html

container-realm_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
Use the servlet container to authenticate users, as per defined by the servlet spec.
This is historically what Jenkins has been doing up to 1.163. It is useful mainly
for the following situations:

<ol>
<li>
You've been using Jenkins before 1.164 and would like to keep its behavior.
</li>
<li>
You've already configured your container with the right security realm and
prefer Jenkins to just use it. (Sometimes the container offers better documentation
or custom implementations to connect to a specific user realm.)
</li>
</ol>
</div>

<div>
Utilise le conteneur de servlet pour authentifier les utilisateurs,
comme défini dans les spécifications des servlets.
C'est historiquement ce qu'a fait Jenkins jusqu'à la version 1.163.
Cela reste utile principalement dans les situations suivantes :

<ol>
<li>
Vous avez utilisé Jenkins avant la version 1.164 et vous désirez
conserver le même comportement.
</li>
<li>
Vous avez déjà configuré votre conteneur avec le bon royaume (realm)
de sécurité et vous souhaitez le faire utiliser par Jenkins.
(parfois le conteneur fournit une meilleure documentation ou des
implémentations custom pour se connecter à un royaume utilisateur
spécifique)
</li>
</ol>
</div>

war/src/main/webapp/help/security/full-control-once-logged-in_fr.html

Files

full-control-once-logged-in_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
In this mode, every logged-in user gets full control of Jenkins. The only user
who won't have full control is anonymous user, who only gets read access.

<p>
This mode is useful to force users to log in before taking actions, so that
you can keep record of who has done what. This setting can be also used in
public-facing Jenkins, where you only allow trusted users to have user accounts.
</div>

<div>
Dans ce mode, un utilisateur connecté obtient le contrôle complet de
Jenkins. Le seul utilisateur qui n'a pas le contrôle complet est
l'utilisateur anonymous, qui n'a que l'accès en lecture seule.

<p>
Ce mode est utile pour forcer les utilisateurs à se logger avant de faire
certaines actions, afin de conserver une trace de qui a fait quoi.
Ce mode peut également être utilisé dans le cas d'une installation publique
de Jenkins, où vous ne pouvez avoir confiance que dans les utilisateurs
qui possèdent des comptes.
</div>

war/src/main/webapp/help/security/ldap/groupSearchBase_fr.html

Files

groupSearchBase.html

groupSearchBase_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
One of the searches Jenkins does on LDAP is to locate the list of groups for a user.
<p>
This field determines the query to be run to identify the organizational unit that
contains groups. The query is almost always <tt>"ou=groups"</tt> so try that first,
though this field may be left blank to search from the root DN.
</p><p>
If login attempts result in "Administrative Limit Exceeded" or similar error, try to
make this setting as specific as possible for your LDAP structure, to reduce the scope
of the query. If the error persists, you may need to edit the
<tt>WEB-INF/security/LDAPBindSecurityRealm.groovy</tt> file that is included in
<tt>jenkins.war</tt>. Change the line with: <br/>
<tt>groupSearchFilter = "(| (member={0}) (uniqueMember={0}) (memberUid={1}))";</tt><br/>
to query only of the field used in your LDAP for group membership, such as: <br/>
<tt>groupSearchFilter = "(member={0})";</tt><br/>
Then restart Jenkins and retry the login.
</p>
</div>

<div>
Une des recherches faites par Jenkins sur LDAP consiste en la localisation de la liste des groupes
d'un utilisateur.

<p>
Ce champ détermine la requète à lancer pour identifier l'unité organisationnelle qui contient des groupes.
La requète est presque toujours <tt>"ou=groups"</tt>; dans la plupart des cas, vous devriez donc laisser
ce champ vide et laisser cette requète par défaut s'exécuter.
</div>

war/src/main/webapp/help/security/ldap/managerDN_fr.html

Files

managerDN.html

managerDN_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
If your LDAP server doesn't support <a href="http://www.google.com/?q=LDAP+anonymous+bind">anonymous binding</a>
(IOW, if your LDAP server doesn't even allow a query without authentication),
then Jenkins would have to first authenticate itself against the LDAP server,
and Jenkins does that by sending "manager" DN and password.

<p>
A DN typically looks like <tt>CN=MyUser,CN=Users,DC=mydomain,DC=com</tt>
although the exact sequence of tokens depends on the LDAP server configuration.
It can be any valid DN as long as LDAP allows this user to query data.

<p>
This configuration is also useful when you are connecting to Active Directory
from a Unix machine, as AD doesn't allow anonymous bind by default. But
if you can't figure this out, you can also change AD setting to allow
anonymous bind. See <a href="http://www.novell.com/coolsolutions/appnote/15120.html">this document</a> for how to.
</div>

<div>
Si votre serveur LDAP ne supporte pas le <a href="http://www.google.com/?q=LDAP+anonymous+bind">binding anonyme</a>
(c'est-à-dire, si votre serveur LDAP ne permet pas le requêtage sans authentification),
alors Jenkins va devoir s'authentifier auprès du serveur. Il fait cela en envoyant le
DN et le mot de passe du "gestionnaire".

<p>
Un DN ressemble typiquement à <tt>CN=MyUser,CN=Users,DC=mydomain,DC=com</tt>
bien que la séquence exacte des éléments dépend de la configuration du serveur LDAP.
Cela peut être tout DN valide, tant que LDAP autorise cet utilisateur à lancer des
requêtes sur les données.

<p>
Cette configuration est également utile quand vous êtes connectés à Active Directory
à partir d'une machine Unix, car AD ne permet pas le bind anonyme par défaut. Si cette
configuration vous parait trop complexe, vous pouvez simplement changer les paramètres de
AD afin d'authoriser le binding anonyme.
Voir <a href="http://www.novell.com/coolsolutions/appnote/15120.html">ce document</a>
pour plus d'explications.
</div>

war/src/main/webapp/help/security/ldap/managerPassword_fr.html

Files

managerPassword.html

managerPassword_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information	04.02.2013 00:16:10, no SCM information
<div> Password for the manager DN specified above. </div>	<div> Le mot de passe du gestionnaire DN spécifié ci-dessus. </div>

war/src/main/webapp/help/security/ldap/rootDN_fr.html

Files

rootDN.html

rootDN_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
For authenticating user and determing the roles given to this user, Jenkins performs
multiple LDAP queries.

Since an LDAP database is conceptually a big tree and the search is performed recursively,
in theory if we can start a search starting at a sub-node (as opposed to root), you get
a better performance because it narrows down the scope of a search.
This field specifies the DN of such a subtree.

<p>
But in practice, LDAP servers maintain an extensive index over the data, so specifying
this field is rarely necessary — you should just let Jenkins figure this out
by talking to LDAP.

<p>
If you do specify this value, the field normally looks something like <tt>"dc=sun,dc=com"</tt>
</div>

<div>
Pour authentifier les utilisateurs et déterminer leurs rôles,
Jenkins exécute de multiples requêtes LDAP.

Comme une base LDAP peut se voir comme une structure arborescente
et que la recherche se fait de façon récursive, en théorie, si nous
pouvons commencer une recherche à partir d'un sous-noeud (plutôt
qu'à partir de la racine), les performances seront meilleures, puisque
le périmètre de la recherche est plus petit.

Ce champ spécifie le DN de ce sous-arbre.

<p>
En pratique, les serveurs LDAP conservent un index très complet sur les
données, donc peupler ce champ est rarement nécessaire.
Vous devriez laisser Jenkins déterminer cela lors des communications
avec LDAP.

<p>
Si vous fournissez cette valeur, le champ sera du type
<tt>"dc=sun,dc=com"</tt>.
</div>

war/src/main/webapp/help/security/ldap/server_fr.html

Files

server.html

server_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
Specify the name of the LDAP server host name (like <tt>ldap.sun.com</tt>).
If your LDAP server uses a port other than 389 (which is the standard for LDAP),
you can also append a port number here, like <tt>ldap.acme.org:1389</tt>.
To connect to LDAP over SSL (AKA LDAPS), specify it with the <tt>ldaps://</tt> protocol,
like <tt>ldaps://ldap.acme.org</tt> or <tt>ldaps://ldap.acme.org:1636</tt> (if
the port is other than the default 636).
</div>

<div>
Spécifie le nom du serveur host LDAP (par exemple <tt>ldap.sun.com</tt>).
Si votre serveur LDAP utilise un port autre que 389 (le standard pour LDAP),
vous pouvez suffixer un numéro de port ici, par exemple <tt>ldap.acme.org:1389</tt>.
Pour se connecter à LDAP par SSL (c-à-d LDAPS), utilisez le protocole
<tt>ldaps://</tt>, par exemple <tt>ldaps://ldap.acme.org</tt> ou
<tt>ldaps://ldap.acme.org:1636</tt> (si le port n'est pas le port par défaut 636).
</div>

war/src/main/webapp/help/security/ldap/userSearchBase_fr.html

Files

userSearchBase.html

userSearchBase_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
One of the searches Jenkins does on LDAP is to locate the user record given the user name.
If you specify a relative DN (from the root DN) here, Jenkins will further narrow down
searches to the sub-tree.

<p>
But in practice, LDAP servers maintain an extensive index over the data, so specifying
this field is rarely necessary.

<p>
If you do specify this value, the field normally looks something like <tt>"ou=people"</tt>
</div>

<div>
Une des recherches faite par Jenkins sur LDAP consiste à obtenir les
informations utilisateur à partir de son nom.
Si vous fournissez ici un DN relatif (au DN racine), Jenkins limitera
le périmètre de la recherche au sous-arbre correspondant.

<p>
En pratique, les serveurs LDAP conservent un index très complet
sur les données, donc ce champ est rarement nécessaire.

<p>
Si vous peuplez cette valeur, elle devrait être du type
<tt>"ou=people"</tt>.
</div>

war/src/main/webapp/help/security/ldap/userSearchFilter_fr.html

Files

userSearchFilter.html

userSearchFilter_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
One of the searches Jenkins does on LDAP is to locate the user record given the user name.

<p>
This field determines the query to be run to identify the user record. The query is
almost always <tt>"uid={0}"</tt> as per defined in <a href="http://www.ietf.org/rfc/rfc2798.txt">RFC 2798</a>,
so in most cases you should leave this field empty and let this default kick in.

<p>
If your LDAP server doesn't have uid or doesn't use a meaningful uid value, try <tt>"mail={0}"</tt>,
which lets people login by their e-mail address.

<p>
If you do specify a different query, specify an LDAP query string with marker token "{0}",
which is to be replaced by the user name string entered by the user.
</div>

<div>
Une des recherches faite par Jenkins sur LDAP consiste à obtenir les
informations utilisateur à partir de son nom.

<p>
Ce champ indique quelle requête lancer pour identifier les informations
utilisateur. Cette requête est presque toujours <tt>"uid={0}"</tt>
comme défini dans la
<a href="http://www.ietf.org/rfc/rfc2798.txt">RFC 2798</a>, donc
dans la majorité des cas, vous devriez laisser ce champ vide
et laisser Jenkins utiliser la requête par défaut.

<p>
Dans le cas où une requête différente est nécessaire, fournissez ici
une requête LDAP avec un marqueur "{0}",
qui sera remplacé par le nom fourni par l'utilisateur.
</div>

war/src/main/webapp/help/security/legacy-auth-strategy_fr.html

Files

legacy-auth-strategy.html

legacy-auth-strategy_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information	04.02.2013 00:16:10, no SCM information
<div> Behaves exactly the same as Jenkins <1.164. Namely, if you have the "admin" role, you'll be granted full control over the system, and otherwise (including anonyomus users) you'll only have the read access. </div>	<div> Ceci permet un comportement exactement similaire à celui de Jenkins d'avant la version 1.164. C'est-à-dire que, si vous avez le rôle "admin", vous aurez le contrôle complet sur le système. Si vous n'avez pas ce rôle (ce qui est le cas des utilisateurs anonymes), vous n'aurez que l'accès en lecture seule. </div>

war/src/main/webapp/help/security/no-authorization_fr.html

Files

no-authorization.html

no-authorization_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
No authorization is performed. Everyone gets full control of Jenkins,
including anonymous users who haven't signed on.

<p>
This is useful in situations where you run Jenkins in a trusted environment
(such as a company intranet) and just want to use authentication for
personalization support. In this way, if someone needs to make a quick
change to Jenkins, they won't be forced to log in.
</div>

<div>
Aucune restriction n'est faite sur les autorisations. Tous les utilisateurs
ont le contrôle complet de Jenkins, y compris les utilisateurs anonymes qui
ne se sont pas authentifiés.

<p>
Cela est utile dans les situations où vous lancez Jenkins dans un
environnement de confiance (comme un intranet d'entreprise) et où vous
souhaitez utiliser l'authentification uniquement pour la personnalisation.
De cette façon, si quelqu'un a besoin de faire un changement rapide
sur Jenkins, cette personne ne sera pas forcée à s'authentifier.
</div>

war/src/main/webapp/help/security/private-realm_fr.html

Files

private-realm.html

private-realm_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information	04.02.2013 00:16:10, no SCM information
<div> Use <a href="asynchPeople">Jenkins's own user list</a> for authentication, instead of delegating that to the external system. This is suitable for smaller set up where you have no existing user database elsewhere. </div>	<div> Utilise la <a href="asynchPeople">liste des utilisateurs gérée par Jenkins</a> pour les authentifier, plutôt que de déléguer à un système externe. Cette solution est pratique pour les configurations simples où vous n'avez pas d'utilisateurs dans une base de données ailleurs. </div>

war/src/main/webapp/help/security/private-realm/allow-signup_fr.html

Files

allow-signup.html

allow-signup_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
By default, Jenkins allows users to create accounts by themselves, via the "sign up" link on the top right shoulder of the page.
But if you'd like to prevent random users from creating accounts, and instead tightly control how user accounts are created,
uncheck this box.
<p>
When this checkbox is unchecked, someone with the administrator role would have to create accounts.
<p>
By default, Jenkins does not use captcha verification if the user creates an account by themself.
If you'd like to enable captcha verification, install a captcha support plugin, e.g. the Jenkins
<a href="https://wiki.jenkins-ci.org/display/JENKINS/JCaptcha+Plugin">JCaptcha Plugin</a>.
</div>

<div>
Par défaut, Jenkins permet aux utilisateurs de se créer un compte eux-mêmes, à l'aide du lien "S'inscrire"
en haut à droite de la page.
Mais si vous souhaitez éviter que n'importe puisse créer des comptes et si vous préférez contrôler précisément
comment les comptes utilisateurs sont créés, alors décochez cette option.

<p>
Quand la case est décochée, une personne possédant le rôle administrateur devra créer ces comptes.
</div>

war/src/main/webapp/help/shell/shellexe_fr.html

Files

shellexe.html

shellexe_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information	04.02.2013 00:16:10, no SCM information
<div> Normally you should just leave this field empty and let Jenkins pick up the right shell executable. If your <tt>sh</tt> (Windows) or <tt>/bin/sh</tt> binary exists outside your <tt>PATH</tt>, however, specify the absolute path to the shell executable. </div>	<div> En général, ce champ peut rester vide pour laisser Jenkins choisir le bon sh. Néanmoins, si votre binaire <tt>sh</tt> (Windows) ou <tt>/bin/sh</tt> est placé hors de votre <tt>PATH</tt>, spécifiez le chemin absolu vers l'exécutable sh. </div>

war/src/main/webapp/help/system-config/cvs-browser_fr.html

Files

cvs-browser.html

cvs-browser_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
<p>
Specifies paths of the CVS repository browser web application.
Setting these values allows Jenkins to generate links from changesets to those pages.
There are two different entries for each CVSROOT.

<dl>
<dt>URL</dt>
<dd>
URL of the page that displays details about a particular file
in the repository.
</dd>

<dt>Diff URL</dt>
<dd>
URL of the page that displays details about differences between two revisions.
</dd>
</dl>

<p>
The following macro characters are available.
<table>
<tr>
<td>%%P</td>
<td>Path name of the file under CVS, like "foo/bar/Zot.java"</td>
</tr>
<tr>
<td>%%r</td>
<td>Revision of the old version (for diff URLs)</td>
</tr>
<tr>
<td>%%r</td>
<td>Revision of the new version (for diff URLs)</td>
</tr>
</table>
</div>

<div>
<p>
Spécifie les chemins du l'application web qui sert de navigateur de repository CVS.
Ces valeurs permettent à Jenkins de générer des liens à partir des listes de changements
vers ces pages.
Il y a deux valeurs à fournir pour chaque CVSROOT.

<dl>
<dt>URL</dt>
<dd>
L'URL de la page qui affiche les détails d'un fichier particulier.
</dd>

<dt>Diff URL</dt>
<dd>
L'URL de la page qui affiche les détails des différences entre deux revisions.
</dd>
</dl>

<p>
Les caractères de macro suivants sont disponibles.
<table>
<tr>
<td>%%P</td>
<td>Chemin vers le fichier sous CVS, du type "foo/bar/Zot.java"</td>
</tr>
<tr>
<td>%%r</td>
<td>Numéro de révision de la version précédente (pour les Diff URLs)</td>
</tr>
<tr>
<td>%%r</td>
<td>Numéro de révision de la nouvelle version du fichier (pour les Diff URLs)</td>
</tr>
</table>
</div>

war/src/main/webapp/help/system-config/defaultJobNamingStrategy.html (Master)

Files

defaultJobNamingStrategy.html

globalEnvironmentVariables.html

MISSING

04.02.2013 00:16:10, no SCM information
<div> This is the default configuration and allows the user the choose any name he likes. </div>

war/src/main/webapp/help/system-config/globalEnvironmentVariables_fr.html

Files

globalEnvironmentVariables_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information	04.02.2013 00:16:10, no SCM information
<div> These key-value pairs apply for every build on every node. They can be used in Jenkins' configuration (as $key or ${key}) and will be added to the environment for processes launched from the build. </div>	<div> Ces paires clé-valeur s'appliquent à chaque build de chaque noeud. Elles peuvent être utilisées dans la configuration de Jenkins (avec $cle ou ${cle}) et seront ajoutées à l'environnement pour les processus lancés par le build. </div>

war/src/main/webapp/help/system-config/homeDirectory_fr.html

Files

homeDirectory.html

homeDirectory_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
Jenkins stores all the data files inside this directory in the file system.
You can change this by either:
<ol>
<li>
Using your web container's admin tool to set the <tt>JENKINS_HOME</tt>
environment entry.
<li>
Setting the environment variable <tt>JENKINS_HOME</tt> before launching
your web container.
<li>
(Not recommended) modifying web.xml in <tt>jenkins.war</tt> (or its expanded image
in your web container).
</ol>
This value cannot be changed while Jenkins is running.
This entry is mostly for you to make sure that your configuration is taking effect.
</div>

<div>
Jenkins place tous les fichiers de données dans ce répertoire du système de fichiers.
Vous pouvez changer cette valeur :
<ol>
<li>
Soit en utilisant l'outil d'administration de votre conteneur web pour
positionner la variable <tt>JENKINS_HOME</tt>.
<li>
Soit en positionnant la variable <tt>JENKINS_HOME</tt> avant de lancer
votre conteneur web.
<li>
Soit (non recommandé) en modifiant le fichier web.xml dans
<tt>jenkins.war</tt>
(ou sa version décompressée dans votre conteneur web).
</ol>
Cette valeur ne peut être changée quand Jenkins est lancé.
Elle a principalement pour but de vous permettre de
constater que votre configuration a bien été prise en compte.
</div>

war/src/main/webapp/help/system-config/master-slave/availability_fr.html

Files

availability.html

availability_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
Controls when Jenkins starts and stops the slave.

<dl>
<dt><b>
Keep this slave on-line as much as possible
</b></dt>
<dd>
This is the default and normal setting.
In this mode, Jenkins uses tries to keep the slave on-line.
If Jenkins can start the slave without user assistance, it will periodically
attempt to restart the slave if it is unavailable.
Jenkins will not take the slave off-line.
</dd>



<dt><b>
Take this slave on-line when in demand and off-line when idle
</b></dt>
<dd>
In this mode, if Jenkins can launch the slave without user assistance, it will periodically
attempt to launch the slave while there are unexecuted jobs which meet the following criteria:
<ul>
<li>They have been in the queue for at least the specified startup demand period</li>
<li>They can execute on this slave</li>
</ul>

The slave will be taken off-line if:
<ul>
<li>There are no active jobs running on the slave</li>
<li>The slave has been idle for at least the specified idle period</li>
</ul>
</dd>
</dl>
</div>

<div>
Contrôle le moment où Jenkins démarrage et arrête l'esclave.

<dl>
<dt><b>
Maintenir l'esclave activé le plus longtemps possible
</b></dt>
<dd>
C'est la configuration par défaut et la plus classique.
Dans ce mode, Jenkins fait des tests réguliers pour conserver l'esclave
actif.
Si Jenkins peut démarrer l'esclave sans l'aide de l'utilisateur et
que l'esclave n'est pas disponible,
il tentera régulièrement de le relancer.
Jenkins ne cherchera pas à le désactiver.
</dd>



<dt><b>
Activer l'esclave en cas nécessité et le désactiver lorsqu'il n'est plus nécessaire
</b></dt>
<dd>
Dans ce mode, si Jenkins peut démarrer l'esclave sans l'aide de l'utilisateur, il
cherchera régulièrement à l'activer tant qu'il y aura des jobs en attente
respectant les critères suivants :
<ul>
<li>Ils sont dans la file d'attente depuis au moins aussi longue que la période d'attente spécifiée</li>
<li>Ils peuvent s'exécuter sur cette machine</li>
</ul>

L'esclace sera désactivé si :
<ul>
<li>Il n'y a plus de job en cours sur cet esclave</li>
<li>L'esclave a été inactif depuis au moins la période d'inactivité spécifiée</li>
</ul>
</dd>
</dl>
</div>

war/src/main/webapp/help/system-config/master-slave/clock_fr.html

Files

clock.html

clock_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information	04.02.2013 00:16:10, no SCM information
<div> Many aspects of a build are sensitive to the clock, and therefore if the clock of the machine that Jenkins runs and that of the slave differ significantly, it can cause mysterious problems. Consider synchronizing clocks between machines by NTP. </div>	<div> De nombreux aspects d'un build dépendent de l'horloge. Par conséquent, si l'horloge de la machine qui exécute Jenkins et celle de la machine esclave sont très différentes, des comportements étranges peuvent se voir. Il est recommandé d'utiliser NTP pour synchroniser les horloges entre les machines. </div>

war/src/main/webapp/help/system-config/master-slave/demand/idleDelay_fr.html

Files

idleDelay.html

idleDelay_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information	04.02.2013 00:16:10, no SCM information
<div> The number of minutes that this slave must remain idle before taking it off-line. </div>	<div> Le nombre de minutes d'inactivité de cet esclave avant la tentative de déconnexion. </div>

war/src/main/webapp/help/system-config/master-slave/demand/inDemandDelay_fr.html

Files

inDemandDelay.html

inDemandDelay_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information	04.02.2013 00:16:10, no SCM information
<div> The number of minutes for which jobs must be waiting in the queue before attempting to launch this slave. </div>	<div> Le nombre de minutes que les jobs doivent attendre dans la file d'attente, avant la tentative d'activation de cet esclave. </div>

war/src/main/webapp/help/system-config/master-slave/description_fr.html

Files

nodeEnvironmentVariables.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
Optional human-readable description of this slave. This information
is displayed on the project configuration screen.

<p>
When you have slaves that are different from others, it's often helpful
to use this field to explain what is different. For example, entering
"Windows slave" in this field would allow project owners to choose to
always build on a Windows machine (for example, if they need some
Windows-specific build tool.)
</div>

<div>
Une description optionnelle de cet esclave, lisible pour un être humain.
Cette information est affichée sur l'écran de configuration du projet.

<p>
Quand vous avez des esclaves différents des autres, il est souvent
utile d'utiliser ce champ pour expliquer ces différences. Par exemple,
"Esclave Windows" permet aux propriétaires des projets de choisir de
toujours construire sur une machine Windows (typiquement, s'ils ont besoin
d'un outil spécifique sous Windows).
</div>

war/src/main/webapp/help/system-config/master-slave/jnlp-tunnel_fr.html

Files

jnlp-tunnel.html

jnlp-tunnel_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
When a slave is launched through JNLP, the slave agent attempts to connect to a specific TCP port of Jenkins
to establish a communication channel.
But some security sensitive network can prevent you from making this connection.
This can also happen when Jenkins runs behind a load balancer,
<a href="http://www.serverwatch.com/tutorials/article.php/3290851">apache reverse proxy</a>
into <a href="http://en.wikipedia.org/wiki/Demilitarized_zone_(computing)">DMZ</a>, and so on.

<p>
This tunneling option allows you to route this connection to another host/port, and useful for those situations.
The field can either take "<tt>HOST:PORT</tt>", "<tt>:PORT</tt>", or "<tt>HOST:</tt>". In the first format,
JNLP slave agent will connect to the given TCP port on the given host, and assume that you've configured your
network so that this port forwards the connection to Jenkins' JNLP slave TCP port.

<p>
In the latter two formats, the default host name and port number (that is, the host name that Jenkins runs,
and the TCP port that Jenkins opened) are used to augment the missing values. In particular the <tt>HOST:</tt> format
is useful if the HTTP reverse proxy is used and Jenkins actually runs on another system.
</div>

<div>
Quand un esclave est lancé par JNLP, l'agent de l'esclave tente de se connecter à Jenkins par un port
TCP spécifique, afin d'établir un canal de communication.
Certains réseaux très sécurisés peuvent vous empècher d'effectuer cette connexion.
Cela peut également être le cas quand Jenkins tourne derrière un répartiteur de charge (load balancer),
un <a href="http://www.serverwatch.com/tutorials/article.php/3290851">reverse proxy apache</a>
dans une <a href="http://en.wikipedia.org/wiki/Demilitarized_zone_(computing)">zone démilitarisée (DMZ)</a>, etc.

<p>
Cette option de tunneling vous permet, dans ces situations, de rediriger la connexion sur un autre host ou
un autre numéro de port. Le champ supporte les formats "<tt>HOST:PORT</tt>", "<tt>:PORT</tt>" et "<tt>HOST:</tt>".
Dans le premier format, l'agent JNLP de l'esclave se connectera sur le numéro de port TCP et le host spécifiés et
supposera que vous avez configuré votre réseau de façon à ce que ce port fasse suivre la connexion sur le
port TCP de l'esclave JNLP de Jenkins.

<p>
Dans les deux derniers formats, le nom de host et le numéro de port par défaut (c'est-à-dire le nom de host que
Jenkins utilise et le numéro de port que Jenkins a ouvert) sont utilisés pour compléter les valeurs manquantes.
En particulier, le format <tt>HOST:</tt> est utile si un reverse proxy HTTP est utilisé et que Jenkins tourne en fait sur
un autre système.
</div>

war/src/main/webapp/help/system-config/master-slave/jnlpSecurity_fr.html

Files

jnlpSecurity.html

jnlpSecurity_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
Controls how Jenkins permits launching via JNLP.

<dl>
<dt><b>
Launch only from Computer detail. Require Login if security enabled.
</b></dt>
<dd>
<em>This is the default and normal setting.</em>
In this mode, Jenkins provides the JNLP launch link on the computer view.
If Security is enabled, then the link will only be available to authenticated users.
</dd>

<dt><b>
Launch from front page. Require Login if security enabled.
</b></dt>
<dd>
In this mode, Jenkins provides the JNLP launch link on both the computer view and the Build Executor Status
sidepanel.
If Security is enabled, then the link will only be available to authenticated users.
</dd>

<dt><b>
Launch only from Computer detail. Login never required.
</b></dt>
<dd>
In this mode, Jenkins provides the JNLP launch link on the computer view.
The link will always be available whenever the slave is offline.
<br />
<b>WARNING!</b> In this mode security is disabled. Thus slaves can be started by <em>anyone
that can access this server</em>. Slaves have the ability to execute arbitrary code on the
master. <b>Do not select this option unless you are fully aware of the risks</b>
</dd>



</dl>
</div>

<div>
Contrôle comment Jenkins autorise les lancements par JNLP.

<dl>
<dt><b>
Lancement uniquement à partir des "Détails de l'ordinateur".
Un login est demandé si la sécurité est activée.
</b></dt>
<dd>
<em>Ceci est le comportement par défaut.</em>
Dans ce mode, Jenkins fournit le lien de lancement JNLP
sur la vue des détails de l'ordinateur. Si la sécurité est
activée, le lien ne sera disponible que pour les utilisateurs
identifiés.
</dd>

<dt><b>
Lancement à partir de la page d'accueil. Login demandé si la
sécurité est activée.
</b></dt>
<dd>
Dans ce mode, Jenkins fournit le lien de lancement JNLP
à la fois sur la vue de l'ordinateur et sur le panneau
du Lanceur de build sur le côté de la fenêtre. Si la
sécurité est activée, alors le lien ne sera disponible que
pour les utilisateurs identifiés.
</dd>

<dt><b>
Lancement seulement à partir des "Détails de l'ordinateur".
Un login n'est jamais demandé.
</b></dt>
<dd>
Dans ce mode, Jenkins fournit le lien de lancement JNLP
sur la vue de l'ordinateur. Le lien sera toujours disponible
quand la machine-esclave est déconnectée.
<br />
<b>Attention!</b> Dans ce modèle, la sécurité est désactivée.
Les esclaves peuvent donc être lancés par
<em>toutes les personnes qui ont accès au serveur</em>.
Les esclaves ont la capacité d'exécuter n'importe quel code
sur la machine maître.
<b>Ne sélectionnez pas cette option si vous n'avez pas
bien conscience des risques encourus.</b>
</dd>



</dl>
</div>

war/src/main/webapp/help/system-config/master-slave/numExecutors_fr.html

Files

numExecutors.html

numExecutors_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
This controls the number of concurrent builds that Jenkins can perform on this slave.
So the value affects the overall system load Jenkins may incur.
A good value to start with would be the number of processors.

<p>
Increasing this value beyond that would cause each build to take longer, but it could increase
the overall throughput, because it allows CPU to build one project while another build is waiting
for I/O.

<p>
Setting this value to 0 is useful to remove a disabled slave from Jenkins temporarily without
losing other configuration information.
</div>

<div>
Ceci contrôle le nombre de builds concurrents que Jenkins peut exécuter
sur cet esclave. La valeur affecte la charge système que Jenkins peut
causer. Une bonne valeur pour commencer serait le nombre de processeurs.

<p>
Augmenter cette valeur au-delà du nombre de processeurs peut rallonger
la durée individuelle des builds, mais aussi augmenter la capacité.
En effet, cela permet au processeur de construire un projet
pendant qu'un autre est en attente d'entrées/sorties.

<p>
Positionner cette valeur à 0 est utile pour désactiver un esclave
temporairement indisponible, sans perdre le reste de la configuration.
</div>

war/src/main/webapp/help/system-config/master-slave/usage_fr.html

Files

usage.html

usage_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
Controls how Jenkins schedules builds on this machine.

<dl>
<dt><b>
Utilize this slave as much as possible
</b></dt>
<dd>
This is the default and normal setting.
In this mode, Jenkins uses this slave freely. Whenever there is a build
that can be done by using this slave, Jenkins will use it.
</dd>

<dt><b>
Leave this machine for tied jobs only
</b></dt>
<dd>
In this mode, Jenkins will only build a project on this machine when
that project specifically has this slave as the "assigned node".

This allows a slave to be reserved for certain kinds of jobs.
For example, to run performance tests continuously from Jenkins,
you can use this setting with # of executors as 1, so that only one performance
test runs at any given time, and that one executor won't be blocked
by other builds that can be done on other slaves.
</dd>
</dl>
</div>

<div>
Contrôle comment Jenkins programme les builds sur cette machine.

<dl>
<dt><b>
Utilise cet esclave le plus possible
</b></dt>
<dd>
C'est l'option normale, configurée par défaut.
Dans ce mode, Jenkins utilise librement cet esclave. A chaque fois
qu'un build peut être exécuté sur cet esclave, Jenkins le fera.
</dd>

<dt><b>
Utilise cette machine seulement pour les jobs spécifiques à celle-ci
</b></dt>
<dd>
Dans ce mode, Jenkinsne construira un projet sur cette machine que
lorsque un projet aura été assigné spécifiquement à cet esclave.

Cela permet à un esclave de n'être utilisé que pour certains types
de jobs. Par exemple, pour lancer des tests de performance en
continu à partir de Jenkins, vous pouvez utiliser cette option
avec le nombre d'exécuteurs à 1, afin de ne lancer qu'un test de
performance à la fois. Cet exécuteur ne sera pas bloqué par les
autres builds qui peuvent être lancés sur les autres esclaves.
</dd>
</dl>
</div>

war/src/main/webapp/help/system-config/nodeEnvironmentVariables_fr.html

Files

nodeEnvironmentVariables_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information	04.02.2013 00:16:10, no SCM information
<div> These key-value pairs apply for every build on this node and override any global values. They can be used in Jenkins' configuration (as $key or ${key}) and be will added to the environment for processes launched from the build. </div>	<div> Ces paires clé-valeur s'appliquent à chaque build de ce noeud et prennent la place d'éventuelles valeurs globales. Elles peuvent être utilisées dans la configuration de Jenkins (avec $cle or ${cle}) et seront ajoutées à l'environnement pour les processus lancés par le build. </div>

war/src/main/webapp/help/system-config/patternJobNamingStrategy.html (Master)

Files

patternJobNamingStrategy.html

MISSING

04.02.2013 00:16:10, no SCM information

<div>
Define a pattern (regular expression) to check whether the job name is valid or not.
<p>
Forcing the check on existing jobs, will allow you to enforce a naming convention on existing jobs - e.g. even if the user does not change the name,
it will be validated with the given pattern at every submit and no updates can be made until the name confirms.<br>
<i>This option does not affect the execution of jobs with non-compliant names.
It just controls the validation process when saving job configurations.</i>
</div>

war/src/main/webapp/help/system-config/quietPeriod_fr.html

Files

quietPeriod.html

quietPeriod_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information	04.02.2013 00:16:10, no SCM information
<div> <p> When set to >0, a newly scheduled build waits for this many seconds before actually being built. This is useful for collapsing multiple CVS change notification e-mails into one. </div>	<div> Avec une valeur > 0, lorsqu'un build est programmé, il attend le nombre de secondes indiqué avant de vraiment commencer son exécution. Utile pour rassembler les emails de multiples changements CVS dans un seul. </div>

war/src/main/webapp/help/system-config/systemMessage_fr.html

Files

systemMessage.html

systemMessage_fr.html

OUTDATED

18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:10, no SCM information
<div> This message will be displayed on <a href=".">the top page</a>. Useful for posting a system-wide notification to users. Can contain HTML tags or whatever markup language is defined for the system. </div>	<div> Ce message sera affiché sur la <a href=".">page principale</a>. Utile pour afficher des informations relatives à tout le système à l'ensemble des utilisateurs. Peut contenir des tags HTML. </div>
(old value)

war/src/main/webapp/help/tasks/aggregate-test/auto-aggregate_fr.html

Files

auto-aggregate.html

auto-aggregate_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
When checked, Jenkins simply aggregates tests from
all the transitive downstream jobs of this project. This is convenient
as you don't have to individually list them and keep them up to date
as you add/remove jobs. This normally works just fine, as your test
jobs are normally set up as downstream jobs of the build job.

<p>
If for some reasons the auto aggregation doesn't work, you can always
manually specify a list of jobs to be aggregated.
</div>

<div>
Quand cette case est cochée, Jenkins aggrège simplement les tests des
jobs transitifs en aval pour ce projet. Cela est commode, car nous n'avez
pas à les lister individuellement et garder cette liste à jour quand vous
ajoutez ou supprimez des jobs. Généralement, cela suffit, du moment que vos
jobs de test sont configurés comme des jobs en aval du job de build principal.

<p>
Si par extraordinaire l'aggrégation automatique ne marche pas, vous pouvez
toujours spéficier manuellement une liste de jobs à aggréger.
</div>

war/src/main/webapp/help/tasks/aggregate-test/help_fr.html

Files

sendToindividuals_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
Because tests often dominates the execution time, a Jenkins best practice
involves splitting test executions into different jobs, possibly in multiple
different jobs.

<p>
When you do that, setting test aggregation is a convenient way of
collecting all the
test results from such downstream test jobs and display it along with the
build that they are testing. In this way, people can see the overall test
status of the given build quickly.
</div>

<div>
Parce que les tests prennent la majeure partie du temps d'exécution, une
bonne pratique Jenkins consiste à séparer l'exécution des tests dans des
jobs différents, voire de multiples jobs.

<p>
Si vous faites ainsi, demander l'aggrégation des tests est une manière
pratique de collecter les résultats des tests provenant de jobs en aval
et de les afficher avec le build qu'ils ont testé. De cette façon, les
utilisateurs peuvent voir rapidement le statut général des tests d'un
build donné.
</div>

war/src/main/webapp/help/tasks/aggregate-test/manual-list_fr.html

Files

manual-list.html

manual-list_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information	04.02.2013 00:16:10, no SCM information
<div> Specify a list of job names manually here. Multiple names can be separated by comma, like "<tt>foo, bar</tt>" </div>	<div> Indiquez ici manuellement la liste des jobs. De multiples noms peuvent être séparés par une virgule, par exemple "<tt>foo, bar</tt>". </div>

war/src/main/webapp/help/tasks/fingerprint/keepDependencies_fr.html

Files

keepDependencies.html

keepDependencies_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
If this option is enabled, all of <a href="lastSuccessfulBuild/fingerprint">
the builds that are referenced</a> from builds of this project (via fingerprint)
will be protected from log rotation.

<p>
When your job depends on other jobs on Jenkins and you occasionally need
to tag your workspace, it's often convenient/necessary to also tag your
dependencies on Jenkins. The problem is that the log rotation could
interfere with this, since the build your project is using might already be
log rotated (if there have been a lot of builds in your dependency), and
if that happens you won't be able to reliably tag your dependencies.

<p>
This feature fixes that problem by "locking" those builds that you depend on,
thereby guaranteeing that you can always tag your complete dependencies.
</div>

<div>
Si cette option est activée tous les
<a href="lastSuccessfulBuild/fingerprint">builds référencés</a> par les
builds de ce projet (à travers les empreintes digitales) seront protégés
lors de la rotation des log.

<p>
Quand votre job dépend d'autres jobs sur Jenkins et que vous avez
occasionnellement besoin de tagguer votre workspace, il est souvent
pratique (voire nécessaire) de tagguer aussi vos dépendances sur Jenkins.
Le problème est que la rotation du log peut avoir des effets néfastes,
puisqu'un build utilisé par votre projet pourra être affecté par un
nettoyage suite aux rotations des logs (s'il y a eu beaucoup de builds
dans cette dépendance). Si cela arrive, vous ne pourrez plus tagguer
vos dépendances de façon fiable.

<p>
Cette fonctionnalité règle ce problème en "lockant" ceux de ces builds
dont vous dépendez, garantissant ainsi que vous pourrez toujours tagguer
toutes vos dépendances.
</div>

war/src/main/webapp/help/tasks/junit/report_fr.html

Files

report.html

report_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
Jenkins understands the JUnit test report XML format (which is also used by TestNG).
When this option is configured, Jenkins can provide useful information about test results,
such as historical test result trends, a web UI for viewing test reports, tracking failures,
and so on.

<p>
To use this feature, first set up your build to run tests, then
specify the path to JUnit XML files in the
<a href="http://ant.apache.org/manual/Types/fileset.html">Ant glob syntax</a>,
such as <tt>**/build/test-reports/*.xml</tt>. Be sure not to include any non-report
files into this pattern. You can specify multiple patterns of files separated by commas.

<p>
Once there are a few builds running with test results, you should start seeing
something like <a href="https://wiki.jenkins-ci.org/display/JENKINS/JUnit+graph">this</a>.
</div>

<div>
Jenkins comprend le format XML des rapports de test JUnit (qui est le
même pour ceux de TestNG).
Quand cette option est configurée, Jenkins peut fournir des informations
utiles sur les résultats des tests, tels que les tendances historiques
sur les résultats des tests, une interface web pour visualiser les rapports
de test, tracer les échecs, etc.

<p>
Pour utiliser cette fonctionnalité, tout d'abord configurez votre build
pour lancer des tests, puis spéficiez le chemin vers les fichiers XML
JUnit en utilisant
<a href="http://ant.apache.org/manual/Types/fileset.html">
la syntaxe classique de Ant</a>, par exemple
<tt>**/build/test-reports/*.xml</tt>.
Assurez-vous de ne pas inclure des fichiers qui ne contiennent pas de
rapports dans ce pattern.

<p>
Une fois que des builds produisent des résultats de test, vous devriez
commencer à voir quelque chose
<a href="https://wiki.jenkins-ci.org/display/JENKINS/JUnit+graph">comme ça</a>.
</div>

war/src/main/webapp/help/tasks/mailer/sendToindividuals_fr.html

Files

sendToindividuals.html

CURRENT

04.02.2013 00:16:10, no SCM information

<div>
If this option is checked, the notification e-mail will be sent to individuals who have
committed changes for the broken build (by assuming that those changes broke the build).
<p>
If e-mail addresses are also specified in the recipient list, then both the individuals
as well as the specified addresses get the notification e-mail. If the recipient list
is empty, then only the individuals will receive e-mails.
</div>

<div>
Si cette option est choisie, les notifications par email seront envoyées
aux personnes qui ont fait des modifications dans un build en échec
(on suppose que ces changements ont cassé ce build).
<p>
Si des adresses email sont aussi spécifiées sur la liste des destinataires,
alors l'email de notification est envoyé à la fois à cette liste et aux
personnes ayant fait des modifications.
Si la liste des destinataires est vide, alors seules les personnes
changeurs recevront des emails.
</div>

war/src/main/webapp/help/tasks/mailer/smtpAuth_fr.html

Files

smtpAuth.html

smtpAuth_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information	04.02.2013 00:16:10, no SCM information
<div> Use SMTP authentication when sending out e-mails. If your environment requires the use of SMTP authentication, specify its user name and the password here. </div>	<div> Cette option provoque l'authentification SMTP lors de l'envoi d'emails. Si votre environnement nécessite l'utilisation de l'authentification SMTP, spécifiez ici son nom d'utilisateur et mot de passe. </div>

war/src/main/webapp/help/tasks/maven/properties_fr.html

Files

properties.html

properties_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information	04.02.2013 00:16:10, no SCM information
<div> Properties needed by your Maven build can be specified here (in the standard properties file format): <pre># comment name1=value1 name2=value2 </pre> These are passed to Maven like <tt>"-Dname1=value1 -Dname2=value2"</tt> </div>	<div> Les propriétés nécessaires pour votre build Maven peuvent être spécifiées ici (avec le format standard des fichiers de propriétés): <pre># commentaire nom1=valeur1 nom2=valeur2 </pre> Ces propriétés sont passées à Maven ainsi: <tt>"-Dnom1=valeur1 -Dnom2=valeur2"</tt> </div>

war/src/main/webapp/help/tools/help-label.html (Master)

Files

help-label.html

tool-location-node-property.html

MISSING

29.08.2013 16:34:29, no SCM information
<div> Optional label to restrict the use of this installation method. This label could be a Label Expression (for example : "linux&&x64" or "windows&&x86"). Only nodes which validate this label (or label expression) will be considered. </div>

war/src/main/webapp/help/tools/tool-location-node-property_fr.html

Files

tool-location-node-property_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information	04.02.2013 00:16:10, no SCM information
<div> You can specify the location of certain tools on this node, overriding the global configuration. (You may prefer to use automatic tool installers instead, removing the need to configure each node separately.) </div>	<div> Vous pouvez spécifier l'endroit où se trouvent certains outils sur ce noeud. Cela remplacera la configuration globale. </div>

war/src/main/webapp/help/user/description_fr.html

Files

OUTDATED

18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:10, no SCM information
<div> This description is placed on the user top page so that visitors can know who you are. You can use any HTML tags (or markup in the configured language) here. Consider putting some links to other pages related to you. </div>	<div> Cette description est placée sur la page principale de l'utilisateur, afin que les visiteurs puissent vous connaitre. Vous pouvez utiliser des tags HTML. N'hésitez pas à ajouter des liens vers d'autres pages vous concernant. </div>
(old value)

war/src/main/webapp/help/user/fullName_fr.html

Files

fullName.html

fullName_fr.html

CURRENT

04.02.2013 00:16:10, no SCM information	04.02.2013 00:16:10, no SCM information
<div> Specify your name in a more human friendly format, so that people can see your real name as opposed to your ID. For example, "Jane Doe" is usually easier for people to understand than IDs like "jd513". </div>	<div> Indiquez votre nom dans un format lisible pour un humain. Les visiteurs verront votre vrai nom à côté de votre identifiant. "Jean Dupont" est plus facile à retenir que "jd513"... </div>

war/src/main/webapp/help/view-config/description_fr.html

Files

OUTDATED

18.05.2013 17:17:16, no SCM information	04.02.2013 00:16:11, no SCM information
<div> This message will be displayed on <a href=".">the view page</a>. Useful for describing what this view is about, or linking to relevant resources. Can contain HTML tags or whatever markup language is defined for the system. </div>	<div> Ce message s'affichera sur la <a href=".">page de visualisation</a>. Utile pour décrire l'objectif de cette vue ou pour donner des liens vers des ressources supplémentaires. Supporte les tags HTML. </div>
(old value)

war/src/main/webapp/help/view-config/filter-executors.html (Master)

Files

filter-executors.html

MISSING

04.02.2013 00:16:11, no SCM information

<div>
If checked, only those build executors will be shown that could execute the jobs in this view.
</div>

war/src/main/webapp/help/view-config/filter-queue.html (Master)

Files

filter-queue.html

MISSING

04.02.2013 00:16:11, no SCM information

<div>
If checked, only jobs in this view will be shown in the queue.
</div>

war/src/main/webapp/help/view-config/includeregex_fr.html

Files

includeregex.html

includeregex_fr.html

CURRENT

04.02.2013 00:16:11, no SCM information	04.02.2013 00:16:11, no SCM information
<div> If configured, the regular expression will be applied to all job names. Those that match the regular expression will be shown in this view. Tip: to <em>exclude</em> certain patterns, use negative lookahead. For example, to display all jobs not named <samp>test<i>something</i></samp>, use: <samp>(?!test.).</samp> </div>	<div> Quand cette option est activée, l'expression régulière sera appliquée à tous les noms des jobs. Ceux qui y correspondent seront affichés dans cette vue. </div>

war/src/main/webapp/help/view-config/statusFilter.html (Master)

Files

statusFilter.html