adamcin / crx-content-package-deployer

Provides Jenkins integration with Adobe Granite

CRX Content Package Deployer Plugin

(crx-content-package-deployer)

Deploys content packages to Adobe Granite applications, like Adobe CQ 5.4, CQ 5.5, and AEM 5.6

Features

1. Supports password-less HTTP Signature authentication using your configured SSH Private Keys, eliminating the need to coordinate password exchange between developers, devops, and operations teams.

2. Downloads and/or deploys 1-to-many CRX packages per execution, and deploys each CRX package to 1-to-many servers per execution

3. The multiselect-enabled Package Choice Parameter allows for execution of parameterized builds using a selection widget populated with a list of packages retrieved from a CRX server.

Components

CRX Content Package Choice Parameter

Summary

The CRX Content Package Choice Parameter is a build parameter which allows a user to select any number of content packages available for download from a CRX server as as a valid, newline-separated Package Id field value, which can then be used in other components provided by this plugin.

Configuration

Build with Parameters

Download Content Packages from CRX

Configuration

Console Output

Deploy Content Packages to CRX

Configuration

Console Output

crx-content-package-deployer's Issues

Deploying content package throws NullPointerException if package already exists

Hi,
This is happening in AEM 6. While trying to deploy a package in AEM 6 and if the package already exists, NullPointerException is thrown from the code and the deployment fails.
Works fine if the package does not already exists in AEM. Below is the error:

FATAL: Failed to deploy package: null
java.lang.NullPointerException
at net.adamcin.granite.client.packman.AbstractPackageManagerClient.existsOnServer(AbstractPackageManagerClient.java:823)
at org.jenkinsci.plugins.graniteclient.DeployPackageCallable$Execution.doExecute(DeployPackageCallable.java:71)
at org.jenkinsci.plugins.graniteclient.DeployPackageCallable$Execution.doExecute(DeployPackageCallable.java:61)
at org.jenkinsci.plugins.graniteclient.GraniteClientExecutor.execute(GraniteClientExecutor.java:87)
at org.jenkinsci.plugins.graniteclient.DeployPackageCallable.invoke(DeployPackageCallable.java:123)
at org.jenkinsci.plugins.graniteclient.DeployPackageCallable.invoke(DeployPackageCallable.java:42)
at hudson.FilePath.act(FilePath.java:980)
at hudson.FilePath.act(FilePath.java:958)
at org.jenkinsci.plugins.graniteclient.DeployPackagesBuilder.perform(DeployPackagesBuilder.java:273)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
at hudson.model.Build$BuildExecution.build(Build.java:199)
at hudson.model.Build$BuildExecution.doRun(Build.java:160)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533)
at hudson.model.Run.execute(Run.java:1745)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Build step 'Deploy Content Packages to CRX' changed build result to FAILURE
Build step 'Deploy Content Packages to CRX' marked build as failure
Finished: FAILURE

Thanks,

java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper

This happens when using Jenkins ver. 1.607.

Related Error messages:

ERROR: Failed to list package files: remote file operation failed

FATAL: No package found matching filter *.zip
java.io.IOException: No package found matching filter *.zip
at org.jenkinsci.plugins.graniteclient.DeployPackagesBuilder.selectPackages(DeployPackagesBuilder.java:338)
at org.jenkinsci.plugins.graniteclient.DeployPackagesBuilder.perform(DeployPackagesBuilder.java:259)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761)
at hudson.model.Build$BuildExecution.build(Build.java:203)
at hudson.model.Build$BuildExecution.doRun(Build.java:160)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536)
at hudson.model.Run.execute(Run.java:1741)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:374)

Unable to Deploy packages to a publisher

This is a little strange behavior.

On AEM 6.0, for deploying to Author its works fine. However, if we try deploying to Publisher we get to see the following exception:

Deploying packages to http://xxxxxxxxx:4503/
FATAL: Failed to deploy package: Failed to login with provided credentials
java.io.IOException: Failed to login with provided credentials at net.adamcin.granite.client.packman.async.AsyncPackageManagerClient.login(AsyncPackageManagerClient.java:197) at org.jenkinsci.plugins.graniteclient.GraniteClientExecutor.doLoginPOST(GraniteClientExecutor.java:138) at org.jenkinsci.plugins.graniteclient.GraniteClientExecutor.doLogin(GraniteClientExecutor.java:103)
at org.jenkinsci.plugins.graniteclient.GraniteClientExecutor.execute(GraniteClientExecutor.java:86)
at org.jenkinsci.plugins.graniteclient.DeployPackageCallable.invoke(DeployPackageCallable.java:123)
at org.jenkinsci.plugins.graniteclient.DeployPackageCallable.invoke(DeployPackageCallable.java:42)
at hudson.FilePath.act(FilePath.java:989)
at hudson.FilePath.act(FilePath.java:967)
at org.jenkinsci.plugins.graniteclient.DeployPackagesBuilder.perform(DeployPackagesBuilder.java:273)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.build(MavenModuleSetBuild.java:906)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:857)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533)
at hudson.model.Run.execute(Run.java:1718)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Build step 'Deploy Content Packages to CRX' changed build result to FAILURE
Build step 'Deploy Content Packages to CRX' marked build as failure

.......
If we try to install the same package using CURL command with the default credentials of admin:admin, we receive success.

Not sure what credentials are getting passed.

Deployment is getting stuck

Jobs log :

Deploying packages to http://dev00:7120/crx/de/../..
Deploying /opt/app/workload/jenkins/ecms/data/jobs/testDeploy/workspace/aem-upperfunnel-apps-1.0.32-SNAPSHOT.zip to http://dev00:7120/crx/packmgr/index.jsp#/etc/packages/Upperfunnel/aem-upperfunnel-apps-1.0.32-SNAPSHOT.zip

After this it just gets stuck and there is nothing in Jenkins log as well.

I checked the connection from job configuration and it is successfull!!

I am using plugin version 1.5.3
AEM is 6.1 SP1