Wiki

string
the url of the application homepage
A special build parameter is used by Packager to associate a Hudson job build with its own versions.
Name
Type
Description
packager_token
string
Used to match a CakePHP version to a Hudson Job/Build. See below.
Matching Cake Version to Hudson Build:
- Packager passes a unique ID as build parameter "packager_token" in the call to start a new Hudson build.
- The Hudson job's build script makes a HTTP POST callback to Packagerwith the packager_token, Hudson job name, and Hudsonbuild number.
-Packager now knows which build number on Hudson corresponds to its Version.
Hudson Build Status:
- Packagerpolls Hudson to find out latest build status of all jobs. This can be set up as a cron job every few seconds, minutes, etc.
- Packager can figureout how to download the artifact when a build is successful.
Hudson Build Notification
Update- Update the Version to reflect build status and artifact filename
If
- If version was based on a synch, and if the build was successful, then update the Appcast feed

Description
source_type
stringchoice
official, zip, git
source_official_tag
guid
string
is {9F661F94-F17F-4F5C-B1C8-2955C85C8FE9} 9F661F94-F17F-4F5C-B1C8-2955C85C8FE9
support_url
string

Description
source_type
stringchoice
official, zip, git
source_official_tag
guid
string
is {9F661F94-F17F-4F5C-B1C8-2955C85C8FE9} 9F661F94-F17F-4F5C-B1C8-2955C85C8FE9
support_url
string

Publish artifacts to SCP repository (=Packager server)
Call Packager Hudson controller to notify the build is done. Tell it the brand name, version ID, status, and artifact filename
Build Parameters
Parameters for the build's custom options are passed using an HTTP POST request.
Example Hudson Build using a file parameter (name=test.txt&file=...) and a string parameter (name=foo&value=bar)
<form name="parameters" action="/job/Test/build?delay=0sec" method="post">
<input name="Submit" value="Build" type="submit" />
</form>
The parameters for Packager are:
Name
Type
Description
source_type
string
official, zip, git
source_official_tag
string
the git tag name on the official Pandion repository
source_zip_file
file
Client.zip
source_git_url
string
the url of the git repository
custom_brand_xml
file
brand.xml
custom_default_xml
file
default.xml
logo_about
file
logo_about.png
logo_ico
file
logo_ico.ico
logo_png
file
logo_png.png
logo_signin
file
logo_signin.png
version_major
string
X.y.z
version_minor
string
x.Y.z
version_build
string
x.y.Z
name
string
display name of the brand
name_safe
string
name used for files and directories, cannot include / : * ? " < > |
homepage_url
string
the url of the application homepage
company
string
the name of the application owner organization
guid
string
unique identifier used by Windows Installer for upgrades, default for Pandion IM is {9F661F94-F17F-4F5C-B1C8-2955C85C8FE9}
support_url
string
the url of an online support resource like documentation or user training guide
info_url
string
the url of the application homepage
Hudson Build Notification
Update the Version to reflect build status and artifact filename

Publish artifacts to SCP repository (=Packager server)
Call Packager Hudson controller to notify the build is done. Tell it the brand name, version ID, status, and artifact filename
Build Parameters
Parameters for the build's custom options are passed using an HTTP POST request.
Example Hudson Build using a file parameter (name=test.txt&file=...) and a string parameter (name=foo&value=bar)
<form name="parameters" action="/job/Test/build?delay=0sec" method="post">
<input name="Submit" value="Build" type="submit" />
</form>
The parameters for Packager are:
Name
Type
Description
source_type
string
official, zip, git
source_official_tag
string
the git tag name on the official Pandion repository
source_zip_file
file
Client.zip
source_git_url
string
the url of the git repository
custom_brand_xml
file
brand.xml
custom_default_xml
file
default.xml
logo_about
file
logo_about.png
logo_ico
file
logo_ico.ico
logo_png
file
logo_png.png
logo_signin
file
logo_signin.png
version_major
string
X.y.z
version_minor
string
x.Y.z
version_build
string
x.y.Z
name
string
display name of the brand
name_safe
string
name used for files and directories, cannot include / : * ? " < > |
homepage_url
string
the url of the application homepage
company
string
the name of the application owner organization
guid
string
unique identifier used by Windows Installer for upgrades, default for Pandion IM is {9F661F94-F17F-4F5C-B1C8-2955C85C8FE9}
support_url
string
the url of an online support resource like documentation or user training guide
info_url
string
the url of the application homepage
Hudson Build Notification
Update the Version to reflect build status and artifact filename

