[
https://issues.jboss.org/browse/JBIDE-22689?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-22689:
------------------------------------
The latest Neon-based staging build update site for JBT aggregate:
http://download.jboss.org/jbosstools/neon/staging/updates/
for JBDS:
https://devstudio.redhat.com/10.0/staging/updates/
OTOH, we could set a default URL for the components based on the project's github
project name, if that can be computed within Maven, eg., for jbosstools-server, use
${jbosstools-server-site}
(
https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... )
Then we'd be comparing against the latest CI build, rather than the latest STAGING
build. Would also need support for a fallback (skip test & pass the check) when
there's no baseline URL to check, as this introduces a circular dependency in that we
can't build the snapshot until the staging site exists, and we need to aggregate the
snapshots to produce the staging site.
enable baselineRepositories check to ensure timestamps increment for
meta-changes too
-------------------------------------------------------------------------------------
Key: JBIDE-22689
URL:
https://issues.jboss.org/browse/JBIDE-22689
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: build
Affects Versions: 4.4.1.AM1
Reporter: Nick Boldt
Assignee: Mickael Istria
Fix For: 4.4.1.AM2
To make sure to report a problem if we need to upversion for a meta-change (eg., build
configuration) and there's no accompanying new commit to force the timestamp to
increment:
From
https://wiki.eclipse.org/Tycho/Reproducible_Version_Qualifiers
{code:xml}
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-p2-plugin</artifactId>
<version>${tycho.version}</version>
<configuration>
<baselineRepositories>
<repository>
<url>[some url]</url>
</repository>
</baselineRepositories>
</configuration>
</plugin>
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)