Provides functionality for tracking status and other aspects pertaining to PDS products that are not captured in the Registry Service.
The documentation for the latest release of the Tracking Service, including release notes, installation and operation of the software are online at https://nasa-pds.github.io/tracking-service/.
If you would like to get the latest documentation, including any updates since the last release, you can execute the "mvn site:run" command and view the documentation locally at http://localhost:8080.
The software can be compiled and built with the "mvn compile" command but in order to create the JAR file, you must execute the "mvn compile jar:jar" command.
In order to create a complete distribution package, execute the following commands:
% mvn site
% mvn package
A release candidate should be created after the community has determined that a release should occur. These steps should be followed when generating a release candidate and when completing the release.
git clone git@github.com:NASA-PDS/tracking-service.git
For internal JPL use, the ConMan software package can be used for releasing software, otherwise the following sections outline how to complete these steps manually.
Update pom.xml for the release version or use the Maven Versions Plugin, e.g.:
# Skip this step if this is a RELEASE CANDIDATE, we will deploy as SNAPSHOT version for testing
VERSION=1.15.0
mvn versions:set -DnewVersion=$VERSION
git add pom.xml
Build and Publish Software to Sonatype Maven Repo.
# For operational release
mvn clean site deploy -P release
# For release candidate
mvn clean site deploy
Note: If you have issues with GPG, be sure to make sure you've created your GPG key, sent to server, and have the following in your ~/.m2/settings.xml:
<profiles>
<profile>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<properties>
<gpg.executable>gpg</gpg.executable>
<gpg.keyname>KEY_NAME</gpg.keyname>
<gpg.passphrase>KEY_PASSPHRASE</gpg.passphrase>
</properties>
</profile>
</profiles>
# For Release Candidate, you may need to delete old SNAPSHOT tag
git push origin :$VERSION
# Now tag and push
git tag ${VERSION}
git push --tags
From cloned repo:
git checkout gh-pages
# Create specific version site
mkdir -p $VERSION
# Copy the over to version-specific and default sites
rsync -av target/site/ $VERSION
rsync -av $VERSION/* .
git add .
# For operational release
git commit -m "Deploy $VERSION docs"
git push origin gh-pages
Update pom.xml with the next SNAPSHOT version either manually or using Github Versions Plugin.
For RELEASE CANDIDATE, ignore this step.
git checkout master
# For release candidates, skip to push changes to master
VERSION=1.16.0-SNAPSHOT
mvn versions:set -DnewVersion=$VERSION
git add pom.xml
git commit -m "Update version for $VERSION development"
# Push changes to master
git push -u origin master
Currently the process to create more formal release notes and attach Assets is done manually through the Github UI but should eventually be automated via script.
NOTE: Be sure to add the tar.gz and zip from the target/ directory to the release assets, and use the CHANGELOG generated above to create the RELEASE NOTES.
Deploy software to Sonatype SNAPSHOTS Maven repo:
# Operational release
mvn clean site deploy
https://search.maven.org/search?q=g:gov.nasa.pds%20AND%20a:tracking-service&core=gav
https://oss.sonatype.org/content/repositories/snapshots/gov/nasa/pds/tracking-service/
If you want to access snapshots, add the following to your ~/.m2/settings.xml:
<profiles>
<profile>
<id>allow-snapshots</id>
<activation><activeByDefault>true</activeByDefault></activation>
<repositories>
<repository>
<id>snapshots-repo</id>
<url>https://oss.sonatype.org/content/repositories/snapshots</url>
<releases><enabled>false</enabled></releases>
<snapshots><enabled>true</enabled></snapshots>
</repository>
</repositories>
</profile>
</profiles>
docker build --network=host -t tracking_service:$(git rev-parse HEAD) -f Dockerfile.local .
docker build --build-arg VERSION=${VERSION} --network=host -t tracking_service:${VERSION} - < Dockerfile.release
The image is built to run tracking within tomcat. To verify the build and run the equivalent of mvn site:run as describe above, add /tmp/run.sh to the end of the docker run command.
All of the run examples below use the host network for simplicity but this can be very insecure. These are just simple examples are not intented to be how to securely run an exposed service. Use the appropriate network in your operations to meet your security needs.
Lastly, using the --expose (-p) switch of docker run, the 8080 port can be moved without having to rebuild the container.
docker run --rm --expose 8080:8080 tracking_service:$(git rev-parse HEAD)
docker run --rm --expose 8080:8080 tracking_service:${VERSION}