[
https://issues.apache.org/jira/browse/SLING-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15588624#comment-15588624
]
Bertrand Delacretaz commented on SLING-6103:
--------------------------------------------
The build passed now at
https://builds.apache.org/view/S-Z/view/Sling-Dashboard/job/sling-contrib-crankstart-launcher-1.8/9/
after changing the build's "goals and options" settings to
{code}
-U clean verify
-Dorg.ops4j.pax.url.mvn.repositories=http://repo.maven.apache.org/maven2@id=apache-releases,http://repository.apache.org/content/groups/snapshots-group@snapshots@noreleases@id=apache-snapshots
{code}
[~rombert] how do we make those job-specific settings permanent? I suppose we
need to modify {{tooling/jenkins/create_jobs.groovy}} to add an optional
per-job variable ("extraGoals" ?) for these settings?
> crankstart-launcher ITs fail when executed in isolation (on Jenkins)
> --------------------------------------------------------------------
>
> Key: SLING-6103
> URL: https://issues.apache.org/jira/browse/SLING-6103
> Project: Sling
> Issue Type: Bug
> Components: Crankstart
> Reporter: Robert Munteanu
> Assignee: Bertrand Delacretaz
> Labels: sling-IT
>
> When building on Jenkins SNAPSHOT dependencies can't be found. I assume that
> this is because they haven't been installed in the local repository and the
> IT does not look in the apache snapshots repository.
> In that case, it should be similar to SLING-6080 and SLING-6074.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