<input name="Submit" value="Build" type="submit" />
</form>
Hudson Build Notification
Update the Version to reflect build status and artifact filename
If version was based on a synch, and if the build was successful, then update the Appcast feed

<input name="Submit" value="Build" type="submit" />
</form>
Hudson Build Notification
Update the Version to reflect build status and artifact filename
If version was based on a synch, and if the build was successful, then update the Appcast feed

If the version was published in an appcasting track, remove it from the track and update the appcast feed
Return to Version Archive and show success notification
Custom Building
Building a Version
User enters Add Version form and presses Build (submit) button
Server creates new Version object and stores all properties and status of "Build in Progress"
User sees Version Archive page
Hudson controller checks if a job by this Brand name already exists on the Hudson build server (Hudson HTTP API)
If not, create the job by cloning the BrandMaster job (/createItem with POST data: name=Goliath&mode=copy&from=BrandMaster)
Hudson controller runs a parametrized build of the job, supplying all necessary data to Hudson via HTTP API POST form. (/job/Goliath/buildWithParameters)
Hudson BrandMaster job
Pre build:
Checkout official Pandion IM git repository
Build:
Depending on Source Code origin option:
Nothing
Replace Client subdirectory with extracted custom ZIP archive
Clone custom git repo and replace the official Client subdir with the custom Client subdir
Replace Client settings files
Replace Client and Host branded icon files
(Put the needed Extras in place?)
Set VERSION_MAJOR, VERSION_MINOR, BUILD_NUMBER, and other build_config.bat options
Run build_host.bat
Run build_msi.bat
Post build:
Clean up the file parameters
Archive the artifacts
Publish artifacts to SCP repository (=Packager server)
Call Packager Hudson controller to notify the build is done. Tell it the brand name, version ID, status, and artifact filename
Example Hudson Build using a file parameter (name=test.txt&file=...) and a string parameter (name=foo&value=bar)
<form name="parameters" action="/job/Test/build?delay=0sec" method="post">
<input name="name" value="test.txt" type="hidden" />
<input name="file" type="file" />
<input name="name" value="foo" type="hidden" />
<input name="value" value="bar" type="text" />
<input name="Submit" value="Build" type="submit" />
</form>

If the version was published in an appcasting track, remove it from the track and update the appcast feed
Return to Version Archive and show success notification
Custom Building
Building a Version
User enters Add Version form and presses Build (submit) button
Server creates new Version object and stores all properties and status of "Build in Progress"
User sees Version Archive page
Hudson controller checks if a job by this Brand name already exists on the Hudson build server (Hudson HTTP API)
If not, create the job by cloning the BrandMaster job (/createItem with POST data: name=Goliath&mode=copy&from=BrandMaster)
Hudson controller runs a parametrized build of the job, supplying all necessary data to Hudson via HTTP API POST form. (/job/Goliath/buildWithParameters)
Hudson BrandMaster job
Pre build:
Checkout official Pandion IM git repository
Build:
Depending on Source Code origin option:
Nothing
Replace Client subdirectory with extracted custom ZIP archive
Clone custom git repo and replace the official Client subdir with the custom Client subdir
Replace Client settings files
Replace Client and Host branded icon files
(Put the needed Extras in place?)
Set VERSION_MAJOR, VERSION_MINOR, BUILD_NUMBER, and other build_config.bat options
Run build_host.bat
Run build_msi.bat
Post build:
Clean up the file parameters
Archive the artifacts
Publish artifacts to SCP repository (=Packager server)
Call Packager Hudson controller to notify the build is done. Tell it the brand name, version ID, status, and artifact filename
Example Hudson Build using a file parameter (name=test.txt&file=...) and a string parameter (name=foo&value=bar)
<form name="parameters" action="/job/Test/build?delay=0sec" method="post">
<input name="name" value="test.txt" type="hidden" />
<input name="file" type="file" />
<input name="name" value="foo" type="hidden" />
<input name="value" value="bar" type="text" />
<input name="Submit" value="Build" type="submit" />
</form>

API callback from payment processor tells Packager to store the new plan in the User object
Send changed plan notice via email to the use
Disable the Hudson job for the brand (Hudson HTTP API)
Signed In Without Active Subscription
Show brand name in header as disabled/faded

API callback from payment processor tells Packager to store the new plan in the User object
Send changed plan notice via email to the use
Disable the Hudson job for the brand (Hudson HTTP API)
Signed In Without Active Subscription
Show brand name in header as disabled/faded