Difference between revisions of "Global Configuration Files"

From Lingoport Wiki
Jump to: navigation, search
(config_custom_tasks.xml)
(config_attask.properties)
Line 28: Line 28:
 
== config_attask.properties ==
 
== config_attask.properties ==
   
Configuration file for creating an AtTask (Workfront) project that corresponds with a prep kit. This file can exist at the project level, group level and global level.
+
Configuration file for creating an AtTask (Workfront) project that corresponds with a prep kit.
   
 
Each task under the AtTask project will correspond to one locale in the prep kit. A document listing the changed keys will be uploaded for each task.
 
Each task under the AtTask project will correspond to one locale in the prep kit. A document listing the changed keys will be uploaded for each task.
   
 
A template as well as a URL may be attached to each task if configured.
 
A template as well as a URL may be attached to each task if configured.
  +
  +
This file can exist at the project level, group level and global level.
   
 
== config_custom_tasks.xml ==
 
== config_custom_tasks.xml ==

Revision as of 21:20, 27 April 2016

Global File Structure

The global configuration files are located in config directory under the L10n Streamlining directory (typically ~jenkins/Lingoport_Data/L10nStreamlining)

<L10nStreamlining>
├── config
│   ├── config_attask.properties
│   ├── config_custom_tasks.xml
│   ├── config_email_global.xml
│   ├── config_file_cherry_picker.xml
│   ├── config_lingotek_api.properties
│   ├── config_lingotek_file_format.properties
│   ├── sonar-project-template.properties
│   
├── <group_name>
│   ├── config
│       ...
│   
└── projects
    └── <project 1>
        ├── config
        ...

Most of the global config files contain information that is consistent throughout all groups and projects.

config_attask.properties

Configuration file for creating an AtTask (Workfront) project that corresponds with a prep kit.

Each task under the AtTask project will correspond to one locale in the prep kit. A document listing the changed keys will be uploaded for each task.

A template as well as a URL may be attached to each task if configured.

This file can exist at the project level, group level and global level.

config_custom_tasks.xml

Configuration file for custom tasks.

This file can exist at the project level, group level and global level.

config_email_global.xml

config_file_cherry_picker.xml

This is a template file to be copied under the project config directory if needed.

It helps special situations where files to be sent for translation are far and few and possibly locale dependent. This should be used with care.

config_lingotek_api.properties

config_lingotek_file_format.properties

sonar-project-template.properties