Creating the Run Tile

The run tile defines a few key properties: where to find the bootstrap resources, how we name run resources, who is responsible for the domains.

pom.xml
tile.xml
Jenkinsfile

Declare the project#

pom.xml

<?xml version="1.0" encoding="UTF-8"?>
<project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"
  xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <modelVersion>4.0.0</modelVersion>

  <parent>
    <groupId>io.practiv.stable.anvil</groupId>
    <artifactId>anvil-parent</artifactId>
    <version>#{anvil-parent.version}</version>
  </parent>

  <groupId>io.practiv.stable.anvil</groupId>
  <artifactId>anvil-tile-run</artifactId>
  <version>1.999-SNAPSHOT</version>
  <packaging>tile</packaging>

  <name>${project.artifactId}</name>
  <description>Build environment for Practiv</description>

</project>

Tile.xml#

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">

  <distributionManagement>
    <repository>
      <id>branchout-maven-upload</id>
      <name>Releases</name>
      <url>${uploadMavenRepository}</url>
    </repository>
  </distributionManagement>

  <properties>
    <environmentDockerRegistry>docker.build.forge.practiv.io</environmentDockerRegistry>
    <globalDockerRegistry>[globalDockerRegistry]</globalDockerRegistry>
    <branchoutRunName>forge</branchoutRunName>
    <environmentSwitch>${environment}</environmentSwitch>
    <darkEnvironment>${environment}</darkEnvironment>
    <letsEncryptEmail>systems@practiv.com</letsEncryptEmail>
    <branchoutGroups>anvil practiv</branchoutGroups>
  </properties>

</project>

Jenkinsfile#

buildApi()