zenofx.com

Docker IPv6 support

Sat, 10 Sep 2022 00:00:00 +0000

Our non-public infrastructure is (mostly) IPv6 only. Therefore, we need outgoing* IPv6 support on our Docker based Gitlab runners. Complete IPv6 support is out of scope of this snippet – a more complete answer may be found on Docker IPV6 Guide.

Simply follow these steps:

Enable IPv6

Edit /etc/docker/daemon.json on the Docker host

{
  "ipv6": true,
  "fixed-cidr-v6": "fd00::/80"
}

and restart the daemon, e.g.

sudo service docker restart

Enable outgoing traffic using NAT

sudo ip6tables -t nat -A POSTROUTING -s fd00::/80 ! -o docker0 -j MASQUERADE

Test outgoing traffic from a Docker guest

docker run --rm -t busybox ping6 ipv6.google.com

Make changes permanent

This obviously depends on your distribution. For Debian/Ubuntu based distributions, we edit /etc/systemd/system/multi-user.target.wants/docker.service:

ExecStartPre=ip6tables -t nat -A POSTROUTING -s fd00::/80 ! -o docker0 -j MASQUERADE

For this to test, you need to reboot your system.

* IP always needs to work in both directions. "Outgoing" means our Docker guests contact IPv6 only servers, but are not accessible via IPv6.

Android ant support

Tue, 23 Aug 2022 00:00:00 +0000

There are legitimate reasons to still build Android apps using ant. First of all, you may be responsible for supporting a legacy project with very limited new development. Migrating such a project to AndroidStudio and gradle may require more effort than you can spare (especially as you’d also have to migrate the project structure).

However, there are a few quirks that you have to keep in mind. The following setup works for us:

Platform setup

Tools 25.2.5 seem to be the last version with ant support. We’re using build-tools 25.0.3, but more modern versions also should work. For installing the current Android target 31 you’ll have to use the sdkmanager from tools dir, otherwise you’ll get a target not found error.

sdkmanager --install "platform-tools"
sdkmanager --install "tools;25.2.5"       
sdkmanager --install "build-tools;25.0.3"
ANDROID_TARGET=$(grep "^target=" project.properties |cut -d "=" -f 2)
${ANDROID_HOME}/tools/bin/sdkmanager "platforms;${ANDROID_TARGET}"

To enforce the use of build-tools 25.0.3, you can put the following line in your project.properties file:

sdk.buildtools=25.0.3

Use patched build.xml

The build.xml file from the ${ANDROID_HOME}/tools/ant dir does not work anymore for modern targets. Especially, the code signing process has to be adapted. You can use our patched build-android-sdk.xml. This file has to be referenced from your build.xml file (near the end of the file) like this:

<import file="/path/to/build-android-sdk.xml" />

Call ant

ant clean debug lint     # Debug build, lint
ant clean release        # Signed release build

(Limited) Eclipse support

Support for Eclipse using Andmore from Eclipse Marketplace seems to be abandoned. Currently we can’t recommend this approach.

However, some of our developers use a configuration which allows at least editing Android apps within Eclipse. For this, you have to patch org.eclipse.andmore.base_0.5.1.201701251432.jar with some classes from an ancient Oracle Java 8 release.

jar xvf rt.jar sun/misc/BASE64Decoder.class sun/misc/BASE64Encoder.class sun/misc/CharacterDecoder.class sun/misc/CharacterEncoder.class
jar uvf <path/to/org.eclipse.andmore.base_0.5.1.201701251432.jar> sun/misc

Where org.eclipse.andmore.base_0.5.1.201701251432.jar is found, depends on your installation – usually either in Eclipse/plugins or in your home dir in .p2/pool/plugins.

You’ll still get an ugly error when compiling files (“Errors occurred during the build.”). To avoid this, you can check

Skip packaging and dexing until export or launch

in Eclipse Android preferences. Probably you can even restore packaging and dexing by including crypto classes from sun.misc, but this is beyond the scope of this snippet.

Atlassian Marketplace Publishing

Thu, 18 Apr 2019 00:00:00 +0000

Our complete deployment process is driven by Gitlab CI/CD (before that, we were using Jenkins). Plugins for the Atlassian Marketplace used to be an exception for several years. Annoyed by this situation, we decided to develop a Maven plugin which integrates smoothly into Atlassian’s plugin build process and allows an easy deployment to the Marketplace. However, for us the last submission step (switching the version from “Private” to “Public”) remains manual.

The plugin is based on Atlassian’s Marketplace API Java client. Source code for the plugin is availabe on Bitbucket under GPLv3.

Integration

Insert into your pom.xml’s <plugins> section:

<plugins>
  ...
  <!-- Marketplace deployer -->
  <plugin>
    <groupId>com.zenofx.maven</groupId>
    <artifactId>marketplace-maven-plugin</artifactId>
    <configuration>
      <username>user@example.com</username>
      <password>{token encrypted by mvn -ep}</password>
      <licenseType>GPL</licenseType>
      <paymentModel>FREE</paymentModel>
      <releaseSummary>Summary</releaseSummary>
    </configuration>
    <executions>
      <execution>
        <goals>
          <goal>createVersion</goal>
        </goals>
      </execution>
    </executions>
  </plugin>
  <!-- Switch off default deployer -->
  <plugin>
    <artifactId>maven-deploy-plugin</artifactId>
    <configuration>
      <skip>true</skip>
    </configuration>
  </plugin>
</plugins>

Usage

After integrating into your pom, an additional target deploy is available:

atlas-mvn clean deploy

Supported configuration properties

username Username for Atlassian Marketplace.

password Token for Atlassian Marketplace (passwords are not supported any more). The token has to be encrypted using atlas-mvn -ep.

buildNumber Build number, if not set computed from semantic version.

buildPattern (Default: %1d%03d%03d) Pattern for computing build number from semantic version. Default value according to Atlassian versioning proposals.

licenseType License type (COMMERCIAL, COMMERCIAL_FREE, BSD, ASL, GPL, LGPL, EPL or ATLASSIAN_CLOSED_SOURCE).

paymentModel Payment Model (FREE, PAID_VIA_VENDOR or PAID_VIA_ATLASSIAN).

releaseNotes Release notes.

releaseSummary Release summary.

status (Default: PRIVATE) Status of version after upload (PRIVATE, PUBLIC or SUBMITTED). This is only for completeness, please always use PRIVATE and submit manually.

supported (Default: true) Is this version supported?

beta (Default: false) Is this a beta version?

type (Default: JAR) Type of artifact (JAR or OBR).