Skip to content
Snippets Groups Projects
Commit 03630b1c authored by Tony Chemit's avatar Tony Chemit :grinning:
Browse files

base-11 docker image definition

parent ef1b115f
No related branches found
No related tags found
No related merge requests found
FROM maven:3.9.9-eclipse-temurin-11-alpine
MAINTAINER Tony Chemit <dev@tchemit.fr>
ENV LANG en_US.UTF-8
COPY home /root/
RUN chmod 600 -R /root/.ssh ; chmod 600 -R /root/.gnupg
RUN (ln -s .m2/settings-security.xml .settings-security.xml)
RUN wget -q -O - https://gitlab.com/ultreiaio-infra/scripts/raw/master/install.sh | bash
\ No newline at end of file
alias ll='ls -l'
[user]
name = Ultreia.io Maven Build Agent
email = maven-build-agent@ultreia.io
[push]
default = simple
[color]
ui = true
\ No newline at end of file
# Options for GnuPG
# Copyright 1998, 1999, 2000, 2001, 2002, 2003,
# 2010 Free Software Foundation, Inc.
#
# This file is free software; as a special exception the author gives
# unlimited permission to copy and/or distribute it, with or without
# modifications, as long as this notice is preserved.
#
# This file is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
# implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
#
# Unless you specify which option file to use (with the command line
# option "--options filename"), GnuPG uses the file ~/.gnupg/gpg.conf
# by default.
#
# An options file can contain any long options which are available in
# GnuPG. If the first non white space character of a line is a '#',
# this line is ignored. Empty lines are also ignored.
#
# See the man page for a list of options.
# Uncomment the following option to get rid of the copyright notice
#no-greeting
# If you have more than 1 secret key in your keyring, you may want to
# uncomment the following option and set your preferred keyid.
#default-key 621CC013
# If you do not pass a recipient to gpg, it will ask for one. Using
# this option you can encrypt to a default key. Key validation will
# not be done in this case. The second form uses the default key as
# default recipient.
#default-recipient some-user-id
#default-recipient-self
# Use --encrypt-to to add the specified key as a recipient to all
# messages. This is useful, for example, when sending mail through a
# mail client that does not automatically encrypt mail to your key.
# In the example, this option allows you to read your local copy of
# encrypted mail that you've sent to others.
#encrypt-to some-key-id
# By default GnuPG creates version 4 signatures for data files as
# specified by OpenPGP. Some earlier (PGP 6, PGP 7) versions of PGP
# require the older version 3 signatures. Setting this option forces
# GnuPG to create version 3 signatures.
#force-v3-sigs
# Because some mailers change lines starting with "From " to ">From "
# it is good to handle such lines in a special way when creating
# cleartext signatures; all other PGP versions do it this way too.
#no-escape-from-lines
# If you do not use the Latin-1 (ISO-8859-1) charset, you should tell
# GnuPG which is the native character set. Please check the man page
# for supported character sets. This character set is only used for
# metadata and not for the actual message which does not undergo any
# translation. Note that future version of GnuPG will change to UTF-8
# as default character set. In most cases this option is not required
# as GnuPG is able to figure out the correct charset at runtime.
#charset utf-8
# Group names may be defined like this:
# group mynames = paige 0x12345678 joe patti
#
# Any time "mynames" is a recipient (-r or --recipient), it will be
# expanded to the names "paige", "joe", and "patti", and the key ID
# "0x12345678". Note there is only one level of expansion - you
# cannot make an group that points to another group. Note also that
# if there are spaces in the recipient name, this will appear as two
# recipients. In these cases it is better to use the key ID.
#group mynames = paige 0x12345678 joe patti
# Lock the file only once for the lifetime of a process. If you do
# not define this, the lock will be obtained and released every time
# it is needed, which is usually preferable.
#lock-once
# GnuPG can send and receive keys to and from a keyserver. These
# servers can be HKP, email, or LDAP (if GnuPG is built with LDAP
# support).
#
# Example HKP keyserver:
# hkp://keys.gnupg.net
# hkp://subkeys.pgp.net
#
# Example email keyserver:
# mailto:pgp-public-keys@keys.pgp.net
#
# Example LDAP keyservers:
# ldap://keyserver.pgp.com
#
# Regular URL syntax applies, and you can set an alternate port
# through the usual method:
# hkp://keyserver.example.net:22742
#
# Most users just set the name and type of their preferred keyserver.
# Note that most servers (with the notable exception of
# ldap://keyserver.pgp.com) synchronize changes with each other. Note
# also that a single server name may actually point to multiple
# servers via DNS round-robin. hkp://keys.gnupg.net is an example of
# such a "server", which spreads the load over a number of physical
# servers. To see the IP address of the server actually used, you may use
# the "--keyserver-options debug".
keyserver hkp://keys.gnupg.net
#keyserver mailto:pgp-public-keys@keys.nl.pgp.net
#keyserver ldap://keyserver.pgp.com
# Common options for keyserver functions:
#
# include-disabled : when searching, include keys marked as "disabled"
# on the keyserver (not all keyservers support this).
#
# no-include-revoked : when searching, do not include keys marked as
# "revoked" on the keyserver.
#
# verbose : show more information as the keys are fetched.
# Can be used more than once to increase the amount
# of information shown.
#
# use-temp-files : use temporary files instead of a pipe to talk to the
# keyserver. Some platforms (Win32 for one) always
# have this on.
#
# keep-temp-files : do not delete temporary files after using them
# (really only useful for debugging)
#
# http-proxy="proxy" : set the proxy to use for HTTP and HKP keyservers.
# This overrides the "http_proxy" environment variable,
# if any.
#
# auto-key-retrieve : automatically fetch keys as needed from the keyserver
# when verifying signatures or when importing keys that
# have been revoked by a revocation key that is not
# present on the keyring.
#
# no-include-attributes : do not include attribute IDs (aka "photo IDs")
# when sending keys to the keyserver.
#keyserver-options auto-key-retrieve
# Display photo user IDs in key listings
# list-options show-photos
# Display photo user IDs when a signature from a key with a photo is
# verified
# verify-options show-photos
# Use this program to display photo user IDs
#
# %i is expanded to a temporary file that contains the photo.
# %I is the same as %i, but the file isn't deleted afterwards by GnuPG.
# %k is expanded to the key ID of the key.
# %K is expanded to the long OpenPGP key ID of the key.
# %t is expanded to the extension of the image (e.g. "jpg").
# %T is expanded to the MIME type of the image (e.g. "image/jpeg").
# %f is expanded to the fingerprint of the key.
# %% is %, of course.
#
# If %i or %I are not present, then the photo is supplied to the
# viewer on standard input. If your platform supports it, standard
# input is the best way to do this as it avoids the time and effort in
# generating and then cleaning up a secure temp file.
#
# If no photo-viewer is provided, GnuPG will look for xloadimage, eog,
# or display (ImageMagick). On Mac OS X and Windows, the default is
# to use your regular JPEG image viewer.
#
# Some other viewers:
# photo-viewer "qiv %i"
# photo-viewer "ee %i"
#
# This one saves a copy of the photo ID in your home directory:
# photo-viewer "cat > ~/photoid-for-key-%k.%t"
#
# Use your MIME handler to view photos:
# photo-viewer "metamail -q -d -b -c %T -s 'KeyID 0x%k' -f GnuPG"
# Passphrase agent
#
# We support the old experimental passphrase agent protocol as well as
# the new Assuan based one (currently available in the "newpg" package
# at ftp.gnupg.org/gcrypt/alpha/aegypten/). To make use of the agent,
# you have to run an agent as daemon and use the option
#
# For Ubuntu we now use-agent by default to support more automatic
# use of GPG and S/MIME encryption by GUI programs. Depending on the
# program, users may still have to manually decide to install gnupg-agent.
use-agent
# which tries to use the agent but will fallback to the regular mode
# if there is a problem connecting to the agent. The normal way to
# locate the agent is by looking at the environment variable
# GPG_AGENT_INFO which should have been set during gpg-agent startup.
# In certain situations the use of this variable is not possible, thus
# the option
#
# --gpg-agent-info=<path>:<pid>:1
#
# may be used to override it.
# Automatic key location
#
# GnuPG can automatically locate and retrieve keys as needed using the
# auto-key-locate option. This happens when encrypting to an email
# address (in the "user@example.com" form), and there are no
# user@example.com keys on the local keyring. This option takes the
# following arguments, in the order they are to be tried:
#
# cert = locate a key using DNS CERT, as specified in RFC-4398.
# GnuPG can handle both the PGP (key) and IPGP (URL + fingerprint)
# CERT methods.
#
# pka = locate a key using DNS PKA.
#
# ldap = locate a key using the PGP Universal method of checking
# "ldap://keys.(thedomain)". For example, encrypting to
# user@example.com will check ldap://keys.example.com.
#
# keyserver = locate a key using whatever keyserver is defined using
# the keyserver option.
#
# You may also list arbitrary keyservers here by URL.
#
# Try CERT, then PKA, then LDAP, then hkp://subkeys.net:
#auto-key-locate cert pka ldap hkp://subkeys.pgp.net
File added
File added
File added
File added
<settingsSecurity>
<master>{TUTLKxvRF2UHcErRAK4ZWR5TITg+4/X0huvNimFifD0=}</master>
</settingsSecurity>
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
<mirrors>
<mirror>
<id>Sonatype Public Group</id>
<name>Maven Repository skip external</name>
<url>https://oss.sonatype.org/service/local/repositories/releases/content/</url>
<mirrorOf>*,!oss-snapshot,!oss-releases,!central,!osgeo,!apache-nexus-staging</mirrorOf>
</mirror>
</mirrors>
<servers>
<!-- To interact with GitLab (via the gitlab maven plugin and to deploy site via scm-publish maven plugin) -->
<server>
<id>ird.forge</id>
<username>ultreiaio</username>
<password>{cNEs7cb9o6oHxRhUeTfg9nGiu6LuNggJ/gZ2XCrkM4mT3WUeO3CqBXh7deRyK5bb}</password>
<privateKey>{cNEs7cb9o6oHxRhUeTfg9nGiu6LuNggJ/gZ2XCrkM4mT3WUeO3CqBXh7deRyK5bb}</privateKey>
</server>
<!-- To publish artifact iv ossrh -->
<server>
<id>ossrh</id>
<username>mK6WJO6g</username>
<password>X9vBVs9QSgzAY5au+dA4gwdIsUPW1FasTcpUZ3dIydBF</password>
</server>
</servers>
<pluginGroups>
<pluginGroup>org.codehaus.mojo</pluginGroup>
<pluginGroup>pl.project13.maven</pluginGroup>
<pluginGroup>io.ultreia.maven</pluginGroup>
<pluginGroup>io.ultreia.java4all.eugene</pluginGroup>
<pluginGroup>io.ultreia.java4all.jaxx</pluginGroup>
<pluginGroup>io.ultreia.java4all.i18n</pluginGroup>
<pluginGroup>io.ultreia.java4all.http</pluginGroup>
<pluginGroup>io.ultreia.java4all.config</pluginGroup>
<pluginGroup>io.ultreia.gitflow</pluginGroup>
</pluginGroups>
<activeProfiles>
<activeProfile>ossrh</activeProfile>
</activeProfiles>
<profiles>
<profile>
<id>ossrh</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<repositories>
<repository>
<id>central</id>
<url>
https://repo1.maven.org/maven2
</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>central</id>
<url>
https://repo1.maven.org/maven2
</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</pluginRepository>
</pluginRepositories>
</profile>
<profile>
<id>oss-release-profile</id>
<activation>
<property>
<name>oss</name>
<value>true</value>
</property>
<activeByDefault>true</activeByDefault>
</activation>
<repositories>
<repository>
<id>oss-public</id>
<url>
https://oss.sonatype.org/content/groups/public
</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
<repository>
<id>oss-releases</id>
<url>
https://oss.sonatype.org/service/local/repositories/releases/content/
</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>oss-plugin-public</id>
<url>
https://oss.sonatype.org/content/groups/public
</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</pluginRepository>
<pluginRepository>
<id>oss-plugin-releases</id>
<url>
https://oss.sonatype.org/service/local/repositories/releases/content/
</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</pluginRepository>
</pluginRepositories>
</profile>
</profiles>
</settings>
Host *
IdentityFile ~/.ssh/maven
StrictHostKeyChecking no
|1|OQ1dcMGBAAhmJ6t9REQ4/hSKAIE=|Mzr399RYOQM0Fyo6ZBfn8kdDj3I= ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBFSMqzJeV9rUzU4kWitGjeR4PWSa29SPqJ1fVkhtj3Hw9xjLVXVYrU9QlYWrOLXBpQ6KWjbjTDTdDkoohFzgbEY=
|1|QJjRWS/6T5cT2qWzVzJMafECwOs=|qo5DAcsyOLRUOG9XpKPWrPDZO8Y= ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBFSMqzJeV9rUzU4kWitGjeR4PWSa29SPqJ1fVkhtj3Hw9xjLVXVYrU9QlYWrOLXBpQ6KWjbjTDTdDkoohFzgbEY=
\ No newline at end of file
-----BEGIN RSA PRIVATE KEY-----
MIIEpgIBAAKCAQEA4FbTcP9MZRLmdJBpjNjlzYD4MQnxmhvTYfZNaPE5y1yUS5YA
Yp3pzlA4MgH6W1eDvB+yMdm274ChMRrLTSAQdsP63x02AWHga0RSUkIFx1srPbVT
JaMksIikmI2/9zuI63+M1t2ZymS70+b6CHGMbT2slzrfV6X0LqiOSPDGDJ1Ch6mv
INSlD/lX9tRmMxVtsf3ZOpEH83P5yXymURtXTWM4Lx/yGyKqD0JYujOl89YK9Zv6
vRzOp/IVvB3eezCBZVmU8y1rykpJM2bBgya1V1zt8wOTSpEjQ913AD9SXjeRT+gQ
+8dQ5eR6HbAK/7fcfwwHHeUrla2WphCZl6wumwIDAQABAoIBAQCLu+lF5+84wbYE
AvOLxIoXH+739J6lhBF9YkJDTIXYMpk4H32r73pzhKoMFAlSHcezRPbkcByvP6qn
gG4DYyZ+I4I+uN4rrEBx8ANqsy8QRqw/apMYzW6L+wCy+RAKOe4F6dPa/frOA0Kv
MZ6p5bg3TwQSypvU50yaR2kg68AgmCRw/5Wr6fpk/0E4zE9xVOY7tLmT92zixR9b
V78H6jqMYUy2LR9bzq8ZUxaZMttZBnaVxAbYEwnFn+CVeJreltja9f4oznM3bK/l
fFWwJUN8axZyAwqCZhynEciFPmhxnqNxEO0L1y1Rqow1lOwScORAL61HVxmdMGIF
7bURt/yhAoGBAP+KjkI2gDfk1TglB2mylIGQLF9Ffk9tPVtkO07nGDqMKtqZG6x4
FGm/psdB2JccE5ur/IyBKQ/BRkxpwxNY0Ohw90hgyWFwYInV6pN2L+o0tFBYYqxa
GwU7qaq77oUvfuLL+lXmrFcPKegeeA+C7plcjqi7086DTc10jkGIL+bRAoGBAOC9
7hlED73OCJkn7VtwWlgdDwIosSjN2AjSkb5D5/4NkvDtQe2LcBCi+hiDnbZGNEk4
L01ygbp+lR7lvbu+SrR+NxU8PQU3QJcYn/zherGDTtymCglw7lTJFEMgVNrNtd8t
E0nuYPmYXjUn9MM+iz9aR41JL/FPfn0ghzkaTzGrAoGBAOl9xqKFff6UXqagXveb
Lsp7269pphIY9JlPKkncKm1Eqdt3Tqv2RGCjt1YVujvIcboqGeagFc7JgNxNPuus
maXpomlF1nvr3KnVBjObKAjOA3vuZqqo4kuTymGwui6DyWKdkq1uykX6GwZ24Kj7
r9v9kHRouw3VN//k4h7Ku0ohAoGBAJTwSeKkoGoBKOGW/E4k3zqVx2R+4ylPgWQX
aE7XYd+Tz1WrZo2uYs4js+qbDuHFFNGRUofY4vBdAyY+ysapDYkgPBDuouHaBAwe
XaiRJWaOxqyjvPMUzF2UBMGXo6R9v5HvpWDRgaLnv0cq+6KIyG9rvQ98+TDKpeD2
taa6MNGRAoGBAOoZWZtVr6UwiK9D8GGyfchOjU5IeRc+RQE0kBFHqTThm+xkbC0M
4afe2cTBkiPrpUAuJnTgOgFUoQt/K6GPyT4j2quFggSqxcGabicxO7+LdlTSSKE+
KGs8sFdxczjxesQnn01dOePAiTATXYvnjWVEXvy/qpBjuGY1Y36g36Oa
-----END RSA PRIVATE KEY-----
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDgVtNw/0xlEuZ0kGmM2OXNgPgxCfGaG9Nh9k1o8TnLXJRLlgBinenOUDgyAfpbV4O8H7Ix2bbvgKExGstNIBB2w/rfHTYBYeBrRFJSQgXHWys9tVMloySwiKSYjb/3O4jrf4zW3ZnKZLvT5voIcYxtPayXOt9XpfQuqI5I8MYMnUKHqa8g1KUP+Vf21GYzFW2x/dk6kQfzc/nJfKZRG1dNYzgvH/IbIqoPQli6M6Xz1gr1m/q9HM6n8hW8Hd57MIFlWZTzLWvKSkkzZsGDJrVXXO3zA5NKkSND3XcAP1JeN5FP6BD7x1Dl5HodsAr/t9x/DAcd5SuVrZamEJmXrC6b tchemit@tc-work
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment