I've been trying to upload my jmx test scripts to Blazemeter but it always gives me this screen after running the test. Any common mistakes I could be making that would lead to this issue? Here are some of the log reports too, they don't make much sense to me. There appears to be some problem with a yaml file but I didn't upload one, so if it needs one to work that might be it. Any help or advice is appreciated, thanks.
[13-08-21 02:14:50] [INFO] [r-v4-6116b69a143f3372092493] system: Status changed to PREPARING_PROVISIONING (14)
[13-08-21 02:14:50] [INFO] [r-v4-6116b69a143f3372092493] system: Status changed to CONFIGURING_DEPENDENCIES (10)
[13-08-21 02:14:51] [INFO] [r-v4-6116b69a143f3372092493] system: Status changed to PREPARING_PROVISIONING (14)
[13-08-21 02:15:48] [INFO] [r-v4-6116b69a143f3372092493] system: Prepare: Verify file path /usr/local/taurus-cloud/files
[13-08-21 02:15:48] [INFO] [r-v4-6116b69a143f3372092493] system: Prepare: file path created
[13-08-21 02:15:48] [INFO] [r-v4-6116b69a143f3372092493] system: Prepare: Verify file path /tmp/artifacts/admin
[13-08-21 02:15:48] [INFO] [r-v4-6116b69a143f3372092493] system: [Init Info: Before init variables]
original_config: https://a.blazemeter.com/api/v4/taurus/r-v4-6116b69a143f3372092493/original-config
custom_config: https://a.blazemeter.com/api/v4/taurus/r-v4-6116b69a143f3372092493/custom-config
EVENTS_URL: https://data.blazemeter.com/api/v4/taurus/r-v4-6116b69a143f3372092493/events
FILE_NAME: TestPlan _1_.jmx
SCRIPT_TYPE: jmeter
INSTANCE ID: None
[13-08-21 02:15:48] [INFO] [r-v4-6116b69a143f3372092493] system: Prepare: file path created
[13-08-21 02:15:48] [INFO] [r-v4-6116b69a143f3372092493] system: Prepare: Verify file path /tmp/artifacts
[13-08-21 02:15:48] [INFO] [r-v4-6116b69a143f3372092493] system: Prepare: file path created
[13-08-21 02:15:48] [INFO] [r-v4-6116b69a143f3372092493] system: Prepare: Verify file path /usr/local
[13-08-21 02:15:48] [INFO] [r-v4-6116b69a143f3372092493] system: Prepare: Verify file path /usr/local/bztcloud
[13-08-21 02:15:48] [INFO] [r-v4-6116b69a143f3372092493] system: Prepare: file path created
[13-08-21 02:15:48] [INFO] [r-v4-6116b69a143f3372092493] system: Session id is set
[13-08-21 02:15:48] [INFO] [r-v4-6116b69a143f3372092493] system: Prepare: file path created
[13-08-21 02:15:48] [INFO] [r-v4-6116b69a143f3372092493] system: Starting Taurus Cloud - Cloud Launcher
[13-08-21 02:15:48] [INFO] [r-v4-6116b69a143f3372092493] system: Testing Operation System: ***linux***
[13-08-21 02:15:48] [INFO] [r-v4-6116b69a143f3372092493] system: Running Taurus update
[13-08-21 02:15:48] [INFO] [r-v4-6116b69a143f3372092493] system: Starting Taurus update
[13-08-21 02:15:48] [INFO] [r-v4-6116b69a143f3372092493] system: Taurus update complete
[13-08-21 02:15:48] [INFO] [r-v4-6116b69a143f3372092493] system: [Init Info: After init variables]
original_config: https://a.blazemeter.com/api/v4/taurus/r-v4-6116b69a143f3372092493/original-config
custom_config: https://a.blazemeter.com/api/v4/taurus/r-v4-6116b69a143f3372092493/custom-config
EVENTS_URL: https://data.blazemeter.com/api/v4/taurus/r-v4-6116b69a143f3372092493/events
FILE_NAME: TestPlan _1_.jmx
SCRIPT_TYPE: jmeter
INSTANCE ID: None
[13-08-21 02:15:48] [INFO] [r-v4-6116b69a143f3372092493] system: Running blacklist check
[13-08-21 02:15:48] [INFO] [r-v4-6116b69a143f3372092493] system: Applying blacklist
[13-08-21 02:15:48] [INFO] [r-v4-6116b69a143f3372092493] system: Prepare: Preparing test launcher environment
[13-08-21 02:15:49] [INFO] [r-v4-6116b69a143f3372092493] system: Getting base configuration from configuration file https://a.blazemeter.com/api/v4/taurus/r-v4-6116b69a143f3372092493/original-config and additional configuration from the custom configuration https://a.blazemeter.com/api/v4/taurus/r-v4-6116b69a143f3372092493/custom-config
[13-08-21 02:15:49] [INFO] [r-v4-6116b69a143f3372092493] system: Blacklist check completed (Check: 1)
[13-08-21 02:15:50] [INFO] [r-v4-6116b69a143f3372092493] system: Downloading the configuration file from https://a.blazemeter.com/api/v4/taurus/r-v4-6116b69a143f3372092493/original-config
[13-08-21 02:15:50] [INFO] [r-v4-6116b69a143f3372092493] system: Running BZT...
[13-08-21 02:15:50] [INFO] [r-v4-6116b69a143f3372092493] system: verify_ssl value:
[13-08-21 02:15:50] [INFO] [r-v4-6116b69a143f3372092493] system: Status changed to INIT_SCRIPT (50)
[13-08-21 02:15:50] [INFO] [r-v4-6116b69a143f3372092493] system: Downloading the custom configuration file from https://a.blazemeter.com/api/v4/taurus/r-v4-6116b69a143f3372092493/custom-config
[13-08-21 02:15:50] [WARNING] [r-v4-6116b69a143f3372092493] system: Error handling original config as yaml; saving file as is
[13-08-21 02:15:53] [INFO] [r-v4-6116b69a143f3372092493] system: Running command: atop ('-a', '-w', '/tmp/artifacts/admin/atop.binlog', '15')
[13-08-21 02:15:54] [INFO] [r-v4-6116b69a143f3372092493] system: Jetlag: Download process completed
[13-08-21 02:15:54] [INFO] [r-v4-6116b69a143f3372092493] system: Jetlag: Skip download ()
[13-08-21 02:15:55] [INFO] [r-v4-6116b69a143f3372092493] system: Jetpack: Download process completed
[13-08-21 02:15:55] [INFO] [r-v4-6116b69a143f3372092493] system: Jetpack: Downloading skipped (No URL)
[13-08-21 02:16:00] [INFO] [r-v4-6116b69a143f3372092493] system: Jetpack: Starting jetpack...
[13-08-21 02:16:00] [INFO] [r-v4-6116b69a143f3372092493] system: Jetpack: Version 5.0.1
[13-08-21 02:16:19] [INFO] [r-v4-6116b69a143f3372092493] system: Status changed to TAURUS_ENGINE_READY (90)
[13-08-21 02:16:19] [INFO] [r-v4-6116b69a143f3372092493] system: Status changed to TAURUS_ENGINE_INIT (71)
[13-08-21 02:36:26] [INFO] [r-v4-6116b69a143f3372092493] system: Status changed to TERMINATING (130)
[13-08-21 02:36:41] [INFO] [r-v4-6116b69a143f3372092493] system: Status changed to TAURUS_BZT_DONE (135)
[13-08-21 02:36:42] [INFO] [r-v4-6116b69a143f3372092493] system: Collecting atop.binlog - saving to log file
[13-08-21 02:36:42] [INFO] [r-v4-6116b69a143f3372092493] system: Starting cloud shutdown
[13-08-21 02:36:43] [INFO] [r-v4-6116b69a143f3372092493] system: Moving file /tmp/artifacts/jetpack.properties
[13-08-21 02:36:43] [INFO] [r-v4-6116b69a143f3372092493] system: Moving admin artifacts and creating zip
[13-08-21 02:36:43] [INFO] [r-v4-6116b69a143f3372092493] system: Moving file /tmp/artifacts/merged.yml
[13-08-21 02:36:43] [INFO] [r-v4-6116b69a143f3372092493] system: Moving file /tmp/artifacts/merged.json
[13-08-21 02:36:43] [INFO] [r-v4-6116b69a143f3372092493] system: Moving file /tmp/artifacts/final-overrides.yml
[13-08-21 02:36:43] [INFO] [r-v4-6116b69a143f3372092493] system: Moving file /tmp/artifacts/jetlag-download.log
[13-08-21 02:36:43] [INFO] [r-v4-6116b69a143f3372092493] system: Moving file /tmp/artifacts/effective.json
[13-08-21 02:36:43] [INFO] [r-v4-6116b69a143f3372092493] system: Moving file /tmp/artifacts/network_checking.log
[13-08-21 02:36:43] [WARNING] [r-v4-6116b69a143f3372092493] system: File /tmp/artifacts/taurus-base-config.yml not found on disk
[13-08-21 02:36:43] [INFO] [r-v4-6116b69a143f3372092493] system: Moving file /tmp/artifacts/jetpack.log
[13-08-21 02:36:43] [INFO] [r-v4-6116b69a143f3372092493] system: Moving file /tmp/artifacts/cloud-launcher.log
[13-08-21 02:36:43] [INFO] [r-v4-6116b69a143f3372092493] system: Moving file /tmp/artifacts/taurus-custom-config.yml
[13-08-21 02:36:43] [INFO] [r-v4-6116b69a143f3372092493] system: Moving file /tmp/artifacts/exported.jetlag.ldjson
[13-08-21 02:36:43] [INFO] [r-v4-6116b69a143f3372092493] system: Moving file /tmp/artifacts/effective.yml
[13-08-21 02:36:43] [INFO] [r-v4-6116b69a143f3372092493] system: Moving file /tmp/artifacts/jetpack-download.log
[13-08-21 02:36:43] [WARNING] [r-v4-6116b69a143f3372092493] system: File /tmp/artifacts/taurus_start.log not found on disk
[13-08-21 02:36:43] [INFO] [r-v4-6116b69a143f3372092493] system: Moving file /tmp/artifacts/jetlag.log
[13-08-21 02:36:43] [INFO] [r-v4-6116b69a143f3372092493] system: Zipping artifacts into file /tmp/artifacts/admin-artifacts.zip
[13-08-21 02:36:43] [INFO] [r-v4-6116b69a143f3372092493] system: Zipping path /tmp/artifacts/admin
[13-08-21 02:36:44] [INFO] [r-v4-6116b69a143f3372092493] system: Admin artifacts zip files generated [/tmp/artifacts/admin-artifacts.zip, /tmp/artifacts/admin-artifacts.zip.tail.bz]
[13-08-21 02:36:44] [INFO] [r-v4-6116b69a143f3372092493] system: Zipping artifacts into file /tmp/artifacts/artifacts.zip
[13-08-21 02:36:44] [INFO] [r-v4-6116b69a143f3372092493] system: Zipping path /tmp/artifacts
[13-08-21 02:37:25] [INFO] [r-v4-6116b69a143f3372092493] system: Artifacts zip files generated [/tmp/artifacts/artifacts.zip, /tmp/artifacts/artifacts.zip.tail.bz]
[13-08-21 02:37:28] [INFO] [r-v4-6116b69a143f3372092493] system: Status changed to TAURUS_IMAGE_DONE (136)
[13-08-21 02:37:28] [INFO] [r-v4-6116b69a143f3372092493] system: Taurus completed (Exit: 1)
[13-08-21 02:37:28] [INFO] [r-v4-6116b69a143f3372092493] system: 0 seconds until process run completion
[13-08-21 02:37:28] [INFO] [r-v4-6116b69a143f3372092493] system: Finished file upload
[13-08-21 02:37:29] [INFO] [r-v4-6116b69a143f3372092493] system: Status changed to ENDED (140)
[13-08-21 02:37:29] [INFO] [r-v4-6116b69a143f3372092493] system: Terminate command sent
I believe this form of questions should go to BlazeMeter Support
I can only guess that BlazeMeter engine might not like your TestPlan _1_.jmx filename, try removing spaces and underscores, it might fix the problem.
Also you can look at the BZT.log file from the Logs Report view, most probably it will be way more informative.
Related
The frontend-maven-plugin tries to download a node file which does not exist.
When I look into https://nodejs.org/dist/v10.15.3 I can only see a file named node-v10.15.3-darwin-x64.tar.gz
[INFO] --- frontend-maven-plugin:1.7.5:install-node-and-npm (install node and npm) # oauth-ui-authorization-code-angular-zuul ---
[INFO] Installing node version v10.15.3
[INFO] Downloading https://nodejs.org/dist/v10.15.3/node-v10.15.3-darwin-arm64.tar.gz to /Users/me/.m2/repository/com/github/eirslett/node/10.15.3/node-10.15.3-darwin-arm64.tar.gz
[INFO] No proxies configured
[INFO] No proxy was configured, downloading directly
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] mymodule 2.2.6.RELEASE FAILURE [ 4.536 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 36.930 s
[INFO] Finished at: 2022-09-28T14:28:09+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.7.5:install-node-and-npm (install node and npm) on project mymodule: Could not download Node.js: Got error code 404 from the server. -> [Help 1]
[ERROR]
This is a bug in the frontend-maven-plugin.
An upgrade to the current version should help:
<plugin>
<groupId>com.github.eirslett</groupId>
<artifactId>frontend-maven-plugin</artifactId>
<version>1.12.1</version>
...
Thanks to:
https://github.com/apache/druid/issues/10804
https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/m1-mac-cant-build-wknd-tutorial-get-quot-could-not-download-node/m-p/399462
I am executing liquibase through Maven like mvn liquibase:update and as you can see I am getting output in the console
[INFO] Scanning for projects...
[INFO]
[INFO] -------< LiquibaseInstanaExperiment:LiquibaseInstanaExperiment >--------
[INFO] Building LiquibaseInstanaExperiment 0.0.1-SNAPSHOT
[INFO] --------------------------------[ pom ]---------------------------------
[INFO]
[INFO] --- liquibase-maven-plugin:3.3.2:update (default-cli) # LiquibaseInstanaExperiment ---
[INFO] ------------------------------------------------------------------------
[INFO] Parsing Liquibase Properties File
[INFO] File: C:\Users\RaghavGupta\Downloads\LiquibaseInstanaExperiment/liquibase.properties
[INFO] 'referencePassword' in properties file is not being used by this task.
[INFO] 'referenceUsername' in properties file is not being used by this task.
[INFO] 'referenceUrl' in properties file is not being used by this task.
[INFO] ------------------------------------------------------------------------
[INFO] Executing on Database: jdbc:postgresql://52.118.184.180:5432/postgres
INFO 5/19/22, 2:27 PM: liquibase: Successfully acquired change log lock
INFO 5/19/22, 2:28 PM: liquibase: Reading from databasechangelog
INFO 5/19/22, 2:28 PM: liquibase: Successfully released change log lock
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 22.277 s
[INFO] Finished at: 2022-05-19T14:28:12+05:30
[INFO] ------------------------------------------------------------------------
I want this output or system logs to move into a log file. How do we do that?
This is done by executing -l,--log-file <arg> to log the file to where all build output will go.
Example:
mvn <your parameters> --log-file log.txt
I have a Spring Boot app with jib-maven configured
POM
<plugin>
<groupId>com.google.cloud.tools</groupId>
<artifactId>jib-maven-plugin</artifactId>
<version>2.1.0</version>
<configuration>
<from>
<image>openjdk:11-jre-slim</image>
</from>
<to>
<image>registry.demo/${project.artifactId}</image>
<tags>
<tag>${project.version}</tag>
</tags>
<tags>
<tag>latest</tag>
</tags>
</to>
<container>
<jvmFlags>
<jvmFlag>-XX:+UseContainerSupport</jvmFlag>
<jvmFlag>-XX:MinRAMPercentage=60.0</jvmFlag>
<jvmFlag>-XX:MaxRAMPercentage=90.0</jvmFlag>
<jvmFlag> -XshowSettings:vm</jvmFlag>
</jvmFlags>
<mainClass>com.demo.DemoApplication</mainClass>
</container>
</configuration>
SKAFFOLD.YAML
apiVersion: skaffold/v2beta1
kind: Config
metadata:
name: springtokube
build:
artifacts:
- image: registry.demo/springtokube
jib:
project: com.demo:springtokube
local:
push: true
concurrency: 1
useBuildkit: false
useDockerCLI: true
deploy:
kubectl:
manifests:
- deployment.yaml
ALSO SET INSECURE REGISTRY
skaffold config set --global insecure-registries registry.demo
But when using minikube I can run successfully
skaffold dev
When using other cluster (ON-PREM) I get
FATA[0016] exiting dev mode because first build failed: build failed: building [registry.demo/springtokube]: build artifact: getting image: GET http://registry.demo/v2/: : Not Found
What might be the problem?
I restarted today using kubectl context
skaffold debug --no-prune=false --cache-artifacts=false
And It Failed
Listing files to watch...
Generating tags...
- registry.demo/springtokube -> registry.demo/springtokube:cf60c31
Found [minikube] context, using local docker daemon.
Building [registry.demo/springtokube]...
.............
...............
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.294 s - in com.demo.springtokube.SpringtokubeApplicationTests
2020-04-15 08:45:48.277 INFO 30662 --- [extShutdownHook] o.s.s.concurrent.ThreadPoolTaskExecutor : Shutting down ExecutorService 'applicationTaskExecutor'
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] --- maven-jar-plugin:3.1.2:jar (default-jar) # springtokube ---
[INFO] Building jar: ....../springtokube/target/springtokube.jar
[INFO]
[INFO] --- spring-boot-maven-plugin:2.2.6.RELEASE:repackage (repackage) # springtokube ---
[INFO] Replacing main artifact with repackaged archive
[INFO]
[INFO] --- jib-maven-plugin:2.1.0:build (default-cli) # springtokube ---
[INFO]
[INFO] Containerizing application to registry.demo/springtokube:cf60c31, registry.demo/springtokube...
[WARNING] Base image 'openjdk:11-jre-slim' does not use a specific image digest - build may not be reproducible
[INFO] Getting manifest for base image openjdk:11-jre-slim...
[INFO] Building dependencies layer...
[INFO] Building resources layer...
[INFO] Building classes layer...
[INFO] Using credentials from Docker config (~/.docker/config.json) for registry.demo/springtokube:cf60c31
[WARNING] Cannot verify server at https://registry.demo/v2/. Attempting again with no TLS verification.
[WARNING] Cannot verify server at https://registry.demo/v2/springtokube/blobs/sha256:1fb3fb86aa52691fa3705554da5ba07dcb556f62a93ba7efab0e397ca3db092c. Attempting again with no TLS verification.
[WARNING] Cannot verify server at https://registry.demo/v2/springtokube/blobs/sha256:88a7d9887f9fdeb5a4736d07c64818453e00e71fe916b13f413eb6e545445a68. Attempting again with no TLS verification.
[WARNING] Cannot verify server at https://registry.demo/v2/springtokube/blobs/sha256:a6c851c4b90b9eb7af89d240dd4f438dba9feba5c78600fed7eadddf8cb7b647. Attempting again with no TLS verification.
[INFO] The base image requires auth. Trying again for openjdk:11-jre-slim...
[INFO] Using credentials from Docker config (~/.docker/config.json) for openjdk:11-jre-slim
[INFO] Using base image with digest: sha256:01669f539159a1b5dd69c4782be9cc7da0ac1f4ddc5e2c2d871ef1481efd693e
[INFO]
[INFO] Container entrypoint set to [java, -XX:+UseContainerSupport, -XX:MinRAMPercentage=60.0, -XX:MaxRAMPercentage=90.0, -XshowSettings:vm, -cp, /app/resources:/app/classes:/app/libs/*, com.demo.springtokube.SpringtokubeApplication]
[INFO]
[INFO] Built and pushed image as registry.demo/springtokube:cf60c31, registry.demo/springtokube
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 20.058 s
[INFO] Finished at: 2020-04-15T08:45:57+03:00
[INFO] ------------------------------------------------------------------------
Pruning images...
FATA[0024] exiting dev mode because first build failed: build failed: building [registry.demo/springtokube]: build artifact: getting image: GET http://registry.demo/v2/: : Not Found
I thought the minikube works. But disabling cache fails to build
if I run
skaffold debug OR skaffold dev
Works Fine
But if I run with cache disabled
skaffold debug --no-prune=false --cache-artifacts=false
FAILS it shows the logs above
After days of struggling I found a solution.
Following Brian de Alwis suggestions I was able to make Skaffold work with Self Signed Certificate.
Skaffold build or dev does not use certificate put in.
/etc/docker/certs.d/myregistrydomain.com/ca.crt
The path is used by docker client only.
The solution was to put yout registry certificate into
/usr/local/share/ca-certificates/myregistrydomain.com.crt
Then
update-ca-certificates
Check The link for more info
If you are using self signed certificate no need for insecure registry in your scaffold yaml file
apiVersion: skaffold/v2beta1
kind: Config
metadata:
name: springtokube
build:
# insecureRegistries:
# - myregistrydomain.com
Or Running skaffold with
skaffold dev --insecure-registry=myregistrydomain.com
Hope this help someone else struggling to make skaffold works with self signed certificate
When running the below command to deploy a springboot application, I endup getting Unauthorized error.
What config is missing?
mvn package dcos:uploadArtifact dcos:deployUCR
[INFO] --- dcos-maven-plugin:0.6-SNAPSHOT:uploadArtifact (default-cli) # springreactorcontext ---
[INFO] About to execute DC/OS pushArtifact.
[INFO] Uploading this file: /Volumes/data/projects/espre05/javanotes/springreactorcontext/target/springreactorcontext-1.0.jar
[INFO] Response from DC/OS [201]
[INFO]
[INFO] --- dcos-maven-plugin:0.6-SNAPSHOT:deployUCR (default-cli) # springreactorcontext ---
[INFO] About to execute DC/OS deployUCR
[INFO] app definition: /Volumes/data/projects/esp/javanotes/springreactorcontext/application.json
[INFO] legacy default app definition: /Volumes/data/projects/esp/javanotes/springreactorcontext/app-definition.json
[INFO] dcos token: /Volumes/data/projects/esp/javanotes/springreactorcontext/.dcos-token
[INFO] dcos url: http://172.17.0.3
[INFO] ignore ssl certificate: true
[INFO] deployable: EMPTY
[INFO] TempFile: /var/folders/86/9nj0h71j6kz9grdp6zkg2tkm0000gq/T/ucr-deploy14723186433955340084json
[INFO] Calculated url: http://172.17.0.3/service/marathon/v2/apps/springreactorcontext
[INFO] Response from DC/OS [401] <!DOCTYPE html>
<html>
<head>
<title>Unauthorized</title>
I'm using wso2 emm 2.2.0 Beta, Please refer the below error console. when I run the maven install I got maven assembly plugin issue.
So please let me know why it occurs? and give some suggestion to fix this problem.
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building WSO2 Mobile Device Manager (MDM) - Distribution 2.2.0-BETA2
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- incremental-build-plugin:1.3:incremental-build (default) # wso2emm ---
[INFO] Verifying module descriptor ...
[INFO] Verifying parent modules...
[INFO] Verifying resources...
[INFO] Resources directory does not exist : /home/next/Praveen/Project/secureON/Project/Project_Setup/product-emm-2.2.0-BETA2/modules/distribution/src/main/resources
[INFO] Verifying sources...
[INFO] No sources to check ...
[INFO]
[INFO] --- buildnumber-maven-plugin:1.3:create (default) # wso2emm ---
[INFO] Storing buildNumber: 27 Oct 2016 at timestamp: 1477554746130
[WARNING] Cannot get the branch information from the git repository:
Detecting the current branch failed: fatal: Not a git repository (or any of the parent directories): .git
[INFO] Executing: /bin/sh -c cd /home/next/Praveen/Project/secureON/Project/Project_Setup/product-emm-2.2.0-BETA2/modules/distribution && git rev-parse --verify HEAD
[INFO] Working directory: /home/next/Praveen/Project/secureON/Project/Project_Setup/product-emm-2.2.0-BETA2/modules/distribution
[INFO] Storing buildScmBranch: UNKNOWN_BRANCH
[INFO]
[INFO] --- maven-remote-resources-plugin:1.5:process (default) # wso2emm ---
[INFO]
[INFO] --- maven-assembly-plugin:2.4:single (1-pre-dist) # wso2emm ---
[INFO] Reading assembly descriptor: /home/next/Praveen/Project/secureON/Project/Project_Setup/product-emm-2.2.0-BETA2/modules/distribution/src/assembly/dist.xml
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.203s
[INFO] Finished at: Thu Oct 27 13:22:26 IST 2016
[INFO] Final Memory: 13M/188M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.4:single (1-pre-dist) on project wso2emm: Failed to create assembly: Error creating assembly archive dist: You must set at least one file.
If you want to build WSO2 EMM 2.2.0 Beta follows the below steps.
Clone the product-emm repo
git clone https://github.com/wso2/product-emm.git
Checkout the v2.2.0-BETA tag.
git checkout v2.2.0-BETA
Build from root pom. Go to project root folder and issue
mvn clean install
If you want just product zip you can build the distribution module for that go to project root -> modules ->distribution folder and issue mvn clean install from there. you can find the build zip file in distribution/target folder.
It seems like you are in master branch. The failing maven goal for you added after the emm beta tag creation. The reason for failing is, in build time it tries to connect to some resources in internet and your computer failed to connect to that resources on internet. If you really want to build the master branch (2.2.0-SNAPSHOT), just check your internet connection or firewall blockings.