drone-mvn-auth

Drone plugin for generating the settings.xml with the server authentication for a Maven repository.

Please note that dependencies are saved in the .m2 directory.

Configuration

The following parameters are used to configure the plugin:

• servers[]: the servers
• servers[].id: the server id
• servers[].username: the server username
• servers[].password: the server password
• profiles[]: the profiles
• profiles[].id: the profile id
• profiles[].repositories[]: the profile's repositories
• profiles[].repositories[].id: the profile's repository id
• profiles[].repositories[].name: the profile's repository name
• profiles[].repositories[].url: the profile's repository url
• profiles[].repositories[].layout: the profile's repository layout
• profiles[].plugin_repositories[]: the profile's plugin repositories
• profiles[].plugin_repositories[].id: the profile's plugin repository id
• profiles[].plugin_repositories[].name: the profile's plugin repository name
• profiles[].plugin_repositories[].url: the profile's plugin repository url
• profiles[].plugin_repositories[].layout: the profile's plugin repository layout
• active_profiles[]: the active profiles
• debug: debug mode (optional: set to true for verbose messages)

Secrets mode

The secrets mode allows for usage of Drone secrets for parameters. For every parameter, the secret prefix to use is maven_. For example, for storing the servers parameter as a secret, the key would be maven_servers. The value for that parameter would still need to be serialised JSON.

Drone configuration example

pipeline:
  build:
    image: maven:3-alpine
    commands:
      - mvn install -gs settings.xml
      
  authenticate:
    image: robertstettner/drone-mvn-auth
    pull: true
    servers:
      - id: release
        username: ${NEXUS_USERNAME}
        password: ${NEXUS_PASSWORD}
      - id: snapshot
        username: ${NEXUS_USERNAME}
        password: ${NEXUS_PASSWORD}
    profiles:
      - id: my-profile
        repositories:
          - id: myRepo
            name: Repository for my libraries
            url: http://maven.my.com
            layout: default
        plugin_repositories:
          - id: myRepo
            name: Repository for my libraries
            url: http://maven.my.com
            layout: default
    active_profiles:
      - my-profile
              
    
  deploy:
    image: maven:3-alpine
    commands:
      - mvn clean deploy -gs settings.xml

Drone configuration example with secrets

The example below shows how to use the plugin with secrets. An example of the servers parameter value for the secret maven_servers could be: [{"id": "release","username":"foo","password":"bar"}]

pipeline:
  build:
    image: maven:3-alpine
    commands:
      - mvn install -gs settings.xml
      
  authenticate:
    image: robertstettner/drone-mvn-auth
    pull: true
    secrets: [ maven_servers ]
    profiles:
      - id: my-profile
        repositories:
          - id: myRepo
            name: Repository for my libraries
            url: http://maven.my.com
            layout: default
        plugin_repositories:
          - id: myRepo
            name: Repository for my libraries
            url: http://maven.my.com
            layout: default
    active_profiles:
      - my-profile
              
    
  deploy:
    image: maven:3-alpine
    commands:
      - mvn clean deploy -gs settings.xml

License

MIT