Started by an SCM change
[EnvInject] - Loading node environment variables.
Building on master in workspace /var/lib/jenkins/jobs/afp-repo/workspace
[workspace] $ hg showconfig paths.default
[workspace] $ hg pull --rev default
pulling from https://bitbucket.org/isa-afp/afp-devel/
no changes found
[workspace] $ hg update --clean --rev default
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
[workspace] $ hg log --rev . --template {node}
[workspace] $ hg log --rev . --template {rev}
[workspace] $ hg log --rev 937445d525d561387502f5f6027d08146e42059f
changeset:   6540:937445d525d5
user:        wenzelm
date:        Sun Apr 24 12:04:55 2016 +0200
summary:     removed (outdated) generated file;

[workspace] $ hg log --template "<changeset node='{node}' author='{author|xmlescape}' rev='{rev}' date='{date}'><msg>{desc|xmlescape}</msg><added>{file_adds|stringify|xmlescape}</added><deleted>{file_dels|stringify|xmlescape}</deleted><files>{files|stringify|xmlescape}</files><parents>{parents}</parents></changeset>\n" --rev default:0 --follow --prune 937445d525d561387502f5f6027d08146e42059f --encoding UTF-8 --encodingmode replace
    >> Job status: [afp-repo-afp] the 'build only if scm changes' feature is disabled.
Starting build job afp-repo-afp.
Finished Build : #173 of Job : afp-repo-afp with status : SUCCESS
Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
Finished: SUCCESS